The most important points to consider in a framework agreement are the following Step 9: Review the data and save the agreement by clicking on the SAVE icon. Data Model — Purchase Orders and Framework Agreements Now that we have understood where framework agreements are stored as data – i.e. in tables where you actually suspect «standard» orders – and how to identify them – by document category and document type – let`s look at some aspects of the process. You can clearly see the category (K or L) and the associated document type (LP, WK, MK). Our system includes a total of 154 agreements. A framework agreement can be of the following two types — For example, to refer to standard orders, you can use the ME23N transaction; T-Code ME33K shows you contracts, and ME33L is the right choice for planning agreements. You can see that the Mnemonic K and L document categories also partially appear in transactions. Step 1: Go to the Contract Creation screen. The T code for creating framework agreements is ME31K. I wish you great pleasure in addressing the subject of framework agreements and that we will soon be here for the second part, «Framework agreements — documentation on demand». The contract is a long-term purchase contract with a supplier for the supply of materials. These are valid for a certain period of time and cover a predefined total purchase quantity or a predefined total purchase value.
Here you can not schedule the lines. In the case of value contracts, the quantity of the item is often secondary, as the total value of the order counts. For example, a «Facility Management» value contract in the amount of €1,000,000 can be concluded with a service provider. This includes the three areas of building cleaning, necessary repairs and disposal. Here, individual quantities can be allocated much less concretely, and a construction of global value makes more sense. Another example would be office supplies (pens, post-it notepads) that are too «singular» at the post level to be included in a framework agreement. The terms of a framework agreement are valid for a certain period of time and cover a certain quantity or predefined value. In many areas, SAP® pursues a concept of document type and type.
The class of document is an approximate division, the type of document is the finest differentiation of the class of document. When analyzing in an order scenario, you may be interested in the following four categories of documents: Contract The contract is a draft contract that does not contain delivery dates for the material. There are two types of contracts: To view a framework agreement, go to the T code ME33K and enter the contract number. The Seller undertakes to supply the Buyer with certain goods/products during the agreed period and on the agreed terms. On the other hand, the buyer is also responsible for the purchase of the agreed quantities according to the conditions set out in the framework agreement. By clicking on the hat icon (the header data – remember?), you arrive at the place where the target value of the contract is also visible (in this case, of course, the sum of the two positions). I will now take a closer look at the target values at the article and header level in framework agreements. The framework agreement is a long-term purchase contract between the seller and the customer. Framework agreements are of two types: contracts are often of paramount importance.
This may be the case in SAP® as the procurement organization is of central importance (and the work can be linked to the procurement organization). The purchasing organization appears in the EKKO table for each contract (field: EKKO_EKORG). In corporate structures, however, it often happens that large contracts (e.B. purchase of laptops throughout the Group) are negotiated centrally and can then be used in a decentralised manner. In this case, it is possible to work with almost superior purchasing organizations that are assigned to decentralized purchasing organizations as a reference purchasing organization. The latter can then use and retrieve the framework agreements created under the reference purchasing organization. From the data analyst`s perspective, you can find the assignment of purchasing organizations (field: T024Z_EKORG) to possible reference purchasing organizations (field: T024Z_EKORZ) in Table T024Z. A framework purchase agreement consists of the following elements: Let`s start with examples of different types of framework agreements.
Here I look: In SAP MM Purchasing, these agreements are divided into «contracts» and «planning agreements». Delivery schedules, on the other hand, are more oriented towards quantities and, in addition, towards specific quantities delivered on certain delivery dates (this is called calendar lines). One could easily say that these are more binding quantitative contracts – but in data analysis in SAP®, they appear separately with their own category of documents compared to quantity or value contracts. But we`ll come back to that later. A contract is a long-term framework agreement between a supplier and a buyer for a predefined material or service over a period of time. There are two types of contracts — You can also access the framework agreement creation screen by following the following path: Note: There can of course be other types of documents, both in the standard and in the context of Customizing. For our blog post, the mentioned ones are enough to explain the connections. In this blog, I would like to give you an overview of framework agreements in SAP® in the purchasing module. In addition to describing the concept itself, I will give you an overview of its mapping from the point of view of data analysis, i.e. SAP tables and at® the field level. The framework purchase contract is often referred to as a ceiling or umbrella order. .