SAP IBP for response and supply

Objectives

After completing this lesson, you will be able to:

  • understand the innovations in IBP for response and supply

Withdrawal From Alternative Plants

Overview

In order-based planning, components of production data structures (PDS) can now be withdrawn from different locations than the production location, which means that components in planned orders and integrated production orders can have locations differing from the location of the finished product. The new function provides an alternative to using stock transfer orders for components and is especially useful when plants are close together.

The function is enabled by the component location ID attribute of the PDS component. If it differs from the location ID attribute on the PDS header, planning will create component requirements with locations different from those of the finished product receipt.

Integration (RTI) - SAP ECC, S/4HANA

With real-time integration (RTI), you can integrate components with issuing plants other than the receiving plant of the output material. These components must be defined in SAP ERP Central Component (SAP ECC) or SAP S/4HANA with the special procurement key Withdrawal from alternative plant.

Production and planned orders using a different location on component level than on finished product level can be integrated into SAP IBP, and planned orders including components with alternative plants can be integrated to your SAP ECC or SAP S/4HANA system as well.

Note
To be able to integrate components withdrawn from alternative plants, you need to map the LOCNO_COMP field in the production source of supply BOM in the Real-Time Integration Profiles app.

Configuration (in IBP)

To enable the withdrawal of components from alternative plants, your IBP model must comply with a series of requirements. If you build a planning area from scratch based on a copy of the SAP7F sample planning area in SAP IBP 2311 or later, your planning area is already configured to use the new function: Master data type, planning level + your component location ID is assigned to the new PDS Component Location ID attribute business meaning in the Business Meanings for Order-Based Planning app.

However, if you want to adapt an existing planning area to the use of alternative plants as component locations, we suggest you follow the relevant migration procedure described in Setting Up Withdrawals from Alternative Plants in the SAP help portal.

Configuration - Prerequisites

If you want to adapt an existing planning area, please consider:

  • You use a planning area based on the flexible master data model.
  • The component location ID must be present in your master data model and in the DAYPDSCOMP planning level. If your planning area is based on version 2311 or higher of SAP Integrated Business Planning for Supply Chain (SAP IBP), these prerequisites are met. If your planning area is based on a lower version of the sample, perform the steps described under Setting Up Withdrawals from Alternative Plants in the SAP help portal.
  • In the Real-Time Integration Profiles app, you have upgraded to RTI structure version 2 of the Production Source of Supply BOM RTI structure element. (If you are already using this version, refresh the list of components.)
  • In your business meaning profile, the component location ID attribute has been assigned to the PDS Component location ID business meaning.
  • The component location ID has been filled with the withdrawal plants. New customers as of the 2311 release or higher of SAP Integrated Business Planning for Supply Chain (SAP IBP) can integrate issuing plants of components with the special procurement key Withdrawal from alternative plant using real-time integration (RTI). Customers using an SAP7F-based planning area created before 2311 need to follow the steps described under Setting Up Withdrawals from Alternative Plants in the SAP help portal.

    Setting Up Withdrawals from Alternative Plants

Process

In your planning model, component location IDs differ from location ID of finished product.

The supply planning run creates planned orders for the (semi-)finished product using the location ID assigned to the PDS header. It creates dependent demand for components using component location IDs assigned to the PDS components.

Example:

The following graphic shows such a planned order with the component (COMP) input from another plant than the finished good (FG) output.

Start an outbound integration job. Planned orders including component location information are integrated to SAP ECC or SAP S/4HANA.

You can verify that dependent demands are assigned to alternative plants in transaction Stock/Requirements List (MD04) in SAP ECC or SAP S/4HANA.

Planned orders are turned into production orders in SAP ECC or SAP S/4HANA. Upon order execution, components are physically withdrawn from alternative locations.

Interactive Planning: Simulate Sales Order

Deprecation of Simulate Sales Order App

The Simulate Sales Order app has been deprecated and will be removed in 2402.

If you want to simulate new sales orders, please start using the new Simulate Sales Order function in the Projected Stock or View Confirmations app

  • You can now create and change sales orders and start a planning run, in the main view of the app.
  • You can delete a sales order that has been created in SAP IBP by choosing the Delete icon in the relevant row of the table.
  • You can now create and change sales orders and start a planning run, in the main view of the app.
  • You can delete a sales order that has been created in SAP IBP by choosing the Delete icon in the relevant row of the table.
  • In the Projected Stock app, you can now simulate a new sales order directly in the app by choosing Simulate Sales Order in the Element View and entering the required information.
  • You can also now use the Change button to change a sales order.
  • You can delete a sales order that has been created in SAP IBP by choosing the Delete icon in the relevant row of the table.
  • You can as well change integrated sales orders
  • You cannot delete integrated sales orders.
  • New schedule lines cannot any longer be added to an integrated sales order
  • You can now use the Simulate Sales Order and Change functions to achieve the same results.

Start Planning Run

  • You can start a planning run to see the effects of your changes using the Start Planning Run button in app Projected Stock or app View Confirmations.
  • The planning run is now decoupled from the creation of a sales order.

Start Planning Run

  • You can start a planning run to see the effects of your changes
  • The planning run is now decoupled from the creation of a sales order

Planning Version and scenarios

You can save new or changed sales orders to a planning version or scenario, but not to your base version.

In addition:

Functionality is offered in flexible and static OBP planning areas.

Enhancements to Transportation Load Building

  • The Transportation Load Building component of Planner Workspaces now provides settings for component filters and settings that are specific to TLB.
  • Component filters:
    • Version / Scenario: Select one version or scenario, multi-selection is not possible.
    • Time Periods: Select one interval of time periods.
    • Filter Options: Defines the source of the filters for versions / scenarios and time periods. The source can be the workbook or the component.
    • Outlook: Component specific attribute-based filters will be added in a future release
  • Settings specific to TLB:
    • Filter for Stock Transfer: Defines whether the distribution order table shows at stock transfer lanes only deployment requisitions or all types of requisitions.
    • Unload Operation: Defines the target order type and the fixing status of unloaded items.
    • Outlook: Configuration of table views for load items and for distribution orders will be added in a future release.
  • The settings can be saved to a new content type "Transportation Load View".
  • A new TLB component that has been added to a workbook has initially a standard transportation load view assigned which provides predefined values for all settings. The TLB component can be used and saved with the standard view, it is not mandatory to assign a user-created view.
  • Changes to settings can be applied at any time in design and plan mode, but they cannot be saved to the standard view. Create a transportation load view by using the Save As method in the Additional Options (three dots) menu to save custom-defined settings.
  • Assign a transportation load view that has been created by you or shared with you by selecting the view in the drop-down list Transportation Load View at the tab General of the TLB component's settings. Select < Standard View > to return to the default values of all settings.
  • Transportation load views can be renamed, shared with other users, and deleted in the Manage Workspace Content app and in the Content Administration app.
  • If planner workspace content is transported in a system landscape then similar to other content types transportation load views must be manually added to the export software collection. TLB components which have the standard view assigned are included automatically into the export.
  • The setting "Filter for Stock Transfer" affects planned distribution orders at stock transfer transportation lanes that match the applied filters. It can be set to:
    • All Requisitions (default value)

      The planned distribution order table displays all matching requisitions. Use this value if no deployment planning is performed or if stock transfer requisitions shall also be displayed.

    • Deployment Requisitions

      The planned distribution order table displays only deployment requisitions. Use this value if transportation loads shall only be build for deployment quantities.

  • (Subcontracting) purchase requisitions at procurement transportation lanes that match the applied filters are not affected by this setting and are always displayed.
  • The unload action removes the item(s) from the transportation load and recreates them as new requisitions which will then appear in the planned distribution order table. If the last item is unloaded then the load is deleted.
  • In contrast to the delete action, the unload action keeps the planned distribution quantities. Use the unload action if you want to change the quantity or scheduled dates of the items or if you want to add the items to a new load.
  • The new requisitions are created according to the settings of the unload operation (tab General of the component's settings)
  • "Target for Stock Transfer" can be set to:
    • Deployment Requisitions (default value)

      Load stock transfer requisitions are recreated as deployment requisitions. Use this value if loads are only build for deployment quantities and the deployment status should be kept after unload.

    • Stock Transfer Requisitions

      Load stock transfer requisitions are recreated as stock transfer requisitions. Use this value if a subsequent supply planning run shall be able to replan the unloaded items (deployment requisitions are fixed in supply planning).Note: If you set „Filter for Stock Transfer" to Deployment Requisitions and "Target for Stock Transfer" to Stock Transfer Requisitions then the unloaded items will not appear in the distribution order table, but the stock transfer requisitions will be created and a data simulate or data save will simulate or save them.

  • "Fixing Status" can be set to:
    • Unfixed (default value)

      The created requisitions are unfixed for planning.Use this value if a next supply or deployment planning run shall be able to replan the unloaded items.

    • Fixed

      The created requisitions are fixed for planning.Use this value if a next supply or deployment planning run shall not be able to replan the unloaded items.

  • The planned date of a requisition can be changed by double-clicking into the cell of the column Planned Date in the distribution order table. Type in a new date or use the date picker.
  • The requisition is scheduled backwards from the chosen planned date with respect to planning calendars and durations of the transportation lane.
  • The planned start date of a stock transfer requisition or of a deployment requisition can be changed in the same way, in this case the order is scheduled forwards from the chosen planned start date.
  • If the new goods receipt date does not match to the applied time periods filter then the requisition will not be visible anymore in the distribution order table, but a data simulate or data save will simulate or save the rescheduled requisition.
  • Due to a technical limitation of the order scheduling method, the goods receipt date cannot be changed directly. If a certain goods receipt date is required, e.g. to load the requisition into a selected transportation load, then a suitable planned date or planned start date must be chosen by considering the planning calendars and durations of the transportation lane.
  • The fixing status of a requisition can be changed by clicking into the cell of the column Fix in the distribution order table.
  • A fixed requisition cannot be overwritten by a next planning run. All interactive planning actions set automatically the status to fixed, except for the unload action which applies the setting of the unload operation.
  • Requisitions can be deleted by selecting them and choosing Delete.
  • Like any other interactive change, fixing and deletion of requisitions are simulated or saved by choosing data simulate or data save.
  • The planned distribution order table allows to copy a value to several cells in the same column and by that change multiple requisitions at once
  • Copy a value from one cell to multiple neighboring cells in the column Quantity, Planned Start Date, Planned Date, or Fix by selecting a cell and dragging the small square in the lower right-hand corner up or down to the cells that you want to contain that value
  • Copy a value from one cell by pressing the control button and C on your keyboard and paste it to multiple cells in the same column by pressing the control button and V. This method is only available for the columns Quantity and Fix.

Support of extensible Master Data Attributes in View Confirmations

  • If you work with a planning area based on flexible master data, you can now use extension master data attributes for order-based planning in the View Confirmations App.
  • Once you have added the extension attributes (like the depicted example of Customer City) and activated your master data, you can start using the new attributes as filter or columns in the app.
  • The fields are initially hidden in the filter and columns section and need to be added via configuration if required

Other improvements in View Confirmations

  • We have introduced the "Completed" confirmation status. If you selected this confirmation status as your filter, only sales orders are displayed that no longer have open quantities.
  • Schedule Lines of orders are now visualized in the side panel.
  • When navigating from the main screen to the detail screen, per default the Order Network is visualized first. In case you are interested in the Competing Sales Orders information you need to navigate to this detail via the respective tab.
  • In the Competing Sales Orders tab, the Schedule Lines and the Product Allocations are now available in the side panel under respective tabs.
  • In the main view of the View Confirmations app, you can now simulate new sales order or make changes to existing orders.
  • For newly created sales orders and current planning scope a planning run can be started.
Note
The Simulate Sales Order feature can still be started from the Competing Sales Orders detail view. However this feature will be deprecated soon and we strongly recommend to use the new functionality that is offered on the main screen of the View Confirmations App.

Planning Purchasing Receipts in PPDS

Abbreviations used in this document

  • BAdI Business Add In
  • CI-DS SAP Cloud Integration for Data Service
  • CIF Core Interface. Real-time interface used for integration between SAP S/4H ERP / SAP ECC and SAP S/4H PP/DS
  • DEF Default (Mode of Transport / Means of Transport)
  • DSCe Digital Supply Chain Edition, side-by-side SAP S/4HANA instance for advanced planning
  • DPS Detailed Planning and Scheduling (as a process)
  • ERP Enterprise Resource Planning / Backend system for supply chain planning systems / ERP capabilities reside on SAP S/4H or SAP ECC
  • IBP Integrated Business Planning (as an application)
  • GI / GR Goods Issue / Goods Receipt
  • MM Materials Management (component in SAP ECC / SAP S/4HANA)
  • MPS Master Production Scheduling
  • MP&S Manufacturing Planning and Scheduling (a.k.a. embedded PP/DS on S/4HANA)
  • MoT / MTr Mode of Transport (term used in IBP)/ Means of Transport (term used in PP/DS), synonymous in this solution
  • OSP Operational Supply Planning (as a process)
  • OBP Order-based Planning (component in IBP a.k.a. IBP Response)
  • PP/DS Production Planning and Detailed Scheduling (component in SAP S/4HANA, a.k.a. M&PS)
  • PP Production Planning (depending on context component in SAP ECC / SAP S/4HANA including the process of manufacturing execution or component and process in PP/DS that covers demand by generating planned supply elements)
  • RCCP Rough Cut Capacity Planning
  • PIR Purchasing Infor Record
  • PPIM Production Planning Integration Mode
  • RTI Real-time Integration (effectively meaning Order-Based Planning with Flexible Master Data). Real-time interface used for integration between SAP S/4H ERP / SAP ECC and SAP IBP OBP.
  • SD Sales and Distribution (component in SAP ECC / SAP S/4HANA)
  • S&OP Sales and Operations Planning (as a process)
  • SoS Source of Supply
  • STR / STO Stock Transfer Requisition / Stock Transfer Order
  • SYPP Synchronized Production Planning (a.k.a. Production Planning Integration of IBP)
  • TLB Transport Load Building
  • TLANE Transportation Lane

Bottom-Up Integration

An integration flow for a business document that starts in the hierarchically lower level detailed planning system PP/DS and ends in the hierarchically higher-level network planning system OBP. The message flow between both planning systems goes via an in-between ERP backend system SAP S/4H or SAP ECC

Concurrent Planning

A planning set up where two planning systems at two different levels of planning hierarchy plan the same location product in parallel while using techniques such as horizons or integration modes to avoid unintentional mutual overwrites of planning results

Distribution

In OBP used as a synonym for procurement from other locations in all kinds, such as stock transfers between plants of same company code or procurement from external vendors.

Execution order

Document that has been converted to an execution state after planning such as production order, purchase order, or stock transport order

Middle-Out Integration

An integration flow for a business document that starts in an in-between ERP backend system SAP S/4H or SAP ECC and ends in parallel in two planning systems: The hierarchically high-level network planning system OBP and the hierarchically lower level detailed planning system PP/DS.

Planned Purchasing Receipt

Requisition in procurement from other locations such as purchase requisition, stock transfer requisition, or subcontracting purchase requisition. These purchasing documents are in planning stage like planned orders in inhouse production.

Top-Down Integration

An integration flow for a business document that starts in the hierarchically high-level network planning system OBP and ends in the hierarchically lower level detailed planning system PP/DS. The message flow between both planning systems goes via an in-between ERP backend system SAP S/4H or SAP ECC.

Overview and Motivation

Order-based process integration with PP/DS is differentiated by Production Planning Integration Modes (PPIM)With IBP 2311 PPIM 3 offers the option whether to plan purchasing receipts in PP/DS or not.

* Deployment and TLB can only be used properly if their planning outcome in only displayed in PP/DS. Using Deployment and TLB for location products in PPIM 3 with the short-term planning option regarding purchasing receipts in PP/DS is not supported.

Order integration is now enabled for planning of purchasing receipts in short-term PPDS

  • Stock transfers and purchase requisitions only planned in OBP.
  • No delegation to PP/DS, displayed only as eXternal orders in PPDS.
  • Source of supply is at the source location level: Mode of Trans-port in OBP does not match with Means of Transport in PP/DS.
  • Handling and Transport resources not assigned to receipts.
  • Stock transfers and purchase requisitions also planned in PPDS
  • Horizon based concurrent planning of purchasing receipts:
  • No distinction of planning stage OBP vs. PP/DS, same order type for planned purchasing receipts planned in OBP and planned in PP/DS
  • No handover step from OBP to PP/DS as opposed to planned orders
  • Consistent detailed level source of supply: Mode of Transport in OBP matches with Means of Transport in PP/DS from planning to execution
  • Handling and Transport Resources can be assigned to receipts

Inhouse Supplies (Comparison as sound track)

  • Differentiated types of planed orders: Generated by order-based planning (rough-cut) vs. PPDS (detailed)
  • Handover process: Convert order-based planned orders into PPDS planned orders in the short term
  • Bi-directional integration with same production version ID
  • Flexible delegation concept
    • Displayed in PPDS only
    • Scheduled in PPDS only
    • Planned in PP/DS within a specified horizon (DPS horizon)

New planning capabilities for purchasing receipts widen the order-integration framework

Motivation

Production Planning Integration Modes allow a differentiated division of labor between OBP as a network planning system and PP/DS as a more detailed production planning system. Thus, OBP integrates the entire supply chain independent of detailed planning concepts in different parts of the horizontal supply chain.

Flexible

In in-house production, the delegation options range between display only, schedule only, and short-term planning in PP/DS. The integration mode for short-term planning in PP/DS now allows the choice between display only and short-term planning for stock transfer requisitions and purchase requisitions.

Further Outlook

We plan two-stage planning capabilities for purchasing receipts, so OBP planned requisitions can be distinguished from PP/DS planned requisitions. New modes of integration are part of product direction.

*Only available for Flexible Planning areas and Real-Time Integration. This is the current state of planning and may be changed by SAP at any time.

Process

Reference Process by production planning integration mode: PPIM 3 - Short-term production planning and detailed scheduling delegated without advanced planning scope limitations.

Simplified modeling example for the new option to plan purchasing in PP/DS.

This example is based on a simple multi-level production and distribution use case with a meaningful Production Planning Integration Mode (PPIM) assignment of location materials.

A finished good PHONE is sold via Distribution Center DC71. The distribution chain is exclusively planned in the OBP Operational Supply Planning business process. At the same time, stock transfer requisition requirements for Production Plant FA71 need to be integrated into PP/DS. Therefore, PHONE in DC71 has PPIM Displayed in DPS (9).

The DC is replenished through a two-level in-house production of PHONE in production plant FA71. The finished good PHONE and the component BULKPHONE shall be planned in OBP as well as PP/DS within the PP/DS horizon. Therefore, these products have PPIM Short-term production planning and detailed scheduling delegated (3).

The PHONE in FA71 can also be sourced from another factory depending on capacity shortages, priorities, or quota. PP/DS shall refine short-term transfers between FA72 and FA71. So, the scope restriction for advanced planning is blank (new option *) for PHONE in FA71.

The externally purchased item CPU is needed as component for BULKPHONE. Like the finished goods in FA71 it is planned in both IBP OBP and PP/DS. Therefore, it has PPIM (3) with unrestricted scope in PP/DS too ( * ). Thus, purchasing becomes more agile.

The overflow factory FA72 has a less complex production environment and can rely on rough-cut production planning w/o using PP/DS for short-term refinement. All PPIMs are Displayed in DPS (9). Safety stock buffers until the next OBP run exist for unexpected short-term STR requirements from FA71 planned by PP/DS.

Date/Time consistency across systems matters in order-based process integration. Activity Models with Dates and Times in OBP, PP/DS, and ERP for Stock Transfers*

*This illustration provides an overview for the use case of stock transfers which is more complex compared to one-sided external purchasing without Transportation and GI activities.

** The GI Activity is not modeled in OBP. Therefore GI Processing Time in all systems shall be maintained as zero.

*** In OBP: only calculated for consumption at start and saved as (Resource) Consumption Date.

WADAT = input element TST02

Process Integration when using PPIM 3 w/o scope limitations in PP/DS Process Steps

Process Integration when using PPIM 3 w/o scope limitations in PP/DS Process Steps

Process Integration when using PPIM 3 w/o scope limitations in PP/DS

* Except for the use case of ERP shipment and transportation scheduling of stock transport orders. In this case the no-rescheduling flag has to be checked as a client level setting in the customizing of stock transport orders for both OBP and PP/DS integration respectively

Process Integration when using PPIM 3 w/o scope limitations in PP/DS

Process Integration when using PPIM 3 w/o scope limitations in PP/DS

* Except for the use case of ERP shipment and transportation scheduling of stock transport orders. In this case the no-rescheduling flag has to be checked as a client level setting in the customizing of stock transport orders for both OBP and PP/DS integration respectively

Process Integration when using PPIM 3 w/o scope limitations in PP/DS

Summary of new process capabilities with restrictions and prerequisites for purchasing receipts.

Use the overall scenario with the following considerations:

Restrictions/Prerequisites:

  • With PPIM 3, there is no two-stage concept for planned purchasing receipts as opposed to planned orders:
    • No formal distinction is made between the Operational Supply Planning Stage vs. Detailed Planning and Scheduling Stage
    • OBP, ERP, or PP/DS cannot distinguish the planning system that owns the planned purchasing receipt, so mutual overwrites are possible between OBP and PP/DS. The following measures are necessary for automated planning runs:
      • On OBP side: Activate the DPS Horizon for Distribution for the location products in question in the OBP planning run profile
      • On PPDS side: Control the replanning of planned distribution receipts with BAdI enhancements described in Note 3291712.
    • There is no handover process for planned purchasing receipts in PPIM 3
    • As opposed to planned orders, planned purchasing receipts created in OBP are subject to resource scheduling. Planned purchasing receipts created in OBP are assigned to PP/DS resources (i.e. inbound handling resources and transportation resources applicable to the PP/DS transportation lane and may consume capacity.
  • Planned Purchasing Receipts outside the PP/DS Horizon cannot be protected against PP/DS runs out of the box. For this feature a mandadory BAdI extension is required and a sample BAdI is delivered.
  • Planned Purchasing Receipts within the PP/DS Horizon cannot be protected such that the PP/DS runs adhere to the overall OBP planned volumes and sources of supply while creating replacement orders with PP/DS specific lot sizes. For this optional feature (prebuild or master production planning scenario) a BAdI extension is required and a sample BAdI is delivered.
  • Deployment STRs and TLB orders from Order-based planning cannot be distinguished in PP/DS by ATP category. Hence, they cannot be protected against PP/DS runs. The use of Deployment and TLB for location materials without scope limitation for purchasing receipts in PP/DS is not supported.

Process Integration when using PPIM 3 w/o scope limitations in PP/DS

Summary of new process capabilities with restrictions and prerequisites for purchasing receipts.

Availability Dates/Times at the ship-to location are integrated consistently with the following considerations:

  • Availability date is not part of the ERP model. ERP persists the GR Processing Time (WEBAZ) instead.
  • Availability Date is integrated between OBP and PP/DS by converting it into the GR Process Time equivalent when passing scheduling results from OBP to PP/DS (top-down integration) or from PP/DS to OBP (bottom-up integration) via ERP.
  • If shipment and transportation scheduling of stock transport orders is customized in ERP, the Availability Date might be integrated without scheduling in OBP and PP/DS. In this case, a no-rescheduling flag is checked as a client level setting in the customizing of stock transport orders for both OBP and PP/DS integration.
  • Also, GR Processing Time is received by both planning systems, when the order is last schedule in ERP (Middle-Out integration).*
  • GR Processing Time equivalent is re-transformed into an exact Availability Date and Time in the receiving planning system.

Restrictions/Prerequisites:

  • Use inbound / receiving calendars in all planning systems as well as for inbound handling resources in PP/DS such they are consistent with the ERP factory calendar regarding non-working days. This means: No product or transportation lane specific inbound calendars
  • Use 00:00:00-24:00:00 time streams in PPDS for above calendars as OBP has a daily granularity for scheduled durations. In case of resource scheduling in PP/DS use handling resources without breaks or shifts for the same reason.
  • As ERP perceives inbound GR processing times of zero as initial and replaces them by GR Processing times from local master data, the GR Processing Time as per material master in ERP (as well as in the advanced planning tab of the material master) must be zero if any OBP or PP/DS transportation lane has a GR Processing time equal to zero.
  • Availability Date inconsistencies may occur for GR activities that end on the last second before a receiving calendar gap: Goods Receipt activities completed on the last working day before a receiving calendar gap are available at 00:00:00 of the first non-working day in PP/DS while they appear as available at 00:00:00 hrs on the first working day after the calendar gap in OBP and ERP.

    Example: If a transport ends with a planned delivery time at night from Thursday to Friday at 00:00:00, the GR processing time is 1 day, and Saturday as well as Sunday are a non-working days, the calculated availability in PP/DS is Saturday 00:00:00 whereas it is Monday 00:00:00 in OBP and ERP.

    Further restrictions and prerequisites for a consistent master set up may apply. Refer to SAP notes 3372270 and 3372280.

Process Integration when using PPIM 3 w/o scope limitations in PP/DS

Summary of new process capabilities and restrictions for purchasing receipts.

Alternative purchasing sources of supply are integrated at the detailed level mode of transport in both directions between OBP and PP/DS by mapping Modes of Transport IDs in OBP with Means of Transport ID in PP/DS.

Restrictions/Prerequisites:

  • Model transportation master data consistently in OBP and PP/DS
    • Every Means of Transport ID of every Transportation Lane in PP/DS (as a combination of ship-from location, ship-to location and product) has to have a corresponding Mode of Transport ID of a Transportation Lane in OBP (as a combination of ship-from location, ship-to location, product, mode of transport, and ADDLANE ID) and vice versa.
    • The resulting pairs of transportation lanes must have consistent master data attributes, in particular with respect to durations and calendars
    • Process step Conversion of Stock Transfer Requisitions to Stock Transfer Orders: When converting STRs, the Planned Delivery Time of the STO may be filled from ERP master data rather than from the referenced STR, if a Purchasing Info Record or a Special Procurement Key is maintained on the ERP side. This might lead to a mismatch of the scheduled Requirement Date of the STO in the Ship-From Location when comparing the ERP system on one side with the planning systems OBP or PP/DS on the other. A mismatch would usually occur in case of multiple MoT as the lead time as per TLANE in OBP or PP/DS would deviate from the common Purchasing Info Record or Material Master in ERP. However, this would neither affect multi-level planning consistency in OBP or PP/DS nor consistency between these planning systems.
  • In middle-out integration the Mode/Means of Transport is defaulted in both target systems unless a valid mode of transport can be referenced from prior planning.
    • As ERP has no concept of transportation options that corresponds to OBP or PP/DS, in middle-out integration without a reference to OBP or PP/DS, planned purchasing receipts are defaulted with the Mode/Means of Transport ID DEF.
    • This requires the set-up of a fallback Mode/Means of Transport DEF in both target planning systems.
    • If the defaulting is not desired in case of middle-out integration without reference to prior planning in OBP or PP/DS, BAdI, extensions for respective RTI and CIF integration may be considered in custom implementation projects without sample coding delivered by SAP.

Further restrictions and prerequisites for a consistent master set up may apply. Refer to SAP notes 3372270 and 3372280.

Process Integration when using PPIM 3 w/o scope limitations in PP/DS

Summary of new process capabilities and restrictions for stock transfers

Requirement Dates/Times at the ship-from location are integrated consistently with the following considerations:

  • The requirement date is not part of the ERP model and ERP persists Planned Delivery Time (PLIFZ) instead.
  • The Requirement Date is integrated between OBP and PP/DS by recalculating it independently in the receiving target planning system in both ways of integration based on the received Planned Delivery Time (Transport End Date/Time) as an anchor point as well as the local transportation master data while using a consistently integrated Mode/Means of Transport .
  • Accordingly, when integration originates from ERP (Middle-Out integration) the planned delivery time in ERP as a duration is ignored in both target planning systems
  • When OBP or PP/DS planned purchasing receipts are converted the MoT/MTr as well as the Planned Delivery Time are both inherited to the execution order so the transportation scheduling remains unchanged compared to the preceeding stock transfer requisition.

Restrictions/Prerequisites:

  • As planned delivery time is ignored in middle-out integration and the mode of transport is defaulted to DEF in use cases where documents are created or changed in a way deviant from prior planning in OBP or PP/DS, maintain planned delivery time in the material master consistently with the DEF transportation lanes in OBP and PP/DS.
  • Use consistent transportation calendars as well as consistent shipping calendars on the OBP and the PP/DS side.
    • In case of resource scheduling the calendar of the PP/DS transportation resource has to be consistent with the transportation calendar at the OBP Transportation Lane.
    • The shipping calendar in PP/DS is assigned at location level. In OBP, use the same shipping calendar for all products and TLANES with same ship-from location.
  • Use 00:00:00-24:00:00 time streams in PPDS for above calendars and transportation resources without breaks or shifts as order-based planning has a integer daily granularity for scheduled durations.
  • Keep transport durations per Means of Transport in PP/DS in sync with lead times in OBP transportation lanes.
  • Maintain transport durations in PP/DS such days correspond to integer days for lead times in OBP, such as 24:00 or 72:00 hours.
  • Maintain GI Processing Time in ERP and PP/DS as zero because the GI activity is not modeled in OBP.

Further restrictions and prerequisites for a consistent master set up may apply. Refer to SAP notes 3372270 and 3372280.

Configuration and Prerequisites

Configuration and Prerequisites for short-term planning of purchasing receipts in PP/DS (Overview)

In order to plan purchasing receipts in OBP and PP/DS concurrently with PPIM 3 location products the following configuration settings and prerequisites have to be considered:

  1. IBP OBP and S/4H PPDS: Maintain additional location product master data for Production Planning Integration. Maintain PPIM and DPS Horizon for location product and distribute master data to OBP.
  2. S/4H PP/DS: Advanced Planning Flag (PP/DS): Leave scope restriction value in S/4H material master blank.
  3. IBP OBP: Planning Run Profiles: Activate DPS Horizon switch not only for Production but also for Distribution
  4. S/4H PP/DS: SAP Notes for sample BAdI enhancements to protect OBP plans in PP/DS.
    • Protect OBP Plan outside PP/DS Horizon (Mandatory).
    • Adhere to the overall OBP planned quantities even within PP/DS Horizon (Optional).
    • See SAP note: 3291712 - Preserve the Overall Order-Based Planning Outcome with Production Planning Integration Mode 3
  5. IBP OBP and S/4H PPDS: Keep master data in sync between OBP, PP/DS, and ERP.
    • Modes of Transport (OBP) and Means of Transport (PP/DS)
    • Calendars
    • Durations in scheduling (GI Processing Time, Transport or Lead Times, and GR Processing Time)

Maintain additional location product master data for Production Planning Integration with OBP

  • Planning of Purchasing Receipts in OBP and PP/DS concurrently is only supported for:
    • Production Planning Integration Mode Detailed Production Planning and Scheduling Delegated (3).
    • Planning with Flexible Planning Areas in OBP / Real-Time Integration.
  • The Detailed Planning and Scheduling Horizon has to be maintained in order to protect short-term purchasing receipts planned by PP/DS from overwrites in OBP mid-to-long-term planning.
  • Order-integration for Synchronized Planning for Production requires that the location product attributes.
    • Production Planning Integration Mode.
    • Detailed Planning and Scheduling Horizon are maintained consistently across OBP, ERP backend and PP/DS.
  • Use transaction SYPP_MARC_EXT_MAINT* in order to keep PPIM and DPS Horizon consistent across systems.
    • In a 2-system landscape where PPDS is used in the SAP S/4HANA ERP system there is a Send to IBP option to update IBP centrally from S/4HANA.
    • In a 3-system landscape where PPDS is used on a separate S/4H instance (DSC edition) the SYPP_MARC_EXT_MAINT procedure has to be performed redundantly in the DSCe instance. The "Save and Send to IBP" button has to be used in SAP ERP to update IBP centrally.

*Define Material Attributes for Production Planning Integration, see SAP Note 3250473 for details

Maintain additional location product master data for Production Planning Integration with OBP

With IBP release 2311 the PP/DS Scope Limitation value "Blank" is supported for PPIM 3.

Leave scope limitation empty for short-term planning of purchasing receipts in PP/DS.

  • As part of the Flexible Integration feature of PP/DS, all PPIMs have corresponding scope limitation values in the advanced planning integration settings in S/4H. That's how PPIM ownership regarding read and write options is enforced in S/4H PP/DS per location product.
  • Before IBP release 2311 all PPIMs including PPIM 3 were only supported in combination with scope limitation values that disable the planning of purchasing receipts in PP/DS.
  • Since OBP release 2311, the scope limitation value "blank" is supported in combination with PPIM 3.
  • Leave the scope limitation field blank: (i.e. unrestricted) for PPIM 3 products if you want to plan purchasing receipts in PP/DS
  • Limitation: Don't use this option if Deployment or TLB are used in OBP
  • Deployment or TLB requisitions do not have specific ATP categories that can be distinguished or protected in PP/DS

For more information about the Flexible Integration feature in PP/DS on SAP S/4HANA refer to Online Help

Maintain OBP Planning Run Profile to protect PP/DS plan in OBP

  • The DPS Horizon is a freeze horizon for OBP planning runs; it can be activated or deactivated as a switchable constraint.
  • The DPS Horizon enables extending freeze periods beyond the mere distribution and production freeze horizons.
  • While the production and distribution freeze horizons may represent an absolute minimum planning time fence to protect the execution range for purchase orders and production orders respectively, the DPS Horizon can be used to protect the PP/DS planning results within the greater PP/DS Horizon from overwrites on the OBP side.
  • In PPIM 3 the planned orders in the Production Planning Stage Detailed Planning and Scheduling (DPS) cannot be deleted by OBP runs. The active use of the DPS Horizon switch for in-house production is only needed to prevent OBP from creating OBP planned orders on top of what PP/DS has planned.
  • In the case of planned purchasing receipts, however, there is no explicit PP Stage DPS with PPIM 3.Therefore, the active use of the DPS Horizon switch for distribution is needed for both reasons of protection in regular (e.g. daily) OBP runs:
    • prevent OBP from creating OBP requisitions on top of what PP/DS has planned within the PP/DS Horizon.
    • prevent OBP from deleting requisitions that PP/DS has planned within the PP/DS Horizon.
  • If you plan purchasing receipts in PP/DS, use the "Detailed Planning and Scheduling Horizon (Distribution)":
    • Set the DPS Horizon as active object based for the DPS Horizon (Distribution) switch.
    • As a selection criterion for object based activation use PPIM 3.
    • In addition, and as a safety net for a wrong set-up of the DPS Horizon for the location products in question, you may also consider to set the Distribution Freeze Horizon value as equal to the DPS Horizon rather than the bare minimum for the execution planning time fence.

For details on the DPS Horizon switch for distribution refer to this prior What's new document

BAdI Enhancements have to be implemented to protect OBP planned purchasing receipts in PP/DS

In concurrent planning of purchasing receipts in PP/DS using PPIM 3 w/o a scope limitation in PP/DS no formal distinction is made between planned purchasing receipts owned by OBP vs. PP/DS:

  • For planned purchasing receipts there is only a single stage as opposed to planned orders where a distinction is made between planned orders in stage Operational Supply Planning (OSP) and Detailed Planning and Scheduling (DPS)
  • There is no handover process step.
  • PP/DS runs would directly overwrite OBP planned purchasing receipts.

Hence, OBP plans have to be protected in PP/DS using the PP/DS and DPS Horizons as a marker of application ownership.

  1. In order to prevent the deletion of OBP planned purchasing receipts beyond the PP/DS Horizon a mandatory BAdI implementation is needed.
  2. In order to protect the overall OBP planned volume of purchasing receipts from optimized mid-term network planning within the PP/DS Horizon an optional sample BAdI implementation is available.
  3. Sample BAdI Code is available for both use cases with this SAP Note: 3291712 - Preserve the Overall Order-Based Planning Outcome with Production Planning Integration Mode 3

Mandatory BAdI Implementation planned purchasing receipts outside the DPS Horizon

Prevent deletion of OBP plans outside the PP/DS Horizon

In a usual PP Run of PP/DS planned receipts outside the DPS horizon are deleted:

  • If there is no reuse and the flag "Consider demand outside the PP/DS Horizon" is not set, deletion happens without replacing the OBP planned receipts
  • If the flag "Consider demand outside the PP/DS Horizon" is set for the PP run, a single supply element for demand during the entire time span outside the PP/DS horizon is created within the PP/DS Horizon at the edge of the PP/DS horizon

Both cases are not desired for concurrent planning of planned purchasing receipt in PPIM 3. Therefore:

  • A mandatory BAdI has to be implemented that preserves all unfixed planned purchasing receipts outside the PP/DS horizon irrespective of the demand situation.
    • PP Heuristics must be used with the BAdI implementation
    • See SAP Note 3291712 - Preserve the Overall Order-Based Planning Outcome with Production Planning Integration Mode 3
  • The "Consider demand outside the PP/DS Horizon" flag must not be set in the heuristic profile.

It is advisable to maintain a specific "Planning Group" for PPIM 3 location products with concurrent planning of purchasing receipts in PP/DS as a selection criterion for filters in the BAdI Implementation.

Optional BAdI Implementation for planning within the DPS Horizon

Handling of Prebuild for PPIM 3

There is a sample BAdI implementation for PP/DS PP Heuristics that enforces adherence to OBP plans even within the PP/DS horizon.

See SAP Note 3291712 - Preserve the Overall Order-Based Planning Outcome with Production Planning Integration Mode 3

With this extension it is possible to include a subset of location products in Production Planning Integration Mode 3 - (Short-term production planning and detailed scheduling delegated) into PP/DS planning runs while decoupling them from gross or net demand to refine the previous supply situation only.

The enhanced PP heuristic will stick to the supply situation that existed before the run. It will only replace due external planned orders and unfixed planned orders by new planned orders which comply with the specified PP/DS lot size restrictions. Thus an OBP optimized planning situation can be preserved for a subset of PPIM 3 location products with respect to overall production or purchasing volume and the respective sources of supply despite entering the PP/DS horizon while using infinite PP heuristics such as the standard lot size heuristic.

If the procurement type is F or X the enhanced PP heuristic also preserves the quantities and sources of supply of existing unfixed planned purchasing receipts when replacing them to adapt the existing plan for PP/DS lot sizing.

As the optional BAdI protects all unfixed planned purchasing requisitions beyond the PP/DS horizon the mandatory BAdI sample is not required if the optional BAdI sample is implemented.

Keep Master Data for Transportation Planning in sync between OBP and PP/DS

OBP Side master data at location product level

Master Data Type

Location products in PPIM 3 without scope limitation in PP/DS shall be maintained as follows:

  • OBP Inbound (Receiving) Calendar ID shall be same as OBP Production Calendar ID which again shall be same as the ERP Factory Calendar according to transaction OX10.
  • Goods Receipt Processing Time shall be same as material master data for ERP and PP/DS

The above settings:

  • are relevant, if the order-based setting Source of Supply Master Data / Use Master Data Defined for Transportation Lane in the Settings for Order-Based Planning App is equal to no.
  • ensure the consistency of the Availability date and time across OBP, ERP, and PP/DS as they ensure a consistent handling of the Goods Receipt Processing Time.
  • The resulting product limitations are as follows:No location product specific Inbound (Receiving) Calendars

  • Location products in PPIM 3 without scope limitation in PP/DS shall be maintained as follows:

    OBP Shipping Calendar shall be same as PP/DS Shipping Calendar at Ship-From Location

    The above setting is relevant, if the order-based setting "Source of Supply Master Data / Use Master Data Defined for Transportation Lane" in the "Settings for Order-Based Planning" App is equal to "no".

    Ensure the consistency of the Requirement Date/Time at the ship-from location across OBP, ERP, and PP/DS.

    As the GI Processing Activity is not modeled in OBP, the transport start has not only to comply with working days on the transportation calendar but also with working days on the shipping calendar in addition.

    The resulting product limitations are as follows:

    For the same ship-from location no shipping calendars specific to location products can be used.

Further restrictions and prerequisites for a consistent master set up may apply. Refer to SAP notes 3372270 and 3372280.

OBP Side Master Data at Transportation Lane Level

Master Data Type Transportation Lane (TLANE)

The scheduling and source of supply consistency of purchasing documents between OBP and PP/DS depends on a 1:1 relationship and consistency of sources of supply.

Therefore the following rules apply:

  • All OBP and PPDS Transportation Lanes must have at least 1 Mode/Means of Transport named DEF.
  • Only combinations of LocFrom x LocTo x Product x MoT ID / Means Of Transport ID that exist in PP/DS can be maintained in OBP
  • All combinations of LocFrom x LocTo x Product x MoT ID / Means Of Transport ID that exist in PP/DS must be maintained in OBP
  • Multiple VALIDITY FROM/TO intervals per LocFrom x LocTo x Product shall be represented via distinct MoT / MTr entries
  • No more than one ADDLANE ID per combination of LocFrom x LocTo x Product x MoT ID / Means Of Transport

If any of these above rules is violated, during determination of TLANEs at RTI Inbound integration, standard fallback logic applied to inbound documents in order to find closest SoS / TLANE in OBP.

Transportation scheduling (in particular with respect to the Requirement Date/Time at ship-from location) and transport capacity usage might be inconsistent among systems in this case.

Regarding Goods Receipt Scheduling all Transportation Lanes for location products in PPIM 3 without scope limitation in PP/DS shall be maintained as follows:

  • OBP Inbound (Receiving) Calendar ID shall be same as OBP Production Calendar ID which again shall be same as the ERP Factory Calendar according to transaction OX10.
  • Goods Receipt Processing Time shall be same as the GR processing time specified for the combination of product, ship-to-location, and ship-from location in the PP/DS transportation lane
  • If no GR Processing Time is specified for the PP/DS Transportation Lane the material master setting applies. In this case maintain GR Processing Time same as master data type location product for all TLANES.
  • If the Goods Receipt Processing Time for any OBP Transportation Lane is equal to 0, then the GR processing time specified for the material master in ERP has to be 0 as well

The above settings

  • are relevant, if the order-based setting "Source of Supply Master Data / Use Master Data Defined for Transportation Lane" in the "Settings for Order-Based Planning" App is equal to "yes".
  • ensure the consistency of the Availability date and time across OBP, ERP, and PP/DS as they ensure a consistent handling of the Goods Receipt Processing Time as a duration.

The resulting product limitations are as follows:

  • No location product specific or transportation lane specific Inbound Calendars
  • No transportation lane specific goods receipt processing times for different modes of Mode of Transport.

Regarding Transportation Scheduling of stock transfers Transportation Lanes for location products in PPIM 3 without scope limitation in PP/DS shall be maintained as follows:

  • For each Means of Transport ID in the PP/DS Transportation Lane per product, ship-to, and ship-from location:
  • There shall be a corresponding OBP transportation lane with an identical Mode of Transport ID
  • The Lead Time (transportation time) in the OBP transportation lane shall be equal to the Transport Duration in PP/DS.

    If the Transport Duration is not maintained for the MTr in the PP/DS Transportation Lane, the transport duration is taken from the material master. In this case the lead time on the OBP Transportation Lane must be the Planned Delivery Time in material master.

  • The Transportation Calendar in OBP shall be consistent with the PP/DS transportation calendar and -if applicable- with the calendar of the transport resource in PP/DS
  • The Shipping Calendars of all OBP transportation lanes for the same ship-from location shall be consistent with the Shipping Calendar of the PP/DS location
  • As the GI Processing Activity is not modeled in OBP, the transport start has not only to comply with working days on the transportation calendar but also with working days on the Shipping Calendar in addition.

The above settings are

  • relevant for the consistency of the Requirement Date/Time in the ship from location across OBP, ERP, and PP/DS
  • relevant for the consistency of the (Transportation) Resource consumption date at start in OBP

The resulting product limitations are as follows:

  • Need to keep Sources of Supply 1:1 and consistent between OBP and PP/DS
  • For the same ship-from location no shipping calendars specific to transportation lanes can be used.

Further restrictions and prerequisites for a consistent master set up may apply. Refer to SAP notes 3372270 and 3372280.

PP/DS side master data at location level

Calendars and Handling Resources assigned in Transaction /SAPAPO/LOC3

Locations for products in PPIM 3 without scope limitation in PP/DS shall be maintained as follows:

  • All transportation relevant calendars shall be maintained with full day time streams that span from 00:00:00 to 24:00:00 for the respective working day
  • This applies to Shipping Calendars, Receiving Calendars, and resource calendars for Inbound Handling Resources and is due to the fact that OBP transportation scheduling happens multiples of in integer days
  • Consistency of the Availability date and time across OBP, ERP, and PP/DS and consistent handling of the Goods Receipt Processing Time
    • Non-working days of Receiving Calendars as well as calendars for Inbound Handling Resources shall have same gaps as the Factory Calendar in ERP.
    • If these calendars are not maintained (initial), the factory calendar is used as a fallback.
    • Inbound Handling Resources used in resource scheduling must not have breaks or shifts.
  • Consistency of the Transportation Scheduling across OBP and PP/DS:
    • The PP/DS Shipping Calendar per ship-from location shall be used for all products and TLANES at the same location on the OBP side.
    • The PP/DS Transportation Calendar per combination of Means of Transport / Ship-From Location / Ship-To Location / Product shall be used for all TLANES at the same combination on the OBP side.

The resulting product limitations for PP/DS usage are as follows:

Only full-day time streams and inbound handling resources with 60x60x24 seconds for each working day.

PP/DS and ERP side master data at location product level Transaction MM02

Locations for products in PPIM 3 without scope limitation in PP/DS shall be maintained as follows:

Advanced Planning Tab

Mandatory settings:

  • Goods Issue and Goods Receipt times must be consistent across the MRP2 and the Advanced Planning Tabs
  • Goods Issue Time must be zero across the MRP2 and the Advanced Planning Tabs as GI Time is not modelled in OBP

Recommendations:

  • PP/DS Horizon (S/4H > release 2021):
    • Do not maintain the PP/DS Horizon, so it is defaulted by the DPS Horizon for PPIM 3
    • If you maintain the PPDS Horizon per location product then maintain it in sync with the DPS horizon
  • Consider to assign a specific planning group to control selections for BAdI enhancements protecting planned purchasing receipts in PP/DS when using PP Heuristics
  • Consider to assign enhanced PP Heuristics as Product Heuristic

MRP2 Tab:

  • Location Products in PPIM 3 without scope limitation in PP/DS only make sense for Procurement Type X or F
  • The Planned Delivery Time shall be equal to the OBP Lead Time of the DEF Transportation Lane
  • The Scheduling Margin Key shall have a release period of zero days (recommendation)

PP/DS side master data at transportation lane level

Transaction /SAPAPO/SCC_TL1

PP/DS Transportation Lanes for products in PPIM 3 without scope limitation in PP/DS shall be maintained as follow:

Product-LocFrom-LocTo Specific Transportation Lane settings

  • A GR Processing Time (specific to the PPDS transportation lane) can only be maintained if the order-based setting "Source of Supply Master Data / Use Master Data Defined for Transportation Lane" in the "Settings for Order-Based Planning" App is set to "yes".
  • If a GR Processing Time is maintained, all transportation lanes with the same product, location-from, and location-to in OBP must have the same GR Processing Time
  • If order based setting for transportation is "yes" and no GR Processing Time is maintained, all transportation lanes with the same product and location-to in OBP must have the same GR Processing Time as the material master
  • If a GR Processing Time is maintained as zero days, the Goods Receipt Processing Time in the Material Master has to be zero as well.

Means of Transportation (MTr) specific Transportation Lane settings:

  • For each MoT in OBP there must be a MTr with the same ID, same Transportation Calendar and the same Transport Duration
  • There must be at least one MTr with the key value DEF (Default). This is needed for stock transfer requisitions or stock transport orders:
    • created in ERP without reference to stock transfers planned in OBP or PP/DS
    • changed in ERP with respect to scheduling relevant order data
  • If a transportation resource is assigned for resource scheduling, a receiving handling resource must be assigned to the ship-to location.
  • The transportation calendar must be consistent with the OBP side, that is:
    • Consistent non-working days,
    • Full 24 hour time streams that span from 00:00:00 to 24:00:00
  • The transport duration in hours must be consistent with the lead time in the OBP Transportation Lane in days and correspond to integer days, such as 48:00 hrs
  • Resource Scheduling: If a transportation resource is assigned to the Means of Transport
    • an inbound handling resource has to be maintained for the ship-to location
    • the transportation resource must not have breaks or shifts, that is 24 hour availability for comparable resource consumption with OBP
    • the transportation resource calendar must be consistent with the OPB transportation calendar with respect to non-working days and fulfill the same requirements as for the transportation calendars, i.e. consistent non-working days and full 24 hour time streams

Further restrictions and prerequisites for a consistent master set up may apply. Refer to SAP notes 3372270 and 3372280.

In case stock transport orders in ERP are scheduled with exact dates and times using shipment and route scheduling capabilities of the ERP SD Module these exact dates and times can be integrated to OBP and PP/DS without rescheduling in the target planning system.

In this case the target planning system integrates the following exact dates directly from the ERP system, without re-scheduling in addition to the Planned Delivery Date/Time:

  • Availability Date/Time
  • Goods Issue Date/Time (currently not relevant)
  • Requirement Dates/Time

A consistency check is applied to the above dates in case of no-rescheduling:

  • Requirement (Planned Start) Date is not in the past
  • Requirement Date <= Planned Delivery Date (GR Date) <= Availability Date

If the consistency checks are not passed, then backward and forward scheduling will happen in the target system despite the no-rescheduling flag.

Restriction: If the no-rescheduling flag is set, no transport or handling resource will be assigned to the stock transport order in PP/DS.

Additional things to consider for S4/HANA PP/DS as DSC Edition 3 system landscape

  • Maintain Factory Calendar in the DSC instance consistently with the Factory Calendar in the ERP system (transaction OX10).
  • Maintain PPIM and DPS Horizon using Transaction SYPP_MARC_EXT_MAINT consistently with SYPP_MARC_EXT on ERP.

    Further restrictions and prerequisites for a consistent master set up may apply. Refer to SAP notes 3372270 and 3372280.

Further sources of information

SAP Help

SAP Note

  • 3372270 - "Short-term production planning and detailed scheduling delegated (3)" without scope restriction in S/4HANA advanced planning
  • 3372280 - Ensuring Date and Time Consistency of Purchasing Receipts between SAP IBP Order-based Planning, SAP S/4 ERP and SAP S/4 PP/DS in order-based production planning integration
  • 3291712 - Preserve the Overall Order-Based Planning Outcome with Production Planning Integration Mode 3 after Rolling into the PP/DS Horizon

Log in to track your progress & complete quizzes