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. 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. 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). 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. 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. I can tell myself the T code so I can see a list of contracts. z.B. how we see purch req list in ME5A. Contracts are often of a higher nature. This may be the case at SAP® since the purchasing organization is essential (and which can be linked to the purchasing organization). The purchasing organization appears in the EKKO table for each agreement (box EKKO_EKORG). However, in group structures, large contracts (e.g. purchase of laptops throughout the group) are often negotiated centrally and can then be used in a decentralized manner.