Sap Outline Agreement Document Type

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. In the SAP system® itself. B you can access the call documentation in the ME33K transaction using the histogram icon and get information about what has already been published. 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. Let`s start with examples of different types of framework agreements. Here`s what I`ll see: Supplier selection is an important process in the supply cycle. Creditors can be selected based on the bidding process. After pre-selecting a creditor, an organization enters into an agreement with the latter to provide certain items subject to certain conditions. When an agreement is reached, a formal contract is usually signed with the Kreditor. A framework agreement is therefore a long-term purchase agreement with a creditor.

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). 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 classic relational data model avoids redundancy in . B data is divided into head and article data for supporting documents and transactions. In the head of the room, you will find data valid for the entire document (and all the elements). In a conventional order scenario, the occupancy head contains attributes such as creditor, probation, order date and payment terms. On the other hand, the current data on order positions are the order quantity, the category of goods, the material number and the price.