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. The framework agreement is a long-term sales contract between Kreditor and Debitor. The structure agreement is of two types: the delivery plan is a long-term sales contract with the creditor, in which a creditor is required to provide equipment on pre-established terms. Details of the delivery date and the amount communicated to the creditor in the form of the delivery plan. The classic relational data model avoids redundancy in . B data is divided into head and article data for supporting documents and transactions. In the head of the room, you will find data valid for the entire document (and all the elements). In a conventional order scenario, the occupancy head contains attributes such as creditor, probation, order date and payment terms.
On the other hand, the current data on order positions are the order quantity, the category of goods, the material number and the price. Can someone give me the name of the table that stores the data of the agreement that was created with tcode ME31n. Let`s start with examples of different types of framework agreements. That is where I will look: now that we have discovered where the framework agreements are held as data — in tables where they actually think that “standard” orders — and how to identify them — by document type and by document type — let`s look at some aspects of the process. Framework agreements are an important issue that we must constantly address in our analysis of procurement data. Unlike individual contracts, which are often ad hoc, framework agreements are constructs for a longer-term business relationship. In the SAP system® itself. B you can access the call documentation in the ME33K transaction using the histogram icon and get information about what has already been published. You can clearly display the category (K or L) and the type of document associated (LP, WK, MK). Our system includes 154 agreements. 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). Data model – Commands and framework agreements By clicking on the hat icon (which recalls head data?) you get to where the target value of the contract is visible (in this case, of course, the sum of the two items).