SAP IBP for response and supply

A user can now create multi-purpose resources that can be used to constrain production, purchasing and stock transfer quantities simultaneously. Additionally, a new resource period type is introduced as an attribute on the resource for all resource types to enable time aggregated resource consumption per resource.

Value Proposition

• Model constraints on an aggregated level
• Support additional use cases such as:
  • Use multi-purpose resource as a production resource to have multiple production resources with different period types
  • Use of a multi-purpose resource as an aggregated constraint

Capabilities

• New resource type multi-purpose resource with flexible source of supply assignment possibilities
• Model all existing resources on an aggregated level
• Flexible period type for all resources

This feature is available only in planning areas based on the flexible sample planning area SAP7F.

If you would like to start using multi-purpose resources, but you have already created the RESOURCELOCATION virtual master data in your planning area, you need to adjust the configuration.

Planning Level DAYPDSRES has to updated accoring to the following:

1. In the Planning Areas app, remove all references to the RESOURCELOCATION virtual master data from the Source column for all attributes of the Location master data, but keep this value for at least one attribute which is not relevant for multi-purpose resources, for example, WORKCENTER.  See the screenshot to the right.
2. Save your changes. The Source Assignment for Attributes field must be now visible and set to User-Defined

The planning area has to be reactivated.

A new resource type is available (type = 4, multi-purpose resource), which can be used as a production and a transportation resource at the same time.

The following resource attributes are available:

• Required: Resource ID, Resource Type, Capacity Consumption Policy (only E - consumption at end is supported), Bucket UoM, Display Bucket UoM, Resource Time Zone
• Optional: Resource Description, Default Capacity, Resource Period Type, Marked for Deletion
• The rest of the attributes must be empty.

The new resource type can be maintained with CI-DS and data integration for the RESOURCE master data.

New attribute Resource Period Type can be used to define the period type of the resource on the resource level. It enables different period types per resource. The period type defines how the defined resource capacity is considered and consumed. The attribute can be used for the new multi-purpose resources and for the existing production and transportation resources as well.

Allowed values: empty (default), D (Day), W (Week), TW (Technical Week), M (Month), Q (Quarter), Y (Year), where the ID is fix, the description is translatable. The default value means that the Resource Period Type setting is read from the Settings for Order-based Planning.

If the period type is not valid due to the time profile setup (the used period type does not exist in the time profile) the master data can be saved, but the default value (Settings for Order-based Planing) is used during the planning run.

Multi-purpose resources can be assigned to any type of source of supply freely: production, external procurement or internal stock transfer.

The assignment can be maintained with CI-DS and data integration for the PDSRES and TLANERESOURCE master data.

Optionally, the resource assignment can be maintained via the Rule-based Master Data Maintenance on an aggregated level (e.g. prudct family). See the next section in this document for en example.

The screenshots show an example where the multi-purpose is used for constraining both production and procurement simultaneously. The production data structure is constrained by both a production and a multi-purpose resource.

• Any resources can be set up as aggregated constraints via the Manage Rules for Master Data Maintenance app. In this section, we will look at an example with multi-purpose resources as aggregated constraints, but the same approach can be used to configure aggregated production resources and aggregated transportation resources.
• There are various use cases for rule-based master data maintenance, including assigning resources to source of supply on an aggregated level. The tool has been delivered with release 2211.
• On the next slides, we provide a step by step setup for multi-purpose resources as aggregated constraints for production and procurement in a factory. Some finished products are produced (Phone A and Phone B), some are procured (Phone C and Phone D). All products belong to the PHONE product group.

Maintain a new resource that serves as an aggregated constraints.

This example has a resource created in the Manage Master Data app:

• Resource Type = 4 (Multi-purpose Resource)
• Period Type = Week (time aggregated consideration and consumption of resource capacity)
• Capacity Consumption Policy = E (as this resource will be used for production and procurement, only consumption at end is allowed)

This new simple master data type defines the aggregated level. In this example, the aggregated constraint is relevant at product group level.

Two rules are required: one for PDS resource assignments and another one for transportation resource assignments. The rules are configured in the Manage Rules for Master Data Maintenance app.

Execute application job Rule-Based Master Data Maintenance with each previously created rules.

All products that belong to product group PHONE have now a multi-purpose resource constraint. Please note that the component materials (product group COMP) are not constrained by this aggregated constraint in same factory.

Existing consumption key figures can be used to display the consumption of multi-purpose resources in the planning views in Planner Workspaces or in the Excel add-in.

Similarly to production and transportation resources, Fiori app displays the consumption details for multi-purpose resources on both Supply and Resource Usage tabs.

When a multi-purpose constraint inhibits the on-time fulfillment of a demand, a resource gating factor is displayed in the View Gating Factors, View Confirmations and in the Order Network.

Existing global Capacity constraint switch is valid for all resources including multi-purpose resource.

New rule-based section Multi-Purpose Capacity Rule enables rule-based inactivation of multi-purpose resources.

Additionally, attribute Resource Period Type is now available for all Capacity Rules.

Not supported

• App Supply Chain Dependencies doesn't show supply chain networks connected by multi-purpose resources
• No minimum constraints are available
• Further aggregated constraints, for example inventory constraints are not supported

• The action "Create" at top of the Planned Distribution Orders list allows to interactively create a new Stock Transfer Requisition, Deployment Requisition, Purchase Requisition, or Subcontracting Purchase Requisition
• An order type is active when a transportation lane exists for this order type which fits to the current filter and has a valid transportation group assigned (is applicable to Transportation Load Building)
• If filter button "Loadable" is active then only requisitions for the transportation group of the selected transportation load can be created
• If filter button "All" is active then requisitions for all transportation groups which fits to the current workbook filter can be created

• The "Create" dialog lets you first select the target location product of the new requisition and then secondly the transportation lane
• If only one transportation lane exists for the target location product then this lane is automatically selected
• The requisition is created by considering all relevant durations and calendars of the transportation lane, but by ignoring all kinds of constraints such as lot size, validity, resource capacity, or freeze horizon
• The requisition is scheduled backwards from the entered planned date. A goods receipt date which would fit to a goods receipt date of a transportation load cannot be defined for the new requisition. In order to get a desired goods receipt date, the receiving calendar, goods receipt processing time, and transportation calendar must be considered when entering the planned date.
• The requisition is created even if it's goods receipt date does not match the selected time periods. In this case, the requisition will not be visible in the Transportation Load Building component but it will be saved to the version or scenario when choosing Data - Save.

• Transportation loads can be built for subcontracting products by assigning a transportation group to the subcontracting purchasing transportation lane (stock transfer type = 3)
• A transportation group can have a mix of normal purchasing (stock transfer type = 0) and subcontracting (stock transfer type = 3) lanes, but all assigned lanes must have the same target location, mode of transport, and supplier = subcontractor
• A TLB run cannot split the quantity of a subcontracting purchase requisition, that means either the entire quantity is part of one load or it is not loaded at all
• The TLB component in Planner Workspaces app allows to interactively create and load subcontracting purchase requisitions

Build Transportation Loads for Subcontracting Components Provisioning

• Transportation loads can be built for component stock transfers (the component stock transfer lanes exist in IBP, but the stock transfer requistions are not integrated to ERP).
• The created transportation loads provide only visibility into the loading capacity demand of component stock transfers. The load stock transfer requisitions cannot be integrated to ERP and must be manually unloaded or deleted in IBP afterwards.

Problem that was to be solved

• In production planning integration mode short-term production planning and detailed scheduling delegated (3)
  • short-term production planning is owned by PPDS
  • planned orders created by mid-to-long term order-based runs are handed over to PP/DS, such they are replaced by PP/DS orders with the same quantity and the same source of supply (hand-over step)
  • the PP/DS orders generated during hand-over are not compliant with the lot-size constraints that apply for PPDS planning runs, so there is a need to re-plan the OBP planning results in PPDS before detailed scheduling
• However, the PP Heuristics that are run in the short-term are infinite
  • the PP/DS production plan that results from infinite PP heuristics runs may not adhere appropriately to the optimized OBP plan with respect to production quantities or source of supply decisions:
    • OBP's prebuild decisions for capacity constraints or seasonal demand beyond the PPDS horizon cannot be protected
    • OBP's late or non-delivery decisions are ignored and every demand is fulfilled in time infinitely
  • Infinite planning may be OK for uncritical upstream components. However, there are always key products or components such as Master Production Scheduling (MPS) items where PP/DS has to adhere to the OBP plan strictly, even in the short-term, while there is a need to cut bucket sized OBP orders into orders that fulfil PP/DS lot size requirements

How the problem was solved

With a consulting note* SAP delivers a sample BAdI implementation which enables to change PP Heuristic logic such that

• PPDS production planning is decoupled from net demand
• Replaces all
  • OBP planned orders (external), that are due for handover to PP/DS (DPS handover time in the past)
  • unfixed PPDS planned orders

between the planning time fence and the PPDS Horizon by creating new planned orders such that they:

• • fulfill lot-size constraints
  • stick to the production version of the planned order that is deleted

while:

• • • lot-size surplus is consumed by the subsequent planned orders that are replaced
• Table SYPP_MARC_EXT has been opened for extension fields
  • Delivered sample BAdI logic applies to all location products in PPIM 3
  • By extending SYPP_MARC_EXT with a custom field the sample logic can be restricted to a relevant subset of PPIM 3 location products

*3291712 - Preserve the Overall Order-Based Planning Outcome with Production Planning Integration Mode 3 after Rolling into the PP/DS Horizon

https://launchpad.support.sap.com/#/notes/3291712

Differentiation of orders for replanning vs. protection in an enhanced PP Heuristics Run for prebuild for location products in production planning integration mode 3

This visual shows you the full extent of processes in case of production planning integration for the OBP application. In this case S&OP and Tactical Supply planning as a key figure based high-level application is not used and the OBP network plan is created in the form of orders directly. The order based plan is also available in PP/DS via order-to-order integration into ERP and PP/DS so that same demand and supply picture is available in all systems. PP/DS is allowed to plan on the same location products currently. The planning scope may include PP heuristic or PPO in the short term as well as DS heuristics or DS optimizer to create a detailed schedule.

The planning in PP/DS is factory/plant specific as opposed to the network plan from OBP. The purpose of PP/DS is to generate a production plan with is feasible and directly releasable to production when production orders are created. Based on the production plan which is available in OBP real time a short term production plan as of PP/DS can be deployed into the distribution network using OBP. The newly available TLB function prepares bundling to transport and helps to create ready made purchase orders for procurement execution.

Enhanced Standard Lot Size Heuristic: (1) neglects net demand/projected stock, (2) adheres to cumulated planned production quantities per source of supply, (3) deviates slightly for lot size surplus

Current Date April 4th / DPS Horizon: 60 days

Current Date April 4th / Planning Time Fence 30 days / PP/DS Horizon: 90 days

Planned Order 50336 has a different Production Version 2

Current Date April 4th / Planning Time Fence 30 days / PP/DS Horizon: 90 days

Planned Order 50347 has a different Production Version 2

Current Date April 4th / DPS Horizon: 60 days

https://launchpad.support.sap.com/#/notes/3291712

Response and Supply offers 2 options to determine the Minimum Remaining Shelf Life (MRSL) requirement for Forecasts

• Maintenance of the MRSL in the Location Product Master Data
• Flexible Determination of Minimum Remaining Shelf Life via Key Figure (New)

For the determination of MRSL for Sales Orders two options are available

• MRSL is derived from batch assigned in ERP (difference between the delivery date and the shelf life expiration date of the batch)
• MRSL is determined via BADI implementation

Modelling of MRSL Key Figure

As a pre-condition the solution requires a key figure that deliveres an MRSL value for specific attribute combinations

In a nutshell the MRSL values are maintained as attribute value of Master Data Types

The documentation includes a modelling guideline based on an example

Assign Key Figure in OBP based settings

In the App „Settinggs for Order-based Planning" the key figure needs to be assigned in section Forecast.

Note: If no key figure is assigned, the solution will take the MRSL value from the Location Product Master Data

The Key Figure is based on 3 different Master Data Types, processed in the defined sequence

• Product / Customer Classification
• Customer Region / Product Group
• Location / Product

For these the Master Data depicted on the right side has been maintained.

Guidance

If you're planning full networks, we recommend that you use the same time aggregation profile for deployment planning as you used for supply planning.

If the deployment scope is split into multiple subnetworks, we recommend that you use the same time aggregation profile for all subnetworks in the network.

• You can also have subnetworks in the network that you plan without time aggregation.
• The time aggregation profile of the subnetworks you plan in the deployment process should be the same time aggregation profile as you used for supply planning.

If location products are in the planning scope of both supply planning runs as well as deployment runs, we recommend that these planning runs either both use the same time aggregation profile or that in neither of them telescopic planning is applied.

But no external key figures are availableIn particular missing on PRODLOCDEMAND and PRODLOCPEG

New and Delivered in 2305

• New external Data Sources
  • STD_SFC_REV for (confirmed) Order Revenue
  • STD_MALO_ASU_REV for pegged Revenue
• New external Key Figures
  • Order Revenue: TOTAL_REVENUE
  • Confirmed Revenue
    • In Time: REVENUE_CONFIRMED_INTIME
    • Late: REVENUE_CONFIRMED_LATE
  • Pegged Revenue: PEGGED_REVENUE

OBP Restrictions

Only for analytical case. Currency not used in any planning run or other algorithm

Clash with Fiori UI where the amount is always display in document currency

In particular in in PWS: Key figure display in target currency, Order Detail List then displayed in document currency

Forecast has no Amount. Can only be used in pure order use case like Revenue at Risk

PLOBJ creation not automatic but by Report: Generate Planning Objects for External Key Figures

Use Currency Conversion in IBP

+ Conversion Configuration in Key Figure Definition

MDTs:

• Currency with Key CURRID as MDT
• Reference MDT for CURRENCYTO with CURRTOID as Key
• Compound MDT with CURRID and CURRTOID as Key + Exchange Rate as (numeric) Attribute (No Numerator/Denominator here possible because of Disaggregation Issues)

Planning level

• Currency + EXCHANGERATE Key figure (could also be Attribute as Key figure):
  • Conversion Source and root: CURRID
  • Conversion Target and root: CURRTOID
• Normal PL must now include CURRID as root
  • Add Exchange rate in Calculation to Base and Calculate Key Figures to use
  • In addition Use Helper Key figure for Planning Run if needed, but CC usually not the case
• Target Currency Key Figure having as CURRTOID as target
  • No additional key figure here. Normal Key figure with currency conversion also visible there

https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/bf99e931b8d44aafb4e306ec3602cbdd/561e135510fdec14e10000000a4450e5.html?version=2008

https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/bf99e931b8d44aafb4e306ec3602cbdd/3a36cbe2bee6433f97befb3fe19e8f1d.html?version=2008

Remember also existing Extractors for Currency and - Conversion

As any other SFC master data type, currency and exchange rate not filled with RTI

CI-DS can be used using extractors for 2 alternatives

1. Currency with for attribute as key figure (with constant currency)

/IBP/CURRENCY_ATTR (currency attributes)

/IBP/CURRENCY_TEXT (currency descriptions and attributes)

Reading directly from tables  TCURC and TCUR

1. Using time dependent key figure
2. Exchange using /IBP/EXCHANGE_RATES_KF extractor rate reading directly from TCUR. MDT extractor /IBP/EXCHANGE_RATE_ATTR only needed for key figure as attribute)

https://help.sap.com/docs/SAP_ERP_SUPPLYCHAIN_INTEGRATION_ADDON_FOR_SAP_INTEGRATED_BUSINESS_PLANNING/ccfe175310e04be9b38087c8df73974d/65c1296d49504768aeec0220eca0dd15.html?version=1.1%20SP13

https://help.sap.com/docs/SAP_ERP_SUPPLYCHAIN_INTEGRATION_ADDON_FOR_SAP_INTEGRATED_BUSINESS_PLANNING/ccfe175310e04be9b38087c8df73974d/db5ec84cee8c474e8466add5a1b6a065.html?version=1.1%20SP13

RTI Solution

• Use CIF Interface Table IT_ATPFIELD for Sales Order Inbound to provide CUST_ATTR fields
  • Customer then has to implement Enhancement Spot /BADI on S/4 Side for CIF_SL_DOC_MAP_IBP to provide CUST_ATTR* fields in IT_ATPFIELD
  • CIF IBP inbound for sales order take over CUST_ATTR* fields from IT_ATPFIELD into sales CUST_ATTR* fields.
  • Valid field conversion is checked, in case of failure the SO inbound stops with error message indicating which field causes the failure
  • Only order Type sales order (SD_ITM) is supported (what happens if customers provides this for outbound deliveries?)
• See Consulting note for example BADI Implementation provided (note 3288554, will be released in 05)

And…

• All other OBP Apps
• Allocations
• Use for Filter or Drill in Apps and Excel

Supply Usage and Gating Factors

The supply planning and the deployment run calculate in addition to the supply plan and pegging, supply usage information and gating factors like

• Detailed Pegging
• Requested Dates
• Gating Orders
• Gating Factors

These data help to analyze the planning results in Fiori applications like

• Analyze Supply Usage,
• View gating Factors or
• Order Network.

They are the basis for key figures showing quantities at requested dates or gating order quantities.

Supply usage and gating factors are always calculated for the complete network. If the planning cycle is split in to multiple steps using subnetwork planning, intermediate planning results might lead to inconsistent and misleading supply usage and gating factors for the planner.

In supply planning runs and deployment runs, you can now skip the generation of supply usage and gating factor information.

Supply usage and gating factors can be calculated as part of the last subnetwork planning run or using the new job template "Order-Based Planning: Supply Usage and Gating Factor Run"

Meeting Notes: 26.05.2021:

-Udo Summ / Florian Roeger / Thomas Fiebig

1

Frage Udo: Werden im PRP DPS Aktiv vs. DistrFreeze Aktiv verprobt?

Antwort: Nein nicht nötig, das haben wir nur für PPIM 1 (Inhouse, zweistufig) gebraucht, weil die LX Aufträge nicht in Fertigungsaufträge konvertierbar sind.

2

Frage Florian: Sollen beide DPS Switches (Inhouse Distribution) getrennt schaltbar sein.

Antwort: Ja, wenn auch nich jede Konstellation für jedes PPIM Sinn macht. Die Alternativen wären nicht besser:

A1 Ein gemeinsamer Switch wäre ein incompatible Change für PPIM 0, 1, 3, 9. Im Übrigen zu einschränkend

A2 Den Distribution switch nur einzuschalten, wenn auch der Production Switch eingeschaltet ist, wäre zu kompliziert in der Umsetzung. Ebenfalls zu einschränkend.Die sinnvollen Konstellationen werden per PPIM dokumentiert. Bei Zuwiderhandlungen brechen Prozesse nicht. Das ist der Preis dafür, dass wir einen PPIM unabhängigen Switch gebaut haben.

Empfehlungen:

PPIM 0/9: Keine Empfehlung. Beliebig je nach Anwendungsgrund aktiv setzen

PPIM 1: Nur den Production Switch im Wechsel (wöchentlich/täglich) aktiv setzen

PPIM 3: Nur den Production Switch dauerhaft aktiv setzen

PPIM 4: Beide Switches gemeinsam und dauerhaft aktiv setzen

PPIM 2, 5: Irrelevant

Getrennte Switches für PPIM 0 machen jedenfalls in jeder Konstellation Sinn:

PPIM 0 Getrennt schaltbar, wenn es einen Planning Policy Grund für eine Short-Term Sperre gibt, also einen Grund über das Minimum (eines oder beides der Freeze Horizons), eines der beiden Horizonte auf DPS (Mid-term/Rough Cut) zu verlängern.

3

Keine grundsätzlichen Einwände hinsichtlich Machbarkeit.

DPS Horizon for STRs and Purchase RequisitionsWhy needed?

The production freeze horizon and the distribution freeze horizons in order-based planning correspond to the field planning time fence in SAP S/4H. The purpose of the planning time fence is to protect short-term execution from planning changes in a horizon where execution orders have to be created and released to be executed within lead time at latest.

The purpose of the DPS Horizon is to protect short-term planners who are interactively improving or detailing out automated operational plans from short-term planning changes in an extended horizon for detailed planning.

PPIM No detailed planning and scheduling (0)

• Flipping horizons between DPS and Production also makes sense for purchasing and distribution
• DPS Horizon could be used for order bundling in execution, for example

PPIMs with planning or scheduling in PPDS

• In OBP there is a distinction between distribution and production freeze
• In PP/DS there is only the PP/DS Horizon as counterpart
  • If there is a freeze horizon, the expectation in PPDS is that Procurement Type does not matter for procurement type X
• PPIM Detailed Scheduling delegated (1)
  • Within DPS Horizon, OBP had be enabled not to change procurement plan while optimizing the make schedule
• PPIM Short-term production planning and detailed scheduling delegated (3)
  • Procurement Types was needed F and X in addition to Procurement Type E with IBP release 2308

Current Date March 31st

Planning situation in SAP IBP Order-based Planning after supply runusing a Planning Run Profile where DPS Horizon is inactive for both production and distribution

Planning situation in SAP IBP Order-based Planning after supply runusing a Planning Run Profile where the DPS Horizon is active for production only

Planning situation in SAP IBP Order-based Planning after supply runusing a Planning Run Profile where the DPS Horizon is active for distribution only

Planning situation in SAP IBP Order-based Planning after supply runusing a Planning Run Profile where the DPS Horizon active for both, production and distribution

Planning situation in SAP IBP Order-based Planning after supply runPlanning Run Profile: Rule based activation using PPIM

https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/feae3cea3cc549aaa9d9de7d363a83e6/79c4182e754e45b8aec87b48daea08a4.html?locale=en-US

https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/09154e4f345c46edb1d74f782be4d9bd/500bbde40bec414cb95f635e71c8d051.html?locale=en-US

• The distribution freeze horizon can now be defined at the transportation lane and thereby can be set differently for each mode of transport
• The production freeze horizon can now be defined at the production data structure and thereby can be set differently for each production version
• Attribute "Freeze Horizon" defines the number of days. Possible values are equal or larger than 0. Default value is 0.
• Attribute "Freeze Horizon Policy" specifies whether the end date or the start date of planned elements is considered. Possible values are empty (end date, default value) and "S" (start date).
• The new attributes are available in order-based planning models based on external master data and based on flexible master data. See the linked application help pages for more information on how to set these attributes in each model.

https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/09154e4f345c46edb1d74f782be4d9bd/f0bc96c626504eb78cf7a95cf24c973c.html?locale=en-US

https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/343592b029c94595896e51477ca08505/26775be7e03540af88ab8830a108c744.html?locale=en-US

• In order to use the freeze horizon defined at the source of supply, the settings "Use Master Data Defined for Transportation Lane / Production Data Structure" must be set to yes in the app Settings for Order-Based Planning, see the application help page for more information.
• Note, that this is a planning area-specific setting. So you need to decide whether you want to define the freeze horizon for all transportation lanes / production data structures or you want to define it for all location products. It is not possible to use the freeze horizon defined at transportation lane / production data structure and at location product at the same time in a planning area.

https://help.sap.com/docs/SAP_INTEGRATED_BUSINESS_PLANNING/feae3cea3cc549aaa9d9de7d363a83e6/9e620d5639307c65e10000000a44147b.html?locale=en-US

Externally Planned, Unfixed Elements without a Source of Supply

• Planned elements created in IBP always have a source of supply, but planned elements created externally may have not a valid source of supply in IBP, e.g. purchase requisitions can be created in SAP ERP or S/4HANA without a source of supply
• Externally created planned elements are integrated as fixed for planning, but users can unfix these elements
• Such unfixed planned elements without a source of supply are protected by the distribution/production freeze horizon defined at location material
• But they are not protected by the distribution/production freeze horizon defined at transportation lane/production data structure. In this case, a planning run will delete these elements and, if the quantity is required to satisfy demand, recreate the element at a source of supply at a later date outside of the freeze horizon.

• The attribute "Freeze Horizon Policy" at transportation lane and at production data structure allows to define whether the end date or the start date of planned elements is considered for the freeze horizon
• Policy Planned End Date: Existing elements with an end date within the freeze horizon are fixed for planning. New elements are created with their end date after the freeze horizon, but their start date can lie within the freeze horizon.
• Policy Planned Start Date: Existing elements with an start date within the freeze horizon are fixed for planning. New elements are created with their start date after the freeze horizon.
• The freeze horizon policy is not available at location product level. If master data is read from the location product, then the policy is defaulted to Planned End Date.

Effective Planning Calendar and Time Zone for Distribution Freeze Horizon in Working Days

• If you use the option "Working Days" in the Planning Run Profiles app in the General Parameters tab under "Consider for freeze horizon" then the effective planning calendar and time zone in which the working days are considered for the distribution freeze horizon depends on the freeze horizon policy
• The working days for the production freeze horizon are always considered in the production calendar defined at the location product and in the location's time zone, regardless of the freeze horizon policy

• Freeze horizons can now also be considered in weeks or in months. Two new options have therefore been added in the Planning Run Profiles app in the General Parameters tab under „Consider for freeze horizon".
• The new options convert the defined number of days (at location product or at source of supply) to a number of weeks (by dividing it by seven) or a number of months (by always dividing it by 30, regardless of the length of the actual month)
• The first frozen week/month is the one in which the planning start date lies. The second frozen week/month is the following, and so forth.
• Note: If you maintain a horizon that is smaller than seven or 30 days, and you choose to consider the freeze horizon in weeks or months, and the planning start date is close to the end of the week or month, then this can lead to a shorter freeze horizon than if you considered the freeze horizon in calendar days.

You can now run a subcontracting process with operational supply planning.

Value Proposition

• Operative supply plans for subcontracting
• Seamless integration with SAP ERP subcontracting

Capabilities

• Real-time integration with SAP ERP
• Subcontracting with any order-based job: supply heuristic, supply optimizer, key-figure to order, DDR or TLB
• Consider subcontractor limits via transport constraint
• Consider component constraints in network
• Visibility for subcontracting orders with per-order component requirements in IBP
• Core process: components provisioned via purchasing plant

Master data created by RTI

• Subcontracting lane
• PDS at subcontractor
• Location-products at subcontractor
• Component lanes for provisioning from plant

Note: finished good at supplier loc-prod exists but does not show material flow. Demand isplaced directly at component.

• Subcontracting lane is a source or supply
• Application creates subcontracting purchase requisitions including component demands based on this lane and its assigned PDS
• Any job/algorithm: supply heuristic, supply optimizer, DDR, TLB
• Interactive planning: Projected Stock UI and key-figure to order job