Press the button to see the details of the head in the delivery plan: Use the button to view the details of the head This is due to the fact that delivery plans require finding the classification. Select the appropriate position line and press the button in the position section of the delivery plan: Click Detail Button for a position line Press the current status of the delivery plan: State of the delivery plan Fig. 4 – Order documentation for a quantity contract in the EKAB table A framework contract is a long-term framework contract with the Kreditor. It contains the terms and conditions of the material to be supplied by the supplier. 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). 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. You can search for the search term that is managed in the customer`s basic data or name.
To stay search-specific, enter the corresponding distribution organization, so that only debtors kept in your distribution organization are displayed. If you decide to find the customer with the name, enter the customer`s first name with the name before and after the name. This is called wildcard research. 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. A contract is a framework agreement between you and your client, valid for a specified period of time. The contract does not include classifications, quantities or delivery dates. The same functions are available in contracts as in orders. They can also agree on specific price agreements. The customer completes the contract with individual permissions. Divisions are created in the share command when they are placed. The release order is then treated like any standard command.
All special price agreements are copied to the contract. Orders to unlock value and quantity contracts are included 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. From a risk perspective, the theme of framework agreements offers a series of fascinating starting points, among others: A contract is basically a long-term framework agreement between the seller and the customer. It is carried out on pre-defined materials or services that must be provided within a specified time frame.