To create context, we start with normal unique commands: as far as the database is concerned, they are recorded in SAP® in the EKKO (command head) and EKPO (command position) tables. For example, if you want to track, you can use the SE16 browser to view the contents of the table. You can clearly see the category (K or L) and the associated document type (LP, WK, MK). Our system includes a total of 154 contracts. On this blog, I would like to give you an overview of framework contracts in SAP® in the Purchasing module. In addition to the sketch of the concept itself, I give you an overview of the image from the point of view of data analysis, in other words SAP® tables and field plan. Data Model: Orders and Framework Contracts For value contracts, the quantity of items is often secondary, as the total value of the contract matters. For example, a facility management contract of €1,000,000 can be concluded with a supplier. This includes the three points of building cleaning, possible repairs and disposal. In this case, individual sizes can be assigned much less concretely, and an overall construction makes more sense. Another example would be office equipment (pens, post-it notepads) that is too “singular” at the room level to be defined in a framework agreement.
By clicking on the hat icon (the header data – remember?), you get to where the target value of the contract is also visible (in this case, of course, the sum of the two items). I will now take a closer look at the objectives at the position and head level in the framework agreements. In the case of value contracts, the different uns quantified positions often add up to a cumulative contract value, which is then set at the aqueous head (EKKO_KTWRT). . . .