Flexible Planning

Flexible Planning
LO935
0
LO935 Flexible Planning
LO935
Flexible Planning
SAP AG 2001
R/3 System
Release 4.6C
Mai 2001
Material number 50047186
0.2
Copyright
Copyright 2004 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.
SAP AG 2004
Some software products marketed by SAP AG and its distributors contain proprietary software components of
other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400,
iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are
trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or
registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web
Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other
countries all over the world. All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National product specifications
may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and
SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP
Group products and services are those that are set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as constituting an additional warranty.
0.3
Information Systems
Level 3
Level 2
LO020
LO935
5 days
Flexible Planning
Processes in
Procurement
LO150
5 days
Processes in Sales
and Distribution
LO930
2 days
Logistics Information
System (LIS)
Reporting
LO050
5 days
Manufacturing
Planning & Execution
for Discrete & Repetitive
SAP AG 1999
2 days
LO555
2 days
Technical Aspects in
LIS with Special Focus
on PURCHIS/INVCO
LO630
2 days
on SIS
LO275
2 days
on PPIS
AC615
2 days
Executive Information
System (EIS) 1 Reporting
AC620
2 days
Executive Information
System (EIS) 2 Setting up the System
CA705
2 days
Basics of the Report
Painter/Report W riter
CA710
3 days
Advanced Functions
of the Report Writer
LO940
Advanced LIS
Configuration
2 days
0.4
Prerequisites
Essential:
Knowledge of content of LO930 - Logistics Information
System (LIS) Reporting
Recommended:
LO050 - Manufacturing Planning & Execution for Discrete &
Repetitive
SAP AG 2002
0.5
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.
1
Course Overview
Contents:
Course Goals
Course Objectives
Course Content
Course Overview Diagram
Main Business Scenario
SAP AG 2002
(C) SAP AG
LO935
1.2
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 2002
(C) SAP AG
LO935
1.3
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 2002
(C) SAP AG
LO935
1.4
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 2002
(C) SAP AG
LO935
1.5
Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Stat. Forecast
Info
Structure
Allocations
Events
Job
Mass Processing
Production Planning
SAP AG 2002
(C) SAP AG
LO935
1.6
Business Scenario
You are a member of your companys planning
implementation team. You must define your info

structure, that means your planning levels
(characteristics) and key figures you want to plan.
SAP AG 2002
(C) SAP AG
LO935
1.7
Logistics Planning Systems
Sales organization
Division
Sold-to party
Material
Plant
Sales plans
Production
plans
.
SOP
SOP
..
SKUs/
configurable materials
Statement of
demand
.
Demand
Demand
Management
Management
..
Order and rate proposals

BOM explosion
Scheduling at work
centers
Quantities .and dates
MPS/MRP
MPS/MRP
..
Production controlled
by run schedule
headers
Repetitive
Repetitive
Manufacturing
Manufacturing
Production order
control
SFC
SFC
SAP AG 2002
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 that you can use to set
sales, production, and other supply chain and logistics targets. SOP uses historical, existing, and
estimated future data to perform planning calculations. You would generally use SOP for medium- to
long-term planning. You can also perform resource planning to determine the amounts of the work center
capacities and other resources required to meet these targets. SOP supports both high-level planning of
complex planning hierarchies and detailed planning of finished products, allowing for either a top-down
or a bottom-up approach to planning.
SAP based the architecture of the logistics planning system on the MRP II concept.
(C) SAP AG
LO935
1.8
Business Applications of SOP
Sales Planning
Production Planning
Purchasing
Retail
SAP AG 2002
In SOP, you can plan future sales volumes based on historical data, as well as market intelligence and
anticipated trends and changes at your company. You can also perform aggregate sales planning. With
SOP, you can keep sales plans 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.
You can also plan complex products, manufactured in a large number of variants.
In purchasing, you can use SOP to plan quotas for multiple sources of supply or to track purchasing
budgets.
In retail, you can use the SOP system to plan purchasing budgets and monitor open-to-buy.
(C) SAP AG
LO935
1.9
Info Structure Definition
Characteristics
Key figures
398
157
Period unit
Versions
Region
Sales organization
Material
Plant
Others
Incoming orders
Invoiced sales
Others
Day
Week
X Month
Fiscal year variant
Flexible time buckets
A00
A00 Active
Active
000
000 Actual
Actualdata
data
001
001 Forecast
Forecastbased
basedon
ontrend
trendmodel
model
002
Sales
incl.
market
intelligence
002 Sales incl. market intelligence
Others
Others
SAP AG 2002
Sales & Operations Planning uses the same data infrastructure as the logistics information systems (for
example, the Sales Information System). In other words, the system stores planning data, as well as
actual data in information structures.
An information structure holds three different types of information:
Characteristics are criteria that the system uses to perform data reduction, and includes items such as
sales organization, distribution channel, customer, material, and plant.
Periods are time units that give the information structures a time reference. The system displays and
stores planning data 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, for example, 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.
(C) SAP AG
LO935
1.10
Flexible Planning: Master Data
Characteristics
Info structure
EUROPE
Central
Paris
Region
Sales organization
Sales office
Material
North
America
USA
North
South
New York
Dallas
(Product groupings or materials)
SAP AG 2002
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 structure illustrated in the graphic as the sales forecast hierarchy (SFH).
(C) SAP AG
LO935
10
1.11
Flexible Planning vs. Standard SOP
Flexible Planning
Standard SOP
Multiple options for

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

the planning table is
user-defined
Standard planning table
SAP AG 2002
Sales & Operations Planning consists of two elements: flexible planning and standard SOP.
The graphic shows you the differences.
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 modify it to suit your company's needs.
(C) SAP AG
LO935
11
1.12
Use of Copy Management in Planning
Update
Rules
Copy data
from one
info structure
to another
S001
S730
Automatic
Periodic
S140
Flexible
Info structures
SAP AG 2002
You use Copy Management as 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. The primary benefit is the reduction in the operating system load that results
from the decrease in the number of info structures the system must update. (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.
(C) SAP AG
LO935
12
1.13
Standard Analyses: Reporting Techniques
Analysis of S730
Drill down
to sales
offices
Additional
Information
Sales
Incoming
organization orders
100,000
US
Invoiced
sales
90,000
Material master
Customer master
Documents
Sales organization: US
Drill
down to
customers
Sales office
Incoming
orders
Invoiced
sales
US North
US South
60,000
40,000
50,000
40,000
Sales organization: US
Sales office: US North
Customer
Incoming
orders
Jones, Inc. 25,000

Smith, Inc. 35,000
Invoiced
sales
20,000
30,000
.
.
.
SAP AG 2002
You can run a standard analysis for any planning version based on consistent planning. Select
Environment Reporting.
You can store the standard analysis as a selection version. A selection version is not the same as a
planning version.
(C) SAP AG
LO935
13
1.14
Standard Analyses: Analytical Techniques
ABC Analysis
Planned/Actual
Comparisons
Sales orders
Previous/Current Year Comparison: Invoiced

Sales
Customer Planned Actual Difference %
Customer 1 $30,000 $40,000 $10,000
33%
Customer 2 $66,000 $70,000 $ 4,000
6%
Customer 3
A B
C
Customers
Customer Sales Orders No.

No.
orders
Dual Classification
Order
value
Baxter 5000 3000

Taylor 9000 15000
Crowth 6000 9500
100
3000
750
No.
orders
Cumulative Curve
Classification
Materials (%)
Invoiced sales
Incoming orders
12/95 1/96 2/96 3/96 4/96 5/96
SAP AG 2002
You can use a wide range of functions to examine the underlying key figures and characteristic values of
an analysis from a business perspective. All the functions for statistical analyses present information in
easy-to-use graphics.
(C) SAP AG
LO935
14
1.15
Introduction: Summary
Sales & Operations Planning (SOP) is the planning
tool of the Logistics Information System.

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 2002
(C) SAP AG
LO935
15
2
Planning Methods
Contents:
Uses of the planning methods
Consistent planning
Level-by-level planning
SAP AG 2002
(C) SAP AG
LO935
2.2
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 2002
(C) SAP AG
LO935
2.3
Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Stat. Forecast
Info
Structure
Allocations
Events
Job
Mass Processing
Production Planning
SAP AG 2002
(C) SAP AG
LO935
2.4
Planning Methods: Business Scenario
You are a member of your companys planning
implementation team. You have already created the

info structure for the new SOP planning initiative.
Now you must decide which planning method will
meet your companys requirements best.
SAP AG 2002
(C) SAP AG
LO935
2.5
Planning Methods
Level-by-level
Top-down
Consistent
Bottom-up
& top-down
SAP AG 2002
Sales & Operations Planning (SOP) supports both top-down and bottom-up planning.
The different planning methods support these two approaches in different ways by. 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 the original data using
Copy Management.
(C) SAP AG
LO935
2.6
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
New Jersey
New Jersey
New Jersey
AM001
AM002
AM003
AM004
0001
0001
0001
0001
600
-
60 %
California
California
California
AM001
AM002
AM003
1001
1001
1001
400
-
40%
SAP AG 2002
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 system uses proportional factors to determine the value of the total in relation to the details.
Similarly, the system also determines the value of one detail in relation to another detail using the
proportional factors. For more information on the proportional factors, see the Master Data unit.
In the example in the graphic, the system uses proportional factors to perform disaggregation.
(C) SAP AG
LO935
2.7
Change Consistent Planning
You change incoming orders from 1000 to 2000:
1000
2000
Region
Material
Plant
Order quantity
New Jersey
New Jersey
New Jersey
New Jersey
AM001
AM002
AM003
AM004
0001
0001
0001
0001
600
100
150
50
California
California
California
AM001
AM002
AM003
1001
1001
1001
400
200
100
Region
Material
Plant
Order quantity
New Jersey
New Jersey
New Jersey
New Jersey
AM001
AM002
AM003
AM004
0001
0001
0001
0001
1200
100
150
50
California
California
California
AM001
AM002
AM003
1001
1001
1001
800
200
100
SAP AG 2002
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.
The system aggregates data dynamically when you call the planning table.
In the example in the graphic, a planner has selected material AM001 is selected. He or she is planning
the order quantities of this material in all regions and plants. The planner changes the total order quantity
from 1000 to 2000 units. The system performs disaggregation automatically based on previously planned
data.
(C) SAP AG
LO935
2.8
Consistent Planning Views
Bulbs
SAP AG 2002
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 example in the graphic shows two possible views: the central planning of all light bulbs in the US
and the decentralized planning of standard-sized light bulbs 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.
(C) SAP AG
LO935
2.9
Save Consistent Planning
Characteristcs
Key figure
65 pc
Sales organization
Distribution channel
Material
30 pc
35 pc
10 pc 20 pc 5 pc 30 pc
Order quantity visible
10 pc 20 pc 5 pc 30 pc
Order quantity stored
SAP AG 2002
In consistent planning, the system stores data at the detailed level. If you enter the planning table at
aggregate level, the system aggregates the key figure values.
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.
(C) SAP AG
LO935
2.10
Level-By-Level Planning
Master data
Original plan
Changed plan
Incoming orders quantity

Foreground
Saved
Foreground
Saved
50
40
50
50
50
40
Sales organization
Distribution channel 30
Material
20 10
20
15
100
30
5
20
0
20
10010 15
100 5
75
40
20 10 15
75
5
40
20 10 15
Planned incoming order quantities are changed from 30 pc and

20 pc to 75 pc and 40 pc at distribution channel level
SAP AG 2002
In level-by-level planning, the planning hierarchy levels are independent of each other. The system
stores data separately at each planned level.
You have a hierarchical view of the data in the planning table.
The system does not perform automatic aggregation or disaggregation. Plans at different levels are not
necessarily consistent.
In level-by-level planning, the system does not automatically fed changes you make at one level to other
levels.
It is possible to impose data consistency across several planning levels. To disaggregate data, you must
use the Edit Disaggregate line function in the planning table. The system then bases disaggregation 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.
(C) SAP AG
LO935
10
2.11
Consistent vs. Level-By-Level
Consistent Planning
Planned values saved at detailed level only.
Planned values can be saved at all levels.
Entire planning hierarchy can be planned in

one transaction (no characteristic values
selection).
At least one characteristic value must be specified.

Each level must be planned and disaggregated
individually
Planning table can be called with gaps in list

of selected characteristic values.
Planning table must be called without gaps in list of

selected characteristic values.
Planning values are visible:

(i) for the characteristic values
combination you enter
(ii) at the detailed level
(iii) at all levels in between
Planning values are visible:

(i) for the characteristic values
combination you enter
(ii) at the level below that
Identical key figures planned at total and

detailed level.
Key figures at owner and member levels can be different.
Key figures are defined in the planning type

once only.
Key figures must be defined at both owner and member

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.
Level-By-Level Planning
SAP AG 2002
Standard SOP always uses the level-by-level planning method.

Standard SOP is based on information structure S076.
(C) SAP AG
LO935
11
2.12
Comparison of the Different Planning Methods
Function
Consistent
Level-By-Level
Automatic aggregation
Automatic disaggregation
based on factors saved in
database
Yes
Yes
No
No
Automatic time-dependent
disaggregation based on
previous planning data
Yes
No
Create planning hierarchy
Yes
Yes
Planning types/macros
Set opening stock
automatically in background
Yes
Yes
Yes
Yes
Forecast
Yes
Yes
Events
Yes
Yes
Resource leveling
Yes
Yes
Background processing
Fix key figure values in the
planning table
Long texts for versions and
periods in the planning table
Yes
Yes
Yes
Yes
Yes
Standard analysis for info structure
Yes
No
Transfer to Demand Management
Yes
Yes
No
SAP AG 2002
(C) SAP AG
LO935
12
2.13
Customizing for Flexible Planning
Field catalogs:
key figures
Define planning type

Define
information
structure
Define screen
layout
Define
macros
Field catalogs:
characteristics
Planning
method
Planning
units
Key figure
parameters
SAP AG 2002
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 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:
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.
(C) SAP AG
LO935
13
2.14
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 2002
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. The following
explains two of them. 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 you are planning for
this information structure.
Key figure restricted DB update off
You can improve performance if you set this indicator. However, the system cannot save two planning
types of an information structure simultaneously because it reads all the key figures in the information
structure when it saves a planning type based on the information structure.
If you do not set this indicator, the system automatically locks and saves only those key figures
contained in one planning type. This means that two or more planning types of an information structure
can be saved at the same time.
(C) SAP AG
LO935
14
2.15
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 2002
(C) SAP AG
LO935
15
2.16Data Used in the Exercises

Data
Data in Training System
Data in IDES System
Information
Structure
S630 to S650
S630 to S650
S140
S140
Sold-to Customers
1001, 1175
1001, 1175
1002,1012,1033,1174,
1300, 1670, 1671, 1900,
1901, 2004, 2140, 2200,
2300, 2500, 14000, 99999
1002,1012,1033,1174,
1300, 1670, 1671, 1900,
1901, 2004, 2140, 2200,
2300, 2500, 14000, 99999
Sales Organization
1000
1000
Distribution
Channel
12
12
Division
00 when ordering
00 when ordering
04 when planning
04 when planning
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
Materials
(C) SAP AG
LO935
16
2.17Planning Methods 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
K (consistent)
Exchange rate type
Statistics currency
UNI
Base unit of measure
CAR (carton)
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 advises you
that each change you make will have an effect on all other clients in
the system. Press Enter to continue.
______________________________________________________
______________________________________________________
(C) SAP AG
LO935
17
2.18Planning Methods 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
Statistics currency
UNI
CAR (carton)
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 advises you
that each change you make will have an effect on all other clients in
the system. Press Enter to continue.
Tools AcceleratedSAP 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
(C) SAP AG
LO935
18
3
Master Data
Contents:
Planning hierarchy
Product group
Proportional factors
Version management
SAP AG 2002
(C) SAP AG
LO935
3.2
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 2002
(C) SAP AG
LO935
3.3
Master Data: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Stat. Forecast
Info
Structure
Allocations
Events
Job
Mass Processing
Production Planning
SAP AG 2002
(C) SAP AG
LO935
3.4
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 2002
(C) SAP AG
LO935
3.5
Characteristic Values to be Planned
Characteristics
Sales
organization
Values
USA
Europe
Paris
Dallas
Boston
Sales office
Jones, Inc.
Smith, Inc.
Customer
L - 40F
L - 60F
L - 60C
Material
L - 100F
L - 100C
SAP AG 2002
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.
(C) SAP AG
LO935
3.6
Planning Hierarchies
Characteristics
Info structure
EUROPE
Central
Paris
Region
Sales organization
Sales office
Material
USA
North
America
North
South
New York
Dallas
(Product groupings or materials)
SAP AG 2002
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, choose 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.
(C) SAP AG
LO935
3.7
Automatic Creation of a Planning Hierarchy
Characteristic value combinations

found in version 000
1997
Eur Central Paris M1
USA North NY M6
USA North NY M7
USA North NY M8
USA North NY M9
USA North NY M10
USA South Dal. M11
USA South Dal. M12
USA South Dal. M13
USA South Dal. M14
USA South Dal. M15
USA South Dal. M16
USA South Dal. M17
x
x
x
x
x
x
x
x
x
x
x
x
x
1998
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Data is filtered
using method
SAP AG 2002
You can create a planning hierarchy automatically based on actual data (version 000) or existing planned
data (versions A00-999).
To create a planning hierarchy automatically based on actual data, choose Master data Generate
master data.
It is often not necessary, or even desirable, to plan all products sold to all customers, including materials
rarely sold. SAP offers you two ways to filter out characteristic value combinations (that is, 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 met. 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 the system would find in the specified time frame and therefore helps
you decide how best to create the planning hierarchy.
(C) SAP AG
LO935
3.8
Proportional Factors for Consistent Planning
Info structure S624

Europe
40%
60%
100%
30%
L-40F
12%
USA
50%
50%
Paris
Dallas
Boston
100%
100%
100%
Smith, Inc.
Jones, Inc.
Baker, Inc.
20%
L-60F
8%
50%
70%
30%
20%
80%
L-100F
L-40F
L-60F
L-60F
L-100F
20%
21%
9%
6%
24%
SAP AG 2002
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.
You can calculate constant proportional factors for consistent planning one of two ways:
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, choose 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, choose 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, the system bases subsequent disaggregation 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 choose Edit
Disaggregate line.
(C) SAP AG
LO935
3.9
Proportional Factors for Level-By-Level Planning
Info structure S625

Europe
40%
60%
100%
30%
L-40F
USA
50%
50%
Paris
Dallas
Boston
100%
100%
100%
Smith, Inc.
Jones, Inc.
Baker, Inc.
20%
L-60F
50%
70%
L-100F
L-40F
30%
L-60F
20%
L-60F
80%
L-100F
SAP AG 2002
Using proportional factors, you describe the dependencies 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. The planning method determines whether or not this happens
automatically (see the Planning Methods Unit).
In level-by-level planning, the system performs disaggregation based on the proportional factors
between adjacent planning levels. This applies both to Standard SOP and to information structures in
Flexible Planning for which you have defined level-by-level planning.
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 level-by-level planning automatically, you have two choices:
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
(C) SAP AG
LO935
3.10
Product Group Hierarchy
Lightbulbs
Plant 9999
Line "clear"
Line "frosted"
Plant 0001
40 watt
Plant 0001
60 watt
Plant 0001
Plant 0002
40 watt
Plant 0002
60 watt
Plant 0002
100 watt
Plant 0002
SAP AG 2002
You create the master data for standard SOP by maintaining one or more product groups.
A product group can consist of either additional 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.
You can perform cross-plant planning.
You can perform planning out at the 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.
(C) SAP AG
LO935
10
3.11
Version Management
Info
Structure
A00
Active Version
001
Simulation 1
002
Simulation 2
000
Actual Data
Copy
Demand Mgt.
Updating
SAP AG 2002
(C) SAP AG
LO935
11
3.12
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 2002
(C) SAP AG
LO935
12
3.13Master Data 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 format. Create a planning hierarchy for
your info structure that supports the data on the following sheet:
Sales Organization 1000 Germany Frankfurt

Customer 1000 Becker Berlin
Division 04 Lighting,
Plant 1200
Material
L-80F 80 Watt Frosted Light bulbs

Month+1
Month+2
Month+3
Month+4
Month+5
Last Years Invoiced Sales
10000
11000
12000
13000
14000
Last Years Invoiced Qty
1000
1100
1200
1300
1400
Sales Forecast Qty
Material
L-40C 40 Watt Clear Light bulbs
Month+1
Month+2
Month+3
Month+4
Month+5
5000
6000
7000
8000
9000
500
600
700
800
900
Sales Forecast Qty
(C) SAP AG
LO935
13

Customer 1175 Elektromarkt Bamby
Plant 1200
Material

Month+1
Month+2
Month+3
Month+4
Month+5
10000
11000
12000
13000
14000
1000
1100
1200
1300
1400
Sales Forecast Qty
Material
Month+1
Month+2
Month+3
Month+4
Month+5
5000
6000
7000
8000
9000
500
600
700
800
900
Sales Forecast Qty
Material
Month+1
Month+2
Month+3
Month+4
Month+5
2500
3000
3500
4000
4500
250
300
350
400
450
Sales Forecast Qty
1-1-1 Based on this input sheet, what are the planning levels you will enter into your
planning hierarchy?
0.2.13
0.2.10
0.2.2
0.2.7
0.2.14
0.2.11
1
0.2.3
0.2.8
0.2.27
0.2.24
0.2.16
0.2.21
0.2.28
0.2.25
0.2.17
0.2.22
(C) SAP AG
LO935
0.2.5
0.2.19
14
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, select All maintnce to
bypass this message.
Dont 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 current 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
(C) SAP AG
What is the difference between your manual entries and the automatically
created entries?
LO935
15
_________________________________________________________
_________________________________________________________
_________________________________________________________
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 zero calculated for sold-to partner 1000?
_________________________________________________________
_________________________________________________________
(C) SAP AG
LO935
16
3.14Master Data 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
Material

Month+1
Month+2
Month+3
Month+4
Month+5
10000
11000
12000
13000
14000
1000
1100
1200
1300
1400
Sales Forecast Qty
Material
Month+1
Month+2
Month+3
Month+4
Month+5
5000
6000
7000
8000
9000
500
600
700
800
900
Sales Forecast Qty

Customer 1175 Elektromarkt Bamby
Plant 1200
Material

Month+1
Month+2
Month+3
Month+4
Month+5
10000
11000
12000
13000
14000
1000
1100
1200
1300
1400
Sales Forecast Qty
Material
Month+1
Month+2
Month+3
Month+4
Month+5
5000
6000
7000
8000
9000
500
600
700
800
900
Sales Forecast Qty
Material
Month+1
Month+2
Month+3
Month+4
Month+5
2500
3000
3500
4000
4500
(C) SAP AG
LO935
17

Sales Forecast Qty
250
300
350
400
450
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
1000
Sold-to Party
1175
Material
Material
Material
Material
Material
L-80F
L-40C
L-60C
L-80F
L-40C
Plant
1200
1-1-2
Plant
1200
Plant
1200
Plant
1200
Plant
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, select All maintnce to
bypass this message.
Dont 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.
(C) SAP AG
LO935
18
Logistics Logistics controlling Flexible planning Master data

Planning hierarchy Create
Enter your info structure S630 + ##. Click the green check button twice.
On the Create Planning Hierarchy screen, enter sales organization 1000.
Choose [Next level]. Enter division 04.
Choose [Next level]. Enter Sold-to 1000 and 1175.
Choose [Next level].
Continue entering data using the input sheet above. When you are
finished, choose [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-##, choose 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 current 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
(C) SAP AG
LO935
19
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, choose [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.
Choose [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
(C) SAP AG
LO935
20
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 zero calculated for sold-to partner 1000?
Because there are no actual data for sold-to partner 1000
(C) SAP AG
LO935
21
4
Planning Types and Macros
Contents:
Planning types
Include actual data
Performance enhancements
Drill down functionality
Variable time buckets
Macros
SAP AG 2002
(C) SAP AG
LO935
4.2
Planning Types and Macros: Objectives

Create your own planning type
Outline the use of planning type info
Create your own macros
Explain different ways to execute macros
SAP AG 2002
(C) SAP AG
LO935
4.3
Planning Types and Macros: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Stat. Forecast
Info
Structure
Allocations
Events
Job
Mass Processing
Production Planning
SAP AG 2002
(C) SAP AG
LO935
4.4
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 2002
(C) SAP AG
LO935
4.5
Planning Types
Planning type: SALES
Info
Structure
Version
A00
Incoming orders qty.

Incoming orders
Invoiced quantity
Invoiced sales
Production qty.
Stock level
Target stock level
Days supply
Target days supply
Version
001
Incoming ord. qty.

Incoming orders
Invoiced quantity
Invoiced sales
Planning type: PRODUCTION
Sales
Production qty.
Stock level
Target stock level
SAP AG 2002
In Flexible planning, you can create your own customized planning screens, referred to as planning
types.
A planning type is a self-defined view on the planning data in an information structure. You can create as
many planning types as you need for an information structure.
To create a planning type, choose 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.
(C) SAP AG
LO935
4.6
Create a Planning Type 1
The
Theplanning
planningtype
type
determines
determinesthe
thehorizon
horizon
and
the
time
grid
and the time gridof
of
planning
planning
Planning
Table:
Include
Includeactual
actualdata
data
from
Version
from Version000
000
in
inthe
theplanning
planningtable
table
You
Youcan
cancreate
createmacros
macros
in
the
planning
type
in the planning type
to
tocalculate
calculatekey
keyfigures
figures
The
Theplanning
planningtype
type
determines
determineswhich
which
key
keyfigures
figuresare
aredisplayed
displayed
in
the
planning
in the planningtable
table
SAP AG 2002
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 the system can perform 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 unlimited possibilities with
regard to the information you can plan.
The actions you perform to create a planning type are:
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
(C) SAP AG
LO935
4.7
Create a Planning Type 2
Define:
Define:
drilling
drillingdown
down
performance
performance
extended
extendedselection
selection
screen
screen
Planning type
Info structure
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 2002
The aggregate planning indicator in the planning type info enables:

Drilldown in the planning table
Variable time buckets
Saving of fixed values
Performance enhancements
If you set the indicator, the system aggregates the key figure values by the database server, and transfers
only the totals to the application server. If you do not set this indicator, the system transfers the details to
the application server, which aggregates them. The system automatically sets the indicators for planning
types that you created in Release 3.0 or 3.1 when you upgrade.
(C) SAP AG
LO935
4.8
Defining a Planning Table
Select key figures
from info structure
- Order value
- Consistent
- Level-by-level
- Delta
- Confirmed quantity
- Open order quantity
Planning table
- Open order value

- Delivery quantity
- Sales
Planning
type
Orig. sales
Event
Corr. sales
Deviation in %
Macro
Event/orig. sales * 100
= Deviation in %
+ -
/ etc.
Define additional
lines
- Event
- Corrected sales
- Actual data
from previous year
SAP AG 2002
A planning type typically contains a subset of the key figures in the underlying information structure.
You can also define additional lines whose contents the system obtains, 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 so that the system automatically
executes it 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 the system reads into the external data line, you must use the MCP20001 functional
enhancement in a Customizing project (transaction CMOD).
You set attributes for each line in a planning type.
(C) SAP AG
LO935
4.9
Aggregation and Disaggregation:
Determine by Aggregation Type
Define Info Structure

Planning
method
Define Planning Type
Planning
units
Define screen
layout
Define
macros
Key figure
parameters
Set
aggregation type
SAP AG 2002
The aggregation type of a key figure specifies how the system aggregates and disaggregates that key
figure. You set the aggregation type in Customizing (either in Set planning parameters for info structures
and key figures or in Maintain planning types).
The three aggregation types are:
The system calculates an average
The system calculates a total; the system performs disaggregation based on the proportional factors
The system does not perform any aggregation
Total calculated is the default aggregation type for planned key figures. The default aggregation type for
a freely defined line is no aggregation. For more information, see the IMG.
(C) SAP AG
LO935
4.10
Standard Planning Types
SOPKAPA
SOPKAPAM
SOPDIS
SAP AG 2002
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.
(C) SAP AG
LO935
10
4.11
Aggregate Planning
Improved performance
Aggregated
Database
server
Application
server
Detailed
SAP AG 2002
Aggregate planning indicator

You set this indicator in the planning type by selecting Maintain planning types in Customizing. The
database server aggregates key figures in this planning type, and it transports only these totals to the
application server. If you do not set this indicator, the database server transports details to the application
server, which then aggregates them. The system automatically sets the indicators for planning types that
you created in Release 3.0 or 3.1 when you upgrade.
This indicator enables the following:
Improved performance
Flexible time buckets
Permanent fixing
(C) SAP AG
LO935
11
4.12
Variable Time Buckets
3.0
4.0
Database ... W17
W18
W19 ...
Display
W18
W19 ...
... W17
Database ... W17 W18.4 W18.5 W19 ...

Display
or
... W17
...
W18
04/97
W19 ...
05/97
Data entry in different time buckets possible

Aggregation and disaggregation based on predefined time
bucket grid
SAP AG 2002
You can plan using more than one period indicator. For these indicators, you let the system generate a
technical period that it saves as a fiscal year variant. You must set the planning method of the
information structure to 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.
The system automatically generates a technical fiscal year variant. 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.
(C) SAP AG
LO935
12
4.13
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 2002
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.
(C) SAP AG
LO935
13
4.14
Standard Macro Operations
Operand 1
(mandatory)
Operator
+
Operand 2
(optional)
Result
*
Key figure
/
>
Key figure
or
numerical
value
Key figure
<
=
Key figure
=V
Key figure
Key figure
owner
DM
Key figure
member
Key figure
member
AM
Key figure
owner
SAP AG 2002
You record or create a macro with the aid of predefined operators.

In level-by-level planning, you must define the level at which the system executes a macro either the
owner or member level.
(C) SAP AG
LO935
14
4.15
Automatic Macro Execution
Event
Macro
Read
data
INITIAL
Enter
Read data
Save data
DEFAULT
Save
data
FINAL
Time
SAP AG 2002
You can specify that the system is to execute a macro automatically for a particular planning type. The
three ways to execute a macro automatically are:
The system runs the initial macro whenever you call up the planning table.
The system runs the default macro whenever you regenerate the planning table, (for example, when
you press Enter), or when you call up or save the planning table. This can result in the macro running
several times.
The system runs the final macro immediately before saving the data.
To define a macro for automatic execution, choose Goto Planning type info from the planning type
menu.
Alternatively or in addition, you can write macros that you can execute manually at any time in the
planning table (with Edit Macro).
(C) SAP AG
LO935
15
4.16
Planning Types and Macros: Summary

Outline the use of planning type info
Generate your own macros
Explain different ways to execute macros
SAP AG 2002
(C) SAP AG
LO935
16
4.17Planning Types and Macros 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 years 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 years historical values are populated. The sales force must fill in
this years sales quantity forecast.
Sales Organization 1000 Germany

Customer 1001 Lampen-Markt GmbH
Month 1
Sales Forecast Qty
Actual Invoiced Qty
Actual Invoiced Sales
Division 04 Lighting
MaterialL-80F 80 Watt Frosted Light bulbs
Month 2
Month 3
Month 4
Month 5
1000
1100
1200
1300
1400
10000
11000
12000
13000
14000
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:
(C) SAP AG
LO935
17
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 years and previous years actual invoiced quantity, allowing
the sales reps to compare against the forecast as you go forward in time.
Include this years and last years actual invoiced sales values.
Note: You must include the line Invoiced Sales in the planning type 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 a dialog box to enter a transport and

correction request. Follow these steps:
1. Select Create request.
2. Enter a description. Include your groups number in the text.
3. Save.
A task number will be assigned automatically. You can use this number in
subsequent exercises.
1-2
Using your new planning type, go to interactive planning without entering

characteristics 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?
_____________________________________________________________
_____________________________________________________________
(C) SAP AG
LO935
18
1-2-4 Using this new planning type, which month is the earliest you can manipulate
the forecast values?
_____________________________________________________________
(C) SAP AG
LO935
19
Exercises
Topic: Macros
Create macros within your planning types
Management would like to see how sales are progressing relative to last
years 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 years
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 lower-left corner of the steps for
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.
____________________________________________________________
____________________________________________________________
____________________________________________________________
____________________________________________________________
(C) SAP AG
LO935
20
____________________________________________________________
____________________________________________________________
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 select 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.2.3
*2-3
Save your version.
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?
____________________________________________________________
(C) SAP AG
LO935
21
4.18Planning types and Macros 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 years historical values are populated. The sales force must fill in
this years 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
1000
1100
1200
1300
1400
10000
11000
12000
13000
14000
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
(C) SAP AG
LO935
22
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 Qty, 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 years and previous years actual invoiced quantity, allowing
the sales reps to compare against the forecast as you go forward in time.
To add this years and previous years 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 years and last years actual invoiced sales values.
Note: You must include the line Invoiced Sales in the planning type 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 years and the previous years 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.
(C) SAP AG
Save your new planning type.
LO935
23
Note: You will be prompted by a dialog box to enter a transport and

correction request. Follow these steps:
4. Select Create request.
5. Enter a description. Include your groups number in the text.
6. Save.
A task number will be assigned automatically. You can use this number in
subsequent exercises.
1-2
Using your new planning type, go to interactive planning without entering

characteristics 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
Aggregate information
Un
Sales Forecast Qty
CA
R
PrvYrAct Invoiced qty
Version 001
Inactive
M 05.1998
M 06.1998
M 07.1998
M 08.1998
M 09.1998
M 10.1998
1068
2750
2090
2168
2274
3996
805164
2063472
1559754
1623144
1702468
8835844
Actual Invoiced Qty

PrvYrAct Invoiced Sales
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?
(C) SAP AG
LO935
24
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.
1-2-5 Save your version.
(C) SAP AG
LO935
25

Topic: Macros
2-1
Create a macro for planning type ZSALES-## comparing current sales to this years
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
The system provides prompts in the lower-left corner of the steps for
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 Forecast Qty
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.
(C) SAP AG
LO935
26
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-2-3 Save your version.
*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
(C) SAP AG
LO935
27
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 FORECAST QTY * 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 Forecast Qty
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
(C) SAP AG
LO935
28
On the first line (which should be blank):

5. First Operand: Sales Forecast Qty
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.
(C) SAP AG
LO935
29
5
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 2002
(C) SAP AG
LO935
5.2
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 2002
(C) SAP AG
LO935
5.3
Gerneral Planning Functions: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Stat. Forecast
Info
Structure
Allocations
Events
Job
Mass Processing
Production Planning
SAP AG 2002
(C) SAP AG
LO935
5.4
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 2002
(C) SAP AG
LO935
5.5
Planning Table
Planning
Charact.
Edit
Create Plan: Consistent Planning

Extras System Help
Goto
Distribute ...
Region
Plant
Version
Key figure
USA
3
001
Disaggregate line
Sales organization
Material
0 column ...
On
South
Header area:
shows which master
data you are planning
and which version
Version 001
New, inactive
Aggregated information
Un M 01.1999 M 02.1999 M 03.1999 M 04.1999 M 05.1999 M 06.1999

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

The header area shows the master data you are planning and the version.
The input matrix is laid out in rows and columns. The left column shows the key figures being planned;
if desired, you can switch to a display that shows the characteristic values being planned (Views Key
figure format). The right column shows the units of the key figures.
You can enter data in any of the following ways:
Manually
Using distribution operators (+, -, *, /)
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. The system sets
this indicator 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.
(C) SAP AG
LO935
5.6
Drill Down in Interactive Planning
North
America
USA
North
South
Atlanta
Dallas
SAP AG 2002
Drilling Down in Consistent Planning

You can drill down level by level in the planning table of consistent planning. To do so, you must have
set the Aggr. planning indicator in the planning type. The system sets this indicator automatically for any
planning types that you created in Release 3.0 or 3.1.
(C) SAP AG
LO935
5.7
Views in the Planning Table
All key figures view
Total view:
All key figures at
entry level
Incoming ord. qty.

Incoming orders
Detailed view:
All key figures at
member level
Invoiced quantity
Invoiced sales
Key figure invoiced sales
Key figure view:

One key figure at sum
and member level
Sum of members
Sold-to party 1
Sold-to party 2
Sold-to party 3
SAP AG 2002
Without the indicator aggregate planning in the planning type info, you can choose:
Goto Total
This takes you to the aggregate view on your data. If you are using the consistent planning method,
you see the total key figure values for all selected characteristic value combinations. If you are using
the level-by-level planning method, you see the total key figure values at owner level.
Views Member
This takes you to the detailed view on your data. If you are using the consistent planning method, you
see the key figure values at the most detailed level of the characteristic values combination. This is
often the material level. If you are using the level-by-level planning method, you see the key figure
values at member level.
Views Key figure format
When you place your cursor on a key figure and choose 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 figures 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.
(C) SAP AG
LO935
5.8
Basic Functions of the Planning Table
Places after decimal point
Distribution functions
Operator
OP Description
6. 123
Replace time series values with the value
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 2002
You can set the number of decimal places of any key figure and characteristic value. Either the Global
Settings made in Customizing for that unit or the number of places shown in the planning table at the
time of saving determines the number of decimal places the system saves.
You can distribute a value across a selected time series using an operator.
The zero column has no particular period unit. Opening stock levels appear here. You can enter other
opening values in this column. The zero column is used only if you dont have historical data in your
planning type (like in Standard SOP), if you did not select any historical periods 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.
(C) SAP AG
LO935
5.9
Permanent Fixing of Values
Total incoming orders quantity:

20,000 pc
3,000
(15%)
3,000
(15%)
Total incoming orders quantity changed to:

30,000 pc
5,000
(25%)
3,000
(10%)
3,000
(10%)
9,545
(32%)
3,000
(10%)
3,000
(15%)
6,000
(30%)
11,454
(38%)
Fixing
Fixingatataggregate
aggregatelevel
levelalso
also
causes
fixing
at
detailed
causes fixing at detailedlevel
level
SAP AG 2002
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. The system automatically sets this indicator for any information structures that you created
in Release 3.0 or 3.1; 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. When the system generates the info structure, it automatically creates a new
key figure on the database to store fixed values. (See the definition of the database table using
transaction SE16). The system does not set this indicator for key figures in information structures that
you created in Release 3.0 or 3.1; manual action is necessary on your part.
You set the Aggr. planning indicator in the planning type. The system fixes key figures values in the
database when you fix them in the planning table when you save the planning version. The systems
automatically sets this indicator for any planning types that you created in Release 3.0 or 3.1; 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.
(C) SAP AG
LO935
5.10
Units of Measure
Customizing of Info Structure
Master Data (material master record)
Base units of measure
Planning Table
Planning unit
Toggle
Hierarchy unit
SAP AG 2002
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.
(C) SAP AG
LO935
10
5.11
Planning Units
Currency unit
USD
DEM
CAD
Planning
units
Unit of measure
PC
BOX
Period unit
TO
SAP AG 2002
You enter an exchange rate type with the currency unit. This allows 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 you did not define a storage period in level-by-level planning, you can change the period unit for part
of or all of the planning horizon in the planning table.
In consistent planning, you can select a 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).
(C) SAP AG
LO935
11
5.12
Copying Key Figures from One Info Structure to
Another
Consistent
Consistent
Consistent
Level-by-level
SAP AG 2002
You can copy key figure values from one information structure to another. These can be either monetary
values or quantities.
The three standard copying methods are:
From consistent planning to consistent planning
From consistent planning to level-by-level planning
If you need a different combination of planning methods, you must write your own user method in
Customizing.
(C) SAP AG
LO935
12
5.13
Copying Key Figures: Warehouse Split
Info structure
Version
From
S730
003
Planning data is created in

information structure
01/01/1997
12/ 31/1997
TO
Key figure
Invoiced sales quantity
..
.
..
.
0003
Sales organization
0002
Sales organization
Sales organization
Sales office
Customer
Material
Individual plans are

aggregated
0001
01
1001
Total sales of
material
L-60F
Warehouse split
Key figure is selected
Sales:
Plant 1200
A
Material
Sales:
Plant 3200
SAP AG 2002
The system considers the warehouse split if you copy from an info structure without a plant to an info
structure with a plant in the hierarchy.
If you perform this action at the product group level, the system automatically aggregates the material
data.
In Standard SOP, you can then plan the production quotas of different plants.
The system treats each combination of material and plant (SKU) as a separate planning object in
standard SOP. When the system copies data from Flexible Planning to Standard SOP, it must distribute
the material data across all the plants in which you have planned the material. 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.
(C) SAP AG
LO935
13
5.14
General Planning Functions: Summary

Use the planning functions
Use Aggregate Planning
Copy data between info structures
SAP AG 2002
(C) SAP AG
LO935
14
5.15General Planning Functions Exercises

Unit: General Planning Functions
Topic: Planning Table

Know how to use the planning functions
As a sales planner, you plan to sell 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 groups 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
(C) SAP AG
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?
LO935
15
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
(C) SAP AG
Save your plan.
LO935
16
5.16General Planning Functions Solutions

Unit: General Planning Functions
Topic: Planning Table
1-1
Change your sales plan version 001 using your groups 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. If your info structure used level-by-level
planning instead of consistent planning, you would be required to enter sales
organization 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 click the [Distribute] button)
2. Check the planning horizon to confirm the correct months have been
selected.
Enter 30000 into the Sales Forecast Qty key figure.

Select = = in the Op field (Operator) to distribute the value over the period and replace old
values
5. Press [Enter].
Deselect the columns using Edit select Deselect periods.
1-1-4 Create a column for line totals. Select all columns to be totaled.
Settings Show row totals All columns
1-1-5 How do you get rid of the line total column?
Settings Show row totals Hide
(C) SAP AG
LO935
17
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 drilldown 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 makes the value
unfixed.
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.
(C) SAP AG
LO935
18
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 Choose 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
(C) SAP AG
Save your plan.
LO935
19
6
Statistical Forecast
Contents:
Forecast models
Forecast profiles
Forecast versions
Outlier control
Workdays correction
SAP AG 2002
(C) SAP AG
LO935
6.2
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 2002
(C) SAP AG
LO935
6.3
Statistical Forecast: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Stat. Forecast
Info
Structure
Allocations
Events
Job
Mass Processing
Production Planning
SAP AG 2002
(C) SAP AG
LO935
6.4
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 2002
(C) SAP AG
LO935
6.5
Forecast
Consumption
Consumption
Actual
Actual data
data
Analysis of historical data

enables prediction of
future patterns
Use of robust, proven forecast
models
Forecast
Forecast
Prediction
Prediction
exponential smoothing
moving averages
Automatic model selection is

possible
Graphical monitoring and
manipulation of both historical data
and forecast results.
Used
Used as
as planning
planning figures
figures
SAP AG 2002
You use forecasting in SOP 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. The system stores actual data in the information structure, version 000.
Consumption data includes all kinds of goods issues including goods written off as scrap. The system
stores the consumption data of a material 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.
The system always bases any statistical forecast in Consistent planning on the actual data of version 000.
You can either make the forecasted values your plan or modify them.
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 material (for example, because it is new), you can still run
the forecast for this material 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. The system supports this function for level-by-level planning.
(C) SAP AG
LO935
6.6
Forecast Profiles: Concept
Model selection
Forecast model
explicit model
constant
explicit model with

additional test
trend
best fit selection
Parameters
- forecast basis
(consumption/sales)
- seasonal length
season
seasonal trend
- smoothing parameters
- 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 2002
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:
You save time if you use the same settings repeatedly.
You can use forecast profiles 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 are 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%
(C) SAP AG
LO935
4th historical value: 6.25% and so on.
(C) SAP AG
LO935
6.7
Forecast Profiles: Example
Forecast Results Based on
Constant Model
Qty.
Regular
lightbulbs
Profile 1: assume
constant model
time
Forecast Results Based on

Seasonal Model
Christmas
lights
Profile 2: assume
seasonal model
Christmas
SAP AG 2002
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
(C) SAP AG
LO935
6.8
Automatic Aggregation of Historical Data
Product Division
'Clear Lightbulbs'
300 Boxes
60 Watt
Clear
40 Watt
Clear
100 Boxes
200 Boxes
SAP AG 2002
If you carry out the forecast at a high level, the system automatically aggregates historical data.
For this reason, the results of the forecast will be different if the you run the forecast at a high level and
the system disaggregates the results 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
forecasting in the variant.
(C) SAP AG
LO935
6.9
Forecast Versions
Forecast results
Historical data
Forecast
database
Planning table
M 10.1999 M 11.1999 M 12.1999
Sales
1100000
1100000
Sales qty 2000
1000000
2200
2200
Price
500
500
500
SAP AG 2002
Forecast versions are a fast way to simulate different forecast results for the same planning version.
When you save the planning table, the system stores all forecast versions in the forecast database.
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, the system saves forecast versions at the level you created them.
In consistent planning, the system saves forecast versions for the current planning object. If you base
your actual planning 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 currently displayed 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.
(C) SAP AG
LO935
10
6.10
Interactive Business Graphic
Forecast Results
Click and Drag
Corrected 80
sales in $ 70
60
50
40
30
20
10
0
1st
Qtr
2nd
Qtr
3rd
Qtr
4th
Qtr
SAP AG 2002
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.
(C) SAP AG
LO935
11
6.11
Automatic Outlier Control
8
7
6
Background correction
Manual identification and average calculation
5
4
Tolerance lane
= ep *1.25* MAD
3
2
ep = ex-post forecast
1
0
today
SAP AG 2002
Automatic background correction of outliers in historical data:

To correct outliers automatically in the historical data on which the system based the forecast, choose
Outliers in the forecast profile and enter a sigma value between 0.6 and 2.0. The system calculates a
tolerance lane for the historical time series, based on the sigma factor. The system corrects historical data
that lies outside the upper or lower band of this tolerance lane to the ex post forecast value.
The sigma factor defines the width of the tolerance lane for outlier control . 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 the system 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, choose 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.
(C) SAP AG
LO935
12
6.12
Workdays Correction
History
M1
M2
M3
1900
2100
2300
Days
19
21
23
Corr.
2000
2000
2000
Original
Forecast
Uncorr.
Days
Original
M4
M5
M6
2000
2000
2000
22
20
18
2200
2000
1800
Average month defined as 20 workdays

(forecast profile)
SAP AG 2002
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 period field of the forecast profile. The system then
corrects the forecast data based on the actual number of workdays in the period. The factory calendar
defines the actual number of workdays in the period.
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 selecting Set parameters of info structures and key
figures. You enter the forecast period in the Period ind. field of the forecast profile
(C) SAP AG
LO935
13
6.13
Statistical Forecast: Unit Summary

Carry out a forecast
Base the forecast on the number of workdays in
a period
SAP AG 2002
(C) SAP AG
LO935
14
6.14Statistical Forecast 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 on-line help for the Correct Outlier Indicator
on the Forecast: Historical Values screen.
__________________________________________________________
__________________________________________________________
__________________________________________________________
(C) SAP AG
LO935
15
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 evaluate your forecast version.
The forecast version contains all historical date, all parameters you have used
for the last forecast and the last result.
(C) SAP AG
LO935
16
6.15Statistical Forecast 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.
1. Planning Change
2. Enter your groups planning type ZSSALES-##.
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
(C) SAP AG
LO935
17
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 on-line 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 evaluate your forecast version.
The forecast version contains all historical date, all parameters you have used
for the last forecast and the last result.
1. Planning Change
2. Enter your groups planning type ZSALES-##.
3. Enter sales organization 1000, division 04.
4. Select the active version.
(C) SAP AG
LO935
18
5. Place your cursor on the Sales Forecast Qty field in the planning table.
6. Edit Forecast. Click the Version button.
(C) SAP AG
LO935
19
7
Events
Contents:
Defining an event
Assigning an event
Displaying an event
SAP AG 2002
(C) SAP AG
LO935
7.2
Events: Unit Objectives

Outline the role of events in SOP
Create and use events
Analyze the result in the planning table
SAP AG 2002
(C) SAP AG
LO935
7.3
Events: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Stat. Forecast
Info
Structure
Allocations
Events
Job
Mass Processing
Production Planning
SAP AG 2002
(C) SAP AG
LO935
7.4
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 next month (your second
planned month).
SAP AG 2002
(C) SAP AG
LO935
7.5
Events
Start of event
%
Corrected Planned Sales
100 %
Original Planned Sales
W
W
07/97 08/97
W
11/97
Period
W1
W2
W3
W4
W5
Normal planned sales
100
100
100
100
100
Proportional event
Time
+10% +20% +10% -5%
Corrected planned sales 110
W
W
09/97 10/97
120
110
95
100
SAP AG 2002
Events allow you to predict the impact of one-time events that you cannot deduce from historical data.
Examples of events include:
Price changes such as promotions
Special deals with major customers and vendors
Competitor sales activities
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). The graphic shows a percentage (proportional event).
The impact of the event appears in the corrected key figure values of the planning table.
(C) SAP AG
LO935
7.6
Events: Assignment to Information Objects
Event list
Info structure
Assignment
Characteristics
Easter promotion
Mid-season sales
.
.
Special contracts
Key figure
Planning
versions
Start date
1999
Material 1
.
.
Material 5
Material 5
.
.
Material 20
SAP AG 2002
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 (for example, sales organization and sales district)
Key figure (for example, invoiced sales value)
Planning version
This information determines how the event appears in the planning table.
The period unit of the event must be either the planning period of the information structure or one of the
periods in the time buckets grid. If the event period is different from the period unit in which the
planning taxable appears, the system automatically distributes the event value to the correct period.
(C) SAP AG
LO935
7.7
Events: Display in the Planning Table
Planning type
Planning type
Info structure
Insert event
lines
Invoiced sales
Actual sales
Cumulative Event
Proport. Event
Correct. sales
SAP AG 2002
To view an event in the planning table, you must first assign it to a planning type and then plan that
planning type.
The system disaggregates cumulative event data to the detailed level using the constant proportional
factors, not current planning data.
Proportional events appear at the detailed level only.
The system calculates and displays data on event lines automatically in the planning table at run time. It
does not save it to database when you save the planning version.
(C) SAP AG
LO935
7.8
Events: Unit Summary

Create and use events
Analyze the result in the planning table
SAP AG 2002
(C) SAP AG
LO935
7.9Events 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. Marketing estimates 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:
It is 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 quantity is
calculated only when you save your plan. Only changed quantities
are calculated.
(C) SAP AG
LO935
7.10Events Solutions
Unit: Events
Topic: Defining, Assigning, and Displaying Events
1-1
Create an event PROMOTION## based on the business scenario described in the

exercise. You will use the following parameters:
It is 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##. Click 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 Enter.
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.
Choose '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 ZSALES-##
Place the cursor on sales forecast qty and select [event].
Select key figure sales and press Enter.
Save your planning type.
(C) SAP AG
LO935
10
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 ZSALES-##
Enter sales organization 1000, division 04 and select the active 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
calculated only when you save your plan. Only changed quantities
are calculated.
(C) SAP AG
LO935
11
8
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
(C) SAP AG
LO935
8.2
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
(C) SAP AG
LO935
8.3
Production Planning: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Stat. Forecast
Info
Structure
Allocations
Events
Job
Mass Processing
Production Planning
SAP AG 1999
(C) SAP AG
LO935
8.4
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
(C) SAP AG
LO935
8.5
Production Macros in Standard SOP
Synchronous to sales
Sales
Production
W29/99
W30/99
M08/99
M09/99
50
50
70
70
220
220
250
250
W29/99
W30/99
M08/99
M09/99
50
60
10
70
70
10
220
250
40
250
250
40
W29/99
W30/99
M08/99
M09/99
70
40
0
220
330
11
250
265
11
Target stock level

Sales
Production
Target stock level
Target days' supply
Sales
50
Production
80
Target days' supply 3
SAP AG 2002
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.
The system calculates and displays stock levels and days' supplies automatically when you regenerate
the planning screen.
The system accounts for opening stock levels.
To set opening stock levels manually in Standard SOP, choose Goto Opening stock level.
(C) SAP AG
LO935
8.6
Special Macro Operations
Operator
LO
L1
L2
L3
L4
PR
RW
ZS
Description
Stock balance
Target stock receipts
Receipts
Issues
Target stock / issues
Target supply / production
Days supply
Historical total
SAP AG 2002
The system has eight operators you can use to 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, choose Macro Record and then 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.
(C) SAP AG
LO935
8.7
Rough-Cut Planning Profiles
Duration
Resource
Week 1
Work center group WCG 19
Costs
Week 3
Raw material 13
Work center group WCG 12
Week 2
10
Unit
Pallet
Day
Day
20
20
USD
SAP AG 2002
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 system supports the following resource types:
Work center capacities
Materials
Production resources/tools
Costs
Rough-cut planning profiles can also give you an aggregate (summarized) picture of resources:
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.
(C) SAP AG
LO935
8.8
Determination of Capacity Load
A B
C
D
Planned quantity
x
Time per piece
=
Work center
Capacity
requirements
Available
capacity
Labor
SAP AG 2002
You perform resource leveling with reference to a plant. If your information structure does not contain
the characteristic plant, or if the system cannot uniquely identify from the characteristic values defined
in your rough-cut planning profile, you must 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
You define the determination of capacity load in the rough-cut planning profile. The system reads the
available capacity from the bottleneck work center defined in the resource table of the rough-cut profile.
The system calculates the capacity load by 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 resource table you will create a resource load of two hours for each planned base
quantity.
(C) SAP AG
LO935
8.9
Resource Leveling: Capacity Load
Material:
Plant:
Version:
100 Watt Clear

0001
A00
Sales
Production
Stock level
Active
M10/1997 M11/1997 M12/1997 Unit

100
200
200
Box
100
200
200
Box
100
100
0
Box
Assembly line 1
Machine
Available
Requirements
Load
200
50
25
200
100
50
H
H
%
Assembly line 1
Labor
Available
Requirements
Load
500
50
10
500
100
20
H
H
%
Annual planning 1997
SAP AG 2002
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 system
computes the new capacity instantly when you choose Enter.
(C) SAP AG
LO935
8.10
Resource Leveling
Work center hierarchy
Product group hierarchy
Overal
Overal
production
production
sector
sector
Production
Production
series
series
AM2
AM2
Production
Production
line
line 11
Light switches
Lightbulbs
Line 1
Line 3
Production
Production
series
series
AM3
AM3
...
Line 2
Production
Production
line
line nn
SAP AG 2002
You can carry out resource leveling either on a high level or at SKU level in both Flexible Planning and
Standard SOP.
Dont create the rough-cut profiles for different levels for the same material, because the resource loads
will add up.
(C) SAP AG
LO935
10
8.11
Customizing of Resource Leveling
Parameters of
Info Structure
Scheduling
Parameters
Routing
Selection
Profile
Priority 1 =
Capacity
key figure
Usage 1
Status 4
Planning Plant
Profile
Sel. ID
Priority 2 =
Usage 3
Status 4
Los Angeles
...
SAP AG 2002
A unique plant reference is required to carry out capacity leveling. If you are in Flexible Planning and
the system cannot identify a unique plant from the planning hierarchy, the system checks to see if you
have defined a plant for the information structure in the Customizing step Set parameters for info
structures and key figures. If you did not identify a plant, the system bases capacity leveling on the
universal SOP plant defined in the Customizing step Set planning plant for SOP.
The priority in which the system reads the rough-cut planning profile or routing depends on the
Customizing settings you have made in:
Configure scheduling parameters
Define routing selection
(C) SAP AG
LO935
11
8.12
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
(C) SAP AG
LO935
12
8.13Production Planning 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 you 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 Sales to
your planning type and changing the description to Sales. 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
(C) SAP AG
LO935
13
Receipts: Production
Issues: Sales
Stock: Stock level.
Days supply consists of
Days supply: Days supply
Issues: Sales
Stock: Stock level.
The system provides prompts in the bottom left-hand corner of the
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
Issues: Sales
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
Issues: Sales
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.
(C) SAP AG
LO935
14
Production Planning Exercises

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.
2-1
Using your new planning type ZPROD-##, change your active version.
2-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.
2-1-2 Distribute target stock of 100 and target days supply of 20 days for each of the
next 5 periods.
2-1-3 Run the macro PRODUCTION/TARGET STOCK. Explain the result.
2-1-4 Run the macro PRODUCTION/TARGET SUPPLY. Explain the result.
2-1-5 Save your plan.
(C) SAP AG
LO935
15
Exercises
Topic: Create a Rough-cut Planning Profile
Create a rough-cut planning profile
Now you want to analyze 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.
3-1
In Customizing specify key figure PRODU for capacity planning of your info structure
S6##.
3-2
Create a rough-cut planning profile for your info structure S6##.
3-3
Assign the rough-cut planning profile to Sales Organization 1000, Division 04.
3-4
Maintain the following profile:

Time span
1 workday
Base quantity
Status
Use
From lot size
To lot size
100000
3-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.
(C) SAP AG
LO935
16
3-5
Returning to your Rough-Cut Planning Profile. Enter the bottleneck work center, L1000 in plant 1200, and the unit minute. You need 12 minutes 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 time spans. All entries are
summed up to calculate the capacity requirements for one base
quantity.
3-6
(C) SAP AG
Save your rough-cut planning profile.
LO935
17
Exercises
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.
4-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.
4-2
Change the plan for the new version 1##. Specify Sales Organization 1000 and
Division 04 and perform a capacity check.
4-3
Level the capacity load.

If you have stored your planned version, the capacity requirements
are also stored. To recalculate the capacity load with a changed
rough-cut planning profile, you have to change the planned
production quantities.
(C) SAP AG
LO935
18
8.14Production Planning 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 Sales to
your planning type. The production planner should normally not change the sales
quantities, so define this line as an output line.
To add the field Sales, Edit Assign structure or [Add structure row]
Select Sales
Edit Row attributes
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.
Edit Row attributes
Change the row attributes to Average calculated
Define Stock level and Days' supply as output lines.

Edit Row attributes
Change the row attributes to Output line
(C) SAP AG
LO935
19

1-2
Save your planning type
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
Issues: Sales
Stock: Stock level.
Days supply consists of
Days supply: Days supply
Issues: Sales
Stock: Stock level.
The system provides prompts in the bottom left-hand corner of the
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
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
(C) SAP AG
LO935
20
Issues: Sales
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
Issues: Sales
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.
(C) SAP AG
LO935
21
Solutions
Topic: Create a Production Plan
2-1
Using your new planning type ZPROD-##, change your active version.
1. Planning Change
2. Enter your new planning type ZPROD-##.
4. Select active version the same version you created with the forecast tool earlier
in the course.
2-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.
2-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.
2-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 and target stock
level.
2-1-4 Run the macro PRODUCTION/TARGET SUPPLY. Explain the result.
(C) SAP AG
LO935
22
Production quantities are determined by the sales and the necessary stock to
cover the target days supply of the next month
2-1-5 Save your plan.
(C) SAP AG
LO935
23
Solutions
Topic: Create a Rough-cut Planning Profile
3-1
In Customizing specify key figure PRODU for capacity planning of your info structure
S6##.
Tools AcceleratedSAP Customizing Edit Project
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.
3-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
3-3
Assign the rough-cut planning profile to Sales Organization 1000, Division 04.
Enter Sales Organization 1000, division 04 and press Enter.
3-4
Maintain the following profile:

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

customization settings to determine whether this rough-cut profile is allowed.
(C) SAP AG
LO935
24
Selection Indicator 03 is always used for the capacity analysis in

flexible planning.
Create an alternative session

From the main SAP menu,
Tools AcceleratedSAP Customizing Edit Project SAP Reference
IMG
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.
Functions Resources Planning Configure scheduling parameters.
For plant 1200, SOP orders, and all production schedulers, in Rough-cut
scheduling check that you have SelID rough plng 03 and Generate capacity
reqs. is selected.
3-5
Returning to your Rough-Cut Planning Profile. Enter the bottleneck work center, L1000 in plant 1200, and the unit minute. You need 12 minutes during the first time span
to produce the base quantity of cartons.
Enter Bottleneck in the first field of the resource table.
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 min. Press Enter.
Enter 12 minutes 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.
3-6
(C) SAP AG
Save your rough-cut planning profile.
LO935
25
Solutions
Topic: Check the Capacity Load of Your Planned
Quantities
4-1
Copy your active version to version 1##.

Planning Version management Copy
Enter your info structure S6## and press Enter.
Enter the active version as the source version and version 1## as the target version
and click [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.
4-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.
4-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.
(C) SAP AG
LO935
26
If you have stored your planned version, the capacity requirements

are also stored. To recalculate the capacity load with a changed
rough-cut planning profile, you have to change the planned
production quantities.
(C) SAP AG
LO935
27
9
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
SAP AG 1999
(C) SAP AG
LO935
9.2
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
(C) SAP AG
LO935
9.3
Mass Processing: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Stat. Forecast
Info
Structure
Allocations
Events
Job
Mass Processing
Production Planning
SAP AG 1999
(C) SAP AG
LO935
9.4
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
(C) SAP AG
LO935
9.5
Possible Mass Processing Tasks
Macros
Copy key figures from one info structure to another
Forecasting
Copy/delete planning versions of one info structure
Calculate opening stock levels
SAP AG 2002
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.
(C) SAP AG
LO935
9.6
Steps in Mass Processing
Create profile
Define activity
Create job
Planning type
Objects
Info structure
Action
11
10
12
1
2
Version
Profile
Schedule job
4
7
6 5
Activity
SAP AG 2002
You can carry out the following planning activities using the sequence shown in the graphic:
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
When performing mass processing, the system bases these activities 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 the system processes actions within one activity 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 (blank), Started or completed with errors (E), or Completed successfully (S)
You can reuse planning jobs.
(C) SAP AG
LO935
9.7
Copy to
CO/PA
Copy IS IS
Transfer to
Dem. Mgt
Forecast
Macro
Detailed Steps in Mass Processing
Characteristics assignment
Key figure assignment
Profile
Activity
Create job and schedule
SAP AG 2002
The graphic 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 the
system will process: Planning Mass processing Revise. You can exclude from the report any
characteristic value combinations that you do not wish to process with this job.
(C) SAP AG
LO935
9.8
Execution
Job overview
Job queue
Schedule
Job
Forecast
Job
Forecast
Job 1
finished
Revise
Job
11
10
12
1
3
Material 1
forecasted
Material 2
forecasted
..
..
Material 100 forecasted
4
7
Job 1
9
6 5
SAP AG 2002
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 the system
process 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 the system carried out different actions, 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.
(C) SAP AG
LO935
9.9
Macro Calculation at Different Planning Levels
Example: Macro operation +1
Changed plan
Original plan
Detailed level
Sales organization
Material
50
54
40
30
100
20
20 10
15
1005
Aggregate l.
0
100
32
51
40
22
21 11 16
30.5
20.5
6 20.5 10 15.5 5
SAP AG 2002
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 system switches on the Aggr. planning indicator in the
planning type info.
2. At the detailed level, the system switches off the Aggr. planning indicator in the planning type info.
In background processing, the system calculates the results at the planning level defined in the variant.
(C) SAP AG
LO935
9.10
Assignement of Forecast Profiles to Materials
Job 1
Activity 1
Material 1
Material 2
..
..
Material 100
Constant profile
Job 2
Activity 2
Material 3
Material 4
..
..
Material 200
Trend profile
SAP AG 1999
(C) SAP AG
LO935
10
9.11
Data Exchange Between CO-PA and Flexible
Planning
CO-PA profile
Key figures
assignment
CO-PA
CO
CO-PA
Flexible
CO-PA
Planning
Characteristics
assignment
SAP AG 2002
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. The system supports this function 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
(C) SAP AG
LO935
11
9.12
Opening Stock
Zero
column
Feb.
Unit
Sales
Box
Production
Box
Stock
90 boxes
Jan.
90
Box
SAP AG 2002
The zero column has no particular period unit. The system displays opening stock levels here. You can
enter other opening values in this column. Only use the zero column if you dont have historical data in
your planning type (like in Standard SOP, or in Flexible Planning if you have not selected historical
periods 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 appear in the zero column of the planning table at run time. In consistent planning, the
system automatically aggregates the results. In level-by-level planning, the system sets them to the level
you specify in the planning job.
You can set opening stock one of three ways:
Read current stock
Calculate average stock
Apply a user method defined in Customizing
(C) SAP AG
LO935
12
9.13
SOP
3 basic
transfer
options
Demand Management
Flexible planning
xyzxyz xyzxyz
11
ab cab cab cabc
22
xyzxyz xyzxyz
11
ab cab cab cabc
22
ab cab cab cabc
22
xyzxyz xyzxyz
33
xyzxyz xyzxyz
11
ab cab cab cabc
22
xyzxyz xyzxyz
11
ab cab cab cabc
22
ab cab cab cabc
22
xyzxyz xyzxyz
33
xyzxyz xyzxyz
11
ab cab cab cabc
22
xyzxyz xyzxyz
11
ab cab cab cabc
22
ab cab cab cabc
22
xyzxyz xyzxyz
33
Standard SOP
- product group
Standard SOP
- material
SAP AG 2002
You can carry out the transfer of data to Demand Management either online or in background.
You have three basic processing options when 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 system transfers the data either directly from the
materials, or as proportions of the product group.
You transfer one material's data. The system transfers the data either directly 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 you can transfer it to
Demand Management more than once. The system issues a warning if you try to transfer a material from
a product group not marked as the MRP product group for that material.
When you carry out the transfer, the system creates planned independent requirements in Demand
Management.
(C) SAP AG
LO935
13
9.14
Synchronized Data Transfer to Demand Mgmt
Sales organization
Division
Sold-to party
Material
Plant
Sales plans
Production plans
..
.
Flexible
Flexible
Planning
Planning
Customizing:
Customizing:
Key
Keyfigure
figure
Planning
Planningversion
version
Demand
Demandversion
version
Key figure is transferred

when the flexible planning
version is saved
Independent
Requirements
Statement of
demand
Demand
Demand
Management
Management
..
.
SAP AG 2002
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 system is to transfer data (Sync. version)
Demand version to which the system is to transfer data
(C) SAP AG
LO935
14
9.15
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 2002
You can 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 the system can find a plant or plants for the material in the planning hierarchy, it transfers data to
Demand Management for these plants.
2) If the system cannot find a plant in the planning hierarchy, the system checks to see which plants you
have maintained for the material in the material master record. It then checks to see whether you have
maintained distribution quotas for the material in Define proportional distribution across plants. The
system bases its transfer to Demand Management on these quotas.
3) If the system cannot find distribution quotas 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
system bases its transfer to Demand Management 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 the system cannot find any distribution quotas (neither material-specific nor generic ones), the
system splits the data equally among all the plants in the material master record.
(C) SAP AG
LO935
15
9.16
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
(C) SAP AG
LO935
16
9.17Mass Processing 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 version 1##. Transfer at plant level.
(C) SAP AG
LO935
17
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

parameters. It does not display the list itself.
1-1-6 Display the results in Demand Management.
(C) SAP AG
LO935
18
9.18Mass Processing 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 groups info structure, S6## in the table field.
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##.
(C) SAP AG
LO935
19
Settings Mass processing Activities

Choose [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 version 1##. 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. Choose 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
Choose Execute.
2. Info structure: your groups info structure
Version: Activeversion, A00.
Choose 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.
Choose the Attributes button.
A dialog box will display the message Please check whether material and
plant are in the execution level. Choose [Continue].
Enter a description for your variant. Save your variant. Click 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##
Choose Execute.
(C) SAP AG
LO935
20
Choose Immediate.
Choose 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
Choose Execute.
You should see your job Transfer to demand management. If the status is
Active ,then press Refresh until it becomes Finished.
To see the output of the job, click once on the job name and press Spool List.
Select the spool. Choose [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 Production planning Demand management
Planned indep.reqmts Display
Enter any material and Plant 1200.
Select the selected version indicator and enter your demand version ##.
Press Enter and work through the warning by pressing Enter again.
Compare the result with the planned quantities of your planning version 1##
using the planning type ZPROD-##.
(C) SAP AG
LO935
21
10
Allocations
Contents:
Prerequisites for product allocations
Allocation procedures and objects
Info structure for product allocations
Discrete allocations
Cumulative allocations
SAP AG 1999
(C) SAP AG
LO935
10.2
Allocations: Unit Objectives

Outline the principles of allocation
Maintain the allocation determination
procedure
Explain the difference between discrete and
cumulative allocation
SAP AG 1999
(C) SAP AG
LO935
10.3
Allocations: Course Overview
Planning Types
Master Data
Planning
Functions
Planning Method
Stat. Forecast
Info
Structure
Allocations
Events
Job
Mass Processing
Production Planning
SAP AG 1999
(C) SAP AG
LO935
10.4
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
(C) SAP AG
LO935
10.5
What is Product Allocation?
DEMAND
Managing demand against constrained supply
1/99 2/99
3/99
4/99
SUPPLY
SAP AG 2002
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, sales organizations, and so on, 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 need for different phases of allocation control during the overall constraint
period.
(C) SAP AG
LO935
10.6
Sales Order Processing
Customer: Star Markets

Req. Delivery Date: 20.01.99
ATP check is OK
Item 10
Bulb L-40F
On time delivery
20.01.99
Complete delivery
01.02.99
Delivery proposal
20.01.99
01.02.99
Flex. Planning
Allocation
100 BOX
Allocation fails
Only 80 left
80 BOX
100 BOX
80 BOX
20 BOX
SAP AG 2002
Product allocation encompasses allocations to all characteristics of the sales order, including sales
organizations and channels, external customer groups, and specific customers.
For other characteristics, you must use the user exit, INCLUDE Fv45vfzy user exit_quota_key_va (or
transaction SE38).
(C) SAP AG
LO935
10.7
Definition of Product Allocation
Material
Master Rec.
Procedure
Procedure:
Obj.1
Obj.1
Obj.2
Obj.3
12.98
06.99
12.99
12.04
Material
Component
Work center
Allocated qty.
S140
Committed qty.
Demand
SAP AG 2002
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 Specify 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.
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.
(C) SAP AG
LO935
10.8
Custom Defined Allocation Structure
Characteristics
Info structure
Allocation Obj.
Region
Sales organization
Customer
Alloc. Object 1
Alloc. Object 2
Characteristic value specified

in the planning hierarchy
Collective characteristics
maintained in the planning hierarchy
North
South
(Customers)
SAP AG 2002
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 planning hierarchy with the allocation objects on the highest level. Establish the
proportional factors to get allocation percentages for specific characteristic values.
The system performs the allocation check 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 collective characteristics to it by
selecting the Customizing activity Permit collective product allocation in info structures. This creates a
default entry for the specified nodes in the hierarchy.
You cannot use deviating masking symbols for different procedures linked to the same info structure. If
you have assigned an info structure several times, you can perform the assignment with or without a
format template.
(C) SAP AG
LO935
10.9
Product Allocation Object Validity
JANUARY
Updating
date
Work center problems
WEEK
Component shortage
SAP AG 2002
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. The system determines the relevant object based on the updating date for the key figure of the
info structure,. 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 and 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
(C) SAP AG
LO935
10.10
Allocation Planning Table
Characteristics
Key figures
Alloc. Object: Bulbs

Dist. Channel: 01
Sales Org: 0001

Cust. Grp: 02
1 / 99
2 / 99
3 / 99
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
Open product alloc.
2,300
3,000
3,000
SAP AG 2002
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).
(C) SAP AG
LO935
10
10.11
Discrete Allocation
750
Available Allocation: 500PC

500
250
are not available

Order Qty
Allocation Qty
*Unused 250PCs from 01/98
1/99 2/99 3/99
4/99
Current
Period
SAP AG 2002
The system supports the following allocation methods:

Discrete allocation
Cumulative allocation
If you did not set the ATP consumption indicator in the Customizing activity Maintain procedure, the
system uses 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 (the
system ignores unused product allocation quantities from past periods). When you use the discrete
method, you cannot use the following product allocation functions:
Consumption periods
Allocation steps
(C) SAP AG
LO935
11
10.12
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 2002
Setting this ATP consumption indicator in the Customizing activity Maintain procedure the system uses
the cumulative allocation method. This method involves a checking logic that corresponds to ATP
cumulating 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 that the system is to use as
the valid consumption period.
The number of past periods identifies the number of periods before the product allocation date in the
order that the system can use for calculating unused allocations. The system then cumulates the
unused product allocation quantities of these past periods before checking the product allocation for
the current period.
The number of future periods identifies the number of periods after the product allocation date in the
order that the system can use them for the future allocations. If you do not confirm the requested
quantity within the future periods, it remains unconfirmed.
(C) SAP AG
LO935
12
10.13
Allocation Window Logic
-2 month
+1 month
40
40
20
60
40
1/99
2/99
3/99
4/99
40
5/99
Order 100 Car.
SAP AG 1999
You can use the consumption periods in the following ways:

past periods
2
999
999
future periods
Result
Above example
Unlimited product allocation (default value)
Unlimited cumulation 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
(C) SAP AG
1
999
0
LO935
13
10.14
Allocations: Unit Summary

Outline the principles of allocation
Maintain the allocation determination procedure
Explain the difference between discrete and
cumulative allocation
SAP AG 1999
(C) SAP AG
LO935
14
10.15Allocations - 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.
(C) SAP AG
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
LO935
15
(C) SAP AG
Group Number
Customer group
Customer
17
02
22000
18
02
99999
LO935
16
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:
Sales Organization:
Distribution Channel:
Customer group:
Customer:
Work center
1000
12
Your customer group
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.
(C) SAP AG
LO935
17
1-6
Create a sales order.

Logistics Sales and distribution Sales Order Create
On the selection screen, enter the following data:
Order type:
OR
Sales Organization:
1000
12
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.
Work center
Sales Organization:
Customer group:
Customer:
1000
12
Your customer group
Your customer
1-7-1 Why is synchronous updating used?
(C) SAP AG
LO935
18
10.16Allocations - Solutions
Unit: Allocations
In this unit, each group is assigned their own customer in Sales

Organization 1000, Distribution Channel 12.
(C) SAP AG
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
LO935
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.
(C) SAP AG
LO935
20
1-5
Maintain in Flexible Planning customer requirements and allocations quantities for

your customer. Use planning type COMMIT and inactive version 000.
Sales Organization:
Customer group:
Customer:
Work center
1000
12
Your customer group
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.
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
Sales Organization:
1000
12
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.
(C) SAP AG
LO935
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
Work center
Sales Organization:
Customer group:
Customer:
1000
12
Your customer group
Your customer
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.
(C) SAP AG
LO935
22
11
Conclusion
Planning Types
Master Data
Planning
Functions
Planning Method
Stat. Forecast
Info
Structure
Allocations
Events
Job
Mass Processing
Production Planning
SAP AG 1999
(C) SAP AG
LO935
11.2
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
(C) SAP AG
LO935
11.3
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
(C) SAP AG
LO935
11.4
Logistics Planning Systems
Sales organization
Division
Plant
Material
Sales plans
Production
plans
.
SKUs/
configurable materials
SOP
SOP
..
Statement of
demand
.
Demand
Demand
Management
Management
..
Order and rate proposals

BOM explosion
Scheduling at work
centers
Quantities .and dates
MPS/MRP
MPS/MRP
..
Production controlled
by run schedule
headers
Repetitive
Repetitive
Manufacturing
Manufacturing
Production order
control
SFC
SFC
SAP AG 1999
(C) SAP AG
LO935
11.5
Information Flow
SD
Demand Management
Sales order in August 1998:

Laptop DD-415
Planned independent requirements

Consumed with sales orders at SKU level
SIS Updating
Flexible Planning (SOP)
Sales order for August 1998:

sales organization EAST,
distribution channel WHOLESALE,
material LAPTOP DD-415
Sales plan 1999

Event planning
Resource leveling
Planned production quantities 1999
SAP AG 2002
The graphic shows the flow of information from the SD module through the Sales Information System
and Sales and Operations Planning to Demand Management.
(C) SAP AG
LO935
12
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
(C) SAP AG
LO935
12.2
Functional Enhancements
MCP20001
Read external data
MCP20002
Calculate initial macro

"
default macro
"
final macro
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)
R/3
User
Exit
SAP AG 2002
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 graphic lists the support functional enhancements. The following rules
apply to the functional enhancements:
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 system or from
a third-party system.
If you write a complex macro with the MCP20002 user enhancement, you must define this macro in a
planning type. The macro name must begin with the string USER.
(C) SAP AG
LO935
12.3
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 2002
After you have changed data in the planning table you can use MCP20011 to analyze, enhance, or
change data records before the system stores them in the database, for example, to fill character key
figures.
Use MCP20012 to inactivate function codes such as Disaggregate line.
Use MCP20013 to initialize the planning table, for example, select periods, change line status to output
only, enter key figure values (for example, 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 the MCP20015 user exit.
If you have set the Key-figure-restricted DB update to on (transaction MC7F), the MCP20017 user exit
allows you to further reduce the number of key figures the system is to lock.
Use MCP20018 to define possible entries for the maintenance of a planning hierarchy.
(C) SAP AG
LO935
12.4
User Methods
Automatic creation of a planning hierarchy

Reduce planning records
Reorganize actual data
Set opening stock
Copy between info structures
SAP AG 2002
You can create your own user methods in Copy Management for the functions shown in the graphic. 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 exist. For example, a method allows you to perform complex
transformations on statistical data. It consists of administrative information and an ABAP FORM routine
that you write yourself.
(C) SAP AG
LO935

Flexible Planning

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Flexible Planning

Încărcat de

Drepturi de autor:

Formate disponibile

Flexible Planning

Copyright 2004 SAP AG. All rights reserved.

Project team members responsible for planning in

Notes to the user

This course will enable you to:

differences between them

On completing this course, you will be able to:

Planning Types and Macros

General Planning Functions

You are a member of your companys planning

implementation team. You must define your info

Order and rate proposals

(Product groupings or materials)

Multiple options for

Content and layout of

Standard planning table

Jones, Inc. 25,000

Previous/Current Year Comparison: Invoiced

Customer Sales Orders No.

Baxter 5000 3000

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

Sales & Operations Planning (SOP) is the planning

tool of the Logistics Information System.

other supply chain and logistics activities.

Operations Planning have the same data

elements: Flexible planning and standard SOP.

On completing this unit, you will be able to:

You are a member of your companys planning

implementation team. You have already created the

Material AM001 is selected from planning hierarchy

Planned qty Proportion

Consistent planning has two main advantages:

Order quantity visible

Order quantity stored

Incoming orders quantity

Incoming orders quantity

Planned incoming order quantities are changed from 30 pc and

Planned values can be saved at all levels.

Entire planning hierarchy can be planned in

At least one characteristic value must be specified.

Planning table can be called with gaps in list

Planning table must be called without gaps in list of

Planning values are visible:

Planning values are visible:

Identical key figures planned at total and

Key figures at owner and member levels can be different.

Key figures are defined in the planning type

Key figures must be defined at both owner and member

Macros can be calculated at any level.

Macros can be calculated at either owner or member

Standard SOP always uses the level-by-level planning method.

Create planning hierarchy

Standard analysis for info structure

Transfer to Demand Management

Define planning type

You are now able to:

2.16Data Used in the Exercises

Data in Training System

Data in IDES System

L-40C, L-40F, L-40R,

L-40C, L-40F, L-40R,

L-60C, L-60F, L-60R,

L-60C, L-60F, L-60R,

L-80C, L-80F, L-80R,