They can establish a delivery plan in relation to the centrally agreed contract, which is advantageous for price negotiations, as purchases are made in large quantities. These conditions, which are mentioned in the agreement, should not change. Step 4 – Indicate delivery date and target quantity. Click Save. The planning lines are now maintained for the delivery plan. A structure contract consists of two types, the – contract and a delivery plan. A contract is a longer-term agreement with a lender (one of two forms of „framework agreement“ in the SAP system) to provide equipment or service for a fixed period of time. For this concept, different terms can be used in the buying literature, including „Blanket Order,“ „blanket contract,“ „system contract“ and „period contract.“ 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. You can create delivery plans with or without publication documentation. With publication, the documentation has an advantage because, in this case, you have sent a data set on the delivery plan to a supplier that you can display at any time. 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. 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. Here, I deal with the subject mainly from the point of view of sap® data, that is, the terminology used and the processes presented are partly system-specific. 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 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. You can use delivery plans with or without exit documentation. An unlock can be used to inform the lender that it must provide the indication of the material on the dates. 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.
There are two types of documents for delivery plans: let`s start with examples of different types of framework agreements. Here`s what I`ll see: prognosis and JIT are two kinds of appointment authorization.