Sap Scheduling Agreement Tables

Try so, I hope the planning details are stored in the VBEP table, then get the vbeln from there and get the status data record I don`t need to retrieve the packaging types of the delivery plan. As a general rule, the objective of framework agreements is to set 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. We know that there is a BadI (“Sales Scheduling Agreement Delivery Schedule Check”) that allows us to define customer checks for delivery plan delivery data. I hope that you have enjoyed addressing the issue of framework agreements and that we will soon meet again for the second part of the “Call Agreements”. Agreements are now at the origin of a long-term structured procurement process. But what about individual buying on the concrete basis of an agreement? We are also talking about call-offs. These are specific specific markets, in reference to the framework agreement. How you can determine these searches by analyzing the data, the tables in which they are recorded, and whether the information about goods and invoices is relevant or relevant in this context – this is something for the next post in the series.

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). I don`t want a BAPI for that. I just need a query between tables. 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. Now it`s becoming exciting (at least for data analysts): framework agreements such as quantity 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. To create a context, we start with ordinary tasks: as far as the database is concerned, these are stored in SAP® in the tables EKKO (command head) and EKPO (command position).