Fig. 4 – Call documentation of a quantitative contract in the EKAB table I hope you enjoyed the entry into the field of framework contracts and that we will soon meet here for the second part „Framework contracts – Documentation on demand“. For completeness, the following screenshot shows the EKAB table for the value contract 4600000030 in Example 2. Release orders can be identified in the same way: supplier selection is an important process in the purchasing cycle. Suppliers can be selected through the offer process. After pre-selecting a supplier, an organization enters into an agreement with that particular supplier to deliver certain items under certain conditions. When an agreement is concluded, a formal contract is usually signed with the supplier. A framework contract is therefore a long-term sales contract with a supplier. − A framework contract can be composed of the following two types – To refer to default orders, you can use z.B.
the ME23N transaction; T-Code ME33K shows you contracts, and ME33L is the right thing to do for delivery plans. You can see that the category of supporting documents Mnemonik K and L is also present in part in the transactions. 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. The above categories of supporting documents are assigned to each purchase receipt in the EKKO head data table as an attribute (field: EKKO_BSTYP). This means that the class of documents allows us to distinguish delivery plans from other contracts. But how to distinguish value contracts from volume contracts? This is where the type of evidence described above begins: in the standard is the type of proof „MK“ for volume contracts and „WK“ for value contracts. However, both types of records have the same class of „K“ records.
While document categories are primarily used for categorization, document types are often used to customize them, i.e. assign attributes to document types that are then used to organize/control processes in a system. You can also find them in the EKKO table, the field name is EKKO_BSART. In particular, orders for the release of a framework agreement for value and volume contracts are included in a separate table called EKAB. To view the entries, the SAP® SE16 transaction can be used. The following figure shows the release orders in the EAKB table filtered by „our“ volume contract 4600000062 of the first example. . . .