SAP AG 1

Demand
Pl anni ng
Pr omot i on Pl anni ng,
Dat a Handl i ng,
Mac r os, CBF
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 :
Promotion planning
Data handling
Macros
Characteristic-based forecasting (CBF)
Demand Planning is part of SAP APO
SAP APO is an application of the mySAP SCM solution
Contents:
SAP AG 3
SAP AG 2003
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
Apply the new promotion planning concepts
Use the enhanced data handling capabilities
Work with the new macro workbench
Describe the characteristic-based forecasting
(CBF) improvements
At the conclusion of this unit, you will be able to:
SAP AG 5
SAP AG 2003
Pr omot i on Pl anni ng: Topi c Obj ec t i ves
Apply the new promotion planning concepts:
Promotion base
Promotion reporting
Promotion BAPIs (to connect to CRM)
At the conclusion of this topic, you will be able to:
SAP AG 6
SAP AG 2003
Pr omot i on Base
Requirement
Promotions are defined on different levels. It should
be possible to differentiate between these levels.
Industries
Consumer products
New Solution (SAP APO 4.0)
The new concept is based on a `Promotion base
where a combination of characteristics is defined
(customer and product for example).
The user can define several promotion bases (with
different promotion key figures) so that promotions
can be created on and separated between different
levels.
During assignment of promotion objects, checks will
be made to guarantee consistency of the promotions.
Current Solution (SAP APO 3.1)
Several promotions, using different characteristic
combinations, are assigned to the same promotion
key figure, meaning that the values are mixed and
summed.
Therefore, it can be difficult to assess the impact of
one particular promotion.
SAP AG 7
This example shows the definition of a promotion base
Transaction: /SAPAPO/MP40 - Maintain Promotion Base
SAP AG 2003
Ex ampl e: Cr eat e Pr omot i on Base
SAP AG 8
This example shows how a promotion base is assigned to a promotion and also shows that the
corresponding key figure is selected automatically
Transaction: /SAPAPO/MP34 - Promotion Planning
SAP AG 2003
Ex ampl e: Assi gn Pr omot i on Base t o a Pr omot i on
SAP AG 9
SAP AG 2003
Pr omot i on Repor t i ng
Requirement
It should be possible to report on the existing
promotions.
Industries
Consumer products
New Solution (SAP APO 4.0)
A new reporting tool has been created using the ALV
control. You can now:
Report at both aggregated and detailed level
Show the attributes or select using attributes
Show data within a consistent time axis
Use macros in reporting
Store the reports
Schedule reports in a background job
This report also takes into account the new
`promotion base concept.
Current Solution (SAP APO 3.1)
A simple report is available.
SAP AG 10
This example shows the initial screen for promotion reporting and how to start a report
Transaction: /SAPAPO/MP41 - Maintain Settings for Reporting
SAP AG 2003
Ex ampl e: Pr omot i on Repor t i ng Mai n Vi ew
SAP AG 11
This example shows the general settings for promotion reporting and also shows how to maintain the
detailed reports
Transaction: /SAPAPO/MP41 - Maintain Settings for Reporting
SAP AG 2003
Ex ampl e: Pr omot i on Repor t i ng Gener al Set t i ngs
Maintain detailed report
SAP AG 12
This example shows the detailed reports
Transaction: /SAPAPO/MP41 - Maintain Settings for Reporting
SAP AG 2003
Ex ampl e: Det ai l ed Pr omot i on Repor t s
SAP AG 13
This example shows how to maintain the detailed reports (which drilldown objects are selected)
Transaction: /SAPAPO/MP41 - Maintain Settings for Reporting
SAP AG 2003
Ex ampl e: Mai nt ai n Det ai l ed Pr omot i on Repor t s
SAP AG 14
This example shows the report result
Transaction: /SAPAPO/MP41 - Maintain Settings for Reporting
SAP AG 2003
Ex ampl e: Di spl ay Repor t Resul t s
SAP AG 15
Note that there was a corresponding development in SAP CRM 4.0 to provide the BAPI with data from
there. However, the BAPI in SAP APO offers a generic interface to any other tool or system.
Transaction: BAPI BAPI Explorer
SAP AG 2003
Pr omot i on BAPI s
Requirement
Enable a direct transfer of a campaign created in the
CRM marketing planner to SAP APO promotion
planning.
Industries
Consumer Products
New Solution (SAP APO 4.0)
BAPIs are delivered for SAP APO. mySAP CRM
delivers the interface to provide the BAPI with data
(with SAP CRM 4.0).
BAPI: BAPI_PRMSRVAPS_SAVEMULTI
Creates/changes promotions in SAP APO. If the
promotion is created with an active status, SAP
liveCache is also updated. Once the promotion is
active, it can no longer be changed with the
SaveMultiple method.
Cannibalization groups and attributes have to exist in
SAP APO.
BAPI: BAPI_PRMSRVAPS_DELMULTI
Deletes promotions. If the promotion is active, the
BAPI also deletes SAP liveCache data.
BAPI: BAPI_PRMSRVAPS_GETLIST
Reads data of promotions.
Current Solution (SAP APO 3.1)
Campaigns created in SAP CRM are stored in SAP BW
From there the values (key figures) can be transferred
to SAP APO DP.
Constraint: The campaign/promotion object is not
transferred, only the values.
SAP AG 16
SAP AG 2003
Dat a Handl i ng: Topi c Obj ec t i ves
Use the enhanced data handling capabilities:
Memory usage reduction in SAP liveCache
Realignment redesign
Characteristic combination deletion
Disaggregate fixing information
Use of parallel processes
Redesign of modeling DP BOM relationships
New average calculation type
At the conclusion of this topic, you will be able to:
SAP AG 17
SAP AG 2003
Reduc i ng Memor y Usage i n SAP l i veCac he
Requirement
Hardware for SAP liveCache is expensive. Therefore,
the required space should be minimal.
Industries
All
New Solution (SAP APO 4.0)
The horizons for allocating SAP liveCache space can
be defined on a key-figure-specific basis.
The expected reduction of allocated SAP liveCache
space is often > 50%.
Current Solution (SAP APO 3.1)
SAP liveCache space is allocated for all key figures of
a planning area and version for the same horizon.
If there is only a relatively small amount of data for a
time series, the data is stored in a specific
(compressed) way that results in a reduced memory
requirement. However, this approach is not applicable
for the majority of the key figures.
SAP AG 18
This example shows how to maintain horizons dependent on key figures
Transaction: /SAPAPO/MSDP_ADMIN - Administration of Demand Planning and Supply Network
Planning
SAP AG 2003
Ex ampl e: Mai nt ai ni ng Key-Fi gur e-Spec i f i c Hor i zons
SAP AG 19
SAP AG 2003
Real i gnment Redesi gn
Requirement
Enhance realignment functionality.
Industries
All
New Solution (SAP APO 4.0)
Realignment and copy functionalities are separated:
Realignment based on the planning object structure
Copy based on the planning area
User friendly error handling
User friendly log (success or error messages)
User friendly interface for maintenance
Additional options for a copy/realignment step:
State: New state draft
Proportion: Target value is x% of the source value
Validity date: Step is valid from date y on
Menu entry: DP -> Environment -> Data Administration
-> Data Realignment (transaction:
/SAPAPO/RLGCOPY)
Generated selection variants (used for alerts, forecast
profiles and orders with consumption group
information) are considered and changed during the
realignment run, but already existing generated
selections are not overwritten.
Direct access to the realignment step screens from
the interchangeability application.
Current Solution (SAP APO 3.1)
The realignment table and report is based on a
planning area and not on the planning object
structure. Problems occur if the planning object
structure is linked to more than one planning area.
Mixing of copy and realignment functionalities
Unusable log (success or error messages)
Poor user interface for defining realignment steps
Gaps: Selections, alerts, consumption group
SAP AG 20
All planning areas linked to the actual planning object structures are determined
All existing planning versions for the linked planning area(s) are determined
The realignment process for liveCache time series data, promotions, selections, and notes is then
performed automatically for all the planning area/planning version combinations.
The realignment process is completed for all planning areas that are linked to the planning object structure
and for all relevant planning versions
It is not possible to restrict the process to specific planning areas or planning versions, nor is it possible to
realign data from one planning version to another planning version
Transaction: /SAPAPO/RLGCOPY - Data Realignment
SAP AG 2003
Ex ampl e: Real i gnment
The realignment report executes the
realignment steps based on the entries
in the corresponding realignment
table. Only records with state and a
validity date on or before the current
day will be processed.
A variant for the realignment report
can be defined and run in the
background.
Promotions are considered during
realignment if the source combination
is deleted.
Notes are considered during
realignment, but already existing notes
for the target combinations are not
overwritten
SAP AG 21
liveCache time series and InfoCube data cannot be copied within the copy process.
From a source characteristic combination to another already existing characteristic combination. This can
be done on the most detailed level and also on the persistent aggregate level.
Within the same planning area/InfoCube.
Within the same planning version or between different planning version.
No characteristic combinations can be created/deleted (all target characteristic combinations must exist).
Transaction: /SAPAPO/RLGCOPY - Data Realignment
SAP AG 2003
Ex ampl e: Copy
The copy report executes the copy
steps based on the entries of the
corresponding copy table. Only
records with state and a validity date
on or before the actual day are
processed.
The copy report has an obligatory
input field for the planning area.
You can select one or more planning
versions
From and to date must be entered to
restrict the horizon
You can select one or more InfoCubes
Promotions are not considered during
the copy process.
Notes are considered during the copy
process, but already existing notes for
the target combinations are not
overwritten.
SAP AG 22
This example shows administration for the realignment and copy job logs
Transaction: /SAPAPO/RLGCOPY - Data Realignment
SAP AG 2003
Ex ampl e: Real i gnment /Copy: J ob Logs
Log messages are written to a log database
table. This means that you can see the logs at
any time and run statistics.
Log messages are organized in categories:
Error, Warning, Success
It is also possible to delete the content of the
log table according to user-defined criteria or
selections.
SAP AG 23
SAP AG 2003
Del et i on of Char ac t er i st i c Combi nat i ons
New Solution (SAP APO 4.0)
Characteristic combinations of a master planning
object structure can be deleted by choosing them
from a list.
Requirement
Deletion of characteristic combinations should be
easy.
Industries
All
Current Solution (SAP APO 3.1)
Characteristic combinations of a master planning
object structure can be deleted using the following
selections:
One characteristic combination
All characteristic combinations at aggregated level
All characteristic combinations of the master
planning object structure.
SAP AG 24
This example shows the new button for starting this functionality
Transaction: /SAPAPO/MC62 - Maintain Characteristic Values
SAP AG 2003
Ex ampl e: Mai nt ai n Char ac t er i st i c Combi nat i ons
SAP AG 25
This example shows a list of characteristic combinations with some rows selected. If you choose the
highlighted button, these lines will be deleted.
Transaction: /SAPAPO/MC62 - Maintain Characteristic Values
SAP AG 2003
Ex ampl e: Del et e Char ac t er i st i c Combi nat i ons f r om
Li st
SAP AG 26
SAP AG 2003
Di saggr egat i on of Fi x i ng I nf or mat i on
Requirement
Since users typically want to save fixing information
at an aggregate level, they create persistent
aggregates at all levels where they want to fix data.
However, using many persistent aggregates
negatively affects performance and memory.
Therefore, the requirement is to preserve fixing
information at aggregate level without creating
persistent aggregates.
Industries
All
New Solution (SAP APO 4.0)
Fixing information can now be disaggregated to
detailed level to preserve fixing information at
aggregate level without creating persistent
aggregates. When data is accessed at aggregated
level, the fixed values of the underlying details are
aggregated and are displayed as fixed values at
aggregate level.
With this solution, the fixing information for non-
persistent aggregates only exists at the most detailed
level.
Current Solution (SAP APO 3.1)
Fixing of data is only possible at the most detailed
planning level, or at the level of persistent (non-
temporary) aggregates.
SAP AG 27
SAP AG 2003
Use of Par al l el Pr oc esses
Requirement
Performance: The creation of time series objects (for
a planning area) can negatively affect performance if
there is a large data volume, especially in an initial
run.
Industries
All
New Solution (SAP APO 4.0)
The creation of time series objects for initialization
and delta update can be run in parallel.
Report /SAPAPO/TS_PAREA_PARALPROC_SET has
the following settings:
Number of combinations in a block
Minimum number of combinations
Maximum number of work processes
Current Solution (SAP APO 3.1)
The time series objects are created by using one work
process only.
SAP AG 28
SAP AG 2003
Redesi gn of DP BOM Rel at i onshi p Model i ng
Requirement
It should be possible to set different values for the
free characteristics ( location or brand for instance) in
dependent characteristic combinations.
With this enhancement, it will be possible to define
different characteristics for the output and input
products of one PPM.
Industries
All
New Solution (SAP APO 4.0)
The free characteristics of dependent characteristic
combinations can be different.
Two new characteristics have been introduced:
9ABOMID: Used to ensure the classification of
dependent characteristic combinations.
9ABOMIO: Can be used to restrict the selection to
the output products in interactive
planning.
It is no longer necessary to read master
data (PPMs) after all the characteristic
combinations have been created.
Free characteristics can only be modified by
implementing the COMBI_ENRICH method of BAdI:
/SAPAPO/SDP_MASTER.
All dependent characteristic combinations are deleted
when users try to delete a single characteristic
combination.
Current Solution (SAP APO 3.1)
The free characteristics of dependent characteristic
combinations must be identical.
SAP AG 29
The new calculation method can be assigned when defining key figures in a planning area
SAP AG 2003
New Aver age Cal c ul at i on Type
Requirement
Calculation of average values over several
aggregation levels.
Industries
All
Current Solution (SAP APO 3.1)
The average is calculated based on the next
aggregation level down.
0 0
0
100
100
50
New Solution (SAP APO 4.0)
A new calculation method has been added that
calculates the average based on the most detailed
level.
0 0
0
100
100
33
SAP AG 30
SAP AG 2003
Mac r os : Topi c Obj ec t i ves
Work with the new macro workbench
Features of the macro workbench
Semantic checks
At the conclusion of this topic, you will be able to:
SAP AG 31
SAP AG 2003
Mac r o Wor k benc h
Requirement
Macros should be handled on one screen.
Industries
All
New Solution (SAP APO 4.0)
A macro workbench is available where you can do the
following:
Copy macros from one macro book to another.
Delete macros books.
Add macro books to transport requests.
Filter macro book display by name, author,
creation date, last changed by, SNP/DP.
Display your own macros books.
Maintain default values for the parameters of a
macro such as direct/no direct execution of the
macro, no confirmation prompt, and so on.
Run a semantic check on different macro books
or individual macros of a macro book.
Current Solution (SAP APO 3.1)
The initial screen of the MacroBuilder is very simple.
The user can only choose a macro book name that is
usually the name of a planning book/data view.
SAP AG 32
This example shows the new Macro Workbench with some of its functions
Transaction: /SAPAPO/ADVM - Macro Workbench
SAP AG 2003
Ex ampl e: Mac r o Wor k benc h Feat ur es
SAP AG 33
SAP AG 2003
Semant i c Chec k f or Mac r os
Requirement
A high percentage of problems related to the macro
area are caused by semantic errors.
Prepared macro structures may be syntactically
correct, but the usage of these macro functions and
execution settings may not bring the expected results
at the end.
Industries
All
New Solution (SAP APO 4.0)
Semantic check will be triggered in the MacroBuilder
with the help of buttons and right-click menu items.
Semantic check runs on several levels, such as:
Planning book/data view, macro, macro step, and
macro step argument.
Results are displayed in a list. Warning messages are
automatically corrected.
Semantic check is easily expandable.
Current Solution (SAP APO 3.1)
The MacroBuilder offers a syntax check only.
SAP AG 34
This example shows a semantic check log
It provides recommendations about how to improve the macro
Transaction: /SAPAPO/ADVM - Macro Workbench
SAP AG 2003
Ex ampl e: Resul t s of Semant i c Chec k s
SAP AG 35
SAP AG 2003
CBF: Topi c Obj ec t i ves
Describe the characteristic-based forecasting
(CBF) improvements:
Planning and consumption of configured
products
Drilldown
At the conclusion of this topic, you will be able to:
SAP AG 36
SAP AG 2003
Pl anni ng and Consumpt i on of Conf i gur ed Pr oduc t s
Requirement
To all configured products to be planned (CDP and
IBASE).
Industries
All
Especially: Discrete, Automotive
New Solution (SAP APO 4.0)
You can now plan configured products and
assemblies at finished product level.
Furthermore, incoming sales orders for finished
products will consume the planned quantities.
The release functionality between DP and SNP is
enhanced (using a consumption group).
Consumption will be based on the characteristics-
based forecast for the configured products and the
corresponding dependent requirements.
Current Solution (SAP APO 3.1)
CBF is already offered as part of Demand Planning. It
allows you to plan configurable products, but not
configured finished products and assemblies.
It is not possible to generate configured orders (CDP
orders) or configured orders for the IBASE explosion
of the iPPE.
It is not possible for configured sales orders to
consume forecasts for configured products.
SAP AG 37
SAP AG 2003
Dr i l l dow n i n CBF
Requirement
Drilldown functionality for CBF and non-CBF
characteristics.
Industries
All
New Solution (SAP APO 4.0)
Drilldown is possible for CBF and non-CBF (free)
characteristics with a possible combination of free
and CBF characteristics.
Current Solution (SAP APO 3.1)
Drilldown is possible for CBF characteristics only.
SAP AG 38
SAP AG 2003
Demand Pl anni ng: Uni t Summar y
You are now able to:
Apply the new promotion planning concepts
Use the enhanced data handling capabilities
Work with the new macro workbench
Describe the characteristic-based forecasting
(CBF) improvements