Data Model – Orders and Structure Agreements Once you have defined the types of documents for delivery plans, select the line for the type of document and double-click on Authorized Item Categories. Manage on the screen Categories of items allowed for The category of articles, as shown in the following table. These categories of items can be configured to meet business requirements. This configuration determines the categories of items that can be selected by the user when developing the delivery plan for a specific use site. In this step, an exit profile for delivery plans is managed with a certificate of authorization. This profile determines the execution strategy and how delays and immediate requirements are taken into account when implementing. To maintain the exit profile, go to IMG (SPRO) > Materials Management > purchase > planning contract > manage SA`s establishment profile with the sharing document. 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. 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. 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). The classic relational data model avoids redundancy in . B data is divided into head and article data for supporting documents and transactions. In the head of the room, you will find data valid for the entire document (and all the elements). In a conventional order scenario, the occupancy head contains attributes such as creditor, probation, order date and payment terms. On the other hand, the current data on order positions are the order quantity, the category of goods, the material number and the price. How do you see the difference between SAP® whether it is a normal order or a framework agreement – and, if so, what kind of agreement? Experienced SAP users® among you will of course cite the LaPi Site, which is quite true. Nevertheless, it is worth having a more detailed look. 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.