In my last blog, I explained some basics of framework contracts (value and volume contracts as well as delivery plans) in SAP®. The basic table of vendors in SAP is LFA1 for general information. As I have already said, I shall now look at the contracts for the release of a framework agreement. I`ll first briefly explain how to replay them to SAP® before moving on to the data situation. In detail, it is a question of recording the release orders at the level of the table. This means that, in both cases, our contract termination order, taken from Example 1, with purchase number, 4500017169 and point 10, the content “4600000062” (number of the contract to be released) and “10” (contractual position). This EKPO table also shows the three orders that were placed on “deleted” and therefore did not give rise to release orders. Accounting is an important part of the purchasing process, so there are a number of direct relationships between PO tables and accounting tables such as BKPF and BSEG. BKPF – BSET Accountant Head – BSEG Tax Data Segment – BSEC Accounting Segment – Single Account Data EKKO Data Segment – EKPO Purchase Disk Head – EKBE Purchasing Station – Deliver below a list of SAP database tables related to the order, the data they store and their relationship. Also click the table name to get all the details of the fields that make up the table key along with other information such as control tables, text tables, and so on. What is the name of the base table of the order contract? And by the way, tell me a relative table on concordance. The order number and its relationship to the corresponding framework contract (more precisely the position of the contract, consisting of a proof number and a proof position) are documented. We can now see how a total of four control posts relate to our contractual position, but only one resulted in a release order – the first three positions have the L license plate as an attribute.

Here are the details of the different fields in this table. You can find the description, data type, and length assigned to each of the fields in the EKCPI table. SAP EKCPH Table for – Purchase Contract Head Information (Note that some of the SAP tables below contain strains related to SAP PO) An SAP Table for – Purchasing Information Kit: So the EKAB Purchasing Organization Board is a good starting point for our sharing orders. But it`s also worth noting that in addition to the hiding place in a separate table, lists of contract sharing orders can also be generated as part of data analysis on the initial order tables (see EKKO/EKPO in the first blog post). For example, the EKPO (control items) table also displays the KONNR and KTPNR fields (contract number and contract position). For order positions relating to a contract (more specifically a contractual position), these contain the corresponding contract number and the position values of the contract. A release order is an order (or order request from which an order is then generated) with a reference to a framework contract. This is important, because it is good to know that at least for the statistics of release orders in SAP®, tracking operations such as the entry of goods and invoices at first do not play any role in the registration. .

. .