Centralized contracting allows a central purchasing organization to establish a contract with a supplier that is not specific to a single plant. This allows the purchasing organization to negotiate with a supplier using the requirements of the entire company for specific materials or services. Unlike facility-specific contracts, you can create different conditions for different placements for partners. As part of the SAP MM purchase, these agreements are divided into “contracts” and “delivery plans”. In the case of value contracts, the total value of all decommitment orders issued against the contract must not exceed a certain amount. In the contract head data, you must mention the target value in addition to the validity period. You can also enter the target quantities of the material. The contract will be respected once the overall objective has been achieved. The following figure shows a value contract, called by Operation ME33K: The framework sales contract is often referred to as a framework or roof order. It is essentially a long-term agreement between the procurement department and the supplier of equipment or services for a defined period of time.
The purchasing department negotiates with the supplier a number of conditions for the duration of the contract. At the time of setting up the hardware base, you must keep purchase and accounting data if the contract position is a storage position. 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: distributed contracts are centrally concluded contracts. You can create a contract in an SAP system and then make it available to other independent SAP systems. This means that the treaty will be distributed among other systems. All SAP systems are independent and the data we need to be must be identical to each system. Data exchange is carried out via Application Link Enabling (ALE) for continuous comparison and comparison of changes. The release documentation for the contract position is updated for each order item, which is then established in connection with a contract. M (Unknown Material) and W (Material Group) are contract-specific position categories that constitute contractual agreements for a group of materials in which you can record contractual positions without a hardware base specification. In the volume contract, the total quantity of each item to be ordered is available for the period covered by the contract. After entering the validity period, you must record the target quantity at the position level.
In this type of contract, the contract is fulfilled when an objective set by contractual position is achieved. The terms of a framework contract apply up to a specified period and cover a certain quantity or predefined value. 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. Purchasing organizations and centralized contracts Things are getting exciting (at least for data analysts): framework contracts such as volume contracts, value contracts and delivery plans are not stored in their own tables, but also in the EKKO and EKPO tables. Don`t be confused by names or take them to the letter. Step 2 – Indicate the number of the delivery plan. The contract does not contain any specific delivery date or individual delivery quantities….