Sap Contract Agreement Tableadmin
As the name suggests, volume contracts are usually concluded for specific target quantities of specific products or materials, for example. B for a contract item called “1000 engines.” This means — if a quantity contract contains different positions — that the target quantities (and therefore the monetary values) are differentiated by post. Second, our contract could include “2000 special valves.” Purchasing organizations and centrally agreed contracts For our value contract, we were of course able to follow this in the EKPO by filtering on the basis of KONNR – 46000003030; But I`m not going to show this screenshot here. The offer, order, SA and contract were registered in ekko and EKPO Table. A share order is an order (or order request from which an order is generated) with a reference to a framework agreement. This is important because it is good to know that at least for SAP`s marketing authorization statistics® subsequent transactions, such as inflows of goods and invoices, play no role in the first step. In the statistics (i.e. in the view of the booking and also in the view of the data), a quantity or value is displayed as a shared order once the order is placed. Even if there is no delivery (and/or receipt) or receipt of the invoice, this transfer order documentation initially shows a reduction in the remaining/residual value.
This is also shown in the EKAB table, as it contains only the quantity and net value of the order as fields, but no information about receiving or receiving the goods. Sharing commands can be easily identified with SAP® GUI as shown below. The example is based on a quantity contract that we can consult with the ME33K® transaction of SAP: the 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). To return to standard commands, you can use z.B the ME23N transaction. T-code ME33K shows you contracts, and ME33L is correct for delivery plans. You can see that the category of Mnemonics K and L vouchers also appears in part in bookings. Orders to unlock value and quantity contracts are included in a separate table called EKAB. SAP® SE16 transaction can be used to display items. The screenshot below shows the release commands in the EAKB table, filtered by “our” quantity contract 46000000062 of the first example. From a risk perspective, the theme of framework agreements offers a number of fascinating starting points, among others: this blog post explained how to identify the contracts for sharing framework agreements in SAP® with SAP® transactions such as SE16 and ME33K, but also how the process is recorded from the data point of view – z.B.
on attributes in EKKO/EKPO and in the EKAB output table.