Agreement Number Sap

As a general rule, the objective of framework agreements is to set a ceiling or a total volume (i.e. a target value). For quantity contracts that are very specific to individual materials and therefore often related to a material number (field: EKPO_MATNR), because the number of parts or the number of parts play an important role here (although there are other possibilities. B for an unknown material or consumables that I will not study here). This is why the target value here is at the level of the respective contract position, since the target quantity (field: EKPO_KTMNG) multiplied by the price of the material in question gives the reference value (field: EKPO_ZWERT) of each item. Agreements are now at the origin of a long-term structured procurement process. But what about individual buying on the concrete basis of an agreement? We are also talking about call-offs. These are specific specific markets, in reference to the framework agreement. How you can determine these searches by analyzing the data, the tables in which they are recorded, and whether the information about goods and invoices is relevant or relevant in this context – this is something for the next post in the series. Contracts are often superior in nature. This may be the case with SAPĀ® because the buying organization is essential (and the work that may be related to the purchase organization).

The purchase organization is shown in the EKKO table for each agreement (field: EKKO_EKORG). However, in high-demand structures, large contracts (for example. B the purchase of laptops throughout the company) are negotiated centrally and can then be used in a decentralized manner. In this case, it is possible to cooperate with near-superior purchasing organizations, which are attached to decentralized purchasing organizations as a reference purchasing organization. They can then use and consult framework agreements established under the reference purchasing agency. From the data analyst`s perspective, you will find in table T024Z the allocation of purchasing organizations (field: T024Z_EKORG) to possible business reference organizations (field: T024Z_EKORZ). For the sake of completeness, a screenshot of a value contract bearing the document number 46000003030 is presented below; The statistics on release orders for Article 20 are similar: the corresponding order number and its relation to the corresponding framework agreement (specifically the contractual position, including the proof number and the proof post) are documented. We can now see how four command positions relate to our contractual position, but only one has resulted in a sharing order – the first three items have the L deletion mark as an attribute. Step 4 – Indicate delivery date and target quantity. Click Save. The planning lines are now maintained for the delivery plan. It is interesting to note that although the publication order statistics show a total of four supporting documents, the cumulative total for the first three is 0.

Only the last order with the order number 4500017169 and Article 10 contains an order of 2 tons, reducing the amount of open target from 250 to 248 tons. Now it`s becoming exciting (at least for data analysts): framework agreements such as quantity contracts, value contracts and delivery plans are not stored in their own tables, but also in the EKKO and EKPO tables. So don`t get confused by names or take them too literally. The framework agreement is a long-term sales contract between Kreditor and Debitor.