Data Model: Orders and Framework Contracts On this blog, I want 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. The EKAB table is therefore a good starting point for our unlocking missions. 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. Now that we have discovered where framework agreements are held as data – in tables where « standard » commands are suspected – and how to identify them – by document type and document type – we now look at some aspects of the process. I hope that these two blog posts on the topic of framework agreements have been useful. Please send us your feedback if you have any questions or comments or if you may see things differently in professional practice. 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. 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.
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. assign attributes to document types that are then used to organize/control processes in a system. You can also find them in the EKKO table, the field name is EKKO_BSART. Delivery plans, on the other hand, are more focused on quantities, but also on the concrete quantities delivered on certain delivery dates (we speak of classifications). One could easily say that these are more binding quantitative contracts – but in the analysis of data at SAP® they appear separately with a separate category of supporting documents compared to volume or value contracts. But later. 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 an unlock order is usually recorded as soon as the order indicates it, regardless of the goods and invoices.. . . .