A contract is a longer-term agreement with a lender (one of two forms of “framework agreement” in the SAP system) to provide equipment or service for a fixed period of time. For this concept, different terms can be used in the buying literature, including “Blanket Order,” “blanket contract,” “system contract” and “period contract.” Futures agreements, on the other hand, are based more on quantities and, in addition, on concrete quantities of delivery on certain delivery dates (we are talking about dates). Quite simply, these are more restrictive quantitative contracts – but in the analysis of the data in SAP® they appear separately with their own category of supporting documents in relation to volume or value contracts. But later. 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.
A framework purchase contract consists of the following elements: The corresponding order number and its relationship with the corresponding framework agreement (specifically: the contractual position, including the voucher number and the proof post) are documented. We can now see how four command positions relate to our contractual position, but only one has resulted in a sharing order – the first three items have the L deletion mark as an attribute. Now that we have discovered where the framework agreements are kept as data — in tables where you actually suspect standard commands — and how to identify them — by document category and document type — let`s look at some aspects of the process. I hope that you have enjoyed addressing the issue of framework agreements and that we will soon meet again for the second part of the “Call Agreements”. Data model – commands and framework agreements A framework agreement can be of two following types – this blog post explained how to identify framework agreement sharing contracts in SAP® with sap® transactions such as SE16 and ME33K, and how the process is recorded from a data point of view – z.B. on attributes in the EKKO/EKPO and in the EKAB output order documentation table. It turned out that an authorization order is usually registered as soon as the order refers to it, regardless of the receipt of the goods and invoices. How do you see the difference between SAP® whether it is a normal order or a framework agreement – and, if so, what kind of agreement? Experienced SAP users® among you will of course cite the LaPi Site, which is quite true.
Nevertheless, it is worth having a more detailed look. It contains only one element. After you mark this item, you can click on the graphic icon to see the statistics in the release order. This shows how many release mandates have already been placed for a framework agreement (specifically for a framework agreement position) and, if so, the remaining amount.