From a risk perspective, the topic of framework contracts offers a number of exciting starting points, including: A long-term framework contract between a supplier and a customer for predefined hardware or service over a period of time. There are two types of contracts – Step 2 – Indicate the number of the delivery plan. It`s a bit more technical, but to be complete, it`s a screenshot of the document type table with customizing settings in SAP® if they`re needed for data analysis purposes. The numbers of the corresponding document types, for example.B. Parameters for selecting fields, etc., are included in this table: the objective of framework agreements is usually to set a ceiling or a total volume (i.e. a target value). For quantitative contracts, this is very specific to individual materials and therefore often to a material number (box: EKPO_MATNR), because.B this is where the number of parts or units plays an important role (even if there are other possibilities for an unknown material or consumer, but I will not come back to it here). For this reason, the reference value must be found at the level of the contractual position, because the target quantity (box: EKPO_KTMNG) multiplied by the price of each material gives the reference value (box EKPO_ZWERT) of each position. I hope that you have appreciated the entry into the issue of framework agreements and that we will soon meet for the second part , `Framework agreements – documentation on demand`. I hope that these two blog posts on the topic of framework agreements have been useful. Please send us your feedback if you have any questions or comments or if you may see things differently in professional practice. A framework agreement can consist of the following two types: Enter Step-2 Validity of the contract end date in the head data image. You can clearly see the category (K or L) and the associated document type (LP, WK, MK).
Our system includes a total of 154 contracts. This blog post explained how to identify framework contract sharing orders in SAP® with SAP® transactions such as SE16 and ME33K, and how the process is recorded from a data perspective – i.e. via the attributes of the EKKO/EKPO and in the EKAB publication order documentation table. It showed that a release order is usually recorded as soon as the order indicates it, regardless of the inflows of goods and invoices. By clicking on the hat icon (the header data – remember?), you get to where the target value of the contract is also visible (in this case, of course, the sum of the two items). I will now take a closer look at the objectives at the position and head level in the framework agreements. Please, tell me which table is used to store the data of the framework agreements Here I mainly approach the subject by analyzing sap® data, that is, the terminology used and the processes presented are partly system-specific. Now that we have discovered where framework agreements are held as data – in tables where „standard“ commands are suspected – and how to identify them – by document type and document type – we now look at some aspects of the process. Delivery plans, on the other hand, are more focused on quantities, but also on the concrete quantities delivered on certain delivery dates (we speak of classifications). One could easily say that these are more binding quantitative contracts – but in the analysis of the data at SAP® they appear separately with a separate category of supporting documents compared to volume or value contracts.
. . .