Data Model – Orders and Framework Agreements A delivery plan is a long-term framework agreement between lender and customer on pre-defined hardware or service obtained on pre-defined dates over a period of time. A delivery plan can be drawn up in two ways: the above voucher categories are assigned as an attribute to each purchase supporting document in the EKKO head data table (field: EKKO_BSTYP). This means that the document category allows us to distinguish delivery plans from other contracts. But how do you distinguish value contracts from volume contracts? This is where the storm table described above comes in: in the standard, the type of contract “MK” is for volume contracts and “WK” for value contracts. However, both types of documents have the same category of “K” document. While document categories are primarily used for categorization, document types are often used to customize, i.e. attributes are assigned to document types, which are then used to organize the process/control process in a system. You can also be in the EKKO table, the field name is EKKO_BSART. Finally, it is interesting to think about what a contract-sharing order in SAP ® means from the point of view of data analysis: Sap® follows in many areas a concept of category of vouchers and occupancy rate.
The document category is a rough classification, the type of document is the finer differentiation of the document category. When analyzing an order scenario, you may be interested in the following four categories of documents: Step 2 – Enter the delivery plan number. 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: a framework agreement is a long-term purchase agreement with a creditor that contains terms and conditions for the material to be supplied by the lender. Hello, I`m looking for a sap-type report that shows all the orders that were made for a framework agreement. I need them all together – I know that for every article of the Treaty, I can see them separately in the Treaty itself. 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. 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. A framework agreement does not contain data on certain delivery dates or quantities to be delivered. This data is transmitted to the creditor in two ways, depending on the nature of the framework agreement.
A creditor is informed of quantities and delivery times, either in a specific form of order called the contract unlockability order, or in a delivery schedule. 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 level, the item does not indicate the performance of the target or a documented residual value in the same way as for the group contract position.