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. Framework agreements are an important issue that we must constantly address in our analysis of procurement data. Unlike individual contracts, which are often ad hoc, framework agreements are constructs for a longer-term business relationship. To return to standard commands, you can use z.B the ME23N transaction. T-code ME33K shows you contracts, and ME33L is correct for delivery plans. You can see that the category of Mnemonics K and L vouchers also appears in part in bookings. You can clearly display the category (K or L) and the type of document associated (LP, WK, MK).
Our system includes 154 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. In value contracts, the quantity of items is often secondary, since the total value of the contract counts. For example, a “facility management” contract of 1,000,000 euros could be concluded with a supplier. This includes the three building cleaning, repair and disposal items. In this case, individual quantities can be attributed in a much less concrete way and an overall structure is more judicious. Another example would be office equipment (pens, post-it notebooks), too “singular” in individual articles to be punished in a framework agreement. Data model — commands and framework agreements that I don`t want for that. I just need a query between tables. To get the packaging mode for the delivery plan, go first to Table A016, enter the corresponding details, delivery plan number, item and call the condition number (KNUMH). With this condition number, you enter the KONP table and enter the condition number in KNUMH.
This is the unique key in both tables. Here you get types of conditions. Agreements are now at the origin of a long-term structured procurement process. But what about individual buying on the concrete basis of an agreement? We are also talking about call-offs. These are specific specific markets, in reference to the framework agreement. How you can determine these searches by analyzing the data, the tables in which they are recorded, and whether the information about goods and invoices is relevant or relevant in this context – this is something for the next post in the series. 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”. In the case of value contracts where different un quantified positions are often added to a cumulative value of the contract, which is then determined at the level of the occupancy head (EKKO_KTWRT). Since different quantities per item (and therefore target quantities) tend to play a minor or not at all, and are often used for services, etc., you will probably find a definition at the level of material groups (field: EKPO_MATKL).