Demand Planning
SAP Business ByDesign
Demand Planning
Table of Content
1
About this Document ....................................................................................................................... 3
1.1 Purpose .................................................................................................................................... 3
1.2 Reference System and Model Company.................................................................................... 3
2
Master and Organizational Data ...................................................................................................... 4
3
Business Process Tasks ................................................................................................................. 5
3.1
3.2
Demand Planning...................................................................................................................... 5
3.1.1 Important Note .............................................................................................................. 5
3.1.2 Set up a Demand Plan .................................................................................................. 5
3.1.3 Interactive Demand Planning ......................................................................................... 7
3.1.4 Supply Planning ............................................................................................................ 9
Connected Scenarios .............................................................................................................. 10
July 28, 2012
2
Demand Planning
1 About this Document
1.1 Purpose
The objective of this business scenario document is to give you hands-on experience of running the
chosen business processes in a realistic business environment using the SAP Business ByDesign
system. It allows you to quickly become familiar with this business scenario by guiding you through the
steps that you need to carry out in the reference system.
To obtain a better understanding of the business processes that make up this scenario, also
refer to the Scenario Outline for this scenario.
1.2 Reference System and Model Company
A reference system is a system that is preconfigured and loaded with fictitious users and sample data.
The users and sample data are based on the model company Almika Inc.. By following the step-by-step
instructions in this document, you can assume the identity of the Almika users and use the built-in sample
data to carry out each of the business process tasks. This hands-on experience will help you to
understand the relevance and benefits of this business scenario.
To learn more about the model company that uses the business processes described in this
document, read the Company Fact Sheet, which contains an overview of the reference
company, its organizational set up, employees and their different roles and work centers, as well
as a comprehensive list of the master data used in your system.
You can find the Company Fact Sheet in the Help Center of your reference system. To access
this document, choose Help  Help Center and open the link under the heading CompanySpecific Help.
July 28, 2012
3
Demand Planning
2 Master and Organizational Data
Each SAP Business ByDesign Reference System contains essential master and organizational data,
which

reflect the typical organizational structure of a mid-size company of a specific industry

allow you to run the industry specific processes using the appropriate master data, for example,
materials, vendors or customers.
For this scenario, use the master data as described below.
If you want to run the scenario with customer and project-specific values, you can copy master data with
certain characteristics from the sample entries in the table and adapt this data.
For an illustration of the organizational data as well as additional information (bill of material, logistics
layout) about the reference company, refer to the Company Fact Sheet.
Master / Org. Data Type
Name and Value
Forecasting Group ID
100001
Planning Area ID
Almika Heating Cleveland
P1100
Product ID
Combi ME (P100405)
July 28, 2012
Usage
4
Demand Planning
3 Business Process Tasks
3.1 Demand Planning
3.1.1 Important Note
This document describes how you can set up a new demand plan that can be used for Interactive
Planning without any existing historical demand. During planning, very simple historical data is entered.
If you would like to use more sophisticated planning functions, you can make use of three predefined
demand plans. You can then skip chapter 3.1.2 (Set up a demand Plan) and directly start with the chapter
3.1.3 (Interactive Demand Planning).
The three predefined demand plans are based on different forecasting models:

DP_10: This demand plan contains two items which show seasonal demand
(compressors are the essential element of an air conditioner and will have strongly
skewed demand in the summer. Burner elements for furnaces will have the reverse
usage pattern).
 Forecasting Model: Seasonal Linear Regression

DP_11: This demand plan is set up to demonstrate the ability to forecast trends. The
item is new in the market and has found market acceptance. Demand is growing at a
regular rate.
 Forecasting Model: Linear Regression

DP_12: This demand plan is set up to demonstrate averaging consumption to forecast
future demand.
 Forecasting Model: Weighted Moving Average
3.1.2 Set up a Demand Plan
What You Should Know
The Supply Planner sets up a demand plan which contains the products and parameters required for a
forecast of a future demand.
The system helps to create a new demand plan using a guided process. The Supply Planner selects the
products for each planning area, the statistical forecast parameters, and the time parameters the plan has
to take into consideration.
Logon and Work Center Information
Logon ID (Role)
SUPPLYPLANNER01P (Supply Planner / Richard Stone)
Work Center / View
Demand Planning  Demand Plans
July 28, 2012
5
Demand Planning
Procedure
Field Name
Data to Enter
Activity / Button / Comment
Demand Plans view
Click New.
New Demand Plan guided activity
Step 1: Define General Settings
Demand Plan ID
FC_2012
Demand Plan Description
Forecast 2012
Planning ModeMulti Level Planning
Enabled
No
ForecastingStatistical Forecasting
Enabled
Yes
Time – Plan Demand In
Month
Time - Forecast Start Date
<First day of the current
month>
Time - Forecast Horizon
4
Time – History Horizon
6
Click Next.
Step 2: Select Planning Criteria
Click Next.
Step 3: Maintain Scope
Click Add Row.
Product ID
Click Object Value Selector
Select: Product ID
Click Advanced.
Product Group Type
Forecasting Group
Product Group ID
100001
Click Go.
Product ID
Combi ME (P100405)
Select the line.
July 28, 2012
6
Demand Planning
Field Name
Data to Enter
Activity / Button / Comment
Select: Planning Area ID
Planning Area ID
Almika Heating Cleveland
P1100
Click Next.
Step 4: Define Forecasting Models
Forecasting Models
Moving Average,
Linear Regression
Select the lines.
Click Add Item.
Forecasting Model
Variants - Use as Default
1 Average (Mark Check Box)
Forecasting Model
Variants
2 Moving Average
Select the line.
Model Variant Settings –
Number of Periods
3
Click Next.
Step 5: Set Time Parameters
Release Offset
0
Release Horizon
3
Click Next.
Step 6: Review
Click Finish with Activation.
Step 7: Confirmation
Click Close.
3.1.3 Interactive Demand Planning
Logon and Work Center Information
Logon ID (Role)
Work Center / View
SUPPLYPLANNER01P
(Supply Planner / Richard Stone)
Demand Planning  Demand Plans
July 28, 2012
7
Demand Planning
Procedure
Field Name
Data to Enter
Activity / Button / Comment
Demand Plans view
Demand Plan ID
FC_2012
Select the line.
Click Plan.
Planning Board screen
Click Choose Planning Board
Layout  Maximal Layout.
Click Move To
 History Start.
Final Actuals
1st Month
(current month -6)
20
Final Actuals
2nd Month
(current month -5)
20
Final Actuals
3rd Month
(current month -4)
20
Final Actuals
4th Month
(current month -3)
10
Final Actuals
5th Month
(current month -2)
10
Final Actuals
6th Month
(current month -1)
10
Click Move To
 Forecasting Start
Copy Statistical Forecast
to Final Forecast
Select the checkbox.
Click Run Statistical
Forecast.
The rows Statistical Forecast and Final Forecast show the calculated forecast per period
July 28, 2012
8
Demand Planning
Field Name
Data to Enter
Activity / Button / Comment
depending on the final actuals and the forecasting model.
Model Variant ID
2 Moving Average
Click Run Statistical
Forecast.
Model Variant ID
3 Linear Regression
Click Run Statistical
Forecast.
The Statistical Forecast and Final Forecast values are calculated according to the
forecasting model.
Click Save, then click Close.
Demand Plans view
Demand Plan ID
Click Release.
FC_2012
Release screen
Click Apply, and then click
Close.
Typically, the forecast release would be an automated step. However, in order to show you
this particular step, the job has not been scheduled. To define and schedule the job, go to
Automated Actions in the Demand Planning work center, define the Release Run, and then
define the required Schedule.
3.1.4 Supply Planning
Logon and Work Center Information
Logon ID (Role)
SUPPLYPLANNER01P
Work Center / View
Supply Planning  Products
(Supply Planner / Richard Stone)
Procedure
Field Name
Data to Enter
Activity / Button / Comment
Products view
Show List
All Products by Selection
Product ID
Combi ME (P100405)
July 28, 2012
Click Advanced.
9
Demand Planning
Field Name
Data to Enter
Activity / Button / Comment
Planning Area ID
Almika Heating Cleveland
P1100
Click Go, then click Open.
Product Planning Details: Combi ME (P100405) / Almika Heating Cleveland P1100 screen
For an overview, see the Supply and Demand List. Entries named forecast in the
Category column are the result of the demand planning done previously. At this stage, the
planning data has entered the supply level.
Click Run Planning  Single
BoM Level.
Run Planning: Single BoM Level window
Allow Planning Proposals
Creation In Past
<Do not mark the check box>
Click OK.
Product Planning Details: Combi ME (P100405) / Almika Heating Cleveland P1100 screen
Typically, the MRP run would be an automated step. However, in order to show you this
particular step, the job has not been scheduled. To define and schedule the job, go to
Automated Actions in the Supply Planning work center, define the Planning Run, and then
define the required Schedule.
Click Save and Close.
3.2 Connected Scenarios
The subsequent steps such as production and purchasing are documented in the business scenario
document:
 Make-to-Stock
 Procure-to-Pay (Stock)
July 28, 2012
10
Demand Planning
Icons
Caution
Example
Tip
Note
User ID and User Role
Work Center and Work Center View
Copyright
© 2012 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vend ors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture,
Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect,
RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
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 o f Citrix Systems Inc.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C® , World Wide Web Consortium, Massachusetts Institute of Technology.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World
are trademarks or registered trademarks of Research in Motion Limited.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google
Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and servic es mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countr ies.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360° , and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.
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 materia ls. 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 here in should be construed as constituting an additional
warranty.
July 28, 2012
11