Scheduling Agreement Header Table In Sap

VBAK &you can get the details of the VBAP article for this vbeln. Then, with this condition, the data set no and the element chk the KONP table. To create context, we start with normal unique commands: as far as the database is concerned, they are recorded in SAP® in the EKKO (command head) and EKPO (command position) tables. For example, if you want to track, you can use the SE16 browser to view the contents of the table. It`s a bit more technical, but to be complete, it`s a screenshot of the document type table with customizing settings in SAP® if they`re needed for data analysis purposes. This table contains circles of numbers for the corresponding document types, for example.B. Field selection parameters, etc.: delivery plans are defined and managed as documents in the system. It is possible to group these documents under different types of documents depending on the business requirements. First, you need to define the document types and their attributes in customizing. Framework agreements such as volume contracts, value contracts and delivery plans are not stored in their own tables, but also in the EKKO and EKPO tables. Don`t be confused by names or take them to the letter. I hope that you have appreciated the entry into the issue of framework agreements and that we will soon meet for the second part , `Framework agreements – documentation on demand`.

The agreements laid the foundation for long-term structured procurement. But concretely, what is the individual purchase on the basis of an agreement? Here too, we talk about “call-offs”. These are specific specific contracts, with reference to the framework agreement. How you can identify these searches through data analysis, in which tables they are recorded, and whether the entries of goods and invoices are relevant or relevant in this context, this is something for the next blog post in the series. To refer to default commands, 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. Framework contracts are an important issue that we must constantly address in our data analytics for procurement. Unlike individual contracts, which are often ad hoc, framework contracts are constructions aimed at a longer-term business relationship.

Therefore, if we add document types to our table above, it looks like this (this time I omitted document categories and document types that are not related to the contract: the classic relational data model avoids redundancy, for example by dividing data into head and position data for the document and transactions…