This blog explains how to identify framework agreement sharing contracts in SAP® with SAP® transactions such as SE16 and ME33K, and how the process is recorded from a data perspective – that is, on attributes in EKKO/EKPO and in the EKAB information documentation table. It turned out that an authorization order is usually registered as soon as the order refers to it, regardless of the receipt of the goods and invoices. 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. A framework purchase contract consists of the following: You can clearly display the category (K or L) and the corresponding occupant (LP, WK, MK). Our system includes 154 agreements. Step 4 – Indicate delivery date and target quantity. Click Save. The planning lines are now maintained for the delivery plan. Orders to unlock value and quantity contracts are included in a separate table called EKAB.
SAP® SE16 transaction can be used to display items. The screenshot below shows the release commands in the EAKB table, filtered by “our” quantity contract 46000000062 of the first example. 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.” Let`s start with examples of different types of framework agreements. I`ll look here: Contract The contract is a draft contract, and they do not contain delivery dates for the equipment. The contract is of two types: but a delivery plan is a form of contour purchase agreement under which materials are purchased on pre-defined dates within a specified time frame. A delivery plan consists of a set of items for which a type of supply is defined. The A supply contract 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: the framework agreement is a long-term sales contract between Kreditor and Debitor. Structure agreements are two types: 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. 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. In my last blog, I explained some framework agreements (value and quantity contracts as well as delivery plans) in SAP®. 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.