The above voucher categories are assigned as attributes to each purchase proof in the EKKO head data table (field: EKKO_BSTYP). This means that the document category allows us to distinguish delivery plans from other contracts. But how do you distinguish value contracts from volume contracts? This is where the storm table described above comes in: in the standard, the type of contract “MK” is for volume contracts and “WK” for value contracts. However, both types of documents have the same category of “K” document. While document categories are primarily used for categorization, document types are often used to customize, i.e. attributes are assigned to document types, which are then used to organize the process/control process in a system. You can also be in the EKKO table, the field name is EKKO_BSART. To create a context, we start with ordinary tasks: as far as the database is concerned, these are stored in SAP® in the tables EKKO (command head) and EKPO (command position). If you want to track it, you can use z.B. the table browser SE16 to view the contents of the table. – Copy the order note (TVCPF, BM1 and BM3 tables) Let`s start with examples of different types of framework agreements. Here`s what I`ll see: it`s a little more technical, but here, for the sake of completeness, a screenshot of the document type table with the customizing settings in SAP® if they are needed for data analysis purposes.
Numbering circles for the corresponding types of proofs, z.B. Field selection settings, etc., are included in this table: please indicate the default table in which contract details and calendar details are stored. So if we add types of proofs to our table above, the situation is this (this time I omitted the categories of proofs and types of proofs that are not relevant to the contract: table T166P SAP for – Articles in purchase print In this blog, I would like to give you an overview of the framework agreements in SAP® in the purchasing module. In addition to the design of the concept itself, I give you an overview of its assignment from the point of view of data analysis, that is, SAP® tables and field levels. I hope that you have enjoyed addressing the issue of framework agreements and that we will soon meet again for the second part of the “Call Agreements”. Now it`s becoming exciting (at least for data analysts): framework agreements such as quantity 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. – Assigning SAP transactions in the types of supporting documents (tables T169, T169F). Here are the details of each field in this table.
You`ll find the description, type of data and assigned lenses for each field in the EKCPI table. – Packaging groups (tables T6B2, T6B2T, T6B2F) Contracts are often superior. This may be the case with SAP® because the buying organization is essential (and the work that may be related to the purchase organization).