It`s a little more technical, but here, for the sake of completeness, a screenshot of the document type table with customizing settings in SAP® if they are needed for data analysis purposes. Numbering circuits for the corresponding types of proofs, for example. B Field selection parameters, etc., are included in this table: the above voucher categories are assigned as an attribute to each supporting piece 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. Data model – commands and framework agreements You can clearly display the category (K or L) and the corresponding number of occupants (LP, WK, MK). Our system includes 154 agreements. The most important points to consider in a framework agreement are, as with other purchase documents, a framework agreement consists of the following: a framework agreement can be the following two types — now that we have developed framework agreements that are data — in tables where you really think they are standard orders — and how to identify them — by type of document and by type of document — let us look at certain aspects of the process. Contracts are often superior in nature.
This may be the case with SAP® because the buying organization is essential (and the work that may be related to the purchase organization). The purchase organization is shown in the EKKO table for each agreement (field: EKKO_EKORG). However, in high-demand structures, large contracts (for example. B the purchase of laptops throughout the company) are negotiated centrally and can then be used in a decentralized manner. In this case, it is possible to cooperate with near-superior purchasing organizations, which are attached to decentralized purchasing organizations as a reference purchasing organization. They can then use and consult framework agreements established under the reference purchasing agency. From the data analyst`s perspective, you will find in table T024Z the allocation of purchasing organizations (field: T024Z_EKORG) to possible business reference organizations (field: T024Z_EKORZ). Futures agreements, on the other hand, are based more on quantities and, in addition, on concrete quantities of delivery on certain delivery dates (we are talking about dates).
Quite simply, these are more restrictive quantitative contracts – but in the analysis of the data in SAP® they appear separately with their own category of supporting documents in relation to volume or value contracts. But later. A contract is a long-term framework agreement between a lender and a customer via pre-defined equipment or service over a period of time. There are two types of contracts – by clicking on the hat symbol (which recalls head data?) you get to where the target value of the contract is visible (in this case, of course, the sum of the two elements). I will now take a closer look at the target values for articles and heads in framework agreements.