Outline Agreement A
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. In sap-MM purchases, these agreements are subdivided into “contracts” and “supply contracts.” 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. Let`s start with examples of different types of framework agreements. I will address this point: a contract is a longer-term agreement with a supplier (one of two forms of “framework agreement” in the SAP system) to provide equipment or provide a service for a specified 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.” 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. How do you see the difference between SAP® whether it is a normal order or a framework agreement – and, if so, what kind of agreement? Experienced SAP users® among you will of course cite the LaPi Site, which is quite true. Nevertheless, it is worth having a more detailed look. The terms of a framework agreement apply up to a specified period of time and cover a certain pre-defined amount or value. 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. Data model – commands and framework agreements 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 structure agreement can be of the following two types: Step 4 – Indicate the delivery date and target quantity. Click Save. The planning lines are now maintained for the delivery plan. 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 developed in two ways: it now becomes exciting (at least for data analysts): framework agreements such as volume contracts, value contracts and delivery plans are not stored in their own tables, but also in the EKKO and EKPO tables.