Sap Table Name for Contract Agreement

The document types mentioned above are assigned to each purchase document in the EKKO header data table as an attribute (field: EKKO_BSTYP). In terms of analysis, this means that the category of documents allows us to distinguish delivery schedules from other contracts. But how to distinguish value contracts from volume contracts? This is where the type of document explained above comes in: in the standard, the document type "MK" stands for quantity contracts and "WK" for value contracts. However, both types of documents have the same category of "K" documents. While document categories are mainly used for categorization, document types are often used for adaptation, that is, attributes are assigned to document types, which are then used for process organization/process control in a system. They can also be found in the EKKO table, the field name is EKKO_BSART. Contracts are often of a higher nature. 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. The objective of framework agreements is usually to set an upper limit or a total volume (i.e. a target value). In the case of quantitative contracts, this is very specific to individual materials and therefore often linked to a material number (field: EKPO_MATNR), because here the number of parts or units plays an important role (even if there are other possibilities for an unknown material or consumable, for. B example, which I will not discuss here). For this reason, the target value can be found here at the level of the respective contractual position, because the target quantity (field: EKPO_KTMNG) multiplied by the price of the respective material gives the target value (field: EKPO_ZWERT) of the individual item. To create context, we start with normal point-in-time commands: as far as the database is concerned, these are stored in SAP® in the EKKO (order header) and EKPO (order item) tables. If you want to follow this, you can e.B. Use the SE16 table browser to view the contents of the table.

The framework agreement is a long-term purchase contract between the seller and the customer. Framework agreements are of two types: So, if we add document types to our table above, it looks like this (this time I omitted the categories of documents and the types of documents that are not relevant to the contract): Now it becomes exciting (at least for data analysts): Framework agreements such as quantity contracts, Value contracts and planning agreements are not stored in their own tables, but also in EKKO and EKPO tables. So don`t get confused by the names or take them too literally. Centrally agreed purchasing organizations and contracts Let`s start with examples of different types of framework agreements. Here I will look: Contract The contract is a draft contract, and they do not include the delivery dates for the material. There are two types of contracts: in the case of value contracts, the quantity of items is often of secondary importance, since 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. 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 following figure shows a value contract called by the ME33K transaction: The document type is the BSTYPE field of TABLE EKKO. It will be in the tables EKKO (HEader) and EKPO (DETAILS). You need to know the type of doucment - MK and WK for quantity and value contracts. Access EKKO with BSTYP (purchase document type) as `K` as a contract and BSART (purchase document type) as WK or MK.

Planning agreements, on the other hand, are based more on quantities and also on specific quantities delivered on certain delivery dates (we speak of 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. Framework agreements are an important topic that we need to address continuously in our data analysis for procurement. Unlike individual orders, which are often ad hoc in nature, framework agreements are constructs aimed at establishing a longer-term business relationship. Step 2 Validity Enter the contract end date in the header data screen. 4 – The order documentation of a quantity contract in the framework table of the EKAB contract is a long-term purchase contract between the lender and the customer. For completeness, the following screenshot shows the EKAB table for the value contract 460000003030 in Example 2. Sharing contracts can be identified in the same way: I hope these two blog posts on the topic of framework agreements have been helpful.

Please send us your feedback if you have any questions or comments or if you see things differently in professional practice. Contract The contract is a draft contract and does not contain delivery dates for the equipment. The contract consists of two types: this means that our non-contractual contract in these two areas consists of Example 1 with the purchase number 4500017169 and Article 10 of the content "4600000062" (number of the supply contract) and "10" (object of the contract). This EKPO table also displays the three commands that were set to "deleted" and therefore did not result in recovery requests. Now that we`ve figured out where framework agreements are kept as data – in tables where you actually suspect standard orders – and how they`re identified – by document category and document type – let`s look at some aspects of the process. A framework agreement can be of the following two types: orders for the release of value and volume contracts are contained in a separate table called EKAB, among others. Further elaboration of the details focuses on quantity and value contracts. 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. Quantity contracts, as the name suggests, are usually concluded for specific target quantities of certain goods or materials.

B for example a contract position called "1000 engines". This means – if a quantitative contract includes different positions – that the target quantities (and therefore also the monetary values) are differentiated according to the positions. As a second additional point, our order could include "2000 special valves". .