Delivery plans are defined and managed as documents in the system. It is possible to group these documents under different types of documents depending on the business requirements. First, you need to define the document types and their attributes in customizing. A sharing profile determines the period during which versions (delivery plan types) are generated against a delivery plan and passed to the provider. This also controls the frequency of versioning; the aggregation of the quantities provided for from the day following the establishment of the release; and the carrying out of a tolerance check. The main points to consider in the context of a framework contract are the following A framework contract consists of the following elements: Contract The contract is a draft contract and does not contain a date of delivery of the material. A framework contract is a long-term sales contract with a seller that contains conditions for the material to be delivered by the seller. The above categories of supporting documents are assigned to each purchase receipt in the EKKO head data table as an attribute (field: EKKO_BSTYP). This means that the class of documents allows us to distinguish delivery plans from other contracts. But how to distinguish value contracts from volume contracts? This is where the type of evidence described above begins: in the standard is the type of proof “MK” for volume contracts and “WK” for value contracts. However, both types of records have the same class of “K” records.
While document categories are primarily used for categorization, document types are often used to customize them, i.e. assign attributes to document types that are then used to organize/control processes in a system. You can also find them in the EKKO table, the field name is EKKO_BSART. The framework purchase contract is often referred to as a framework or roof order. It is essentially a long-term agreement between the procurement department and the supplier of equipment or services for a defined period of time. The purchasing department negotiates with the supplier a number of conditions for the duration of the contract. After you define the document types for delivery plans, select the document type row and double-click the allowed item categories. On the screen, maintain the categories of items allowed for the document type, as shown in the following table. These position categories can be configured according to the corporate requirement. This configuration defines the categories of positions that can be selected by the user for a particular document type when creating the delivery plan.
Data Model – Orders and Framework Contracts So how do you see the difference in SAP® whether it`s a normal order or a framework agreement – and, if so, what kind of agreement? Experienced sap® users among you will of course cite the type of document, which is quite accurate. Nevertheless, it is worth taking a closer look. Step 4 – Indicate the delivery date and target quantity. Click Save. For the delivery plan, classifications are now maintained. As part of the SAP MM purchase, these agreements are divided into “contracts” and “delivery plans”. The following tables include the default settings for SAP. Through IMG (SPRO), depending on business requirements, the additional delivery plan garden can be defined > materials sector > the purchase > > types of documents….