Sap Outline Agreement Configuration

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). A framework contract is a long-term sales contract with a creditor that contains terms and conditions for the equipment to be provided by the creditor. The main points to remember in the framework agreement are: the framework agreement is a framework long-term purchase agreement between the lender and the debtor. The structure agreement is two types: you can clearly display the category (K or L) and the corresponding occupant (LP, WK, MK). Our system includes 154 agreements.

The terms of a framework agreement apply up to a specified period of time and cover a certain pre-defined amount or value. 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. The above voucher categories are assigned as attributes to each purchase proof in the EKKO head data table (field: EKKO_BSTYP). This means that the document category allows us to distinguish delivery plans from other contracts. But how do you distinguish value contracts from volume contracts? This is where the storm table described above comes in: in the standard, the type of contract “MK” is for volume contracts and “WK” for value contracts. However, both types of documents have the same category of “K” document. While document categories are primarily used for categorization, document types are often used to customize, i.e. attributes are assigned to document types, which are then used to organize the process/control process in a system.

You can also be in the EKKO table, the field name is EKKO_BSART. This is due to the organizational structure, reference purchasing organization, configurations, basic data, etc.

SimaGrafik