dp promotion plng, data handling, macros,cbf 4.0

8/13/2019 DP Promotion Plng, Data Handling, Macros,CBF 4.0

1/38

SAP AG 1

DemandPlanning

Promotion Planning,Data Handling,Macros, CBF

Product Management GBU SCM, SAP AG


2/38

SAP AG 2

SAP AG 2003

Demand Planning

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:


3/38

SAP AG 3

SAP AG 2003

Demand Planning Process

Final demand plan

Data

preparation

Data

preparation

Historical data

C

O

L

L

A

B

O

R

A

T

I

ON

S

I

M

U

L

A

T

I

O

N

Data analysis

& adaptation

Data analysis

& adaptation

Forecasting &

lifecycle management

Forecasting &

lifecycle management

Promotionplanning

Promotion

planning

INTERACTIVE PLANNING

BATCH PROCESSING & MANAGEMENT BY EXCEPTION

Data transferData transfer


4/38

SAP AG 4

SAP AG 2003

Unit Objectives

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:


5/38

SAP AG 5

SAP AG 2003

Promotion Planning: Topic Objectives

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:


6/38

SAP AG 6

SAP AG 2003

Promotion 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 basewhere a combination of characteristics is defined

(customer and product for example).

The user can define several promotion bases (withdifferent promotion key figures) so that promotionscan be created on and separated between differentlevels.

During assignment of promotion objects, checks willbe 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 andsummed.

Therefore, it can be difficult to assess the impact of

one particular promotion.


7/38

SAP AG 7

This example shows the definition of a promotion base

Transaction: /SAPAPO/MP40 - Maintain Promotion Base

SAP AG 2003

Example: Create Promotion Base


8/38

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

Example: Assign Promotion Base to a Promotion


9/38

SAP AG 9

SAP AG 2003

Promotion Reporting

Requirement

It should be possible to report on the existing

promotions.

Industries

Consumer products


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.


A simple report is available.


10/38

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

Example: Promotion Reporting Main View


11/38

SAP AG 11

This example shows the general settings for promotion reporting and also shows how to maintain the

detailed reports


SAP AG 2003

Example: Promotion Reporting General Settings

Maintain detailed report


12/38


13/38

SAP AG 13

This example shows how to maintain the detailed reports (which drilldown objects are selected)


SAP AG 2003

Example: Maintain Detailed Promotion Reports


14/38

SAP AG 14

This example shows the report result


SAP AG 2003

Example: Display Report Results


15/38

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

Promotion BAPIs

Requirement

Enable a direct transfer of a campaign created in the

CRM marketing planner to SAP APO promotion

planning.

Industries

Consumer Products


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.


Campaigns created in SAP CRM are stored in SAP BWFrom there the values (key figures) can be transferred

to SAP APO DP.

Constraint: The campaign/promotion object is not

transferred, only the values.


16/38

SAP AG 16

SAP AG 2003

Data Handling: Topic Objectives

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



17/38

SAP AG 17

SAP AG 2003

Reducing Memory Usage in SAP liveCache

Requirement

Hardware for SAP liveCache is expensive. Therefore,

the required space should be minimal.

Industries

All


The horizons for allocating SAP liveCache space can

be defined on a key-figure-specific basis.

The expected reduction of allocated SAP liveCachespace is often > 50%.


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.


18/38

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

Example: Maintaining Key-Figure-Specific Horizons


19/38

SAP AG 19

SAP AG 2003

Realignment Redesign

Requirement

Enhance realignment functionality.

Industries

All


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, forecastprofiles and orders with consumption groupinformation) are considered and changed during therealignment run, but already existing generatedselections are not overwritten.

Direct access to the realignment step screens fromthe interchangeability application.


The realignment table and report is based on a

planning area and not on the planning objectstructure. 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


20/38

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

Example: Realignment

The realignment report executes the

realignment steps based on the entriesin 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


21/38

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).


SAP AG 2003

Example: 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 areprocessed.

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.


22/38

SAP AG 22

This example shows administration for the realignment and copy job logs


SAP AG 2003

Example: Realignment/Copy: Job 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.


23/38

SAP AG 23

SAP AG 2003

Deletion of Characteristic Combinations


Characteristic combinations of a master planningobject structure can be deleted by choosing them

from a list.

Requirement

Deletion of characteristic combinations should be

easy.

Industries

All


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.


24/38

SAP AG 24

This example shows the new button for starting this functionality

Transaction: /SAPAPO/MC62 - Maintain Characteristic Values

SAP AG 2003

Example: Maintain Characteristic Combinations


25/38

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

Example: Delete Characteristic Combinations fromList


26/38

SAP AG 26

SAP AG 2003

Disaggregation of Fixing Information

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


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 areaggregated 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.


Fixing of data is only possible at the most detailed

planning level, or at the level of persistent (non-

temporary) aggregates.


27/38

SAP AG 27

SAP AG 2003

Use of Parallel Processes

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 initialrun.

Industries

All


The creation of time series objects for initialization

and delta update can be run in parallel.

Report /SAPAPO/TS_PAREA_PARALPROC_SET hasthe following settings:

Number of combinations in a block

Minimum number of combinations

Maximum number of work processes


The time series objects are created by using one work

process only.


28/38

SAP AG 28

SAP AG 2003

Redesign of DP BOM Relationship Modeling

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


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 masterdata (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.


The free characteristics of dependent characteristic

combinations must be identical.


29/38

SAP AG 29

The new calculation method can be assigned when defining key figures in a planning area

SAP AG 2003

New Average Calculation Type

Requirement

Calculation of average values over several

aggregation levels.

Industries

All


The average is calculated based on the next

aggregation level down.

0 0

0

100

100

50


A new calculation method has been added thatcalculates the average based on the most detailed

level.

0 0

0

100

100

33


30/38

SAP AG 30

SAP AG 2003

Macros : Topic Objectives


Features of the macro workbench

Semantic checks



31/38

SAP AG 31

SAP AG 2003

Macro Workbench

Requirement

Macros should be handled on one screen.

Industries

All


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.


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.


32/38

SAP AG 32

This example shows the new Macro Workbench with some of its functions

Transaction: /SAPAPO/ADVM - Macro Workbench

SAP AG 2003

Example: Macro Workbench Features


33/38

SAP AG 33

SAP AG 2003

Semantic Check for Macros

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


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.


The MacroBuilder offers a syntax check only.


34/38

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

Example: Results of Semantic Checks


35/38

SAP AG 35

SAP AG 2003

CBF: Topic Objectives


(CBF) improvements:

Planning and consumption of configured

products

Drilldown



36/38

SAP AG 36

SAP AG 2003

Planning and Consumption of Configured Products

Requirement

To all configured products to be planned (CDP and

IBASE).

Industries

All

Especially: Discrete, Automotive


You can now plan configured products and

assemblies at finished product level.

Furthermore, incoming sales orders for finishedproducts 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.


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.


37/38

SAP AG 37

SAP AG 2003

Drilldown in CBF

Requirement

Drilldown functionality for CBF and non-CBF

characteristics.

Industries

All


Drilldown is possible for CBF and non-CBF (free)characteristics with a possible combination of free

and CBF characteristics.


Drilldown is possible for CBF characteristics only.


38/38

SAP AG 2003

Demand Planning: Unit Summary

You are now able to:

Apply the new promotion planning concepts

Use the enhanced data handling capabilities



(CBF) improvements

dp promotion plng, data handling, macros,cbf 4.0

Documents