Anda di halaman 1dari 31

SAP AG 1

Demand
Pl anni ng
I nt er ac t i ve Pl anni ng
& For ec ast i ng
Product Management GBU SCM, SAP AG
SAP AG 2
SAP AG 2003
Demand Pl anni ng
This session includes the following parts of the Demand
Planning scenario:
Interactive planning
Forecasting
Lifecycle planning
Demand Planning is part of SAP APO
SAP APO is an application of the mySAP SCM solution
Contents:
SAP AG 3
SAP AG 2003
The Demand Pl anni ng Pr oc ess
Final demand plan
Data
preparation
Data
preparation
Historical data
C
O
L
L
A
B
O
R
A
T
I
O
N
S
I
M
U
L
A
T
I
O
N
Data analysis
& adaptation
Data analysis
& adaptation
Forecasting &
lifecycle management
Forecasting &
lifecycle management
Promotion
planning
Promotion
planning
INTERACTIVE PLANNING
BATCH PROCESSING & MANAGEMENT BY EXCEPTION
Data transfer
Data transfer
SAP AG 4
SAP AG 2003
Uni t Obj ec t i ves
Use the new interactive planning features
Describe the forecasting enhancements
Perform improved lifecycle planning
At the conclusion of this unit, you will be able to:
SAP AG 5
SAP AG 2003
I nt er ac t i ve Demand Pl anni ng: Topi c Obj ec t i ves
Use the new interactive planning features:
Key figure selection
Copy & Paste
Data export
Paging on Web
At the conclusion of this topic, you will be able to:
SAP AG 6
SAP AG 2003
Key Fi gur e Sel ec t i on
Requirement
A data view in a planning book shows several pre-
defined key figures. To enable a more focused
analysis, it should be possible to restrict the amount
of key figures displayed.
New Solution (SAP APO 4.0)
In addition to the existing solution, the user can
directly select multiple key figures from a list.
This functionality is available on both (upper & lower)
tables.
Current Solution (SAP APO 3.1)
The user can select:
All key figures
One key figure (if this is done several times, a
reduced view can be created).
This functionality is available on the upper table only.
Industries
All
SAP AG 7
The `Multiple key figures option has been added
The dialog box allows you to choose the required key figures easily
Functional in both the upper and lower table
Transaction: /SAPAPO/SDP94 - Interactive Demand Planning
SAP AG 2003
Ex ampl e: Sel ec t Key Fi gur es on Upper Tabl e
SAP AG 8
Copy, cut, and paste using the right-hand mouse button is not supported
SAP AG 2003
Copy/Past e
Requirement
To support the planners daily tasks, it should be easy
to transfer individual pieces of data and blocks of data
by using a simple copy and paste function.
Industries
All
New Solution (SAP APO 4.0)
A copy, cut, and paste functionality is offered:
Inside the SAP APO table
From the SAP APO table to Excel
From Excel into the SAP APO table
To copy and paste, choose the following key
combinations: CTRL + C for copy, CTRL + X for cut,
CTRL + V for paste.
Current Solution (SAP APO 3.1)
No solution (only complete export from the SAP APO
table).
SAP AG 9
This example shows a copy from EXCEL to SAP APO
Approach this function with caution because there are no plausibility checks and no undo function
This function can also be used for SNP planning books and data views
Transaction: /SAPAPO/SDP94 - Interactive Demand Planning
SAP AG 2003
Ex ampl e: Copy/Past e f r om EXCEL t o SAP APO Tabl e
SAP AG 10
SAP AG 2003
Ex por t i ng f r om Pl anni ng Book s
Requirement
There should be a data export functionality for offline
work and external data manipulation.
Industries
All
New Solution (SAP APO 4.0)
The interactive planning table is loaded into a local
ASCII file (.CSV) that includes a pivot sorting
operation and switching of columns and rows.
This is enabled by triggering the export from the front
end.
Current Solution (SAP APO 3.1)
The current export functionality has some constraints:
Pivot sorting and columns/row switching options are
not taken into consideration.
Reason: Export is triggered from the application
without taking into consideration front-end
manipulations.
Thus, the layout of the Excel file does not correspond
to the layout of the SAP APO table after pivot sorting
or switching columns and rows.
SAP AG 11
This example shows the export of an SAP APO table with pivot sorting and switching of columns and
rows.
Note that the structure is identical in both SAP APO and EXCEL.
Transaction: /SAPAPO/SDP94 - Interactive Demand Planning
SAP AG 2003
Ex ampl e: Ex por t i ng f r om Pl anni ng Book s
SAP AG 12
SAP AG 2003
Pagi ng f or Web Col l abor at i on
Requirement
There should be a typical Internet paging functionality
to divide large data sets into smaller sets that fit on
one screen.
Industries
All
New Solution (SAP APO 4.0)
There is now a paging function for the data table in
net-enabled Collaborative Supply and Demand
Planning (ITS-Service: CLPSDP). It enables huge data
table to be divided into smaller data blocks.
Prevents performance problems and can prevent the
ITS from hanging.
Current Solution (SAP APO 3.1)
Collaborative planning shows all selected data in one
table.
SAP AG 13
If user parameter /SAPAPO/CLP_DRILLROW is set when the user drills down to a disaggregated data
level in Collaborated Supply and Demand Planning, the paging functionality will be active and the data
table will be divided by the number of rows set in this user parameter.
User parameter /SAPAPO/CLP_REPHEAD (the user parameter that is used to repeat the header data after
each object key figure or characteristic value depends on the pivot function in collaboration see note
385222) cannot be used together with /SAPAPO/CLP_DRILLROW. If both parameters are set together,
only /SAPAPO/CLP_DRILLROW is taken into consideration and /SAPAPO/CLP_REPHEAD will be
ignored. /SAPAPO/CLP_REPHEAD can only be used if no value is set for /SAPAPO/CLP_DRILLROW.
Transaction: SU3 - Maintain User Profile
SAP AG 2003
Ex ampl e: User Par amet er s f or t he Web
New user parameter
to define the number
of rows to be shown
SAP AG 14
This example shows the new paging buttons and the influence of the user parameter on the number of
rows shown.
Transaction: /SAPAPO/CLPISDP - Collaborative Demand Planning
SAP AG 2003
Ex ampl e: Pagi ng Func t i onal i t y i n t he Web
Paging buttons
Since the user parameter is set to a
maximum of 10 lines, only 8 lines are shown
SAP AG 15
SAP AG 2003
For ec ast i ng: Topi c Obj ec t i ves
Describe the following forecasting enhancements:
Univariate forecasting
Graphic of univariate forecasting
Automatic model selection
Composite forecasting
Forecast profile assignment
At the conclusion of this topic, you will be able to:
SAP AG 16
Note: BADIs for forecast parameters:
SAPAPO/SDP_FCSTPARA (SAP APO 3.x)
SAPAPO/SCM_FCSTPARA (SAP APO 4.0)
SAP AG 2003
Requirement
a) Decimal places should not be omitted but taken
into consideration.
b) The Croston forecast method should generate a
sporadic forecast.
c) Automatic Alpha adaptation should be improved.
Industries
All
New Solution (SAP APO 4.0)
a) The new `Add up decimal places indicator has
been added to the control parameters of the
univariate forecast profile.
b) The new `Generate sporadic forecast indicator has
been added to the control parameters of the
univariate forecast profile if the Croston method is
selected.
If this indicator is set, the system distributes the
demand intermittently based on the average
interval between buckets with historical demand.
This functionality is available in SAP APO 3.x
through a BAdI.
c) The `Error Measure field has been added to the
model parameters of the univariate forecast profile
if the constant model with alpha adaptation
(method 12) is selected.
It allows a (customer-specific) error measure to be
selected. In this case, automatic model selection 2
is performed.
There is a modification note (number: 572125) for
SAP APO 3.x.
Current solution (APO 3.1)
a) Decimal places are omitted.
b) The forecast is distributed equally among all the
time buckets in the forecast period (a constant
forecast).
c) The current Alpha adaptation often leads to results
that are not useful.
Uni var i at e For ec ast i ng
SAP AG 17
SAP AG 2003
Gr aphi c f or Uni var i at e For ec ast i ng
Requirement
Enhancements of the graphic on univariate forecast
screen.
Industries
All
New Solution (SAP APO 4.0)
The following enhancements have been developed:
Axis format information can be saved.
Graphic change of a single data point (similar to a
graphic on the interactive planning screen).
Smoothing of the changed single point. The user
can specify an alpha factor to be used (similar to
exponential smoothing).
Creation of a trend curve (calculated by linear
regression) or any line defined by a BAdI
implementation through a marked curve.
Current Solution (SAP APO 3.1)
Graphic function during forecasting is only a display
functionality.
It is not possible to store axis format information.
SAP AG 18
This example shows the new settings dialog box. To find this on the forecast screen, go to: Edit -> Graphic
Settings
SAP AG 2003
Ex ampl e: Gr aphi c Set t i ngs
SAP AG 19
This example shows the new smoothing functionality
SAP AG 2003
Ex ampl e: Smoot hi ng of Manual Changes
Without smoothing
With smoothing
SAP AG 20
This example shows the trend curve
The BAdI `FAHMI1 is an internal example and is not delivered to customers, it does however show how
a customer specific solution is integrated.
SAP AG 2003
Ex ampl e: Cr eat i ng a Tr end Cur ve
BADI
Original data (blue
line) disappears and
is overwritten by
trend curve (red line)
SAP AG 21
Automatic model selection is forecasting strategy 56
Note: The test for sporadic is also available through a BAdI for SAP APO 3.x.
SAP AG 2003
Requirement
a) It should be possible to select different error
measures.
b) The seasonal length is sometimes not known and
should be identified.
c) Additional test for sporadic history.
d) Additional test for white noise.
Industries
All
New Solution (SAP APO 4.0)
a) The `Error Measure field has been added to the
model parameters of the univariate forecast profile
if automatic model selection 2 is selected.
It allows a (customer-specific) error measure to be
selected.
b) The `Variation Length field has been added to the
model parameters of the univariate forecast profile
if automatic model selection 2 is selected.
A seasonal length test is performed. This test
considers the specified length and the variation.
c) A sporadic history test has been added. This test
assigns the Croston method if the ratio of historical
periods with a 0 demand > 66%.
d) A test for white noise has been added. This test
assigns a constant method.
Current Solution (SAP APO 3.1)
a) MAD is used as the error measure
b) The seasonal length is used as specified.
c+d) No solution
Aut omat i c Model Sel ec t i on
SAP AG 22
SAP AG 2003
Requirement
a) You should be given the option of selecting the
method with lowest forecast error as an alternative
to pick-the-best.
b) Forecasts with errors should not be considered.
Industries
All
New Solution (SAP APO 4.0)
a) The user can define a mode specifying the error
measure to be considered. The user can also use a
self-defined error measure.
b) The user can set an indicator to exclude the
forecasts from the calculation. The proportion that
was intended for this profile is distributed among
the other individual profiles.
If errors occur in all profiles despite this indicator
being set for them all, the forecast terminates and
an error message is issued.
Current Solution (SAP APO 3.1)
No solution available.
Composi t e For ec ast i ng
SAP AG 23
This example shows the new composite forecast profile enhancements:
You can select a mode/method
There is a new indicator for excluding forecasts from the calculation
Transaction: /SAPAPO/MC96B - Maintain Forecast Profiles
SAP AG 2003
Ex ampl e: Composi t e For ec ast Pr of i l e
SAP AG 24
SAP AG 2003
Requirement
To avoid unnecessary complexity, assignments for
high level selections should also be used
automatically for more detailed selections.
Industries
All
New Solution (SAP APO 4.0)
A new indicator called `Also similar selections has
been added to the assign forecast profile screen.
The system uses this profile assignment for all
subordinate selections. For example, if the selection
is PRODUCT = P1, the profile for this selection is also
used for PRODUCT =P1, LOCATION = L1.
It is also possible to specify more detailed
assignments to other profiles without invalidating the
more generic assignment.
Current solution (SAP APO 3.1)
No solution available.
For ec ast Pr of i l e Assi gnment
SAP AG 25
SAP AG 2003
Li f ec yc l e Pl anni ng: Topi c Obj ec t i ves
Perform improved lifecycle planning
Like modeling with alternative characteristics
Aggregated lifecycle planning
At the conclusion of this topic, you will be able to:
SAP AG 26
Like modeling assigns historical data from corresponding SKUs to new products
Phase-in and phase-out profiles manipulate the increase and decrease of the forecasts and model lifecycle
curves
SAP AG 2003
Pr of i l es Used f or Li f ec yc l e Pl anni ng
Actuals for old product
Forecast for new product
Lifecycle
Like modeling
Phase-in profile Phase-out profile
SAP AG 27
Report /SAPAPO/RMDP_FCST_LC_UPGRADE supports the upgrade of all existing lifecycle profiles in
SAP APO 3.x. See note 588986.
SAP AG 2003
Requirement
You should have the option of using the historical
data of other characteristic combinations to
forecast a new product for instance.
Industries
All
New Solution (SAP APO 4.0)
Like profiles can be defined for another characteristic;
the same product in another location for instance.
Current Solution (SAP APO 3.1)
Only one characteristic (usually the product) is
considered, which means that other products in the
same location can be used.
Li k e Model i ng w i t h Al t er nat i ve Char ac t er i st i c s
SAP AG 28
This example shows the like modeling with an alternative location.
There is a new transaction: /SAPAPO/MSDP_FCST1 - Lifecycle Planning
SAP AG 2003
Ex ampl e: Li k e Model i ng Usi ng Al t er nat i ve Loc at i ons
SAP AG 29
Note: Report /SAPAPO/RMDP_FCST_LC_UPGRADE supports the upgrade of all existing lifecycle
profiles in SAP APO 3.x. See note 588986.
SAP AG 2003
Aggr egat ed Li f ec yc l e Pl anni ng
Requirement
Lifecycle profiles (like, phase-in, phase-out) defined
on a detailed level should be taken into consideration
during forecasting at aggregated level.
Industries
All
New Solution (SAP APO 4.0)
The assignments of all lifecycle profiles (like, phase-
in, phase-out) are also taken into account at
aggregated level. This function is activated by two
indicators in the basic settings.
Current Solution (SAP APO 3.1)
Assignment of lifecycle profiles is taken into
consideration when the forecast is performed at a
basic settings level or lower.
SAP AG 30
This example shows the two indicators for activating the new function.
A new transaction is available: /SAPAPO/MSDP_FCST1 - Lifecycle Planning
SAP AG 2003
Ex ampl e: Aggr egat ed Li f ec yc l e Pl anni ng Set t i ngs
SAP AG 31
SAP AG 2003
Demand Pl anni ng: Uni t Summar y
You are now able to:
Use the new interactive planning features
Describe the forecasting enhancements
Perform aggregated lifecycle planning