The terms of a framework contract apply up to a specified period and cover a certain quantity or predefined value. The path to creating a delivery plan – Logistics → materials sector → purchase → framework contract → delivery plan → → Vendor Known. 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 searches through 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. Let`s start with examples of different types of framework agreements. Here`s what I`m looking at: the above categories of supporting documents are assigned as attributes 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 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. 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 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). . . .