Scheduled Planned Order in ERP with Qty = 10.
- SAP Managed Tags:
Introduction
This blog provides an overview of the integration and functionality of SAP S/4HANA 2021 Manufacturing for planning and scheduling (aka ePP/DS) as modular deployment side-by-side to ECC with Digital Supply Chain, Edition for S/4HANA and a use case for takt-based, flow manufacturing in PP/DS to demonstrate the PP/DS integration and functionality.
As demo scenario in PP/DS on DSC for SAP S/4HANA you find a overview description on basic configuration, master data for a takt-based, flow manufacturing for configurable products.
The use case shows an planning scenario with Model-Mix-Planning and Sequencing in PP/DS for SAP DSC Edition for SAP S/4HANA.
SAP DSC Edition for S/4HANA offers SAP S/4HANA innovations to customers independently from SAP- ECC as many customers are not planning to convert their SAP ECC 6.0 to SAP S/4HANA soon nor to implement SAP S/4HANA in a Greenfield approach
For overview information about the DSC Edition for S/4HANA Manufacturing for planning and scheduling see Thomas Klemm’s blog “SAP S/4HANA 2020 Manufacturing for planning and scheduling – modular deployment side-by-side to ECC” and in document “SAP Digital Supply Chain Management, Edition for SAP S/4HANA” section “SAP DSC Edition for S/4HANA Manufacturing for Planning and Scheduling overview and roadmap Information”.
Latest information on restrictions for SAP DSC Edition for S/4HANA Manufacturing for Planning and Scheduling and a complete installation guide can be found in note “2997719 - Restrictions and Implementation Recommendations for Using Advanced Planning Side-by-Side w...
Target audience of this blog are project team members and key users who are interested in PP/DS on SAP DSC Edition for SAP S/4HANA or responsible for the implementation of production planning with SAP DSC Edition for SAP S/4HANA.
Readers should be aware of the key functional solution in production planning and scheduling with PP/DS.
Overview
With SAP DSC Edition for S/4HANA Manufacturing for Planning and Scheduling customers can use advanced planning (PP/DS) side-by-side with an ERP system.
This means an SAP-ERP system is connected to an SAP S/4HANA system, which is exclusively used for DSC edition (no other SAP S/4HANA components can be used in the same client).
SAP DSC Edition for S/4HANA -Manufacturing for Planning and Scheduling
Integrating PP/DS
I will not describe any details concerning technical settings for data exchange nor Basic Settings for setting Up the System Landscape.
Nevertheless, basic knowledge of the various system architecture (APO, S/4HANA, DSC Edition) supports understanding of the SAP System integration with SAP DSC Edition for SAP S/4HANA.
You will find information concerning data exchanged between SAP APO and the ERP system and how the systems integrated from a technical point of view in the SAP Help Portal: refer to Integration via Core Interface (CIF)
The transfer of master data and transaction data between APO and other SAP systems is controlled in the Core Interface (CIF) by an integration model.
When master data is transferred from SAP ECC to APO-PP/DS, it is mapped to corresponding master data in APO. Not all the data is transferred from ECC to APO, only that which is relevant for planning in APO
PPDS Integration Technology with APO-PP/DS
PP/DS Integration Technology with APO-PP/DS
Master Data
- Replication via I-Model Generation & Activation
Transactional Data
- Replication via I-Model Generation & Activation
In the SAP S/4HANA System the PPDS functionality gets co-deployed with SAP S/4HANA on the same system.
PP/DS is an integral part of S/4HANA, not an add-on, not side-by-side and the integration has been simplified with an easy master data and integration model maintenance.
For details on “Best practices for implementation of Production Planning and Detailed Scheduling for SAP S/4HANA” refer to SAP note 2712349 and the PPDS Cookbook attached to the SAP Note.
https://launchpad.support.sap.com/#/notes/2712349
The SAP Note and the PDF document should not be considered as the implementation how-to documentation for the embedded PP/DS processes and scenarios. It is a collection of best practices based on the experience collected by SAP experts in the recent PP/DS on SAP S/4HANA implementation projects.
PPDS Integration Technology with PP/DS for SAP S/4HANA
PPDS Integration Technology with PP/DS for SAP S/4HANA (important object types below)
Master Data
- CDS Redirect
- Material
- Replication w/o I-Model
- Location
- Work Center
- PDS
- Replication w/ I-Model Gen & Act:
- External Procurement
- Setup Group & Key
Transactional Data
- Replication w/o I-Model
Equal to the SAP-ECC & APO-PP/DS integration both systems (SAP-ECC and DSC Edition for S/4HANA) are connected via Core Interface (CIF) with the difference that the integration to PP/DS in DSC is partially mapped via the ERP of DSC for S/4HANA. Some master data cannot be transferred but must be created in both systems as described in sections 4.1 of SAP Note 2997719
PPDS Integration Technology with PP/DS of SAP Digital Supply Chain Management, edition for SAP S/4HANA
PPDS Integration Technology with PP/DS of SAP Digital Supply Chain Management, edition for SAP S/4HANA (DSC system) ( important object types below)
Master Data
- Manual Replication
- Plants, MRP Areas, Business Partner
- Replication w ALE/IDOC (step 1) ERP to DSC and w/ I-Model Gen & Act within DSC (step 2)
- Class & Char
- Replication w/ I-Model Gen & Act to ERP of DSC
(following CDS Redirect or simpl. Int.)
- Material
- Work Center / Capacity
- Replication w/ I-Model Gen & Act:
- all others
Transactional Data
- Replication w/ I-Model
Settings for Master- and Transaction Data Integration for both systems (SAP-ECC and PP/DS for DSC on S/4)
The following summary gives an overview about main master- and transaction data and the prerequisites for the master and transaction data integration for PP/DS of DSC for SAP S/4HANA.
As mentioned this article should not be considered as the implementation how-to documentation for the PP/DS of DSC nor PP/DS processes and scenarios.
Depending on your business processes, additional configuration settings and master data may be required.
For current constraints and restrictions of Manufacturing for planning & scheduling (aka ePP/DS) capability of SAP Digital Supply Chain Management, edition for SAP S/4HANA (DSC system), see SAP Note 2997719.
Location
Plant (Location) cannot be transferred by CIF and must be created in the PP/DS on DSC system manually via customizing (same for MRP Area and Business Partner).
Define Plant in DSC customizing and for Locations in PP/DS execute the following reports to create and update locations in ePP/DS
- Create – /SAPAPO/CREATE_LOCATION for creating and Update – /SAPAPO/UPD_LOC_SP_PL for updating Plant, MRP Area and Shipping Point
Material / Product
With SAP APO-PP/DS materials are transferred from the ERP system to the SCM system via the Core Interface (CIF) and created in APO as master data object product in PP/DS.
In SAP S/4HANA you activate an SAP S/4HANA Material for planning in embedded PP/DS by activation of the “Advanced Planning” checkbox in the “Advanced Planning” tab of the material master. In SAP S/4HANA CDS redirects on SCM tables - CDS views have been introduced to redirect product master data from material master tables to SAP SCM tables.
With PP/DS for DSC, edition for SAP S/4HANA there is a hybrid of both functions.
First a CIF transfer SAP-ECC to DSC for S/4 replicate the material master in the ERP of DSC.
In the DSC material master the “Advanced Planning” checkbox of the material master will be activated by CIF and in PP/DS for DSC the product master data is available via CDS view to the material master
Basically, the integration via CIF only transfers the data that is relevant for PP/DS, but with DSC for SAP S/4HANA the material master will be recreated in DSC.
Since some master data and master data attributes cannot be transferred using CIF and therefore must be maintained as prerequisite in the ERP of DSC system.
You have to prepare the ERP system in the DSC for the communication with the SAP-ECC system.
For details refer to chapter 4.1 Manual Creation of Master Data in PP/DS System (p. 21) in SAP Note 2997719.
WorkCenter-Capacity / Resources
Work Centers and Resources are transferred from SAP-ERP to DSC for SAP S/4HANA using the same procedure as the integration of Materials/Products.
The CIF transfer SAP-ECC to DSC for S/4 replicate also the Work Center in the ERP of DSC. Following a simplified integration (No CDS view and No IMod) will create the Resources in PP/DS of DSC automatically.
Same as at the material integration some master data for WorkCenter in ERP of DSC cannot be transferred by CIF but must be created in both systems as described in sections “4.1 Manual Creation of Master Data in PP/DS System” in SAP Note 2997719.
Master data for WorkCenter in ERP of DSC which have to be created manually are Work Center Responsible, Storage Location Storage Resource and Shifts, Formulas, and other Capacity-Relevant Objects.
Which master data must be created separately in ERP of DSC depends on the individual customer scenario -check your SAP ERP master data , if they are relevant for the very same master data in ERP on DSC as prerequisite for data integration within DSC for SAP S/4HANA.
Classes and Characteristics
If you are using classes and characteristic in your Production Planning scenario, the integrations process is different as classes and characteristics have to be transferred via Application Link Enabling (ALE).
You also have to make sure that the master data are set up in the SAP-ERP and DSC for SAP S/4HANA system and transferred in the correct order. For details see chapter 7.1 Master Data Integration with Classes and Characteristics of SAP Note 2997719.
Integration with Classes and Characteristics in classical PP/DS scenario
For material classifications and variant data, only the initial transfer via CIF is currently supported. Since the update transfer is currently not supported you have to execute the Report RIMODINI (Report to start Initial Supply for Integration Models) regularly.
Model Mix Planning and Sequencing (Lean-Automotive Scenario)
Depending on the planning and scheduling processes, shop floor layout, product complexity, stability of production, and other criteria the companies have different requirements to production planning.
Production Planning and Detailed Scheduling in SAP S/4HANA supports various Manufacturing Models:
- Discrete Manufacturing
- Process Industrie
- Repetitive Manufacturing
- MTO / MTS / ETO…
- Special topics like SAP for Mill Products
SAP Manufacturing experts often have knowledge on business processes in Discrete Manufacturing and Repetitive Manufacturing and have at least basic knowledge or experience in “classic PP/DS” using the standard PP and DS Heuristics for Planning and Scheduling.
Most KBA, Blogs and others focus on ‘classical PP/DS’ (see Blog “Overview of the key functionality Production Planning and Detailed Scheduling in embedded PP/DS on S...”
SAP Experts often struggles with the PP/DS setup and configuration of production planning and scheduling in repetitive and flow manufacturing.
The following section of this blog post provides you with a high level description of a use case of ‘Single Line Planning with Model Mix Planning and Sequencing via iPPE” in PP/DS on DSC for SAP S/4HANA in the Automotive business Axle manufacturing.
This article will describe the special scenario ‘Lean-Automotive’ - this solution mainly based SAP ERP classic master data for manufacturing - based on SAP classic BoM and Routing. In the iPPE only dummy headers and very basic data are needed and only in PP/DS.
It is a simple lean solution for enhancing existing SAP ERP processes with sequence optimization in PP/DS in DSC for SAP S/4HANA.
For details refer to SAP Note 627377 - Consulting Note : Model-Mix-Planning and Sequencing
https://launchpad.support.sap.com/#/notes/627377
The information of the blog does not replace the SAP Help nor the SAP Service notes.
Repetitive manufacturing is typically used in production processes that meet the following criteria:
- The same or similar products are produced over a longer period.
- The manufactured products are not produced in individually defined lots.
(Instead, a total quantity is produced within a certain time at a defined takt.) - The products are scheduled on a production in a defined sequence.
- Routings are usually simple
- High product stability, high repetition rate, low product complexity
The term “repetitive manufacturing” can be categorized in takt-based flow manufacturing, mass production, and period-based production (as classic REM)
Takt-based flow manufacturing is when the production process is controlled by a cycle. Each material/planned order is dispatched to the production line with the same takt time/rate during takt-based scheduling.
The component Model-Mix-Planning is used for takt-based, flow manufacturing for configurable products with a high volume of orders, such as engines or axles, for example.
In this type of production, different products are often produced together on one production line or a line network.
Model Mix Planning is based on the master data of the integrated Product and Process Engineering (iPPE).
For details see SAP help “Integrated Product and Process Engineering (iPPE)”
Overview Discrete Manufacturing w ‘classical’ PPDS and REM w MMP SEQ
As mentioned, based the ‘Lean-Approach’ of Model-Mix-Planning and Sequencing mainly on classic master data for manufacturing (based on SAP classic BoM and Routing)
Only iPPE dummy headers and very basic data are needed and only in PP/DS.
Big-Picture “Lean-Approach” MMP , SEQ in PP/DS
"Image/data in this Blog is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
System landscape for Demo Scenario
Setup Model Mix Planning and Sequencing (Configuration, Master Data and Business Processes)
In the next section you will find an example scenario on high level and a how-to guide to implement and run Model-Mix-Planning and Sequencing with iPPE as Lean-Approach in SAP-ERP and DSC Edition for S/4HANA Manufacturing for planning and scheduling.
You’ll have a good understanding about the basic functionality of MMP&SEQ and should be able to compare the functionality and applications to a classical PP/DS scenario.
When you reproduce the next steps in your system it may support you in Prototyping and Proof of Concept of this SAP Manufacturing solution.
Pre-Requisites in SAP-ERP and SAP-DSC Edition for S/4HANA Manufacturing for planning and scheduling
| Basic Settings for Creating the System Landscape | Setting Up System Connections in SAP-S/4HANA (see also chapter “3 Customizing and Configuration” in SAP S/4HANA Manufacturing for Planning & Scheduling - Implementation Guide (2021.1) |
| Configuration schema in PP/DS to ‘VC’ | Set the Variant configuration schema in PP/DS to ‘VC’ using SPRO path: Advanced planning à Define Configuration Schema (CDP or Variant Configuration) |
| Setup and Integration of Master Data - | Manual Creation of Master Data in the SAP-DSC Edition for S/4HANA System See chapter “4.1 Manual Creation of Master Data in PP/DS System” |
For details refer to the installation guide in SAP note “2997719 - Restrictions and Implementation Recommendations for Using Advanced Planning Side-by-Side w...
Setup and Integration of Master Data in SAP-ECC
Create Characteristic in SAP-ERP |
Transaction [t-code]: CT04
Create Characteristic “DSC_AXLE”
Format CHARACTER 3
Char.Values: STD (Standard) & HVY (Heavy Load)
Create Characteristic
Create Class in SAP-ERP |
t-code: CL02
Create Class ‘DSC_Axle’
Class type ‘300 - Variants’
Char: ‘DSC_AXLE’
Org.Area ‘B’
(Determine the scope of the class and characteristic master data to be transferred in the integration model by specifying the organizational area , see also SAP help:
Integration of Classes and Characteristics -> Prerequisites
Create Class
Transfer Class &Characteristic from SAP-ERP to PP/DS-DSC |
Send Characteristic from SAP-ERP to PP/DS-DSC |
See also chapter “7.1 Master Data Integration with Classes and Characteristics” of the Implementation Guide in SAP Note 2997719
t-code BD91
On the ‘Distribute All Characteristics via ALE’ select the following entries.
Characteristic: DSC_AXLE
Logical System: QKKCLNT440 (your DSC Edition System)
Send Characteristic from SAP-ERP to PP/DS-DSC
Confirm PopUp
Send Class from SAP-ERP to PP/DS on DSC |
t-code BD92
On the ‘Distribute Classes via ALE: send direct ’ select the following entries.
Class Type 300 – Variants
Class: DSC_AXLE
Logical System: QKKCLNT440 (your DSC Edition System)
Send Class from SAP-ERP to PP/DS-DSC
Confirm PopUp
Integration model for class & characteristic to be generated and activated in ECC & PP/DS |
t-code CFM1 & CFM2
Integration Model:
Model Name DSC_CHARCL
Logical System QKKCLNT440
APO Application DSC_PPDS
SelClasses&Char = fagged
Org.area ind. B (see also Integration of Classes and Characteristics à Prerequisites)
Class Type 300
Integration model for class and characteristic from SAP-ECC to DSC for SAP S/4HANA
Data transfer from S/4-DSC-ERP to DSC-PP/DS |
Transfer Class and Characteristic from ECC System to DSC for S4 |
Configure also in DSC for S/4HANA the Org.Area Ind ; Indicator for an organizational area used in Char.& Class as selection criteria in integration model
t-code CFM1 & CFM2
Integration Model:
Model Name DSC_CHARCL
Logical System QKKCLNT440
APO Application DSC_PPDS
SelClasses&Char = fagged
Org.area ind. B
Class Type 300
Transfer Class and Characteristic from DSC-ERP System to PP/DS-DSC-S/4
Create Configurable Material (KMAT) in SAP-ERP |
t-code MM01
Create KMAT in SAP-ERP:
Matnr DSC_KMAT_137 in Plant ERN1
On Basic Data 2 – flag material as “Configurable Material”
On Classification - assign Class-type 300 and Class/Char ‘DSC_AXLE’ to material:
Create Configurable Profile for KMAT |
t-code CU41
Create configurable profile for object material and material KMAT DSC_KMAT_137
On Screen “Configurable profile for Material” define Prof.Name DSC_KMAT
By ‘Class Assignments’ assign Class&Char DSC_AXLE to Configurable profile
In Config.Profile Details set flag for Planned/Production Order
Create Material Variant Material (FERT/HALB) in SAP-ERP |
t-code MM01
Create Material Variant in SAP-ERP:
Matnr DSC_FG_137_VAR_STD
& DSC_FG_137_VAR_HVY in Plant ERN1
On Basic data 2 and MRP 3 View assign Material (KMAT) DSC_KMAT_137 to Material;
Classify Characteristic (STD or HVY)
Basic Data 2 and MRP3 View
Characteristic value
Transfer KMAT Configurable profile to DSC |
t-code CLD1
Distribute Configuration Profile (Mat)
On the ‘Distribute of Configuration Profiles for Materials’ select the following entries.
Material DSC_KMAT_137
Logical System: QKK9CLNT440 (DSC Edition System)
Confirm PopUp
Generate & Activate Integration Model for Material and Planned-&Production Order in ECC |
Generate & active Integration Model for Material
Model Name DSC_MAT
Logical System QKKCLNT440
APO Application DSC_PPDS
Material DSC*
Plnt ERN1
Application A ( indicator for location product to be active Advanced planning in the target system in DSC-S/4)
Generate & active Integration Model for Planned & Production Orders
Model Name DSC_ORD
Logical System QKKCLNT440
APO Application DSC_PPDS
Material DSC*
Plnt ERN1
Create manufacturing master data in SAP-ERP |
Create Bill-of-material for KMAT
T-code CS01
Enter the following data:
Material DSC_KMAT_137
Plant ERN1
BOM Usage 1 Production
On screen ‚Create material BOM: General Item Overview” maintain the following components as BOM.items
(prerequisite: Create material master for components with t-code MM01)
Create Link of Material-Variant to Configurable Material
T-code CS40
Enter Material DSC_FG_137_VAR_STD ( & DSC_FG_137_VAR_HVY)
Plant ERN1
BOM usage 1
Assigne to Configurable Material BOM
Assigne Material-Variants to KMAT BoM and check assignments with ‘All Assignments to BOM’
Create WorkCenter for Order Scheduling in ERP-PP
WorkCenter for Takt Scheduling -Var. Duration
t-code CR01
Work Center: DSC_TAKT
Plant. ERN1
Create Work Center for Offset – schedule fixed duration
Work Center: DSC_OFFS
Plant. ERN1
Standard Value key for Duration:
Maintain Formula for Processing Capacity Requirementson tab Capacities accordingly.
Create ERP Manufacturing Routing for Finished Good Axle
(in PP/DS planned by Lean-Automotive with iPPE master data)
t-code CA01
Create production versions
t-code C223
Create production versions as follows
Check in DSC Edition on S/4HANA -Material Master Data - Configuration Data / Class/Characteristic and Advanced Planning |
Check after the transfer of material masers via integration model that Classification view has been copied from the source system, otherwise create manually and assign relevant classes.
Set material to configurable if setting was not transferred. (Before DSC on S/4HANA 2021)
Configure variants in Basic Data 2 and MRP 3 views after configuration profiles were imported and data were not transferred via CIF (before DSC on S/4HANA 2021)
t-code MM02
Check Material Master in DSC Edition – Configuration Data / Adv.Plan
Material
DSC_KMAT_137 (KMAT) /
DSC_FG_137_VAR_STD & DSC_FG_137_VAR_HVY
Plant
ERN1
Advanced Planning View
Plan Explosion to ‘3’ – Single Explosion of iPPE ; and Planning Procedure to ‘4’ Planning in Planning Run
If Material is a Material Variant -->
Check Basic Data 2 & MRP 3 View & Characteristic
(Check also configuration in DSC Product Master)
Now the required master data in ERP have been created and transferred to DSC.
In the next section the master data in SAP DSC Edition for S/4HANA Manufacturing for Planning & Scheduling (PP/DS) for this scenario will be created.
Create iPPE – Master Data in DSC Edition |
Only very basic iPPE needed and only in DSC Edition for S/4HANA
For details on iPPE see SAP help “Integrated Product and Process Engineering (iPPE)”
With Integrated Product and Process Engineering (iPPE) all master data can be maintained in the BOM, the routing, and line design in one model and it is particularly suitable for repetitive manufacturing.
Within one master data:
- maintain BOM data for configurable and non-configurable materials using the product variant structure and the assemblies.
- maintain routing data using the process structure
- maintain structures of production lines using line design.
- …and Relations between Application objects
iPPE: iNTEGRATED Product and Process Engineering
Start with User assignment in iPPE workbench
In the iPPE application users can create and edit a large amount of different data.
User profiles preselect and restrict the quantity of data available for predefined work areas in iPPE and making it easier to work with the data.
T-code OPPE13
On screen “User assignment in iPPE workbench”
select “Total display” available in 5th Position in the drop-down list
- set flag active for “Standard Profile” & “General Display Variants
Create iPPE master data (only dummy / Basic data)
t-code /PPE - (do not use /SAPAPO/PPE)
Create Access Node ex: DSC_MFG_AXLE, Enter Class details.
Function ‘Create’
- Create Application ‘CMP - Product Structure’
- Choose Tye ‘Product Variant Structure’ flagged
- Type S_HD - Access Node
- Node DSC_MFG_AXLE
- Class DSC_AXLE
- Class Type 300 - Variants
- Press Function ‘Create’
on Screen ‘iPPE:Change’ enter Description “iPPE Axle Manufacturing in DSC”
Assign Variant under Access Variants Tab
Enter Material in Tab ‘Access Variants’ (Qty = 1 EAN)
Access Variant Material Qty /UM
1 DSC_KMAT_137 1 EA
V1 DSC_FG_137_VAR_STD 1 EA
V2 DSC_FG_137_VAR_HVY 1 EA
Create Line Routing
Enter Node “DSC_MFG_AXLE” and Class details.
Function ‘Create’
- Create Application ‘ACT - Process Structure’
- Choose Tye ‘Routing’ flagged
- Type S_ACTHD – Line Routing
- Node DSC_MFG_AXLE
- Class DSC_AXLE
- Class Type Variant
Press Function ‘Create’
Create Activity
Enter: "DSC_AXLE_LINE_ACTIVITY" and Class details
- Create Application ‘ACT - Process Structure’
- Choose Tye ‘Routing’ flagged
- Type S_ACTST – ACTIVITY (Line)
- Node DSC_AXLE_LINE_ACTIVITY
- Class DSC_AXLE
- Class Type Variant
Press Function ‘Create’
Assign Mode under Activity in field: Primary Resource
Enter "DSC_AM" - Resource as free text and confirm to create Resource
Confirm “Selected Production Resource Does Not Exist. Do You Want to Create it?” (see next step)
Create Production Resource DSC_AM of type: Operation Facilities
Assign rate under Mode Tab
Drag & drop Activity under Routing
Create Component / Structure node
- Create Application ‘CMP – Product Structure’
- Choose Tye ‘Product Varian Structure flagged
- Type S_ST – Structure Node
- Node DSC_AXLE_COMPONENT
- Class DSC_AXLE
- Class Type Variant
Press Function ‘Create’
Assign your Components under Variants Tab for the Structure Node, for this Demo scenario a dummy component will be assigned ex: DUMMYPOS.
Once Planned Order planned by MMP & SEQ and published to ECC will get the component assigned from the Production version (BoM & Routing) in ERP.
You can also assign component that are planned with ‘classical’ PP/DS in DSC
Assign Structure node to Access Node Header under Relationship Tab Upward: DSC_MFG_AXLE
Drag & Drop Structure node to Activity of all variants
Create Line /Resource under Factory Layout,
Enter "DSC_ASSEMBLY_LINE"
- Create Application ‘FLO – Factory LAYOUT’
- Type S_FLOLIN – Line
- Node DSC_ASSEMBLY_LINE
Press Function ‘Create’
Assign below details regarding number of Takt and enter Line resource name.
Line Resource "DSC_ASSEMBLY_LINE_RES”"
Assign the Action point (End) in Line under Action Point Tab “DSC_AC_POINT”
configure Reporting Point : 0001
Assign Line Balance ‘DSC_LB’ on Tab Line Balance in Line and Save.
Enter Effectivity for Line Balance i.e. Valid from Date
Create Production Version:
Navigate to “Accesses” Tab for Access Node (1) , then change usage to Production (2) & enter Plant (3) & click on create Production version (4)
Repeat the same steps for all variants
On Screen ‘Production Version Create” fill all the details regarding Routing, Line resource & production version ID. (PV01)
Enter & Save
Master Data in the iPPE has been successfully created.
Execute iPPE Consistency Check
Check the consistencies of the PPE with option "Create New Check logs"
T-code: PPECHK
Select: Material ‘DSC*’ and Plant ERN1
Log shows ‘No Error in iPPE‘
Convert the iPPE Data in PP/DS
Create Line Resource “DSC_ASSEMBLY_LINE_RES” in iPPE
T-code: PPEAPO
Select your Material ‘DSC*’ in Location ERN1
Check the Log
Assign Production Rate in the Resource Production Line created in the previous step under tab: Time continuous Capacity
t-code: /SAPAPO/RES01
Select Resource ‘DSC_ASSEMBLY_LINE_RES’ in Location ‘ERN1’, Planning Version ‘000’
Assign the resource to model 000
Generate PDS (Production Data structure)
The production data structure (PDS) contains active master data from Integrated Product and Process Engineering (iPPE) and provides the basis for planning in PP/DS.
The PDS is generated from a production version in the iPPE in PP/DS.
T-code: /SAPAPO/GEN_PDS
Select your Material ‘DSC*’ in Location ERN1
Display Logs: no Error --> PDS generated
Display Production Data Structure (PDS) for the Demo Products
t-code /SAPAPO/CURTO_SIMU
The master data for the demo scenario have been created
in the next step the Model-Mix-Planning and Sequencing will be configured in PP/DS
Configuration related to Model Mix Planning & Sequencing in DSC Edition |
MMP in PP/DS is a component for takt-based, flow manufacturing for configurable products with a high volume of orders, such as engines or axles, for example. In this type of production, different products are often produced together on one production line or a line network.
Purpose of Model Mix Planning is to create a production schedule in the medium to long-term planning horizon. In PP/DS various heuristic procedures are available for dispatching the orders.
In the planning the system takes the delivery dates, available capacities, and any existing restrictions into account.
For details on Model-Mix-Planning refer to SAP Help Model Mix Planning
This Blog provides information on a simple/high level planning scenario, you can use this guide to setup your own scenario in your system and get hands-on exercises in MMP & SEP.
This article does not cover the complete range of planning and scheduling functions of MMP&SEQ in detail.
Model Mix Planning and Sequencing uses procedures as a planning function.
You can use procedures of varying complexity, depending on the planning result and horizon desired.
The following table lists the procedures provided by SAP as standard.
| Procedure | Capa. Load | Restrictions | Desired date |
| Materials Planning ProcedureSimple procedure used to create planned orders for uncovered requirements | X | ||
Percentage Smoothing This procedure divides the orders equally across the planning periods to achieve a hundred percent load per period. | X | ||
Prioritized Equal Distribution A procedure that distributes the variants equally within a planning period (day, shift) and distributes according to priority. | X | X | |
LP Procedure Procedure used in the medium to long-term horizon for multiline planning. Using the LP procedure, you can achieve an optimum assignment of period packages to the processing paths of the products produced on a line network. | X | X | X |
Genetic Algorithm Procedure that achieves an optimized sequence of orders in the short-term horizon. This procedure is highly recommended when dealing with complex situations with a large number of soft restrictions. | X | X | X |
Slotting Heuristics Heuristic used in the short-term horizon for make-to-order production to create an optimum order sequence for multi-variant products. This heuristic is particularly suitable for dealing with problems mainly concerned with hard restrictions. | X | X | X |
Configure Slotting Heuristics
For details see SAP help Slotting Heuristic
t-code: SPRO
IMG path: Advanced planning -> Model mix Planning -> Define Slotting Heuristic
(you can use & copy SAP Standard as template 01SAP_QS_01, 01SAP_QS_02)
Z1DSC_QS_01 Z1DSC_QS_02
Define Planning Calendar / Time Stream
Before maintaining Procedure Package & Restriction, define time stream
IMG path: Advanced planning -> Master data à Calendar -> Maintain Planning Calendar
(Time Stream)
See Creating and Assigning the Planning Calendar
Define Procedure Package
With procedure package, you can split the planning period into several planning horizons and assign a different procedure to each horizon. This means you can increase the level of detail of your planning on a step-by-step basis.
See Defining Procedure Packages
t-code SPRO ; IMG path: Advanced planning -> Model mix Planning -> Define Procedure Packages
copy ’01SAP_MMP…’ profiles to ‘Z1DSC_MMP….’ (e.g. 01SAP_MMP_10 to Z1DSC_MMP_10)
Assign Horizon with Period and assign the algorithm created in previous step in Procedure Profile
If you want to define your own , user-specific procedure packages please check the also the IMG activity documentation of IMG "Define Procedure Packages.
You find details on the Functionality of single procedures also in the customizing:
You can setup the following Procedure Packages to test Model-Mix-Planning:
| Procedure Packages | |||||||||||||||
| Name | RefCalender | Planning Offset | Description | ||||||||||||
| ZDSC_MMP_001 | ZDSC_MMP | 1 | DSC Simple Material Planning Procedure | ||||||||||||
| Horizons | |||||||||||||||
| Sequence | Name | Description | Period to | Adj.Per | Planning basis | Proc.Profil | |||||||||
| 10 | 01SAP_PA01 | Simple Materials Planning Procedure | 200 | REQDAY (Req. per day (lot size>1) | |||||||||||
| Procedure Packages | |||||||||||||||
| Name | RefCalender | Planning Offset | Description | ||||||||||||
| ZDSC_MMP_002 | ZDSC_MMP | 1 | DSC Percentage Smoothing & Simple MRP | ||||||||||||
| Horizons | |||||||||||||||
| Sequence | Name | Description | Period to | Adj.Per | Planning basis | Proc.Profil | |||||||||
| 10 | 01SAP_PG04 | Percentage Smoothing (Mixing/Date) | 10 | 1 | REQDAY (Req. per day (lot size>1) | 01SAP_PG_01 | |||||||||
| 20 | 01SAP_PA01 | Simple Materials Planning Procedure | 200 | REQDAY (Req. per day (lot size>1) | |||||||||||
| Procedure Packages | |||||||||||||||
| Name | RefCalender | Planning Offset | Description | ||||||||||||
| ZDSC_MMP_003 | ZDSC_MMP | 1 | DSC Percentage Smoothing & Simple MRP | ||||||||||||
| Horizons | |||||||||||||||
| Sequence | Name | Description | Period to | Adj.Per | Planning basis | Proc.Profil | |||||||||
| 10 | 01SAP_BS02 | Prioritized Equal Distribution | 10 | 1 | REQDAY (Req. per day (lot size>1) | 01SAP_BS_01 | |||||||||
| 20 | 01SAP_PA01 | Simple Materials Planning Procedure | 200 | REQDAY (Req. per day (lot size>1) | |||||||||||
| Procedure Packages | |||||||||||||||
| Name | RefCalender | Planning Offset | Description | ||||||||||||
| ZDSC_MMP_004 | ZDSC_MMP | 1 | Gen.Alghm; Percent.Smthng, Simple MRP | ||||||||||||
| Horizons | |||||||||||||||
| Sequence | Name | Description | Period to | Adj.Per | Planning basis | Proc.Profil | |||||||||
| 10 | 01SAP_GA02 | Genetic Algorithm | 10 | ORDSLG (Ord. w (lot size =1) | 01SAP_GA_04 | ||||||||||
| 20 | 01SAP_PG04 | Percentage Smoothing (Mixing/Date) | 80 | 6 | REQDAY (Req. per day (lot size>1) | 01SAP_PG_01 | |||||||||
| 30 | 01SAP_PA01 | Simple Materials Planning Procedure | 200 | 12 | REQDAY (Req. per day (lot size>1) | ||||||||||
Define restriction based on business needs
Restrictions are conditions based on characteristics which you use to determine the sequence of orders in Model Mix Planning.
Using restrictions, you can define certain limits on the production capacity. This may be necessary, for example, if the availability of a particular component is limited or similarly if personnel capacity is limited.
For details refer to SAP Help Restrictions
Restrictions often used in MMP&SEQ projects are:
- Spacing
- Quantity
- Block
- Even distribution
In this demo scenario on the axle manufacturing line resource a block of minimum 9 and maximum 12 Standard (STD) axles must be assembled following by a block auf minimum 3 and maximum 6 heavy load axis (HVY)
In PP/DS block restrictions will be used to limit the occurrence of Axle types to a certain number of consecutive products (e.g. max 12 STD followed by min 3 HVY Axles)
Maintenance via T-code: /SAPAPO/RET2
Enter the following selection:
Planning Version : ‘000’
Line ‘DSC_ASSEMBLY_LINE’
Switch from Display to Change mode
On Screen ‘Restrictions: Maintain’ execute function ‘Create Restriction’
and enter the following data;
Name ‘DSC_ASSEMBLY_LINE_STD’ (Standard on DSC Assembly Line )
Prod. Line ‘DSC_ASSEMBLY_LINE’
Category ‘Block’
Click “Value Assignment” and confirm ‘Selection Condition’ on the PopUp
On Screen ‘Restrictions: Maintain’ Enter the following value:
DSC_AXLE = ‘STD’
Define the Minimum & Maximum Block size ( e.g. Minimum =9; Maximum = 12)
Repeat this step for Restriction “DSC_ASSEMBLY_LINE_HVY” (Heavy on DSC Assembly Line ) - DSC_AXLE = ‘HVY’ and Blocksize = Minimum = 3, Maximum = 6
Display Characteristics/Restrictions Using Visualization Profile
You can define Visualization Profile for the display of the characteristics & Restriction created in previous step in the sequence schedule via Customizing or you can also define a visualization profile for restrictions directly in the sequence schedule using the Create Visualization Profile function
For details refer to SAP help Display Characteristics/Restrictions Using Visualization Profile
IMG path: Advanced planning -> Model mix Planning -> Define Visualization Profiles
On Screen ‘Change View “Visualization Profil”: Overview’ choose ‘New Entries’ and enter the following data:
Visualzn Profile ZDSC_AXLE
Description Visual Profile DSC Lean-Auto
On Screen ‘Change View “Characteristics/ Restrictions”: Overview’ choose ‘New Entries’ and enter the following data for Visualzn Profile ZDSC_AXLE
On Screen ‘Change View “Application”: Overview’ choose ‘New Entries’ and enter the following data for Visualzn Profile ZDSC_AXLE
Create Layout:
For details refer to SAP help Defining Users and Line-Specific Layouts
Run Planning in DSC-PP/DS - Model Mix Planning & Sequencing in DSC Edition |
In the next section the Model Mix Planning will be executed.
First you create a simulative Demand as prerequisite for planning, than you execute a model mix planning run for a longer planning horizon, check the result in the Product Planning Table or Product View and in the short-term horizon execute the interactive Sequencing.
For details refer to SAP Help: Carrying Out Model Mix Planning
Create Demand as simulative Forecast in PPDS via Product Planning table
t-code: /SAPAPO/PPT1
Enter the following selection
Plng Version 000
Location ERN1
Planning Horizon (Current Week / Monday till end of next week Friday)
From 07.03.2022
To 18.03.2022
On tab Line/ Resource enter Production Line “DSC_ASSEMBLY_LINE”
Via Settings -> User Settings set variant ‘SAP_MMP’ and on tab ‘Resource’ set Flag “Unit of Measure for the Base Rate”
Unit of Measure for the Base Rate = ‘active`
Determines, that the available capacity for the line resources to the quantity of the base rate is displayed in the periodic resource view.
If you do not set this indicator, the available capacity is displayed in the time unit, which you define in the user settings. Define the base rate in the master data for the resources
In this DSC Scenario the available capacity of Line Resource DSC_ASSEMBLY_LINE_RES
is 1.440 EA per Day
Enter a negative demand as Forecast for the current week.
e.g. Standard: today+1, +2, +3, +4 = -800
Heavy: today+1, +2, +3, +4 = -400
Alternatively you can maintain the simulative Forecast also via the Product View
(t-code /SAPAPO/RRP3)
Select the following Charts in the Product Planning Table
- Production View: Periodic
- Product View: Periodic
- Resource View: Periodic
Carrying Out Model Mix Planning
T-code /SAPAPO/SEQ2
On Screen Model-Mix-Planning Run enter the following data and Execute (F8)
Planning Version 000
Model Mix Procedure Package: ZDSC_MMP_001 (test 1)
ZDSC_MMP_002 (test 2)
ZDSC_MMP_003 (test 3)
ZDSC_MMP_004 (test 4)
Access by Line DSC_ASSEMBLY_LINE
Check Order on Product view (//RRP3) / Product Planning Table (//PPT1)
In MMP with Model Mix Procedure Package ZDSC_MMP_001 the PP/DS system generated a
planned order for each requirement. The quantity and availability date in the planned order matches exactly with the requirement quantity and requirement date.
In MMP with Model Mix Procedure Package ZDSC_MMP_002 and ZDSC_MMP_003 the PP/DS system generated a planned order for each requirement and scheduled the planned orders finitly into the buckets.
With Procedure Package ZDSC_MMP_004 also sequencing w lot size 1 is executed.
To provide a feasible plan from MMP to SEQ you should run a MMP that consider the available capacity (run finitly)
Run Interactive Sequencing
t-code /SAPAPO/SEQ1
On screen Sequencing enter the following data
Planning Version 000
Planning Horizon (the current week)
From 10.03.2022 00:00: 00 (today + 1 day)
To 17.03.2022 23:59:59
Access by Line DSC_ASSEMBLY_LINE
If MMP planned with LotSize > 1 execute Takt-based-Scheduling on screen Sequencing: Display
Using takt-based scheduling, you can split up all the orders with a lot size greater than one in the stipulated planning horizon into orders with the lot size one
Select the Orders in Dates/Shifts you want to schedule in sequence by PP/DS Sequencing and load them to "Dispatched orders horizon from-to"
Execute Slotting Heuristic or Z1DSC_QS_02 (or Z1DSC_QS_01)
(Assign Visual Profil created before)
Check result of Sequencing ( Finite scheduling & Block restrictions)
Find in the next picture the logic of order scheduling with takt based manufacturing-
A order lot of 10 EA needs 15 minutes do be produced on the line resource
10 minutes processing time per takt and 5 minutes offset
See the order dates detail
BADI and User Exit for Lean Automotive Scenario
The following enhancements via User Exit in SAP-ERP and BADI in DSC for S/4HANA are required for the Lean-Automotive Approach for MMP & SEQ
| Test Case Description | ||||
| System | UserExit in SAP-ERP System | Description | | |
| SAP-ERP | R/3 UserExit: EXIT_SAPLCORD_004 SAP Exit Name: CIFORD02 (Enhancement for Transferring Customer-Specific Order Fields) | IPPE planned orders (for products e.g DSC_FG_137_VAR_STD , DSC_FG_137_VAR_HVY), which were created in PP/DS in DSC, will be transferred back to SAP-ERP and reverse. The production version within the planned order should not be transferred back to PP/DS, because in PP/DS are already an iPPE production version exists. | ||
| Coding | *&---------------------------------------------------------------------* *& Include ZXCIFU07 *&---------------------------------------------------------------------** ERP UserExit: EXIT_SAPLCORD_004 * IPPE planned orders (for products e.g. DSC_FG… (your MatNr), * which were created in PP/DS, will be transfered back to ERP and reverse. * The production version within the planned order should not be transfered back to APO, * because in APO are already an iPPE production version exists.* DATA DECLARATION ********************************************************************** FIELD-SYMBOLS: <ls_ord> TYPE cif_apoord, <ls_out> TYPE cif_apoout. * PROGRAM ********************************************************************** LOOP AT it_ord ASSIGNING <ls_ord>. READ TABLE it_out ASSIGNING <ls_out> WITH KEY ordnr = <ls_ord>-ordnr. IF <ls_out>-material = 'DSC_FG_137_VAR_STD' OR <ls_out>-material = 'DSC_FG_137_VAR_HVY'.CLEAR <ls_ord>-prod_ver. ENDIF. ENDLOOP. UNASSIGN <ls_ord>. | |||
| System | BADI in PP/DS in DSC for SAP S/4HANA | Description | | |
| PP/DS on DSC for S/4HANA | BADI Name /SAPAPO/RRP_SRC_EXIT: Implementation Name (e.g.) ZDSC_LA_RRP_SRC_EXIT Method: - RRP_USEX_PLORD_CREATE (Planned Order About to be Created …) - RRP_USEX_COLLECT_EVENTS (Collect the events for the ord. transfer to ECC system - RRP_USEX_PUBLISH_EVENTS (Allow publication of orders to the ECC system) | Transfer of iPPE planned Orders from SAP-ERP to PP/DS through change of type of MRP explosion from ‘3’ to ’_’ only for products eg. DSC_FG_137_VAR_STD and DSC_FG_137_VAR_HVY… | ||
| Coding | METHOD /sapapo/if_ex_rrp_src_exit~rrp_usex_plord_create. * PP/DS Badi: ZDSC_LA_RRP_SRC_EXIT Method RRP_USEX_PLORD_CREATE, I * Transfer of iPPE planned Orders from ERP to PP/DS through change of type of MRP explosion from ‘3’ to ’_’ only for products * eg. DSC_FG_...(Your MatNr) DATA: lt_iv_au_pegid TYPE /sapapo/pegid_tab, ls_au_pegid TYPE /sapapo/cdps_pegid_str, lt_ev_matnr TYPE STANDARD TABLE OF /sapapo/matnr, ls_matnr_out TYPE /sapapo/matnr, ls_au_outputs TYPE /sapapo/om_io, l_au_active TYPE c, l_au_exit TYPE c, ls_au_inputs TYPE /sapapo/om_io. LOOP AT ct_outputs INTO ls_au_outputs. ls_au_pegid-pegid = ls_au_outputs-pegid. * determine material no CALL FUNCTION '/SAPAPO/DM_PEGID_GET_MATERIAL' EXPORTING iv_pegid = ls_au_pegid-pegid IMPORTING ev_matnr = ls_matnr_out EXCEPTIONS plobj_not_found = 1 model_not_found = 2 accid_not_found = 3 internal_error = 4. IF sy-subrc = 0. IF ls_matnr_out = 'DSC_FG_137_VAR_STD' OR ls_matnr_out = 'DSC_FG_137_VAR_HVY'. * only then switch on transfer of IPPE planned orders to ERP? IF cs_ordkey-trpid_type = '003'. "gc_trprodtype_ippe. cs_ordkey-oltptransfer = space. ELSE. * switch off transfer of IPPE planned orders to ERP? ENDIF. ENDIF. ENDIF. ENDLOOP. | |||
method /SAPAPO/IF_EX_RRP_SRC_EXIT~RRP_USEX_COLLECT_EVENTS. CV_COLLECT_EVENTS = 'X'. endmethod. | ||||
METHOD /sapapo/if_ex_rrp_src_exit~rrp_usex_publish_events. CV_PUBLISH_EVENTS = 'X'. ENDMETHOD. | ||||
I hope you enjoyed this blog and gained an overview about PP/DS on DSC Edition for S/4HANA , how the DSC Edition is integrated with a SAP-ERP system and got a high level overview on Model-Mix-Planning and Sequencing in PP/DS for SAP S/4HANA.
The use case in this article should have provided you a step-by-step guide how you can configure and run your own "lean-" MMP&SEQ planning scenario with iPPE.
18 Comments
| User | Count |
|---|---|
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
