From a risk perspective, the topic of framework contracts offers a number of exciting starting points, including: it is interesting to consider what a contract sharing contract actually means to SAP® from a data analysis perspective: framework agreement sharing contracts for value and volume contracts are, among others, recorded 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 according to « our » volume contract 4600000062 in the first example. In this step, a release profile is maintained for delivery plans with proof of release. This profile determines the output creation strategy and how backlog and immediate requirements will be taken into account when creating output. To maintain the release profile, you can go to IMG (SPRO) > the materials > purchasing industry > delivery plan > release profile for SA with proof of sharing. You define it in the output class that you will find in CL02. 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: with SAP S/4HANA Logistics` Sourcing and Procurement LoB, it is possible to use SAP Best Practices` activation approach to tailor delivery plans. However, if you use the traditional customizing approach, this blog post can be helpful. Interestingly, although the statistics for release orders are able to show a total of four purchase receipts, the cumulative sum for the first three is 0. Only the last order with order number 4500017169 and position 10 shows a series of releases of 2 tons, thus reducing the open target quantity from 250 tons to 248 tons.
After you define the document types for delivery plans, select the document type row and double-click the allowed item categories. On the screen, maintain the categories of items allowed for the document type, as shown in the following table. These position categories can be configured according to the corporate requirement. This configuration defines the categories of positions that can be selected by the user for a particular document type when creating the delivery plan. . . .