To refer to default commands, you can use z.B. the ME23N transaction; T-Code ME33K shows you contracts, and ME33L is the right thing to do for delivery plans. You can see that the category of supporting documents Mnemonik K and L is also present in part in the transactions. An SAP table for – Purchase information kit: The dates of organization of purchase of his EKPO, just give the agreement no and you will find the net price if the item. It`s a bit more technical, but to be complete, it`s a screenshot of the document type table with customizing settings in SAP® if they`re needed for data analysis purposes. This table contains circles of numbers for the corresponding document types, for example.B. Field selection settings, etc. 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 RFQ, the order, the SA and the contract were recorded in the EKKO and EKPO table. 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. VLPKM is a standard SAP table used for setting up delivery plans based on customer data and available in R/3-SAP systems based on version and output level. 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. Table T166P SAP for – Position Texts in Purchase Printouts The above supporting document categories are assigned to each purchase receipt in the EKKO Head Data Table (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 mainly used for categorization, document types are often used to customize them, that is: document types are assigned to attributes 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. The agreements laid the foundation for long-term structured procurement. But concretely, what is the individual purchase on the basis of an agreement? Here too, we talk about “call-offs”. These are specific specific contracts, with reference to the framework agreement. How you can identify these calls by data analysis, in which tables they are recorded and whether the entries of goods and invoices are relevant or relevant in this context – this is something for the next blog post in the series….