With SAP S/4HANA Logistics` Sourcing and Procurement LoB, it is possible to use the SAP Best Practices activation approach to tailor delivery plans. However, if you use the traditional customizing approach, this blog post can be helpful. 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. Those who work with the traditional approach to adjusting delivery plans in SAP know that defining types and categories as well as maintaining release creation profiles can be a struggle if you don`t know what you`re doing. The above information should prove useful for those working in sourcing and as an introduction to those starting with SAP. 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. The following tables include the default settings for SAP. The IMG (SPRO) allows you to define additional types of delivery plan through IMG (SPRO) > > purchases > delivery plan > type of document. Could you tell me the table in which the delivery plan data for purchase planning approval is stored. A sharing profile determines the period during which versions (delivery plan types) are generated against a delivery plan and passed to the provider. This also controls the frequency of versioning; the aggregation of the quantities provided for from the day following the establishment of the release; and the carrying out of a tolerance check. 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. #37 LDUHR – Loading time (local time) #69 NO_SCEM – Order not transferred to SCEM #9 AMENG – Previous quantity (delivery items) EKETH – Delivery plans: History tables.
. #73 DATESHIFT_NUMBER – number of extensions from the current date. . Select the row for each item category and double-click the link – document type order requirement. In the edit view, set “Link required document type of order”: Preview of allowed document tracking. . You already have an active moderator notification for this content. #52 DELIVERY DATE – Delivery date at the place of delivery. . If you have an answer to this question, use the form of your answer at the bottom of the page instead. #46 GEO_ROUTE – Description of a geographical route Your complete guide to SAP S/4HANA Sourcing and Procurement is available here! Get step-by-step instructions for setting up purchasing, invoicing, supplier management and evaluation, and centralized purchasing. Learn how to integrate SAP S/4HANA with SAP Ariba, SAP Fieldglass and more..