RKT SCM 5.

0
PP/DS

Planning - Enhancements in
SCM 5.0

SAP AG 2005

Planning - Enhancements in SCM 5.0

Content:
- Withdrawal from Alternative Location
- CTP Enhancements
- Fix Pegging in ATP/CTP Process
- New Heuristic Enhancements
- Capacity Push Heuristic

SAP AG 2005

Unit Objectives

At the conclusion of this unit, you will be able to:

SAP AG 2005

Work with the process withdrawal from alternative location

Understand the CTP enhancements

Create fix pegging relationships in a ATP/CTP Process

Use the new heuristic enhancements

Execute the Capacity Push Heuristic

Withdrawal from alternative location

The Withdrawal from Alternative Location Process:

the component demand of an inhouse production is created in a location different from the
production location. Goods issue of the component is posted directly in this issuing location.
Withdrawal from alternative plant is also available in R/3. In R/3 the process is controlled
with a special procurement key. In R/3 customizing of the special procurement key 70 is an
example for withdrawal from alternative plant. Thats why the process is also known as the
SOBSL-70 process.
Withdrawal from Alternative Location can be combined with:
- phantom assemblies
- MRP areas (issuing plant)
- Co-Products
- subcontracting
Product substitution heuristic can be carried out in the issuing location only

SAP AG 2005

Withdrawal from alternative location

Business Process
Production plant
Step 1
Planned order
creation

Issuing location

Component demand
withdrawn from
other location

Step 2
Planning
components

Pegging

Planned receipt

Production plant

Issuing location

Step 3
Procurement
of components

Stock

Step 4
Withdraw
component

SAP AG 2005

Withdrawal from alternative location

Advantages of Withdrawal from Alternative Location versus stock transfer orders:

- Less administrative effort

No need to manage stock transfer orders. No need to post goods issue and goods receipt for the stock transfer order.

- Using stock transfer orders would require managing stock in two different locations.
Monitoring stock would be more difficult. Planning would be more difficult. Responsibility for stock would be obscured.

- In the stock transfer process the receiving location assumes responsibility for the product
at the time of goods issue in the delivering location.
This contradicts Kanban and JIT philosophy, where the supplier of a component should be responsible for the component stock.

SAP AG 2005

Withdrawal from alternative location

Limitations:
- not supported by iPPE, because iPPE does not support location dependent attributes
on BOM item level
- not supported by the PPM
- issuing location must be either a production plant or a distribution center.
- currently not supported by SNP
- PDS has to be regenerated after a change of the special procurement key in R/3
- heuristic for the supersession chain can only be executed in the issuing location

SAP AG 2005

Withdrawal from alternative location

R/3 Customizing:

SAP AG 2005

Withdrawal from alternative location

The special procurement key can be entered in BOM on item level or in the
components material master.

Special procurement key

SAP AG 2005

Withdrawal from alternative location

Phantom assemblies
Withdrawal in an alternative location can be mixed with phantom assemblies. If a
component is a phantom assembly in the issuing location, then the BOM of the
component is exploded in the issuing location. All components of the phantom
assembly are by default withdrawn from the issuing location unless the component of
the phantom assembly has got its own different issuing location

Plant

42

Issuing plant

Phantom

92000014
L20011210140

42

64637967
L22011220000

42

70075431
L22011230000

51

51

70075431
L22011230000

42

FIN__38LF
FIN__38LF

51

51

FIN__38LF
FIN__38LF

51

SAP AG 2005

Order components

DU

76587710
6963405300

5899

5899

76587710
6963405300

Withdrawal from alternative location

SAP AG 2005

Withdrawal from alternative location

SAP AG 2005

CTP Enhancements
In SCM 5.0 the change capabilities of CTP, based on fix pegging, was enhanced.
Multiple changes of already saved sales order items are vital elements of the business
process. To assure consistent planning behavior, the possibilities for changes are
restricted. For efficient changes of sales order items the planning algorithms of CTP
(and MATP) have to determine the receipt elements, which are assigned to the sales
order items. This is quite easy in a make-to-order scenario, where the receipts are
linked to the demands via accounting.
The assignment in a make-to-stock scenario can change during time. Often one
receipt is assigned to more than one demand. This makes it quite difficult to propagate
the changes properly through the supply chain. The re-create receipt elements
functionality was therefore restricted to make-to-order sales order items until SCM 4.1.
Now the functionality is provided for a make-to-stock scenario as well. This will lead to
better confirmation results.

SAP AG 2005

CTP Enhancements
Re-create Receipt Elements for fix pegged Receipts
This CTP functionality is an extended method of the product availability check. It will be
available, if in the ATP check instruction the re-create receipt elements indicator is
set. Additionally fix. Pegging in CTP/ATP in the PP/DS planning procedure is set. In
the case of moving requirement dates the system behavior is as follows :

1.

2.

a v a i la b i lit y c h e c k
f o r th e r e q u e s te d d a te :
n o a v a i la b i lit y
3.

n e w r e c e ip t c r e a te d b y C T P :
c o n f irm a tio n d a te
= re q u ire m e n ts d a te
4.

t
r e c h e c k o f th e s a le s o rd e r
ite m f o r a n e a r lie r d a te ,
ig n o r in g th e o ld r e c e ip t

SAP AG 2005

t
a n e w r e c e ip t is c r e a te d f o r
a n e a r li e r d a t e ( if p o s s ib le )
r e s u ltin g in a b e tte r c o n f ir m a tio n

CTP Enhancements
Re-create Receipt Elements for fix pegged Receipts
In the case of increasing the item quantity the system behaves in that way:

1.

2.

sa le s o rd e r ite m w h ic h
h a s b e en c rea ted w ith C T P

rec h ec k o f th e sa le s o rd e r
ite m w ith a h ig h e r q u a n tity

3.

4.

t
a v a ila b ility c h e c k c o n firm s
n o th in g a n d th e p r o d u c tio n
is c a lle d fo r th e to ta l q u a n tity

SAP AG 2005

t
fo r o n e sa le s o rd er item
o n ly o n e r ec e ip ts h a s b e en
c r ea te d

CTP Enhancements
Re-create Receipt Elements for fix pegged Receipts

SAP AG 2005

CTP Enhancements
Re-create Receipt Elements for fix pegged Receipts

SAP AG 2005

CTP Enhancements
Redistribution of Receipt Elements for Production Directly
The standard behavior of the CTP scenario is as follows. A newly created sales order
item is always confirmed against surpluses, which have been present before the
creation and/or receipts which have been created during the ATP transaction, although
from planning perspective it could be confirmed on the requirements date.

2.

1.

a n ew sa le s o rd e r ite m w ith a n
e a rlie r req u ire m e n ts d a te is
A T P -c h ec k ed

sa le s o rd er in th e fu tu re
w a s c o n firm e d a g a in st a n
e a rly re c e ip t
3.

4.

A T P c a n n o t c o n firm a n d C T P
is c a lled . U n fo rtu n a te ly th e
c re a ted re c e ip t is la te

SAP AG 2005

T h e n ew s a le s o rd er ite m is
c o n firm e d a g a in s t th e la te
rec e ip t

CTP Enhancements
Redistribution of Receipt Elements for Production Directly
To get the new behavior Production Directly must be set in the ATP check instruction
and Direct Production with Receipt Redistribution indicator is switched on in the
PP/DS planning procedure (also Fix Pegging in CTP/ATP)

1.

2.

a new sales order item is

created and checked via
net-requirements calculation

sales order in the future

was confirmed against an
early receipt
3.

4.

The receipt is created on the

date with the deficit which is
far in the future

SAP AG 2005

the sales order item can be

confirmed for the requirements
date, because there is no deficit

CTP Enhancements
Redistribution of Receipt Elements for Production Directly

SAP AG 2005

CTP Enhancements
Redistribution of Receipt Elements for Production Directly

SAP AG 2005

Fix pegging in ATP/CTP process

Fixed Pegging synchronization to ATP
Previously, you needed to carry out the heuristic SAP_PP_019 Create Fixed Pegging
Relationships in the ATP and CTP process several times a day after confirming the
sales order. This fixed the assignments between the requirement and receipt elements
created by the ATP or CTP check. The confirmation situation may have also changed
by the time the heuristic was carried out because the heuristic was normally executed
in a separate planning step.
As of Release SCM 5.0, the PP planning procedure was enhanced in such a way, that
the system now automatically creates fixed pegging relationships between customer
requirements and receipt elements in an ATP and CTP process, after you have saved
the confirmed sales order. This fixes the assignment that the ATP/CTP check created
at the finished product level. A confirmed sales order item is therefore fixed to the
relevant receipt element.
Now ATP confirmation and material flow determination in PP/DS is matching.

SAP AG 2005

Fix pegging in ATP/CTP process

CTP and multilevel planning actions due to PP planning procedure
SD

ATP

PP finished
good

PP component

Create
sales order
Run CTP
Create
order
Check PP planning
procedure fo
component
Check
availability /
Create order
for
component
Adjust order date
/Delete order
Check production
date /availability
Confirm sales order

SAP AG 2005

Fix pegging in ATP/CTP process

Lack of Consistency

ATP

SD

DS

PP

Create
sales order
ATP process

Run ATP
confirmation

CTP process

Run CTP

Run PP
fix pegging

Time shift
Different behaviour
Less usability

Adjust material flow

before PP (optional)

MRP process

Run production
planning
Adjust material flow
before DS (optional)

Adjust material flow

after DS (optional)

Run backorder
processing

SAP AG 2005

Adjust material flow

after BOP (optional)

OPT process

Run detailed
scheduling

Fix pegging in ATP/CTP process

Settings in Planning Procedure:

SAP AG 2005

Fix pegging in ATP/CTP process

Differences of the two possible ABAP Classes:

For the CTP process, the standard class /SAPAPO/CL_RRP_CTP is offered. This class
controls system behavior in the CTP check in connection with fixed pegging. As an
alternative to this ABAP class, you can use the standard class of the ATP process
/SAPAPO/CL_RRP_FIX, if you wish to have a different system behavior in the CTP
process.
The key difference between the two classes is, that in the case of the class
/SAPAPO/CL_RRP_CTP the system deletes the existing fixed pegging relationships
and reassigns the customer requirements to the receipt elements with each new invocation
of the CTP check for an already confirmed sales order (if you change the desired date/time
in the sales order for example). The system then creates new fixed pegging relationships to
fix the assignment.
In the case of the class /SAPAPO/CL_RRP_FIX, on the other hand, the fixed pegging
relationships are retained. A renewed check is always carried out against the fixed pegging.
The system merely adjusts the pegging quantities, if necessary, but leaves the fixed
pegging relationships unchanged.

SAP AG 2005

Fix pegging in ATP/CTP process

Settings in ATP-Check Mode:

SAP AG 2005

Fix pegging in ATP/CTP process

Settings in Global Parameters:

SAP AG 2005

Fix pegging in ATP/CTP process

Settings in Material Master (only necessary, if Global Settings for Fixed Peg. = 2):

SAP AG 2005

Fix pegging in ATP/CTP process

Limitations:

- only for ATP with production type characteristic evaluation (ATP check mode)
- only for sales documents like sales orders, quotations and request f. quotation
- ATP allocations cannot be supported
- fixed pegging creation within BOP is limited to PP/DS ATP

SAP AG 2005

Heuristic Enhancements
Overview
Order Re-explosion
Performed whenever changes in master data occur. Up to SCM 4.1 only for
complete pegging areas with loss of scheduling dates. Changes in the far future
could so affect current production plans
Now scheduling dates are kept, if possible
Re-explosion can now be performed for a selection of orders
Those Enhancements werde made for the heuristics SAP_PP001 - 005,
SAP_PP_013, SAP_PP_017, SAP_PP_SL001, SAP_PP_C001, SAP_PP_CTP
More selection fields and flexible safety time
Enhancements for the Bottom-up and Top-down Re-scheduling Heuristics
SAP_PP_009 and SAP_PP_010)
Creation/deletion and replacement of a fixing or a planning interval for a
resource
Enhancement for the Heuristic SAP_DS_03

New service heuristic for Multi-level Order Planning

to perform order and activity enabled heuristics in a reasonable sequence for a
selection of resources, orders or activities (SAP_PP_022)

SAP AG 2005

Heuristic Enhancements
Order Re-explosion

Behavior until SCM 4.1

Initial situation

G4

GW
G1

GZ
G3

GY
G2

GX

New behavior
G4
G1
G3
G2

SAP AG 2005

Heuristic Enhancements
Order Re-explosion

SAP AG 2005

Heuristic Enhancements
Rescheduling heuristics bottom-up and top-down (SAP_PP_009 and
SAP_PP_010)
These heuristics have been enhanced, so that you can interactively select only
one order or activity (and leave other orders of the pegging area untouched) for
rescheduling. This is a single-level process. If you want to execute multilevel
rescheduling for an entire order network, you must include the heuristic in the new
service heuristic SAP_PP_022.
In addition, both heuristics have been enhanced with the safety time field. You
can now choose whether or not you want to use the safety time of the product
master, or if you want to use the safety time only as long as it does not cause
scheduling violations.
Multilevel planning of individual orders (SAP_PP_022)
This new service heuristic enables multilevel planning of an order with
consideration of the low-level codes. From the detailed scheduling table, you can
interactively select resources and activities or directly select an order. The system
determines the dependent orders and executes multilevel planning. To do this, the
system works with the heuristic you have assigned to SAP_PP_022. The
rescheduling heuristics can be used bottom-up or top-down.

SAP AG 2005

Heuristic Enhancements
Re-scheduling with Flexible Safety Times
safety time

Respecting
full safety time
Selected order

Partially
respecting safety time
(no adjustment)

Not respecting
safety time

SAP AG 2005

Heuristic Enhancements
Re-scheduling with Flexible Safety Times

SAP AG 2005

Heuristic Enhancements
Heuristic SAP_DS_03
You can use this heuristic to create, delete, and replace a fixing or a planning
interval for a resource. This heuristic can be included in the production planning
run and can be accessed interactively from the DS planning board.
New functionalities of this heuristic:
- Deactivate sequence-dependent setup activities in the fixing interval - to
ensure a stable planning situation in the short-term horizon. The setup time
determined from the setup matrix is retained, when the operation sequence on a
resource changes due to confirmations.
- Fix operations
Operations in the fixing interval are fixed, meaning the operations are protected
from any potential changes made by detailed scheduling. The associated orders
are not date fixed or PP-fixed. This means that these orders can be changed at
any time by an MRP run. To protect these operations/orders from changes by
production planning, you can use the Fix Operations field in the heuristic
settings to define, that the operations in the selected fixing interval are date fixed
and PP-fixed.

SAP AG 2005

Capacity Push Heuristic

Task of the new Heuristic (SAP_PP_CDOC)
Typically a resource is not loaded 100% at a time. Often time-slots occur, which
should be filled with orders consuming the available capacity. This will lead to a
better resource utilization. The new Capacity-Push-Heuristic, which can be used
in the Detailed scheduling planning board and the Resource planning table, will
interactively fill available time-slots.
The Capacity-Push-Heuristic will create or change planned orders to fill a given
time-slot on a resource as good as possible.
The heuristic itself might act as possible template for other heuristics which deal
with capacity push.

SAP AG 2005

Capacity Push Heuristic

General remarks:
- planned orders can be created or changed
- production orders with the status not released can be changed
- production orders with the status released but not yet (partial) confirmed can
be changed
- orders can have more than one operation.
- The date of an order could vary from now to the end of the planning horizon by
taking account of validity horizons of the sources of supply. Heuristic settings shall
allow creating/elongating the order into the past.
- The planned operation of an order cannot spread over a time-slot, where other
operations are available unless there is enough capacity on a multi-resource.
- Authorizations for creating/changing of orders are considered.

SAP AG 2005

Capacity Push Heuristic

Limitations:
- Only one resource will be considered at a time
- Only time-continuous resources are considered; no bucket resources and thus
time-slots within a bucket
- designed for interactive use only
- not in every case the heuristic will fill the resource 100%. In some cases small
capacity gaps may still remain in the selected time period.
- You cannot use the heuristic, if a variable continuous consumption has been
maintained in the source of supply of the product for multi-resources.
- You cannot include the heuristic in a production planning run.
- The order quantity is adjusted by taking into account the capacity of the
selected resource. If an order reserves additional resources, the system will not
take the capacity of those resources into account when adjusting the quantity.

SAP AG 2005

Capacity Push Heuristic

1 Extend forward
2 Extend backward
3 Create new

SAP AG 2005

Capacity Push Heuristic

Operations on a ressource:
Initial situation

One new order

Serveral new orders

due to lot-size

Elongating to the right

Elongating to the left

SAP AG 2005

Capacity Push Heuristic

Special topics for multi-resources:
Adjusting an existing order will use the capacity-requirements of this order. If
there is enough capacity on the multi-resource over the given time-frame this
order will be placed parallel to existing orders. If the free capacity over the timeframe is not constant the elongation of the order will stop before filling the whole
time-frame at that point in time, where not enough capacity exist.
Creation of new orders, which positioned parallel to each other orders:
A new order can be placed parallel to some already existing orders if there is
enough capacity at the resource.
But no orders will be created which are placed parallel to just newly created
orders at the actual heuristic call.
If order-creation stops due to restrictions of the lot-size no new additional orders
will be created.

SAP AG 2005

Planning - Enhancements in SCM 5.0 - Unit Summary

You are now able to:

SAP AG 2005

Work with the process Withdrawal from Alternative Location

Understand the CTP Enhancements

Create Fix Pegging relationships in ATP/CTP Process

Use the New Heuristic Enhancements

Execute the Capacity Push Heuristic

Copyright 2005 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information
contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other
countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications
may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.

SAP AG 2005