The following criteria can also be defined in the profile: the system does not take into account the remaining classifications after the 7th day in the JIT or the 180th day of forecasting from today, as is kept in the establishment profile (release horizon: overall working days). In this step, an exit profile for delivery plans is managed with a certificate of authorization. This profile determines the execution strategy and how delays and immediate requirements are taken into account when implementing. To maintain the exit profile, go to IMG (SPRO) > Materials Management > purchase > planning contract > manage SA`s establishment profile with the sharing document. After setting the types of documents for delivery plans, select the line for the type of document and double-click on Authorized Item Categories. Manage on the screen Categories of items allowed for The category of articles, as shown in the following table. These categories of items can be configured to meet business requirements. This configuration determines the categories of items that can be selected by the user when developing the delivery plan for a specific use site. The following tables contain SAP`s default settings; Additional delivery document types can be defined based on business requirements via IMG (SPRO) > Materials Management > purchases > delivery plan > Define types of proofs. Those who work with the traditional approach to customize delivery plans in SAP know that setting types and categories as well as maintaining output profiles can be difficult if you don`t know what you`re doing.
The above information should be a reminder for those who are in the acquisition and introduction for those who started with SAP. Delivery plans are defined and managed as supporting documentation in the system. It is possible to group these documents into different types of documents according to commercial requirements. First, you need to define the types of document and their attributes when adjusting. A validation profile is used to determine the period during which sharing (delivery modes) of a delivery plan is generated and transmitted to the creditor. It also controls the parity of the versions; Aggregation of expected quantities from the day after the date of availability; and conducting a tolerance test. With SAP S/4HANA Logistics` LoB sourcing and procurement system, SAP`s best practice activation approach can be used to customize delivery plans. However, if you use the traditional approach of customizing, this blog post can be helpful. When a creation profile is available, it will aggregate the release data (i.e. expected) in quantities and dates. Generate JIT – Prognose-Release without assigning a publication profile.
It generates an SA version in accordance with the creative strategy and inputs on the home screen for the creation of SA. The profile of the version is the profile that actually makes the difference between the JIT calendar and the forecast schedule. If you don`t assign an exit profile to the delivery plan, there`s no difference between JIT and the delivery plan. This can be included in the expression of the LPJ1-LPH1 messages for the same calendar lines. In addition, we control the schedules of the lines to be sent and in which mode of sharing. Z.B. NEw only, modified, next date, etc. Create a version creation profile with the following details in the Aggregation tab. 1.) and why is it used in delivery plans? They establish delivery plan releases (delivery plans) that include classifications of a particular delivery plan item.