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. I hope these two blog posts on framework agreements have been helpful. Please send us your comments if you have any questions or comments, or perhaps see things differently in professional practice. 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. By clicking on the hat icon (which recalls the head data -?) you get to where the target value of the contract is visible (in this case, of course, the sum of the two elements). I will now take a closer look at the target values for articles and heads in framework agreements. Orders to unlock value and quantity contracts are included in a separate table called EKAB.

SAP® SE16 transaction can be used to display items. The screenshot below shows the release commands in the EAKB table, filtered by “our” quantity contract 46000000062 of the first example. Pls tells me what is the table used to store the data of the framework agreements The relevant order number and its relationship with the corresponding framework agreement (specifically: the position of the contract, including the voucher 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. In my last blog, I explained some framework agreements (value and quantity contracts as well as delivery plans) in SAP®. In this blog, I would like to give you an overview of the framework agreements in SAP® in the purchase module. In addition to the design of the concept itself, I give you an overview of its assignment from the point of view of data analysis, that is, SAP® tables and field levels. The delivery plan is a long-term sales contract with the Kreditor, in which a creditor is required to provide equipment on pre-determined terms. Details of the delivery date and the amount communicated to the creditor in the form of the delivery plan.

To return to standard commands, you can use z.B the ME23N transaction. T-code ME33K shows you contracts, and ME33L is correct for delivery plans. You can see that the category of Mnemonics K and L vouchers also appears in part in bookings. The framework agreement is a long-term sales contract between Kreditor and Debitor. To be complete, the screenshot below shows the EKAB table for the 460000003030 value contract in example 2.