Sap Create Agreement Number

Step 2 – Include the delivery plan number. As a general rule, the objective of framework agreements is to set a ceiling or a total volume (i.e. a target value). For quantity contracts that are very specific to individual materials and therefore often related to a material number (field: EKPO_MATNR), because the number of parts or the number of parts play an important role here (although there are other possibilities. B for an unknown material or consumables that I will not study here). This is why the target value here is at the level of the respective contract position, since the target quantity (field: EKPO_KTMNG) multiplied by the price of the material in question gives the reference value (field: EKPO_ZWERT) of each item. A number can no longer be changed after being assigned and stored. The terms of a framework agreement apply up to a specified period of time and cover a certain pre-defined amount or value. The framework agreement is a long-term sales contract between Kreditor and Debitor. The structure agreement is of two types: in this blog I would like to give you an overview of the framework agreements in SAP® in the purchase module. In addition to the design of the concept itself, I give you an overview of its assignment from the point of view of data analysis, that is, SAP® tables and field levels. 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. 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. A framework contract is a long-term sales contract with a creditor that contains terms and conditions for the equipment to be provided by the creditor. To return to standard commands, you can use z.B the ME23N transaction. 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 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. Let`s start with examples of different types of framework agreements. I would like to tell you this: I hope you enjoyed addressing the subject of framework agreements and that we will meet soon for the second part, „Outline Agreements – Call-off documentation”. You can clearly display the category (K or L) and the type of document associated (LP, WK, MK). Our system includes 154 agreements.

In value contracts, the quantity of items is often secondary, since the total value of the contract counts. For example, a „facility management” contract of 1,000,000 euros could be concluded with a supplier.