I hope these two blog posts on framework agreements have been helpful. Please send us your comments if you have any questions or comments, or perhaps see things differently in professional practice. It is interesting to note that although the publication order statistics show a total of four supporting documents, the cumulative total for the first three is 0. Only the last order with the order number 4500017169 and Article 10 contains an order of 2 tons, reducing the amount of open target from 250 to 248 tons. The EKKO is the tribal control board. EKPO is the table of articles. EKBE is the table of order history. EBAN is the table of order requirements. EBKN is the “Order Account Assignment” table. The vendor`s basic data table in SAP is LFA1 for general information. This means that, in both areas, our contract relaxation mandate has content “4600000062” (contract number to be published) and “10” (contract article) from example 1 with the purchase number 4500017169 and article 10.
This EKPO table also displays the three commands that were placed on “deleted” and therefore did not result in release orders. The main SAP control tables are EKKO. Each order is identified by EBELN (PO number) The total net value of the order for all sharing commands is displayed in the line marked in yellow. However, because the target value is stored at the head, the item does not display the performance of the target or a documented residual value in the same way as for the position of the quantity contract (if you want to display the target value at the head, select the hat symbol in the ME33K home screen as usual). Figure 1 – Consultation of statistics on order-sharing contracts for a contractual position The relevant order number and its relationship to the corresponding framework agreement (specifically the contract 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. The EKKO-BSART cheyp distinguishes the different types of requirements and the command in the SAP system. Finally, it is interesting to think about what a contract-sharing order really means in SAP® from the point of view of data analysis: the first list contains only PO data tables. In the next part, the customization tables for the order will be listed in the SAP-MM purchase. In my last blog, I explained some framework agreements (value and quantity contracts as well as delivery plans) in SAP®. Hello Thanks for your reply, and if I use me31k to create a chord, and generate a figure like 4600000067, in which table would I find this number? From a risk perspective, the Framework Agreements theme offers a number of fascinating starting points that can be taken into account, including: Here is a list of the main SAP-PO tables in which purchase information is stored, including the details of the head and items of each order.
EKKO – Purchasing Manager EKPO – MARA Trade Items – EKET Materials General Data – EKKN Delivery Plan Lines – Passage in the EKBE Purchase Book – Purchasing History Below, you`ll find a list of SAP purchasing database tables, the data they store and how they are linked to each other. Also click on the table name to get all the details of the fields, including the key of the table along with other information such as control tables, text tables… 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.