This blog post explained how to identify framework contract sharing orders in SAP® with SAP® transactions such as SE16 and ME33K, and how the process is recorded from a data perspective – i.e. via the attributes of the EKKO/EKPO and in the EKAB publication order documentation table. It showed that a release order is usually recorded as soon as the order indicates it, regardless of the inflows of goods and invoices. The order number and its relationship to the corresponding framework contract (more precisely the position of the contract, consisting of a proof number and a proof position) are documented. We can now see how a total of four control posts relate to our contractual position, but only one resulted in a release order – the first three positions have the L license plate as an attribute. A contract is a long-term framework contract between a supplier and a customer for a predefined hardware or service over a specified period of time. There are two types of contracts: the EKAB table is therefore a good starting point for our unlocking missions. But it`s also worth noting that in addition to the hiding place in a separate table, lists of contract sharing orders can also be generated as part of data analysis on the initial order tables (see EKKO/EKPO in the first blog post). For example, the EKPO (control items) table also displays the KONNR and KTPNR fields (contract number and contract position). For order positions relating to a contract (more specifically a contractual position), these contain the corresponding contract number and the position values of the contract. The delivery plan is a long-term sales contract with the supplier in which a supplier is required to supply material on specified terms. information on the delivery date and quantity communicated to the supplier in the form of the delivery plan.
Step 2 – Indicate the name of the supplier, the type of contract, the purchasing organization, the purchasing group and the factory as well as the date of the agreement. If you are using the value contract, make sure that you are not maintaining a target quantity in the contract position. Otherwise, the default alert message 06078 was displayed. Remember that for value contracts, the contract quantity should not be maintained, except for the target value. Otherwise, the quantity contract will be used instead. Volume contract – For this type of contract, the total value is indicated in relation to the total quantity of materials to be delivered by the supplier. If the target contract value is exceeded, SAP populates a standard message 06,042. However, the examination does not take place if the order is established with several positions for which the totals exceed the target value. For example, the target value of your order has been set at AUD 10,000 and the first release order has been established for a total value of AUD 8,000.
If a new release order is created with several items, each with a value of less than AUD 2,000 (= 10,000 – 8,000) but the total value of each item is greater than AUD 2,000, the message is not displayed. From a risk perspective, the theme of framework contracts offers a number of exciting starting points, including: Supplier selection is an important process in the procurement cycle.. . . .