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.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. terminate contracts are drawn up by reference to a centrally agreed contract, under which materials are purchased on specific dates within a specified period. The main difference is that contracts do not have a schedule position, but the delivery plan will have schedule positions. On this blog, I would like to give you an overview of framework contracts in SAP® 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. The figure below shows a value contract that is called through the ME33K transaction: The contract does not have predefined delivery dates. First of all, you need to create a contract, and in this regard, you need to create a lot of orders (i.e. release orders) that are based on each time you need to create a delivery until the contract expires. 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. .