For value contracts, the quantity of items is often secondary, as the total value of the order 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. 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. Fig. 4 – Release order documentation for a volume contract in the EKAB table The terms of a framework contract apply up to a certain period and cover a certain quantity or predefined value. 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.

A delivery plan is a long-term framework contract between the supplier and the customer for predefined material or service that is provided on predefined dates within a time frame. A delivery plan can be drawn up in two ways: a framework contract can consist of the following two types – so the EKAB table is a good starting point for our unlocking markets. But it`s also worth noting that in addition to the hiding place in a separate table, lists of contract sharing orders can also be generated as part of data analysis on the initial order tables (see EKKO/EKPO in the first blog post). For example, the EKPO (control items) table also displays the KONNR and KTPNR fields (contract number and contract position). For order positions relating to a contract (more specifically a contractual position), these contain the corresponding contract number and the position values of the contract. The above categories of supporting documents are assigned to each purchase receipt in the EKKO head data table as an attribute (field: EKKO_BSTYP). This means that the class of documents allows us to distinguish delivery plans from other contracts. But how to distinguish value contracts from volume contracts? This is where the type of evidence described above begins: in the standard is the type of proof „MK“ for volume contracts and „WK“ for value contracts. However, both types of records have the same class of „K“ records. While document categories are primarily used for categorization, document types are often used to customize them, i.e.

attributes are assigned to document types that are then used for organizing/managing processes in a system. You can also find them in the EKKO table, the field name is EKKO_BSART. 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. This blog post explained how to identify framework contract sharing orders in SAP® with SAP® transactions such as SE16 and ME33K, and how the process is recorded from a data perspective – i.e. via the attributes of the EKKO/EKPO and in the EKAB publication order documentation table. It showed that a release order is usually recorded as soon as the order indicates it, regardless of the inflows of goods and invoices. As I have already said, I shall now look at the contracts for the release of a framework agreement. I`ll first briefly explain how to replay them to SAP® before moving on to the data situation.


Categories: Allgemein