APO Production Planning & Detailed Scheduling

Production Planning and
Detailed Scheduling (PP/DS)
Release 30A
ADDON.NDAPOPP
SAP Online Help 26.06.01
Copyright
©
Copyright 2000 SAP AG. All rights reserved.
No part of this brochure 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 , NT , EXCEL , Word and SQL Server are
registered trademarks of Microsoft Corporation.
® ® ® ® ® ® ®
IBM , DB2 , OS/2 , DB2/6000 , Parallel Sysplex , MVS/ESA , RS/6000 ,
® ® ® ® ®
AIX , S/390 , AS/400 , OS/390 , and OS/400 are registered trademarks of
IBM Corporation.
®
ORACLE is a registered trademark of ORACLE Corporation, California,
USA.
® ® TM
INFORMIX -OnLine for SAP and Informix Dynamic Server are registered
trademarks of Informix Software Incorporated.
® ® ® ®
UNIX , X/Open , OSF/1 , and Motif are registered trademarks of The Open
Group.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of

®
W3C , World Wide Web Consortium, Laboratory for Computer Science
NE43-358, Massachusetts Institute of Technology, 545 Technology Square,
Cambridge, MA 02139.
®
JAVA is a registered trademark of Sun Microsystems, Inc. , 901 San
Antonio Road, Palo Alto, CA 94303 USA.
®
JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used
under license for technology invented and implemented by Netscape.
SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com

Workplace, mySAP.com Business Scenarios, mySAP.com Application
Hosting, WebFlow, R/2, R/3, RIVA, ABAP, SAP Business Workflow, SAP
EarlyWatch, SAP ArchiveLink, BAPI, SAPPHIRE, Management Cockpit,
SEM, are trademarks or registered trademarks of SAP AG in Germany and in
several other countries all over the world. All other products mentioned are
trademarks or registered trademarks of their respective companies.
Production Planning and Detailed Scheduling (PP/DS) 30A 2

Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Tip

Production Planning and Detailed Scheduling (PP/DS) .......................................................... 15

PP/DS Business and Integration Scenarios......................................................................... 17
OLTP - PP/DS Scenario ................................................................................................... 18
Demand Planning and PP/DS Scenario ........................................................................... 27
Supply Network Planning and PP/DS Scenario ............................................................... 28
Planning Configurable Products with the PPM................................................................. 30
Characteristics Planning on iPPE Basis ........................................................................... 31
PP/DS Process..................................................................................................................... 32
Order .................................................................................................................................... 35
Basic Functions .................................................................................................................... 36
Pegging............................................................................................................................. 36
Dynamic Pegging .......................................................................................................... 38
Pegging Interval......................................................................................................... 39
Pegging Strategy ....................................................................................................... 42
Delivery Tolerance..................................................................................................... 44
Fixed Pegging ............................................................................................................... 44
Creating Fixed Pegging Relationships Manually....................................................... 45
Calculation of the actual pegging quantity................................................................. 46
Displaying Pegging Information .................................................................................... 47
Pegging Structure of an Order .................................................................................. 48
Considering Pegging Relationships .............................................................................. 48
Considering Fixed Pegging Relationships................................................................. 49
Considering Dynamic Pegging Relationships ........................................................... 50
Lot Size Calculation .......................................................................................................... 51
Fixed Lot Size ............................................................................................................... 52
Lot-for-Lot Order Quantity ............................................................................................. 53
Rounding ....................................................................................................................... 53
Scrap Calculation.............................................................................................................. 55
Calculation of Assembly Scrap ..................................................................................... 55
Calculation of Activity Scrap.......................................................................................... 56
Calculation of Days' Supply .............................................................................................. 57
Minimum Days' Supply.................................................................................................. 59
Firming Orders for Production Planning ........................................................................... 60
Detailed Scheduling.......................................................................................................... 62
Detailed Scheduling Activities ....................................................................................... 64
Calculation of the Capacity Requirements of an Activity .............................................. 66
Calculation of the Net Duration of an Activity............................................................ 67
Calculation of the Resource Consumption Values of an Activity .............................. 68
Capacity and Resource Consumption for PP/DS Resource Categories ............... 69

Splitting Operations ................................................................................................... 70

Selecting Objects to be Scheduled ............................................................................... 70
Scheduling Dependent Objects .................................................................................... 71
Mode Selection ............................................................................................................. 72
Mode.......................................................................................................................... 73
Mode Priority.............................................................................................................. 75
Linking of Modes ....................................................................................................... 75
Restrictions for automatic mode selection................................................................. 76
Adjusting Setup Time .................................................................................................... 77
Setup Matrix .............................................................................................................. 77
Synchronizing Activities on Multi-Resources ................................................................ 79
Controlling Detailed Scheduling.................................................................................... 80
Finite and Infinite Scheduling .................................................................................... 81
Detailed Scheduling Strategy .................................................................................... 82
Definition of Detailed Scheduling Strategies ......................................................... 83
General Settings .................................................................................................... 85
Specifying the Planning Period .......................................................................... 85
Specifying the Planning Direction ...................................................................... 86
Specifying the Maximum Scheduling Duration .................................................. 87
Considering Order Validity ................................................................................. 87
Determination of the Validity Period of an Order............................................ 87
Restrictions for automatic mode selection ......................................................... 88
Settings for Selected Operations ........................................................................... 88
Scheduling Mode................................................................................................ 89
Infinite Scheduling .......................................................................................... 89
Searching for a Slot ........................................................................................ 90
Adding an Operation at the End of the Schedule ........................................... 90
Inserting an Operation .................................................................................... 90
Inserting an Operation and Closing Gaps ...................................................... 91
Squeezing in an Operation ............................................................................. 92
Scheduling in Non-Working Times..................................................................... 92
Specifying the Scheduling Sequence................................................................. 94
Desired Scheduling Date ................................................................................... 94
Settings for Dependent Operations ....................................................................... 95
Scheduling Submode ......................................................................................... 95
Scheduling Dependent Operations According to the Scheduling Mode ........ 96
Considering Time Relationships between Operations ....................................... 97
Considering Pegging Relationships ................................................................... 98
Considering Fixed Pegging Relationships...................................................... 99
Considering Dynamic Pegging Relationships .............................................. 100

Scheduling with Time Buffers........................................................................... 102

Restrictions for automatic mode selection ....................................................... 103
Compact Scheduling ........................................................................................ 103
Compact Scheduling for Deallocated Operations ........................................ 104
Compact Scheduling for Deallocated Operations and Selected Orders ...... 105
Compact Scheduling for All Affected Orders................................................ 106
Scheduling Without Compact Scheduling .................................................... 108
Planning with Shelf Life Data.......................................................................................... 108
Maintenance of Master Data .............................................................................................. 110
Maintenance of PP/DS Settings ......................................................................................... 111
Transfer of Receipts and Requirements to PP/DS............................................................. 112
Conversion of SNP Orders into PP/DS Orders .............................................................. 114
Transfer of Sales Orders from R/3 to APO..................................................................... 116
Transfer of DP Demands to PP/DS ................................................................................ 117
Automated Production Planning and Optimization............................................................. 118
Automatic Planning......................................................................................................... 118
Automatic Planning Immediately................................................................................. 119
Automatic Planning in the Planning Run..................................................................... 121
Production Planning Run ................................................................................................ 122
Executing the Production Planning Run Online .......................................................... 125
Executing the Production Planning Run in the Background ....................................... 126
Model Mix Planning ........................................................................................................ 126
Processing Restrictions............................................................................................... 128
Restriction Groups................................................................................................... 129
Restrictions .............................................................................................................. 130
Restriction Categories and Attributes .................................................................. 131
Characteristic Values and Combinations of Characteristic Values ......................... 134
Restrictions on Products ...................................................................................... 135
Validity Periods........................................................................................................ 135
Creating the Restriction Group................................................................................ 136
Creating Restrictions ............................................................................................... 137
Working with Restrictions ........................................................................................ 138
Copying Restrictions of Other Lines and Planning Versions ............................... 139
Checking Restrictions.............................................................................................. 139
Examples for Restrictions........................................................................................ 140
Carrying Out Model Mix Planning ............................................................................... 143
Procedure ................................................................................................................ 144
Requirements Planning Procedure...................................................................... 144
Percentage Smoothing ........................................................................................ 145
Prioritized Equal Distribution................................................................................ 146

Genetic Algorithm ................................................................................................ 148

Planning Basis and Planning Result.................................................................... 149
Model Mix Planning Run.......................................................................................... 150
Access Model Mix Planning................................................................................. 152
Integrate as Heuristic in Production Planning Run .............................................. 153
Sequence Schedule ................................................................................................ 154
Access Sequence Schedule ................................................................................ 155
Displaying the Characteristics ............................................................................. 156
Characteristics-Based Selection ...................................................................... 156
Display the Restriction Violations ........................................................................ 157
Change Planning Manually.................................................................................. 158
Display in the Product Planning Table .................................................................... 159
Takt-Based Scheduling in Model Mix Planning ....................................................... 159
Production Planning Using the Rapid Planning Matrix (RPM) ....................................... 161
Rapid Planning Matrix (RPM)...................................................................................... 164
RPM Product ........................................................................................................... 166
Integration of the Rapid Planning Matrix in the Planning Process.............................. 166
Maintaining and Transferring Master Data.................................................................. 169
Master Data Maintenance in the DI System............................................................ 169
Create/Change iPPE Access Object ................................................................... 172
Transferring iPPE Data to the APO......................................................................... 172
Create an Integration Model for iPPE Data ......................................................... 174
Activate an Integration Model .............................................................................. 175
Transfer Changes in the Master Data to the APO............................................... 175
Check the Transfer Results ................................................................................. 176
Master Data Maintenance in the APO..................................................................... 177
Defining the Global Settings ................................................................................ 177
Change Product Master ....................................................................................... 178
Control Parameters for RPM Products ................................................................ 179
Execute Checks for RPM Products ..................................................................... 180
Planning Process with the Rapid Planning Matrix ...................................................... 181
Determining the Requirements Dates for Components .......................................... 183
Determining the Valid Line Balance..................................................................... 184
Takt-Based Scheduling........................................................................................ 184
Grouping Component Requirements....................................................................... 186
Determining the BOM Explosion Date..................................................................... 187
Comparing the Explosion Results........................................................................ 188
Planning ...................................................................................................................... 191
Execute a Model Mix Planning Run ........................................................................ 192
Update Matrices ...................................................................................................... 193

Update the Matrix in the Product View .................................................................... 194

Set Planning File Entries for RPM Products............................................................ 194
Parallel Processing During the Planning Matrix Run .............................................. 195
Execute Planning Run for APO Components.......................................................... 196
Evaluation of the Planning Results ............................................................................. 197
Displaying the Rapid Planning Matrix...................................................................... 197
Display Planning Matrix ....................................................................................... 199
Display Orders with Explosion Errors...................................................................... 200
Display Performance Data....................................................................................... 201
RPM Time Bucket ....................................................................................................... 201
Maintaining Time Bucket for Grouping Component Requirements......................... 202
Display the Resource Time Stream......................................................................... 203
Calculate the Time Bucket Profile for a Resource .................................................. 205
Display Time Bucket Profile from LiveCache .......................................................... 206
Reorganize Time Bucket Profile from LiveCache ................................................... 207
Heuristics ........................................................................................................................ 207
Heuristics for Production Planning.............................................................................. 209
Heuristics in Interactive Planning................................................................................ 211
Detailed Scheduling Heuristics ................................................................................... 213
Schedule Deallocated Operations........................................................................... 214
Lead Time Reduction .............................................................................................. 215
Backlog Rescheduling ............................................................................................. 215
Sequencing.............................................................................................................. 215
Manual Sequencing................................................................................................. 216
Merging orders on container resources................................................................... 216
Planning Heuristics in Repetitive Manufacturing (REM Heuristics) ............................ 217
Heuristic for Multi-Resource Planning (Even) ......................................................... 219
Heuristic for Multi-Resource Planning (Primary Resource)..................................... 219
Example for Multi-Resource Planning with Primary Resource ............................ 220
Example for the Planning Run with REM Heuristics ............................................... 222
Setting Up REM Heuristics ...................................................................................... 224
Create REM Heuristics with your Own Algorithm.................................................... 225
Creating Heuristics Using Your Own Algorithm .......................................................... 226
Optimization .................................................................................................................... 227
Objective Function ...................................................................................................... 229
Optimization of Setup Times and Setup Costs ....................................................... 230
Optimization of Mode Costs .................................................................................... 230
Optimization of Delay Costs .................................................................................... 231
Campaign Optimization ........................................................................................... 232
Optimization of Earliness Costs........................................................................... 233

Constraints for the Optimization.................................................................................. 234

Optimization Range..................................................................................................... 236
Fixing Activities, Operations and Orders..................................................................... 237
Calling Up the Optimization in the DS Planning Board............................................... 237
Optimization Run......................................................................................................... 238
Consistency Check.................................................................................................. 239
Process Pegging Relationships............................................................................... 239
Process Time Relationships .................................................................................... 241
Follow-Up Optimization ........................................................................................... 241
Multi-Agent Optimization ............................................................................................. 242
APO Optimization Extension Workbench (APX)......................................................... 243
Sequence Optimization ........................................................................................... 245
Cutting Optimization ................................................................................................ 250
Access to Data in SAP APO.................................................................................... 251
User-Specific Data ............................................................................................... 252
User-Specific Tables ........................................................................................ 252
Create and Maintain User-Specific Tables ...................................................... 253
Access User-Specific Tables ........................................................................... 253
Calling an External Optimizer .................................................................................. 256
External Procurement......................................................................................................... 256
Planning and Source Determination in External Procurement ....................................... 257
Scheduling in the Case of External Procurement Orders ........................................... 260
Checking the Earliest Availability Date.................................................................... 261
Scheduling Taking Resources into Account............................................................ 262
Converting Orders in APO .......................................................................................... 264
Executing Mass Conversions of Orders .................................................................. 266
Converting Individual Orders In Interactive Planning .............................................. 267
Scheduling Agreement Processing Using APO and an OLTP System .......................... 268
Scheduling Agreement................................................................................................ 272
Release Creation Profile.......................................................................................... 273
Creating Scheduling Agreement Releases ............................................................. 275
Displaying Scheduling Agreement Releases .......................................................... 277
Outputting Scheduling Agreement Releases .......................................................... 278
Master Data in Procurement........................................................................................... 281
External Procurement Relationship ............................................................................ 282
Processing an External Procurement Relationship .................................................... 285
Determining the Source of Supply During Automatic Planning ...................................... 288
Determining the Source of Supply in Interactive Planning.......................................... 290
Quota Arrangements................................................................................................... 292
Subcontracting................................................................................................................ 293

Subcontracting without a Source Location.................................................................. 296

Displaying and Checking the Planning Situation................................................................ 296
Product View................................................................................................................... 297
Order Processing View ................................................................................................... 299
Requirements View......................................................................................................... 301
Receipts View ................................................................................................................. 302
Pegging Structure of an Order........................................................................................ 303
Displaying Pegging Information...................................................................................... 303
Display of Alerts.............................................................................................................. 304
Interactive Planning............................................................................................................ 306
Maintenance of Receipts and Requirements (Orders) ................................................... 307
Product View ............................................................................................................... 308
Order Processing View ............................................................................................... 309
Requirements View ..................................................................................................... 311
Receipts View ............................................................................................................. 312
Displaying Pegging Information .................................................................................. 313
Maintaining Receipts................................................................................................... 314
Maintaining Requirements .......................................................................................... 316
Firming Orders for Production Planning...................................................................... 317
Creating Fixed Pegging Relationships Manually ........................................................ 319
Product Heuristic in Interactive Planning .................................................................... 321
Definition of Detailed Scheduling Strategies............................................................... 322
E-mail Connection....................................................................................................... 323
Product Planning Table .................................................................................................. 324
Planning Using the Product Planning Table ............................................................... 326
Configuration............................................................................................................... 327
Loading and Modifying Profiles from Customizing .................................................. 328
Accessing Charts..................................................................................................... 330
Setting the Column Width for Charts....................................................................... 331
Changing the Days’ Supply Unit.............................................................................. 331
Defining Periods (Buckets) ...................................................................................... 331
Define Time Zones .................................................................................................. 333
Navigation in the Product Planning Table................................................................... 334
Navigating in the Product Planning Table ............................................................... 334
Production Planning .................................................................................................... 336
Product View: Periodic ............................................................................................ 336
Defining the User Settings for the Periodic Product View ................................... 338
Defining the Settings in the Periodic Product View ............................................. 339
Product View: Individual Elements .......................................................................... 341
Defining Settings in the Product View: Individual Elements ................................ 342

Product View: Quantity Graphic .............................................................................. 343

Capacity Planning ....................................................................................................... 344
Resource View: Periodic ......................................................................................... 344
Defining User Settings for the Periodic Resource View ...................................... 345
Defining the Settings in the Periodic Resource View .......................................... 345
Production View: Periodic........................................................................................ 347
Defining User Settings for the Periodic Production View..................................... 348
Production View: Individual Elements ..................................................................... 349
Accessing Optimization in the Product Planning Table .............................................. 350
Calculating the Ranges of Coverage in the Product Planning Table.......................... 350
Displaying Continual Input/Output .............................................................................. 351
Access the Plan Monitor ............................................................................................. 355
Accessing the Production List ..................................................................................... 355
Examples .................................................................................................................... 357
REM Production Planner ......................................................................................... 357
Model Mix Production Planner ................................................................................ 358
MTS Production Planner ......................................................................................... 358
Procurement Planner............................................................................................... 358
Customer-Specific Enhancements.............................................................................. 359
Inserting Additional Charts ...................................................................................... 359
Inserting Additional Info Rows ................................................................................. 359
Scheduling with the Detailed Scheduling Planning Board.............................................. 360
Detailed Scheduling (DS) Planning Board .................................................................. 362
Chart ........................................................................................................................ 364
Legend ................................................................................................................. 366
Overview of Chart Settings .................................................................................. 366
Printing................................................................................................................. 368
Selection of Objects to be Displayed....................................................................... 368
Specifying the Order Category to be Displayed .................................................. 370
Work area ............................................................................................................ 371
Segmentation of the Display Period .................................................................... 373
Navigating................................................................................................................ 374
Setting the Visible Time Segment........................................................................ 374
Zooming the DS Planning Board ......................................................................... 374
Changing the Relative Size of the DS Planning Board Section .......................... 375
Sorting Rows........................................................................................................ 376
Searching for objects ........................................................................................... 376
Displaying and Changing Objects........................................................................ 377
Handling Objects ..................................................................................................... 377
Selecting Objects ................................................................................................. 378

Highlighting objects.............................................................................................. 379

Highlighting Objects with Alerts ........................................................................... 379
Hiding objects ...................................................................................................... 380
Changing the Object Display ............................................................................... 380
Exploding and Hiding Multiple Loading................................................................ 381
Hiding and displaying non-working times ............................................................ 382
Displaying Blocks................................................................................................. 382
Setting a Time Zone............................................................................................. 383
Transfer Data from Planning Board to Customer Exit APOCDPS0 ........................ 383
Calling Up the Detailed Scheduling Planning Board................................................... 383
Calling Up the DS Planning Board Directly ............................................................. 384
Calling Up the DS Planning Board in Order Processing ......................................... 385
Calling Up the DS Planning Board in the Product Planning Table.......................... 386
Editing the Simulation Version ................................................................................ 387
Profile Maintenance................................................................................................. 388
Profile for the DS Planning Board........................................................................ 389
Maintain profile in the current settings menu....................................................... 390
Displaying Current Profiles .................................................................................. 391
Check and Evaluate the Schedule.............................................................................. 391
Calling Up the Alert Monitor..................................................................................... 392
Highlighting Objects with Alerts ............................................................................... 393
Calling Up the Plan Monitor..................................................................................... 393
Displaying the Order List ......................................................................................... 394
Displaying Operation List......................................................................................... 394
Evaluations for Work-in-Process (WIP) Stock......................................................... 395
WIP Data for Operations with Continuous Input or Output.................................. 396
Displaying Work-in-Process Stock....................................................................... 397
Displaying Resource Load Curves .......................................................................... 398
Displaying the Resource Load List.......................................................................... 399
Displaying the Fill Level........................................................................................... 399
Displaying Product Stock ........................................................................................ 400
Displaying the Production Overview........................................................................ 401
Displaying Pegging Relationships Between Orders................................................ 401
Displaying Relationships Between Operations ....................................................... 402
Displaying Scheduling Log ...................................................................................... 403
Displaying and Changing Objects ........................................................................... 403
Solving Scheduling Problems ..................................................................................... 404
Manual Scheduling with Drag&Drop ....................................................................... 405
Scheduling or Rescheduling Operations and Orders Using Drag&Drop............. 406
Deallocating Operations and Orders ................................................................... 408

Loading Alternative Resources............................................................................ 410

Rescheduling Operations and Orders ..................................................................... 410
Deallocating Operations and Orders ....................................................................... 412
Detailed Scheduling Heuristics................................................................................ 413
Schedule Deallocated Operations ....................................................................... 414
Lead Time Reduction........................................................................................... 415
Backlog Rescheduling ......................................................................................... 415
Sequencing .......................................................................................................... 415
Manual Sequencing ............................................................................................. 416
Merging orders on container resources ............................................................... 416
Scheduling Operations in Non-Working Times ....................................................... 417
Fixing Operations, Orders and Time Intervals......................................................... 418
Definition of Detailed Scheduling Strategies ........................................................... 419
Displaying and Changing Objects ........................................................................... 421
Displaying Scheduling Log ...................................................................................... 421
Specifying the Maximum Scheduling Duration........................................................ 422
Update the Simulation Version ................................................................................... 422
Save the Simulation Version ....................................................................................... 423
Working with Production Campaigns.............................................................................. 424
Creating Production Campaigns ................................................................................. 425
Processing Production Campaigns............................................................................. 425
Push Production ............................................................................................................. 428
Working in the Push Production View......................................................................... 430
Calling Up Push Production ........................................................................................ 432
Using Push Production................................................................................................ 433
Manufacturing Execution.................................................................................................... 434
Integration of the Production Control System................................................................. 434
Transfer of Order Sequences ..................................................................................... 435
Test Transfer of Order Sequences.......................................................................... 436
Action Handler............................................................................................................. 437
Actions and Functions ............................................................................................. 439
Tracking................................................................................................................... 440
Access Tracking Information ............................................................................... 441
Changing Activities of an Order............................................................................... 442
Test the Action Handler ........................................................................................... 443
Transaction Codes and Other Technical Information ................................................. 444
Production Backflush ...................................................................................................... 445
Backflush Procedure ................................................................................................... 446
Backflush Process in Sales-Order-Related Production........................................... 449
Creating the Backflush ................................................................................................ 449

Define and Set Default Values for Profiles .............................................................. 450

Define Logical System............................................................................................. 451
Defining Reporting Point Types............................................................................... 452
Display Backflushes .................................................................................................... 453
Processing Errors........................................................................................................ 453
Postprocessing Backlogs In Individual Records ..................................................... 454
Processing the Backflushes ........................................................................................ 455
Product Cost in Sales-Order-Related Prod. with Reporting Points............................. 456
Goods Receipt Costing............................................................................................ 458
Work in Process in Sales-Order-Related Reporting Point Backflush...................... 459
Archiving Backflush Data from the Production Backflush........................................... 459
Archiving Backflush Data......................................................................................... 461
Deleting Backflush Data .......................................................................................... 462
Executing Postprocessing for Backflush Data......................................................... 462
Evaluating Backflush Data....................................................................................... 463
BAPIs for the Production Backflush ............................................................................ 463
Technical Appendix..................................................................................................... 464
Converting Orders in APO .............................................................................................. 467
Executing Mass Conversions of Orders...................................................................... 469
Converting Individual Orders In Interactive Planning.................................................. 470
Evaluations ......................................................................................................................... 471
Order and Resource Evaluations ................................................................................... 472
Evaluations for Work-in-Process (WIP) Stock ................................................................ 473
WIP Data for Operations with Continuous Input or Output ......................................... 474
Transfer of Orders to the OLTP System ............................................................................ 476
Exception Based Management: PP/DS ............................................................................. 477

Production Planning and Detailed Scheduling (PP/DS)

Purpose
The component Production Planning and Detailed Scheduling (PP/DS) enables you to plan
and optimize multi-site production while simultaneously taking into account product and
capacity availability. PP/DS is designed to plan critical products; for example, with long
replenishment lead times or that are produced on bottleneck resources.
With PP/DS you can create executable production plans and
• Reduce lead times
• Increase on-time delivery performance
• Increase throughput of products based on better resource coordination.
• Reduce inventory costs because the work in process inventory is reduced as a result of
better coordination of product release.
Integration
The data relevant for planning, such as master and transaction data, is provided by a
connected OLTP System. Products are planned in the APO System and the planning results
are then transferred to the OLTP System, where you perform execution functions.
Requirements data from long and medium-term planning can also be transferred to PP/DS
within APO from Demand Planning and Supply Network Planning.
The following diagram represents the integration between an OLTP system and the APO
system and its components:
Integration within APO and with an OLTP System
OLTP APO
Supply Chain Cockpit
Advanced
Advanced Forecasting
Forecasting and
and Demand
Demand Planning
Planning
Production
Production
Sales order Planning
Planning &&
Detailed
Detailed
Scheduling
Scheduling
Supply
Supply
Production
ATP
ATP Network
Network
Planning
Planning
Inventory
management
Deployment
Deployment
The following table shows how PP/DS is integrated with the OLTP System and other APO
components:
Integration with Other APO Components and an OLTP System

To Procedure Other Information

Set up master data Transfer the master data from The OLTP System provides
the OLTP System and PP/DS with master and
maintain the necessary data in transaction data. You control
the APO System [Page 18] which data is to be transferred
to and from the OLTP System
in the integration model
[External] of the core interface
[External]. For more
information, see Integration of
APO and R/3 [External].
Set up the Supply Chain Use the Supply Chain In the SCE, you assign the
Model [External] Engineer (SCE) [External] locations, products, resources
and production process
models (PPM) to a model. You
then add transportation lanes
[External] to link supply to
demand locations and to
allocate products to the
transportation lanes.
Make the unconstrained Release the demand plan to Requirements that fall within
forecast (from Demand Supply Network Planning. the production horizon and
Planning) available in PP/DS [External] thus the planning responsibility
[Page 27] of PP/DS, are transferred
directly to PP/DS.
Transfer the planning results Convert the orders that lie in You can also to convert
of Supply Network Planning to the production horizon into specific individual orders
PP/DS for more detailed PP/DS orders [Page 114]. [Page 114] that are outside the
planning [Page 28] production horizon.
Perform an ATP check using Create a sales order in the If the result of the ATP check
Global ATP and PP/DS connected OLTP System is to produce, Global ATP calls
[External] [Page 116] up PP/DS to determine the
availability date while taking
product availability and
capacity into account.
Display exceptional, Access the Alert Monitor You can define which types of
unexpected or critical [Page 304] alerts you would like the
situations in the PP/DS system to generate and
planning process display. [External]
Perform execution of orders Use the connected OLTP For example, confirmation,
[Page 18] System goods receipt.
Features
• Automatic Planning [Page 118]
You can define that the System is to plan products automatically in PP/DS when you
change orders or data relevant to planning in the APO System or the connected
OLTP System. This enables up-to-date planning data in both systems.
With automatic planning, the system checks the availability of resources and
components when orders are created. The result is feasible availability dates for the
product and its components.
• Automatic, multi-level transfer of changes to quantities and dates

Using pegging [Page 36], the APO system creates a relationship between the receipt
and requirements elements of a product within a location. The system generates a
pegging structure that is organized according to the BOM structures of all relevant
products. The dynamic pegging structure ensures that quantity or scheduling
changes are transferred to orders at lower levels of the BOM structure.
• Interactive Planning [Page 306]
You can use interactive planning for important products that you wish to plan
manually and to solve any planning problems that have arisen during automatic
planning. Interactive planning is supported by the following tools:
− Detailed scheduling planning board [Page 362]
In the DS Planning Board the planning situation and resource schedule are
displayed in Gantt charts. You use the detailed scheduling planning board to
reschedule orders or operations manually.
− Product planning table [Page 324]
You use the product planning table to plan the production quantities for products
and the schedule of the production lines.
− Optimization [Page 227]
Using the optimization tool, you can optimize the resource schedule according to
certain criteria, such as setup times and setup costs, to improve the planning
situation and solve particular detailed scheduling problems.
• Heuristics and Background Planning
− Heuristics [Page 207]
You use heuristics to solve specific planning tasks for selected objects
(depending on the focus of planning: products, operations, resources or line
networks) using a particular planning procedure algorithm. You can apply
heuristics both during interactive planning [Page 211] and during the production
planning run [Page 122].
− Production Planning Run [Page 122]
You use the production planning run to execute heuristics [Page 207], detailed
scheduling functions or optimization for a large number of objects online or as a
background job. During the production planning run, several heuristics or
functions can be executed one after another.
Constraints
The component Production Planning and Detailed Scheduling is a planning tool. Execution
functions, such as shop floor control with confirmation, purchasing and so on, must be
performed in an OLTP system.
PP/DS Business and Integration Scenarios

OLTP - PP/DS Scenario

Purpose
The component Production Planning and Detailed Scheduling (PP/DS) enables you to plan
multi-site production while taking into account product and capacity constraints with the goal
of reducing lead times and increasing due date performance. PP/DS is designed to plan
critical products, for example, with long replenishment lead times or that are produced on
bottleneck resources.
APO is a planning tool. Execution functions, such as confirmations, goods receipt,
purchasing, and so on, are performed in an OLTP system.
The OLTP system also provides the APO System with data relevant for planning (master data
and transaction data). Products are planned in the APO System and the planning results are
transferred back to the OLTP system. If necessary, planning is completed in the OLTP
system when, for example, not all products of a BOM structure are planned in APO.
Which Products Should You Plan in APO?
Type of Planning Recommended Possible in Not Not

in APO APO Recommended Possible in
in APO APO
Externally procured X
products with long
replenishment lead time
All in-house products X
produced on a bottleneck
resource
All products that were X
planned using MRP in a
standalone OLTP System
Products planned using X
reorder point planning
(non-critical products)
forecast-based planning
(non-critical products)
time-phased materials
planning (non-critical
products)
Kanban (non-critical
products)
We recommend planning critical products and critical components in APO and non-critical
products and components in the OLTP System. However, if you plan a component in APO,
you must also plan all components in the BOM path up to the BOM header product in APO. If
you plan a component in the OLTP System, you must also plan all sub-components in the
OLTP System.

Incorrect Correct
Key:
Planned in APO
Planned in R/3
Prerequisites
APO and R/3 System Prerequisites
For more information on system prerequisites, see the Checklist for Setting Up the System
Infrastructure [External].
R/3 Settings
• To exclude the products that are to be planned in APO from material requirements
planning in the R/3 System, you must define an appropriate MRP type. To do this,
proceed as follows in the R/3 System:
a. In Customizing for MRP under Master data → Check MRP types, define a new MRP
type by choosing New entries. In the MRP procedure field, enter the X indicator for
Without MRP, with BOM explosion.
b. Enter the new MRP type for these products in the MRP data of the R/3 material
master records.
• To ensure that customer requirements are created for materials that are not included in
planning in the R/3 System, you have to change the settings in Customizing for Sales and
Distribution. There are two possible options:
− In Customizing for Sales and Distribution, under Sales → Sales documents →
Schedule lines → Define schedule categories, set the schedule line category CN for
No mat. planning. Set the Req./Assembly indicator to ensure that requirements are
transferred.
The disadvantage of this option is that customer requirements are now created
for materials in all systems, not only for materials that are not planned in the R/3
System or the APO System.
− In Customizing for Sales and Distribution, under Sales → Sales documents →
Schedule lines → Assign schedule categories, you can define when which schedule
line category is to be used. This is dependent on the item category in the sales order
and the MRP type. You create a new entry in the schedule line assignment table for
the required item category and MRP type you have defined for products to be
planned in APO. You can thus use the schedule line category CP (stands for MRP) in
order to allow customer requirements to be created.
• A production process model (PPM) consists of a BOM and routing (in the case of process
industries, a material list and a recipe). You therefore need to specify which routing is to
be assigned to which BOM in the R/3 System to enable a PPM to be created by APO
when you transfer master data. You do this by defining a production version in the
material master records of the products produced in-house that are to be planned in APO
and entering the routing number. To do this proceed as follows:

In the R/3 material master, create a production version by choosing Production

versions on the MRP 4 tab. Enter the version number, description, and validity period
and then choose Details. In the Planning type field, enter the routing number in the
Group field and N for Routing in the Type field.
APO Core Interface in R/3

• You have performed an initial transfer of the master and transaction data to APO using an
integration model in the core interface. You must transfer the master data of products that
are to be planned in APO, and the master data of all their components. The data is
transferred to your active model 000 and your active planning version 000.
Customizing for APO

In Customizing for APO, choose Production Planning and Detailed Scheduling (PP/DS) →
Global Settings and make the following settings:
Global Parameters and Defaults for APO PP/DS
Customizing Use
Maintain Number Ranges for You use the number ranges to allow orders that are created in
Orders APO to be assigned an internal number.
Maintain Global Parameters You use strategy profiles to control detailed scheduling for:
and Defaults - Schedule
Orders: Strategy Profiles • Interactive planning (orders that are scheduled or
rescheduled in interactive planning)
• R/3 integration (orders that are transferred from the R/3
System to the APO System)
• Planning run (orders that are scheduled or rescheduled in the
planning run)
• Capable-to-Promise
• Conversion of SNP -> PP/DS (orders that are used in the
conversion of SNP orders to PP/DS orders)
• BAPI (orders that are transferred to the APO System via
BAPI)
Maintain Global Parameters You use the categories to display the appropriate description of
and Defaults: Categories for the receipts and requirements in the evaluation screens of
PP/DS Production Planning and Detailed Scheduling. You only need to
enter categories for non-R/3 OLTP Systems, as APO is
preconfigured for R/3.
You maintain the categories in Customizing by choosing Global
ATP Check → General Settings → Maintain Categories.
Explode BOM You specify whether the production process model (PPM) is to be
exploded during planning or whether the BOM and routing is to
Can be defined for each
be exploded in the R/3 System.
product in the product
master To allow for better system performance, we recommend
exploding the PPM in APO.
APO Master Data

• You have created a model in the Supply Chain Engineer.
• You have created a planning version for the model and you have set the PP/DS: Change
planning active indicator for the planning version.
• You have assigned the resources to the model in the Supply Chain Engineer.

• You have assigned the production process models to the model.

• You have maintained the transportation lanes between locations in the Supply Chain
Engineer to model the transfer and delivery of products.
• To allow the procurement option with the most favorable costs to be selected during
automatic planning:
− You have maintained the costs for products produced in-house in the production
process model.
− You have maintained the costs for the transportation lanes in the Supply Chain
Engineer (for products procured externally and stock transferred from other
locations).
• You have maintained the necessary APO product master data on the PP/DS tab.
Settings in APO Product Master
Setting Consequences
Automatic planning immediately If you select this indicator for a finished product and its
[Page 119] components, the system plans these products automatically.
Automatic planning in the If you select this indicator for a product, the system creates a
planning run [Page 121] planning file entry for the product every time a change
relevant to planning occurs. This product is then planned the
next time you execute a production planning run [Page 122]
in net change mode.
Manual planning with check If you select this indicator for a product, the system searches
for an existing suitable receipt element. If none are available,
you have to create an order manually to cover the
requirements. Alerts are created in the case of product
shortages.
Manual planning without check If you select this indicator for a product, the system does not
search for a suitable receipt element. The product is always
considered to be available. Alerts are created in the case of
product shortages.
In the Explosion field, set: If you do not enter a value, the default from Customizing is
used (Customizing for Supply Chain Planning, under
Explode production process
Maintain Global Parameters and Defaults). Ensure that you
model
set Explode production process model as the default.
You also can explode the BOM and routing in

the R/3 System. However, this is not
recommended since it affects system
performance.
Data Flow
Before you can start planning in APO, you must execute an initial data transfer from the R/3
System to the APO System.
• Transferring master/transaction data
The following data can be transferred from the OLTP system to APO:
Master Data Transferred from R/3 to APO
R/3 Master Data Transferred Master Data in APO

Material master records Product master records

Plants (storage locations, Locations
distribution centers)
Vendors Locations
Production process model The BOM and routing from the R/3 System are created as a
(BOM/material list, routing/recipe PPM in APO.
and production version)
Work centers The capacities of the work centers are created as resources
in APO.
Customers Locations
Scheduling agreements External procurement relationships
Contracts External procurement relationships
Purchasing info records External procurement relationships
Transaction Data Transferred from R/3 to APO
R/3 Transaction Data Transferred Transaction Data in APO

Sales orders Sales orders
Production/process orders Production/process orders
Manual reservations Manual reservations
Purchase requisitions/orders Purchase requisitions/orders
Planned orders Planned orders
Planned independent Planned independent requirements
requirements
Stocks Stocks
Classes and characteristics Classes and characteristics
Later, changes to data in the master or transaction data are filtered and routed
automatically through an active data channel, which uses ALE and BAPI technology.
2. Stock and requirements information is transferred automatically (via RFC).
An order created in the R/3 System is transferred automatically to APO.
Procurement, transport and planned orders that are created in APO are transferred
automatically to the OLTP system. Any changes made in the APO System are
transferred automatically to the OLTP system and vice versa.
Scenario
This scenario describes generic order processing in APO and OLTP without making reference
to the source of the requirements. The process described here only deals with products
produced in-house. For information on how externally procured products are planned in APO,
see Scheduling Agreement Processing Using APO and an OLTP System [Page 268] and
Planning and Source Determination for External Procurement [Page 257].
The processes involved for products produced in-house include:
• Automatic planning in APO
• Planning in the production planning run
• Completion of planning in OLTP for non-APO components

• Interactive planning in APO

• Execution in R/3
Process Flow
The graphic below depicts the process flow of an order in APO, starting from the entry of a
requirement in APO, through to the goods receipt in OLTP system.
Process Flow of an Order Produced In-House in APO and R/3
Plant
R/3
R/3 APO
Complete Automatic
Complete
dep.reqmts
Create
Createorders
orders Automaticplanning/
planning/
dep.reqmts background
backgroundplanning
planning
Change
Changedep.
dep. Change
Changeorders
orders
reqmts
reqmts Interactive
Interactiveplanning
planning
Planned
Plannedorder
orderconverted
converted
automatically: Set
Setconversion
conversionindicator
indicatorfor
automatically:System
Systemtransfers
transfers for
production production
productionorder
productionorder
orderback
backto
toAPO
APO order
Print
Printpull
pulllist
list
Reduce
Reducerequirements/
requirements/
Component
Componentwithdrawal component
withdrawal componentstock
stock
Confirmation Reduce
Reducequantities
quantities
Confirmation
Reduce
Reduceorder
orderreceipt,
receipt,
Create
Creategoods
goodsreceipt Increase
receipt Increasestock
stock
Automatic Planning in APO

There are two methods of automatic planning in PP/DS: Automatic planning immediately and
Automatic planning in the planning run:
• You use automatic planning immediately [Page 119] for multi-level planning of products
that use lot-for-lot order quantity or fixed lot-sizing procedures.
• You use automatic planning in a planning run [Page 121] to plan products using other lot-
sizing procedures that are available as heuristics, such as period lot-sizing or purchase
order optimization heuristics.
You can define how the product is to be planned in the PP/DS tab of the product master. Both
types of automatic planning are triggered when:
• New requirements are transferred to PP/DS
• Requirements are changed
• Stocks are moved
• Product master data is changed
• The production process model (PPM) is changed
• Other changes relevant to planning occur

Process for Automatic Planning Immediately

1. New or changed requirements must be covered. The APO System firstly attempts to
cover the requirements with existing stock or orders. If sufficient stock with appropriate
schedules is available, planning is complete. The APO System assigns the requirements
to the receipt elements using pegging [Page 36].
2. If there is not sufficient stock to cover the requirements for a product, APO creates
corresponding orders to cover these requirements. APO performs a net requirements
calculation to determine the total order quantity. The following are taken into account
during this calculation:
− Lot-size [Page 51]
− Scrap [Page 55]
− Rounding values [Page 53]
3. APO determines how the order is to be procured using the procurement type you defined
in the product master. The system creates planned orders or purchase requisitions
respectively depending on whether the product is produced in-house or procured
externally.
If you have defined several procurement options, APO selects the alternative with the
most favorable costs, provided that you have maintained the costs in the production
process model (for products produced in-house) or in the transportation lanes of the
Supply Chain Engineer (for products procured externally).
4. APO then schedules the order.
For external procurement, the planned delivery time of the product, which is defined
in the product master, is used.
If the stock is transferred from another location, the transport duration that is defined
in the transportation lanes in the Supply Chain Engineer is used.
For in-house production, APO explodes the PPM and performs Detailed Scheduling.
Scheduling is based on the operation durations defined in the production process
model; that is, the start and finish dates of the order are based on the start of the first
operation and the end of the last. If you have defined Finite Scheduling for resources,
capacity is also taken into account during this process. The exact procedure for
scheduling depends on the scheduling strategies [Page 82] you have maintained.
The requirement quantities as well as the availability dates and times have now been
determined automatically by APO. Automatic planning is now complete.
5. The planned orders created in APO are transferred to the OLTP system automatically.
The output of these orders is firmed, meaning that the order quantities are not changed
during automatic planning. Activities, however, may be changed. This type of firming
corresponds to order header firming in the R/3 System.
The input of an order (components) is firmed as soon as you make any changes
manually. The production process model (PPPM) is not re-exploded for the order
if the PPM changes. This type of firming only affects the components and
corresponds to firming the explosion in the R/3 System.
For detailed information on make-to-order production with R/3 and APO, see Availability
Check Calling PP/DS [External].
Automatic Planning in the Planning Run

You use automatic planning in the planning run to plan products using heuristics [Page 207]
that you have defined for each product. You are able to use your own heuristics or you can
use heuristics provided by SAP. A large variety of heuristics are available to plan products
that address particular planning problems, including various lot-sizing heuristics and purchase
order quantity optimization. When automatic planning is triggered, a planning file entry is

created for the products. These products are then planned in the next net change planning
run. An advantage of planning products in the production planning run [Page 122], as
opposed to automatically and immediately, is that, you can control when and how often
products are planned. You are therefore able to improve system performance by executing
planning runs at less busy times of the day.
You can plan products according to the heuristic defined in the product master by starting the
production planning run using one of the following heuristics:
• SAP_MRP_001: Product Planning (Comp. acc. Low Level Code)
• SAP_MRP_002: Product Planning (Plan Comp. Immediately)
For more information, see Heuristics

for production planning [Page
209] and Automatic planning in the planning run [Page 121].
Planning in the Production Planning Run
In addition to planning the products defined as being planned using automatic planning in the
planning run [Page 121], the production planning run [Page 122] can also be used to plan
manually planned products and to apply heuristics to products planned using automatic
planning immediately [Page 119]. Manually planned products are usually critical products that
require particular attention when planning. You can start the production planning run for a
selection of products and plan these products according to one or several heuristics.
Less critical products that are planned using automatic planning immediately can be
replanned using a heuristic in order to apply a particular lot-sizing heuristic. For example, you
use automatic planning immediately to carry out a multi-level availability check for products
and then apply a period lot-sizing heuristic to group the receipt elements into weekly lots.
The production planning run can also be used to apply other types of heuristics whose
planning focus is not on products, as in the case of the production planning heuristics [Page
209], but rather on resources, orders and line networks. Standard heuristics exist in the
following areas:
• Detailed scheduling [Page 413]
These heuristics are scheduling heuristics, whose planning focus is on resources and
operations. Examples of these heuristics include Reduce lead times and Resolve
backlog.
• Repetitive manufacturing [Page 217]
These heuristics generate planned orders to cover requirements taking into account
the resource capacity for each period. The focus of planning is on resources, line
networks and products.
• Model mix planning [Page 150]
This heuristic optimizes the sequence of configurable products while taking any
restrictions into account. The focus of planning is on resources and line networks.
Completion of Planning in OLTP for Non-APO Components

When a requirement is transferred from the R/3 System, only the products relevant to APO
are transferred from the R/3 System to APO. APO plans these products, which represent a
component list, for example, component list A. The orders for component list A are transferred
back to the R/3 System. The bill of material is re-exploded in the R/3 System, producing a
new component list, for example, component list B. A comparison of the two lists is performed
in the R/3 System:
Comparison of Component Lists in R/3 and APO
If component is: then:

in lists A and B List A is valid. The quantity and date determined by APO are used.

only in list B Planning of the component is completed in the R/3 System. The quantity is
determined during the BOM explosion and the date is determined from the
start of the first activity of the order.
only in list A This is not permitted. The complete bill of materials must be maintained in
the R/3 System.
The components that are to be planned in the R/3 System (only in component list B) are
planned during the next MRP run.
Interactive Planning in APO

In APO, you can then interactively plan products [Page 306] to improve the planning situation
and to plan any products that are defined as being planned manually in the product master.
The following tools are available to improve the planning situation:
• DS planning board [Page 360]
• Product planning table [Page 324]
• Heuristics [Page 207]
• Optimizer [Page 227]
To plan any products manually, you can create orders and change dates and quantities [Page
314] directly in APO.
Execution Functions in APO

The conversion of planned orders and purchase requisitions into production orders and
purchase orders respectively can now be triggered in the APO System directly. You do this by
setting a conversion indicator for the orders you wish to convert. The orders are then sent to
the connected OLTP System and are automatically converted. The converted orders are sent
back to the APO System with a changed ATP category, for example, Preq for purchase
requisition becomes PchOrd for purchase order.
You can convert planned orders and purchase requisitions either:
• Individually in interactive planning [Page 470]
• By executing mass conversion [Page 469] using selection criteria.
Execution Functions in R/3

The following execution functions are performed in the R/3 System; the table shows how the
events are registered in the APO System:
Interaction between R/3 and APO during Execution
Execution in R/3 What happens in R/3? What happens in APO?

ATP Check The ATP-check triggered by The ATP-check triggered by the
the conversion is carried out conversion is carried out in APO.
in APO.
Scheduling to Scheduling is performed to The dates determined during
determine costs determine costs. This Detailed Scheduling in APO are
(Controlling) information is only required not changed.
by Controlling. The dates
determined here are not used
for production planning.
Print pull list You print the pull list in the
R/3 System.
Withdraw The requirements and The requirements and
component stock are component stock are reduced in

components reduced. the APO System synchronously.

Confirmation Quantities are reduced. When Quantities are reduced and the
you partially confirm operations receive the same
quantities, the operation is dates as in the R/3 System
moved to the confirmed start synchronously.
date and keeps its original
Completion confirmation or final
duration.
delivery leads to reduction of the
When you confirm completion open quantity of the
of an operation, the operation corresponding order in APO to
receives both the confirmed zero. The order is not longer
start and finish date. displayed in the product view.
Post goods receipt The order for the receipt is The order for the receipt is
reduced and the stock is reduced and the stock is
increased. increased in APO synchronously.
Demand Planning and PP/DS Scenario

Purpose
You use APO Demand Planning (DP) [External] to create a forecast of market demand for
your company's products. This component allows you to take into consideration the many
different causal factors that affect demand. The result of APO Demand Planning is the
demand plan.
Using the DP library of statistical forecasting and advanced macro techniques, you can create
forecasts based on demand history as well as any number of causal factors, perform
predefined and self-defined tests on forecast models and forecast results, and adopt a
consensus-based approach to reconcile the demand plans of different departments.
The long-term planning results (demand plan) of Demand Planning are transferred to Supply
Network Planning [External] and/or Production Planning and Detailed Scheduling so that the
demand can be covered by stock and production orders. Demands may initially be transferred
to Supply Network Planning for medium-term planning and then later transferred to PP/DS for
more detailed, short-term planning, or they may be transferred directly to PP/DS (where they
are referred to as "requirements").
Prerequisites
• See Release of the Demand Plan to SNP [External].
• On the Model/Planning Version Management: Change Planning Data screen, you have
maintained the production horizon for your planning version. You can also maintain the
production horizon on the SNP 2 tab of the product master. The production horizon
defined in the product master has priority over the horizon defined in Customizing.

• You are using the same planning version for Supply Network Planning and Production
Planning and Detailed Scheduling. You have set the PP/DS: Change planning active
indicator and the SNP: Change planning active indicator for the planning version.
Process Flow
1. You create a demand plan in Demand Planning. For more information, see Demand
Planning Process [External].
2. When you are satisfied with the demand plan, you release it to Supply Network Planning
[External]. During this process, demands outside of the defined production horizon are
transferred to Supply Network Planning, whereas demands that are within the production
horizon are transferred to PP/DS. You can either:
− Release the demand plan with mass processing [External] or
− Release the demand plan online [External]
Make sure that you enter an SNP version that is also used for PP/DS. To enable
demands to be transferred to PP/DS, you must consider the length of the
production horizon when defining the planning horizon of the demands to be
transferred.
3. The system copies the demands from the DP version to the SNP version you have
entered and saves them in the liveCache. If the demands are outside of the production
horizon, the system saves them as SNP orders, and if they are within the production
horizon, as PP/DS orders.
4. If you have defined that the products are to be planned automatically [Page 118] on the
PP/DS tab of the product master, the system automatically assigns existing receipt
elements to the demands (requirements) in PP/DS.
5. If no suitable receipt elements are available, the system automatically creates a receipt
element to cover the demands. If you have defined manual planning for the product, an
alert will inform you of a product shortage. You the create a receipt for the product
manually. If you are also using Supply Network Planning, you create orders to cover
product requirements medium-term in Supply Network Planning. As soon as the orders
reach the short-term planning horizon defined by the production horizon, you convert
them to PP/DS orders [Page 114]. For more information on the integration between
Supply Network Planning and PP/DS, see Supply Network Planning and PP/DS Scenario
[Page 28].
Supply Network Planning and PP/DS Scenario

Purpose
Supply Network Planning is used for long to medium-term planning. One of the main
advantages of Supply Network Planning is sourcing, that is, determining where which product
will be procured and how. Functions, such as, deployment and transport load building are
available to optimize sourcing. Supply Network Planning uses bucket capacity when planning
products, which means the finest level at which you can plan is on a daily basis. It is therefore
not able to take sequence constraints into account during planning. In order to be able to

schedule orders precisely (in hours/minutes/seconds) and to take sequence constraints into
account, orders must be planned using Production Planning and Detailed Scheduling
(PP/DS).
PP/DS is used for short-term planning. You specify this short-term planning horizon by
defining a production horizon. The production horizon is used to separate the planning
responsibilities between Supply Network Planning (used outside the production horizon) and
PP/DS (used inside the production horizon). More detailed resources and production process
models enable a finer level of planning. By converting the orders from Supply Network
Planning to PP/DS, you achieve the following.
• The operations are brought into the correct sequence.
• The exact time of production is determined.
• Any missing components and operations are added (that is, components or operations
that are not included in the production process model used by Supply Network Planning
but are included in the more detailed PPM used by PP/DS).
As soon as at least one activity of an order in Supply Network Planning falls in the production
horizon, it will no longer be planned by Supply Network Planning. You convert the orders that
are in the production horizon into PP/DS orders. The converted orders are still visible for the
supply network planner as aggregated demand but are treated as firmed production and
cannot be changed by the supply network planner. During automatic planning, the system
only creates receipt elements to cover requirements that lie within the production horizon. You
can, however, manually create orders outside the production horizon. These orders are
firmed in Supply Network Planning and can only be changed in PP/DS.
Interaction Between Supply Network Planning and PP/DS
SNP
create
production horizon
100 Scheduling according

to the PPM for SNP
today
production horizon
100
today
delete
PP/DS
production horizon
100 Scheduling according

to the PPM for PP/DS
today
create
PP/DS again
Visibility of Planning for Both Supply Network Planner and PP/DS Planner
Supply Network Planning orders and PP/DS orders of the same planning version load the
same resources. It is therefore important that the load of a resource is visible to both the
supply network planner and the PP/DS planner. It is possible to define resources that allow a
bucket approach and a detailed approach, which enables you to use the same resource for

Supply Network Planning and PP/DS. If PP/DS creates orders outside the production horizon,
the supply network planner can see the resource load as a bucket requirement. There are two
forms of mixed resources [External]: the single mixed resource and the multi-mixed
resource. These correspond to the single-activity resource and the multi-activity resource
respectively. Both forms of the mixed resource calculate the bucket capacity from the
resource capacity.
As neither setup nor sequence constraints are taken into account in Supply Network
Planning, the theoretically available bucket capacity can be reduced using a loss factor.
Both the PPM for Supply Network Planning and the PPM for PP/DS can use the single-mixed
or multi-mixed resource. You can assign a PP/DS PPM to a PPM used in Supply Network
Planning to ensure that the correct PPM is used in PP/DS when the orders are converted and
re-created.
Prerequisites
See Conversion of SNP Orders into PP/DS Orders [Page 114].
Process Flow
1. Requirements that are outside the production horizon are transferred from Demand
Planning to Supply Network Planning.
If the requirements lie in the defined production horizon, they are transferred
directly to PP/DS when you release the demand plan to Supply Network
Planning. For more information, see Transfer of DP Demands to PP/DS [Page
117].
2. You plan the products in Supply Network Planning. You can use the following functions:
− Planning run [External]
− Capable-to-match [External]
− Supply network optimization [External]
− Deployment [External]
− [External]Transport load building [External]
− Interactive planning [External]
3. Once the orders fall into the short-term planning period, defined by the production
horizon, you convert them into PP/DS orders.
For more information, see Conversion of SNP Orders into PP/DS Orders [Page 114].
Planning Configurable Products with the PPM

You use a production process model [External] (PPM) together with characteristics-
dependent plannin [External]g to reduce the amount of master data [External] by collecting
similar objects in one set of master data. The PPM stores characteristics-dependent
production plan references for similar products (product family) with different qualities and
characteristic value assignments [External]. This gives you a non-specific product, which
means that you only need to maintain one PPM for several similar products instead of one for
each individual product, which significantly reduces maintenance effort.
You use characteristics [External] to describe a product in greater detail, in other words, you
can use characteristics to select a PPM. Based on the appropriate PPM, you then generate a
planned order [External] with a single product number for a specific master product.
Depending on the assigned characteristic propagation [External], you can trigger production
for a master product based on certain characteristics.

You set characteristic propagation in order to define how characteristic value assignments
should be distributed within the PPM. Characteristics are used first of all for configuration
purposes, then for calculating planning parameters, for performing block planning [External],
and finally, for performing pegging [External].
Characteristic values are propagated when you explode a PPM. During the PPM explosion,
the system propagates characteristic values from the master product to the activities
[External] and dependent components of the resulting order. User-specific functions are also
available if you want to perform more complex calculations.
Production Process Model

C
PPM is a combination
of routing and BOM
C
C Characteristics
Input activity
Output activity
Input/Output activity
Activity without input

or output
Characteristics Planning on iPPE Basis

Purpose
You use the classical R/3 characteristics and the integrated product and process engineering
(iPPE) to represent the master data, if you want to plan products with many variants. Here,
orders with small lot sizes are predominant.
In characteristics planning, not only individual characteristics and characteristic values are
taken into account, but combinations of characteristics in the product, which were regularly
observed in the past.
Implementation Considerations
To guarantee a correct transfer and maintenance of the R/3 classes and characteristics in
APO, you must set the option Determine class system in Customizing for APO to IBase and
R/3 characteristics.
You find this work step in the SAP Reference IMG under Advanced Planner and Optimizer →
Basic Settings → Define class system.
Only when this setting has been made are the R/3 classes and characteristics shown in the
APO menu under Master data.
Integration
The characteristics planning is integrated in Demand Planning.

Features
Within preplanning it is necessary to create a requirements forecast using detailed
information, rather than merely individual characteristic values. There are often dependencies
between different characteristics and characteristic values, which are important for future
planning.
Within characteristic planning you can define combinations of characteristics for the products
in planning tables. The information from the planning tables, together with the object
dependencies for the component variants, serves to determine the forecast requirements.
To carry out the characteristics planning in APO, the configurable product is assigned a
forecast profile. In the profile, all characteristics are defined that are relevant for planning.
If the production heuristic is started in production planning (demand planning), the system
triggers the explosion of the iPPE and the requirements are determined.
The results in characteristics planning are then transferred to Demand Planning.
The component requirements are then transmitted to the current planning version for
assembly/component planning requirements. When sales orders are received, production
orders are created and exploded. The dependent requirements from the production orders
take into account the planned assembly and component requirements.
Constraints
You create and maintain the classes, characteristics and the iPPE structures in the DI
System. The initial distribution of the data and the subsequent changes are transferred to the
APO System via the CIF interface.
PP/DS Process
Purpose
This process describes how you use the component Production Planning and Detailed
Scheduling.
Prerequisites
• For the integration between the APO System and an OLTP system:
− In the OLTP system, you must have set up an interface to the APO System via which
the data is to be transferred:
If you have a R/3 System as an OLTP system, to do this you have to generate
[External] and activate [External] an integration model in the R/3 System.
− In APO, you must have maintained a business system group.
For more information, see Integration of APO and R/3 [External]. In this
documentation, note the document Checklist for Setting Up the System Infrastructure
[External].
• If you want to perform integrated long, medium and short-term planning in APO, you have
to use the components Demand Planning [External] and/or Supply Network Planning
[External] in addition to PP/DS.
Process Flow
The process flow for planning with PP/DS is illustrated in the following diagram.

Planning Process for Production Planning and Detailed Scheduling
Maintain
Maintainmaster
masterdata
data
Maintain
MaintainPP/DS
PP/DS
settings
settings
Transfer
Transferorders,
orders,
requirements
requirementstoto
PP/DS
PP/DS
OLTP→
OLTP →PP/DS
PP/DS
DP→
DP →PP/DS
PP/DS
SNP→
SNP →PP/DS
PP/DS
Execution Automatic
Automaticplanning
planning
Execution Production
(conversion, ProductionPlanning
PlanningRun
Run
(conversion,confirmation,
confirmation, Model-Mix
backflush...) Simulation
Simulation Model-MixPlanning
Planning
backflush...) Multi-level
Multi-levelATP
ATPCheck
Check
Transfer Management
Management by
by
Transferreceipt
receiptelements
elements Display
and exception
exception Displayand
andevaluate
evaluate
andorders
ordersto
tothe
theOLTP
OLTP planning
system planningsituation
situation
system
Interactive
Interactiveplanning
planning
Create,
Create,change
changeorders
orders
Create,
Create,change
changerequirements
requirements
Reschedule
Rescheduleorder
orderininthe
theplanning
planningboard
board
Use
Useproduct
productplanning
planningtable
table
Optimize
Optimizeschedule
schedule
Use
Usepush
pushproduktion
produktion
1. You maintain the master data. [Page 110]

2. You maintain the settings for interactive planning with PP/DS. [Page 111]
3. You transfer requirements and orders from the OLTP System, from Demand Planning or
from Supply Network Planning [Page 112].
4. Planning is performed.
− To cover the requirements of automatically planned products, the system performs
planning automatically [Page 118]. There are two types of automatic planning in
PP/DS:
• Automatic planning immediately: [Page 119] You use this type of planning for
multilevel planning of products with exact or fixed lot sizes. Planning is triggered
as soon as a change relevant to planning occurs.
• Automatic planning in the planning run [Page 121]: You use Automatic planning
in the planning run to plan products using other lot-sizing procedures that are
available as heuristics [Page 207], such as period lot-sizing or purchase order
optimization heuristics. When changes relevant to planning occur, a planning file
entry is created. These products are then planned during the next net change

production planning run using the heuristic defined for the product in the Product
Master.
− During planning, the system creates and schedules [Page 62] the required receipt
(planned orders for in-house production, purchase requisitions or transport orders for
external procurement).
− To cover the requirements of very important, manually planned products, you plan
interactively [Page 306], that is, you manually create receipt elements.
5. You perform background planning [Page 122]:
− To plan less important or less problematic products, or to solve specific planning
problems using heuristics [Page 207], you can perform a production planning run
[Page 122] as a background job.
− The production planning run can also be used to apply other types of heuristics
whose planning focus is not on products, as in the case of the production planning
heuristics [Page 209], but rather on resources, orders and line networks. For
example, you can reorganize the resource schedule according to certain criteria (for
example, sequence) using detailed scheduling heuristics [Page 413] or optimization.
6. You display and check the planning situation [Page 296], using, for example the Alert
Monitor [External] or the Plan Monitor [External]. You check for any alert situations and
deal with them using interactive planning.
7. You plan interactively [Page 306]
− To plan manually planned products
− To solve planning or scheduling problems or to optimize the schedule.
To do this you use, for example:
− Heuristics [Page 207]
− Detailed scheduling planning board [Page 360]
− Push production [Page 428]
8. The receipt elements that were created or changed are automatically transferred to the
OLTP system [Page 476].
If you do not plan all products of a BOM structure in APO, you must complete
planning in the OLTP System.
9. You perform the execution in the OLTP-System, for example:
− Confirmation
− Posting goods receipt/issue
For more information, see:

• OLTP-PP/DS Scenario [Page 18]
• Demand Planning and PP/DS Scenario [Page 27]
• Supply Network Planning and PP/DS Scenario [Page 28]
• Global ATP Check [External]

Order
Definition
Object that defines
• Which products are required or staged and when and where this occurs
• Which operation may be required for this and which resources are used
In the SAP Advanced Planner and Optimizer (SAP APO), orders represent requirements
elements, receipt elements, and stock elements such as the following objects:
• Sales orders
• Planned independent requirements
• Planned orders
• Production orders
• Purchase requisitions
• Purchase orders
• Transport orders
• Scheduling agreements
• Reservations
• Stock
Use
Sales orders and stocks are transferred from an OLTP system to the APO System. You
cannot change these objects in the APO System. As a planning system, APO only generates
orders of the type APO planned order, which are, for example, planned orders for in-house
production or purchase requisitions for external procurement. You can also create and
change APO planned orders in the APO System manually. In addition, you can change
production orders and purchase requisitions that have been transferred from the OLTP
system.
Structure
An order may consist of the following elements:
Order element Description
Output product (product receipt) The product that the order stages.
An order can have several product receipts, such as:
• An in-house production order for the manufacture of co-
products
• A purchase order or a scheduling agreement with
several schedule lines, whereby each schedule line has
one product receipt

Input product (product The product that the order requires, such as a component
requirement) for producing the order product
An order can have several product requirements, such as:
• An in-house production order that requires several
components (dependent requirements) to product the
output product
• A sales order with several schedule lines, whereby each
schedule line has one product receipt
Operations [External] and Operations for staging the output products
activities [External]
The operations are executed at resources. The input and
output products are assigned to the activities of the order.
An order does not usually include all elements. A sales order, for example, only has input
products but no activities and no output products. A planned order for in-house production, on
the other hand, includes all elements. To generate the output product, the order requires
components that are processed, for example, in several activities at different resources.
Integration
The APO System is a planning system. Orders are executed in an OLTP system that is linked
to the APO System. The planned orders and purchase requisitions created in the APO
System are transferred to the R/3 System. Likewise, production orders, purchase orders, and
reservations are transferred from the R/3 System to APO. Any changes made to the orders
are transferred from APO to the R/3 System and vice versa. For more information, see OLTP-
PP/DS Scenario [Page 18].
Basic Functions
Use
The System uses the following functions during planning:
• Pegging [Page 36]
• Scrap Calculation [Page 55]
• Lot Size Calculation [Page 51]
• Days' Supply Calculation [Page 57]
Pegging
Use
Pegging is used during planning to assign product receipts, which should cover the
requirement, to a product requirement. Pegging links the requirements elements and receipt
elements [External] through all BOM levels, that is, it organizes the material flow, from the

procurement of components and raw materials to delivery of a sales order, for example.
Orders that are linked together, and their pegging relationships, form a Pegging Structure
[External]. The graphic below gives an example of a pegging structure. The arrows represent
the material flow, that is, the pegging relationships.
Sales order
10 20 10 40 60 (-10)
10 20 10 40 50
Shortage
30 100
Stock transfer order

30 100
Surplus
30 20 50 30
50 50 50 (+20)
Production order
50 50 50
50 30 20 50
80 80 (+10)
Purchase order
A production order, which requires a specific component can, for example, be pegged to a
purchase requisition for the component (external procurement) or to a production order for the
component (in-house production). With an in-house production order, the component is the
output product of a specific activity. The availability date of the component is determined by
the activity date. Thus, the activity dates are also relevant for a pegging relationship to an in-
house production order.
The following pegging procedures are available:
• Dynamic Pegging [Page 38] is carried out automatically by the system when planning, if
the requirements or receipts situation changes. With dynamic pegging, the system
deletes existing pegging relationships and creates new ones. Thus, with dynamic
pegging, the assignment of a receipt element to a requirement element is generally not
retained for long if the planning changes.
• Fixed Pegging [Page 44] is used if you wish to fix the assignment of a receipt element to
a requirements element and if the system should not change this assignment during
automatic planning. Fixed pegging relationships are retained during planning and can
only be deleted manually.
Features
• Pegging Area
Pegging can only link requirements elements and receipt elements within a pegging
area, that is, requirements elements and receipt elements must
− consume or deliver the same product (with the same characteristics)
− be in the same location

− be planned in the same planning version

− have the same account assignment
− be in the same planning section
• Alerts
In connection with pegging, quantity problems (uncovered requirements, surplus
receipts) and date problems (receipts too early or too late) may occur during
planning. The system can create alerts for these problems and display the alerts in
the planning interface or in the Alert Monitor. For more information, see Display of
Alerts [Page 304].
• Displaying Pegging Information
You can display pegging information in the order processing view. For more
information, see Display pegging information [Page 313]
• Considering pegging relationships in detailed scheduling
The system can consider pegging relationships in Detailed scheduling [Page 62], that
is, it can carry out scheduling or rescheduling of objects (orders, operations,
activities) such that pegging relationships are taken into consideration and
requirements dates are not violated. This can mean that a date change is
automatically transferred to dependent objects. You can determine if and how the
system should consider pegging relationships in the Detailed scheduling strategy
[Page 82]. For more information, see considering pegging relationships [Page 98]
Dynamic Pegging
Use
The system carries out dynamic pegging [Page 36] automatically if the requirements or
receipt situation changes, that is, if requirement or receipts are created or their quantities and
dates change. With dynamic pegging, the system deletes existing dynamic pegging
relationships and recreates the pegging relationship. As the planning situation is constantly
changing, pegging relationships created once are not usually maintained for long.
Features
The system carries out pegging of receipt elements [External] and requirements elements in
accordance with the following system standard or user-defined values:
• The system may only peg receipt and requirements elements from the same pegging
area [External].
• To cover a new or changed requirement, the system must first use available receipts
whose quantities are not or are only partially assigned to other requirements.
• The system can assign several receipt elements to one requirements element or one
receipt element to several requirements elements depending on the required or available
quantities (see graphic under Pegging [Page 36]).
• The system may only cover a requirement with receipt elements whose availability dates
lie within the user-defined pegging interval [Page 39].
• If the quantities of the receipts within the pegging interval are insufficient to cover a
requirement, the system tries to create new receipts during automatic planning. In the
Detailed scheduling strategy [Page 82] you set whether or not the system must also
consider the pegging interval [Page 98] when scheduling the newly created orders.

• The system must peg receipts and requirements in accordance with the user-defined
pegging strategy [Page 42] for the product (for example, it must use the earliest receipt in
the pegging interval).
• The system may only peg a requirement with a receipt if the receipt corresponds with the
shelf-life requirements of the requirement. For more information, see Planning with shelf-
lives [Page 108]
• The system may cover a requirement, in the context of user-defined Delivery tolerances
[Page 44] using an insufficient or an excessive total receipt quantity.
For more information, see Pegging [Page 36]
Pegging Interval
Definition
Time segment around a requirements date, containing the receipt elements [External] that the
system can use to cover the requirement in dynamic pegging [Page 38].
The system cannot assign receipt elements with availability dates outside the pegging interval
to the requirement. Dynamic pegging relationships are therefore only created within the
pegging interval.
Use
In dynamic pegging, the system automatically assigns the receipts that should cover a
requirement to the requirement. Ideally, the receipt and requirements dates should be the
same. Generally, this is not fully achieved in planning; that is, the availability dates can be
earlier or later than the requirements date. In certain circumstances deviations are
permissible. If the availability date is too late, this can lead to problems with a lack of material
or with adherence to sales order dates. If the availability date is too early, this does not make
sense economically and can cause shelf-life or storage problems. Thus, if a receipt element is
too late or too early, it should not be used to cover a requirement; you can exclude these
receipt elements using the pegging interval.
The pegging interval is determined in the location product master as product specific. You
define this using the maximum allowed deviation of the availability date from the requirements
date (maximum allowed advance of a receipt and maximum allowed delay of a receipt).
Integration
Alert threshold for date alerts
With a dynamic pegging relationship, in the context of the pegging interval, the availability
date can lie either before or after the requirements date; the product is therefore available
either too early or too late. In the location product master, you can determine from which time
deviations between the requirements and availability date the system should create date
alerts. If you wish to see the date alerts in dynamic pegging, you must define the threshold
values so that they lie within the pegging interval. You can define whether or not the system
displays the alerts in the PP/DS alert profile. For more information, see display of alerts [Page
304]
Quantity problems
If the quantities of the receipts within the pegging interval are insufficient to cover a
requirement, there is a shortage. The system can create orders with automatic planning and
then assign the requirement with dynamic pegging (as long as the availability date is within
the pegging interval). In the detailed scheduling strategy [Page 82], you can determine
whether or not the system should create orders so that the availability dates are within the
pegging interval and (as timely as possible) before the requirements date, (see Considering
pegging relationships [Page 98]). If the availability date of the newly created orders is outside

the pegging interval, the system cannot produce a dynamic pegging relationship. The
shortage therefore still remains for the requirement, and the new receipts create a surplus (if
the system does not use these receipts to cover different requirements). You must solve the
shortage and surplus problems interactively or by using specific heuristics. You can define
whether or not the system displays alerts for shortages or surpluses in the PP/DS alert profile.
For more information, see display of alerts [Page 304].
The system optimizes [Page 227] delays based on the pegging relationships. If
there is no pegging relationship between a receipt and the pegged requirement
(for example, a sales order), the sales order dates cannot be considered during
optimization.
Example
You have determined in the location product master that,
• The system can only create a dynamic pegging relationship if the availability date of the
product is at most three days before and one day after the requirements date for the
product
• The system should create an alert if the receipt date is more than one day before the
requirements date, or if it is after the requirements date
The following graphic gives an example of a planning situation. The pegging interval is shown
from the point of view of a requirements element (marked in yellow), that is, in relation to a
specific requirements date. The question for this view is: Which receipt element may the
system use to cover this requirement? Answer: The system can assign receipt elements a, b
or c to the requirements element. The assignment chosen by the system depends on the
pegging strategy [Page 42] specified. If the system assigns receipt element a or c, the system
creates an alert showing that the receipt is too early or too late. Only assignment of b has no
alerts.
Pegging interval from the point of view of a requirements element

Pegging Interval
Requirements
date
Alert Alert
-7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 5 Days
100 100 100 100 100 100
100 100 100 100 100 100 100
a b c
The pegging interval can also be considered from the point of view of the receipt element, that
is, in relation to a specific receipt date, as shown in the next graphic. The question for this
view is: To which requirement can the system assign the receipt element? Answer: The
system can assign the receipt element to requirements A, B or C. If the system assigns the
receipt element to requirements A or C, the system creates an alert showing that the receipt
is too early or too late. Only assignment to B has no alerts.
Pegging interval from the point of view of a receipt element

Pegging Interval
Availability date
Alert Alert
-8 -7 -6 -5 -4 -3 -2 -1 0 1 2 3 4 Days
A B C
100 100 100 100 100 100
100 100 100 100 100 100 100
Pegging Strategy
Definition
Regulation that determines in which time sequence the system should cover requirements in
dynamic Pegging [Page 38], and in which time sequence the system should use receipt
elements [External] in the pegging interval [Page 39] to cover a requirement. The pegging
strategy therefore controls,
• Which requirement the system covers first
• Which receipts the system uses first
Use
Basically, the system begins in dynamic pegging by covering the earliest requirement, and
then processes the next requirement, and so on. Since the availability dates of several
receipts may lie within the pegging interval, you must determine which receipts the system
should use first.You have the following options:
• Use the earliest receipt (First in first out)
Here, the system covers a requirement with the earliest receipt in the pegging
interval, that is, first the first receipt in the pegging interval, then the second, and so
on. With this strategy surplus receipts are only available later.
• Use timely receipts
Here, the system covers a requirement with the most timely receipt in the pegging
interval. The system first searches from the requirements date towards the beginning
of the pegging interval. If the system does not find any receipts in this direction, it
then searches from the requirements date towards the end of the pegging interval.
This strategy supports synchronous requirements production.

You can determine the pegging strategy product-specifically in the location product master on
the requirement tab page.
Example
The graphic below explains the pegging strategies using the example given under pegging
interval [Page 39].
Pegging Strategies
Pegging Interval Pegging Interval

Requirements Requirements
date date
Alert Alert Alert Alert
-3 -2 -1 0 1 Days -3 -2 -1 0 1 Days
100 100 100 100 100 100
100
100 100 100 100 100 100 100
a b c a b c
1 2
Use
Useearliest
earliestreceipts
receiptspegging
peggingstrategy
strategy Use
Usetimely
timelyreceipts
receiptspegging
peggingstrategy
strategy
The availability dates for receipt elements a, b and c lie within the pegging interval for the
yellow requirements elements. Which receipt element the system assigns to the requirements
element depends on the pegging strategy, as explained below:
• With the use earliest receipt pegging strategy, the system begins the search for receipt
elements at the beginning of the pegging interval. It therefore assigns receipt element a
to the requirements element. Since the availability date of receipt element a is more than
one day before the requirements date, the system creates an alert. If receipt element a
produced 50 pieces instead of 100 pieces, the system would assign another 50 pieces to
the requirements element from receipt b.
• With the use timely receipt pegging strategy, the system searches for receipt elements
from the requirements date to the beginning of the pegging interval. It therefore assigns
receipt element b to the requirements element. If receipt element b produced only 50
pieces instead of 100 pieces, the system would assign another 50 pieces to the
requirements element from receipt a. If receipt elements a and b were not available, the
system you not find any receipts in this direction. If this was the case, the system would
search to the end of the pegging interval and assign receipt element c to the
requirements element.

Delivery Tolerance
Definition
Maximum allowed shortage or surplus of a requirement.
Use
In certain cases, shortages or surpluses can be tolerated within a specific scope, for example
in make-to-order production with characteristics dependent planning, where a product is
produced for the customer according to customer-specific requirements. With dynamic
pegging, the system can cover a requirement within the context of delivery tolerances with an
insufficient or excessive total receipt quantity. A requirement for which there is a shortage is
nonetheless considered as covered, in the context of the maximum allowed shortage.
You can set the delivery tolerances in the location product master as product specific.
Fixed Pegging
Use
You use Fixed Pegging [Page 36] if you wish to fix the assignment of a receipt element
[External] to a requirement element and if the system should not change this assignment
during planning. The following pegging types exist:
• Manually fixed pegging
You can create a manually fixed pegging relationship [Page 319]. To do this,
determine the desired pegging quantity, that is, the (partial) quantity of the receipt that
you wish to assign to the requirement.
• Automatically fixed pegging
In the following cases, the system can fix pegging relationships automatically:
− In order network planning
If you have determined in the location product master for a product that the
dependent requirements for the product should be planned as an order network,
the system does not use existing receipt elements to cover the dependent
requirements. Instead it creates exactly one receipt element with the required
quantity (exact lot size) for each dependent requirement and assigns it to the
requirement element. The system fixes this pegging relationship automatically.
− In Capable-to-Match planning (CTM planning)
You can determine if the system should create a pegging relationship in a
Capable-to-Match [External] planning run in the CTM Profile [External] on the
Strategy tab page. The system can also create fixed pegging relationships in the
CTM planning run dependent on the characteristics of the requirement (see rules
based CTM planning [External]). The system can change automatically fixed
pegging relationships in a subsequent CTM planning run. The system cannot
change manually fixed pegging relationships in the CTM planning run.
Fixed pegging relationships cannot be transferred to an OLTP system.

Creating Fixed Pegging Relationships Manually

Use
You wish to create total or partial fixed assignment of the product quantity produced by an
order to a specific requirements element. The system should not change this assignment
during automatic planning.
To do this you can create a fixed pegging relationship manually between the receipt element
[External] and the requirements element. You define the desired pegging quantity, that is, the
(partial) quantity of the receipt that you wish to assign to the requirement.
Unlike dynamic pegging, there are no time constraints for creating fixed pegging relationships.
The system can create date alerts and display them in the Alert Monitor [Page 304] if the time
deviations between availability and requirement dates are too large.
Prerequisites
You are in the change mode of the order processing view [Page 309].
Procedure
1. To display the existing pegging relationships for the order, double-click on the order tree
− under receipts on an order product, or
− under requirements on an order component
2. Choose the Pegging tab page.
− If you clicked on Receipts in step 1, you will see the pegging relationships to an
order product, that is, the requirements elements consumed by the order product.
For each requirements element, the quantity of order products with dynamic
assignment to the requirements element is shown in the Dynamic Pegging Quantity
column.
− If you clicked on Requirements in step 1, you will see the pegging relationships to
an order component, that is, the receipt elements that deliver this component. For
each receipt element, the quantity of components with dynamic assignment to the
order is shown in the Dynamic Pegging Quantity column.
3. In the Desired Pegging Quantity column, enter the quantity of the order product that you
wish to assign to the requirements element, or enter the quantity of components that a
receipt element should deliver to the order.
The desired pegging quantity can be different from the quantity that a receipt element
can actually deliver. The system determines the actual pegging quantity automatically
[Page 46].
If you choose Pegging alternatives, you will obtain a list of all possible requirements
or receipt elements that could consume the order product or deliver the component.
4. Select the requirements or receipt element and choose Fix.
Result
You have created a fixed assignment of the desired pegging quantity to a requirements
element or a receipt element. The system does not change this fixed assignment during
planning. If there is only fixed assignment for part of the product or component quantity, the
rest is not assigned or has dynamic assignment to requirements or receipt elements.
If you wish to undo the fixed assignment, select the requirement or receipt element and
choose Defix.

Example
A receipt element with an order quantity of ten pieces has dynamic assignment to a
requirements element with ten pieces. You can fix six pieces and thus fix assignment of the
requirements element. The remaining four pieces are then still assigned dynamically to the
requirements element, the system can change this assignment during automatic planning.
A product can be planned as an order network. To cover a requirement for such a

product, the system does not use any existing receipt elements, but creates
exactly one receipt element for the dependent requirement with the required
quantity (exact lot size) and assigns it to the requirement element. The system
fixes this pegging relationship automatically.
Calculation of the actual pegging quantity

Use
If you create a fixed pegging relationship manually [Page 319], enter the desired pegging
quantity, that is, the (partial) quantity of the receipt element [External] that you wish to assign
to the requirements element. The quantity that is actually transferred from the receipt to the
requirement is calculated automatically by the system during planning and may differ from the
desired quantity.
For pegging relationships that are fixed automatically by the system, there is no
difference between the desired and the actual pegging quantity; the system
adapts the quantities automatically.
There may be deviations between the desired quantity and the actual quantity of transferred
quantities in the following cases:
• The receipt quantity or the requirements quantity changes after you have fixed the
pegging relationship with the desired pegging quantity.
You have created a fixed pegging relationship between a receipt element with a
quantity of 20 pieces and a requirements element with a quantity of 20 pieces.
You have specified 20 pieces as the desired pegging quantity; the complete
receipt quantity should be assigned to the requirement. Then the receipt quantity
is reduced to 15 pieces (for example, because a total of just 15 pieces was
confirmed due to an unpredictably large quantity of scrap. The actual pegging
quantity is therefore 15 pieces.
• You have specified a desired pegging quantity which is greater than the quantity
delivered by the receipt element.
You have created a fixed pegging relationship between a receipt element with a
quantity of 15 pieces and a requirements element with a quantity of 20 pieces.
You have specified 20 pieces as the desired pegging quantity. Since the receipt
element only delivers 15 pieces, the actual pegging quantity is 15 pieces. If 19
pieces are confirmed for the receipt element due to an unpredictably small
amount of scrap, the actual pegging quantity is 19 pieces.

Integration
The system displays the actual transferred quantities in the pegging structure of an order
[Page 303], for example.
You can find further information under pegging [Page 36] and fixed pegging [Page 44].
Displaying Pegging Information

Prerequisites
You are in the order processing view [Page 309].
Procedure
The following table shows how you can display Pegging [Page 36] information.
Pegging Information Procedure

• Current requirements for In the order tree, double-click on an order product or on a
an order product component
• Current receipts for a On the Pegging tab page you can see what quantity of the order
component product is assigned to which requirements, or which receipts
deliver which component quantities to the order. The assignment
can be dynamic [Page 38] or fixed [Page 44].
You can manually create fixed pegging relationships [Page 319].
• Alternative requirements Choose Pegging alternatives on the Pegging tab page.
for an order product
The system displays other requirements elements or Receipt
• Alternative receipts for a elements [External] that you can assign to the order product or
component the order component.
To display the pegging alternatives, you must be in the change
mode of the order processing view.
Total pegging structure [Page Choose Context.
303] of the order
• The Structure tab page displays a list of the pegging
structure.
• In the standard system, the planning board 1 tab page
displays a Detailed scheduling planning board [Page 385]
with a chart [Page 364], which displays a Gantt chart
containing the time position of the orders to the products
concerned and the pegging relationships between the
orders. Dynamic pegging relationships are displayed in
green, and fixed pegging relationships are displayed in red.
The pegging structure for the order is highlighted in color.

Pegging Structure of an Order

Definition
Pegging Structure [External], which contains the order that you are currently processing in the
order processing view [Page 309].
Structure
You call up the pegging structure for an order in the order processing view via Context.
Layout of the Pegging Structure screen
Screen area Contents
Top Requirements of the end products produced in the order
Bottom left Pegging structure of the selected requirement

The requirement is the top node of the pegging structure. If there is no
requirement for an end product, the order for the end product is the top node
of the pegging structure.
Bottom right Detailed information on the receipt [External] and requirements elements in
the pegging structure
Considering Pegging Relationships

Use
If an order transfers its product to another order, these orders are linked by a fixed [Page 44]
or a dynamic [Page 38] pegging relationship. A planned order, which requires a certain
component can be linked to a purchase requisition for the component in external
procurement, or to a planned order for the component in in-house production (see pegging
[Page 36]).
You may wish to consider pegging relationships if an order or an activity from an order is
being scheduled or rescheduled, that is, the system must schedule or reschedule such that
no requirements dates are violated. This can mean that the system must schedule or
reschedule objects (orders, activities) which have pegging relationships accordingly; date
values or date changes must therefore be propagated to the dependent objects.
In the Detailed scheduling strategy [Page 82] you can define whether or not the system
should consider pegging relationships during detailed scheduling [Page 62]. You have the
following options:
• Consider fixed pegging relationships [Page 99]
• Consider fixed and dynamic pegging relationships [Page 100]
Integration
If pegging relationships are not considered during scheduling or rescheduling, date problems
(availability date too late or much too early) or, with dynamic pegging relationships, new
quantity problems (shortages or surpluses) may occur. You define the alert thresholds for
date alerts (maximum advance and maximum delay of the availability date) in the location
product master. If these thresholds are exceeded during planning, the system creates date

alerts. If you wish to display date and quantity problems in the alert monitor [Page 304], you
must use the corresponding PP/DS alert profile.
Prerequisites
If the system is to consider pegging relationships during scheduling or rescheduling, you must
also define in the detailed scheduling strategy that the system should consider time
relationships between operations [Page 97].
Considering Fixed Pegging Relationships

Use
You can define in the detailed scheduling strategy [Page 82] whether the system should
consider the fixed pegging relationships [Page 44] to other dependent objects when
scheduling or rescheduling [Page 62] an object (activity, operation or order). Considering
fixed pegging relationships means scheduling or rescheduling an object and its dependent
object such that no requirements dates are violated. You have the following options:
• Do not consider fixed pegging relationships
• Consider fixed pegging relationships
• Consider fixed pegging relationships in the propagation range [External]
In principle, the system retains fixed pegging relationships during scheduling or rescheduling,
that is, the assignment of a receipt element [External] to a requirements element is
maintained.
Prerequisites
For more information about the prerequisites, see considering pegging relationships [Page
98].
Features
Do not consider fixed pegging relationships
The system schedules or reschedules an object without considering requirements dates. This
means that the requirements dates may be violated. If the availability date is earlier or later
than the alert thresholds specified in the location product master, the system will create a date
alert.
Consider fixed pegging relationships

The system must schedule or reschedule an object such that the availability date is as close
as possible to, but still before the requirements date. If the object has a fixed pegging
relationship to an unfixed [Page 418] object, the system must schedule or reschedule this
dependent object accordingly; for an unfixed deallocated object, the system must also adjust
the dates and modes. A fixed [Page 418] dependent object defines a fixed availability date or
a fixed requirements date which restricts the scheduling or rescheduling of the object. If it is
not possible to schedule or reschedule the object and its dependent objects accordingly, the
system does not carry out scheduling or rescheduling.
A sales order or a planned independent requirement is fixed and defines a fixed

requirements date. With the consider fixed pegging relationships option, the
system must schedule a planned order for the sales order or planned
independent requirement so that the availability date is as close as possible
before the requirements date.

The system cannot correct an existing delay situation − in a pegging relationship

the availability date is after the requirements date − , that is, it schedules or
reschedules the object without time constraints.
Consider fixed pegging relationships only in the propagation range

Objects outside the propagation range [External] are, in principle, fixed during planning, that
is, these objects define fixed availability dates or requirements dates. This can lead to severe
limitations for the planning. With the consider fixed pegging relationships only in the
propagation range option, you can plan more flexibly, since the system must consider a
pegging relationship between an object in the propagation range and an object outside the
propagation range (see do not consider fixed pegging relationship); the system can schedule
or reschedule the object in the propagation range without constraints. However, the system
must consider pegging relationships between objects within the propagation range (see
consider fixed pegging relationships).
Considering Dynamic Pegging Relationships

Use
consider the dynamic pegging relationships [Page 38] to other objects when scheduling or
rescheduling [Page 62] an object (activity, operation or order). After scheduling or
rescheduling, the system carries out dynamic pegging, in which it deletes the existing
dynamic pegging relationships and creates new ones. Considering dynamic pegging
relationships means scheduling or rescheduling an object and its dependent objects such
that,
• The pegging relationships between the object and its dependent objects, which existed
before scheduling or rescheduling, are maintained, that is, are recreated in dynamic
pegging after scheduling or rescheduling.
• No requirements dates are violated
You can only consider dynamic pegging relationships together with fixed pegging
relationships [Page 99]. You have the following options:
• Do not consider dynamic pegging relationships
• Consider dynamic pegging relationships in the propagation range [External]
Prerequisites
If the system should consider pegging relationships, you must also define in the detailed
scheduling strategy that it must consider fixed pegging relationships [Page 99]. For more
information about further prerequisites, see considering pegging relationships [Page 98].
Features
Do not consider dynamic pegging relationships
The system schedules or reschedules an object without time constraints, that is, without
considering the pegging interval [Page 39]. After scheduling or rescheduling, the system
carries out dynamic pegging in accordance with the pegging settings in the location product
master (for example, pegging interval [Page 39] and pegging strategy [Page 42]). Since the
pegging interval was not considered during scheduling or rescheduling, the original pegging

relationship, that is, the original link between receipt elements [External] and requirements
elements can be lost. If the system is not able to create a new corresponding pegging
relationship, quantity problems may now occur. If, for example, an order is not assigned to
any receipt, there is a shortage for the order. If no requirement is assigned to the order, the
order creates a surplus. If the system was able to maintain the pegging interval during
scheduling or rescheduling, date problems may occur if the deviation of the availability date
from the requirements date exceeds the alert threshold for date alerts specified in the product
master.
Consider dynamic pegging relationships in the propagation range

The system must not consider a dynamic pegging relationship between an object in the
propagation range [External] and an object outside the propagation range; the system can
schedule or reschedule the object in the propagation range without time constraints (see
above).
However, the system must consider dynamic pegging relationships between objects within
the propagation range; the system must schedule or reschedule an object such that the
dynamic pegging relationship to a dependent object in the propagation range is maintained
and that the availability date is as timely as possible, or at least is between the beginning of
the pegging interval and the requirements date. If the object has a dynamic pegging
the dates and modes. A fixed dependent object defines a fixed availability date or a fixed
requirements date which restricts the scheduling or rescheduling of the object. If it is not
possible to schedule or reschedule the object and its dependent objects accordingly, the
As, with this option, the system maintains the pegging interval for a dynamic pegging
relationship within the propagation range, the system creates (with all probability) the same
dynamic pegging relationship after scheduling or rescheduling in dynamic pegging.
• In complex scheduling situations, however, the original pegging relationship may be lost.
If the system can create a different pegging relationship, the availability date does not
deviate further from the requirements date than is allowed by the pegging interval.
• The system cannot correct an existing delay situation − in a pegging relationship the
availability date is after the requirements date −, that is, it schedules or reschedules the
object without time constraints.
• If pegging relationships exist between receipts and requirements [Page 239], the
optimization can minimize delays of receipts [Page 231]. If there is no longer a pegging
relationship between a requirement, for example a sales order, and a planned order for
this sales order, the sales order date cannot be considered during optimization.
Lot Size Calculation

Use
The system calculates the lot-size based on the lot-sizing procedure defined in the product
master record in APO.
Prerequisites
You have maintained the lot size data and if you have assembly scrap, you have specified the
percentage (only for products produced in-house) in the product master record in APO.

Process
1. When planning the products, the system determines the shortage quantities for the
relevant requirement dates. The shortage quantities must be covered by receipt
elements.
2. Based on the shortage quantity, the scrap and the total quantity to be produced are
calculated. If no assembly scrap [Page 55] was defined in the product master record, the
shortage quantity remains unchanged.
3. The total quantity of the order is determined based on the lot size data that is maintained.
The following procedures can be used for lot-size calculation in APO:
− Lot-for-lot order quantity [Page 53]
− Fixed lot size [Page 52]
The result of the lot-size calculation is the quantity to be produced or procured, which you can
display or change in the order. You can also specify additional restrictions that should be
considered in the lot-size calculation when maintaining the product master records.
These restrictions include:
• Minimum lot size
A minimum purchase order quantity is defined per lot.
• Maximum lot size
A maximum purchase order quantity is defined per lot.
• Rounding value
A value is entered; multiples of which are used for rounding.
• Rounding profile [Page 53]
Staggered roundings can be made.
You entered a fixed lot size with 100 pieces and a scrap of 10% as the lot-sizing procedure in
the product master record in APO. The requirement quantity (shortage determined) is 100
pieces.
1. Scrap calculation:
The system calculates the scrap and determines the total quantity of 111 pieces to
be procured using the following formula:
Total quantity = 100 pieces (100% - 10%) = 100 pieces/0.9 = 111 pieces.
2. Calculation of the quantities to be procured:
111 pieces must be ordered. The fixed lot size is 100 pieces per order. As a result,
the system generates two orders with 100 pieces per order.
Fixed Lot Size

Use
You choose a fixed lot size for a product if it is necessary for technical reasons; for example,
pallet size or tank contents.

Prerequisites
You have selected Fixed lot size in the Lot size view of the product master record in APO and
entered the quantity.
Features
The system uses the fixed lot size that was defined in the product master record in the
calculation for product shortages that meet the criteria for fixed lot size. If the quantity of a
fixed lot size is insufficient to eliminate the shortage, several lots are scheduled for the total
quantity of the fixed lot size for the same date until there is no longer a shortage.
Lot-for-Lot Order Quantity

Use
The system uses the exact shortage quantity (requirement minus available warehouse stock)
as the lot size in the calculation for product shortages that meet the criteria for lot-for-lot order
quantity. For the corresponding requirements date, the planned warehouse stock equals 0.
Prerequisites
You have selected Lot-for-lot qty in the Lot size view of the product master record in APO.
Features
Planning is carried out according to the requirements. This means that an order is generated
for every requirement.
Rounding
Use
Rounding is used to adjust units of measure used in product planning to the units of measure
used in delivery or transportation. For example, you use rounding if deliveries for purchase
orders can only be made in units of ten.
You define a rounding profile, which the system then uses to calculate the quantity to be
procured for the order.
A rounding profile comprises:
• Level
• Threshold value
• Rounding value
Multiple combinations of threshold and rounding values can be defined for a rounding profile.
The individual combinations are then assigned to a level.
The threshold value represents the value to which the system rounds up the next deliverable
quantity. If the threshold value is not reached, the system performs a rounding operation
based on the next smaller level. Once the smallest level is reached, the system rounds up to
the multiple of the rounding value if the required quantity is greater than the threshold value.
Otherwise the required quantity remains unchanged.

The rounding value is the value to which the system rounds up once the threshold value has
been exceeded.
Prerequisites
• You have defined a rounding profile in Customizing for APO, under Master Data →
Product in the IMG activity Maintain Rounding Profiles.
• You have specified a rounding profile in the APO product master record.
Example
A specific rounding profile has been defined in APO as follows:
2=→=5
32 →=40
This means that from a requirement of 2 units the system rounds up to 5 units and from a
requirement of 32 units it rounds up to 40 units. If the requirement is lower than the first
threshold value, the original requirement value is used unchanged. If the first threshold value
is exceeded, the value is always rounded up.
Based on these settings, the following situation can be modeled, for example:
A base unit of measure of 1 piece has been defined for a product. The product is to be
ordered in sets (1 set equals 5 pieces) or in pallets (1 pallet equals 8 sets corresponding to 40
pieces).
The system uses the rounding profile to calculate the quantities for the order proposal as
follows:
Requirement (pieces) Order proposal quantity

(pieces)
1 1
2 5
6 10
7 10
21 25
31 35
32 40
41 45
74 80
• For a requirement of 7 pieces, the system checks how often 7 can be divided by 5. This
results in an order quantity of 5 pieces (1x5=5). The system rounds up the remaining 2
pieces to 5 pieces. Thus, for a requirement of 7 pieces, one order proposal is created for
10 pieces.
• For a requirement of 74 pieces, the system checks how often 74 can be divided by 40.
This results in an order quantity of 40 pieces (1x40=40). The system rounds up the
remaining 34 pieces to 40 pieces. Thus, for a requirement of 74 pieces, one order
proposal is created for 80 pieces.

Scrap Calculation
Use
If you have scrap when producing a product, the quantity to be produced has to be increased
accordingly so that you receive the desired quantity. You can model scrap in the following
ways:
• At Assembly Level [Page 55]
Here you specify how much scrap is produced when manufacturing the product,
independent of the manufacturing process used.
• At Activity Level [Page 56]
Here you specify in the production process model exactly how much scrap is
produced in each processing step. You can therefore model scrap dependent on the
manufacturing process used.
Scrap calculation is only relevant for products produced in-house. The System calculates the
scrap automatically using the desired yield and the scrap data and increases the quantity to
be produced and the component requirements. You should only use one of the above
mentioned procedures for a product as otherwise too much scrap is calculated.
Calculation of Assembly Scrap

Use
For a product produced in-house, you can specify in the product master, how much scrap is
produced when manufacturing the product, independently of the manufacturing process used.
If scrap is produced, a larger quantity of the product has to be produced to receive the
required yield. The system automatically corrects the quantity to be produced in the following
places:
• In the lot size calculation [Page 51], which is performed during automatic planning and
the Product Heuristic [Page 321] function
• When manually creating an order [Page 314]
The system calculates the total quantity to be produced using the desired yield and the
assembly scrap according to the following formula:
Total quantity = Yield x 100% / (100% - scrap in %)
When the system increases the total quantity, it also increases the following accordingly:
• The quantity of the components that are required to manufacture the product
• In the case of quantity-dependent processing times, the net duration of the activities
[Page 67]
• In the case of quantity-dependent resource consumption, the resource consumption of
the activities [Page 68]
Prerequisites
You have entered the assembly scrap percentage in the location-specific product master of
the product on the Lot Size tab.

You should define scrap either at assembly level or at activity level [Page 56] as
otherwise too much scrap is calculated.
Example
You create an order and enter a yield of 100 pieces. In the product master, you
have entered assembly scrap of 20%. The system therefore creates an order for
125 pieces.
Calculation of Activity Scrap

Use
For a product produced in-house, you can specify in the production process model (PPM)
exactly how much scrap is produced in every processing step. If scrap is produced in an
activity, the activity has to process a larger quantity in order to achieve the required yield. The
activity therefore consumes more components. In the case of quantity-dependent processing
times and quantity-dependent resource consumption, the net duration [Page 67] and the
resource consumption [Page 68] of the activity is also increased. The system corrects the
quantity during the PPM explosion. The total quantity to be produced of an activity is
calculated during the PPM explosion according to the following formula:
Total Quantity = Yield x 100% / (100% - Scrap in %)
In the PPM, you can choose whether the yield to be produced of an activity is:
• The order quantity
The total quantity of the activity is calculated based on the order quantity.
• The total quantity required by the successor activity
When a successor activity has to process a particular total quantity, this yield has to
be delivered by the predecessor activity. The quantity of the predecessor activity is
therefore also increased to allow for scrap in the successor activity.
Prerequisites
• You have entered the scrap percentage for the activities that have scrap in the production
process model.
• To allow the quantity increase of a predecessor activity due to scrap of a successor
activity, you have to have set the Material flow indicator for the relationship between
these activities.
You define scrap either at assembly level [Page 55] or at activity level for a
product, otherwise too much scrap is calculated.
Example
Scrap Without Material Flow

An order comprises three successive operations that each consist of one

processing activity. You have not set the Material flow indicator for the
relationships between activity 1 and activity 2, and between activity 2 and activity
3. This means that the activity quantities are to be calculated individually for each
activity based on the order quantity. You have entered the following scrap data
for the activities:
• Scrap for activity 1: 5%
• Scrap for activity 3: 5,5%
The quantity to be produced by the order is 100 pieces. Using this data, the
system calculates the quantities to be processed or that are required in the
activities:
• Quantity for activity 3: 100 pieces / 0.945 = 106 pieces
If each of the activities require special components, these have to be provided
according to the activity quantities, for example, 105 pieces for activity 1, 108
pieces for activity 2 and 106 pieces for activity 3.
Scrap With Material Flow

As in the example above, an order comprises three successive operations that
each consist of one processing activity. You have set the Material flow indicator
for the relationships between activity 1 and activity 2, and between activity 2 and
activity 3. This means that the quantity to be processed in an activity is to be
provided by the predecessor activity. You have maintained the following scrap
data in the PPM:
• Scrap for activity 3: 5,5%
The quantity to be produced by the order is 100 pieces. Using this data, the
system calculates the activity quantities:
For the order to deliver 100 pieces, the first activity must process 120 pieces, the
second 114 pieces and the third 106 pieces. The components have to be
provided according to the activity quantities, for example, 120 pieces for activity
1, 114 pieces for activity 2 and 106 pieces for activity 3.
Calculation of Days' Supply

Use
You use the days supply to see how long stock and receipts can cover requirements so you
can take action to avoid product shortages. The days' supply in APO indicates the number of
calendar days left until stock falls below zero.

In Customizing, you are able to define exactly which stock and receipt categories are to be
compared with which forecast and requirement categories. This definition is referred to as a
days' supply type. The system can calculate up to three different days' supply types when you
access the product view [Page 308] or the Alert Monitor. Since there is more than one days'
supply type, you can compare the effects different categories have on product availability and
see whether any action is required.
An example of three different days' supply types could be that:

• You take current stock and all requirements into account.
• You take current stock, all requirements, and receipts that you are certain to receive into
account, such as, for example, production orders or purchase orders.
• You take all stock, requirements and receipts into account.
When defining the days' supply type, you can also define values for the minimum days' supply
[Page 59]. These are used to trigger alerts to warn you of potentially critical situations
regarding product availability.
Prerequisites
• You have maintained days' supply types, including the values for the minimum days'
supply in Customizing for Production Planning and Detailed Scheduling.
• You have entered the days' supply types (maximum of three) that are to be calculated by
the system in Customizing for the Order View, under Set Layout, Maintain General
Settings.
Features
There are two standard days' supply types that you can copy in order to create new days'
supply types:
• SAP1 (contains all stock, requirements and forecasts currently defined in the R/3 System)
• SAP2 (contains all stock, receipts, requirements and forecasts currently defined in the
R/3 System)
You copy the standard days' supply types and then delete the categories you do not wish to
include in the calculation of days' supply.
The days' supply is calculated for each pegging area as follows when you access the Product
View or the Alert Monitor:
Days' supply = (Stock + Receipts) / (Requirements + Forecast)
Exactly which receipt/requirement elements are included depends on the categories you have
defined for the days' supply type in Customizing for Production Planning and Detailed
Scheduling.
As days' supply is calculated for each pegging area, you may have several different days'
supply for the same product in the same location and in the same planning version due to
different account assignment objects. The days' supply displayed varies depending on where
you view it:
• In the product view, one value is displayed for each of the days' supply types (maximum
of three). The days' supply of the pegging area with the lowest days' supply is displayed.
Only one minimum days' supply alert is displayed for this one pegging area. Alerts and
the calculated days' supply for other pegging areas can only be displayed in the Alert
Monitor.
• In the Alert Monitor [External], you can view all alerts for all pegging areas of a product.
The calculated days' supply for each pegging area is displayed alongside the values
defined for the minimum days' supply. On the initial screen of the Alert Monitor, you can

branch into the profile maintenance in which you can overwrite the days' supply types to
be calculated that you have defined in Customizing.
Minimum Days' Supply

Definition
A value used to trigger alerts in PP/DS to inform the planner of critical situations regarding
product availability. You can define up to three values (in calendar days) for the minimum
days' supply when defining the days' supply type in Customizing for Production Planning and
Detailed Scheduling. The values should allow you sufficient time to react to the problem to
avoid a product shortage.
The days' supply [Page 57] is calculated automatically by the system when you call up the
Alert Monitor or the Product View. The calculated days' supply is then compared to the values
you have set for the minimum days' supply. As soon as the days' supply falls short of one of
these values, an alert is generated. The three values have a different priority assigned to
them and each causes a different alert to be triggered:
• Error
Alert with the highest priority. You enter the lowest number of calendar days that still
allows you to take action to avoid a product shortage. For example, if a product has a
replenishment lead time of 5 days, you could enter 5 days' as the absolute minimum
days' supply for this alert.
• Warning
Alert with medium priority. The number of calendar days you enter for this alert
should be higher than the error alert to allow you more time to take action (for
example, 10 days).
• Info
Alert with the lowest priority. The number of calendar days you enter for this alert
should be higher than the other two alerts types (for example, 15 days).
When defining a days' supply type, you can also specify a user exit for the minimum days'
supply values. User exits can be used, for example, to define different minimum days' supply
for particular products. If you specify a user exit in the days' supply type, this will overwrite the
values for the minimum days' supply. For more information, see the document on the user
exit APOCV001.
Integration
Alerts for the minimum days' supply are displayed:
• In the Alert Monitor. The alerts are displayed in the Alert Monitor for each pegging area.
You can overwrite the days' supply types and thus the minimum days' supply values from
Customizing by branching to the profile maintenance from the initial screen of the Alert
Monitor.
• In the Product View. The days' supply of the pegging area with the lowest days' supply is
displayed for each of the days' supply types. One alert is thus displayed for this one
pegging area. Alerts for other pegging areas of the product can only be seen in the Alert
Monitor.

Firming Orders for Production Planning

Use
An order can be firmed for planning using the production planning heuristics. PP Firming can
be triggered automatically by the system, or can be controlled by the user. The system cannot
change a PP firmed order; that is, the system cannot change the receipt quantity of the order
or delete the order, even if the requirements have changed. You can, however, change a PP
firmed order manually.
Prerequisites
An order is PP firmed if it has the status PP firmed. The system sets this status automatically
• If the availability date of the order is within the planning time fence
• If the order is an SNP order
• If the order has one of the following statuses:
− Output firmed
− Input firmed
− Date firmed
The following table gives the meaning of these statuses, and shows through which
user or system actions an order obtains these statuses.
Status Meaning Triggering actions or statuses
Output firmed The receipt quantity for the Changing the receipt manually
order is firmed. In PP planning,
You can change the receipt manually in the order
the system cannot change the
processing view [Page 309], for example, you can:
receipt quantity of the order or
delete the order. • Change the date, the quantity or the source
The output firmed status refers • Set the conversion indicator
to the order header firming in
the SAP R/3 system. Here, the system automatically sets the status
output firmed.
Firming the receipt manually
You can firm a receipt manually by setting the
status output firmed manually in the order
processing view.
Status input firmed
If the order is given the status input firmed (see
input firmed), the system also automatically sets
the status output firmed.
Order is a purchase order or a production order
Production orders and purchase orders transferred
from the OLTP System are automatically given the
status output firmed in the SAP APO system.

Input firmed The order BOM is firmed. If you Changing a component manually
change the receipt quantity of
You can change the order BOM manually in the
the order manually, the system
order processing view, for example, you can:
does not automatically explode
the PPM, but you can choose if • Change the required quantity
the system
• Use a different product as a component
• should retain the current
components and only In addition to the status input firmed, the system
adjust their quantities to the also automatically sets the status output firmed;
new receipt quantity that is, you can now only change the receipt
quantity of the order manually.
• should explode the PPM
(thus overwriting your
manual changes to the
BOM).
The input firmed status refers to
the explosion firming in the SAP
R/3 system.
Date firmed The dates and resource Firming with the detailed scheduling function
allocations for the order or Fix
individual operations of the
To prevent the system from changing the dates
order are firmed. The system
and resource allocations of the operations of an
cannot reschedule firmed
order in detailed scheduling [Page 62] or in
operations to other dates or
optimization [Page 227], you can use the detailed
other resources.
scheduling function fix [Page 418] to firm the order
or individual operations of the order in the
production planning run [Page 122] or in the
detailed scheduling planning board [Page 362]. By
firming, an operation is given the status firmed and
the order is given the status date firmed.
Resetting the PP firming

In the following cases, you can reset the PP firming of an order; that is, the system can
change the receipt quantity of an order or delete the order with subsequent PP planning.
The order is PP firmed How to reset the PP firming

Because you changed the order manually, Reset the status output firmed manually in the order
or firmed the receipt manually (status output processing view.
firmed)
Exception: If you have set the conversion indicator for
an order, you can not reset the PP firming.
Because you have firmed the operations of Reset the firming in the production planning run or in
the order using the detailed scheduling the detailed scheduling planning board using the
function Fix (status Date firmed) detailed scheduling function defix [Page 418].
Because the availability date of the order is If you set suitable settings in the planning time fence,
within the planning time fence the availability date may lie outside the planning time
fence.
You define the planning time fence in the product
master or in the product view.
Because the order is an SNP order outside Convert the SNP order into a PP/DS order [Page 114].
the production horizon

Detailed Scheduling
Use
Detailed scheduling is used to:
• Determine the resources and dates for processing operations [External], taking resource
and product availability into consideration.
• Support the scheduler when scheduling resources, that is, when creating an optimal
processing sequence for operations
The basic detailed scheduling activities [Page 64] are
• Scheduling, that is, dispatching operations to resources at a specific time
• Rescheduling, that is, dispatching already scheduled operations to a different time or to
different resources
• Deallocating, that is, removing scheduled operations from the resource schedule
Prerequisites
The system can trigger detailed scheduling activities automatically, for example, the system
automatically schedules the order operations when creating an order. You can also start
detailed scheduling activities in the production planning run [Page 122] or in the detailed
scheduling planning board [Page 362] specifically for selected [Page 70] operations or orders.
Here, the system automatically carries out detailed scheduling activities for affected
dependent objects [Page 71], if necessary. For more information, see detailed scheduling
activities [Page 64].
Features
Controlling Detailed Scheduling
Alongside the desired scheduling date [Page 94], the basis of detailed scheduling for an
order, are the capacity requirements [Page 66] of the activities [External]. You control which
constraints, rules, and parameters the system must consider during scheduling [Page 80]
using the settings and data in the following objects:
• Resource [External]
• Production process model (PPM) [External] or iPPE plan [External]
• Strategy profile [Page 419]
Dates and Planning Directions

The starting point for scheduling or rescheduling is the desired start or end date [Page 94] of
the orders or operations. If, for example, you create an order, the availability date of the main
order product defines the desired end date. If you reschedule an operation in the detailed
scheduling planning board using Drag&Drop for example, the desired date is the date on
which you “let go” of the operation.
Starting from the desired date, the system searches for a scheduling date in the set planning
direction [Page 86] for the last activity (planning direction backwards) or for the first activity
(planning direction forwards) of an operation or an order. If the first activity is scheduled, it is
then the turn of the next activity in the sequence, and so on until all activities of the operation
or order are scheduled or rescheduled. The system cannot schedule or reschedule an activity
before or after the application dependent earliest possible or latest possible date [Page 85].

Resource Availability
The dates on which an activity can be scheduled or rescheduled on a resource depends on
the capacity requirement [Page 66] of the activity and on the working times and capacity of
the resource. In general, you can only process activities during the working times of a
resource, and you can therefore only schedule these activities in regular working times. In
working times you can schedule activities finitely or infinitely [Page 81], that is, with or without
consideration of the resource capacity and the existing resource load. If necessary, you can
also schedule activities during non-working times, for example, breaks [Page 92]. Scheduling
during downtime [External] − caused for example by a machine breakdown or by
maintenance − is not possible. In order to schedule activities that are longer than related
working times, it must be possible to interrupt them with non-working times.
Selection of Resources
You can enter several alternative sets of resources (modes [Page 73]) at which the activity
can be processed, in the PPM for the activity. The mode selection [Page 72] can be automatic
or manual [Page 405], as in the detailed scheduling planning board.
Time Relationships
Time relationships that control which minimum and maximum time intervals activities can
have can exist between activities. The system always considers the obligatory end-start
relationships between activities for an operation. For example, when you have entered a
minimum interval of one hour between two activities in an operation, the system cannot
schedule or reschedule these activities in such a way that the time interval is less than one
hour. You define in the detailed scheduling strategy if the system should consider time
relationships between activities from different operations [Page 97] when scheduling.
Pegging Relationships
Pegging relationships [External] can exist between the activities of different orders. An activity
therefore produces a material that then undergoes further processing by an activity of another
order. The pegging relationship requires − with a certain time tolerance − that the material be
available at the right time, that is, that the supplying activity is scheduled at the appropriate
time. You define in the detailed scheduling strategy if the system should consider pegging
relationships [Page 98] during scheduling.
Automatic Propagation of Changes

When you schedule or reschedule an operation or an order, other operations and orders are
affected, for example, due to time relationships or pegging relationships. In order that the
schedule remains consistent, subsequent rescheduling is often required. This is performed
automatically by the system. For more information, see scheduling dependent objects [Page
71].
Adjusting Setup Time

The duration of the setup activity for an operation may depend on the setup status of the
resource at the time of scheduling; that is, it depends on which operation was processed prior
to this at the resource. For set-up activities on single resources [External], the system can
automatically adjust the setup time [Page 77] during detailed scheduling.
Synchronizing Activities on Multi-Resources

Several activities can be processed simultaneously on a multi-resource [External]. How many
can be processed depends on the resource consumption [Page 68] of the activities and on
the capacity of the multi-resource. The system can synchronize the start times of the activities
[Page 79] during detailed scheduling if the duration of the activities and one further
characteristic of the activities match.
Block Planning
In block planning [External] you can define blocks [External] for resources, that is, time
periods that are reserved for production of products with particular characteristics. The

system automatically considers this during detailed scheduling and only schedules or
reschedules activities into the blocks with the corresponding characteristics.
Scheduling Log
The system collects messages that it generates in interactive scheduling or in the production
planning run in the scheduling log. You can call up the scheduling log
• In the detailed scheduling planning board under Extras
• In the Production Planning area menu under Reporting → Planning Run Reporting
Terminating Scheduling
In complex scheduling situations in which many constraints and dependencies must be
considered, the duration of scheduling can be very long. The system is set internally to
terminate scheduling after 10 minutes. You can set another maximum scheduling duration
[Page 422]. in the detailed scheduling strategy.
Alerts
In the case of scheduling problems, for example, resource overload [Page 81], the system
can create alerts that are displayed in the Alert Monitor [External]. You must use a
corresponding PP/DS alert profile [External] for this purpose.
Detailed Scheduling Activities

Use
The following detailed scheduling activities are used to
• determine dates and resources for operations
• define the schedule for resources
Detailed Scheduling Activities
Activity Use
Schedule For an operation of a newly created order or for a deallocated operation
• The resources [Page 73] are determined on which the operation should be processed
• The date is determined when the operation should be processed on the resources
With scheduling, the operation is dispatched to the resources. Scheduling an order means
scheduling all the operations of the order.
Reschedule A new date or new resources are determined for a scheduled operation.
With rescheduling, the operation remains dispatched to resources; after rescheduling, it
occupies either the previous resources or the new resources. Rescheduling an order means
rescheduling all the operations of the order.
Deallocate An operation is removed from the resource schedule.
With deallocation, the operation is given the status deallocated; the operation does not
occupy any resources. Deallocating an order means deallocating all the operations of the
order.

An operation in the SAP APO system is either scheduled − this has no specific
status − or deallocated, and has the status deallocated.
Adjust A new date or new resources are assigned to a deallocated operation.
With adjusting, the operation keeps the status deallocated, that is, the operation does not
occupy the resources to which it is assigned. Adjusting does not change any resources
schedules.
Adjusting is a detailed scheduling activity that is carried out automatically by the system for
dependent objects, for example, if relationships or pegging relationships have to be
retained. You cannot adjust deallocated operations manually.
Fix The resource and date for the operation is fixed.
With fixing, a scheduled or deallocated operation is given the status fixed. A fixed scheduled
operation cannot be rescheduled or deallocated, and a fixed deallocated operation cannot
be scheduled or adjusted.
Prerequisites
Detailed scheduling activities can be triggered by the user, or automatically by the system.
Detailed scheduling activities are usually carried out automatically by the system without any
input by the user.
Triggering Detailed Scheduling by the User

You can start detailed scheduling activities specifically for selected [Page 70] operations or
orders in the production planning run [Page 122] or in the detailed scheduling planning board
[Page 362]. To do this, there are several detailed scheduling functions [Page 404] and
detailed scheduling heuristics [Page 413] available, which carry out one or more detailed
scheduling activities according to specific criteria and, if necessary, in a specific sequence.
You can also trigger detailed scheduling activities manually using Drag&Drop [Page 405] in
the detailed scheduling planning board. For more information, see solving scheduling
problems [Page 404].
Triggering Detailed Scheduling Activities by the System

The following table shows a few cases when the system triggers detailed scheduling activities
automatically.
Activity Description
Schedule The system schedules an order automatically
• When exploding a Production Process Model (PPM) or an iPPE plan (that
is, if an order is created in the SAP APO system, if the order quantity
changes or if an order is rescheduled and the order date changes so that
the PPM or iPPE plan with which the order was created is no longer valid)
• When transferring unfixed orders from an OLTP system to the SAP APO
system
Reschedule, If the system schedules objects selected by the user, it also automatically
adjust, carries out detailed scheduling activities for all the affected dependent
deallocate operations [Page 71], so that the schedule remains consistent. For example, it
carries out rescheduling or deallocation for scheduled dependent operations,
and it adjusts deallocated dependent operations.
Fix If an operation is scheduled or rescheduled during a non-working time, the
system fixes the operation automatically.

Operations that cannot be changed or can only be changed with restrictions

If an operation has one of the following statuses, you or the system cannot make changes to
the resources and dates of the operation, or only specific changes can be made.
Status of the What you can do
operation
Finally confirmed No change can be made. The operation has already been carried out
and is therefore no longer subject to scheduling.
Started or partially The operation is in process.
confirmed
You can only reschedule the remaining capacity requirements for
operations after you have interrupted [External] the operations in the
detailed scheduling planning board.
Fixed So that the dates and resources for fixed operations can be changed
again, you must undo the fixing [Page 237] for this operation in the
detailed scheduling planning board, or in the production planning run.
You can fix [Page 237] operations in the detailed

scheduling planning board or in the production planning
run. The system automatically fixes operations that are
scheduled in non-working times [Page 92].
Calculation of the Capacity Requirements of an

Activity
Use
The capacity requirement of an activity [External] describes how much of the productive time
[External] and the capactiy of a resource is required to process an activity. Since various
resources may be necessary to process an activity, there may be several capacity
requirements for an activity (one for each resource in the mode [Page 73]). Thus, each
capacity requirement is determined through the net duration [Page 67] and the corresponding
resource consumption [Page 68] of the activity.
The system calculates the net duration, the resource consumption values and thus the
capacity requirements of an activity
• If it explodes the production process model [External] (PPM) or the iPPE plan [External],
that is:
− When an order is created
− When the order quantity is changed
− If the order date is changed so that the current PPM or the current iPPE plan is no
longer valid (see considering order validity [Page 87])
• If you confirm an operation
Here, the system determines the capacity requirements for the remaining quantities.
Integration
Based on the capacity requirements and the desired scheduling date, the system determines
the mode [Page 72] and the scheduling date for an activity during detailed scheduling [Page

62]. By doing so, the system takes into account that the resources are not available
continuously, for example, due to breaks and that the rate of resource consumption [External]
can deviate from 100 percent. Therefore, the gross duration of the activity, that is, the time
interval between the start and finish date, differs from the net duration. The working time data
and the rate of resource consumption referred to in the mode as the calendar resource, are
decisive for scheduling.
In the case of finite scheduling [Page 81], you can only schedule an activity in time intervals of
sufficient size [Page 67], in which enough capacity is available simultaneously at all the
resources required to process the activity. In the case of infinite scheduling, the system does
not consider the limited capacity of a resource; an activity can therefore be scheduled on any
date, independent of resource consumption.
Calculation of the Net Duration of an Activity

Use
The net duration of an activity is the pure working time that a resource needs to execute the
activity. Non-working times, such as breaks or maintenance phases are not included in the
net duration; for example, in particular the rate of resource utilization [External] of the
resource is assumed to be 100 percent.
The net duration can consist of a fixed part and a variable part that is dependent on the order
quantity. Frequently the duration of a setup activity is independent of quantity, while the
duration of a processing activity is dependent on quantity. The system calculates the net
duration of an activity as follows:
Net duration = Fixed duration + Variable duration x Order quantity / Output quantity
The data used in the calculation is described in the following table.

Data for calculating the net duration
Data Description
Output quantity Base quantity of the primary order product
You assigned the primary order product to an activity as the output product.
You specify the base quantity here.
Fixed duration Working time that is used for the activity, independent of the produced
quantity
Variable Working time used to produce the output quantity of the primary order
duration product (without fixed duration)
The quantity produced by an activity may differ from the order quantity:
• If scrap [Page 56] is produced, the activity must produce a correspondingly larger
quantity. In the case of resource consumption that is dependent on quantity, the resource
consumption of the activity also increases.
• The system can split an operation automatically [Page 70] when creating an order.
Integration
Net duration and the resource consumption values define the capacity requirements [Page
66] of the activity.

Prerequisites
• You have maintained the above data in the PPM or iPPE plan for the activity.
• Activities cannot have a duration of zero. Exception: During setup time adjustment [Page
77] and setup optimization [Page 227], the setup activities can have a duration of zero
according to a setup matrix during the transition between identical setup statuses.
Calculation of the Resource Consumption Values of

an Activity
Use
The resource consumption of an activity [External] is the capacity of the resource that is
necessary for the execution of the activity.
An oven has a capacity of 1000 units. The resource consumption for a tempering
activity that is executed in this oven is variable and can be between 1 and 1000
pieces, corresponding to the quantity to be produced.
To process an activity, it may be necessary to use several resources that are occupied
simultaneously by the activity. Therefore, there may be several resource consumption values
for the activity (one for each resource in the mode [Page 73]).
The resource consumption for an activity can have a fixed part that is independent of order
quantity, and a variable part that is dependent on quantity. A part dependent on quantity is
only allowed in the case of multi-resources [External]:
• Single-activity resources [External] and single-mixed resources [External] can only be
occupied by one activity at any point in time. Here the resource consumption,
independent of quantity, is equal to 1 and corresponds to the capacity of these resources.
In the case of single-resources, there is only a dependency on quantity for the net
duration of an activity [Page 67].
• Multi-activity resources [External] and multi-mixed resources [External] can process
several activities simultaneously. The resource consumption can consist of a fixed part
and a variable part, and a variable resource consumption is only allowed in the case of a
net duration independent of quantity.
The resource consumption of multi-resources can exceed the capacity of the
resource, for example, in the case of large order quantities.
− In this case, the system reduces the resource consumption by default to the value of
the standard capacity and increases the net duration of the activity accordingly. For
example, if the resource consumption is twice as large as the standard capacity of the
resource, then the system doubles the net duration of the activity. If you have not
specified a standard capacity, the resource consumption and net duration retain their
original values. The activity can therefore not be scheduled.
− To prevent exceeding the resource capacity, you can set in the production process
model that the system should automatically split an operation [Page 70] when
creating an order.
For an overview of the possible values for capacity and resource consumption for PP/DS
resource categories, see Capacity and Resource Consumption for PP/DS Resource
Categories [Page 69].
The system calculates the resource consumption values for an activity as follows:

Resource consumption = Fixed consumption

+ Variable consumption x Order quantity / Output quantity
The data used in the calculation is described in the following table.

Data for Calculating the Resource Consumption
Data Description
Output quantity Base quantity of the primary order product
You assigned the primary order product to an activity as the
output product. You specify the base quantity here.
Fixed resource consumption Capacity of the resource that is used for the activity,
independent of the produced quantity
Variable resource consumption Capacity of the resource used to produce the output quantity
of the primary order product (without fixed consumption)
The quantity produced by an activity may deviate from the order quantity: If scrap
[Page 56] is produced, the activity must produce a correspondingly larger
quantity. In the case of resource consumption that is dependent on quantity, the
resource consumption of the activity also increases.
Integration
Net duration and the resource consumption values define the capacity requirements [Page
66] of the activity.
Prerequisites
You have maintained the above data in the PPM or iPPE plan for the activity.
Capacity and Resource Consumption for PP/DS

Resource Categories
The following table shows the possible values for capacity and resource consumption [Page
68] for the resource types you use in PP/DS for planning in-house production. For the single-
mixed [External] and multi-mixed resources [External], for which you define a time-specific
capacity and a period-specific capacity, and which are therefore used in both PP/DS and
SNP, only the time-specific capacity relevant to PP/DS or the resource consumption relevant
to PP/DS is described.
Possible values for capacity and resource consumption for PP/DS resource types
Resource Type Description Capacity Resource Consumption
Fixed Variable

Single-activity Can only process one 1 1 Not possible

resource activity at a time
[External]
Single mixed
resource
[External]
Multi-activity Can process several Value in any unit of Value and unit Only possible
resource activities measurement of for fixed
[External] simultaneously. measurement activity
To represent a machine
Activities share the of the required duration [Page
Multi-mixed group, enter a whole
resource’s capacity capacity 67]
resource number without a unit of
[External] measurement for the
number of machines.
Splitting Operations
Use
The system can split an operation automatically when creating an order, if the quantity of the
main order product to be produced exceeds the operation split quantity. In this case, the
system divides the order quantity into the operation splitting quantities (plus the remainder, if
necessary) and creates capacity requirements [Page 66] for these partial quantities for the
activities of the operation. The system can schedule these capacity requirements on the
alternative primary resources [Page 73] of the operation, depending on the capacity situation.
You use splitting, for example,
• If an operation is processed on a multi-activity resource and the activities of the operation
have a quantity-dependent resource consumption [Page 68]
If the order quantity is too large, the capacity of the multi-activity-resource may be
exceeded. You can systematically avoid such situations by using splitting.
• If the activities of an operation have quantity-dependent activity durations
In this case an order quantity that is too large can lead to a long operation duration
that, may make it impossible to produce the order on time.
Prerequisites
You have specified an operation splitting quantity in the production process model, for the
operations to be split.
Selecting Objects to be Scheduled

Use
You can select activities, operations or orders that you wish to schedule [Page 64] as follows:
• By selecting the objects [Page 378] in the detailed scheduling planning board [Page 362]
• By specifying the objects in the production planning run [Page 122]
By selecting a specific object you can automatically choose more objects, as follows:
• By selecting an order, you select all operations in that order.

• By selecting a resource, you select all the operations on the resource whose start date
occurs in the planning period [Page 85].
• By selecting an activity in the detailed scheduling planning board, you select the complete
operation.
When you create an order in the SAP-APO System or transfer an order to the SAP-APO
System, the selected orders are the order and its component orders.
So that the scheduling remains consistent − according to your detailed scheduling

strategy [Page 82] − the system does not only schedule the selected objects, but
also automatically schedules more objects:
• If you schedule with an insert scheduling mode [Page 89], the system must move
operations to a resource in order to create slots for an operation to be inserted, or to
close gaps.
• If you have defined that time relationships [Page 97] or pegging relationships [Page 98]
are to be retained, the system must also schedule or reschedule dependent objects
accordingly.
Scheduling Dependent Objects

Use
The following time or resource-related dependencies can exist between operations:
• Pegging relationships [Page 98]
• Time relationships [Page 97]
• Linking of modes [Page 75]
If an operation is scheduled or rescheduled, further dependent operations may be affected
by these dependencies. Further detailed scheduling activities [Page 64] that the system can
carry out automatically, are often necessary for these dependent operations so that the
scheduling remains consistent, for example, so that time relationships are not violated.
Features
Controlling Detailed Scheduling for Dependent Operations
You control the scheduling of dependent operations using the detailed scheduling strategy
[Page 82]. For example, you can set the following:
• Whether the system must retain time relationships or pegging relationships during
scheduling
• Which detailed scheduling activities the system should carry out for already scheduled
dependent operations, in case relationships are violated
You have the following options in the scheduling submode [Page 95]:
− Deallocating dependent operations
− Rescheduling dependent operations infinitely
− Rescheduling dependent operations finitely with the defined scheduling mode [Page
89]
If necessary, the system adjusts deallocated dependent operations.
For more information on further control options, see settings for dependent objects [Page 95].

Scope of Scheduling
The following operations may have dependent operations, which the system must consider
during scheduling:
• Operations selected for the scheduling [Page 70]
• Operations on the resources on which the selected operations were scheduled or
rescheduled
If you schedule or reschedule a selected operation on a resource using a finite insert
scheduling mode [Page 89], the system shifts the operations on the resource to
create a gap for the selected operation or to close gaps, if necessary. The shifted
operations may have dependent operations that the system must also reschedule or
deallocate as required.
• Dependent operations
A dependent operation can also have dependent operations; this may mean that
there is a chain of rescheduling.
For detailed scheduling in the detailed scheduling planning board [Page 362] and in the
production planning run [Page 122] you can use the propagation range [Page 111] to restrict
the resources on which the system can carry out detailed scheduling activities, for example,
for dependent operations.
Compact Scheduling
In order to achieve scheduling with as few time intervals as possible between the operations
of an order, you can implement compact scheduling [Page 103].
Example
For an example of finite rescheduling of a selected operation and its dependent operations,
see scheduling dependent operations according to the scheduling mode [Page 96].
Mode Selection
Use
In the production process model (PPM), you can assign several modes [Page 73] to an
activity, that is, several sets of alternative resources on which the activity can be processed.
With linking of modes [Page 75], selecting a mode for one activity also specifies the modes
for all the activities to which there are time relationships. This is particularly valid for the
activities of an operation that are always processed on the same primary resource (mode
linkage via the primary resource).
Mode selection during scheduling can be performed either manually by the user, or
automatically by the system, as follows:
• Manual Mode Selection in the Detailed Scheduling Planning Board
An operation is already assigned in certain mode in the detailed scheduling planning
board [Page 362]. You can select another mode for the operation by shifting the
operation to the primary resource of the desired mode using Drag&Drop.
You can use manual mode selection if you
− Schedule or reschedule operations and orders using Drag&Drop [Page 406]
− Deallocate an operation using Drag&Drop [Page 412]
You can use modes of all priorities [Page 75] when using manual mode selection for
operations.

• Automatic Mode Selection

The system selects the mode automatically
− When an order is created
− When you schedule a deallocated operation with the scheduling function reschedule
[Page 410]
− When the system reschedules a scheduled dependent operation or adjusts the dates
for a deallocated dependent operation, because time relationships [Page 97] or
pegging relationships [Page 98] to other operations have to be retained.
With automatic mode selection, the system can use modes with priorities [Page 75] A
to O. It automatically selects the mode with the highest priority for the operation, and
can thus − depending on the scheduling direction [Page 86] − do the following, where
possible:
− Close the operation as early as possible with forward scheduling
− Start the operation as late as possible with backward scheduling
You can restrict the automatic mode selection using the detailed scheduling strategy
[Page 103].
Mode assignment of an operation usually remains
− When a selected operation is rescheduled with the scheduling function Reschedule or
with a detailed scheduling heuristic [Page 413]
− When an insert scheduling mode [Page 89] (insert operation [Page 90], squeeze in
operation [Page 92] or insert operation and close gaps [Page 91]) is defined, and an
operation is rescheduled by the system to a resource in order to make room for an
operation to be inserted or to close gaps in the schedule.
− When an operation is deallocated by the system [Page 412]
Exception: When deallocating a dependent operation using the scheduling
submode [Page 95] deallocated dependent operations a linking of modes can
force a change of modes.
Prerequisites
You have maintained more than one mode for each activity in an operation in the PPM. If you
only define one mode for an activity, the operation can only be assigned to this mode.
Mode
Definition
Set of resources used for performing an activity [External].
Use
In the mode, you define:
• The duration of the activity.
• The capacity used by the activity (resource consumption).
During scheduling, the system uses this data and the quantity to be produced to calculate the
duration [Page 67] of the activity and the consumption of resources [Page 68] (capacity
requirements). An activity occupies all the resources of the mode simultaneously. That is, it
has the same start and finish date on all resources.

To represent alternative processing variants, you can assign several modes to an activity and
then define various priorities [Page 75] for these modes. In the detailed scheduling planning
board, you perform mode selection [Page 72] manually. With automatic mode selection (for
example, when creating an order), the system selects the mode automatically according to
priority and the availability date.
Structure
A mode contains exactly one primary resource, and − optionally − several secondary
resources. Each resource may appear only once in a mode. You define one of the resources
as a calendar resource. The system uses the calendar of the resource when scheduling the
activity. The various functions of the resources in the mode are described below:
Resource Description
Primary resource The primary resource may be a resource that is particularly important for
processing the activity and for your schedule (it may be a bottleneck, for
example). You therefore want to schedule it as detailed as possible, that is, by
using the full PP/DS functionality. The following PP/DS functions are only
possible for primary resources:
• Functions for a sequence-dependent setup on the basis of a setup matrix
[Page 77] (setup adjustment [Page 77], setup optimization [Page 227]).
• Block Planning [External]
• Campaign planning [Page 424]
• Synchronization [Page 79] of activities to multi-resources.
Secondary You can use the secondary resources, for example, to represent various tools
resource that are required in addition to the tools of the primary resource to execute the
activity.
The functions listed under the primary resources cannot be used for the
secondary resources. For example, you cannot execute a sequence-dependent
setup for a secondary resource nor can you execute block planning. Therefore,
you cannot use a resource as a secondary resource for a mode:
• To which a setup matrix has been assigned
• For which blocks [External] have been defined.
Calendar resource The system uses the working times and non-working times of the calendar
resource for scheduling the activity, that is, the working and non-working times of
the calendar resource are decisive for all resources in the mode and overwrite
the calendar of the resources. When scheduling, the system uses working and
non-working times to search for an appropriate scheduling date on the primary
resource on which the activity can be processed on the primary resource and on
the secondary resources simultaneously. As only the calendar resource is used,
the duration of the activity is the same on all resources.
Integration
If you want to make the mode selection for an activity dependent on which mode is used for
an activity of another operation, you can link the modes for these activities. Mode-linked
activities cannot be scheduled on random modes independently of each other. This is
particularly valid for the activities of an operation that are always processed on the same
primary resource (mode linkage via the primary resource). For more information, see Linking
of Modes [Page 75].

Mode Priority
Definition
The rank of a mode [Page 73] within the group of modes assigned to an activity.
Use
You can define several modes for an activity, that is, several sets of resources on which the
activity can be carried out. In general, these alternatives are not of equal value. For example,
you may want to load a fast, expensive machine more than you want to load the slower,
inexpensive replacement machine. This means you have to assign priorities to the modes: A
mode with priority A has the highest priority (for example, the special machine), a mode with
priority B has the next highest priority (for example, the replacement machine), and so on up
to priority O. Various modes can have the same priority. With automatic mode selection
[Page 72] (for example, when creating an order), the system selects the mode automatically
according to priority and the availability date.
You assign priority Z to the modes you only want to schedule manually in the DS planning
board. You manually schedule the resources you only want to use in exceptional situations for
production (test or training machines). You can schedule modes of all priorities manually in
the DS planning board.
Linking of Modes
Use
With automatic mode selection [Page 72] (for example, when creating an order) the system
selects the mode [Page 73] for an activity automatically according to the mode priority [Page
75] and the availability date. However, you can also define that the mode to be selected for an
activity depends on which mode has already been selected for another activity. The following
link categories are available:
• Linking modes with the same mode name
You can only use this link category to link activities from different operations.
• Linking modes with the same primary resource
This link category is mandatory for linking the activities of one operation. You can
also use this link category to link activities that belong to different operations.
An operation is a simple, open chain of activities that are all processed on the
same primary resource and that are linked by start and end dates. Every activity
– with the exception of the last one – can only be followed by one further activity
within the operation. The last activity may not have a follow-on activity in the
operation. No other operation can be scheduled between the activities of an
operation.
Prerequisites
You have to make the following settings in the production process model (PPM) to link the
modes of two activities when scheduling:
• To link modes with the same name, you must:

− Create a relationship between the activities that have to belong to several operations
and assign the link category 3 (same mode number) to this relationship.
− Define at least one mode with the same name for each of the activities.
− Assign the same priority to the linked modes
The system can automatically schedule modes with priorities A to O. You cannot
use the mode link functions for modes that are only scheduled manually (mode
priority Z).
• To link modes with the same primary resource, you must:
− Create a relationship between the activities and assign the link category 2 (same
primary resource) to this relationship.
The system automatically activates the primary resource link in the operation
when you create the mandatory start and end relationship between the activities
of an operation.
− Define at least one mode with the same primary resource for each one of the
activities.
In the operation, all activities must have at least one mode with the same primary
resource.
− Specify the same resource consumption for the primary resource in the modes to be
linked if the primary resource is a multi-resource.
The same resource consumption is only required when linking to multi-activity
and multi-mixed resources. In the case of single-activity and single mixed
resources, the activity always uses the complete resource. That is, the resource
consumption is always 1 for single-activity resources.
− Assign the same priority to the linked modes
The system can automatically schedule modes with priorities A to O. You cannot
use the mode link functions for modes that are only scheduled manually (mode
priority Z).
Restrictions for automatic mode selection

Use
With automatic mode selection [Page 72] the system determines modes [Page 73] for the
operation. The following options are available in the detailed scheduling strategy [Page 82] for
restricting the mode selection:
• The system may only use modes with a minimum priority [Page 75]
If, for example, you enter B as the minimum priority, the system can only use
modes with priority A or B for an operation.
You can select any modes for an operation in manual scheduling with Drag&Drop
[Page 405].
• The system must keep the mode for dependent operations.
Linking of modes overrides these restrictions.

Adjusting Setup Time

Use
The duration of the setup activity of an operation can depend on the setup status of the
resource at the date when the operations is scheduled or rescheduled. The duration therefore
depends on which operations were previously processed on the resource. When scheduling
or rescheduling an operation at a single-activity resource [External] or at a single mixed
resource [External], the system automatically adjusts the duration of the setup activities for
the operation to be scheduled or rescheduled to that of its predecessor.
Prerequisites
In order for the system to adjust the setup times for the operations at a single resource
[External] depending on sequence, the following conditions must be fulfilled:
• You use the single resource in the production process models (PPM) exclusively as a
primary resource (see Mode [Page 73]).
• You have defined a setup matrix [Page 77] for the location.
• You have assigned the setup matrix to the single resource in resource maintenance.
• You have maintained the following data in the PPM for operations that are to be setup at
the single resource depending on sequence.
− You defined the necessary setup status [External] for processing the operation by
assigning a setup group [External] or a setup key [External] to the operation.
− You defined a setup activity for the operation.
An operation can only consist of one setup activity.

When an operation contains several activities, the setup activity must be the first
activity for the operation. The setup activity can only have a relationship to one
subsequent activity in the operation.
− You set the Setup activity indicator for the setup activity.
During setup time adjustment, the system only interprets an activity as a setup
activity with a duration dependent on sequence when the Setup activity indicator
is set for the activity. It is therefore not sufficient to define a setup activity that is
dependent on sequence by assigning an activity the activity type S (Setup). In the
case of setup activities for which you do not set the indicator, the system uses the
setup time from the mode [Page 73], and not from the setup matrix; that is, the
duration of the setup activity is constant and is not dependent on the sequence.
Setup Matrix
Definition
A matrix that contains, for each possible setup transition [External] at a single resource
[External], the setup duration and the setup costs that are necessary to change the setup
status [External] of the resource to another setup status.

Use
You can use a setup matrix to model setup times and setup costs for a single resource that
are dependent on sequence. Based on the setup matrix, the system can do the following:
• Execute a setup time adjustment [Page 77] automatically during detailed scheduling for
the setup activities
• Determine optimal operation sequences based on setup time or setup costs during
optimization [Page 227]
• Determine the production process model for creating a setup and cleaning order during
campaign optimization [Page 232]
Setup time adjustment and setup optimization can only be applied to single
resources that are used exclusively in the modes [Page 73] of the production
process model as a primary resource.
A setup matrix is only valid for a particular location.
Structure
Setup transition types
A setup status is defined in the setup matrix either by a setup group [External] or by a setup
key. The following types of setup transition are possible:
• Standard setup transitions
Here you characterize the preceding setup status as well as the subsequent setup
status in the setup transition using a setup group.
• Exceptional setup transitions
Here you characterize at least one of the setup statuses using a setup key.
You can only define an exceptional setup transition as an exception to the standard
setup transition in the setup matrix. The setup groups for this standard setup
transition must contain the setup key for the exceptional setup transition.
Setup groups and setup keys − as in the case of the setup matrix − are only valid for a
particular location.
Completeness of setup matrix

The setup matrix must contain all setup transitions that can occur at the resource. You do not
have to define each setup transition explicitly. Using an asterisk (*), which you enter in a
setup transition instead of a setup group, you can define generic setup transitions in the
setup matrix. However, the asterisk (*) only replaces the setup groups that you also use in the
setup matrix explicitly to define setup transitions, and not all setup groups that you defined for
the location.
Using the setup groups A, B, C and the setup key a, you have defined the
following setup transitions in the setup matrix: AB, AC, Aa.
Using a setup transition ** in the setup matrix, you include the following setup
transitions: AA, BA, BB, BC, CA, CB, CC. These are the missing combinations for
the setup groups used explicitly in the setup matrix. If you have also defined the
setup groups D, E and F in the location, the setup transitions with these setup
groups are not included when using the generic setup transition **. You have only
explicitly used the setup groups A, B and C in the setup matrix.

By entering a setup transition *a, you are including the following setup transitions:
Ba, Ca. These are the missing transitions for the setup groups used explicitly in
the setup matrix according to setup key a.
Initial setup statuses

It can happen that the setup status of the resource is not defined at the point in time when you
schedule an operation at this resource. This happens, for example, in the Detailed Scheduling
planning board [Page 362] if you reschedule an operation at the start of the planning period
and no operation has been scheduled in the display period before this. Here, the setup status
of the resource is not defined for the system because no operation has yet been processed
on it. In such cases, you can enter setup transitions in the setup matrix between an initial
setup status for the resource and the possible setup statuses. You define such transitions by
not entering a setup group or a setup key for the preceding setup status.
For performance reasons, it is recommended that you define setup matrices

that are as small as possible, with only a few setup transitions. Therefore, you
should do the following:
• Classify the setup transitions using setup groups and setup keys only to a degree of detail
that is necessary
• Use as few exceptional setup transitions as possible
Transfer of Setup Keys, Setup Groups, and Setup Matrices

Using the following report, you can transfer these objects from one APO system to an other
APO system:
Report Transfer from

/SAPAPO/SETUP_GROUP_COPY Setup groups and setup keys
/SAPAPO/SETUP_MATRIX_COPY Setup matrices
A prerequisite for a successful transfer is that the locations for which these objects were
created are available in the target system. This is also valid for the plan numbers which you
can specify in the setup matrices for campaigns. These plan numbers must also exist in the
target system. You define the target system by specifying the RFC destination of the system.
Synchronizing Activities on Multi-Resources

Use
Using the synchronization procedure, the system creates blocks of activities on a multi-activity
resource [External] or on a multi-mixed resource [External] during the scheduling process.
These blocks can be processed simultaneously as they are of equal length and they also
have a further common characteristic. The blocks are created as the system schedules each
activity to be newly scheduled on the multi-resource as follows:
• If the desired start or finish date [Page 94] of the activity lies between the start and finish
date of an activity that is already scheduled, is of the same length and has a further
common characteristic, the system schedules the activity on the start date of this activity,
if sufficient capacity exists.

• If there is not sufficient capacity available on this date, the system schedules the activity
to be scheduled before the activity already scheduled in the case of backward scheduling
or after the activity already scheduled in the case of forward scheduling. In both cases, no
overlapping is allowed.
The system always schedules activities with different lengths or with different characteristics
with no overlaps.
For example, using the synchronization procedure, you can represent the loading
of an oven. You can describe an over as a multi-activity resource. As the oven
can only be filled or emptied all at once, it has to be completely filled with
products that have to be kept at the same temperature for the same length of
time. Therefore, you can only schedule baking activities with the same duration
and which have to be carried out at the same temperature. Baking activities that
require either a different duration or which require the oven to be set to a different
temperature can only be carried out either before or afterwards and overlapping
is not allowed.
Prerequisites
The following prerequisites must be fulfilled for the system to synchronize the schedule of a
multi-activity resource:
• You only use the multi-activity resource in the modes [Page 73] of the activities as the
primary resource.
• In the production process model, you must assign a setup key or a setup group to every
operation to be carried out on the multi-resource.
Using the setup key or the setup group, you assign a certain characteristic value (for
example, a certain temperature) to the activities of an operation. The same setup
keys or setup groups mean the same characteristic values, for example, the same
temperature. Different setup keys or setup groups mean different characteristic
values, for example, different temperatures.
Note that the setup key for multi-resources is used differently than the one for
single resources [External].
• For single resources, the setup key [External] or the setup group
[External] classifies the setup status [External] of the resource. The
system evaluates the setup status of the resource during setup
adjustment [Page 77] or during setup optimization [Page 227] using the
setup matrix [External].
• For multi-resources, the setup key or the setup group represents any
value of a characteristic (for example, a certain temperature) you want to
use to synchronize activities.
Controlling Detailed Scheduling

Use
You control which constraints, rules, and parameters the system must consider during
scheduling [Page 62] using the settings and data in the following objects:

Object Settings for detailed scheduling

PPM For example, here, you specify for each activity [External] along with the resource
[External] consumption [Page 68] and the activity duration [Page 67] (per basic unit of the main
order product):
iPPE Plan
[External] • Whether time relationships exist between the activities [External] of different
operations
• How long the minimum and maximum permissible time intervals between the
activities are
• Whether activities can be interrupted by non-working times (for example, breaks)
Resource For example, here you specify, in addition to the working and non-working times:
[External]
• How high the rate of resource utilization [External] is
• Whether the resource is a multi-resource [External] or a single-resource [External]
• Whether the resource is to be scheduled finitely or infinitely [Page 81]
You can change the scheduling data for the resources in interactive detailed scheduling
with the detailed scheduling planning board [Page 360].
Strategy Here you define the detailed scheduling strategy [Page 82] with which the system
profile [Page performs detailed scheduling, for example,
419]
• In which planning direction [Page 86] the system searches for a scheduling date
• Whether the system schedules or reschedules activities finitely or infinitely [Page 81]
on the resources
• With which scheduling mode [Page 89] the system schedules the resource with finite
scheduling of operations, for example, by insertion [Page 90] in the existing
schedule.
• Whether the system must consider the product availability (pegging relationships
[Page 98])
• Whether the system must retain time relationships between operations [Page 97]
You generally use different strategy profiles, specific to each scheduling problem, for the
various applications in Production Planning and Detailed Scheduling. In interactive
scheduling [Page 306], you can change the strategy settings at any time by choosing
Settings.
Finite and Infinite Scheduling

Use
You can define whether the system is not allowed to exceed the capacity of the resource
(finite scheduling), or whether it can schedule any number of operations simultaneously on
a resource (infinite scheduling) during detailed scheduling [Page 62] . When performing
finite or infinite scheduling, you must select a corresponding scheduling mode [Page 89] in
the detailed scheduling strategy [Page 82] and define in the resource whether the resource
should be scheduled finitely or infinitely.
A resource overload [External] which can be displayed in the alert monitor [External] for finite
resources can result from the infinite scheduling. You must use a corresponding PP/DS alert
profile [External] for this purpose. In the resource, you define the maximum duration of a
resource overload [External] before the system recognizes it as such and generates an alert.

The following table provides a summary of how the system behaves in the event of a finite or
an infinite resource when you use a finite or infinite scheduling mode.
Finite Scheduling Mode Infinite Scheduling Mode
Finite Resource The system considers the resource The system does not consider the
load. It executes scheduling only resource load.
when there is sufficient capacity.
The system creates alerts in the case
The system creates alerts in the of resource overload.
case of resource overload.
Infinite Resource The system does not consider the resource load.
The system does not create alerts in the case of resource overload.
Detailed Scheduling Strategy

Definition
A record of settings that control the detailed scheduling [Page 62] of operations and orders in
Production Planning and Detailed Scheduling.
Use
Using the detailed scheduling strategy, you specify which rules and constraints the system
uses to determine dates and resources for orders and operations, and which scheduling
constraints (for example, product and resource availability) it considers when doing this.
Additional operations may be affected by the scheduling or rescheduling of an operation that
you have selected specifically for scheduling [Page 70]. In order that the schedule remains
consistent, the system must also schedule or adjust [Page 64] these operations accordingly.
Scheduling or rescheduling of an operation can therefore trigger a chain reaction of detailed
scheduling activities for the objects concerned.
You reschedule an urgent operation to another date, on which the resource is

already occupied.
• If you have defined an insert scheduling mode [Page 89] in the detailed scheduling
strategy, the system must move the operations on the resource to create a slot for this
operation (scheduling mode insert operation [Page 90]), and to close the newly created
gaps (scheduling mode inserting an operation and closing gaps [Page 91]).
• If you have defined in the detailed scheduling strategy that the system must retain time
relationships [Page 97] or pegging relationships [Page 98] to the dependent operations
[Page 71] when rescheduling the operations and the neighboring operations, the system
must then reschedule the dependent operations so that these relationships are not
violated.

Structure
You can use strategy settings to control both the scheduling of the selected operations, and
the subsequent rescheduling of the affected operations. You can divide the strategy settings
into the following groups accordingly:
• Settings for Selected Operations [Page 88]
• Settings for Dependent Operations [Page 95]
• General Settings [Page 85]
Definition of Detailed Scheduling Strategies

Use
You maintain detailed scheduling strategies [External] in a strategy profile. You generally use
different strategy profiles, specific to each scheduling problem, for the various applications in
Production Planning and Detailed Scheduling. When transferring orders from an OLTP
system you use, for example, a strategy profile with “soft” settings, to ensure that the
scheduling will succeed. For specific interactive scheduling with the detailed scheduling
planning board [Page 362] you use strategy settings that are customized specially for the
resources to be scheduled.
Features
You can define several detailed scheduling strategies in a strategy profile, that is, you can
define several records of strategy settings. If scheduling or rescheduling using a strategy fails,
the system can switch to the next strategy, and so on. In the strategy profile, you define,
• Which strategies the system is allowed to use in the strategy profile (by marking the
permitted strategies as active)
• The sequence in which the system should use the active strategies (by numbering the
strategies)
The active strategy with the smallest number has the highest priority. The system uses this
strategy first. If it is not successful, the system uses the active strategy with the next highest
number, and so on. If the system is unable to perform scheduling or rescheduling with any of
the strategies, it simply does not perform either function.
Activities
You maintain strategy profiles in Customizing for Production Planning and Detailed
Scheduling or in the area menu for Production Planning under Environment → Current
Settings.
The following table is a compilation for background scheduling and interactive scheduling,
where you define the strategy profile for the various applications of production planning. In
interactive scheduling, you can change the strategy settings of the active strategy profile
interactively.
Strategy settings for background planning
Application Customizing
Scheduling orders in the production planning You enter the strategy profile that the system should
run [Page 122] with product-specific heuristics use for the respective application in Customizing for
Production Planning and Detailed Scheduling under
Scheduling orders transferred from the R/3 Maintain Global Parameters and Default Values.
System [Page 112]

Scheduling orders during the Capable-to-

Promise process [External]
Scheduling orders during conversion of SNP
orders to PP/DS orders [Page 114]
Scheduling BAPI transferred orders
Scheduling or rescheduling operations and Change the strategy settings for the DS heuristics in
orders with detailed scheduling heuristics the Customizing for Heuristics.
[Page 413] (DS heuristics) in the production
planning run
Strategy Settings for Interactive Scheduling
Application Customizing Interactive Change

Scheduling and rescheduling You enter the strategy profile Choose another strategy profile or
orders in the in Customizing for Production change the setting for the active
Planning and Detailed profile under Settings → Strategy.
• Order processing view Scheduling under Maintain
[Page 309] Global Parameters and Default
• Product planning table Values in the field Interactive
[Page 324] scheduling.
• Detailed scheduling
planning board called up in
order processing [Page
385]
the product planning table
[Page 386]
Scheduling and rescheduling You enter the strategy profile • You can specify the strategy
operations and orders in the in the overall profile for the profile of your choice when
directly called up DS planning detailed scheduling planning calling up the detailed
board [Page 384] (manually board. You define overall scheduling planning board.
[Page 405] or with the profiles in Customizing for
reschedule [Page 410] Production Planning and • Choose another strategy
planning function). Detailed Scheduling or in the profile or change the settings
area menu for Production for the active profile under
Planning under Environment Settings → Strategy in the
→ Current Settings. detailed scheduling planning
board. You can also change
the settings for the active
strategy profile using the
buttons in the detailed
scheduling planning board.
Scheduling and rescheduling Change the strategy settings Choose the required heuristic and
of operations and orders with for the DS heuristics in the change the strategy settings
DS heuristics [Page 413] in the Customizing for Heuristics. under Settings → Heuristics.
DS planning board
If you change a strategy setting, the system immediately takes the changed settings into
consideration for your subsequent scheduling activities.

General Settings
Definition
Settings in the detailed scheduling strategy [Page 82],
• that affect detailed scheduling [Page 62] in general, for example, the maximum
scheduling duration [Page 422]
• that are valid for all operations that are scheduled or rescheduled, for example, the
planning direction [Page 86]
Specifying the Planning Period

Use
The following application-specific time conditions exist for detailed scheduling:
• A planning period in which the schedule can be changed, that is, in which operations and
orders can be scheduled, rescheduled or deallocated
• An earliest possible start date for which an operation or order can be scheduled or
rescheduled
• A latest possible date for which an operation or order can be scheduled or rescheduled
The following table compiles the planning period, and the earliest and latest scheduling dates
for different applications in Production Planning and Detailed Scheduling.
Application Earliest Possible Start Latest Possible Planning Period

Date Date
Manual and automatic creation Today’s date plus or 31.12.2730 at Period between the
and rescheduling of orders in minus the offset time 23:59:49 earliest and latest
the APO System [External] date
This date is the
Transfer of orders to the APO You define the offset latest possible end
System time in the detailed date for an
scheduling strategy operation.
Conversion of Supply Network
[Page 419].
Planning orders to PP/DS
orders
Detailed scheduling planning The later of the End of the planning You define the
board in order processing [Page following dates: period planning period in the
385] time profile. You can
• Today’s date plus This date is the
only reschedule
Directly called detailed or minus the offset latest possible start
those operations that
scheduling planning board time date for an
begin in the planning
[Page 384] operation.
• Start of the period.
Detailed scheduling heuristics planning period
[Page 413]
Production planning run [Page
122]

Product planning table [Page The later of the End of the planning You define the
324] following dates: horizon planning horizon
when calling up the
Detailed scheduling planning • Today’s date plus product planning
board in the product planning or minus the offset table.
table [Page 386] time
• Start of the
planning horizon
You maintain time profiles in Customizing for the detailed scheduling planning board or in the
area menu for Production Planning under Environment → Current Settings.
Specifying the Planning Direction

Use
You use the planning direction to control the direction in which the system − starting at the
desired scheduling date [Page 94] − searches for a scheduling date for an operation or order.
The system only searches in the planning period [Page 85], that is, depending on the
planning direction up to the earliest possible or latest possible scheduling date.
You have the following possible planning directions:
• Planning direction forwards
• Planning direction backwards
• Planning direction forwards with reverse
• Planning direction backwards with reverse
Planning Direction with Reverse

If the system does no find a scheduling date up to the earliest or latest possible scheduling
date in the planning direction, it switches the planning direction and tries to schedule the
operation or order as close as possible to the desired date in the other planning direction. If
this is not possible, the system does not execute scheduling or rescheduling.
The availability date of the order product is decisive when creating orders. Here you typically
select the planning direction backwards with reverse in order for scheduling to succeed. The
default date for the reversal of the planning direction is the current date plus or minus the
offset time. If you create an order manually, you can specify a reversal date.

Specifying the Maximum Scheduling Duration

Use
The system cancels scheduling or rescheduling of operations or orders by default after a
certain number of scheduling steps (corresponding to a scheduling duration of approximately
10 minutes). This can occur when the system has to consider many dependencies during
scheduling or rescheduling; for example, relationships between operations. The maximum
scheduling duration refers to the scheduling or rescheduling of the selected operations [Page
70] and to all necessary subsequent rescheduling. If the system cancels scheduling, no
operations or orders are scheduled or rescheduled.
You can set another maximum scheduling duration in the detailed scheduling strategy [Page
82].
Considering Order Validity

Use
In the detailed scheduling strategy [Page 82], you can define whether the system should
consider the validity period of the order [Page 87] during scheduling and rescheduling.
Features
You have the following options:
• Consider the validity periods
If you select this option, the system must consider the validity periods both for the
order that is to be scheduled or rescheduled, as well as for the dependent orders that
are linked to the order by means of pegging relationships (component orders and
recipient orders). It is not possible to schedule or reschedule orders outside their
validity periods.
• Consider validity periods for dependent orders only
If you select this option, the system does not need to consider the validity periods for
the order that is to be scheduled or rescheduled; the order can therefore be
scheduled outside of its validity period. In the case of dependent orders however, the
system must consider the validity periods (assuming that you have configured the
strategy profile in such a way that pegging relationships must be considered).
• Do not consider the validity periods
If you select this option, the system does not have to consider any validity periods.
If the validity period of an order is violated during scheduling or rescheduling, the system
generates a corresponding message. The system performs a plan explosion using the
production process model or iPPE valid at this time in the order processing view [Page 309]. It
does not perform a plan explosion in the detailed scheduling planning board [Page 362].
Determination of the Validity Period of an Order

Use
The system determines the validity period of an order during the explosion of the iPPE plan
[External] or the production process model [External] (PPM). When determining the validity

period, the system considers the validity periods for the iPPE plan itself, the components, and
the activities for an order that was created on the basis of an iPPE plan. For an order based
on a production process model, the system considers the validity periods for the order
products and for the components.
The following table shows when an order lies within the validity period.
Schedule Validity period for the order
PPM Start or finish dates of selected activities for the order lie within the validity
period.
You specify in the PPM on the activity level which activities and activity dates are
decisive.
iPPE Plan The start date of the first activity for the order lies within the validity period.
Integration
In the detailed scheduling strategy [Page 82], you can define whether the system should
consider the validity period [Page 87] of the order during scheduling or rescheduling.

Use
[Page 405].
Settings for Selected Operations

Definition
Settings in the detailed scheduling strategy [Page 82] that control the scheduling or
rescheduling [Page 62] of the selected operations [Page 70]:
• Scheduling Mode [Page 89]
• Scheduling in Non-Working Times [Page 92]
• Scheduling Sequence [Page 94]
• Desired Scheduling Date [Page 94]

Scheduling Mode
Use
Using the scheduling mode, you define how the system schedules or reschedules a selected
operation [Page 70] on a resource. You can schedule finitely or infinitely [Page 81] on a
resource. The following finite and infinite scheduling modes are available for this purpose:
Scheduling Mode Description Type Can be used for

Infinite scheduling Schedules or reschedules an operation Infinite Infinite and finite
[Page 89] without considering the resource load on resources
the desired date [Page 94]
Searching for a Searches for a sufficiently large slot with Finite Finite resources
slot [Page 90] sufficient capacity for an operation
Adding an Adds an operation at the end of the
operation at the schedule
end [Page 90]
Inserting an Inserts an operation as close to the Finite Finite Single-
operation [Page desired date as possible in the existing activity resources
90] schedule and shifts neighboring [External]
operations that lie in the planning
direction [Page 86] if necessary
Inserting an Inserts an operation and subsequently
operation and closes gaps in the schedule
closing gaps
[Page 91]
Squeezing in an Inserts an operation on the desired date
operation [Page in the existing schedule and shifts
92] neighboring operations in both directions
if necessary
Using the Finite Scheduling indicator, you specify in the scheduling parameters
for the resource whether that resource is finite or infinite. In the case of infinite
resources, the system always schedules or reschedules an operation infinitely on
the desired date [Page 94], that is, without considering the existing resource load.
You control how the system reschedules dependent operations [Page 71] using the
scheduling submode [Page 95].
Infinite Scheduling
Use
You can use this infinite scheduling mode [Page 89] to schedule or reschedule an operation
directly on the desired date [Page 94] without considering the resource load. You can use this

scheduling mode for both finite and infinite resources For more information on finite and
infinite scheduling modes and resources, see Finite and Infinite Scheduling [Page 81].
Features
If the desired date falls in a non-working time, the system automatically shifts the operation to
the next possible date in the planning direction [Page 86].
A resource overload [External] which can be displayed in the alert monitor

[External] for finite resources can result from the infinite scheduling of an
operation. You must use a corresponding PP/DS alert profile [External] for this
purpose.
Searching for a Slot

Use
You can use this finite scheduling mode [Page 89] to schedule or reschedule an operation −
from the desired date [Page 94] − in the first slot in the planning direction [Page 86] that is
sufficiently large and in which sufficient capacity is available. You can only use this scheduling
mode for resources that are to be finitely scheduled. For more information about finite and
infinite scheduling modes and resources, see Finite and Infinite Scheduling [Page 81].
Adding an Operation at the End of the Schedule

Use
The finite scheduling mode [Page 89] allows you to add an operation at the last operation on
a resource, independently of the set planning direction [Page 86].
You can only use this scheduling mode for resources that are to be finitely scheduled. For
more information about finite and infinite scheduling modes and resources, see Finite and
Infinite Scheduling [Page 81].
Inserting an Operation
Use
You can use this finite scheduling mode [Page 89] to insert an operation in an existing
schedule on (or as close as possible to) the desired date [Page 94], even when in the
schedule for this date there is no slot, or just a slot that is too small. If necessary, the system
creates a slot that is large enough by shifting the neighboring operations that lie in the
planning direction [Page 86] onto the resource.
You can only use this scheduling mode for single-activity resources [External] that are to be
finitely scheduled. For more information on finite and infinite scheduling modes and
resources, see Finite and Infinite Scheduling [Page 81].

Features
When inserting an operation, the system shifts the operations already scheduled on the
resource in order to create a suitably large slot for the operation that has to be inserted. In this
way, the sequence of operations that have already been planned remains unchanged, and
operations that have already been scheduled are not rescheduled on alternative resources
(alternative modes [Page 73]).
The date on which the operation is inserted depends on the resource schedule on the desired
date, and on the planning direction:
• There is no operation scheduled on the desired date
In this case, the system schedules the operation to be inserted on the desired date. If
necessary, operations that were already scheduled are shifted as follows:
− When the planning direction is backwards, the operations scheduled before the
desired date are shifted into the past.
− When the planning direction is forwards, the operations scheduled after the desired
date are shifted into the future.
• An operation has already been scheduled on the desired date
In this case the operation to be inserted is inserted, depending on the planning
direction, immediately after (when the planning direction is forwards) or immediately
before (when the planning direction is backwards) the operation that has already
been scheduled. If necessary, the operations that have already been scheduled are
shifted, as described previously.
If the system cannot generate a sufficiently large slot, for example, because otherwise the
relationships would be violated, all operations remain where they are. The operation is not
inserted.
If the system cannot perform scheduling or rescheduling using the scheduling

mode Insert operation, you can schedule an operation or order at the end of the
schedule using the finite strategy add an operation [Page 90].
Inserting an Operation and Closing Gaps

Use
You can use these finite scheduling modes [Page 89] to insert an operation at the desired
date [Page 94] in the existing resource schedule (see insert operation [Page 90]). The system
subsequently attempts to close gaps in the schedule, that is, either
• The gap created through rescheduling the operation, or
• All gaps to the beginning or end of the resource schedule
The system does not change the sequence of the operations on the resources.
You can only use these scheduling modes for single-activity resources [External] that are to
be finitely scheduled. For more information about finite and infinite scheduling modes and
Features
• Inserting an operation and closing a local gap

If you set this scheduling mode, the system attempts to insert the operation finitely at
the desired date when rescheduling an operation. The system then tries to close the
gaps in which the operation was originally scheduled.
You use this scheduling mode, for example, if you have formed one or more
operation blocks without gaps for a resource, and want to prevent the formation of
new gaps within a block during the detailed sequence planning.
• Inserting an operation and closing gaps up to the start/end
If you set this scheduling mode, the system also attempts to insert the operation
finitely at the desired date. The system then tries to close all gaps in the planning
direction for the resource schedule to the beginning or end of the planning period; in
block planning [External] the system only closes gaps to the beginning or end of the
block concerned.
The system begins by closing the gaps on the earlier of the following dates:
− Original operation date
− New operation date
The system starts with the first gap in the planning direction, and then attempts to
close the next gap, and so on. It cancels this process if it cannot move an operation,
for example, because relationships to other operations can otherwise not be retained.
You use this scheduling mode, for example, if you want to create a schedule without
gaps for a resource.
The system does not close the following gaps:
• A gap caused by changes to an order, for example, by changing the order quantity or by
deleting an order
• A gap, caused by deallocating [Page 412] an operation
• An already existing gap
Squeezing in an Operation
Use
You can use this finite scheduling mode [Page 89] to schedule or reschedule an operation in
an existing schedule on the desired date [Page 94], even when there is no slot for this date,
or the slot is too small. If necessary, the system creates a slot that is large enough by shifting
the neighboring operations on the resource in both directions.
You can only use this scheduling mode for single-activity resources [External] that are to be
finitely scheduled. For more information about finite and infinite scheduling modes and
Scheduling in Non-Working Times

Use
You can configure the detailed scheduling strategy [Page 82] in such a way that operations
can also be scheduled during regular non-working times (breaks, weekends, and so on) for a

resource, that is, in times where the resource cannot work according to plan. By using this
strategy, you do not have to change the resource data explicitly when you want to finish an
operation after the end of the regular working time, for example, after the end of the last shift.
In downtimes [External] of a resource you cannot schedule any operations.
Features
By setting the indicator Non-working times in the detailed scheduling strategy, you specify
that the same capacity and rate of resource utilization is available in non-working times at the
resource as was available in the regular working times immediately prior to this. This data is
valid until the start of the next regular working time. You can schedule operations at any time.
The operations can lie completely or partially in non-working times.
Capacity, capacity utilization
Regular work time

Non-working time
Time
An operation that you schedule in a non-working time is automatically fixed by the system.
This means that neither you nor the system can shift this operation to a normal working time
during the next scheduling. Even if you reset the Non-working times indicator, operations that
are scheduled in non-working times remain fixed. In order to be able to reschedule a fixed
operation, you must undo the fix [Page 418].
Activities
If you want to work with another capacity in non-working times, for example with only three
people instead of four, you must change the resource data.
• In the detailed scheduling planning board [Page 362], working times are shown in white,
regular non-working times (such as breaks and weekends) in gray, and downtimes
[External] (for example, through machine shutdowns) in dark gray.
• You can display and hide [Page 382] non-working times in the detailed scheduling
planning board. You cannot display and hide downtimes in the detailed scheduling
planning board.

Specifying the Scheduling Sequence

Use
You use the scheduling sequence to specify in which sequence the system executes the
scheduling or rescheduling of an operation group or order group. You can set up the
sequence using various criteria, for example:
• Order priority
• Resource
• Product number
The scheduling sequence is relevant for
• Manual scheduling and rescheduling [Page 406] of operations and order groups using
drag and drop
• Scheduling and rescheduling of operations and order groups using the planning function
Reschedule [Page 410]
• Scheduling with detailed scheduling heuristics [Page 413]
The scheduling sequence is not relevant for scheduling an order. The scheduling sequence is
valid for all detailed scheduling strategies [Page 82] in a strategy profile.
Activities
When you schedule or reschedule a group of selected operations or orders, the system first
puts the operations and orders in the desired sequence before scheduling or rescheduling
them. The system then executes the scheduling or rescheduling of the operations or orders
following that sequence.
Depending on the planning situation and the other settings in the detailed
scheduling strategy, the scheduled or rescheduled operations at the resources
can follow a sequence other than the one you specified in the scheduling
sequence.
Desired Scheduling Date

Use
When scheduling or rescheduling operations and orders [Page 62], the system uses the
desired scheduling date as a starting point, and looks for a scheduling date in the planning
direction [Page 86] you have set. A desired scheduling date is only relevant for an object that
you have selected for scheduling [Page 70], for example, for the order that you want to
create, or for the operation you want to move to another date. Other objects may be affected
by the scheduling or rescheduling of the selected object, for example, by relationships that
must be observed. The system must therefore reschedule additional objects under certain
circumstances. The system determines the dates for these objects automatically; the dates
themselves are based on the objects that have been selected for scheduling.
The following table shows how the desired scheduling date – depending on the application –
is defined.

Application Definition of the Desired Date

Creating an order • If you create an order manually in Production Planning and
Detailed Scheduling (PP/DS), you enter an availability date
for the order product.
• If the system creates an order (for example, for dependent
requirements), it automatically determines this date on the
basis of the requirements date for the independent
requirements.
• If an order from Supply Network Planning (SNP) is converted
[Page 114] into a PP/DS order, the date of the SNP order is
transferred.
Transferring an order to the The dates are transferred.
SAP APO system (from an
SAP R/3 system, from an
OLTP system using BAPIs)
Manual rescheduling [Page You define the desired scheduling date for the activity, the
406] in the detailed operation, or the order using Drag&Drop.
scheduling planning board
[Page 362]
Scheduling using the You can use this scheduling function in the detailed scheduling
scheduling function planning board and in the production planning run. You define the
Reschedule [Page 410] desired scheduling date in the detailed scheduling strategy.
Scheduling with detailed You can use detailed scheduling heuristics in the detailed
scheduling heuristics [Page scheduling planning board and in the production planning run.
413] The desired scheduling date is heuristics-dependent.
Settings for Dependent Operations

Definition
Settings in the detailed scheduling strategy [Page 82] that control the rescheduling [Page 71]
of the dependent operations:
• Scheduling Submode [Page 95]
• Considering Time Relationships [Page 97]
• Considering Pegging Relationships [Page 98]
• Scheduling with Time Buffers [Page 102]
• Restrictions for automatic mode selection [Page 103]
• Compact Scheduling [Page 103]
Scheduling Submode
Use
If a scheduled operation is rescheduled or a deallocated operation is scheduled, further
dependent operations [Page 71] may be affected via pegging relationships [Page 98] or time

relationships [Page 97]. Further detailed scheduling activities [Page 64] that the system can
process automatically, are often necessary so that the schedule remains consistent, for
example, so that time relationships are retained. You can determine how the system
schedules dependent operations on the dependent resources using the scheduling submode
in the detailed scheduling strategy [Page 82]. (Dependent resources are resources that are
occupied by dependent operations). You have the following options:
• Scheduling Dependent Operations According to the Scheduling Mode
In this case, the system uses the same scheduling mode [Page 89] for scheduling on
the dependent resources as on the selected resources. (Selected resources are
resources which are occupied by operations selected for the scheduling [Page 70]).
If, for example, you have defined insert operation [Page 90] as the scheduling mode
for the selected resources, the system also reschedules the dependent operations on
the dependent resources using insert operation.
Example [Page 96]
• Deallocating dependent operations
Here, the system deallocates the dependent operations on the dependent resources;
that is, the dependent operations are given the status deallocated, and are no longer
dispatched on the resources (see also deallocating operations and orders [Page
412]).
This scheduling submode is recommended if you have defined different scheduling
responsibilities for resources using different work areas. A change in the scheduling
in a scheduling area does not automatically lead to rescheduling of the dependent
operation on the resources. Instead, the dependent operations are removed from the
scheduling.
• Scheduling dependent operations infinitely
Here, the system reschedules the dependent operations on the dependent resources
infinitely, that is, without considering the current resource load (see also finite and
infinite scheduling [Page 81]).
Scheduling Dependent Operations According to the

Scheduling Mode
The following graphic shows an example for the rescheduling of an operation using the insert
operation scheduling mode [Page 90] and the scheduling dependent operations according to
the scheduling mode scheduling submode [Page 95]. You have defined that the system
should maintain time relationships [Page 97].

Before Rescheduling
Selected
operation
Selected A10
resource
Resource 1 A10 B10
Resource 2 A20 B20
Resource 3 A30 B30

Dependent
resources
Time axis
Dependent
operations
After Rescheduling
Resource 1 A10 B10
Resource 2 A20 B20
Resource 3 A30 B30
Time axis
Relationship
You reschedule operation A10 to another date. Operation A10 is the selected operation, and
resource 1 is therefore the selected resource. The system must shift operation B10 on the
selected resource to a date in the future so that operation A10 can be scheduled on the new
desired date. A10 and B10 have time relationships to further dependent operations on
dependent resources 2 and 3. The system also reschedules these dependent operations with
the insert operation scheduling mode in order that the relationships can be observed.
Considering Time Relationships between Operations

Use
In an order, two activities from different operations may be linked by a time relationship that
specifies the minimum or maximum interval between the activity dates. In the Detailed
scheduling strategy [Page 82] you can define whether or not the system should consider
cross-operational time relationships during detailed scheduling [Page 62].
Relationships between the activities of an operation are considered by the

system.
Considering cross operation relationships means scheduling or rescheduling an operation
such that no minimum or maximum intervals are violated. The system must schedule or
reschedule the dependent operations accordingly; Date default values, or date changes must
therefore be propagated to the dependent operations. You have the following options:
• Do not consider relationships
• Consider relationships

• Consider relationships in the propagation range [External]

You can set that the system does not consider maximum intervals. This can be useful in
complex planning situations, so that the system can (more easily) find a solution in detailed
scheduling that can be used as a starting point for further planning.
Integration
If time relationships are not considered during scheduling or rescheduling, the minimum or
maximum intervals may be violated. If you want to display alerts for violated minimum or
maximum intervals [Page 304] in the Alert Monitor, you must use a corresponding PP/DS
alert profile.
Features
Do not consider relationships
The system schedules or reschedules an operation without considering relationships. This
means that the minimum or maximum intervals could be violated.
Consider relationships
The system must carry out scheduling or rescheduling of an operation such that the minimum
or maximum interval is retained. If the operation has a relationship to an unfixed [Page 418]
operation, the system must schedule or reschedule this dependent operation accordingly; for
an unfixed deallocated operation, the system must also adjust the dates and modes. A fixed
[Page 418] dependent operation defines a fixed reference date for the minimum or maximum
interval that restricts the scheduling or rescheduling of the operation. If it is not possible to
schedule or reschedule the operation and its dependent operation accordingly, the system
does not carry out scheduling or rescheduling.
Only consider relationships in the propagation range

Operations outside the propagation range [External] are fixed during planning. This can lead
to severe limitations for the planning. With the consider relationships only in the propagation
range option, you can plan more flexibly, since the system must not consider a relationship
between an operation in the propagation range and an operation outside the propagation
range (see do not consider relationships); the system can schedule or reschedule the
operation in the propagation range without constraints. However, the system must consider
relationships between operations in the propagation range (see consider relationships).
If a relationship for which no minimum interval has been maintained in the

production process model or iPPE plan exists between two operations, the
system uses the minimum interval 0.
Considering Pegging Relationships

Use
If an order transfers its product to another order, these orders are linked by a fixed [Page 44]
or a dynamic [Page 38] pegging relationship. A planned order, which requires a certain
component can be linked to a purchase requisition for the component in external
procurement, or to a planned order for the component in in-house production (see pegging
[Page 36]).
You may wish to consider pegging relationships if an order or an activity from an order is
being scheduled or rescheduled, that is, the system must schedule or reschedule such that

no requirements dates are violated. This can mean that the system must schedule or
reschedule objects (orders, activities) which have pegging relationships accordingly; date
values or date changes must therefore be propagated to the dependent objects.
In the Detailed scheduling strategy [Page 82] you can define whether or not the system
should consider pegging relationships during detailed scheduling [Page 62]. You have the
following options:
• Consider fixed pegging relationships [Page 99]
• Consider fixed and dynamic pegging relationships [Page 100]
Integration
If pegging relationships are not considered during scheduling or rescheduling, date problems
(availability date too late or much too early) or, with dynamic pegging relationships, new
quantity problems (shortages or surpluses) may occur. You define the alert thresholds for
date alerts (maximum advance and maximum delay of the availability date) in the location
product master. If these thresholds are exceeded during planning, the system creates date
alerts. If you wish to display date and quantity problems in the alert monitor [Page 304], you
must use the corresponding PP/DS alert profile.
Prerequisites
If the system is to consider pegging relationships during scheduling or rescheduling, you must
also define in the detailed scheduling strategy that the system should consider time
Considering Fixed Pegging Relationships

Use
consider the fixed pegging relationships [Page 44] to other dependent objects when
scheduling or rescheduling [Page 62] an object (activity, operation or order). Considering
fixed pegging relationships means scheduling or rescheduling an object and its dependent
object such that no requirements dates are violated. You have the following options:
• Do not consider fixed pegging relationships
• Consider fixed pegging relationships
• Consider fixed pegging relationships in the propagation range [External]
In principle, the system retains fixed pegging relationships during scheduling or rescheduling,
that is, the assignment of a receipt element [External] to a requirements element is
maintained.
Prerequisites
For more information about the prerequisites, see considering pegging relationships [Page
98].
Features
Do not consider fixed pegging relationships
The system schedules or reschedules an object without considering requirements dates. This
means that the requirements dates may be violated. If the availability date is earlier or later
than the alert thresholds specified in the location product master, the system will create a date
alert.

Consider fixed pegging relationships

The system must schedule or reschedule an object such that the availability date is as close
as possible to, but still before the requirements date. If the object has a fixed pegging
the dates and modes. A fixed [Page 418] dependent object defines a fixed availability date or
a fixed requirements date which restricts the scheduling or rescheduling of the object. If it is
not possible to schedule or reschedule the object and its dependent objects accordingly, the
A sales order or a planned independent requirement is fixed and defines a fixed

requirements date. With the consider fixed pegging relationships option, the
system must schedule a planned order for the sales order or planned
independent requirement so that the availability date is as close as possible
before the requirements date.
The system cannot correct an existing delay situation − in a pegging relationship

the availability date is after the requirements date − , that is, it schedules or
reschedules the object without time constraints.
Consider fixed pegging relationships only in the propagation range

Objects outside the propagation range [External] are, in principle, fixed during planning, that
is, these objects define fixed availability dates or requirements dates. This can lead to severe
limitations for the planning. With the consider fixed pegging relationships only in the
propagation range option, you can plan more flexibly, since the system must consider a
pegging relationship between an object in the propagation range and an object outside the
propagation range (see do not consider fixed pegging relationship); the system can schedule
or reschedule the object in the propagation range without constraints. However, the system
must consider pegging relationships between objects within the propagation range (see
consider fixed pegging relationships).
Considering Dynamic Pegging Relationships

Use
consider the dynamic pegging relationships [Page 38] to other objects when scheduling or
rescheduling [Page 62] an object (activity, operation or order). After scheduling or
rescheduling, the system carries out dynamic pegging, in which it deletes the existing
dynamic pegging relationships and creates new ones. Considering dynamic pegging
relationships means scheduling or rescheduling an object and its dependent objects such
that,
• The pegging relationships between the object and its dependent objects, which existed
before scheduling or rescheduling, are maintained, that is, are recreated in dynamic
pegging after scheduling or rescheduling.
• No requirements dates are violated
You can only consider dynamic pegging relationships together with fixed pegging
relationships [Page 99]. You have the following options:
• Do not consider dynamic pegging relationships

• Consider dynamic pegging relationships in the propagation range [External]
Prerequisites
If the system should consider pegging relationships, you must also define in the detailed
scheduling strategy that it must consider fixed pegging relationships [Page 99]. For more
information about further prerequisites, see considering pegging relationships [Page 98].
Features
Do not consider dynamic pegging relationships
The system schedules or reschedules an object without time constraints, that is, without
considering the pegging interval [Page 39]. After scheduling or rescheduling, the system
carries out dynamic pegging in accordance with the pegging settings in the location product
master (for example, pegging interval [Page 39] and pegging strategy [Page 42]). Since the
pegging interval was not considered during scheduling or rescheduling, the original pegging
relationship, that is, the original link between receipt elements [External] and requirements
elements can be lost. If the system is not able to create a new corresponding pegging
relationship, quantity problems may now occur. If, for example, an order is not assigned to
any receipt, there is a shortage for the order. If no requirement is assigned to the order, the
order creates a surplus. If the system was able to maintain the pegging interval during
scheduling or rescheduling, date problems may occur if the deviation of the availability date
from the requirements date exceeds the alert threshold for date alerts specified in the product
master.
Consider dynamic pegging relationships in the propagation range

The system must not consider a dynamic pegging relationship between an object in the
propagation range [External] and an object outside the propagation range; the system can
schedule or reschedule the object in the propagation range without time constraints (see
above).
However, the system must consider dynamic pegging relationships between objects within
the propagation range; the system must schedule or reschedule an object such that the
dynamic pegging relationship to a dependent object in the propagation range is maintained
and that the availability date is as timely as possible, or at least is between the beginning of
the pegging interval and the requirements date. If the object has a dynamic pegging
the dates and modes. A fixed dependent object defines a fixed availability date or a fixed
requirements date which restricts the scheduling or rescheduling of the object. If it is not
possible to schedule or reschedule the object and its dependent objects accordingly, the
As, with this option, the system maintains the pegging interval for a dynamic pegging
relationship within the propagation range, the system creates (with all probability) the same
dynamic pegging relationship after scheduling or rescheduling in dynamic pegging.
• In complex scheduling situations, however, the original pegging relationship may be lost.
If the system can create a different pegging relationship, the availability date does not
deviate further from the requirements date than is allowed by the pegging interval.
• The system cannot correct an existing delay situation − in a pegging relationship the
availability date is after the requirements date −, that is, it schedules or reschedules the
object without time constraints.
• If pegging relationships exist between receipts and requirements [Page 239], the
optimization can minimize delays of receipts [Page 231]. If there is no longer a pegging
relationship between a requirement, for example a sales order, and a planned order for
this sales order, the sales order date cannot be considered during optimization.

Scheduling with Time Buffers

Use
In Production Planning and Detailed Scheduling, if you want to protect an activity or the
primary resource, on which the activity is processed, from unforeseen delays in material
staging, you can schedule using a resource-specific time buffer. The time buffer represents a
type of safety time: Using the time buffer, the system keeps a larger time interval between the
activity and its predecessor activities during scheduling. Possible delays in the predecessor
activities can be caught by the time buffer and a standstill in resources due to material
shortage can thereby be avoided. Here, predecessor activities are the activities that have a
time relationship or a pegging [Page 36] relationship to the activity.
When scheduling with time buffers, the system must – depending on the type of relationship –
keep the following minimum time intervals between the activities:
• In a pegging relationship, the availability date must be earlier than the requirements date
by at least the duration of the time buffer.
• In a time relationship, the minimum time interval defined in the production process model
(PPM) is increased between the activities by the duration of the time buffer.
If you do not specify a minimum interval in the PPM for a relationship, the system
uses 0 as the minimum interval; during scheduling with time buffers, the minimum
interval is therefore the duration of the time buffer.
In the PPM you can specify for each relationship if the system can use the time buffer
during scheduling.
Scheduling with time buffers is not relevant to activities of orders that are based on an iPPE
plan.
Prerequisites
General Prerequisites
• You specified a time buffer in the primary resource for which you wish to carry out
scheduling with time buffers.
• You specified in the detailed scheduling strategy [Page 82] that the system should
consider time relationships.
Specific Prerequisites for Scheduling with Time Buffers in Time Relationships

• In the PPM for the time relationships, for which you wish to schedule with time buffers,
you specified that the system can use the time buffer during scheduling (reference
subtype 2).
Note that it often does not make sense to have a time buffer between the setup
activity and the processing activity of an operation.
• You specified in the detailed scheduling strategy that the system must use the time
buffers for these time relationships during scheduling.

Specific Prerequisites for Scheduling with Time Buffers in Pegging Relationships

• You specified in the detailed scheduling strategy that the system should consider pegging
relationships.
• You specified in the detailed scheduling strategy that the system must use the time
buffers for the pegging relationships during scheduling.

Use
[Page 405].
Compact Scheduling
Use
In compact scheduling, the system tries to achieve a schedule for deallocated operations or
for whole orders that has the smallest possible time intervals between the operations; ideally,
the intervals are the minimum intervals defined in the production process model or in the iPPE
plan. This means that, by using compact scheduling, you can reduce or minimize the lead
times, thereby achieving a more compact schedule.
Prerequisites
• You have specified in the strategy profile that the system should consider the time
• You have set compact scheduling in the strategy profile.
Features
The following options are available for compact scheduling:
• Schedule deallocated operations compactly
If you choose this option, the system compactly schedules the deallocated [Page 412]
operations for all orders affected by the rescheduling of an operation. The system
tries to adjust the dates and modes [Page 72] of the deallocated operations so that, if

possible, the time intervals to the operations with which they have time relationships
are as small as possible.
Example [Page 104]
• Schedule deallocated operations and selected orders compactly
If you choose this option, the system compactly schedules the orders selected for
scheduling in addition to the deallocated operations (see above), that is, the system
schedules each of the selected orders in such a way that the intervals between its
operations are as small as possible, independent of whether the operations are
scheduled or deallocated.
Example [Page 105]
• Schedule all affected orders compactly
If you choose this option, the system compactly schedules all the orders, including
the selected orders, that is has to reschedule as a result of scheduling or
rescheduling an operation or order. The system tries to achieve the minimum interval
between the operations in all the affected orders, independent of whether the
operations are scheduled or deallocated.
Example [Page 106]
• No compact scheduling
If you choose this option, the system only reschedules the operations if the
relationships to these operations are violated, and you specified in the strategy profile
that these relationships must be considered. Rescheduling is executed in such a way
that the relationships are no longer violated; that is, the intervals between the
operations do not fall below the minimum, and the maximum intervals are not
exceeded. It is therefore not necessary to achieve the minimum intervals.
Example [Page 108]
• The system always tries to achieve the minimum interval between the activities in an
operation, independent of whether or not you set compact scheduling.
• If you do not define a minimum interval for a relationship in the production process model
or in the iPPE plan, the system uses an interval of 0.
Compact Scheduling for Deallocated Operations

The following graphic explains, in the form of an example, how the system executes compact
scheduling [Page 103] for deallocated orders. During the compact scheduling of deallocated
[Page 412] operations, the system compactly schedules the deallocated operations from all
the orders affected by the rescheduling of an operation.
Compact Scheduling for Deallocated Operations

Before rescheduling
A10
Resource 1 A10 B10 C10
Time axis
After rescheduling
Time axis
Relationship
Deallocated operation
Orders A, B and C each contain the scheduled operations 10, 20 and the deallocated
operation 30. The end-start relationships between operations 10 and 20, and between
operations 20 and 30 are defined with a minimum interval of 0.
When you reschedule the scheduled operation A10, the system tries to shift the deallocated
operation A30 as close as possible to operation A20, taking into account the minimum interval
(even when A20 was not shifted and the relationship to A30 was not violated).
As a result of rescheduling A10, the scheduled operation B10 from order B is affected, for
example, because the planning mode Insert operation is set, and B10 therefore has to be
shifted. The system now tries to shift the deallocated operation B30 in such a way that the
minimum interval to B20 is achieved (even when the relationship was not violated).
Order C is not affected by rescheduling operation A10. Therefore, the deallocated operation
C30 is not scheduled compactly; that is, it is not shifted towards operation C20.
Compact Scheduling for Deallocated Operations and

Selected Orders
scheduling [Page 103] for deallocated operations and selected orders.
Compact Scheduling for Deallocated Operations and Selected Orders

Before rescheduling
A10
Time axis
After rescheduling
Time axis
Relationship
Orders A, B and C each contain the scheduled operations 10, 20 and a deallocated [Page
412] operation 30. The end-start relationships between operations 10 and 20, and between
When you reschedule the scheduled operation A10, order A is the order selected for
scheduling. The system, therefore, schedules the whole of order A compactly; that is, it tries
to do the following:
• Shift the scheduled operation A20 as close as possible to operation A10, taking into
account the minimum interval
• Shift the deallocated operation A30 as close as possible to operation A20, taking into
shifted. Due to the fact that order B is not a selected order for scheduling, the system only
schedules the deallocated operation B30 for this order compactly; that is, it tries to shift the
deallocated operation B30 up to the scheduled order B20.
Order C is not affected by rescheduling operation A10. Therefore, the deallocated operation
C30 is not scheduled compactly; that is, it is not shifted towards operation C20.
Compact Scheduling for All Affected Orders

scheduling [Page 103] for all orders. Here the system compactly schedules all orders that are
affected when rescheduling an operation.

Compact Scheduling for all Orders
Before rescheduling
A10
Time axis
After rescheduling
Time axis
Relationship
Orders A, B and C each contain the scheduled operations 10, 20 and the deallocated
operation 30. The end-start relationships between operations 10 and 20, and between
When you reschedule the scheduled operation A10, order A is the order selected for
scheduling. The system, therefore, schedules the whole of order A compactly; that is, it tries
to do the following:
• Shift the scheduled operation A20 as close as possible to operation A10, taking into
• Shift the deallocated operation A30 as close as possible to operation A20, taking into
shifted. Therefore, order B is also scheduled compactly; that is, the system tries to do the
following:
• Shift the scheduled operation B20 as close as possible to operation B10, taking into
• Shift the deallocated operation B30 as close as possible to operation B20, taking into
Order C is not affected by rescheduling operation A10. The order is, therefore, not scheduled
compactly.

Scheduling Without Compact Scheduling

The following graphic explains, by using an example, how the system schedules if you
schedule without compact scheduling [Page 103]. Without compact scheduling, the system
only reschedules an operation if the relationships to this operation are violated and, according
to the strategy profile, these relationships must be considered.
Scheduling Without Compact Scheduling
Before rescheduling
A10
Time axis
After rescheduling
Time axis
Relationship
Orders A, B and C each contain the scheduled operations 10, 20 and a deallocated operation
30. The relationships (end-start relationships) between operations 10 and 20, and between
shifted. The system, therefore, shifts operation B10.
By rescheduling A10 and B10, none of the relationships to other operations was violated;
therefore, the system does not reschedule any other operations.
Planning with Shelf Life Data

Use
You can specify that shelf life data is to be taken into account for planning in PP/DS. The
goals of such planning may be, for example:
• To recognize that stock is about to expire

• To only deliver/commit products to customers if the required shelf life criteria has been
met
• To only assign stock or a manufacturing order to a consumer if the consumption takes
place within the usability period
Shelf life is visualized in the product view and in push production.
Integration
If the shelf life data is to be transferred from an OLTP system (for example, from R/3) to APO,
this must be specified in the product master in APO. You can enter further shelf life data in
APO that is taken into account when you plan in PP/DS.
Shelf Life Information in R/3

In R/3, the following objects contain shelf life information:
• Material master
If a value is entered in the Total shelf life field in the R/3 material master (General plant
data/Storage1 view), the Planning with shelf life indicator is set in the APO product
master and the total shelf life is transferred to the Shelf life field.
• Batch
If the material to be produced is to be handled in batches in R/3 and the availability date
and expiration date characteristics are defined for the creation time, this data is
transferred to APO.
• (Configured) Sales order
If the required minimum shelf life and maximum shelf life are defined as characteristics
and have values assigned to them in the sales order, this data is also transferred to APO.
The standard characteristics SAP_SL_MIN, SAP_SL_MAX and SAP_SL_UTC are used to
transfer shelf life information to APO. They must be filled manually or by way of dependencies
in R/3.
Shelf Life Information in APO

Along with the information about total shelf life transferred from R/3, the following information
can be entered or adjusted in the product master in APO:
• The maturity time, which is the time required by the product after the goods receipt before
it can be used (availability time); the maturity time and the usability time together make up
the shelf life period (ending with the expiration date)
• The required minimum shelf life, possibly already taken from R/3
• The required maximum shelf life, possibly already taken from R/3
These entries serve as default values for receipts (for example, a manufacturing order
generated in APO) and requirements (for example, a planned independent requirement), for
which no values have been transferred from R/3 or the OLTP System.
Features
In PP/DS planning, product receipts and product requirements are compared with regard to
their shelf life data or shelf life requirements. Matching receipts and requirements are linked to
each other. The following conditions apply:
• The receipt must at least keep for the minimum shelf life of the requirement.
• The receipt may only keep up to the maximum shelf life of the requirement.
• The requirement time may not lie before the maturity time.

Example
A product receipt requires 5 days of maturity time starting from today. It can then be used for
20 days. Therefore, the expiration date for the product receipt is in 25 days. The requirements
are as follows:
Requirement A: Required in 15 days, required minimum shelf life of 6 days, required
maximum shelf life of 12 days
Requirement B: Required in 20 days, required minimum shelf life of 6 days, required
Requirement C: Required in 10 days, required minimum shelf life of 6 days, required
The product receipt, which reaches its expiration date in 25 days is only linked with
requirement A, since requirement A meets both conditions (minimum shelf life date in 21
days, maximum shelf life up to 27 days).
Recommendation
Use the exact lot size as the lot-size procedure. If you use a different procedure, the system
creates lots without taking the shelf life of the receipts or of the requirements into account.
This may cause requirements and receipts to be linked even if they do not match. In such
cases, however, the system will eventually recognize this and an alert will be triggered.
Maintenance of Master Data

Purpose
This process flow describes the master data that is necessary for Production Planning and
Detailed Scheduling and in which sequence you have to maintain it. If you do not use APO as
an ATP server, you can transfer most master data from a connected OLTP System and
simply maintain part of the settings. For more information on which master data has to be
maintained after transfer from the OLTP System, see OLTP - PP/DS Scenario [Page 18] and
Integration Scenario: Master Data [External].
Prerequisites
If you do not use APO as an ATP server but as a planning system, you have to perform an
initial transfer of master data to APO using an integration model in the core interface
[External]. You must transfer the master data of all products that are to be planned in APO.
Process Flow
1. You create a supply chain model [External] in the model/planning version master data or
in the Supply Chain Engineer.
2. You create a planning version [External] based on the supply chain model and you set
the PP/DS: Change planning active indicator for the planning version.
3. You maintain a location [External] (type: plant) in which a product is to be produced. You
assign the location to the model [External] by choosing Assign model on the initial
location master data screen or you assign it in the Supply Chain Engineer.
4. You maintain the following data in the Product Master [External] records in this location
for the product and its components that are produced in-house:
− The lot size, scrap and rounding data in the Lot Size tab.
− Whether the product is to be planned automatically [Page 118] or manually (with or
without check) by setting the appropriate indicator in the PP/DS screen, in the section
entitled Automatic planning for all changes.

− Whether a product is to be produced in-house or procured externally in the GI/GR

screen, in the Procurement field.
You assign the products to the model [External] by choosing Assign model on the
initial Product Master screen or you assign them in the Supply Chain Engineer.
5. You maintain single-activity resources or multi-activity [External] on which the products
are to be produced. You define the working times and capacity for these resources. If you
also use Supply network Planning to plan products, you maintain mixed-single or mixed-
multi resources [External]. These types of resources can used both in Supply Network
Planning and Production Planning and Detailed Scheduling as it has both a bucket
capacity and detailed capacity.
You assign the resources to the model [External] by choosing Model Assignment on
the Process Resource screen or you assign them in the Supply Chain Engineer.
6. You maintain production process models [External] for the product and the components
that are produced in-house.
You assign the production process models to the model in the Supply Chain
Engineer.
7. You maintain the transportation lanes [External] between locations in the Supply Chain
Engineer to model the transfer and delivery of products.
Maintenance of PP/DS Settings

Use
You can change and save the following settings for Production Planning and Detailed
Scheduling (PP/DS) for each user at any time before or during interactive planning:
• Propagation range
The propagation range [External] allows you to specify the resources and products for
which changes can be made in planning either interactively [Page 306] or in the
production planning run [Page 122].
− The resources of the propagation range are relevant for resource-related planning.
You can only change planning for resources of the propagation range. This means,
for example, you can only schedule or reschedule operations at these resources.
− The products of the propagation range are relevant for product-related planning. You
can only make changes in planning for products of the propagation range. This
means, for example, you can only create orders for these products.
If you create an order for a product that is in the propagation range but which
contains components that are not in the propagation range, the system does not
create any orders for these components. Instead, it writes a planning file entry for
them.
If you do not interactively set a propagation range, the system uses the propagation
range you have defined in Customizing for Supply Chain Planning under Maintain
Global Parameters and Defaults.
The propagation range is not relevant for the following processes:

• Transfer of orders to PP/DS [Page 112] from an OLTP system or from Supply Network
Planning
• Capable-To-Promise (CTP) [External]
• Strategy profile

You use the strategy profile to control how orders are scheduled or rescheduled. In
the strategy profile you can define, for example, whether forward or backward
scheduling is to be used and whether you want to schedule finitely or infinitely. For
more information, see Detailed Scheduling [Page 62] and Detailed Scheduling
Strategy [Page 82].
If you do not interactively set a strategy profile on the planning screen, the system
uses the strategy profile that you have entered in Customizing for Supply Chain
Planning under Maintain Global Parameters and Defaults.
• Alert profile
You use the alert profile to specify the problems and non-typical situations in planning
for which alerts are to be displayed in the Alert Monitor. For more information, see
Display of Alerts [Page 304].
• Time zone
You can define the time zone that is to be used for time entries.
• Layout
You can make settings for the presentation of and navigation between planning data
in the product view [Page 308] and in the order processing view [Page 309].
• You make the basic Customizing settings for PP/DS in Customizing for Supply Chain
Planning under Maintain Global Parameters and Defaults and in Customizing for
Production Planning and Detailed Scheduling. For more information, see the
Implementation Guides (IMG) for Supply Chain Planning and Production Planning and
Detailed Scheduling.
• You can create and change propagation ranges and strategy profiles in both Customizing
for Production Planning and Detailed Scheduling and from the SAP Easy Access menu
by choosing Supply Chain Planning → Production Planning → Environment → Current
Settings.
Transfer of Receipts and Requirements to PP/DS

Use
APO requires master data and transaction data from the connected OLTP system in order to
be able to plan products. You can control which master and transaction data is to be
transferred to APO using an integration model [External] in the core interface [External].
Transaction data is then transferred automatically to PP/DS in the APO System.
Orders can also be transferred to PP/DS from within the APO System, that is, from other APO
components, such as Demand Planning and Supply Network Planning. You use Production
Planning and Detailed Scheduling for short-term planning. More detailed production process
models and resources that are scheduled within the accuracy of a second allow a finer level
of planning. Orders from long to medium-term planning (Demand Planning and Supply
Network Planning) must be transferred to PP/DS once they reach the short-term planning
period, which is defined by the production horizon.
Integration
Orders are transferred to PP/DS from the following sources:
• A connected OLTP system

• APO Supply Network Planning

• APO Demand Planning
• APO Global ATP
Prerequisites
integration model [External] in the core interface [External].
• You have maintained the necessary master data [Page 110] and PP/DS settings [Page
111].
• If you use Supply Network Planning and/or Demand Planning, you have maintained the
production horizon in Customizing for Supply Chain Planning, under Maintain Global
Parameters and Defaults.
Features
Transferring Objects From a Connected OLTP System
The objects that are transferred to APO from the connected OLTP system are controlled
using an integration model the core interface. You can select the following transaction data in
the integration:
• Sales order
• Production/process orders
• Manual reservations
• Purchase requisitions/orders
• Planned orders
• Planned independent requirements
• Stocks
• Classes and characteristics
This data is then transferred automatically to the APO. Any changes to the data are filtered
and routed automatically through an active data channel, which uses ALE and BAPI
technology. For more information, see Integration of APO and R/3 [External].
Transferring Receipts from Supply Network Planning
You use Supply Network Planning (SNP) for long-term to medium-term aggregated planning,
and Production Planning and Detailed Scheduling (PP/DS) for detailed, short-term scheduling
of orders and resources within the accuracy of a second. You use the production horizon
[External] to separate the responsibility for planning. Planning in the production horizon is
done in PP/DS, and planning outside of the production horizon is mainly done in SNP
planning. You can convert SNP orders that are within or outside of the production horizon to
PP/DS orders.
For more information, see Conversion of SNP Orders into PP/DS Orders [Page 114].
Transferring Demands from Demand Planning
You transfer planned independent requirements from Demand Planning to PP/DS by
releasing the demand plan to Supply Network Planning. During this process, all requirements
that are in the production horizon are transferred to PP/DS, whereas all requirements outside
the production horizon and thus in the medium to long-term planning horizon, are transferred
to Supply Network Planning.
For more information, see Transfer of DP Demands to PP/DS [Page 117].
Transferring Customer Requirements from APO Global ATP and an OLTP System

When you create a sales order in the connected OLTP system for a product that is planned in
APO, an ATP check is carried out in the APO System. If the result of the ATP check is that
the product has to be produced, Global ATP transfers the requirement to PP/DS. PP/DS
creates temporary planned orders and transfers the dates of these planned orders back to the
OLTP system as the sales order availability date. Once you save the order, the temporary
planned orders become permanent orders.
For more information, see Availability Check Using PP/DS [External].
Creating Orders in PP/DS
Within PP/DS itself, receipts are created automatically by APO during planning (provided that
the products are defined as being planned automatically in the Product Master). You can also
manually create receipts [Page 314] and planned independent requirements [Page 316]
directly in PP/DS.
Conversion of SNP Orders into PP/DS Orders

Use
You use Supply Network Planning [External] (SNP) for long-term to medium-term aggregated
planning. SNP plans based on resources with a period-related available capacity, whereby
the smallest possible period is one day. Therefore, you can only plan in SNP within the
accuracy of a day and without taking sequence constraints into account. You use Production
Planning and Detailed Scheduling (PP/DS) to schedule order dates and resources within the
accuracy of a second in the short-term horizon. PP/DS plans on the basis of detailed
production process models (PPM) and resources with available capacity that is based on
exact times.
The production horizon [External] allows you to separate responsibility for planning. Planning
in the production horizon is done in PP/DS, and planning outside of the production horizon is
primary done in SNP. If you want to perform detailed planning for SNP receipts in short-term
planning, you must plan these receipts in Production Planning and Detailed Scheduling
(PP/DS). Within a planning version, you can convert SNP orders that are within or outside of
the production horizon to PP/DS orders.
You can convert orders as follows:
• You can convert orders that are within or outside of the production horizon individually.
• You can convert all SNP orders for which at least one activity begins within the production
horizon.
Prerequisites
To convert orders, you must have made settings for the following master data:
Object Settings
Planning version In Model and Planning Version Management you have set the following
indicators for the planning version:
PP/DS: Change planning active
SNP: Change planning active

Resources You have assigned the SNP resources and the PP/DS resources to the model of
the planning version.
If you want to plan with the same resources in SNP and PP/DS, you
use mixed resources for which you can define both an available
capacity based on exact times, well as a period-related available
capacity.
PPM • You have defined a PPM for SNP and a PPM for PP/DS.
• You have assigned the PP/DS PPM to the SNP PPM.
Production horizon You have defined a production horizon for the location product as follows:
Global for all products in Customizing for Production Planning and Detailed
Scheduling under Maintain Global Parameter and Defaults
Product-specific in the location product master on the SNP 2 tab
If you define a product-specific production horizon, the system uses the product-
specific production horizon.
Features
Conversion for In-House Production
If you convert an SNP receipt for in-house production, the system:
• Deletes the SNP receipt
• Explodes the PP/DS PPM
• Creates a new in-house production order for PP/DS
Control of Conversion
You can control conversion as follows:
• You can specify that the system may not delete the newly created receipts in the PP
planning that follows.
• You can specify whether the system is to use the sources of supply determined in SNP or
whether it is to determine new ones.
• You can use the conversion mode to specify whether the system
− Is to plan all components
− Is only to plan those components that were not planned in SNP
− Is not to plan components that are defined in the location product master as being
planned automatically
You have the following control options for converting all orders in the production horizon:
• You can use the category to specify the types of receipt elements the system is to convert
(for example, receipts for in-house production).
• You can define a larger horizon in which the system is to convert orders.
Visibility of Converted Orders

SNP orders converted to PP/DS orders are still visible in SNP as aggregated demands. If you
use the same resources in SNP and in PP/DS (mixed resources), the resource schedule is
visible in SNP and in PP/DS.
Conversion in the Background

You can also convert orders in the background.

Activities
Function Menu path
Converting SNP orders From the Interactive Production Planning menu area, access the
individually product view for the product.
Call the order processing view [Page 309] for the receipt element to be
converted.
Choose Edit → Convert SNP order.
Converting all SNP From the Production Planning menu area, choose Environment →
orders in the production Conversion of Supply Network Planning -> Production Planning.
horizon
Transfer of Sales Orders from R/3 to APO

Purpose
If APO is used as a planning system for a product, planning may only be carried out in the
APO System. Planning in R/3 and APO will react differently to the same events (for example,
creation of sales order). If planning was carried out in R/3 and APO simultaneously, order
proposals would be generated in R/3 as well as in APO. These orders would be different. You
cannot reconcile the two plans. The product must therefore be excluded from material
requirements planning in the R/3 System. Even if planning is carried out in APO, the
execution of the plan and especially the creation of sales orders are still performed in the R/3
System (or another OLTP system). It is therefore necessary to transfer data between the R/3
System and the APO System. This process flow describes how to create a sales order in the
R/3 System so that corresponding customer requirements are created in the APO System.
Process Flow
1. To ensure that customer requirements are created for materials that are not included in
planning in the R/3 System, you have to change the settings in Customizing for Sales and
Distribution in the R/3 System. There are two possible options:
− In the IMG activity Define Schedule Categories, you set the schedule line category
CN for No mat.planning and then set the Req./Assembly indicator to enable customer
requirements to be transferred.
A disadvantage of this method is that customer requirements are created for all
materials that are not planned, not only for those planned in the R/3 System and
APO.
− In the IMG activity Assign Schedule Categories, you assign the schedule line
category CP (for MRP) to a new MRP type, which you can create for products that
are to be planned in APO (in Customizing for MRP, IMG activity Check MRP Types)
to allow customer requirements to be created. For more information on how to
proceed, see Creating Materials in the R/3 System for Transfer of Sales Orders.
2. In the material master record of the products, enter the MRP type that you defined in step
one.
3. Assign an integration model in the R/3 System ensuring that you enter the appropriate
material number, plant and that you select Material Master and any other master data you

wish to transfer in the Add to Integration Model section of the screen. You must also
select at least Customer orders to enable sales orders to be transferred.
4. Activate the integration model in the R/3 System for the initial data transfer. Select the
initial transfer data mode Transmit all objects.
5. Check the product in the APO product master. Ensure that the Possibly indiv. cust. dmnd
indicator is set on the Demand tab of the product master. This corresponds to the
Dependent requirements indicator in R/3. On the PP/DS tab, set the automatic or manual
planning (with or without check) indicator for the product and select whether the BOM and
routing from the R/3 System or the production process model is to be used.
6. Create a sales order in the R/3 System for the product.
7. Check that the sales order has been created correctly in the current stock/requirements
list of the R/3 System.
8. Check that the customer requirements have arrived in the APO System by accessing the
product view for the product. If you have defined automatic planning for the product in the
APO product master (PP/DS tab), PP/DS creates a procurement proposal for the product
to cover the customer requirement.
See also:
Availability Check Calling PP/DS [External]
OLTP - PP/DS Scenario [Page 18]
Transfer of DP Demands to PP/DS

Purpose
Demands creating in Demand Planning need to be transferred to Supply Network Planning
and Production Planning and Detailed Scheduling (PP/DS) to enable suitable receipt
elements to be created or assigned to cover these demands. To transfer the demand plan to
PP/DS, you release the demand plan to Supply Network Planning. During this process,
demands outside the defined production horizon are transferred to Supply Network Planning,
whereas demands within the production horizon are transferred to PP/DS. The demands are
therefore transferred to either medium-term planning or short-term planning horizons.
Prerequisites
• See Release of the Demand Plan to SNP [External].
• You have maintained the production horizon for your planning version on the
Model/Planning Version Management: Change Planning Version Data screen. You can
also maintain the production horizon on the SNP 2 tab of the product master. The
production horizon in the product master takes priority over the parameter in Customizing.
Process Flow
1. In Demand Planning, you release the demand plan to Supply Network Planning. You can
either:
• Release the demand plan of multiple products [External]
• Release the demand plan of one product [External]
Make sure that you enter an SNP version that is also used for PP/DS. To enable
demands to be transferred to PP/DS, you must consider the length of the
production horizon when defining the planning horizon.

2. The system copies the demands from the DP version to the specified SNP version and
saves them as SNP orders in the liveCache if the demands are outside the production
horizon. It saves them as PP/DS orders in the liveCache if the demands are within the
production horizon.
3. If you have defined that the products are to be planned automatically on the PP/DS
screen of the product master, the system automatically assigns existing receipt elements
to the demands in PP/DS. If no suitable receipt elements are available, the system
automatically creates a receipt element to cover the demands. If you have defined
manual planning for the product, you will receive an alert to inform you of a product
shortage. You then create a receipt for the product manually.
Automated Production Planning and Optimization
Automatic Planning
Use
There are two types of automatic planning in Production Planning and Detailed Scheduling:
Automatic planning immediately and Automatic planning in a planning run.
• You use automatic planning immediately [Page 119] for multi-level planning of products
that use lot-for-lot order quantity or fixed lot-sizing procedures.
• You use automatic planning in the planning run [Page 121] to plan products using other
lot-sizing procedures that are available as heuristics [Page 207], such as period lot-sizing
or purchase order optimization heuristics.
You can define how the product is to be planned on the PP/DS tab of the product master.
Both types of automatic planning are triggered when:
• Product master data is changed
Integration
The orders created during automatic planning are immediately transferred to the connected
OLTP system [Page 476] so that up-to-date planning data is available in both systems.
Prerequisites
You have set either the Automatic planning immediately indicator or the Automatic planning in
the planning run indicator in the product master (PP/DS tab) for the product. If you wish to
check the availability of components of the product, you must also set the Automatic planning
immediately indicator.

Features
Automatic Planning Immediately
Products are planned immediately when automatic planning is triggered. The system
performs an availability check for a product and its components. If a product is not available, it
automatically creates suitable receipt elements while taking resource capacity into account.
The system selects the procurement alternative according to priority and costs that can fulfil
the order on the requested date. For more information, see Automatic Planning Immediately
[Page 119].

When changes relevant to planning occur, a planning file entry is created. These products are
then planned during the next net change production planning run using the heuristic [Page
207] defined for the product in the product master or, if you have not defined a heuristic here,
the default heuristic from the global settings in Customizing is used. A variety of heuristics are
available for Production Planning that can be used to plan products. For more information,
see Automatic Planning in a Planning Run [Page 121]
For more information on the production planning run, see Production Planning Run [Page
122].
Automatic Planning Immediately

Purpose
You use Automatic planning immediately to perform multi-level planning of products that use
lot-for-lot order quantity or fixed lot-sizing procedures. Products are planned immediately
when automatic planning is triggered.
Automatic planning is triggered when:
• Product master data that is relevant to planning is changed
Once automatic planning is triggered, the system performs an availability check for a product
and the components that are also defined as being planned automatically and immediately. If
a product is not available, it automatically creates suitable receipt elements while taking
resource capacity into account. The system selects the procurement alternative with the most
favorable costs that can fill the order on the requested date.
To plan products using any other lot-sizing procedure, you use the planning strategy
automatic planning in the planning run [Page 121].
Prerequisites
• You have set the Automatic planning immediately indicator in the product master (PP/DS
tab) for the product. If you wish to perform an availability check for the product, you must
also set the Automatic planning immediately indicator for the components of the product.
• To allow the procurement option with the most favorable costs to be selected during
automatic planning:
− You have maintained the costs for products produced in-house in the production
process model.

− You have maintained the costs for the transportation lanes in the Supply Chain
Engineer (for products procured externally and stock transferred from other
locations).
• For the other prerequisites, see the necessary master data [Page 110] and PP/DS
settings [Page 111].
Process
In order to cover new or changed requirements for each product that is planned automatically
and has undergone a change relevant to planning, the APO system performs the following
steps during automatic planning:
1. The system attempts to cover the product requirement with existing stock or orders with
appropriate dates and assigns available receipt elements to the requirement using
pegging [Page 36].
If enough stock or orders exist to cover the requirements, planning is completed.
2. If not enough of the product exists, the system determines the quantity that is to be
procured based on the requirement that is not covered, using lot-size calculation [Page
51] and taking into account the assembly scrap [Page 55].
3. Using the type of procurement you defined in the product master, the system determines
how the product is to be procured:
− If you have defined in-house production, the system creates planned orders. If you
have defined several production process models (PPM), the system selects the most
favorable PPM according to the priority and costs.
− If you have defined that the product is to be procured externally, the system creates
purchase requisitions, schedule lines, or stock transfer orders. If you have maintained
several procurement options in the Supply Chain Engineer, the system selects the
alternative according to its priority and costs.
− If you have defined that the product can be procured externally or by in-house
production, then the system selects the alternative according to the priority and costs
from the production process models or the Supply Chain Engineer.
4. The system schedules the orders:
− For external procurement, the planned delivery time of the product is determined from
the transportation lanes maintained in APO.
− For in-house production, the APO system explodes the PPM and performs detailed
scheduling to determine the dates for the order.
When exploding the PPM for products, the system determines component
requirements, the net duration [Page 67] and the resource consumption [Page 68] of
the activities. During this process, assembly scrap [Page 56] is taken into account
when determining the component requirements.
To determine the requirement dates of the components, the activities are scheduled
to the resources [Page 62]. Scheduling is carried out according to the settings you
have maintained in the strategy profile [Page 82], in which you define the constraints
the system is to consider during detailed scheduling, for example, the component
availability and the capacity of the resources.
There are two kinds of resources: bottleneck resources and non-bottleneck

resources. Usually, there are only a few bottleneck resources in a production
plant. For every resource, you can determine if you want to carry out finite
scheduling [External] or infinite scheduling [External]. In most cases, you
carry out finite scheduling for bottleneck resources only. In addition, you can
also carry out finite scheduling for resources that you think may be bottleneck

resources. For non-bottleneck resources, you usually carry out infinite

scheduling.
5. If constraint violations occur, for example, the customer requirement date cannot be met
or the capacity of a finite resource is exceeded, they are displayed as alerts [Page 304].
You can reprocess the planning results manually [Page 306].
Result
The availability check is carried out for all bill of material levels until suitable receipt elements
have been found or created for all levels. The orders created during automatic planning are
immediately transferred to the connected OLTP system [Page 476] so that up-to-date
planning data is available in both systems.

Use
You use Automatic Planning in the Planning Run to plan products using heuristics [Page 207]
that you have defined for each product. You are able to use your own heuristics or you can
use heuristics provided by SAP. A large variety of heuristics are available to plan products
that address particular planning problems, including lot-sizing heuristics and purchase order
quantity optimization.
Automatic planning immediately [Page 119] only allows you to use lot-for-lot order
quantity or a fixed lot size to plan products.
Automatic planning is triggered when:
• Product master data that is relevant to planning is changed
When automatic planning is triggered, a planning file entry is created for the products. These
products are then planned in the next net change planning run. An advantage of planning
products in the production planning run [Page 122], as opposed to automatically and
immediately, is that, you can control when and how often products are planned. You are
therefore able to improve performance by executing planning runs at less busy times of the
day.
Prerequisites
• You have set the Automatic planning in the planning run indicator in the product master
(PP/DS tab) for the product.
• You have maintained which heuristic is to be used to plan the product in the PP/DS tab of
the product master, in the Heuristic field.

• If you do not wish to use the standard SAP heuristics, you have created/maintained
heuristics in Customizing for Production Planning and Detailed Scheduling, under
Heuristics → Maintain Heuristics.
• You have entered the default product heuristic that is to be used to plan all products for
which no heuristic has been defined in the product master, in Customizing for Production
Planning and Detailed Scheduling, under Global Settings → Maintain Global Settings and
Defaults.
Features
You can plan products according to the heuristic defined in the product master by starting the
production planning run using one of the following heuristics:
• SAP_MRP_001: Product Planning (Comp. acc. LLevl Code)
• SAP_MRP_002: Product Planning (Plan Comp. Immdiately)
For more information on these heuristics, see Heuristics for Production Planning [Page 209].
You can plan just the products that have undergone a change relevant to planning (net
change planning run) by selecting the Planning file entry created indicator on the initial
Production Planning Run screen. If you do not select this indicator, all products in your
selection are planned.
You specify which products and which locations are to be planned for a planning version in
the appropriate fields. Additionally, propagation ranges are used to define the scope of
planning. Only products that are contained in the propagation ranges are planned during the
planning run. The propagation range can thus be used to restrict the level of planning, that is,
by using a propagation range that does not contain the components for a product, you can
plan single-level. In this case, a planning file entry is set for the component so the dependent
requirements are planned during the next planning run for this product.
If you do not enter a propagation range on the initial screen, all products you
have entered for the production planning run are planned, including their
components.
Activities
To access the production planning run from the SAP Easy Access menu, choose Production
Planning → Automated Production Planning and Optimization → Production Planning Run.
Production Planning Run

Use
You use the production planning run to execute planning for a very large number of objects
online or in the background. You can define which objects are to be planned with which
heuristics [Page 207] or functions.
The objects must be compatible with the selected heuristic or planning function, for example,
you can use production planning heuristics [Page 209] for products. You therefore use
different heuristics or functions to address different types of problems. Functions such as
optimization [Page 227] or scheduling functions can also be selected and executed during the
production planning run. You may execute several heuristics or functions one after another.
You use the production planning run in net change planning to plan those products you have
defined in the product master as being planned automatically in the planning run [Page 121].
You can also use the production planning run to plan products defined as being planned

manually, as well use a heuristic to reschedule products that have been defined as being
planned automatically and immediately [Page 119]. An example of this may be that you first
plan automatically and immediately so that an availability check is performed, and then
reschedule the products using a heuristic for periodic lot-sizing.
Prerequisites
In Customizing for Production Planning and Detailed Scheduling, you have defined the
profiles with which the planning area and the settings for the scheduling functions are defined.
The following profiles are required for the production planning run:
Profiles for the Production Planning Run
Profile Description
Time profile You use the time profile to specify the time period for which planning
is to be executed. Only the orders or operations that lie within this
planning period can be rescheduled.
Propagation range You use the propagation range to specify which resources and
products can be changed. You can only change the schedule for
resources and products that lie within the propagation range.
Strategy profile You use the strategy profile to specify the detailed scheduling
strategies for scheduling and rescheduling operations and orders.
Optimization profile You use an optimization profile to define settings for optimization.
Features
You can define several successive processing steps for the production planning run in which
the system executes various heuristics or functions for the defined objects. For each
processing step, you specify:
• The heuristic or function to be executed in this step
• The profile to be used for the heuristic or function. If you select the optimization function,
you must enter an optimization profile.
• The objects at which the heuristics or functions are to be executed
Production planning has two forms: functions and heuristics. For scheduling and optimization
you use functions. You cannot change functions. Heuristics, on the other hand, can be
maintained in Customizing for Production Planning and Detailed Scheduling. You can also
program your own algorithms and apply them as heuristics during the production planning
run. SAP delivers some standard heuristics and standard functions. These are described
briefly below.
Standard Heuristics for the Production Planning Run

• Production planning [Page 209]
These heuristics are mainly lot-sizing procedures, whose planning focus is on
products. Examples of these heuristics include periodic lot-sizing and order quantity
optimizing. Two important heuristics are Product planning and Production planning
run using low-level code. These heuristics execute the heuristic that is defined for
each product in the product master. For more information, see Automatic Planning in
the Planning Run [Page 121].
These heuristics are for scheduling or rescheduling and their planning focus is on
resources and operations. Examples of these heuristics include Reduce runtime and
Remove backlog.

These heuristics generate planned orders for requirements taking into account the
resource capacity for all periods. The planning focus is on resources, line networks
and products.
• Model Mix Planning [Page 150]
restrictions into account. The planning focus is on resources and line networks.
Standard Functions for the Production Planning Run

Along with the heuristics, you can use the following scheduling functions in the production
planning run.
Scheduling Functions
Function Objects Settings Description

Deallocate • Operations You use this function if you want to
remove operations or orders from
• Orders the schedule.
• Resources
Reschedule • Operations Strategy profile You can use this function to:
• Orders • Schedule operations or orders
that were deallocated
• Resources
• Reschedule operations or
orders that are affected by
scheduling problems
Fix objects • Orders You use this function to fix
operations and orders. This
• Operations ensures that the system cannot
reschedule these operations or
orders in a subsequent processing
step.
Undo fix on • Orders You use this function to undo the
objects fixing of objects. The system can
• Operations then reschedule these operations
or orders in a subsequent
processing step.
Optimization Resources Optimization You use this function to optimize
profile the schedule.
Transfer objects • Operations You use this function to transfer
to the customer objects to the customer exit
exit APOCDPS0 • Orders APOCDPS0.
• Resources
• Products
Activities
You call up the production planning run from the SAP Easy Access Menu by choosing
Production Planning → Automated Production Planning and Optimization → Production
Planning Run.

Executing the Production Planning Run Online

Use
You can execute the production planning run immediately online. Online execution should
only be used for smaller schedules or for tests with small amounts of data.
To prevent time-consuming jobs from adversely affecting the system response

time in the interactive mode, the time for the execution of the report is limited. If
the report runs for more than 5 minutes in the interactive mode, the system
cancels the report automatically. You should therefore choose background
processing [Page 126] for extensive planning jobs.
Prerequisites
You have defined the necessary profiles in Customizing for Production Planning and Detailed
Scheduling. For more information, see Production Planning Run [Page 122].
Procedure
1. In the APO Easy Access Menu, choose Production Planning → Automated Production
Planning and Optimization → Production Planning Run.
The Production Planning Run screen appears.
2. Enter the required data:
• Planning version
• Time profile
• Propagation range
By choosing , you can use data that has already been defined for the production
planning run.
3. Enter the heuristic or function to be used for each processing step, along with the type of
objects that are to be planned.
4. Choose Selection Criteria for each processing step to limit which objects are to be
planned and to set additional indicators specific to the type of objects.
For example, in the case of heuristics whose planning focus is on products, you can
select whether the production planning run is to be carried out in the net change
mode by selecting the indicator Planning file entries created.
5. If you want to execute the production planning run at a later date using this data, you can
save the current settings as variants as follows:
a. Choose .
b. Enter a variant name and a description.
c. Save the data.
Choose .

Result
The system executes mass planning immediately online.
Executing the Production Planning Run in the

Background
Use
You execute the production planning run as a background job if you would like to planning a
large number of objects. To do this, you can use variants that contain the settings for this
mass planning. With this function, you are able to start the job immediately or define that the
job is to be started at a later time to help improve system performance during busier times.
Prerequisites
You have created a variant to use during background planning.
Procedure
1. In the SAP Easy Access menu, choose Production Planning → Automated Production
Planning and Optimization → Production Planning Run in Background.
The Background Planning: Variants screen appears. The variants already created are
displayed.
2. Select the variant with which you want to execute the production planning run.
If required, you can:
• Display a variant
• Change a variant
• Create a variant
3. If you want to start the background job immediately, choose Start immediately.
4. If you want the background job to start at a later time, choose Schedule and define the
starting time or, in case of a periodic execution, the starting times.
Result
Background planning is executed either immediately or at the time you entered. You can
check the status of the job by choosing System → Own jobs.
Model Mix Planning

Purpose
You use this component for takt-based flow manufacturing of configured products. You can
assign daily and shift packages and then create an optimized sequence for these orders.
In this type of production, products that are often configured are produced together on one
production line. In model mix planning you can determine an order sequence with start and
end dates, that fulfills specific business aims, taking into account restrictions and customers’
preferred dates. This could be, for example, the following:
• an equal load of the line segments or takts

• a minimization of restriction violations

• a minimization of the absolute schedule deviation
• Model mix planning is suited for the demands of large order volumes, such as those in
the automotive industry. It enables you to plan several thousand orders in only a few
minutes.
• Model mix planning is based on the master data of the integrated product and process
engineering (iPPE). As you can only represent a process with iPPE for Release APO
3.0A in conjunction with the system Discrete Industries (DI), you should currently only use
model mix planning with this OLTP system.
See also:
Repetitive Manufacturing with Integrated Product and Process Engineering [External].
Integration
• Model mix planning carries out takt-based scheduling on the basis of the iPPE Line
Design function and the line resources.
• In connection with model mix planning, you can carry out fast requirements planning with
the planning matrix, or a single explosion of orders.
• If you carry out model mix planning periodically as automatic planning, you can integrate
it as a heuristic in the production planning run of the APO System. Then you can carry out
planning run in the background every night, for example.
• You can also link the APO System to a subsystem. In this way you can transfer the
planned order sequence to a production control stem, for example. (See also: Integration
of the Production Control System [Page 434]).
Features
Restrictions
When planning the sequence, model mix planning uses restrictions, with which you can
determine the conditions for the sequence. The restrictions are therefore master data for
planning:
• You can define restrictions for characteristic values, characteristic value combinations,
and materials. Here, you usually refer to the availability of machines, work, or materials.
• The system differentiates between six restriction categories [Page 131] that you can use,
such as the quantity restriction, depending on your business requirements.
• You can group the restrictions in restriction groups, and thus assign them to a planning
version and a production line.
Model Mix Planning

You can carry out the actual planning both automatically in the model mix planning run, as
well as in interactive sequencing.
• Model mix planning
With the model mix planning run, you can carry out automatic planning, in which you
plan various planning horizons with complex procedures in several steps. In addition,
you can also combine the four standard procedures or your own procedures. You can
define the number and the length of the horizons, as well as the procedures to be
used. In the long to medium-term area, you can assign the orders to only one period
slot, whilst in the short-term area, you can carry out a complex sequencing that
includes all restrictions. Depending on your settings, the system only uses existing

planned orders, or also converts customer orders and planned independent

requirements into planned orders.
• Sequencing
You use sequencing for the short-term horizon, to display the orders in their temporal
sequence, and if necessary to make changes. You can then change the sequence
manually, deallocate orders or even start a new procedure. In addition, you can view
the restriction violations and the characteristic values of the orders.
Constraints
If you have defined line networks in iPPE Line Design, you can only currently carry out model
mix planning for one of these lines. The sequence here is then valid for all other lines of the
line network.
In addition, the lines can only be arranged in sequence. In model mix planning, you cannot
plan lines arranged in parallel.
Processing Restrictions
Purpose
You use this process to create the restrictions you require as master data for model mix
planning. Restrictions are conditions to be taken into account by the planning process when
optimizing the order sequences. You use the restrictions to determine rules for the occurrence
of certain characteristic values to ensure an optimum load for personnel and machines as well
as to guarantee the availability of materials.
You group the restrictions into restriction groups and then assign these groups to the lines
and planning versions.
Prerequisites
• In the Discrete Industries System, in the integrated Product and Process Engineering
(iPPE), you must create a line structure. The line structure can consist of one individual
line or a line network.
For a line within the line network, you must select the indicator, Planning segment
and the indicator Model Mix Planning allowed (see also: Planning Segment [External]
in Line Design).
• In the class system in the Discrete Industries System, you must Create Characteristics
[External] for which you want to define restrictions.
• You must transfer the iPPE master data and the characteristics to the APO System using
the APO Core Interface (see also: Class System [External]).
Process Flow
1. Creating the restriction groups.
Using restriction groups, you can define groups of restrictions which you can then
jointly transfer to the model mix procedure First, you create the restriction groups.
You assign the restriction group to the appropriate line and a planning version.
2. Creating the restrictions.
You create a restriction for every required characteristic value or for every
combination of characteristic values. You can choose between six restriction
categories and you have various options for controlling the temporal validity of the
restrictions. From the restriction maintenance transaction, you can directly access the
dependency editor where you can define combinations of characteristic values.

Result
You have defined the restrictions and their validities. If you want to test which restrictions are
active at a certain point in time for a certain production line and planning version, use the
function Checking Restrictions [Page 139].
Restriction Groups
Use
Using restriction groups, you can group restrictions in a certain period or according to specific
business criteria. You assign the restriction groups to a line structure and a planning version.
This means you have the option of transferring all the restrictions in a group to a Model Mix
Planning procedure in one step.
This means, for example, that you can define different restriction groups for every-day
production and for the Christmas or the summer seasons.
Prerequisites
You must create a line structure in iPPE Line Design.
Features
• The restriction group has a periodic validity [Page 135] and is assigned to precisely one
production line and one planning version. You can define the start date of the validity
period. The system determines the end date automatically according to the start date of
the following restriction group.
Note that once you have assigned the restriction group to a line and planning
version, you cannot then change the line or the planning version.
• A restriction group can contain as many restrictions as you want.
• You can assign every restriction to several restriction groups and therefore to several
lines or planning versions. A restriction must be assigned to at least one restriction group.
The following diagram shows the assignment of restrictions to restriction groups, lines and
planning versions:
Planning
Planning version
version 1
Line
Restriction group 1 Restriction group 2
Restriction 1 Restriction 2 Restriction 3

Restrictions
Use
Using restrictions, you can define conditions for the occurrence of characteristic values in a
planning period. For example, you may define that a maximum of 50 vehicles with air
conditioning can be produced in one shift as the system vendor can only supply you with this
quantity.
The restrictions are then used in Model Mix Planning to calculate an optimal order sequence.
The system supports six restriction categories:
• Quantity restriction
You can use this category to limit the occurrence of a combination of characteristic
values to either a minimum or a maximum quantity.
• Spacing restriction
You can use this category if you only want to allow the occurrence of a combination
of characteristic values in a certain interval (maximum or minimum).
• Block restriction
You can use this category if you only want to allow the occurrence of a combination
of characteristic values in certain blocks.
• K-in-M restriction
You can use this category if you want to allow the occurrence of a combination of
characteristic values to a minimum or maximum quantity in a certain interval (for
example, three out of five products must have air conditioning).
• Position restriction
You can use this category if you want to limit the occurrence of a certain combination
of characteristic values to a certain position of a partial sequence.
• Even distribution
You can use this category to evenly distribute the occurrence of a certain combination
of characteristic values over the planning period.
Integration
A restriction has a direct link to a characteristic value or to a combination of characteristic
values. From the maintenance screens, you can directly access the dependency editor of the
class system where you can define the combination of characteristic values as a selection
condition. If you want to define several restrictions from different categories for a combination
of characteristic values, you have to create several restrictions as a result of this direct link.
Features
• Attributes [Page 131]
The restriction has a direct link to a combination of characteristic values. As,
however, the conditions for these combinations of characteristic values may change
over time, you can define different attributes with different validity periods and
weightings for a restriction. Therefore, the restriction determines the category of the
planning condition and the link to the characteristic value combination and the
attributes determine the actual conditions.
• You can assign statuses for the complete restriction as well as for its attributes.
− If you lock a restriction, all its attributes are also locked.
− Once you have released the restriction, you can decide for each attribute whether it is
to be selected and you can also provide a reason.

• The system automatically saves who created the restriction, the date on which it was
created as well as who was last to change the data and the change date. You can display
the data from the application.
The following diagram shows the elements of the restriction:
Restriction
Restriction
Header
Header data
data
•• Name
Name and
and description
description
•• Status
Status
•• Administrative
Administrative data
data
•• Restriction
Restriction category
category
Attribute
Attribute 11
•• Validity
Validity period
period and
and reference
reference shift
shift
•• Condition
Condition for
for characteristic
characteristic value
value
•• Weighting
Weighting
•• Selection
Selection indicator
indicator Combination of charac. values
• Characteristics
• Characteristic values
Attribute
Attribute 22
• Link
•• Validity
Validity period
period and
and reference
reference shift
shift
•• Condition
Condition for
for characteristic
characteristic value
value
•• Weighting
Weighting
•• Selection
Selection indicator
indicator
..
.
Attribute
Attribute nn
•• Validity
Validity period
period and
and reference
reference shift
shift
•• ...
...
Restriction Categories and Attributes

Use
The restriction has a direct link to a combination of characteristic values. As, however, the
conditions for these combinations of characteristic values may change over time, you can
define different attributes with different validity periods and weightings for a restriction. This
means you can define different conditions for the different shifts in a day, for example.
The restriction’s attributes vary depending on the restriction category.
Features
The following attributes are the same for all restriction categories:
• Start date and start shift
For each attribute of the restriction, you define a start date and a start shift. The end
date of the attribute is determined automatically by the system according to the start
date of the next attribute for which the selection indicator has been set (see below).
Therefore, when setting the start date of an attribute, make sure you are aware that
this may influence the end date of another restriction.
• The start shifts are numbered on a daily basis – you can define a start shift between 1
and 3. If you do not use shifts, enter 1 as the start shift.
• Reference shift
Using the reference shift, you can limit the validity of restrictions to one shift in a day
only. This means, for example, that you can plan the night shift using other
restrictions from the ones you use to plan the day shift.

The shift specifications for the attributes do not depend on the shift model you
may have defined for the line resource. The system does not determine the shift
program until Model Mix Planning as this can be changed in the short term. If, for
example, you have defined a restriction with the third shift as a reference shift
and the line only operates during two shifts, this restriction is not taken into
account.
Two attributes can have the same start date and the same reference shift as long
as the selection indicator is only selected for one of the attributes. This means
you can create several, identical restrictions for simulation purposes and then
select one.
• Hard and soft restrictions
In Model Mix Planning, the system always tries to adhere to all restrictions. However,
the more orders and characteristics you have, the more difficult this becomes.
Therefore, you can define hard and soft restrictions. That is, you can prioritize the
restrictions.
− In Model Mix Planning, the system is not allowed to violate hard restrictions.
− Soft restrictions, on the other hand, can be violated. Note that you can also define a
weighting for important and not so important restrictions. The highest weighting is 1
and the lowest weighting is 9. If you define a weighting of 9, this restriction will most
likely be violated.
Note that currently, only the genetic algorithm [Page 148] can differentiate
between hard and soft restrictions. The prioritized equal distribution [Page 146]
procedure assumes that all selected restrictions are hard and the other two
procedures do not take any restrictions into account at all.
• Selection indicator
You can use this indicator to activate an attribute for Model Mix Planning. If you do
not select this indicator, the attribute is not taken into account in planning. You can
also enter a description or a reason for the selection, if necessary.
The following attributes vary depending on the restriction category:
• Quantity restriction
Using the quantity restriction, you can define quantity limits for the characteristic
value combinations in the form of maximum and minimum quantities per day or shift.
Example: You can produce a maximum of 50 vehicles with air conditioning per shift.
• Spacing restriction
Using the spacing restriction, you can define a maximum interval between the
occurrence of the characteristic value combination.
Example: A minimum spacing of three for the characteristic “sunroof” means that, at
most, every fourth vehicle may be equipped with a sunroof.
• K-in-M restriction
Using the K-in-M restriction, you can limit the occurrence of a certain combination of
characteristic values in a defined partial sequence (interval). You can enter the
minimum number, the maximum number and the interval.
Example: At least two of five vehicles are to be assembled with sports seats.

The K-in-M restriction is very performance intensive in Model Mix Planning.

Therefore, you should try and use this restriction as little as possible and instead
use the quantity or spacing restrictions.
• Position restriction
Using this restriction, you can limit the occurrence of a certain combination of
characteristic values to a defined partial sequence or a particular position within the
complete sequence. This may make sense if, for example, you want to place a
prototype on a predefined position on the production line. You can assign a minimum
and a maximum position.
Example: In the shift in question, the vehicle is to be placed on the production line in
place 100 at the earliest and in place 101 at the latest.
• Block restriction
Using this restriction, you can limit the occurrence of a certain combination of
characteristic values to a particular number of products produced directly one after
the other on the production line.
Example:
At least five vehicles of the same color are to be produced in a row.
It does not make sense to use block restrictions if you use the prioritized equal
distribution [Page 146] procedure as the aim of this procedure is to distribute the
variants over the planning period evenly.
• Even distribution
Using this restriction, you can distribute products with a certain combination of
characteristic values evenly over the planning period.
Here, the system does not carry out sequencing for one day or shift only but for the complete
validity period of the restriction or for the complete planning horizon. This means, for example,
that the system also tries to adhere to the restriction between the last products of one day and
the first products of the following day.
The following diagram provides an overview of all the common attributes and the attributes
that depend on the restriction category.
Quantity
Quantity restriction
restriction Position
Position restriction
restriction
Common
Common attributes
attributes
•• Maximum
Maximum •• Maximum
Maximum
•• Minimum •• Start
Start date
date •• Minimum
Minimum Minimum
•• Time
Time unit
unit •• Start
Start shift
shift
•• Reference
Reference shift
shift Block
Block restriction
restriction
Spacing
Spacing restriction
restriction •• Hard restriction •• Minimum
Minimum
Hard restriction
•• Maximum
Maximum •• Maximum
Maximum
•• Weighting
Weighting of of soft
soft
•• Minimum
Minimum
restrictions
restrictions K-in-M
K-in-M restriction
restriction
•• Selection
Selection indicator
indicator •• Maximum
Maximum
Even
Even distribution
distribution •• Selection description
Selection description •• Minimum
Minimum
•• Interval
Interval

Characteristic Values and Combinations of

Characteristic Values
Use
Characteristics are objects in the class system. They are used to describe the features of
products. The individual values of a characteristic are simply known as the characteristic
values. A characteristic may be the engine of a vehicle, for example and the characteristic
values are then the various engine variants.
You can define restrictions for individual characteristic values or you can also define them for
a combination of several characteristic values. This means that characteristic value
combinations are links of characteristic values which you can use to define restrictions for one
specific product.
For example, you can define the following combination of characteristic values:
Characteristic:
Characteristic: Combination of of characteristic values
•• Engine
Engine type
type 1.
1. Petrol 2.0
2.0 and diesel
diesel 2.0
2.
2. Petrol 2.0
2.0 or petrol
petrol 3.0
Characteristic
Characteristic values:
values: 3.
3. Not
Not diesel 2.0
2.0 and not
not petrol
petrol 2.0
•• Diesel
Diesel 2.0
2.0
•• Diesel
Diesel 2.2
2.2
•• Petrol
Petrol 2.0
2.0
•• Petrol
Petrol 3.0
3.0
Integration
You define the characteristic value combinations for a restriction when creating the restriction
by accessing the dependency editor from the restriction.
Prerequisites
You must have created the characteristics in the Discrete Industries system and transfered
the data to the APO System using the APO Core Interface.
Features
• Every restriction is linked to exactly one combination of characteristic values. If you want
to define several restrictions for one combination of characteristic values, you have to
enter the definition of the characteristic values for every restriction.
• You can define the combination of characteristic values when creating a restriction in the
dependency editor using the same syntax rules as for selection conditions. When
changing a restriction, you can also change the combination of characteristic values.
However, you cannot assign an already existing combination of characteristic values to a
restriction.
• You can use the operators “and”, “or” and “not” when defining the combination of
characteristic values.
• You can also define restrictions for product numbers [Page 135].
• The combination of characteristic values has no separate period of validity – the system
only takes the validity of the restriction into account.
Example
You want to define a restriction for a vehicle which has air conditioning and a 3L petrol
engine. You could define the combination of characteristic values as follows:
Air_conditioning = “YES” and engine = “B30”

You want to define a restriction that has air conditioning but which is not right-hand drive. You
could define the combination of characteristic values as follows:
Air_conditioning = “YES” and not steering = “right”
Activities
You create the combination of characteristic values when creating the restriction [Page 137].
See also:
For more information on the definition of characteristics and characteristic values, refer to the
documentation on the Class System (CA-CL) under Object Dependencies for Characteristics
[External] and Characteristics (CL-CLCHR) [External].
Restrictions on Products
Use
As well as creating restrictions on combinations of characteristic values, you can also define
restrictions for product numbers. This means, for example, that not only can you define the
restriction for the characteristic Air conditioning, you can also define the restriction for the
product number of the air conditioning system. This may make sense if you can assembly
several product variants as air conditioning systems but you only want to create the restriction
for one particular product variant.
Prerequisites
• In Customizing for Model Mix Planning, in the IMG activity Defining Restrictions for Data
Elements, in the Characteristic field, you must enter a description of your choice for the
data element Product number.
• In the Discrete Industries System, you must have created a characteristic with the same
description and transferred it to the APO System using the APO Core Interface.
Features
In the restriction maintenance screen, you can define a restriction for the product number by
entering the defined characteristic in the characteristic valuation in the dependency editor.
The system treats this restriction in exactly the same way as a restriction on a “normal”
characteristic.
Validity Periods
Use
You can define a validity period for the attributes of the restrictions and also for the restriction
groups. Using the reference shift in the attributes of the restrictions, you can also determine
that the restriction is only to be valid for one particular shift.
The system only uses the attribute of a restriction for planning when all these validity periods
overlap.
Features
The following conditions must be fulfilled if the system is to use a restriction’s attribute in
period for planning:
• The period of the restriction group to which the restriction is assigned must be valid.

• You must have defined the validity period of the restriction comprising of a start date and
shift, an end date and shift and the reference shift.
• You must release the restriction.
• You must select the attribute of the restriction.
Example
The restriction group Standard production is to be replaced by the restriction group Christmas
th th
from the 15 December to cover the Christmas period. Then from the 15 January, the
restriction group Standard production is to be used again.
The restriction Diesel engine has only been assigned to the restriction group Standard
production. This restriction group is valid from today to infinity (31.12.9999).
Therefore, all attributes of this restriction are not valid from the start date of restriction group
Christmas to the second start date of the restriction group Standard production.
Today 15. December 15. January
Normal production
production Christmas
Christmas Normal production
production
Valid Valid
Restriction: Diesel engine
Activities
Use the function Check Restrictions [Page 139] to display all the restrictions valid for a certain
period.
Creating the Restriction Group

Use
This procedure describes how to create the first restriction group for a production line. In this
case, the system determines the sequence of the worksteps as you can only create
restrictions for a restriction group.
Procedure
1. Choose Production Planning → Automated Production Planning and Optimization →
Model Mix Planning → Create/Change Restriction Maintenance.
The Maintain Restrictions screen appears.
2. Enter the following data:
− Planning version. Note that you cannot later change the planning version.
− If necessary, the planning horizon which you can use to limit the selection of the
restrictions according to validity period.
− The production line to which you want to assign the restriction group. This line then
appears in the application as the default value.
3. If you also want to display the restrictions in the navigation tree of the application which
have been assigned to another planning version or another production line, select the All
indicator in the selection of the screen entitled Display other restrictions.

4. Choose .
The Restrictions: Maintain screen appears. In the data section, the system displays
the screen for creating the restriction group.
5. In the Restriction group field, enter the name of the restriction group and, if necessary,
you can also enter a description for the restriction group (optional).
6. Enter the start date of the restriction group.
− The system initially sets the end date of the restriction group to infinity. If, later, you
create other restriction groups for the same planning version and line, the start date
of the next restriction group determines the end date of this restriction group.
− Later, you can specify other start dates for the restriction group. This makes sense if
one particular restriction group is to be replaced by another group over the Christmas
period, for example. After Christmas, you can then restart the group that was
replaced.
7. If you want to change the production line you entered in the initial screen, you can still
change your entry in the Line field.
8. Choose .
The system copies the specifications of the restriction group and displays them in a
tabular overview.
9. Choose again.
Result
The system displays the restriction group in the navigation tree and you can immediately
create the first restrictions. Proceed by Creating Restrictions [Page 137].
Creating Restrictions
Prerequisites
• You must have created the characteristics and the characteristic values in the Discrete
Industries system and transferred the data to the APO System using the APO Core
Interface.
• You must already have created a restriction group for the planning version.
See also:
Creating the Restriction Group [Page 136]
Procedure
1. Select a restriction group in the navigation tree and choose Restriction.
In the data section of the screen, the system displays the sections Restrictions and
Restrictions in restriction group. If you have just newly created the first restriction
group for this planning version, the system automatically branches to this screen.
2. In the Name field, enter the name of the restriction and in the adjacent field a description.
3. If you do not want to release the restriction for planning immediately, select the Locked
indicator under Status.
4. Select a restriction category from the list provided. Note that you cannot change the
restriction category later.
5. In the Restrictions in restriction group, you assign the restriction to the appropriate
restriction groups. You can assign the restriction to several restriction groups.

6. Choose .
The system branches to the dependency editor where you can define the
combinations of characteristic values.
7. Make the characteristic valuation using the standard dependency editor syntax rules.
8. Check your entries in the characteristic valuation by choosing and correct any errors.
9. Choose to save your entries.
The system returns to the Restrictions: Maintain screen where the attributes of the
new restriction are now displayed. The Attributes [Page 131] vary depending on the
restriction category.
10. Enter the validity period, the limits for the combination of characteristic values and the
priority of each attribute (every row).
11. Then choose the Selection indicator to activate the attributes you want the system to take
into account in planning.
12. Choose to save the restriction.
Result
You have created a restriction. If you want to create more restrictions, you can use this
restriction as a template by choosing Restriction.
Working with Restrictions

Use
This procedure describes how you can work with the restrictions you have already created.
Procedure
1. If you want to assign a restriction to another restriction group, you can do this using the
drag & drop technique.
You can also choose Restriction and then select the restriction group in the table.
2. To delete a restriction, select it and then choose Restriction.
i. The system deletes the restriction from all restriction groups.
If you want to delete a restriction group, you must already have deleted all your
restrictions.
3. If you want to copy a restriction,
a. Select it and choose Restriction.
b. Then enter a name for the new restriction and choose .
The system copies the attributes and the characteristic valuation of the restriction.
4. You can change the description of a restriction or of a restriction group by selecting it and
choosing Restriction or Group.

Copying Restrictions of Other Lines and Planning

Versions
Use
You can use this procedure if you want to copy restrictions with any planning version and line
assignment to a restrictions group. This may make sense, for example, if you first create the
restrictions for a planning version you want to use for simulation. Then you can copy the
restrictions as necessary to the productive planning version.
Procedure
Model Mix Planning → Create/Change Restriction Maintenance.
The Maintain Restrictions screen appears.
2. Enter the planning version, the planning horizon and the production line to which you
want to copy the restrictions.
3. In the section of the screen entitled Display other restrictions, select All. In so doing, you
instruct the system to display the restriction groups of all planning versions and of all
production lines in the navigation tree.
4. Choose .
The Restrictions: Maintain screen appears. In the navigation tree, the system displays
all restriction groups under the folder Further groups. You can now copy the
restrictions from these restriction groups using the drag & drop technique. However,
you cannot process them.
5. Select a restriction and drag it to a restriction group of the production line you used to
access the transaction.
The system displays a dialog box in which you can give the copied restriction a new
name.
6. In the field, New name enter a name or you can also simply use the name of the copied
restriction.
Make sure that the copied restrictions no longer have any reference to the old
restrictions. Even if you also copy the old name of the restriction.
7. Choose to create the restriction.
Result
You have copied a restriction. You can also select several restrictions and copy them to the
appropriate restriction group together.
Checking Restrictions
Use
You can use this function to check which restrictions the system selects and passes on to
Model Mix Planning in a certain period.
In the restrictions, you can define different validity periods for restriction groups and attributes.
You can also assign a status to the restrictions and you can determine exactly which
attributes are to be selected and which are to remain inactive. Once you have determined the

validity periods and areas of validity, you can use this function to define which restrictions are
to be passed on to Model Mix Planning in certain periods or only for one particular shift.
Procedure
Model Mix Planning → Check Active Restrictions.
2. Enter the planning version.
3. Enter the planning horizon including the start shift and the final shift.
4. Enter the appropriate line in the Line field.
5. Choose .
Result
In a list, the system shows the attributes of the restrictions in separate rows selected
according to the planning horizon.
Examples for Restrictions

Below is an example for every restriction category.
Quantity restriction
As your system supplier can only deliver a maximum of 300 sunroofs a day, define a quantity
restriction for the characteristic value:
sunroof = 'Y'
Here, define the following attribute for the restriction:
Start
Start Start
Start End
End End
End Ref.
Ref. Min.
Min. Max.
Max. Time
Time Hard
Hard Weigh-
Weigh-Selec-
Selec- Selection
Selection
date
date shift
shift date
date shift
shift shift
shift unit
unit ting
ting tion
tion description
description
1.06.
1.06. 11 31.12.
31.12. 11 300
300 Day
Day X
X X
X Mandatory
Mandatory
2001
2001 9999
9999
•
st
The restriction’s attribute starts on the 1 June 2001, in the first shift and is initially valid to
infinity as no other attribute has been maintained.
• The attribute is hard as this restriction may not be violated.
• The attribute also receives the selection indicator with the comment ‘Mandatory’ as the
restriction is required as a result of the supplier’s capacity situation.
Spacing restriction
One employee in production is responsible for assembling air conditioners in the night shift.
He requires three takts to assembly an air conditioner. Therefore, you define a spacing
restriction in which you define that, at most, every fourth vehicle may have air conditioning.
The characteristic value is as follows:
air_condition = 'Y'
Start
Start Start
Start End
End End
End Ref.
Ref. Min.
Min. Max.
Max. Hard
Hard Weigh-
Weigh-Selec-
Selec- Selection
Selection
date
date shift
shift date
date shift
shift shift
shift ting
ting tion
tion description
description
1.06.
1.06. 33 31.12.
31.12. 33 33 33 11 X
X --
2001
2001 9999
9999

•
st
The restriction’s attribute starts on the 1 June 2001, in the third shift (night shift) and is
initially valid to infinity as no other attribute has been maintained.
As more employees are available in the other two shifts, enter the third shift as
reference shift so that this attribute is only valid for the night shift.
• The minimum spacing allowed for the air conditioners is three. This means that, at most,
every fourth vehicle may be equipped with an air conditioner.
• The attribute is not hard as this restriction may be violated occasionally. However, you set
the weighting very high at 1.
• The attribute also contains the selection indicator meaning that it is active.
K-in-M restriction
As a result of the assembly team leader’s experience, you know that the production load in
summer is very evenly distributed if at least three of five vehicles are equipped with a petrol
engine. Therefore, you define a K-in-M restriction with this condition for the following
characteristic value:
engine = 'petrol'
According to the current demand program, however, the percentage of diesel vehicles falls
from September which is why you then want to produce four out of five vehicles with a petrol
engine.
Start Start End End Ref. Min. Max. Inter- Hard Weigh- Selec- Selection
date shift date shift shift val ting tion description
1.06. 1 31.08. 3 2 3 5 2 X Up to
2001 2001 September
1.09. 1 31.12. 3 2 4 5 2 X From

2001 9999 September
•
st
The first attribute for the restriction starts on the 1 June 2001 in the first shift and is valid
st
until the second attribute starts on the 1 September. The second attribute is valid to
infinity.
• After the first attribute, at least 2 and a maximum of 3 out of 5 vehicles in the sequence
may be equipped with petrol engines.
• After the second attribute, at least 2 and a maximum of 4 out of 5 vehicles in the
sequence may be equipped with petrol engines.
• The attribute has not been indicated hard but as been assigned a high weighting as, in
individual cases, other sequences may also be produced.
• The attributes also contain the selection indicator. That is, they are active.
Position restriction
The Research & Development department wants to test a prototype in production. For this
purpose, the development engineers are going to visit the production line at 10.00 am to
monitor the production of the prototype. Therefore, you define a position restriction for the
following combination of characteristic values:
etype22 = 'YES'
Start Start End End Ref. Min. Max. Time Hard Weigh- Selec- Selection
date shift date shift shift unit ting tion description
1.06. 1 31.12. 3 100 105 Tag X X

2001 9999

•
st
The attribute for the restriction starts on the 1 June 2001 in the first shift and is valid to
infinity.
• The vehicle is to be given a sequence number between 100 and 105 in the day’s
sequence.
• The attribute is hard as the engineers can only be at the production line during this time.
Block restriction
In order to run your paint shop economically, it is important to assemble as many vehicles of
the same color as possible in sequence. Therefore, define a block restriction in which at least
5 red vehicles must be produced in sequence. The combination of characteristic values is as
follows:
v_color = 'RED'
Start Start End End Ref. Min. Max. Hard Weigh- Selec- Selection
date shift date shift shift ting tion description
1.06. 1 31.12. 3 5 2 X
2001 9999
•
st
infinity.
• At least five red vehicles are always to be produced in sequence.
• The attribute has a soft weighting, but has been given a high priority as the restriction
strongly influences the affectivity of the production line.
Even distribution
You produce a certain percentage of right-hand drive vehicles. You want to evenly distribute
the production of these vehicles over the planning horizon so that your assembly capacities
are evenly loaded. For this purpose, you define an even distribution restriction with the
following combination of characteristic values:
steering_r = 'YES'
Start Start End End Ref. Weigh- Selec- Selection

date shift date shift shift ting tion description
1.06. 1 31.12. 3 4 X
2001 9999
•
st
infinity.
• At least five red vehicles are always to be produced in sequence.
• The attribute has been given a soft weighting and has not been given a very high priority.
You cannot assign a hard restriction when using the even distribution restriction as this
would not make good business sense.

Carrying Out Model Mix Planning

Purpose
This process describes the entire procedure that you can use for model mix planning for your
takt-based flow manufacturing. First of all you carry out a model mix planning run in the
background, for a longer planning horizon. Then you check the result for the medium-term to
the long-term horizon in the product planning table and for the short-term horizon in
sequencing.
Prerequisites
• In the Discrete Industries System, in Integrated Product and Process Engineering (iPPE),
you have to create a line structure. The line structure can consist of one individual line or
a line network.
For a line within the line network, you must select the indicator, Planning segment
and the indicator Model Mix Planning allowed (see also: Planning segment [External]
in Line Design).
Also note that with model mix planning you can currently only plan line networks
that only have sequentially arranged line elements. Line elements arranged in
parallel cannot be planned.
• You have transferred the customer orders, the pre-planning requirements and the
planned orders from the OLTP System (Discrete Industries), or created them in the APO
System.
• If you want to carry out planning taking account the restrictions, you have created the
restrictions in the system. In addition, in this case, these orders have to be evaluated.
Process Flow
1. You start the model mix planning run to carry out planning for a planning version and a
line structure, over a certain planning horizon.
2. First of all the system determines the orders, the requirements and the valid restrictions
that lie in the planning horizon.
3. The system gradually processes the individual horizons with the procedures assigned, as
you have defined in your procedure package, and then posts the changes (see also:
Model Mix Planning Run [Page 150] ). The planning basis [Page 149] of the relevant
procedure has a strong influence on the planning result.
4. You can display or manually process the planning result in the product planning table
[Page 159] or in the interactive sequence schedule [Page 154] .
Result
You have carried out the model mix planning for the desired planning horizon.
• At this point the planned orders do not yet contain any components. Therefore you carry
out requirements planning in connection with model mix planning, using the planning
matrix [Page 161] or a classic single explosion.
• If you have linked the APO System to a subsystem, you can transmit the planning to this
system using the transfer of order sequences [Page 435] .

Procedure
Use
In model mix planning you can use procedures of varying complexity, depending on the
planning result and horizon desired. SAP delivers four procedures as standard.
• Material requirements planning procedure
This very simple procedure serves to create planned orders for the uncovered
requirements in the planning horizon.
• Percentage smoothing
This procedure servers to divide the orders equally across the planning periods, in
order to achieve a hundred percent load per period.
• Prioritized equal distribution
This procedure serves to distribute the variants equally within a planning period (day,
shift) and to distribute according to priority.
• Genetic algorithm
This procedure serves to reproduce an optimum sequence of orders, taken into
account all restrictions and customers’ preferred dates.
Activities
You can integrate the procedures in a model mix planning run [Page 150] or you can also call
them up in the interactive sequence schedule [Page 154] .
Requirements Planning Procedure

Use
You can use this simple procedure in the long-term planning horizon, for example, if you
simply want to carry out a net requirements calculation for primary requirements. The system
determines requirements that have not been covered and then creates planned orders for
them.
Integration
You can only use this process by integrating it in Customizing for model mix planning in a
procedure package. You cannot start this procedure from interactive sequencing, as it does
not create any order sequences. Also, you cannot set any further parameters.
The procedure is defined in the function module /SAPAPO/SEQH_PURE01_CALL.
Features
• The requirements planning procedure does not take restrictions or customer dates into
account.
• Depending on the planning basis [Page 149] chosen, it creates cumulated planned order
quantities on a daily or shift level, or planned orders with quantity 1.

Percentage Smoothing
Use
With this simple procedure you can reach a hundred-percent period load, preferably in the
medium to long-term horizon. This operation is also called period-slot creation. In this way the
system checks the load of a period and
• in the case of overloading, moves orders back
• in the case of underloading, fills the period with orders from the following periods.
Integration
You can only use this process by integrating it in Customizing for model mix planning in a
procedure package. You cannot start this procedure from interactive sequencing, as it does
not create any actual order sequences. Also, you cannot set any further parameters.
The procedure is defined in the function module / SAPAPO/SEQH_PG01_CALL.
Features
The procedure determines the operating time of the line from the lines resource and begins to
determine requirements, beginning with the first period of the horizon defined:
• If there is available capacity in the operating time, the system moves orders from the
subsequent period forward, until the operating time is fully loaded.
• If the capacity is overloaded, the system moves orders to the next period, without taking
account its load.
After it has processed the period, it continues with the following period until it has reached the
end of the horizon.
• When moving orders from a period, the system does not simply take the last orders in the
period, but maintains the quantity relationship of the period. The quantity relationship
refers to the pegging areas, which are made up of product, location, account assignment
object, and planning version.
• The procedure does not take restrictions or customer dates into account.
• The procedure does not carry out sequencing on the orders, but simply creates
cumulated planned order quantities on a daily or shift level.

Load
100%
Start horizon End horizon
100%
Start horizon End horizon
Prioritized Equal Distribution

Use
With this procedure you can distribute the orders equally across the planning horizon,
corresponding to their configuration. In the distribution, the procedure gives priority to the
orders whose characteristic values are the most common in the given quantity of orders.
You can use this procedure as follows:
• If you produce a small number of variants in lots, you can create individual orders for the
lots, and then distribute the individual products to achieve an equal load in the assembly.
• If you produce highly-configurable products, you can use the procedure in the medium to
short-term to create a temporary sequence in this horizon. For the short-term, you can
then use a more complex procedure such as the genetic algorithm, and thus improve the
quality of the sequence.
Integration
You can carry out this procedure by:
• Integrating it in Customizing for model mix planning in a procedure package for the model
mix planning run
• Accessing it from the interactive sequencing.
The procedure is defined in the function module /SAPAPO/SEQH_BS01_CALL and uses the
table /SAPAPO/SEQC_BSV.
Parameters
The procedure can take into account all restriction categories except block restrictions. When
you call up the procedure, you can determine which restriction categories should be taken
into account, and up to which weight. For example, you can determine that only those
quantity restrictions should be taken into account, that are weighted with priority 4 or higher.

You can save the parameters in a processing profile in Customizing for model mix planning,
or you can enter it again every time you call up the procedure.
Note however, that the prioritized equal distribution interprets all restrictions
selected as hard. The procedure cannot differentiate between hard and soft
restrictions.
See also:
Restriction Categories and Attributes [Page 131]
Features
In the planning, the system proceeds as follows:
1. The prioritized equal distribution begins at the beginning of the planning horizon and
determines the given orders and the relevant characteristics. The characteristics in which
you have defined restrictions are relevant.
2. The system calculates the priority of each relevant characteristic by dividing the
occurrence of the characteristic by the number of products. It also makes note of this
priority for all other iterations.
3. The system calculates the prioritization of each order, by adding up the priorities of its
relevant characteristics.
4. It schedules the order with the highest priority, as long as there are no restriction
violations.
− If the order does not fulfill the restrictions, it checks the order with the next highest
priority.
− If none of the orders in the period fulfill the restrictions, the system checks the orders
from the following period (day or shift) and brings these forward.
− If no orders in the planning horizon fulfill the restrictions, the system schedules the
order with the highest priority.
As the prioritized equal distribution regards all restrictions as hard, each

restriction violation is also a hard restriction violation. The system does not cancel
the procedure, but still schedules the orders.
5. After it has scheduled an order, the system recalculates the priorities. In addition, it adds
the priorities determined in step 2 to the priority of the order for each characteristic. In the
first iteration, the priorities of the characteristics double. However, for the characteristics
that occurred in the last order scheduled, the system subtracts the number 1.
6. The system repeats steps 3 to 5 until all orders have been scheduled.
Example
Initial sizes:
• Number of products: 100
• Occurrence of characteristic A: 50
• Occurrence of characteristic B: 40
• Products without characteristics: 30
• Restrictions are not taken into account here.
It follows that:
• Priority of characteristic A = 50/100 = 0.5

• Priority of characteristic B = 40/100 = 0.4

First iteration:
• If an order contains characteristic A and characteristic B, it has priority 0.9
• If an order only contains characteristic A, it has priority 0.5
• If an order only contains characteristic B, it has priority 0.4
• If an order does not contain any characteristics, it has priority 30/100 = 0.3
An order with characteristics A and B is therefore scheduled first.
Second iteration
The system determines the priorities of the characteristics again, by adding the
priority determined above to each characteristic and subtracting one from the
scheduled characteristics:
• Characteristic A was scheduled in the first iteration: priority = 0.5 + 0.5 – 1 = 0
• Characteristic B was scheduled in the first iteration: priority = 0.4 + 0.4 – 1 = -0.2
This results in the following priority for the orders:
• If an order contains characteristic A and characteristic B, it has priority -0.2
• If an order only contains characteristic A, it has priority 0
• If an order only contains characteristic B, it has priority -0.2
• If an order does not contain any characteristics, it has priority 0.3 + 0.3 = 0.6
An order without characteristics is therefore the next to be scheduled.
The next iterations follow the same schema.
Genetic Algorithm
Use
This procedure is based on the principle of evolution. You can use it in the short-term
planning horizon if you want to create an order sequence that takes into account all customer
preferred dates as well as all restrictions.
In the procedure, the system creates several sequences, which it then evaluates. Only the
sequences with the best evaluation appear in the next evaluation and are then improved here.
Integration
You can carry out this procedure by:
• integrating it in Customizing for model mix planning in a procedure package for the model
mix planning run
• accessing it from interactive sequencing.
The procedure is defined in the function module /SAPAPO/SEQO_GA01_CALL and uses the
table /SAPAPO/SEQC_GAV.
Parameters
• The procedure can take into account all restriction categories [Page 131] . When you call
up the procedure, you can determine which restriction categories should be taken into
account, and up to which weight. For example, you can determine that only those quantity
restrictions should be taken into account, that are weighted with priority 4 or higher.

• The procedure can take into account a date earlier or later that the customer’s preferred
date. When you call up the procedure for make-to-order production and for make-to-stock
production, you can set whether you want to tolerate an earlier or later date.
• You can limit the maximum run time of the procedure. Although the procedure usually
reaches a good result after one minute, you can improve the result with a long run time.
You can save the parameters in a processing profile in Customizing for model mix planning,
or you can enter it again every time you call up the procedure.
Features
In the planning, the system proceeds as follows:
1. The genetic algorithm begins at the beginning of the planning horizon and determines the
given orders and the relevant characteristics. The characteristics in which you have
defined restrictions are relevant.
2. After the start sequence transferred, the system creates any further sequences and
evaluates them using penalty points. The evaluation is guided by the violations of the soft
restrictions or the observance of the customer’s preferred dates. For example, an interval
restriction that has been exceeded of the maximum interval of 2, receives more penalty
points than an interval restriction that has only been exceeded by one item. The number
of penalty points grows quadratically with the violation of the items.
3. The system retains the sequences with the best evaluation and tries to improve these. It
does this by creating part sequences from the sequences it has transferred, and arranges
these in different ways.
4. From the newly created sequences, it again transfers those with the best evaluation and
repeats step 3, as long as the maximum run time of the procedure has not yet been
reached.
If a hard restriction violation occurs, which the genetic algorithm cannot resolve,
the system ends the procedure. The sequence of the orders remains as it was
before the procedure. As long as this happens within the model mix planning run,
the system continues with the next planning horizon.
Planning Basis and Planning Result

Use
With this function you determine whether the system
• should only refer to APO planned orders or uncovered requirements as the planning
basis
• should create only APO planned orders with order quantity 1 (individual orders) or
cumulated for the amount of the requirements per period.
Integration
You determine the planning basis and the planning result in the list field Planning basis, when
you determine the horizons of a procedure package in Customizing for model mix planning.
Features
• Requirements-based, cumulated per day or shift:

For planning, the system refers to all APO planned orders and all requirements in the
form of customer orders and planned independent requirements (net requirements
calculation). It creates APO planned orders with an order quantity greater than 1 as
the planning result. The requirements are grouped either daily or per shift, depending
on your settings. The planning run sets the start date of the planned orders at the
start of the shift or at the beginning of the workday. You use these settings preferably
in the long-term planning horizon for the percentage smoothing or the MRP
procedure, if you do not want to carry out sequencing.
• Requirements-based with individual orders:
For planning, the system refers to all APO planned orders and all requirements in the
form of customer orders and planned independent requirements (net requirements
calculation). For uncovered requirements, it creates APO planned orders with order
quantity 1. The system deletes non-firmed planned orders with an order quantity
greater than 1, and recreates them as planned orders with order quantity 1. In the
same step it carries out takt-based scheduling.
You can use this setting in the medium-term planning horizon for the prioritized equal
distribution or the genetic algorithm.
• Order-based with individual orders:
For planning, the system only refers to those APO planned orders that already exist
in the system. If there are planned orders with an order quantity greater than 1, it
deletes them and creates new APO planned orders with order quantity 1. In the
same step it carries out takt-based scheduling.
You can use this setting in the short-term planning horizon for the prioritized equal
distribution or the genetic algorithm.
You can carry out sequencing in connection with takt-based scheduling, only for
individual planned orders. For prioritized equal distribution, or for the genetic
algorithm, you should therefore use individual orders.
Model Mix Planning Run

Use
With this function you can carry out automatic planning over a large planning period, which
you divide into several planning horizons.
In this way you can gradually increase the level of detail of the planning by using procedures
of varying complexity in the corresponding planning horizons. The gradual planning could
take the following form, for example:
• In the long-term horizon, you want to achieve a 100% line load, and thus create
cumulated planned orders on a period level.
• In the medium-term horizon you want to create a provisional sequence and thus take all
quantity restrictions into consideration.
• In the short-term horizon you plan the final sequence considering all restrictions and
customers’ preferred dates.
Integration
Customizing
You define the composition of the planning run in Customizing for model mix planning in a
procedure package. Here, you enter the individual procedures and determine the length and

number of planning horizons. You assign any procedure to each horizon. You can also
determine the following functions:
• Adjustment periods
Using the adjustment periods between the procedures, you can allow the planning
horizons to overlap. Then the system transfers the orders that it scheduled at the end
of a planning horizon to the next planning horizon and thus the next procedure. This
makes sense, as the orders from a procedure that cannot be brought into a permitted
sequence, are scheduled at the end of the planning horizon.
• Planning offset
If you do not want to make any more changes in the short-term horizon, you can
enter a planning offset in the procedure package. Then you can start the first horizon
of the planning run starting from the current date, delayed by a few days or shifts.
• Planning basis
The planning basis [Page 149] determines whether:
− the system carries out a net requirements planning before the procedure
− the system creates cumulated or individual planned orders as the planning result.
• Processing profile
For the prioritized equal distribution and the genetic algorithm, you can create a
processing profile in Customizing for model mix planning. You then enter the
processing profile in the planning horizon.
Heuristics
You can start the planning run manually or schedule it as a background job. In addition, you
can integrate the model mix planning run as a heuristic in the production planning run of the
APO System. For example, you can carry out a planning run every night, and thus periodically
update your planning.
See also:
Integrate as Heuristic in Production Planning Run [Page 153].
Prerequisites
• In Customizing for model mix planning you have defined a procedure package for the
planning run.
• You have defined the restrictions corresponding to your requirements.
• There are orders (evaluated) or requirements in the planning period.
Features
If you start the planning run, the system processes the horizons per time period, beginning
with the short-term horizon. It deals with each horizon in the following way:
1. The system imports the orders and the requirements for the relevant horizon.
Depending on the planning basis you have set in the procedure package, the system
only considers:
− the orders that are already in the system
− the orders that are already in the system as well as the requirements. In this case it
carries out a net requirements calculation.
2. The system determines the restrictions that are valid and activated in the planning
horizon.

3. The system compare the characteristics of the orders determined with the characteristics
of the restrictions determined. Only the characteristics in which restrictions are
maintained are relevant for planning.
4. The system calls up the procedure and proceeds as follows;
− If you have set a planning basis with cumulated planned order quantities for the
relevant procedure, the system schedules all orders in parallel with the period start as
the start date. Sequencing does not, therefore, take place.
In this case you display the planning result in the product planning table [Page
159] , and if necessary you process it manually.
− If you have set a planning basis with individual planned orders, the system carries out
sequencing in connection with a finite takt-based scheduling without gaps.
In this case you display the planning result preferably in the interactive sequence
schedule [Page 154]. Here you can view a tabular overview of the order
sequence with the relevant data, such as the dates or the characteristic
evaluation.
5. If you have defined an adjustment period, the procedure transfers the orders within the
adjustment period to the following procedure.
6. The system compares the planning results and posts the changes.
7. The system continues with the following procedure.
Example
The following diagram displays a possible planning run with three procedures that SAP
delivers as standard:
Update
Step 1
Gen. algorithm
Orders,
reqmts
Update
Step 2
Equal distribution
Orders,
reqmts
Update
Step 3
Percentage smoothing
Orders,
reqmts
Horizon 1 Horizon 2 Horizon 3 Time
Adjustment horizon
Access Model Mix Planning

Procedure
Model Mix Planning → Model Mix Planning Run.
This takes you to the screen Model Mix Planning Run.
2. Enter a planning version.

3. In the field Model mix procedure, enter a procedure package.

4. Enter the line structure for which you want to plan. This can be a line network or a line.
5. If you want to test the definition of the procedure, choose Definition of the model mix
procedure. This takes you to Customizing for Model Mix Planning.
6. Choose .
The system carries out the planning run corresponding to the procedure package.
Result
You can display the planning results in the interactive sequence schedule [Page 154] or in the
product planning table [Page 159] .
Integrate as Heuristic in Production Planning Run

Use
You can use this function if you want to carry out the model mix planning run periodically in
the background, such as every night, or every weekend.
Integration
The production planning run is provided within production planning and detailed scheduling in
the APO System for periodic planning with heuristics. For further information see Heuristics
[Page 207] .
Prerequisites
In Customizing for Production Planning and Detailed Scheduling you have to create a
procedure package as a heuristic for the model mix planning run. To do this, enter the name
of the procedure package as the heuristic, and the function module
/SAPAPO/SEQ_MODELMIX_RUN_01 as the function.
Features
With the integration in the production planning run, you can have the system trigger a model
mix planning run hourly, daily, weekly or monthly.
Activities
1. Choose Production planning →=Automated production planning and optimizing
→=Production planning run to create a variant for background planning.
Enter the heuristic defined next to the global settings, under Function/Heuristic and
the object 6 (line networks).
Choose to show the selection fields of the lines, and then enter the lines you
want.
2. Choose Production planning →=Automated production planning and optimizing →
Production planning run in background, and schedule the variant periodically.

Sequence Schedule
Definition
With this object you can display, evaluate, and process the results of model mix planning. The
sequence schedule represents the sequence of the APO orders for a planned version and a
line structure, in table form. It provides information about all detailed data, such as the start
and end dates or the characteristics evaluation.
In addition, you can check the quality of the sequence by displaying the restriction violations.
Then you can move the orders manually, or carry out an individual procedure.
Structure
The sequence schedule consists of a navigation tree and four detailed data areas:
• Navigation tree
The navigation tree displays all days of the planning horizon in the first hierarchy
level that you have entered in the initial screen. In the second hierarchy level, it
displays the shifts or the daily standard available capacity.
You can select the periods in the navigation tree that you want to display in the
detailed data area.
You can only change sequences if all orders have order quantity one. If a shift or a
day in the planning horizon contains an order with order quantity greater than one,
the navigation tree has the symbol in the second level, instead of the symbol .
In this case you have to carry out takt-based scheduling with individual orders, before
you can move to change mode. You can also reduce the planning horizon so that
only orders with quantity 1 remain in the horizon.
Alongside the total order quantity and the operating time of the line, the navigation
tree also shows the load per shift. Using the status symbols, you can establish
whether the operating time is being used to its full capacity, , not being used to full
capacity , or overloaded .
• Restrictions
In this area, the sequence schedule shows the attributes of the restrictions, which are
valid in the current time period selected. These attributes are taken into account in
sequencing.
• Backlog
In this area, the system displays the planned orders that are scheduled before the
current date, but which have not yet been released for production.
• Scheduled orders
In this area, the system displays the planned orders that are scheduled in the time
period currently selected. The status symbols show you whether you can still
reschedule an order, or whether it is already in production.
• Rescheduled orders
In this area the system displays the rescheduled planned orders. Rescheduled orders
initially do not cover requirements any longer, and do not load the capacity of the line
resource. However, if you carry out a new model mix planning run, it takes the
rescheduled orders into account and schedules them again.
The orders in this screen do not depend on the planning horizon that you have just
selected. The system always displays all rescheduled orders.

Integration
The data relevant for planning is imported each time the sequence schedule is accessed, so
that it always displays the current data. However, you can only move to the change mode if all
orders have order quantity 1 and are scheduled in takts. If this is not the case, you can start
individual orders in connection with takt-based scheduling, from sequencing.
Access Sequence Schedule

Procedure
Model Mix Planning → Sequencing.
The Sequencing screen appears.
2. Enter a planning version.
3. In the Planning horizon area, enter the time period you want to display.
4. Enter the line structure for which you want to plan. This can be a line network or a line.
5. Choose .
The system reads the available operating time of the line resource and the planned
orders that are within the time period, and then calls up the sequence schedule in
display mode.
The sequence schedule displays the time period you have specified only in the
navigation tree. In the detailed area Scheduled orders, it does not yet show any
orders.
6. You can select the time period that you want to look at in the area Scheduled orders, by
− double clicking on a day or a shift
− dragging a day or a shift to the data area with drag & drop
− selecting a period and then choosing Scheduled orders with the right mouse button.
If you want to display a larger period of time, you can also select several days by
holding down the Shift key or the Ctrl key.
The system displays the lists in the data area with the SAP List View (ALV),
which is used in many SAP applications and which offers many generic display
functions. For further information on the SAP List Viewer see the documentation
Introduction to the SAP System under Lists.
7. You can only move to change mode of the sequence schedule if all orders that are in the
planning horizon of the navigation tree, have order quantity 1, and are scheduled in takts.
− If this prerequisite is not fulfilled, then first of all carry out takt-based scheduling with
individual orders, by choosing . After takt-based scheduling, you will automatically
be in the change mode.
− If you do not want to schedule the entire planning horizon in takts, which you have
displayed in the navigation tree, you can reduce the horizon beforehand. To do so,
select the days in the navigation tree in blocks that you want to exclude, and choose
.
− If the prerequisites are fulfilled, choose to move to change mode.

Result
You have called up the sequence schedule and moved to change mode. You can now
process the sequence manually, start a process or recalculate the restriction violations.
Displaying the Characteristics

Use
With this function you can display the evaluation of ten characteristics per order, directly in
one column of the sequence schedule. In this way the characteristics that are particularly
important or critical for your production are available in planning, directly in the overview.
To be able to visually differentiate between characteristics columns, you can mark each
column with a different color.
Integration
You define which characteristics the system is to display within the sequence schedule, in the
characteristic views in Customizing for model mix planning. You can define as many
characteristic views as you wish, and in each you can enter up to ten characteristics. In
addition, enter a description for a characteristics view and the background color for the
column in the sequence schedule.
As you can also display these characteristic views in other applications such as the product
planning table, you can specify for which applications a characteristics view should be valid.
Features
• You can define as many characteristic views as you wish, and in each you can enter up
to ten characteristics.
• From sequencing you can switch between the characteristics views.
• From sequencing, you can branch to the maintenance of the characteristics views in
Customizing.
• For the detailed data areas Backlog, Scheduled orders and Reschedule orders, you can
display different characteristics views.
• If you have displayed the characteristics in Sequencing, you can also select orders with a
specific Characteristic evaluation [Page 156] .
Activities
If you want to display a characteristics view, chose in the relevant data area and then
select the view you want.
Characteristics-Based Selection
Use
With this function you can select all orders in the list, which have a specific characteristic
value assignment. In this way you can select and deallocate all vehicles in the coming shift
that have a sunroof, for example, if the vendor responsible cannot deliver in this period.
Prerequisites
You have included the relevant characteristic in a characteristic shift, and displayed this in the
sequence schedule.

Procedure
1. Select the columns of the characteristic desired.
2. If you want to select the orders of a specific row (item) of the sequence schedule first of
all, also select this row.
3. Choose .
This takes you to the dialog box Characteristics-based selection.
4. In the section Enter selection values, enter the characteristic evaluation that you want to
select.
Note that the system differentiates between lower and upper case in the
characteristics.
5. If you want to limit the number of orders selected, also enter a maximum number.
6. Choose .
The system selects all orders with the corresponding characteristic evaluation.
Display the Restriction Violations

Use
With this function you can calculate and display the restriction violations of the sequence
currently displayed. In this way you can ascertain which restrictions are violated, and how
often. In addition, the system calculates a so-called fitness level, which represents an
evaluation number for the quality of the total sequence.
Features
• The system temporarily saves the result of each calculation that you make in the current
sitting. In this way you can compare the quality of various sequences.
• In the result log, status icons show you which type of violation has occurred:
− No restriction has been violated
− A hard restriction has been violated
− A soft restriction has been violated
For each violation of a soft restriction, the system gives penalty points that are also
dependent on the gravity of the violation. For example, if a restriction allows a
maximum interval of two items, a violation with an interval of three items will receive
less penalty points than a violation with an interval of four items. The sum of the
penalty points gives you the fitness of the sequence. A fitness of 0 means that no
restrictions have been violated.
When soft restrictions are violated, the system also specifies the following values for items
restrictions, block restrictions, interval restrictions and ‘K-in-M’ restrictions:
• Maximum violation
Specifies the maximum violation in items. For example, in a block restriction that
allows a maximum block size of 3, a block of 5 could be the greatest violation. The
system would then give a 2, for the maximum violation.
• Average violation

Specifies the average violation in items. For example, in a block restriction that allows
a block size of 3, blocks could occur with 4 and 5 products. The system adds the
items of each violation and divides them across the entire number of violated
restrictions. The system rounds the result up and displays it.
Sum of individual violations in items

Average violation =
Total number of restrictions violated
Activities
In the sequence schedule choose and then the entry Recalculate, or one of the
temporarily stored calculations, according to the time.
Change Planning Manually

Use
In the change mode of the sequence schedule, you can process the planning manually. You
can:
• move and firm scheduled orders to a different item
• deallocate scheduled orders
• reschedule deallocated orders or orders in the backlog
• start a process manually.
In addition, the general functions of the SAP List Viewer (ALV) are available to you, such as
printing the list.
Prerequisites
• You have called up the sequence schedule in change mode.
• If you want to start a procedure manually from sequencing, you must have selected the
indicator Interactive for the procedure, in Customizing for model mix planning, in the work
step Define procedure packages, under Individual procedure.
Procedure
• You can move an order in the sequence schedule using drag & drop, by:
− dragging to another item within a detailed data area
− moving to another detailed data area.
• You can also change the planning, by
− selecting an order in the area Scheduled orders, and selecting to deallocate it
− selecting an order in the area Deallocated orders or Backlog, and selecting to
schedule it.
If you move an order to another item within the area Scheduled orders, the system
automatically firms the order to the item. The order will then no longer be moved if
you start a procedure.
Deallocated orders no longer have any effect on requirements and require no
resources.
• If you want to firm an order manually, choose .

• If you want to stop this choose .

• If you want to start a procedure, choose and then the procedure you want.
In the following dialog box you can set the parameters for the procedure. You can
specify a processing profile, which you defined in Customizing, or you can enter all
parameters manually.
Display in the Product Planning Table

Use
You can use this display if you have created planned orders with cumulated quantities, on a
shift or daily level as a planning result. The period-based view and the view of the individual
elements support you in displaying and reprocessing the planning result.
Integration
For further information see the documentation on the product planning table [Page 324].
Features
The product planning table gives you a good overview of the entire planning situation, in
various subscreens. You can, for example, also display the preplanning requirements and the
resource load for several lines, as well as product views for a period basis or individual
elements.
Activities
1. Choose Production planning →=Interactive production planning →=Product planning table.
The Product planning table screen appears.
2. Enter the planning version and planning horizon.
3. On the tab page Line / Resource in the field Line, enter the appropriate line structure.
4. Choose .
This takes you to the product planning board, from where you can view and process
the planning.
Takt-Based Scheduling in Model Mix Planning

Use
Takt-based scheduling is a type of scheduling, which is specially used for takt-based
production lines. As model mix planning is intended for planning takt-based production lines,
you can only work with takt-based scheduling here.
The system does not calculate the lead time of an order from the duration of the activities, but
by multiplying the number of takts with the takt time. Therefore, the takt time is the reciprocal
of the rate.
Integration
Takt-based scheduling is based on the master data of iPPE Line Design. Here you can divide
your line into line segments over as many hierarchy levels as you wish, and group several
lines to line networks.
See also:

For further information see the documentation of iPPE Line Design [External] under Takt-
based scheduling [External] .
Features
Note the following points in model mix planning:
• You can only plan line networks, whose lines are all arranged sequentially. You cannot
plan lines arranged in parallel.
• You can only carry out takt-based scheduling if you have already separated the orders.
You cannot schedule orders with an order quantity larger than one.
• In model mix planning it is usually assumed that the production line does not stop during
the day, for a break, for example. Therefore, the system calculates the capacity of the line
and the start times of the orders in the following way:
a. It determines the operating time from the shift capacity of the line resource, minus
breaks.
b. It calculates how many products can be produced in this time, by dividing the
operating time by the takt time.
c. It divides the number of products equally over the day, without taking breaks into
account.
It only uses this takt interval for scheduling. The start and end dates of the order
activities could therefore occur in a break.
The following diagram displays this procedure:
Operating time
4 hours 4 hours
8 am 12 pm 1 pm 5 pm
Takt-based scheduling
With a takt time of 1 hour, 8 products can enter the line. However, model mix
planning calculates with 9 hours and a takt time of 1 hour and 7.5 minutes.
This results in the following start times:
11 22 33 44 55 66 77 88
8:00:00
8:00:00 9:07:30
9:07:30 10:15:00
10:15:00 11:22:30
11:22:30 12:30:00
12:30:00 13:37:30
13:37:30 14:45:00
14:45:00 15:52:30
15:52:30
8 am 12 pm 1 pm 5pm

Production Planning Using the Rapid Planning Matrix

(RPM)
Purpose
This component contains the functions for planning component requirements for the final
assembly of products with many variants and large numbers of orders.
It is an enhancement of the Production Planning and Detailed Scheduling component in the
APO. It uses a new technique for BOM explosion in the liveCache [External] for the APO to
process large amounts of data much faster than was possible in planning up to now.
You use this component when you must plan production in the APO for configurable products
with many variants and large numbers of sales orders. This form of planning is
recommended for make-to-order repetitive manufacturing, which arises in the automotive and
high-tech industries, for example.
Production planning using the rapid planning matrix [Page 164] is fast for the following
reasons:
• Planning is based on integrated Product and Process Engineering (iPPE) [External].
• A planning matrix for the RPM product [Page 166] is generated in the liveCache for the
APO. The liveCache contains the data relevant to planning so time-consuming database
accesses are no longer necessary.
• The valid BOM item is determined simultaneously for all orders.
Implementation considerations
You can use the rapid planning matrix only in connection with integrated Product and Process
Engineering (iPPE). You maintain integrated Product and Process Engineering in a Discrete
Industries System (4.6B).
Integration
Integration with planning components in the APO and the DI System
Function required Component necessary Further information

Generate planned orders for the Model Mix Planning [Page 126] The APO uses model mix planning
RPM product and define order (APO) to generate planned orders for the
sequence sales orders, to determine the
sequence of the planned orders on
Generate rapid planning matrix
the production line, and the start
and end dates for the planned
orders. The component
requirements are scheduled in the
rapid planning matrix based on the
order start dates.
Then the matrix for a product is
generated.
Update rapid planning matrix Production Planning and Detailed You can start the planning run to
Scheduling [External] (APO) update the matrix either directly
from the menu for the rapid
planning matrix, from the product
view, or from the product planning
board or you can run planning in
the background.
Continue planning on lower low- Production Planning and Detailed The components that are to be

level codes Scheduling (APO) planned in the APO are planned

using Production Planning and
Detailed Scheduling.
Continue planning on lower low- Material Requirements Planning The planning file entries for
level codes (DI System) components that are to be planned
in the DI System are transferred to
the DI System where they are
planned in the next planning run.
Evaluate planning results in the Evaluations for Production You can use a separate evaluation
APO Planning and Detailed Scheduling to display the rapid planning matrix
(APO) that the APO generated for a
product.
You can also evaluate the
planning results in the product
view and in the product planning
board.
Evaluate planning results in the DI Evaluations for requirements You can evaluate the planning
System planning results for the components in the
MRP list or the stock/requirements
list.
Integration with master data components in the APO and the Automotive System
Function required Component necessary Further information
Maintain master data in the R/3 Material master Define planning data
System
Maintain production version
Classification system You define the classes for the
RPM products and the
characteristics for the classes. You
must use single-value
characteristics only.
Variant configuration You define object dependencies.
Only simple selection conditions
are possible. You can maintain
object dependencies directly in the
iPPE [External] product structure.
You also create a configuration
profile.
integrated Product and Process • You enter the BOM data in a
Engineering(iPPE) [External], product variant structure.
consisting of:
• You use line design to
• Product structure [External] represent the structure of your
production lines and you
• Line design [External]
define the data for scheduling.
• Process structure [External]
• You use the process structure
component to create routing
data and assign the
components to the individual
activities.
Engineering Change Management You can use engineering change

management [External] to manage

different change statuses for the
product variant structure and start-
up parameters. Planning then
takes the change statuses into
consideration. The time-based
validities are taken into
consideration at explosion as well
as the parameters location,
product class, and start-up
parameters.
Resource You create a line resource
[External] for the production line
that you want to plan. Takt-based
scheduling is based on the line
resource and the data from line
design.
Transfer master data to the APO APO Core Interface [External] The R/3 System provides the APO
with master and movement data.
You use the integration model for
the integration model [External] for
the APO Core Interface to control
the data transfer [External].
All transferred master data is
automatically assigned to model
000 (model for active planning).
Change master data in the APO Product master
Features
You can use the rapid planning matrix to plan the requirement quantities and dates for
components of a product very quickly. The planning is single-level. The subordinate BOM
levels are planned either in the DI System using requirements planning or in the APO using
The rapid planning matrix offers the following functions:
• Single-level explosion of the iPPE data consisting of the product variant structure, line
design, and the process structure
• Determination of the components required and the characteristic values
• Scheduling
Takt-based scheduling [Page 184] is used to schedule.
The rapid planning matrix uses the order start date and the master data that you have
maintained in integrated Product and Process Engineering to determine the exact
requirement dates for the components.
The rapid planning matrix automatically changes the requirement dates of the
components to match any changes to the start date that are caused by sequence
changes in model mix planning.
• Grouping of the component requirements for each period
The requirements for components that are not assigned to the sales order can be
grouped for each period. Planning then generates only one procurement element for
the grouped requirements. You can use a time bucket profile to define the periods.
• Continuation of planning for the components in the DI System

You can continue planning for less important components in the DI System. The
planning files entries for these components are transferred to the DI System and
planned using requirements planning. This enables you to take the load off the APO
without losing the advantages of the quick explosion in the matrix.
• Evaluations
The Matrix display [Page 197] evaluation (transaction MDMD) displays the rapid
planning matrix and has numerous search functions.
You can also use the evaluations for Production Planning and Detailed Scheduling,
the product view or the product planning board, for example, to check and edit the
planning results.
The requirements for components that are transferred to the DI System and planned
using requirements planning are displayed in the MRP list and the stock/requirements
list as APO requirements.
Constraints
• A rapid planning matrix can process a maximum of:
− 64,000 orders for each valid production version
− 16,000 component nodes in a product variant structure
− 64,000 component variants (but automatic division into sub-matrices is possible so
that you can create any number of component variants)
− 4,096 color nodes
• You cannot use the product process model (PPM) in the APO together with the rapid
planning matrix.
• The CDP (Characteristic Dependent Planning) characteristics in the APO cannot be used.
You must create the characteristics in the DI System and use the CIF interface to transfer
them to the APO.
• Phase-out control (discontinuation when stock has been used up) is not possible.
• You cannot firm components in a planned order.
Rapid Planning Matrix (RPM)

Definition
The rapid planning matrix is a product-related database object that is stored in the liveCache
for the APO system. The rows of the rapid planning matrix contain all the components of a
product that the system determines from the component variants of the product variant
structure [External] (PVS) for the product. The columns contain the lined-up APO planned
orders for the product. The use of a component in an APO order is indicated by an X in the
appropriate row of the rapid planning matrix.
The structure of the rapid planning matrix is made clear in the following graphic:

Access node 2 Orders

1 for final
assembly
Order data
Order Order Order Order Order Order

Components
01 02 03 04 05 06
Prd Prd Prd Prd
A B C D
Green bumper x x - x - x
White bumper - - - - x -
Red bumper - - x - - -
Navigation system GPS - - x x x x
2.5l engine - x - - x -
Windshield wiper arm x x x x x x
PVS explosion
3 - Interpretation of effectivity
- Interpretation of object dependencies
Use
The rapid planning matrix is the basis of the new form of production planning in the APO. The
matrix is used for products with many variants and large numbers of orders to quickly
determine the requirement quantities and dates for the components of a product.
Structure
The rapid planning matrix consists of two matrices:
• Characteristic value matrix
The characteristic value matrix represents a method of storing the object
dependencies for the individual orders in the liveCache. The rows of this matrix
contain the maximum possible characteristics. The configurations from the orders are
in the columns.
• Component variant matrix
All the components for the product (corresponds to the super BOM) and the order
data are in the component variant matrix.
The rapid planning matrix is formed by the data from both matrices. The
components/characteristic values for each order are indicated by an X.
Integration
You can use the data provided by the rapid planning matrix in any system and any
transaction. The rapid planning matrix automatically translates changes to master data, such
as the product variant structure, the line resource, and so on, and changes to the order
sequence.
The rapid planning matrix is filled with the following data:
• Data from integrated Product and Process Engineering (product variant structure
[External], line design [External], process structure [External])
• Data for the line resource [External], such as takt time, shift sequence
• Data from the APO planned orders for the product, such as the start and end date for the
order
• Which components are needed for which order (= setting the crosses) is determined by
exploding the product variant structure whilst taking object dependencies [External] and

the validity data maintained in engineering change management [External] into

consideration.
The following functions use data from the rapid planning matrix:
• Determination of the component requirements for each order and each defined period for
further planning in the APO and MRP in the R/3 System
• Generation of order BOMs for backflush at reporting points
• Transfer of the characteristic value matrices as the basis for sequencing in Sequencing
• Forecast delivery schedule/JIT delivery schedule/sequence JIT call
RPM Product
Definition
Configurable product that is produced in-house and is planned in the APO using the rapid
planning matrix.
You define this type of planning for a product by setting the indicator for matrix explosion in
the Task list explosion field in the APO product master.
Integration of the Rapid Planning Matrix in the

Planning Process
Purpose
This process describes how to proceed when planning products with many variants and large
numbers of orders. This is necessary, for example, in the automotive industry. The production
is make-to-order; the planned orders for the product ordered by the customer and for
important components are assigned to the pegged customer order.
You can use this planning process for final products and for important assemblies, such as
engines, for example.
You can use this form of repetitive manufacturing only when you use integrated Product and
Process Engineering (iPPE) to manage master data (BOMs, routings, production lines). In
this case, you can use APO only together with a DI System (from Release 2.0).
Prerequisites
• You have set up an interface between the DI System and the APO. See also:
Transferring iPPE Data to the APO [Page 172].
Process flow
The following graphic shows the planning process for repetitive manufacturing for
configurable products with a DI System and the APO:

mySAP.com
Maintain iPPE data in the Automotive for DI System
System and transfer to the APO
APO
Maintain master data in the APO
Maintain PP/DS
settings
Transfer stocks,
sales orders to
the APO
Run model mix

planning; the
rapid planning
matrix for the
RPM product is
created
automatically
Transfer planning
file entries for
components (B and
C parts)
Run planning for

Run requirements APO components
planning for the
components
transferred
Evaluate and edit Evaluate and edit

the planning results the planning results
(product planning
board, product view,
for example)
Transfer orders Use Production of the

for the Purchasing final product/
components Workbench to enter backflush
procure data
certain
components
Production/procurement Update of backflush

of components data in the Automotive
(conversion, backflush, System
and so on)
1. You maintain the master data in the DI System [Page 169] and transfer the master data
to the APO.
You check and add to the transferred master data in the APO.
2. You maintain the PP/DS settings [Page 111], such as the factory calendar, propagation
area, and so on, in the APO.

3. You transfer the necessary movement data, such as sales orders, stocks, receipt
elements, and so on, to create a uniform planning situation in both systems.
4. You run model mix planning for the RPM product [Page 166] in the APO. Model mix
planning generates an APO planned order with quantity 1 for each sales order,
depending on the settings. Model mix planning assigns the planned order to the line
resource on which the final assembly is to be executed and defines the order sequence
with the start and end dates of the planned orders. This APO planned order does not
have a component list.
The last step of the planning run is to explode the product variant structure and to
create a rapid planning matrix. The rapid planning matrix determines the
requirement quantities and dates for the components required for each order. See
also: Planning [Page 191].
5. You can update the rapid planning matrix at any point in time when changes are made.
You start the planning run for the rapid planning matrix from the product view or directly in
the menu for the rapid planning matrix. See also: Update Matrices [Page 193].
6. You are recommended to use the Automotive System rather than in the APO to plan less
important components (B and C parts) so as not to overload the APO. The procedure is
as follows:
a. The planning file entries for these components are transferred automatically to the
DI System.
b. You plan requirements for these components in the DI System. Requirements
planning uses the dependent requirements for the components from the rapid
planning matrix in the APO.
c. You use the MRP list and the stock/requirements list to evaluate the results of
requirements planning.
d. You produce/procure the components in the DI System; you convert the planned
orders or purchase requisitions that are generated to cover the dependent
requirements in the matrix, backflush, if necessary, post the goods receipt and goods
issue, and so on.
7. We recommend that you use the APO to plan important components that are
produced in-house or that are procured externally (A parts), such as the engine or the
wiring harness in the automotive industry.
a. You run planning in APO for these components; the planning run generates APO
planned orders to cover the dependent requirements determined by the rapid
planning matrix. The planning run executes a single explosion of the iPPE data for
components produced in-house to determine the dependent requirements for the
subordinate components.
b. You evaluate the planning results for the final product and for the components that
you have planned in the APO and, if necessary, process the procurement elements
generated by the APO. You use the product planning board or the product view, for
example, to do this.
c. You can transfer the APO planned orders for the components to the DI System where
you can produce/procure (conversion, backflush, and so on).
or
d. You can use the component Collaborative Procurement in APO to process and
convert the APO planned orders and the APO purchase requisitions for the
components that are procured externally. This component supports you in
determining the source, in using scheduling agreements, and so on.
e. You plan and control the production of the final product (final assembly) in the APO,
by using the product planning board and sequencing, for example. You also enter
the production backflush in the APO. The backflush data is transferred to the DI
System. The goods receipt for the RPM product and the goods issue for the

components are automatically posted at the same time in the Automotive System
(backflush). The updated stock values for the components are transferred from the DI
System to the APO. The dependent requirements in the rapid planning matrix are
updated simultaneously; the component requirements are reduced. See also:
Backflush in APO [Page 445].
Maintaining and Transferring Master Data

Process flow
1. You create master data in the Automotive System. See also: Master Data Maintenance in
the DI System [Page 169].
2. You use the APO Core Interface to transfer the iPPE data. See also: Transferring iPPE
Data to the APO [Page 172].
All independent data, such as material masters, resources, and so on, are transferred
with the iPPE structures when you transfer the iPPE data. You must transfer the
plants, storage locations, customer and vendor masters, and so on, before you
transfer the iPPE data and use the APO for the first time. See also: Initial Data
Provision [External] in the documentation for the APO Core Interface.
3. You check the transferred data in the APO, change the APO product masters, and create
the settings relevant for planning. See also: Master Data Maintenance [Page 177].
Master Data Maintenance in the DI System

Purpose
This process describes the master data that you must maintain in the DI System, so that you
can execute production planning using the rapid planning matrix in the APO.
Prerequisites
Customizing for MRP
• You have defined an MRP type for the products that are to be planned only in the APO.
To do this, you proceed as follows:
In Customizing for MRP, choose Master Data → Check MRP Types. In the nest
screen, choose New entries and define a new MRP type. In the MRP procedure field,
enter the indicator X (Without MRP, with BOM explosion) in order to exclude MRP.
• You have created an MRP type for the components that are to be planned further using
the matrix in the DI system after the determination of requirements.
To do this, you proceed as follows:
Define a new MRP type and in the MRP procedure field, enter the indicator D for
Material requirements planning and in the Planning method field, enter the indicator 2
for Import dependent requirements from external system.
Customizing for Sales

In order to ensure that customer requirements are also generated for the products that are to
be planned in the APO, you must change the following settings in Customizing for Sales:
In Customizing for Sales, choose Sales → Sales Documents → Schedule Lines → Assign
Schedule Line Categories. Make a new entry for the item category with which you work in the

sales order. Assign the MRP type, which you have created for the products that are to be
planned only in the APO, and the schedule line category CP (MRP) to this item category.
Process flow
1. Maintain characteristics and variant classes.
You create the characteristics for the RPM product [Page 166] in the classification
system.
You define a class for the RPM product [Page 166] with the class type 300 (for
variants) and assign the previously defined characteristics to it.
You can find further information about characteristics and classes in the SAP Library
under Cross-Application Components → Classification (CA-CL) → Classification
System (CA-CL).
2. Maintain variant configuration.
In order for the RPM product to be configurable, you must maintain dependencies
and a configuration profile for the RPM product. If necessary, assign the dependency
to the previously created characteristics. In the product variant structure, you maintain
the dependency for the selection of the item variant.
You can find further information in the SAP Library under Logistics → Logistics –
General (LO) → Variant Configuration (LO-VC).
3. Create material master for RPM product.
You create the RPM product as a configurable material, that means that you set the
indicator Material is configurable (Basic Data 2 view).
In the classification screen, you assign the class that you have created for the RPM
product.
4. Determine which components for the RPM product and components on subordinate BOM
levels are also to be planned in the APO.
In the case of multi-level BOM structures, note that if components on subordinate
BOM levels are to be planned in the APO, the superior assembly must also be
planned in the APO.
Incorrect Correct
Legend:
Planned in the APO
Planned in the Automotive System
5. Maintain MRP data in the material master.

In the case of an RPM product and important components that are to planned only
in the APO, you enter the MRP type that excludes the material from MRP.
In the case of the components that are to be planned further using the matrix in the
DI system, you enter the MRP type that has been created for them.
In the case of an RPM product that is to be planned using the rapid planning matrix,
you enter the strategy group 25 Make-to-order for configurable material.

In the case of components, for which the APO is to group requirements from a
particular period, enter the indicator 2 (Collective requirements only) in the
Individual/collective field.
You can improve performance during planning by setting the collective

requirements indicator for as many components as possible.
In the case of components, whereby the requirements are to be assigned to the
pegged sales order, enter the indicator 1 (Individual requirements only) in the
Individual/collective field.
6. Maintained integrated Product and Process Engineering.
• You create a multi-level product variant structure for all low-level codes. See also:
Create a Multi-Level Product Structure [External].
If one or more components, which you install in the final assembly, must be
assembled directly before being installed and this assembly and the installation
are to be included in one step, then you must create an access node or structure
node and assign all nodes, for which the variants have the materials that are
assembled before installation assigned to them.
The headlamps are installed during the final assembly. The headlamps are not
assembled before delivery and must therefore be assembled before the
installation. In this case, you do not assign the node for the finished headlamp to
the node that you have created for planning. You have to assign the nodes that
you created for the individual parts of the headlamp instead. See also: Create
Nodes with Single-Level Structure for the Rapid Planning Matrix [External]
• You create a process structure for the assembly and assign the components to
the individual activities. See also: Creating a Single-Level Process Structure for a
Material [External].
• In Line Design, you create an iPPE node of line or line network type for the
production line. See also: Process Line Structure [External].
• In Line Design, you execute line balancing. See also: Process Line Balance
[External].
7. Maintain iPPE access object in the production version [External].
You create a production version for the RPM product that you want to plan using the
matrix and maintain the iPPE access object. In the iPPE access object, you enter the
access node/variant for the product variant structure or you enter a node with a
single-level structure for the rapid planning matrix if you have created one. You also
enter the routing header node for the process structure and the node that you have
created for the production line. See also: Create/Change iPPE Access Object [Page
172].
For every component produced in-house, for which the MRP run or the production
planning in the APO is to execute an individual explosion of the iPPE data, you create
a production version and maintain the iPPE access object.
8. On the tab page Access, you enter the material number, the plant and the production
version in the access node that you want to use for the planning.
If you want to plan a component produced in-house in the APO, you must then also
enter the material number, plant and production version that you have maintained for
the iPPE access object, on the tab page Access.

Create/Change iPPE Access Object

Prerequisites
• You have created the product structure for the product.
• You have created a process structure for the product.
• You have created a line structure for the production line on which the product is
produced.
• You have created an access at the node so that you can refer to the access in the access
object.
Procedure
1. In the menu for the iPPE Workbench, choose Environment → Create or Change iPPE
Access Object.
The Create or Change iPPE Access Object screen appears.
2. In the Product field, enter the product that you have maintained at the access variant.
Enter the location and in the Description field, enter the description that have maintained
at the access of the access node. Choose .
The system checks whether an access object for the product already exists. When an
access object exists, it is displayed. The rows are ready for input when no production
version exists.
3. If you have not maintained an access object for the product, enter the following data:
Product structure
Enter the node for the product structure (access node) with the class, the class type,
the variant and the alternative.
Process structure
Enter the routing header for the process structure.
Line structure
Enter the node that you have created for the line for the product to be produced.
Enter the node for the line network when you work with line networks.
4. Maintain the data for the validity area and choose .
5. Choose to save the access object.
Transferring iPPE Data to the APO

Purpose
The process describes how to use the APO Core interface to transfer the iPPE data (product
variant structure [External], process structure [External], line structure [External]) to the APO.
You use this process only when you want to use the Rapid Planning Matrix to plan certain
products in the APO, for example, and manage the master data for these products in the
Automotive System.

Prerequisites
• You have entered the iPPE access object [External] for each product that you want to
plan in the APO.
• You have made the required settings in the Automotive System and in the APO to set up
the interface between both systems. The steps required for this can be found in the
document Checklist for Setting Up the System Infrastructure [External]. For more
information, see Integration of APO and R/3 [External].
• You have ensured that the Customizing settings defined in the Automotive System for
Administration for iPPE Objects match the settings in Customizing for the APO; you must
maintain the same Customizing settings for the iPPE Objects in the APO as in the
Automotive System.
The settings in Administration for iPPE Interface do not have to be identical.

However, note that the iPPE user interface in the APO looks different when you
have different Customizing settings for the user interface in the APO to those in
the Automotive System.
Process Flow
1. You must create at least one integration model for all products for which you have
created a production version with an iPPE access objects. This is to provide the APO with
iPPE data for the first time. All iPPE structures to be transferred and the dependent data
for the selected products are grouped in this integration model. When you create the
integration model, you enter the product numbers, locations, and production versions, if
applicable, whose iPPE structures are to be transferred. You can create several
integration models.
The system uses the product numbers to determine all the production versions with
iPPE access objects. Dependent objects (master data, such as product masters for
components, classes, resources) are included in the integration model. See also:
Create an Integration Model for iPPE Data [Page 174].
A production version with an iPPE access object can be included in only one
active integration model so that the transfer works. You must deactivate the other
integration model when the production version that you want to transfer is
included in a different integration model.
2. You activate the integration model [Page 175] to start the data transfer.
3. You must transfer changes [Page 175] when you change iPPE data that you have
already transferred to the APO. There is a report for this that should be executed in the
background.
When new master data, such as a new component in the PVS or a new resource
in the process structure, is added to iPPE data that has been transferred, you
must transfer the master data to the APO; you must create and activate a new
integration model for this master data.
4. Once the transfer has started, you can check in the Automotive System which objects
were transferred to the interface and whether there were any errors. You can check in the
APO System which objects were transferred to the APO and whether there were any
errors. See also: Check Transfer Results [Page 176].

Result
Copies of the transferred iPPE data (product variant structure, process structure, and line
structure) for the products defined in the integration model are in the APO. You can use the
same iPPE transaction as in the Automotive System to check the data in the APO.
Create an Integration Model for iPPE Data

Use
The system uses the integration model for certain products to determine the iPPE data to be
transferred.
Prerequisites
You have entered the iPPE access object [External] for each product that you want to plan in
the APO.
Procedure
1. Choose Logistics → Central Functions → Supply Chain Planning Interface → Core
Interface Advanced Planner and Optimizer → Integration model → Generate → Activate
in the SAP Easy Access Menu to create an integration model.
The Create Integration Model screen appears.
2. Enter the following data in the upper area of the screen:
Enter a name in the Model name field to distinguish between the different integration
models.
Enter the RFC destination defined for APO in the Target system field.
Enter a description in the Application field. This is only for your information.
3. Select the iPPE field in the selection area.
4. Scroll down and enter the product numbers, the plants/locations and, if applicable, the
production versions for the products whose iPPE data you want to transfer.
The system searches for all the products’ production versions with iPPE access
objects when you enter just product numbers. The system uses the iPPE access
objects to put together all product, process, and line structures as well as dependent
master data, such as product numbers of the components, resources, and so on.
5. Choose Execute.
The Dependent objects found dialog box appears.
6. Choose Yes.
Another dialog box appears in which you must decide whether the dependent
products, classes, and resources are to be included. (The dependent resources are
the resources assigned in the line and process structure.)
7. Choose Yes.
The system displays the number of resources included in the integration model in a
dialog box.
8. Choose Continue.
A list with the selected objects, such as product, iPPE access object, or resource, is
displayed.

9. Select an object by clicking it and choose Detail to display the concrete product number,
resource name, and so on.
10. Save the list to generate the integration model.
Result
You have generated an integration model for the iPPE data for the products defined in the
selection.
Activate an Integration Model

Use
You activate an integration model to release the data determined at creation for transfer. This
report also starts the data transfer.
Prerequisites
You have created an integration model.
Procedure
1. Choose Integration model → Activate from the Core Interface Advanced Planner and
Optimizer node.
The Activate or Deactivate Integration Model screen appears.
2. Enter the name of the model, which you defined when you created the integration model,
in the Model field and choose Execute.
The selected integration model is displayed.
3. Click the model name and choose the Active/Inactive function key to activate the
integration model.
is displayed next to the date of the integration model.
4. Choose the Start function key to start the data transfer.
Transfer Changes in the Master Data to the APO

Use
You must transfer changes that you make in the Automotive System to the APO when you
have used an active integration model to transfer the iPPE data to the APO. You use the
Evaluate and Send Change Recordings report to transfer the changed iPPE data. You
should run this report in the background as all production versions must be exploded.
The iPPE change transfer is independent of the change transfer for other master data
transferred to the APO. This is why you do not need to restrict the logical systems in the
selection screen, as the restriction has no effect. Every changed object in every active
integration model is transferred immediately to every system affected when you transfer
changes to iPPE data.

Prerequisites
• You have executed the following steps in Customizing for Supply Chain Planning
Interfaces (SCPI), which is under Logistics – General:
− You have checked that the Change pointers activated – generally indicator is set in
the IMG activity Activate Change Pointers Generally (transaction BD61).
− You have activated the following message types in the IMG activity Activate
Change Pointers for Message Types (transaction BD50):
− CIF_PPE_ACT (process structure)
− CIF_PPE_BAL (line balancing)
− CIF_PPE_CMP (product variant structure)
− CIF_PPE_FLO (line structure)
• You have created and transferred the iPPE data, including all dependent objects such as
product/material numbers for components, classes, change numbers and resources, for
example, to the APO in an integration model. You must create and transfer a new
resource, which you assign when you change a process structure, for example, in a new
integration model before you can transfer the changes for the process structure in
question.
Procedure
1. Choose Change transfer → Master Data from the Core Interface Advanced Planner and
Optimizer node.
The system displays the Evaluate and Send Change Recordings screen.
2. Enter the RFC destination defined for APO in the Logical system field. Select the iPPE
field.
3. Choose Execute.
Check the Transfer Results

Use
You can check the result of transfers using evaluations in the Automotive System and the
APO.
Procedure
1. Choose the menu path Logistics → Central Functions → Supply Chain Planning Interface
→ Core Interface Advanced Planner and Optimizer → Monitoring → Application Log
→=Display entries in the SAP Easy Access Menu to check iPPE objects that were
transferred from the source system to the CIF interface.
The system displays the Evaluate application log screen.
2. Enter PVS in the Object field and choose Execute.
A list with transfer dates and users appears.
3. Double-click the row for which you want to display the objects flagged for transfer.
A list with the objects transferred to the CIF interface is displayed as well as any error
messages.
Check the object in the APO:
1. Choose transaction /SAPAPO/C3 in the APO to check the objects transferred to the APO.

The system displays the Evaluate application log screen.

2. Enter CIF in the Object field and iPPE in the Sub-object field and choose Execute.
The system displays a list of transfer logs.
3. Double-click a log.
The system displays a list of messages. Information messages are indicated by a
green point, warning messages by a yellow triangle, and error messages by a red
point.
Master Data Maintenance in the APO

Purpose
This process describes the master data that you have to change in the APO after the data is
transferred.
Prerequisites
• You have transferred the iPPE data from the Automotive System.
• In the APO Customizing for Production Planning, you have maintained one or more time
buckets in the IMG activity Maintain Time Buckets Profile for Grouping of Component
Requirements.
Process flow
1. In Customizing for Production Planning and Detailed Scheduling (PP/DS) or in the menu
for the rapid planning matrix, you have made the global settings [Page 177] for the rapid
planning matrix.
2. You make changes to the product masters [Page 178] for the transferred materials.
3. You maintain additional control data for each RPM product. You can use this control data
to influence the planning run performance. See also: Control Parameters for RPM
Products [Page 179]
4. You check the master data for the RPM products using the report RPM material check
[Page 180].
5. In the Supply Chain Engineer, if necessary, you maintain transportation lanes between
the locations in order to model the transportation and delivery of products.
Defining the Global Settings

Use
You use the global settings to define the parameters for planning with the rapid planning
matrix in Customizing for the Rapid Planning Matrix.
Features
Activate rapid planning matrix
The RPM active indicator is set as standard. This indicator must be set in order to use the
rapid planning matrix for planning.

Define parallel processing

You can define whether the planning run is to be processed in parallel and whether additional
sub-matrices are to be generated. See also: Parallel Processing [Page 195].
Define behavior when colored product masters are missing

The component nodes and color nodes are exploded when the matrix is generated; all colors
assigned to a color node are listed for each colored component. The system checks whether
there is a matching product master for each combination of component and color (door red,
door blue, and so on). You can define when the error message "No product master created
for colored product" is displayed in the Color behavior field. The error message is displayed
in the status line during the planning run as necessary.
You can make the following settings:
• The error message is always displayed when the product master for the colored product
is missing, even when no requirements are determined for the product.
• The error message is displayed when a requirement is determined in the matrix for the
component, door blue for example, and there is no product master for this component.
• The error message is never displayed; the missing product master is ignored.
Define the explosion date for the component BOMs

You can define how the system determines the explosion date for the component BOMs,
which are determined by the rapid planning matrix, in the BOM explosion date field. See also:
Determining the BOM Explosion Date [Page 187].
Determining the Valid Line Balance

You define how the system determines the valid line balance, which is required for takt-based
scheduling, in the Line bal. date field. See also: Determining the Valid Line Balance [Page
184].
Activities
From Customizing for Production Planning and Detailed Scheduling (PP/DS), choose Rapid
Planning Matrix → Maintain Global Settings (Valid for all Clients).
Change Product Master

Use
After the transfer from the DI System, you must make changes to the product masters for the
RPM products and, if necessary, to the product masters for the components.
Procedure
1. The following fields have been transferred from the DI System or are now set in the APO
as follows:
Material master (DI System) Product master (APO)
MRP type, that excludes MRP in the R/3 --
system
MRP type that is set with the planning Tab page Procurement: the indicator P
method 2 (import dependent requirements (procurement planning: external) is set in the
from external system) procurement type field
Individual/coll. indicator 1 (individual Tab page Demand: Possible
requirements only) indiv.cust.reqmts is selected

Individual/coll. indicator 2 (collective Tab page Demand: Always collective

requirements only) reqmnts is selected
Lot size Tab page Lot size: lot size is transferred from
R/3 system, for example, in the case of lot-
for-lot order quantity Lot-for-lot is selected
---- Tab page PP/DS: Manual planning without
availability check
2. In the field Explode task list on the tab page PP/DS of the product master for the RPM
product, enter the indicator 4 for matrix explosion of iPPE.
3. In the product master record for the components that are to be planned further in the
APO, you maintain the following fields:
• Select Automatic planning in planning run.
• In the Explode task list field, select 3 for single explosion of iPPE.
• If the Always collective reqmnts indicator is set, you should enter a time
bucket for the grouping of the component requirements. If you do not enter a
time bucket, the system then uses the time bucket
SAP_PROFILE_DEFAULT during the planning. The APO creates this during
the first planning run.
4. In the case of components that are to be planned further in the DI System and for which
you have set the Always collective reqmnts indicator, you should also enter a time bucket
for the grouping of the component requirements.
The DI System can only group the dependent requirements on a daily basis. For
example, if the APO has grouped the dependent requirements on a shift basis,
the Automotive system then uses the dependent requirements for the shifts to
calculate the total dependent requirements per day.
Control Parameters for RPM Products

Use
You can use this function to enter additional control parameters for the planning of each
material, thus improving the system performance.
Prerequisites
You have entered indicator 4 for Matrix explosion of iPPE in the Explode task list field in the
product master for the final product that you want to plan using the rapid planning matrix.
Features
The products that are flagged for planning with the rapid planning matrix are listed
automatically with the location in the overview screen for maintaining additional data. You can
enter the following additional control parameters for each product:
Creation of sub-matrices
You can define into how many sub-matrices a rapid planning matrix is to be divided in the
Sub-Mats field. The matrix is divided up horizontally. The planning run generates the number
of sub-matrices that you have defined instead of one large matrix.

You divide into sub-matrices when a product consists of a large number of components which
means that the entire rapid planning matrix consists of a large number of rows. Approximately
64,000 rows are technically possible. You can accelerate the planning run by dividing a large
matrix into several small sub-matrices and processing planning in parallel. See also: Parallel
Processing [Page 195].
You must define Create submatrices even without parallel processing in the Parallel
processing field in the global settings [Page 177] so that the planning run always generates
sub-matrices.
Checks for selecting multiple and required components

You can define that the planning run checks whether the multiple selection and required
component selection conditions at the component variants could be adhered to at explosion
for iPPE in the Multiple selection and Required component fields. Explosion errors are
displayed in the matrix display and the order evaluations when these selection conditions
could not be adhered to.
Display planning progress

You can define that information about the progress of planning is displayed in the status row
during the planning run in the Progress field.
Use of a buffer for selection conditions

You can use the Buffer field to define that the selection conditions are written to an internal
buffer. This is recommended when several historical statuses for a component variant use
the same object dependencies within the PVS or when you have defined the same selection
conditions for a component variant in object dependencies. Using the buffer improves the
system performance for the planning run in this case.
Using the database view to set up the super BOM

You can use the View field to define that the super BOM is set up by using database views,
which is a fast process. However, this procedure can lead to errors when the iPPE data is
inconsistent.
The super BOM is set up by individually accessing the tables involved when you do not set
the indicator.
Activities
In order to maintain this control data, start from the Production Planning menu and choose
Automatic Production Planning and Optimization → Rapid Planning Matrix → Settings →
Maintain Additional Data for RPM Materials.
Execute Checks for RPM Products

Use
Before you start the first planning run for the products that you want to plan using the rapid
planning matrix, you should check that all master data and necessary settings have been
entered. A report is available for this check.
Procedure
1. Starting from the Production Planning menu, choose Automatic Production Planning and
Optimization → Rapid Planning Matrix → Tools → RPM Material Check.
TheVarious checks for RPM products screen then appears.
3. Choose .

Result
The system creates a list of all products that are to be planned using the matrix. (These are
all products, for which you have set the indicator 4 in the Explode task list field in the product
master.)
The following errors may be listed:
• Product not assigned to a model
• No production version
• iPPE access object not maintained in the production version
• Access node/access variant, node for line, routing header node of process structure not
entered in the iPPE access object
• Product not in the list for the transaction MDRPM (Change Additional Data for RPM
Products)
Planning Process with the Rapid Planning Matrix

Purpose
This process describes planning for configurable products with large numbers of orders that
are produced using make-to-order repetitive manufacturing.
Prerequisites
• You have transferred the required movement data, such as stocks, planned orders,
production orders, purchase requisitions, and manual reservations, to the APO. See
OLTP-PP/DS Scenario [Page 18] for more information.
• You have created the required master data in the DI System and transferred the data to
the APO, where you have made any necessary changes. See also: Master Data
Maintenance and Transfer [Page 169].
• You have entered the sales orders in the DI System and transferred them to the APO.
You must create and activate an integration model with sales orders only once. New and
changed sales orders are transferred automatically.
• You have made the basic settings for planning with the rapid planning matrix in the
activity Maintain Global Settings [Page 177] in Customizing for Production Planning and
Detailed Scheduling (PP/DS) under Rapid Planning Matrix (RPM).
• You have created one or more time bucket profiles in the activity Maintain Time Buckets
Profile for Grouping of Component Requirements in Customizing for Production Planning
and Detailed Scheduling (PP/DS) and assigned the time bucket profiles to the
components in the product masters.
• You have defined the algorithms and planning horizons which model mix planning is to
use for calculations in the short-, middle-, and long-term in the activity Define Procedure
Packages under Model Mix Planning in Customizing for Production Planning and Detailed
Scheduling (PP/DS). You must define that model mix planning in the short- and medium-
term planning horizon generates planned orders with quantity 1.
Process flow
1. The planning run for model mix planning [Page 150] generates APO planned orders for
the transferred sales orders, assigns the APO planned orders to the line that you
predefined, determines the sequence of the orders, and schedules takts. Model mix
planning results in APO planned orders that are assigned to sales orders and the start

and end date (date and time) but do not include components. The APO orders are
assigned to the pegged sales orders. See also: Planning [Page 191].
2. The planning run for model mix planning then generates the rapid planning matrix for the
product to be planned.
The system simultaneously explodes the product variant structure for all APO orders
for the product and uses this data to generate the rapid planning matrix. The standard
explosion date for the PVS is the start date of the first activity (= date on which the
product enters the first line segment of the line resource). The following steps are
executed:
Creation of a characteristic value matrix
The characteristics are displayed in the rows (characteristic values for the class
of the configuration material). Configurations of the product are displayed in the
columns. The configurations are determined by the system from the APO orders.
Generation of the component variant matrix
The component variant matrix is used to determine component requirements. The
system determines all the components possible for a product (super BOM) and
the quantities and writes them in the matrix rows. The system writes the APO
planned orders for the product in the columns. The system uses the object
dependencies and time-based validity to determine the components that are
necessary for the order and puts an X at the corresponding component.
3. The rapid planning matrix determines the requirement dates for the components [Page
183] in the form of takt-based scheduling [Page 184]. The schedule is dynamic and starts
at the start date for the APO order for the final product using the master data that you
defined in the line resource and in the process structure in Line Design. The system
determines the valid line balance that you created in Line Design. See also:
Determination of the Valid Line Balance [Page 184].
The matrix automatically adapts the requirement dates for the components when the
start date of the APO order for the final product is changed.
The requirement dates for the components are not automatically adapted when
the APO planned order is assigned to a different production line; the final product
is to be produced on a different production line. You must start the planning run to
set up a new matrix.
4. The system aggregates the dependent requirements for all components with
Individual/coll. indicator 2 (Collective requirements only). The system aggregates the
requirements within the defined periods, such as shifts, for example. See also: Grouping
Component Requirements [Page 186].
5. The system generates dependent requirements that are assigned to the pegged sales
order for all components with Individual/coll. indicator 1 (Individual requirements only).
6. The rapid planning matrix generates planning file entries for all components for which
requirements are determined.
7. There are two options for continuing planning based on the results of the rapid planning
matrix:
− Further planning in APO
Execute the APO planning run for the components that are defined for planning in
APO. This planning run generates planned orders to cover the requirements.
These orders are automatically adapted to any changes to the orders for the final
product when you run planning again. The components required are determined
by individually exploding the PVS when the components themselves are
assemblies that are produced in-house.
− Further planning in the DI System

The planning file entries generated by the matrix are transferred from the APO to
the DI System, using the CIF interface, when the components are defined for
further planning in the DI System. The system transfers these planning files
entries in the MRP run to the DI System, transfers the requirements for the
components from the rapid planning matrix to the APO, and generates
corresponding procurement elements. The dependent requirements from the
matrix are displayed as APO requirements in the DI System.
You must execute the MRP run in the Automotive System again when changes
are made to the APO orders for the final product, due to a sequence change in
Sequencing, for example. Only then can the procurement elements for the
components be changed accordingly.
Determining the Requirements Dates for Components

Use
You can use this function to determine the exact requirements dates for the components
irrespective of the line structure. This is particularly important in the case of complex lines with
relatively long lead times, as the requirements dates can deviate greatly from the starting
point of an order.
Integration
The system uses takt-based scheduling [Page 184] in Production Planning with the rapid
planning matrix in the APO System to determine the requirements dates. In Customizing for
the Rapid Planning Matrix, you can set the key date, for which the system determines the
valid line balance. This can be
• the current date or
• the valid line balance for the valid-from date for the production version.
You can find further information about this in the APO documentation for the Rapid Planning
Matrix.
Prerequisites
You have mapped a complete data model in integrated Product and Process Engineering and
created a valid line balance. In doing this, you have assigned the components to the activities
and the activities to the line segments. See also: Process Line Balance [External].
Features
By assigning the activities to the line segments, you also indirectly determine at what points in
the line particular components are installed. Using the line and the line balance, you also
determine the installation points for components. The system thereby has the option of
determining offsets for components relative to the order start date.
To do this, the system determines how many takts an order has to pass through in order to
reach the installation point for a particular component. It multiplies this number of takts with
the takt time and thereby calculates the difference between the order start date and
requirements date for a particular component (lead-time offset).
If the start date is changed, the rapid planning matrix automatically adjusts the requirements
dates for the components.
So that it is not necessary to generate a procurement element for each dependent
requirement, you can, if necessary, group together the component requirements.

Example
Line 1
Segment 1 Segment 2 Segment 3 Segment 4 Segment 5 Segment 6 Segment 7 Segment 8
ACT 1 ACT2 ACT3 ACT 4 ACT 5 ACT 6 ACT 7 ACT 8 ACT 9
C1 C2 C3 C4 C5 C6 C7 C8
Takt time Takt time Takt time Takt time Reqmts date
component C5:
Order start +
4*takt time
Determining the Valid Line Balance

Use
You can create several line balances with different validity periods [External] in iPPE line
design to represent different line loads, for example. The rapid planning matrix must then
select one line balance to determine the requirement dates.
Prerequisites
You have defined how the system determines the valid line balance in the Line bal. date field
in the global settings [Page 177].
Features
You can make the following settings:
• Date of the planning run
The system determines the line balance that is valid when you run planning.
• Valid-from date for the production version
You must enter the same valid-from date in the production version for the final
product to be planned as you have entered in the line balance to ensure that the
planning run can determine the correct line balance.
Takt-Based Scheduling
Use
You use this scheduling type for scheduling production lines. When using takt-based
scheduling, the system does not use the duration of the activities to calculate the lead time for
an order but multiplies the number of takts by the takt time. The takt time is the reciprocal
value of the production rate.

This scheduling type enables the scheduling of a high volume of orders because the system
does not have to determine the duration from the routing but only has to generate the
capacity requirements for the line resources.
In Flow Manufacturing and Repetitive Manufacturing, the materials are processed

in each takt on the line for the duration of the takt time defined. The execution
time that is determined from the routing may deviate from this takt time. Takt-
based scheduling for flow manufacturing using takts is therefore more precise
than lead time scheduling.
Integration
Takt-based scheduling is executed in the APO System only. The APO System uses the
following master data from iPPE line design and from the line resource:
• the operating time of the line
• the number of takts (processing stations) that a material has to pass through on the
production line. To do this, the system determines the longest (critical) path through the
line structure.
• the base rate the production rate valid on the key date, for which the reciprocal value
determines the takt times.
• the product-dependent rates that the system stores as a factor relative to the base rate.
Takt-based scheduling then multiplies this factor by the valid production rate for the
period and overrides the production rate in the scheduling.
Features
• When using takt-based scheduling, the system multiplies the number of takts in the
longest path along the line by the takt time. The takt time comes from the production rate
if you have entered a valid production rate for the current period. Otherwise, the system
uses the base rate for the line.
As the system determines the longest path along the line, any feeder production lines
that may be used are also scheduled.
• The system determines the operating time for the line using the line resource and takes
into account shift models and break times. If you have grouped several lines in a line
network, the system takes into account the different operating times for the individual
lines.
• You can use two procedures for takt-based scheduling.
− If you adjust the speed of the production line to suit the operating level, you use the
rate-dependent takt time [External].
− If you keep the production line at the same speed, you can use the rate-independent
takt time [External].
Note that the performance level that you can enter in the line resource has a
similar effect on the production rate. The system uses the production rate to
calculate a percentage factor relative to the base rate. The system then multiplies
the base rate by this factor when scheduling. The performance level has exactly
the same function. If you enter a production rate and also change the
performance level for the line, these two parameters are multiplied.
For example, if the base rate is 100 pieces per hour, the production rate is 80
pieces per hour and the performance level is 80%, the system schedules 64
pieces per hour.

Example
The following example shows how the lead time scheduling using the routing would give an
incorrect result. In comparison, takt-based scheduling, whereby you multiply the takt time with
the number of takts, gives a correct result.
Line 1
Segment 1 Segement 2 Segment 3 Segment 4 Segment 5
Takt time
ACT 1 ACT 2 ACT 3 ACT 4 ACT 5 ACT 6
Lead time Error

ACT 1 ACT 2 ACT 3 ACT 4 ACT 5 ACT 6
scheduling
Takt-based
scheduling Takt time Takt time Takt time Takt time Takt time
Grouping Component Requirements

Use
For components that are set in the material or product master so that they can be grouped,
the APO calculates the total dependent requirements per period from the results of the matrix.
The periods are freely definable. This has the advantage that it is not necessary to generate a
procurement element for each individual dependent requirement. It is only necessary to
generate one procurement element for the dependent requirements that fall within a certain
period. This helps to greatly reduce the volume of data.
Integration
The APO calculates the total dependent requirements of a component for freely definable
periods. If the components are planned further in the DI System, the periods within a day are
grouped into days during the transfer of these grouped requirements.
Production is executed on a two-shift basis. You have set shifts as the periods for
the grouping in the APO. The APO calculates a total for shift 1 and 2. During the
transfer of the requirements to the DI System (during the planning run), the
system displays the total for shift 1 and 2, because the DI System can only
calculate on a daily basis.
Prerequisites
• In Customizing for Production Planning and Detailed Scheduling, you have maintained
one or more time buckets in the IMG activity Maintain Time Buckets Profile for Grouping
of Component Requirements. If you create various time buckets, you can group the
various components according to various rules. It can therefore be useful, for example, to
set a daily grouping for components that are to be planned further in the DI System and,
in contrast, can be useful in the short term to set hourly grouping for APO components.
• In the product masters for the components, you have selected Always collective reqmts
and assigned a time bucket.

Features
In the first step, the matrix determines the exact requirements dates for the components
[Page 183] .
The system then determines the periods for the grouping of a component using the time
bucket in the product master. The time bucket is independent from the location and the
factory calendar. The system uses the assignment in the product master to determine the
necessary line resources and thereby the valid shift sequence for the resources as well as the
factory calendar. The system uses the entries for the time bucket, the shift sequence and the
factory calendar to determine the periods in which the dependent requirements are to be
grouped.
For example, you can use a time bucket to determine that the dependent requirements are to
be grouped monthly in the long-term horizon, weekly in the mid-term horizon and daily or by
shift in the short-term horizon. In addition, you can define user-specific periods within a shift.
For example, each hour should be the start of a new period, in which case the dependent
requirements are grouped on an hourly basis.
In the last step, the system generates all requirements for a component that fall within a
period and groups these together. The further planning is then executed on the basis of the
total requirement.
The requirements dates for the component A, which is required 2 days after the
planning day (= today), are 6.00 am, 6.10 am, 6.20 am, 6.30 am and so on. The
requirements quantity for each order is to be 1 piece. In the time bucket, you
have defined that the requirements are to be grouped on an hourly basis, that
means, the system determines the time period from 6.00 am to 6.59 am as period
1 for the following day. The system groups the requirements that lie within this
period and calculates a total requirement of 6 pieces.
Determining the BOM Explosion Date

Use
Once the PVS is exploded, using the time bucket profile to group the requirements for
components for which you have defined Always collective requirements reduces the volume
of data. The BOM selected when the requirements for the components (assemblies) on the
lower BOM levels are exploded must match the components for final assembly. You can use
an indicator to define which data the system is to use for exploding the component BOMs of
an RPM product.
You thus ensure that
• the correct BOM for exploding an in-house product component
• the correct historical status of a variant
• the correct requirement dates for the subordinate components
can be determined.
Integration
The system always uses the start date of the planned order for the RPM product as the
explosion date of the PVS for the RPM product.
Prerequisites
You have selected the Always collective requirements field on the Demand tab page in the
product master for the components.

You have defined how the system determines the BOM explosion date in the BOM explosion
date field in the global settings [Page 177]. You can define different settings for certain
components in the BOM explosion date field on the PP/DS tab page in the product master for
the components.
Features
Use the requirement date for the component as the BOM explosion date
The requirement date determined for the installation of the component by the rapid planning
matrix (by using takt-based scheduling) is used as the explosion date for the BOMs for
components produced in-house. This date is also used to determine which components are
valid when you use engineering change management to manage historical statuses.
Use the BOM explosion date in the order for the RPM product
The BOM explosion date in the planned order for the RPM product is used as the explosion
date for the BOM and to determine which components are valid.
Valid-from date of the component variant as BOM explosion date

The valid-from date that you have defined in the component variant is used as the explosion
date for the BOMs and to determine which components are valid.
Example
You have defined Assembly 1 to be valid from 4 January 2000 and Assembly 2 to be valid
from 07 January 2000 at the component variant for the node WHEEL in the PVS. 4 January
2000 is used as the explosion date for the BOM for Assembly 1 and to determine the
subordinate components when the matrix determines Assembly 1; the BOM that is valid on 4
January is used and the components of the wheel that are valid on 4 January are selected
when the BOM for Assembly 1 is exploded.
The results of this procedure are correct only when you use the same change numbers on the
subordinate BOM levels as for the superior assembly (Assembly 1 in this case).
BOM explosion date from order or valid-from date for the component variant
The date for the BOM explosion and determining the valid components is the date furthest in
the future. The system compares the BOM explosion date in the planned order for the final
product with the valid-from date for the component variant determined by the matrix.
Start-up parameters from the order for the RPM product cannot be taken into
consideration at explosion when you have defined Always collective requirements
for the components produced in-house.
You must define Individual customer requirements in the product master for the
components produced in-house when you want to take start-up parameters into
consideration when planning the components.
Comparing the Explosion Results

This example shows how the settings in the BOM explosion date field affect the explosion of
the components for the RPM product and the resulting requirement situation for the
subordinate components:

Access node for the planning of

car model A
Component node: assembly
Assembly 1 Ae1 1.1. - 30.6.

Assembly 2 Ae2 1.7. - unrestricted
Component node: A Component node: B
K8 Ae1 1.1. - 28.2. K4 Ae1 1.1. - 30.6.

K9 Ae9 1.3. - unrestricted K5 Ae2 1.7. - unrestricted
In the final assembly, the material assembly 1 is installed in the car model A. The change
number Ae 1 is used to control that this assembly may be used between 1 January and 30
June. Assembly 1 consists of components K4 and K8. For this reason, the change number is
also entered for the component variants for K4 and K8. The component K4 will be replaced by
component K5 from 1 July using the change number Ae2. Assembly 1 will therefore be
replaced by assembly 2 with the same change number. With change number Ae9, the
component K8 is replaced by K9 at component node A. However, this change is not passed
on to the superior assembly.
The planning matrix for the car is as follows:

Mat.no. Ch.no from to SUP Order A1 A2 A3 A4 A5
Exp. date 15.6 18.6. 1.8. 1.7. 5.7.
Req.date 15.6. 18.6. 19.6. 1.7. 5.7.
SUP VP1
Assy.1 Ae1 1.1. 30.6. u

Assy.2 Ae2 1.7. - v w x z
Note:
SUP = Start-up parameters
Explosion date = BOM explosion date for planned order (in this example, the finish date of the
planned order is used)
Requirements date = Date on which the car is required for the outbound delivery
The letters u to z have been used to replace crosses for the assembly selected so that it is
easier to differentiate between them.

Explanation for setting of crosses

For order A2, the assembly 2 (=v) has been selected because this was determined in the
start-up parameters used.
In the case of order A3, the requirements date deviates from the explosion date. However,
assembly 2 (=w) is selected because the explosion date is binding for the selection of the
assembly.
In the case of orders A1, A4 and A5, there are no special features to be taken into account
and the assembly valid on the explosion date is therefore selected.
Requirements situation and BOM explosion for assemblies

The crosses set in the matrix and the BOM explosion for the assemblies, taking into account
the various alternatives for the determination of the valid BOM, result in the following
situation:
Alternative 1 Alternative 2 Alternative 3 Alternative 4
Expl. = Order Expl=ComVar Expl = Mix Expl=ReqDat
Requirements Req.date for Exp. Comp Expl. Comp Expl. Comp Expl. Comp
assembly date date date date
Assy. 1 (u) 13.6. 15.6. K9,K4 1.1. K8,K4 15.6. K9,K4 13.6. K9,K4
Assy. 2 (v) 16.6. 18.6. K9,K4 1.7. K9,K4 1.7. K9,K5 16.6. K9,K4
Assy. 2 (w) 17.6. 1.8. K9,K5 1.7. K9,K5 1.8. K9,K5 17.6. K9,K4
Assy. 2 (x) 29.6. 1.7. K9,K5 1.7. K9,K5 1.7. K9,K5 29.6. K9,K4
Assy. 2 (z) 3.7. 5.7. K9,K5 1.7. K9,K5 5.7. K9,K5 3.7. K9,K5
Explanation of table
Requirements date for assembly
When planning the car, the planned order finish date is used as the BOM explosion date for
the car. Using takt-based scheduling, the planning matrix has determined that the assembly is
installed 2 days before the finish date of the planned order, that means, the safety time for
assembly 1 or assembly 2 and the subordinate components is 2 days and the requirement
date for the components is 2 days before the requirement date for the car.
Explosion date
In the explosion date column, you can see the explosion date for the BOM of the assembly
selected, that has been determined by the setting in the product master for the assembly
(alternatives 1-4).
Component
In the component column, you can see the components that the planning run determines
starting from the explosion date for the assembly.
Explosion date for alternative 1
This is the date for the BOM explosion for the assembly selected. In the case of alternative 1,
the indicator for Use BOM explosion date in order for final product has been set in the BOM
explosion date field in the product master for the assemblies. The BOM explosion date from
the planned order for the car is therefore used for the BOM explosion of the assembly 1 or 2.
The component K5 should have been selected for v, because assembly 2 is made using K5
(assembly 2 has been selected due to the start-up parameters). The correct component K5
cannot be determined because the start-up parameter for the sales order is not taken into
account at the component variant.

In the case of alternative 2, the indicator for Use effective-from date for comp. var. as BOM
explosion date has been set in the BOM explosion date field in the product master for the
assemblies. The date from which the assembly is valid is therefore used for the BOM
explosion of the assembly 1 or 2. This date comes from the change number that you have
entered for the component variant.
K8 should have been determined for u, because assembly 1 has been selected and K8 is
used to make this assembly. However, K8 has another validity period (valid until 1 March, K9
is then valid afterwards).
In the case of alternative 3, the indicator for BOM explosion dte fm order or effective-fm dte
for comp. var. has been set in the BOM explosion date field in the product master for the
assemblies.
This setting generally gives a correct result, because the valid-from date that lies furthest in
the future or on the next planning date is always selected.
In the case of alternative 4, the indicator for Use BOM explosion date as requirements date
for component has been set in the BOM explosion date field in the product master for the
assemblies. The requirements date for the assembly is used for the explosion.
This setting always selects the wrong components if, due to a special explosion, such as
when using the start-up parameters, the requirements date deviates too far from the
explosion date for the order.
In the case of v, w and x, K4 is therefore always selected, even though assembly 2 is made
using K5.
Summary
Alternative 3 is the best setting because this always gives the correct result if change statuses
with start-up parameters are passed on to the superior assembly. (See order A2 ).
Planning
Use
There are different functions for generating and updating a rapid planning matrix:
• Model mix planning run
• Update matrix
Integration
Generating a matrix is integrated in the model mix planning run.
Updating a matrix is integrated in the product view and in the product planning board.
Prerequisites
You have defined a process package in Customizing for Model Mix Planning.
Features
Model Mix Planning
You run model mix planning [Page 150] when you have transferred new sales orders to the
APO. The APO generates planned orders for the customer requirements and schedules the
planned orders on the production line that you have defined. Then the sequence of the

planned orders, and thus the start and end dates for the orders, are defined. The matrix
explosion is executed and the rapid planning matrix is exploded.
You have combined the planning algorithms in the process package for model mix planning
and defined in each algorithm that the planning run is to generate planned orders with
quantity 1 or more. You use a process package to define how the system is to proceed in the
short-, medium, and long-term planning horizon.
Example
You have entered percentage smoothing [Page 145] as the algorithm and have defined that
several requirements are to be grouped in one planned order in the long-term planning
horizon. The planning run generates several requirements for one planned order. The
planned orders generated are grouped in time buckets, such as shifts, for example. The
orders are parallel to each other; their duration is distributed throughout the shift. Scheduling
schedules the start date for all these planned orders to the start of the shift and the end date
to the end of the shift. Then the rapid planning matrix is generated. The matrix determines the
dependent requirements and the requirement dates. Scheduling for the component
requirements is not exact because the planned orders for the final product are not scheduled
exactly. An exact determination of the requirement dates is not necessary in the long-term
horizon.
You have set the prioritized equal distribution [Page 146] in the medium-term planning
horizon and the generic algorithm [Page 148] in the short-term horizon. The planning run
generates planned orders with quantity 1 in both processes and determines the exact
sequence of the orders. The start and end dates for the planned orders are determined by
using this sequence. Then the rapid planning matrix is generated. The matrix can determine
exact requirement dates for the components in this case.
Update matrix
You can use the Update Matrices [Page 193] function in the menu for the Rapid Planning
Matrix to run planning for all or individual RPM products. The prerequisite is that the APO has
already generated planned orders for the RPM products to be planned; you have run model
mix planning.
Update matrix from the product view/product planning board

You can update the rapid planning matrix for a particular RPM product from the product view
or from the product planning board too. See also: Update Matrix in the Product View [Page
194].
Execute a Model Mix Planning Run

Prerequisites
You have defined a process package in Customizing for Model Mix Planning.
Procedure
Optimization → Model Mix Planning → Model Mix Planning Run.
This takes you to the initial screen for the planning run.
2. Enter the planning version and the line.
The line is the iPPE node that you have created for the line or line network where the
product is to be manufactured.
3. Enter a Model Mix Procedure Package and, if necessary, restrict the horizon for the
planning.

4. Choose .
Update Matrices
Use
This is how you start the planning run for the rapid planning matrix. You can update existing
matrices for all RPM products or for individual RPM products and create new matrices.
Prerequisites
You have used Model Mix Planning [Page 192] or the Plan product function in the Product
view to generate planned orders for the RPM product that are assigned to the pegged sales
order.
Procedure
Optimization → Rapid Planning Matrix → Update Matrices.
2. Enter the planning version and specify whether the planning run is for all products by
selecting All marked RPM products. Choose Select products when you want to plan only
particular products and enter the product number and location.
3. Check and, if required, change the control parameters for the planning run.
Parallel processing
Set the indicator to define that the planning run is to be processed in parallel. See
also: Parallel Processing [Page 195].
Explode
The system automatically sets this indicator when a new matrix must be generated
for the product due to a change. The system then re-explodes the master data for the
product. You can set the indicator manually when you want the planning run to
generate a new matrix.
No new matrix is generated in the planning run when you delete the indicator.
Re-read iPPE
The system automatically sets this indicator when you change planning-relevant
master data for the product (product master, iPPE data, change numbers, object
dependencies). The system then re-explodes the master data and updates the
existing rapid planning matrix. The master data is re-read in the planning run, even if
you have not changed the master data, when you manually set the indicator.
Re-read configuration
You set this indicator only when there were explosion errors in the last planning run.
The indicator has the effect that all configurations are re-read from the database in
the planning run and the configuration data is used to set up a new characteristic
value matrix.
You can use the Set Planning File Entries for RPM Products [Page 194] function
when you want to use different control parameters to those in the initial screen for
certain RPM products.

4. Choose to start the planning run.
Update the Matrix in the Product View

Procedure
1. Starting from the Production Planning menu, choose Interactive Production Planning →
Product View.
This takes you to the initial screen for the product view.
2. Enter the RPM product and the location and choose .
This takes you to the product view.
3. Choose to make changes and use planning functions.
4. Choose the function key Product heuristic.
5. Choose .
This takes you to the dialog box Run the RPM.
The control indicators set by the APO for running planning are displayed in the dialog
box.
6. Choose to start the planning run for the rapid planning matrix.
Messages may be displayed in the dialog box when there are errors generating the
matrix, such as the product master for a colored material has not been created.
Result
The rapid planning matrix for the product is updated.
Set Planning File Entries for RPM Products

Use
You can use the planning file entries for each RPM product to define whether the rapid
planning matrix for the product is to be generated in the next planning run, whether the iPPE
data is to be re-read, or whether the characteristic value matrix is to be set up again. The
control parameters that you define are stored so that you can use them in the next planning
run.
This procedure has the advantage that you can define control parameters for each RPM
product. This is particularly important when you want to use the Update Matrices [Page 193]
function to simultaneously plan several RPM products because you define the same control
parameters for all RPM products in the initial screen for this function.
Prerequisites
You have used the rapid planning matrix to plan the RPM product.
Procedure
1. Starting from the Production Planning node, choose Automated Production Planning and
Optimization → Rapid Planning Matrix → Planning File Entries for Planning Matrices.
This takes you to the Set Planning File Entries for RPM Products screen.
2. Enter the planning version and choose .

A list is displayed with all the RPM products for which a matrix has been generated.
3. You can check and change the control parameters for the next planning run for each
RPM product.
Parallel processing
Set the indicator to define that the planning run is to be processed in parallel. See
also: Parallel Processing [Page 195].
Explode
The system automatically sets this indicator when a new matrix must be generated
for the product due to a change. The system then re-explodes the master data for the
product. You can set the indicator manually when you want the planning run to
generate a new matrix.
No new matrix is generated in the planning run when you delete the indicator.
Re-read iPPE
The system automatically sets this indicator when you change planning-relevant
master data for the product (product master, iPPE data, change numbers, object
dependencies). The system then re-explodes the master data and updates the
existing rapid planning matrix. The master data is re-read in the planning run, even if
you have not changed the master data, when you manually set the indicator.
Re-read configuration
You set this indicator only when there were explosion errors in the last planning run.
The indicator has the effect that all configurations are re-read from the database in
the planning run and the configuration data is used to set up a new characteristic
value matrix.
4. Choose .
Parallel Processing During the Planning Matrix Run

Use
In order to improve performance during the planning run, you can determine that the planning
is to be executed using parallel processing.
In the case of products with many component variants, you can also determine that the
system creates several sub-matrices for a product instead of one very large matrix. The
splitting of one large matrix into several sub-matrices accelerates the planning run only if this
is done when using parallel processing.
Integration
You make the settings for parallel processing in the global settings [Page 177] or in the initial
screen for the planning matrix run.
Prerequisites
In Customizing for Production Planning and Detailed Scheduling (PP/DS), you have entered
the server that you want to use for the planning in the IMG activity Maintain Destinations for
Parallel Processing.
If you want to split a large matrix into several sub-matrices, you must use the control data for
RPM products [Page 179] function to determine the number of sub-matrices required for each
product that is to be planned using the rapid planning matrix.

Features
Parallel processing
During the planning run, the rapid planning matrix should always be created with parallel
processing.
To do this, choose the setting RPM part of planning run is always processed in parallel in the
Parallel Processing field in the global settings. If you have selected this setting in
Customizing, the part of the planning run where the planning matrix of a product is created is
always executed using parallel processing, even if you have not set the indicator for parallel
processing in the initial screen of the planning run.
Parallel processing with creation of sub-matrices

Sub-matrices should then be created only if the planning run is executed using parallel
processing.
To do this, choose the setting Sub-matrices only in parallel processing in the Parallel
Processing field in the global settings and set the indicator for parallel processing in the initial
screen of the planning matrix run. See also: Update Matrices [Page 193].
The use of sub-matrices is recommended if the product requires a large number of
components. The planning matrix is then split into several matrices. The planning run should
be executed using parallel processing so that performance is not impeded by the splitting into
several matrices.
Execute Planning Run for APO Components

Use
The rapid planning matrix has determined dependent requirements for the components. In
order to execute production planning for the components that are to planned in the APO, you
must execute a planning run. You can execute the planning run immediately or in the
background.
Prerequisites
• On the PP/DS tab page of the product master for the APO components, you have
selected Automatic planning in planning run.
• In the Explode task list field on the PP/DS tab page, you have set the indicator 3 for
single explosion of iPPE.
• You have created the planning matrix for the RPM product. The planning matrix has
determined dependent requirements for the components and planning file entries.
Procedure
1. Starting from the Production Planning node, choose Automated Production Planning and
Optimization → Production Planning Run.
2. Enter the planning version, a time profile and the propagation range.
3. Enter a heuristic and in the Obj. field, enter the indicator 4 for products.
4. Choose the function key Selection criteria.
A dialog box for defining the products to be planned appears.
5. Enter * in the product field and select the indicator for only products with planning file
entries.

6. Choose .
Result
The APO plans all products that have planning file entries.
Evaluation of the Planning Results

Use
After planning, you can display the planning results for the RPM product and the components.
Various functions are available for this.
Prerequisites
You have run model mix planning or planned the RPM product using the product view.
Features
Displaying the Rapid Planning Matrix [Page 197]
You can use this function to display the characteristic value matrix and the component variant
matrix that have been generated by the planning run for an RPM product.
Display Planned Orders with Explosion Errors [Page 200]
You can use this function to display the orders for which no or too many component variants
have been selected due to an error in the object dependency or an error in the order
valuation.
Display Performance Data [Page 201]
You can use this evaluation to check how long the APO took to generate the matrix.
Product View [Page 308]
In the product view, you can display the planning results including the stock requirements
situation for each individual product that you plan in the APO.
Product Planning Table [Page 324]
In the product planning table, you can display and further process the planning results for the
RPM product and its components that are also planned in the APO.
Displaying the Rapid Planning Matrix

Use
You can use this function to display the rapid planning matrix generated for a product by the
APO.
Features
Accessing the rapid planning matrix
You can access the rapid planning matrix for a product by starting from the Rapid Planning
Matrix node and selecting Display Matrix. See also: Display the Rapid Planning Matrix [Page
199].

Displaying general data

The general data contains the entries for product, location, production version and the
number of planned orders.
By choosing , you can display further information about the RPM product and about the
planning matrix generated, such as the iPPE object used, and the entries for the component
variant matrix.
Display the characteristic value matrix

In the characteristic value matrix, you see the characteristics with the characteristic values in
rows. Each column corresponds to one order. If there is an X in the column for the orders, this
shows that a characteristic value has been selected for a particular planned order.
Display all characteristic values:
If you choose this function key, a list with all characteristics and characteristic values, which
you have maintained for the RPM product, appears.
Find characteristic:
If you choose this function key, the Find characteristic dialog box appears. Enter the required
characteristic and, if necessary, the required characteristic value and choose . The system
jumps to the corresponding row in the characteristic value matrix.
Display the component variant matrix

In the component variant matrix, you see the iPPE nodes with the component variants in
rows. You also see the product number for the component selected. If there is an X in the
column for the orders, this shows that a component variant has been selected for a particular
planned order. If an explosion error [Page 200] has occurred for an order and a component
variant, this is shown by a (required component error) or a (multiple selection error).
All component variants
If you choose this function key, a list with all of the component variants that you have
maintained in the product variant structure appears. The system also displays detailed
information for each component variant, such as the use of start-up parameters, use of an
RPM time bucket, line resource and line segment, where the components are to be installed,
and so on.
All color variants
If you choose this function key, a list with all of the color nodes with the assigned color
variants that you have maintained in the product variant structure appears.
Find component node
If you choose this function key, the Find component node dialog box appears. Enter the
required node and, if necessary, the required variant and choose . The system jumps to
the corresponding row in the component variant matrix.
Indicate backflushed components in the component variant matrix

The information on the backflush status is displayed for each component in the component
variant when you have set the With backflush info indicator on the initial screen.
An X at a component variant means that the component for the order was selected by
planning but no backflush has been entered.
A plus sign (+) at a component variant means that the backflush in APO has been entered for
this component and the order in whose column the plus sign is displayed. However, the
goods issue for the component (backflush) is not yet posted in the DI System.
A circle (O) at a component variant means that goods issue has been posted in the DI
System based on the backflush data transferred from the APO.

A minus sign (-) at a component variant means that the production backflush in the APO for
this product has been cancelled, but the goods issue that has been posted for the relevant
component in the DI System is not yet cancelled.
Display all orders

If you choose the function key All orders, the list with all of the planned orders in the matrix
appears. For each planned order, the system displays the sales orders, to which the planned
orders are assigned.
Display order data

You can display the order data for an X by positioning the cursor by and X and then choosing
(Cursor) position → Column (order) → Information about order.
Display order BOM

You can display the BOM for a particular order by positioning the cursor by an X and then
choosing (Cursor) position → Column (order) → Order BOM.
Scroll functions
You can use the scroll keys to navigate through the matrices quickly.
Display details
You can display details for orders, characteristic values and component variants as well as
technical information for a matrix.
Go to master data
• By double-clicking in the relevant field of the component variant matrix, you can go to the
product masters for the components and to the product variant structure.
• If you choose Goto → Product master, the product master for the RPM product appears.
Display the product view for the RPM material

Choose Goto → Product view in order to access the product view for the RPM product. From
here, you can trigger the planning for the product again.
Display Planning Matrix

Procedure
1. Choose Display Matrix from the Rapid Planning Matrix node.
The initial screen appears.
3. Position the cursor in the Product field and choose F4.
A dialog box containing all RPM products, for which the system has generated a
planning matrix, appears.
4. To select an RPM product, double-click on it..
The system copies the product number, location and production version to the initial
screen. (The production version is displayed in the Source of supply field.)
5. If you want to see the backflush status of the components in the display, select the With
backflush info indicator.
6. Select whether the system is to sort the planned orders by the requirements date or by
the explosion date of the PVS (this is generally the start date of the planned order).

7. Choose .
The overview screen for the matrix display appears.
8. In order to display the RPM product, location, production version and number of planned
orders, choose General data in the overview screen.
9. In the overview screen, choose Characteristic matrix.
This expands the matrix with the characteristic values. An X indicates that a
characteristic value has been selected for a particular order.
10. In the overview screen, choose Component variant matrix.
This expands the component variant matrix. An X indicates that a component variant
has been selected for a particular order.
11. In order to display the legends for the symbols that are displayed in the columns, choose
Extras → Legends → Crosses.
12. In order to display the meanings of the icons displayed, choose Extras → Legends →
Icons.
Display Orders with Explosion Errors

Use
This function involves a check that determines for which orders certain components could not
be selected correctly, because, for example, there is an error in the object dependency, which
you have maintained in iPPE, or because there is an error in the order valuation. The
explosion could not determine the correct components because of these reasons.
Prerequisites
You have set the Multiple selection and Required component indicators in the Control Data
for RPM Products transaction for each product whose explosion is to be checked.
Procedure
1. Starting from the Rapid Planning Matrix node, choose Orders with Explosion Errors.
This takes you to the initial screen for the evaluation.
2. Enter the planning version, the product, and the location and choose .
This takes you to the list of orders for the selected product that have explosion errors.
Result
The following data for each planned order with incorrect explosion is displayed in the list:
• the order number of the planned order
• the BOM explosion date of the planned order
• the iPPE node where the error occurred
• the type of error
The error type Required component means that no component variant was selected
although the system must determine at least one component variant because the
node is indicated as a required component in the PVS. You indicate that a node in the
PVS is a required component by setting the Required component indicator on the tab
page Basic Data.

The error type Multiple selection means that more than one component variant was
selected although you have defined that only one component node can be selected at
the node.
Multiple selection is then not allowed for a node if you have not set the Multiple
selection indicator in the basic data for the node.
If you have set the Multiple selection indicator, the multiple selection of
component variants is allowed and no errors occur when using multiple selection.
Display Performance Data

Use
You can use this function after the planning run to check how long the system took for each
individual step involved in generating the planning matrix.
Procedure
1. Starting from the Rapid Planning Matrix node, choose Tools → Display Performance
Data.
The Output RPM performance statistics screen appears.
The system creates a list with the performance data for the RPM products that have
been planned.
Result
The system displays the following information for each RPM product that has had a planning
matrix generated:
• production version (with iPPE access object) that was used as the basis for planning
• number of sub-matrices generated
• duration of individual steps, such as generation of characteristic value matrix, generation
of component variant matrix, and so on
• number of objects
RPM Time Bucket

Definition
Information that defines the time horizon for grouping the component requirements. It involves
the following entries:
• which time units are used
• how many periods of the individual time units are used
• the sequence, in which the periods with different time units appear in the table.

Use
You use an RPM time bucket to determine the periods (buckets) that are to be used for
grouping the component requirements, which have been determined by the matrix. The
system groups the dependent requirements of the components, for which you made the
necessary settings in the material master/product master so that they can be grouped.
This has the advantage that the system does not have to generate a procurement element for
each individual dependent requirement. It is only necessary to generate one procurement
element for all dependent requirements that fall within a certain period. This helps to greatly
reduce the volume of data.
Maintaining Time Bucket for Grouping Component

Requirements
Use
In this activity in Customizing for Rapid Planning Matrix, you define the time bucket for the
grouping of component requirements, which have been determined by the rapid planning
matrix.
For components that you have set in the material or product master so that they can be
grouped (Always collective reqmts field), the APO calculates the total dependent
requirements of a component per period using the results of the matrix. You can use a time
bucket profile to freely define the periods. Requirements grouping by period has the
advantage that the system does not have to generate a procurement element for each
individual dependent requirement. It is only necessary to generate one procurement element
for all dependent requirements that fall within a certain period.
You use this procedure for components that are not directly intended for a particular sales
order.
Prerequisites
• You have maintained the factory calendar for a location.
• You have created a line resource and a shift sequence for this resource.
Features
The maintenance of the time bucket is independent from the location and the factory
calendar. You assign the time bucket to a product by entering a time bucket ID in the RPM
TmBcktsProf field in the product master (Demand tab page). The system uses the
assignment to determine the necessary line resources and thereby the valid shift sequence
for the resources as well as the factory calendar. The system uses the entries for the time
bucket, the shift sequence and the factory calendar to determine the periods in which the
dependent requirements are to be grouped.
If you wish to simulate the effect of a time bucket on a particular resource, choose the
Simulation for a resource function key. The system then calculates the time bucket for the
resource selected. See also: Calculate the Time Bucket for a Resource [Page 205]
Define periods
For example, you can use a time bucket to determine that the dependent requirements are to
be grouped monthly in the long-term horizon, weekly in the mid-term horizon and daily or by
shift in the short-term horizon. In addition, you can breakdown a shift into further subdivisions.
For example, each hour should be the start of a new period, in which case the dependent
requirements are grouped on an hourly basis. To do this, you enter the number of shifts, in
which there is to be a further division such as hourly grouping, in the lowest line of the time

bucket. In addition, you must maintain the table in the lower screen area. Enter a time offset
for the further subdivisions. For example, if the requirements are to be grouped hourly, enter
1:00:00 first, then 2:00:00 in the second row, and so on. The system then calculates period 1
as 6.00 am to 6.59 am, period 2 as 7.00 am to 7.59 am, and so on.
However, you can also set just daily groupings or shift groupings.
Standard time bucket

The time bucket SAP_PPROFILE_DEFAULT is offered as default. During the first planning
run, the system checks that you have created a time bucket and made the assignment in the
product master. If you have not done this, the system then automatically uses the time bucket
SAP_PROFILE_DEFAULT. The system then always uses this time bucket when grouping the
component requirements if you have selected Always collective reqmts in the product
master for the components and have not entered a user-defined time bucket in the product
master.
Activities
In order to create a time bucket, start from Customizing for Production Planning and Detailed
Scheduling (PP/DS) and choose Rapid Planning Matrix → Maintain Time Buckets Profile for
Grouping of Component Requirements.=
The maintenance of a time bucket is made clear in the following example:
The dependent requirements are to be grouped monthly in the long-term horizon, weekly in
the mid-term horizon and daily or by shift in the short-term horizon. For this, you set the time
bucket as follows:
Length Unit of length Unit of aggregation
Year
1 Month Month
1 Month Week
1 Week Day
1 Day Shift
Smaller subdivision
The system interprets the time bucket starting from the bottom and working upwards. Starting
from the planning date, the periods are to be shifts for the first day, then days for a week, and
then weeks for a month. The last period is to be a month.
Display the Resource Time Stream

Use
If errors occur when defining the periods for the grouping of component requirements, these
may be related to errors in the maintenance of the line resource. You can use this report to
check very quickly the data, which you have maintained for the line resource and which the
liveCache used when calculating.
Integration
Alongside the time bucket that you assign to the components, the line resouce that have
entered in the line design plays an important role in defining the periods for the requirements

grouping. The system uses the line resource to determine the times (shift sequence,
workdays, week program, break, and so on) that are used when working.
Prerequisites
• You have created a line resource as well as a shift sequence and break pattern for this
resource.
Features
The report reads the resource data from the liveCache and puts it in a list. This data is stored
in the form of a time stream in the liveCache.
You can choose to display the shift sequence, day program, week program, month or year.
Activities
1. Starting from the Rapid Planning Matrix node, choose Tools → Time Buckets Profile →
Display Resources Time Stream.
This takes you to the initial screen for the display.
2. Enter the line resource, location, planning version and date, from which the time stream is
to be generated. Select for which period type, such as shift or month, the system is to
generate the time stream.
3. Choose .
A list containing the following data appears:
Start time
This start time is displayed in the format year month day time. The time is displayed
using the UTC [External] format, because the liveCache only works with UTC.
The start time shows the start of a period. For example, if you have entered shifts as
the period, the system always displays the start of the shift as the start time.
End time
This time is also displayed in UTC format.
The end time shows the end of the period selected. For example, if you have entered
shifts as the period, the system displays the end of the shift.
Date
In the case of shifts, this date shows the day on which a shift falls.
Shift number from product planning table
In the case of multiple-shift operation, the shifts contained in one day are numbered
consecutively, for example, early shift = 1, late shift =2 and night shift = 3.
Period indicator
This shows for which period type the time stream has been generated, for example, S
for shift and M for month.
Period duration
Duration of period displayed
Duration
Rate of resource utilization
Shows the rate of utilization, which the liveCache uses when calculating. You enter
the resource utilization rate on the Standard capacity tab page of the resource
master.

Calculate the Time Bucket Profile for a Resource

Use
You can use this function to simulate determining the periods for the grouping of components.
Integration
You can also calculate the time bucket profile in Customizing when maintaining the time
bucket. You start the function by accessing a particular time bucket and choosing the
Simulation for a resource function key.
Prerequisites
• You have maintained an RPM time bucket [Page 201].
Features
The calculation of a time bucket profile is made clear in the following example:
You have set the time bucket as follows:
Length Unit of length Unit of aggregation
- - Year
1 Month Month
1 Month Week
1 Week Day
1 Day Shift
In this example, a resource with a shift sequence of 3 shifts (6.00 to 14.00, 14.00 to 22.00,
22.00 to 6.00) is used. You set a start date of 8 December 1999, for example. The simulation
then produces the following result for the time bucket described above:
Shifts
• Period 1: 8 December 1999, 06.00 to 13.59
• Period 3: 22.00 on 8 December 1999 to 05.59 on 9 December.
Days
• Period 6: 11 December 1999, 06.00 to 05.59 and so on up to 18 December 1999 at
05.59.
Weeks
• Period 11: 06.00 on 20 December 1999 to 05.59 on 27 December 1999
• Period 12: 06.00 on 27 December 1999 to 05.59 on 03 January 2000

• Period 13: 06.00 on 13 Janurary 2000 to 05.59 on 10 January 2000

• Period 14: 06.00 on 10 January 2000 to 05.59 on 17 January 2000
• This then continues with weeks up to 05.59 on 31 January.
• Period 17: 06.00 on 31 January 2000 to 05.59 on 01 February 2000
Months
Period 18: 06.00 on 1 February 2000 to 05.59 on 01 March 2000
A month always starts with the first workday and ends on the first workday of the following
month.
Activities
Calculate Time Buckets Profile for Resource.
2. You enter the line resource, location , planning version, time bucket and start date and
choose .
Display Time Bucket Profile from LiveCache

Use
You can use this function to check the time bucket profile that the liveCache has calculated
for the resource entered by you.
Integration
This function provides the same results as the function Calculate the Time Bucket Profile for a
Resource [Page 205].
Prerequisites
• You have maintained an RPM time bucket [Page 201].
Features
The time bucket profile for a resource is calculated during the planning run and is then saved
in the liveCache. You can use this function to check the results of this calculation.
Activities
Display Time Buckets Profile from liveCache.
2. You enter the line resource, location , planning version, time bucket and select forward
scheduling.

If you enter a lead time, the report then moves the time stream back by the
number of minutes entered. For example, if you set a lead time of 10 minutes and
the period start is at 14.00 hours, the system then displays the period start as
13.50.
The lead time is the time between the start of an order and the installation of a
component. It is calculated from the number of stations and the takt time. For
example, a component is installed at station 4. The takt time is 10 minutes; this
results in a lead time of 3 x 10 minutes = 30 minutes.
You can also set a lead-time offset. In this case, the report moves the time
stream forward by the number of minutes entered.
3. Choose .
The system displays the periods that the liveCache has determined using the
resource data and the time bucket profile.
Reorganize Time Bucket Profile from LiveCache

Use
If you change a time bucket or no longer use it, it is useful to not just delete the time bucket
profile in Customizing but to also delete the time stream (consisting of the periods from the
time bucket and the requirements dates for the components), which the planning run
generated for the components involved.
Features
The reorganization run checks for a planning version whether a time stream is still used. If a
time stream is no longer used, the system then deletes it.
Activities
1. In order to execute the reorganization, start from the Rapid Planning Matrix node and
choose Tools → Time Buckets Profile → Reorganize Time Buckets Profile from
liveCache.
Heuristics
Use
You use heuristics [External] to solve specific planning tasks for selected objects (depending
on the focus of planning: products, orders, operations, resources or line networks) using a
particular planning procedure (algorithm). You are able to use your own heuristics or the
heuristics provided by SAP. SAP provides a number of standard algorithms (also referred to
as function modules) to solve specific planning tasks. For each algorithm, you are able to vary
the settings, thereby defining different heuristics using the same algorithm.

You use heuristics in both interactive planning and during background planning. In the
product master for each product, you can define which heuristic is to be used during the
production planning run [Page 122] or when executing the product heuristic in interactive
planning.
Prerequisites
• You have maintained the necessary master data [Page 110] and the PP/DS settings
[Page 111].
• You have defined a propagation range (see Maintenance of PP/DS Settings [Page 111])
that contains the products you want to plan.
• You have maintained which heuristic is to be used to plan the product on the PP/DS tab
of the product master.
• If you do not wish to use the standard SAP heuristics, you have created or maintained
• You have created/maintained heuristic profiles that are used to control which heuristics
are displayed in the menus of interactive planning in Customizing for Production Planning
and Detailed Scheduling, under Heuristics → Maintain Heuristics Profiles. You have
entered the appropriate heuristic profile in the desired overall profile of the order view, DS
planning board and the product planning table.
which no heuristic has been defined in the product master in Customizing for Production
Defaults.
Features
Standard Heuristics
Several standard heuristics are provided by SAP in the following areas:
• Production planning [Page 209]
These heuristics are mainly lot-sizing procedures whose planning focus is on
products. Examples of these heuristics include periodic lot-sizing and purchase order
optimization.
These heuristics are scheduling heuristics whose planning focus is on resources and
operations. Examples of these heuristics include reduce lead times and resolve
backlog.
These heuristics generate planned orders to requirements taking into account the
resource capacity for each period. The focus of planning is on resources, line
networks and products.
• Model mix planning [Page 150]
restrictions into account. The focus of planning is on resources and line networks.
Defining Your Own Heuristics

In APO, you are able to define your own heuristics using the algorithms provided by SAP. You
can define heuristics in Customizing for Production Planning and Detailed Scheduling, under
Heuristics → Maintain Heuristics, by entering the algorithm provided by SAP and defining the
settings as required.

You are also able to use your own algorithms to create heuristics provided that you integrated
the algorithm into the APO System. For more information, see Creating Heuristics Using Your
Own Algorithms [Page 226].
Heuristics for Automatic Planning in a Planning Run

You are able to define a heuristic at product-location level that is to be used for automatic
planning during the planning run. On the PP/DS tab of the product master, you can define
which heuristic is to be used to plan the product. You can set the Automatic planning in
planning run [Page 121] indicator for a product. In this case, the system generates a planning
file entry for the product every time a change relevant to planning is made. The products are
then planned during the next net change planning run (you set the Planning file entry created
indicator on the initial screen) using the heuristic defined in the product master (if you enter
the product heuristic on the initial screen of the production planning run).
If you do not set the Planning file entry created indicator, a regenerative planning run will be
performed, thereby planning all products in the selection.
If the products are to be planned according to the heuristic maintained in the product master,
you use the Product Heuristic. You may, however, perform a net change planning run using a
different heuristic.
You can also execute several heuristics on the same products in one planning run. The
heuristics are executed in the sequence you enter them on the initial screen. An example of
this could be that you perform the SAP001 Schedule sequence heuristic to improve the
resource loading and then perform the SAP_PP_007 Move requirements to receipts heuristic
to reschedule the top level orders accordingly.
Heuristics in Interactive Planning

You are able to define which heuristics appear in the interactive planning menus of the:
• Order view screens [External]
You do this by defining a heuristic profile containing the relevant heuristics in Customizing for
Production Planning and Detailed Scheduling, and then by entering the appropriate heuristic
profile in the overall profile for the screens. You are then able to start the heuristics in
interactive planning by accessing them from the menu.
In the interactive planning screens, you can plan the product according to the heuristic
defined in the product master by using the Product Heuristic function, or you can choose
another heuristic and vary the parameters for this heuristic by using the Variable Heuristic
function. The variable heuristic also allows you to select components for the products that are
also to be planned with the heuristic.
For more information, see Heuristics in Interactive Planning [Page 211].
Planning Run in Simulation Mode

You can execute a production planning run and save the results in a simulation version. This
allows to decide at a later point in time whether or not to merge the simulation into the
operative planning version.
Heuristics for Production Planning

Use
You use these heuristics [External] to plan products during interactive planning or the
production planning run [Page 121]. The heuristics cover requirements using the lot-sizing

procedures defined for the heuristic. Heuristics are available for both products produced in-
house and products procured externally.
An important production planning heuristic is the Product heuristic. You use this heuristic to
execute the heuristic defined in the Product Master for each product. The product heuristic
can be started in the interactive planning screens by choosing Product heuristic or by starting
the production planning run using the Product heuristic.
Prerequisites
• You have maintained which heuristic is to be used to plan the product in the PP/DS tab of
the Product Master.
• You have created/maintained heuristic profiles that are used to control which heuristics
are displayed in the menus of interactive planning in Customizing for Production Planning
and Detailed Scheduling, under Heuristics → Maintain Heuristics Profiles. You have
entered the appropriate heuristic profile in the desired overall profile of the order view, DS
planning board and the product planning table.
which no heuristic has been defined in the Product Master, in Customizing for Production
Defaults.
Features
SAP provides several standard heuristics for production planning whose planning focus is on
products. The heuristics available and their uses are described below
• SAP_PP_001: Change order manually
You use this heuristic to generate new receipt elements to cover product
requirements. Here, the lot size parameters maintained in the product master are
taken into consideration.
• SAP_PP_002: Planning standard lots
You use this heuristic to create new receipt elements in order to cover product
requirements. Product requirements can be purchase requisitions, planned
independent requirements, transfer requests or dependent requirements. Receipt
elements are created for in-house production or external procurement, depending on
transportation lanes, the PPM or the procurement type in the product master. Lot
sizes defined in the product master are used to calculate the receipt quantities.
• SAP_PP_003: Planning deficits
You use this heuristic to plan just the shortages and to reduce surpluses. Dynamic
pegging relationships are taken into account with this heuristic.
• SAP_PP_004: Planning standard lots in 3 horizons
You use this heuristic to define three planning horizons within which a different lot-
sizing procedure can be used. You are able to choose between a procedure with lot-
for-lot order quantities or various period lot sizes.
• SAP_PP_005: Part period balancing
You use this heuristic to optimize setup and storage costs when calculating the lot
size. Starting from the product shortage date, consecutive requirements quantities
continue to be collected in a lot until total storage costs exceed the setup costs. Lot-
sizing parameters are taken into account during this procedure.
• SAP_PP_006: Least-Unit Cost Procedure: External procurement

You use this heuristic to calculate the quantities of external procurement orders for
material bottlenecks of a product. The system specifies the unit costs for each
manufacturer, taking into consideration storage costs, fixed order costs, quantity-
dependent discounts and manufacturer-dependent dispatch times. Once the optimum
discount scale is reached and the costs begin to rise again, no more lots are created.
• SAP_PP_007: Reorder point planning
You use this heuristic so that procurement is always triggered when the sum of the
inventory levels and fixed receipts exceeds the so-called reorder point. The reorder
point should cover the expected average material requirements during the
replenishment lead-time.
• SAP_MRP_001: Product planning (comp. according to low-level code)
You use this heuristic to plan products according to the heuristic defined in the
Product Master for each product. The heuristic is carried out for the top level product
using low-level coding, that is, if a component is not available on time, the top order is
not rescheduled. The components that are defined as being planned automatically
(both immediately or in planning run) are then planned using the heuristic defined in
the Product Master. If you have not defined a heuristic for a product in the Product
Master, the APO System uses the default heuristic you have entered for the Product
heuristic in Customizing for Production Planning and Detailed Scheduling, under
Global Settings → Maintain Global Parameters and Defaults.
Components that are defined as being planned manually (both with and without
availability check) are not taken into account during the production planning run. The
availability check for components planned manually with check is not carried out.
• SAP_MRP_002: Product planning (plan comp. immediately)
You use the product heuristic to plan products according to the heuristic defined in
the Product Master for each product. The heuristic is carried out for the top-level
product. Components that are defined as being planned automatically and
immediately are planned using a simple lot-sizing heuristic. Planning with this
heuristic is carried out according to multi-level logic, that is, if a component is not
available on time, the top-level order is rescheduled. For the components that are
defined as being planned automatically in the planning run, planning file entries are
created. The product heuristic can be executed in interactive planning and during the
production planning run. If you have not defined a heuristic for a product in the
Product Master, the APO System uses the default heuristic you have entered for the
Product heuristic in Customizing for Production Planning and Detailed Scheduling,
under Global Settings → Maintain Global Parameters and Defaults.
The availability check is carried out for components that are defined as being planned
manually with availability check.
You are able to create your own heuristics based on the standard algorithms provided by SAP
in Customizing for Production Planning and Detailed Scheduling, under Heuristics → Maintain
Heuristics. You can therefore change the parameters for the algorithm and define new
heuristics.
Heuristics in Interactive Planning

Use
You are able to execute heuristics in the following interactive planning screens of Production
Planning and Detailed Scheduling:
• Order view screens [External]


You use heuristics in interactive planning to improve the planning situation by addressing
specific planning problems with appropriate heuristics, as well as to plan any products that
are defined as being planned manually.
Prerequisites
• You have defined which heuristic is to be used to plan the product in the PP/DS tab of the
product master.
• If you do not wish to use the SAP standard profiles, you have created/maintained
heuristic profiles that are used to control which heuristics are displayed in the menus of
interactive planning in Customizing for Production Planning and Detailed Scheduling,
under Heuristics → Maintain Heuristics Profiles. You have entered the appropriate
heuristic profile in the desired overall profile of the order view, DS planning board and the
product planning table.
which no heuristic has been defined in the product master, in Customizing for Production
Planning and Detailed Scheduling under Global Settings → Maintain Global Settings and
Defaults.
Features
Executing Heuristics from Interactive Planning Menus
You are able to define which heuristics appear, and thus can be executed, in the interactive
planning menus of the:
• DS planning board
• Order view screens
• Product planning table
You do this by defining a heuristic profile containing the relevant heuristics in Customizing for
Production Planning and Detailed Scheduling, and then by entering the appropriate heuristic
profile in the overall profile for the screens. SAP provides standard heuristic profiles for each
of the three screens:
Standard Heuristic Profiles
Heuristic Profile Long Text Contents

SAP001 Standard heuristic Contains the detailed scheduling heuristics whose
profile: Graphical focus are on resources and operations. This is the
planning board default heuristic profile in the Overall profile for the
DS planning board.
SAP002 Standard heuristic Contains all production planning heuristics. The
profile for production planning focus of these heuristics is on products.
planning This is the default heuristic profile for the Overall
profile for the order view screens.
SAPREM Standard heuristic Contains the detailed scheduling heuristics and the
profile: Product two heuristics for repetitive manufacturing. The
planning table focus of the latter is on resources, line networks,
and products. This is the default heuristic profile for
the Overall profile for the product planning table.

You can use the default standard heuristic profiles or define your own combination of
heuristics that are to be displayed in the interactive planning menus.
Product Heuristic
In the interactive planning screens, you can plan the product according to the heuristic
defined in the product master by using the Product heuristic function.
The heuristic is carried out for the top level product. Components that are defined as being
planned automatically and immediately are planned using a simple lot-sizing heuristic. The
planning with this heuristic is carried out according to multi-level logic, that is, if a component
is not available on time, the top level order is rescheduled. For the components that are
defined as being planned automatically in the planning run, planning file entries are created.
If you have not defined a heuristic for a product in the product master, the APO System uses
the default heuristic you have entered for the Product heuristic in Customizing for Production
Planning and Detailed Scheduling, under Global Settings → Maintain Global Parameters and
Defaults.
Variable Heuristic
You can execute a heuristic and vary the parameters for this heuristic by using the Variable
heuristic function. An example of this could be that for the period lot-sizing heuristic, you vary
the lot-sizing procedure to be used or the length of one of the three horizons. The variable
heuristic also allows you to select components for the products that are also to be planned
with the heuristic. This functions thus allows multi-level planning using the same heuristic.
Detailed Scheduling Heuristics

Use
The following heuristics [Page 207], that you can use in the production planning run [Page
122] or in the DS planning board [Page 362] for solving special scheduling tasks, are
available for detailed scheduling:
Detailed scheduling heuristics (DS heuristics)
DS heuristic Use
Schedule deallocated operations [Page Schedule selected deallocated [Page 412]
414] operations
Lead time reduction [Page 415] Reduce the lead time [External] for orders that are at
selected resources
Backlog rescheduling [Page 415] Reschedule operations at a resource that lie in the
past
Sequencing [Page 415] Schedule selected operations in a predefined
sequence
Manual sequencing [Page 416] Schedule selected operations in a sequence that
was already created manually.
You can only use this heuristic in the DS planning
board.

Merging orders on container resources Merge selected synchronized planned orders at

[Page 416] multi resources with storage characteristics
(container resources [External]).
board.
Prerequisites
To be able to call up the heuristics in the menu for the DS planning board under Functions →
Heuristics, you must make these heuristics available in the DS planning board using a
heuristic profile. You define heuristic profiles in Customizing for Production Planning and
Detailed Scheduling, and you enter the following in Customizing for the corresponding
application:
• For the DS planning board called up directly [Page 384], you enter the heuristic profile in
the overall profile for the DS planning board or when calling up the DS planning board.
For further information about the overall profile, see the Implementation Guide for the DS
planning board that is called up directly.
• For the DS planning boards that can be called up in the production planning table [Page
386] or in order processing [Page 385], the system uses the heuristic profile that you
entered in Customizing for the Production planning table or the Order view respectively.
You enter additional heuristics in this heuristic profile that you use especially in the
production planning table or in the order view.
Features
• Strategy settings
Depending on the heuristic, you can change the selected strategy settings that the
heuristic uses to schedule or reschedule operations. Certain strategy settings are
permanently set by SAP and cannot be changed.
• Planning Period
The system uses heuristics to reschedule operations that start in the planning period.
Activities
• If you want to start a heuristic in the DS planning board, select the desired object and
call up the heuristic by choosing Functions → Heuristics. You can change the settings for
the heuristics in the DS planning board by choosing Settings → Heuristics.
• If you want to use a heuristic in the production planning run, enter the heuristic and the
object for which you want to execute the heuristic in the corresponding processing step in
the production planning run.
Schedule Deallocated Operations

Use
Using this heuristic [Page 207], you can schedule selected deallocated [Page 412] operations
again in the production planning run [Page 122] and in the DS planning board [Page 362].
This heuristic uses the function module /SAPAPO/HEUR_DISPATCH.
For further information regarding prerequisites and activities for using the Detailed Scheduling
heuristics, see Detailed Scheduling heuristics [Page 413].

Lead Time Reduction

Use
Using this heuristic [Page 207], you can reduce the lead time [External] for orders in the
production planning run [Page 122] and in the DS planning board [Page 362] that have
operations at selected resources.
The system fixes [Page 418] the selected resources and thereby all the operations that are
scheduled at these resources. Starting at each fixed operation, the system schedules the
other operations from the affected order in such a way that the smallest possible time
intervals between the operations from that order are achieved.
This heuristic uses the function module /SAPAPO/HEUR_REDUCE_LEADTIME.
Backlog Rescheduling
Use
You can use this heuristic [Page 207] to reschedule the backlog in the production planning
run [Page 122] and in the DS planning board [Page 362]; that is, you can automatically
reschedule the operations that lie in the past in the planning period [Page 85] to the current
date or in the future.
Features
The current date and current time is the default for the earliest possible start date for the
operations to be rescheduled. With the help of the offset time in the heuristic settings, you can
shift the earliest possible start date into the past or into the future.
This heuristic uses the function module /SAPAPO/HEUR_RESOLVE_BACKLOG.
For more information regarding prerequisites and activities for using the detailed scheduling
heuristics, see Detailed scheduling heuristics [Page 413].
Sequencing
Use
Using this heuristic [Page 207], you can schedule selected scheduled operations in a
particular sequence in the production planning run [Page 122] and in the DS planning board
[Page 362].
This heuristic uses the function module /SAPAPO/HEUR_PLAN_SEQUENCE.
Activities
You specify the scheduling sequence in the heuristic settings. When you start the heuristic for
the selected operations, the system deallocates these operations and then schedules them
again one after another in the set sequence.

For more information about prerequisites and activities for using the detailed scheduling
Manual Sequencing
Use
You can use this heuristic [Page 207] to do the following in the DS planning board [Page 362]:
• Create a scheduling sequence of your choice for a group of selected scheduled
operations
• Subsequently schedule the operations in this sequence
You create the sequence of operations manually on a graphical list interface when calling up
the heuristic.
Due to the fact that you create the operation sequence manually when calling up
the heuristic, you cannot use this heuristic in the production planning run [Page
122].
Features
The list interface in divided into two sections, between which you can shift operations using
Drag&Drop. In one of the sections, you create the list of operations to be rescheduled in the
desired sequence. You can use the other section as a work area and a temporary store for
operations. You can also put the operations in this section that are not to be rescheduled.
When you have created the operation list, you can start rescheduling. You define the
rescheduling strategy settings in the heuristic settings.
This heuristic uses the function module /SAPAPO/HEUR_PLAN_SEQUENCE_MAN.
Merging orders on container resources

Use
You can use this heuristic [Page 207] to merge planned orders you have selected in the DS
planning board [Page 362].
The system increases the order quantity of an existing order to the sum of all selected
individual orders and deletes the other selected orders. All of the pegging relationships are
transferred to the merged order.
This heuristic uses the function module /SAPAPO/HEUR_MERGE_ORDERS.
Prerequisites
Before orders can be merged, the following prerequisites must be met:
• All orders must reference the same production process model
• All orders must be planned orders
• All orders must be synchronized, that is, the start and end times of the orders must be the
same.

• All orders must be scheduled at a multi resource with storage characteristics

• Synchronization must be activated in the master data of the resource
Planning Heuristics in Repetitive Manufacturing (REM

Heuristics)
Use
Heuristics [External] serve to solve specific problems within the area of production planning
and detailed scheduling.
For planning production in repetitive manufacturing, SAP provides two basic heuristics
(REM heuristics; REM = Repetitive Manufacturing). You can change the settings for these
heuristics in Customizing, or use them as a template for programming heuristics with your
own algorithm (see Setting Up REM Heuristics [Page 224] Create REM Heuristics with your
own Algorithm [Page 225] ).
The SAP standard REM heuristics are particularly suitable for planning non-configurable
products that are to be produced on simply structured lines (such as filling lines). With
these heuristics you can plan several resources (in repetitive manufacturing with PPM) or
lines (in REM with iPPE: resources of type line) simultaneously. In this way you can produce
products on alternative resources (lines), and load them as you wish within finite planning.
For planning configurable products, a special planning run is available within

model mix planning with a special heuristic. For further information see Model Mix
Planning Run [Page 150].
Integration
You can use the REM heuristics the following scenarios:
• Repetitive Manufacturing with the Production Process Model (PPM) [External].
• Repetitive Manufacturing with Integrated Product & Process Engineering (iPPE)
[External]
The heuristics can be used both in interactive planning and background planning.
Prerequisites
• The products that you want to plan are not configurable.
• The structure of your repetitive manufacturing is very simple with only one operation per
resource. If there are several operations per resource, the system takes the last operation
as the basis for scheduling.
Complex iPPE line networks cannot be planned with these REM heuristics. With
line networks that consist of several lines, the system always plans the last line.
• The products that you want to plan within a planning run with a specific REM heuristic are
on the same low-level code and you plan the bill of material structure sequentially from
top to bottom.

You cannot plan final products and dependent assemblies at the same time. If
you plan the finished products, the dependent requirements for the assemblies
can only be taken into account in a subsequent heuristic run.
• You have maintained the necessary master data.
Features
The following REM heuristics are contained in the SAP scope of delivery:
• Heuristic for Multi-Resource Planning (Even) [Page 219] (SAP_REM_001).
In this heuristic, the resources are loaded as evenly as possible.
• Heuristic for Multi-Resource Planning (Primary Resource) [Page 219] (SAP_REM_002).
In this heuristic, resources that are defined as primary resources (the preferred
resource) are loaded first of all. Planned orders are not moved to the alternative
resources until these resources are at full capacity.
Both SAP REM heuristics initially carry out the net requirements calculation, then calculate
the lot sizes according to the settings in the product master and finally create scheduled APO
planned orders for the available requirements, taking into account the free resource capacity
available per period. Depending on your settings, the periods could be daily, weekly, or
monthly. User-defined time periods are also possible.
To determine the requirement quantities and dates for the necessary components, the REM
heuristics then carry out a single-level individual explosion of the iPPE data, or the production
process model and thus determine the dependent requirements for the BOM level directly
below.
The heuristics only work with firm setup times and do not take into account
sequence-dependent setup, as defined in the setup matrix of the production
process model.
Activities
You can start the planning run with REM heuristics in the following applications:
• In the product planning table: Select the resource you want to plan, display the view
Heuristics (or choose Variable heuristic, or in the menu Planning →=Heuristic), select
the heuristic you want, make any other settings for the heuristic and start the planning
run.
• In the production planning run: Enter the heuristics you want and the resources to be
planned, save your entries in a variant and plan the variant as desired. The planning run
is then automatically started as a regular background job.
• In other applications of interactive planning (detailed scheduling planning board, product
view).
See also:
Production planning run [Page 122]
Heuristics [Page 207] .

Heuristic for Multi-Resource Planning (Even)

Purpose
You use the heuristic multi-resource planning (even)
(/SAPAPO/REM_HEUR_TEMPLATE), if you produce several products in repetitive
manufacturing from the same resources (lines) and prefer one specific resource because of
costs, or other reasons.
This heuristic is deliberately kept simple and does not take into account
parameters in the planning algorithm such as the planning time fence and the
production horizon. Also, it does not provide for any splitting of lots.
Therefore, you should use this heuristic primarily as a template for
programming heuristics with your own algorithm. Do not use it unchanged in
your operative planning.
For further information on adjusting the heuristic, see Setting Up REM Heuristics
[Page 224] and Create REM Heuristics with your own Algorithm [Page 225] .
Prerequisites
See Planning Heuristics in Repetitive Manufacturing (REM Heuristics) [Page 217] .
Process Flow
When using this heuristic, the system tries to distribute the planned orders across all the
resources as evenly as possible. If there are no resources available for a period, the planned
orders are moved to free resources in the previous period. If no free resources have been
found for remaining requirements before the order start date, even in the previous periods, a
planned order is not created, resulting in a shortage.
The procedure runs as follows:
1. The system determines the load of all resources to be planned per period. The load is
calculated from the firm operations that are assigned to the resources.
2. The system looks in the resource with the least load for a lot, which could be produced on
the resource, and checks whether the capacity of this lot fits in the current period.
3. If it does, it makes a scheduling proposal for this lot and loads the resource. If not, it
checks whether the lot could be produced in one of the previous periods.
4. Lots that cannot be completely produced in any period, are not scheduled.
Heuristic for Multi-Resource Planning (Primary

Resource)
Purpose
You use the heuristic multi-resource planning (primary resource)
(/SAPAPO/REM_HEUR_WAVE), if you produce several products in repetitive manufacturing
from the same resources (lines) and prefer one specific resource because of costs, or other
reasons. This resource is then the primary resource.
In the settings for the heuristic you can determine the criteria the system should use to
determine the primary resource. The criteria can be either the priority of the session [External]
(when using the PPM ) or the production rate [External] (when using iPPE).

Prerequisites
See Planning Heuristics in Repetitive Manufacturing (REM Heuristics) [Page 217] .
Process Flow
When using this heuristic, the system first of all tries to load the primary resource and then the
alternative resources to full capacity. Because of the wavelike calculation, the planning
algorithm of this heuristic is also known as a wave algorithm.
The planning takes place in three steps:
1. Finite backward scheduling, starting from the end of the planning period (backward
wave).
The lots with requirements dates in the last period are initially dispatched to the
primary resource of the corresponding product. If the primary resource is fully loaded,
remaining lots are divided across alternative resources. If, in the last period, the
alternative resources are also fully loaded, surplus lots are put at the resources of the
previous period. In this way the lots with the earliest requirements dates are moved
first.
2. Finite forward scheduling starting from the beginning of the planning period (forward
wave).
This step applies to lots that the system could not schedule finitely in the first step.
The process is the same as in step 1: the lots whose requirements dates are in the
first period, are dispatched to the primary resource of the corresponding product. If
the primary resource is fully loaded, remaining lots are divided across alternative
resources. If, in the first period, the alternative resources are also fully loaded, surplus
lots are put at the resources of the following period. In this way the lots with the latest
requirements dates are moved first. There are two options for moving lots, depending
on your settings. The system either looks for the next gap, or it moves surplus lots to
the next period.
3. Finite or infinite scheduling of the remaining lots
The step concerns lots that the system could not schedule finitely even in the second
step. That is, there is no available capacity for them in the planning period.
Depending on the settings, these lots can be scheduled finitely or infinitely at the end
of the planning period, scheduled infinitely at the beginning of the planning period, or
not scheduled at all.
There are two alert situations:
− Finite scheduling at the end of the planning period can result in delays.
− Infinite scheduling at the end or at the beginning of the planning period results in
capacity overload, sometimes with delays.
− If scheduling does not take place at all, this can result in a shortage, sometimes with
delays.
Example for Multi-Resource Planning with Primary

Resource
Scenario
For a period of five weeks (W1 to W5) there are weekly requirements for two products.

Product 1 (P1, displayed light) can be produced on resources R1 and R2; the primary
resource is R1.
Product 2 (P1, displayed dark) can be produced on resources R2 and R3; the primary
resource is R2. On each resource a maximum of 100 pieces can be produced per week.
Step-by-step planning
1. The system creates planned orders for the requirements for P1 and P2 from the
corresponding primary resources R1 and R2. This causes overloading on both
resources in W5 and W1.
This is the situation after the normal MRP run in the R/3 System, that is a
planning run using the infinite capacities.
300
W1 W2 W3 W4 W5
260
250
250 230
190
200
150
100 80 80 80
50
40
50 30
0
R1 R2 R3 R1 R2 R3 R1 R2 R3 R1 R2 R3 R1 R2 R3
2. Backward wave: In W5 the system distributes planned orders for P2 to the alternative
resource R3, until this is at full capacity. In this way the overloading in R1 and R2 in W5 is
partially reduced.
W1 W2 W3 W4 W5
300
260
250
250
190
200
150 130
100
100 80 80 80
50
40
50 30
0 0 0 0
0
3. The system divides the remaining overload from R1 and R2 from W5 to the primary
resources in the previous week, that is W4. The resulting overload on R1 in W4 is moved
to the secondary resource R3. In W5, all resources are now at full capacity, in W4, R1 is
at fully capacity, R2 at 80% capacity and R3 at 70%. In W3 and W2, the situation is not
critical. In W1, there is an overload on R1 and R2, which have to be reduced.
300
W1 W2 W3 W4 W5
260
250
250
200
150
100 100 100 100
100 80 80 80
70
40
50 30
0 0 0 0
0
4. Forward wave: In W1 the system divides planned orders for P2 to the alternative
resource R3, until this is at full capacity. In this way the overloading in R1 and R2 in W1 is
partially reduced.

300
W1 W2 W3 W4 W5
250
250
200
160
150
100 100 100 100 100
100 80 80 80
70
40
50 30
0 0
0
5. The system divides the remaining overload from R1 and R2 from W1 to the primary
resources in the following week, that is W2. The resulting overload on R1 in W2 is moved
to the secondary resource R3 and to the primary resource R1 in W3. In this way, you
reach a balanced situation, with the load on the primary resources.
300
W1 W2 W3 W4 W5
250
200
150
100 100 100 100 100 100 100 100 100 100
100 80 80
70
60
50
0
0
Example for the Planning Run with REM Heuristics

Scenario
You produce three different types of soda: orange, lime, and blackcurrant flavor. These
products are represented in the diagram as orange, green, and purple triangles.
Each soda consists of the bottle with a label (square) and the actual drink (circle). The soda
drink itself (circle) consists of the raw material (a non-variable part) and the corresponding
flavoring (squares). The bottle, raw material, and flavoring are procured externally.
There are two resources available for filling the bottles (‘final assembly’): resource 1 and
resource 2. Orange and purple soda can only be filled from one resource, however the green
soda can be filled on both.
For creating the actual soda from the raw material and flavoring (‘pre-assembly’) there are
two other resources available: resource 3 and resource 4. Orange and purple soda can only
be produced from one resource, however the green soda can be produced on both.
You have determined requirements for your three products, using an R/3 System, for
example, or using the application components DP/SNP in APO, and now you want to plan the
products.

Plant 1
R/3, DP/SNP ...
Requirements
Soda with Soda with Soda with

orange flavor lime flavor blackcurrent flavor
Final assembly: bottle filling Pre-assembly: producing the liquid
Res. 1 Res. 3 Resources
Res. 2 Res. 4
Soda
Bottle Liquid Products
Raw material Flavoring

(non-variable
part)
Step-by-step planning
1. Resources 1 and 2 in the final assembly are the critical bottleneck resources that you
should plan particularly carefully. In addition, you want to make sure that when the green
soda is filled, resource 1 is loaded first of all, because this resource is the most
economical. Therefore you plan the finished products (triangles) using the heuristic Multi-
resource planning with primary resource (SAP_REM_002).
2. Pre-assembly planning is not critical, as far as capacity is concerned. In addition, when
producing the green soda, there is no difference between resources 3 and 4. Therefore
you plan the assembly (circle) using the heuristic Multi-resource planning (even)
(SAP_REM_001).
3. The raw materials that are procured externally (squares) are planned at the end with an
MRP heuristic, such as the heuristic Product planning run according to low-level codes
(SAP_MRP_001).
Step
Step1:
1: Planning
Planningthe
thefinal
finalassembly
assembly
Plant 1 Heuristic:
Heuristic:e.g.
e.g.SAP_REM_002
SAP_REM_002
Selection:
Selection:res.
res.11++res.
res.22
Step
Step2:
2:Planning
Planningthe
thepre-assembly
pre-assembly
Heuristic: e.g. SAP_REM_001
Heuristic: e.g. SAP_REM_001
Final assembly Pre-assembly Selection:
Selection:res.
res.33++res.
res.44
Res. 1 Res. 3
Step
Step3:
3:MRP
MRP
Heuristic:
Heuristic:e.g.
e.g.SAP_MRP_001
SAP_MRP_001
Res. 2 Res. 4 Selection:
Selection:Raw
Rawmaterials
materialswith
with
planning
planningfile
fileentry
entry

Setting Up REM Heuristics

Both of the REM basic heuristics consist of three function modules. The first and the third
function modules are responsible for the preparation and follow-up of the heuristic run and are
therefore identical in both heuristics. The second module describes the actual heuristic run
and contains the planning algorithm; this module is different in both heuristics.
Function group /SAPAPO/PT_HEUR_REM
Grouping the required data:

SAP Standard
/SAPAPO/COLLECT_DATA_REM_HEUR
Resources or iPPE lines, products, locations,

planning period, heuristic parameters,
requirements, receipts
Heuristic:
Planning algorithm: /SAPAPO/REM_HEUR_TEMPLATE
/SAPAPO/REM_PLAN_TEMPLATE or or /SAPAPO/REM_HEUR_WAVE
/SAPAPO/REM_PLAN_WAVE
or customer-specific function
module
New planned orders
Posting the orders in the liveCache: SAP Standard

/SAPAPO/CREATE_SCHED_REM_HEUR
Module /SAPAPO/COLLECT_DATA_REM_HEUR
This module collects the master data and movement data necessary for repetitive
manufacturing, and transmits this to the module, which contains the planning algorithm.
If the heuristic starts with the resources, the system first of all determines all products that can
be produced on the specified resources. Then it checks whether the products can also be
produced using other, unspecified resources. If other products can be produced on these
additional resources, it checks whether these products can be produced in other resources. It
repeats this process until a closed quantity of resources and products to be planned is
defined.
The heuristics can also start with the products. When determining the scope of
planning, the system proceeds in the same way.
Then the system determines the master data and transaction data necessary for the REM
heuristics, for the resources and product/location combinations. This can be, for example,
production process model, rate, requirements, stocks, receipts, resource schedule and so on.
If you want to program a heuristic with your own algorithm, you can copy this module directly,
without changing it.
Module /SAPAPO/REM_PLAN_TEMPLATE (multi-resource planning even) or

/SAPAPO/REM_PLAN_WAVE (multi-resource planning with primary resource)
This module contains the actual planning algorithm; you can copy it and adjust it to match
your requirements.

The module /SAPAPO/REM_PLAN_WAVE is relatively complex; only use it as a

template it you have sufficient experience with SAP Systems. The module
/SAPAPO/REM_PLAN_TEMPLATE on the other hand, is deliberately simple and
can act as a template for programming your own algorithm.
Module /SAPAPO/CREATE_SCHED_REM_HEUR
This module updates the results of the planning run in the liveCache, that is, it creates,
changes or deletes planned orders.
First of all, the system deletes all orders, which were already available before the planning run
with the REM heuristic, and which were not firmed. It then updates the schedule proposal for
orders to be scheduled finitely. It then updates the schedule proposal for orders not to be
scheduled finitely.
If you want to program a heuristic with your own algorithm, you can also copy this module
directly, without changing it.
For exact technical information see the online documentation on the individual
function modules.
Create REM Heuristics with your Own Algorithm

Use
You can define REM heuristics, which you use as a basis for your own planning algorithm.
You then integrate this in the APO System, so that they are available in the production
planning run and in interactive planning. In this way you can enter your specific planning
requirements.
Procedure
1. For general instructions on creating heuristics with your own algorithm, see Creating
Heuristics Using Your Own Algorithm [Page 226]. Follow the procedure described there.
2. Copy the REM heuristic function module /SAPAPO/REM_HEUR_TEMPLATE (multi-
resource planning even) or /SAPAPO/REM_HEUR_WAVE (multi-resource planning with
primary resource) and insert it in the function group that you copied in step 11.
3. Replace the middle part of the REM heuristic function module (containing the planning
algorithm) with your own function module. You can find out the various options for
programming, in the original function module /SAPAPO/REM_PLAN_TEMPLATE or
/SAPAPO/REM_PLAN_WAVE.
The module /SAPAPO/REM_PLAN_WAVE is relatively complex; only use it as a

template it you have sufficient experience with SAP Systems. The module
/SAPAPO/REM_PLAN_TEMPLATE on the other hand, is deliberately simple and
can act as a template for programming your own algorithm.

Creating Heuristics Using Your Own Algorithm

Use
You can define heuristics based on your algorithms and integrate these into the APO System.
This allows you to program algorithms that specifically address your planning needs. You can
then execute your own heuristics in the production planning run and during interactive
planning.
Your own heuristics are an enhancement of the SAP planning process.

Please note that even small changes or enhancements to the planning process
can lead to unexpected planning results. Any changes or enhancements you
make are at your own risk.
SAP cannot be held responsible for any defects or malfunctions resulting from
changes or enhancements to the software.
Procedure
1. Copy the function group /SAPAPO/RRP_HEUR_TEMPLATE under a new name. This is
to be used as a main program for the subscreen in which you can maintain settings for
the heuristic. A dialog box appears in which the function module that are to be copied are
listed. Copy and rename the following:
− Function module for the algorithm /SAPAPO/HEU_TEMPLATE
− Get function module /SAPAPO/HEU_TEMPLATE_DATAGET (used to read the
output structure for the screen)
− Set function module /SAPAPO/HEU_TEMPLATE_DATASET (used to fill the output
structure for the screen)
2. Create an output structure for the subscreen in the ABAP Dictionary. You can use the
structure /SAPAPO/HEU_TEMPLATE_D1000_STR as a template.
3. Replace the name of the template output structure with your output structure name
everywhere this appears in the function group, for example, in the
− Top include
− Set function module
− Get function module
− Subscreen 1000
4. Use the subscreen 1000 for the maintenance of the heuristic settings.
5. The structure /SAPAPO/HEUR_SETTINGS contains the tables in which the settings for
the heuristics are stored on the database. Use one of the existing tables or create your
own include structure in the table /SAPAPO/HEURCUST.
6. Modify the set function module to ensure that the relevant settings stored in the structure
/SAPAPO/HEUR_SETTINGS are copied into the corresponding fields of the output
structure for the subscreen.
7. Modify the get function module to ensure that the fields of the output structure are copied
into the corresponding fields of the structure /SAPAPO/HEUR_SETTINGS.
8. Program the algorithm function module.
The interface consists of importing and exporting parameters.
Importing parameters include:
− Relevant settings /SAPAPO/HEUR_SETTINGS

− Planning version. You must ensure that this data is transferred to the liveCache.
− Simulation version. You must ensure that this data is transferred to the liveCache.
− The structure /SAPAPO/HEUR_OBJECT_KEYS. This structure contains the tables
with the planning objects (resources, line networks, products, orders and operations)
Exporting parameters include:
− (E_CHANGED_OBJECTS). This updates the objects in the main program.
− (E_OBJECT_KEYS). This is used during background planning to transfer the objects
from one processing step to another.
For an example of how algorithms are programmed, see the algorithm for the
standard heuristic SAP001 Standard lot-sizing heuristic.
9. To integrate the heuristic into the APO System and the production planning run, enter the
following objects in the table /SAPAPO/HEURFUNC:
− The function module for the planning algorithm
− Function group
− The subscreen
− The set function module
− The get function module
In the table /SAPAPO/HEURFUNC, you must also define where the heuristic may be
executed, for example, in the production planning run or in the DS planning board,
and for which objects it can be executed, for example, for products, resources, or
operations.
10. Create a heuristic in Customizing for Production Planning and Detailed Scheduling based
on the algorithm you have defined. For more information on defining heuristics, see
Customizing for Production Planning and Detailed Scheduling.
Optimization
Use
You can use the optimization to optimize the production date and the resource allocation
[Page 72] for operations, based on the following criteria:
• Total lead time [External]
• Setup times [Page 230]
• Setup costs [Page 230]
• Delay costs [Page 231]
• Mode costs [Page 230]
The optimization determines a schedule for scheduling in the optimization range [Page 236] in
which a result as close as possible to the desired result, for example, the minimum setup
time, is achieved. To do this, the system varies the start dates and the resource allocation for
the operations. You can also execute campaign optimization [Page 232] in the optimization.
You can execute a simulative optimization and adopt the optimized schedule into the
operative planning version.

Integration
The optimization is integrated into the following applications:
• Detailed Scheduling planning board [Page 237]
• Production planning run [Page 122]
You execute the optimization interactively in the planning board and planning table, and in the
background for the production planning run.
If you have called up the optimization in the DS planning board or in the product planning
table, the system adopts the optimized schedule into the current simulative schedule when
the optimization has finished. If you execute the optimization in the production planning run or
in the DS planning board, you can elect to save the planning results either as a simulation
version or in the planning version.
Prerequisites
• The master data for optimization is maintained in Customizing for Basic settings (for
example, the network connections to the optimization server and the maximum number of
users).
• You have defined your own optimization profile for the following cases:
− You want to work with your own presettings for the optimization
− You want to execute the optimization with changed capacities for multi-resources
[External]
Features
Optimization principle
The optimization evaluates a schedule; that is, it evaluates the dates, the resource allocation
and the sequence of activities, based on the objective function [Page 229]. The objective
function is the sum of various weighted time and costs that are especially critical for
scheduling. During optimization, the system tries to reduce the value of the objective function;
that is, it tries to find a schedule in which the various times and costs − according to their
weighting − are as low as possible. In general, it is not possible to fulfill all the scheduling
objectives to the same extent. For example, a reduction in the setup time could lead to an
increase in the total lead time.
Optimization procedure
How suitable an optimization procedure is in finding a good solution, depends on the
scheduling problem. You can choose between the following optimization procedures:
• Constraint propagation
This procedure is suitable for complex scheduling problems in which many
interdependencies and constraints have to be considered, and where it is difficult for
the planner, for example, to find a feasible solution by scheduling interactively in the
DS planning board.
• Genetic algorithm
This procedure is suitable for scheduling problems in which the planner is faced with
the problem of finding a very good solution, and not just a feasible one. A typical use
for this procedure is in establishing an optimal sequence based on the setup of
operations.
Which optimization procedure and which weighting of optimization criteria you use to obtain
good solutions, is dependent on the scheduling situation and the organizational goals. You

decide on the quality of the solutions by setting the processing time for the optimization. The
rules of thumb are as follows:
• The more time you have, the better the solution will be
• The more extensive and complex the problem is, the more time you require
Constraints for the optimization

During optimization, the system considers the various constraints [Page 234] in the schedule.
In doing this, it is necessary to differentiate between hard constraints, which the system
must adhere to, and soft constraints, which the system tries to adhere to, but which the
system violates if necessary in order to find a solution that complies with the hard constraints.
The working time for a resource is, for example, a hard constraint: The system is only allowed
to schedule activities in working times. Requirement dates from sales orders are soft
constraints. The system is also allowed to schedule receipts after the requirement date.
These delays can, however, be minimized during optimization.
Earliest start date for the optimized schedule

Before the optimization, you specify the earliest date on which the optimization function can
schedule the activities. You cannot enter an earliest start date that lies in the past.
Objective Function
Definition
A function of variables that are relevant to planning which is minimized during the optimization
[Page 227].
Use
Based on the objective function, the system evaluates the schedule during optimization in the
optimization range [Page 236], that is, the dates, the resource allocation [Page 72] and the
sequence of activities. The objective function for the PP/DS optimization is the sum of the
following weighted time and costs that reflect the central scheduling problems for production
planning:
• Total lead time [External]
• Sum of the setup times [Page 230]
• Sum of the setup costs [Page 230]
• Sum of the delay costs [Page 231]
• Sum of the mode costs [Page 230]
The weighting that you apply to the various times or costs when defining the objective
function reflect the importance of each problem for your schedule. For example, if a very
important scheduling objective of yours is to have low setup costs, you weight the setup costs
in the objective function particularly highly. During optimization, the system tries to minimize
the objective function; that is, it tries to find a schedule in which the various times and costs −
according to their weighting − are as low as possible. Due to the fact that the various
scheduling objectives generally compete with one another, it is often not possible to achieve
all of the objectives to the same extent. For example, a reduction in the setup time can lead to
an increase in the total lead time [External].

Optimization of Setup Times and Setup Costs

Use
With the optimization [Page 227], you can optimize the schedule for single resources
[External] based on the sum of the setup times and sum of the setup costs. The system
determines setup times and setup costs that are dependent on sequence from the setup
matrix [Page 77].
Prerequisites
• You modeled the single resources and the operations that are processed at these
resources in exactly the same way as for the setup time adjustment [Page 77].
• You strongly weighted the setup times or the setup costs in the objective function [Page
229].
Features
In the objective function, the system interprets the values for the setup times and setup costs
from the setup matrix as follows:
• You enter the setup time in a unit of your choice (for example, hours or minutes) in the
setup matrix. The system uses the setup duration in seconds in the objective function. If
you enter, for example, a setup duration of 10 minutes in the setup matrix, the system
uses the value of 600 (seconds) in the objective function.
• You enter the setup costs without unit of measurement in the setup matrix. In the
objective function, the system uses directly the value entered in the setup matrix. If you
enter, for example, setup costs with a value of 10 in the setup matrix, the system uses the
value of 10 (seconds) in the objective function.
In the objective function, the setup costs with a value of 10 correspond to a setup duration of
10 seconds. You must consider this relationship between setup times and setup costs when
defining the objective function, that is, when specifying the weighting for the setup times and
the setup costs.
Optimization of Mode Costs

You can use the optimization [Page 227] to optimize the schedule according to the sum of the
mode costs for the activities. The mode costs for an activity are the costs that are incurred
when executing an activity in a particular mode [Page 73]; they are calculated as follows from
the fixed and variable costs:
Mode costs = Fixed costs + Variable costs x Duration of activity
You maintain the fixed and variable costs depending on the mode priority [Page 75]; as the
priority decreases, the costs must either increase or remain the same. The system uses the
activity duration in seconds for calculating the mode costs.
In order to reduce the costs for an activity, the system can choose a mode with lower costs for
the activity during optimization; that is, it reschedules the activity to an alternative primary
resource with lower costs and to the corresponding secondary resources.

Prerequisites
• You defined the fixed and variable costs depending on the mode priority in the
optimization profile or when calling up the optimization on the Costs tab page. If you do
not enter any mode costs, the system uses the system default value.
• You strongly weighted the mode costs in the objective function [Page 229].
Optimization of Delay Costs

Use
You can use the optimization [Page 227] to optimize the schedule according to the costs that
are associated with the delayed completion of orders or activities. The following optimization
criteria are available:
• The sum of the delay costs in the optimization horizon
• The maximum delay costs for a single order or a single activity
A delay occurs when:
• A receipt date is later than a requirement date [Page 239]
• The latest allowable start or finish date for an activity [Page 241] is before the actual start
or finish date
How much the delay of a single order or activity costs depends on the order priority and the
duration of the delay; this is calculated as follows:
Delay costs = Costs dependent on priority x Duration of delay
You maintain the priority-dependent costs depending on the order priority; as the priority
decreases, the costs must either decrease or stay the same. The order priority can be
specified by the sales order, the planned requirement or - depending on the product - by the
product master. You specify – depending on the planning version – in the Model and Version
Management where an order obtains its priority from. An activity inherits the priority from the
order. The system uses the duration of the delay in seconds for calculating the delay costs.
During optimization, in order to reduce delay costs, the system tries to schedule orders and
activities that have a high priority with the smallest possible delay (if necessary, at the
expense of orders and activities with lower priority for which greater delays are not so crucial).
Prerequisites
• You defined the priority-dependent costs depending on the order priority in the
optimization profile or when calling up the optimization on the Costs tab page. If you do
not enter any costs, the system uses the system default value.
• You strongly weighted the delay costs in the objective function [Page 229].
Features
When a receipt delivers several requirements with a delay, the system uses the biggest delay
for this receipt for one of the requirements.

Campaign Optimization
Use
You can also execute campaign optimization for bottleneck resources during optimization
[Page 227]. During campaign optimization, the system optimizes the duration and sequence
of campaigns with respect to the following optimization criteria:
− Sum of the earliness costs [Page 233]
− Sum of the delay costs [Page 231]
− Sum of the setup times [Page 230]
− Sum of the setup costs [Page 230]
Campaign optimization is possible for orders that only contain one operation that is processed
at a bottleneck resource. Already existing campaigns can be retained, extended or dissolved
during campaign optimization.
Following campaign optimization, the system optimizes the overall schedule while retaining
the optimized campaigns.
Prerequisites
• The production process models are modeled as follows:
− A production process model is only allowed to contain one operation that is
processed at a bottleneck resource.
You define a resource as a bottleneck resource by setting the Bottleneck

resource indicator for the resource in resource maintenance.
− The bottleneck resource must be the primary resource for the mode [Page 73].
− In the alternative modes for processing the operation, the primary resource must also
be a bottleneck resource.
• You have defined a campaign profile.
In the campaign profile, you specify the following:
− The maximum campaign duration (maximum number of charges in a campaign)
− The position of a setup and clean-out order in a campaign
Before optimizing, the system deletes the setup and clean-out orders in the
optimization range [Page 236], that is, it deletes the orders you have specified as
being at the beginning or at the end in interactive campaign planning. The system
only creates setup and clean-out orders again after optimization if you have
specified in the campaign profile that these orders are to be at the beginning or
end of the campaign.
You define the campaign profiles specific to the setup group and location in
Customizing for Production Planning and Detailed Scheduling. The position of a
setup and clean-out order is valid for a single client.
• If the system should create setup and clean-out orders after optimization, you must have
specified production process models (PPMs) for the setup transitions in the setup matrix.
The system is to use these PPMs to generate the orders. A PPM for setup and clean-out
may only contain operations that have one processing activity at the most.
• You have made the following settings on the Additional strategies and Basic settings tabs
in the optimization profile or while calling up optimization:
− You have set the Campaign optimization indicator

− You have defined the weighting for the objective function for the campaign
optimization
− You have specified how the already existing campaigns have to be handled during
the campaign optimization (retain, extend, dissolve)
− You have defined the weighting for the objective function for the optimization of the
overall schedule
• You have defined the optimization range as follows:
− The complete set of alternative bottleneck resources must be contained in the
resource selection for the optimization
− No other bottleneck resources are allowed to be contained in the resource selection
Activities
The system executes campaign optimization as follows:
1. The system deletes the setup and cleaning orders in the optimization horizon. The orders
for which you have specified a position at the start or end of the campaign in interactive
campaign scheduling are handled by the system as setup and cleaning orders.
2. If you specified in the optimization profile that the existing campaigns are to be dissolved,
the system dissolves the existing campaigns.
3. The system creates optimal campaigns at the bottleneck resources. As required, the
system either retains existing campaigns, or extends them.
The system varies the start dates and the resource assignments for the operations
during campaign optimization. It chooses between the alternative bottleneck
resources that are allowed to process the operation. The operations at the non-
bottleneck resources are scheduled infinitely.
4. The system optimizes the overall schedule. To do this, it uses the objective function for
the overall schedule. The operations at non-bottleneck resources are now scheduled
finitely.
5. If you have specified in the campaign profile that a setup and clean-out order are to be at
the beginning or end of a campaign, the system creates a setup and clean-out order. It
uses the production process model that you entered in the setup matrix for the setup
transition to do this.
Optimization of Earliness Costs

Use
In the campaign optimization [Page 232], you can optimize the schedule according to the
storage costs that are associated with the early completion of orders or activities.
Earliness occurs when:
• A receipt date is earlier than a requirement date [Page 239]
• The actual start or finish date for an activity is before the latest allowable start or finish
date for an activity [Page 241]
How much the early completion of a single order or a single activity costs, depends on the
duration of the earliness and the storage costs for the order product. This is calculated as
follows:
Earliness costs = Duration of earliness x Storage costs

You define the storage costs in the product master (per base unit of measure and day). The
system uses the duration of earliness in seconds for calculating the earliness costs.
It is important to consider that the earliness costs are independent of the quantity
produced.
Prerequisites
You strongly weighted the earliness costs in the objective function [Page 229] for the
campaign optimization.
Features
When a receipt delivers several requirements too early, the system uses the earliest delivery
for this receipt for one of the requirements.
Constraints for the Optimization

Use
During optimization [Page 227], the system considers the various constraints in the schedule.
In doing this, it is necessary to differentiate between hard constraints, which the system
must adhere to, and soft constraints, which the system tries to adhere to, but which the
system violates if necessary in order to find a solution that complies with the hard constraints.
The working time for a resource is, for example, a hard constraint: During the
optimization, the system is therefore only allowed to schedule activities in working
times. Requirement dates from sales orders are soft constraints. Therefore, the
system is also allowed to schedule receipts after the requirement date. These
delays [Page 231] can, however, be minimized during optimization.
Features
The constraints related to various scheduling objects are listed in the following tables.
Resources
Scheduling data Constraint Description

Working and non-working times Hard The system can only schedule activities in
working times during the optimization.
Rate of resource utilization Hard
[External]

Capacity Hard The system schedules finitely [External] during

optimization.
For the multi resources [External], you can
specify in the optimization profile a capacity on a
periodic basis that is different from the one
specified in the master data. When optimizing,
the system loads the multi resource up to the
value of the capacity defined in the optimization
profile. You can, for example, define reduced
capacities, thereby reserving capacity in the
optimized schedule for last minute special
orders.
Orders

Validity of the production Hard The system can only reschedule orders in such a
process model (PPM) or the way that the order lies within the validity period
iPPE for the PPM or iPPE.
Pegging relationship [Page 36]

From a receipt element to a Hard The system must schedule the receipt element
non-fixed requirement element punctually, that is, before the requirement
element.
From a receipt element to a Soft The fixed requirement element defines a
fixed requirement element (for requirement date. Receipt dates are allowed to
example, a sales order) be later. The delays [Page 231] can be
minimized during optimization.
Fixed pegging relationship Hard The system retains the assignment of the receipt
[Page 36] element to the requirement element. The system
processes the fixed pegging relationships in
exactly the same way as the dynamic pegging
relationships.
Time relationship between activities [Page 241]

Between two non- Hard The system is not allowed to violate the
fixed activities relationship; that is, the interval must
not be smaller than the minimum and
the maximum interval must not be
exceeded.
Between a fixed The relationship Hard A relationship between a fixed and a
and a non-fixed defines an earliest non-fixed activity defines an earliest
activity start or finish date start or finish date or a latest start or
for the non-fixed finish date for the non-fixed activity.
activity.
As a default, the latest start or finish
dates for the optimization are a soft
constraint. The non-fixed activity may,
therefore, be scheduled late. However,
optimizing the delay costs can minimize
delays.
You can specify that the system
considers the latest start or finish dates
to be hard constraints, and is therefore
not allowed to violate them.
The relationship Soft (Default)

defines a latest start
Hard
or finish date for the
non-fixed activity.
The optimization does not consider the scheduling parameters in the resources,
and the detailed scheduling strategies [Page 82].
Optimization Range
Definition
A range for which the system optimizes the schedule during optimization [Page 227]. The
optimization range is defined by the following:
• The optimization horizon [External]
• The resources that are transferred to the optimization
Use
During optimization, the system can only change the schedule within the optimization range;
that is, it can only reschedule activities that:
• Lie entirely within the optimization horizon
• Are at the resources that are transferred to the optimization
In particular, the system can only reschedule an activity to alternative resources [Page 72]
during optimization when these resources are included in the resource selection for the
optimization.
During optimization, the system does not change the schedule outside of the optimization
range. Activities outside of the optimization range are therefore fixed during optimization.
However, the fixed activities determine by their relationships to the non-fixed activities in the
optimization range, whether and how far these activities can be rescheduled during
optimization. The optimized schedule is, therefore, adjusted to accommodate the fixed
activities.
Additional activities within the optimization horizon can be fixed [Page 237] for the
optimization.

Fixing Activities, Operations and Orders

Use
Activities, operations and orders can be fixed during optimization [Page 227]. The system
does not reschedule fixed objects during optimization. However, the fixed objects determine
by their time relationships [Page 241] or pegging relationships [Page 239] whether, and by
how far, these objects can be shifted during optimization. The optimized schedule is,
therefore, adjusted to accommodate the fixed objects.
• The following objects are always fixed:
− Activities that are do not lie, or only partially lie, within the optimization range [Page
236]
− Started, partially confirmed or finally confirmed operations
− Operations that you fixed [Page 418] in the production planning run or in the DS
planning board
− Sales orders
• You can fix the following objects for the optimization as required:
− Selected order types (for example, in-house production orders or external
procurement orders)
− Orders that only lie partially in the optimization range
− Released orders
− Orders that contain fixed, started, partially confirmed or finally confirmed operations
You enter the corresponding settings when calling up the optimization, or in the
optimization profile on the Order processing tab page.
Calling Up the Optimization in the DS Planning Board

Use
You can call up the optimization [Page 227] in the DS planning board and optimize the
schedule for the current simulation version.
Prerequisites
• The master data for optimization is maintained in Customizing for Basic settings (for
example, the network connections to the optimization server and the maximum number of
users).
• If you want to work with your own presettings for the optimization, or if you want to
execute the optimization with changed capacities for multi-resources [External], you have
defined your own optimization profile and entered it in the appropriate place. The
appropriate place is dependent on where you call up the DS planning board [Page 383]
(for example, directly or in order processing). If you do not enter an optimization profile,
the system uses a standard optimization profile.
Procedure
1. Select the resources in the DS planning board that you want to transfer to the
optimization.

If you do not select any resources, the system automatically transfers particular
resources to the optimization, depending on where you called up the DS planning
board. For example, in the directly called-up DS planning board, the system transfers
the resources that you specified in the work area [Page 371] to the optimization.
2. Choose Optimize.
3. Enter the following data:
Data Description
Start and end date for the optimization horizon The system optimizes the schedule for this
time period during the optimization run.
Earliest start date for the optimized resource The system schedules the activities no earlier
load than this date.
4. Choose Optimize.
The PP/DS Optimizer screen appears.
5. If you want to display the list of resources transferred to the optimization, choose Display
resource list.
6. You can change the settings for the optimization as required (for example, the
optimization criteria or the run time for the optimization run) by choosing Display settings.
7. To start the optimization run, choose Start optimization run.
Result
The system executes the optimization.
While the optimization is running, the progress of the values for the individual optimization
criteria is displayed graphically. Another screen section displays the messages created by the
system regarding the network or the optimization.
After the optimization run has ended, you can start a new optimization run as required, with
changed optimization settings. When you return to the DS planning board, the system adopts
the result of the optimization run that was executed last into the simulation version of the DS
planning board.
You can use the Plan Monitor [External] to compare the results of various
optimization runs.
Optimization Run
Prerequisites
You started the optimization run interactively (for example, in the DS planning board [Page
237]) or in the production planning run [Page 122].

Process
1. The system executes pegging [Page 239] and converts the pegging relationships that lie
partially or completely within the optimization range into time relationships or
requirements dates. This provides hard or soft constraints [Page 234] for the optimization;
that is, it limits the possible scheduling dates.
2. The system evaluates the time relationships between the activities [Page 241]. (Time
relationships are defined in the production process model or in the iPPE.) Relationships
between activities that are not fixed [Page 237] represent hard constraints for the
optimization. The system converts the relationships to fixed activities [Page 241] into
earliest and latest start and finish dates for the non-fixed activities. The earliest dates
represent hard constraints for the optimization. You can specify for the latest dates
whether they are hard or soft constraints.
3. Optional: The system executes a consistency check [Page 239] for the master data.
4. The system optimizes the schedule in the optimization range [Page 236] based on the
specified objective function [Page 229], hereby considering all the constraints [Page 234].
To do this, it varies the dates and the resource allocation [Page 72] for the activities.
Optional: In the optimization, the system can execute a campaign optimization [Page
232] with a special objective function.
5. Optional: The system executes a follow-up optimization [Page 241] in which it tries to
schedule the activities that were scheduled too early closer to the requirement dates.
6. The system saves the optimized schedule either in the planning version (production
planning run [Page 122]) or in the simulation version (production planning run, DS
planning board [Page 237]), depending on where you started the optimization.
Consistency Check
Use
Optionally, the system executes a consistency check in the optimization run for the data
transferred to the optimization, before the actual optimization is executed. During this check,
for example, the system checks the master data for incorrect settings. For performance
reasons, you should only use this check if you are in the implementation phase and are
configuring the master data.
Activities
If you do not want to execute the consistency check, you set the Skip data consistency check
indicator on the Enhanced settings tab page in the optimization profile, or when calling up the
optimization.
Process Pegging Relationships

Purpose
This process describes how the system does the following at the start of the optimization run:
• Executes pegging [Page 36]

• Converts the pegging relationships into relationships between receipt elements [External]
and requirement elements, or into requirement dates for receipt elements ("due dates").
The relationships and the requirement dates represent hard and soft constraints [Page 234]
respectively for the optimization, and based on these, the system must schedule receipt
elements on time, or it can minimize the delays for receipt elements [Page 231].
Prerequisites
The optimization run has started.
Process
1. The system executes "normal" pegging; that is, the area in which the system creates
dynamic pegging relationships is not limited to the optimization range [Page 236]. The
system uses the pegging parameters from the product master. Fixed pegging
relationships remain unchanged.
2. The system deletes the dynamic pegging relationships that lie completely within the
optimization range.
3. The system creates new dynamic pegging relationships for the receipt and requirement
elements that lie within the optimization range. In doing so, the system can execute
backward scheduling. As a default during backward scheduling, the system can link a
requirement element to a receipt element that is up to 24 hours late. You can enter
another value in the optimization profile or when calling up the optimization. The value set
for backward pegging in the product master is not relevant for the optimization.
4. The system converts the pegging relationships that are partially or completely in the
optimization range either into requirement dates for the receipt elements or into
relationships between receipt elements and requirement elements as follows:
− Pegging relationship to a fixed requirement element
A pegging relationship between a receipt element and a fixed requirement
element [Page 237] (for example, a sales order or an input node for an activity
outside of the optimization range) defines a requirement date for the receipt
element. The requirement date is a soft constraint [Page 234] for the optimization
that the system is allowed to violate. Therefore, the system is also allowed to
schedule the receipt element after the requirement date. However, these delays
[Page 231] can be minimized during optimization.
− Pegging relationship to a non-fixed requirement element
The system converts a pegging relationship between a receipt element and a
non-fixed requirement element into a relationship between the receipt element
and a requirement element. This relationship is a hard constraint [Page 234];
during the optimization, it forces the receipt element to be scheduled on time; that
is, the receipt date cannot be later than the requirement date. Therefore, the
system eliminates, if necessary, the delay of a receipt element for a non-fixed
requirement element.
• Based on the pegging relationships, the system can avoid or minimize delays during
optimization. Shortages cannot usually be eliminated due to the fact that during
optimization, the system only evaluates the pegging relationships that were created
before the optimization.
• The newly created pegging relationships are only valid for the optimization. After adopting
the optimized schedule into the planning version, the system creates, if necessary, new
pegging relationships.

Process Time Relationships

Use
A relationship with a minimum or maximum time interval can exist between two activities.
(You define time relationships in the production process model or in the iPPE.) At the start of
the optimization run, the system evaluates the relationships between the activities and then
determines the possible scheduling dates for the activities.
• Relationship between two non-fixed activities
During optimization, the system must always adhere to the relationship between two
non-fixed [Page 237] activities; they represent a hard constraint [Page 234]. The
system is not allowed to drop below the minimum interval, and the maximum interval
must not be exceeded.
• Relationship between a fixed and a non-fixed activity
Using the relationship between a non-fixed activity and a fixed activity, the system
determines the earliest or the latest start or finish dates for the non-fixed activity.
These dates represent hard or soft constraints for the optimization as follows:
− Earliest start or finish dates are a hard constraint for the optimization.
− As a default, latest start or finish dates are soft constraints [Page 234] that the system
is allowed to violate. These delays [Page 231] can be minimized during optimization.
If required, you can specify that the system also considers the latest dates as hard
constraints.
The following table provides a summary of the dates defined by a relationship to a
fixed activity. The relationship goes from the first activity to the second.
The first activity The second activity The activities are linked The relationship
is: is: by a relationship with defines the
the following: following:
Fixed Non-fixed Maximum interval Latest start or
finish date
Fixed Non-fixed Minimum interval Earliest start or
finish date
Non-fixed Fixed Maximum interval Earliest start or
finish date
Non-fixed Fixed Minimum interval Latest start or
finish date
Follow-Up Optimization
Use
During optimization [Page 227], the system tends to schedule activities earlier than the
requirement date. In order to correct this early scheduling, the system can automatically
execute a follow-up optimization in the optimization run after the actual optimization has
finished. During the follow-up optimization, the system tries to schedule the activities that

were scheduled too early closer to the requirement date. This corresponds to backward
scheduling.
Prerequisites
If the system is to execute a follow-up optimization, you must enter the following settings in
the optimization profile or when calling up the optimization:
• Set the Backward scheduling indicator on the tab page Additional strategies
• Specify whether, during the follow-up optimization, the system can change the resource
allocation [Page 73] established during optimization, or whether it must stay the same.
• Specify whether, during the follow-up optimization, the system can increase the total lead
time [External] achieved during optimization
Multi-Agent Optimization
Use
The multi-agent optimization is available so that you can optimize in parallel on one
optimization server with several processors. During multi-agent optimization, the system uses
all the processors in parallel for the optimization; it can execute the optimization on each
processor using a different (user-defined) objective function. Each "agent" optimizes the
same given scheduling problem with "its" objective function [Page 229]. The agents do not,
however, execute the optimization independently of one another; they communicate the
solutions that they reach in each optimization step to each other, and exchange the good
interim solutions. (Due to this synergy effect, you cannot replace the multi-agent optimization
by executing the optimization in parallel using appropriate weightings for various simulation
versions.)
Multi-agent optimization offers you the following advantages:
• You reach a high quality solution in a short time The increase in speed relates
approximately to the number of processors
• Your ability to make decisions regarding the selection of solutions increases; you can
compensate for the uncertainty in the definition of the objective function by using several
objective functions. For the same scheduling problem, you get several alternative
solutions of equal overall quality, but with varying evaluations for the sub-objectives (for
example, delays or setup times).
You must weight the individual sub-objectives in the overall objective function
when optimizing several objectives in Production Planning and Detailed
Scheduling. In general, the weighting is not based on business costs, but reflects
preferences. Therefore, there is a degree of uncertainty in the weighting. For
example, if you weight delays against setup times with a ratio of 1:2, an increase
of 20 minutes in the delay can be compensated by a reduction of 10 minutes in
the setup times. In the event that the possible solutions in the following table are
found during optimization, the system only provides the best solution (A).
However, the alternative solutions B or C, whose values are only marginally
worse, could be of interest to you.
Solution Delay Setup time Value of objective

function
A 4000 0 4000
B 2001 1000 4001

C 0 2002 4004
Delays, setup times and objective function values are all in minutes.
Prerequisites
• You have maintained the settings for the parallel optimization.
You enter the settings for the parallel optimization in Customizing for Basic settings
under Optimization → Basic functions.
• You have set the objective function for the agents.
You specify the objective functions via optimization profiles that you enter in the
optimization profile or on the Multi-agent optimization tab page when calling up the
optimization.
APO Optimization Extension Workbench (APX)

Purpose
Nowadays, optimization plays a key role in supply chain management. Effective optimization
tools, which can be adapted to suit the needs of their respective users, have a significant
influence on planning and production efficiency and thus represent a critical factor on the
market.
The standard optimization facility in the Advanced Planner and Optimizer (SAP APO) allows
you to access optimization tools at various points:
• In strategic planning, when the entire supply chain is built (Component Network Design
[External]).
• In tactical medium and long-term planning (Supply Network Planning [External])
• In operative production planning (Production Planning and Detailed Scheduling
[External])
• In transportation planning (Transportation Planning [External] and Vehicle Scheduling
[External])
The components listed here optimize generic target figures, i.e. parameters such as
production costs or lead times, which are of general interest to every company.
Important statistics for individual enterprises or sectors of industry in particular are not taken
into consideration here. For example, geometrical or technological constraints could be
important for optimizing the sequence of operations on a machine. These can include criteria
such as dimensions, weights, temperatures, etc. The most important optimization criteria
include minimum waste and maximum machine utilization. These specific constraints and
target figures are not taken into account by standard optimizers.
Integration
The APO Optimization Extension Workbench (APX) provides a new means of making
optimization strategies more flexible. The primary purpose of the workbench is to extend the
standard planning tools in SAP APO to include user-specific optimization components. These
individual optimizers are launched directly from APO. Together with the standard optimizers

and heuristics, they form one planning system. This system provides the right degree of
flexibility to be adapted to the precise needs of the user.
In addition to the functional integration of the external optimizer in the standard APO
component environment, the optimizer is to be incorporated closely so that it can freely use
the APO data stock (from the liveCache and the database server). The results of an
optimization can then be returned to the APO data stock. This means that a separate
database is not required. The connection is realized using BAPI technology.
The constraints and target figures that are so user specific that they cannot be handled by
standard optimizers require figures that are not contained in the standard APO data stock.
The APO database, therefore, can be extended. You can create or populate new tables. This
data is also accessed using BAPI technology.
In this way, external optimizers can be made an integral component of the APO system. As
with the other APO components, they are called from APO, access the APO data stock, and
then save their results to the data stock again.
See Example: Cutting Optimization [Page 250]
Features
The integration of external optimizers in SAP APO is independent of the individual
components. The applications for tactical planning (Supply Network Planning, Transportation
Planning, etc.) and operational planning (Production Planning and Detailed Scheduling,
Vehicle Scheduling) are affected in the same way.
These components, in turn, feature four different planning options:
Standard Heuristics
Standard heuristics are a means of instantly creating a working plan, i.e. one that
takes the specified APO constraints into account. Since the system is to produce a
result as quickly as possible, local optimization criteria are primarily used instead of
global ones. These are implemented in ABAP.
Standard Optimizers
Optimizers enhance the results calculated by the heuristics. Global optimization
criteria, such as the total manufacturing time, the total setup costs, or the average
delay, are used for this purpose. The planning, itself, takes place in the background.
Depending on the extent of the problem, this make take from a few minutes up to a
few hours. Since optimization algorithms usually have extensive runtimes due to their
complexity, they are implemented in C++.
User-Specific Heuristics
Naturally, users can develop their own heuristics and adapt them to their specific
problem. As with standard heuristics, this is done in the ABAP programming
environment.
User-Specific Optimizers
The APO Optimization Extension Workbench provides the option of integrating user-
specific optimization algorithms in SAP APO
SAP APO allows you to integrate these different planning algorithms in one planning system
to fulfill all of the customer's requirements. The algorithms can be started in any order and the
planning problem can be processed entirely or just in part (depending on the relevant
resources / locations and time period). The potential planning scenarios, in turn, can be
adapted here to each individual user.
See Example: Sequence Optimization [Page 245]

Sequence Optimization
The following simplified example from the steel industry is intended to illustrate a potential
planning scenario.
Slabs (blocks of unrolled steel) from the steel works are first rolled in a hot rolling mill to form
sheet steel with a thickness of a few millimeters. This sheet steel can be treated (for example,
anodized, galvanized, coated) in subsequent steps. Although the hot rolling mill can
theoretically process orders in any sequence, system wear and tear can be reduced
considerably if certain constraints are taken into account. A special sequence optimizer,
which is integrated in APO by means of the Optimization Extension Workbench, is used to
determine the ideal order sequence.
One of these constraints is that change in the width and thickness of the rolled sheet steel
between one rolling operation and the next should be as small as possible. The width of the
sheet-steel plates should first increase and then decrease gradually. The thickness of the
plates is subject to fluctuations that should be avoided as far as possible.
The individual width and thickness fluctuations are totaled in an objective function. The best
sequence is the one in which the objective function has the lowest result. If, in addition to the
total fluctuations in thickness and width, different weightings are to be used that can be
modified by the user, the result can be changed with regard to one of the constraints.
1. Production planning for the entire plant can thus be carried out in a number of ways
(scenarios): With backward scheduling, starting from the sales orders, the operations are
first scheduled for the last production unit in such a way that the due date is the same as
the delivery date. This ensures that stock is not built up as a result of the product being
completed too early, and that customer satisfaction is not jeopardized due to delays. If the
system continues to plan backwards in this manner, this will result in a series of
operations on the first production unit (hot rolling mill) that usually cause a high level of
wear and tear on the machinery. It is extremely likely that this sequence will not satisfy
the special constraints, which, if fulfilled, would cause a minimum level of wear and tear.
A large number of setup times indicates that worn machine parts are changed frequently.
2. The second scenario is based on a predefined sequence of operations on the hot rolling
mill. These operations can be either derived from the existing sales orders or determined
using step 1.
This sequence will now be changed using the sequence optimizer, while taking into
account the additional constraints (that is, the minimum level of wear and tear on the
machinery). Forwards planning carried out afterwards ensures that subsequent
operations are scheduled in accordance with the relevant relationships or pegging
relationships. The operations are scheduled for the other resources in accordance with
the sequence of operations in the hot rolling mill. Since the sequence optimizer is not
aware of the position of the last operation in a sales order, the due dates are usually
violated. The products are either completed too early or too late.
The following graphic describes backward scheduling that considers the due dates but on the
other hand violates the sequence constraints

Due dates satisfied

max. customer service & min. inventory
resources
other
hot strip mill

Many setup operations due to incorrect sequence
no min. costs & no max. production
The following graphic describes how the sequence optimizer violates the due dates of the
sales orders in connection with forward scheduling

1.)
resources
other
3.)
hot strip mill
2.)
Due dates not satisfied

no max. customer service (lateness) & no min. inventory
resources
other
hot strip mill
Less setup operations due to optimized sequence

min. costs & max. production
As scenarios 1 and 2 demonstrate, there is a distinct tradeoff between meeting the

customer's deadline, on one hand, and optimizing the sequence of operations in the
hot rolling mill on the other. All of the objectives can be achieved by applying a
combination of both scenarios: First backwards planning is carried out (as in scenario
1). The location of the operations on the hot rolling mill can be regarded as ideal as
far as meeting the due dates is concerned. Every shift in any of these operations to
the left makes it more likely that production for the associated sales order will be
completed too early. Any shift to the right will probably cause production to be
delayed. As far as the due dates are concerned, therefore, as few operations as
possible should be shifted on the hot rolling mill, and, if so, this shift should be
minimal. The total distance of all the operations from their original position can be
regarded as a measure of the "similarity" between the processing sequence specified
by the optimizer and the original sequence.

This measure of similarity is also included in the optimization as a target figure. As

already described above, the objective function is defined as the total of all the
individual weighted target figures. The measure of similarity can be regarded as a
target figure and, therefore, must also be minimized. Once it has been assigned a
weighting, it is included in the total of the remaining target figures, and thus in the
objective function. The weighting is the central element that defines the quality of the
end result. If it is high, there will be little change to the sequence of operations on the
hot rolling mill so as to favor the due dates. If it is low, the sequence, in particular, will
be optimized.
In a further step, the total number of shifts to the left on the planning table (towards
the past) can be distinguished from those to the right. By using different weightings,
shifts to the left or right can be assigned different penalties. Depending on these,
either completion of the sales orders too early or a delay will be permitted. By
changing the weightings, the end result of planning can be modified to accommodate
completion of the sales orders too early, their delay, or a less favorable sequence of
operations on the hot rolling mill.
The operations shifted to the right on the planning table, in particular, can bring about
a violation in the relationships to subsequent operations (for other resources). In
order to correct this and optimize the remainder of the plan at the same time, the
schedule for the remaining resources must be determined with the APO PP/DS
Optimizer. The optimized operation sequence must be fixed in advance. In this way,
the aforementioned violations will be corrected.
The following graphic shows the sequence optimizer under the additional constraint to shift as
few operations as possible. It provides a solution for the conflict between meeting the due
dates and the consideration of the sequence on the hot rolling mill

1.)
resources
other
3.)
hot strip mill
2.)
1.)
resources
other
3.)
hot strip mill
2.)
In short, an optimum production schedule can be calculated with the following

scenario:
a. The heuristic calculates a proposal for system planning.
b. The sequence builder optimizes the sequence of operations on the hot rolling mill,
while taking the total number of changes to the original schedule into account.
c. The standard optimizer corrects any violations to relationships and optimizes the
schedule for the remaining resources.
This example shows how standard heuristics and user-specific optimizers can be combined to
solve a scheduling problem. The procedure illustrated here is typical for many of the problems
associated with sequence optimization. However, there are also other technically-related

tasks involved in optimizing individual systems or entire enterprises in different sectors of

industry. The APO Optimization Extension Workbench can be used in a similar manner to
plan transportation in accordance with certain constraints and objectives, and for planning in
the medium and long term.
Cutting Optimization
Coils (rolls of steel) from a rolling mill with a specific width and length are to be cut to size in
accordance with the customer's specifications. The resulting products are either smaller coils
or sheet-metal plates, which are then delivered to the customer.
The cutting procedure is subject to certain geometrical restrictions: the total width of the coils
or sheet-metal plates must not be greater than the width of the original coils. The same
applies to the lengths. The blanking waste produced is returned to the steel production
process as "scrap".
Whereas the geometrical dimensions "length" and "width" are managed as attributes in
characteristics dependent planning, the special restrictions governing these dimensions are
not known to the detailed scheduling components in APO. This means that they will not be
taken into account and will most likely be violated in standard planning. The objective of
minimizing the amount of blanking waste is also an additional optimization criterion that is
specific to this type of production and is also unknown to standard optimizers.
An external optimizer is required, therefore, to maintain the constraints and minimize blanking
waste. This optimizer can accommodate and correct the incorrect (as far as the additional
constraints are concerned) plan in APO and optimize the blanking waste at the same time.
The modified production plan is then returned to APO. The following graphics show you how
to achieve this by changing the corresponding pegging relations.
The following graphic displays the APO planning result before cutting optimization.
Additional constraint are violated. Large amount of scrap
Customer orders:
Cut Coils (width + length)
Large amount of scrap
1 3 2
5 4
Cutting1 Cutting2 Cutting3
Additional constraints:
z.B.: width(B) ≥ width(2)+width(5)
most probably violated by standard toolscht
A B C
Rolls from rolling mill
The following graphic displays the APO planning result after cutting optimization.

Customer orders:
Cut coils (length + width)
Target 2:
2 Minimize special
1 4 measures
3
5 (Amount of scrap)
Cutting1 Cutting2
Target 1:
Consider additional constraints
A B
Rolls from rolling mill
Access to Data in SAP APO

Use
The APO Optimization Extension Workbench uses "Business Application Programming
Interfaces" (BAPIs) to provide data stored on the database and in the liveCache to external
optimizers. This means that all of the BAPIs provided by SAP APO can also be used by
external optimizers.
BAPIs are based on business objects. Typical business objects in SAP APO include
locations, products, resources, PPMs, and orders of all types. These objects are assigned
methods that allow you to create, read, change, and delete instances of the objects. When
you do so, the system takes into account a series of attributes that describe these instances
in greater detail. How these attributes are assigned to individual fields and structures in the
database or liveCache is not relevant for using the BAPIs. The business object
"ManufacturingOrderAPS" (manufacturing order) is primarily in use at present in conjunction
with the APX. The following methods are used here:
Features
• SaveMultiple
Creates new or changes existing manufacturing orders. Detailed scheduling is then
started automatically, which searches APO for a PPM that can be used here, and
schedules the associated operations and activities, while taking all of the applicable
restrictions into account.
• ChangePeggingMultiple
Creates, changes, or deletes the pegging relationships between the INPUT nodes of
the order and the OUTPUT nodes of a different order or stock. The associated
attributes can also be changed.
• GetList
Determines all of the manufacturing orders that satisfy a specific selection criterion.
Here, the system reads not only the attributes of the order header, but also all of the

input and output products, together with their attribute instances and associated
pegging relationships.
• DeleteMultiple
Deletes one or more manufacturing orders. All of the associated operations and
activities are deleted at the same time.
For further information see User-Specific Data [Page 252].
User-Specific Data
Use
Working with an external optimizer often entails incorporating user-specific data. Since
building a separate (external) database to store this data does not make sense, SAP provides
the option of extending the existing APO databases. There are two ways of doing this:
1. Additional data can be modeled as characteristics of individual products. This is part of
characteristics dependent planning (CDP) in APO. The characteristics are implemented
with the standard APO functionality and can then be interrogated by the external
optimizer using the standard BAPIs.
2. If it is not possible to model additional information as product characteristics, the SAP
APO database structure can be extended. Two procedures can be used here:
a. Existing database tables can be extended by adding new columns. These extensions
primarily affect tables for resources, PPMs, orders, and all other elements that are
assigned business objects. The data stored in these columns can be accessed using
the methods of the relevant business objects. These methods contain ExtensionIn
and ExtensionOut parameters at their interfaces for this purpose. These are actually
containers, which record the individual table extensions and modifications.
b. If the additional information cannot be assigned directly to the business objects, it
must be modeled and stored in separate tables. Whereas creating and managing
these tables is part of SAP Basis (see transactions "se11" and "se16"), access to
their content from an external optimizer is provided by a special APO Optimization
Extension Workbench module.
See example User-Specific Tables [Page 252]
User-Specific Tables
The table „KOMPATIBLE_STAHLTYPEN“ serves as example that additional information cannot
be assigned automatically to business objects. This information has to be modeled and stored
in separate tables.
KOMPATIBLE_STAHLTYPEN
Steel type Compatible Steel Type Degree

of Compatibility
A60 A61 1
A60 A65 1
A60 B82 3

A60 B92 3
A61 A60 1
A61 A65 2
... ... ...
This table describes steel types that are compatible with one another. Assume steel of type
"B82" is being manufactured at a certain furnace in a steel works and a sales order for steel
type "A60" is received. In this case, an optimizer could choose to start a new furnace or to
use the compatible (that is, usually the type with the higher quality) steel type "B82". The
degree of compatibility is also specified.
While the steel type of a product can be modeled as a characteristic, the information
described above can only be mapped effectively in a separate table.
Create and Maintain User-Specific Tables

Use
The names of user-specific tables that are to be used by external optimizers must start with
"YAPX_" or "ZAPX_". In other words, the tables are in the customer namespace and are
assigned to the APX. The tables are created with transaction "se11". The contents of the
tables are created, modified, or deleted with transaction "se16".
Access User-Specific Tables

Use
External optimizers can access tables in the "YAPX_" or "ZAPX_" namespace using the
function module "/SAPAPO/APX_GET_ANY_TABLE". This function module can be called from
Visual Basic, C++, and Java programs by means of a remote function call (RFC).
Procedure
APX_GET_ANY_TABLE only expects the name of the table to be read as an input parameter.
APX_GET_ANY_TABLE
Input Parameter Type Length

TAB_NAME CHAR 30
Result
The output comprises an ABAP structure and three tables. The structure contains general
information on the table to be read:
Result Parameter Type Length
TAB_INFO
TAB_NAME CHAR 30
NUMBER_OF_COLUMNS INT1 3

NUMBER_OF_LINES INT4 10
The first entry simply confirms the table name TAB_NAME, which has already been transferred
as an input parameter. In the following section, «TAB_NAME» refers to the table whose name
is stored in TAB_NAME (in other words, the table to be read). The other parameters specify
the number of columns and rows in «TAB_NAME».
The "TAB_STRUCTURE" table describes the structure of the «TAB_NAME» table, that is, its
fields and the respective field type. This information is available from the ABAP Dictionary.
TAB_STRUCTURE is structured as follows:
Result Parameter Type Length
TAB_STRUCTURE
FIELD_NAME CHAR 30
FIELD_TYPE CHAR 1
FIELD_LENGTH NUMC 6
FIELD_DECIMALS NUMC 6
The FIELD_NAME field contains the field names that were specified in transaction "se11"
when the «TAB_NAME» table was created. FIELD_TYPE is the ABAP data type of the
respective field. The following assignments can arise:
C Character
N Numeric text
D Date: YYYYMMDD
T Time: HHMMSS
X Byte (heXadecimal)
I Integer
P Packed number
F Float
S String
X Byte sequence (X string)
The FIELD_LENGTH and FIELD_DECIMALS fields specify the length and number of decimal
places for the relevant field in the «TAB_NAME» table.
The TAB_CONTENTS table specifies the content of «TAB_NAME». Here, each data record is
copied field by field from «TAB_NAME» to TAB_CONTENTS. Every data record in
TAB_CONTENTS represents a field in «TAB_NAME». The sequence of the data records is
identical to that of the data records in TAB_STRUCTURE.
The TAB_CONTENTS table comprises three fields:
TAB_CONTENTS
Result Parameter Type Length Decimal places

TAB_CONTENTS
STRING_LIKE CHAR 128
FLOAT_LIKE FLTP 16 16
INTEGER_LIKE INT4 10
TO_BE_CONTINUED CHAR 1

The data field type (FIELD_TYPE from TAB_STRUCTURE) determines which field in
TAB_CONTENTS is filled. Packed numbers are transferred as floats. Even integers are not
transformed. All other data is represented as strings.
The only exception is with the transmission of character strings and byte sequences, which
can have an unlimited length in ABAP. If these are longer than 128 bytes, they are split into
one or more parts. In this case, the TO_BE_CONTINUED field is filled with an X. The next data
record of TAB_CONTENTS is then the continuation of the contents of this long data field from
«TAB_NAME». This can be repeated as often as required.
The following section illustrates the content of the transferred data structures using the
example of the KOMPATIBLE_STAHLTYPEN table mentioned above.
The TAB_NAME table has the contents KOMPATIBLE_STAHLTYPEN. Calling
"/SAPAPO/APX_GET_ANY_TABLE", therefore, produces the following results:
TAB_INFO-TAB_NAME = KOMPATIBLE_STAHLTYPEN
TAB_INFO-NUMBER_OF_COLUMNS = 3
TAB_INFO-NUMBER_OF_LINES = 79
KOMPATIBLE_STAHLTYPEN
FIELD_NAME FIELD_TYPE FIELD_LENGTH FIELD_DECIMALS

STAHLTYP C 3 -
KOMPATIBLER_STA C 3 -
HLTYP
Degree of I 2 -
compatibility
N_C_D_T_X_S_x P_F I TO_BE_CONTINUED

A60 - - -
A61 - - -
- - 1 -
A60 - - -
A65 - - -
- - 1 -
A60 - - -
A82 - - -
- - 3 -
... ... ... -

Calling an External Optimizer

Use
You can call external optimizers as well as standard optimization in both the detailed
scheduling planning board [Page 362] and product planning table [Page 324].
Prerequisites
You have defined external optimizers in the Customizing for Optimization under Master data
for the Optimization Extension Workbench.
Procedure
Select an external optimizer when calling up the optimization in the detailed scheduling
planning board [Page 237] or when calling up the optimization in the product planning table
[Page 350].
The GUI of the external optimizer is then displayed.
This window contains the external optimizer GUI within the SAP GUI frame. The
APO Optimization Extension Workbench uses Microsoft's ActiveX technology.
The frame generated by the SAP GUI is an OCX container. Therefore the
developer of the external optimizer must provide an OCX file. The OCX GUI
should allow you to enter parameters for an objective function, such as horizons
or weights. The developer of the external optimizer is entirely responsible for
designing the GUI, controlling the optimization run, and displaying the result (for
example, using the calculated target figures). This also includes the option of
embedding the external optimizer in the OCX. In this case, the optimizer runs on
the workstation. Alternatively, the OCX (in addition to the GUI) can simply control
data exchange between the relevant workstation and a central optimization
server. The results are still to displayed in the SAP APO system in the form of
planning tables or other graphics.
External Procurement
Use
You use APO to plan (for example, due to longer replenishment lead times) critical, externally
procured products, or to gain an overview of the total BOM structure within one system. You
can use planning tools and functions in APO, for example, finite planning of products
(including externally procured products) and heuristics for PO quantity optimization, to help
you plan critical, externally procured materials efficiently.
You can use the purchasing information that is now present in the APO system to improve the
cooperation between plant and vendor. This means that you can, for example, send releases
by email directly to the vendors when you process scheduling agreements, or can allow the
vendor to confirm the releases over the Internet. For more information, see under Scheduling
Agreement Processing Using APO and OLTP Systems [Page 268].
Integration
You can copy the required master data from the connected OLTP system. The orders created
in APO for external procurement can be passed on to the OLTP system to be converted into
purchase orders. This means that the system constantly contains the most current
information.
For more information, see under Converting Orders in APO [Page 467].

Prerequisites
Before you can use the external procurement functions in APO, you can copy the relevant
master data from the OLTP system using the APO Core Interface (CIF):
• Material master records (Created in APO as product master)
• Vendor master records (Created in APO as locations)
• Purchasing info records (Created as External Procurement Relationship [Page 282] in
APO)
• Scheduling agreements (Created as external procurement relationship in APO)
• Contracts (Created as external procurement relationship in APO)
Features
An external procurement order in APO can concern procurement from external vendors, as
well as procurement from another plant. Both vendors and plants are displayed as locations in
APO.
If you want to procure a product externally, you can use Scheduling Agreements [External],
Contracts [External] and Purchasing Info Records [External] from your OLTP system. The
relevant data are made available in your APO system in the form of external procurement
relationships.
The following special forms of procurement are possible in APO:

− Subcontracting [External]
− Consignment [External]
− Stock transfer [External] for stock transport scheduling agreements.
This means that all procurement functions and purchasing information are now available to
you in the APO system. You can also use Quota Arrangements [Page 292] to divide up the
requirements according to your needs.
Another advantage of planning externally procured products in APO, is that you can use
resources in Production Planning and Detailed Scheduling to plan external procurement
orders. This allows you to plan goods receipt, transportation, and goods issue exactly, taking
account of capacities.
You can also trigger conversion of externally procured orders into purchase orders directly in
APO. That is to say, you have complete control over the order in the APO system.
Planning and Source Determination in External

Procurement
Purpose
In APO, you can plan externally procured products in the same interface as products
produced in-house. You can use planning tools and functions in APO, for example finite
planning of products and PO quantity optimization, to help you plan critical, externally
procured materials efficiently. Because you can now also work with scheduling agreements,
contracts, purchasing info records, and quota arrangements in APO, you can make use of all
the procurement functions in Production Planning and Detailed Scheduling.
Planning and production of externally procured products are both carried out in APO. To do
this, you use the materials management component in an OLTP system (for example, an R/3
system) and the procurement functions in an APO system.

The OLTP system used in this process is an R/3 system.
Prerequisites
• SAP R/3 system (as of Release 4.0)
• SAP R/3 system (as of Release 3.0A)
Process Flow
In the diagram below you can see in which systems the different functions are performed,
when a product is planned that is to be externally procured with reference to a contract or
purchasing info record. For information on how to plan scheduling agreements, see under
Scheduling Agreement Processing Using APO and OLTP Systems [Page 268].
Process for Externally Procured Products in an OLTP System and APO
Plant
R/3
R/3 APO
System
Systemcreates
createsexternal
external
Create
CreateContract
Contract/ /Info procurement
Record/Sched.
Info procurementrelationship
relationship(info
(info
Record/Sched.Agreement
Agreement Initial record,
record, contract,OLTP
contract, OLTP
Transfer scheduling agreement)
scheduling agreement)
to APO
Create
CreatePurchase
PurchaseRequisition
Requisition
Convert
ConvertPurchase
PurchaseRequisitions:
Requisitions:
System
Systemsends
sendsaapurchase
purchaseorder
order Convert
Convertor
orTransmit
TransmitPurchase
Purchase
back
back to the APOsystem
to the APO system Requisitions
Requisitions
Generate
GenerateDelivery/
Delivery/ Reduce
ReduceSchedule
ScheduleLines
Lines
Confirmation
Confirmation
Increase
IncreaseStock,
Stock,
Generate Reduce
ReduceDelivery
Deliveryand
andSchedule
GenerateGoods
GoodsReceipt
Receipt Lines
Schedule
Lines
1. You create purchasing info records and outline agreements in the R/3 system.
You enter all scheduling agreements, contracts, and purchasing info records you
want to transfer to APO in the Integration Model [External] for the APO Core Interface
(CIF). These master data are first transmitted during the initial data transfer into the
APO system. Subsequent changes to these master data in the R/3 system are saved
for the next transfer of changes.
2. The APO system generates an External Procurement Relationship [Page 282].
The scheduling agreements, contracts, and purchasing info records transferred by
the R/3 system are created in the APO system as external procurement relationships.
External procurement relationships are product-specific and are assigned to
transportation lanes. Transportation lanes are automatically created in APO when you
transmit data from the R/3 system. The external procurement relationship therefore
contains the contractual details of the relationship between a source location (vendor
or issuing plant) and a target location (plant).

For more information on external procurement relationships, see External

Procurement Relationships [Page 282] and Processing External Procurement
Relationships [Page 285].
3. You create purchase requisitions in APO.
You can create purchase requisitions manually or automatically:
− In APO, you can create purchase requisitions interactively in the Product View [Page
308], Receipt View [Page 312], or the Product Planning Table [Page 324]. During
determination of sources of supply for the order, the system displays the contracts
and purchasing info records defined in the procurement relationship, as well as all
other possible sources of supply. If you select an OLTP scheduling agreement,
contract, or purchasing info record, the system then generates a purchase requisition
for the requested quantity with reference to the corresponding object. The number of
the scheduling agreement, contract, or purchasing info record is displayed on the
Periods tab page in the product view or in the product planning table.
Information on the external procurement relationship is also displayed in the order

view. To display this information, double-click on the number of the
requirement/receipt element in the product view, then select the corresponding
order object under Receipts in the order tree. Choose to display the data in
the external procurement relationship.
If you have defined Quota Arrangements [Page 292] for a product, the vendors
for whom the quota arrangements have been maintained are flagged accordingly
in the Supply Source Determination dialog box. The dialog box also displays
other information on the quota arrangements. The system automatically highlights
the vendor to which the requirements should be assigned. However, you can also
select a different source of supply from the list of permitted procurement
alternatives.
For more information, see Determining Sources of Supply During Interactive
Planning [Page 290].
− During Automatic Planning [Page 119] and during the Production Planning Run [Page
121] , the system automatically generates an order as soon as planning is triggered.
The system selects the procurement alternative that can deliver the goods on time
and according to the priority and costs. If an OLTP scheduling agreement, contract,
or purchasing info record is selected, the system then generates a purchase
requisition with reference to the corresponding object.
If you have defined Quota Arrangements [Page 292] for a product, the system
automatically assigns the requirements to the vendors according to these
maintained quota arrangements.
For more information, see Determining Sources of Supply During Automatic
Planning [Page 288].
4. Convert purchase requisitions.
If you set the conversion indicator for an order in interactive planning, the system
automatically creates a purchase order against this order in the connected OLTP
system.
For more information on converting orders in interactive planning, see Convert
Individual Orders in Interactive Planning [Page 470].
If you use mass conversion for orders, then you can either transfer or convert orders
from a specific period.
During mass conversion of orders, only those orders are selected where the opening
date is in the past.

The opening date is calculated as follows:

Delivery date – Planned delivery date – Opening period
If you select the Convertible orders indicator in the mass conversion function, then
the system creates purchase orders in the OLTP system against all orders where the
opening date is in the past.
If you select the Transferable orders indicator in the mass conversion function, then
the system creates purchase requisitions in the OLTP system against all orders
where the opening date is in the past.
For more information on mass conversion of orders, see Executing Mass Conversion
of Orders [Page 469].
5. Purchase order is generated.
If you have set the conversion indicator for a purchase requisition, then a purchase
order is automatically created in the OLTP system.
If you have not set the conversion indicator for a purchase requisition, then a
purchase requisition is automatically created in the OLTP system that you must then
convert into a purchase order in Purchasing.
The purchase orders have been transferred to the APO system.
6. Create an inbound delivery in the R/3 system.
Create an inbound delivery in the R/3 system. The data from this inbound delivery are
automatically transmitted to the APO system.
7. The APO system reduces the schedule lines.
The schedule lines are subtracted from the notified quantity in APO.
8. Create a goods receipt.
Create a goods receipt in the R/3 system. This goods receipt is automatically
transferred to the APO system.
9. The APO system increases the stock and reduces the schedule lines.
The inbound delivery is reduced by the goods receipt quantity in APO (if you use
APO). The schedule lines are also reduced accordingly.
Scheduling in the Case of External Procurement

Orders
When external procurement orders are created, the activities goods issue, transportation, and
goods receipt are scheduled. Scheduling takes place on the basis of either the planning
calendar (time stream) or the resources. Scheduling takes place via resources if a resource
has been defined for all activities whose duration is greater than zero. If even one resource is
missing, scheduling takes place using the calendar. If there is no calendar either, scheduling
takes place on the basis of calendar days.
If scheduling takes place on the basis of resources, the same scheduling functions that are
also applied in the case of in-house production are used. In this way, limited capacities can be
taken into account in the planning. Each resource has an available time and an available
capacity. Using this information, the system is able to determine the dates and shift the orders
in the course of the planning, taking working times and capacities into account.

If scheduling is carried out using the planning calendar, the activities are fixed so that they are
not shifted into non-working time during the planning. If the relevant order is assigned a new
date, the goods issue, transportation, and goods receipt are rescheduled.
If you use production planning and detailed scheduling, you must work with
resources in order to allow the planning functions the greatest possible freedom.
You can work with infinite resources, but if so you have to maintain at least one
resource calendar.
You should do without scheduling via resources only if you use Supply Network
Planning exclusively.
Process Flow
Scheduling takes place in APO in two steps:
1. Checking the Earliest Availability Date [Page 261]
Prior to the actual scheduling, the system checks the earliest possible availability date
in order to determine a starting date for the scheduling process.
2. Scheduling Taking Resources into Account [Page 262]
After determining the starting date for scheduling (either the desired availability date
or the earliest possible availability date: see Checking the Earliest Availability Date),
the system schedules the activities goods issue, transportation, and goods receipt.
Checking the Earliest Availability Date

When a new order is created, the system calculates the earliest possible availability date and
compares it with the desired date.
The availability date is used as the starting date for the scheduling and is calculated as
follows:
Today’s date + planned delivery time [External] + GR processing time [External]
If the desired availability date for this order lies before the availability date calculated by the
system, the latter uses the calculated date for scheduling purposes – not the desired date.
If the desired availability date is after the calculated availability date, the desired date is used
as the starting date for scheduling.
The planned delivery time is the vendor’s delivery time and comprises the following:
Vendor’s production time + GI processing time + transportation time
In the R/3 System, the planned delivery time is specified in calendar days. In
APO, the planned delivery time is scheduled on the basis of the production
calendar of the vendor location. If no production calendar has been maintained
by the vendor, the planned delivery time is in calendar days, just as in the R/3
System.
You maintain the planned delivery time in your APO system in the external procurement
relationships (contract, scheduling agreement, purchasing info record). If there is no entry
there, or the entry is zero, the system uses the planned delivery time from the product master.
If the date for an order is changed manually, the planned delivery time is no longer taken into
account. Instead, a new scheduling process is triggered. Such a change may result in a
violation of the planned delivery time, so that the opening date is shifted back into the past. In
this case, you are informed accordingly via an alert in the Alert Monitor.

Example
To make photovoltaic modules, you need silicon wafers measuring 15 cm by 15 cm, which
you procure externally from Super Silicon Corp.
On 01.15.2001, an external procurement order for 120 silicon wafers is created. The silicon
wafers are to be available in Production on 01.23.2001.

The APO system calculates the earliest availability date on the basis of the data on the
planned delivery time and GR processing time maintained in the system.
In this example, the planned delivery time amounts to seven days.
Since the silicon wafers delivered must pass through quality control, the GR process takes
another two days.
On the strength of this data, the system gives 01.24.2001 as the earliest availability date for
the silicon wafers.

(Scheduling without considering resources)
GR
Planned Delivery Time

22. te
1
1
01
001
1
day
001
1
01. . date
01. ility
200
200
200
200
200
200
200
200
200
200
01. v. da
ired .20.20
1.2
3.2
- to
26.
27.
16.
17.
18.
19.
24.
25.
28.
aila
iv
i
2
2
l
t de
1
01.
01.
01.
01.
01.
01.
01.
del
01.
01.
01
200
t av
lies
15.
lie s
Ear
Des
01.
E ar
Scheduling Taking Resources into Account

After determining the starting date for scheduling (either the desired date or the earliest
possible availability date: see Checking the Earliest Availability Date [Page 261]), the system
schedules the activities goods issue, transportation, and goods receipt.
In doing so, it checks the capacities of the relevant resources (if necessary, shifting dates
such as the delivery date and the availability date).
Example
To make photovoltaic modules, you need silicon wafers measuring 15 by 15 cm, which you
procure externally from Super Silicon Corp.
On 01.15.2001, an external procurement order for 120 silicon wafers is created. The silicon
wafers are to be available in Production on 01.23.2001. In checking the earliest availability
date, the system determines 01.24.2001 as the starting date for the scheduling process.

Scheduling
The scheduling of goods issue, transportation, and goods receipt provides you with the
following information:
The transportation of the silicon wafers is delayed by one day, since the capacity of the
transport resource on 01.20.2001 is already 100% utilized. The goods receipt cannot be
processed immediately either, because there are no spare quality control resources.
On the basis of the information on the goods issue processing time, transportation time,
goods receipt processing time, resources and resource capacity utilization, the system
calculates 01.28.2001 as the availability date.
Scheduling Taking Resources into Account
Capacity utilization
in % Goods
receipt
Bucket resource
for goods receipt
in % Transport
Bucket resource
for transportation
in % GI
Bucket resource
for goods issue
d ay
20 0 e
1
0 01
1
1
1
01. date
0 1. r y d a t
200
200
200
2 00
2 00
2 00
2 00
200
200
200
2 00
01. date
- To
ired 1.20.2
1 6.
1 7.
2 2.
2 4.
2 5.
2 6.
2 7.
1 8.
1 9.
2 1.
23.
2 8.
iv.
ility
1
01.
01.
01.
01.
01.
01.
01.
01.
01.
eliv
d el
200
la b
l. d
15.
i
Ava
R ea
01 .
Des
Resource Capacity Utilization

You can use the following resource types:
• For goods receipt and issue: Single [External], multi [External], bucket [External], single-
mixed [External], and multi-mixed resource [External]
• For transportation: bucket, single-mix, multi-mix, and transportation resource
If you use Supply Network Planning, you cannot use single and multi resources.
The system uses the following data on activity duration for scheduling purposes:
• Goods issue
The GI processing time is maintained in the location-dependent product master of the
source location.
• Transportation
The transportation time is maintained in the transportation lane for the means of
transport.
• Goods receipt
The GR processing time is maintained in the location-dependent product master of
the source location.

In addition to their respective durations, the goods issue, transportation, and goods receiving
processes can consume bucket capacity.
The system calculates the bucket capacity consumption by reference to the following sources:
• Goods receipt
The system uses the following for its calculations:
− The bucket resource maintained in the master data of the destination location (e.g.
plant) (Handling Resource Inbound field), and
− The bucket capacity consumption specified in the location-dependent product master
of the destination location (Consumption of Handling Capacity Through Goods
Receipt in UoM field).
• Transportation
− The bucket resource maintained in the master data for the means of transport, and
− The bucket capacity consumption specified in the product-dependent means of
transport.
• Goods issue
− The bucket resource maintained in the master data of the source location (e.g.
vendor) (Handling Resource Outbound field), and
− The bucket capacity consumption specified in the location-dependent product master
of the source location (Consumption of Handling Capacity Through Goods Issue in
UoM field).
The bucket capacity consumption, which can be maintained in the product master or in the
transportation lanes, always relates to a base unit of measure. If the available capacity of the
resource has been maintained in a different unit than the base unit of a product (e.g. kg
instead of pc), a suitable conversion factor must be defined in the product master.
For more information, see Resource [External].
Converting Orders in APO

Use
There are several methods available for triggering conversion of planned orders into
production orders, and purchase requisitions into purchase orders in the connected OLTP
system:
• Transfer only for orders with conversion indicator
• Transfer of all PP/DS orders
• No transfer of PP/DS orders
Transfer Only for Orders with Conversion Indicator

Prerequisites
• In Customizing for Production Planning and Detailed Scheduling (PP/DS) under Global
Settings → Maintain Global Parameters and Defaults, you have selected Transfer

Only for Orders with Conversion Indicator for Transmission to OLTP

External Procurement and/or In-House Production.
• You have maintained a planned delivery time in the external procurement relationship.
• You have maintained an opening period for planned orders for each product in the
product master on the PP/DS tab page at location level.
• In Customizing for the Advanced Planner and Optimizer, maintain distribution criteria with
the publication type External Procurement by choosing Basis Settings → Integration →
Publication → Maintain Distribution Definition.
Features
automatically creates a purchase order against this order in the connected OLTP system.
For more information on converting orders in interactive planning, see Convert Individual
Orders in Interactive Planning [Page 470].
If you use mass conversion for orders, then you can either transfer or convert orders from a
specific period.
During mass conversion of orders, only those orders are selected where the opening date is
in the past.

If you select the Convertible orders indicator in the mass conversion function, then the system
creates purchase orders in the OLTP system against all orders where the opening date is in
the past.
If you select the Transferable orders indicator in the mass conversion function, then the
system creates purchase requisitions in the OLTP system against all orders where the
For more information on mass conversion of orders, see Executing Mass Conversion of
Orders [Page 469].
Transfer of All PP/DS Orders

Prerequisites
Settings → Maintain Global Parameters and Defaults, you have selected Transfer of
all PP/DS orders for Transfer to OLTP External Procurement and/or In-House
Production.
Features
All orders from your APO system are always transferred to your OLTP system.
If you have made this setting and there are a large number of orders in your APO
system, this can have a negative impact on performance.

No Transfer of PP/DS Orders

Prerequisites
In Customizing for Production Planning and Detailed Scheduling (PP/DS) under Global
Settings → Maintain Global Parameters and Defaults, you have selected No transfer of
PP/DS orders for Transfer to OLTP External Procurement and/or In-House Production.
Features
No orders are transferred from the APO system to the OLTP system. No orders are converted
to purchase orders or production orders in the latter system.
The setting is useful, for example, if you have not connected an OLTP system to
your APO system.
Executing Mass Conversions of Orders

Use
You can use this function to transfer all planned orders and purchase requisitions where the
opening period is in the past to the OLTP system, or to convert them into production orders
and purchase orders. The opening date is calculated as follows: Delivery date – Planned
delivery date – Opening period.
For a description of how to convert individual orders, see Converting Individual Orders in
Interactive Planning [Page 470].
You have maintained an opening period for planned orders for each product in
the product master on the PP/DS tab page at location level.
Procedure
1. From the SAP Easy Access Menu, choose Production Planning → Manufacturing
Execution → Conversion of Orders/Purchase Requisitions.
The Mass Conversion of Orders in the Active Planning Version screen appears.
2. You can restrict the selection of the orders to be converted using the required selection
criteria.
Selection criteria for mass conversion
Selection Criteria Description

Product Limits the selection to the products you enter.
Location Limits the selection to the locations you enter.
Offset for the opening period Lengthens/Shortens the opening period. Only orders falling within
the opening period are converted and/or transferred.
Select in-house production If you want to convert planned orders into production orders, or to
transfer these to the OLTP system, you must set this indicator.
Production planner You can restrict the selection of planned orders to be converted
and/or transferred that affect a specific planner.

Only fully scheduled orders You must plan all activities for an order. No activities must be
deallocated.
Select external procurement If you want to convert purchase requisitions into purchase orders,
or to transfer these to the OLTP system, you must set this
indicator.
Purchasing group You can restrict the selection of purchase requisitions to be
converted and/or transferred that affect a specific purchasing
group.
Special stock Limits the selection, for example, to one account.
Source Limits the selection to the source locations you enter.
Only firmed orders Only orders whose output is firmed are converted and/or
transferred.
If you do not want to limit the selection, the system processes all orders whose
opening dates are in the past. The opening period is defined for each product in
the product master.
3. Choose .
If you have selected the Display indicator in the Execution options area, the Receipts
screen now appears. The system shows you all the orders that are deemed
convertible and/or transferable according to the selection criteria.
Select the orders that you want to
− convert, and choose Set conversion indicator
− transfer, and choose Transfer orders
If you have set the Immediately indicator in the Execution options area, the system
automatically converts all convertible orders and/or automatically transfers all
transferable orders to the OLTP system.
Result
The system sets a conversion indicator for the convertible purchase requisitions and planned
orders. The orders planned for conversion are transferred to the OLTP system, and are
automatically converted to purchase orders or production orders.
The system transfers the transferable purchase requisitions and planned orders to the
connected OLTP system.
Subcontracting PReqs and purchase requisitions for OLTP scheduling

agreements cannot be automatically converted in the OLTP system.
To convert these purchase orders into purchase orders and/or scheduling
agreement schedule lines, use the Create Purchase Order using Assignment List
function in the OLTP system.
Converting Individual Orders In Interactive Planning

Use

You can directly trigger the conversion of planned orders into production orders and purchase
requisitions into purchase orders on the interactive planning screens of the Product View
[Page 308] and the Product Planning Table. The orders you designate for conversion in the
APO System are sent to the connected OLTP System and are automatically converted there.
Procedure
1. Access the Product View [Page 308] or the Product Planning Table from the SAP Easy
Access Menu by choosing Production Planning → Interactive Production Planning →
Product View or Product Planning Table.
The Product View or the Product Planning Table screen appears.
2. Choose the Individual Elements tab in the Product View or the Product: Individual
Elements view in the Product Planning Table.
3. Select the planned orders and/or purchase requisitions to be converted.
For a purchase requisition to be automatically converted into a purchase order, a

procurement alternative must be assigned to the requisition.
4. Choose Set Conversion Indicator.
The system sets the conversion indicator for the selected orders.
5. Choose to save your planning results.

The orders designated for conversion are transferred to the connected OLTP System,
where the conversion is triggered automatically.
If you create an external procurement order and immediately set the conversion
indicator for this order, the OLTP System automatically creates a purchase order
once you have saved the data. No purchase requisition then exists for this order
in the OLTP system.
If you wish to create a purchase order with reference to a requisition, you must
first save the external procurement order and wait until the requisition data has
been passed on from the OLTP system to the APO system. When this has taken
place, you can set the conversion indicator.
Subcontracting requisitions and purchase requisitions relating to OLTP

scheduling agreements cannot be automatically converted in the OLTP system.
To convert these requisitions into purchase orders or scheduling agreement
delivery schedule lines, use the Create Purchase Order via Assignment List
Scheduling Agreement Processing Using APO and an

OLTP System
Purpose
APO allows you to plan externally procured products in the same planning interface as the
products produced in-house, thereby providing an overview of the complete pegging structure
[Page 303]. Extensive planning functions, such as, finite scheduling of products, purchase
order quantity optimization, and sophisticated planning tools, enable you to effectively plan
critical materials that are procured externally in APO.

Scheduling agreements [Page 272] increase collaboration between the plant and the vendor.
Vendors require shorter lead times as they are better informed on requirement quantities
which allows them to allocate their resources more efficiently.
Scheduling agreement processing in APO is performed using a Materials Management
component of an OLTP System (for example, an R/3 System) and the planning functions of
the APO System.
The OLTP system described in this process is an R/3 System.
Prerequisites
• SAP R/3 System (from Release 4.0)
• SAP APO System (from Release 3.0A)
• You have defined the Leading System is an external system in the Additional data screen
of the scheduling agreement maintenance in the R/3 System and have entered the
scheduling agreements into the integration model [External] of the APO core interface
[External] (CIF) in the Plug-In system
• If you require additional functions when creating scheduling agreement releases, such as,
creation of forecasts/planning delivery schedules, execution of tolerance checks,
definable release horizon, you define a release profile in Customizing for Supply Chain
Planning, under Collaborative Procurement → Maintain Release Profile. You then assign
the release profile to the external procurement relationship.
• You have defined how the releases are to be outputted in Customizing for Supply Chain
Planning, under Collaborative Procurement → Define Message Trigger.
Process Flow
The diagram below shows in which system the various functions are performed during the
complete process.
Scheduling Agreement Processing in an OLTP System and APO
Plant Vendor
R/3
R/3 APO Internet*
System
Systemcreates
createsext.
ext.
Create
Createscheduling
scheduling procurement
procurement
agreement
agreement relationship
Initial relationship
transfer
to APO Display/
Display/
Create
Createschedule
schedule confirm
confirmrelease
release
lines
lines
Releases
Releasesstored
storedinin
scheduling
schedulingagreement
agreement
as
asschedule
schedulelines
lines Create
Createrelease
release
Business
Connector System
Create
Createshipping
shipping Reduce
XM
notification/ Reduceschedule
schedule L
notification/ lines/releases
lines/releases
ED
confirmation
confirmation I
Display
Displayrelease
release
Increase
Increasestock,
stock,
Reduce
Reduceshipping
shipping
Create
Creategoods
goods notification,
notification,
receipt
receipt schedule
schedule
lines/releases
lines/releases

* The Internet option is only possible if you also use the Supplier Workplace. For more
information, see the point 5 below.
1. You create scheduling agreement in the R/3 System
For scheduling agreements to be considered in APO, you must define that the
Leading System is an external system in the maintenance of the scheduling
agreement and enter the scheduling agreements into the integration model [External]
of the APO core interface [External] (CIF) in the Plug-In system. This master data is
transferred to the APO System in an initial data transfer. Changes to scheduling
agreements in the R/3 System are stored for the next incremental data transfer.
2. APO creates an external procurement relationship [Page 282]
The scheduling agreement transferred from the R/3 System is created as an external
procurement relationship in the APO System. The external procurement relationship
is product-specific and is assigned to a transportation lane. The external procurement
relationship thus contains the contractual details of the relationship between a source
location (vendor or plant) and a target location (plant).
You are able to display and maintain the master and transaction data of the
scheduling agreement in the external procurement relationship. This data includes:
− General information, such as procurement type, document number, vendor, and so
on.
− Settings, such as planned delivery time and whether the procurement relationship is
active or inactive.
− Data on the assigned transportation lanes: You are able to directly change the priority
and costs for the transportation lane in the procurement relationship maintenance.
The priority and the costs of the transportation lanes are considered when
determining a source of supply.
− Scheduling agreement data
APO-specific settings include:
• LiveCache update
You can define when the information is to be made available in LiveCache,
for example, when the scheduling agreement releases are created, or when
the releases are outputted.
• Forecast/planning delivery schedule
You can define whether a forecast/planning delivery schedule is to be
created in addition to the operative delivery schedule, and sent to the vendor.
• Internet release [External]
This option if available is you also use the Supplier Workplace to enhance
collaborative procurement. You can define that the scheduling agreement
releases are to be confirmed by the vendor via the internet.
• Release creation profile [External]
You can control how and when scheduling agreements are created by
defining a release creation profile in Customizing for Supply Chain Planning
(under Collaborative Procurement → Maintain Release Profile) and assigning
the release creation profile to a procurement relationship.
• E-Mail address
The scheduling agreement releases are sent in XML format (Extensible
Markup Language) to the address maintained here. If you have not
maintained an address here, the e-mail is sent to the address maintained in
the source location.
Additional functions include:

− Costs
You can display the exact costs for the procurement relationship, that is, fixed
and variable costs for a minimum no. of units.
− Purchase order history
You can display all transactions/events for a scheduling agreement, for example,
goods receipt and invoice receipts.
− Release creation profile [External]
Here you branch into Customizing and can display the release creation profile.
− Release Documentation
You can display the scheduling agreement release that have already been
created for a scheduling agreement item.
3. You create schedule lines in APO
In APO, you can create schedule lines interactively in the Product View [Page 308] or
the Product Planning Table [Page 324]. When determining the source of supply for
the order, the scheduling agreement, in addition to any other possible sources of
supply are displayed. If you select the scheduling agreement, schedule lines are
created for the desired quantities.
During automatic planning [Page 118] and planning during the production planning
run [Page 122], the system automatically creates an order when planning is triggered.
The system selects the procurement option that can supply the goods on time and
according to the priority and costs. If a scheduling agreement is selected, schedule
lines are automatically created.
4. You create scheduling agreement releases in APO
In APO, you can create scheduling agreement releases [Page 275]:
− Interactively in the Product Planning Table [Page 324],
− Interactively in the Period tab of the Product View [Page 308], or
− As a background job.
In Customizing for Supply Chain Planning, under Collaborative Procurement →
Maintain Release Creation Profile [Page 273], you can define how scheduling
agreement releases are to be created, for example, you can define when and how
often releases are to be created, how the release/forecast horizon is to be
determined, and so on.
You are also able to define how the release is to be outputted [Page 278], that is,
whether the releases are outputted immediately (that is, when the releases are
generated), or in the form of a background job. You define this in Customizing for
Supply Chain Planning, under Collaborative Procurement → Define Message Trigger.
You can define that APO is to send a message to the vendor automatically informing
him/her of the scheduling agreement releases as soon as they are created. This is
achieved using IDOCs or XML (Extensible Markup Language) and a business
connector to the vendor's system.
For information on how to display scheduling agreement releases, see Displaying
Scheduling Agreement Releases [Page 277].
5. Vendor displays/confirms releases via the Internet (optional)
You are now able to use the Supplier Workplace (SWP) together with the APO
System and an R/3 System (currently available with Release 4.6C and Automotive
Release 2.0) to further enhance collaborative procurement across the supply chain.
The Supplier Workplace (SWP) allows a vendor to display and confirm scheduling
agreement releases via the Internet.

To be able to confirm scheduling agreements via the Internet, you must set the
Internet Release indicator to 1 for Quantity and date confirmation: Internet
release.
The vendor can view certain information on scheduling agreement, schedule lines,
goods receipt, pricing agreements, and so on, in the customer's system. The quick
and easy access to this information enables the vendor to plan resources more
effectively and helps to strengthen vendor-customer relationships.
For more information see the R/3 documentation in Material Management (MM) -
Supplier Workplace and Internet Release.
6. The releases are stored in the scheduling agreement as schedule lines in the R/3 System
The scheduling agreement releases created in the APO System are transferred to the
R/3 System and are stored in the scheduling agreement as schedule lines.
7. You create shipping notification in the R/3 System
You create a shipping notification in the R/3 System. This is automatically transferred
to the APO System.
8. APO reduces schedule lines/releases
In APO, the schedule lines and scheduling agreement releases are reduced by the
notified quantity.
9. You create goods receipt
You create the good receipt in the R/3 System. The goods receipt is automatically
transferred to the APO System.
10. APO increases stock and reduces schedule lines/releases
In APO, the shipping notification, if used, is reduced by the goods receipt quantity.
The schedule lines and scheduling agreement releases are also reduced accordingly.
Scheduling Agreement
Definition
Outline Agreement [External] against which materials are procured at predefined points in
time over a certain period.
Structure
A scheduling agreement consists of a number of items, for each of which a certain form of
procurement is defined. The following forms of procurement exist:
• Standard
• Consignment
• Stock transfer
The total quantity of the material specified in an item of a scheduling agreement can be split
up into individual quantities that are to be made available by the vendor on different dates
and/or times over a certain period.
You send scheduling agreement (SA) releases (types of delivery schedule) to the vendor to
inform the latter when which quantities are to be delivered. (See Creating Scheduling
Agreement Releases [Page 275] and Outputting Scheduling Agreement Releases [Page
278])

The Release Creation Profile [External] enables you to define the conditions under which
releases issued against a scheduling agreement are generated. You assign a release
creation profile to an item of a scheduling agreement in the external procurement relationship.
(See Release Creation Profile [Page 273])
You can display the releases transmitted to a vendor at any time. (See Displaying Scheduling
Agreement Releases [Page 277])
Scheduling agreements from the R/3 System are represented in the Advanced
Planner and Optimizer (APO) by “external procurement relationships”.
External procurement relationships belong to the Master Data [External] in APO.
In addition to Scheduling Agreements [External], the latter represent other
sources of master data in your APO system such as Purchasing Info Records
[External] and Contracts [External] originating from your OLTP System [External]
(e.g. an R/3 system) and provide all the information necessary for the planning of
material procurement activities. (See External Procurement Relationship [Page
282].)
In APO, a distinction is made between OLTP scheduling agreements and APO scheduling
agreements:
• OLTP Scheduling Agreement
Delivery schedule lines and releases against OLTP scheduling agreements are
generated in the OLTP system.
When you create an external procurement order with reference to an OLTP
scheduling agreement, a purchase requisition is automatically created in your OLTP
system. In the OLTP system, such requisitions are converted into delivery schedule
lines and the relevant SA releases created. The schedule lines are transferred to the
APO system for planning purposes. As soon as inbound deliveries or goods receipts
relating to the SA releases are created in the OLTP system, the relevant data is
transferred to the APO system.
• APO Scheduling Agreement

Delivery schedule lines and releases against APO scheduling agreements are
generated in the APO system.
When you create external procurement orders with reference to an APO scheduling
agreement, delivery schedule lines are automatically created for the relevant
scheduling agreement in the APO system. SA releases are then created in the APO
system. In order that inbound deliveries and goods receipts can be posted in your
OLTP system, the data of the SA release is transferred to the OLTP system and there
converted into SA delivery schedule lines. As soon as inbound deliveries or goods
receipts relating to the SA releases are posted in the OLTP system, the relevant data
is transmitted to the APO system.
Release Creation Profile

Use
The release creation profile is used to specify the following for operative and
forecast/planning delivery schedules:

• How the horizon for the SA releases (delivery schedules) is determined

• How schedule lines from the past are treated in the SA releases
• Which event triggers the release creation process (changes in schedule lines and/or the
advent of the next transmission date)
• Whether a tolerance check is carried out for releases that are created due to changes in
schedule lines
The release creation profile can provide for the following with regard to an
external procurement relationship for a scheduling agreement item:
Your vendor is sent operative delivery schedules on a weekly basis. These
schedules contain lines covering the next three weeks in each case. In addition,
the vendor receives a forecast/planning delivery schedule at the beginning of
each month, which covers the following three months.
If the lines of the scheduling agreement delivery schedule stored in the system
have changed to a significant extent, additional SA releases can be sent to the
vendor.
Features
You can define the following in the release creation profile:
Area You define for each SA release type (operative or F/P schedule):
Layout • Whether backlogs and immediate requirements are to be determined for
the release type
• For which Release Horizon [External] release quantities are shown
Modes of creation • Whether (and if so, under which conditions) an SA release is created
(creation strategy)
Tolerances • Whether a tolerance check is carried out for releases that are created due
to changes in schedule lines You can specify that SA releases are
created only in the event of major changes
You assign the release creation profile to an external procurement relationship for a
scheduling agreement item, thus defining how SA releases are generated for this SA item.
When scheduling agreement data is transferred from your OLTP system to the
APO system via the Core Interface Advanced Planner and Optimizer (CIF) , the
release creation profile is not included in the data transmitted. You must create a
new release creation profile in your APO system and assign to it the external
procurement relationship for the relevant scheduling agreement item.
If you wish to use forecast/planning (F/P) delivery schedules in addition to operative

schedules, you must specify this in the external procurement relationship (Scheduling
agreement with forecast field on the Scheduling Agreement tab page).
Only if you have specified in the external procurement relationship that F/P delivery schedules
are to be created will the settings for F/P schedules from the release creation profile be taken
into account in the SA release creation process.

You wish to provide your vendor not only with data on your concrete short-term
material requirements (via operative delivery schedules) but also with data on
your more tentative longer-term requirements (via forecast/planning schedules).
Therefore, you select the Scheduling agreement with forecast indicator for item
10 of scheduling agreement no. 5500000001 in the external procurement
relationship.
Activities
You define the release creation profile in Customizing for Supply Chain Planning under
Collaborative Procurement → Maintain Release Creation Profile.
You then assign this release creation profile to the external procurement relationship for the
scheduling agreement item on the Scheduling Agreement tab page.
Creating Scheduling Agreement Releases

Use
In the case of scheduling agreements, releases (so-called SA releases) take the form of
delivery schedules. In APO, there are two kinds of delivery schedule issued against
scheduling agreements: the operative schedule and the forecast/planning schedule.
This function allows you to create operative delivery schedules and/or forecast/planning
schedules.
The Release Creation Profile [External] enables you to define the conditions under which
releases issued against a scheduling agreement are generated. You assign a release
creation profile to an item of a scheduling agreement in the external procurement relationship.
Integration
If you wish to work with Internet Releases [External] you must use the Supplier Workplace
(SWP), which your vendors can access via the Internet. Your vendors can display and
acknowledge scheduling agreement releases via the Internet.
If you wish to work with Internet releases, you must specify this for each
scheduling agreement item via the Internet releases indicator on the
Scheduling Agreement tab page in the external procurement relationship.
Please note that the release creation profiles in the R/3 System for the scheduling
agreements concerned must likewise provide for the creation of Internet releases.
(See External Procurement Relationship [Page 282].)
For more information, refer to the MM Supplier Workplace and MM Purchasing
documentation (section Internet Release).
Prerequisites
In the release creation profile, which you maintain in Customizing for Supply Chain Planning
under Collaborative Procurement, you can specify when and how often SA releases are to be
generated.
For more information, refer to the section Release Creation Profile [Page 273].

Features
Creating Scheduling Agreement Releases
You can create operative and forecast/planning delivery schedules. In addition, you can first
carry out a test run to see which SA releases would be created.
You have the option of displaying a detailed log listing all the relevant scheduling agreement
items.
Scheduling Agreement Releases in the Product View and the Product Planning Table
You can also create SA releases for selected schedule lines in the product view, on the
Periods tab page, or in the product planning table.
To do so, the following steps are necessary:
1. Select the desired schedule lines (LP-EIN) and choose .
2. In the subsequent menu, choose Generate operative delivery schedule or Generate
forecast/planning schedule.
You can also display existing SA releases via the menu.

If you enter or change a requirement in the product planning table, choose ENTER. The
system issues a message advising you that the order or schedule line was created
successfully or (if applicable) with a delay.
SA releases are displayed as new orders of the Category [External] LP-ABR or

LP-VOR.
The following categories exist:
• Standard scheduling agreement delivery schedule (LP-EIN)
Quantities generated automatically via the planning run or created manually
by the materials planner that have not yet been transmitted to the vendor.
• Operative delivery schedule (LP-ABR)
Short-term requirements (fixed) transmitted to the vendor which are delivery-
relevant
• Forecast/planning schedule (LP-VOR)
Longer-term requirements (fixed) transmitted to the vendor which are non-
delivery-relevant (i.e. indicative only)
The data of the last transmission is completely replaced by the new data in the
liveCache [External]. In APO, only the operative delivery schedules are needed in
the liveCache: forecast/planning schedules are not needed.
The liveCache contains the following categories: LP-EIN, LP-ABR, and LP-AVI
(shipping notification).
The database additionally contains data on operative and forecast/planning
schedules and acknowledgments.
The PO history contains information on goods and invoices received. Since there should be
no data redundancy in APO viz à viz R/3, it is freshly imported from the R/3 System per
Remote Function Call (RFC) in each case.

Activities
From the menu, choose Supply Chain Collaboration Collaborative Procurement
Scheduling agreement releases Create releases.
Enter the necessary data (e.g. location and product) and choose .
A window appears, showing you:
• How many scheduling agreement items have been selected
• How many operative and/or forecast/planning delivery schedules have been created
If you are using a detailed log, the system will show which scheduling agreement,
which location, which product, and which item were taken into account in the SA
release creation process.
For more information on outputting scheduling agreement releases and how to display
previously outputted releases, refer to the sections Outputting Scheduling Agreement
Releases [Page 278] and Displaying Scheduling Agreement Releases [Page 277].
Displaying Scheduling Agreement Releases

Use
This function enables you to view the final information transmitted (or to be transmitted) to the
vendor in the form of a scheduling agreement (SA) release (a kind of delivery schedule).
You can display simultaneously the SA releases (operative and forecast/planning schedules)
that have been created against several scheduling agreements.
Activities
1. Choose Supply Chain Collaboration Collaborative Procurement Scheduling
agreement releases Display scheduling agreement releases.
In the product view and product planning table, you can display the transmitted
SA releases for the external procurement relationship per scheduling agreement
item. Choose to display scheduling agreement releases.
You can display releases against a scheduling agreement from within the
external procurement relationship. Choose SA releases.
2. Enter the necessary data (e.g. product and location) and choose .
3. You get a list showing all the scheduling agreements that satisfy your selection criteria,
together with the associated SA releases.
This list includes the following data:
− The release quantity (scheduled quantity)
− The Quantity of Goods Received [External], (goods receipt or GR quantity) per
schedule line
− The Cumulative Received Quantity [External]
− The cumulative (total) requested quantity of an SA release
− The time stamp of the scheduling agreement release

− The status of the scheduling agreement release:

SA release newly created; not yet transmitted
SA release already transmitted
Vendor has acknowledged the SA release
4. In the list, you can select two releases and compare them with each other.
Select two releases and choose Compare.
In the window that appears, you see the comparison of the release quantities, the
open quantities and the cumulative quantities.
You can use the graphical display function ( Graphic) to compare more than
two SA releases with each other.
For more information, refer to the sections Creating Scheduling Agreement Releases [Page
275] and Outputting Scheduling Agreement Releases [Page 278].
Outputting Scheduling Agreement Releases

Use
The individual schedule lines of a scheduling agreement release provide the vendor with data
on the quantities to be delivered and required delivery dates over the specified timeframe.
The delivery schedule lines transmitted to the vendor in an SA release can be displayed and
retraced at any time (see Displaying Scheduling Agreement Releases [Page 277]).
You can use this program to transmit scheduling agreement releases to the relevant Source
Locations [External] (e.g. vendors) on a regular basis. You can transmit SA releases to
vendors via e-mail, XML, or the Internet, or in hardcopy form.
Instead of the conventional message control facility, the Post Processing Framework (PPF) is
used, which provides a uniform interface to any output media. SAP Smart Forms are used for
mass printing purposes.
For more information, refer to the Basis documentation (sections Post Processing Framework
(PPF) [External] and SAP Smart Forms (BC-SRV-SCR) [External]).
SA releases can also be outputted from the R/3 System if you are working in APO without
Release Documentation [External], i.e. the creation, transmission (e.g. via a printer) and
administration of the releases is carried out in the R/3 System. You can specify this in the
Additional data for the scheduling agreement via the Ex. planning indicator.
Integration
If you wish to work with Internet Releases [External] you must use the Supplier Workplace
(SWP), which your vendors can access via the Internet. Your vendors can display and
acknowledge scheduling agreement releases via the Internet.
If you wish to work with Internet releases, you must specify this for each
scheduling agreement item via the Internet release indicator on the Scheduling
Agreement tab page in the external procurement relationship.
Please note that the release creation profiles in the R/3 System for the scheduling
agreements concerned must likewise provide for the creation of Internet releases.

(See External Procurement Relationship [Page 282])

For more information, refer to the MM Supplier Workplace and MM Purchasing
documentation (section Internet Release).
Prerequisites
Maintaining the Release Creation Profile
In Customizing for the Advanced Planner and Optimizer (APO) under Supply Chain Planning
Collaborative Procurement Maintain Release Profiles you can maintain a release
creation profile and assign it to the scheduling agreement item in the external procurement
relationship.
Setting the Message Trigger

If you wish to output SA releases using this program, Processing via selection report must be
set as the transmission time-spot (time of dispatch). (Supply Chain Planning Collaborative
Procurement Set Message Triggers).
Furthermore, you can make the following settings for the application Scheduling agreement
release under Trigger type:
• Time of Processing
You can choose between the following processing time-spots:
− Immediate processing
− Processing via selection report
The point in time at which the liveCache is updated should agree with the
processing time-spot for the trigger type.
You define when the liveCache is updated on the Scheduling agreement tab
page in the external procurement relationship.
SAP recommends the following combinations:
Trigger type liveCache
Immediate processing 10 (at the time of release creation)
Processing via selection report 40 (at the time of release output)
• Partner role (VN = vendor)

When you maintain a partner role, the latter must agree with the role in the external
procurement relationship ( Partners tab page) so that triggers are generated.
If several addresses with the partner role VN have been maintained in the external
procurement relationship, for example, a trigger is generated for each address with a
matching partner role. It is also possible to assign different output media to the
addresses. This enables an SA release to be outputted several times (i.e. to different
addresses via different media).
If you have not maintained an output medium in the external procurement
relationship, the medium that has been selected as the Default in Customizing is
used.
The printer is determined from the user parameters. Other printer determination
processes can be implemented via a Business Add-In [External].
• Independently of partners

If you select this indicator, the address number from the location is used if no address
has been maintained in the external procurement relationship.
• Multiple transmission
If you select this indicator, you can re-output already outputted SA releases on the
trigger list.
• Changeable
If you select this indicator, you can change certain data (such as the medium type)
when outputting SA releases (i.e. in the trigger list). Key fields such as the trigger type
or application cannot be changed.
• Trigger merging
If a release is updated even though a not-yet-outputted release already exists,
triggers are merged. This has the effect, for example, that only a single trigger
appears on the trigger list, so that just one release is outputted.
You can use the following media to output scheduling agreement releases:
• XML
• Fax (PPF/smart forms)
• E-mail (PPF/smart forms)
• Printer (PPF/smart forms)
The following settings are possible for the media fax, e-mail, and printer under
Medium Configuration:
Form name: /SAPAPO/SF_SARELEASE_TEMPLATE
Processing class: /SAPAPO/CL_SF_PROC_SARELEASE
Processing method: EXEC_SMART_FORM_SAR
Please note that the smart form is only a template, which you should adjust to suit
your needs. When creating your own forms, you must adopt the interface from
the template.
Features
This program processes triggers selected according to the criteria entered.
Activities
1. Choose Supply Chain Collaboration Collaborative Purchasing Scheduling
agreement releases Create releases.
On the next screen, enter your selection criteria.
2. When selecting scheduling agreements, you can use the application key as a selection
criterion.
Enter Lieferplannummer* in the Application key field (e.g. 5500000221*).
The application key comprises the following:

− Scheduling agreement number

− Item number
− Release type (operative delivery schedule or forecast/planning schedule;
technical values 1, 2 respectively)
− Release number
3. Choose .
The trigger list appears.
There you see the status, indicating whether or not the SA release has been
processed (and if so, whether or not processing was successful).
The following statuses are possible:
Processed.
(That is, the scheduling agreement release has already been outputted but it can
be re-outputted.)
Not yet processed
Incorrectly processed
4. Select the desired SA releases and choose to output operative and forecast/planning
delivery schedules.
You can also send SA releases several times or choose another printer.
The SA release is transmitted to the address in the external procurement relationship.
If no address is recorded there, it is sent to the address in the source location
(address number in source location).
Further functions are available to you on the trigger list:
Preview
If “printout” has been defined for the selected SA release, you can display the
print preview.
Processing log
The processing log is only available in the case of incorrectly processed SA
releases (status Incorrect).
During the outputting of SA releases, the print-dependent data is updated (e.g. the data in the
SA release such as the processing data (time stamp), liveCache (if defined in the external
procurement relationship)).
When displaying scheduling agreements, you see from the status which SA
releases have already been transmitted.
Master Data in Procurement

Definition
Key data for the planning of materials procurement activities.
The following master data is available to you in the Advanced Planner and Optimizer (APO)
for the purposes of external procurement:

• External Procurement Relationship [Page 282]
External Procurement Relationship

Definition
External procurement relationships belong to the Master Data [External] in the Advanced
Planner and Optimizer (APO). In addition to Scheduling Agreements [External], the latter
represent other sources of master data in your APO system such as Purchasing Info Records
[External] and Contracts [External] originating from your OLTP System [External] (e.g. an R/3
system) and provide all the information necessary for the planning of material procurement
activities.
External procurement relationships enable you to do the following:
• Generate delivery schedule lines for an item of a scheduling agreement (APO Scheduling
Agreement [External]) directly within the APO system
• Generate purchase requisitions with reference to a purchasing info record, a contract, or
a scheduling agreement item (OLTP Scheduling Agreement [External]) in yor OLTP
system from within the APO system
The external procurement relationship links the Transportation Lane [External] with
information from your OLTP system:
The transportation lane represents the business relationship between a source location (e.g.
a vendor) and a target location (e.g. a plant).
The external procurement relationship supplements the information of the transportation
lane by creating a link to a specific contract that exists in your OLTP system for the source
and target locations.
External procurement relationships can exist for the following forms of

procurement:
− Standard
− Subcontracting [External]
− Consignment [External]
− Stock Transfer [External] for stock transport scheduling agreements
The product Screw 01 can be procured by your Houston plant from the vendor
Meyer Co. The product is to be procured via a scheduling agreement that already
exists in your R/3 System.
In your APO system, the link between the vendor Meyer Co. (source location)
and your Houston plant (target location) for the product Screw 01 is represented
by a transportation lane. Furthermore, an external procurement relationship
exists, creating a link between this transportation lane and the scheduling
agreement in your R/3 system.

R/3 system (OLTP system)
Scheduling agreement
Vendor: Meyer Co.
Validity:
01.01.2000 - 12.31.2000
Item Material Qty. Plant

10 Screw 01 10,000 CA Houston
APO system
Sched. agmt.
In R/3 System Vendor Meyer Co.
Product
Screw 01
Transportation lane Plant Houston
Ext. procurement relationship Transportation lane
Use
Up to Release 2.0B, only vendors are suggested through the source determination process in
APO.
As of Release 3.0A, the system can also suggest purchasing info records and contract or
scheduling agreement items through the source determination process if you are working with
external procurement relationships in APO.
You create an external procurement relationship in the product view and the
system shows you all the possible sources of supply. If you choose a contract
item at this point, a purchase requisition referencing this item is created in your
OLTP system.
Structure
An external procurement relationship contains the following data:
• General data
The General data includes information on the purchasing info record, contract, or
scheduling agreement (e.g. the procurement category, the logical system, the
document number, the vendor, etc.).
• Settings
Under Settings, you can see which planned delivery time a material has, and whether
the external procurement relationship is active or inactive.
An external procurement relationship is usually deactivated if the purchasing info
record, contract, or scheduling agreement is deleted in the OLTP system. If the
external procurement relationship is inactive, it is no longer taken into account in the
source determination process and no new transportation lanes can be created for it.
• Data on the transportation lane

On the Assigned Transportation Lanes tab page, you can display data on the
transportation lanes and maintain the priority. You can also block and unblock
the assigned transportation lanes on this tab page.
• Scheduling agreement data (only in the case of APO scheduling agreements)
You can display and in some cases maintain the following data on the Scheduling
Agreement tab page:
− Settings
− Movement data
− Delivery data
• Partners (only in the case of APO scheduling agreements)
On the Partners tab page, you can specify:
− The address (e.g. postal address, e-mail address) to which scheduling agreement
releases are to be sent
− The medium (e.g. fax, e-mail) via which scheduling agreement releases are to be
outputted
− Which partner role your vendor assumes (here: source location)
If you have not maintained an address here, the SA release will be sent to the
address maintained in the master data for the source location. The medium and
the partner role are then determined from the default values maintained in
Customizing for Supply Chain Planung under Collaborative Procurement → Set
Message Triggers.
You can also call up additional information by clicking one of the following buttons:
• Costs
This gives you more precise information on the product costs (e.g. scale prices and
their validity periods).
• Release Creation Profile [External] (only in the case of APO scheduling agreements)
This takes you into Customizing, where you can display the release creation profile.
• SA releases (only in the case of APO scheduling agreements)
Here you can display the scheduling agreement releases that have already been
generated for a scheduling agreement item.
• PO history (only in the case of APO scheduling agreements)
Here you can view all the transactions and events that have been recorded for an
item of a scheduling agreement (e.g. receipts of goods and invoices).
Integration
The external procurement relationship is linked directly with the relevant transportation lane
and supplements the information provided by the latter. From the external procurement
relationship, you can also branch directly to the transportation lane in order to maintain
relevant data.
If your OLTP system is an R/3 system, you can transfer purchasing info records, contracts,
and scheduling agreements (and changes thereto) to your APO system via CIF.
For more information on external procurement relationships, refer to Processing an External
Procurement Relationship [Page 285].

Processing an External Procurement Relationship

Use
The External Procurement Relationship function enables you to check (and adjust where
necessary) the data pertaining to your external procurement relationships.
External procurement relationships constitute master data in the Advanced Planner and
Optimizer (APO). They provide the APO system with data from purchasing info records,
contracts, and scheduling agreements for the purpose of planning materials procurement
activities. Thus, with an external procurement order, for example, not only can you reference
a vendor, but you also have the option of directly referencing a specific item of an existing
contract.
When you transfer purchasing info records, contracts, or scheduling agreements from your
OLTP System [External] to your APO system via the Core Interface Advanced Planner and
Optimizer (CIF), external procurement relationships and the associated transportation lanes
are created in the APO system for this data automatically. In the process, a separate external
procurement relationship is created for each contract or scheduling agreement item.
(See also External Procurement Relationship [Page 282])
Integration
The external procurement relationship is directly linked with the relevant transportation lane
and supplements the latter by providing data from the purchasing info record, contract, and
scheduling agreement. From the external procurement relationship, you can also branch
directly to the transportation lane in order to maintain the latter’s data.
If your OLTP system is an R/3 system, you can transfer purchasing info records, contracts,
and scheduling agreements (and changes thereto) to your APO system via CIF.
Prerequisites
Before you can work with external procurement relationships in APO, you must transfer the
following data to it from your OLTP system via CIF:
• Plants
• Material master records
• Vendor master records
• Purchasing info records
• Scheduling agreements
• Contracts
In APO, you can work with the forms of procurement Standard, Subcontracting
[External], and Consignment [External]. For scheduling agreements, you can also
utilize the form of procurement Stock Transfer [External].
Transferring Master Data for the First Time
1. Create an integration model in your OLTP system, in which you specify which data is to
be transferred to the APO system (transaction CIF; Integration Model → Generate →
Create).
2. Then activate the integration model (Integration Model → Activate).
Transferring Changed Master Data
If purchasing document or master data has changed, you can carry out a transfer of the
changed data.

To transfer changes to purchasing info records, contracts, and scheduling agreements, call
up the transaction CIF Integration Model and then choose Transfer of Changes → Master
Data from the menu. Then select the Sources of Supply indicator.
The transfer of changes may result in data that you have changed in your APO system being
overwritten.
In your APO system, you have an external procurement relationship for item 10 of
your scheduling agreement no. 5500000001 from your OLTP system. In the APO
system, you change the planned delivery time for this external procurement
relationship from ‘5 days’ to ‘3 days’.
In the OLTP system, the original planned delivery time is then changed from ‘5
days’ to ‘6 days’. The changed planned delivery time is now transferred from the
OLTP system to the APO system. The planned delivery time, which amounts to 3
days in APO, is overwritten by the planned delivery time that was changed to ‘6
days’ in the OLTP system.
In an R/3 system, you can use contracts (Centrally Agreed Contracts [External])
and purchasing info records on a cross-plant basis simply by not assigning any
plants to them.
If you transfer such a centrally agreed contract or cross-plant purchasing info
record to your APO system, an external procurement relationship will be created
for each plant of the relevant purchasing organization that exists in your APO
system.
Features
The External Procurement Relationship function enables you to display, change, and restrict
the usability of the external procurement relationships that exist in the APO system (in the
latter case, by blocking the transportation lane, for example).
You define which external procurement relationships are to be displayed to you on the initial
screen for this function. For example: all external procurement relationships for a target
location (e.g. plant 0001), all those for a source location (e.g. vendor Meyer Corp.), or all
those with a certain external procurement category (e.g. “contract”).
The desired external procurement relationships are displayed in an overview tree in the left-
hand part of the screen, listed by external procurement category (purchasing info record,
contract, OLTP scheduling agreement, APO scheduling agreement) and the logical system
from which the data originates.
If you choose an external procurement relationship from the overview tree, the following data
on this relationship will be displayed in the right-hand part of the screen:
• General information on the external procurement relationship (such as the source and
target location, the product, and the validity of the external procurement relationship)
• Status of the external procurement relationship (active or inactive)
• Associated transportation lanes
• Scheduling agreement data – e.g. the release creation profile (only in the case of APO
scheduling agreements)
Changing an External Procurement Relationship

Only the certain data in an external procurement relationship can be changed using the
following functions:
• Change planned delivery time

• Activate, deactivate, and delete external procurement relationship

• Change transportation lane (Environment → Transportation Lane → Maintain)
• Create new transportation lane (Environment → Transportation Lane → Create)
You can process a transportation lane in an external procurement relationship as

follows:
• Change priority
• Block transportation lane
If you block an external procurement relationship, the latter can no longer be selected
in the source determination process.
If the external procurement relationship references an APO scheduling agreement, you can
also maintain the following data:
• Release Creation Profile
The release creation profile for the scheduling agreement is not transferred from the
OLTP system. You must create a separate release creation profile in the APO system
and assign it to the external procurement relationship. You define the release creation
profile in Customizing for Supply Chain Planning under Collaborative Procurement →
Maintain Release Creation Profile.
• Update liveCache
When an external procurement relationship is created, the field Update liveCache is
automatically populated with the value 10 – At time of release creation.
• Scheduling Agreement with Forecast
You use this indicator to specify whether forecast/planning delivery schedules are to
be generated in addition to operative schedules. In the standard system, this indicator
is not preselected when an external procurement relationship is created.
If you principally wish to work with forecast/planning delivery schedules, you can
specify via the BAdI [External] /SAPAPO/PWB_TPSRC_IN that the indicator is to be
automatically preselected when an external procurement relationship is created. With
the aid of this BadI, you can also influence other data of the external procurement
relationship or transportation lane.
You can also specify in the release creation profile whether forecast/planning
delivery schedules are to be generated in addition to operative schedules. For
this reason, the settings in the release creation profile and the Scheduling
Agreement with Forecast field must be harmonized.
• Internet Release
This indicator enables you to specify whether or not the scheduling agreement
release is an Internet Release [External] and whether it has to be acknowledged by
the vendor.
• Address Data
Address data is not transferred from the OLTP system. If you do not maintain any
address data on the Partners tab page, the address data of the source location is
used.
Use the button to maintain your own address data for an external procurement
relationship.

You can only influence other data by making a change in the OLTP system (e.g. a change to
the scheduling agreement).
Deactivating an External Procurement Relationship

If a purchasing info record, a contract, or a scheduling agreement is deleted in your OLTP
system, the relevant external procurement relationship is deactivated in the APO system.
This procurement alternative can no longer be used in the source determination process. The
log of the source determination process draws your attention to the fact that the relevant
procurement alternative has been deactivated.
Furthermore, no new transportation lanes can be created for deactivated external
procurement relationships.
Deleting an External Procurement Relationship

If you no longer need an external procurement relationship in the APO system, you can delete
it.
In order for you to be able to do this, the external procurement relationship should have been
deactivated. Furthermore, no external procurement orders or quota arrangements may exist
in the APO system for this external procurement relationship.
You can delete external procurement relationships as follows:
• In the external procurement relationship
Display the relevant external procurement relationship (Master Data → Procurement
Master Data → Procurement Relationships) and choose .
• Using the report Delete Procurement Relationships
Choose Master Data → Procurement Master Data → Delete Procurement
Relationships and select the desired external procurement relationships. Choose
Delete. All external procurement relationships marked with are deleted.
Determining the Source of Supply During Automatic

Planning
Use
During Automatic Planning [Page 118], the system automatically determines the procurement
type and selects the procurement alternative that can deliver the required quantity of goods
on time. If you have maintained several procurement alternatives, the system uses the one
with the highest priority and the lowest costs.
Prerequisites
• On the PP/DS tab page of the product master (Planning when Changing area), you have
specified whether the product (including the necessary components) is to be planned
immediately [Page 119] or via the planning run [Page 121] .
• You have defined the relevant procurement type for the product and the necessary
components on Procurement tab page of the product master. You can enter E for in-
house production, F for external procurement or X for in-house production or external
procurement.
• You have created alternative sources of supply for the product:
− In the case of products manufactured in-house, you represent the alternative
procurement options by creating different Production Process Models [External].

− In the case of external procurement and stock transfers, you define the different
procurement options in the Supply Chain Engineer in the form of transportation lanes.
When you transfer scheduling agreements, contracts and purchasing info records
from the OLTP System, External Procurement Relationships [Page 282] are created.
• You have maintained the procurement costs for each alternative.
− With in-house production, you maintain the costs in the production process model. To
do this, choose Goto → Costs (starting from the Change Production Process Model
screen) and enter the fixed and variable costs under Multi-Level Costs.
− With external procurement and stock transfers, you maintain the costs for the
manually created transportation lanes in the Supply Chain Engineer. For scheduling
agreements, contracts and purchasing info records, the costs are taken from the
OLTP System and can be displayed in the External Procurement Relationships [Page
282].
Features
Determining the Procurement Type
On the basis of the settings in the product master, the system determines whether the product
is to be produced in-house or procured externally. If you allow both procurement types for a
product, APO initially determines which alternative is to be used on the basis of the priority
and then on the basis of costs. If the product is produced in-house, the system creates a
planned order. If it is procured externally, it creates a purchase requisition (referencing an
OLTP scheduling agreement, contract, or info record, if used) or a delivery schedule line (for
an APO scheduling agreement), depending on the type of source used.
Determining Alternative Procurement Options

The procurement alternatives are evaluated and selected on the basis of the following criteria:
1. Quota arrangement
Procurement alternatives that are covered by a quota arrangement are given
preferential treatment.
2. Priority (highest priority = 0)
3. Costs
The costs from the procurement cost function are used. If scheduling agreements,
contracts, or purchasing info records are used, the costs for the cost function are
taken from the OLTP system. The cost function can be maintained manually in APO
for transportation lanes. If no procurement cost function has been maintained, the
manually created costs for the transportation lane are used.
4. Procurement type
In-house production takes priority over external procurement if both are permitted.
5. Adherence to desired delivery date
If possible, the system selects the procurement alternative with the highest priority and the
lowest costs, which can also deliver on the desired date. If none of the available procurement
alternatives can deliver on time, the system creates the receipt for a later date.
The Business Add-In [External] (BadI) /sapapo/pwb_sos enables you to influence

the source determination process. (For example, you may wish to have the
system first take the costs into account and only then the priority of the
procurement alternative.)

Determining the Source of Supply in Interactive

Planning
Use
You can manually select the source of supply when creating an order in Interactive Planning
[Page 306]. During Automatic Planning [Page 118], the system automatically selects the
procurement alternatives that can deliver a sufficient quantity of goods on time, with the
highest priority, and at the lowest cost. During interactive planning, this procurement
alternative is highlighted, but you are able to select the most suitable one for your purposes
from all the alternatives listed. You are also able to display additional information on each
source of supply.
Prerequisites
• You have created the alternative sources of supply for the product:
− In the case of products produced in-house, you represent the alternative procurement
options by creating different Production Process Models [External].
− In the case of external procurement and stock transfers, you define the different
procurement options in the Supply Chain Engineer in the form of transportation lanes.
When you transfer scheduling agreements, contracts, and info records from the
OLTP System, external procurement relationships are created.
• You have maintained the procurement costs for each alternative.
− With in-house production, you maintain the costs in the production process model. To
do this, choose Goto → Costs (starting from the Change Production Process Model
screen) and enter the fixed and variable costs under Multi-Level Costs.
− With external procurement and stock transfers, you maintain the costs for the
manually created transportation lanes in the Supply Chain Engineer. For scheduling
agreements, contracts and purchasing info records, the costs are taken from the
OLTP System and can be displayed in the External Procurement Relationship [Page
282] and during the interactive source determination process.
Features
When manually creating a receipt element that has more than one source of supply, you can
choose which source is to be used for the element. The Source Determination dialog box
appears, showing all allowed procurement alternatives.
The procurement alternatives are sorted and displayed according to the following criteria:
5. Quota arrangement
Procurement alternatives that are covered by a quota arrangement are given
preferential treatment. A procurement alternative that is due for allocation under a
quota arrangement is thus highlighted as the best source.
6. Priority (highest priority = 0)
7. Costs
The costs from the procurement cost function are used. If scheduling agreements,
contracts, or purchasing info records are used, the costs for the cost function are
taken from the OLTP system. The cost function can be maintained manually in APO
for transportation lanes. If no procurement cost function has been maintained, the
manually created costs for the transportation lane are used.
8. Procurement type
In-house production takes priority over external procurement if both are allowed.
9. Adherence to desired delivery date

The system highlights the most favorable procurement option according to the criteria.
However, you can interactively select any one of the allowed sources of supply.
If possible, the system suggests a procurement alternative with the highest

priority and the lowest costs which can also deliver on the desired date.
Procurement alternatives that cannot deliver on the desired date are marked with
. The system calculates an availability date on the basis of Infinite Scheduling
[External] and compares this date with the desired delivery date.
If you choose such a procurement alternative because none of the available
alternatives can deliver on time, for example, the system creates the receipt for a
later date.
You can also select several procurement alternatives. The system then selects
the best one.
The Source Determination dialog box contains a large amount information on the sources of
supply, which is distributed over three tab pages:
• Sources of supply
− Status of the sources of supply, whether they are subject to a quota arrangement and
whether they are able to deliver goods on or by a certain date.
− Location
− Means of transport
− Priority
− Total costs
− Procurement type
− Validity conditions
− Document numbers
− Information for PPM
− Information for RFQ
− Transport information
By selecting a source of supply and choosing Costs, you can view the fixed and
variable costs for that source.
• Log
The log contains additional information on all procurement alternatives.
Here you will find, above all, information on procurement alternatives for the relevant
product which are not shown on the Sources of Supply tab page (e.g. because the
source is currently blocked).
• Quota arrangements
If you have maintained quota arrangements for a transportation lane, a third tab page
Quota Arrangements appears. Here you can view information on the quota
arrangements between the source and target locations defined for this product. This
information includes the quota base quantity, the defined quotas, the total assigned
quantity and which heuristic is to be used to plan the quota item.

For more information on defining quota arrangements, See Quota Arrangement

Maintenance [External]. For information on how quota arrangements are used during
planning in PP/DS, see Quota Arrangements [Page 292].
Activities
You access the interactive planning screens by choosing Production Planning → Interactive
Production Planning → Product View or Product Planning Table or Receipts View or Order
Processing from the SAP Easy Access menu. For more information on how to create receipts,
see Maintaining Receipts [Page 314].
Quota Arrangements
Use
You use a quota arrangement [External] in APO to apportion product quantities among source
or destination locations according to your wishes. You can specify weightings for partner
locations, external procurement, and in-house production, according to which the quantities
are to be apportioned.
There are two different quota arrangement types:
• Incoming quota arrangement
You use an incoming quota arrangement to specify which proportion of a requirement
is to be procured from which source location (e.g. vendor).
• Outgoing quota arrangement
You use an outgoing quota arrangement to determine which proportion of the receipts
is to be delivered onward to which destination location (e.g. one of your distribution
centers).
Vendor Müller Vendor Schmidt
Incoming Quotation 3 (60%) 2 (40%)
Plant
Stuttgart
Outgoing Quotation 2 (50%) 1 (25%) 1 (25%)
Distribution Center Distribution Center Distribution Center

München Frankfurt Mainz
How quota arrangement items are planned depends on whether or not you have specified (in
the product master) that the quota arrangement heuristic is to be used to plan the product:

Quota Arrangement Heuristic

If you have defined the quota arrangement heuristic for the product, the apportionment of
requirements among the quota arrangement items takes place when the requirements are
analyzed. All quota arrangement items are planned separately according to the item heuristic
you have defined in the Supply Chain Engineer. By planning each quota arrangement item
separately, the system is able to take planning parameters such as lot-sizing procedures,
procurement lead times, rounding profiles, or the vendor calendars of the various sources of
supply into account.
Prerequisites
• In order for the planning to be carried out at quota arrangement item level, you have
specified (on the PP/DS tab page of the product master record) the quota arrangement
heuristic as the heuristic for planning the product. In the Supply Chain Engineer you have
specified the heuristic that is to be used to plan the quota arrangement item. For more
information, see Maintaining Quota Arrangement Items [External].
• You have specified that the product is to be planned either automatically (see Automatic
Planning in the Planning Run [Page 121]) or manually with or without check on the PP/DS
tab page of the product master.
Allocation Quota Arrangement

If you have not defined a quota arrangement heuristic for the product, the system will first
form lots and then apportion them among the various vendors and/or plants in the course of
the source determination process. You are therefore not able to take the above mentioned
planning parameters into account using this method. If you want to plan the quota
arrangement individually, you must therefore define the quota arrangement heuristic at
product level.
Prerequisites
You have defined the Quota Arrangement Header [External] and Quota Arrangement Items
[External] for the relevant vendors and/or plants in the Supply Chain Engineer.
Subcontracting
Purpose
Subcontracting is a form of procurement, in which a manufacturer orders a product from a
vendor/subcontractor and at the same time, provides the vendor/subcontractor with certain
components required to manufacture the ordered product. Subcontracting is performed in
APO via stock transfer. You define the subcontractor as a location and create transportation
lanes between the plant and the subcontractor to enable the transfer of stock in both
directions.
Prerequisites
You have maintained the following master data:
• In the Supply Chain Engineer, you have created a transportation lane from the vendor to
your plant for the ordered products and have allocated the ordered products to the
transportation lane and set the Source of Supply indicator to X for External Procurement
with Subcontracting.
• In the Supply Chain Engineer, you have created a transportation lane from your plant to
the vendor for the products to be provided.
• At the vendor's location, you have maintained the master data for the products and the
production process models and have assigned them to the active model.

Note the following:
If you want to create a subcontracting purchase requisition in the R/3 System for
a product that is planned in APO, you have to enter a vendor for the
subcontracting purchase requisition order, as otherwise it cannot be transferred
to the APO System.
Process Flow
1. A new requirement or a changed requirement for an ordered product must be covered.
Planning in APO is triggered either automatically or manually.
2. During planning, the system determines the source of supply for this product and finds a
transportation lane to the vendor in APO. This transportation lane has the External
Procurement with Subcontracting indicator.
3. The system generates a stock transfer order from the vendor (subcontractor) to your plant
in your plant.
4. The system searches for a valid PPM in the vendor's location and uses this PPM to
create a planned order for the ordered product at the vendor's location.
5. The dependent requirements for the planned order of the vendor are then planned. The
system determines the source of supply and finds a transportation lane back to the
ordering party (your plant). The system generates a stock transfer order from the plant to
the vendor for the products to be provided. Planning is thus complete in APO. This
process is depicted in the following diagram:
1. Plant (location 123) Subcontractor (location 456)
Source of supply for product Z

determined
Requirement for packaged screws (comprises

Planned order for packaged
two components: screws and packaging)
screws generated
Order for transfer of packaged screws from
subcontractor (location 456) to plant (location
123) generated
2. Plant (location 123)

Subcontractor (location 456)
Source of supply for components

(screws and packaging) determined
Order for transfer of components (screws

and packaging) from plant to subcontractor Components (screws and packaging) are
generated planned

3.
Plant (location 123) Subcontractor (location 456)
Plant delivers the components (screws and

packaging) to the subcontractor
Subcontractor delivers the

ordered product (packaged
screws) to the plant
6. When you save the planning results in APO, the orders are sent to the R/3 System. The
R/3 System creates a subcontracting purchase requisition. The planned order at the
vendor and the stock transfer order in your plant are assigned the same number in APO
as the subcontracting purchase requisition in the R/3 System.
7. You perform the execution of the order in the R/3 System. The procedure for processing
subcontracting purchase requisitions created in APO is the same as for those created in
the R/3 System:
a. You convert the subcontracting purchase requisition into a subcontract order.
b. You post the transfer of stock from normal stock to stock with subcontractor in the R/3
System.
In the R/3 System, the stock is special stock as it is still classed as being in the
plant. This same stock is normal stock in the APO System, as in APO it is at the
vendor's location.
c. The ordered product is manufactured by the vendor and delivered to the ordering
party. You post the goods receipt for the subcontract order in the R/3 System. The
stock of the components is reduced automatically when you post the goods receipt of
the ordered product.
If you post goods receipt of only part of the order, the order quantity is reduced
proportionately in the APO System and the R/3 System.

Subcontracting without a Source Location

Purpose
In APO you can plan subcontracting in two ways - either with or without a vendor. When you
plan with a vendor, the manufacturing order is generated by the vendor, while when you plan
without a vendor, the manufacturing order is created in the target location. The main
difference is in how you plan material requirements for the products to be provided. When
planning with the vendor, the requirements and stocks of the products to be provided are
MRP-relevant in the source location and material requirements can be planned for each
vendor individually. When you plan without a source location, the requirements and stocks
are MRP-relevant in your own plant. In this case, you cannot plan the transportation of
products to be provided to the vendors.
Subcontracting without planning the source location is recommended if the products to be
provided are not to be planned individually and if there is only one vendor for each product. If
planning takes place in R/3, a production process model (PPM) does not have to exist in
APO. In this case, you do not have to manually maintain any data in APO.
Prerequisites
The product is not maintained at the source location.
The following master data must have been created:
• For the ordered products, a transportation lane from the vendor to your plant must have
already been created. The Source of supply type indicator must be set to External
procurement with subcontracting.
• A PPM must be created in the target location. In addition, at least one operation and one
resource must exist for the PPM. Both must be assigned to the model and the PPM must
be active.
If a routing exists in R/3, the PPM can also be created via CIF. Another possibility is
to create a routing with a dummy work center in R/3 and the create the PPM via CIF.
Process Flow
1. A subcontracting purchase requisition is created during a planning run or manually. This
is visually represented in APO by a transfer order and a planned order. Both orders are
given the number of the purchase requisition in R/3. In R/3 the purchase requisition has
the components from the planned order.
2. The purchase requisition is converted to an order in R/3. In APO, the purchase requisition
is deleted and the order takes its place. Two orders are also created for the order.
3. A transfer posting is made for the product to be provided in the subcontracting stock. This
is MRP-relevant in your own plant, just like normal stock.
4. A goods receipt is posted for the order. The order quantity is then reduced by the goods
receipt quantity in APO, the products to be provided are debited by the subcontracting
stock and the stock for the finished product is increased.
Displaying and Checking the Planning Situation

Purpose
Since planning is run automatically whenever changes are made, the planning results or
stock/requirement situation must be checked on a regular basis and any alerts triggered must
be processed.
You can do this in the following views:

• Requirements view [Page 311]

You can display all requirements for a product in all locations or for all products in one
location.
• Receipts view [Page 312]
You can display all receipts for a product in all locations or for all products in one
location.
• Product view [Page 308]
You can display the current stock/requirements situation for a product, as well as
product master data, and days' supply information.
• Order processing view [Page 309]
You can display all data relevant to an order, including header data, order status,
product receipts, product requirements and operations, and pegging relationships.
• Context for order [Page 303]
You can display the pegging structure [Page 303] for an order. This is a graphical
presentation of all orders that are required to produce a finished product or an
assembly for a specific requirement.
You can display the current stock/requirements situation for a product, as well as the
load on a production line.
• Detailed scheduling planning board [Page 362]
You can display the resource schedule and order dates.
Process Flow
1. You call up the appropriate PP/DS view.
2. You check the planning.
The system displays planning problems on the planning screen or in the Alert
Monitor. For more information, see Display of Alerts [Page 304].
3. You solve the planning problems (see interactive planning [Page 306]).
Product View
Definition
An evaluation screen in Production Planning and Detailed Scheduling that provides an
overview of the current stock/requirements situation for a product in a location and a planning
version, as well as various planning functions.
Use
This evaluation provides you with an overview of the current stock/requirements situation of a
product and allows you to interactively change order dates and quantities. You can also:
• Display all receipts and requirements for a product along with any quantity or date alerts
• Display aggregated receipts and requirements for a particular period
• Display stock in other locations
• Display product master

• Display the days' supply for the product

• Display change log of manual changes in the product view (Changes function key).
Structure
The product view comprises header data and four tabs:
The header data contains information on the product, location, planning version and days'
supply [Page 57]. Up to three different days' supply types can be displayed (if you have
entered these days' supply types in Customizing for Supply Chain Planning, in the IMG
activity Global Parameters and Defaults). The days' supply provides information on the
number of days before stock falls below zero for a product.
• Individual elements list
The elements list displays all existing receipt elements and requirement elements of a
product in the location, along with information on dates, quantities, and alerts [Page
304]. You can change the dates and quantities of the orders. To access the order
processing [Page 309] screen for an order, double-click the order in this view.
• Periods view
On the Period tab you can display the period totals. The following information
appears:
− Available quantity
The result of requirements and receipts being settled against each other.
− Actual days' supply
Starting from the defined end of the day, the actual days' supply specifies how
many hours the available quantity will cover requirements.
− Total receipts
Receipts are added together for a period (for example, for each day). You can
display the individual elements in the period view by double-clicking on Total
receipts in the table.
− Total requirements
Requirements are added together for a period (for example, for each day). You
can display the individual elements in the period view by double-clicking Total
requirements in the table.
• Stock view
In this view, you can see how much stock of a product is in each of the locations to
which the product is assigned. Any stock assigned to an account is listed separately.
The storage location, batch, category and unit of measure are also displayed. By
double-clicking a location node in this view, the product view for the product in this
location is displayed.
• Product master data
The product master for the location product is displayed. This enables you to check
product master settings to understand the planning results without exiting the screen.
Integration
In addition, you can:
• Create orders [Page 314]
• Go to the Alert Monitor [Page 304]
• Change strategy settings [Page 419]

• Execute product heuristics [Page 321]
Order Processing View

Definition
Screen in Production Planning and Detailed Scheduling for displaying and processing an
order.
Use
In the order processing view, you can create, change or delete an order [Page 314]. You
create receipts for components for which you have defined manual planning in the product
master. You can use product heuristics [Page 321] to improve planning for the components.
In the order processing view, you can display the order in its environment, which includes:
• Pegging information
• Status information
• Alternative procurement options
• Operations
Structure
The order tree is displayed on the left side of the order processing view. It consists of the
order as the top node, as well as subnodes under which the actual order objects are listed.
Elements of the Order Tree
Subnodes Order objects

Receipts Products of the order
Requirements Components of the order
Operations Operations and activities of the order
By double-clicking an element of the order tree (node or order object) you control the content
on the right side of the order processing view.
Content of the right screen area after double-clicking a node
Node Content of the right screen area

Order Header data of the order such as dates, alerts [Page 304] and status information
The APO System displays the status of the order according to the status change
made in the integrated OLTP system (for example, released or confirmed).
On this screen you can:
• Set the conversion indicator [Page 467] to specify that the order is to be
converted automatically after it has been transferred to the OLTP system.
• Fix the output of an order [Page 317] to specify that automatic planning cannot
change the order quantity.
The APO System automatically sets the Input firmed indicator when you manually
change the quantity of a component.
Receipts List of order products with the detail data, such as the availability dates and
quantities.
Reqmts List of order components with the detail data, such as the requirements dates and
quantities.
Operations List of order operations with the detail data, such as dates and quantities.
Content of the right screen area after double-clicking an order object
Order object Content of the right screen area

Order product Product view [Page 308], plus the following tabs:
Component • The Pegging struct. tab contains the pegging information [Page
313] for an order product or for a component. You can manually
create fixed pegging relationships [Page 319].
• The Alternatives tab contains the options for external
procurement of the order product or the components. You can
enter alternative quantities and availability dates for the
procurement options and have the system perform a product
availability check. You can create orders for alternative
procurement options.
Operation Operation data, for example, resources being used, input and output
products and relationships
Activity Activity data
Integration
Calling the Order Processing View
You can call the order processing view either:
• Directly in the interactive production planning menu
• In the receipts view [Page 312] and in the product view [Page 308] by double-clicking an
order
Detailed Scheduling Strategies

The system performs detailed scheduling [Page 62] for an order using the detailed scheduling
strategy [Page 82] you have specified under Settings.

Alert Monitor
The display of alerts [Page 304] for quantity and date problems are integrated in the order
processing view. To display further alerts, for example, for resource problems, you can call up
the Alert Monitor [Page 304].
Plan Monitor
To display the quality of the planning based on your own criteria, you can call up the Plan
Monitor [External].
DS Planning Board
To display the schedule of the orders in a Gantt chart, you can call up two differently
configured DS planning boards [Page 385] from the order processing view. Here you can
manually reschedule orders or call the optimizer [Page 227].
Requirements View
Definition
A reporting screen in Production Planning and Detailed Scheduling that provides an overview
of all requirements for a product in a planning version, or for all products in a location of a
planning version, depending on your selection criteria when accessing the screen.
Use
This report allows you to display an overview of the requirements for one or more products
and if required, change them. The system displays both requirements created in APO and
those transferred from the OLTP system.
From within the requirements overview, you can:
• Change existing requirements
• Create new requirements
• Display the complete pegging structure [Page 303] of the order that APO created for a
requirement by double-clicking on the relevant requirement
• Change the time zone for displaying dates by choosing Settings → Time zone.
• Display change protocol for manual changes in the Requirements View (Changes
function key)
Structure
Based on the data you entered on the Process Requirements screen, the system searches
for the requirements of one or all products of a planning version and lists them in the
requirements table. This contains the following information:
• Requirements date and time
• Category of the order
For example, whether it is a forecast requirement or customer requirement.
• Characteristics
• Number of the requirement elements
• Target/source, that is, the production plant, supplying plant, or supplier
• Product and product description

• Receipt and requirements quantity

• Requested quantity (for example, in the sales order)
• Base unit of measure of the product
Integration
From the Requirements View, you can access the following functions:
• Create order [Page 316]
• Context for an order [Page 303] (by double-clicking on a requirement in the table)
Receipts View
Definition
overview of all receipts for a product in a planning version, or for all products in a location of a
planning version, depending on the selection criteria used to access the screen.
Use
This evaluation allows you to display and edit all receipts for a product or for all products in a
location. The system lists automatically and manually created receipts, as well as receipts
created in the R/3 System.
In the Receipts View, you can
• Change existing receipts
• Create new receipts
• Display change protocol of manual changes in the Receipts View (Changes function key)
Structure
Based on the data you entered on the Process Receipts screen, the system searches for the
receipts of one or all products of a planning version and lists them in the receipts table. This
contains the following information:
• Date and time of availability
If the product is manufactured in-house, the order can be a planned order or a
production order. If the product is procured externally, the order can be a purchase
requisition or a purchase order.
• Characteristics
• Receipt elements' number
• Receipt and requirements quantities


Integration
You can access the following functions from the Receipts View:
• Display the Process Order [Page 309] screen for the selected order by double-clicking it
Pegging Structure of an Order

Definition
Pegging Structure [External], which contains the order that you are currently processing in the
order processing view [Page 309].
Structure
You call up the pegging structure for an order in the order processing view via Context.
Layout of the Pegging Structure screen
Screen area Contents
Top Requirements of the end products produced in the order
Bottom left Pegging structure of the selected requirement

The requirement is the top node of the pegging structure. If there is no
requirement for an end product, the order for the end product is the top node
of the pegging structure.
Bottom right Detailed information on the receipt [External] and requirements elements in
the pegging structure

Prerequisites
Procedure


303] of the order
structure.
Display of Alerts
Use
When problems and non-typical situations arise during planning, the system generates alerts
to inform the planner. The following tools are available for displaying alerts during interactive
planning:
• Alert Monitor [External]
The Alert Monitor can display a wide range of PP/DS-specific alerts, for example, for
capacity, date and quantity problems. The Alert Monitor is configurable. In a PP/DS
alert profile [External] you can specify both the alert types that can be displayed as
well as the threshold value for the priority of the alerts (error, warning, or information),
depending on the size of the problem. For example, for a delay of a day the Alert
Monitor is to trigger an error alert, and for a delay of an hour, an info alert.
You can display or hide the Alert Monitor as required. In the order processing view
[Page 309] a list of the order-related alerts is also integrated.
• Alert icons
Icons display date or quantity problems for the receipts or requirements on the
planning screen. The meaning of the icon depends on the priority of the alerts.
Meaning of the Alert Icons

Icons Meaning
displayed
Info alert, lowest priority
Warning alert, medium priority
Error alert, highest priority
Prerequisites
• Under Supply Chain Monitoring in the Alert Monitor, you have defined a PP/DS alert
profile [External] with the alert types you want to see in planning.
For interactive planning, it is defined internally in the program that alerts are to be
generated for the displayed objects or for the objects from the direct environment of
the displayed objects. When the DS planning board is called up directly [Page 392],
alerts are also generated for the objects of the propagation range. Objects that you
have specified in the alert profile are not taken into consideration.
• Under Settings in interactive planning, you have entered the desired PP/DS alert profile.
Exception: For a DS planning board called directly, you enter a PP/DS alert profile when
calling it up.
• You have made the necessary settings in the master data for the various alerts types.
The following table contains a description of selected alerts and master data settings.
Alerts Description / Settings in the Master Data
Quantity alerts During pegging [Page 36], a requirement is assigned a receipt. If a staged
product quantity from a receipt is not assigned or not completely assigned to
a requirement, this receipt generates a surplus. If a product quantity required
by a requirement is not covered or not completely covered by receipts, a
shortage is generated. When surpluses and shortages arise during planning,
the system automatically generates quantity alerts.
In dynamic pegging [Page 38], you use the pegging interval [Page 39] to
restrict the time period in which receipts can be assigned to a requirement.
From the point of view of a requirement, a shortage occurs if there are no or
too few receipts in the pegging interval of the requirement. From the point of
view of a receipt, there is a surplus if the receipt quantity is not assigned or
only partially assigned to requirements. You define the pegging interval in the
location product master on the Demand tab.
Date alerts If a dynamic or fixed pegging relationship exists between a receipt and a
requirement, date problems must also be considered in addition to quantity
problems. The availability date can be before or after the requirements date,
which means the product is available too early or too late.
On the Demand tab in the location product master, you specify from which
time deviations between the requirements and availability date the system is
to create date alerts. You define the threshold values for the alerts so that
they are within the pegging interval.

Capacity alerts To enable the system to generate alerts for a resource when it is overloaded
[External], you must specify the following on the Planning parameter tab in the
resource:
• That they are scheduled finitely [External]
• Which resource load the system is to interpret as resource overload
Capacity alerts are only displayed in the Alert Monitor, and not in icons on the
planning screen.
Other alerts See PP/DS Alert Profile [External]
Activities
• To access the Alert Monitor in interactive planning, choose Alert Monitor.
• In interactive planning, you can use another alert profile at any time via Settings.
For more information, see Exception-Based Management: PP/DS [Page 477]
Interactive Planning
Purpose
You use interactive planning for products that are to be planned manually. Since the system
does not create any receipt elements to cover these products, you must create the receipt
elements interactively. You also use interactive planning to improve the results of automatic
planning and to deal with any problems that may have arisen. You can manually change
dates and quantities of orders in various PP/DS views. You can use the DS planning board
[Page 362] to perform interactive sequence planning for the operations and orders.
Prerequisites
You have maintained all necessary master data [Page 110] and PP/DS settings [Page 111].
Process Flow
1. To review the results of automatic planning, access one of the following views:
− Product view [Page 308]
− Order processing view [Page 309]
− Receipts view [Page 312]
− Requirements view [Page 311]
2. Check the planning results for any problems regarding order dates and quantities. They
will appear on the planning screen or in the Alert Monitor. For more information, see
Display of Alerts [Page 304].
3. If a product has a red alert icon regarding its quantity, there is a product shortage. This
occurs with products that are planned manually. You solve this problem by creating an
appropriate receipt [Page 314] to cover the requirement.
4. If a product has a red alert icon regarding its date, there is a due-date violation, which
means that the date of the receipt is after the requirements date or that no receipt exists
at all. In this case, you either create a receipt to cover the requirement or you can change
the date of an existing receipt [Page 314].

5. After you have manually created or changed orders, choose Product Heuristic [Page 321]
in order to trigger planning for the product. The heuristic [Page 207] that is defined for the
product in the product master is executed. If you do not wish the order to be changed,
you can manually firm the order [Page 317]. You can also fix pegging relationships [Page
319] so that the assignment of a receipt element to a requirement element is not changed
during planning.
6. To have a detailed view of an order and the resources within it, access the DS planning
board [Page 385]. Here you can reschedule orders and operations, and check the
capacity of resources. For more information, see Scheduling with the DS Planning Board
[Page 360].
7. After interactive planning, you can optimize [Page 227] the resource schedule.
Maintenance of Receipts and Requirements (Orders)

Use
In addition to automatic planning, you can also plan products manually and create, change
and delete orders manually to improve the planning situation. You are able to change orders
created in APO and orders transferred from the connected OLTP System. In various PP/DS
screens, you can change the quantities and dates of orders, change the source/target
location of an order, firm orders, fix pegging relationships as well as reschedule dates of
operations or orders.
Integration
The evaluation screens in Production Planning are integrated with the DS Planning Board
[Page 385] and the Alert Monitor [External].
Prerequisites
You have maintained the necessary master data and PP/DS settings.
Features
The following screens are available to you in PP/DS for the maintenance of orders:
• Process order [Page 309] screen
In this screen, you can display all data relevant to one order. You can change order
dates, quantities, locations, as well as firm orders and fix pegging relationships.
• Product View [Page 308]
In this screen, you can display the current stock/requirement situation for a product
and various product information, including the Product Master. You can change order
dates and quantities.
• Receipts View [Page 312]
In this screen, you can display all receipts of one or several products. You can
change order dates and quantities.
• Requirements View [Page 311]
In this screen, you can display all requirements of one or several products. You can
change order dates and quantities.
• DS Planning Board [Page 362]
You use the DS planning board to schedule or reschedule orders and/or operations.
You can change order dates and operation dates.

When you manually create receipts, lot-sizing procedures and rounding values
are not taken into account. After any manual changes of quantities, including the
creation of an order, you should use the Product Heuristic [Page 321] function to
enable the lot-sizing procedure and rounding values to be considered.
Activities
Access the appropriate evaluation from the Production Planning menu.
For more information on how to maintain receipts and requirements, see Maintaining Receipts
[Page 314] and Maintaining Requirements [Page 316].
Product View
Definition
overview of the current stock/requirements situation for a product in a location and a planning
version, as well as various planning functions.
Use
This evaluation provides you with an overview of the current stock/requirements situation of a
product and allows you to interactively change order dates and quantities. You can also:
• Display all receipts and requirements for a product along with any quantity or date alerts
• Display aggregated receipts and requirements for a particular period
• Display stock in other locations
• Display product master
• Display the days' supply for the product
• Display change log of manual changes in the product view (Changes function key).
Structure
The product view comprises header data and four tabs:
The header data contains information on the product, location, planning version and days'
supply [Page 57]. Up to three different days' supply types can be displayed (if you have
entered these days' supply types in Customizing for Supply Chain Planning, in the IMG
activity Global Parameters and Defaults). The days' supply provides information on the
number of days before stock falls below zero for a product.
• Individual elements list
The elements list displays all existing receipt elements and requirement elements of a
product in the location, along with information on dates, quantities, and alerts [Page
304]. You can change the dates and quantities of the orders. To access the order
processing [Page 309] screen for an order, double-click the order in this view.
• Periods view
On the Period tab you can display the period totals. The following information
appears:

− Available quantity
The result of requirements and receipts being settled against each other.
− Actual days' supply
Starting from the defined end of the day, the actual days' supply specifies how
many hours the available quantity will cover requirements.
− Total receipts
Receipts are added together for a period (for example, for each day). You can
display the individual elements in the period view by double-clicking on Total
receipts in the table.
− Total requirements
Requirements are added together for a period (for example, for each day). You
can display the individual elements in the period view by double-clicking Total
requirements in the table.
• Stock view
In this view, you can see how much stock of a product is in each of the locations to
which the product is assigned. Any stock assigned to an account is listed separately.
The storage location, batch, category and unit of measure are also displayed. By
double-clicking a location node in this view, the product view for the product in this
location is displayed.
• Product master data
The product master for the location product is displayed. This enables you to check
product master settings to understand the planning results without exiting the screen.
Integration
In addition, you can:
• Create orders [Page 314]
• Execute product heuristics [Page 321]
Order Processing View

Definition
Screen in Production Planning and Detailed Scheduling for displaying and processing an
order.
Use
In the order processing view, you can create, change or delete an order [Page 314]. You
create receipts for components for which you have defined manual planning in the product
master. You can use product heuristics [Page 321] to improve planning for the components.
In the order processing view, you can display the order in its environment, which includes:

• Pegging information
• Status information
• Alternative procurement options
• Operations
Structure
The order tree is displayed on the left side of the order processing view. It consists of the
order as the top node, as well as subnodes under which the actual order objects are listed.
Elements of the Order Tree
Subnodes Order objects

Receipts Products of the order
Requirements Components of the order
Operations Operations and activities of the order
By double-clicking an element of the order tree (node or order object) you control the content
on the right side of the order processing view.
Content of the right screen area after double-clicking a node
Node Content of the right screen area

Order Header data of the order such as dates, alerts [Page 304] and status information
The APO System displays the status of the order according to the status change
made in the integrated OLTP system (for example, released or confirmed).
On this screen you can:
• Set the conversion indicator [Page 467] to specify that the order is to be
converted automatically after it has been transferred to the OLTP system.
• Fix the output of an order [Page 317] to specify that automatic planning cannot
change the order quantity.
The APO System automatically sets the Input firmed indicator when you manually
change the quantity of a component.
Receipts List of order products with the detail data, such as the availability dates and
quantities.
Reqmts List of order components with the detail data, such as the requirements dates and
quantities.
Operations List of order operations with the detail data, such as dates and quantities.
Content of the right screen area after double-clicking an order object
Order object Content of the right screen area

Order product Product view [Page 308], plus the following tabs:
Component • The Pegging struct. tab contains the pegging information [Page
313] for an order product or for a component. You can manually
create fixed pegging relationships [Page 319].
• The Alternatives tab contains the options for external
procurement of the order product or the components. You can
enter alternative quantities and availability dates for the
procurement options and have the system perform a product
availability check. You can create orders for alternative
procurement options.
Operation Operation data, for example, resources being used, input and output
products and relationships
Activity Activity data
Integration
Calling the Order Processing View
You can call the order processing view either:
• Directly in the interactive production planning menu
• In the receipts view [Page 312] and in the product view [Page 308] by double-clicking an
order
Detailed Scheduling Strategies

The system performs detailed scheduling [Page 62] for an order using the detailed scheduling
strategy [Page 82] you have specified under Settings.
Alert Monitor
The display of alerts [Page 304] for quantity and date problems are integrated in the order
processing view. To display further alerts, for example, for resource problems, you can call up
the Alert Monitor [Page 304].
Plan Monitor
To display the quality of the planning based on your own criteria, you can call up the Plan
Monitor [External].
DS Planning Board
To display the schedule of the orders in a Gantt chart, you can call up two differently
configured DS planning boards [Page 385] from the order processing view. Here you can
manually reschedule orders or call the optimizer [Page 227].
Requirements View
Definition
A reporting screen in Production Planning and Detailed Scheduling that provides an overview
of all requirements for a product in a planning version, or for all products in a location of a
planning version, depending on your selection criteria when accessing the screen.

Use
This report allows you to display an overview of the requirements for one or more products
and if required, change them. The system displays both requirements created in APO and
those transferred from the OLTP system.
From within the requirements overview, you can:
• Change existing requirements
• Create new requirements
• Display the complete pegging structure [Page 303] of the order that APO created for a
requirement by double-clicking on the relevant requirement
• Display change protocol for manual changes in the Requirements View (Changes
function key)
Structure
Based on the data you entered on the Process Requirements screen, the system searches
for the requirements of one or all products of a planning version and lists them in the
requirements table. This contains the following information:
• Requirements date and time
For example, whether it is a forecast requirement or customer requirement.
• Characteristics
• Number of the requirement elements
• Receipt and requirements quantity
Integration
From the Requirements View, you can access the following functions:
• Context for an order [Page 303] (by double-clicking on a requirement in the table)
Receipts View
Definition
overview of all receipts for a product in a planning version, or for all products in a location of a
planning version, depending on the selection criteria used to access the screen.

Use
This evaluation allows you to display and edit all receipts for a product or for all products in a
location. The system lists automatically and manually created receipts, as well as receipts
created in the R/3 System.
In the Receipts View, you can
• Change existing receipts
• Create new receipts
• Display change protocol of manual changes in the Receipts View (Changes function key)
Structure
Based on the data you entered on the Process Receipts screen, the system searches for the
receipts of one or all products of a planning version and lists them in the receipts table. This
contains the following information:
• Date and time of availability
If the product is manufactured in-house, the order can be a planned order or a
production order. If the product is procured externally, the order can be a purchase
requisition or a purchase order.
• Characteristics
• Receipt elements' number
• Receipt and requirements quantities
Integration
You can access the following functions from the Receipts View:
• Display the Process Order [Page 309] screen for the selected order by double-clicking it

Prerequisites

Procedure

303] of the order
structure.
Maintaining Receipts
Use
If you have defined in the Product Master that a product is to be planned manually, you have
to create and change all orders for that product manually. You are able to create and change
orders from various screens.
If you have defined in the Product Master that a product is to be planned automatically, the
system creates and changes receipts automatically to ensure that requirements for these
products are covered. However, you are still able to create and change orders for these
products manually if you want to improve the planning situation.
You can change both receipts created in APO and receipts that were transferred from the
OLTP System to APO.
This procedure tells you on which screens you can create, change and delete orders and
what to be aware of on each screen.

Prerequisites
Procedure
Where to Create, Change and Delete a Receipt in PP/DS
Function Follow-on menu path What you should know

Create a receipt:
From the initial Production → Interactive planning →
Planning menu Create order
• On the initial Process
order [Page 309] screen
Choose Create order
• On the Process order
screen
• On the Product View
[Page 308]
• On the Process receipts
screen
• On the Receipts View
[Page 312]
On the Product View Enter the order data in the You are not able to change the
elements table. start date of the order when
creating an order in this
On the Receipts View Enter the order data in the manner. The current date and
receipts table. time is used as the start date
for the order. If you wish to
create an order with a different
start date, create an order by
choosing Create order.
Change a receipt
Change the quantity or date of
date:
On the Receipts View Choose Change and change
the data in the table
On the Product View
On the Process order screen Double-click on Product
receipts in the order tree. The
Product receipts table
appears.
Or double-click on the product
in the order tree. The elements
list appears.
Change source/target location Choose Change in the section This is the only screen in
on the Process order screen of screen entitled which you can change the
Source/Target source/target location of a
receipt.
Firm output of receipt on the Set Output firmed indicator Firming the output, means that
Process order screen the order quantity of the
product receipt will no longer
be changed by the system

during planning. You may still

change this order manually.
For more information, see
Firming Orders [Page 317].
Delete a receipt
On the Process order screen Choose Delete
On the Receipts View Select receipts to be deleted
and choose Delete at the
On the Product View bottom of table
Result
Any changes you make to receipts are automatically transferred to the OLTP System.
See also:
Maintaining Requirements [Page 316]
Maintaining Requirements
Use
Requirements are transferred from the connected OLTP System or from Demand
Planning/Supply Network Planning. As of Release 2.0A, you are also able to create planned
independent requirements directly in PP/DS. You can manually change the quantities and
dates of these requirements from various PP/DS screens
This procedure contains information on where you can create, change and delete
requirements in PP/DS.
Prerequisites
Procedure
Where to Create, Change and Delete Requirements in PP/DS
Function Follow-on menu path What you should know

Create a requirement:
In the product view [Page 308] Choose Change and enter the You are only able to create
order data in the table planned independent
In the requirements view requirements in PP/DS. To
[Page 311] create the requirement, enter
a negative value for the order
quantity.
Change a requirement
Change the quantity or date of
a requirement:
In the requirements view Choose Change and change You cannot change the source
the data in the table. location of the requirement. If
In the product view you wish to do so, delete the
requirement and create it with
the new source location

In the order processing [Page Double-click Product

309] view requirements in the order
overview tree. The Product
requirements table appears.
Or double-click a product in
the order overview tree. The
elements list appears.
Firm output of requirement on Set Output firmed indicator When you firm the output, the
the Process order screen order quantity can no longer
be changed by the system
during planning. You may still
change the quantity manually.
For more information, see
Firming Orders [Page 317].
Delete a requirement
In the Order processing view Choose Delete order
In the Requirements view Select requirements to be
deleted and choose Delete at
In the Product view the bottom of table
Result
Any changes you make to the requirements are automatically transferred to the OLTP
System.
See also:
Maintaining Receipts [Page 314]
Firming Orders for Production Planning

Use
An order can be firmed for planning using the production planning heuristics. PP Firming can
be triggered automatically by the system, or can be controlled by the user. The system cannot
change a PP firmed order; that is, the system cannot change the receipt quantity of the order
or delete the order, even if the requirements have changed. You can, however, change a PP
firmed order manually.
Prerequisites
An order is PP firmed if it has the status PP firmed. The system sets this status automatically
• If the availability date of the order is within the planning time fence
• If the order is an SNP order
• If the order has one of the following statuses:

− Output firmed
− Input firmed
− Date firmed
The following table gives the meaning of these statuses, and shows through which
user or system actions an order obtains these statuses.
Status Meaning Triggering actions or statuses
Output firmed The receipt quantity for the Changing the receipt manually
order is firmed. In PP planning,
You can change the receipt manually in the order
the system cannot change the
processing view [Page 309], for example, you can:
receipt quantity of the order or
delete the order. • Change the date, the quantity or the source
The output firmed status refers • Set the conversion indicator
to the order header firming in
the SAP R/3 system. Here, the system automatically sets the status
output firmed.
Firming the receipt manually
You can firm a receipt manually by setting the
status output firmed manually in the order
processing view.
Status input firmed
If the order is given the status input firmed (see
input firmed), the system also automatically sets
the status output firmed.
Order is a purchase order or a production order
Production orders and purchase orders transferred
from the OLTP System are automatically given the
status output firmed in the SAP APO system.
Input firmed The order BOM is firmed. If you Changing a component manually
change the receipt quantity of
You can change the order BOM manually in the
the order manually, the system
order processing view, for example, you can:
does not automatically explode
the PPM, but you can choose if • Change the required quantity
the system
• Use a different product as a component
• should retain the current
components and only In addition to the status input firmed, the system
adjust their quantities to the also automatically sets the status output firmed;
new receipt quantity that is, you can now only change the receipt
quantity of the order manually.
• should explode the PPM
(thus overwriting your
manual changes to the
BOM).
The input firmed status refers to
the explosion firming in the SAP
R/3 system.

Date firmed The dates and resource Firming with the detailed scheduling function
allocations for the order or Fix
individual operations of the
To prevent the system from changing the dates
order are firmed. The system
and resource allocations of the operations of an
cannot reschedule firmed
order in detailed scheduling [Page 62] or in
operations to other dates or
optimization [Page 227], you can use the detailed
other resources.
scheduling function fix [Page 418] to firm the order
or individual operations of the order in the
production planning run [Page 122] or in the
detailed scheduling planning board [Page 362]. By
firming, an operation is given the status firmed and
the order is given the status date firmed.
Resetting the PP firming

In the following cases, you can reset the PP firming of an order; that is, the system can
change the receipt quantity of an order or delete the order with subsequent PP planning.
The order is PP firmed How to reset the PP firming

Because you changed the order manually, Reset the status output firmed manually in the order
or firmed the receipt manually (status output processing view.
firmed)
Exception: If you have set the conversion indicator for
an order, you can not reset the PP firming.
Because you have firmed the operations of Reset the firming in the production planning run or in
the order using the detailed scheduling the detailed scheduling planning board using the
function Fix (status Date firmed) detailed scheduling function defix [Page 418].
Because the availability date of the order is If you set suitable settings in the planning time fence,
within the planning time fence the availability date may lie outside the planning time
fence.
You define the planning time fence in the product
master or in the product view.
Because the order is an SNP order outside Convert the SNP order into a PP/DS order [Page 114].
the production horizon
Creating Fixed Pegging Relationships Manually

Use
You wish to create total or partial fixed assignment of the product quantity produced by an
order to a specific requirements element. The system should not change this assignment
during automatic planning.
To do this you can create a fixed pegging relationship manually between the receipt element
[External] and the requirements element. You define the desired pegging quantity, that is, the
(partial) quantity of the receipt that you wish to assign to the requirement.
Unlike dynamic pegging, there are no time constraints for creating fixed pegging relationships.
The system can create date alerts and display them in the Alert Monitor [Page 304] if the time
deviations between availability and requirement dates are too large.

Prerequisites
You are in the change mode of the order processing view [Page 309].
Procedure
2. To display the existing pegging relationships for the order, double-click on the order tree
− under receipts on an order product, or
− under requirements on an order component
3. Choose the Pegging tab page.
− If you clicked on Receipts in step 1, you will see the pegging relationships to an
order product, that is, the requirements elements consumed by the order product.
For each requirements element, the quantity of order products with dynamic
assignment to the requirements element is shown in the Dynamic Pegging Quantity
column.
− If you clicked on Requirements in step 1, you will see the pegging relationships to
an order component, that is, the receipt elements that deliver this component. For
each receipt element, the quantity of components with dynamic assignment to the
order is shown in the Dynamic Pegging Quantity column.
5. In the Desired Pegging Quantity column, enter the quantity of the order product that you
wish to assign to the requirements element, or enter the quantity of components that a
receipt element should deliver to the order.
The desired pegging quantity can be different from the quantity that a receipt element
can actually deliver. The system determines the actual pegging quantity automatically
[Page 46].
If you choose Pegging alternatives, you will obtain a list of all possible requirements
or receipt elements that could consume the order product or deliver the component.
6. Select the requirements or receipt element and choose Fix.
Result
You have created a fixed assignment of the desired pegging quantity to a requirements
element or a receipt element. The system does not change this fixed assignment during
planning. If there is only fixed assignment for part of the product or component quantity, the
rest is not assigned or has dynamic assignment to requirements or receipt elements.
If you wish to undo the fixed assignment, select the requirement or receipt element and
choose Defix.
Example
A receipt element with an order quantity of ten pieces has dynamic assignment to a
requirements element with ten pieces. You can fix six pieces and thus fix assignment of the
requirements element. The remaining four pieces are then still assigned dynamically to the
requirements element, the system can change this assignment during automatic planning.
A product can be planned as an order network. To cover a requirement for such a

product, the system does not use any existing receipt elements, but creates
exactly one receipt element for the dependent requirement with the required
quantity (exact lot size) and assigns it to the requirement element. The system
fixes this pegging relationship automatically.

Product Heuristic in Interactive Planning

Use
You use the Product Heuristic function in interactive planning:
• To plan products that you have defined as being planned manually.
• To plan products for which you have defined automatic planning immediately [Page 119],
but would like to subsequently apply a heuristic. You use automatic planning immediately
to perform multi-level planning for a product. However, only fixed lot-sizes or lot-for-lot
order quantities are possible with this planning procedure. If you would like to
subsequently change planning to use, for example, a period lot-sizing procedure, you use
the product heuristic.
The product heuristic executes the heuristic for the product that is defined in the PP/DS tab of
the location product master.
Prerequisites
• You have defined which heuristic is to be used to plan each product on the PP/DS tab of
the product master.
• You have specified a scheduling strategy to be used for interactive planning in
Customizing for Supply Chain Planning in the IMG activity Maintain Global Parameters
and Defaults. Alternatively, you can interactively change the scheduling strategy settings
in the PP/DS screens.
• You have made the necessary PP/DS settings [Page 111].
• You have maintained all necessary master data [Page 110].
Features
The product heuristic plans products according to the heuristic defined in the product master
for each product. The heuristic is carried out for the top level product. Components that are
defined as being planned automatically and immediately are planned using a simple lot-sizing
heuristic. The planning with this heuristic is carried out according to multi-level logic, that is, if
a component is not available on time, the top level order is rescheduled. For the components
that are defined as being planned automatically in the planning run, planning file entries are
created. If you have not defined a heuristic for a product in the product master, the APO
System uses the default heuristic you have entered for the Product heuristic in Customizing
for Production Planning and Detailed Scheduling, under Global Settings → Maintain Global
Parameters and Defaults.
The availability check is carried out for components that are defined as being planned
manually with availability check.
Activities
You can start the Product Heuristic function in the following views:
• Product view [Page 308] [Page 308]
• Receipts view [Page 312] [Page 312]
• Requirements view [Page 311] [Page 311]
• Order processing view [Page 309]


Use
Features
strategies)
Activities
Settings.
interactively.
System [Page 112]
planning run


385]
[Page 386]
DS planning board
E-mail Connection
Use
You can use the e-mail connection function to send an e-mail quickly and easily from the
product view and the order maintenance screen to your vendors. This is useful, for
example, if exception situations have appeared in the result of the planning run and you want
to inform the relevant vendors in writing immediately.
Prerequisites
You have set up the APO system so that e-mails can be sent and have entered the e-mail
addresses for your vendors in the system in either or both of the following:

• in the external procurement relationships [Page 282] (scheduling agreements only)
To enter an e-mail address there, select the scheduling agreement item first, then
go to tab strip Partners and enter the e-mail address along with the option Mail
(MAI) in the Medium field.
• in the location master of the vendor
Features
Types of e-mail
• E-mail to all possible vendors of an externally procured product (general e-mail)
To find out the possible vendors, the system checks the external procurement
relationships defined for the product.
You access this function from the product view [Page 308] directly by selecting .
The e-mail addresses of all possible vendors appear in the send screen and you can
delete any that you do not require.
• E-mail to the vendor of an item in a scheduling agreement, purchase requisition or
purchase order (specific e-mail)
You access this function from the product view [Page 308] by double-clicking the item
and then selecting or from the order maintenance screen [Page 309] directly.
With both types of e-mail, the system looks up the e-mail address of the vendor in the
procurement relationships first. If it does not find an entry there, it turns to the location master
of the vendor next. This procedure is repeated for each external procurement relationship.
General features
• The system copies certain parameters directly into the e-mail:
− with the general e-mail: product number, location and e-mail address(es) of the
recipient(s)
− with the specific e-mail: product number, order number and e-mail address of the
recipient
• You can enter a title, add free text, change the recipient and attach files manually.
Product Planning Table

Purpose
In interactive planning in APO, the product planning table from 3.0 provides you with an
additional, universal planning tool – as well as the detailed scheduling planning board and the
product view. You can use the product planning table to create a master plan and you can
use it to evaluate the results of the planning run. It is an operative planning tool and is used
for planning production quantities. The product planning table is particularly useful for
repetitive manufacturers as you can use it to plan materials and loads on the production
lines/resources simultaneously. Therefore, it covers both product and capacity planning. As
well as for production planning, you can also use the product planning table for planning
externally procured components. That is, the product planning table also provides an interface
for the procurement planner.
• In Repetitive and Flow Manufacturing, planning and control is carried out on the basis of
periods and quantities. The layout of the product planning table has been designed to
support this requirement and is also based on periods to provide a very clear, easy-to-
interpret overview of products and production lines over the time axis.

• The product planning table is the planner’s most important tool for dispatching the
production quantities. At a glance the planner can check production quantities, monitor
the available capacity of the production lines and check up on the availability situation of
the products produced on each line
• You can directly enter and change production quantities in the product planning table.
You can reassign production quantities to alternative resrouces.
• As planning is often carried out on a shift basis, functions are also available in the product
planning table for distributing production quantities over shifts. You can also define a
flexible period split. Here, different periods can follow each other, for example two days in
shifts, three weeks in days and two months in weeks.
• You can also use the product planning table for planning and procuring components. This
means, the procurement planner can monitor the stock/requirements situation and create
or change purchase requisitions and schedule lines/scheduling agreement releases
directly in the product planning table. SAP also provides a separate default profile for the
procurement planner which he can choose for the configuration of the product planning
table.
Integration
The product planning table is completely integrated in the APO PP/DS environment. In
production planning – as for all of PP/DS –you have the choice of working with the PPM or
with the Integrated Product and Process Engineering (iPPE [External]). The product planning
table provides the same integration and functionalilty as other PP/DS functions, such as the
product view, for example.
For example, you can access the following functions from the product planning table:
• Heuristics for automatic planning
• PP/DS Optimizer
• Alert Monitor
• Plan Monitor
• Detailed scheduling planning board
See also:
APO Repetitive Manufacturing [External]
Features
The product planning table provides you with a periodic, aggregated view of:
• Production
• External procurement
You select the resources and products for which planning is to be carried out using a
navigation tree. You use the navigation tree for displaying alerts and for navigating through
the Supply Chain and the BOM. You can group by location, planner, resources, rows and
sources.
A flexible selection of detailed screens with many views is available:
• Product View: Periodic
• Product View: Individual Elements
• Product View: Quantity Graphic
• Resource View: Periodic
• Resource View: Individual Elements
• Production View: Periodic

• Production View: Individual Elements

• Optimizer
• Detailed scheduling planning board (see also: documentation on Detailed Scheduling
Planning Board [Page 362] APO_DS_038, especially New: Accessing the DS Planning
Board in the Product Planning Table [Page 386]).
• Alert Monitor (see also the documentaion on the Alert Monitor [External])
• Plan Monitor (see also documentation on the Plan Monitor [External])
• Stock Overview (see documentation on the Product View [Page 308])
You can also access Heuristics and Optimization procedures from the product planning table.
Planning Using the Product Planning Table

Purpose
This process describes how to use the product planning table for interactive planning to solve
planning problems with dates and sequencing, for example, while taking available resources
into account.
Prerequisites
• SAP delivers the product planning table with the standard settings. If you want to
configure the product planning table to suit your own particular planning needs, make the
necessary settings in Customizing for Production Planning and Detailed Scheduling
which can be accessed and modified in the application under user settings. You can find
more information under Configuration [Page 327] and in the implementation guide (IMG)
for Production Planning and Detailed Scheduling.
• To enable integration with R/3, you must maintain the integration model. See also:
Settings in the APO Page [External].
• You must maintain either the PPM or iPPE for planning.
Process Flow
Direct access:
1. You access the product planning table by choosing the following menu path: Production
Planning→ Interactive Production Planning → Product Planning Table.
2. In the initial screen, select the products and resources to be planned.
3. Check the current planning situation.
4. You change the planned quantities for production or external procurement manually or
you can trigger automatic planning runs.
5. Once a link is established with the R/3 System, the changed data is transferred
automatically when the planning result is saved. Here, you can plan and backflush other
components. The planning results and stock changes from the R/3 System are
transferred back to APO.
6. Recheck the changed planning situation in the product planning table.
Access via Alert Monitor:

1. Select PP/DS Alerts in the Alert Monitor. See also: Alert Monitor [External].

2. Use the right mouse button to select an alert. You then receive the possible functions of
the PP/DS in a dialog box which you can access to solve the problem situation.
3. Choose the product planning table which appears in a new window. The planning
situation for the alerts is displayed.
4. You change the planned quantities for production or external procurement manually or
you can trigger automatic planning runs.
5. Once a link is established with the R/3 System, the changed data is transferred
automatically when the planning result is saved. Here, you can plan and backflush other
components. The planning results and stock changes from the R/3 System are
transferred back to APO.
6. Choose Back to return to the Alert Monitor.
7. Choose Refresh to receive the current alert situation.
Configuration
Use
You can use this function to configure the product planning table to suit your requirements.
You can choose several views and display them on one screen, load profiles from
Customizing, modify them in the user settings of the application and save them as your
variants.
Prerequisites
You must have created or maintained profiles in Customizing. Standard profiles exist for all
profiles that you want to modify.
See also Loading and Modifying Profiles from Customizing [Page 328] and the IMG texts for
the product planning table: Supply Chain Planning → Production Planning and Detailed
Scheduling → Product Planning Table.
Features
• You can choose between the following views:
− In the periodic Product view, you can see the available quantity, the days’ supply and
the periodically totaled receipts and requirements for each product.
− In the periodic Resource view, you can compare the available capacity and the
capacity requirements for a resource and check the load of the resource as a
percentage.
− In the Product view: Individual elements, you receive detailed information on an
individual product.
− The Production view: Individual elements lists the orders for an individual resource.
− The Product view: Quantity graphic provides a graphic display of all the quantities.
− The periodic Production view contains information on all products produced using the
individual resources.
− Other PP/DS functions which you can integrate into the product planning table as
charts include the Alert Monitor, the Planning Monitor, the DS planning board and the
Optimizer.
• You can configure all views via the user settings in the product planning table. That is,
you can define layout settings, which rows you want to display, whether you want
individual quantities or totaled quantities and if you want to display profiles from other
PP/DS functions.

Loading and Modifying Profiles from Customizing

Use
The first time you access the product planning table, you load a standard profile from the total
settings via a dialog box. This is comprised of the standard profiles of the individual charts.
Via the user settings, you can change standard profiles or profiles you have defined yourself
in Customizing and save as your variant. You can save as many variants as you want.
See also the IMG texts in Customizing for APO under Supply Chain Planning → Production
Planning and Detailed Scheduling → Product Planning Table.
The following profiles are available for configuring the product planning table:
Profile Use
Maintain days’ supply types You define types of days’ supply.
Determine stock, receipt, requirement
and forecast categories for the
calculation of the days’ supply.
Define the visualization of the Define the views for displaying the
characteristics. characteristics when working with
configurable products. In this way, you
can define a view for the 10 most
important characteristics and define a
color code for these characteristics.
Set layout These settings affect charts, periods,
row descriptions and general settings for
table formats, column widths and days’
supply types.
• Available charts
• Chart profile
Default profiles exist for the
Model Mix Production Planner
MTS Production Planner
REM Production Planner
Procurement Planner
• Period profile
• Row description profile
• General settings
Create periodic planning You make several settings such as
layout, row display, units of measure or
quantity display for the charts Product
view: periodic, Resource view:
periodic and Production view:
periodic.
Maintain optimization profile You make the settings for optimization in
Production Planning and Detailed

Scheduling.
Heuristics in the product planning table You maintain the heuristics for
interactive planning and for planning in
background mode and control which
heuristics are accessible in an
application in a heuristics profile.
DS planning board in the product You maintain the period profile and the
planning table planning board profile for the DS
planning board [External] which you can
• Period profile
access in the product planning table.
• Planning board profile
Make total settings for the product You define a total profile comprised of
planning table the profiles for all the various charts plus
the profiles of other applications.
Maintain propagation range In the propagation range [External] you
define which resources and products you
can plan in production planning and
detailed scheduling.
In Customizing, you can change all the standard profiles with the exception of the standard
profile for the DS planning board in the product planning table.
Procedure
Loading the profiles:
1. The first time you access the product planning table, a dialog box appears in which all the
standard profiles in the total settings for the product planning table are listed.
2. Choose a profile by double-clicking it.
3. Save the selected profile as your user variant.
You can always only select one profile, but you can save as many profiles as you
want as user variants.
4. If you want to load another profile from Customizing later, choose Load profile from
Customizing in the user settings.
You receive the same dialog box as is displayed the first time you accessed the
product planning table (Selection of the PPT initial view) where you can choose a
profile and save it as a user variant.
Loading profiles from other PP/DS applications:

In the product planning table, via the user settings, you can also define the profiles from other
applications such as the DS planning board, Alert Monitor, Heuristics, Opimizer and Strategy
and save them as user variants. To do this, choose the tab page Profiles, select a profile and
save it.
Modifying profiles:
You can change and save the already existing profiles in Customizing.
The changes to the standard profiles are then visible to all users as Customizing
is not user-specific.

Note that changes to Customizing are not automatically updated in the variants
which means you have to reload the profiles to the user settings of the product
planning table.
Modifying user variants:

In the user settings, you make changes to your user variants on the various tab pages and
save these either under the same variant or you create a new variant.
The changes to your user settings are user-specific.
Accessing Charts
Use
The product planning table consists of many charts. You can display a maximum of three
charts at one time (see Configuration [Page 327] for the short description of the individual
charts). The navigation tree in the left, lower section of the screen lists the charts and displays
which ones are shown or hidden. If you loaded the standard profile SAP001, the charts; Alert
Monitor, Periodic Resource View and Periodic Product View are displayed, for example.
Prerequisites
The overview tree must be in display mode. Do this by selecting .
Procedure
Accessing charts using the navigation tree:
1. Using the drag and drop technique, you can easily move the individual charts between
the show or hide folders. If three charts are already being displayed and you try to add a
fourth, the system automatically hides the chart currently displayed at the bottom of the
screen.
2. If you only want to see one chart and you want this chart to fill the screen, you should
hide the overview tree on the left-hand side of the screen.
Accessing charts via the user settings and saving the setting as a user variant.
1. In the user settings, choose the tab page Charts.
2. In the section entitled, Tree, set whether the overview tree on the left-hand side of the
screen is to be shown or hidden.
3. In the other sections, determine the charts you want to display and the sequence in which
they are to be displayed.
4. In the Available Charts section, you can determine which and how many charts are to be
included for selection in the overview tree. All charts are contained in the standard profile
SAP001.
5. Choose Copy, if you only want to use these settings in the current session of the
product planning table. If you want to save the settings in your user variant or if you want
to create a new variant, choose Save current variant or New variant.

Setting the Column Width for Charts

Use
You use this function to determine the width of the columns for all tables in the product
planning table.
Procedure
1. In the user settings, choose the tab page General.
2. Enter a width for the text column and a width for the quantity column and save your
settings.
If you selected the standard profile SAP001, the width of the text column is preset
to 25 and the width of the quantity column is preset to 10.
Changing the Days’ Supply Unit

Use
In Customizing for the product planning table, for the navigation tree, you define which stock,
receipt, and requirement categories are to be taken into account when calculating the days’
supply. Two standard days’ supplies are available in Customizing – SAP1 and SAP2. You can
also create new days’ supply types by copying one of the standard days’ supplies. In the user
settings for the product planning table, you can only determine the unit of the days’ supply.
See also the IMG text for the days’ supply: Supply Chain Planning → Production and Detailed
Scheduling → Product Planning Table → Maintain Days’ Supply Types.
See also: Calculating the Days’ Supply [Page 57].
Procedure
1. In the user settings, choose the tab page General.
In the Days’ Supply section, you can see the days’ supply types you defined in the
Customizing profile.
2. Select another unit using F4 and save your setting.
If you selected the standard profile for the total setting SAP001, the days’ supply
is displayed in days.
Defining Periods (Buckets)

Use
Several of the tables in the product planning table are subdivided into buckets (periods). This
means, the system provides you with a periodic view of:
• Production

• External procurement
In Customizing, you can maintain the period profile and then you can set either shifts, days,
weeks, or months for planning in the product planning table.
See also the IMG text for the period profile: Supply Chain Planning → Production and
Detailed Scheduling → Product Planning Table → Set Layout → Maintain Period Profile.
For externally procured products, the planning calendar entered in the location in
the production calendar is used.
The planning calendar was enhanced to include the calculation, “shift split within
a week”. You can enter a maximum of three shifts per day in this shift split. This
means you can also use a shift view in the product planning table for externally
procured products.
A fixed and a flexible period split is available. You have the option of splitting the complete
period of examination into shifts, days, weeks or months. Orders, requirements and capacity
loads are totaled in the corresponding periods.
You can use the flexible period split to display various periods at the same time – for
example, you could first plan in shifts, then in days and then in weeks.
A typical period split is:
• The first two days in shifts
• The first two weeks in days
• The rest of the first month in weeks
• The rest of the period of examination in months
When setting shifts, a night shift that starts before 24.00 hours is treated as
belonging to the day before. That means, that orders, which are scheduled in this
night shift, are displayed in the day before when the daily setting is used.
However, if the personal time zone or the UTC time zone is set, this rule does not
apply. See also: Define Time Zones [Page 333].
You define the shifts in the master data for the resource. Master Data →
Resource → Definitions → Shifts. The numbering of the shifts in the shift
sequence follows their sequence along the time axis, that means, the first shift
that begins within a day is shift 1.
Procedure
1. In the user settings, choose the tab page Periods.
2. If you only want to define one period for all tables in the product planning board, do this
using the input help and choose Copy settings.
3. If you want to set a flexible period spit, choose user defined. In the User-defined period
split section, set the subsequent periods in which you want the planning situation to be
displayed.
4. Choose Copy settings or save your settings in your variant or in a new variant.

Define Time Zones

Use
You can define time zones for all PP/DS functions. These are the time zone, in which the
location is situated, the UTC time zone that is valid worldwide and the local time zone for the
user.
Prerequisites
You have entered the time zone for the setting Time Zone of Location in the master data.
Master Data → Location. Enter an existing location or create a new location. On the following
screen, the Time zone field is on the General tab page. Use the input help to select a time
zone. If you do not enter anything, the time set for the system is used automatically.
Procedure
1. Choose Settings → Time zone.
2. Select one of the options.
• Time zone of the location: time that is valid for the location selected and that you have
entered in the master data for this location.
• Local time zone of user: time that is saved in the user profile (System → User Defaults →
Own Data).
• All times are displayed in UTC format: Universal Time Coordinated (=UTC), which is the
time specification format that is valid worldwide. Time differences caused by summer time
and winter time are not taken into account for UTC.
The rule that orders in the night shift that start before 24.00 hours are
automatically displayed on the previous day does not apply for the local time
zone and the UTC time zone.
S1 S2 S3
t
0.00 6.00 14.00 22.00 24.00 6.00
Let us assume that there are three shifts of 8 hours. For a night shift that starts
before 24.00 hours, the system still displays the orders on the previous day if you
have set days for the periods in the product planning table.
The system always schedules orders backwards from the end of the bucket
[External]. If you set the time zone of the location, the bucket end is the end of the
shift. If you set the local time of the user or the UTC time, the bucket end is 24.00
hours in the respective time zone.

Result
All charts in the product planning table are switched to the new time zone.
Navigation in the Product Planning Table

Use
The navigation tree in the upper left-hand edge of the screen displays the work scope of the
product planning table. You use this navigation tree to define which objects you want to
display in the individual views. You can group the navigation tree according to various
categories. It provides you with information on BOMs and alerts for the products and you can
show or hide objects as necessary. You can see which objects are shown or hidden in the
charts by the color coding of the product rows.
You can switch the navigation tree on or off if you want to see the charts in a full-screen
display.
Features
The navigation tree displays the objects you selected in the initial screen of the product
planning table. In the navigation tree, the following sort and display functions are available:
• Switching on / off the navigation tree
• Grouping objects according to the following categories:
− Product
− Location
− Planner
− Resource
− Destination (lokction or resource )
− Source (location or resource )
You can only group according to the categories line and product group (product
hierarchy) if they were entered in the initial screen.
• Displaying alerts (days’ supply alerts, date and quantity alerts)
• Displaying BOM and where-used list for components
• Settings objects to “processed” and bringing them back into the worklist:
• Switching on/off, selecting and activating objects
Navigating in the Product Planning Table

Procedure
Switching on / off the navigation tree:
You can switch off the navigation tree if you require more space for displaying the charts.
Choose Overview tree on/off.

Grouping objects according to various categories:

1. Choose Group.
2. From the available categories, choose the ones according to which you want to group the
objects.
Depending on the profile you set, a certain grouping is preset. For example, for
the purchasing planner, the grouping by source. See also: Examples [Page 357].
Displaying alerts (days’ supply alerts, date and quantity alerts) in the navigation tree:
1. You must maintain the profile for the alert monitor so that the alerts are displayed in the
navigation tree along with their priority levels. (See also: PP/DS Alert Profile [External].)
2. The type of days’ supply displayed depends on the alert monitor profile. As soon as alerts
occur, one of the following icons appears depending on the priority level: (Error),
(Warning), (Information).
3. By choosing Filter and Change filter, you can use alert types to determine which objects
are displayed in the navigation tree and you can cancel the display of certain priority
levels.
If you only want to display objects which have alerts, in the filter settings, delete the
indicator Display elements without alerts.
4. Choose Filter and Activate filter to reactivate an existing filter.
Displaying the BOM for the products:

1. In the navigation tree, expand the object whose BOM you want to see.
The BOM depends on the orders in the system and is only displayed if orders exist
for the product.
2. In the navigation tree, you can also further expand the components required for the
assembly of the finished product if orders also exist for these components.
3. BOM display is not only limited to the product in the selected location – it is also valid for
products in other plants.
Displaying the where-used list for components:

1. By expanding the navigation tree, you can display the where-used list for components if
orders exist for products which require these components.
2. If the components are also required for other products, orders also have to exist for these
finished products. Otherwise, you cannot display the where-used list.
3. The where-used list is not only limited to the BOM of the product – it also shows the
usage of the product in other plants or distribution centers.
Settings objects to “processed” and bringing them back into the worklist:
1. Once you have completed planning for a product or for a line and a resource, you can set
the product to “processed”. Select a row and choose Processed.
A new folder entitled Processed is created in the navigation tree. When you expand
this folder, the processed object appears.
2. You can return processed objects back to the worklist by choosing the icon In worklist.

However, you can also plan objects in the Processed folder. The folder for the
processed objects is only used to improve the clarity of the information.
Hiding, showing, replacing and activating objects:

1. Select the objects you want to see in all views by choosing Show.
The selected objects appear in the navigation tree highlighted in yellow.
2. If you want to display an object in the Product View: Quantities Chart, the Product View:
Individual Elements and the Resource View: Individual Elements set it to active by
double-clicking it.
The activated object appears in the navigation tree highlighted in green. If another
object is activated the object previously activated remains selected, that is, it is
highlighted yellow.
One of the objects is always automatically activated – usually the first object in the
navigation tree. In each view, the activated object is always displayed in the first row.
3. Using the function Replace (icon ), two steps are carried out simultaneously: All objects
are hidden and only the selected ones are displayed.
Here, the system groups the resources or products.
When selecting products, the resources used to produce the products are selected and
shown.
When selecting resources, the products produced on them are selected and shown.
Production Planning
Use
You can access various charts for planning the product. The Product View: Periodic provides
information on the available quantities, orders and critical situations and the Product View:
Individual Elements shows information on the requirement and stock situation. The quantity
graphics represent the requirements and receipts for one product.
Features
Product View: Periodic [Page 336]
Product View: Individual Elements [Page 341]
Product View: Quantity Graphic [Page 343]
Product View: Periodic

Use
The periodic product view provides information on the receipts and requirements for products.
Key figures, such as, the available quantities, days’ supplies, for example, are displayed.
Receipts and requirements are cumulated periodically. Color highlights draw your attention to
critical situations, for example, material shortages. To solve these critical situations, you can
change existing planned independent requirements, planned orders or purchase requisitions

or you can create new ones or delete existing ones. To do this you simply enter other or new
values in the table.
The following table corresponds to the chart in the system. Every product contains a new row.
You can define the titles of these rows in the user settings. In the user settings, you can also
define whether you want to see a single-row or a multi-row view, which rows you want to see
and which periods are set. (See also: Defining the User Settings for the Periodic Product View
[Page 338]).

1.08.2000 1.08.2000 1.08.2000 1.08.2000
Product R1
Available 150
quantity
Days‘ supply 100 50
Plnd. indep. 100
requirements
Planned
order
Total 20 80
requirements
Product R2
150
50 100
100
Integration
In the periodic product view, you can access other views. Depending on which profile you
selected in the user settings, the system displays the product planning table with a different
configuration. (See also: Configuration [Page 327]).
Features
• You can access the view Product View: Individual Elements from the periodic product
view. The number of products displayed is reduced to the product selected in the periodic
product view. Via Further processing functions, you can also show the Alert Monitor and
the quantity graphic.
• You can define a product-specific planning time fence.
• You can also access information on the source of supply, firm orders and conversion
indicators. This means that planned orders (or purchase requisitions) are then
automatically converted into production orders (or purchase orders) when being
transferred to the R/3 System. Then, the conversion indicator is set in the Product View:
Individual Elements.
• You can branch further to create scheduling agreement releases, operative delivery
releases and forecast/planning delivery schedules.
• Via the other icons, you can also execute additional processing functions, such as
selecting, showing products, scrolling, creating a fullscreen display, hiding charts and so
on.

Defining the User Settings for the Periodic Product

View
Use
In Customizing and in the user settings, you can define the layout and the rows to be
displayed and their titles for the periodic product view.
See also the IMG text for the product profile: Supply Chain Planning → Production Planning
and Detailed Scheduling → Product Planning Table → Create Periodic Planning. In the
activity, choose Maintain Product View.
• You can choose between a single-row and a multiple-row display. In the single-row
display, exactly one row is displayed per product or per pegging area. If, for example,
you choose the available quantity, the system provides you with a quick overview of the
availability situation in production.
• You can determine which information rows are to be displayed for the single and for the
multi-row displays.
• You can define the sequence of the text objects for the row description of the header
rows.
• For the quantities rows (receipts, requirements, planned independent requirements), you
can set a partially aggregated and a disaggregated, detailed view.
Procedure
Setting a single-row display:
1. In the user settings, choose the tab page Product 1.
2. If you want a single-row display, set the indicator correspondingly. Use the F4 help to
choose the information row you want to display.
Setting a multiple-row display:

1. For the multi-row display, you can set several indicators for displaying additional
information rows:
Distributed quantities: The total quantity (for a planned order, for example) is split
over several periods (buckets) in an additional information row. If, for example, you
set the period profile to shifts, the system displays the quantity which can be
produced in each shift. To do this, you must have set continuous receipts/reqmts in
the PPM or in iPPE.
Characteristics: If characteristics exist for a product, the valuated orders are
displayed in an additional information row. Here, enter the profile of a characteristics
view from which the characteristics are to be displayed. The display is only possible
when using the function Characteristic-Dependent Planning [External].
Cumulated per product: Several MRP segments can exist for a product in a
location, for example in make-to-order production. This indicator determines that the
requirements and receipts of such products are displayed as totaled quantities in the
table.
2. In the Info Rows table, you can specify which information rows you want to set and the
order in which you want them to be displayed. Choose an information row for each row of
the table using the input help. You can use drag & drop to change the sequence as
necessary.
Determining the text item for the header row:

The header row of the periodic product view contains various text objects for the material and
location such as material number, material short text, location number and location short text.

You can define positions for these objects which determines a sequence in which they are
displayed.
Defining the quantity rows:

1. Choose the tab page Product 2.
2. Use the corresponding indicator to define whether you want to set the aggregated, the
partially aggregated or the disaggregated view for the quantities receipts, requirements
and planned independent requirements. You can also select several views at the same
time.
Aggregated: For every pegging area, the system displays the additional information
rows total receipts, total requirements and total planned independent requirements.
Partially aggregated: This view consists of partial totals. Here, the quantities of an
ATP category are totaled. This means if you have set the aggregated and the partially
aggregated view together, the system adds the planned order quantity, the purchase
requisition quantity and the production order quantity under the total receipts. At the
same time the total sales order quantity is displayed under the total requirements.
When dealing with components, the dependent requirements total and the
reservations total is displayed in the additional rows.
Disaggregated: Planned or production orders are broken down per planning ID and
output resource. Sales orders or purchase requisitions are split according to
individual customers or suppliers. Dependent requirements are listed according to
target resource, planning ID.
You can only make manual changes to orders, purchase requisitions or planned
independent requirements in the disaggregated view.
3. Enter a quantity type for each quantity. For every aggregation level, you have to
differentiate between two quantity types for each of the three quantities receipts,
requirements and planned independent requirements.
Receipts Requirements Plnd indep. reqmts
Total quantity Desired quantity Original quantity
Yield Confirmed quantity Consumed quantity
You also have the option of setting the two quantity types at the same time. If these
two quantity types are different, two new information rows become visible.
4. In the section entitled, Row description, by defining a position, you can define which text
objects appear in the rows receipts, requirements and planned independent requirements
and the sequence in which they are to be displayed.
Defining the Settings in the Periodic Product View

Use
You can make the following settings for the periodic product view in the chart itself using the
icons and Further processing functions.
Procedure
Accessing individial elements for the product:
1. Select a product.
2. Use the icon to access the individual elements of a selected product. The periodic
product view is then replaced by the Product View: Individual Elements.

3. Choose Back or Change to product table to return to the Product View: Periodic.
4. You can display a more limited view of the individual elements – only for one period – by
double-clicking a row in the table or by placing the cursor on a row and choosing
Show cell details.
5. Choose Hide cell details to close the view again.
Show resources for the product:

1. In the periodic product view, select one or several products.
2. By choosing the icon the system selects all the resources on which the selected
product can be manufactured. These resources are then displayed in the Resource View:
Periodic and in the Production View: Periodic. Therefore, it makes sense to access these
views additionally.
Accessing the Alert Monitor and the quantity graphic:

1. Choose Further processing functions and Alert Monitor to access the alerts for the order.
2. Choose Further processing functions and Quantity graphic to access the quantity graphic
view for the selected product.
Accessing the source determination:

1. Choose Further processing functions and Source determination.
2. In the dialog box that appears, the system displays possible supply sources for a product
for in-house production and for external procurement.
This window also appears in the Product View when creating planned orders –
here it is only used for information purposes (info on procurement alternatives).
Firming orders:
You have various possibilities for firming orders:
1. Select a product or the order row for a product and choose Further processing functions
and Firm orders.
All the orders for the selected product are firmed. Then the Firming indicator is
selected in the Product View: Individual Elements.
2. Select a product or the order row for the product and a row or a column.
All the orders for the selected product in the selected period are firmed. Then the
Firming indicator is selected in the Product View: Individual Elements.
2. Choose Further processing functions and Delete firming to cancel the firming.
Setting the planning time fence

1. Select a product and a column.
2. Choose Further processing options and Set the planning time fence.
The date of the selected column is used as the end date of the planning time
fence.
If you only select one product and no column, the system displays a dialog box in
which the end of the selection period is proposed as the end date of the planning
time fence.

Setting the conversion indicator:

1. Choose Further processing options and Set the conversion indicator.
The conversion indicator is then selected for the selected orders in the Product
View: Individual Elements. The conversion indicator is used to convert the
planned orders into production orders (or purchase requisitions into purchase
orders) when transferring the data to the R/3 System.
2. Choose Further processing functions and Delete conversion indicator if you do not want
the planned orders to be converted into production orders.
Creating scheduling agreement releases:

1. You have created scheduling agreements [Page 272] and schedule lines in APO.
2. In the periodic product view, select the product for which you want to create scheduling
agreement releases.
3. Choose Process sched. agrmt releases.
4. Depending on which type of release you want to create, choose Create operative delivery
schedule or Create forecast/planning delivery schedule.
A success message confirms the creation of the scheduling agreement release.
5. Choose Display sched. agrmt releases.
6. In the new view, you can see all the scheduling agreement releases for the selected
product.
Product View: Individual Elements

Use
The Product View: Individual Elements contains all the available receipt elements (orders)
and issue elements (requirements) of a product in a location as well as information on
requirement and availability dates and times, ATP categories, start dates and times, excess
quantitites or missing quantities and required quantities. By double-clicking one of the orders,
you can access the order processing [Page 309] screen for this particular order. In the Alert
Monitor, you can also display the alerts [Page 304]. You can change the dates and quantities
of the orders in the Product View: Individual Elements.
The following table corresponds to the chart, but does not list all available columns:
Reqmt/Ava Reqmt / Cate- Receipt / Stoc Start date Desired Excess Availab Target Resou
il. date gory issue k quantity / le rce
Avail.
element
date Missin
g qty
14.07.2000 23:59:59 VP- 50- 12.07.2000 50- 50-
BED
15.07.2000 23:59:59 VP- 50- 50- 100-
BED
16.07.2000 23:59:59 VP- 50- 50- 150-
BED

Integration
The Product View: Individual Elements basically corresponds to the stock/requirements list in
R/3 and also exists in the product view in APO.
Features
You can always only access the Product View: Individual Elements for one product/location
combination. You can execute the following functions:
• You can access the Product View: Periodic.
• You can define a planning time fence.
• You can change the source of supply.
• You can delete orders and schedule lines.
• Orders and schedule lines can be firmed and you also have the option of canceling the
firming indicator again.
• You can set and delete a conversion indicator.
Defining Settings in the Product View: Individual

Elements
Use
You can make the following settings for the Product View: Individual Elements in the chart or
using the icons.
Procedure
Accessing other functions:
1. To access the periodic product view, choose Switch to product view: periodic.
If this view has already been accessed, the icon remains gray and can no longer
be selected.
2. By double-clicking an order, you access the Process order screen.
Here, you can set the planning time fence and the conversion indicator and you
can change the source of supply.
Setting the planning time fence:

3. Select an order.
4. Choose Planning time fence.
The availability date plus one second is defined as the end of the planning time
fence.
If you only select one product and no column, the system displays a dialog box in
which the end of the selection period is proposed as the end date of the planning
time fence.

Changing the source:

1. Select an order and choose Change source.
In the dialog box Source Determination you can see the alternative sources of
supply.
2. Select an alternative source of supply and choose Continue.
Deleting orders and schedule lines:

1. Select one or several orders or schedule lines.
2. Choose Delete orders /schedule lines.
Firming and unfirming orders and schedule lines:

1. Select an order or a schedule line.
2. Choose Firm order /schedule line.
The indicator in the Firming ind. column is selected and the system displays a
success message.
3. Choose if you want to cancel the firming indicator.
Setting and deleting the conversion indicator:

1. Select an order.
2. Choose Set conversion indicator.
The indicator is selected in the Conversion ind. column. The conversion indicator
is used to convert the planned orders into production orders when transferring the
data to the R/3 System.
3. Choose Delete conversion indicator if you want to cancel the flag for converting the
planned orders into production orders.
Product View: Quantity Graphic

Use
In the quantity graphic, you receive the graphic display of the production quantities for a
particular product. The system shows the cumulated requirements and the cumulated
receipts.
Features
1. The requirements and receipts of a product which you selected in the overview tree are
displayed graphically.
2. You can print the graphic.
3. You can modify the display period.
Activities
1. Double-click a product in the overview tree for which you want to display the quantity
graphic.
In the overview tree, the product is highlighted in green.
2. Access the chart Product View: Quantity Graphic.

You receive a graphic display of the cumulated requirements (red) and the
cumulated receipts (green) and, if necessary the stock (blue).
3. Choose Print to print out the graphic.
4. You have the option of changing the display period which corresponds to the selection
period in the standard settings. Choose Display period and enter a number of days for
which the graphic is to be created in the dialog box which appears. In the Offset from
today field, you can also set exactly when the display period is to commence – for
example one week from today.
5. Choose Fullscreen if you want to display the quantity graphic as a fullscreen display.
Then the other preset views are hidden. You can display these views again by
reaccessing them from the navigation tree.
Capacity Planning
Use
Other charts are available in the product planning table for capacity planning. The system
displays the requirement and availability data of the resources and their loads as a
percentage. For the resources, the system displays information on the products, the order
quantities to be produced in each period and detailed information on dates and quantities.
From the capacity views, you can start the Alert Monitor and the resource alerts, you can
access graphics and go to sequencing.
Features
Resource View: Periodic [Page 344]
Production View: Periodic [Page 347]
Production View: Individual Elements [Page 349]
Resource View: Periodic

Use
The resource view determines the load of a resource as a percentage using the capacity
requirements [External] and the maximum capacity load [External].
A differentiation is made between the requirements and load of the resource and displayed in
a time unit that you can change.
Resource View: Periodic

Un Due 1.08.2000 2.08.2000 3.08.2000 4.08.2000
Resource R1 % 50 50 100 75
Reqmt Hr 4 4 8 6
Load Hr 8 8 8 8
Resource R2 25%
Reqmt Hr 2
Load Hr 8 8 8 8

Integration
From the periodic resource view, you can access the Production View: Individual Elements,
the Production List and the master data for the resource. You can also access the Alert
Monitor.
Features
1. You can choose between a single-row and a three-row view. In the three-row display, the
capacity load is displayed as a percentage and the requirements and load in a time unit.
2. You can change the time unit for the requirements and the load.
3. You can access the Production View: Individual Elements from the periodic resource view
where you can see all orders on one selected resource.
4. By selecting the icon Row details or by double mouse click, the system displays the
orders for the selected period in a new view.
5. In the overview tree, you can show and select the products manufactured on the
resource.
6. You can show the Alert Monitor and display all the alerts for the resource.
7. You can choose the resource schedule. See also Accessing the Production List [Page
355].
8. By accessing the master data for the resource, you can enter or change the operating
time and the downtime.
Defining User Settings for the Periodic Resource View

Use
You can set the unit in which the capacity requirements and load are to be displayed in
Customizing and in your user settings and you can define that only one row is to be displayed
with the load as a percentage.
See also the IMG text for the capacity profile: Supply Chain Planning → Production Planning
and Detailed Scheduling → Product Planning Table → Create Periodic Planning. In the
activity, choose Maintain Resource View.
Procedure
1. In the user settings, choose the tab page Capacity.
2. Using the input help, choose a unit of measure in which you want to display the capacity.
3. If you select the indicator Single row, the system only displays the load of the resource as
a percentage in the periodic resource view. By double clicking this row, the system
displays the other two rows; Requirements and Available.
Defining the Settings in the Periodic Resource View

Use
You can make the following settings for the periodic resource view in the chart itself using the
icons and Further processing functions.

Procedure
Setting a triple-row view and changing the time unit:
1. By double-clicking the resource, you switch to the triple or single-row view.
2. Using the input help, you can choose another time unit.
Changing to the Production View: Individual Elements:

1. Select a resource.
2. Choose Production View: Individual Elements. The new chart replaces the periodic
resource view and lists the orders for the selected period for the selected resource only.
3. Choose Change to resource view to return to the periodic resource view.
If you double-click cell in the requirements row, the system displays a variant of
the Production View: Individual Elements in which you can only see the order of
the selected period column.
To access this additional view, you can also select a column and choose Show
cell details.
Displaying alerts:
1. Choose Further processing functions and Display resource alerts.
The Alert Monitor with the various alert types is shown as the first chart.
Show products on resource:

2. Choose Products on resource.
In the overview tree, the system displays the products produced on this resource
highlighted in yellow.
Changing the operating time:

2. Choose Further processing options and Resource operating time.
The system displays the screen for changing the operating time.
3. Change the start or the end time of the resource. The operating time is calculated
automatically. You can increase the rate of resource utilization if, for example, you had to
reduce the operating time.
See also: Standard Capacity [External].
Changing the downtime:

2. Choose Further processing options and Resource downtime.
3. In the Product Planning Table dialog box, enter the start and end of the downtime and
choose a type of downtime.
4. Choose Continue.
Resource availability and percentual load are change correspondingly.
See also: Downtimes [External].

Production View: Periodic

Use
The periodic production view provides a combined view of resources and products. The
selected resources are listed and the products manufactured using these resources are
displayed. In the product’s rows, the orders are displayed with the total quantity and with the
distributed quantities if the order is produced over several periods.
As in the Product View: Periodic, you can create, change and delete orders.
The following table provides an example of two products, whose orders are produced on two
resources one after the other:
Produ ctio n View : Periodic

1.08.2000 2.08.2000 3.08.2000 4.08.2000
R esource R 1 % 100 70 80
Product 1 (O rders) 150
(Distributed) 100 50
(Distributed) 20 80
R esource R 2 % 50 100 100
(Distributed) 50 100
(Distributed)
Prerequisites
If you want to start Sequencing from the Periodic View: Periodic, work with iPPE.
All the other functions are possible when using iPPE as well as when using the
production process model.
Features
1. You can change to the Production View: Individual Elements from the periodic resource
view where you can see all orders on one previously selected resource.
2. By selecting the icon Row details or by double mouse click, the system displays the
orders for the selected period in a new view.
3. In the overview tree, you can show and select the products manufactured on the
resource.
4. You can show the Alert Monitor and display all the alerts for the resource.
5. You can choose the resource schedule. See also: Accessing the Production List [Page
355].
6. By accessing the master data for the resource, you can enter or change the operating
time and the downtime.
You can also access all the functions mentioned above from the Resource View: Periodic.
See also: Defining the Settings in the Periodic Resource View [Page 345].

7. You can determine the row descriptions in the user settings and define how many info
rows are to be displayed. See also: Defining User Settings for the Periodic Production
View [Page 348].
8. You can change the unit of measure interactively.
9. As in the Product View: Periodic, you can create, change and delete orders.
10. From the periodic resource view, you can start Sequencing [External] provided that you
work with iPPE. See also Sequence Schedule [Page 154].
Defining User Settings for the Periodic Production

View
Use
In Customizing, you can select a profile for the periodic production view or you can define
yourself how many and which information rows are to be displayed in this view. In your user
settings, you can also define which objects are to appear in which order for the header row
and you can determine which objects appear in which order for the header of a new resource.
Procedure
1. In the user settings, choose the tab page Production.
2. As was possible for the periodic product view, you can set one or several of the following
indicators:
Characteristics: If characteristics exist for a product, they are displayed in an
additional information row. Here, enter the profile of a characteristics view from which
the characteristics are to be displayed.
Selected products: Only the products selected in the navigation tree are displayed in
the chart. Therefore, you do not have to display all the products produced on the
resource – only the ones selected are displayed.
Distributed quantities: The total quantity (for a planned order, for example) is split
over several periods (buckets) in an additional information row. If, for example, you
set the period profile to shifts, the system displays the quantity which can be
produced in each shift.
Cumulated per product: Several MRP segments can exist for a product in a
location, for example in make-to-order production. This indicator determines that the
requirements and receipts of such products are displayed as totaled quantities in the
table.
3. You can also set the indicator Selected products. This means that only the products you
select in the navigation tree are displayed. For the periodic production view, this means
that only certain products of the resource are displayed.
4. In the section Text items for resource/product view, you can set which objects are to
appear in which sequence in the individual rows of the periodic production view.
5. If several resources have been specified, you can determine the position for the objects
Resource and Resource description for the titles of every additional resource.

Production View: Individual Elements

Use
In the Production View: Individual Elements, you are provided with an overview of the orders
which are produced on the selected resource. Here, you are provided with detailed
information such as start and end date, availability dates and quantity specifications.
The following table corresponds to the chart, but does not list all available columns:
Order List: Resource / Location (to Sat. 26.08.00)

Product Product Start date Finish date Category Receipt / Avail. date Total
description issue quantity
element
FERT01 Finished 28.07.2000 28.07.2000 PLAUF 0000001 28.07.2000 10
material 01 07524
Integration
From the Production List: Individual Elements, you can access the Resource View: Periodic
and the Alert Monitor, you can also access the order processing and you can branch to the
Features
• Using the icon Switch to resource view, you can access the Resource View: Periodic.
This replaces the Production View: Individual Elements. If the periodic resource view has
already been accessed the icon remains gray.
• You can show the products for the resource which are displayed in the navigation tree.
• Via Alerts for resource, you access the Alert Monitor.
• You can access details on the order. Here, you branch to order processing. See also
Order Processing View [Page 309].
• From this chart, you can also access and print the production list. See also: Accessing
the Production List [Page 355].
• Using the icon , you can also delete orders. You cannot create any orders or change
any order quantities.
• The Finish date and Time of the activity can be modified interactively.
• Select the icon to access the detailed scheduling planning board. The system does
not only display the resources of the Production View: Individual Elements, but also all
the other resources that are selected in the overview tree.
Activities
You double-click the resources in the navigation tree to control which resources are
displayed.

Accessing Optimization in the Product Planning Table

Use
In the product planning table [Page 324], you can access Optimization [Page 227] where you
can optimize the production dates and the resource schedule. You can convert optimized
production plans into schedules. The optimization is integrated as a chart in the product
planning table.
Prerequisites
• The master data for the optimization is maintained in Customizing of the Basis Settings
(for example, the network links to the optimization server and the maximum number of
users).
• If you want to work with your own optimizing settings or if you want to carry out
optimization with the changed capacities of Multi Resources [External] , you must define
your own optimization profile and enter it in Customizing for the Product Planning Table.
Procedure
1. In the overview tree, click on Optimizer and use drag & drop to drag this view into the
highest folder so that it is displayed.
If you choose Optimize, the system displays the same view in the fullscreen.
Then you first have to select the appropriate resources in the resource view.
2. In the resource view, select the resources you want to transfer to the optimization.
If you do not select any resources, the system select all resources selected in the
navigation tree provided that you have grouped by resources in the navigation tree.
3. If necessary, maintain the settings for the optimization via Configuration. (See also:
Calling Up the Optimization in the DS Planning Board [Page 237].) )
For example, you can define the optimization procedure, the optimization period and
the criteria for the optimization.
You can also change the horizon in one of the other views, for example, in the
resource view by selecting the period to be covered by planning.
Calculating the Ranges of Coverage in the Product

Planning Table
Use
The system calculates the range of coverage in the product planning table using the available
quantity displayed. The available quantity is the difference between all receipts and
requirements or planned independent requirements at the end of a period.
In each period, the range of coverage shows how long (from the end of the period) the
available quantity will cover the requirements in the future. It is therefore a days’ supply based
upon the available quantity.
The system does not use a days’ supply type when calculating the range of
coverage.

Integration
The calculation of the range of coverage is therefore different from the calculation in PP/DS.
Compare: Calculation of Days‘ Supply [Page 57].
Features
The system calculates the range of coverage as days’ supply using the available quantity at
the end of a period. The periods come from the production calendar for the location.
pc Cumulative
receipts
Days‘ supply P1
Available Cumulative
quantity P1 requirements
t
P1 P2 P3
Displaying Continual Input/Output

Use
There are two options for displaying continual input/output in the product planing table:
• In the subscreen Product view: Quantity graphic, the system displays the receipts and the
requirements in a graphic. Continual input or output is linear.
• In the Product view: Periodic, the system displays the continual input/output as a split
quantity if you have set the split quantities indicator. The receipt or requirement is then
split at the bucket borders and distributed over several periods.
Prerequisites
• In the user settings for the product planning table, you have set the split quantities
indicator on the tab page Product 1.
• In the production process model, you have set the indicator C for the display of continual
input/output. Master Data → Production Process Model.
• If you work with the iPPE, you have set the receipt type C for continual receipt in the
access object.

• In the dialog box, which opens when you choose Product heuristic, you have set when
the continual input or output is to take place in the Scheduling group frame. Set the
Available date indicator and, if necessary, a period factor.
Features
Three possible situations can occur with continual input/output. These are described below
using examples.
The products are: FERT01 (finished product),
HALB01 (assembly),
ROH01 (raw material).
1. Discrete Input – Continual Output
For the finished product FERT01, there is a discrete input of 1000 pieces on 10
August 2000 in the form of a purchase requisition from the distribution center. In
order to cover this requirement, a planned order for 1000 pieces is generated on
9 August 2000. For the product FERT01, the external procurement indicator has
been set in the distribution center location, the in-house production indicator has
been set in the plant location and the indicator “C” for continual has been set for
the output in the PPM for FERT01. The production duration for 1000 pieces is 2
days. There is a 1:1 relationship between each manufacturing level.
Without continual input/output, you would see the planned order for 1000 pieces
only on 9 August 2000. In the case of continual input/output, the system takes
into account the start date, finish date and production restrictions (capacity,
production time frame, breaks, and so on) and calculates the output quantity for
each time point on the graph between the start and finish date for the order. This
cannot be displayed to the second (Product view: Indiv.elem.), but only at bucket
level in the Product view: Periodic for the product. In the top graphic, you
therefore see a cumulative output quantity of 400 pieces for 8 August 2000 and
an output quantity of 600 pieces for 9 August 2000.
These two “continual” quantities form the input for the next planning level (input
for HALB01), where the continual output quantity is calculated using the same
principle and displayed.
1000
500
0 08.08.2000 09.08.2000
CW 32

P r o d u c t V ie w : P e rio d ic
Un 0 8 .0 8 .2 0 0 0 0 9 .0 8 .2 0 0 0 1 0 .0 8 .2 0 0 0
F E R T 0 1 / F i n is h e d P r o d u c t
A v a ila b le q u a n tity PC 1000
T o t a l r e q u ir e m e n t s PC
P u r c h a s e r e q u i s it i o n PC 1000
F E R T 0 1 / F i n is h e d P r o d u c t
A v a ila b le q u a n tity PC 400
P l n d . in d . r e q m t s PC
T o t a l r e q u ir e m e n t s PC 1000-
P la n n e d o r d e r PC 1000
D is t r ib u t e d PC 400 600
2. Continual Output - Continual Input
HALB01 is a dependent requirement for FERT01. The product HALB01 is

indicated as continual input in the PPM for FERT01 and as continual output in the
PPM for HALB01. Starting with the continual input quantities (dependent
requirements), the system generates continual output quantities for covering the
requirements. The symmetrical course of the cumulative requirements and
receipts in the graphic is a result of the 1:1 relationship between FERT01 and
HALB01.
1000
500
0 08.08.2000 09.08.2000
CW 32


Un 08.08.2000 09.08.2000 10.08.2000 11.08.2000
FERT01 / Finished Product
Available quantity PC
Total requirements PC 1000-
Dependent reqmts PC 1000-
Distributed PC 400- 600-
Planned order PC 1000
Distributed PC 400 600
3. Continual Input – Discrete Output
The product ROH01 is indicated as continual input in the PPM for HALB01 and
the continual dependent requirements for ROH01 come from this. In the product
master for ROH01, the procurement alternative is “F” for external procurement,
that means, the system generates 2 discrete purchase requisitions for 400 and
600 pieces.
1000
500
0 08.08.2000 09.08.2000
CW 32

Un 08.08.2000 09.08.2000 10.08.2000 11.08.2000
FERT01 / Finished Product
Available quantity PC
Total requirements PC 1000-
Dependent reqmts PC 1000-
Distributed PC 400- 600-
Purchase requisition PC 400 600

Access the Plan Monitor

Use
The plan monitor evaluates the current plan using key figures. It should be used on an
interactive basis with order-based applications such as CTM and PP/DS. You can use a key
figure profile to determine particular key figures for the evaluation of a plan.
For further information about the plan monitor, see: Plan Monitor [External].
Prerequisites
You have created a key figure profile. Supply Chain Monitoring → Current Settings → Define
Key Figure Profile. See also: Creating a Key Figure Profile [External].
If you set the use of the application data in the key figure profile for the planning version,
periods and business objects, the system calculates the figures also or only for objects that
you have selected in the navigation tree of the product planning table. If you do not want to
use any application data, define the objects, for which the system should calculate the figures,
directly in the key figure profile.
Procedure
1. On the tab page Profile in the user settings, use the input help to select a key figure
profile, which you have defined.
2. Access the plan monitor from the overview tree.
3. If you have set the use of the application data in the key figure profile, the system
calculates the figures for all resources or products that have been selected in the
navigation tree. If you want to restrict the selection, you can select one or more resources
or products in the respective subscreen.
Accessing the Production List

Use
From the product planning table, you can access and print a production list. Using the
production list, the employee in production can see how the resources are occupied, for
example.
Integration
You can access the production list from the Easy Access Menu and also from the Resource
View: Periodic and the Production View: Periodic.
Prerequisites
You must select one or more resources in the Resource View: Periodic or in the Production
View: Periodic.
Features
The production list displays the order quantities produced on the resources in a table
organized by days or shifts. You are provided with information on orders, activities and dates.
The production list contains the following information, for example:
• Resource description
• Quantities such as total quantity, yield, open quantity
• Availability dates

• Type of each activity as well as start and finish date

• Order status such as, released, partially backflushed or finally backflushed
• Backlog, that is the order quantity dispatched before the beginning of the production list’s
display period
Activities
Accessing the production list from the Easy Access Menu:
1. From the APO menu, choose Production Planning → Reporting → Production List or in
the Resource View: Periodic choose Further processing functions and then choose Print
resource schedule.
2. The start date of the period of examination is usually preset to the current date.
3. If, in the resource view, you selected a resource, this is preset in the Resource field.
4. You can select by resource or by line. If you choose to select by line, if necessary, enter
the profile of the characteristic view and the line resource.
5. Choose between displaying by order or by period. In the periodic display, the orders
which overlap several periods are displayed distributed over the periods.
The period is “shift” and the quantity to be produced is 120 pieces. The production
time is 8 hours in shift 1 and four hours in shift 2. This means 80 pieces are displayed
in shift 1 and 40 pieces are displayed in shift 2.
If you choose to display by period, choose a period using the input help. If you want to
display the order quantities that lie before the start date select Quantity before the start
date.
You can only display the production list in days or shifts.

6. You can also define sort criteria and you can choose an extended table display.
7. Choose Execute.
The production list is displayed.
Accessing the production list from the Resource View: Periodic or from the Production
View: Periodic
1. Select one or more resources in the Resource View: Periodic or in the Production View:
Periodic.
2. Select Further processing functions and then choose Print resource schedule.
3. The start date of the period of examination is usually preset to the current date. If
necessary, change the period of examination.
4. You can sort the production list by resources or by date.
5. Choose between displaying by order or by period (see above). If you choose to display by
period, choose a period using the F4 help. If you want to display the order quantities that
lie before the start date select Quantity before the start date.
You can only display the production list in days or shifts.

6. If you want to print the list without displaying it first, select the Print immediately indicator.

Examples
Use
Profiles have been defined in Customizing for the various planning processes. Depending on
which type of production you use and which functions you work with, you can load one of the
profiles. That is, you can copy a profle to your user settings and change it as necessary.
All proposed profiles exist of a useful combination of the planning table views for the
corresponding planning type so that, at a glance, the planner can see the planning situation
and change it, if necessary. For several profiles, settings have been maintained for the
detailed scheduling planning board, heuristic profiles defined and settings have also been
made for the profile General Settings. In the total settings, you can define which profiles are
selected for each planner.
The profiles are only used as a reference and you can change them as necessary in your
user settings. That is, you can redefine which views are grouped together.
Features
As well as the standard profile SAP001, profiles also exist for the following planning types:
• Production Planner – Repetitive Manufacturing [Page 357]
• Production Planner – Model Mix [Page 358]
• Production Planner – Make-to-Stock Production [Page 358]
• Procurement Planner [Page 358]
Activities
1. In the user settings, choose Fetch variant from Customizing and select the profile that
corresponds to your planning function.
2. Choose Continue.
See also: Loading and Modifying Profiles from Customizing [Page 328].
REM Production Planner

This planner plans the loading of the lines or the resources. He selects the products
according to the resources available and tries to create an optimal plan. In the navigation tree,
he usually groups according to resources.
The chart profile REM production planner contains the following views:
• Resource View. Periodic: In this view, the REM planner sees the capacity load of the
resources and the availability of the products produced on the resources. He can
recognize overloads.
• Product View: Periodic: In this view, the planner can see material shortages in the Avail.
qty row and backlogs in the Overdue column. He can immediately correct problem
situations in the product view or, if necessary, he can access a suitable heuristic. See
also: Planning with REM Heuristics [Page 217].
The Repetitive Manufacturing Standard Profile is preset as the planning table profile for
the detailed planning planning board.

Model Mix Production Planner

If you work with iPPE and Model Mix Planning [Page 126], you can use this profile.
In model mix production, many configured products are often manufactured together on one
production line. The production planner can use the product planning table for medium-term
planning and for monitoring the model mix production. The planner is usually responsible for
one or several lines. Therefore, he usually groups the navigation tree according to lines and
also accesses the product planning table using lines from the selection screen.
The heuristic profile MMPand the MMP profile for the profile General Settings are preset in
the total profile, production planner model mix. Here, grouping according to the production
line is preset in the navigation tree.
The chart profile, production planner model mix contains the following views:
• Product View: Quantity Graphic: In this view, the planner sees the availability situation in
variant production.
In make-to-order production, the planner should replace this chart with the
Production View: Individual Elements as this view provides more information on
individual orders – for example the order number, account assignment, resource,
dates and so on.
• Production View: Periodic: In this view, the planner can see the quantity to be produced
per period on the line resource per product/variant. The planner also has the option of
displaying the quantity per characteristic value periodically. From this view, the planner
can also branch to Sequencing.
MTS Production Planner

A separate profile is available for this planning type – especially for production by lots. The
planner’s main task is to ensure that the resource is well and consistently loaded. He can do
this using the Detailed Scheduling Planning Board and the Product View: Individual Elements.
The chart profile MTS production planner groups the following views:
• Detailed scheduling planning board: Shows the resource schedule graphically. The
planner can move the orders per drag & drop.
• Product View: Individual Elements: In this view, the planner can check and change the
planning situation.
Procurement Planner
The procurement planner in external procurement must be able to recognize bottlenecks and
problem situations in production and to create purchase requisitions or schedule lines or a
scheduling agreement release for the suppliers. The procurement planner groups the
navigation tree by suppliers or by planners and, in the initial screen, selects by supply source.
The chart profile procurement planner groups the following views:

• Alert Monitor. Here the planner recognizes the material shortages of the selected product.
By double-clicking a product in the Alert Monitor, the planning situation is displayed in the
Product View: Individual Elements.
• Product View: Periodic: Here, the planner can create and change purchase requisitions
and schedule lines. By choosing Processing sched. agrmt releases, the planner can
access detailed information on scheduling agreements.
Customer-Specific Enhancements
Use
Two options are available for making customer-specific enhancements which you can use to
insert your own charts in the product planning table and your own rows in the Product View:
Periodic and the Resource View: Periodic.
Inserting Additional Charts [Page 359]
Inserting Additional Info Rows [Page 359]
Inserting Additional Charts

Use
You can use this function to insert additional charts into the product planning table. To do this,
two templates exist in the system for displaying master data for the product and the resource
which you can copy and change as necessary. For example, you can calculate your own key
figures. You find the templates in the function group /sapapo/pt_scr_template. They refer to
screen 1000 (product master data) and 2000 (resource master data).
Both screens are integrated in the product planning table environment. The products or
resources selected in the navigation tree appear in these screens and you can use them as
templates.
Procedure
1. Copy the template to the customer’s name space in a new function group and enhance it
as necessary.
2. Enter your own chart in table /sapapo/pt_frdyn to link it to the product planning table.
You can find more information in the top include /sapapo/lpt_scr_templatetop.
Inserting Additional Info Rows

Use
You can use a Business Add-In (BADI) to show further information rows in the Product View:
Periodic and in the Resource View: Periodic of the product planning table. You can use the
existing example coding as a template.

Procedure
1. A detailed example coding exists for this Business Add-In which you can copy and modify.
By choosing Goto -> Example coding -> Display in the BADI Builder, you access the
method /SAPAPO/IF_EX_PPT_INFOROWS~PT_USEX_INFOROWS where you can access
the example coding by double-clicking.
2. Define further information rows in table /sapapo/ptcrows in the maintenance view
/sapapo/vptcrows and save your entries.
3. Create an implementation for the Business Add-In, if necessary, using the example coding
as a template.
Scheduling with the Detailed Scheduling Planning

Board
Purpose
This process describes how you schedule interactively with the help of the detailed
scheduling planning board [Page 362] in order to solve scheduling problems at resources; for
example, problems with dates and sequencing problems.
Prerequisites
SAP issues the detailed scheduling planning board with standard settings (for example, for
configuration or layout). If you want to configure a detailed scheduling planning board for your
specific planning requirements, you must execute the relevant settings. For more information,
see profile maintenance [Page 388] and the Implementation Guide (IMG) for Production
Planning and Detailed Scheduling.
Process
The process is shown in the following graphic:

Call
Callup
up
planning
planning
board
board
Identify
Identify
planning
planning
problems
problems
Solve
Solve
Update
Update planning
planning
planning
planning problems
problems
Save
Save
planning
planning
1. Call up the detailed scheduling planning board directly in the Production Planning area
menu [Page 384], in order processing [Page 385], or in the product planning board [Page
386].
You perform simulative planning in the detailed scheduling planning board − as you
do for every application in interactive production planning (for example, product
planning table or order processing): When calling up the application, the system
automatically generates a copy of the current planning version [External], known as a
simulation version [External]. You schedule in this simulation version based on the
status of the planning version at the time the application is called up.
2. Check the schedule and identify the scheduling problems [Page 391]
The following are helpful:
− The Alert Monitor [External]
− The Plan Monitor [External]
− Various evaluations, for example, resource overload [Page 399] or work-in-process
stocks [Page 397]
3. Try to solve the scheduling problems [Page 404] by doing the following:
− Scheduling or rescheduling operations or orders using Drag&Drop [Page 406]
− Rescheduling or scheduling operations or orders with the help of detailed scheduling
heuristics [Page 413], for example, with sequencing [Page 415] or with backlog
rescheduling [Page 415]

− Changing the capacity and planning parameters of the resources [Page 421]
− Creating or changing orders [Page 421]
− Optimizing the schedule [Page 227]
4. Update the simulation version as required [Page 422]
The planning version may change while you are processing the simulation version
using the detailed scheduling planning board when other planners confirm operations
or create orders. If you want to take the current planning status into account in the
simulation version, you must update the simulation version. During the update, the
system merges the planning data from the planning version with the data in the
simulation version that has a higher priority than the planning data in the simulation
version.
5. Save the schedule [Page 423].
The planning version remains unchanged by your scheduling activities in the
simulation version until you copy the planning data from the simulation version to the
planning version. Because you have changed the planning version in the meantime
(see above), the system does not simply copy the simulation version to the planning
version when you save, but merges the planning data of the simulation version with
the planning version. In doing so, the system only adopts planning data from the
simulation version into the planning version when the planning situation in the
planning version does not have priority.
You rescheduled an operation in the simulation version on another date. In the

meantime, the operation is confirmed in the planning version. If you adopt the
simulation version into the planning version, the confirmation of the operation has
priority over the rescheduling; that is, the change of date is not copied into the
planning version.
In the directly called up detailed scheduling planning board, you can also save the
simulation version without changing the planning version. You can process the saved
simulation versions at a later point in time with the detailed scheduling planning
board.
Detailed Scheduling (DS) Planning Board

Definition
Configurable graphical planning interface for the interactive detailed scheduling [Page 62] of
resources and orders in Production Planning and Detailed Scheduling.
Use
You use the detailed scheduling planning board to do the following:
• To graphically represent the scheduling situation
You can graphically display different aspects of scheduling in the charts [Page 364] of
the detailed scheduling planning board, for example, you can display the situation of
operations on resources with regard to time, and the development of the resource
load or pegging relationships between orders with regard to time.
• To interactively solve scheduling problems
You can perform interactive scheduling in the detailed scheduling planning board to
solve scheduling problems such as sequence or date problems on resources [Page

404]. Various scheduling functions and heuristics [Page 413] are available in addition
to manual scheduling with Drag&Drop [Page 405].
The detailed scheduling planning board is integrated in different Production Planning
applications. You can call up the detailed scheduling planning board [Page 383]
• Directly in the Production Planning area menu [Page 384]
• In order processing [Page 385]
• In the product planning table [Page 386]
You simulate planning in the product planning table. For more information, see scheduling
with the detailed scheduling planning board [Page 360].
Structure
see the Detailed Scheduling Planning Board [Page 388] and the Implementation Guide (IMG)
Configuration
A planning board can consist of up to eight charts [Page 364] arranged over one another. You
specify the configuration and layout of the DS planning board using a planning board profile.
Display period and planning period

The DS planning board displays the schedule for a time period defined by the user. You can
change the schedule for a particular time period within the display period, that is, in the
planning period [Page 85]. How you specify the time periods depends on where you call up
Displayed objects
Which objects are displayed in the DS planning board depends on where you call up the DS
planning board. For more information, see Selection of the objects to be displayed [Page 368]
Objects that can be scheduled

You specify which objects (resources, products) you can schedule in interactive Production
Planning and Detailed Scheduling using a Propagation range [External]. You can enter
resources and products in the propagation range. The resources in the propagation range are
relevant for resource-related scheduling in the DS planning board; the products are relevant
for product-related scheduling in interactive scheduling, for example, order processing. You
cannot change the schedule for objects outside of the propagation range.
Integration
The following functions and tools are available in the DS planning board:
• Detailed scheduling functions
When you schedule operations or orders in the DS planning board, the system
automatically uses the functions from detailed scheduling [Page 62]. For example, it
can automatically adjust the setup times [Page 77] or consider the blocks in block
planning [External]. You control detail scheduling with the help of detailed scheduling
strategies [Page 82] that you specify in a strategy profile. You can change the
detailed scheduling strategies at any time.
• Optimization
To optimize the schedule, you can call up the optimization [Page 227] in the DS
planning board.
• Interactive block maintenance

You can call up block maintenance in the DS planning board and interactively change
blocks.
• Campaign planning
You can process campaigns [Page 425] in the detailed scheduling planning board.
• Alert Monitor
You can call up the Alert Monitor [Page 392] at any time in the DS planning board to
display scheduling problems.
• Plan Monitor
You can call up the plan monitor [Page 393] in the DS planning board to evaluate the
planning quality according to user-defined criteria and key figures.
• Legend
The meaning of the various graphical representations for rows, orders and operations
in the DS planning board is explained in a legend [Page 366]. You can also change
the display of rows and graphical objects [Page 380] in the legend.
• Simulation versions
In the directly called up detailed scheduling planning board, you can also save the
simulation version without changing the planning version. To continue editing a
simulation version at a later date with the DS planning board, call up the simulation
version in the DS planning board area menu.
Chart
Definition
Independent screen within the detailed scheduling planning screen [Page 362]. A planning
board can be made up of up to eight charts arranged over one another.
Use
A chart shows for selected objects
• The situation of activities, operations or orders over time as a Gantt chart
• The situation of activities, operations and orders with the time relationships and pegging
relationships between the operations and orders over time as a Gantt chart
• Resource load, fill level or product stock curves that show the development of the
resource load, fill level or product stock over time
Structure
You define the number, content and layout of the charts in the detailed scheduling planning
board in the planning board profile. A chart consists of the following parts:
• Title row
The title row contains the name of the chart.
• Object rows with a table section and a diagram section
Descriptive data is displayed in the table section of a row; for example, name and
location of the resource for which the position of the operations over time are
displayed in the diagram section, or the name of the product to which the product
stock is displayed in the diagram section. The following chart types are possible:

− In a resource chart, resource-specific fields are displayed in the table section.

− In a product chart, product-specific fields are displayed in the table section.
− In an order chart, order-specific fields are displayed in the table section.
− In an operation chart, operation-specific fields are displayed in the table section.
You can choose to display the following objects in the diagram section of a row:
− Graphical objects [External] that show the situation of activities, operations, or orders
over time
− Product stock, fill level or resource load curves
You can display activities, operations, or orders with particular attributes in a chart.
For example, you can display scheduled operations in one resource chart, and only
deallocated [Page 412] operations in another (pool chart).
You can define charts with curves or network views as:
− Static charts that are always displayed in the detailed scheduling planning board
− Dynamic charts that you can show or hide in the planning board for selected objects
• Time scale
All charts in the planning board display the same time period in the diagram section.
You can shift this time period, for example, by scrolling in all the charts
simultaneously. For the diagram section of each chart, there is a time scale that is
made up of three independent time scales for the pre-evaluation period, the planning
period [Page 85] and the post-evaluation period. The scales and formatting (color,
font type) of the time scales are preset by SAP. You can change these settings for
each chart in the detailed scheduling planning board by choosing Settings. If you
change the scale of a time scale in a chart, this scale change automatically adjusts
the corresponding time scales for the other charts, so that all charts always have the
same scale.
Display of Rows and Graphical Objects

In the planning board profile, you specify the display type for rows in the table section and
graphical objects in the diagram section for each chart using decision tables. The display is
defined independently of the displayed objects. For example, the table section of a row for a
bottleneck resource can be automatically represented by a red background, and confirmed
operations in the diagram section by a green bar. You can change the display of table rows
and graphical objects using the legend. The meaning of the graphical representations is
explained in the legend [Page 366].
For more information, see:
• Selection of objects to be displayed [Page 368]
• Overview of Chart Settings [Page 366]
• Maintain DS Planning Board Profiles in the Implementation Guide for Production Planning
and Detailed Scheduling
Integration
You can reschedule activities, operations, and orders [Page 404] in the charts. For manual
rescheduling [Page 405], you specify which scheduling functions the system performs if you
move an activity, operation, or an order using Drag&Drop in the planning board profile for
each chart.

Legend
Definition
Modeless dialog box, in which the meanings of the row display and graphical objects
(activities, operations and orders) for the first four static charts [Page 364] of the detailed
scheduling planning board [Page 362] are explained.
Use
You can change the display of rows and graphical objects [Page 380] in the legend.
Structure
The legend is configured like the planning board. For a chart in the planning board there are
two charts in the legend; one for the table section and one for the diagram section.
• The following is displayed in the chart for the table section:
− The names of the row formats with which the rows are displayed
− The names of the fields that are displayed in the columns of the table section
• The following is displayed in the chart for the diagram section:
− The names of the various graphical objects [External] that are displayed in the
planning board
− The fields that are used for labeling the graphical objects
− The graphical representation of the graphical objects
Overview of Chart Settings

The structure and layout of charts [Page 364] in the detailed scheduling planning board [Page
362] are defined by a planning board profile [Page 389]. The following tables give an overview
of the settings.
General Settings
Setting Comments
Title Short description of the chart
Charts You can define up to eight charts for the planning board.
The following chart categories are available:
• Resource chart
• Product chart
• Order chart
• Operation chart
Height of chart
Scheduling function performed by You have the following options:
the system when you manually
reschedule an activity, operation, • Schedule/Reschedule
or order using Drag&Drop [Page

405] • Deallocate
• No action
Settings for the table section of a chart

Setting Comments
Field selection for the columns The chart type specifies which fields can be selected for the table
section.
Column title
Sorting of columns
Dividing line between columns
Column widths
Row format (font, color) Dependent on displayed information.
Settings for the diagram section of a chart

Setting Comments
Displayed objects [Page 368] The following are possible, depending on the chart type:
• Activities
• Operations
• Orders
• Product stock, resource load, fill level
• Time relationships between operations and pegging
relationships between orders
The color of the lines used to represent the objects is set by SAP:
• Blue: Time relationship
• Green: Dynamic pegging relationship
• Red: Fixed pegging relationship
Graphical presentation of the You define the graphical presentation depending on the
activities, operations and orders characteristics of the operations and orders; for example, depending
and their labeling (graphical on status.
objects [External])
You can change the graphical presentation using the legend [Page
366].
Dividing line between rows
Labeling non-working times Non-working times are highlighted in light gray in the diagram
section. Working times are shown in white
Automatically expanding multiple Various activities, operations, and orders may overlap, that is, the
loading graphical objects may overlap within a row. You can choose a
multiple row display for this case.
You can also expand the multiple loading [Page 381] in the detailed
Step for displaying the date and Changeable in the planning board
for determining the desired
scheduling date [Page 94] when
manually scheduling and

rescheduling activities, operations,

and orders [Page 406]
Vertical orientation lines that are
shifted along with the tip of the
cursor (time line)
Selecting alternative resources This function is very performance-intensive.
when manually scheduling or
rescheduling activities, operations,
and orders [Page 406]
Displaying campaigns A campaign is emphasized by a narrow lilac-colored bar. The bars
are located behind the graphical objects for the operations which
belong to the campaign.
Settings for the time scale

Setting Comments
Period pattern Changeable in the planning board
Formatting and scale Changeable in the planning board
For more information, see Zooming the Planning Board [Page 374].
For more information, see Maintain Planning Board Profiles in the Implementation Guide for
Printing
Use
In the DS planning board [Page 362] you can print individual charts from the planning board.
Activities
You can print the desired charts from the DS planning board by choosing APO DS planning
board → Print.
Selection of Objects to be Displayed

Use
When you call up the detailed scheduling planning board [Page 362], the system
automatically selects the resources, products, orders, and operations that are displayed in the
detailed scheduling planning board. The system displays rows in the charts [Page 364] or
graphical objects [External] in the diagram section of the rows for the relevant activities,
operations, or orders.
Features
You must distinguish between the following objects when determining the objects to be
displayed:

• Objects that can be displayed in the detailed scheduling planning board

• Objects that are transferred to the detailed scheduling planning board
• Objects that are actually displayed
Objects that can be displayed in the detailed scheduling planning board

The following objects can be displayed in the DS planning board:
• Resources with a capacity that is scheduled on an exact time scale:
− Single-activity resources [External]
− Single-mixed resources [External]
− Multi-activity resources [External]
− Multi-mixed resources [External]
• Orders in Production Planning and Detailed Scheduling (PP/DS) and their activities and
operations
• Orders in Supply Network Planning (SNP) and their activities and operations
You can determine according to your requirements, that either only activities, operations and
orders for PP/DS or for SNP [Page 370] are displayed in a product, order or operation chart.
Objects that are transferred to the detailed scheduling planning board

When you call up the detailed scheduling planning board in order processing [Page 385] or in
the product planning table [Page 386], the system determines these objects depending on the
context. If you call up the detailed scheduling planning board directly [Page 384], the object
selection is user-defined. This is displayed in the following table.
Calling up the Planning Board Objects Transferred to the Planning Board

Directly in the Production Planning menu Objects that you have defined using the work
[Page 384] area [Page 371]
In order processing [Page 385] • The order you are currently processing
• All orders from the corresponding pegging
structure
• The resources on which the orders are
processed
• The products that are produced from the
orders
In the product planning table [Page 386] • The resources and products from the
navigation tree in the product planning
table [Page 334]
• The orders for these resources and
products
You can display rows for the transferred objects as follows in the various charts:
• You can display a row for each resource transferred in a resources chart.
• You can display a row for each product transferred in a product chart.
• You can display a row for each order transferred or for each operation of a transferred
order in an order chart.

You can display the activities, operations, or orders for the object in a row with their place in
time in the diagram section of a row; these are represented by the corresponding graphic
objects [External].
• You can display all the operations that are processed on these resources in the diagram
section of a resource row.
• You can display all the orders available for this product in the diagram section of a
product row.
• You can display the order or order operations in the diagram section of an order or
operation row.
Objects that are actually displayed

You specify which of these objects are actually displayed in the detailed scheduling planning
board, as well as how they are displayed using the decision tables in the planning board
profile for each chart. You can use the decision tables to suppress the display of rows of
graphical objects for random objects; the system uses the decision tables to filter the objects
to be displayed from the objects transferred to the detailed scheduling planning board. For
more information on decision tables, see the implementation guide (IMG) for the planning
board profile.
• You can interactively hide objects [Page 380] in the detailed scheduling planning board.
• In the propagation range [External] you specify for which resources you can change the
schedule.
Specifying the Order Category to be Displayed

Use
By default, the DS planning board [Page 362] displays activities, operations and orders for the
following order types:
• Orders from Production Planning and Detailed Scheduling (PP/DS orders)
• Orders from Supply Network Planning (SNP orders)
Thus, PP/DS and SNP activities or operations are displayed by default in a resource chart
[Page 364] in the DS planning board for a single-mixed resource [External] or a multi-mixed
resource [External], in a product chart for a PP/DS and SNP product order.
You can define according to your requirements, that either only activities, operations and
orders for PP/DS or SNP are displayed in the product, order or operation charts in the DS
planning board.
Procedure
1. In the SAP menu, choose System → User defaults → Own data.
2. Enter the SET/GET parameter /SAPAPO/CDPS_APPLI in the Parameter tab page under
Parameters.
3. For this SET/GET parameter, you enter the value for the desired order category:
SET/GET parameter values for the order categories to be displayed

Display Value

Activities, operations and orders from PP/DS CDPS

Activities, operations and orders from SNP SNP
4. Save the data.
Result
The next time the DS planning board is called up, it only displays the desired activities,
operations and orders in a product, order or operations chart. In a resource chart, objects
from SNP and PP/DS are still shown for mixed resources.
If you want to display both order categories again in all charts, remove the SET/GET
parameter from the parameter table.
Work area
Definition
User-defined selection of resources, products, and orders for the directly called detailed
scheduling planning board [Page 384].
Use
With the help of the work area, the system determines the resources, products and orders
which can be transferred to the detailed scheduling planning board and displayed.
You specify for which of the transferred objects the system displays rows or
graphic objects using the decision tables in the planning board profile; you can
suppress the display of rows or graphic objects for selected objects here. For
more information, see the implementation guide (IMG) for the planning board
profile.
For each transferred object, a row can be displayed as follow:
• You can display a row for each resource transferred in a resources chart.
• You can display a row for each product transferred in a product chart.
• You can display a row for each order transferred or for each operation of a transferred
order in an order chart.
You can display the activities, operations, or orders for the object in a row with their place in
time in the diagram section of a row; these are represented by the corresponding graphic
objects [External].
• You can display all the operations that are processed on this resource in the diagram
section of a resource row.
• You can display all the orders available for this product in the diagram section of a
product row.
• You can display the order or order operation in the diagram section of an order or
operation row.

Structure
You define the resources, products, and orders for the work area in the various views:
• You define resources in the resource view.
• You define products in the product view.
• You define orders in the order view.
In each view, the system provides fields specific to the view as selection criteria; for example,
in the resource view, it provides the resource name and resource type. Within a view, you can
group the selection criteria into various sets. The following is valid for the interaction between
the selection criteria:
• A logical AND links the selection criteria within a set.
• A logical OR links the selection criteria for various sets.
Alternative Displays
From the objects that you define in the various views for the work area, the system
determines the objects rows in the charts. You can specify for each view individually:
• Whether the system only displays rows for the objects that you have defined in the
respective view
• Whether the system determines the object rows to be displayed in the chart from the
resources:
− That you have specified in the resource view, and
− That the system determines from the products in the product view and from the
orders in the order view
These alternatives are described in the following sections.
Display Rows in the Chart for Objects Specified in the View

When you specify this for a view, only rows for those objects that you defined in the view are
displayed, in other words:
• Only rows for those resources that you specified in the resource view are displayed in a
resource chart.
• Only rows for those resources that you specified in the product view are displayed in a
product chart.
• Only rows for those orders that you specified in the order view are displayed in an order
chart.
Display Rows for Objects in the Chart that were Determined from the Resources of all
Views
The system determines the object rows to be displayed in the chart from the resources:
• That you have specified in the resource view, and
• That the system determines from the orders in the order view and from the products in
the product view
To do this, the system determines all orders from the products in the product view
that belong to these products. From these orders or from the orders in the order view,
the system determines all operations, and from these operations, resources.
These resources determine the object rows in the different charts as follows:
• You can display rows for these resources in a resource chart.
• You can display rows for orders that have operations on these resources in an order
chart.

• You can display rows for products which have orders with operations on these resources
in a product chart.
Objects in an Operation Chart

The system displays all operations with an operation on the resources determined for the
resource chart in the rows of a static operation chart.
In the case of the second display option (determine displayed objects from all
resources in the work area), each chart generally contains a lot more objects than
in the case of the first alternative. The system has to read the objects to be
displayed when configuring the planning board. Due to performance reasons, you
should only choose the second alternative when you really require the associated
information in the planning board.
For the same reason, you should define the planning board − as in the standard
system − without a static operation chart. Instead of this, you can use a dynamic
operation chart that you can display and hide in the planning board for selected
operations or orders; it only displays the selected operations or operations for the
selected orders.
You define work areas in Customizing for Production Planning and Detailed Scheduling by
choosing Profiles. When you call up the planning board, you can either change the work area
or specify another one.
You can interactively hide objects [Page 380] in the detailed scheduling planning board.
Segmentation of the Display Period

Use
You can divide the display period of the detailed scheduling planning board into smaller time
segments to improve performance when calling up the detailed scheduling planning board
[Page 362]. When you call up the planning board, the system only loads the objects for the
segments that lie in the visible time segment of the detailed scheduling planning board. Only
when you change the visible area here, for example, by scrolling or by changing the scale of
the time scale, does the system load the object data of the additional segments.
Segmentation of the display period is strongly advised for large display periods with large
amounts of data,
and is relevant for the directly called detailed scheduling planning board [Page 384] as well as
the detailed scheduling planning board that you call up in order processing [Page 385]. You
cannot use segmentation for the detailed scheduling planning board called up in the product
planning table [Page 386].
Features
You define the number of segments into which the display period is divided in the time profile.
The duration of a segment is the number of days in the display period divided by the number
of segments.
You configure the visible area in such a way in the detailed scheduling planning
board for a segmented display period that it starts with the first graphical object of
the already loaded segments or with the last graphical objects of the already
loaded segments using the functions Edit → Visible time segment → Begin with
first graphical object or Finish with last graphical object. If the system has not

loaded all segments of the display period, it may be that you do not see the first
or last graphical object in the display period.
Navigating
Setting the Visible Time Segment

Use
You can set the start of the diagram section in the DS planning board [Page 362], that is, the
start of the visible time segment, to a particular date; for example:
• To the current date
• To a date specified by you
• To the start date of the first graphical object in a selected row
You can set the end of the diagram section to the finish date of the last graphical object in a
row.
The system automatically displays a vertical line in the diagram section for the
current date.
Procedure
Using the DS planning board menu
Choose the required option using Edit → Visible time segment.
If you want to set the start of the visible segment to the start date of the first graphical object
in a row or the end of the diagram section to the finish date of the last graphical object in a
row, you select beforehand the table section for this row or a random graphical object in this
row.
Using the mouse

• Pull a frame in the diagram section of the chart by pressing simultaneously the STRG key
and the left mouse button. When you release the mouse button, the start of the diagram
section is set to the date that is defined by left frame border.
• You can click on a table row using the right mouse button and, using the appropriate
menu option in the context menu, you can:
− Set the start of the diagram section to the start of the first graphical object in the row
− Set the end of the diagram section to the end of the last graphical object in the row
Zooming the DS Planning Board

The following table contains a summary of how you can change the scale of the display in the
DS planning board [Page 362].

Function Procedure
Gradually zoom into or out of the Choose Settings → View → Zoom
contents of the whole DS in or Zoom out
planning board
Switch between the current Choose Settings → View → Full
display and the overview of the screen on/off
whole display period in the
diagram section
Change the time scale of the You have the following options:
diagram section
• Choose the desired scale using Setting →
View; for example Week or Day.
• Using the right mouse button, click on the
time scale of any chart and choose the
desired scale; for example, daily scale or
weekly scale.
• While holding down the CTRL key and
pressing the left mouse button, pull a frame
around the area in the diagram section that
you want to zoom in on.
You can change the basic
dimensions (width, height) and the
formatting (color, labeling) of the
time scale by choosing Settings →
Time scale.
Changing the Relative Size of the DS Planning Board

Section
Use
In the DS planning board [Page 362], you can change the relative size of the charts and the
relative size of the diagram section and table section. Sections that are no longer visible can
be reached by scrolling vertically or horizontally.
Procedure
1. Place the cursor on the borderline between two screen sections.
The cursor changes into a double arrow.
2. Press the left mouse button and move the borderline to the desired position.
3. Release the mouse button.

Sorting Rows
Use
You can sort the rows in a chart in the DS planning board [Page 362] according to various
sort criteria; for example, in an order chart, you can sort according to the start date of the
orders.
Procedure
Choose Edit to select the desired sort functions:
• By choosing New sort, you sort the rows according to the currently set sort criteria
• By choosing Change sort, you define new sort criteria and sort the rows accordingly.
Result
The rows are sorted.
Searching for objects

Use
In the detailed scheduling planning board [Page 362] you can
• Search for an order in the diagram section
• Search for a row or a field with a specific text in the table section
Procedure
Searching for a row or a field in the table section
1. Select any row in the table section.
2. Choose Edit → Find.
You reach a dialog box, in which the table rows displayed in the planning board are
listed alphabetically.
3. Select the desired table row in the list
You do not have to scroll through extensive lists: If you enter a table row text or the
first characters of a table row text as a search string and press the return key, the list
will go to the first table row which contains a corresponding table row.
4. Choose Continue.
The system displays the part of the DS planning board with the desired row.
Search for an order in the diagram section

1. Select any graphic object.
2. Choose Edit → Find.
3. Enter the number of the desired order.
4. Choose Continue.
5. The system selects the desired order and its operations in all charts.

If you don’t mark any objects in the planning board, you can reach the order
search via Edit → Search.
Displaying and Changing Objects

Use
You can display, create, or change the following objects or certain planning data for these
objects in the detailed scheduling planning board [Page 362]:
Object Display Create Change Delete
Resource x x
Order x x x x
Product x
Operation x x
To change the planning situation, you can do the following in the planning board:
• Change the working times of a resource
• Create new orders
• Reschedule operations on an alternative resource, or deallocate [Page 412] operations
Procedure
To call up the desired object:
• Double-click on the object, or
• Select [Page 378] the object and choose Goto → <Object>
Result
You go to the display or maintenance for the object.
To return to the DS planning board, choose Back.
• When you have created or changed an order, you must first update the planning board
[Page 422] so that you can view the changed situation. If you have changed an order, you
do not need to update the planning board.
• If you have made changes to resource data, the system copies these changes to the
simulative scheduling function in the planning board. The changes are simulative until you
copy the simulation version to the planning version. The system then saves the changed
resource data in the resource dependent on the planning version.
For more information, see scheduling with the detailed scheduling planning board [Page 360].
Handling Objects

Selecting Objects
Use
You select objects in the DS planning board [Page 362]:
• Before you execute scheduling functions on them; for example, before rescheduling
operations or orders
• To highlight objects
Prerequisites
In the DS planning board profile or in the DS planning board under Settings→ Select, you
specified:
• Which objects can be selected in the DS planning board; for example, only objects in the
diagram section, or all objects
• How the selection is displayed; for example, using colors or frames
You specify the selection color in the DS planning board profile.
Procedure
How you select and deselect objects is summarized in the following table:
Objects How to select the objects

An activity, an operation, a table row Click on the object.
An activity group, operation group, order While pressing the SHIFT key, click on the objects
group or press the left mouse button and pull a frame
around the objects.
Several table rows Click on the objects, while pressing the SHIFT key.
All objects
All objects in the chart in which the cursor is
positioned
All graphical objects for the selected table
rows
Choose Edit → Select, and then the desired
All table rows for the selected graphical selection function.
objects
Highlighted objects
All operations and orders belonging to the
selected operation or order
same block as the selected operation or
order
same campaign as the selected operation or
order
Objects How to undo the selection
An activity, an operation, a table row Press the SHIFT key and click on the object.
All objects Choose Edit → Select → Deselect all.

For more information, see Highlighting Objects [Page 379].
Highlighting objects
Use
If you want to highlight selected activities, operations or orders in the diagram section of the
detailed scheduling board [Page 362] , you can do so by using colors. The objects are
allocated colors that are defined by SAP.
Procedure
Select [Page 378] the operation or order, and choose Edit → Highlight in color.
Result
The operation or order is highlighted in color. If you want to remove the highlights, choose
Edit → Undo colored highlights.
You can select highlighted objects in order to execute a scheduling function on them (for
example, Deallocate) by choosing Edit → Select.
You can also only label those objects for which alerts exist [Page 393].
Highlighting Objects with Alerts

Use
In the diagram section of the DS planning board [Page 362], you can highlight the activities,
operations and orders for which there are alerts. The objects are highlighted accordingly,
depending on whether an error, a warning or information exists.
Prerequisites
You have set the following in the detail screen for the planning board profile:
• Which alerts are relevant for this highlighting function
You use a PP/DS alert profile [External] for this purpose. You define the PP/DS alert
profile in the SAP Easy Access menu under Supply Chain Monitoring → Alert
Monitor.
• How the graphical objects affected by alerts are highlighted
For more information, see the Implementation Guide for the DS planning board under
Maintain planning board profiles.
Procedure
Choose Extras → Alerts → Display.
To remove the highlights, choose Extras → Alerts → Hide.
You can also display alerts in the alert Monitor [Page 392].

Hiding objects
Procedure
Select [Page 378] the row with the object in the table section of the detailed scheduling
planning board [Page 362] or the graphical object [External] in the diagram section as follows,
and choose Edit → Hide object:
• To hide a resource, select the row with this resource in the table section of a resource
chart, a resource load chart, or a fill level chart. The system hides the resource rows of all
resource and resource load charts.
• To hide a product, select the row with this product in the table section of a product chart
or product stock chart. The system hides the product rows of all product and product
stock charts.
• To hide an order, choose
− the row with the order or a row with an operation of the order in the table section of
the order or operation chart
− the graphical object for the order or for an operation of the order in the diagram
section of any chart
The system removes the rows and graphical objects representing the order or an
operation of the order from all charts.
Result
When you update the planning [Page 422], the hidden objects are displayed again in the
Changing the Object Display

Use
In the legend [Page 366] for the detailed scheduling planning board [Page 362], you can
• Change how rows are displayed in the table section
• Change how graphical objects [External] are displayed (activities, operations, and orders)
• Change the format for labeling the graphical objects
Procedure
1. Choose Extras → Legend in the planning board.
The system displays the legend as a non-modal dialog box, that is, while the legend
is open, you can continue working in the planning board.
2. Double click on the appropriate area of the legend:
If you want to change: Double click on the following area of the legend:
The format of a table row In the table section of <Chart> (table section), on the
row where the row format has to be changed

The graphical representation of In the diagram section of <Chart> (diagram section), on

the graphical object the graphical representation of a graphical object to be
changed
The format of the labeling for a In the table section of <Chart> (diagram section), on
graphical object the row where the graphical object has to be changed
The maintenance screen for the row, graphical object, or labeling appears, and you
can change the settings.
3. To save the changed settings in the current planning board profile, choose Save.
You cannot change SAP standard profiles.
4. Choose Exit.
The legend appears again.
− The changed settings are displayed in the legend for graphical objects, regardless of
whether you have saved the settings. When you close the legend, you can decide if
you want to adopt the changed settings in the planning board.
− Changed settings for table rows and labeling only become effective the next time you
call up the planning board. They are therefore not immediately displayed in the
legend or in the planning board.
Exploding and Hiding Multiple Loading

Use
The graphical objects [External] for activities, operations, orders or campaigns can overlap in
a line in the diagram section of the DS planning board [Page 362]. A resource can, for
example, be loaded with several operations at the same time. The system displays multiple
loading by underlining the overlapping objects in green.
You can explode multiple loading on the DS planning board; that is, you can choose a display
with multiple lines, or you can hide it by choosing a single line display.
SAP sets the color of the line used to highlight the overlaps; you cannot change
this color.
Prerequisites
If the system is to interpret objects that immediately follow one another as multiple loading,
you set the Identical date indicator in the detail screen for the DS planning board.
Procedure
Automatically expanding multiple loading
You set the Automatic expand indicator in the detail screen for the DS planning board.
When you call up the DS planning board, multiple loading is automatically expanded.

Expand multiple loading directly in the DS planning board

1. Select the rows for which you want to expand multiple loading.
2. Choose Edit → Multiple loading → Expand.
The system displays new rows for the overlapping objects.
Hide multiple loading

If you want to switch from a multiple row display to a single row display, choose Edit →
Multiple loading → Hide.
Hiding and displaying non-working times

Use
You can display or hide the regular non-working times (for example, breaks or weekends)
common to all resources in the resource charts of the detailed scheduling planning board
[Page 362]. When non-working times are hidden, any operations that are partially or fully
scheduling in non-working times are either displayed in shortened form, or hidden altogether.
• In a resource chart the working times are displayed in white, the downtimes [External] in
dark gray and regular non-working times in light gray (if you have set in the planning
board profile that regular non-working times should be displayed).
• You can schedule or reschedule operations in non-working times [Page 92].
• You cannot display and hide downtimes in the detailed scheduling planning board. You
cannot schedule operations during downtimes.
Procedure
Set the Hide NWT indicator in the time profile if the system should automatically hide non-
working times when you call up the detailed scheduling planning board. This is not relevant
for the detailed scheduling planning board that you call up in the product planning table [Page
386].
To display or hide non-working times in the detailed scheduling planning board, choose
Settings → Non-Working Times → Show or Hide.
Displaying Blocks
Use
You can display blocks [External] for the resources in a resource chart in the detailed
scheduling planning board [Page 362].
Prerequisites
You have defined blocks for the resources.
For more information, see Block Planning [External].

Procedure
1. Select [Page 378] the resources in the resource chart for which you wish to display the
blocks.
2. Choose Extras → Blocks → Display.
Result
The blocks are displayed. They are displayed using various colors that always follow the
same rolling sequence. The system chooses the colors automatically.
By choosing Extras → Blocks → Hide, you can hide the blocks for the selected resources.
By double clicking on a block, you go to block maintenance and can process the blocks.
When you change blocks, you can reschedule the operations in the planning board that are
affected by a change to the blocks using the scheduling function Reschedule [Page 410].
Setting a Time Zone

In the DS planning board [Page 362], the system displays as a default the data for the time
zone that you set in your master record.
If you want to change the time zone, select the desired time zone by choosing Settings →
Time zone.
Transfer Data from Planning Board to Customer Exit

APOCDPS0
Use
In the detailed scheduling planning board [Page 362], you can transfer selected objects
(resources, products, order, operations, and their capacity requirements)to the customer exit
[External] APOCDPS0 using Functions → User. The system can automatically change data
for these objects in the customer exit and return them to the detailed scheduling planning
board for display. If a corresponding logic is implemented in the customer exit, the system
saves the changed data in the liveCache.
For more information, see the system documentation for the customer exit.
Calling Up the Detailed Scheduling Planning Board

Use
You can call up the detailed scheduling planning board [Page 362]:
• Directly in the interactive Production Planning area menu [Page 384]
In the directly called up detailed scheduling planning board
− You plan in a predefined Work area [Page 371] and a predefined planning version
[External]
− You can create various simulation versions [External] for the planning version

You can compare simulation versions, for example with the plan monitor or with
the evaluations. You can also continue to edit the simulation versions at a later
with the DS planning board [Page 387], and if necessary, you can incorporate
them in the planning version.
• In order processing [Page 385]
When you use the detailed scheduling planning boards called up in order processing,
you perform scheduling in the environment of the order you are currently processing.
• In the product planning table [Page 386]
When you use the detailed scheduling planning board called up in the product
planning table, you perform scheduling in the environment of the resources and
products in the product planning table.
see the Detailed Scheduling Planning Board [Page 388] and the Implementation Guide (IMG)
Calling Up the DS Planning Board Directly

Use
In the detailed scheduling planning board [Page 362] (DS planning board), called up directly
in the Interactive Production Planning area menu, you work in a work area [Page 371] and
planning version [External] that are defined explicitly before calling up the DS planning board.
The following options exist for calling up the DS planning board, over several menu paths.
• Using the variable view and − optionally − views 1, 2 and 3, you can freely choose the
planning version and the profile [Page 389] (for example, the work area) with which the
system should configure the DS planning board in an initial screen when calling up the
planning board. You choose this option if you want to work with several work areas and
planning version in the variable planning board.
• You can also call up the DS planning board directly in Views 1 to 3, that is without the
initial screen for profile selection. You determine the profile, for example the work area, in
user maintenance. This option is relevant if you always want to work with the same
settings, for example with the same work area and the same planning version.
You can also create various simulation versions [External] for a planning version in the
directly called DS planning board. You can compare simulation versions, for example with the
plan monitor [External] or with the DS evaluations [Page 472]. You can also continue to edit
the simulation versions at a later date with the DS planning board, and if necessary, you can
incorporate them in the planning version.
Prerequisites
To call up the planning table without the initial screen using one of the menu paths view 1 to
view 3, you must enter an overall profile [Page 389], in which the skip initial screen indicator is
set, in the user maintainence for the SET/GET parameter for this menu path (see table). The
overall profile contains all settings for the planning board.
SET/GET parameters for the views 1 to 3
Menu path SET/GET Parameter

View 1 /SAPAPO/CDPS_VIEW_1
Procedure
1. In the SAP Easy Access Menu under Production Planning → Interactive Production
Planning → DS planning board, choose the view in which you want to call up the planning
board.
Depending on your settings (see prerequisites) you will move immediately to the DS
planning board or the initial screen for the profile selection.
2. Choose the profiles in the initial screen with which you want to work.
If necessary, you can change the selection criteria in the sets for the work area [Page
371] by choosing Edit → Change set. By choosing All views/work area, you can
display the selection criteria for the work area. You can save the changed work area.
The system saves the work area specifically for the user using your user name as the
Customizing ID.
3. Choose Execute.
Result
The system configures the DS planning board. It creates a copy of the planning version,
called a simulation version [External], and displays this simulation version. You can now start
with simulative scheduling. For more information, see scheduling with the detailed scheduling
If necessary, change the setting for the planning under Settings, for example,
• The detailed scheduling strategies [Page 419] for manual scheduling [Page 405], or
reschedule [Page 410] for scheduling with the scheduling function
• The settings for the DS heuristics [Page 413]
Calling Up the DS Planning Board in Order Processing

Use
With the two differently configured detailed scheduling planning boards [Page 362] (DS
planning boards) that you can call up in order processing [Page 309], you plan in the
environment of the order [Page 368] that you are currently processing.
• Planning board 1 shows a product chart [Page 364] in the standard system with the
input and output products of the order. All orders for these products are shown in the
diagram section. The order you are currently processing and the associated orders linked
by pegging relationships are highlighted in color. Green lines are used to display dynamic
pegging relationships between orders; red lines are used to display fixed pegging
relationships.
• Planning board 2 shows several charts in the standard system, including, for example, a
resource chart in which the resources on which orders are to be executed are displayed.
The situation of the operations on these resources with regard to time is displayed for
these resources.
In order processing and the DS planning board that you call up in order processing, you
perform simulative planning − in a similar way to the directly called DS planning board [Page
384] − on the basis of the planning version [External] for which you have called up order

processing. In contrast to the directly called DS planning board, you cannot explicitly save
the simulation version [External] in order processing for further processing at a later date if
required. If you exit and save order processing, you also copy the changes that you have
performed in the DS planning board for the schedule to the planning version.
Procedure
1. If necessary, choose the profile [Page 389], with which you wish to call up the DS
planning board in order processing, under Settings and Settings → User settings on the
Profile tab page.
For more information, see profile maintenance [Page 388].
2. Choose Context in the order processing view.
3. Choose the tab with the desired DS planning board.
Only some of the functions and settings options are available for the DS planning
board on the tab page that you call up using planning board.
4. To call up the DS planning board with full planning board functionality, choose Full
screen.
Result
The system configures the DS planning board and you can analyze [Page 391] or edit [Page
404] the detailed scheduling problems. If necessary, change the setting for the planning under
Settings, for example,
To return to order processing, choose Back.
Calling Up the DS Planning Board in the Product

Planning Table
Use
When you use the detailed scheduling planning board [Page 362] (DS planning board)
displayed in the product planning table [Page 324], you perform scheduling in the
environment of the products and resources [Page 368] in the product planning table. By
default, the detailed scheduling planning board displays a resource chart [Page 364]; this
displays the resource schedule for the planning horizon, that you entered when calling up the
product planning table.
In the product planning table and detailed scheduling planning board that you call up in the
product planning table, you perform simulative planning − in a similar way to the directly
called detailed scheduling planning board [Page 384] − on the basis of the planning version
[External] for which you have called up the product planning table. In contrast to the directly
called detailed scheduling planning board, you cannot explicitly save the simulation version
[External] in the product planning table for further processing at a later date if required. If you
save in the product planning table, you also copy the changes that you have simulated in the
DS planning board for the schedule to the planning version.

Procedure
1. If necessary, select the profile [Page 389], with which you wish to call up the DS planning
board in the product planning table, under Settings and Settings → User settings on the
Profile tab page.
2. Double click on Detailed scheduling planning board in the overview tree for hidden charts
or drag this entry using Drag&Drop to the overview tree for hidden charts.
If the detailed scheduling planning board is not available in the overview tree for
hidden charts, you can specify in the user settings that it should either be displayed or
be available in the overview tree.
Result
The system displays the detailed scheduling planning board as a chart in the product planning
table. You can manually schedule objects with Drag&Drop [Page 406]. You can call up
additional scheduling functions using context menus. To do this, click on an object in the table
section with the right mouse button or on a graphical object in the diagram section.
If necessary, change the setting for the planning under Settings, for example,
Editing the Simulation Version

Use
You can do the following with a simulation version [External] that you created with the directly
called detailed scheduling planning board [Page 384] (DS planning board)
• Continue processing it with the DS planning board
• Incorporate it in the planning version [External] if necessary
• Delete it
You perform simulative planning in the detailed scheduling planning board (DS
planning board), on the basis of the planning version for which you have called up
the DS planning board. In the directly called DS planning board, you can save the
simulative planning under a specific name explicitly as a simulation version for
the planning version. You can compare simulation versions, for example with the
plan monitor [External] or with the DS evaluations [Page 472].
Procedure
1. In the SAP Easy Access menu choose Production planning → Interactive production
planning → Detailed Scheduling Planning Board → Simulation version.
2. Choose the desired simulation version.
3. Choose the desired function.

Function Use
Edit When you want to continue editing the simulation version with the DS planning
board
For more information, see scheduling with the detailed scheduling planning
board [Page 360].
Transfer When you want to incorporate planning data from the simulation version into the
planning version
For more information, see saving the simulation version [Page 423].
Delete When you want to delete the simulation version
4. The system executes the selected functions and calls up the detailed scheduling planning
board with the simulation version.
Note that the simulation versions go out of date quickly for Edit and Transfer, if
the scheduling in the planning version changes quickly.
Profile Maintenance
Purpose
Profiles [Page 389] are used to configure the detailed scheduling planning board [Page 362]
(DS planning board) and integrated functions. SAP issues standard profiles for the DS
planning board that you cannot change. The following process describes how you can create
and use your own profile.
Process
1. Create a profile.
You can do this, if necessary, by copying the default profile and making changes to it.
The following table shows where you can create profiles.
Profiles Maintenance
Alert profile, key figure schema In the area menu for Supply Chain Monitoring
All Profiles [Page 389] except for the In the Production Planning and Detailed Scheduling
alert profile and key figures schema Customizing
All profiles except for the period In the Production Planning area menu under current
profile, alert profile and key figures settings [Page 390]
schema
2. You enter the profile at the relevant position:

− For the DS planning board, called up directly [Page 384] in the area menu for
Production planning, you can enter the profile when calling up the planning board, or
you can enter an overall profile in the user maintenance. You can change selected
settings interactively under Settings (for example, in the strategy profile [Page 419]).
− For order processing, the product planning table and the DS planning boards
integrated into these applications, you enter the profile in the Customizing for Global
Settings, Order Processing and the Product planning table. These profiles are default
values. You can change settings in the profile interactively under Settings or under

Settings → User settings (for example, in the strategy profile [Page 419]) or you can
select other profiles (for example, the propagation range).
For more information, see the Implementation Guide for Production Planning and Detailed
Scheduling.
Prerequisites
You must have authorization for maintaining profiles.
Profile for the DS Planning Board

Definition
Thematically grouped settings
• For the structure and contents of the detailed scheduling planning board [Page 362] (DS
planning board)
• For the following functions integrated in the DS planning board:
− Detailed Scheduling [Page 62]
− Detailed scheduling heuristics [Page 413]
− Alert Monitor [External]
− Plan Monitor [External]
Use
The profiles listed in the following table are used for the DS planning board and the functions
in the DS planning board. You can call up the DS planning board in order processing [Page
385], in the product planning table [Page 386] or directly [Page 384]; note that some profiles
can only be used for the directly called up DS planning board and for the DS planning board
in order processing.
Profile for the DS Planning Board
Profile Settings Use
Overall profile * Planning version and all following only for directly called up
profiles planning boards
Time profile * • Time period that is displayed in the only for
planning board (display period)
• Directly called
• Time period that you can schedule planning board [Page
(planning period [Page 85]) 384]
• Planning board in
order processing
[Page 385]
Work area [Page 371] * Objects that can be displayed in the only for directly called up
DS planning board planning boards

Planning board profile * • Selection of objects to be

displayed [Page 368]
• Configuration of the planning
board and display of the objects
[Page 364]
Period profile * Period for presentation of medium
resource load [Page 398]
Propagation range Resources that you or the system are
[External] allowed to schedule
Strategy profile Detailed scheduling strategies [Page
82] for manual scheduling and
rescheduling [Page 406] and for the
scheduling function Reschedule [Page
410]
Heuristic profile DS heuristics [Page 413], available in
the DS planning board
Optimization profile Presetting for the optimization [Page
237]
Alert profile Alerts that the system displays in the
Alert Monitor [Page 392] when
scheduling problems occur
Key figures schema Key figures for the Plan Monitor [Page
393]
The profiles marked with a * (asterisk) are only used for the planning board. The other profiles
are also used for other applications in production planning.
User-specific Profile
A distinction is made between general and user-specific profiles, except for profiles in the
propagation range, key figure schema and alert profile. User-specific profiles have, in
addition to the profile name, a user-specific identification − the Customizing ID. If your
Customizing ID is the same as the user name that you use to log onto the system, the system
will use the user-specific profile by default.
Maintain profile in the current settings menu

Prerequisites
You must have authorization to maintain profiles [Page 389].
Procedure
1. In the SAP Easy Access Menu, choose Production planning → Environment → Current
settings.
2. To call up the documentation for the profile, click on the corresponding entry using the
right mouse button, and choose Display documentation.
3. To create or change a profile, double-click with the left mouse button on the desired
activity.

You cannot change SAP standard profiles (for example, SAP001). When you want to
work with a modified standard profile, copy the SAP standard profile as a user-
specific profile and change it.
Displaying Current Profiles

Use
You can display the profile currently being used in the following detailed scheduling planning
boards (DS planning boards).
• In the directly called [Page 384] DS planning board.
• In the full screen of the DS planning board called up in order processing [Page 385].
Procedure
Choose Settings → Profiles
Check and Evaluate the Schedule

Use
Using the following functions, you can check and evaluate the schedule in the DS planning
board according to various scheduling aspects or scheduling problems:
Functions for checking and evaluating the schedule
Information Function
Alerts • Calling Up the Alert Monitor [Page 392]
• Highlighting Objects with Alerts [Page 393]
Quality of the schedule Calling Up the Plan Monitor [Page 393]
Resources • Displaying the Order List [Page 394]
• Displaying Operation List [Page 394]
• Displaying Work-in-Process Stock [Page 397]
• Displaying Resource Load Curves [Page 398]
• Displaying the Resource Load List [Page 399]
• Displaying the Fill Level [Page 399]
• Displaying a Resource [Page 421]
Orders • Displaying Pegging Relationships [Page 401]
• Displaying Orders [Page 421]
Operations • Displaying Relationships Between Operations [Page 402]
• Displaying an Operation [Page 421]
Products • Displaying the Product Stock [Page 400]
• Displaying the Production Overview [Page 401]
• Displaying the Product [Page 421]

Scheduling Displaying the Scheduling Log [Page 421]
Calling Up the Alert Monitor

Use
You can call up the Alert Monitor in the DS planning board [Page 362]. By doing this, you can
display scheduling problems; for example, a resource overload. The following table
summarizes for which objects the system creates alerts.
Objects for which the system creates alerts in the DS planning board
DS planning board The system creates alerts for the following:

Called up directly [Page 384] • The resources and products in the propagation range
[External]
• The resources that are defined in the various views in the
work area [Page 368]
• The products and orders that you entered in the work area
Called up in order processing • The order you are currently processing
[Page 385]
• The resources and products for the order
Called up in the product • The resources and products that are displayed in the product
planning board [Page 386] planning board
• The orders for these products
• The orders that are processed at these resources
• You can also display particular scheduling problems directly in the planning board by
customizing the graphical objects [External] accordingly: You can, for example, specify
that delayed orders are displayed graphically in a different way to orders that are on time.
For further information, see DS planning board [Page 362].
• In the planning board, you can color graphical objects that are affected by alerts
depending on the alert type [Page 393]; that is, depending on whether there is an error, a
warning or information for this object.
Prerequisites
• You have defined the settings for the Alert Monitor and an alert profile with the alerts that
are relevant for your schedule in the DS planning board.
You define the settings for the Alert Monitor and alert profile in the SAP Easy Access
Menu by choosing Supply Chain monitoring → Current settings.
For further information, see:
− Management by Exception: PP/DS [Page 477]
− PP/DS alert profile [External]
• The DS planning board called up directly: You entered the alert profile in the overall
profile or when calling up the planning board.
• The DS planning board in the order view or in the product planning board: You
entered the alert profile in Customizing for the order view or the product planning board.

Procedure
To call up the Alert Monitor, choose Extras → Alert Monitor.
Highlighting Objects with Alerts

Use
In the diagram section of the DS planning board [Page 362], you can highlight the activities,
operations and orders for which there are alerts. The objects are highlighted accordingly,
depending on whether an error, a warning or information exists.
Prerequisites
You have set the following in the detail screen for the planning board profile:
• Which alerts are relevant for this highlighting function
You use a PP/DS alert profile [External] for this purpose. You define the PP/DS alert
profile in the SAP Easy Access menu under Supply Chain Monitoring → Alert
Monitor.
• How the graphical objects affected by alerts are highlighted
Procedure
Choose Extras → Alerts → Display.
To remove the highlights, choose Extras → Alerts → Hide.
You can also display alerts in the alert Monitor [Page 392].
Calling Up the Plan Monitor

Use
You can call up the Plan Monitor in the DS planning board [Page 362] that is called up
directly. You can use the Plan Monitor to evaluate the schedule based on freely define key
figures.
For more information, see the documentation for the Plan Monitor [External].
Prerequisites
• You have defined a key figure profile with the desired key figures for the Plan Monitor.
You define key figure profiles in the SAP Easy Access menu by choosing Supply
Chain Monitoring → Current Settings.
• You entered the key figure profile in the overall profile for the DS planning board that is
called up directly, or you entered it when the planning board was called up.

Procedure
Choose Extras → Plan Monitor
Displaying the Order List

Use
For selected resources, you can display a list of all the orders in the DS planning board [Page
362] that have been processed within the display period at these resources.
Procedure
1. Select the desired resources.
If you do not select a resource, you can enter resources when calling up the order list.
2. Choose Extras → Evaluations → Order list.
You can also call this evaluation in the area menu of Production Planning under
Reporting → Order and Resource Reporting. There you can carry out the
evaluation of any planning version and any evaluation period. You will find more
information under Order and Resource Evaluations [Page 472].
Displaying Operation List

Use
For selected resources, you can display a list of all operations in the DS planning board [Page
362] that have been scheduled within the display period at these resources.
Procedure
3. Select the desired resources.
If you do not select a resource, you can enter resources when calling up the
operation list.
4. Choose Extras → Evaluations → Operation list.

Evaluations for Work-in-Process (WIP) Stock

Use
Work-in-process (WIP) stocks are stocks of components or unfinished products that are
waiting at a resource for further processing. Quantities and queue times are important
indicators for assessing the quality of the schedule in relation to costs and the lead times for
orders [External].
The following evaluations resources are available for the WIP in the order and resource
evaluations [Page 472] and in the DS planning board [Page 362]:
Evaluations for WIP stock
Evaluation Description
WIP list This evaluation shows order-internal WIP stock for the order product for
selected resources. You use this evaluation if the order product is passed on,
on behalf of one operation to another, whereby the total quantity is passed on
or is needed at once (that is, there is an availability date or a requirement
date per operation).
The following is displayed for each operation at the selected resources:
• The quantity of the unfinished main product in the order, which is
provided by the preceding operation in the order and which is waiting for
further processing.
• As WIP queue time: The time between the availability date and the
requirement date. The queue time is negative if the availability date lies
after the requirement date.
For operations with continuous input or output you cannot use this evaluation.
Here you use the Enhanced View of the evaluation WIP list (network).
WIP list This evaluation shows the WIP stock for components for selected
(network) resources that are provided by other orders.
The following is displayed as a default for each operation at the selected
resources:
• As the WIP quantity: The total quantity of a component provided by
operations from other orders and waiting for further processing
• As the WIP queue time: The time between the availability date for the
total quantity and the earliest requirement date for the component
The queue time is negative if the availability date lies after the requirement
date. The system calculates using this evaluation for short queue times,
• If several orders deliver an operation or if an order produces a component
continuously (because the system calculates using the availability date
for the total quantity)
• If an order delivers several operations or if an operation uses the
component continuously (for the system calculates using the earliest
requirements date)
For this evaluation you should therefore choose Enhanced View. Here
• the total quantity is broken down into the supplying orders
• the individual WIP queue time is displayed for each single quantity
• WIP stock for operations with continuous input or output [Page 474] is
evaluated in more detail

The system displays the WIP data in the SAP List Viewer. Note: In the Enhanced
view, you can only use the summation function of the SAP List Viewer effectively
for WIP quantities. The summation function provides the sum of the individual
queue times for the WIP queue times, instead of the more generally required sum
of the queue times weighted by the individual quantities.
Activities
You call up the WIP evaluations
• in the Reporting area menu under Order and Resource Reporting
• in the detailed scheduling planning board under Extras → Evaluations
WIP Data for Operations with Continuous Input or

Output
Use
In the Enhanced view of the evaluation WIP list (network) [Page 473] the system also
calculates WIP data for operations that produce or consume material at a constant rate
(operations with continuous output or input).
Features
Below you will find a description of how the system calculates WIP data for the simplest case,
in which the total material quantity that an operation needs and continuously consumes, is
continuously provided by exactly one operation.
The system uses the following data for the calculations:
• The total quantity that is transferred
• Start and end date for the material transfer in the producing operation
The system uses these dates and the total quantity to determine the temporal
development of the transferred material quantity; that is, of the total quantity that the
operation produces as planned up to a specific point in time and has transferred to
the consuming operation. Before the transfer starts, the transferred quantity is zero;
the operation has not yet transferred a material. Between the start and end date, the
transferred quantity increases uniformly to the total quantity. (The system assumes
that the operation transfers the material continuously even in non-working times). At
the end date, the operation has transferred the total quantity. As of this point in time,
the entire quantity transferred is constantly the same as the total quantity.
• Start and end of the material consumption in the consuming operation
development of the consumed material quantity; that is, of the total quantity that the
operation has consumed as planned up to a specific point in time. Before the
consumption starts, the consumed quantity is zero; the operation has not yet
consumed a material. Between the start and end date, the consumed quantity
increases uniformly to the total quantity. (The system assumes that the operation
consumes the material continuously even in non-working times). At the end date, the
operation has consumed the total quantity. As of this point in time, the entire quantity
consumed is constantly the same as the total quantity.

The system determines the WIP curve from the temporal curves of the transferred and
consumed quantity. The WIP curve displays the difference between the entire transferred
quantity and the entire quantity consumed for each point in time. The curve depends on
• the rates with which the quantities are transferred or consumed
• the relative temporal position of the transfer and consumption dates
The curve values can be positive and negative. Positive values indicate that the material was
completed but has not yet been processed further. Negative values indicate missing material.
This case occurs, for example, if the consuming operation needs material earlier or consumes
it faster than it was provided by the producing operation. Negative values are also a sign of
inconsistent planning.
The system shows the following data in the WIP evaluation:
• WIP area
The WIP area is the area under the WIP curve.
• Total quantity that the producing operation transfers to the consuming operation
• WIP time
The WIP time is the quotient from the WIP area and the total quantity.
• Maximum value of the WIP curve
• Minimum value of the WIP curve
Similarly, the system carries out the calculation of the WIP data in the general case, if several
operations, which are continually producing or consuming, are involved in the material flow.
The system breaks down the WIP data here, corresponding to the partial quantities that flow
between a producing and a consuming operation respectively. You differentiate between the
following cases:
• A producing operation delivers several consuming operations.
The system assumes that the operation that is continuously producing firstly delivers
the consuming operation, which has the earliest start date for material consumption.
When this operation has received the total quantity required, the producing operation
delivers the material to the next consuming operation, and so on.
• Several producing operations deliver a consuming operation.
The system assumes that the consuming operation firstly consumes the material of
the operation, which has the earliest start date for material transfer. If this material is
consumed, the consuming operation consumes the material that is provided by the
next producing operation, and so on.
In the WIP evaluation, the WIP data refers in these cases to the partial quantity of the material
that is transferred from a producing operation to a consuming operation. The WIP times are
determined by the partial quantities and by their availability dates or requirement dates.
Displaying Work-in-Process Stock

Use
For work-in-process stock (WIP stock) you can call the following evaluations for selected
resources in the DS planning board [Page 362]:
• WIP list [Page 473]
• WIP list (network) [Page 473]

The system executes the evaluations for the display period of the DS planning board.
Procedure
1. Select the resources for which you want to display WIP stock, and select the desired WIP
evaluation by choosing Extras → Evaluations.
If you do not select a resource, you can enter resources when calling up the WIP
lists.
2. If you want to display the list broken down by order for the WIP list (network), in which
WIP data is evaluated in detail for operations with continuous input or output, set the
Extended view indicator.
You can also call these evaluations in the area menu of Production Planning
under Reporting → Order and Resource Reporting. There you can carry out the
information under Order and Resource Evaluation [Page 472].
Displaying Resource Load Curves

Use
In the Detailed Scheduling planning board [Page 362], you can display charts with resource
load curves that represent the resource load over time for the resources. In a resource load
chart, the resource load at any point in time or the average resource load per shift or for
periods defined by yourself are displayed.
You can use static or dynamic charts for resource load charts.
• A static chart is displayed permanently in the DS planning board and shows the
resource load curves for all resources in the DS planning board. You cannot show and
hide a static chart in the DS planning board.
• You can show and hide a dynamic chart in the DS planning board. It shows resource
load curves for the resources that you previously selected in the DS planning board.
Resource overload is displayed in red in the standard issue. You can set another color in
Customizing for the DS planning board profile.
Prerequisites
• You have defined a static or a dynamic resource load chart in Customizing for the DS
planning board.
• You have specified for the chart whether the resource load at a point in time or the
average resource load per shift or per period is displayed.
• You have defined a corresponding period profile for displaying the average resource load
for a period you defined yourself.
For further information, see the Implementation Guide for the DS planning board under
Maintain planning board profiles and Maintain period profiles.
Procedure
Showing a dynamic resource load chart
1. Select the desired resources
2. Choose Extras → Resource load →

− Display as chart, if the resource load chart should be shown within the DS planning
board
− Display as a dialog box, if the resource load chart should be shown as an extra dialog
box
Hiding a dynamic resource load chart

Choose Extras → Resource load → Hide chart
Displaying the Resource Load List

Use
In the DS planning board [Page 362], you can display a resource load list. In the resource
load list, you can see how heavily loaded the resources are in the periods in the display
period. The resource load can also be displayed per block [External].
It is possible to display the resource load list for the following resources:
• Multi-activity resources [External] und multi-mixed resources [External]
• Single activity resources [External] und single mixed resources [External]
Procedure
1. Select the resources for which you want to display the resource load.
If you do not select a resource, you can enter resources when calling up the resource
load.
2. Choose Extras → Evaluations → Resource load.
3. To specify the period intervals in the display period, enter a period.
Displaying the Fill Level

Use
In the Detailed Scheduling planning board [Page 362], you can display charts with fill level
curves that represent the fill level over time for container resources [External].
You can use static or dynamic charts for fill level charts.
• A static chart is displayed permanently in the DS planning board and shows all the fill
level curves for all resources in the DS planning board. You cannot show and hide a
static chart in the DS planning board.
• You can show and hide a dynamic chart in the DS planning board. It shows the fill level
curves for the container resources that you previously selected in the DS planning board.

Prerequisites
You have defined a static or a dynamic fill level chart in Customizing for the DS planning
board.
Procedure
Showing a dynamic fill level chart
3. Select the desired resources
4. Choose Extras → Fill level →
− Display as chart, if the fill level chart should be shown within the DS planning board
− Display as a dialog box, if the fill level chart should be shown as an extra dialog box
Hiding a dynamic fill level chart

Choose Extras → Fill level → Hide chart
Displaying Product Stock

Use
In the Detailed Scheduling planning board [Page 362], you can display charts with product
stock curves that represent the available quantity over time for the products. In addition to the
physical stock, the planned receipt and requirement quantities are also considered as
available quantity.
You use static or dynamic charts to display product stock charts.
• A static chart is displayed permanently in the DS planning board and shows the product
stock curves for all products in the DS planning board. You cannot show and hide a static
chart in the DS planning board.
• You can show and hide a dynamic chart in the DS planning board. It shows the product
stock curves for the products that you previously selected in the DS planning board.
Prerequisites
You have defined a static or a dynamic product stock chart in Customizing for the DS
planning board.
Procedure
Showing a dynamic product stock chart
5. Select the desired products.
6. Choose Extras → Product stock →
− Display as chart, if the product stock diagram should be shown as a chart in the DS
planning board
− Display as a dialog box, if the product stock diagram should be shown as an extra
dialog box

Hiding a dynamic product stock chart

Choose Extras → Product Stock → Hide chart
Displaying the Production Overview

Use
You can display a production overview for selected products in the DS planning board [Page
362]. The production overview is a list in which the quantities and status of products within
the display period are listed; for example, which quantities of a product have been released or
confirmed.
Procedure
5. Select the desired products.
If you do not select a product, you can enter products when calling up the production
overview.
6. Choose Extras → Evaluations → Production overview.
Displaying Pegging Relationships Between Orders

Use
In the DS planning board [Page 362], you can display charts with network views for orders. A
network view for orders is a Gantt diagram in which the position of orders in relation to time
and the pegging relationships [External] between orders are displayed. Green lines are used
to display dynamic pegging relationships; red lines are used to display fixed pegging
relationships.
You can use static or dynamic charts for network views.
• A static chart is displayed permanently in the DS planning board and shows all pegging
relationships for all orders in the DS planning board. You cannot show and hide a static
chart in the DS planning board.
• You can show and hide a dynamic chart in the DS planning board. It shows the pegging
relationships for all orders that you previously selected in the DS planning board.
Prerequisites
You have defined a static or a dynamic network view chart for orders in Customizing for the
DS planning board.

Procedure
Showing a dynamic network view chart
7. Select the desired orders.
8. Choose Extras → Network view of orders →
− Display as chart, if the network view should be shown as a chart within the DS
planning board
− Display as a dialog box, if the network view should be shown as an extra dialog box
Hiding a dynamic network view chart

Choose Extras → Network view of operations → Hide chart.
Displaying Relationships Between Operations

Use
In the DS planning board [Page 362], you can display charts with network views for
operations. A network view for operations is a Gantt diagram in which the position of
operations in relation to time and the relationships between the operations are displayed as a
blue line.
You can use static or dynamic charts for network views.
• A static chart is displayed permanently in the DS planning board and shows all time
relationships for all operations in the DS planning board. You cannot show and hide a
static chart in the DS planning board.
• You can show and hide a dynamic chart in the DS planning board. It shows the
relationships for all operations that you previously selected in the DS planning board.
Prerequisites
You have defined a static or a dynamic network view chart for operations in Customizing for
For further information, see the Implementation Guide for the DS planning board by choosing
Procedure
Showing a dynamic network view chart
9. Select the desired operations.
10. Choose Extras → Network view of operations →
− Display as chart, if the network view should be shown as a chart within the DS
planning board
− Display as a dialog box, if the network view should be shown as an extra dialog box
Hiding a dynamic network view chart

Choose Extras → Network view of operations → Hide chart.

Displaying Scheduling Log

Use
In the scheduling log, the system collects messages that it creates when scheduling and
rescheduling operations and orders.
The following table contains the user-specific settings for the scheduling log that you enter in
user maintenance using SET/GET parameters.
User-specific settings for the scheduling log

Setting SET/GET Parameter Value Comments
Set number of primary /SAPAPO/CDPS_LOGSIZE Defined by user 100 primary nodes are
nodes displayed as a default.
Hide information /SAPAPO/CDPS_LOGFILT I Only error messages are

messages displayed. Primary nodes for
which there are only information
messages are hidden.
Hide parameter values P For example, no order numbers
in long texts are displayed.
Hide information IP or PI Only error messages are
messages and displayed. Parameter values in
parameter values the long texts for error message
are hidden.
Procedure
To display the scheduling log in the DS planning board, choose Extras → Scheduling log.

Use
Resource x x
Order x x x x
Product x
Operation x x

Procedure
Result
Solving Scheduling Problems

Use
After you have identified the scheduling problems in the detailed scheduling planning board
[Page 362], you try to solve these problems. In the planning board, there are several
functions, in addition to manual rescheduling with Drag&Drop [Page 406] and detailed
scheduling heuristics [Page 413] that are available to you. You can use these functions to
execute certain scheduling steps automatically, or which support you in other ways during
scheduling. These functions are as follows:
Function Use
Scheduling or rescheduling operations and orders When you want to schedule or reschedule
using Drag&Drop [Page 406] operations and orders manually
Deallocating Operations and Orders [Page 412] When you want to (temporarily) remove
individual operations and orders from the
resource schedule
Rescheduling Operations and Orders [Page 410] When you want to schedule or reschedule
operations and orders and be supported by
the system
Scheduling Operations in Non-Working Times When you want to finish an operation or
[Page 417] order with short notice outside of the
regular working time
Fixing Operations and Orders [Page 418] When you want to fix operations and
orders on their particular date and resource
allocation

Interrupting started or partly confirmed operations When you want to reschedule a operation
[External] that has started or has been partly
confirmed
Heuristic Backlog Rescheduling [Page 415] When you want to reschedule operations
and orders that lie in the past
Heuristic Sequencing [Page 415] When you want to reschedule operations
and orders in a certain sequence that you
have defined using sort criteria
Manual Heuristic Sequencing [Page 416] When you want to reschedule operations
and orders in a certain sequence that you
have defined manually
Optimizing Scheduling [Page 227] When you want to optimize scheduling with
regard to certain criteria, for example, with
regard to setup times
Loading Alternative Resources [Page 410] When you want to reschedule operations
on alternative resources in the planning
board
Changing Detailed Scheduling Strategies [Page When you cannot solve the scheduling
419] problem with the current detailed
scheduling strategy
Displaying and Changing Objects [Page 421] When you want to, for example, change
the scheduling data for the resources
Displaying the Scheduling Log [Page 421] When you want to know whether there
were problems during scheduling, and if
so, which problems
For more information, see detailed scheduling activities [Page 64].
Manual Scheduling with Drag&Drop

Use
You can manually schedule operations and orders in the DS planning board [Page 362] by
shifting the corresponding graphical objects [External] with Drag&Drop within a chart or into
another chart: Manually shifting a graphical object triggers − depending on your settings − one
of the following scheduling functions in the (target) chart.
• Schedule or reschedule
The system schedules or reschedules the shifted operation or order to the desired
date that was specified with Drag&Drop. You can also reschedule an operation on an
alternative resource. An operation or order that was previously deallocated loses the
deallocated status after being scheduled or rescheduled successfully. For more
information, see Schedule or reschedule operations and orders with Drag&Drop
[Page 406].
• Deallocate
The system deallocates the shifted operation or order. The object is given the status
deallocated. For more information, see Deallocate operations and orders [Page 412].
• No action
No scheduling function is triggered. The affected object remains in its original location
and retains its status. It cannot be shifted.

You specify in the planning board profile for each chart in the Drag&Drop Act. field, which
scheduling functions are triggered in a chart when you shift a graphical object within this chart
or into this chart with Drag&Drop. Depending on the triggered scheduling function, a chart for
manual scheduling is a scheduling chart, a deallocation chart or a display chart.
You should use the decision table in the planning board profile to determine that
a planning chart displays objects with the status scheduled and a deallocation
chart displays objects with the status deallocated.
Prerequisites
• The graphical elements for the graphical object that you want to shift with Drag&Drop are
not allowed to be fixed.
You fix a graphical element by setting the Fix indicator in the planning board profile
for that graphical element.
When using the standard profiles issued by SAP, you cannot shift the following
objects with Drag&Drop (the Fix indicator for the graphical elements of these objects
is set):
− Sales orders
− Purchase requisitions
− Started, partially confirmed and finally confirmed operations
If you want to reschedule operations that have been started and finally confirmed,
you must first interrupt these operations in the detailed scheduling planning board
[External].
• The operation or order that you want to schedule is not allowed to be fixed in the
schedule.
You can fix operations with the scheduling function Fix [Page 418] or using Schedule
in non-working time [Page 417]. An order is fixed when all operations in the order are
fixed. Before you can reschedule a fixed operation, you must first undo the fix [Page
418] for this object.
• An operation that you want to schedule must lie within the planning period [Page 85].
You cannot schedule or reschedule operations that lie outside of the planning period;
the schedule outside of the planning period (pre-evaluation and post-evaluation
period) cannot be changed. In addition, you cannot schedule or reschedule
operations in the pre-evaluation and post-evaluation period. The earliest possible
time at which you can schedule or reschedule an operation is today's date plus/minus
the offset time [External].
Scheduling or Rescheduling Operations and Orders

Using Drag&Drop
Use
You can schedule or reschedule objects in a planning chart [Page 405] in the detailed
scheduling planning board [Page 362] using Drag&Drop, that is,
• Reschedule a scheduled operation to another date or another mode [Page 73], that is, to
another primary resource

• Reschedule a deallocated [Page 412] operation to a particular date on a specific mode

• Reschedule a scheduled order on another date
• Reschedule a deallocated order to a specific date
• Schedule or reschedule a group of operations or orders to a specific date
To do this, use Drag&Drop to shift the relevant graphical object [External] or the group of
graphical objects to the desired position in the planning chart or from another (planning) chart
to this planning chart. You can shift an order to the desired date, for example, or an operation
to the desired date and primary resource.
As you shift the graphical object or a group of graphical objects, the current date is displayed
by a vertical line on the tip of the cursor. You specify the desired scheduling date [Page 94] by
"releasing" the graphical object or group of graphical objects on this date. This date is the
desired start date (forwards planning direction) or the desired finish date (backward planning
direction) for the object − depending on the planning direction [Page 86].
You can also move an activity of an operation using Drag&Drop and in doing so determine
the desired date or the desired primary resource for this activity. This schedules or
reschedules the whole operation: Once the system has scheduled or rescheduled the activity
successfully, it then schedules or reschedules the other activities of the operation to the
desired resource using midpoint scheduling. This means it schedules the previous activities
with backward scheduling and the subsequent activities with forwards scheduling.
Prerequisites
• You have defined planning charts for the detailed scheduling planning board. When
planning resources and dates for operations, you use a resource chart as a planning
chart, and when planning the date for orders, you use an order chart. You can find more
information regarding the general prerequisites under Manual scheduling with Drag&Drop
[Page 405].
• By choosing Settings → Increments in the detailed scheduling planning board, you
specified the desired precision with which you can specify a scheduling date using
Drag&Drop. If you set the increments to be, for example, weekly, you can only shift the
desired scheduling date for an object to the beginning (forwards planning direction) or
end (backward planning direction) of a calendar week.
• The following prerequisites must be fulfilled in order to schedule or reschedule an activity
or an operation to a specific resource using Drag&Drop.
− The resource is one of the primary resources [Page 73] of the operation.
− The primary resource is displayed in the resource chart of the detailed scheduling
planning board.
• In Functions you can load alternative resources in the detailed

scheduling planning board [Page 410], if necessary.
• If you want the system to select possible alternative primary
resources automatically while you shift an operation with Drag&Drop,
you set the Select alternative resources indicator in the detail screen
of the planning board profile. The selection function for alternative
resources is very performance intensive.
• Using Settings → Strategy you have set the desired detailed scheduling strategies [Page
82] that the system should use during scheduling or rescheduling. Here you determine, in
particular, the scheduling sequence for a group of activities, operations or orders.
Procedure
Activity Procedure

Schedule or reschedule a single While holding down the left mouse button, drag the
object object to the desired date, and if necessary drag an
activity or operation to the desired primary resource.
Schedule or reschedule a group of 1. Select the objects [Page 378] that you want to
object to a specific date reschedule.
2. While holding down the SHIFT key and pressing the
left mouse button, drag the group of objects onto the
desired date
The system schedules or reschedules the objects in the
order that you set in the detailed scheduling strategy,
depending on the desired date.
Result
Depending on the desired date set using Drag&Drop, the system tries to find the next
available date on which it can schedule or reschedule [Page 62] the object or an object from
the group of objects, based on the settings in the detailed scheduling strategy [Page 82].
Depending on the detailed scheduling strategy the system then reschedules further objects
automatically.
• If you have set one of the insert planning modes [Page 89] (Insert operation [Page 90],
Squeeze in operation [Page 92] or Insert operation and close gaps [Page 91]) in the
detailed scheduling strategy, the system shifts operations to the resource, to create a
sufficiently large gap for the operation to be inserted or to close the gaps. The system
does not reschedule these operations on other resources, that is, the mode is retained.
• If you have specified in the detailed scheduling strategy that the system must consider
the time relationships [Page 97] between the operations in an order or the pegging
relationships [Page 98] between the operations of several orders, the system also
reschedules, if necessary, these dependent operations or adjusts the dates − for
deallocated operations − when rescheduling an operation. The system automatically
carries out mode selection [Page 72] for the dependent operations.
If scheduling of a deallocated operation is successful, the operation is given the status
scheduled.
If the system does not find a date for consistent scheduling or rescheduling of all objects
concerned, or if the maximum duration set for scheduling [Page 422] has been exceeded, the
system does not schedule or reschedule the objects. Therefore, the objects retain their
original dates and − in the case of deallocated objects − they retain the deallocated status.
For information regarding scheduling problems, see the following:
• The Alert Monitor [Page 392]
• The scheduling log [Page 421]
Deallocating Operations and Orders

Use
You can use this function in the detailed scheduling planning board [Page 362], in the
production planning run [Page 122], or automatically in Detailed Scheduling [Page 62] to
deallocate operations or orders, that is, remove them from the resource load. You set this
function, for example, if you want to specify the production dates of operations for important
orders first, and then later schedule the operations for less important orders.

A deallocated operation has the status deallocated. It is then assigned to a specific mode
[Page 73], but does not load the resources of this mode. The system adjusts dates or modes
of deallocated operations automatically during planning, for example,
• if time relationships [Page 97] or pegging relationships [Page 98] must not be violated
• if linking of modes [Page 75] exists for a scheduled operation, which is rescheduled to
another mode
• if you have set compact scheduling [Page 103]
Prerequisites
A deallocation chart must be defined for the DS planning board so that you can deallocate
operations or orders manually using Drag&Drop in the DS planning board. You can find more
information under manual scheduling using Drag&Drop [Page 405].
Procedure
Deallocate objects in Detailed Scheduling planning board via Drag&Drop
Drag the operations or orders into the deallocation chart using Drag&Drop (see also
scheduling or rescheduling operations and orders using Drag&Drop [Page 406]).
The system deallocates the objects. Each selected object has − depending on the planning
direction ### its current start or end date. Operations maintain their mode assignment, with
the following exception: if the deallocation chart is a resource chart, you can assign a new
mode to the operations, by dragging the operation to an alternative primary resource. The
system adjusts the operation duration accordingly in the calendar resource of the new mode.
Deallocate objects in Detailed Scheduling planning board with planning function

“deallocate”
1. Select the operations or orders [Page 378] that you want to deallocate.
2. Choose Functions → Deallocate.
direction ### its current start or end date. Operations maintain their mode assignment.
If you have specified in the detailed scheduling planning board, for example, that
only scheduled operations are displayed in a chart, the deallocated operations
disappear from this chart. If you have defined a chart in the planning board
profile, in which operations with the status deallocated should be displayed, the
deallocated operations are displayed in this chart.
Deallocate objects in the production planning run with planning function “deallocate”
1. Specify the function Deallocate when defining the production planning run for the
processing step in which the system should perform deallocation.
2. Specify the operations or orders that the system should deallocate in this processing
step.
The system deallocates the operations or order in the production planning run. Each selected
object has − depending on the planning direction ### its current start or end date. Operations
maintain their mode assignment.
Automatically Deallocating Operations During Detailed Scheduling

When the system schedules or reschedules an operation, other operations may be affected,
for example, by time relationships [Page 97] or pegging relationships [Page 98] that must be
observed. Instead of rescheduling these dependent operations so that the relationships are
not violated, the system can only adjust the dates for these operations accordingly, and
deallocate the operations. Choose Deallocate dependent operations in the detailed

scheduling strategy [Page 419] for the scheduling submode [Page 95]. As long as no mode
linkage exists, which requires a change of mode, the operations will maintain their mode
assignment.
Result
You can reschedule deallocated operations or orders, that is, you can dispatch them again to
resources
• in the DS planning board manually using Drag&Drop [Page 406] or with the reschedule
planning function [Page 410]
• in the production planning run using the reschedule planning function
Loading Alternative Resources

Use
You can use this function to load the alternative resources [Page 73] for operations or orders
from the production process models in the detailed scheduling planning board [Page 362].
You can then the reschedule operations on the alternative resources.
Prerequisites
This resource must lie within the propagation range [External] so that you can schedule an
operation on an alternative resource.
Procedure
1. Select [Page 378] the operations or orders for which you want to load alternative
resources.
2. Choose Functions → Load alternative resources.
Result
The system loads the alternative resources into the detailed scheduling planning board.
If you have set the indicator Select alternative resources in the detail screen of
the planning board profile, the system highlights alternative primary resources in
green if you reschedule an operation with Drag&Drop [Page 406]. This selection
function is very performance-intensive.
Rescheduling Operations and Orders

Use
You can use this function to do the following in the DS planning board [Page 362] or in the
production planning run [Page 122]:
• Automatically reschedule operations or orders that are already scheduled and are
affected by scheduling problems; that is, without using Drag&Drop

The system only schedules an operation or an order when it is affected by a

scheduling problem, for example, if it is in the past, if relationships are violated or if an
overload has occurred. The system does not reschedule the operation on a different
mode [Page 73].
• Schedule deallocated [Page 412] operations or orders again
The system selects the modes for the operations automatically (see mode selection
[Page 72]).
Only operations and orders that start within the planning period [Page 85] can be
rescheduled. You define the desired scheduling date [Page 94] in the detailed scheduling
strategy [Page 82]. You have the following options:
Desired scheduling dates for rescheduling

Option Description
Current date If you choose this option, the system searches for a new scheduling date
by starting at the current start or finish date for the operations or order −
depending on the planning direction.
Earliest date If you choose this option, the system starts at the earliest possible
scheduling date [Page 85]. The earliest possible date is today’s date
plus/minus the offset time [External] or the start of the planning period.
You set the offset time in the strategy profile. You can only use this
option in combination with the planning direction forwards [Page 86].
When you combine this option with the scheduling mode search for a
slot [Page 90] and a scheduling sequence [Page 94], you can schedule
operations at a resource as early as possible and in a particular
sequence.
Date entered If you choose this option, you enter a date in the DS planning board
when calling up the Reschedule scheduling function; from this date
onwards, the system should search for a scheduling date for the objects.
This option is not relevant for the production planning run.
The earliest start date [Page 85], that the system can use to reschedule the operations or
orders, is the later of the following dates:
• Today’s date plus or minus the offset time
• Start of the planning period
Procedure
Rescheduling operations or orders in the DS planning board
1. Set the detailed scheduling strategy [Page 419], with which the system should carry out
scheduling or rescheduling.
2. Select [Page 378] the operations or orders that you want to reschedule.
3. Choose Functions → Reschedule.
Rescheduling operations or orders in the production planning run

1. Enter the Reschedule function when defining the production planning run for the
processing step in which the system has to schedule or reschedule.
2. Specify the operations or orders that the system should reschedule in this processing
step.
3. Enter a strategy profile.

Deallocating Operations and Orders

Use
You can use this function in the detailed scheduling planning board [Page 362], in the
production planning run [Page 122], or automatically in Detailed Scheduling [Page 62] to
deallocate operations or orders, that is, remove them from the resource load. You set this
function, for example, if you want to specify the production dates of operations for important
orders first, and then later schedule the operations for less important orders.
A deallocated operation has the status deallocated. It is then assigned to a specific mode
[Page 73], but does not load the resources of this mode. The system adjusts dates or modes
of deallocated operations automatically during planning, for example,
• if time relationships [Page 97] or pegging relationships [Page 98] must not be violated
• if linking of modes [Page 75] exists for a scheduled operation, which is rescheduled to
another mode
• if you have set compact scheduling [Page 103]
Prerequisites
A deallocation chart must be defined for the DS planning board so that you can deallocate
operations or orders manually using Drag&Drop in the DS planning board. You can find more
information under manual scheduling using Drag&Drop [Page 405].
Procedure
Deallocate objects in Detailed Scheduling planning board via Drag&Drop
Drag the operations or orders into the deallocation chart using Drag&Drop (see also
scheduling or rescheduling operations and orders using Drag&Drop [Page 406]).
direction ### its current start or end date. Operations maintain their mode assignment, with
the following exception: if the deallocation chart is a resource chart, you can assign a new
mode to the operations, by dragging the operation to an alternative primary resource. The
system adjusts the operation duration accordingly in the calendar resource of the new mode.
Deallocate objects in Detailed Scheduling planning board with planning function

“deallocate”
3. Select the operations or orders [Page 378] that you want to deallocate.
4. Choose Functions → Deallocate.
direction ### its current start or end date. Operations maintain their mode assignment.
If you have specified in the detailed scheduling planning board, for example, that
only scheduled operations are displayed in a chart, the deallocated operations
disappear from this chart. If you have defined a chart in the planning board
profile, in which operations with the status deallocated should be displayed, the
deallocated operations are displayed in this chart.

Deallocate objects in the production planning run with planning function “deallocate”
3. Specify the function Deallocate when defining the production planning run for the
processing step in which the system should perform deallocation.
4. Specify the operations or orders that the system should deallocate in this processing
step.
The system deallocates the operations or order in the production planning run. Each selected
object has − depending on the planning direction ### its current start or end date. Operations
maintain their mode assignment.
Automatically Deallocating Operations During Detailed Scheduling

When the system schedules or reschedules an operation, other operations may be affected,
for example, by time relationships [Page 97] or pegging relationships [Page 98] that must be
observed. Instead of rescheduling these dependent operations so that the relationships are
not violated, the system can only adjust the dates for these operations accordingly, and
deallocate the operations. Choose Deallocate dependent operations in the detailed
scheduling strategy [Page 419] for the scheduling submode [Page 95]. As long as no mode
linkage exists, which requires a change of mode, the operations will maintain their mode
assignment.
Result
You can reschedule deallocated operations or orders, that is, you can dispatch them again to
resources
• in the DS planning board manually using Drag&Drop [Page 406] or with the reschedule
planning function [Page 410]
• in the production planning run using the reschedule planning function
Detailed Scheduling Heuristics

Use
The following heuristics [Page 207], that you can use in the production planning run [Page
122] or in the DS planning board [Page 362] for solving special scheduling tasks, are
available for detailed scheduling:
Detailed scheduling heuristics (DS heuristics)
DS heuristic Use
Schedule deallocated operations [Page Schedule selected deallocated [Page 412]
414] operations
Lead time reduction [Page 415] Reduce the lead time [External] for orders that are at
selected resources
Backlog rescheduling [Page 415] Reschedule operations at a resource that lie in the
past
Sequencing [Page 415] Schedule selected operations in a predefined
sequence
Manual sequencing [Page 416] Schedule selected operations in a sequence that
was already created manually.
board.

Merging orders on container resources Merge selected synchronized planned orders at

[Page 416] multi resources with storage characteristics
(container resources [External]).
board.
Prerequisites
To be able to call up the heuristics in the menu for the DS planning board under Functions →
Heuristics, you must make these heuristics available in the DS planning board using a
heuristic profile. You define heuristic profiles in Customizing for Production Planning and
Detailed Scheduling, and you enter the following in Customizing for the corresponding
application:
• For the DS planning board called up directly [Page 384], you enter the heuristic profile in
the overall profile for the DS planning board or when calling up the DS planning board.
For further information about the overall profile, see the Implementation Guide for the DS
planning board that is called up directly.
• For the DS planning boards that can be called up in the production planning table [Page
386] or in order processing [Page 385], the system uses the heuristic profile that you
entered in Customizing for the Production planning table or the Order view respectively.
You enter additional heuristics in this heuristic profile that you use especially in the
production planning table or in the order view.
Features
• Strategy settings
Depending on the heuristic, you can change the selected strategy settings that the
heuristic uses to schedule or reschedule operations. Certain strategy settings are
permanently set by SAP and cannot be changed.
• Planning Period
The system uses heuristics to reschedule operations that start in the planning period.
Activities
• If you want to start a heuristic in the DS planning board, select the desired object and
call up the heuristic by choosing Functions → Heuristics. You can change the settings for
the heuristics in the DS planning board by choosing Settings → Heuristics.
• If you want to use a heuristic in the production planning run, enter the heuristic and the
object for which you want to execute the heuristic in the corresponding processing step in
the production planning run.
Schedule Deallocated Operations

Use
Using this heuristic [Page 207], you can schedule selected deallocated [Page 412] operations
again in the production planning run [Page 122] and in the DS planning board [Page 362].
This heuristic uses the function module /SAPAPO/HEUR_DISPATCH.

Lead Time Reduction

Use
Using this heuristic [Page 207], you can reduce the lead time [External] for orders in the
production planning run [Page 122] and in the DS planning board [Page 362] that have
operations at selected resources.
The system fixes [Page 418] the selected resources and thereby all the operations that are
scheduled at these resources. Starting at each fixed operation, the system schedules the
other operations from the affected order in such a way that the smallest possible time
intervals between the operations from that order are achieved.
This heuristic uses the function module /SAPAPO/HEUR_REDUCE_LEADTIME.
Backlog Rescheduling
Use
You can use this heuristic [Page 207] to reschedule the backlog in the production planning
run [Page 122] and in the DS planning board [Page 362]; that is, you can automatically
reschedule the operations that lie in the past in the planning period [Page 85] to the current
date or in the future.
Features
The current date and current time is the default for the earliest possible start date for the
operations to be rescheduled. With the help of the offset time in the heuristic settings, you can
shift the earliest possible start date into the past or into the future.
This heuristic uses the function module /SAPAPO/HEUR_RESOLVE_BACKLOG.
Sequencing
Use
Using this heuristic [Page 207], you can schedule selected scheduled operations in a
particular sequence in the production planning run [Page 122] and in the DS planning board
[Page 362].
This heuristic uses the function module /SAPAPO/HEUR_PLAN_SEQUENCE.
Activities
You specify the scheduling sequence in the heuristic settings. When you start the heuristic for
the selected operations, the system deallocates these operations and then schedules them
again one after another in the set sequence.

Manual Sequencing
Use
You can use this heuristic [Page 207] to do the following in the DS planning board [Page 362]:
• Create a scheduling sequence of your choice for a group of selected scheduled
operations
• Subsequently schedule the operations in this sequence
You create the sequence of operations manually on a graphical list interface when calling up
the heuristic.
Due to the fact that you create the operation sequence manually when calling up
the heuristic, you cannot use this heuristic in the production planning run [Page
122].
Features
The list interface in divided into two sections, between which you can shift operations using
Drag&Drop. In one of the sections, you create the list of operations to be rescheduled in the
desired sequence. You can use the other section as a work area and a temporary store for
operations. You can also put the operations in this section that are not to be rescheduled.
When you have created the operation list, you can start rescheduling. You define the
rescheduling strategy settings in the heuristic settings.
This heuristic uses the function module /SAPAPO/HEUR_PLAN_SEQUENCE_MAN.
Merging orders on container resources

Use
You can use this heuristic [Page 207] to merge planned orders you have selected in the DS
The system increases the order quantity of an existing order to the sum of all selected
individual orders and deletes the other selected orders. All of the pegging relationships are
transferred to the merged order.
This heuristic uses the function module /SAPAPO/HEUR_MERGE_ORDERS.
Prerequisites
Before orders can be merged, the following prerequisites must be met:
• All orders must reference the same production process model
• All orders must be planned orders
• All orders must be synchronized, that is, the start and end times of the orders must be the
same.

• All orders must be scheduled at a multi resource with storage characteristics

• Synchronization must be activated in the master data of the resource
Scheduling Operations in Non-Working Times

Use
In the detailed scheduling planning board [Page 362], you can schedule operations using
drag and drop to the regular non-working times at a resource, that is, in times where the
resource is not scheduled to work. By using this strategy, you do not have to change the
resource data directly when you want to finish an operation after the end of the regular
working time, for example, after the end of the last shift. During the non-working time, the
same capacity and the same rate of resource utilization is available as was available in the
regular working time that directly preceded this. For more information, see Scheduling in Non-
Working Times [Page 92].
• You cannot schedule any operations in resource downtimes [External] (for example, due
to machine shutdown).
• In a resource chart the working times are displayed in white, the downtimes [External] in
dark gray and regular non-working times in light gray (if you have set in the planning
board profile that regular non-working times should be displayed).
• You can display and hide [Page 382] non-working times in the detailed scheduling
planning board. You cannot display and hide downtimes in the detailed scheduling
planning board.
Procedure
1. Call up the strategy profile by choosing Settings → Strategy and set the indicator Non-
working times in the detailed scheduling strategy.
2. Choose Enter.
3. Shift the desired operation to the non-working time using drag and drop.
Result
The system schedules the operation on this date when all other prerequisites are fulfilled; for
example, when no constraints are violated by the schedule.
The system fixes the operations that you schedule in non-working times, that is, the
operations can no longer be rescheduled. Even when you reset the indicator Non-working
times, the operations remain fixed. In order to be able to reschedule the operations again, you
must undo the fix [Page 418].

Fixing Operations, Orders and Time Intervals

Use
If you do not wish to make any more changes to the dates and resource allocation for an
operation or order, or if you do not wish to make changes to the resource schedule for a
specific time segment, you can fix the operation, order or resource.
• Fix operation or order
This function is available in the detailed scheduling planning board [Page 362] or in
the production planning run [Page 122]. A fixed scheduled operation cannot be
rescheduled or deallocated, and a fixed deallocated operation cannot be scheduled
or adjusted (see detailed scheduling activities [Page 64]). By fixing an order, you fix
all operations in that order. By fixing, the operation or order is given the following
status:
− An operation is given the status fixed.
− An order, that contains at least one fixed operation, is given the status date fixed and
PP firmed [Page 317], that is, the order is also fixed for planning with the production
planning heuristics.
• Fix time intervals for resources
This function is only available in the detailed scheduling planning board. You cannot
change the schedule in fixed time intervals, that is:
− Operations that lie completely or partially within a fixed time interval are fixed
− You cannot schedule or reschedule operations in fixed time intervals
During optimization [Page 237], the system also considers whether the operations, orders or
time intervals are fixed.
Procedure
Fixing objects in the DS planning board, and undoing the fix
Fix Procedure
Individual operations and orders Select the objects and choose Functions → Fix.
Time interval for a resource 1. Select the resource.
2. Choose Functions → Fix.
3. Define the time interval to be fixed.
The system fixes the objects. If you called up the DS planning board using a standard
planning board profile, the objects are displayed in a different way. The system displays fixed
time intervals in red.
Undo fix Procedure

For individual operations and orders Select the objects and choose Functions → Undo fix.
For time intervals 1. Select the resource.
2. Choose Functions → Fix.
3. Delete the fixed time interval.

The system removes the fix.
Fixing objects in the production planning run, and undoing the fix
Choose the function Fix object or Unfix object for the processing step in the production
planning run in which the objects should be fixed or unfixed.
Enter the objects that are to be fixed or unfixed.
You cannot change the schedule for objects outside the propagation range [Page
111]. You cannot undo this “fixing”.

Use
Features
strategies)
Activities
Settings.
interactively.

System [Page 112]
planning run

385]
[Page 386]
DS planning board


Use
Resource x x
Order x x x x
Product x
Operation x x
Procedure
Result
Displaying Scheduling Log

Use
In the scheduling log, the system collects messages that it creates when scheduling and
rescheduling operations and orders.

The following table contains the user-specific settings for the scheduling log that you enter in
user maintenance using SET/GET parameters.
User-specific settings for the scheduling log

Setting SET/GET Parameter Value Comments
Set number of primary /SAPAPO/CDPS_LOGSIZE Defined by user 100 primary nodes are
nodes displayed as a default.
Hide information /SAPAPO/CDPS_LOGFILT I Only error messages are

messages displayed. Primary nodes for
which there are only information
messages are hidden.
Hide parameter values P For example, no order numbers
in long texts are displayed.
Hide information IP or PI Only error messages are
messages and displayed. Parameter values in
parameter values the long texts for error message
are hidden.
Procedure
To display the scheduling log in the DS planning board, choose Extras → Scheduling log.
Specifying the Maximum Scheduling Duration

Use
The system cancels scheduling or rescheduling of operations or orders by default after a
certain number of scheduling steps (corresponding to a scheduling duration of approximately
10 minutes). This can occur when the system has to consider many dependencies during
scheduling or rescheduling; for example, relationships between operations. The maximum
scheduling duration refers to the scheduling or rescheduling of the selected operations [Page
70] and to all necessary subsequent rescheduling. If the system cancels scheduling, no
operations or orders are scheduled or rescheduled.
You can set another maximum scheduling duration in the detailed scheduling strategy [Page
82].
Update the Simulation Version

Use
You use this function:
• When you want to consider the current status of the schedule for the planning version
[External] in the simulation version [External] that you are currently processing (for
example, in the DS planning board [Page 362])
• When you create or delete orders from the DS planning board

The system merges the planning data from the planning version with that of the simulation
version during the update. During merging, the system only adopts planning data into the
simulation version that have a higher priority than the simulative schedule. For example, the
following have higher priority:
• Confirmed operations
• Deleted orders
• Changed order quantities
For example, if you have shifted an operation to another date in the DS planning
board, that is, in the simulation version, and the operation in the planning version
has been confirmed in the meantime, the system adopts the confirmed operation
into the simulation version; the confirmation has a higher priority than the
rescheduling. If the operation in the planning version was also "only"
rescheduled, the date of the operation in the simulation version has a higher
priority.
You can call up the update interactively in the application. In the planning board profile, you
can specify for the DS planning board (Update interval field) that the system automatically
updates the simulation version at regular intervals.
Activities
To update the simulation version, choose Update. The system updates the simulation version
and displays the updated data. If you execute the update in the DS planning board, the
system determines the objects to be displayed in the planning board [Page 368] in exactly the
same way as when the planning table is called up, that is:
• Based on the work area [Page 371], in the case of a directly called up planning board
[Page 384]
• Based on the order being processed, in the case of the planning board called up in order
processing [Page 385]
• Based on the resources and products in the product planning table, in the case of the
planning board called up in the product planning table [Page 386]
Save the Simulation Version

Use
When you want to adopt the planning data in the simulation version [External] that you are
currently processing in interactive scheduling (for example, in the DS planning board [Page
362]) into the planning version [External], you can save the simulation version. Due to the fact
that the planning data in the planning version could have changed in the meantime (for
example, due to the confirmation of operations), the system does not simply copy the
simulation version into the planning version, but merges the planning version with the
simulation version. During this merging process, the system only adopts planning data from
the simulation version into the planning version when the planning situation in the planning
version does not have priority. For example, the following have higher priority:
• Confirmed operations
• Deleted orders
• Changed order quantities

You rescheduled an operation in the simulation version on another date. In the

meantime, the operation is confirmed in the planning version. If you adopt the
simulation version into the planning version, the confirmation of the operation has
priority over the rescheduling; that is, the change of date is not adopted into the
planning version.
In the directly called up DS planning board [Page 384], you can also save the simulation
version explicitly, without changing the planning version. You can process the saved
simulation versions with the DS planning board at a later point in time in the area menu for the
DS planning board under Simulation version and, as required, adopt them into the planning
version.
Working with Production Campaigns

Use
Production campaigns are used to manufacture products in a single manufacturing process
over a longer period of time.
Integration
You usually create master data (materials, resources, master recipes) in R/3 and transfer it to
APO using an active integration model. There you create production campaigns and plan
them according to your criteria. The data is automatically transferred to R/3 where the
execution and settlement of the campaign take place.
However, you can also transfer campaigns from R/3 to APO, optimize the planning in APO,
and transfer them back to R/3 for execution and settlement.
Features
You can create single or multi-product campaigns (manually) or have them created using the
optimizer (see Campaign Optimization [Page 232]).
The following functions are available:
• Creating production campaigns [Page 425]
• Adding orders to a production campaign [Page 425]
• Deleting orders from a production campaign [Page 425]
• Selecting all operations and orders that belong to the same production campaigns [Page
425] as a selected operation or order (only in the DS planning board)
• Dissolving production campaign [Page 425]; the assignment of the orders to the
campaign is deleted, but the orders themselves still exist
• Converting production campaigns [Page 425] (in process orders)
The production campaigns are transferred to R/3 automatically as long as a corresponding
integration model has been created and activated.
Since only orders with material reference can be processed in APO at the
moment, orders without material reference, such as clean-out orders in R/3, are
not yet supported. You can, however, add clean-out orders to production
campaigns created in APO after they are transferred to R/3.

Creating Production Campaigns

Prerequisites
Orders that are to form a production campaign may not already be assigned to a different
production campaign.
If you want to have production campaigns created automatically, use campaign optimization
[Page 232].
Procedure Outside of the DS Planning Board

1. Choose Production Planning → Interactive Production Planning → Production
Campaign.
The Production Campaign screen appears.
2. Enter the relevant planning version and choose .
The Create Production Campaign screen appears.
3. Enter a description for the production campaign.
4. If required, add orders to the campaign:
To create new orders and add them to the campaign, choose .
Make the required entries, save the order, and transfer it to the campaign.
To add existing orders to the campaign, choose .
Select the orders you want to add from the list and transfer them to the campaign.
5. Save the campaign.
Procedure in the DS Planning Board

1. Select the orders you want to combine in a production campaign. Skip this step if you first
want to define an empty campaign to which you will later add orders.
2. Choose Functions → Production campaign → Create....
A dialog box appears with campaign information (header data).
3. Enter a description for the production campaign and choose Continue.
A results log appears informing you which orders were included in the campaign, how
many were included in total, and whether the campaign was successfully created.
4. If required, add additional orders and save the campaign.
Processing Production Campaigns

In the description for this function, it is assumed that you are either working in:
• The initial screen for the production campaign (Production Planning → Interactive
Production Planning → Production Campaign) or
• The DS planning board (Production Planning → Interactive Production Planning → DS
Planning Board → View <n> or Variable View).
Function Procedure from initial screen in Procedure in the DS planning

the production campaign board

Adding new orders to 1. Enter the relevant planning (not in the DS planning board)
production campaigns version and choose .
2. Select a production campaign
by double-clicking it.
3. Choose .
Make the required entries.
An order is not added to the
campaign unless the
scheduling conditions have
been met. Save the order and
add it to the campaign.
Adding existing orders 1. Enter the relevant planning 1. Select the orders you want to
to production version and choose . add to the campaign.
campaigns
2. Select a production campaign 2. Choose Functions →
from the list by double- Production campaign → Add
clicking it. selected orders.
3. Choose . 3. Select the campaign from the

In the list that appears, select list that appears.
the orders you want to add to The orders are only added to the
the campaign and add them. campaign if the scheduling
The orders are only added to the conditions are met.
campaign if the scheduling
conditions are met.
Deleting orders from 1. Enter the relevant planning 1. Select the orders you want to
campaigns version and choose . delete from the campaign.
2. Select the campaign by 2. Choose Functions →
double-clicking it. Production campaign →
Remove selected orders.
3. Select the order(s) you want
to delete from the campaign 3. Select the campaign from the
and choose . list that appears.
The system tries to schedule the The system tries to schedule the
order so that it is outside of the order so that it is outside of the
campaign. If this is not possible, a campaign. If this is not possible, a
log is generated. However, the log is generated. However, the
order will still be removed from order will still be removed from
the campaign (it remains in the the campaign (it remains in the
original position). original position).
Rescheduling (only in the DS planning board) 1. Select all orders in the

campaigns campaign (using the display
all orders for a campaign
function).
2. Click one of the orders that
belongs to the campaign and
move the campaign while
holding down the mouse
button.
Converting campaigns 1. Enter the relevant planning (not in the DS planning board)
(in process orders) version and choose .
2. Select the campaign you
want to convert and choose

Edit → Convert Production

Campaign.
The campaign is
converted when you
save.
Displaying header data 1. Enter the relevant planning 1. Select an order in the
version and choose . campaign.
2. Double-click a campaign to 2. Choose Functions →
select it. Production campaign →
Display header data.
Dissolving campaigns 1. Enter the relevant planning 1. Choose Functions →
version and choose . Production campaign →
Dissolve.
2. Click the campaign you want
to dissolve. 2. Select the campaign you want
to dissolve and choose
3. Choose Production
Continue.
Campaign → Dissolve.
The campaign is deleted, but the
The campaign is deleted, but the orders that belong to the
orders that belong to the campaign are not deleted.
campaign are not deleted.
Displaying all orders in 1. Enter the relevant planning 1. Choose Functions →
a campaign version and choose . Production campaign →
Select.
2. Double-click a campaign to
select it. 2. Select the campaign.
The system selects the orders in
the campaign.
See also Display of Campaigns.
Displaying all orders for (only in the DS planning board) 1. Select an order in the
the same campaign campaign.
2. Choose Edit → Select → For
the same campaign
See also Display of Campaigns.
Conditions for Scheduling in the liveCache:

• No interruptions at any primary resources
• Quantity of resources used in a campaign must remain small. This means that when
using alternative modes, the user must choose one that is already being used by a
resource in the campaign.
The Item indicator for setup/clean-out orders is taken into account during scheduling.
Display of Campaigns
In the planning board profile for a resource chart, you can specify that campaigns are to be
displayed in the diagram area. In the planning board profile, set the Campaign indicator for
the resource chart. A thin, purple bar represents a campaign. The campaign bar is behind the
graphic objects for the operations or activities that belong to the campaign.

Push Production
Purpose
Push production is used to create a master production schedule starting with products for
which no requirements exist in the system (push products). Push production takes the
predefined scheduling strategies into account.
Push production supports decision-making for a clearly defined push problem (material
without consumer) in short-term to medium-term planning. It helps with the decision of what to
produce and in which quantity to produce it to consume a push material, working in the
opposite direction as requirements explosion. It does not change the master production
schedule based on target product requirements by working from the finished product via the
intermediate products to the raw materials (pull). Instead, it works with requirements
explosion and searches for a use for available raw materials and semi-finished products.
Prerequisites
The Alert Monitor supports you in finding products with a surplus. To do this, the PP/DS
Excess Coverage alert must be activated in the Alert Monitor profile.
You can only branch from the Alert Monitor to push production if the
PP/DS Excess Coverage alert is activated.
Process Flow
Push production takes place in two main steps:
• Identification of push problem - which orders generate a surplus?
• Generation of consumer for this product
Product view
Alert Monitor
Identify push problem
Choose push product
Product master Using push production

Production process System explodes PPM Alert- Monitor
model System makes suggestions
APO - Planning strategies Interaction

Details
Orders are simulated
System checks capacities
Order are assigned to requirements
Copy orders
or
Discard simulation
1. In the system, you identify a quantity of a product for which no consumer is available
(push product). The system supports you with alerts that detect surpluses.

2. You call up push production [Page 432] from either the Product View for the push
product (in the change mode) or from the Alert Monitor.
The Push Production view, which contains all required information and functions for
solving a push problem, appears. This includes, for example:
− Orders with a surplus of a push product
− All production process models with product receipts in which the push material is
used
− All orders that were generated using push production
3. You choose an order with a product surplus.
The system uses the production process model to calculate the quantity of possible
product receipts based on the quantity of push products, and displays this quantity.
4. You select a product you want to produce.
5. You determine the quantity to be produced.
6. You create an order or several orders in a simulation.
− The system schedules according to the scheduling strategy defined.
If there are lot-size constraints, the system calculates the number of orders that
must be created to produce the desired quantity. This calculation is based on the
leading product of the selected production process model. If the number of orders
is greater than one, the result of the calculation is displayed.
− You can change the number of these orders.
The system adjusts the total quantity accordingly.
7. The system updates the Push Production view, resulting in the following:
− The order data of the newly created orders is displayed
− The orders are assigned to the production process models
− The push product quantity is updated
− The quantity of possible product receipts is adjusted
− Warning messages are triggered in the Alert Monitor.
8.
If you want to Then
Change order data Double-click the order.

Delete a simulated order Select the order and choose .
The system deletes the order and updates the
surplus quantity of the push product in the planning
pool.
Discard the simulated push schedule Close push production without saving.
The system discards all orders created in push
production.
Create the simulated orders Save your schedule.
Result
Manufacturing orders that consume the push product are created in a simulation.

You decide whether these orders are to be created or whether the simulation is to be
discarded.
Working in the Push Production View

Use
The Push Production view contains all required information and functions for solving a push
problem.
In the Push Production view, orders are simulated that consume products from a surplus.
Features
The available functions will be described together with the screen areas:
Planning pool
Overview Planning
tree area
Product details
Overview Tree
In the overview tree, the production process models in which the push product is used as a
product requirement are displayed.
All product receipts and product requirements can be displayed for each production process
model.
Simulated orders from push production are assigned to the production process models and
displayed there.
Functions
To Double-click the
Branch to a production process model Production process model
Branch to an order Order

Display the planning situation for a product requirement in the Product requirement
product details area
Display the planning situation for a product receipt in the product Product receipt
details area
Planning Pool
In the planning pool, the orders that contain surplus quantities are displayed.
They appear in a table display, just as they appear in the product view (PP/DS).
All lines can be changed and have a direct influence on the simulation.
Functions
To Double-click the
Change to the order view Corresponding line
Pushbuttons
Pushbutton Function
Copy For a surplus quantity selected in the planning pool,
the producible quantities calculated for each
production process model are displayed in the output
fields Possible planned quantity and Desired
planned quantity in the planning area.
A selected order is deleted.
Planning Area
In the planning area, orders are created which consume the push product.
All production process models for which the push product is used as a production requirement
are listed here. For each production process model, all product receipts are displayed.
The maximum planned quantity that can be produced from the push product is assigned to
each product receipt. The desired planned quantity is also displayed.
If the planning area table is too detailed, an individual sorting criteria can be used
in an additional column in the planning area. It can be created using the user exit
APOPush1.
Functions
To You must
Branch to a production process model Double-click the production process
model
Display the planning situation for a product in the product details Double-click the product receipt
area
Change the desired quantity Overwrite the default value and confirm
the entry
Pushbuttons
Pushbutton Function

Order A simulated order is created for a selected product

receipt taking the corresponding production process
model into account.
If, due to lot-size constraints, more than one order is
required for the production of the desired quantity,
another window appears in which the number of the
required orders is displayed. The number can be
changed.
After the order is created, all planned quantities are
updated.
Product Details
The planning situation for a product receipt or product requirement selected in the overview
tree is displayed here. The planning situation for a product receipt selected in the planning
area is also displayed here.
All lines can be changed and have a direct influence on the simulation.
Functions
To Double-click
Branch to an order An order line
Pushbuttons
Pushbutton Function
A selected order is deleted.
Calling Up Push Production

Prerequisites
There is a product surplus (push product).
The PP/DS Excess Coverage alert must be activated in the Alert Monitor profile.
Procedures
• Calling up push production from the Product View of the push product:
In the change mode of the product view, choose Goto → Push production.
• Calling up push production from the Alert Monitor:
− Choose Products or Locations for products in the Objects area of the Alert Monitor.
In the Alert Monitor, all product-dependent orders with surpluses are displayed for
the selected objects.
− Select an order.
− With the right mouse button, choose Push production.

− The Push Production view appears and copies all orders with a surplus of the same
product to the planning pool.
Result
You can now simulate orders that consume the push product. See: Using Push Production
[Page 433]
Using Push Production

Prerequisites
There are one or several orders with a surplus of a material and there is no consumer in the
system for this material.
You are in the Push Production view.
Procedure
1. Choose an order with a surplus in the planning pool.
2. Choose Copy.
The system copies the surplus quantity into the planning area. Here it calculates the
quantity of product receipts that can be produced based on the production process
model specified.
3. In the planning area, choose a product receipt.
4. If required, change the product quantity suggested by the system.
A dialog box appears in which you can enter your quantity.
5. Choose Order to create a manufacturing order in a simulation.
If more than one order must be created for the selected quantity due to lot-size
constraints, a dialog box appears in which the system suggests the number of orders
that are required to produce the desired quantity. The number of orders depends on
the lot-size constraints of the leading product in the production process model.
If only one order is required, the additional dialog box does not appear.
6. If required, change the number of orders and confirm the entries.
The system creates the orders in a simulation.
The orders can be corrected or deleted.

See also: Working in the Push Production View [Page 430].
7. Choose to create the simulated orders, or choose to discard the simulation. In this
case, you must confirm your entry.
If you discard the simulation, all orders created in push production are
deleted.

Manufacturing Execution
Integration of the Production Control System

Purpose
This component allows you to transfer data between the APO System as a planning system,
and the external system, which adopts control of production or assembly. In this way,
planning data arrives in production, and production data in planning.
To be able to use this component, you must first of all program the interface of the APO
system in such a way, that the data transfer is possible between the APO system and the
production control system.
You find the definition of the interface using the Business Object Builder (transaction code
SW01, object type /SAPAPO/MF). Here you can display the corresponding parameters or
define your own enhancements (components, events) for this object type.
To program, you have to call up the function module SAP_WAPI_CREATE_EVENT from
the production control system via RFC.
You also have to check Customizing for the workflow. To do so choose Automatic
Customizing in the work step Maintain standard settings for SAP Business Workflow by
following the menu path R/3 Basis Customizing →=Business Management →=SAP Business
Workflow (transaction code SWU3).
For further information on the SAP Business Workflow, see:
SAP Business Workflow (BC-BMT-WFM) [External]
Business Object Builder [External]
Maintenance of Object Types [External]
Event [External]
You can find all other technical information on the integration of the production control system
under Transaction Codes and other Technical Information [Page 444] .
Features
The integration of the production control system takes place using the standard interface of
the SAP Business Workflow.
The workflow itself is not used, but simply the interface and the event manager
from SAP Business Workflow.
This interface supports the following functions:
• Transfer of order sequences to the production control system (see Transfer of Order
Sequences [Page 435] ). Order sequences are APO planned orders, whose sequence
you have optimized in the model mix planning of the APO system.
• Automation of specific actions (see Actions and Functions [Page 439] , Action Handler
[Page 437] ). These can contain the following functions:
− Save tracking information for the relevant production step [Page 440]
− Change status and date of activities of an order [Page 442]

− Carry out repetitive manufacturing backflush (only in connection with a DI System)

− Other freely definable functions
Transfer of Order Sequences

Purpose
You use the transfer of the order of sequences in Repetitive Manufacturing, if you work with
Sequencing. In other words, you want to optimize the sequence of planned orders in model
mix planning, with regard to the possibilities of your production line. For further information
see the SAP documentation Model Mix Planning [Page 126] .
If requested by the production control system (with the event [External]
SEQUENCE_REQUEST), the APO System can transfer order sequences to this system via
the workflow standard interface. Order sequences are APO planned orders, whose sequence
you have optimized in the APO System in model mix planning. If the interface is programmed
accordingly, the APO System automatically transfers the order sequences in the background.
The APO System can transfer the order sequence in blocks. If the production control system
has processed all of the transferred order sequence up until the security buffer, it requests the
next order sequence, that is the one following the last order sequence released in the APO
System. The production control system determines the size of the block and the size of the
security buffer, and thus the time of transfer.
Process Flow
1. The production control system requests the order sequence of the APO System (event
SEQUENCE_REQUEST).
The APO System can only transfer the order sequence if Sequencing is not activated
at the same time in the change mode. If this is the case, an express mail will request
you to leave the change mode.
2. The APO System determines the orders to be transferred and sets their status to Firm.
You cannot make any more changes to the sequence of firm orders.
Do not manually withdraw this automatic firming of orders, which are in transition
from released to firmed orders. This could lead to data inconsistency.
3. The APO System transfers the data to the production control system via RFC.
4. The production control sequence receives the data and confirms the successful transfer
of the order sequence (event SEQUENCE_CONFIRM).
5. The APO System sets the status of the transferred orders to Released. When the orders
are released, control is passed over to the production control system. The user can no
longer change released orders in APO Sequencing.
The production control system does not usually recognize the APO order number,
but manages the orders using its own identification system (such as vehicle
number, engine number). In the data transfer, the APO System must convert the
external identification to the new identification, or vice versa. You define this
conversion in a Business Add-In (technical name /SAPAPO/SEQ_EXTCOMM).

Production
Productioncontrol
control APO-System
APO-System
system
system
Requests order sequence
Business
BusinessAdd-In:
Add-In:
IfIfsafety conversion
safetybuffer
buffer Event sequence_request conversion
shortfall external -> internal
external -> internal
shortfall
Sets
Setsstatus
status
totofirmed
firmed
Sends order sequence

Business
BusinessAdd-In:
Add-In:
conversion
conversion
Checks
Checks internal
internal->->external
external
transmitted
transmitted
orders
orders Confirms order sequence
Business
BusinessAdd-In:
Add-In:
Event sequence_confirm conversion
conversion
Sets
Setsstatus
status
totoreleased
released
If errors occur, the workflow administrator receives an email in the SAP Office
mailbox.
Test Transfer of Order Sequences

Use
The transaction Start-up action handler/transfer of order sequences is for testing or setting up
the integration of the production control system. With this action you can manually trigger
specific events [External] in the APO System, without having to transfer data from a
production control system. In this way you can establish whether possible errors in the data
transfer fall between the production control system and the APO System, on the APO System
side, or not.
For the transfer of order sequences, in this transaction you simulate the events
• SEQUENCE_REQUEST (the production control system requests an order sequence from
the APO System).
• SEQUENCE_CONFIRM (the production control system confirms the order sequence that
it has received from the APO System).
You can also test these events with the standard test in the SAP Business
Workflow (transaction code SWUE).
Procedure
1. In the SAP menu choose Production planning →=Manufacturing execution →=Integration
of production control system →=Start-up action handler/transfer of order sequences
(transaction code /N/SAPAPO/AHTS1).
This takes you to the screen Start-up action handler / Transfer of order sequences.

2. In the tab page Request or confirm sequence, enter the necessary data.
3. Choose Trigger event.
The system confirms that an event has been created.
4. In one of the planning evaluations (sequencing, product view, product planning table,
detailed scheduling planning board), check whether the system has set the status of the
orders requested to Firm (Sequence request) or to Released (sequence confirmation).
In this simulation you can only confirm the orders individually.
Result
The status of the orders is changed accordingly.
If errors occur, the workflow administrator is informed by an email in the SAP Office mailbox.
Action Handler
Purpose
You usually use the action handler in repetitive or flow manufacturing, where recurring
production steps in the system always require the same actions. In action control you ensure
that the APO System automatically carries out the start and the process of these actions with
the relevant planned order (see Actions and Functions [Page 439] ). You can also use the
action handler in order-related production.
The action is automatically started if an order arrives at a specific tracking point and the event
[External] TPOINT_REACHED is triggered.
With the action handler you can administer or process up to 50 000 events daily, depending
on your hardware and the run time of the actions.
Prerequisites
In Customizing in the work step Maintain settings for the action handler (transaction code
/N/SAPAPO/AHC1) you have defined the following information:
• Tracking points
Tracking points specify where or when an action is started.
There is currently no link to the APO iPPE-Line Design. You can choose the
names for the tracking points yourself. You must ensure that these names are
recognized in the production control system in the chosen spelling, and that the
relevant link is programmed here.
• Actions and functions
Actions specify which functions are carried out at a tracking point (see Actions and
Functions [Page 439] ).
• Link between tracking points and actions
You can assign exactly one action to each tracking point.
If you always want to start the same function on a production line on all defined
tracking points, such as saving tracking information, you can also assign the

corresponding function module (here /SAPAPO/AHTG_TRACKINGINFO_SAVE)

directly to the event TPOINT_REACHED (Tools →=Business Workflow
→Development →=Definition tools →=Events →=Event linkage → Type linkage or
transaction code SWETYPV). In this case, the settings in Customizing are
ineffective. The APO System automatically carries out the function that is defined
in the type coupling.
With such a fixed assignment you can, if required, also define start conditions,
such as time restrictions (Tools →=Business Workflow →=Development →
Definition tools →=Events →=Event coupling →=Workflow start conditions or
transaction code SWB_ COND).
Process Flow
1. An order arrives at a tracking point (event TPOINT_REACHED).
2. The production control system transfers the event data to the APO System.
3. The APO System checks in Customizing, which action is assigned to the tracking point.
4. The APO System carries out the action assigned to the tracking point.
SAP APO
Action
Action Handler
Handler Access
actions
Event
Event manager
manager Save
analyses
analyses the
the event
event tracking information
and
and triggers
triggers Change status and date of the
the
the action
action activity of an order
Production backflush
Real
Real Delayed
Delayed
time
time (FIFO
(FIFO queue
queue))
Evaluation
of the
tracking
RFC with tracking point, information
order and customer data
Event Event
Tracking
Tracking point
point 11 TP
TP 22 TP
TP 33 TP
TP 44 TP
TP 55 TP
TP nn
Production control system / assembly control system
Errors
If an individual function cannot be carried out within an action, all functions belonging to this
action, which have already been carried out, are reset. The event is stored, with its data. If
you have removed the cause of error, you can carry out the event again (Tools →=Business
Workflow →=Development →=Administration →=Event manager →=Event queue
→=Administration of the event queue or transaction code SWEQADM_1). In this way, all
functions of the action are carried out again.
According to the settings in Customizing (work step Maintain settings for action handler,
transaction code /N/SAPAPO/AHC1) when such an error occurs, an email is sent to the
person entered in the system as being responsible for the tracking point. If no entry has been
made, the email is sent to the workflow administrator. However, you can also deactivate this
email function.

Actions and Functions

Use
Actions consist of one or more functions. When an action is called up, these functions are
processed individually by the action handler in the sequence determined.
It is possible that actions contain the same functions and only vary in the
sequence in which the functions are to be processed.
If an individual function cannot be carried out within an action, all functions belonging to this
action, which have already been carried out, are reset. In this way, data consistency is
guaranteed.
In Customizing, some actions are included that contain the functions named
below, either individually or in combination.
Prerequisites
See Action Handler [Page 437] .
Features
Standard functions
Function modules for the following functions are delivered as standard with the Action
Handler:
• Save tracking information for the relevant production step [Page 440] (function module
/SAPAPO/AHTG_TRACKINGINFO_SAVE).
• Change status and date of activities or an order [Page 442] (function module
/SAPAPO/AHTG_ORDER_MODIFY)
• Carry out repetitive manufacturing production backflush (function module
/SAPAPO/AHTG_CONFIRM_CREATE)
You can only use the function “Production backflush” if you have an SAP DI
System as your OLTP System.
With this function, the production backflush in APO begins. In this way, the following
postings can be carried out in the APO System: inventory posting, reduction of
requirements, adjustment of dates at goods receipt, adjustment of reporting point
quantities. In the DI System additional services and costs can be posted for
components per reporting point.
The link between tracking points and the reporting points in the backflush, must
be managed in the production control system.
Programming additional functions

You can copy the function module /SAPAPO/AHTG_REFERENCE_EXAMPLE and use it as
a template for programming other functions.
Example for possible functions:
• Automatically print data specific to work center (shop papers, component lists).

• Create WM transfer orders for components that are not often required.
Tracking
Use
Tracking is a special function in the Action Handler, which is used to monitor the production
process and to track the status of each planned order, and thus to ensure quality. For this
purpose, at specific tracking points (these correspond to lines, work centers or areas in
production such as picking, packing, shipping) specific information is saved in the APO
database.
Possible questions when using tracking are:
• Which tracking points has an order already passed through on a specific day at a specific
time?
You see whether the order has passed through specific tracking points several times,
if errors have occurred in the production process. In the automotive industry, for
example, this could be when spraying a vehicle.
• How many, or which orders have passed through a specific tracking point in a specific
period of time.
If you have saved the relevant data for the tracking point using a Business Add-In
(see below), you will be able to establish this.
− Which orders have been manufactured in a specific model. For example, in the
automotive industry, which vehicles have been sprayed metallic, and which are
standard, or which vehicles have air conditioning.
− Which processor was responsible for the activity in a resource at a specific time
Prerequisites
See Action Handler [Page 437].
In Customizing in the work step Maintain settings for action handler you have defined the
• Tracking points and their sequence
• Link between the standard actions, which contain the function Save tracking information
(/SAPAPO/AHTG_TRACKINGINFO_SAVE), and the tracking points desired.
Instead of the standard actions, you can also define your own actions, to which
you assign the function Save tracking information.
Features
When an order reaches a tracking point, the system saves the tracking information in the
APO database. The following are standard: event date, event time, tracking point, APO order
number, alternative identification, external date, external time.
You can extend this standard data using a Business Add-In (technical name
/SAPAPO/AHT_TRACKING).

The tracking information is not archived automatically, but remains in the

database. You can delete it manually using a report.
You can access and evaluate the saved tracking information at any time (see Access
Tracking Information [Page 441] ).
Access Tracking Information

Procedure
1. In the SAP menu choose Production planning →=Manufacturing execution → Integration
of the production control system →=Tracking information (transaction code
/N/SAPAPO/TI01).
This takes you to the screen Evaluation Tracking Information.
2. According to the criteria, select Order Alternative identification or Tracking point.
Enter the tracking points that you are responsible for, as individual values, and
save your entries in the display variant.
Customer data programmed using a Business Add-In cannot be used for the
selection.
3. If necessary, change the Selection horizon proposed by the system.
4. Choose .
If you have not restricted the data selection according to order, alternative
identification or tracking point, a warning message appears. Restrict the selection
to increase system performance.
This takes you to the display of the tracking records for the selection. In the left
screen area you see a navigation tree that is grouped according to tracking points. By
double clicking on a tracking point you receive a list of the relevant tracking records in
the right-hand screen area.
5. You have the following options for processing:
Function Accessing the function What you should know
Show/hide navigation
tree
Expand/collapse object Click on the triangle on the left of the
in navigation tree object
Group objects in the Time, Order, Alternative
navigation tree identification, Tracking point
Display tracking records Double click on the object All tracking records on this
for an individual object object are in the right-hand
in the navigation tree. screen area
Customer data, programmed
using a Business Add-In is

displayed in your own columns

Display tracking records 1. Select block of objects with All tracking records for these
for several objects in SHIFT or several separate objects are in the right-hand
the navigation tree. objects with STRG screen area
2. Drag selected objects to the table Customer data, programmed
in the right-hand screen area, or using a Business Add-In is
click right mouse button and displayed in your own columns
choose Adopt selection.
Display tracking records You receive tracking records
for all objects in the navigation
tree
Delete tracking record Select tracking record, + The tracking record is only
selected for deletion It is only
actually deleted on saving
Update display
Check which orders are Select 2 different tracking points and It is a prerequisite for this
currently between two choose (or alternatively click right function that you have defined
tracking points mouse button and choose Calculate in Customizing in the work
Orders in process) step Settings for action
handler, how the tracking
points follow each other
(predecessor/successor
relationship)
Change to order Double click on order number in the This navigation is only
processing tracking record possible, if the order still exists
in the system, and no final
confirmation has been made
Other functions See standard documentation
SAP List Viewer (ALV) Grid
Control (BC-SRV-ALV)
[External]
Changing Activities of an Order

Use
Changing activities of an order is a special function in the Action Handler that is used to make
corrections. For this purpose, at specific tracking points (these correspond to lines, work
centers or areas in production such as picking, packing, shipping), activities are rescheduled
and/or the activity status is changed.
This can be useful in the following cases:
• If for any reason, released orders could not be produced, you must reset the status of the
activities of these orders, so that the orders can be transmitted to the production control
system again.
• If planned orders are not available in the APO System, but the resource planning or
sequencing is not carried out in the APO System, but in the production control system,
the events of the planning must be transferred back to the APO System, so that they are
available for other planning.

• Even if you carry out the planning in the APO System, it can be of use, to ensure quality,
to transfer the actual production data of the production control system to the APO
System, to update the target production data.
Prerequisites
See Action Handler [Page 437].
In Customizing in the work step Maintain settings for action handler you have defined the
• Tracking points
• Link between the standard actions that contain the function Change status and date of
activities of an order (/SAPAPO/AHTG_ORDER_MODIFY) with the tracking points
desired.
Instead of the standard actions, you can of course define your own actions, to
which you assign the function Change status and date of activities of an order.
Features
The changes always refer to one activity of an activity type per resource.
You can make the following changes:
• Change status and/or
• Change date
You enter a strategy profile (backward scheduling, forward scheduling etc) and
depending on the profile you have chosen, either an activity start date or an activity
end date. If you enter both values, the system ignores the date that does not match
the strategy profile. If you do not enter a strategy profile, the system sets backward
scheduling with an infinite number of capacities, as standard.
You enter the target values by the relevant programming in the production control system.
Test the Action Handler

Use
The transaction Start-up action handler/transfer of order sequences with the transaction code
/N/SAPAPO/AHTS1, is for testing or setting up the integration of the production control
system. With this action you can manually trigger specific events [External] in the APO
System, without having to transfer data from a production control system. In this way you can
establish whether possible errors in the data transfer fall between the production control
system and the APO System, on the APO System side, or not.
For the action handler, you simulate the event TPOINT_REACHED (reaching a tracking point)
and start individual functions.
•
You can also test this event with the standard test in the SAP Business Workflow
(transaction code SWUE).
Prerequisites
See Action Handler [Page 437]

Procedure
1. In the SAP menu choose Production planning →=Manufacturing execution →=Integration
of production control system →=Start-up action handler/transfer of order sequences
(transaction code /N/SAPAPO/AHTS1).
This takes you to the screen Start-up action handler / Transfer of order sequences.
2. Enter the necessary data on the tab page Tracking point reached.
3. Choose Trigger event.
The system confirms that an event has been created.
4. Check
− in the tracking information display (transaction /N/SAPAPO/TI01) , whether the
system has saved the tracking information, or
− in one of the planning evaluations (sequencing, product view, product planning table,
detailed scheduling planning board ) whether the system status and date of the
relevant activities has changed.
Result
The system carries out the corresponding action.
If errors occur and the mail function is active in Customizing, an email is sent to the person
entered as responsible for the tracking point, or to the workflow administrator.
Transaction Codes and Other Technical Information

Transaction code Function
SAP Business Workflow
SWU3 Maintain standard settings for SAP Business
Workflow
SWO1 Business Object Builder
SWETYPV Event type coupling
SWB_COND Workflow start conditions
SWEQADM_1 Administration of the event queue
SWUE Create event (test)
Integration of the Production Control
System
/N/SAPAPO/AHC1 Maintain settings for action handler (Customizing)
/N/SAPAPO/AHTS1 Start-up action handler/transfer of order sequences
/N/SAPAPO/TI01 Evaluation tracking information
Other technical information

/SAPAPO/MF Object type of SAP Business Workflow for
integration of production control system
SAP_WAPI_CREATE_EVENT Function module for integration of production

control system
/SAPAPO/AHT_TRACKING Business Add-In for displaying additional
customer-specific tracking information
• /SAPAPO/AHT_TRIF: Table with standard
data for tracking
• /SAPAPO/AHT_TRCS: Table with Customer
Include for additional data for the tracking
point.
• /SAPAPO/AHT_TRCO: Table with Customer
Include for additional data for the order
/SAPAPO/SEQ_EXTCOMM Business Add-In for conversion of external and
internal order identification
/SAPAPO/AHTG_TRACKINGINFO_SAVE Function module “Save tracking information”
/SAPAPO/AHTG_ORDER_MODIFY Function module “Change status and date of
activities of an order”
/SAPAPO/AHTG_CONFIRM_CREATE Function module “Carry out confirmation”
/SAPAPO/AHTG_REFERENCE_EXAMPLE Function module template for programming your
own functions
SEQUENCE_REQUEST Event “Request order sequence”
SEQUENCE_CONFIRM Event “Confirm order sequence”
TPOINT_REACHED Event “Tracking point reached”
Production Backflush
Purpose
You use this component if you work in an environment with a high volume of orders with small
order quantities – often only one piece. The new backflushing function was developed
specifically for this “high-volume-scenario” which is particularly common in the Automotive
and High-Tech Industries. The backflush can now be carried out significantly faster than has
been possible up to now. This is partly due to the new link to the APO system (where the
creation of the backflush is separated from the processing of the backflush data) and to the
increased separation of the Logistics and Controlling functions.
The backflush data is created in APO due to the system’s high availability. The subsequent
processes, that is, the execution of the stock postings, are carried out in the R/3 System
separately from the creation in APO.
For this application, you require a link to APO. Before entering the backflushes in APO, the
relevant master data is transferred from R/3 to the APO System via CIF. The transaction data
entered is sent to the R/3 System.
A backflush can only be carried out for a reporting point which has been defined in Line
Design in the Integrated Product and Process Engineering (iPPE) function. The product
structure of the materials to be backflushed must therefore be maintained in iPPE.

Integration
The Production Backflush is currently only available for Repetitive Manufacturing. A direct link
exists to Periodical Product Cost Controlling via the product cost collector.
Features
The product backflush includes the following functions:
• You can execute the backflush for make-to-order and make-to-stock repetitive
manufacturing.
• You can also backflush at reporting points in make-to-order production.
• To speed up the processing in the R/3 system, synchronous [External] and

asynchronous [External] goods movements are posted separately.
• The goods receipt in the make-to-order procedure is valuated at goods receipt on the
basis of the material consumed. This significantly improves performance.
• WIP (work in process) can be calculated in Controlling.
• You can archive the backflushes using an archiving object.
• The backflush data is updated in the Business Warehouse (BW) where it can be
evaluated.
Constraints
In this release, activity postings and corrections of actual variants are not yet possible. The
integration with other components as the HR update is carried out step-by-step.
Backflush Procedure
Purpose
This process describes the procedure of the production backflush from the creation of the
backflush data right up to the archiving of this data.
Prerequisites
Various prerequisites must be fulfilled in the Automotive System and in APO before you can
backflush your data.
In the Automotive System:

• You must create the integrated product and process engineering (iPPE).
• You must create production versions and maintain the iPPE access. The production
version is only used to find the product cost collector.
• You must create classes and characteristics.
• You must maintain a supply area.
• You must create an integration model in the CIF to transfer this master data.
• You have to create sales orders with characteristic valuations for make-to-order
production and an integration model for the current transmission to APO.
• You must maintain the settings for the valuation types and for batch and stock
determination in the repetitive manufacturing profile.

The settings required for backflushing in Repetitive Manufacturing are not valid
for Production Backflushing. For example, in the production backflush, you
always backflush at reporting points which means that you do not have to
maintain the setting in the REM profile for the reporting point backflush.
See also the IMG texts on production backflushing.
• You must create a product cost collector.
In the APO System:

• You have selected and created a confirmation profile. See Defining and Setting Profiles
[Page 450] .
• APO (planned) orders must exist in APO.
• You have defined reporting point types in the master data. See: Defining Reporting Point
Types [Page 452].
• You have maintained the assembly and components in the product master in view
WE/WA, that means you have set synchronous indicators for the synchronous update
[External] The SAP standard setting is asynchronous.
• Assembly classes, characteristics and the classification are transferred by the iPPE
integration diagram. If the classification was not transferred by the iPPE, you have
assigned the assembly to a class analogous to R/3 (Transaction: CL20N).
Process Flow
The following graphic describes the production backflush procedure with APO and R/3
integration:
APO 3.0 Automotive 2.0
Buffer
Scenario without RPM

Scenario with RPM
Result
• The backflush is always carried out for an APO planned order. Here, you can create the
backflush data for a sales order without specifying any order or directly for an APO
planned order: A creation document is created when backflushing which is then used to
create the backflushing document in R/3 once the backflush data has been transferred

back to the R/3 system. The stock posting is carried out in R/3. Stocks and requirements
are simultaneously adjusted in APO. Capacities are reduced in APO.
• You create the backflush on a separate interface in APO. To do this, choose Production
Planning and Control → Repetitive Manufacturing → Backflush → Production Backflush
in the APO System.
There are three tab pages for creating a backflush depending on its production type.
Make-to-order repetitive manufacturing: Sales orders are created in the R/3
System and the orders are transferred to APO with their characteristic value
assignments via the CIF. Here, MRP is carried out for materials relevant to planning
in APO using the planning matrix (RPM). Materials relevant to planning in R/3 are
planned in the R/3 System with MRP.
Make-to-stock repetitive manufacturing: APO planned orders for make-to-stock
repetitive manufacturing must exist in APO. The selection of the order is made by
location and product. Line planning and the explosion of the components is carried
out in APO.
Make-to-order: The order selected from the APO (Plan-) is entered directly here.
See also: Creating the Backflush [Page 449]
• After creating the backflush, the data is transferred by CIF to R/3 where it is saved in a
buffer in the database. Synchronous goods movements are posted immediately. This
includes the goods receipts and the materials for which you set the Synchron.post GI
indicator in the product master in APO. Asynchronous goods movements, that is, all
goods issues that are not to be posted synchronously, are selected in background
processing later and posted cumulatively.
See also: Processing the Backflush [Page 455]
• Errors can occur at goods receipt and at goods issue. For example, there may not be
sufficient warehouse stock available or important data, such as the issue storage location
may be missing. Backlogs are created for goods issues or receipts which could not be
posted.
See also: Processing Errors [Page 453]
• In certain circumstances, for example, if a product cost collector is missing, a backflush
may not be transferred to the R/3 system. The CIF is then notified of relevant errors
together with suggested solutions.
See the documentation in the APO SAP Library about the qRFC-Monitor.
• The backflush is always reversed in APO. The reversal is always a posting with a
reversed movement direction. This means you enter the quantity in APO that was already
backflushed and which is to be backflushed with a negative indicator. A document-
orientated cancellation does not exist.
• The backflush data is archived in the automotive system.
See also: Archiving Backflush Data from the Production Backflush [Page 459]
• The backflush data is updated in the Business Warehouse (BW).
For more information, refer to the documentation in BW.

Backflush Process in Sales-Order-Related Production

Purpose
This process describes the process of the production backflush, when you work with sales-
order-related production.
Prerequisites
• You have created a sales order in the R/3 System and transmitted it the APO System via
CIF.
• You have maintained the basic data from iPPE in the R/3 System and transmitted it to the
APO System.
Process Flow
• In APO, material requirements planning for APO products takes place with the planning
matrix and an APO planned order is generated from the sales order.
• Then the entries are written to the planning matrix, that is, the component requirements
are recorded for the sales order. Refer to the documentation in the APO SAP Library
about the Planning Matrix [External].
• You can determine the necessary requirements as follows:
1. The system selects a production version for the material. This selection takes places
using the quantity in the order compared with the lot size of the production version, or
using the dates and validity of the production version. If the production versions are
the same, the first one is taken.
2. An iPPE access object is determined from the production version, as well as the
material and the plant.
3. In the iPPE access object, a product structure with an alternative and variant is
defined, as well as a process structure and a line.
4. The product structure is exploded, the object dependencies are evaluated in the
variants of the structure nodes, and the necessary components are determined.
5. Then, the corresponding activities are evaluated for the components selected from
the process structure, which comes from the iPPE access object. In the activity part
of an operation, all activities of this operation are selected.
6. The active line balance is read from the line network, and thus the line network is
exploded.
• When using the planning matrix, only the entire order quantity (often 1) can be
backflushed; it is not possible to backflush partial quantities.
• The production backflush is carried out for the APO planned order or the sales order.
• The rest of the process takes place in the same way as with other types of production.
See also: Backflush Procedure [Page 446] .
Creating the Backflush

Use
The interface for entering the backflush data is in the APO System.

Prerequisites
• In Customizing for the APO System, under Production Backflush → Set Profile, you have
created or selected a profile. Refer to Defining and Setting Profiles [Page 450] .
• In Customizing for the APO System, under Production Backflush → Specify Reason for
Variances, you must define possible reasons for variations or for scrap during the
production backflush. However, the specification of the scrap reason is not mandatory
and is only used for documenting the backflush.
Features
• You enter the backflush data depending on the type of production.
• No separate function for reversal exists in production backflushing. You can only reverse
a backflush by creating another backflush with negative quantities. Therefore, this is a
document-neutral reversal.
Activities
1. To do this, choose Production Planning Control → Repetitive Manufacturing →
Production Backflush → Create in the APO System.
2. Choose the appropriate tab page depending on your production type and enter an order
or a product.
3. If you have maintained the Final confirmation / Partial confirmation field in your profile,
choose one of the options listed in the input help.
Partial confirmation: Further backflushes are expected at the reporting point.
Final confirmation, irrespective of quantity: No further backflushes are expected at the
reporting point.
Final confirmation dependent on backflushed quantity: The system makes the
decision. This means that if the entire expected quantity is backflushed, it posts a
final confirmation; if only a small quantity is backflushed as the order quantity, it posts
a partial backflush.
4. In the Quantities section of the screen enter the quantity you want to backflush.
5. Switch to Scrap, if you want to post a scrap quantity instead of a yield. When posting
scrap, in the Reason field, use the F4 help to select one of the scrap reasons you defined
in Customizing.
6. In the Dates section of the screen, enter the posting date and time zone as well as the
execution start and end of the backflushed data and the forecast finish of all the data to
be backflushed so that the system can adjust the capacity requirements.
7. Record the entry data, the batch number, if necessary and any required text.
8. Choose Delete entry, if the entries were wrong and you want to start again.
9. Save your entries.
The system displays a success message.
Define and Set Default Values for Profiles

Use
For the production backflush, you define a profile in the APO. SAP delivers two standard
profiles, SAP1 and SAP2. You can copy and modify these.

A dialogue box requires you to select a profile the first time you call for a backflush to be
produced. In the user entry maintenance, you can set a profile so that the dialog box no
longer appears in the application.
Procedure
Define profile
1. In Customizing for APO choose Supply Chain Planning → Production Planning and
Detailed Scheduling → Production Backflush → Set Profile.
2. Select a profile and choose Display/Change or choose New Entries, if you want to create
a new profile.
3. Compile the tab pages and fields that you require for your backflush.
For more information, refer to the activity documentation in Customizing.
Set profile:
1. From the application, choose System → User defaults → Own data → Maintain user
entries.
2. Enter the parameter /sapapo/ppc1 and the value SAP1, SAP2, or your self-defined
profile.
Define Logical System

Use
If you work with sales-order-related production, you have to define a logical system for the
production backflush, as sales orders are always created in an R/3 System, and are
converted into planned orders by a heuristic in APO.
It is technically possible for several R/3 Systems to be linked to an APO System. Therefore, it
is necessary to specify the logical system which has the sales order.
In the user defaults, you can set a logical system as a parameter.
Procedure
Set Logical System:
1. Choose Change /Logical System.
2. Enter the logical system in the dialog box.
Set logical system as parameter:

3. From the application, choose System → User defaults → Own data → Maintain user
entries.
4. Enter the parameter /sapapo/ppc1 and the relevant system as the value.
5. Enter the parameter /sapapo/logsys and the value SAP1, SAP2, or your self-defined
profile.

Defining Reporting Point Types

Use
Production backflushes are always carried out at reporting points. There is no backflush
without a reporting point. Therefore, at least one reporting point must be defined at the end of
the line network.
You define the reporting points for a line segment in Line Design in Integrated Product and
Process Engineering, and you assign it various reporting point types. The reporting point
determines, whether in a production backflush
• the capacity is reduced,
• the components are backflushed,
• a goods receipt is posted (this indicator can only be set for one reporting point, usually
the last of the line hierarchy),
• the preceding reporting point is automatically backflushed.
An automatically backflushed preceding reporting point can then no longer be

manually backflushed, but automatically backflushed with every further backflush.
Reporting points RP1, RP2, RP3 are assigned to a line in this sequence; RP3 is a
reporting point of this type.
For RP1, 8 pieces have already been manually backflushed and for RP2, 1 piece.
RP3 has not yet been backflushed.
• A backflush for RP3 with a quantity of 5 pieces causes an automatic backflush for RP2 for
4 pieces. RP2 can then no longer be backflushed manually.
• A new backflush for RP3 for 5 pieces creates a further backflush of 5 pieces for RP2, and
of 2 pieces for RP1. From now on RP1 can also no longer be backflushed manually.
Prerequisites
You have defined reporting points in Line Design. You can determine two reporting points for
each line segment, one at the beginning and one at the end of the segment. See also
Assigning Reporting Points [External] .
In a line hierarchy it is possible that there are two identical reporting points on
different hierarchy levels. For the backflush, one of the two reporting points is
displayed.
Procedure
1. In Customizing for APO choose Master data → Integrated Product and Process
Engineering (iPPE) → iPPE Line Design → Define reporting point types.
2. Enter the description of the reporting point type and select the indicator you want.
3. Save your entries.
If you have set the indicator Backflush components for a reporting point, then not
only those components are backflushed that are assigned to this reporting point,
but also the components of the preceding reporting points, as long as these do

not have the same indicator and as long as they have components assigned to
them. Afterwards all previous reporting points, except ones with the same
indicator, are tested and these components that are assigned to reporting points
are backflushed.
The same procedure is used for the reporting point type Reduce capacities.
For matrix orders, alongside the rules mentioned above, there is a special rule
that the components of a line segment are backflushed at the first reporting point
of the line segment, as long as the reporting point has the indicator Backflush
components. This does not necessarily have to be at the end of the line segment.
Display Backflushes
Use
If you have backflushed successfully, you can display the backflushes in APO.
Features
• You use selection criteria to select the backflushes.
• You can create a list of backflushes.
• You can display detailed data (this interface corresponds to the screen for entering the
backflush data).
• You can display administrative data.
Activities
1. In the APO menu choose Production planning → Manufacturing execution → Production
backflush REM → Display production backflush REM.
2. Enter one or more selection criteria. Under Representation select a grouping type (sales
order, product, or order) and choose Execute.
3. Expand the overview tree.
The system displays a list of order numbers, the reporting points and the
backflushes that have taken place for these reporting points.
5. To access the detailed view, select a backflush and choose Detail.
This takes you to the initial screen for entering backflushes with the data entered.
6. You can also call up the administrative data via Goto → Administration on/off.
If the fields Synchronous posting open and Asynchronous posting open are
selected, these postings are still outstanding.
Processing Errors
Use
Errors may occur when posting goods receipts and goods issues. It is possible that the
logical stock level is insufficient at the time of the withdrawal posting. Or, errors occurred in
the master data if, for example, the system could not determine a storage location or if the
material data is locked by another user.

A goods receipt posting and a component backflush can only be carried out successfully if the
current stock quantity completely covers the requirements quantity of the material to be
backflushed. If this is not the case, the system creates a backlog for the complete
requirements quantity.
If you set stock determination, the system posts the available quantity and
creates a backlog for the rest quantity.
Integration
You can only process errors in production backflushing by postprocessing in individual
records.
Activities
See also Postprocessing Backlogs from Individual Records [Page 454]
Postprocessing Backlogs In Individual Records

Use
The system creates a separate postprocessing record for every error when backflushing
components or when posting the goods receipt. This is an individual document with document
items for the individual materials. The postprocessing individual document is also referenced
in the backflush document of the production backflush. Every individual document contains
the date of the backflush. When postprocessing, the system creates a material document per
date listing the postprocessing items for this date.
When postprocessing, the system sorts the individual documents according to the time
sequence. That is, you process the oldest document first. You can only postprocess a
postprocessing record on the basis of this individual document if you can post the complete
quantity in this individual record.
You can also set the system so that negative stocks are posted instead of
backlogs for the goods issue. To do this, you must allow posting to negative
stocks in Customizing for Inventory Management and you must also set the
appropriate indicator in the material master record, in the general plant data.
Procedure
1. In the SAP overview tree, choose Logistics → Production → Repetitive Manufacturing →
Production Backflush → Postprocess Individual Component.
The system displays the screen Automatic Goods Receipts: Error Handling.
2. Enter the material you want to postprocess and further selection criteria, such as
production version or order, if required.
3. Choose Execute.
The system displays the initial screen for goods movements with errors.
4. Select the appropriate components and choose Change details.
The system displays the material overview.
5. You can make the following changes:

• Enter the production storage location for the material if this field is empty. This can
happen if you have not entered a production storage location in either the production version,
the material master or in the BOM item.
• If necessary, check the additional data for the material by choosing Select.
6. Save your data.
Processing the Backflushes

Use
You use this report to reduce the work list for backflushes in R/3. Once the backflush data
reaches the R/3 system from APO, it is posted. Goods receipts are considered as
synchronous goods movements and are processed immediately as materials which have the
indicator Synchron.post. GR in the APO product master. The work list, which is processed
by the report, consists of asynchronous goods movements [External] and synchronous goods
movements [External] which could not be posted immediately due to processing errors.
Prerequisites
You have created backflushes in the APO system and the data has been transferred via the
CIF interface to the R/3 System.
You have defined an RFC group in Customizing for production backflushing if you want to use
parallel processing for backflushing.
Features
Using the report, you can process the most extensive worklist of backflushes using parallel
processing. Here, the backflushing data is grouped into data packages and is processed
simultaneously on several servers. The system waits for the completed processes to return
and then assigns new processes to the resources now free. Processes which could not be
completed due to system and communication errors remain in the worklist and are
reprocessed the next time the report is started.
SAP delivers a preset version of the report which you can change and define as your own
variant by choosing Goto → Variant → Save as variant.
Activities
1. To execute the report in the system choose Logistics → Production → Repetitive
Manufacturing → Production Backflush → Postprocessing backflushing processes.
2. Set the processing parameters and the parameters for parallel processing. Under
Backflushes Selection, you can set whether you want to select asynchronous or
synchronous or both types of goods movements.
3. Choose Execute.
4. You automatically receive a log for processing the backflush. You can find a detailed log
under Tools → Business Documents → Environment → Application log.

Product Cost in Sales-Order-Related Prod. with

Reporting Points
Purpose
You are producing in high volumes on a sales order basis and are using the Advanced
Planner & Optimizer (APO). You want to base your calculation of the inventory values at the
goods receipt stage on confirmed, sales-order-related costs. You want to record the work
progress in the system. This enables you to determine the work in process and scrap on the
basis of the costs of the sales orders.
The assignment of product cost collectors to cost object hierarchies does not
apply in this case.
In this scenario, multiple valuation approaches/transfer prices are not possible
when the system calculates work in process and scrap.
Prerequisites
You are using the Advanced Planner & Optimizer 3.0.
For the configurable material, you have created the material master and the Product Variant
Structure [External] with iPPE line design [External].
You have created a product cost collector for the configurable material (preferably with the
controlling level Material/Production Plant/Planning Plant/Production Version or Production
Line. It is also possible to use the combination Material/Production Plant/Planning Plant). You
must have assigned a results analysis key and variance key to the product cost collector.
If you have made your confirmations from the Logistics component up to now,
and are confirming with the APO system for the first time, you must create a new
production version as well as a new product cost collector for this production
version. You can only do this if the existing product cost collector has been
created with Controlling level Material/Production Plant/Planning Plant/Production
Version or Production Line.
Valid cost estimates must exist for the material components. If none exist, the system
determines the prices from the material master.
Process Flow
1. A planned order is automatically generated in the APO system from the sales order of
the Sales application component. From the product variant structure, the system
generates the Rapid Planning Matrix (RPM), which contains the material components
required for production. From the RPM, requirements planning is created according to the
order lot size, and the component list relating to the order for the confirmation is
determined dynamically.
2. Confirmation:
You create confirmations at reporting points during production of the product for the
order. The system determines which material components must have been withdrawn
on the basis of the RPM. This means that the actual withdrawal always matches the
target withdrawal. The order status is updated in the APO system.
An entry document is created for each confirmation in the APO system. From the
entry document, a confirmation document is generated in the Production Planning
component (PP). The goods withdrawals for the same material component and the
same product cost collector are aggregated, and you post them periodically in
inventory management of the APO system and to the production cost collector using

transaction PPCGO (Parallel Processing of Confirmations). To this end, SAP

recommends running report PPC1_CONF_GO as a scheduled background job.
3. Goods receipt:
When the product has been produced and you have entered the final confirmation,
the stock segment is debited with the value of the goods receipt and the product cost
collector is credited with the same amount. The strategy sequence [External] when
determining the valuated sales order stock is different to the sequence in standard
Product Cost by Sales Order. Since no sales order cost estimate was created owing
to the high production volume, costing is carried out at the time of the goods receipt.
This goods receipt cost estimate [Page 458] uses the data from the components in
the backflush documents.
To improve performance of the confirmation process, you can specify that the
quantities are posted independently of the values posted. In such cases, you
calculate the values asynchronously in a valuation run. For more information,
refer to the standard SAP Library for Controlling in the Cost Object Controlling
topics under Product Cost by Period → Period-End Closing in Product Cost by
Period → Separation of Value Calculation from Goods Movements: Effects on
Cost Object Controlling.
4. A cost component split is saved to the database for each cost estimate. Saving the
itemization is not recommended due to the high data volume. You can make a setting in
the costing variant in Customizing so that the itemization is only saved in case of an error.
5. Period end:
At the end of the period, the work in process (WIP) and the scrap variance are
calculated and reported in accordance with the individual product value. This
valuation is based on the costing variant specified in the product cost collector under
Cstg variant planned.
In variance calculation, the scrap variance is the value of the total scrap, because
the planned scrap is always zero. The APO system does not take into account any
planned assembly scrap or operation scrap in the Logistics component.
All other variances are classified as remaining variances. Owing to the high number
of units, the difference between the debit and credit is not allocated to the sales order
stocks. Instead, this difference is posted directly to the price difference account.
6. Cancellation:
You cannot cancel a confirmation with reference to a document.
7. Error handling:
It is possible for a posting to be only partly free of errors. In such cases, the part that
was successfully posted is not reversed. You therefore have to carry out
postprocessing in order to post the part that had errors. It is essential that you check
the log.
For error handling in connection with valuation, you can use customer enhancement
GRCOST01 to carry out a plausibility check of the costing results or to set a price for
the goods receipt.
See also:
For more information, refer to the standard SAP Library under:
Controlling → Cost Object Controlling → Cost Object Controlling: Sales-Order-Related
Production →=Cost Analysis in Mass Production on the Basis of Sales Orders
Controlling → Cost Object Controlling → Product Cost by Period → Product Cost Collector →
Product Cost Collectors in Sales-Order-Related Production

Goods Receipt Costing

Use
This function is part of Product Cost by Period in Sales-Order-Related Production with
Reporting Points [Page 456] and is performed automatically by the system during inventory
posting. It is used to valuate goods receipts and to credit product cost collectors. The sales
order cost estimate does not apply; instead, a cost estimate is created at the time of the
goods receipt.
Integration
You can check the goods receipt cost estimate by choosing Cost Object Controlling →
Product Cost by Sales Order → Cost Estimate → Order BOM Cost Estimate → Display.
To archive the goods receipt cost estimate, you use the same archiving object as that used
for sales order costing.
Prerequisites
When you create sales orders, you must use a requirements type that ensures that the
costing variant contains the following settings:
Access to non-order-related cost estimates for the material components has been defined in
transfer control. If you have not defined a transfer control ID, the system uses the prices from
the material master for the material components.
In the Update tab page, the setting Select only if errors occur should be selected
under Save itemization. This setting limits the data volume when there is a large
number of cost estimates.
If you use multiple valuation approaches/transfer prices, you must have defined a costing
variant and grouped it for each valuation view.
For more information, see Customizing for Cost Object Controlling under Product Cost by
Sales Order → Preliminary Costing and Order BOM Costing → Product Costing for Sales
Order Items / Order BOMs.
To make sure that the sales order cost estimate is excluded, the setting May not be costed
(B) must be selected in the Costing field in the requirements class used for the sales order.
For more information, see Customizing for Cost Object Controlling under Product Cost by
Sales Order → Control of Sales-Order-Related Production.
Valid cost estimates must exist for the material components. If none exist, the system
determines the prices from the material master.
Note also the prerequisites under Product Cost by Period in Sales-Order-Related Production
with Reporting Points.
Features
This type of costing has the same functions as those provided by sales order costing. For
example, the cost component split can be used in the application component Profitability
Analysis (CO-PA). The differences are as follows:
• Costing is not carried out until the time of the goods receipt.
• The goods receipt is costed on the basis of the backflush documents on the components
used.

• Instead of costing the material components, the system uses data from existing cost
estimates (such as valuation data and cost component splits) or the prices from the
material master or individual requirements stock segment of the material components.
• To improve the performance of costing, the application buffer [External] is used.
• The results cannot be used in the Sales and Distribution component (SD) for pricing
purposes.
• A goods receipt cost estimate that has no errors cannot be modified manually.
Work in Process in Sales-Order-Related Reporting

Point Backflush
Use
You can valuate your unfinished products by calculating the work in process (WIP). This
enables you to determine which costs on product cost collectors are for products that have
not yet been transferred into finished goods inventory.
Prerequisites
If you want to settle WIP in Financial Accounting, you must do the following in Customizing for
Controlling under Product Cost Controlling → Cost Object Controlling → Product Cost by
Period → Period-End Closing → Work in Process:
• Define posting rules for settling work in process
• Under Define Results Analysis Versions, select the indicator Transfer to Financial
Accounting in results analysis version 0 (WIP/Results Analysis (Standard)).
You must have assigned a results analysis key to the product cost collector. SAP
recommends that you use results analysis key 000005 (Quantity-based valuation). You
cannot change the assignment once you have calculated WIP the first time.
Features
Work in process is valuated on a quantity basis. With every confirmation, the quantity of input
components withdrawn that was not confirmed as scrap is registered as work in process. This
work in process is credited with the quantities used for the goods receipt that was posted to
the product cost collector. The resulting WIP quantities are valuated in accordance with the
costing variant in the product cost collector, which is defined under Cstg variant planned. This
value is shown as work in process on the product cost collector.
Activities
For the results analysis version, always select version 0 (WIP/Results Analysis (Standard)).
Archiving Backflush Data from the Production

Backflush
Definition
Archiving object PP_CONF for archiving backflushing data (production backflush, component
IS-A).

Use
You can use this archiving object to archive backflushes that no longer have to be
immediately accessible in the system. Due to the high data volume, SAP recommends you
regularly archive backflushes.
When you use the Business Warehouse function, you can only begin to archive
when the new data records have been transferred into the BW.
Structure
The following functions are available for archiving.
Action Description Report
Archive The archiving program records the PPC1_CONF_ARCH_WRI
database tables of the production
backflush in an archiving file with a
special archiving structure. If the
procedure was successful, it deletes
the data from the system directly after
archiving depending on your settings.
Otherwise, you can start the deletion
program separately.
Delete The deletion program deletes all PPC1_CONF_ARCH_DEL
movement data of the archived
database records from the system.
Postprocess The postprocessing program deletes PPC1_CONF_POST_PROC
entries in a supplementary table which
only contains a small amount of data.
The deletion of this data was therefore
moved from the deletion program to the
postprocessing program to improve
performance.
The postprocess can be executed after
the archiving run or you can start it
independently of the archiving process.
Evaluate You can use the evaluation program to PPC1_CONF_ARCH_DSP
display the data of the archived
backflushes. You cannot display an
individual document or an individual
record.
Administration Using this function, you can display the
archiving runs that have already been
carried out.
Integration
A display program in which you can select backflushes by orders, for example, will be
supported in the next release.
The archiving function is limited to the backflush data of the production backflush.
Backflush data from the PP Backlfush in the R/3 system cannot be archived using
the archiving object PP_CONF.

Archiving Backflush Data

Use
The archiving program records all backflushes indicated as “able to be archived” in an archive
file.
Prerequisites
• The backflushes must be indicated “able to be archived”. In a production backflush, all
backflushes for an order are always indicated “able to be archived” together.
• A valuated individual customer stock segment exists for the corresponding orders of the
finished product, that is, the backflush data is no longer required for the valuation.
• The data lies before a defined date which means the residence time [External] has
expired. The residence time cannot be defined in Customizing for the application, but is
determined in the actual archiving program via a parameter.
• If you use the Business Warehouse System (BW), the data to be archived must already
have been transferred to BW.
Procedure
1. Choose Logistics → Production → Repetitive Manufacturing → Production Backflush →
Archiving Backflush Tables → Archive.
2. Select a variant with F4.
3. Choose Maintain if you want to change the residence time. Select Test run if you only
want to simulate the archiving procedure.
4. If you want to create your own variant, enter a variant name that does not yet exist and
choose Maintain. Determine the criteria for the selection of the data to be archived and
define the technical control. Save your variant.
Make sure that you redetermine the selection parameters of the variant or check
the entries for the next archiving run.
4. Define the start date.
5. Determine the spool parameters.
6. Choose Execute.
Result
One or more archiving files are created.
The archiving program logs the procedure in the form of a list. This list is printed according to
your settings (spool parameter, see Procedure) on completion of the program and/or saved in
the printing spool. To access the processing log, place the cursor on the job newly carried out
in the job overview, choose Spool list, indicate the appropriate spool order and choose
Display. If you have not set the indicator for the creation of a processing log in the variant, the
system creates an abbreviated processing log.

Deleting Backflush Data

Use
You can use the deletion program to delete the data records from the archiving file or the
archived backflushes from the database.
You only have to delete the data manually if, in Customizing under Technical
Settings → Settings for the Deletion Program, the Start automat. indicator is not
set or if the indicator Only delete in test mode is set in the variant settings of the
archiving program.
Prerequisites
You must execute the archiving program.
Procedure
Archiving Backflush Tables → Delete.
2. If you only want to simulate the deletion of the data, choose Test run.
3. Select an archive.
4. Define the start date.
5. Determine the spool parameters.
6. Choose Execute.
Result
The data records are deleted.
The deletion program logs the procedure in the form of a list. This list is printed according to
your settings (spool parameter, see Procedure) on completion of the program and/or saved in
the printing spool. To access the processing log, place the cursor on the job newly carried out
in the job overview, choose Spool list, indicate the appropriate spool order and choose
Display. If you have not set the indicator for creating a processing log in the variant, the
system creates an abbreviated processing log.
Executing Postprocessing for Backflush Data

Use
The postprocessing program deletes entries in a supplementary table that only contains a
small amount of data. The deletion of this data was therefore moved from the deletion
program to the postprocessing program to improve performance. Postprocessing can be
carried out after the archiving run or you can start it independently of the archiving process.
Procedure
Archiving Backflush Tables → Postprocess.
2. Process Start date and Spool parameters.
3. Choose Execute.

Result
The entries in the supplementary table are deleted.
Evaluating Backflush Data

Use
You can use the evaluation program to display the data of the archived backflushes.
Prerequisites
You must execute the archiving program and the deletion program.
Procedure
Archiving Backflush Tables → Evaluate.
The screen entitled, Archive Management: Execute Analysis Program appears.
2. Determine whether the program is to be executed in the background (batch) or online.
Batch Online
a) Process Start date and Spool Choose Execute and select the
parameters. archive files you want to
evaluate.
b) Enter the appropriate values and
save your entries.
You return to the initial screen.
c) If necessary, choose one or
more archiving files via the
archive selection.
Result
The contents of the corresponding archiving files are displayed.
BAPIs for the Production Backflush

Purpose
BAPIs control communication between APO and SAP Automotive for the production
backflush. The BAPI descriptions are particularly interesting for users who do not use an APO
System and only wish to use the processes within the R/3 System.
Reporting point structures and backflushes from the R/3 System are received and saved via
the BAPIs. In addition, saved reporting point structures for an external application can be
located and backflushes can be flagged with a deletion indicator. The external system must
map onto the functions of the APO, especially the requirements planning and order
management functions.
Please also refer to the documentation for accessing BAPIs in the system.

Process Flow
Process flow:
The backflush is always carried out for a reporting point. Even if no reporting points exist for
the production process, at least one reporting point must exist at the end of production to
which the goods receipt and goods issues can be posted. When backflushing in production
without reporting points, the BAPI BAPI_MNFCTCONFRCVR_RECEIVE is accessed once at
the end of the line. All components and the accompanying goods receipt are transferred to
this BAPI for backflushing.
The existing reporting points must be passed on to the R/3 system before the first backflush.
This is done using the BAPI, BAPI_MNFCTCONFRCVR_PVR_RECEIVE. When
backflushing, the reporting point structure and a reporting point must be transferred. The
validity of this data is checked upon receipt of a backflush.
The first time a backflush is carried out for an order, the R/3 system saves the reporting point
structure for this order. All other backflushes for this order must be posted with reference to
this reporting point structure. Changes to the reporting point structure are not taken into
account until backflushing the next order.
Functions of the individual BAPIs:

The following four BAPIs guarantee the success of the production backflush and are
accessed by the system in the given order. The BAPIs are implemented as methods of the
Business Object BUS10507.
• Making a reporting point structure known: BAPI_MNFCTCONFRCVR_PVR_RECEIVE
With this BAPI, specifically via the Method ReceiveRPStructure, the reporting point
structures of the lines which refer to the backflushes are made known to the
Automotive system. The first time a backflush is carried out for an order, the system
saves the current, valid reporting point structure of this order. All other backflushes for
this order can only be posted with reference to the reporting point structure that was
valid for the first backflush – even if the reporting point structure of a line has changed
in the mean time.
• Requesting the reporting point structure: BAPI_MNFCTCONFRCVR_RPV_GET
The reporting point structure assigned to an order can be requested using the method
GetRPStructure.
• Creation of a backflush: BAPI_MNFCTCONFRCVR_RECEIVE
This BAPI is responsible for the actual backflush. The backflush for an order cannot
be created until the reporting point structure for the order has been made known to
the Automotive System. The Method ReceiveStockChange is used for this.
• Setting the deletion indicator for backflushing: BAPI_MNFCTCONFRCVR_DELETE
If no further backflush can be carried out for an order, a deletion indicator must be set
for the backflushes already posted. This is achieved via the Method
ConfirmationDelete. The archiving program cannot select the backflushes until the
deletion indicator has been set. See also: Archiving Backflush Data from the
Production Backflush [Page 459].
Technical Appendix
Purpose
The technical notes are aimed at users who modify the production backflush and want to
assign authorizations. They are also interesting for users with no connection to APO, who

want to program their own interface in R/3 for the production backflush. The names of the
objects are listed and the interaction between the tables explained. For the BAPIs, see also
BAPIs for the Production Backflush [Page 463].
Process Flow
Development class:
All objects for the production backflush are in the development class PPC1. From here, you
can navigate to the appropriate function groups, transactions and other objects. Most of the
newly created objects start with PPC_.
Tables:
As no reporting tools are currently available in R/3 for the production backflush, the following
graphic explains in very simple terms how the tables interact with each other. If necessary,
you can write your own reports. Moreover, in the BW, you can create reports.

PPC_ORD_INF PPC_RP_VERS
(Order-rel ated inf o) (Line v ersions)
Reporting point structure per
One record per oder n 1 line v ersion: f illed by a
Inf o: assembly , BAPI
Check
Line v ersion
Key : ORDERID n n
1 At f irst 1 1
backf
backf lush
n PPC_RP PPC_RP_VER
f or an order
Rep.point S_D AT
PPC_HE AD (Backf lush master Line master
Header records) PPC_SCR AP data data
One header record per (Scrap inf o)
backf lush; Inf o on: Only filled in
scrap cases BAPI_PPC_AP OCOMPLISTS
Order, reporting point, 1 c (scrap reason Material mov ements
data entry, account etc.) Key :
assignment, v arious HEADID
control indicators
Key : HEADID
1
1 1 Read
1 or
1 insert
1
BAPI_PPC_AP OHEADS PPC_MAT (Super BO M)
Backf lushing header records One record per material and
logistics key
Inf o on: mat.no, plant, stor.loc.,
HEADID
GR/GI, aggregation, special stock
etc.
Quantitie Key : MATID
cn 1 1
s
n
PPC_CONF_MAT PPC_MAT_DET (Acc. assignment inf o
(Material mov ements) n 1 One record per MA TID and account,
One row per mov ement if v aries from header record (1:n-
Contains only key and ACCID rel .)
quantitie Inf o on: sales order/project, batch
s
Key : HEADID, ACCID Key : ACCID
PPC_RES_H DR (P ost processing)

Post- - One row per post-processing header
processing Link to RESB
P osting
Key: OBJNR (cost collector)
Authorizations:
A new authorization object is available for the production backflush: C_BCKFLUSH.
It contains the fields WERKS (plant) and ACTVT (activity). The check is carried out per plant.
Three activities exist:
• 24 = Archive: Checks the authorization when triggering the archiving run.

• 31 = Backflushes: Checks the authorization when accessing

BAPI_MNFCTCONFRCVR_RECEIVE. No posting can be carried out without these
authorizations.
• A8 = Process mass data: Checks the authorization for the function Processing the
backflushes (transaction PPCGO).
As no transaction is linked to the BAPI, you can only maintain the authorization object via
SU22. The authorizations are not automatically copied to the activity group/role. The
authorizations must be added to the appropriate activity group/role manually.
Converting Orders in APO

Use
There are several methods available for triggering conversion of planned orders into
production orders, and purchase requisitions into purchase orders in the connected OLTP
system:
• Transfer only for orders with conversion indicator
• Transfer of all PP/DS orders
• No transfer of PP/DS orders
Transfer Only for Orders with Conversion Indicator

Prerequisites
Settings → Maintain Global Parameters and Defaults, you have selected Transfer
Only for Orders with Conversion Indicator for Transmission to OLTP
External Procurement and/or In-House Production.
• You have maintained a planned delivery time in the external procurement relationship.
• You have maintained an opening period for planned orders for each product in the
product master on the PP/DS tab page at location level.
Features
automatically creates a purchase order against this order in the connected OLTP system.
For more information on converting orders in interactive planning, see Convert Individual
Orders in Interactive Planning [Page 470].
If you use mass conversion for orders, then you can either transfer or convert orders from a
specific period.
During mass conversion of orders, only those orders are selected where the opening date is
in the past.


If you select the Convertible orders indicator in the mass conversion function, then the system
creates purchase orders in the OLTP system against all orders where the opening date is in
the past.
If you select the Transferable orders indicator in the mass conversion function, then the
system creates purchase requisitions in the OLTP system against all orders where the
For more information on mass conversion of orders, see Executing Mass Conversion of
Orders [Page 469].
Transfer of All PP/DS Orders

Prerequisites
Settings → Maintain Global Parameters and Defaults, you have selected Transfer of
all PP/DS orders for Transfer to OLTP External Procurement and/or In-House
Production.
Features
All orders from your APO system are always transferred to your OLTP system.
If you have made this setting and there are a large number of orders in your APO
system, this can have a negative impact on performance.
No Transfer of PP/DS Orders

Prerequisites
In Customizing for Production Planning and Detailed Scheduling (PP/DS) under Global
Settings → Maintain Global Parameters and Defaults, you have selected No transfer of
PP/DS orders for Transfer to OLTP External Procurement and/or In-House Production.
Features
No orders are transferred from the APO system to the OLTP system. No orders are converted
to purchase orders or production orders in the latter system.
The setting is useful, for example, if you have not connected an OLTP system to
your APO system.

Executing Mass Conversions of Orders

Use
You can use this function to transfer all planned orders and purchase requisitions where the
opening period is in the past to the OLTP system, or to convert them into production orders
and purchase orders. The opening date is calculated as follows: Delivery date – Planned
delivery date – Opening period.
For a description of how to convert individual orders, see Converting Individual Orders in
Interactive Planning [Page 470].
You have maintained an opening period for planned orders for each product in
the product master on the PP/DS tab page at location level.
Procedure
3. From the SAP Easy Access Menu, choose Production Planning → Manufacturing
Execution → Conversion of Orders/Purchase Requisitions.
The Mass Conversion of Orders in the Active Planning Version screen appears.
4. You can restrict the selection of the orders to be converted using the required selection
criteria.
Selection criteria for mass conversion
Selection Criteria Description

Product Limits the selection to the products you enter.
Location Limits the selection to the locations you enter.
Offset for the opening period Lengthens/Shortens the opening period. Only orders falling within
the opening period are converted and/or transferred.
Select in-house production If you want to convert planned orders into production orders, or to
transfer these to the OLTP system, you must set this indicator.
Production planner You can restrict the selection of planned orders to be converted
and/or transferred that affect a specific planner.
Only fully scheduled orders You must plan all activities for an order. No activities must be
deallocated.
Select external procurement If you want to convert purchase requisitions into purchase orders,
or to transfer these to the OLTP system, you must set this
indicator.
Purchasing group You can restrict the selection of purchase requisitions to be
converted and/or transferred that affect a specific purchasing
group.
Special stock Limits the selection, for example, to one account.
Source Limits the selection to the source locations you enter.
Only firmed orders Only orders whose output is firmed are converted and/or
transferred.

If you do not want to limit the selection, the system processes all orders whose
opening dates are in the past. The opening period is defined for each product in
the product master.
4. Choose .
If you have selected the Display indicator in the Execution options area, the Receipts
screen now appears. The system shows you all the orders that are deemed
convertible and/or transferable according to the selection criteria.
Select the orders that you want to
− convert, and choose Set conversion indicator
− transfer, and choose Transfer orders
If you have set the Immediately indicator in the Execution options area, the system
automatically converts all convertible orders and/or automatically transfers all
transferable orders to the OLTP system.
Result
The system sets a conversion indicator for the convertible purchase requisitions and planned
orders. The orders planned for conversion are transferred to the OLTP system, and are
automatically converted to purchase orders or production orders.
The system transfers the transferable purchase requisitions and planned orders to the
connected OLTP system.
Subcontracting PReqs and purchase requisitions for OLTP scheduling

agreements cannot be automatically converted in the OLTP system.
To convert these purchase orders into purchase orders and/or scheduling
agreement schedule lines, use the Create Purchase Order using Assignment List
Converting Individual Orders In Interactive Planning

Use
You can directly trigger the conversion of planned orders into production orders and purchase
requisitions into purchase orders on the interactive planning screens of the Product View
[Page 308] and the Product Planning Table. The orders you designate for conversion in the
APO System are sent to the connected OLTP System and are automatically converted there.
Procedure
2. Access the Product View [Page 308] or the Product Planning Table from the SAP Easy
Access Menu by choosing Production Planning → Interactive Production Planning →
Product View or Product Planning Table.
The Product View or the Product Planning Table screen appears.
5. Choose the Individual Elements tab in the Product View or the Product: Individual
Elements view in the Product Planning Table.
6. Select the planned orders and/or purchase requisitions to be converted.

For a purchase requisition to be automatically converted into a purchase order, a

procurement alternative must be assigned to the requisition.
7. Choose Set Conversion Indicator.
The system sets the conversion indicator for the selected orders.
6. Choose to save your planning results.

The orders designated for conversion are transferred to the connected OLTP System,
where the conversion is triggered automatically.
If you create an external procurement order and immediately set the conversion
indicator for this order, the OLTP System automatically creates a purchase order
once you have saved the data. No purchase requisition then exists for this order
in the OLTP system.
If you wish to create a purchase order with reference to a requisition, you must
first save the external procurement order and wait until the requisition data has
been passed on from the OLTP system to the APO system. When this has taken
place, you can set the conversion indicator.
Subcontracting requisitions and purchase requisitions relating to OLTP

scheduling agreements cannot be automatically converted in the OLTP system.
To convert these requisitions into purchase orders or scheduling agreement
delivery schedule lines, use the Create Purchase Order via Assignment List
Evaluations
Purpose
Various analyses for analyzing scheduling and scheduling problems are available in
Production Planning.
Log for interactive The system automatically generates a planning log or a scheduling
scheduling [Page 306] or for log for a planning run or planning session (for example, with the
production planning runs product view or detailed scheduling planning board).
[Page 122]
You will find scheduling-relevant information in the scheduling log,
for example, for scheduling problems on the resources, and
quantity and product-related information, such as missing
components, in the planning log.
You call up the log under Planning Run Reporting.
Order and resource Includes various evaluations for planning-relevant information, for
evaluations example, for resource load or work-in-process stocks
You will find more information under order and resource
evaluations [Page 472].

Production list Displays a production list for activities on selected resources or

production lines
The production list contains production-relevant data for the
activities, for example, quantities produced, start and end dates.
Planning file entries Displays planning file entries for selected products
The system automatically generates planning file

entries for planning-relevant changes affecting
products which according to the product master are
automatically scheduled in the production planning
run. Planning-relevant changes refer to changes to the
master data or requirements.
Order and Resource Evaluations

Use
The following evaluations, which you can also call up in the area menu of Reporting and in
the detailed scheduling planning board [Page 362], are available for resources, orders, and
products in Production Planning:
Resource load Displays the resource load per period or per block [External] for
selected single or multi-resources
Work-in-Process stocks Displays the Work-in-Process stocks for operations on selected
resources, that is, the quantity of unprocessed material awaiting
further processing in these operations
For more information, see Evaluations for Work-in-Process Stocks
[Page 473].
Operation list Displays a list of operations for selected resources that are
processed on these resources
Order list Displays a list of orders for selected resources that are processed
on these resources
Production overview Displays a production overview for selected products
In the production overview, the quantities and status of products
are listed; for example, which quantity of a product has been
released or confirmed.
You can call up a list with production-relevant data for activities on selected
resources and lines in the area menu of Reporting under Production list.

Features
• An evaluation refers to a certain evaluation period and a certain planning version
[External] or simulation version [External]:
− When you call up the evaluation function in the detailed scheduling planning board,
the system creates the evaluation for the current display period and simulation
version in the detailed scheduling planning board.
− You must specify a planning version and an evaluation period if you call up an
evaluation in the Reporting area menu.
• Using the customer exit [External] APOCSPS5, you can enhance the evaluations with
user-defined columns and enter values in these columns. The system automatically
enters values when you call up the evaluation. For more information, see the system
documentation for the customer exit.
Activities
You call up the evaluations
Evaluations for Work-in-Process (WIP) Stock

Use
Work-in-process (WIP) stocks are stocks of components or unfinished products that are
waiting at a resource for further processing. Quantities and queue times are important
indicators for assessing the quality of the schedule in relation to costs and the lead times for
orders [External].
The following evaluations resources are available for the WIP in the order and resource
evaluations [Page 472] and in the DS planning board [Page 362]:
Evaluations for WIP stock
WIP list This evaluation shows order-internal WIP stock for the order product for
selected resources. You use this evaluation if the order product is passed on,
on behalf of one operation to another, whereby the total quantity is passed on
or is needed at once (that is, there is an availability date or a requirement
date per operation).
The following is displayed for each operation at the selected resources:
• The quantity of the unfinished main product in the order, which is
provided by the preceding operation in the order and which is waiting for
further processing.
• As WIP queue time: The time between the availability date and the
requirement date. The queue time is negative if the availability date lies
after the requirement date.
For operations with continuous input or output you cannot use this evaluation.
Here you use the Enhanced View of the evaluation WIP list (network).
WIP list This evaluation shows the WIP stock for components for selected

(network) resources that are provided by other orders.

The following is displayed as a default for each operation at the selected
resources:
• As the WIP quantity: The total quantity of a component provided by
operations from other orders and waiting for further processing
• As the WIP queue time: The time between the availability date for the
total quantity and the earliest requirement date for the component
The queue time is negative if the availability date lies after the requirement
date. The system calculates using this evaluation for short queue times,
• If several orders deliver an operation or if an order produces a component
continuously (because the system calculates using the availability date
for the total quantity)
• If an order delivers several operations or if an operation uses the
component continuously (for the system calculates using the earliest
requirements date)
For this evaluation you should therefore choose Enhanced View. Here
• the total quantity is broken down into the supplying orders
• the individual WIP queue time is displayed for each single quantity
• WIP stock for operations with continuous input or output [Page 474] is
evaluated in more detail
The system displays the WIP data in the SAP List Viewer. Note: In the Enhanced
view, you can only use the summation function of the SAP List Viewer effectively
for WIP quantities. The summation function provides the sum of the individual
queue times for the WIP queue times, instead of the more generally required sum
of the queue times weighted by the individual quantities.
Activities
You call up the WIP evaluations
WIP Data for Operations with Continuous Input or

Output
Use
In the Enhanced view of the evaluation WIP list (network) [Page 473] the system also
calculates WIP data for operations that produce or consume material at a constant rate
(operations with continuous output or input).
Features
Below you will find a description of how the system calculates WIP data for the simplest case,
in which the total material quantity that an operation needs and continuously consumes, is
continuously provided by exactly one operation.

The system uses the following data for the calculations:

• The total quantity that is transferred
• Start and end date for the material transfer in the producing operation
development of the transferred material quantity; that is, of the total quantity that the
operation produces as planned up to a specific point in time and has transferred to
the consuming operation. Before the transfer starts, the transferred quantity is zero;
the operation has not yet transferred a material. Between the start and end date, the
transferred quantity increases uniformly to the total quantity. (The system assumes
that the operation transfers the material continuously even in non-working times). At
the end date, the operation has transferred the total quantity. As of this point in time,
the entire quantity transferred is constantly the same as the total quantity.
• Start and end of the material consumption in the consuming operation
development of the consumed material quantity; that is, of the total quantity that the
operation has consumed as planned up to a specific point in time. Before the
consumption starts, the consumed quantity is zero; the operation has not yet
consumed a material. Between the start and end date, the consumed quantity
increases uniformly to the total quantity. (The system assumes that the operation
consumes the material continuously even in non-working times). At the end date, the
operation has consumed the total quantity. As of this point in time, the entire quantity
consumed is constantly the same as the total quantity.
The system determines the WIP curve from the temporal curves of the transferred and
consumed quantity. The WIP curve displays the difference between the entire transferred
quantity and the entire quantity consumed for each point in time. The curve depends on
• the rates with which the quantities are transferred or consumed
• the relative temporal position of the transfer and consumption dates
The curve values can be positive and negative. Positive values indicate that the material was
completed but has not yet been processed further. Negative values indicate missing material.
This case occurs, for example, if the consuming operation needs material earlier or consumes
it faster than it was provided by the producing operation. Negative values are also a sign of
inconsistent planning.
The system shows the following data in the WIP evaluation:
• WIP area
The WIP area is the area under the WIP curve.
• Total quantity that the producing operation transfers to the consuming operation
• WIP time
The WIP time is the quotient from the WIP area and the total quantity.
• Maximum value of the WIP curve
• Minimum value of the WIP curve
Similarly, the system carries out the calculation of the WIP data in the general case, if several
operations, which are continually producing or consuming, are involved in the material flow.
The system breaks down the WIP data here, corresponding to the partial quantities that flow
between a producing and a consuming operation respectively. You differentiate between the
following cases:
• A producing operation delivers several consuming operations.
The system assumes that the operation that is continuously producing firstly delivers
the consuming operation, which has the earliest start date for material consumption.

When this operation has received the total quantity required, the producing operation
delivers the material to the next consuming operation, and so on.
• Several producing operations deliver a consuming operation.
The system assumes that the consuming operation firstly consumes the material of
the operation, which has the earliest start date for material transfer. If this material is
consumed, the consuming operation consumes the material that is provided by the
next producing operation, and so on.
In the WIP evaluation, the WIP data refers in these cases to the partial quantity of the material
that is transferred from a producing operation to a consuming operation. The WIP times are
determined by the partial quantities and by their availability dates or requirement dates.
Transfer of Orders to the OLTP System

Purpose
APO is a planning system and requires an OLTP system to perform execution functions. The
planning results of products planned in APO are transferred to the OLTP system. If necessary
planning is completed in the OLTP System when, for example, not all products of a BOM
structure are planned in APO. You can control which master and transaction data is to be
transferred to APO using an integration model [External] in the core interface [External].
Transaction data is then transferred automatically from APO to the OLTP System and back.
For more information, see Integration of APO and R/3 [External].
Prerequisites
integration model [External] in the core interface [External].
• You have maintained the necessary master data [Page 110] and PP/DS settings [Page
111].
Process Flow
1. The planning situation changes. This could be due to, for example, new requirements
being transferred to PP/DS or manual changes.
2. Automatic or manual planning is performed.
When Changes are Transferred to the OLTP System
If the product is changed/planned: then

Automatically Automatic planning [Page 118] is triggered by the
change in the planning situation. The System
creates receipts to cover any new requirements.
The new orders are transferred automatically to
the OLTP system, every time automatic planning
is triggered.
Manually You create a new receipt for a product manually
or you manually change an order [Page 307].
The orders are not transferred to the OLTP
system until you save the planning results.
Once you have saved the results, the orders are
transferred to the OLTP system automatically.

If you manually change order dates or quantities for a product that is planned
automatically, these changes are not transferred to the OLTP System until you
have saved the changes.
3. The orders created/changed in the APO System arrive in the R/3 System. Corresponding
orders are created and any changes to exisiting orders are updated in the R/3 System.
The corresponding orders created in the R/3 System are given an order number by the
R/3 System.
4. The new order number is transferred back to the APO System. The local APO order
number is replaced by the R/3 order number.
For more information on integration between APO PP/DS and the R/3 System, see OLTP -
PP/DS Scenario [Page 18].
Exception Based Management: PP/DS

Purpose
By practicing exception-based management, you maintain ongoing control of the production
and scheduling side of your business. As a planner or manager, you will not be caught
unawares when problems arise. Instead, you will be informed well ahead of time, allowing you
to make necessary adjustments and take appropriate action. The Alert Monitor allows you to
determine which types of exceptions you want to be notified of. It also allows you to prioritize
alerts, thus preventing an information overload.
In the logistical process, a production order or scheduling agreement raises the following
types of questions:
• When and where is a product needed?
• What quantities must be produced?
• Which resources are required?
• What components are necessary?
The Alert Monitor comes equipped with a number of PP/DS alert types which correspond to
the exception situations that could arise in production and scheduling. A complete list is
available in the section on profile maintenance, see link below.
Prerequisites
• Maintain the PP/DS Alert Monitor profile.
• Set Alert Monitor profile indicator in the SCC user settings [External] to view PP/DS alerts
in the control panel [External] of the Supply Chain Cockpit.
Process Flow
If a PP/DS alert is generated, three activities must take place:
1. The situation causing the alert must be analyzed.
2. The responsible person must be informed.
3. The plan may have to be readjusted.
The following diagram depicts this process:

Exception Based Management :

Production Planning and
Detailed Scheduling (PP/DS) Set up PP/DS
alert profile
Run PP/DS
planning
Adjust
plan View alerts
interactively
Notify Analyze
responsible alert
planner situation
For more detailed information, see also:
The PP/DS Alert Profile [External]

The Alert Monitor Window [External]
Sending Messages from the Alert Monitor [External]

APO Production Planning &amp; Detailed Scheduling

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

APO Production Planning &amp; Detailed Scheduling

Uploaded by

Copyright:

Available Formats

Production Planning and

Detailed Scheduling (PP/DS)

No part of this brochure may be reproduced or transmitted in any form or for

Some software products marketed by SAP AG and its distributors contain

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of

SAP, SAP Logo, mySAP.com, mySAP.com Marketplace, mySAP.com

Production Planning and Detailed Scheduling (PP/DS) 30A 2

Production Planning and Detailed Scheduling (PP/DS) 30A 3

Production Planning and Detailed Scheduling (PP/DS) .......................................................... 15

Production Planning and Detailed Scheduling (PP/DS) 30A 4

Splitting Operations ................................................................................................... 70

Production Planning and Detailed Scheduling (PP/DS) 30A 5

Scheduling with Time Buffers........................................................................... 102

Production Planning and Detailed Scheduling (PP/DS) 30A 6

Genetic Algorithm ................................................................................................ 148

Production Planning and Detailed Scheduling (PP/DS) 30A 7

Update the Matrix in the Product View .................................................................... 194

Production Planning and Detailed Scheduling (PP/DS) 30A 8

Constraints for the Optimization.................................................................................. 234

Production Planning and Detailed Scheduling (PP/DS) 30A 9

Subcontracting without a Source Location.................................................................. 296

Production Planning and Detailed Scheduling (PP/DS) 30A 10

Product View: Quantity Graphic .............................................................................. 343

Production Planning and Detailed Scheduling (PP/DS) 30A 11

Highlighting objects.............................................................................................. 379

Production Planning and Detailed Scheduling (PP/DS) 30A 12

Loading Alternative Resources............................................................................ 410

Production Planning and Detailed Scheduling (PP/DS) 30A 13

Define and Set Default Values for Profiles .............................................................. 450

Production Planning and Detailed Scheduling (PP/DS) 30A 14

Production Planning and Detailed Scheduling (PP/DS)

Integration within APO and with an OLTP System

Integration with Other APO Components and an OLTP System

Production Planning and Detailed Scheduling (PP/DS) 30A 15

To Procedure Other Information

Production Planning and Detailed Scheduling (PP/DS) 30A 16

PP/DS Business and Integration Scenarios

Production Planning and Detailed Scheduling (PP/DS) 30A 17

OLTP - PP/DS Scenario

Which Products Should You Plan in APO?

Type of Planning Recommended Possible in Not Not

Production Planning and Detailed Scheduling (PP/DS) 30A 18

Production Planning and Detailed Scheduling (PP/DS) 30A 19

In the R/3 material master, create a production version by choosing Production

APO Core Interface in R/3

Customizing for APO

Global Parameters and Defaults for APO PP/DS

APO Master Data

Production Planning and Detailed Scheduling (PP/DS) 30A 20

• You have assigned the production process models to the model.

Settings in APO Product Master

You also can explode the BOM and routing in

Master Data Transferred from R/3 to APO

R/3 Master Data Transferred Master Data in APO

Production Planning and Detailed Scheduling (PP/DS) 30A 21

Material master records Product master records

Transaction Data Transferred from R/3 to APO

R/3 Transaction Data Transferred Transaction Data in APO

Production Planning and Detailed Scheduling (PP/DS) 30A 22

• Interactive planning in APO

Process Flow of an Order Produced In-House in APO and R/3

Automatic Planning in APO

Production Planning and Detailed Scheduling (PP/DS) 30A 23

Process for Automatic Planning Immediately

APO Production Planning & Detailed Scheduling

APO Production Planning & Detailed Scheduling