Agreement Header Table In Sap

In this blog, I would like to give you an overview of the framework agreements in SAP® in the purchase module. In addition to the design of the concept itself, I give you an overview of its assignment from the point of view of data analysis, that is, SAP® tables and field levels. 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. 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. In the sap purchase component, a kind of framework agreement or longer-term purchase agreement. The contract is a binding obligation to purchase a particular equipment or service from a supplier for a period of time. Framework agreements are an important issue that we must constantly address in our analysis of procurement data. Unlike individual contracts, which are often ad hoc, framework agreements are constructs for a longer-term business relationship. Another type of framework agreement or longer-term purchase agreement. Delivery plans include delivery plans for purchase quantities, delivery dates and possibly specific delivery times over a pre-defined period.

Table T166P SAP for – Article texts in command prints To create context, we start with unique commands: for the database, these are stored in SAP® in the EKKO (Command Head) and EKPO (Command Position) tables. If you want to track it, you can use z.B. the table browser SE16 to view the contents of the table. If we add types of proofs to our table above, the situation is this (this time I omitted the categories of proofs and the types of proofs that are not relevant to the contract: another type of purchase are the order requirements.

Comments are closed.