Data model – orders and framework agreements Futures contracts are in turn based more on quantities and, beyond that, on concrete quantities of delivery on certain delivery dates (referred to as timing). 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. In value contracts, the quantity of items is often secondary, since the total value of the contract counts. For example, a “facility management” contract of 1,000,000 euros could be concluded with a supplier. This includes the three building cleaning, repair and disposal items. In this case, individual quantities can be attributed in a much less concrete way and an overall structure is more judicious. Another example would be office equipment (pens, post-it notebooks), too “singular” in individual articles to be punished in a framework agreement. 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. Now that we have discovered where the framework agreements are kept as data — in tables where you actually suspect standard commands — and how to identify them — by document category and document type — let`s look at some aspects of the process. You can clearly display the category (K or L) and the type of document associated (LP, WK, MK).
Our system includes 154 agreements. In the case of value contracts where different un quantified positions are often added to a cumulative value of the contract, which is then determined at the level of the occupancy head (EKKO_KTWRT). Since different quantities per item (and therefore target quantities) tend to play a minor or not at all, and are often used for services, etc., you will probably find a definition at the level of material groups (field: EKPO_MATKL). 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. 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. 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.