For our value contract, we could of course follow this in the EKPO by filtering on the basis of KONNR – 4600003030; But I`m not going to show this screenshot here. Finally, it is interesting to think about what a contract-sharing mission really means in SAP® from the point of view of data analysis: to be complete, a screenshot of a value contract bearing the number 46000003030 is presented below; The statistics on publishing contracts for point 20 are similar: I hope these two blogs 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. The total net value of the order for all sharing tasks 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). 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.
For the sake of completeness, the screenshot below shows the EKAB table for the 4600000030 value order of example 2. Unlock orders can be identified in the same way: orders for unlocking value and volume contracts are included, among other things, in a separate table called EKAB. SAP® SE16 transaction can be used to display items. The screenshot below shows the release commands in the EAKB table, filtered by “our” quantity contract 46000000062 of the first example. Figure 4 – Documenting orders for a volume contract in the EKAB table A calendar can be drawn in two ways: to be complete, the screenshot below shows the EKAB table for the 46000003030 value contract in example 2. The unlock contracts can be identified in the same way: as mentioned above, I will now check the contracts for unlocking the framework agreement. First, I will briefly explain how you are looking for ® before moving on to the data situation. In detail, this includes the logging of sharing operations at the table level. Now it`s becoming exciting (at least for data analysts): framework contracts such as volume 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. Step 2 – Enter the delivery plan number. The total net value of the order for all release tasks is displayed in the line marked in yellow. However, because the target value is stored on the head, the item does not display target performance or a documented residual value in the same way as for the quantity contract position (if you want to display the target value on the head, select the hat icon on the ME33K home screen as usual).