Vizibelle

Visual Artist

Quantity Agreement Table In Sap

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. Subsequent retail work focuses on quantity and value contracts. 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. This blog explains 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 perspective – that is, on attributes in EKKO/EKPO and in the EKAB information 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. For the sake of completeness, the screenshot below shows the EKAB table for the 4600000030 value order of example 2.

Release orders can be identified in the same way: to refer to standard commands, you can use the ME23N transaction. B; 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. 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. Contract The contract is a draft contract, and they do not contain delivery dates for the equipment. The contract is of two types: as has already been said, I will now look at the framework agreement for sharing contracts.

First, I will briefly explain how they are looking for sap® before moving on to the data situation. In detail, this includes logging sharing operations at the table level. We are in the process of creating change BDCs in which we do not get the table in which the data is stored. 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 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). With regard to order positions relating to a contract (specifically a contractual position), they contain the contract number and the corresponding contract item values. From a risk perspective, the theme of framework agreements offers a series of fascinating starting points for reflection, including: To create a context, we start with normal unique commands: As far as the database is concerned, these are stored in sap® in the tables EKKO (Command Head) and EKPO (command position).