Contracts are often of a higher nature. This may be the case at SAP® since the purchasing organization is essential (and which can be linked to the purchasing organization). The purchasing organization appears in the EKKO table for each agreement (box EKKO_EKORG). However, in group structures, important contracts (e.g. purchase of laptops throughout the group) are often negotiated centrally and can then be used in a decentralised manner. In this case, it is possible to work with almost superior purchasing organizations, which are attached to decentralized purchasing organizations as a reference purchasing organization. The latter can then use and retrieve framework contracts drawn up under the reference purchasing organisation. From the point of view of the data analyst, you will find the assignment of purchasing organizations (field: T024Z_EKORG) to possible reference purchasing organizations (box T024Z_EKORZ) in Table T024Z. Data Model – Orders and Framework Contracts Table T166P SAP for – Position Texts in Purchase Printouts In the SAP Purchasing Component, a kind of “framework agreement” or longer-term purchase agreement. The contract is a binding obligation to source from a supplier for a specified period of time. The agreements laid the foundation for long-term structured procurement. But concretely, what is the individual purchase on the basis of an agreement? Here too, we talk about “call-offs”. These are specific specific contracts, with reference to the framework agreement.
How you can identify these searches through data analysis, in which tables they are recorded, and whether the entries of goods and invoices are relevant or relevant in this context, this is something for the next blog post in the series. Framework contracts are an important issue that we must constantly address in our data analytics for procurement. Unlike individual contracts, which are often ad hoc, framework contracts are constructions aimed at a longer-term business relationship. To refer to default commands, you can use z.B. the ME23N transaction; T-Code ME33K shows you contracts, and ME33L is the right thing to do for delivery plans. You can see that the category of supporting documents Mnemonik K and L is also present in part in the transactions. Another type of “framework agreement” or longer-term purchase agreement. Delivery plans provide for the establishment of delivery plans indicating purchase quantities, delivery dates and, where applicable, precise delivery times over a predefined period. For value contracts, the quantity of items is often secondary, as the total value of the order matters. For example, a facility management contract of €1,000,000 can be concluded with a supplier.
This includes the three points of building cleaning, possible repairs and disposal. In this case, individual sizes can be assigned much less concretely, and an overall construction makes more sense. Another example would be office equipment (pens, post-it notepads) that is too “singular” at the room level to be defined in a framework agreement. The traditional relational data model avoids redundancy, for example by dividing the data on supporting documents and transactions into head and position data. In the head of the supporting document, you will find data valid for the entire document (and all positions). In a typical order scenario, the proof head contains attributes such as creditor, reference currency, order date, and payment terms. In contrast, the current order position data is the order quantity, the type of goods, the material number and the price. . . .
Published by: filtered