Fig. 1 – Viewing call statistics for a contractual position On this blog, I would like to give you an overview of SAP`s framework agreements® in the Purchasing module. In addition to the sketch of the concept itself, I give you an overview of the image from the point of view of data analysis, in other words SAP® tables and field plan. A framework agreement can consist of the following two types: in many areas® SAP follows a concept of document category and document type. The class of record is a rough classification, the type of document is the finer differentiation of the class of record. When analyzing an order scenario, the above four categories of supporting documents may be of interest to you: 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.
A contract is a long-term framework contract between a supplier and a customer for a predefined hardware or service over a specified period of time. There are two types of contracts: it is often in the interest of the purchasing unit to concretize over a long period of time conditions of materials or services that are regularly necessary and / or a large volume. During negotiations, it may be possible to agree on discounts and special conditions that do not apply to one-off orders. Step 2 – Indicate the number of the delivery plan. Requirements planning can be established in such a way that the contract position is automatically linked to an order position as a source of supply. However, this requirement must be converted a posteriori into an order (contract release order). As for the delivery plan, it is possible to directly generate delivery plan positions from the planning run and thus reduce the processing time of the purchasing department.