The offer, order, SA and contract were registered in ekko and EKPO Table. To create a context, we start with ordinary tasks: as far as the database is concerned, these are stored in SAP® in the tables EKKO (command head) and EKPO (command position). If you want to track it, you can use z.B. the table browser SE16 to view the contents of the table. Contracts are often superior in nature. This may be the case with SAP® because the buying organization is essential (and the work that may be related to the purchase organization). The purchase organization is shown in the EKKO table for each agreement (field: EKKO_EKORG). However, in high-demand structures, large contracts (for example. B the purchase of laptops throughout the company) are negotiated centrally and can then be used in a decentralized manner. In this case, it is possible to cooperate with near-superior purchasing organizations, which are attached to decentralized purchasing organizations as a reference purchasing organization. They can then use and consult framework agreements established under the reference purchasing agency. From the data analyst`s perspective, you will find in table T024Z the allocation of purchasing organizations (field: T024Z_EKORG) to possible business reference organizations (field: T024Z_EKORZ). As a general rule, the objective of framework agreements is to set a ceiling or a total volume (i.e.

a target value). For quantity contracts that are very specific to individual materials and therefore often related to a material number (field: EKPO_MATNR), because the number of parts or the number of parts play an important role here (although there are other possibilities. B for an unknown material or consumables that I will not study here). This is why the target value here is at the level of the respective contract position, since the target quantity (field: EKPO_KTMNG) multiplied by the price of the material in question gives the reference value (field: EKPO_ZWERT) of each item. From a risk point of view, the Framework Agreements theme offers a number of fascinating starting points for reflection, including: clicking on the hat symbol (which recalls head data?) you arrive where the target value of the contract is visible (in this case, of course, the sum of the two points). I will now take a closer look at the target values for articles and heads in framework agreements. You can clearly display the category (K or L) and the type of document associated (LP, WK, MK). Our system includes 154 agreements. We are in the process of creating change BDCs in which we do not get the table in which the data is stored.

It`s a little more technical, but here, for the sake of completeness, a screenshot of the document type table with customizing settings in SAP® if they are needed for data analysis purposes. Numbering circuits for the corresponding types of proofs, for example. B Field selection parameters, etc., are included in this table: the above voucher categories are assigned as an attribute to each supporting piece in the EKKO head data table (field EKKO_BSTYP). This means that the document category allows us to distinguish delivery plans from other contracts. But how do you distinguish value contracts from volume contracts? This is where the storm table described above comes in: in the standard, the type of contract “MK” is for volume contracts and “WK” for value contracts.