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. 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. 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. Therefore, if we add document types to our table below, it looks like this (this time I omitted the categories of documents and the types of documents that are not related to the contract: these are the tables in which all purchase receipts, including framework contracts, are recorded. The traditional relational data model avoids redundancy, for example by dividing the data on supporting documents and transactions into head and position data. In the head of the supporting document, you will find data valid for the entire document (and all positions).
In a typical order scenario, the proof head contains attributes such as creditor, reference currency, order date, and payment terms. In contrast, the current order position data is the order quantity, product type, material number, and price. The objective of framework agreements is usually to set a ceiling or a total volume (i.e. a target). For quantitative contracts, this is very specific to individual materials and therefore often to a material number (box: EKPO_MATNR), because.B this is where the number of parts or units plays an important role (even if there are other possibilities for an unknown material or consumer, but I will not come back to it here). For this reason, the reference value must be found at the level of the contractual position, because the target quantity (box: EKPO_KTMNG) multiplied by the price of each material gives the reference value (box EKPO_ZWERT) of each position. Orders for the release of a framework agreement for value and volume contracts are, among other things, included in a separate table called EKAB. .
. .