List Of Agreements In Sap

To return 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. 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. I can tell myself the T.code so I can see a list of contracts. for ex, as we see the purch req list in ME5A. 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. Data model – orders and framework agreements Now it`s becoming exciting (at least for data analysts): framework agreements such as volume contracts, value contracts and delivery plans are not stored in their own tables, but also in the EKKO and EKPO tables. So don`t get confused by names or take them too literally. 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. Supplier selection is an important process in the procurement cycle. Creditors can be selected based on the bidding process. After pre-selecting a creditor, an organization enters into an agreement with the latter to provide certain items subject to certain conditions.

When an agreement is reached, a formal contract is usually signed with the Kreditor. A framework agreement is therefore a long-term purchase agreement with a creditor. 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. 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.