Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Purpose

To guide users to create a simple example of Resource Networks in a Cross-Order context in PP/DS

Overview

This page will describe the master data settings needed in ECC as well as in APO in order to set up the scenario, along with practical examples on how resource networks are considered by the PP heuristics and the PP/DS Optimizer. In this example, the Resource Network will be created manually in APO side instead of being integrated from an ECC environment.

 

Example Creation

Background Information

    • The PP heuristics (like Planning of Standard Lots) do not consider Resource Networks during Source Determination, therefore it is possible that after heuristic run the created planned orders will not be compatible to the demands - they may not be pegged to each other. It is necessary to use PP/DS optimizer (or another DS function) to reschedule the activities into the right resources as per the Resource Network

       

    • The PP/DS Optimizer cannot change source of supply of orders. As a result, in Cross-Order scenario, instead of modeling multiple PDSs/PPMs (each with with a single primary mode), it is recommended to use a single PDS/PPM (for each Product) with alternative modes - the PP/DS Optimizer, then, can switch the activities from one mode to another during optimization. For the purpose of this example, then, Work Center classification is used to transfer alternative modes to APO


    • If orders already existed in the system before consideration of Resource Networks was enabled, these must be reexploded or replaced with new ones in order to get the resource network assignment


    • The Resource Network should be assigned at the Product Master to all production levels involved in the network, including the Finished Product. A component which is procured externally or produced in a Resource that is not part of the Resource Network does not need the Resource Network assigned at the Product Master


    • When the Resource Network is modelled, the links should be created from the Resource of the component material to the Resource of the higher level material, not the opposite

On ECC Side

Create a Characteristic in transaction CT04

  • The Auth. Group should be left empty, to prevent this characteristic from being transferred to APO

 

  • The work centers at a given production level will be classified with the same valuation

 

Create a Class in CL01

  • The Class should have Class Type 019 (Work Center Class) and no Organizational Area should be informed

 

  • The characteristic created in the previous step should be assigned to the class, and again the Organizational Area is not specified

 

Classify the Work Centers in CR02

  • In CR02, when changing the Work Center at the Basic Data tab, the Classification screen can be reached by opening menu Extras and choosing Classification

 

  • Work Center RN01 is an alternative to produce the Semi-Finished Product, thus it is classified with this valuation

 

  • Work Center RN02 is an alternative to produce the Semi-Finished Product, thus it is classified with this valuation

 

  • Work Center RN03 is an alternative to produce the Finished Product, thus it is classified with this valuation

 

  • Work Center RN04 is an alternative to produce the Finished Product, thus it is classified with this valuation

 

Classify the Operations in the Master Recipes (transaction C202)

  • The Operation Classification screen can be reached by double clicking the flag Classification at the Operations Overview in the Master Recipe

 

  • In the Master Recipe of the component, the operation is classified with valuation "Semi-Finished Product"

 

  • In the Master Recipe of the Finished Product, the operation is classified with valuation "FERT"

Send the Master Data to APO

  • Create and activate an integration model containing the materials, work centers, PDSs, and, if required, transactional data as well

On APO side

Check that the PDSs have Alternative Modes (/SAPAPO/CURTO_SIMU)

  • In the PDS of the Finished Product, there are 2 available modes (RN03 and RN04)

  • In the PDS of the component, there are 2 available modes (RN01 and RN02)

Create a Resource Network (/SAPAPO/RESNET)

  • In the Resource Network, the possible/acceptable links can be maintained
  • In example below, it is described that when the component is produced in Resource WRN01_0001_001, the Finished Product must be produced in WRN03_0001_001
  • Also, when the component is produced in Resource WRN02_0001_001, the Finished Product must be produced in WRN04_0001_001

Assign the Resource Network to the Product Master (/SAPAPO/MAT1)

  • In /SAPAPO/MAT1 for the Finished Product go to tab Demand, subtab Pegging and specify the Resource Network Name
  • Also, make sure field Resource Network Strategy has value "Consider Resource Network"

  • In /SAPAPO/MAT1 for the component go to tab Demand, subtab Pegging and specify the Resource Network Name
  • Also, make sure field Resource Network Strategy has value "Consider Resource Network"

Running Planning of Standard Lots heuristic for Finished Product and Component (/SAPAPO/RRP3)

  • At the Product View for the Finished Product, create some forecasts and execute a Product Heuristic (like SAP_PP_002)
  • In this case, mode with Resource WRN03_001_001 was chosen for all 3 planned orders

 

  • Double click one of the planned orders to go to the Order View and check that the Resource Network has been assigned to the order
  • Save

 

  • At the Product View for the component, execute the Product Heuristic. Check that mode WRN02_001_001 was chosen for all planned orders. 
  • This mode is incompatible with WRN03_001_001, thus there are no pegging relationships and the entire order quantity appears under Surplus/Shortage column at the Elements tab

 

  • Double click one of the planned orders and check that also at this level the Resource Network was assigned to the order

 

Running PP/DS Optimizer with Resource Network consideration (/SAPAPO/CDPS0)

  • Open the Detailed Scheduling Planning Board and include all 4 resources in the selection

 

  • Check that all activities for the component are scheduled in mode WRN02_001_001, while all activities for the finished product are scheduled in Resource WRN03_001_001

 

  • Click Optimize... button and confirm the popup

 

  • At the PP/DS Optimizer screen, click Settings button and go to tab Resource Processing
  • There, make sure field Consider Resource Networks has value "Always" and copy

 

  • Execute the optimization

 

  • Press Back button. Now the orders were scheduled in compatible modes. Save and adopt the results

 

  • Open the Product View for the component. Now column Surplus/Shortage shows value 0 for all elements, given they are compatible and fully pegged

 

Taking the Resource Network into Account during Rescheduling (/SAPAPO/CDPS0)

  • At the DSPB, click DS Strategy button. 
  • Activate the flag Consider Resource Network 
  • In tab Strategy Parameters f. Dependent Objects, set Fixed Pegging to "Always Consider" and Dynamic Pegging "Consider Within the Propagation Range" - in Cross-Order resource networks, if pegging is not considered, the Resource Network is also not taken into account even when Consider Resource Network flag is activated

 

  • Reschedule an activity into an alternative mode

 

  • Check that the mode of the pegged order is adjusted accordingly
  • In this case, an activity was moved from Resource WRN01_0001_001 to Resource WRN02_001_001. Consequently, the dynamically pegged order was moved from WRN03_001_001 to WRN04_001_001

Further Info

Using Resource Network Alerts (/SAPAPO/AMON1, /SAPAPO/CDPS0)

  • In transaction /SAPAPO/AMON1, create or change a PP/DS Alert Profile in order to activate the 2 available alert types

 

  • At the Product View for the component, go to Pegging Overview tab

 

  • Then, fix one of the the existing dynamic pegging relationships

 

  • Open the Detailed Scheduling Planning Board and find the fix pegged orders

 

  • Click on DS Strategy button. Then, go to tab Strategy Parameters f. Dependent Objects. Deactivate consideration of Fixed Pegging and Dynamic Pegging. This results in resource networks being ignored during scheduling

 

  • Drag&Drop the activity of the component into the alternative mode. Check that the mode of the finished product did not move. This is a violation of the Resource Network

 

  • Go to menu Extras -> Alerts and choose Display. The fixed pegged orders start to blink to inform the planner about the Resource Network violation

 

  • Drag&Drop the activity of a different order (dynamically pegged) into an alternative mode. Check that in this case they do not blink. The reason is that the dynamic pegging relationship was broken, such that there is no violation. Alerts only occur for fix pegged elements

 

  • Click on Alert Monitor button. The Alert Monitor popup appears and the 2 alerts can be seen in detail

Related Content

Related Documents

SAP Help Resource Network
SAP Help Production Scheduling for Resource Networks
SAP Help Process Industry-Specific Settings in the Optimization Profile
SAP Help Production Data Structure Generated from ERP Master Data
SAP Wiki Scenario - Alternative Modes with Work Center Configuration 

Related SAP Notes/KBAs

SAP KBA 1495983  No Resource Network Functionality Below SCM 7.0