A purchase framework contract consists of the following: I hope you enjoyed getting into the issue of framework agreements and that we will soon meet again for the second part “Outline Agreements – Call-off-Dokumentation “. 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. Contract The contract is a draft contract, and they do not contain delivery dates for the equipment. The contract consists of two types: to refer to standard orders, you can use the transaction ME23N, z.B. T-code ME33K shows you contracts, and ME33L is correct for delivery plans. You can see that the category of Mnemonics K and L vouchers also appears in part in bookings. When creating a contract, you can choose between the following types of contracts: 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. Step 2 – Include the name of the creditor, the type of contract, the purchase organization, the buying group and the factory with the date of the contract. Framework agreements are an important topic that we need to address in our analysis of procurement data. Unlike individual contracts, which are often ad hoc, framework agreements are constructs for a longer-term business relationship. The terms of a framework agreement apply up to a specified period of time and cover a certain pre-defined amount or value. Now it`s becoming exciting (at least for data analysts): framework agreements such as quantity 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. The framework agreement is a long-term sales contract between Kreditor and Debitor. The structure agreement consists of two types: Step 2 – Indicate the delivery plan number. A framework agreement can be of the following two types: Complete all necessary details, such as the date of validity of the agreement, the end date and the terms of payment (i.e. the terms of payment).