Pls tell me what are the tables used to store data from the framework agreements Planning agreements are more quantity-based, and in addition to the actual quantities delivered on certain delivery dates (we are talking about calendar lines). Quite simply, these are more restrictive quantitative contracts - but in the analysis of the data in SAP® they appear separately with their own category of supporting documents in relation to volume or value contracts. But later. From a risk point of view, the Framework Agreements theme offers a number of fascinating starting points for reflection, including: clicking on the hat symbol (which recalls head data?) you arrive where the target value of the contract is visible (in this case, of course, the sum of the two points). I will now take a closer look at the target values for articles and heads in framework agreements. For the sake of completeness, the screenshot below shows the EKAB table for the 4600000030 value order of example 2. Release orders can be identified in the same way: this means that, in both areas, our contract to unblock example 1 with the purchase number 4500017169 and Article 10 contains the content "4600000062" (contract number to be released) and "10" (contract article). This EKPO table also displays the three commands that were placed on "deleted" and therefore did not result in release orders. 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. To create a context, we start with ordinary tasks: as far as the database is concerned, these are stored in SAP® in the tables EKKO (command head) and EKPO (command position). If you want to track it, you can use z.B. the table browser SE16 to view the contents of the table. A share order is an order (or order request from which an order is generated) with a reference to a framework agreement. This is important because it is good to know that at least for SAP`s marketing authorization statistics® subsequent transactions, such as inflows of goods and invoices, play no role in the first step.