In this regard, the system does not take into account the remaining classifications after the 7th day of the JIT or the 180th day of forecast from today as being maintained in the creation profile (release horizon: total working days). 1.) Concept and why is it used in delivery plans? They establish delivery planning procedures (delivery plans) that include classifications for a given delivery plan item. These are snapshots of the entire delivery plan that is stored in the system at certain times. It generates an SA version based on the creation policy and the entries on the input image for creating its version. If there is a creation profile, it aggregates the release dates (i.e. the expected dates and quantities). Create a versioning profile with the following details on the Aggregation tab. The following criteria can also be established in the profile: 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. 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.
Generate JIT & Forecast Release without assigning a versioning profile. 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. .