> Mike Cook Portfolio » Sap Table Outline Agreement

Sap Table Outline Agreement

Posted on Oct 6, 2021 in Uncategorized

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. Step 4 – Indicate the delivery date and target quantity. Click Save. For the delivery plan, classifications are now maintained. The delivery plan is a long-term sales contract with the supplier in which a supplier is required to supply material on specified terms. information on the delivery date and quantity communicated to the supplier in the form of the delivery plan. To create context, we start with normal unique commands: as far as the database is concerned, they are recorded in SAPĀ® in the EKKO (command head) and EKPO (command position) tables. For example, if you want to track, you can use the SE16 browser to view the contents of the table. 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. 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. A delivery plan is a long-term framework contract between the supplier and the customer for predefined material or service that is provided on predefined dates within a time frame. A delivery plan can be established in two ways: the objective of framework contracts 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 the number of parts or units here plays an important role (even if it exists, for example. B for an unknown material or consumer, other possibilities that I will not discuss here). . . .