SCM270 Flexible Planning

SCM270 Flexible Planning
SCM270
Flexible Planning
THE BEST-RUN BUSINESSES RUN SAP
? SAP AG ©2003
SAP AG 2004
? SAP R/3 Enterprise, Extension Set 1.10

? 2004/Q1
? Material number: 50067615
© SAP AG SCM270 Preface-1

Copyright
Copyright 2003 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in
any form or for any purpose without the express permission of
SAP AG. The information contained herein may be changed
without prior notice.
All rights reserved.
? SAP AG 2003
Trademarks:
? Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
? Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered
trademarks of Microsoft Corporation.
? IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®,
AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,
WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM
Corporation in USA and/or other countries.
? ORACLE® is a registered trademark of ORACLE Corporation.
? UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
? Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®,
MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
? HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web
Consortium, Massachusetts Institute of Technology.
? JAVA® is a registered trademark of Sun Microsystems, Inc.
? JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology
invented and implemented by Netscape.
? MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.
? SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein
as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in
several other countries all over the world. All other product and service names mentioned are the
trademarks of their respective companies.

Information Systems
Level 2 Level 3
LO935 2 days
LO020 5 days
Flexible Planning
Processes in
Procurement
LO555 2 days
Technical Aspects in
LO150 5 days LO930 2 days LIS with Special Focus
Logistics Information on PURCHIS/INVCO
Processes in Sales
and Distribution System (LIS)
Reporting LO630 2 days LO940 2 days
LIS with Special Focus Advanced LIS
LO050 5 days Configuration
on SIS
Manufacturing
Planning & Execution LO275 2 days
for Discrete & Repetitive
LIS with Special Focus
on PPIS
AC615 2 days AC620 2 days

Executive Information Executive Information
System (EIS) 1 - System (EIS) 2 -
Reporting Setting up the System
CA705 2 days CA710 3 days
Basics of the Report Advanced Functions
Painter/Report Writer of the Report Writer
? SAP AG 1999

Prerequisites
? Essential:
Knowledge of content of LO930 - Logistics Information
System (LIS) Reporting
? Recommended:
LO050 - Manufacturing Planning & Execution for Discrete &
Repetitive
? SAP AG 2002

Target group
? Project team members responsible for planning in

the Logistics Information System
? SAP AG 1999
Notes to the user

- The training materials are not teach-yourself programs. They complement the course
instructor's explanations. On the sheets, there is space for you to write down additional
information.

Course Overview
Contents:
? Course Goals
? Course Objectives
? Course Content
? Course Overview Diagram
? Main Business Scenario
? SAP AG 1999
© SAP AG SCM270 1-1

Course Goals
This course will enable you to:
? Plan based on information structures

? Use the planning tools in the LIS system
? Summarize the uses of the planning methods and
differences between them
? Maintain master data for various planning methods
? SAP AG 1999

Course Objectives
On completing this course, you will be able to:
? Outline the differences between Standard SOP and

Flexible Planning
? Create sales and production plans
? Use the forecast tool
? Create planning types, macros and events
? Perform resource planning and rough-cut capacity
analysis
? Use mass processing
? Transfer planning results to Demand Management
? SAP AG 1999

Course Contents
Preface
Unit 1 Introduction Unit 7 Events
Unit 2 Planning Methods Unit 8 Production Planning

Unit 3 Master Data Unit 9 Mass Processing
Unit 4 Planning Types and Macros Unit 10 Allocations
Unit 5 General Planning Functions Unit 11 Conclusion

Unit 6 Statistical Forecast
Appendices
? SAP AG 1999

Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Info
Stat. Forecast Structure
May
Allocations
Events
Job
Mass Processing
Production Planning
? SAP AG 1999

Business Scenario
? You are a member of your company‘s planning

implementation team. Define your info structure,
that means your planning levels (characteristics)
and key figures you want to plan.
? SAP AG 1999

Logistics Planning Systems
Sales organization
Division SOP
SOP
Sales plans
Sold-to party
Material Production
. plans
..
Plant
SKUs/ Demand
Statement of Demand
configurable materials Management
Management
demand
...
?Order and rate proposals

MPS/MRP
MPS/MRP
?BOM explosion
?Scheduling at work
centers Quantities. and dates
..
Production controlled Repetitive

Repetitive Production order SFC
SFC
by run schedule Manufacturing
Manufacturing control
headers
? SAP AG 1999
? Sales & Operations Planning (SOP) is the planning tool of the Logistics Information System (LIS).
? Sales & Operations Planning (SOP) is a flexible forecasting and planning tool with which sales,
production, and other supply chain and logistics targets can be set. The basis for this is provided by
historical, existing, and/or estimated future data. Planning with SOP is generally carried out on a
medium to long term basis. Resource planning can also be carried out to determine the amounts of the
work center capacities and other resources required to meet these targets. SOP supports both the high-
level planning of complex planning hierarchies and the detailed planning of finished products.
Therefore, either a top-down or a bottom-up approach to planning is possible.
? The architecture of the logistics planning systems is based on the MRP II concept.

Business Applications of SOP
? Sales Planning
? Production Planning
? Purchasing
? Retail
? SAP
SAP AG 1999
? In SOP, you can plan future sales volumes on the basis of historical data as well as market intelligence
and anticipated trends and changes at your company. Aggregate sales planning is possible. Sales plans
can be kept consistent at all levels of your organization.
? Sales planning provides the input for production planning. You typically carry out production planning
at product group, finished product, or SKU level.
? With SOP, you can manage the allocation of scarce products to different customers or customer groups.
? Complex products manufactured in a large number of variants can also be planned.
? Possible uses of SOP in purchasing are the planning of quotas for multiple sources of supply or the
tracking of purchasing budgets.
? In retail, you can use the SOP system to plan purchasing budgets and monitor open-to-buy.

Info Structure Definition
Region
Characteristics Sales organization
Material
Plant
etc.
Key figures Incoming orders

398
Invoiced sales
157
etc.
Day
Period unit Week
X Month
Fiscal year variant
Flexible time buckets
A00
A00 Active
Active
000
000 Actual
Actualdata
data
Versions 001 Forecast
001 Forecastbased
basedon
ontrend
trendmodel
model
002
002 Sales incl. market intelligence
Sales incl. market intelligence
etc.
etc.
? SAP AG 1999
? Sales & Operations Planning uses the same data infrastructure as the logistics information systems (e.g.
the Sales Information System). In other words, planning data as well as actual data is stored in
information structures.
? There are three different types of information in an information structure:
- Characteristics are criteria by which data reduction is carried out: e.g. sales organization,
distribution channel, customer, material, and plant.
- Periods are time units which give the information structures a time reference. Planning data is
displayed and stored per storage periodicity. This is not necessarily the same as the update period
of the information structure.
- Key figures are values of particular business interest: e.g. incoming sales and production quantities.
Historical key figure values give a measure of business performance.
? In addition, SOP allows you to maintain alternative planning scenarios in the same information structure.
You do this using planning versions . Version A00 is the active planning version. Use it to maintain
your definitive plan. Inactive versions are numerical and consist of three digits. Use them to maintain
test plans.
Remember that version 000 contains actual data. Do not plan version 000.

Flexible Planning: Master Data
Region
Sales organization
Info structure Characteristics Sales office
Material
EUROPE North America

USA
Central North South
Paris New York Dallas
(Product groupings or materials)
? SAP AG 1999
? The objects you plan in SOP depend on the characteristics in the info structure, and on the sequence of
the characteristics in the info structure.
? By defining the values of the planned characteristics, you create the master data for flexible planning.
? Some of you may know the above structure as the ”sales forecast hierarchy” (SFH).

Flexible Planning vs. Standard SOP
Flexible Planning Standard SOP

Multiple options for
Largely preconfigured
customized configuration
Planning hierarchies Product groups
Consistent, level-by-level,
Level-by-level planning
or delta planning
Content and layout of

the planning table is Standard planning table
user-defined
? SAP AG 1999
? Sales & Operations Planning is made up of two elements: flexible planning and standard SOP.
The above table shows you the differences between them.
? To access flexible planning, select Logistics Logistics Controlling Flexible planning.
? To access standard SOP, select Logistics Production SOP.
? You can copy the planning table of standard SOP and then modify it to suit your company's needs.

Use of Copy Management in Planning
Update
Rules
Copy data
from one
S001 info structure
to another
S730
Automatic
S140 Periodic
Flexible
Info structures
? SAP AG 1999
? Copy Management is a tool for managing data in information structures.

? In Sales Operations Planning, you can use it to copy actual data from a standard information structure to
the information structure you want to use for planning. You can therefore carry out comparisons of
planned and actual data.
? Using Copy Management to populate your planned information structures with actual data has
performance advantages. Operative system load is minimized due to the decrease in the number of info
structures that are updated. (You can also supply planned information structures with actual data through
LIS updating.)
? Another possible use of Copy Management would be to copy data you have planned in one information
structure to information structure S140, where you then plan product allocations.
? You access Copy Management in Customizing for the Logistics Data Warehouse.

Standard Analyses: Reporting Techniques
Analysis of S730
Sales Incoming Invoiced
organization orders sales
Additional Drill down
to sales US 100,000 90,000
Information offices
Material master
Customer master
Documents Sales organization: US
Incoming Invoiced
Sales office orders sales
Drill
down to US North 60,000 50,000
customers US South 40,000 40,000
Sales organization: US
Sales office: US North
Incoming Invoiced
Customer orders sales
Jones, Inc. 25,000 20,000
Smith, Inc. 35,000 30,000
.
.
.
? SAP AG 1999
? You can run a standard analysis for any planning version based on consistent planning. Choose
Environment Reporting.
? You can store the standard analysis as a selection version. A selection version is not the same as a
planning version.

Standard Analyses: Analytical Techniques
Planned/Actual ABC Analysis

Comparisons Sales orders
Previous/Current Year Comparison : Invoiced
Sales
Customer Planned Actual Difference %
Customer 1 $30,000 $40,000 $10,000 + A B C

33%
Customer 2 $66,000 $70,000 $ 4,000 + Customers
6%
Customer 3
Customer Sales Orders
Orders No.
orders
orders
Dual Classification Baxter 5000

5000 3000
3000
Taylor 9000 15000
100
100
3000
Crowth 6000
Crowth 6000 9500
9500 750
750
Order
No.
value
orders
Cumulative Curve Classification

Materials (%)
Invoiced sales
12/95 1/96 2/96 3/96 4/96 5/96 Incoming orders
? SAP AG 1999
? A wide range of functions can be used to examine the underlying key figures and characteristic values of
an analysis from a business perspective. All the functions for statistical analyses are graphically
supported.

Introduction: Summary
? SOP is the planning tool of the Logistics

Information System.
? Sales & Operations Planning (SOP) can be used to
plan sales, production, and other supply chain and
logistics activities.
? The Logistics Information System and Sales &
Operations Planning have the same data
infrastructure.
? Sales & Operations Planning is made up of two
elements: Flexible planning and standard SOP.
? SAP AG 1999

Planning Methods
Contents:
? Uses of the planning methods
? Consistent planning
? Level-by-level planning
? SAP AG 1999

Planning Methods: Unit Objectives
On completing this unit, you will be able to:
? Explain the differences between the planning

methods
? Outline the features and benefits of each
planning method
? Maintain Customizing for Flexible Planning
? Summarize performance enhancements
? SAP AG 1999

Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Info
Allocations
May
Events
Job
Mass Processing
Production Planning
? SAP AG 1999

Planning Methods: Business Scenario
? You are a member of your company‘s planning

implementation team. The info structure for the new
SOP planning initiative is already created. Now you
must decide which planning method will meet your
company’s requirements best.
? SAP AG 1999

Planning Methods
Level-by-level Top-down
Consistent Bottom-up
& top-down
? SAP AG 1999
? SOP supports both top-down and bottom-up planning.

? These two approaches are supported in different ways by the different planning methods. It is important
to consider your choice of planning method carefully.
? You cannot define more than one planning method for any information structure. However, you can
always create a new information structure with another planning method and copy over the original data
using Copy Management.

Create Consistent Planning
Material AM001 is selected from planning hierarchy
You enter an order quantity

of 1000 pc. for material AM001:
Automatic disaggregation
Region Material Plant Planned qty Proportion
New Jersey AM001 0001 600 60 %

New Jersey AM002 0001 -
California AM001 1001 400 40%

California AM002 1001 -
California AM003 1001 -
? SAP AG 1999
? Consistent planning has two main advantages:

- Ease of use: you plan your data at one level and can rely on data consistency at all other levels.
- You can create planning data from any perspective you want.
? The value of the total in relation to the details is determined by the proportional factors.
Equally, the value of one detail in relation to another detail is determined by the proportional
factors. For more information on the proportional factors, see Unit Master Data.
? In the above example, disaggregation is based on the proportional factors.

Change Consistent Planning
You change incoming orders from 1000 to 2000:
Region Material Plant Order quantity
New Jersey AM001 0001 600

1000 New Jersey AM004 0001 50
California AM001 1001 400

Region Material Plant Order quantity

2000 New Jersey AM004 0001 50

? SAP AG 1999
? Planning data can be accessed from any level. You determine the combination, or set, of characteristic
values that you want to plan by the values you enter in the initial dialog box when you call the planning
screen; in consistent planning, you can specify any, all, or no characteristic values.
? Data is aggregated dynamically when you call the planning table.
? In the above example, material AM001 is selected for planning. The order quantities of this material are
being planned in all regions and plants. The planner changes the total order quantity from 400 to 800
units. Disaggregation is carried out automatically and is based on previously planned data.

Consistent Planning Views
Bulbs
? SAP AG 1999
? With the consistent planning method, you have a consistent view on your planning data at all times -
whatever level you decide to plan at. In technical terms, the sum of the key figures at the detailed level
gives the key figure at the total level.
? The above example shows two possible views: the central planning of all lightbulbs in the US and the
decentralized planning of standard-sized lightbulbs in New Jersey
? Planning levels are interdependent: changes you make at one planning level have an immediate effect on
all the other planning levels. The system carries out aggregation and disaggregation automatically at
runtime.
? Planning is based on a self-defined information structure.
? Your view on the planning table is non-hierarchical.

Save Consistent Planning
Characteristcs Key figure
Sales organization 75 pc
Distribution channel 30 pc 35 pc
Material 10 pc 20 pc 5 pc 30 pc 10 pc 20 pc 5 pc 30 pc
Order quantity visible Order quantity stored
? SAP AG 1999
? In consistent planning data is stored at detailed level. If you enter the planning table at aggregate level
the key figure values are aggregated.
? This procedure has two advantages:
- You plan your data at one level and can rely on data consistency at all other levels.
- You can create planning data from any perspective you want.

Level-By-Level Planning
Master data
Original plan Changed plan

Incoming orders quantity
quantity Incoming orders quantity
Foreground Saved Foreground Saved
Sales organization 50 40
50 50 40
50
Distribution channel 30 20 100

30 20
0 75 40 75 40
Material 20 10 15 5 20
10010 15
100 5 20 10 15 5 20 10 15 5
Planned incoming order quantities are changed from 30 pc and

20 pc to 75 pc and 40 pc at distribution channel level
? SAP AG 1999
? In level-by-level planning, the planning hierarchy levels are independent of each other. Data is stored
separately at each planned level.
? You have a hierarchical view of the data in the planning table.
? No automatic aggregation or disaggregation is carried out. Plans at different levels are not necessarily
consistent.
? In level-by-level planning, changes you make at one level are not automatically fed through to other
levels.
? It is possible to impose data consistency across several planning levels. To disaggregate data, you must
use the function Edit -> Disaggregate line in the planning table. Disaggregation is then based on the
constant proportional factors from the planning hierarchy. To aggregate data, you must define an
aggregation macro in the planning type.
? The advantage of level-by-level planning is that you get a chance to check your data before passing it on
to other levels.

Consistent vs. Level-By-Level
Consistent Planning Level-By-Level Planning

Planned values saved at detailed level only. Planned values can be saved at all levels.
Entire planning hierarchy can be planned in At least one characteristic value must be specified.
one transaction (no characteristic values Each level must be planned and disaggregated
selection). individually
Planning table can be called with gaps in list Planning table must be called without gaps in list of
of selected characteristic values. selected characteristic values.
Planning values are visible: Planning values are visible:

(i) for the characteristic values (i) for the characteristic values
combination you enter combination you enter
(ii) at the detailed level (ii) at the level below that
(iii) at all levels in between
Identical key figures planned at total and Key figures at owner and member levels can be different.
detailed level.
Key figures are defined in the planning type Key figures must be defined at both owner and member
once only. levels in the planning type.
Macros can be calculated at any level. Macros can be calculated at either owner or member
level, depending on how you have defined them.
? SAP AG 1999
? Standard SOP always uses the level-by-level planning method.

? Standard SOP is based on information structure S076.

Comparison of the Different Planning Methods
Function Consistent Level-By-Level

Automatic aggregation Yes No
Automatic disaggregation Yes No
based on factors saved in
database
Automatic time-dependent Yes No
disaggregation based on
previous planning data
Create planning hierarchy Yes Yes
Planning types/macros Yes Yes
Set opening stock Yes Yes
automatically in background
Forecast Yes Yes
Events Yes Yes
Resource leveling Yes Yes
Background processing Yes Yes
Fix key figure values in the Yes No
planning table
Long texts for versions and Yes Yes
periods in the planning table
Standard analysis for info structure Yes No
Transfer to Demand Management Yes Yes
? SAP AG 1999

Customizing for Flexible Planning
Field catalogs:
key figures Define planning type
Define
information Define screen Define
structure layout macros
Field catalogs:
characteristics
Planning Planning Key figure

method units parameters
? SAP AG 1999
? Before working with flexible planning, you must first make a number of settings in Customizing: for
example, you must define the planning method of each information structure.
? You can use only one planning method to plan an information structure.
? To plan an information structure with a second planning method, create a second information structure
based on the first one and then copy over the actual data using Copy Management. Then define the
planning method of this new information structure.
? You must define the planning units of each information structure. These are:
- currency unit
- period unit (storage periodicity)
- unit of measure
? It may happen in either consistent planning or level-by-level planning that the base unit of a material is
different than the base unit of the information structure. In this case, you maintain the base unit of the
information structure as an alternative unit in the material master record, together with a conversion
factor.

Performance Enhancements
? No user exits
? No zero column usage
? No event usage
? Do not save to forecast DB
? Planning object check off
? Key-figure-restricted DB update off
? ALE permitted
? Document key figure
? SAP AG 1999
? You access the settings listed above in the Customizing activity ”Set parameters of info structures and
key figures”. They are all designed to improve the performance of your information structures. Two of
them are explained in the following notes. For a description of the others read the F1 help.
? Planning object check off:
If you set this indicator, you improve performance. However, the system does not perform the following
checks: Are the selected characteristic value combinations in the planning hierarchy? They might be in
actual data of the information structure, but not in the planning hierarchy.
Has the planning hierarchy been revised? In the master data menu of Flexible Planning, you have an
option for revising the planning hierarchy. This option allows you to exclude one or more
characteristic value combinations (planning objects) from the planning process. When you call the
planning table, the system checks to see which characteristic value combinations are to be planned for
this information structure.
? Key figure restricted DB update off:
If you set this indicator, you improve performance. However, the system cannot save two planning types
of an information structure simultaneously because ALL the key figures in the information structure are
read when a planning type based on the information structure is saved.
If you do not set this indicator, the system automatically locks and saves only those key figures that are
contained in one planning type. This means that two or more planning types of an information structure
can be saved at the same time.

Planning Methods: Unit Summary
You are now able to:

? Explain the differences between the planning
methods
? Outline the features and benefits of each
planning method
? Maintain Customizing for Flexible Planning
? Summarize performance enhancements
? SAP AG 1999

Data Used in the Exercises
Data Data in Training System Data in IDES System

Information S630 to S650 S630 to S650
Structure S140 S140
Sold-to Customers 1001, 1175 1001, 1175
1002,1012,1033,1174, 1002,1012,1033,1174,
1300, 1670, 1671, 1900, 1300, 1670, 1671, 1900,
1901, 2004, 2140, 2200, 1901, 2004, 2140, 2200,
2300, 2500, 14000, 99999 2300, 2500, 14000, 99999
Sales Organization 1000 1000
Distribution 12 12
Channel
Division 00 when ordering 00 when ordering
04 when planning 04 when planning
Materials L-40C, L-40F, L-40R, L-40C, L-40F, L-40R,
L-40Y L-40Y
L-60C, L-60F, L-60R, L-60C, L-60F, L-60R,
L-60Y L-60Y
L-80C, L-80F, L-80R, L-80C, L-80F, L-80R,
L-80Y L-80Y
Plant 1200 1200
Storage Location 0001 0001

Exercises
Unit: Planning Methods

Topic: Planning Methods
? Explain the differences between the three planning methods.
Your sales/forecasting department would like to see changes made to

your plan at all levels of the planning structure, at the time the plan is
changed. Therefore, the consistent planning method best suits the
planning requirements of your organization.
1-1 Using the Implementation Guide (IMG), verify the planning parameters of your info
structure S630 + ##. The parameters should have AT LEAST the following:
Field Name Input Data

Planning Method
Exchange rate type
Statistics currency
Base unit of measure
Planning periods
Capacity figure
1-1-1 What is the menu path in the IMG for changing the planning parameters for an
info structure?
The information message ”The table is client- independent.”, is

advising you that each change you make will have an effect on all
other clients in the system. Press Enter to continue.

Solutions
Unit: Planning Methods

Topic: Planning Methods
1-1 Using the Implementation Guide (IMG), verify the planning parameters of your info
structure S630 + ##. The parameters should have AT LEAST the following:
Field Name Input Data

Planning Method K (Consistent)
Exchange rate type M
Statistics currency UNI
Base unit of measure CAR (carton)
Planning periods M
Capacity figure
1-1-1 What is the menu path in the IMG for changing the planning parameters for an
info structure?
The information message ”The table is client- independent..”, is
advising you that each change you make will have an effect on all
other clients in the system. Press Enter to continue.
Tools ? ASAP ? Customizing ? Edit Project ? SAP Reference IMG

Logistics - General ? Logistics Information System (LIS) ? Planning ?
Master data ? Set parameters for info structures and key figures
Or
Production ? Sales and Operations Planning (SOP) ? Master data ? Set
parameters for info structures and key figures
Scroll down to your info structure S6## and then double-click on the table

Master Data
Contents:
? Planning hierarchy
? Product group
? Proportional factors
? Version management
? SAP AG 1999

Master Data: Unit Objectives
? Name the differences between master data for

Flexible Planning and Standard SOP
? Explain how to create master data
? Outline the role of the proportional factors
? SAP AG 1999

Master Data: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Info
Allocations
May
Events
Job
Mass Processing
Production Planning
? SAP AG 1999

Master Data: Business Scenario
? Your company builds its forecast based on the

history of invoiced quantity for the same quarter of
the previous year. You expect your product mix to
be consistent. Therefore, you can build your
planning hierarchy and calculate your proportional
factors based on this history.
? SAP AG 1999

Characteristic Values to be Planned
Characteristics
Characteristics Values
Sales USA
organization Europe
Paris Dallas Boston

Sales office
Jones, Inc. Smith, Inc.

Customer
L - 40F L - 100F
Material L - 60F L - 100C
L - 60C
? SAP AG 1999
? You create the master data for Flexible Planning by specifying the values of the characteristics you want
to plan. You do this in a planning hierarchy.
? For consistent planning and level-by-level planning, you need to create a planning hierarchy before you
can plan.
? A planning hierarchy is based on an information structure. You can create only one planning hierarchy
per information structure.

Planning Hierarchies
Region
Sales organization
Info structure Characteristics Sales office
Material
EUROPE North
USA
America
Central North South
Paris New York Dallas
(Product groupings or materials)
? SAP AG 1999
? The objects you plan in SOP depend on the characteristics in the info structure, and their sequence.
? By defining the values of the planned characteristics, you create the master data for Flexible Planning.
You do this in a planning hierarchy.
? You can only create one planning hierarchy per information structure.
? In a planning hierarchy, the characteristic values represent the organizational levels at which you want to
plan.
? To create a planning hierarchy manually, select Master data -> Planning hierarchy -> Create from the
Flexible Planning menu.
? You have already defined the default units of a planning hierarchy in the Customizing step Set
parameters of info structures and key figures. These are period unit, base unit of measure, and currency.

Automatic Creation of a Planning Hierarchy
Characteristic value combinations

found in version 000
1997 1998
Eur Central Paris M1 x x
Eur Central Paris M2 x
USA North NY M6 x x
USA North NY M7 x x
USA North NY M8 x x
USA North NY M9 x x
USA North NY M10 x x Data is filtered
USA South Dal . M11 x using method
USA South Dal . M12 x
USA South Dal . M14 x x
USA South Dal . M15 x x
? SAP AG 1999
? You can create a planning hierarchy automatically on the basis of actual data (version 000) or existing
planned data (versions A00-999).
? To create a planning hierarchy automatically on the basis of actual data, select Master data -> Generate
master data.
? It is often not necessary, or even desirable, to plan all products that are sold to all customers, including
materials that are hardly ever sold. SAP offers you two ways to filter out characteristic value
combinations (i.e. data records) for planning:
- specify a time frame
- define your own method in Customizing
? A method is a program or programs written by your company to perform a clearly defined, highly
specific task when certain conditions are fulfilled. For example, a method allows you to perform
complex transformations on statistical data.
? One possible method would be to select materials or customers by their ABC indicator. For example,
you might want to plan A materials individually, and B and C materials in collective planning objects.
? You can simulate the results of this automatic creation function. This lets you see how many
characteristic value combinations would be found in the specified time frame and therefore helps you
decide how best to create the planning hierarchy.

Proportional Factors for Consistent Planning
Info structure S624
40% 60%
Europe USA
100% 50% 50%
Paris Dallas Boston
100% 100% 100%
Smith, Inc. Jones, Inc. Baker, Inc.
30% 20% 50% 70% 30% 20% 80%
L-40F L-60F L-100F L-40F L-60F L-60F L-100F
12%
12% 8% 20% 21%
21% 9% 6% 24%
? SAP AG 1999
? In consistent planning, disaggregation is based on the proportional factors between the total level and the
detailed level.
? You can store constant proportional factors in the planning hierarchy. These proportional factors are not
specific to any one key figure, characteristic value, or period.
? There are two ways to calculate constant proportional factors for consistent planning:
- Using actual data
- Using the proportions already maintained between adjacent levels in the planning hierarchy
? To calculate the proportional factors for consistent planning on the basis of actual data, select Master
data -> Calculate proportions -> Using actual data from the flexible planning menu.
? To calculate the proportional factors for consistent planning on the basis of the level-to-level proportions
in the planning hierarchy, select Master data -> Calculate proportions -> Using planning hierarchy
from the flexible planning menu.
? You can override the constant proportional factors in the planning table at any time. If you do this,
however, subsequent disaggregation is based on the new proportional factors which the system derives
from the detailed planning data, and not on the constant proportional factors. To re-apply the constant
proportional factors to a specific key figure in the planning table, you must select Edit -> Disaggregate
line.

Proportional Factors for Level-By-Level Planning
Info structure S625
40% 60%
Europe USA
100% 50% 50%
Paris Dallas Boston
100% 100% 100%
Smith, Inc. Jones, Inc. Baker, Inc.
30% 20% 50% 70% 30% 20% 80%
L-40F L-60F L-100F L-40F L-60F L-60F L-100F
? SAP AG 1999
? Using proportional factors, you describe the dependencie s of the individual nodes in a planning
hierarchy or a product group hierarchy more closely. These factors allow you to disaggregate planning
data through the planning hierarchy. Whether or not this happens automatically depends on the planning
method (see Unit Planning Methods).
? In level-by-level planning, disaggregation is based on the proportional factors between adjacent planning
levels. This applies both to Standard SOP and to information structures in Flexible Planning for which
level-by-level planning has been defined.
? You can create these proportional factors manually or automatically.
? In most cases, you base this calculation on the actual data in version 000. However, you can also use any
planning version.
? To create the proportional factors for le vel-by-level planning automatically, you have two choices:
- Either create them for a single level in the planning hierarchy or product group with Edit Calculate
proportions
- Or create them for multiple levels of the planning hierarchy or product group with Master data
Calculate proportions Using actual data or Product group Calculate proportions

Product Group Hierarchy
Lightbulbs
Lightbulbs
Plant 9999
9999
Line "frosted" Line "clear"

Plant 0001 Plant 0002
40 watt 60 watt 40 watt 60 watt 100 watt

Plant 0001 Plant 0001 Plant 0002 Plant 0002 Plant 0002
? SAP AG 1999
? You create the master data for standard SOP by maintaining one or more product groups .
? The members of a product group can be either further product groups or materials.
? In a product group, you can group together products according to any criteria (distribution, production
method, and so on).
? For each product group, the system creates a material master record of material type PROD.
? Enter both product groups and materials with a plant reference.
? For each product group member, enter a description, a unit of measure, a units of measure conversion
factor (if the unit of the member is different than the owner unit), and an aggregation factor.
? Cross-plant planning is possible.
? Planning can be carried out at material or product group level
? Use level-by-level planning with product groups.
? Standard SOP always uses the level-by-level planning method.
? Standard SOP is based on information structure S076.

Version Management
Info
Structure
A00 001 002 000

Active Version Simulation 1 Simulation 2 Actual Data
Copy
Demand Mgt. Updating
? SAP AG 1999

Master Data: Summary

? Name the differences between master data for
Flexible Planning and Standard SOP
? Explain how to create master data
? Outline the role of the proportional factors
? SAP AG 1999

Exercises
Unit: Master Data

Topic: Planning Hierarchy
? Explain the two ways of creating master data for flexible planning.
? Outline the role of the proportional factors.
Your company builds its forecast based on the history of invoiced

quantity for the same quarter of the previous year. You expect your
product mix to be consistent. Therefore, you can build your planning
hierarchy and calculate your proportional factors based on this history.
1-1 The following is the forecast input sheet your organization has been using to load
forecasts into your legacy system. It shows actual data collected for the prior year,
allowing space for your sales force to enter the sales forecast in currency values. Your
info structure S630 + ## already supports this forma t. Create a planning hierarchy for
your info structure that supports the data on the following sheet:
Sales Organization 1000 Germany Frankfurt Division 04 – Lighting,

Customer 1000 Becker Berlin Plant 1200
Material L-80F 80 Watt Frosted Light bulbs

Month+1 Month+2 Month+3 Month+4 Month+5
Last Year’s Invoiced Sales 10000 11000 12000 13000 14000
Last Year’s Invoiced Qty 1000 1100 1200 1300 1400
Sales Forecast Qty
Material L-40C 40 Watt Clear Light bulbs
Sales Forecast Qty

Customer 1175 Elektromarkt Bamby Plant 1200

Sales Forecast Qty
Sales Forecast Qty
Sales Forecast Qty
1-1-1 Based on this input sheet, what are the planning levels you will enter into your
planning hierarchy?

1-1-2 Based on the above structure, begin entering your planning hierarchy.
? When creating the planning hierarchy for the first time, leave the
characteristics blank.
A message will be displayed about the proportional factors. Because

we are not entering proportional factors, press All maintnce to bypass
this message.
Don’t forget to enter the data for both Sold-to Parties.
? Leave all the aggregation and proportion factors blank for now, because we
will let the system calculate the proportions based on actual data.
1-1-3 What is the menu path for this function?
1-1-4 Display the hierarchy graphic for your planning hierarchy thus far. How many
boxes (nodes) does it have?

1-2 You have decided entering the planning hierarchy is a tedious task. Since you forecast
based on your history of invoiced quantity, automatically build your planning hierarchy
based on last 12 month (including the actual month).
When you perform this function for the first time, select the simulation indicator. For
the second run, turn off the simulation indicator.
1-2-1 What version will you use to base your planning hierarchy?
1-2-2 When you have rerun this step with the simulation indicator turned off, display
your planning hierarchy, including the hierarchy graphic.
1-2-3 What additional sold-to partner(s) were created?
1-2-4 What materials were created for this partner?
1-2-5 What is the difference between your manual entries and the automatically
created entries?

1-3 Automatically create proportional factors for your planning hierarchy.
? Base this calculation on actual values of the key figure ”invoiced qty.”
? Make sure that the proportions are adjusted in the planning hierarchy.
? Use the last six month for the calculation
1-3-1 What version will you use to calculate your proportional factors?
1-3-2 Display your planning hierarchy. Where do you see the proportional factors?
1-3-3 Why is a proportional factor of sero calculated for sold-to partner 1000?

Solutions
Unit: Master Data

Topic: Planning Hierarchy
1-1 The following is the forecast input sheet your organization has been using to load
forecasts into your legacy system. It shows actual data collected for the prior year,
allowing space for your sales force to enter the sales forecast in currency values. Your
info structure S630 + ## already supports this format. Create a planning hierarchy for
your info structure that supports the data on the following sheet:

Customer 1000 Becker Berlin Plant 1200

Sales Forecast Qty
Sales Forecast Qty

Customer 1175 Elektromarkt Bamby Plant 1200

Sales Forecast Qty
Sales Forecast Qty

Sales Forecast Qty
1-1-1 Based on this input sheet, what are the planning levels you will enter into your
planning hierarchy?
Sales Org
1000
Division
04
Sold-to Party Sold-to Party

1001 1175
Material Material Material Material Material

L-80F L-40C L-60C L-80C L-40C
1-1-2
Plant Plant Plant Plant Plant
1200 1200 1200 1200 1200
Based on the above structure, begin entering your planning hierarchy

? When creating the planning hierarchy for the first time, leave the
characteristics blank.
A message will be displayed about the proportional factors. Because

we are not entering proportional factors, press All maintnce to bypass
this message.
Don’t forget to enter the data for both Sold-to Parties.

? Leave all the aggregation and proportion factors blank for now, because we
will let the system calculate the proportions based on actual data.
Logistics ? Logistics controlling ? Flexible planning ? Master data ?
Planning hierarchy ? Create
Enter your info structure S630 + ##. Press the green check button twice.
On the Create Planning Hierarchy screen, enter sales organization 1000.
Press [Next level]. Enter division 04.
Press [Next level]. Enter Sold-to 1000 and 1175.
Press [Next level].
Continue entering data using the input sheet above. When you are
finished, press [Save].
1-1-3 What is the menu path for this function?

Logistics ? Logistics controlling ? Flexible planning ? Master data ?
Planning hierarchy ? Create
1-1-4 Display the hierarchy graphic for your planning hierarchy thus far. How many
boxes (nodes) does it have?
Planning hierarchy ? Graphics
Enter Info Structure S-##, Press Enter.
Leave the characteristics blank.
The number of nodes is 14 + 1 for the planning hierarchy S##.

1-2 You have decided entering the planning hierarchy is a tedious task. Since you forecast
based on your history of invoiced quantity, automatically build your planning hierarchy
based on the last 12 month (including the actual month).
When you perform this function for the first time, select the simulation indicator. For
the second run, turn off the simulation indicator.
From the Flexible Planning menu:
Master data ? Generate master data
Enter your info structure S630 + ##.
Enter version 000.
Enter the date range specified above.
Be sure the simulation indicator is selected for the first time you run this step.
[Execute]
Green-arrow back.
Turn the simulation indicator off.
[Execute]
1-2-1 What version will you use to base your planning hierarchy?
Version 000 – Actual data
1-2-2 When you have rerun this step with the simulation indicator turned off, display
your planning hierarchy, including the hierarchy graphic.
Master data ? Planning hierarchy ? Display
Leave the characteristics blank.
Drill down to each level in the planning hierarchy using the [Next level]
button.
To see the graphic, press [Hierarchy graphic].
1-2-3 What additional sold-to partner(s) were created?
1001 and 1300

1-2-4 What materials were created for this partner?
L-40F, L-40Y, L-60Y and L-80F ...
1-2-5 What is the difference between your manual entries and the automatically
created entries?
Your manual entries have proportional factors of 0. The automatically
created entries have factors of 100. Technically, there is no difference
between these entries. The behavior of these entries will all be the same.
1-3 Automatically create proportional factors for your planning hierarchy.

? Base this calculation on actual values of the key figure ”invoiced qty.”
? Make sure that the proportions are adjusted in the planning hierarchy.
Set the indicator ”Consistent planning: adjust plng hierarchy proportions.”
? Use the last six month for the calculation
Master data ? Calculate proportns. ? Using actual data
Select ”Consistent planning: Adjust plng hierarchy proportions.”
Press [Enter].
Use version 000.
Use the date range specified above.
Select invoiced quantity.
1-3-1 What version will you use to calculate your proportional factors?
Version 000
1-3-2 Display your planning hierarchy. Where do you see the proportional factors?
Master data ? Planning hierarchy ? Display
The proportional factors are displayed at each level of the planning
hierarchy, relative to the level above.
1-3-3 Why is a proportional factor of sero calculated for sold-to partner 1000?
Because there are no actual data for sold-to partner 1000

Planning Types and Macros
Contents:
? Planning types
? Include actual data
? Performance enhancements
? Drill down functionality
? Variable time buckets
? Macros
? SAP AG 1999

Planning Types and Macros: Objectives

? Create your own planning type
? Outline the use of planning type info
? Generate your own macros
? Explain different ways to execute macros
? SAP AG 1999

Planning Types and Macros: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Info
Allocations
May
Events
Job
Mass Processing
Production Planning
? SAP AG 1999

Planning Types and Macros: Business Scenario
? Management would like to store all planning data,

both sales and production, in the same structure.
? Different departments would like to have different
views of their relevant data.
? Additionaly, certain user groups should be allowed
to display but not change certain key figures.
? SAP AG 1999

Planning Types
Planning type: SALES
Incoming orders qty.

Incoming orders Incoming ord. qty.
Invoiced quantity Incoming orders

Info Invoiced sales Invoiced quantity
Invoiced sales
Structure Production qty.
Stock level
Target stock level
Days‘ supply
Target days‘ supply Planning type: PRODUCTION
Version Version Sales
A00 001 Production qty .

Stock level
Target stock level
? SAP AG 1999
? In Flexible planning, you can create your own customized planning screens. These are called planning
types.
? A planning type is a self-defined view on the planning data in an information structure. The number of
planning types you can create for an information structure is not limited.
? To create a planning type, select Tools -> Planning type/macro -> Create in Flexible planning or carry
out the Customizing step Maintain planning types.
? In level-by-level planning, you define each level of the planning type separately.

Create a Planning Type 1
The
Theplanning
planningtype
type
determines
determinesthe
thehorizon
horizon
and
and the time gridof
the time grid of
Planning planning
Table: planning
Include
Includeactual
actualdata
data
from
from Version000
Version 000
in
inthe
theplanning
planningtable
table
You
Youcan
cancreate
createmacros
macros
The
Theplanning
planningtype
type in
in the planningtype
the planning type
determines which
determines which to
tocalculate
calculatekey
keyfigures
figures
key
keyfigures
figuresare
aredisplayed
displayed
in the planning table
in the planning table
? SAP AG 1999
? A planning type is a customized view on the planning table; for example, you might have one view for
the sales planner and another view for the production planner. A planning type defines the content and
layout of the lines in the planning table as well as the mathematical operations, in the form of macros,
which can be performed on these lines.
? A planning type is based on any information structure of your choice (either a standard information
structure or a self-defined information structure). You therefore have almost infinite possibilities with
regard to the information you can plan.
? The actions you perform to create a planning type are as follows:
?creating planning type info
?assigning a key figure to a line
?creating lines in the planning table
?defining line attributes
?defining macros
?using special operators to define macros for stock balance, production, days' supply, and historical
totals
?translating planning type, freely defined line, and macro texts

Create a Planning Type 2
Define:
Define:
• • drilling
drillingdown
down
Planning type • • performance
performance
Info structure • • extended
extendedselection
selection
screen
screen
Invoiced sales
Actual sales
Proport. Event
Correct. sales
Define
Defineline
linetype:
type:
•• output line
output line
•• planning
planningline
line
•• aggregation
aggregation
•• averaging
averaging
Insert
Insertevent
eventlines
lines
? SAP AG 1999
? The aggregate planning indicator in the planning type info enables:

?Drill down in the planning table
?Variable time buckets
?Saving of fixed values
?Performance enhancements
? If you set the indicator the key figure values are aggregated by the database server and only the totals are
transfered to the application server. If you do not set this indicator, the details are transferred to the
application server, which aggregates them. The indicators for planning types, that you created in Release
3.0 or 3.1 are set automatically when you upgrade.

Defining a Planning Table
Select key figures - Consistent

from info structure - Level-by-level
- Delta
- Order value
- Confirmed quantity
- Open order quantity Planning table
table
- Open order value
Orig. sales
- Delivery quantity Planning
Event
- Sales type
Corr. sales
Deviation in %
Macro
Event/orig. sales * 100
Define additional
= Deviation in %
lines
+ - * / etc. - Event
- Corrected sales
- Actual data
from previous year
? SAP AG 1999
? A planning type typically contains a subset of the key figures in the underlying information structure.
? You can also define further lines whose contents are obtained, for example, by the execution of macros.
? You define macros in a planning type. A macro performs a mathematical operation on an existing field
or fields, and returns a new calculated value. You can set up a macro such that it is automatically
executed when the planner enters or leaves the planning screen, or when he presses Enter.
? In a planning type, you can also insert lines for this year's actual data, last year's actual data, events, and
external data.
? To define which data is read into the external data line, you must use functional enhancement
MCP20001 in a Customizing project (transaction CMOD).
? You set attributes for each line in a planning type.

Aggregation and Disaggregation:
Determine by Aggregation Type
Define Info Structure

Structure Define Planning Type
Type
Planning Planning Define screen Define
method units layout macros
Key figure
parameters
Set
aggregation type
? SAP AG 1999
? The aggregation type of a key figure specifies how that key figure is aggregated and disaggregated. You
set the aggregation type in Customizing (either in Set planning parameters for info structures and key
figures or in Maintain planning types).
? There are three aggregation types:
?An average is created
?A total is calculated; disaggregation is carried out on the basis of the proportional factors
?No aggregation is carried out
? The default aggregation type for planned key figures is "total calculated". The default aggregation type
for a freely defined line is "no aggregation". For more information, see the IMG.

Standard Planning Types
SOPKAPA
SOPKAPAM
SOPDIS
? SAP AG 1999
? Standard SOP comes with three planning types:

?SOPKAPA: the system uses this for the single -level planning of a product group
?SOPKAPAM: the system uses this for the planning of an individual material
?SOPDIS: the system uses this for dual-level planning of a product group
? You can copy any one of these planning types and then modify it to suit your needs.

Aggregate Planning
? Improved performance
? Drill down functionality
Aggregated
Database Application
Application
server server
Detailed
? SAP AG 1999
? Aggregate planning indicator

You set this indicator in the planning type by choosing Maintain planning types in Customizing. Key
figures in this planning type are then aggregated by the database server, and only these totals are
transported to the application server. If you do not set this indicator, the details are transported to the
application server, which then aggregates them. The indicators for planning types that you created in
Release 3.0 or 3.1 are set automatically when you upgrade.
? This indicator enables the following functionality:
?Improved performance
?Drill down functionality
?Flexible time buckets
?Permanent fixing

Variable Time Buckets
3.0 Database ... W17 W18 W19 ...

Display ... W17 W18 W19 ...
4.0 Database ... W17 W18.4 W18.5 W19 ...
Display ... W17 W18 W19 ...
or ... 04/97 05/97
? Data entry in different time buckets possible

? Aggregation and disaggregation based on predefined time
bucket grid
? SAP AG 1999
? You can plan using more than one period indicator. For these indicators, you let the system generate a
technical period that is saved in the form of a fiscal year variant. The planning method of the information
structure must be consistent planning. The following example explains how to plan in weeks and
months.
? Example: Set the information structure parameters for this function in Set parameters of info structures
and key figures as follows:
1) Press F4 on the Planning periods field. (The Storage periodicity field is not ready for input.)
2) In the planning periods box on the next screen, enter 'W' and 'M' in the PI column.
3) Enter a name for your technical fiscal year variant. This name should consist of two letters.
4) Enter a generation horizon. This horizon should encompass the planning horizon - both past and
future periods - that you wish to plan with this information structure.
5) Save these settings.
? A technical fiscal year variant is automatically generated. You return to the Information Structure
Parameters screen. The name of your technical fiscal year variant (see step 3) appears as the fiscal year
variant. A 'G' appears in the Planning periods field. This 'G' stands for generated.
? Define the sequence of the periods in the planning type info.

Macros
? Record function: standard operators

? Record function: special macros for production, stock
balance, days' supply, and historical totals
? Create function
? Functional enhancement MCP20002 (macro "User...")
? SAP AG 1999
? You define very simple macros with the Record function. Follow the instructions at the bottom of the
screen.
? You define more complicated macros with the Create function.
? To calculate production, stock balance, days' supply, or a historical total, you can use one of the special
macros provided by SAP.
? To write your own, highly complex macro, use functional enhancement MCP20002 in a Customizing
project (transaction CMOD). The macro name must begin with the string 'USER'.

Standard Macro Operations
Operand 1 Operator Operand 2 Result

(mandatory) (optional)
+
–
Key figure
*
or
Key figure / numerical Key figure
value
>
<
=
Key figure =V Key figure
Key figure Key figure

DM
owner member
Key figure Key figure

AM
member owner
? SAP AG 1999
? You record or create a macro with the aid of predefined operators.

? In level-by-level planning, you must define the level at which a macro is to be executed. This is either
owner or member level.

Automatic Macro Execution
Event Key stroke

Read Save
data Read data
data
Save data
Macro INITIAL DEFAULT FINAL
Time
? SAP AG 1999
? You can specify that a macro is to be carried out automatically for a particular planning type. There are
three ways to execute a macro automatically:
?The initial macro is run whenever you call up the planning table.
?The default macro is run whenever you regenerate the planning table, (for example, when you press
ENTER), or when you call up or save the planning table. Caution: This can result in the macro
running several times.
?The final macro is run immediately before the data is saved.
? To define a macro for automatic execution, select Goto Planning type info from the planning type menu.
? Alternatively or in addition, you can write macros that can be executed manually at any time in the
planning table (with Edit Macro).

Planning Types and Macros: Summary

? Outline the use of planning type info
? Generate your own macros
? Explain different ways to execute macros
? SAP AG 1999

Exercises
Unit: Planning Types and Macros

Topic: Planning Types
Management would like to store all planning data, both sales and
production, in the same structure. You must determine if the default
planning table layout is sufficient for your requirements.
Management would like a separate view of the data for the sales
personnel and the production planners.
For the SALES view, management wants to see the forecast values for
invoiced sales and have a running comparison to actual sales. In addition,
they want to see last year’s sales as well as the invoiced quantity for the
current year and last year.
1-1 The following is your current forecast input data sheet. Your sales force completes this
form on a rolling monthly schedule, always starting with the actual calendar month.
Note that when your sales representatives receive this form, either electronically or
hard copy, the last year’s historical values are populated. The sales force must fill in
this year’s sales quantity forecast.
Sales Organization 1000 Germany Division 04 – Lighting

Customer 1001 Lampen-Markt GmbH MaterialL-80F 80 Watt Frosted Light bulbs
Month 1 Month 2 Month 3 Month 4 Month 5

Sales Forecast Qty
Actual Invoiced Qty
Actual Invoiced Sales

1-1-1 Create a planning type, ZSALES-## to simulate this form, where ## is your
group number.
Assign the info structure S630 + ## to the planning type.
Be sure your planning type has the following features:
? Include your group number in the description of your planning type.
? Allow the sales representative to plan 12 months of the sales forecast,
starting with this month.
? Allow the sales representative to see the history up to 15 months, but do not
allow changes to the history.
? Create a line for entering the sales quantity forecast. This line will come
from adding the field Invoiced Quantity to your planning type and changing
the description to Sales Forecast Qty.
? Include this year’s and previous year’s actual invoiced quantity, allowing
the sales reps to compare against the forecast as you go forward in time.
? Include this year’s and last year’s actual invoiced sales values.
Note: You must include the line Invoiced Sales in the planning type in
order to include Actual Invoiced Sales and Previous Year Invoiced Sales,
even if you are not forecasting this line. To prevent this line from being
displayed, change the line attributes from planning line to auxiliary line.
? Save your new planning type.
Note: You will be prompted by pop-up window to enter a transport and

correction request. Follow these steps:
1. Select Create request.
2. Enter a description. Include your group’s number in the text.
3. Save.
A task number will be automatically assigned. You can use this number
in subsequent exercises.

1-2 Using your new planning type goto interactive planning without entering charcteristics
and create version 001 for your info structure.
1-2-1 What is the difference between the forecast lines in your plan and the actual
data key figures?
1-2-2 What version stores the actual data?
1-2-3 Use the left and right scroll arrows below the planning table. How far to the left
can you go? How far to the right? Why?
1-2-4 Using this new planning type, which month is the earliest you can manipulate
the forecast values?
1-2-5 Save your version.

Topic: Macros
? Create macros within your planning types
Management would like to see how sales are progressing relative to last
year’s plan. They would like to see the total difference and, optionally,
the percent deviation. They would like to see this information at each
level in the planning table.
2-1 Create a macro for planning type ZSALES-## comparing current sales to this year’s
plan. Define this macro to calculate automatically in your planning table.
2-1-1 Add a new output line to your planning type to accommodate this new field.
Make sure this value will be seen at each level in the planning table. Give this
field a meaningful name, such as Sales Difference.
2-1-2 Using the Record macro function, create a macro called DIFFERENCE that
calculates the difference between current actual invoiced sales and the invoiced
sales forecast. Use the formula
SALES DIFFERENCE = SALES FORECAST QTY – ACTUAL SALES
The system provides prompts in the bottom left-hand corner of the

steps to recording a macro.

2-1-3 Edit the definition of your macro. Using F1 Help, describe the functionality of
the ‘S’ column in the Change Macro feature.
2-1-4 Set up your planning type so your macro is calculated automatically.
2-1-5 Save your planning type.
2-2 Using your new planning type, change the inactive version 001 you already created.
2-2-1 Enter 1000 units sales forecast qty for the actual month and press enter. Where
is the result of the macro calculation displayed?
2-2-2 Is the new field stored in the info structure when the plan is saved?

*2-3 Create a new macro to calculate the percent deviation of your actual sales from your
sales forecast. Be sure this macro, as well as your first macro, calculates automatically
when using your planning type.
2-3-1 Add two new fields to your planning type:
Temp1 – to use for an intermediate calculation
Percent Deviation - for displaying the new calculated value
Make sure the Percent Deviation is an output line that will be displayed at each
level of the planning table.
2-3-2 Using the Create macro function, create a macro called DEVIATION to
calculate the percent deviation. Use the formula
DEVIATION = SALES DIFFERENCE / SALES FORECAST QTY* 100
2-3-3 Set all macros you have defined to calculate automatically in the planning table.
*2-4 Using your planning type, change the version of your plan from above.
2-4-1 Is the percent deviation line populated automatically?
2-4-2 Change some forecast values. Does the percent deviation line change?

Solutions

Topic: Planning Types
1-1 The following is your current forecast input data sheet. Your sales force completes this
form on a rolling monthly schedule, always starting with the actual calendar month.
Note that when your sales representatives receive this form, either electronically or
hard copy, the last year’s historical values are populated. The sales force must fill in
this year’s sales quantity forecast.
Sales Organization 1000 Germany Division 04 – Lighting

Customer 1001 Lampen-Markt GmbH Material L-80F 80 Watt Frosted Light
bulbs
Month 1 Month 2 Month 3 Month 4 Month 5
Sales Forecast Qty
Actual Invoiced Qty
1-1-1 Create a planning type, ZSALES-## to simulate this form, where ## is your
group number.
Tools ? Plng.Type/Macro ? Create
Planning type: ZSALES-##. Do not copy an existing planning type
Specify Info structure: S630 + group number
Text: Planning type for Sales Group ##
? Allow the sales representative to plan 12 months of the sales forecast,
starting with this month.
Enter the current month into the Planning start date
? Allow the sales representative to see the history up to 15 months, but do not
allow changes to the history.
Enter Future periods: 12 and Historical periods: 15
Ensure Ready for input is deactivated. Press Enter to continue

? Create a line for entering the sales quantity forecast. This line will come
from adding the field Invoiced Quantity to your planning type and changing
the description to Sales Forecast Qty.
To add the field Invoiced Sales, Edit ? Assign structure or [Add structure
row]
Select Invoiced quantity.
To change the description to Sales Forecast Qty, you can type over the
existing description, or Edit ? Row attributes
Select Freely defined text and enter the text Sales Forecast Qty.
? Include this year’s and previous year’s actual invoiced quantity, allowing
the sales reps to compare against the forecast as you go forward in time.
To add this year’s and previous year’s actual invoiced quantity, place
your cursor on the field Sales Forecast Qty,
Edit ? Actual data or [Actual data]
Edit ? Actual data, prev. yr or [Actual data, prev. yr]
? Include this year’s and last year’s actual invoiced sales values.
Note: You must include the line Invoiced Sales in the planning type in
order to include Actual Invoiced Sales and Previous Year Invoiced Sales,
even if you are not forecasting this line. To prevent this line from being
displayed, change the line attributes from planning line to auxiliary line.
To add the field Invoiced sales,

Edit ? Assign structure
Select Invoiced sales.
To add this year’s and the previous year’s invoiced sales place your
cursor on the field Invoiced sales,
Edit ? Actual data, prev. yr
Edit ? Actual data
To prevent the field Invoiced sales from displaying in your plan, follow
the menu path
Edit ? Row attributes
Select Auxiliary line.
? Save your new planning type.

Note: You will be prompted by pop-up window to enter a transport and
correction request. Follow these steps:
4. Select Create request.
5. Enter a description. Include your group’s number in the text.
6. Save.
A task number will be automatically assigned. You can use this number
in subsequent exercises.
1-2 Using your new planning type goto interactive planning without entering charcteristics
and create version 001 for your info structure.
From the Flexible Planning menu
1. Planning ? Create
2. Enter your new planning type ZSALES-##.
3. Leave the characteristics blank.
4. Confirm version 001.
Your screen should look similar to the following:
Sales Organization Division

Sold-to Party Material
Plant
Version 001 Version 001 Inactive
Aggregate information Un M 05.1998 M 06.1998 M 07.1998 M 08.1998 M 09.1998 M 10.1998
Sales Forecast Qty CAR

PrvYrAct Invoiced qty 1068 2750 2090 2168 2274 3996
Actual Invoiced Qty
PrvYrAct Invoiced Sales 805164 2063472 1559754 1623144 1702468 8835844
1-2-1 What is the difference between the forecast lines in your plan and the actual
data key figures?
The forecast lines are open for data entry. The actual data is display only.
1-2-2 What version stores the actual data?
Version 000.

1-2-3 Use the left and right scroll arrows below the planning table. How far to the left
can you go? How far to the right? Why?
You can go 15 months to the left (history) and 12 months to the right
(forecast horizon). This is controlled in the planning type info screen.
1-2-4 Using this new planning type, which month is the earliest you can manipulate
the forecast values?
From the current month.

Topic: Macros
2-1 Create a macro for planning type ZSALES-## comparing current sales to this year’s
plan. Define this macro to calculate automatically in your planning table.
Tools ? Plng.Type/Macro ? Change
Enter your new planning type ZSALES-##.
2-1-1 Add a new output line to your planning type SALES to accommodate this new
field. Make sure this value will be seen at each level in the planning table. Give
this field a meaningful name, such as Sales Difference.
1. Edit ? Add row
2. On the new blank line, type Sales Difference.
3. Edit ? Row attributes
Change the row attributes to ‘output line’ and ‘total created.’
2-1-2 Using the Record macro function, create a macro called DIFFERENCE that
calculates the difference between current actual invoiced sales and the invoiced
sales forecast. Use the formula
DIFFERENCE = FORECAST – ACTUAL

steps to recording a macro.
Macro ? Record
1. Macro: DIFFERENCE (this is not case sensitive)
Description: Difference between forecast and sales
2. First line: double-click on Sales Qty Forecast
3. Operation: single-click on minus sign button (subtract)
4. Second line: double-click on Actual Invoiced Quantity
5. Results line: double-click on Sales Difference
6. Single-click on the Exit Macro button to end the recording of the macro.
7. Save your macro.

2-1-3 Edit the definition of your macro. Using F1 Help, describe the functionality of
the ‘S’ column in the Change Macro feature.
To see the definition of your macro, Macro ? Edit. Select your macro.
If you check this box, this macro line will be executed only in selected
columns of the planning table. Macro lines for which you do not check this
box will be executed in all plannable columns of the planning table, not just
in the selected columns.
Therefore, to see your macro calculated for all columns in your planning
table, do not select this box.
2-1-4 Set up your planning type so your macro is calculated automatically.
Goto ? Planning type info
Enter DIFFERENCE as the default macro.
2-1-5 Save your planning type.
2-2 Using your new planning type, change the inactive version 001 you already created.
1. Planning ? Change
2. Enter your new planning type ZSALES-##.
4. Select Inactive version. Choose the version you created with the forecast tool
earlier in the course.
2-2-1 Enter 1000 units sales forecast qty for the actual month and press enter. Where
is the result of the macro calculation displayed?
The macro is calculated by default upon entry into the planning table.The
result is shown in key figure "Sales Difference".
2-2-2 Is the new field stored in the info structure when the plan is saved?
No. It is calculated and displayed only within the planning table, because
"Sales Difference" is no key figure of the info structure.

*2-3 Create a new macro to calculate the percent deviation of your actual sales from your
sales forecast. Be sure this macro, as well as your first macro, calculates automatically
when using your planning type.
Tools ? Plng.Type/Macro ? Change
Enter your new planning type ZSALES-##.
2-3-1 Add two new fields to your planning type:

Temp1 – to use for an intermediate calculation
Percent Deviation - for displaying the new calculated value
Make sure the Percent Deviation is an output line that will be displayed at each
level of the planning table.
1. Edit ? Add row
2. On the new blank line, type Temp1.
Change the row attributes to ‘Auxiliary line.’
4. Edit ? Add row
5. On the new blank line, type Percent Deviation.
Change the row attributes to ‘Output line’ and ‘Total created.’

2-3-2 Using the Create macro function, create a macro called DEVIATION to
calculate the percent deviation. Use the formula
DEVIATION = SALES DIFFERENCE / SALES QTY FORECAST * 100
Macro ? Create
1. Macro: DEVIATION (this is not case sensitive)
Description: Percent sales deviation
2. First Operand: Sales Difference
For all fields on this screen, the F4 Possible Entries option will list all the
valid values. From here, you can select the appropriate value for the field.
3. Op (Operator): / Divide by line
4. Second Operand: Sales Qty Forecast
5. Result: Temp1
On the second line of the macro:
6. First Operand: Temp1
7. Op: * Multiply with Value
8. Second Operand: 100
9. Result: Percent Deviation
10. Save your macro.

2-3-3 Set all macros you have defined to calculate automatically in the planning table.
Because you can only default one macro in a planning type, you must include
the calculations of all macros into one macro definition.
1. Macro ? Edit
2. Select the macro DEVIATION.
3. Place the cursor on the first line of the macro.
4. Edit ? Insert row
On the first line (which should be blank):
5. First Operand: Sales Qty Forecast
6. Op: - Subtract line
7. Second Operand: Actual Invoiced Quantity
8. Result: Sales Difference
9. Save the macro.
10. Goto ? Planning type info
11. Change the default macro to DEVIATION.
12. Save your planning type.
13. You can delete the macro DIFFERENCE if you like, but this is not
necessary.
*2-4 Using your planning type, change the version of your plan from above.
2-4-1 Is the percent deviation line populated automatically?
Yes. The macro is calculated by default upon entry into the planning table.
2-4-2 Change some forecast values. Does the percent deviation line change?
Yes. The macro calculates by default when the Enter key is pressed.

General Planning Functions
Contents:
? Planning table
? Drill down in consistent planning
? Planning views
? Distribution functions
? Zero column – totals column
? Aggregation and disaggregation
? Fixing of key figures
? SAP AG 1999

General Planning Functions: Objectives
? Navigate in the planning table
? Use the planning functions

? Know how to use Aggregate Planning
? Copy data between info structures
? SAP AG 1999

Gerneral Planning Functions: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Info
Allocations
May
Events
Job
Mass Processing
Production Planning
? SAP AG 1999

General Planning Functions: Business Scenario
? As a sales planner, you are planning on selling

30000 cartons of light bulbs during the next six
months. You plan on distributing this evenly
among the six months. You want to disaggregate
these quantities based on prior history.
? SAP AG 1999

Planning Table
Create Plan: Consistent Planning

Create
Planning Edit Goto Extras System Help
Charact. Distribute ... Key figure Disaggregate line 0 column ... On
Region USA Sales organization South

Distribution channel Material
Plant 3
Header area:
Version 001 Version 001 New, inactive
shows which master
data you are planning
Aggregated information and which version
Un M 01.1999 M 02.1999 M 03.1999 M 04.1999 M 05.1999 M 06.1999

Incoming orders $ 950000 1000000 110000 110000 1260000 1380000
Incoming orders qty To 1900 2000 2200 2200 2100 2300
Price $ 500 500 500 500 600 600
Left column:
column: unit in which
Input matrix
key figures
figures the key figure
figure
laid out in rows and columns
being planned is recorded
recorded
? SAP AG 1999
? The planning table consists of a header area and an input matrix.

? The header area shows which master data you are planning and which version.
? The input matrix is laid out in rows and columns. The left column shows which key figures are being
planned; if desired, you can switch to a display that shows which characteristic values are being planned
(Views Key figure format). The right column shows the units of the key figures.
? You can enter data either manually, or by using distribution operators (e.g. +, -, *, /), or by running the
forecast, or by copying data from another information structure.
Extended Selection Screen for Planning Table Access
? You can plan ranges of characteristic value combinations as well as individual characteristic value
combinations. For example, you can plan materials 1 to 3, 5, and 7-9, without planning materials 4, 6,
and 10. You specify these ranges in an extended selection screen before accessing the planning table. To
activate this selection screen, set the Detailed selection indicator in the planning type. This indicator is
set automatically for any planning types that you created in Releases 3.0 and 3.1. If you are planning an
information structure without a planning type, you get the extended selection screen automatically.
? To exclude characteristic value combinations from the planning process, choose Pl.hierarchy Revise.

Drill Down in Interactive Planning
North America
USA
North South
Atlanta Dallas
? SAP AG 1999
Drilling Down in Consistent Planning

? You can drill down level by level in the planning table of consistent planning. The prerequisite is that
you have set the Aggr. planning indicator in the planning type. Any planning types that you created in
Release 3.0 or 3.1 have this indicator set automatically.

Views in the Planning Table
All key figures view

Total view:
All key figures at
- Incoming ord. qty.
Incoming orders
entry level
Invoiced quantity Detailed view:

Invoiced sales All key figures at
member level
Key figure invoiced sales
Sum of members Key figure view:

+ Sold-to party 1
Sold-to party 2
One key figure at sum
and member level
Sold-to party 3
? SAP AG 1999
Without the indicator aggregate planning in the planning type info you can select:
? Goto Total
?This takes you to the aggregate view on your data. If the planning method is consistent planning, you
see the total key figure values for all selected characteristic value combinations. If the planning
method is level-by-level planning, you see the total key figure values at owner level.
? Views Member
?This takes you to the detailed view on your data. If the planning method is consistent planning, you
see the key figure values at the most detailed level of the characteristic values combination. This is
often the material level. If the planning method is level-by-level planning, you see the key figure
values at member level.
? Views Key figure format
?When you place your cursor on a key figure and select this option, you see the values of this key
figure for all characteristic values at the detailed level. The sum of these values appears in the top line
of the input matrix. You can view the characteristic values in the left column as either numbers or
texts.
? Views All members
?This shows you the values of all key figure for all characteristic values at the detailed (consistent
planning) or member (level-by-level planning) level.
? With the indicator aggregate planning in the planning type info you just drill down the next level.

Basic Functions of the Planning Table
Places after decimal point Distribution functions

Operator
OP Description
= Replace time series values with the value
6. 123 + Add the value to the time series
- Subtract the value from the time series
* Multiply the time series values by the value
/ Divide the time series values by the value
% Value as percentage of the time series
etc. ...
Zero column Row totals

Aggregated information
Zero column M 01.1997 ? total

Incoming orders
Incoming orders qty
Price
? SAP AG 1999
? You can set the number of decimal places of any key figure and characteristic value. The number of
decimal places saved is determined by the Global Settings made in Customizing for that unit; otherwise,
by the number of places shown in the planning table at the time of saving.
? You can distribute a value across a selected time series using an operator.
? The so-called "zero column" has no particular period unit. Opening stock levels are displayed here. You
can enter other opening values in this column. The zero column is used only, if you don‘t have historical
data in your planning type (like in Standard SOP, or if no historical periods are selected in the planning
type, or if the historical periods are ready for input).
? You can calculate row totals for all or selected sections of the planning horizon.

Permanent Fixing of Values
Total incoming orders quantity: Total incoming orders quantity changed to:
20,000 pc 30,000 pc
3,000 5,000 3,000

(15%) 9,545
3,000 (25%) 3,000 (10%) (32%)
(15%) (10%)
3,000
(10%)
3,000 6,000
(15%) 11,454
(30%) (38%)
Fixing
Fixingat
ataggregate
aggregatelevel
levelalso
also
causes
causes fixing at detailedlevel
fixing at detailed level
? SAP AG 1999
Saving Key Figures with Fixed Values

? You can fix the value of a key figure in the planning table such that this value does not change when you
change values of the key figure at other planning levels. Since release 4.0 you can save these fixed
values.
The prerequisites for using this function are:
? You create the information structure that you use for planning with the Planning possible indicator
switched on. Any information structures that you created in Release 3.0 or 3.1 will have this indicator set
automatically; no manual action is necessary on your part.
? Before you generate the information structure, you set the fixing indicator for the key figures for which
you want to store the fixing. The generation of the info structure then automatically creates a new key
figure on the data base to store fixed values. (See definition of the data base table using transaction
SE16). Key figures in information structures that you created in Release 3.0 or 3.1 will NOT have this
indicator set automatically; manual action is necessary on your part.
? You set the Aggr. planning indicator in the planning type. Key figures values you fix in the planning
table are then fixed in the database when you save the planning version. Any planning types that you
created in Release 3.0 or 3.1 will have this indicator set automatically; no manual action is necessary on
your part. You can also fix the values of an entire line by double -clicking in the initial column.

Units of Measure
Customizing of Info Structure Master Data (material master record)
Base unit of measure Base units of measure
Planning Table
Toggle
Planning unit Hierarchy unit
? SAP AG 1999
? You maintain the base unit of measure in Customizing Set planning parameters for info structures and
key figures (Transaction MC7F).
? If you maintain in the Material Master a conversion of alternative units you can toggle between the base
unit and other units.

Planning Units
Currency unit
USD CAD
DEM
Planning
units
Unit of measure Period unit
PC TO P T
BOX M W
? SAP AG 1999
? You enter an exchange rate type with the currency unit. This will allow you to convert between
different currencies in the planning table.
? To switch to a different currency unit for a key figure, you overwrite the currency unit on the appropriate
line of the planning table.
? The period unit (storage periodicity) defines the period in which data is called in the planning table
and stored on the database.
? In level-by-level planning, the entry for period unit (storage periodicity) is optional. The planning table
is then called in the period unit in which it was last saved.
? If no storage periodic ity has been defined in level-by-level planning, you can change the period unit of
part or all of the planning horizon in the planning table.
? In consistent planning you can select sequence of periods in the planning type info if you generated
technical periods in Customizing Set planning parameters for info structures and key figures
(Transaction MC7F).

Copying Key Figures from One Info Structure to
Another
? Consistent Consistent
? Consistent Level-by-level
? SAP AG 1999
? You can copy key figure values from one information structure to another. These can be either monetary
values or quantities.
? Three standard copying methods are defined:
?From consistent planning to consistent planning
?From consistent planning to level-by-level planning
?From delta planning to level-by-level planning
? If you require a different combination of planning methods, you must write your own user method in
Customizing.

Copying Key Figures: Warehouse Split
Info structure S730

Version 003
Planning data is created in
From 01/01/1997
information structure
TO 12/ 31/1997
Key figure
Invoiced sales quantity Key figure is selected
Incoming orders quantity
.. ..
. .
Sales organization 0003

Sales organization 0002
Individual
Individual plans
plans are
are
Sales organization 0001 aggregated
Sales office 01
Customer 1001
Material A
Total sales
Total sales of
of Material
L-60F
material
Warehouse split Sales: Sales:

Plant 1200 Plant 3200
? SAP AG 1999
? The warehouse split is taken into consideration if you copy from an info structure without plant to an
info structure with plant in the hierarchy.
? If you perform this action at product group level, the material data is automatically aggregated.
? In Standard SOP, you can then plan the production quotas of different plants.
? Each combination of material and plant (SKU) is treated as a separate planning object in standard SOP.
This means that when the system copies data from Flexible Planning to Standard SOP, it must distribute
the material data across all the plants in which the material is planned. These are the plants you have
maintained for that material in the product group.
? You define this automatic plant distribution ("warehouse split") in Customizing (Define proportional
distribution across plants). If you make no entries in Customizing, the system distributes the data
equally.

General Planning Functions: Summary

? Use the planning functions
? Know how to use Aggregate Planning
? Copy data between info structures
? SAP AG 1999

Exercises
Unit: General Planning Functions

Topic: Planning Table

? Know how to use the planning functions
As a sales planner, you are planning on selling 30000 cartons of light

bulbs during the next six months. You plan on distributing this evenly
among the six months. You want to disaggregate these quantities based
on prior history.
1-1 Change your sales plan version 001 using your group’s planning type ZSALES-##.
1-1-1 To change a plan at the division 04 level of the planning hierarchy, what
characteristics should you specify when entering your plan?
1-1-2 Before you can distribute numbers across months, what must you do?
1-1-3 Using the Distribute function to spread a quantity of 30000 cartons across the
next six months at division level of your planning hierarchy. Enter this plan into
the key figure Sales Forecast Qty.
1-1-4 Create a column for line totals. Select all columns to be totaled.
1-1-5 How do you get rid of the line total column?

1-1-6 Once you have entered your plan, how can you see all the plan values for the
key figure Sales Forecast Qty?
1-2 In the key figure view, at division 04 level, in the current month and next month,
change the Sum of Members to 1000. What happens to the detail lines?
1-2-1 Using these two columns for comparison purposes, in the first column only,
double the Sum of members line. What happens to the detail lines?
1-2-2 In the first column only, change a value in the detail lines. What happens to the
Sum of members line?
1-2-3 In the first column only, enter 1000 in the Sum of Members line again. What
happens to the detail lines now?
1-2-4 Disaggregate the row. What happens to the detail lines?
1-2-5 Fix the value of the second member in the first column.

1-2-6 Increase the Sum of Members line to 2000 for the first column. What happens to
the detail lines now?
If you switch on the fixing generally, all changed data are fixed
automatically
You can save the fixing only in aggregate planning for key figures
which have the flag fix in customization of the info structure.
1-3 Remaining in the key figure view, make the following changes:
1-3-1 Display the characteristic description
1-3-2 Change the lead column widths to 35 and all other columns to 12.
1-3-3 Change the sequence of the characteristic to Material, Sold-to Party, Sales
Organization, Division and Plant.
1-3-4 Drill-down the hierarchy until the material level, or alternatively to when the
detail line includes the material. Change the unit of measure from CAR to PAL.
1-4 Save your plan.

Solutions
Unit: General Planning Functions

Topic: Planning Table
1-1 Change your sales plan version 001 using your group’s planning type ZSALES-##.
Planning ? Change
Specify the planning type ZSALES-##.
1-1-1 To change a plan at the division 04 level of the planning hierarchy, what
characteristics should you specify when entering your plan?
Enter division 04 as characteristic. When using level-by-level planning, you
must enter sales organisation 1000 and division 04.
1-1-2 Before you can distribute numbers across months, what must you do?
Select the months to distribute by either of two ways:
1. Clicking on the header of each column you want to choose
2. Click on the first and last column.
1-1-3 Using the Distribute function to spread a quantity of 30000 cartons across the
next six months at division level of your planning hierarchy. Enter this plan into
the key figure Sales Forecast Qty.
1. Edit ? Distribute (or press the [Distribute] button)
2. Check the planning horizon to confirm the correct months have been
selected.
3. Enter 30000 into the Sales Forecast Qty key figure.
4. Select = = in the Op field (Operator) to distribute the value over the period
and replace old values
5. Press [Enter].
5. Deselect the columns using edit ? select ? ?deselect columns.
1-1-4 Create a column for line totals. Select all columns to be totaled.
Select [key figure], or Views ? All key figures
Settings ? Show row totals ? All columns
1-1-5 How do you get rid of the line total column?

Settings ? Show row totals ? Hide
1-1-6 Once you have entered your plan, how can you see all the plan values for the
key figure Sales Forecast Qty?
Place your cursor on the key figure ”Sales Forecast Qty.” and select [Key
Figure]. To see each level, select the line in which you are interested and drill
down. You can drill down using this method until you reach the lowest level.
The drill-down icons indicate the directions available.
1-2 In the key figure view, at division 04 level, in the current month and next month,
change the Sum of Members to 1000. What happens to the detail lines?
The value on these lines proportionally allocates the total of the Sum of Members.
1-2-1 Using these two columns for comparison purposes, in the first column only,
double the Sum of members line. What happens to the detail lines?
The detail lines increase to total the sum of members line. They retain their
original proportions.
1-2-2 In the first column only, change a value in the detail lines. What happens to the
Sum of members line?
The sum of members line increases to the total of the lines.
1-2-3 In the first column only, enter 1000 in the Sum of Members line again. What
happens to the detail lines now?
The detail lines total the Sum of members line. They however do not retain
their original proportions. The proportions are re-calculated when the detail
line was changed.
1-2-4 Disaggregate the row. What happens to the detail lines?
The detail lines return to their original proportions.
1-2-5 Fix the value of the second member in the first column.
Settings ? Firming ? Switch on.
Double-click on the value. The value should turn red.
Double-click on the line,. The line should turn red.

1-2-6 Increase the Sum of Members line to 2000 for the first column. What happens to
the detail lines now?
The fixed value remains the same. The proportions for the other details lines
are re-calculated.
Changed values are also fixed. Another double click defixes the value.

If you switch on the fixing generally, all changed data are fixed
automatically.
You can save the fixing only in aggregate planning for key figures
which have the flag fix in customizing of the info structure.

1-3 Remaining in the key figure view, make the following changes:
1-3-1 Display the characteristic description
Settings ? Charact. display ? Description
1-3-2 Change the lead column widths to 35 and all other columns to 12.
Settings ? Column width
Enter 35 in the lead column and 12 in self-defined.
1-3-3 Change the sequence of the characteristic to Material, Sold-to Party, Sales
Organization, Division and Plant.
Settings ? Column header info
In detail column, change the sequence.
1-3-4 Drill-down the hierarchy until the material level, or alternatively to when the
detail line includes the material. Change the unit of measure from CAR to PAL.
Either overtype the field ”Un” or click on the column, Settings ? Units ?
Change Units. The system will automatically convert, based on the values in
the Material Master record.
1-4 Save your plan.

Statistical Forecast
Contents:
? Forecast models
? Forecast profiles
? Forecast versions
? Outlier control
? Workdays correction
? SAP AG 1999

Statistical Forecast: Unit Objectives
? Carry out a forecast

? Outline the use of forecast profiles
? Store and load forecast versions
? Base the forecast on the number of workdays
in a period
? SAP AG 1999

Statistical Forecast: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Info
Allocations
May
Events
Job
Mass Processing
Production Planning
? SAP AG 1999

Statistical Forecast: Business Scenario
? Management wants to create a sales plan based

on the historical data for the invoiced quantity.
They also want to see the difference between
calculating the forecast at the aggregate and
disaggregate levels.
? SAP AG 1999

Forecast
Consumption Actual ? Analysis of historical data

Consumption Actual data
data
enables prediction of
future patterns
? Use of robust, proven forecast
models
Forecast
Forecast
Forecast ?exponential smoothing
?moving averages
? Automatic model selection is
Prediction
Prediction possible
? Graphical monitoring and
manipulation of both historical data
and forecast results.
Used
Used as
as planning
planning figures
? SAP AG 1999
? Forecasting in SOP is a tool used to predict future activity based on specific criteria.
? The system reads historical data and calculates values which it proposes as future data.
? This historical data can be either actual data or consumption data. Actual data relates to a key figure such
as invoiced sales. Actual data is stored in the information structure, version 000.
? Consumption data includes all kinds of goods issues including goods that are written off as scrap. The
consumption data of a material is stored in the material master record. You can base the forecast on
consumption data if the planning method is level-by-level and if the info structure contains the
characteristics "material" and "plant".
? Standard SOP refers always to consumption data, because there is no version 000 available.
? Statistical forcast in Consistent planning is always based on actual data of version 000.
? You can either make the forecasted values your plan or modify them further.
? In the planning table, the system guides you through the steps necessary to run the forecast.
? You can also carry out the forecast using a mass processing job.
- Reference materials
? If you do not have any historical values for a materia l (for example, because it is new), you can still run
the forecast for this material by using the consumption quantities of a "reference material." You define
this reference material in the material master record. You must also set the Consumpn. indicator in the
forecast profile. This function is supported for level-by-level planning.

Forecast Profiles: Concept
Model selection
Model Forecast model Parameters
explicit model constant - forecast basis

(consumption/sales)
explicit model with trend
additional test - seasonal length
season
best fit selection - smoothing parameters
seasonal trend
- number of historical
periods
Combine
Profile: low cost products

Profile: seasonal products
Profile: new products
Explicit model: trend
? factor: 0.5 ? factor: 0.3
? SAP AG 1999
? You store standard forecasting settings in a profile.

? You can create and save multiple profiles for different business purposes.
? The benefits of forecast profiles are as follows:
?You save time if the same settings are used repeatedly.
?Forecast profiles can be used for mass processing..
?You reduce keying errors.
? You can use forecast profiles to simulate different "what-if" scenarios and then compare the results.
? To determine the forecast value, all you need is the preceding forecast value, the last historical value,
and the "alpha" smoothing factor. This smoothing factor weights the more recent historical values more
than the less recent ones, so that they have a greater influence on the forecast.
? How quickly the forecast reacts to a change in pattern depends on your choice of smoothing factor. If
you choose 0 for alpha, the new average will be equal to the old one. In this case, the basic value
calculated previously remains, that is, the forecast does not react to current data. If you choose 1 for the
alpha value, the new average will equal the last value in the time series.
? The most common values for alpha lie between 0.1 and 0.5. An alpha value of 0.5 weights historical
values as follows:
?1st historical value: 50%
?2nd historical value: 25%
?3rd historical value: 12.5%
?4th historical value: 6.25% and so on..
Forecast Profiles: Example
Forecast Results Based on

Constant Model
Qty.
Profile 1: assume
constant model
Regular
lightbulbs
time
Forecast Results Based on

Seasonal Model
Profile 2: assume
Christmas seasonal model
lights
Christmas
? SAP AG 1999
? In the above example, future sales of the product families regular lightbulbs and Christmas lights are
forecasted using two different profiles. The first product family has a constant usage. The second
product family contains seasonal articles.
? Forecast Models for Different Historical Patterns
?Pattern Forecast model
?Constant Constant model
?Constant model with smoothing factor adaptation
?Moving average model
?Weighted moving average model
?Trend Trend model
?(1st-order exponential smoothing)
?2nd-order exponential smoothing model (with and without parameter optimization)
?Seasonal Seasonal model (Winters' method)
?Seasonal trend Seasonal trend model
?1st-order exponential smoothing model
?Irregular No forecast
?Moving average model
?Weighted moving average model

Automatic Aggregation of Historical Data
Product Division
'Clear Lightbulbs'
300 Boxes
60 Watt 40 Watt
Clear Clear
100 Boxes 200 Boxes
? SAP AG 1999
? If you carry out the forecast at a high level, the historical data is automatically aggregated.
? For this reason, the results of the forecast will be different if the forecast is run at a high level and the
results are then disaggregated to the detailed level than if you run the forecast at the detailed level.
? If you carry out the forecast in the background with consistent planning, you define the level for
forcasting in the variant.

Forecast Versions
Forecast results
st run
Foreca arter
qu
Historical data in 1st
1
Version
Fore Forecast
c
in 2n ast run database
d qu
arter
Vers
ion 2
Planning table
M 10.1999 M 11.1999 M 12.1999

Sales 1000000 1100000 1100000
Sales qty 2000 2200 2200
Price 500 500 500
? SAP AG 1999
? Forecast versions are a fast way to simulate different forecast results for the same planning version.
? All forecast versions are stored in the forecast database, when you save the planning table.
? You can base several forecast versions on the same corrected historical data and forecast parameters.
? You can view the forecast parameters and forecast results of any existing forecast version.
? In level-by-level planning, forecast versions are saved at the level for which they were carried out.
? In consistent planning, forecast versions are saved for the current planning object. If your actual
planning is based on several planning objects (for example because you entered the planning table with
gaps in the characteristics sequence, you cannot save the forecast result as a forecast version.
? To base the forecast on previously corrected historical values, and not on the original historical values,
set the Corrected values indicator in the forecast profile. The system then calculates the forecast results
using the corrected historical values of the forecast version that is currently displaying in the planning
table.
? You can delete forecast versions in a particular planning version of the information structure; moreover,
you can opt to delete forecast versions based on a particular forecast model (that is, a particular
combination of forecast parameters).
? To delete one or more forecast versions using mass processing, choose Planning -> Mass processing
-> Reorgan. forecast. This function allows you to delete forecast versions in either Flexible Planning or
the material forecast.

Interactive Business Graphic
Forecast Results
Click and Drag
Corrected 80
sales in $ 70
60
50
40
30
20
10
0
1st 2nd 3rd 4th
Qtr Qtr Qtr Qtr
? SAP AG 1999
? You can monitor and modify both the historical data and the forecast results in an interactive business
graphic.
? If you correct the forecast results in the business graphic, you have the option of copying them into the
planning table.

Automatic Outlier Control
8
? Background correction
7
? Manual identification and average calculation
6
5
4
Tolerance lane
3 = ep ± ? *1.25* MAD
2
ep = ex-post forecast
1
0
today
? SAP AG 1999
Automatic background correction of outliers in historical data

? To correct outliers automatically in the historical data on which the forecast is based, select Outliers in
the forecast profile. The system calculates a tolerance lane for the historical time series, based on the
sigma factor. Historical data that lies outside the upper or lower band of this tolerance lane is corrected
to the ex post forecast value.
? The width of the tolerance lane for outlier control is defined by the sigma factor. The smaller the sigma
factor, the greater the control. The default sigma factor is 1; this gives a remaining probability of 10%
for data correction. SAP recommends that you set a sigma factor at between 0.6 and 2.
? If you run the forecast online, historical data that has been automatically corrected by this function is
indicated in column "C" of the Forecast: Historical Values dialog box.
Automatic correction of historical data online
? Alternatively, you can automatically correct historical data online, without having selected Outliers in
the forecast profile. To do this, select "C" for each historical value you want to correct and choose
Correct. The system then calculates the average of all selected historical periods and displays it as the
new corrected historical value.

Workdays Correction
History
M1 M2 M3
Original 1900 2100 2300 Forecast
Forecast
Days 19 21 23 M4 M5 M6
Corr. 2000 2000 2000 Uncorr. 2000 2000 2000
Days 22 20 18
Original 2200 2000 1800
Average month defined as 20 workdays

(forecast profile)
? SAP AG 1999
? Average number of days per forecast period

?You can base the forecast on an average number of days per forecast period. For example, if your
forecast period is "month," you can run the forecast on the assumption that the number of workdays
in each month is 20 by entering "20" in the No. days field of the forecast profile (see above). The
system then corrects the forecast data based on the actual number of workdays in the period. The
actual number of workdays in the period is defined in the factory calendar.
? Forecast periods
?The period indicator on which you base the forecast can be different than the storage periodicity. You
set the storage periodicity in Customizing by choosing Set parameters of info structures and key
figures. You enter the forecast period in the Period ind. field of the forecast profile

Statistical Forecast: Unit Summary

? Carry out a forecast
? Base the forecast on the number of workdays in
a period
? SAP AG 1999

Exercises
Unit: Statistical Forecast
? Carry out the forecast

Management wants to create a sales plan based on the historical data for
the invoiced quantity. They also want to see the difference between
calculating the forecast at the aggregate and disaggregate levels.
1-1 Create a sales plan in the active version A00 for division 04 for the next 12 months
using the forecast tool. Base this plan on historical values, specifically, sales forecast
qty. for the past 12 months. Let the system automatically determine the model
selection. As you perform this task, answer the following questions.
1-1-1 What are the two options for specifying the forecast and historical date ranges?
1-1-2 List three of the seven options for model selection when running your forecast.
1-1-3 Change at least one of the historical values before executing the forecast.

1-1-4 What are the three methods for correcting historical outlier values? Two of
these methods are explained in the online help for the Correct Outlier Ind icator
on the Forecast: Historical Values screen.
1-1-5 Run different forecast models and write down the results like basic value, trend
value, MAD and error total for the different models.
1-1-6 Save your plan. Enter again and evalute your forecast version.
The forecast version contains all historical date, all parameters you have used
for the last forecast and the last result.

Solutions
Unit: Statistical Forecast
1-1 Create a sales plan in the active version A00 for division 04 for the next 12 months
using the forecast tool. Base this plan on historical values, specifically, sales forecast
qty. for the past 12 months. Let the system automatically determine the model
selection. As you perform this task, answer the following questions.
Note: If you are following the solutions, you can complete the steps and then return
to step 6 to answer the questions.
2. Enter your group’s planning type ZS6##-Sales.
3. Enter sales organization 1000, division 04.
4. Select the active version.
5. Place your cursor on the Sales Forecast Qty field in the planning table.
6. Edit ? Forecast
7. Confirm the period intervals for the forecast and the historical data (you may
have to change the interval for the historical data). Also confirm you are using
automatic model selection.
8. To manipulate historical data, select [Historical].
9. To perform the forecast, select [Forecasting].
10. Accept the parameters that are displayed on the Parameters for Automatic
Selection window, select [Forecasting].
11. Scroll through the Results window. Feel free to manually change any forecast
values.
12. Press enter to copy the results into the planning table.

1-1-1 What are the two options for specifying the forecast and historical date ranges?
1. Use period intervals. Enter the exact periods for the forecast and the
historical data. For example, the forecast period range can be entered as
04.98 to 04.99. The historical period range can be entered as 03.97
to03.98.
2. Use number of periods. Enter the number of forecast periods and
historical periods. For example, enter 12 for the number of forecast
periods and 12 for the number of historical periods.
1-1-2 List three of the seven options for model selection when running your forecast.
The seven models are:
Constant Seasonal
Trend Seasonal Trend
Automatic Selection (the system determines the appropriate model)
Historical Weighting
1-1-3 Change at least one of the historical values before executing the forecast.
There are three options for changing the historical values, all from within the
Forecast: Model Selection window, all of which are accessed by pressing the
[Historical] button from the Forecast: Model Selection window:
1. Manually type over the existing values.
2. Use the interactive graphics to click and drag each bar to its correct value.
Copy these results back to the table.
3. Select the periods to correct by checking the ”C” column. Then press the
[Correct] button. This will replace the selected periods with the average
value.
1-1-4 What are the three methods for correcting historical outlier values? Two of
these methods are explained in the online help for the Correct Outlier Indicator
on the Forecast: Historical Values screen.
1. Manually correct the values either by changing them in the Corr. Value
column of the Forecast: Historical Values screen or using the interactive
graphics.
2. Select the values to correct by placing a check in the ”C” column and
pressing the [Correct] button. This will calculate the average of the
corrected historical values and will replace selected values with this value.
3. Select ”Outliers” in the forecast profile and enter the Sigma factor for
outlier control. Run your forecast using this forecast profile.

1-1-5 Run different forecast models and write down the results like basic value, trend
value, MAD and error total for the different models.
1-1-6 Save your plan. Enter again and evalute your forecast version.
The forecast version contains all historical date, all parameters you have used
for the last forecast and the last result.
2. Enter your group’s planning type ZS6##-Sales.
3. Enter sales organization 1000, division 04.
4. Select the active version.
5. Place your cursor on the Sales Forecast Qty field in the planning table.
6. Edit ? Forecast ? Version

Events
Contents:
? Defining an event
? Assigning an event
? Displaying an event
? SAP AG 1999

Events: Unit Objectives
? Outline the role of events in SOP

? Create and use events
? Analyze the result in the planning table
? SAP AG 1999

Events: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Info
Allocations
May
Events
Job
Mass Processing
Production Planning
? SAP AG 1999

Events: Business Scenario
? Your marketing department has decided to run an

promotion on your light bulbs. They estimate that
sales quantity (invoiced quantity) will increase by
25% for the first month and 40% for the second
month the promotion will run. The promotion will
start on the first of the month after next (your
second planned month).
? SAP AG 1999

Events
Start of event
%
Corrected Planned Sales
100 % Original Planned Sales
W W W W W Time
07/97 08/97 09/97 10/97 11/97
Period W1 W2 W3 W4 W5
Normal planned sales 100 100 100 100 100
Proportional event +10% +20% +10% -5%
Corrected planned sales 110 120 110 95 100
? SAP AG 1999
? Events allow you to predict the impact of one-time events that cannot be deduced from historical data.
Examples of events include:
?Price changes such as promotions
?Special deals with major customers and vendors
?Competitor sales activitie s
?Management overrides
?Facts based on market intelligence
? You define an event either as a series of percentage changes ("proportional" events) or as one or more
whole numbers ("cumulative" events). In the above example, the event has been defined as a
percentage.
? The impact of the event is shown in the corrected key figure values of the planning table.

Events: Assignment to Information Objects
Event list Info structure Assignment
Characteristics
Material 1
Key figure .
.
Easter promotion
Material 5
Mid-season sales Planning
. versions
.
Special contracts Start date
1999
Material 5
.
.
Material 20
? SAP AG 1999
? In addition to the amount of the change, an event contains the following information objects:
?Period unit (day, week, month, or other period)
?Date on which the event is to start
?Characteristic values combination (e.g. sales organization and sales district)
?Key figure (e.g. invoiced sales value)
?Planning version
This information determines how the event is displayed in the planning table.
? The period unit of the event does not have to be the same as the period unit of the information structure.
The system assigns the event values to the correct periods in the planning table automatically

Events: Display in the Planning Table
Planning type
Planning type
Info structure
Invoiced sales
Actual sales
Insert event Cumulative Event
lines Proport. Event
Correct. sales
? SAP AG 1999
? In order to view an event in the planning table, you must first assign it to a planning type and then plan
that planning type.
? Cumulative event data is disaggregated to the detailed level using the constant proportional factors, not
on the basis of current planning data.
? Proportional events are displayed at the detailed level only.
? The data on event lines is calculated and displayed automatically in the planning table at runtime. It is
not saved on the database when you save the planning version.

Events: Unit Summary

? Create and use events
? Analyze the result in the planning table
? SAP AG 1999

Exercises
Unit: Events
Topic: Defining, Assigning, and Displaying Events

? Create and use events in a planning type
Your marketing department has decided to run a promotion on your light

bulbs. They estimate that sales quantity (invoiced quantity) will increase
by 25% for the first month and 40% for the second month the promotion
will run. The promotion will start on the first of the month after next
(your second planned month).
1-1 Create an event PROMOTION## based on the above business scenario. You will use
the following parameters:
? Create a monthly, proportional event.
? It will effect the key figure invoiced quantity.
? It will effect the active version.
? The promotion will start on the first day of your second planning month.
? Your event will be assigned to sales organization 1000 and division 04.
1-2 Add the event key figures to your planning type ZSALES-##. Store the corrected
forecast in key figure sales.
1-3 Review your plan using your planning type ZSALES-## and the active version. Look
specifically for sales organization 1000 and division 04. Change the key figure sales
forecast qty in all periods by adding for example a very small number. Save your plan
and enter it again to see the correction due to your event.
Using aggregate planning the corrected invoiced quant ity is only

calculated when you save your plan. Only changed quantities are
calculated.

Solutions
Unit: Events
Topic: Defining, Assigning, and Displaying Events
1-1 Create an event PROMOTION## based on the above business scenario. You will use
the following parameters:
? Create a monthly, proportional event.
? It will effect the key figure invoiced quantity.
? It will effect the active version.
? The promotion will start on the first day of your second planning month.
? Your event will be assigned to sales organization 1000 and division 04.
Tools ? Event ? Create
Enter your new event PROMOTION##. Press the green check.
Enter a description and select proportional and event length month. Press Enter.
Change the 100% to 125% in the first month and 140% in the second month.
Goto ? Create Assignment, or select [Assignment]
Enter your info structure S6##. Press
Select sales organization 1000, division 04, key figure invoiced quantity, your active
version and for the assignment date the first day of your second planning month.
Press 'Flag assignment'.
Select list of assignments to check which characteristics combinations were assigned.
Save the event.

1-2 Add the event key figures to your planning type ZSALES-##. Store the corrected
forecast in key figure sales.
Tools ? Planning type/macro ? Change
Enter your planning type ZS6##-Sales
Place the cursor on sales forecast qty and select [event remark].
Select key figure sales and press Enter.
Save your planning type.
1-3 Review your plan using your planning type ZSALES-## and the active version. Look
specifically for sales organization 1000 and division 04. Change the key figure sales
forecast qty in all periods by adding for example a very small number. Save your plan
and enter it again to see the correction due to your event.
Planning ? Change
Enter your planning type ZS6##-Sales
Enter sales organization 1000, division 04 and select the forecast version you
assigned in the event.
Change ‘Sales Forecast Qty’ using the distribution function and add 0.000001 to
each column. Save your plan.
Enter the plan again and check the result.
Using aggregate planning the corrected invoiced quantity is only

calculated when you save your plan. Only changed quantities are
calculated.

Production Planning
Contents:
? Production macros
? Rough-Cut planning profiles
? Work center hierarchies
? Resource leveling for capacity, cost and materials in
the planning table
? Customizing settings
? SAP AG 1999

Production Planning: Unit Objectives
? Create a production plan

? Explain the use of rough-cut profiles
? Outline the use of work center hierarchies for
different planning levels
? Explain the Customizing settings for rough-cut
planning
? SAP AG 1999

Production Planning: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Info
Allocations
May
Events
Job
Mass Processing
Production Planning
? SAP AG 1999

Production Planning: Business Scenario
? Once the sales reps are comfortable with their

sales forecast, your planners must create a
production plan, based on the sales forecast.
Management would like a PRODUCTION view of
this data that your planners can work with. This
production plan will be adjusted according to the
capacity of a bottleneck work center and will be
passed to demand management.
? Before you can create a production plan, you need

to create a planning type that includes macros
such as stock balance and target days supply.
? SAP AG 1999

Production Macros in Standard SOP
Synchronous to sales
W29/99 W30/99 M08/99 M09/99
Sales 50 70 220 250
Production 50 70 220 250
Target stock level

W29/99 W30/99 M08/99 M09/99
Sales 50 70 220 250
Target stock level 10 10 40 40
Target days' supply

W29/99 W30/99 M08/99 M09/99
Sales 50 70 220 250
Target days' supply 3 0 11 11
? SAP AG 1999
? There are four strategies in Standard SOP for automatically generating a production plan:
?Production quantities are the same as sales quantities in each period ("synchronous to sales")
?Production quantities are such that target stock levels are reached
?Production quantities are such that target days' supplies are reached
?Production quantities are such that the stock level at the end of each period is zero.
? You can also enter production quantities manually.
? Stock levels and days' supplies are calculated and displayed automatically whenever you regenerate the
planning screen.
? Opening stock levels are taken into account.
? To set opening stock levels manually in Standard SOP, choose Goto -> Opening stock level.

Special Macro Operations
Operator Description
LO Stock balance
L1 Target stock receipts
L2 Receipts
L3 Issues
L4 Target stock / issues
PR Target supply / production
RW Days´ supply
ZS Historical total
? SAP AG 1999
? The R/3 System comes with eight special operators with which you can calculate production, stock
balance, days' supply, or a historical total.
? Each of these operators is based on an internally defined formula. For detailed information on these
formulas, see the Extended Help .
? To define a macro with one of these operators, select Macro -> Record and then the pushbutton Special
operation. All you need to do is specify which lines in the planning type are to represent which
operands in the macro. For example, you might define the sales line as goods issues and the production
line as good receipts.

Rough-Cut Planning Profiles
Duration
Resource
Week 1 Week 2 Week 3 Unit
Raw material 13 2 Pallet
Work center group WCG 12 2 2 3 Day
Work center group WCG 19 4 4 Day
Costs 10 20 20 USD
? SAP AG 1999
? You use rough-cut planning profiles to plan critical resources. These might be:
?Bottleneck work center
?Material capacities
?Costs of goods transportation or a marketing campaign
? The following resource types are supported:
?Work center capacities
?Materials
?Production resources/tools
?Costs
? Rough-cut planning profiles can also give you an aggregate (summarized) picture of resources: i.e.
?Workdays (rather than hours or minutes)
?Work center groups and product groups (rather than individual work centers or products)
? An aggregate view of resource loads is particularly desirable for medium- and long-term planning.
? The base quantity is the number of units for which the resource is required. You cannot change the base
quantity once you have saved the rough-cut planning profile. Different lot size ranges may have different
base quantities.

Determination of Capacity Load
A B
A
C
D x = Capacity
requirements
Planned quantity Time per piece
= Available
capacity
Work center Labor
? SAP AG 1999
? Resource leveling is carried out with reference to a plant. If your information structure does not contain
the characteristic "plant" or if no plant is uniquely identifiable from the characteristic values defined in
your rough-cut planning profile, you need to set a planning plant in Customizing for Sales & Operations
Planning (in Set parameters for info structures and key figures and Set planning plant for SOP).
? What to maintain in the rough-cut profile:
?the time span of one planning period in the resources table, expressed in days
?the status of the rough-cut planning profile (as in a routing)
?the usage of the rough-cut planning profile (as in a routing)
?the lot size range for which the profile is valid
?the key figure causing the resource load (if the rough-cut planning profile is defined for an information
structure)
? You define the determination of capacity load in the rough-cut planning profile. The available capacity is
read from the bottleneck work center defined in the recource table of the rough-cut profile. The capacity
load is calculated multiplying the planned quantity by the total time maintained for the work center in
the rough-cut profile. The time span of the profile header is just to model the capacity load to produce x
base quantities on the bases of time. For example if you maintain 1 hour in two periods of the recource
table you will create a recource load of two hours for each planned base quantity.

Resource Leveling: Capacity Load
Material: 100 Watt

Watt Clear
Plant: 0001 Annual planning
planning 1997 Active
Version: A00
M10/1997 M11/1997 M12/1997 Unit
Sales 100 200 200 Box
Production 100 200 200 Box
Stock level 100 100 0 Box
Available 200 200 H

Assembly line 1
Requirements 50 100 H
Machine
Load 25 50 %
Available 500 500 H

Assembly line 1
Requirements 50 100 H
Labor
Load 10 20 %
? SAP AG 1999
? In Standard SOP you can carry out rough-cut, rate-based, or detailed resource planning in the planning
table. The results are based on either a rough-cut planning profile or a routing.
? In Flexible Planning you can only use the rough-cut approach.
? The system computes available capacity, capacity requirements, and capacity load and displays them per
period for every work center and capacity category.
? You see the total requirements planned in SOP for a particular work center and capacity category. For
example, you may plan to produce several materials at the same work center. To find out the source of
the capacity requirements in any period, choose Views -> Capacity situation -> pegged requirements.
? The split planning screen for capacity leveling shows you if capacities are sufficient to meet projected
targets. You can adjust your production quantities until capacity utilization is optimized. The new
capacity loads are computed instantly when you choose Enter.

Resource Leveling
Work center hierarchy Product group hierarchy
Overal
Overal
production
production
sector
sector Light switches Lightbulbs
Production
Production Production
Production
series
series series
series
AM2
AM2 AM3
AM3
Line 1 Line 2 Line 3

Production
Production Production
Production
line
line 11
... line
line nn
? SAP AG 1999
? You can carry out resource leveling either on a high level or at SKU level in both Flexible Planning and
Standard SOP.
? Don‘t create the rough-cut profiles for different levels for the same material, because the resource loads
will add up.

Customizing of Resource Leveling
Parameters of Scheduling Routing

Info
Info Structure Parameters Selection
Profile
Priority 1 = Usage 1
Status 4
Capacity Planning Plant

key figure Profile
Sel. ID Priority 2 = Usage 3
Status 4
Los Angeles
...
? SAP AG 1999
? A unique plant reference is required to carry out capacity leveling. If you are in Flexible Planning and
no unique plant can be identified from the planning hierarchy, the system checks to see if a plant has
been defined for the information structure in the Customizing step Set parameters for info structures and
key figures. If no plant has been entered here, the system bases capacity leveling on the universal SOP
plant defined in the Customizing step Set planning plant for SOP.
? The priority which rough-cut planning profile or routing is read depends on the Customizing settings
you have made in:
?Configure scheduling parameters
?Define routing selection

Production Planning: Unit Summary

? Explain the use of rough-cut profiles
? Outline the use of work center hierarchies for
different planning levels
? Explain the Customizing settings for rough-cut
planning
? SAP AG 1999

Exercises
Unit: Production Planning

Topic: Create a Planning Type for Production
? Create planning type for production

? Create a rough-cut planning profile
? Check the capacity load of your planned quantities
Once the sales reps are comfortable with their sales forecast, your
planners must create a production plan, based on the sales forecast.
Management would like a PRODUCTION view of this data that your
planners can work with. This production plan will be adjusted according
to the capacity of a bottleneck work center and will be passed to demand
management.
Before yo u can create a production plan, you need to create a planning
type that includes macros such as stock balance and target days supply
1-1 Create a planning type ZPROD-## for your info structure S6##.
? Allow the production planner to plan the next 12 months.
? Create a line to display the sales forecast. Do this by adding the key figure Invoiced
Quantity to your planning type and changing the description to Sales Forecast Qty.
The production planner should normally not change the sales quantities, so define
this line as an output line.
? Include the lines Stock level, Target stock level, Production, Days' supply, and
Target days' supply.
? Define Days' supply and Target days' supply so that an average is calculated when
these lines are aggregated.
? Define Stock level and Days' supply as output lines.
? Save your planning type

1-2 Change your planning type ZPROD-## and create three production macros.
1-2-1 Record the macro STOCK using two special operations Stock balance and
Days’ supply.
Stock Balance consists of
Receipts: Production
Issues: Sales Qty forecast
Stock: Stock level.
Days’ supply consists of
Day’s supply: Days’ supply
Stock: Stock level.

steps to recording a macro and the special operations.
1-2-2 Record the macro TARGET using the special operation Target stck/receipts
.Use the description Production/Target Stock ##.
Target stock/receipts consists of
Target Stock: Target stock level
Stock: Stock level.
1-2-3 Record the macro PRODUCTION using the special operation Target
supply/production .Use the description Production/Target Supply ##.
Target supply/production consists of
Target days’ supply: Target Days’ supply
Stock: Stock level.
1-2-4 Save the planning type.
1-2-5 Change the planning type and make the STOCK macro the default macro.
1-2-6 Save your planning type again.

Topic: Create a Production Plan
You decide that your sales plan (the one you created in the events unit)
will form the basis for your production plan.
1-1 Using your new planning type ZPROD-##, change your active version.
1-1-1 Check that the stock balance macro is running correctly.
The macro days’ supply is part of the default macro, but negative
days’ supply are not displayed.
1-1-2 Distribute target stock of 100 and target days’ supply of 20 days for each of the
next 5 periods.
1-1-3 Run the macro PRODUCTION/TARGET STOCK. Explain the result.
1-1-4 Run the macro PRODUCTION/TARGET SUPPLY. Explain the result.
1-1-5 Save your plan.

Topic: Create a Rough-cut Planning Profile
? Create a rough-cut planning profile
Now you want to analyse the capacity situation for your planned
production quantities. Create a rough-cut planning profile to define the
capacity load of your bottleneck work center on division level.
1-1 In Customizing specify key figure PRODU for capacity planning of your info structure
S6##.
1-2 Create a rough-cut planning profile for your info structure S6##.
1-3 Assign the rough-cut planning profile to Sales Organization 1000, Division 04.
Enter Sales Organization 1000, division 04 and press Enter.
1-4 Maintain the following profile:
Time span 1 workday

Base quantity 1
Status 4
Use 1
From lot size 1
To lot size 100000
1-4-1 Using an alternative session, display in the IMG, Resources Planning

customization settings to determine whether this rough-cut profile is allowed.
Selection Indicator 03 is always used for the capacity analysis in

flexible planning.

1-5 Returning to your Rough-Cut Planning Profile. Enter the bottleneck workcenter
L-1000 in plant 1200 and the unit ”hours”. You need 1 hour during the first time span
to produce the base quantity of cartons.
In these time spans you define the capacity requirements for the base
quantity to be produced on your work center. If your production
process for the base quantity lasts several days, you can enter
capacity requirements in the subsequent timespans. All entries are
summed up to calculate the capacity requirements for one base
quantity.
1-6 Save your rough-cut planning profile.

Topic: Check the Capacity Load of your Planned
Quantities
? Check the capacity load of your planned quantities
Use your rough-cut planning profile to get a rough overview of whether

you have created a feasible production plan.
1-1 Copy your active version to version 1##.
If all course members were to plan the same version and the same
work center, all capacity loads would aggregate.
1-2 Change the plan for the new version 1##. Specify Sales Organization 1000 and
Division 04 and perform a capacity check.
1-3 Level the capacity load.
If you have stored your planned version, the capacity requirements

are also stored. In order to recalculate the capacity load with a
changed rough-cut planning profile you have to change the
planned production quantities.

Solutions

Topic: Create a Planning Type for Production
1-1 Create a planning type ZPROD-## for your info structure S6##.
Tools ? Plng.Type/Macro ? Create
Planning type: ZPROD-##. Do not copy an existing planning type
Specify Info structure: S6##
Text: Planning type for Production ##
? Allow the production planner to plan the next 12 months.
Enter Future periods: 12
? Create a line to display the sales forecast. Do this by adding the key figure Invoiced
Quantity to your planning type and changing the description to Sales Forecast Qty.
The production planner should normally not change the sales quantities, so define
this line as an output line.
To add the field Invoiced quantity, Edit ? Assign structure or [Add structure
row]
Select Invoiced quantity
To change the description to Sales Forecast Qty, you can type over the existing
description. Or Edit ? Row attributes
Select Freely defined text and enter the text Sales Qty Forecast
Change the row attributes to ‘Output line’
Set the cursor to the next line
? Include the lines Stock level, Target stock level, Production, Days' supply, and
Target days' supply.
? Define Days' supply and Target days' supply so that an average is calculated when
these lines are aggregated.
Change the row attributes to ‘Average calculated’

? Define Stock level and Days' supply as output lines.
Change the row attributes to ‘Output line’
? Save your planning type
1-2 Change your planning type ZPROD-## and create three production macros.
1-2-1 Record the macro STOCK using two special operations Stock balance and
Days’ supply.
Stock Balance consists of
Stock: Stock level.
Days’ supply consists of
Day’s supply: Days’ supply
Stock: Stock level.

steps to recording a macro and the special operations.
Macro ? Record
1. Macro: STOCK (this is not case sensitive)
Description: Stock balance and days’ supply
2. Select [Special operation]
3. Select Stock balance
4. Choose receipts: Double-click on Production
5. Choose issues: Double-click on Sales Qty forecast
6. Choose stock: Double-click on Stock level
This completes the first special operation, however without saving add a
second special operation
7. Choose first line: Select [Special operation]
8. Select Days’ supply.
9. Choose days’ supply: Double-click on Days’ supply
11. Choose stock: Double-click on Stock level
12. Save the macro. Exit the macro.

1-2-2 Record the macro TARGET using the special operation Target stck/receipts
.Use the description Production/Target Stock ##.
Target stock/receipts consists of
Target Stock: Target stock level
Stock: Stock level.
Macro ? Record
1. Macro: TARGET (this is not case sensitive)
Description: Production/Target Stock ##
2. Select [Special operation]
3. Select Target Stck/receipts
4. Choose target stock: Double-click on Target stock level
5. Choose receipts: Double-click on Production
7. Choose stock: Stock level
8. Save the macro. Exit the macro.
1-2-3 Record the macro PRODUCTION using the special operation Target
supply/production .Use the description Production/Target Supply ##.
Target supply/production consists of
Target days’ supply: Target Days’ supply
Stock: Stock level.
Follow the similar steps to above. Save the macro. Exit the macro.
1-2-4 Save the planning type.
1-2-5 Change the planning type and make the STOCK macro the default macro.
Goto ? Planning type info
Enter STOCK as the default macro.
1-2-6 Save your planning type again.

Topic: Create a Production Plan
1-1 Using your new planning type ZPROD-##, change your active version.
2. Enter your new planning type ZPROD-##.
4. Select Inactive version. Choose the version you created with the forecast tool
earlier in the course.
1-1-1 Check that the stock balance macro is running correctly.
Without production quantities the sales quantities cause negative stock levels
The macro days’ supply is part of the default macro, but negative
days’ supply are not displayed.
1-1-2 Distribute target stock of 100 and target days’ supply of 20 days for each of the
next 5 periods.
Select the months to distribute:
1. Click on the first and last column.
2. Edit ? Distribute, or select [Distribute].
3. Select = in the Op field (Operator) to distribute the value
4. Enter 100 into the Target stock level and 20 into the Target days’ supply
key figure.
5. Press Enter.
1-1-3 Run the macro PRODUCTION/TARGET STOCK. Explain the result.
1. Edit ? ?Macro
2. Select PRODUCTION/TARGET STOCK
3. Press Enter.
Production quantities are determined by the sum of the sales qty forecast and
target stock level.

1-1-4 Run the macro PRODUCTION/TARGET SUPPLY. Explain the result.
Production quantities are determined by the sales qty forecast and the
necessary stock to cover the target days’ supply of the next month
1-1-5 Save your plan.

Topic: Create a Rough-cut Planning Profile
1-1 In Customizing specify key figure PRODU for capacity planning of your info structure
S6##.
Tools ? Business Engineer ? Customizing ? Implement. Projects ?
SAP Reference IMG
Logistics General ? Logistics Information System (LIS) ? Planning ? Master data
? Set parameters for info structures and key figures
Double-click on your info structure S6##
Enter ‘PRODU’ as the capacity figure.
The capacity check is now performed for the key figure Production.
1-2 Create a rough-cut planning profile for your info structure S6##.
Tools ? Rough-cut plng.prfl. ? Create
Enter your info structure and press Execute
1-3 Assign the rough-cut planning profile to Sales Organization 1000, Division 04.
Enter Sales Organization 1000, division 04 and press Enter.
1-4 Maintain the following profile:
Time span 1 workday

Base quantity 1
Status 4
Use 1
From lot size 1
To lot size 100000

1-4-1 Using an alternative session, display in the IMG, Resources Planning
customization settings to determine whether this rough-cut profile is allowed.
Selection Indicator 03 is always used for the capacity analysis in
flexible planning.
Create an alternative session

From the main SAP menu,
Tools ? Business Engineer ? Customizing ? Implement. Projects ? SAP
Reference IMG
Logistics - General ? Logistics Information System (LIS) ? Planning ?
Functions ? Resources Planning ? ?Define routing selection
Check that you have for selection ID 03 with priority 1 a rough-cut planning
profile 3 for usage 1 and status 4.
1-5 Returning to your Rough-Cut Planning Profile. Enter the bottleneck workcenter
L-1000 in plant 1200 and the unit ”hours”. You need 1 hour during the first time span
to produce the base quantity of cartons.
Select [Choose] or double-click on the first line of the resource table.
Select work center. Press Enter.
Enter work center L-1000, plant 1200, unit h. Press Enter.
Enter 1 hour in the first time bucket.
In these time spans you define the capacity requirements for the base
quantity to be produced on your work center. If your production
process for the base quantity lasts several days, you can enter
capacity requirements in the subsequent timespans. All entries are
summed up to calculate the capacity requirements for one base
quantity.
1-6 Save your rough-cut planning profile.

Topic: Check the Capacity Load of your Planned
Quantities
1-1 Copy your active version to version 1##.

Planning ? Version management ? Copy
Enter your info structure S6## and press Enter.
Enter your version for the production plan as source version and the version 1## as
target version and select [copy]
Say [Yes] to target version reset.
If all course members were to plan the same version and the same
work center, all capacity loads would aggregate.
1-2 Change the plan for the new version 1##. Specify Sales Organization 1000 and
Division 04 and perform a capacity check.
Planning ? Change
Enter your planning type ZPROD-## and press Enter.
Enter Sales Organization 1000, division 04 and select [ inactive version].
Select version 1## and press Enter.
Select Views ? Capacity situation ? Rough-cut planning ? Show
The plan displays the capacity categories of your selected work center, and their
available capacity.
The capacity requirements are calculated using your rough-cut planning profile. The
capacity load shows the percentage of allocated available capacity.
1-3 Level the capacity load.

If the capacity load exceeds 100% you have to rearrange your production plan.
Change the planned production quantities in order to obtain feasible results.
If you have stored your planned version, the capacity requirements

are also stored. In order to recalculate the capacity load with a
changed rough-cut planning profile you have to change the
planned production quantities.

Mass Processing
Contents:
? Mass processing tasks such as copy, macro, and
forecast
? Steps necessary to perform mass processing
? Execution at different planning levels
? Transfer to CO-PA
? Opening stock
? Transfer to Demand Management
? SAP AG 1999

Mass Processing: Unit Objectives
? Explain why to use mass processing

? Perform mass processing
? Check a mass processing job
? Copy data from and to CO-PA
? Transfer a production plan to Demand
Management
? Explain how plants are determined
? SAP AG 1999

Mass Processing: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Info
Allocations
May
Events
Job
Mass Processing
Production Planning
? SAP AG 1999

Mass Processing: Business Scenario
? Your sales force has been forecasting sales

quantity and a production plan was created. Now it
is time to transfer this planned production
quantities to demand management so your
production department can start producing
products based on what the sales force will sell.
? SAP AG 1999

Possible Mass Processing Tasks
Macros
Copy key figures from one info structure to another
Forecasting
Transfer to Demand Management
Copy/delete planning versions of one info structure
Calculate opening stock levels
? SAP AG 1999
? You can carry out some of the more complex planning activities in the background, for example,
activities including several actions or involving large volumes of data. This planning mode is known as
"mass processing".

Steps in Mass Processing
Create profile Define activity Create job Schedule job
Planning
Planning type
type Objects
11
12
1
Info structure 10 2
Action 9 3
8 4
Version 7
6
5
Profile
Activity
? SAP AG 1999
? Four planning activities can be carried out using the sequence depicted above:
?Executing a macro
?Forecasting
?Copying key figures from one info structure to another
?Transfer to or from CO-PA
?Transferring SOP data to Demand Management
? These activities, when carried out with mass processing, are based on a planning type.
? You can carry out several planning actions within one job as long as they have the same planning type.
For example, you might run a mass processing job that executes several macros at the same time.
? The sequence in which actions within one activity are processed depends on the sequential numbers you
define for them in the activity.
? The system performs all actions for the first characteristic value before processing the second
characteristic value. Consequently, if you want the system to perform one action for all characteristic
values before it starts the next action, you must define separate planning activities.
? A planning job has one of three statuses:
?Initial (' '), Started or completed with errors (' E'), or Completed successfully (‘S')
? Planning jobs are reusable.

Detailed Steps in Mass Processing
Transfer to
Copy IS IS
Dem. Mgt
Forecast
Copy to
CO/PA
Macro
Characteristics assignment
Key figure assignment
Profile
Activity
Create job and schedule
? SAP AG 1999
? This slide shows the settings you must maintain to perform the different tasks.
? To maintain the assignments, profiles and activities choose Flexible Planning -> Settings
? To create a job and schedule it, choose Flexible Planning -> Planning -> Mass processing
? Before you run a mass processing job, use this report to see which characteristic value combinations will
be processed: Planning -> Mass processing -> Revise. You can exclude from the report any
characteristic value combinations that you do not wish to process with this job.

Execution
Job queue Job overview
Job 1
Job finished
Job
?
Schedule Forecast
Forecast
Revise
Job
12
11 1
10 2 Job 1
9 3
8 4 Material 1 forecasted
7 6 5 Material 2 forecasted
..
..
Material 100 forecasted
? SAP AG 1999
? The job overview lists your jobs and their system status.
? If you want to start the job again set the status to active again (Mass processing -> Change).
? After a mass processing job has run, you can see which characteristic values combinations were
processed using Planning -> Mass processing -> Revise. The mass job report shows you not only the
status of the job, but also the status of each characteristic values combination. If the job contained errors
(status E), you know for which characteristic value combinations you need to repeat the job. The Step
column indicates the sequence in which different actions were carried out: for example, forecast = 1 and
macro = 2. Options of the mass job report:
?View the status message of a characteristic values combination. Select it and choose Edit -> Display
message.
?Sort the report in ascending or descending order. Choose Edit -> Sort ascending or Edit -> Sort
descending.
?Find a characteristic values combination. Choose Edit -> Find and enter the desired search criteria.
?Download the report to a PC file. Choose List -> Save as PC file, select the desired format, and enter
the desired path and file name.
?Delete a characteristic values combination from the report. Select it and choose Edit -> Delete.

Macro Calculation at Different Planning Levels
Example: Macro operation +1
Original plan Changed plan
Detailed level Aggregate l.
Sales organization 50 40 54 51
40
Distribution channel 30 100

20 0 32 22 30.5 20.5
Material 20 10 15
100 5 100 21 11 16 6 20.5 10 15.5 5
? SAP AG 1999
Level of macro calculation

? In online processing, the system calculates the results in one of two ways:
1) At the current level of the planning table: the Aggr. planning indicator in the planning type info is
switched on.
2) At the detailed level: the Aggr. planning indicator in the planning type info is switched off.
? In background processing, the system calculates the results at the planning level defined in the variant.

Assignement of Forecast Profiles to Materials
Job 1
Activity 1 Material 1
Material 2
Constant profile ..
..
Material 100
Job 2
Activity 2 Material 3
Trend profile Material 4
..
..
Material 200
? SAP AG 1999

Data Exchange Between CO-PA and Flexible
Planning
CO-PA profile
Key figures
assignment
CO-PA
CO-PA
Flexible
CO-PA
Planning
Characteristics
assignment
? SAP AG 1999
? You can now transfer data both to and from Profitability Analysis (CO-PA). For example, you might use
the sales plans you receive from CO-PA as the basis for creating sales and production plans in Flexible
Planning. Having finalized these plans, you might pass the results back to CO-PA, which works out the
cost of producing the planned number of units. This function is supported for both consistent and level-
by-level planning. The system converts between units automatically; that is, currency units, units of
measure, and period units.
? You trigger the transfer of data from Flexible Planning to CO-PA in Flexible Planning using mass
processing. You trigger the transfer of data from CO-PA to Flexible Planning in CO-PA with transaction
KE1K, either online or in the background..
? To transfer data maintain the Customizing activity ->Log. General->LIS->Planning-> Functions-
>Mass processing->Transfer LIS/CO-PA
? Create a key figures assignment profile
? Create a characteristics assignment profile
? Create a CO-PA profile

Opening Stock
Zero Jan. Feb. Unit

column
Sales Box
Box
Production Box
Box
90 boxes Stock 90 Box

Box
? SAP AG 1999
? The so-called "zero column" has no particular period unit. Opening stock levels are displayed here. You
can enter other opening values in this column. The zero column is used only, if you don‘t have historical
data in your planning type (like in Standard SOP, or in Flexible Planning if no historical periods are
selected in the planning type, or if the historical periods are ready for input).
? With mass processing, you can set the opening stock levels of one or more materials or product groups.
? The results are visible in the zero column of the planning table at run time. In consistent planning, the
results are automatically aggregated. In level-by-level planning, they are set at the level you specify in
the planning job.
? There are three ways to set opening stock:
?Read current stock
?Calculate average stock
?Apply a user method defined in Customizing

Transfer to Demand Management
SOP 3 basic Demand Management

transfer
transfer
options
options
Flexible planning
xyzxyzxyzxyz 11
abcabcabcabc 22
xyzxyzxyzxyz 11
abcabcabcabc 22
abcabcabcabc 22
xyzxyzxyzxyz 33
Standard SOP
- product group
xyzxyzxyzxyz 11
abcabcabcabc 22
xyzxyzxyzxyz 11
abcabcabcabc 22
abcabcabcabc 22
xyzxyzxyzxyz 33
Standard SOP
- material xyzxyzxyzxyz 11
abcabcabcabc 22
xyzxyzxyzxyz 11
abcabcabcabc 22
abcabcabcabc 22
xyzxyzxyzxyz 33
? SAP AG 1999
? You can carry out the transfer of data to Demand Management either online or in the background.
? There are three basic options for transferring SOP data to Demand Management:
?You transfer material data from the info structure. Use mass processing to transfer a range of
materials.
?You transfer material data from a product group. The data is either transferred direct from the
materials, or as proportions of the product group.
?You transfer one material's data. The data is either transferred direct from the material, or as a
proportion of the owner product group.
? A material can be a member of more than one product group. This means that it can be transferred to
Demand Management more than once. The system issues a warning if you try to transfer a material from
a product group that has not been marked as the MRP product group for that material.
? When you carry out the transfer, planned independent requirements are created in Demand Management.

Synchronized Data Transfer to Demand Mgmt
Sales organization
Division Sales plans
Flexible
Flexible
Sold-to party Production plans
.. Planning
Planning
Material .
Plant
Customizing:
Customizing:
Key figure is transferred ?Key
?Keyfigure
figure
when the flexible planning ?Planning
?Planningversion
version
version is saved ?Demand
?Demandversion
version
Independent
Statement of Demand
Requirements Demand
demand Management
.. Management
.
? SAP AG 1999
? You can have the system create or change independent requirements in Demand Management every time
you save in Flexible Planning. For this purpose, you make the following Customizing settings in Set
parameters of info structures and key figures.
? Field name of the key figure to be transferred
? Planning version in Flexible Planning from which the data is to be transferred (Sync. version)
? Demand version to which the data is to be transferred

Automatic Determination of Plants for Transfer to
Demand Management
1. Plant as defined in planning hierarchy

2. Plant as set in Define proportional distribution
across plants
3. Generic distribution quotas as set for plants
4. Equal distribution among all plants specified in
the material master record
? SAP AG 1999
? It is possible to transfer data to Demand Management from information structures of Flexible Planning
without the characteristic "plant." The system uses the plant distribution quotas you set in the
Customizing activity Define proportional distribution across plants to transfer the data.
? Plant distribution (sometimes known as the warehouse split) works as follows:
1) If a plant or plants can be found for the material in the planning hierarchy, data is transferred to
Demand Management for these plants.
2) If no plant can be found in the planning hierarchy, the system checks to see which plants have been
maintained for the material in the material master record. It then checks to see whether distribution
quotas have been maintained for the material in Define proportional distribution across plants. The
transfer to Demand Management is then based on these quotas.
3) If no distribution quotas are found for the material, the system checks to see whether you have set
generic distribution quotas; that is, distribution quotas that apply to all materials. If so, the transfer to
Demand Management is based on these quotas. If generic quotas exist for some but not all plants
maintained in the material master record, the system assumes that the distribution quotas of plants
without generic quotas are 0.
4) If no distribution quotas are found at all - neither material-specific nor generic ones - the system
splits the data equally among all the plants in the material master record.

Mass Processing: Summary

? Explain why to use mass processing
? Perform mass processing
? Check a mass processing job
? Copy data from and to CO-PA
? Transfer a production plan to Demand
Management
? Explain how plants are determined
? SAP AG 1999

Exercises
Unit: Mass Processing

Topic: Transfer to Demand Management
? Explain how to transfer quantities from flexible planning to demand

management.
Your sales force has been forecasting sales quantity and a production plan
was created. Now it is time to transfer this planned production quantities
to demand management so your production department can start
producing products based on what the sales force will sell.
1-1 Create a background job with the mass processing functionality that transfers the
production quantities you have planned to demand management.
1-1-1 Create a transfer profile. Be sure your profile contains the following:
? Name the transfer profile Demand ##, where ## is your group number
? Use the strategy Material direct from info structure.
? Use the info structure S6## as table.
? Use the key figure production (PRODU).
? A requirements type is not required.
? Specify your group number for the demand program version.
? Do not set the Active flag.
1-1-2 Create an activity for this job.

Use T## for the key, where ## is your group number.
Use 1 for the Act. Sequence, your planning type ZPROD-##
and the transfer profile DEMAND##.
Use the action UEBERGABE Transfer to demand management.

1-1-3 Create the mass processing job, for sales organization 1000 and division 04.
Use the active version. Transfer at plant level.
During this step, the information message No variants found will
appear. This is advising you that you will need to create the variant
to be used when running the background job. Press Continue. In the
subsequent Variants: Change screen assignment screen also press
Continue.
1-1-4 Schedule the job to run immediately.
1-1-5 Monitor the job.
Note: Double-clicking on the spool list displays basic spool list

parame ters. It does not display the list itself.
1-1-6 Display the results in Demand Management.

Solutions
Unit: Mass Processing

Topic: Transfer to Demand Management
1-1 Create a background job with the mass processing functionality that transfers the
production quantities you have planned to demand management.
1-1-1 Create a transfer profile. Be sure your profile contains the following:
? Name the transfer profile Demand##, where ## is your group number
? Use the strategy Material direct from info structure.
? Use the info structure S6## as table.
? Use the key figure production (PRODU).
? A requirements type is not required.
? Specify your group number for the demand program version.
? Do not set the Active flag.
Settings ? Mass processing ? Transfer profiles
Select [New Entries].
Create transfer profile Demand ##.
Select strategy 9: Material direct from info structure.
Enter your group’s info structure.
Select field name PRODU production.
Leave Reqmts Type blank.
Use your group number for the version. This version refers to the version you
will create in demand management, not your plan version.
Be sure to leave the Active flag blank. Selecting Active makes the demand
version active; meaning it will automatically be selected in the next MRP run.
Save your profile.

1-1-2 Create an activity for this job.
Use T## for the key, where ## is your group number.
Use 1 for the Act. Sequence, your planning type ZPROD-##
and the transfer profile DEMAND##.
Settings ? Mass processing ? Activities
Press [New Entries].
Create activity T## where ## is your group number. Use Act. Sequence 1.
Enter your planning type ZPROD-##.
Use the transfer profile you created above, Demand## where ## is your group
number.
Save the activity.
1-1-3 Create the mass processing job, for sales organization 1000 and division 04.
Use the active version. Transfer at plant level.
During this step, the information message No variants found will
appear. This is advising you that you will need to create the variant
to be used when running the background job. Press Continue. In the
subsequent Variants: Change screen assignment screen also press
Continue.
Planning ? Mass processing ? Create
1. Job number: Demand ## where ## is your group number.
Job name: Transfer to demand management
Press Execute.
2. Info structure: your group’s info structure
Version: active version.
Press Execute.
3. Double-click on your production planning type.
4. Create the variant Demand## where ## is your group number.
5. Enter Sales Organization 1000, Division 04.
Select your planning activity T##.
Select aggregation level plant, because you have to transfer at plant level.
Press Continue.

A dialog box will display the message ”Please check whether material and
plant are in the execution level.” Press [Continue].
Enter a description for your variant. Save your variant. Press the green arrow
to go back.
You should see the message ”Planning job created successfully.”
1-1-4 Schedule the job to run immediately.

Planning ? Mass processing ? Schedule
Job number: Demand##
Press Execute.
Press Immediate.
Press the Save button at the bottom of the screen. You should see the message
”Background job scheduled successfully.”
1-1-5 Monitor the job.

Planning ? Mass processing ? Job overview
Press Enter
You should see your job ”Transfer to demand management.” If there is an
”X” in the ”Active” column, press Refresh until the ”X” moves into the
”Finished” column.
To see the output of the job, click once on the job name and press Spool List.
Select the spool. Press [Display]. You should see a list of characteristics that
were sent to demand management.
Note: Double-clicking on the spool list displays basic spool list

parameters. It does not display the list itself.
1-1-6 Display the results in Demand Management.

From the top level R/3 menu:
Logistics ? Production ? Master planning ? Demand management
Planned indep.reqmts ? Display
Enter any material and Plant 1200.
Select your demand version ##.
Compare the result with the planned quantities of your planning version 1##
using the planning type ZPROD-##..

Allocations
Contents:
? Prerequisites for product allocations
? Allocation procedures and objects
? Info structure for product allocations
? Discrete allocations
? Cumulative allocations
? SAP AG 1999

Allocations: Unit Objectives
? Outline the principles of allocation

? Maintain the allocation determination
procedure
? Explain the difference between discrete and
cumulative allocation
? SAP AG 1999

Allocations: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Info
Allocations
May
Events
Job
Mass Processing
Production Planning
? SAP AG 1999

Allocations: Business Scenario
? The quantities your company is producing are

lower than market demand. In order to prevent the
first customer from exhausting your stocks, you
define product allocations for customer groups or
customers.
? SAP AG 1999

What is Product Allocation?
? Managing demand against constrained supply
DEMAND
DEMAND SUPPLY
1/99 2/99 3/99 4/99
? SAP AG 1999
? Product allocation functionality allows you to manage the supply of scarce products to customers so that
each customer receives an allocated amount.
? You can maintain allocations for customer groups or sales organizations etc. as well as for individual
customers.
? The system can perform availability checks in conjunction with product allocation checks.
? The product allocation control process permits the user to manage allocations at a specific material level
up to various material groupings. Product allocation encompasses internal allocations to sales
organizations and channels, as well as external customer groups and specific customers.
? The system also supports the reality that there are different phases of allocation control during the
overall constraint period.

Sales Order Processing
Customer: Star Markets

Req. Delivery Date: 20.01.99
? ATP check is OK
Item 10
Bulb L-40F 100 BOX Flex. Planning
Allocation
Allocation
On time delivery
? Allocation fails
20.01.99 80 BOX Only 80 left
Complete delivery
01.02.99 100 BOX
Delivery proposal
20.01.99 80 BOX
01.02.99 20 BOX
? SAP AG 1999
? Product allocation encompasses allocations to all characteristics of the sales order, including sales
organizations and channels, external customer groups, and specific customers.
? For other charcteristics you have to use the user exit INCLUDE Fv45vfzy user exit_quota_key_va
(transaction SE38).

Definition of Product Allocation
Material
Material Procedure:
Master Rec.
Obj.1 12.98 Component
Obj.1 06.99
Procedure Obj.2 12.99
Obj.3 12.04
Work center
Allocated qty.
S140
Committed qty.
Demand
? SAP AG 1999
? To use product allocations, you must:

?Define an allocation procedure and an allocation object (allocation reason) in the Customizing activity
SD->Basic functions->Availability check and transfer of requirements->Availability check-
>Availability check against product allocation->Maintain procedure and Define object.
?Link the procedure to an info structure in the Customizing activity Availability check against product
allocation->Specif y hierarchy.
?Link your objects to a procedure in the Customizing activity Availability check against product
allocation->Control product allocation.
?Maintain the procedure in the material master records (basic data) of the materials you want to
allocate.
?Maintain planning hierarchy and updating rules for your allocation info structure.
?Switch on allocation for the relevant requirement category and schedule line category in the
Customizing activity Availability check against product allocation->Define flow according to
requirement category and Process flow for each schedule line category .

Custom Defined Allocation Structure
Allocation Obj. Info structure

Characteristics Region
Sales organization
Customer
Alloc. Object 1 Alloc. Object 2
Characteristic value specified

in the planning hierarchy
Collective characteristics North South #

maintained in the planning hierarchy
(Customers)
? SAP AG 1999
? Flexible Planning comes with the info structure S140 for product allocation. You can also create your
own info structure for product allocation.
? You create your plannin g hierarchy with the allocation objects on the highest level. Establish the
proportional factors to get allocation percentages for specific characteristic values.
? The allocation check is performed always on the detailed level of the hierarchy.
? You can specify a masking symbol for each info structure in the Customizing activity Availability check
against product allocation->Specify hierarchy . The masking symbol stands for collective
characteristics. After you create the planning hierarchy, you can add colle ctive characteristics to it by
chosing the Customizing activity Permit collective product allocation in info structures. This creates a
default entry for the specified nodes in the hierarchy.
? No deviating masking symbols are allowed for different procedures linked to the same info structure. If
an info structure has been assigned several times, assignment is permitted with or without a format
template.

Product Allocation Object Validity
JANUARY
Updating
date
Work center problems Component shortage
WEEK 1 2 3 4 5 6
? SAP AG 1999
? The system takes into account different allocation control phases during the overall constraint period.
? You can assign several allocation objects to the allocation procedure. Each object has its own validity
period. On the basis of the updating date for the key figure of the info structure, the system determines
the relevant object. The system then uses this object to determine the corresponding planning hierarchy
which contains product allocations.
? Objects are always valid from the end date of the last object. To switch off the allocation for a certain
period, define a dummy object und set it to inactive.
? The system allows only three updating dates: delivery date, material availability date, and planned goods
issue date.
? You can maintain time dependent conversion factors for your allocation objects in the Customizing
activity Control product allocation

Allocation Planning Table
Characteristics
Alloc. Object: Bulbs Sales Org: 0001

Dist. Channel: 01 Cust. Grp: 02
1 / 99 2 / 99 3 / 99
Key figures
Customer reqts. 5,000 4,000 4,000

Product allocation qty. 3,500 3,000 3,000
Reqts. not covered 1,500 1,000 1,000
Incoming orders qty. 1,200 0 0
Open product alloc. 2,300 3,000 3,000
? SAP AG 1999
? The planning type for the standard info structure S140 is COMMIT. It comes with predefined macros for
product allocation.
? Note: You must plan allocation quantities in version 000 (actual data).
© SAP AG SCM270 10-10

Discrete Allocation
750
Available Allocation: 500PC

500
*Unused 250PCs from 01/98
are not available
Allocation Qty
250
Order Qty
1/99 2/99 3/99 4/99
Current
Period
? SAP AG 1999
? There are two allocation methods in the system:

?Discrete allocation
?Cumulative allocation
? Without setting the indicator ATP consumption in the Customizing activity Maintain procedure, the
system will use the 3.0F product allocation method (discrete ATP check).
? Using this method, the system offsets the quantity confirmed in the sales document against the product
allocation quantity. It uses only the product allocation quantities from current and future periods (unused
product allocation quantities from past periods are not taken into account). When you use the discrete
method, you cannot use the following product allocation functions:
?Consumption periods
?Allocation steps
© SAP AG SCM270 10-11

Cumulative Allocation
1500
Available Allocation: 750 PC

1000
*Unused 250PCs from 01/98
are available
500
1/99 2/99 3/99 4/99
Current
Period
? SAP AG 1999
? Setting this indicator ATP consumption in the Customizing activity Maintain procedure the system uses
the cumulative allocation method. This method involves a checking logic that corresponds to ATP
cumulation logic. The system includes unused product allocation quantities from previous periods when
calculating the available product allocation quantity for the current period.
? Cumulative allocation allows you to use:
?Allocation steps: Here you can define several product allocation steps with different info structures.
?Consumption periods: Here you define a number of past and future periods to be used as the valid
consumption period.
?The number of past periods identifies the number of periods before the product allocation date in the
order that can be used for calculating unused allocations. The unused product allocation quantities of
these past periods are then cumulated before the product allocation for the current period is checked.
?The number of future periods identifies the number of periods after the product allocation date in the
order that can be used for the future allocations. If the requested quantity is not confirmed within the
future periods, it will remain unconfirmed.
© SAP AG SCM270 10-12

Allocation Window Logic
-2 month +1 month
40
40
20
60
40 40
1/99 2/99 3/99 4/99 5/99

Order 100 Car.
Car.
? SAP AG 1999
? You can use the consumption periods in the following ways:
past periods future periods Result
2 1 Above example
999 999 Unlimited product allocation (default value)
999 0 Unlimited cumula tion of unused
quantities of past periods and no
future product allocation quantities
0 999 No cumulation of unused product
allocation quantities of past periods,
unlimited future product allocation quantities
? For the cumulative method you can use different info structures to check at multiple allocation steps.
? Example:
?Step 1: Check order quantity against the customer's product allocation quantities
?Step 2: Check order quantity against plant capacity for the defined periods
© SAP AG SCM270 10-13

Allocations: Unit Summary

? Outline the principles of allocation
? Maintain the allocation determination procedure
? Explain the difference between discrete and
cumulative allocation
? SAP AG 1999
© SAP AG SCM270 10-14

Exercises
Unit: Allocations
? Maintain the allocation determination procedure
The quantities your company is producing are lower than market demand.
In order to prevent the first customer from exhausting your stocks, you
define product allocations for customer groups or customers.
In this unit, each group is assigned their own customer in Sales

Organization 1000, Distribution Channel 12.
Group Number Customer group Customer

01 02 1002
02 02 1012
03 02 1033
04 02 1174
05 02 1175
06 02 1300
07 02 1670
08 02 1671
09 02 1900
10 02 1901
11 02 2004
12 02 2140
13 02 2200
14 02 2300
15 01 2500
16 02 14000
17 02 22000
18 02 99999
© SAP AG SCM270 10-15

1-1 Check in the Material Master whether the material L-40F is allocated.
1-2 In the IMG, check whether the procedure is maintained for discrete or cumulative
allocations in Customizing.
1-3 In the IMG, check which consumption periods are maintained for info structure S140
in Customizing?
1-4 Which object is linked to the procedure and how long is it valid in Customizing?
1-5 Maintain in Flexible Planning customer requirements and allocations quantities for
your customer. Use planning type COMMIT and inactive version 000.
Set the following planning parameters:
Product allocation object: Work center

Sales Organization: 1000
Distribution Channel: 12
Customer group: Your customer group
Customer: Your customer
Plan for key figure Customer reqmts of 100 cartons and an ProdAllocQty of 50 cartons
for each of the next 6 months, and then save your plan.
© SAP AG SCM270 10-16

1-6 Create a sales order.
Logistics ? ?Sales and distribution ? ?Sales ? ?Order ? ?Create

On the selection screen, enter the following data:
Order type: OR
Division: 00
1-6-1 Enter your customer, a PO number, the material L-40F and an order quantity of
40 cartons.
1-6-2 Check the availability of the material:
Your sales order appears in the ATP view as simulated requirements. You also
see the cumulated ATP quantity on this line. The confirmed quantity will be
taken from Plant 1200, storage location 1000.
1-6-3 Return to the single- line entry overview, and change the order quantity to 200
cartons.
If you now check the availability a information window ”Production allocation
check found changes to the confirmation”. Check the product allocation
quantities and the confirmed quantities.
Accept the delivery proposal by clicking [copy] to the right of it.

Check the scheduled lines and write down the confirmed quantities and their
dates.
Save your sales order.
1-7 Change your allocations plan in Flexible Planning and check the updating of the sales
order. Use planning type COMMIT and version 000.
Customer group: Your custome r group
1-7-1 Why is synchronous updating used?
© SAP AG SCM270 10-17

© SAP AG SCM270 10-18
Solutions
Unit: Allocations
In this unit, each group is assigned their own customer in Sales

Organization 1000, Distribution Channel 12.
Group Number Customer group Customer

01 02 1002
02 02 1012
03 02 1033
04 02 1174
05 02 1175
06 02 1300
07 02 1670
08 02 1671
09 02 1900
10 02 1901
11 02 2004
12 02 2140
13 02 2200
14 02 2300
15 01 2500
16 02 14000
17 02 22000
18 02 99999
© SAP AG SCM270 10-19

1-1 Check in the Material Master whether the material L-40F is allocated.
Logistics ? ?Materials management ? Material master ? ? Material ? ? Display
? ?Display current
Enter L-40F and press Enter.
Select Basic data 1 and press Enter.
Check the entry for product allocation: Procedure BULBS
1-2 In the IMG, check whether the procedure is maintained for discrete or cumulative
allocations in Customizing.
Tools ? Business Engineer ? Customizing ? Implement. Projects ?
SAP Reference IMG
Sales and distribution ? ?Basic functions ? ?Availability check and transfer of
requirements ? ?Availability Check ? ?Availability Check Against Product Allocation
? ? Maintain procedure
The ATP consumption indicator for procedure BULBS is set, so cumulative
allocations are used.
1-3 In the IMG, check which consumption periods are maintained for info structure S140
in Customizing?
Availability Check Against Product Allocation ? ? Define consumption periods
For info structure S14, backward consumption of 3 month and forward consumption
of 10 month is maintained. Not used allocations of the past are cumulated for the
current period before product allocation is checked.
1-4 Which object is linked to the procedure and how long is it valid in Customizing?
Availability Check Against Product Allocation ? ? Control product allocation
Select procedure BULBS and press [Continue]
The object WORK CENTER is valid until the 31.12.2004.
It must also be included in the planning hierarchy of the info structure to link the
allocated materials to the planned quantities for the customers.
© SAP AG SCM270 10-20

1-5 Maintain in Flexible Planning customer requirements and allocations quantities for
your customer. Use planning type COMMIT and inactive version 000.

Plan for key figure Customer reqmts of 100 cartons and an ProdAllocQty of 50 cartons
for each of the next 6 months, and then save your plan.
Logistics ? ?Logistics Controlling ? ?Flexible planning ? ?Planning ? ?Change
Enter the planning type COMMIT (linked to info structure S140)
Enter your customer and select inactive version 000
Select the next 6 months and use the distribute function =
Save the plan.
1-6 Create a sales order.
Logistics ? ?Sales and distribution ? ?Sales ? ?Order ? ?Create

On the selection screen, enter the following data:
Order type: OR
Division: 00
1-6-1 Enter your customer, a PO number, the material L-40F and an order quantity of
40 cartons.
1-6-2 Check the availability of the material:
? ?Environment ? ?Availability
Your sales order appears in the ATP view as simulated requirements. You also
see the cumulated ATP quantity on this line. The confirmed quantity will be
taken from Plant 1200, storage location 1000.
© SAP AG SCM270 10-21

1-6-3 Return to the single- line entry overview, and change the order quantity to 200
cartons.
If you now check the availability, an information window ”Product allocation
check found changes to the confirmation” appears. Check the product allocation
quantities and the confirmed quantities.
? ?Goto ? ?Product allocation
Accept the delivery proposal by clicking [copy] to the right of it.
Check the scheduled lines and write down the confirmed quantities and their
dates.
Goto?? ?Item ? ?Schedule lines
Save your sales order.
1-7 Change your allocations plan in Flexible Planning and check the updating of the sales
order. Use planning type COMMIT and version 000.
Logistics ? ?Logistics Controlling ? ?Flexible planning ? ?Planning ? ?Change
1-7-1 Why is synchronous updating used?
For product allocations, synchronous updating is used to ensure that you can
not save the sales order without updating the info structure.
© SAP AG SCM270 10-22

Conclusion
Planning Types
Master Data
Planning
Functions
Planning Method
Info
Allocations
May
Events
Job
Mass Processing
Production Planning
? SAP AG 1999

Course Objectives
? Create sales and production plans
? Use the forecast tool

? Create planning types, macros and events
? Perform resource planning and rough-cut

capacity analysis
? Transfer planning results to the Demand
Management
? Outline the differences between Standard SOP
and Flexible Planning
? Use mass processing
? SAP AG 1999

Recommended Follow-up Activities
? Go through the exercises using IDES data

or your own data
? Read on-line documentation
? Read IMG documentation
? Read release notes
? SAP AG 1999

Logistics Planning Systems
Sales organization
Distribution channel SOP
SOP
Division Sales plans
Production plans
Plant ...
Material
SKUs/ Demand
Demand
configurable materials Statement of
Management
Management
demand
. ..
?Order and rate proposals

MPS/MRP
MPS/MRP
?BOM explosion
?Scheduling at work
centers Quantities. and dates
..
Production controlled Repetitive

Repetitive Production order SFC
SFC
by run schedule Manufacturing
Manufacturing control
headers
? SAP AG 1999

Information Flow
SD Demand Management
Sales
Sales order
order in August 1998: Planned independent requirements
Laptop
Laptop DD-415 Consumed with sales orders at SKU level
level
SIS Updating Flexible Planning (SOP)

Sales order for August 1998: Sales plan 1999
sales
sales organization
organization EAST, Event planning
planning
distribution channel WHOLESALE, Resource leveling
material LAPTOP DD-415 Planned production quantities 1999
? SAP AG 1999
? The above graphic represents the flow of information from the SD module through the Sales Information
System and Sales and Operations Planning to Demand Management.

Appendix
? This section contains supplementary material to be

used as reference
? This material is not part of the standard course
? Therefore, the instructor might not cover this during
the course presentation
? SAP AG 1999
© SAP AG SCM270 Appendix-1

Functional Enhancements
MCP20001 Read external data
MCP20002 Calculate initial macro

"
"
default macro
final macro
R/3 User
Exit
MCP20003 Apply user-defined

functions
MCP20004 Display user-defined

header info
MCP20005 Check authorizations
MCP20006 Customize header info

in EXCEL downloads
MCP20007 Choose user-defined

characteristic values (F4)
? SAP AG 1999
? You can develop your own functional enhancements for planning using a project in Customizing
(transaction CMOD). With a functional enhancement, you can add your own elements to application
logic, screens, and menus. The above functional enhancements are possible for SOP:
?To include external data in the planning table (MCP20001), you must insert a line for this purpose in a
planning type (Edit -> User exit data). External data can be data from elsewhere in the R/3 System or
from a third-party system.
?If you write a complex macro with user enhancement MCP20002, you must define this macro in a
planning type. The macro name must begin with the string 'USER'.

Additional User Exits
? MCP20011 Process data records to be updated

? MCP20012 Exclude function codes
? MCP20013 Set planning table parameters when accessing
? MCP20014 Maintain a key figure text for a charcteristic
? MCP20015 Set the field names material/plant
? MCP20017 Influence the enqueue of key figures
? MCP20018 Provide entries for a level of planning hierarchy
? SAP AG 1999
? After you have changed data in the planning table you can use MCP20011 to analyze, enhance, or
change data records before they are stored in the database e.g. to fill character key figures.
? Use MCP20012 to inactivate function codes such as ”Disaggragate line”.
? Use MCP20013 to initialize the planning table, e.g. select periods, change line status to ”output only”,
enter key figure values (e.g. prices).
? Use MCP20014 to maintain different key figure descriptions for different characteristic values.
? If the system cannot the determine material/plant for your data element for the transfer to Demand
Management, specify your field names in user exit MCP20015.
? If the Key-figure-restricted DB update is switched on (transaction MC7F) the user exit MCP20017
allows you to further reduce the number of key figures to be locked.
? Use MCP20018 to define possible entries for the maintenance of a planning hierarchy.

User Methods
? Automatic creation of a planning hierarchy

? Reduce planning records
? Reorganize actual data
? Set opening stock
? Copy between info structures
? SAP AG 1999
? You can create your own user methods in Copy Management for the above functions. Do this in
Customizing step Define user methods.
? A user method is a program or programs written by your company to perform a clearly defined, highly
specific task when certain conditions are fulfilled. For example, a method allows you to perform
complex transformations on statistical data. It consists of administrative information and an ABAP/4
FORM routine which you write yourself.

SCM270 Flexible Planning

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SCM270 Flexible Planning

Hochgeladen von

Copyright:

Verfügbare Formate

SCM270 Flexible Planning

THE BEST-RUN BUSINESSES RUN SAP

? SAP R/3 Enterprise, Extension Set 1.10

© SAP AG SCM270 Preface-1

Copyright 2003 SAP AG. All rights reserved.

All rights reserved.

© SAP AG SCM270 Preface-2

AC615 2 days AC620 2 days

© SAP AG SCM270 Preface-3

© SAP AG SCM270 Preface-4

? Project team members responsible for planning in

Notes to the user

© SAP AG SCM270 Preface-5

© SAP AG SCM270 1-1

This course will enable you to:

? Plan based on information structures

© SAP AG SCM270 1-2

On completing this course, you will be able to:

? Outline the differences between Standard SOP and

© SAP AG SCM270 1-3

Unit 1 Introduction Unit 7 Events

Unit 2 Planning Methods Unit 8 Production Planning

Unit 4 Planning Types and Macros Unit 10 Allocations

Unit 5 General Planning Functions Unit 11 Conclusion

© SAP AG SCM270 1-4

© SAP AG SCM270 1-5

? You are a member of your company‘s planning

© SAP AG SCM270 1-6

?Order and rate proposals

Production controlled Repetitive

© SAP AG SCM270 1-7

© SAP AG SCM270 1-8

Key figures Incoming orders

© SAP AG SCM270 1-9

EUROPE North America

Central North South

Paris New York Dallas

(Product groupings or materials)

© SAP AG SCM270 1-10

Flexible Planning Standard SOP

Planning hierarchies Product groups

Content and layout of

© SAP AG SCM270 1-11

? Copy Management is a tool for managing data in information structures.

© SAP AG SCM270 1-12

© SAP AG SCM270 1-13

Planned/Actual ABC Analysis

Customer 1 $30,000 $40,000 $10,000 + A B C

Dual Classification Baxter 5000

Cumulative Curve Classification

12/95 1/96 2/96 3/96 4/96 5/96 Incoming orders

© SAP AG SCM270 1-14

? SOP is the planning tool of the Logistics

© SAP AG SCM270 1-15

© SAP AG SCM270 2-1

On completing this unit, you will be able to:

? Explain the differences between the planning

© SAP AG SCM270 2-2

© SAP AG SCM270 2-3

? You are a member of your company‘s planning

© SAP AG SCM270 2-4

? SOP supports both top-down and bottom-up planning.

© SAP AG SCM270 2-5

Material AM001 is selected from planning hierarchy