The framework agreement is a long-term sales contract between Kreditor and Debitor. The structure agreement consists of two types: the data model – orders and framework agreements The relevant order number and its relationship to the corresponding framework agreement (specifically the contract item, consisting of the proof number and the proof post) are documented. We can now see how four command positions relate to our contractual position, but only one has resulted in a sharing order – the first three items have the L deletion mark as an attribute. Contract The contract is a draft contract, and they do not contain delivery dates for the equipment. The contract is of two types: it now becomes exciting (at least for data analysts): framework agreements such as volume contracts, value contracts and delivery plans are not stored in their own tables, but also in the EkKO and EKPO tables. So don`t get confused by names or take them too literally. The main points to remember in a framework agreement are usually the objective of the framework agreements, a ceiling or a total volume (i.e. a target value). For quantity contracts that are very specific to individual materials and therefore often related to a material number (field: EKPO_MATNR), because the number of parts or the number of parts play an important role here (although there are other possibilities. B for an unknown material or consumables that I will not study here). This is why the target value here is at the level of the respective contract position, since the target quantity (field: EKPO_KTMNG) multiplied by the price of the material in question gives the reference value (field: EKPO_ZWERT) of each item. 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). The delivery plan is a long-term sales contract with the Kreditor, in which a creditor is required to provide equipment on pre-determined terms. Details of the delivery date and the amount communicated to the creditor in the form of the delivery plan. 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. I hope these two blog posts on framework agreements have been helpful. Please send us your comments if you have any questions or comments, or perhaps see things differently in professional practice.
As I have said before, I will now look at the mandates to unblock the framework agreement. First, I will briefly explain how they are looking for sap® before moving on to the data situation.