You are on page 1of 15

Page

TABLE OF CONTENTS
1 INTRODUCTION .............................................................................................................................................. 2
1.1 PURPOSE OF THIS DOCUMENT ........................................................................................................................... 2
1.2 INTENDED AUDIENCE ....................................................................................................................................... 2
1.3 RELATED DOCUMENTS ..................................................................................................................................... 2
2 KEY DATA STRUCTURES FOR SCM-DP .................................................................................................... 3
2.1 SETTING UP APO BW ....................................................................................................................................... 4
2.2 SOURCE SYSTEM (FILE): ZISDP ....................................................................................................................... 4
2.3 SETTING UP INFO AREA (APO BW) .................................................................................................................. 4
2.4 INFO-OBJECT CATALOG: .................................................................................................................................. 5
2.5 INFO-OBJECT: ................................................................................................................................................... 5
2.6 SETTING UP THE INFO SOURCE (APO BW) ....................................................................................................... 6
2.7 CREATE INFOSOURCE ....................................................................................................................................... 6
2.8 SETTING UP THE INFO CUBE (APO BW) ........................................................................................................... 6
2.9 CREATE THE UPDATE RULES ............................................................................................................................ 8
2.10 PLANNING OBJECTS STRUCTURE: ................................................................................................................ 8
2.11 MAINTAINING FISCAL YEAR VARIANT AND PERIODS .................................................................................. 8
2.12 STORAGE BUCKET PROFILES: ...................................................................................................................... 9
2.13 SETTING UP THE PLANNING AREA................................................................................................................ 9
2.14 MAINTAINING THE TIME BUCKETS PROFILE .............................................................................................. 10
2.15 SETTING UP THE PLANNING BOOK ............................................................................................................. 11
2.16 CREATING THE FORECAST PROFILE (SAP APO) .................................. ERROR! BOOKMARK NOT DEFINED.
2.17 FORECASTING METHOD: ............................................................................................................................ 12
2.18 CREATING MACROS (SAP APO)................................................................................................................ 12
2.19 ASSIGNING USER TO PLANNING BOOK (SAP APO) ................................................................................... 13
2.20 INITIALIZING THE PLANNING AREA............................................................................................................ 13
2.21 CREATING SELECTION PROFILES FOR THE PLANNING BOOK ...................................................................... 13
2.22 SETTING UP THE RELEASE OF THE DEMAND FORECAST ............................................................................. 14
2.23 CREATING AN ACTIVITY ............................................................................................................................ 14
2.24 BATCH JOBS IN DEMAND PLANNING: ......................................................................................................... 15
Page
1 Introduction

1.1 Purpose of this Document
This document describes all Key Data Structures for SCM-Demand Planning, necessary for
enabling the Ispat’s various business processes defined under Process Definition Documents for
Demand Management and making them operational with requisite controls and business rules.
This document will serve as reference document for system settings and configuration in
Realisation Stage.
This document lists out all KDS whether required to be defined newly or the mySAP Standard
ones which are identified for use in any of the process for Demand Management. The list however
excludes those mySAP Standard KDS that are not identified for a specific use but may not be
deleted from production client for technical or other pragmatic reasons.

1.2 Intended Audience
This document is for internal project distribution. It is to be used to communicate to all team
members the value list of Key Data Structures for Demand Management. It is the responsibility of
all project team members to read the document and seek clarification from Team Leaders or
Project Management if they have any queries.

1.3 Related Documents
This document should be read in conjunction with the following documents:
Process Definition Documents for Demand Management.

Page
2 Key Data Structures for SCM-DP
A basic prerequisite for executing demand forecasts in SAP APO, is the availability of master
& historical sales data.
Master Data Requirements
1. Product Master Data:
 SAP Material Number
 Planning Material
 Product Segment
 Grade

2. Customer Master data:
 Sold-to-Party
 Customer Segment
 Sales Region= Region(Domestic),Country(Exports)

3. Key Account Manager:
 KAM
 KAM-Customer mapping

4. Location Master Data:
 Location

5. Ispat Calendar Master Data: (To Be maintained in SCM)

Calendar months and week numbers must be reflected in the SCM and BIW reporting.
Page
Transaction data
History Data
1. Sales History: Consists of monthly Sales History for each SAP Material Number-APO
Location Combination.
a. Initial Data Load:
 Initial load of past two years sales history data into BIW from SAP ECC
 Initial load of past two years sales history data into APO from BIW
b. Weekly/Monthly Data Load:
 Load of sales history data into BIW from SAP ECC
 Weekly/Monthly load of sales history data into APO from BIW
(All data will be in TON)

2. NSR (Net Sales Realization): Consists of NSR, NSR Value for Planning Product-Customer
a. Initial Load:
 Initial load of past one year NSR into BIW from SAP ECC
 Initial load of past one year NSR into APO from BIW
b. Monthly Load:
 Load of NSR data into BIW from SAP ECC
2.1 Setting up APO BW
To enable SAP APO to load master historical sales data, we need to make several settings in the
BW part of the SAP APO system, which is called the Data Warehousing Workbench.
Creating the Source System (APO BW)
A source system indicates the system from which the transaction data and master data
originated.
Procedure: Access the activity using one of the following navigation options:
SAP SCM menu Advanced Planning and Optimization  Demand
Planning  Environment  Data Warehousing
Workbench
Transaction code RSA1

2.2 Source System (file): ZISDP
2.3 Setting up Info Area (APO BW)
In this activity, you create the info area and the application component in the Data Warehousing
Workbench of the SAP APO BW. The info area is used for cataloging InfoCubes, allowing them to
be assigned more effectively.
Procedure
1. Access the activity using one of the following navigation options:
SAP SCM menu SAP Menu  Advanced Planning and Optimization  Demand
Planning  Environment  Data Warehousing Workbench
Transaction code RSA1
2. On the left side, in the Modeling screen area of the Data Warehousing Workbench, choose
InfoProvider.
3. In the right screen area, right-click InfoProvider and choose Create InfoArea.


4. Enter the following data:

Page
Field name Description User action and values Comment
Info Area ZIS_DP_IA
Long Description Ispat Demand Planning Info Area

2. Choose Continue.
3. In the left part of the Administrator Workbench screen, in the Modeling section, choose
InfoSources.

4. Right-click the InfoSources node and choose Create Application Component.

5. Make the following entries:
Field name User action and values Comment
Application comp.

ZIS_DP_APPLCOMP
Create a new one for Ispat

Long description
Application component for Demand
Planning



2.4 Info-Object Catalog:
 ISPAT KEY-FIGURE CATALOG: ZIS_KF_CAT
 ISPAT CHARACTERISTIC CATALOG: ZIS_CHAR_CAT
2.5 Info-Object:
1. Key Figures: The following spreadsheet contains technical details of the Key-Figures:

2. Characteristics: The following spreadsheet contains technical details of the Key-Figures:




Unit of Measure:
Tonne (TO) will be used as the unit of measure
Page
2.6 Setting up the Info Source (APO BW)

In this activity, you create the InfoSource for transaction data so that you can transfer data from the
source system to the SAP APO System. The InfoSource is created in the Administrator Workbench.
In an InfoSource, the logically linked information is grouped in the form of InfoObjects.
In this activity, you also define the communication structure, assign the source system and define the
transfer rules. The Communication Structure represents the structure of an InfoSource. It contains all
InfoObjects that belong to an InfoSource. The Transfer Structure is the framework in which data from
the source system is transferred to the SAP APO system. Transfer rules enable you to specify how
the fields in the transfer structure are assigned to the InfoObjects in the communication structure.
This is normally a 1:1 assignment, although InfoObjects can also be filled via routines or constants.

Procedure
1. Access the activity using one of the following navigation options:
SAP SCM menu SAP Menu  Advanced Planning and Optimization  Demand
Planning  Environment  Administrator Workbench
Transaction code RSA1
2. In the Modeling section of the Administrator Workbench screen, choose InfoSources.

3. Right-click the Demand Planning Application component you have created, and choose Create
InfoSource.













2.7 Create InfoSource
2.8 Setting up the Info Cube (APO BW)
In this activity, you create an InfoCube, which is a data container for planning data, and assign
characteristics and key figures to it. Then you maintain update rules for the InfoCube. Update rules
Page
specify how data (key figures, time characteristics, characteristics) is written to the InfoCube from the
communication structure of an InfoSource. This way, the InfoSource is linked to the InfoCube. An
InfoCube can receive information from several InfoSources. A set of update rules must be maintained for
each InfoSource you wish to link with the InfoCube.
Procedure
1. Access the activity using one of the following navigation options:
SAP SCM menu SAP Menu  Advanced Planning and Optimization 
Demand Planning  Environment  Administrator
Workbench
Transaction code RSA1
2. In the left screen area of the Administrator Workbench, choose InfoProvider.

3. Right-click the new InfoArea and choose Create InfoCube.

4. In the Edit InfoCube dialog box, make the following entries:



5. Choose Create.
The Choice of BW Application dialog box is displayed.

6. Double-click BW.
7. Assigning the info-object to the InfoCube
8. Create Dimensions assign characteristics








Dimension Description Comments
ZIS_LOCATION Location

ZIS_PRODUCT Product

ZIS_CUSTOMER Customer

VERSION Version

Page
9. Assign characteristics to Dimension

2.9 Create the Update Rules
2.10 Planning Objects Structure:
We need to activate the standard planning object structure for Demand Planning, which groups
together characteristics that can be planned in one or more planning areas of Demand Planning.
You cannot create a planning area without a master planning object structure.
Procedure
1. Access the activity using one of the following navigation options:
SAP SCM menu Advanced Planning and Optimization  Demand Planning
 Environment  Administration of Demand Planning and
Supply Network Planning
Transaction code /SAPAPO/MSDP_ADMIN

The Master Planning Object Structure used in APO Demand Planning: ZISDPDLV for Dolvi. It
contains all the Characteristics listed above. There will be one MPOS per Planning Area.
2. Characteristics for Planning: MPOS will have all the Characteristics
2.11 Maintaining Fiscal Year Variant and Periods
Define Fiscal Year Variant to use posting period as a time bucket in Demand Planning. Define the
following characteristics for a fiscal year variant
1. How many posting periods a fiscal year has
2. How many special periods needed
3. How the system is to determine the posting periods when posting

During Fiscal Year definition the following options can be used:
1. Fiscal Year is the Calendar Year
2. Fiscal Year deviates from the calendar year and is not related to the calendar year
3. Fiscal Year deviates from calendar year and is related to the calendar year

Procedure
1. Access the activity using one of the following navigation options:
SAP SCM menu IMG Activity
Transaction code SPRO
Path mySAP SCM – Implementation Guide  Advanced
Planning and Optimization  Supply Chain Planning
 Demand Planning  Basic Settings  Maintain
Fiscal Year Variants.


Field User action and values
FV
ZIS_FYV
Description ISPAT Fiscal Year Variant
Year Dependent Check
Page
Calendar Yr
Number of Posting
Periods
64
No. of Special Periods


2.12 Storage Bucket Profiles:
Periodicities for a planning area (also called storage buckets profile) define the time buckets in
which data based on a given planning area is saved in Demand. The periodicity for Demand
Planning is usually divided in weeks and months. You need to define a storage buckets profile
before you can create a planning area.
Procedure
1. Access the activity using one of the following navigation options:
SAP SCM menu Advanced Planning and Optimization  Demand
Planning  Environment  Current settings 
Periodicities for Planning Area
Transaction code /SAPAPO/TR32

Storage Bucket Profile will have Posting Periods (Fiscal Variant “IS”) and Calendar Months. The
same Storage Profile will be assigned to all Planning Areas.
Field User action and values
Stor.Bckts Prfl
ZIS_DP_SB_DL & ZIS_DP_SB_KLM
PostPeriod Enable
Fi. Year Variant IS
Start date
End date
2.13 Setting up the Planning Area
A planning area is the central data structure of Demand Planning. It groups the parameters that
define the scope of planning activities.
Procedure
Create a planning area by executing the following steps:
1. Change to the S&DP Administration screen.
SAP SCM menu Advanced Planning and Optimization  Demand Planning 
Environment  Administration of Demand Planning and Supply
Network Planning
Transaction code /SAPAPO/MSDP_ADMIN

Field name User action and values Comment
Planning area ZIS_DP_PA_DL , ZIS_DP_PA_KLMCC,
ZIS_DP_PA_KLMGP & ZIS_DP_PA_KLMCR

Page
Field name User action and values Comment
ZIS_ALLOC_PA_KLM
Master plg object
structure
ZISDPDLV , ZISKLMCR , ZISKLMGP &
ZISKLMCC,ZISKLALO

Database connection LCA (Default)
Stor. bckts prfl ZIS_DP_SB_DL & ZIS_DP_SB_KLM
Unit of measure TO
Versions:
000 version will be used for the active planning (3 month Rolling Forecast) and other simulation
versions will be used for Annual Business Plan, the backup and comparison.
Key figures’ dis-aggregation rules
2.14 Maintaining the Time Buckets Profile
Time bucket profiles define the historical or future time horizon for Demand Planning or Supply
Network Planning. With this step, you define which time buckets can be used for planning, how many
periods of each time bucket are used and in which sequence the time buckets appear in the planning
table.
Procedure
1. Access the activity using one of the following navigation options:
SAP SCM menu Advanced Planning and Optimization  Demand Planning 
Environment  Current settings  Maintain Time Buckets
profile for Demand Planning and Supply Network Planning
Transaction code /SAPAPO/TR30

Time Bucket for Forecasting and Data Cleansing for Annual Business Plan:
History: 24 Months (ZIS_DP_TB_HIS_MONTH)

Number Basic periodicity Periv2 Display
periodicity
Periv1
24 M
M




Future: 15 Months (ZIS_DP_TB_FUTA_MONTH)
Number Basic periodicity Periv2 Display
periodicity
Periv1
15 M
M



Time Bucket for Forecasting and Data Cleansing for 3-Month Rolling Plan:
History: 24 Months (ZIS_DP_TB_HIS_MONTH)
Number Basic periodicity Periv2 Display
periodicity
Periv1
24 M
M
Page


Future: 4 Months (ZIS_DP_TB_FUTM_MONTH)
Number Basic periodicity Periv2 Display
periodicity
Periv1
4 M
M


Future: 4 Months (ZIS_DP_TB_FUTWM) (first 6-8 weeks in weekly buckets and rest in
monthly buckets)
Number Basic periodicity Periv2 Display
periodicity
Periv1
4 M
8 M P IS
P IS


2.15 Setting up the Planning Book
A planning book defines the content and the layout of the interactive planning screen. Planning books
are used in Demand Planning and Supply Network Planning. They allow you to design the screen to
suit individual planning tasks. A planning book is based on a planning area. You can create several
user-specific data views in a planning book. In this step, you create a planning book for Demand
Planning.
Procedure
1. Access the activity using one of the following navigation options:
SAP SCM menu Advanced Planning and Optimization  Demand Planning
 Environment  Current settings  Define Planning Book
Transaction code /SAPAPO/SDP8B

Planning Books and Data Views:
Field name Description User action and values Comment
Planning Book Planning Book
Demand Planning
ZIS_
Planning book text
Planning area Planning Area
Demand Planning
ZIS_DP_PA_DL
Maint. props manually X
Univariate forecast X


Planning Book for Forecasting
This Planning Book will have Characteristics: Customer Segment, Customer, SAP Material
Number and important characteristics of Planning Product.
It will have the following data views:
Data View for KAM Inputs
The following activities will be carried out in this Data View:

Page
Forecast Accuracy Data View for Forecast Accuracy This Data View will be used for
calculating Forecast Accuracy.

Planning Book for SBM Inputs
This Planning Book will have Characteristics: Customer Segment, Customer, Region and
Planning Product.
Data View for SBM Inputs
The following activities will be carried out in this Data View:

This Planning Book will have Characteristics: Customer Segment, Market, and Planning Product.

Data View for TOP & CS Management Inputs
The following activities will be carried out in this Data View:
You need to create a forecast profile to prevent your forecast data from being overwritten.
Univariate forecasting provides methods that allow you to forecast the following time series
patterns, for example, constant demand, trend demand, seasonal demand, and seasonal trend
demand.
1. Access the activity using one of the following navigation options:
SAP SCM menu
Advanced Planning and Optimization  Demand Planning 
Environment  Maintain Forecast Profiles
Transaction code
/SAPAPO/MC96B

2. On the Master Prfl tab page, enter the following values:


2.16 Forecasting Method:
Statistical Models Definition
Forecast Models will be decided after analyzing Historical Data.
2.16.1 Constant model parameters
Master profile
Linked Univariate profile
2.16.2 Trend model parameters
Master profile
Linked Univariate profile:
2.16.3 Trend &Seasonal model parameters
Master profile
Linked Univariate profile:
2.16.4 Forecast Parameters: ,, Υ and  factors
2.17 Creating Macros (SAP APO)
You can use advanced macros to perform complex calculations quickly and easily. Macros are
executed either directly by the user or automatically at a predefined point in time. When defining
advanced macros, you work in a special desktop environment known as the MacroBuilder.
2.17.1 Creating Macros for the Standard View
1. Access the activity using one of the following navigation options:
SAP SCM menu Advanced Planning and Optimization  Demand
Page
Planning  Environment  Current settings  Define
Planning Book
Transaction code /SAPAPO/SDP8B

Macros: To apply Business logics in demand planning
2.18 Assigning User to Planning Book (SAP APO)
You need to assign the default planning book to each DP user. When a planner opens the demand
planning desktop, he or she sees the planning book assigned to them. Note that you can assign
only one planning book to a user.
You can restrict the users’ authorization so that they can only navigate to a specified planning book
or a specific data view.
Procedure
1 Access the activity using one of the following navigation options:
SAP Menu Advanced Planning and Optimization  Demand Planning 
Environment  Current Settings  Assign User to Planning
Book
Transaction code /SAPAPO/SDPPLBK
2.19 Initializing the Planning Area
The purpose of this activity is to initialize the planning area and to create time series objects.
Procedure
1. Access the activity using the following navigation options:
SAP SCM menu
Advanced Planning and Optimization ( Demand Planning (
Environment ( Administration of Demand Planning and
Supply Network Planning
Transaction code /SAPAPO/MSDP_ADMIN
2. Right-click the planning area you created (for example, ZIS_).
3. Choose Create time series objects.
2.20 Creating Selection Profiles for the Planning Book

For your planning process, you need to make a selection that restricts the range of
products and locations. To do this, you create one or more selection profiles.
The demand planner uses the selection profile to quickly access frequently used
selections.
Procedure
1. To access the planning book choose one of the following navigation options:
SAP SCM menu Advanced Planning and Optimization  Demand Planning 
Planning  Interactive Demand Planning
Transaction code /SAPAPO/SDP94
Page
2. In the Planning Book: SAP Standard Demand Planning screen, choose Selection window in the
left screen area.
The Object Selection dialog box is displayed.
2.21 Setting up the Release of the Demand Forecast
2.21.1 Release to SNP
A demand plan is a plan that is free of restrictions. This means, it is created from a
distribution/marketing viewpoint, considering the input from these departments. However, it does
not consider any real production, storage, or transportation capacities. These aspects are
considered during Supply Network Planning. By releasing the demand plan to Supply Network
Planning, the plan can be processed further and decisions about sourcing, deployment and
transportation based on it can be made.
From a technical point of view, you copy the data from the liveCache time series objects into a
forecast category of the liveCache orders.
We recommend that you perform this activity to save the aforementioned settings as a variant. The
variant for releasing the demand plan to SNP is used after the planner has run demand planning
and generated a forecast.
Procedure
1. Access the activity using one of the following navigation options:
SAP SCM menu Advanced Planning and Optimization  Demand
Planning  Planning  Release  Release Demand
Planning to Supply Network Planning
Transaction code /SAPAPO/MC90
2. In the Release to SNP view in the Data source area, make the following entries.
Field name Description User action
and values
Note
Planning
area
ZIS_DP_PA_DL
Planning
version
000 Active version
Key figure Key figure from which
you want to copy the
requirements data.


2.22 Creating an Activity

With this step you define which action takes place, for example, a forecast transfer to the SNP, when you
create and schedule the respective job (see also the next two steps).
Procedure
1. Access the activity using one of the following navigation options:
SAP SCM menu Advanced Planning and Optimization  Demand Planning 
Planning  Demand Planning in the Background  Define
Activities for Mass Processing
Transaction code /SAPAPO/MC8T
Page

2.22.1 Creating a Planning Job

Procedure
1. Access the activity using one of the following navigation options:
SAP SCM menu Advanced Planning and Optimization  Demand Planning
Planning Demand Planning in the Background → Create
Demand Planning in the Background
Transaction code /SAPAPO/MC8D

2.22.2 Scheduling the Planning Job
Procedure
1. Access the activity using one of the following navigation options:
SAP SCM menu Advanced Planning and Optimization  Demand
Planning  Planning  Demand Planning in the
Background  Schedule Demand Planning in the
Background
Transaction code /SAPAPO/MC8G
2. Enter the job name.
3. Choose Program  Execute.
4. In the Start Time dialog box, specify when you wish the job to start running.
5. Choose Save.

2.23 Batch Jobs in Demand Planning:
There are a number of steps that have to run on a daily basis in APO DP to integrate Sales History
received from SAP ECC and to generate order forecast. Forecast models used for each customer
segment and planning product should be different