By clicking on the hat icon (which recalls the head data -?) you get to where the target value of the contract is visible (in this case, of course, the sum of the two elements). I will now take a closer look at the target values for articles and heads in framework agreements. 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. 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. Agreements are now at the origin of a long-term structured procurement process. But what about individual buying on the concrete basis of an agreement? We are also talking about call-offs.
These are specific specific markets, in reference to the framework agreement. How you can determine these searches by analyzing the data, the tables in which they are recorded, and whether the information about goods and invoices is relevant or relevant in this context – this is something for the next post in the series. In this blog, I would like to give you an overview of the framework agreements in SAP® in the purchase module. In addition to the design of the concept itself, I give you an overview of its assignment from the point of view of data analysis, that is, SAP® tables and field levels. Now it`s becoming exciting (at least for data analysts): framework agreements such as quantity contracts, value contracts and delivery plans are not stored in their own tables, but also in the EKKO and EKPO tables. So don`t get confused by names or take them too literally. 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.
Please inform yourself of the standard table in which the details of the contract as well as the details of the appointment are stored all the data. 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. The offer, order, SA and contract were registered in ekko and EKPO Table. You can clearly display the category (K or L) and the type of document associated (LP, WK, MK). Our system includes 154 agreements. In value contracts, the quantity of items is often secondary, since the total value of the contract counts.