The framework agreement is a long-term sales contract between Kreditor and Debitor. Structure agreements are two types: framework agreements are an important issue that we must constantly 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. Supplier selection is an important process in the procurement cycle. Creditors can be selected based on the bidding process. After pre-selecting a creditor, an organization enters into an agreement with the latter to provide certain items subject to certain conditions. When an agreement is reached, a formal contract is usually signed with the Kreditor. A framework agreement is therefore a long-term purchase agreement with a creditor. Step 2 – Enter the delivery plan number. A delivery plan is a long-term framework agreement between the lender and the customer on pre-defined equipment or service obtained on pre-defined dates over a period of time. A delivery plan can be drawn up in two ways: to refer to standard orders, you can use the ME23N reservation to use 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.
The delivery plan is a long-term sales contract with the Kreditor, in which a creditor is required to provide equipment on pre-determined terms. Details of the delivery date and the amount communicated to the creditor in the form of the delivery plan. 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. The above voucher categories are assigned as attributes to each purchase proof 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. Futures agreements, on the other hand, are based more on quantities and, in addition, on concrete quantities of delivery on certain delivery dates (we are talking about dates). Quite simply, these are more restrictive quantitative contracts – but in the analysis of the data in SAP® they appear separately with their own category of supporting documents in relation to volume or value contracts. But later. 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. The contract is a draft contract and they do not contain delivery dates for the equipment. The contract is of two types: the data model — commands and framework agreements On this blog, I want to give you an overview of the framework agreements in SAP® in the purchase module.