Sap Contract Agreement Table

Step-2 Enter the contract`s end date in the head data screen. The framework agreement is a long-term sales contract between Kreditor and Debitor. Structural agreements are two types: contracts are often superior. 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). From a risk perspective, the theme of framework agreements offers a number of fascinating starting points, among others: Table T166P SAP for – Articles in the purchase documents I hope these two blogs on framework agreements have been useful. Please send us your comments if you have any questions or comments, or perhaps see things differently in professional practice. 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 means that, in both areas, our contract relaxation mandate has content “4600000062” (contract number to be published) and “10” (contract article) from example 1 with the purchase number 4500017169 and article 10. This EKPO table also displays the three commands that were placed on “deleted” and therefore did not result in release orders. 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). If you want to track it, you can use z.B. the table browser SE16 to view the contents of the table. The EKAB table is therefore a good starting point for our unlocking missions. It is also interesting to note that in addition to the location in a separate table, lists of contract-sharing mandates can be generated as part of data analysis on the original control boards (see EKKO/EKPO in the first blog post). The EKPO table (command positions). B also shows the KONNR and KTPNR fields (contract number and contract position).