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. Contracts are often superior in nature. This may be the case with SAP® because the buying organization is essential (and the work that may be related to the purchase organization). The purchase organization is shown in the EKKO table for each agreement (field: EKKO_EKORG). However, in high-demand structures, large contracts (for example. B the purchase of laptops throughout the company) are negotiated centrally and can then be used in a decentralized manner. In this case, it is possible to cooperate with near-superior purchasing organizations, which are attached to decentralized purchasing organizations as a reference purchasing organization. They can then use and consult framework agreements established under the reference purchasing agency.
From the data analyst`s perspective, you will find in table T024Z the allocation of purchasing organizations (field: T024Z_EKORG) to possible business reference organizations (field: T024Z_EKORZ). 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. As I have said before, I will now look at the mandates to unblock the framework agreement. First, I will briefly explain how they are looking for sap® before moving on to the data situation. In detail, this includes logging sharing operations at the table level. This means that, in both areas, our contract relaxation mandate has content “4600000062” (contract number to be published) and “10” (contract article) from example 1 with the purchase number 4500017169 and article 10. This EKPO table also displays the three commands that were placed on “deleted” and therefore did not result in release orders. If we add types of documents to our table above, the situation is this (this time I omitted the categories of documents and the types of documents that are not relevant to the contract: let`s start with examples of different types of framework agreements.
For the sake of completeness, the screenshot below shows the EKAB table for the 4600000030 value contract, taken from example 2. Unlocking contracts can be identified in the same way: the purpose of framework agreements is usually 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. Please inform yourself of the standard table in which the details of the contract as well as the details of the appointment are stored all the data. 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.