Writer & Editor

Sap Outline Agreement Header Table

In Uncategorized on October 6, 2021 at 11:22 am

The agreements laid the foundation for long-term structured procurement. But concretely, what is the individual purchase on the basis of an agreement? Here too, we talk about “call-offs”. These are specific specific contracts, with reference to the framework agreement. How you can identify these searches through data analysis, in which tables they are recorded, and whether the entries of goods and invoices are relevant or relevant in this context, this is something for the next blog post in the series. Framework contract is a long-term sales contract between the supplier and the customer. There are two types of framework agreements: a release order is an order (or an order request from which an order is then generated) with a reference to a framework agreement. This is important because it is good to know that, initially, at least for statistics relating to release orders in sap®, tracking operations, such as entries of goods and invoices, play no role in logging. Statistics (i.e. transaction view and data view) display a quantity or value as a release order as soon as the order has been placed. Even if there is ultimately no delivery (and/or receipt of goods) or receipt of invoices, this release order documentation first shows a reduction in the residual quantity/value. This is also shown in the EKAB table, as it contains only the order quantity and net order value as fields, but no information about entering or receiving invoices.

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, important contracts (e.g. purchase of laptops throughout the group) are often negotiated centrally and can then be used in a decentralised manner. In this case, it is possible to work with almost superior purchasing organizations, which are attached to decentralized purchasing organizations as a reference purchasing organization. The latter can then use and retrieve framework contracts drawn up under the reference purchasing organisation. From the point of view of the data analyst, you will find the assignment of purchasing organizations (field: T024Z_EKORG) to possible reference purchasing organizations (box T024Z_EKORZ) in Table T024Z.

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. By clicking on the hat icon (the header data – remember?), you get to where the target value of the contract is also visible (in this case, of course, the sum of the two items). I will now take a closer look at the objectives at the position and head level in the framework agreements. Now it will be 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. . . .