The update of the sharing document is based on the type of contract. The type of contract decides that the release is based on the target value or target amount of the contract. Subsequent retail work focuses on quantity and value contracts. Enter the material and other details like the work. It is not necessary to enter the quantity, since it is a value contract. Save the recording. 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. I hope that you have enjoyed addressing the issue of framework agreements and that we will soon meet again for the second part of the “Call Agreements”. 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. 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. The framework agreement is a long-term sales contract between Kreditor and Debitor. The structure agreement is of two types: to refer 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. Contract The contract is a draft contract, and they do not contain delivery dates for the equipment. The contract consists of two types: 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 specified period. A delivery plan can be drawn up in two ways: step 4 – indicate the delivery schedule and the expected quantity. Click Save. The planning lines are now maintained for 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. By clicking on the hat icon (which recalls the head data -?) you get to where the target value of the contract is visible (in this case, of course, the sum of the two elements). I will now take a closer look at the target values for articles and heads in 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).