In my last blog, I explained some framework agreements (value and quantity contracts as well as delivery plans) in SAP®. It contains only one element. After you mark this item, you can click on the graphic icon to see the statistics in the release order. This shows how many release mandates have already been placed for a framework agreement (specifically for a framework agreement position) and, if so, the remaining amount. Let`s start with examples of different types of framework agreements. For the sake of completeness, the screenshot below shows the EKAB table for the 4600000030 value contract, taken from example 2. Sharing commands can be identified in the same way: so, if we add types of proofs to our table above, the situation is this (this time I omitted the categories of proofs and types of proofs that are not relevant to the contract: an exit 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. Fig. 4 – The documenting of the order of a quantity contract in the EKAB Agreement-framework table is a long-term sales contract between the lender and the customer. The structure agreement is two types: the above categories of proofs 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.
Contract The contract is a draft contract, and they do not contain delivery dates for the equipment. Contract is of two types: Can anyone let me know what the table is for storing contract data (Outline Agreement) in the SAP MM module? It`s a little more technical, but here, for the sake of completeness, a screenshot of the document type table with customizing settings in SAP® if they are needed for data analysis purposes.