Outline Agreement in Sap Table
Can someone tell me what a table is for storing contract data in the SAP MM module? In my last blog, I explained some of the basics of framework agreements (value and quantity contracts as well as planning agreements) in SAP®. This blog post explains how publication orders for framework agreements in SAP® can be identified with SAP transactions® such as SE16 and ME33K and how the process is recorded from a data perspective, i.e. via attributes in EKKO/EKPO and in the documentation table of EKAB publication orders. It has been shown that a call order is usually recorded as soon as it is mentioned in the order, regardless of the goods and invoice receipts. As I mentioned earlier, I will now look at the framework contract release orders. I`ll first briefly explain how to look for them in SAP® before moving on to the data situation. In detail, this involves recording call orders at the table level. For completeness, the following screenshot shows the EKAB table for the value contract 4600000030 in Example 2. Call orders can be identified in the same way: they contain only one element. After selecting this location, you can click the bar chart icon to view task publishing statistics. This shows how many call orders have already been issued for a framework agreement (more precisely: for a framework agreement article) and, if so, how much is still open.
The respective order number and its relationship to the corresponding framework agreement (more specifically: the contract element, consisting of the document number and the document line) are documented. We can now see how a total of four purchase order items relate to our contract item, but only one led to a call order – the first three items have the removal indicator L as an attribute. These are tables in which all procurement documents, including framework agreements, are stored. To create context, let`s start with ordinary tasks: as for the database, they are stored in SAP® in the EKKO (command head) and EKPO (command position) tables. Like what. B, if you want to track it, you can use the SE16 table browser to view the contents of the table. The voucher categories mentioned above are assigned as attributes to each proof of purchase in the EKKO header data table (field: EKKO_BSTYP). This means that the type of document allows us to distinguish planning agreements from other contracts. But how to distinguish value contracts from volume contracts? This is where the storm table described above comes into play: in the standard, the contract type “MK” stands for volume contracts and “WK” for value contracts. However, both types of records have the same “K” class of records.
While document categories are primarily used for categorization, document types are often used for customization, meaning that attributes are mapped to document types that are then used to organize the control process/process in a system. You can also be in the EKKO table, the field name is EKKO_BSART. Fig. Contract The contract is a draft contract and does not contain any delivery date for the material. There are two types of contracts: in this case, it is possible to work with almost superior purchasing organizations affiliated with decentralized purchasing organizations as a reference purchasing organization. You can then use and consult the framework agreements concluded within the framework of the reference purchasing agency. From the data analyst`s point of view, Table T024Z shows the assignment of purchasing organizations (field: T024Z_EKORG) to possible reference organizations related to the company (field: T024Z_EKORZ). An action order is an order (or order request from which an order is generated) with reference to a framework agreement.
This is important because it`s good to know that, at least for SAP`s admission statistics,® tracking transactions, such as goods entries and invoices, play no role in the first step. The corresponding order number and its relationship to the corresponding framework agreement (in particular the contractual situation, including the voucher number and proof) are documented. We can now see how four command positions relate to our contractual position, but only one resulted in a partition order – the first three positions have the removal sign L as an attribute. The delivery schedule is a long-term purchase agreement with the seller in which a creditor is required to supply equipment on predetermined terms. Information on the delivery date and the amount communicated to the creditor in the form of the delivery schedule. These are tables in which all procurement documents, including framework agreements, are stored. Pls tells me what table is used to store framework agreement data From a risk perspective, the topic of framework agreements offers a number of fascinating starting points for reflection, including: You can clearly see the category (K or L) and the associated document type (LP, WK, MK). Our system consists of 154 agreements. Contracts are often of a higher nature. This can be the case with SAP® because the organization of purchasing is essential (and the work that can be related to the organization of purchasing). The purchasing organization is displayed in the EKKO table for each contract (field: EKKO_EKORG).
In highly sought-after structures, however, large contracts (for example, the purchase of laptops throughout .B company) are negotiated centrally and can then be used in a decentralized manner. This means that in these two fields, our contract release order from Example 1 with the purchase document number 4500017169 and Article 10 contains the content “4600000062” (contract number released) and “10” (contract element). This EKPO table also shows the three purchase orders that were set to “deleted” and therefore did not result in call orders. From a risk perspective, the topic of framework agreements offers a number of exciting starting points, including: Framework agreement Release orders for value and quantity contracts are recorded, among other things, in a separate table called EKAB. The SAP SE16 transaction® can be used to view entries. The following screenshot shows the call orders in the EAKB table filtered by “our” quantity contract 4600000062 of the first example. The framework agreement is a long-term purchase contract between the seller and the customer. Framework agreements are of two types: the EKAB table is therefore a good starting point for our call orders. However, it is also worth noting that order release order lists are not only found in a separate table, but can also be generated in the context of data analytics via the original order tables (see EKKO/EKPO in the first blog post). For example, the EKPO table (purchase order lines) also displays the KONNR and KTPNR (contract number and contract item) fields. For purchase order elements that relate to a contract (more specifically: to a contract article), these contain the corresponding contract number and contract position values. I hope that these two blog posts on the subject of framework agreements have been useful.
Please send us your feedback if you have any questions or comments or if you see things differently in professional practice. A call order is a purchase order (or purchase requisition from which a purchase order is then generated) with a reference to a framework agreement. This is important because it`s good to know that, at least for call statistics in SAP®, tracking processes such as merchandise and invoice receipts play no role in logging in the first step. In statistics (i.e. in the transaction view and also in the data view), a quantity or value is displayed as a call order as soon as the order has been made. Even if there is ultimately no delivery (or receipt of goods) or receipt of invoice, this call documentation initially shows a reduction in the remaining quantity/value. This is also shown in the EKAB table as it contains only the purchase order quantity and net order value as fields, but no goods receipt or invoice information. The planning agreement is a long-term purchase agreement with the supplier in which a supplier is required to deliver equipment on predetermined terms. Information on the delivery date and quantity communicated to the supplier in the form of the planning agreement. 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 contract without a contract in these two areas consists of Example 1 with the purchase number 4500017169 and Article 10 of the content “4600000062” (contract contract number) and “10” (object of the contract). . . .