Futures agreements, on the other hand, are based more on quantities and, in addition, on concrete quantities of delivery on certain delivery dates (we are talking about dates). Quite simply, these are more restrictive quantitative contracts – but in the analysis of the data in SAP® they appear separately with their own category of supporting documents in relation to volume or value contracts. But later. In the case of value contracts where different un quantified positions are often added to a cumulative value of the contract, which is then determined at the level of the occupancy head (EKKO_KTWRT). Since different quantities per item (and therefore target quantities) tend to play a minor or not at all, and are often used for services, etc., you will probably find a definition at the level of material groups (field: EKPO_MATKL). Step 2 – Include the delivery plan number. By clicking on the hat icon (which recalls the head data -?) you get to where the target value of the contract is visible (in this case, of course, the sum of the two elements). I will now take a closer look at the target values for articles and heads in framework agreements. A framework contract is a long-term sales contract with a creditor that contains terms and conditions for the equipment to be provided by the creditor. Step 4 – Indicate delivery date and target quantity.
Click Save. The planning lines are now maintained for the delivery plan. Let`s start with examples of different types of framework agreements. Here`s what I`m going to see: Contracts are often superior in nature. This may be the case with SAP® because the buying organization is essential (and the work that may be related to the purchase organization). The purchase organization is shown in the EKKO table for each agreement (field: EKKO_EKORG). However, in high-demand structures, large contracts (for example. B the purchase of laptops throughout the company) are negotiated centrally and can then be used in a decentralized manner. In this case, it is possible to cooperate with near-superior purchasing organizations, which are attached to decentralized purchasing organizations as a reference purchasing organization. They can then use and consult framework agreements established under the reference purchasing agency. From the data analyst`s perspective, you will find in table T024Z the allocation of purchasing organizations (field: T024Z_EKORG) to possible business reference organizations (field: T024Z_EKORZ).
Now that we have discovered where the framework agreements are kept as data — in tables where you actually suspect standard commands — and how to identify them — by document category and document type — let`s look at some aspects of the process. In value contracts, the quantity of items is often secondary, since the total value of the contract counts. For example, a “facility management” contract of 1,000,000 euros could be concluded with a supplier. This includes the three building cleaning, repair and disposal items. In this case, individual quantities can be attributed in a much less concrete way and an overall structure is more judicious. Another example would be office equipment (pens, post-it notebooks), too “singular” in individual articles to be punished in a framework agreement. The framework agreement is a long-term sales contract between Kreditor and Debitor. The structure agreement consists of two types: a contract is a longer-term agreement with a creditor (one of the two types of framework agreement in the SAP system) to provide equipment or provide a service for a fixed period.