Quantity Contract – This type of contract indicates the total value of the equipment provided by the supplier. In many areas, SAP follows® a category concept of proofs and occupancy. The document category is a rough classification, the type of document is the finer differentiation of the document category. When analyzing a market scenario, you may be interested in the four categories of documents above: the above document 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.
Note: Of course, there may be other types of documents, both in the standard and as part of the customizing. For our blog post, these are enough to explain the relationships. A contract is a long-term framework agreement between a lender and a customer via pre-defined equipment or service over a period of time. There are two types of contracts — now that we have developed framework agreements that are considered data — in tables where you really think the “standard” orders — and how to identify them — by document type and by type of document — look at some aspects of the process. In which table are the contract data stored (ME31K)? Data model – Commands and framework agreements Let`s start with examples of different types of framework agreements. I`ll look here: Step 2 – Include the number of the delivery plan. So if we add types of proofs to our table above, the situation is this (this time I omitted the categories of documents and types of proofs that are not relevant to the contract: a framework agreement is a long-term purchase agreement with a creditor that contains general terms for the material to be provided by the customer. Agreements are now at the origin of a long-term structured procurement process. But what about individual buying on the concrete basis of an agreement? We are also talking about call-offs. These are specific specific markets, in reference to the framework agreement. How you can determine these searches by analyzing the data, the tables in which they are recorded, and whether the information about goods and invoices is relevant or relevant in this context – this is something for the next post in the series. A SAP TABLEAU for – Shopping list: Purchasing organization data T166P-Tabelle T166P-Tabelle for – Items in the purchase room Expression Step 4 – Indicate delivery schedule and expected quantity.
Click Save. The planning lines are now maintained for the delivery plan. The storm board is the BSTYP field of the EKKO table. The main points regarding a framework agreement are the following In this blog, I would like to give you an overview of the framework agreements in SAP® in the purchase module.