apo dp_configguide_en_de[1]

46
8/2/2019 APO DP_ConfigGuide_EN_DE[1] http://slidepdf.com/reader/full/apo-dpconfigguideende1 1/46 SAP SCM 5.0 November 2007 English Building Block DPL Demand Planning SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany Building Block Configuration Guide

Upload: kevinwu64

Post on 05-Apr-2018

216 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 1/46

SAP SCM 5.0

November 2007

English

Building BlockDPL Demand Planning

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

Building Block Configuration Guide

Page 2: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 2/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

Copyright

© Copyright 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress 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 componentsof other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, Systemz, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER,

POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBMCorporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

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 of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web

Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology inventedand implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAPproducts and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP AG in Germany and in several other countries all over the world. All other product andservice names mentioned are the trademarks of their respective companies. Data contained in thisdocument 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 itsaffiliated 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 materials. The onlywarranties for SAP Group products and services are those that are set forth in the express warrantystatements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.

© SAP AG Page 2 of 46

Page 3: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 3/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

Icons

Icon Meaning

Caution

Example

Note or Tip

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include fieldnames, screen titles, pushbuttons as well as menu names, paths andoptions.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, programnames, transaction codes, table names, and individual key words of aprogramming language, when surrounded by body text, for example,SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths,messages, source code, names of variables and parameters as well asnames of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2 ) or theENTER key.

Example text Exact user entry. These are words or characters that you enter in thesystem exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace thesewords and characters with appropriate entries.

© SAP AG Page 3 of 46

Page 4: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 4/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

Contents

1 Preparation ........................ ........................... ........................... ........................... .......... ...... ...... .. 5

1.1 Prerequisites ....................... ........................... ........................... .................... ....... ...... ...... .... 51.2 SAP Notes Building Block Demand Planning ............. ........................... .................... ....... .... 5

2 Setting up APO BW ....................... ........................... ........................... ........................... ............. 6

2.1 Creating the Source System (APO BW) ......................... ............................................. .......... 6

2.2 Setting up the Info Source (APO BW) ........................ ........................... .................... ...... ...... 7

2.3 Setting up Info Area (APO BW) .......................... ........................... ........................... ............. 9

2.4 Setting up the Info Cube (APO BW) ........................................ .......................................... .. 10

2.4.1 Creating the Update Rules ........................ ........................... ........................ ...... ...... .... 11

2.5 Creating the Infopackage .......................... ........................... ........................... ................ .... 13

3 Setting up the Demand Planning Book ........................... ........................... .................... ...... ...... 14

3.1 Maintaining Periodicities for Planning Area ............... ........................................ .... ............. . 14

3.2 Activating the Planning Object Structure ........................................ ..................................... 15

3.3 Setting up the Planning Area .......................... ........................... ..................... ...... ...... ....... . 15

3.4 Maintaining the Time Buckets Profile .......................... ........................... ................. ...... ...... 17

3.5 Setting up the Planning Book .......................... .......................... ........................... .............. . 18

3.6 Creating the Forecast Profile (SAP APO) ..... ............................................. .......................... 23

3.7 Creating Macros (SAP APO) ........................ ........................... .................. ...... ...... ...... ....... 25

3.7.1 Creating Macros for the Standard View .............. ........................... ................. ...... ....... 253.7.2 Creating the Sales Volume Macro for the Sales View ..... ............................................. . 31

3.8 Promotion Specific Settings (SAP APO) ........................ ........................... ....... ...... ...... ....... 32

3.8.1 Maintain Promotion Key Figures .......... ........................................ ................................. 32

3.9 Assigning User to Planning Book (SAP APO) .............................. .................... ................... 32

4 Loading Historical Data ......................................... ........................... ..................... ...... ...... ...... 34

4.1 Loading Historical Data from Excel (SAP APO) ..... ........................................................... .. 34

4.2 Testing the Data Upload (SAP APO) ....................... ........................... ........... ...... ...... ....... .. 35

4.3 Maintaining Characteristic Combinations: Non-VMI (SAP APO) ......................... .......... ....... 36

4.4 Maintaining Characteristics Combinations: VMI (SAP APO) ..... ........................................... 37

4.5 Initializing the Planning Area ....................... ........................... ........................... ................. . 38

4.6 Creating Selection Profiles for the Planning Book ......................... .................... ................ .. 39

5 Setting up the Release of the Demand Forecast ......................... ..................... ...... ...... ...... ...... 40

5.1 Release to SNP ......................... .......................... ........................... ........................ ...... ...... 40

5.2 Release to SAP ECC ........................... .......................... ........................... .................... ...... 42

5.2.1 Creating the Transfer Profile .......................... ........................... .............. ...... ...... ....... .. 43

5.2.2 Creating an Activity ....................... ........................... ........................... .......... ...... ....... .. 44

5.2.3 Creating a Planning Job ........................... ........................... ........................... ...... ....... . 455.2.4 Scheduling the Planning Job ........................ ........................... ........................ ...... ....... 46

© SAP AG Page 4 of 46

Page 5: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 5/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

Demand Planning: Configuration Guide

1 Preparation1.1 PrerequisitesThe Demand Planning building block contains all configuration settings that are necessary togenerate demand forecasts in the SAP APO System.

Before starting with the installation, make sure that you have successfully set up the relevantsections of the Connectivity and the Replication building blocks.

A basic prerequisite for executing demand forecasts in SAP APO, is the availability of historicalsales data. In this building block, SAP Best Practices provide the settings for loading historicaldata from an excel file or, alternatively, from your SAP ECC System.

Use the configuration guide to make the configuration settings by performing all required stepsmanually.

1.2 SAP Notes Building Block Demand PlanningCurrently, no SAP Note is required to run this building block:

SAP Note # Component Description

– – –

© SAP AG Page 5 of 46

Page 6: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 6/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

2 Setting up APO BWTo enable SAP APO to load historical sales data, you need to make several settings in the BWpart of the SAP APO system, which is called the Data Warehousing Workbench.

The following section describes the basic steps that are necessary if you want to load historicaldata into SAP APO using Microsoft Excel files as the default source system. However, many of these settings are also required if you intend to use an OLTP system as your source system. Inthe latter case, some additional settings are required which can be found in the Loading Historical Data from OLTP section.

2.1 Creating the Source System (APO BW)

Use A source system indicates the system from which the transaction data and master data originated.This activity is an example that shows you how to create the Excel source system so that you canuse it later for loading the historical sales data from Excel files. You need to create a separatesource system if you want to load the data from a different data source.

Procedure1. 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. In the left screen area of the Data Warehousing Workbench: Modeling screen, choose

Source Systems.

3. In the right screen area, right-click Source Systems and choose Create.

4. In the Select Source System Type dialog box, select the File System (Manual Metadata, Datausing file interface) option and choose Transfer .

The Create Source System dialog box is displayed.

5. Enter Excel in both rows ( Logical System Name and Source System Name ) and chooseEnter .

Sometimes the error message “No entry for BW_USER in table RSADMIN available”appears. In this case, choose Help and double-click on Proposal for Users in SourceSystem in the Performance Assistant.

a) Choose the Customizing activity (transaction RSCUSTV3).

b) Enter RFCUSER in field SS user ALE.

c) Choose Save and choose or create a workbench request.

d) Go back and leave (!) the Data Warehousing Workbench.

e) Try again to create the source system.

If you still encounter problems, see SAP note 410952 (BW User = RFCUSER)

© SAP AG Page 6 of 46

Page 7: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 7/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

2.2 Setting up the Info Source (APO BW)

UseIn this activity, you create the InfoSource for transaction data so that you can transfer data fromthe source system to the SAP APO System. The InfoSource is created in the Data WarehousingWorkbench.

In this activity, you also define the communication structure, assign the source system and definethe transfer rules. The Communication Structure represents the structure of an InfoSource. Itcontains all InfoObjects that belong to an InfoSource. The Transfer Structure is the framework inwhich data from the source system is transferred to the SAP APO system. Transfer rules enableyou to specify how the fields in the transfer structure are assigned to the InfoObjects in thecommunication structure. This is normally a 1:1 assignment, although InfoObjects can also befilled via routines or constants.

Procedure1. 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. In the Modeling screen area on the left, choose InfoSources .

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

4. Make the following entries:

Field name User action and values Comment

Application comp. DP_APPL_COMP The system adds the prefix “Z”ZDP_APPL_COMP

Long description Demand Planning ApplicationComponent

5. Choose Continue.

6. Right-click the Demand Planning Application component you have created, and choose Additional Functions → Create InfoSource 3x.

7. In the Create InfoSource dialog box, select Flexible Update in any Data Target and enter thefollowing values :

Field User action and values

InfoSource DP_IS

Long description Demand Planning InfoSource

Template-Info Source Leave empty

8. Choose Transfer .

9. Right-click the new info source and choose Additional Functions → Create Transfer rules.

10. In the dialog box that appears, enter the source system EXCEL using the input help.

11. Choose Transfer .

12. Confirm the system prompt to save your changes.

13. In the right screen area, choose Communication Structure to expand the structure.

© SAP AG Page 7 of 46

Page 8: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 8/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

14. Enter the following InfoObjects in the InfoObject column:

InfoObjects Description

9ALOCNO APO Location

9AMATNR APO Product

9ABRAND Brand

9ALOCTO APO Destination Loc.

9AVKORG Sales Organization

0CALMONTH Cal.year/month

9AVHISTORY History

0UNIT Unit of measure

15. To expand the transfer structure entry screen, choose “Transfer_structure / Transfer_rules” .

16. In the drop down menu in the Source System field, choose the source system Excel . Thenselect the Transfer Rules tab and choose Propose Transfer Rules .

17. Save the InfoSource.

18. Choose Activate on the menu bar to activate the InfoSource.

19. Go back to the Data Warehousing Workbench .

© SAP AG Page 8 of 46

Page 9: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 9/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

2.3 Setting up Info Area (APO BW)

UseIn 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 tobe assigned more effectively.

Procedure1. 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 , chooseInfoProvider .

3. In the right screen area, right-click InfoProvider and choose Create InfoArea .

4. Enter the following data:

Field name Description User action and values Comment

Info Area DP_INFOAREA

Long Description Demand Planning Info Area

5. Choose Continue .

© SAP AG Page 9 of 46

Page 10: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 10/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

2.4 Setting up the Info Cube (APO BW)

UseIn this activity, you create an InfoCube, which is a data container for planning data, and assigncharacteristics and key figures to it. Then you maintain update rules for the InfoCube. Update rulesspecify how data (key figures, time characteristics, characteristics) is written to the InfoCube fromthe 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 bemaintained for each InfoSource you wish to link with the InfoCube.

Procedure1. 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. In the left screen area of the Data Warehousing Workbench , choose InfoProvider .

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

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

Field name User action and values Comment

InfoCube DP_IC

Description Demand Planning InfoCube

InfoProvider Type Select the radio button Standard InfoCube

5. Choose Create .

The Choice of BW Application dialog box is displayed.

6. Double-click BW.

The Edit InfoCube screen is now divided into four columns:

• Navigation area (Modeling or other) on the left

• InfoProvider area

• Template area• InfoCube area

7. In the Template area, choose with the quick info text Info Source 3.x to display theInfoSource table.

8. In the Select Info Source window, choose All Applications,then click on DP_IS Demand Planning Info Source in the InfoSource table.Choose Continue .

The InfoSource template is now displayed in the template area.

9. Expand all folders of the InfoSource template.

© SAP AG Page 10 of 46

Page 11: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 11/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

10. Select the following characteristics from the template area (in the Characteristics folder):

• APO Location

• APO Product

• Brand

• APO Destination Location

• Sales Organization

11. Using drag and drop, move these characteristics to the Dimension 1 element under theDimensions folder in the InfoCube area on the right.

12. Likewise, assign the time characteristics Calendar year/month to the dimension Time of the InfoCube. As a result, the InfoObject Unit of measure is automatically assigned to theInfoCube.

13. Assign the key figure History to the Key Figures folder of the InfoCube.

14. To assign the APO Planning Version (9AVERSION) characteristics to this InfoCube, right-clickthe InfoCube dimension Dimension 1 and choose InfoObject Direct Input .

15. In the Insert InfoObjects dialog box, enter 9AVERSION and choose Continue . You haveassigned all relevant characteristics to the InfoCube.

16. Save the InfoCube, activate the InfoCube and go back to the Data Warehousing Workbench.

2.4.1 Creating the Update Rules1. Right-click the Demand Planning InfoCube and choose Additional Functions → Create update

rules.

2. In the Info Source field, select the Demand Planning InfoSource and choose Continue

3. In the Update Rules create: Rules screen, default update rules are generated from theInfoCube. Update rules must be created for all key figures and characteristics in the InfoCube.

4. Double-click key figure History or choose Detail . The Update Rule: Detail dialog box isdisplayed.

5. On the Key Figure tab, choose Addition n the Update Type section. .

A key figure can be updated according to different rules ( Addition or No updateoption). No update means that the InfoCube is not updated. In other words, no datarecords are written to the InfoCube during the initial data transfer, or the data recordsthat are already available remain with subsequent transfers. Addition means that newvalues are added where the primary key is the same.

6. In the Update Method section, choose History as a Source Key Fig (Source Key Figure) .

7. Go to the Characteristics tab.

8. Choose method blank of the characteristic APO-Planning Version .9. Choose Constant and enter the value 000.

© SAP AG Page 11 of 46

Page 12: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 12/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

10. Choose Transfer.In the Update Rules table, the status must be green for the next step.

11. Choose Update Rules → Activate from the menu bar and go back to the Data Warehousing Workbench .

© SAP AG Page 12 of 46

Page 13: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 13/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

2.5 Creating the Infopackage

UseIn this step, you create an InfoPackage to upload historical data from an Excel sheet.

Procedure1. Access the Data Warehousing Workbench in SAP SCM using one of the following navigation

options:

SAP SCM menu Advanced Planning and Optimization → Demand Planning →

Environment → Data Warehousing Workbench

Transaction code RSA1

2. In the left part of the Data Warehousing Workbench, in the Modeling section, chooseInfoSources .

3. Look for the relevant InfoSource, for example, DP_IS Demand Planning InfoSource.

4. Expand the InfoSource DP_IS and right-click the second subnode and choose CreateInfoPackage .

5. In the Create InfoPackage dialog box, enter the InfoPackage description (e.g. DemandPlanning Info Package). Choose Save .

6. The Scheduler (Maintain InfoPackage) screen is displayed.

7. Choose the External Data tab page. In the Load external data from section, select Client Workstation .

8. In the File Type section, select the CSV file radio button. In the Data separator field, enter “ ; ”.In the Escape sign field, enter “ “ “.

9. In the Name of file field, enter the path to the Excel file which contains the data to beuploaded.

10. Choose the Processing tab page and select the radio button PSA and then into Data Targets(Package by Package) .

11. Choose the Data targets tab page and select the radio button Select Data Targets.

12. Choose your InfoCube and set the indicator Updating the data target. Do not set the indicator Delete entire content of data target .

13. Choose the Update tab and select the radio button Full update and Always update data, evenif no master data exists for the data .

14. On the Schedule tab page, specify when the data is to be uploaded (either immediately, or asa batch job).

15. Save the Infopackage.

© SAP AG Page 13 of 46

Page 14: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 14/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

3 Setting up the Demand Planning Book

3.1 Maintaining Periodicities for Planning Area

UsePeriodicities for a planning area (also called storage buckets profile) define the time buckets inwhich data based on a given planning area is saved in Demand Planning or Supply NetworkPlanning. The periodicity for Demand Planning is usually divided in weeks and months whereasthe periodicities for SNP are usually made up of days or weeks. You need to define a storagebuckets 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

2. On the Maintain Periodicity screen, choose the storage buckets profile 9ADP .

3. If necessary, change the horizon during which the profile is valid:

Field name Description User action and values Comment

Start date for example,

01.01.2005End date for example,

31.12.2008

4. Save and go back to the SAP Easy Access Menu.

© SAP AG Page 14 of 46

Page 15: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 15/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

3.2 Activating the Planning Object Structure

UseYou need to activate the standard planning object structure for Demand Planning, which groupstogether 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.

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

2. In the upper left screen area, choose Planning areas → Plng object structures.3. Right-click the planning object structure 9ADPBAS and choose Activate (even if the status

light is green).

4. Go back.

3.3 Setting up the Planning Area

Use A planning area is the central data structure of Demand Planning. It groups the parameters thatdefine the scope of planning activities.

ProcedureCreate 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

2. If no planning areas are displayed, choose Plng Object Structures in the upper left screenarea and switch to the Planning area view.

3. In Name screen area, right-click the Planning Areas folder name and choose Create planning area .

4. In the Create Planning Area dialog box, make the following entries:

Field name User action and values Comment

Planning area DP_001

Master plg object structure

9ADPBAS

© SAP AG Page 15 of 46

Page 16: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 16/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

Field name User action and values Comment

Database connection LCA

Stor. bckts prfl 9ADP

Unit of measure for example, PC

Statistics currency for example, EUR

If you want to change settings of an existing planning area, you need to deactivate theactive planning area. To do this, go to the S&DP Administration screen, right-click onthe relevant planning area, and choose Delete time series objects . Make the requiredchanges.

5. Choose Enter .

6. Choose the Key figs tab and select the following key figures for the planning area:

Key fig. Description InfoCube Comment9AVHISTORY History DP_IC Relevant for Scenario MTS

9ADFCST Forecast Relevant for Scenario MTS and VMI

9APROM1 Promotion 1 Relevant for Scenario MTS

9AAFCST Forecast (addition.) Relevant for Scenario MTS

9APRICEFC Planned Price Relevant for Scenario MTS

9AREVFC Sales Forecast Relevant for Scenario MTS

9APPROD Production (Planned) Relevant for Scenario MTS

9AMANUP Manual Correction Relevant for Scenario MTS

9AADDKF1 Additional Field 1 Relevant for Scenario VMI

9AADDKF2 Additional Field 2 Relevant for Scenario VMI

9AADDKF3 Additional Field 3 Relevant for Scenario MTS

9AADDKF4 Additional Field 4 Relevant for Scenario MTS

9AADDKF5 Additional Field 5 Relevant for Scenario MTS

7. Choose Details and assign the InfoCube DP_IC to the key figure 9AVHISTORY. To do this,enter DP_IC in the corresponding field in the InfoCube column.You also need to change the value in the Semantic column from 001 to 002 .

Without the assignment of the InfoCube to the key figure 9AVHISTORY (for historicaldata), historical data from the data source cannot be displayed in the planning book,even if no error messages appear for the upload.

8. Choose Key Fig. Selection to go back.

9. Choose the Key Figure Aggregatn tab page and change the calculation type of all key figuresfrom S to P except for the key figure 9AVHISTORY.

10. Assign the disaggregation key figure APODPDANT to each key figure except for the key figure9AVHISTORY.

11. Save the planning area and go back.

© SAP AG Page 16 of 46

Page 17: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 17/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

3.4 Maintaining the Time Buckets Profile

UseTime bucket profiles define the historical or future time horizon for Demand Planning or SupplyNetwork Planning. With this step, you define which time buckets can be used for planning, howmany periods of each time bucket are used and in which sequence the time buckets appear in theplanning table.

Procedure1. 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 profilefor Demand Planning and Supply Network Planning

Transaction code /SAPAPO/TR30

2. Define the following three profiles using the values in the respective tables:

Profile 1

3. Enter the ID and a name for the time buckets profile:

Field name User action and values Comment

Time buckets prfl ID

DP_4Weeks_5Months In this example, the time horizon spans 6months (5+1). The first month is displayed inweeks.

Short text Enter a name for thisprofile

4. In the entry table, enter the following values. Choose Enter after completing each row to getto the next row.

Number Basic periodicity Periv2 Display periodicity

6 M

1 M W

W

5. Save the profile. Create the following two profiles following the same procedure.

© SAP AG Page 17 of 46

Page 18: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 18/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

Profile 2

6. Create the profile 2 following the same procedure as for profile 1.

Field name User action and values Comment

Time buckets prfl ID

DP_12Months In this example, the time horizon spans 1 year.This year is displayed in 12 months.

Number Basic periodicity Periv2 Display periodicity

12 M

M

Profile 3

7. Create the profile 3 following the same procedure as for profile 1 and 2.

Field name User action and values Comment

Time buckets prfl ID

DP_20Days In this example, the time horizon spans 20 days.

Number Basic periodicity Periv2 Display periodicity

20 T

8. Go back when you have created all profiles.

3.5 Setting up the Planning Book

Use A planning book defines the content and the layout of the interactive planning screen. Planningbooks are used in Demand Planning and Supply Network Planning. They allow you to design thescreen to suit individual planning tasks. A planning book is based on a planning area. You cancreate several user-specific data views in a planning book. In this step, you create a planning bookfor Demand Planning.

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

2. Enter the planning book DP_001 and choose Create .

The Planning Book Wizard dialog box is displayed.

© SAP AG Page 18 of 46

Page 19: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 19/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

3. Make the following entries:

Field name User action and values

Planning Book Enter the planning book DP_001

Planning book text Demand Planning

Planning area Select the planning area DP_001 and choose Enter

Manual ProportionMaintenance

X

Promotion X

Univariate forecast X

4. Choose Continue .

5. Assign the following key figures from planning area to the planning book by using drag anddrop or choose Add all new Key Figures to add all key figures:

Description Value Comment

History 9AVHISTORY Relevant for Scenario MTS

Forecast 9ADFCST Relevant for Scenario MTS and VMI

Promotion 1 9APROM1 Relevant for Scenario MTS

Forecast (addition.) 9AAFCST Relevant for Scenario MTS

Planned Price 9APRICEFC Relevant for Scenario MTS

Sales Forecast 9AREVFC Relevant for Scenario MTS

Production (Planned) 9APPROD Relevant for Scenario MTS

Manual Correction 9AMANUP Relevant for Scenario MTS

Additional Field 1 9AADDKF1 Relevant for Scenario VMI

Additional Field 2 9AADDKF2 Relevant for Scenario VMI

Additional Field 3 9AADDKF3 Relevant for Scenario MTS

Additional Field 4 9AADDKF4 Relevant for Scenario MTS

Additional Field 5 9AADDKF5 Relevant for Scenario MTS

The Proportional factor APODPDANT key figure is automatically added to your planning areawhen you create the planning area. You do not have to add this key figure yourself and assignit to the planning book in this step. When you create the respective view, this key figure will beautomatically there for your selection.

6. Choose Continue .

7. Assign the following characteristics from the planning area to the planning book by using dragand drop:

Description Value

APO Location 9ALOCNO

APO Product 9AMATNR

Brand 9ABRAND

Sales Organization 9AVKORG

APO Destination Loc. 9ALOCTO

© SAP AG Page 19 of 46

Page 20: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 20/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

The characteristic 9AVERSION (APO Planning Version) will be added to the planning bookautomatically after you complete this step.

9. Choose Continue to go to the Data View tab (the Key Fig. Attrib tab is available in the changemode only after you have completed the planning book).

10. On the Data view tab; enter the following values:

Field name User action (Scenario MTS) User action (Scenario VMI)

Data view DP_Standard VMI_Standard

Data view description Demand Planning Demand Planning

TB profile ID (future) DP_4Weeks_5Month DP_4Weeks_5Month

TB profile ID (history) DP_12Month DP_12Month

Status 3 (Changeable) 3 (Changeable)

11. Choose Enter .

12. Select Visible and select the date as of which you wish the past planning horizon to be visiblewhen this data view is opened.

13. Choose Continue , and assign the following key figures from the planning book to the dataview for either the MTS or the VMI scenario, keeping the same order as in the table:

Make-to-Stock

Key Figures Description

9AVHISTORY History

9ADFCST Forecast

9APROM1 Promotion 1

9AAFCST Forecast (additional)

9APRICEFC Planned Price

9AREVFC Sales Forecast

9APPROD Production (Planned)

9AMANUP Manual Correction

9AADDKF4 Additional Field 4

Vendor-Managed Inventory

Key Figures Description

9AADDKF1 Additional Field 1

9AADDKF2 Additional Field 2

9ADFCST Forecast

© SAP AG Page 20 of 46

Page 21: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 21/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

14. Choose Complete.

15. When the Planning Wizard prompt appears, choose Yes to complete the planning book anddata view.

16. On the initial screen, change the planning book you have just created by choosing Edit .

17. If you are installing the VMI scenario, continue with step 21 (entering a free text for the keyfigures).If you are installing the Make-to-Stock scenario, repeat steps 9 to 12 to create the followingviews:

Views View Description Key Figures

DP_CLP COLLABORATIVE DEMAND PLANNING

History

Forecast

Forecast (additional)

DP_RELEASE DEMAND PLANNING - RELEASE VIEW

Manual Correction

18. On the Data View tab page, specify the following TB profile IDs for the DP_RELEASE view,

Field name User action and values

TB profile ID (future) DP_12Month

TB profile ID (history) blank

19. Create the remaining views for the Make-to-Stock scenario according to the steps 9-12:

Views View Description Key FiguresDP_LOGISTICS DEMAND PLANNING - LOGISTICS VIEW

Forecast

Production (Planned)

DP_SALES DEMAND PLANNING - SALES VIEW

History

Forecast

Forecast (addition.)

Planned PriceSales Forecast

Manual Correction

DP_PROP DEMAND PLANNING - PROPORTIONALFACTOR VIEW

Proportional Factor

To modify the proportional factors manually, you need to create a separate data viewcontaining only the APODPDANT key figure to control the authorization to change

these factors. This key figure is a default value in the view and is thus invisible, so youdo not need to assign any key figure from the right list in this view.

© SAP AG Page 21 of 46

Page 22: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 22/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

20. Choose Complete.

21. Go to the Key fig. attributes tab, select the FreeText radio button and make the followingentries for each key figure. Choose Save Setting after entering the data for each key figure(depending on your scenario).

Key Figures Free Text Relevant for scenario

9AVHISTORY Historical Data MTS

9ADFCST Statistical Forecast MTS and VMI

9APROM1 Promotion MTS

9AAFCST Sales Forecast MTS

9APRICEFC Planning Price MTS

9AREVFC Sales Revenue Forecast MTS

9APPROD Logistics Forecast MTS

9AMANUP Final Forecast MTS

9AADDKF1 VMI Historical Data VMI

9AADDKF2 VMI Customer Forecast VMI

9AADDKF3 – MTS

9AADDKF4 Forecast Deviation MTS

9AADDKF5 Customer Forecast MTS

22. Choose Complete and exit the planning book maintenance.

© SAP AG Page 22 of 46

Page 23: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 23/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

3.6 Creating the Forecast Profile (SAP APO)

UseYou 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 seriespatterns, for example, constant demand, trend demand, seasonal demand, and seasonal trenddemand.

Procedure (Non-VMI)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:

Field name User action and values Comment

Planning area DP_001

Master prfl DP_Master_Profile

Description Demand Planning Master Profile

Forecast key figure 9ADFCST

Period indicator M

Forecast horizon Define a time period for your forecast horizon

History horizon Define a time period for your history horizon

3. On the UnivariateProfile tab, enter the following values:

Field name User action and values Comment

Profile DP_UNI_PROFILE

Description Demand Planning Univariate Profile

Key figure 9AVHISTORY

Version 000

Forecast strategy 10

(Forecast with constant models)

Alpha 0,20

Beta 0,30

4. Choose Save Single Profile .

5. On the Master prfl. tab, select Univariate forecast and enter the following values:

Field name User action and values Comment

Univariate forecast DP_UNI_PROFILE

6. Save the forecast profile and go back.

© SAP AG Page 23 of 46

Page 24: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 24/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

Procedure (VMI)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, enter the following values:

Field name User action and values Comment

Planning area DP_001

Master prfl VMI_Master_Profile

Description VMI Master Profile

Forecast key figure 9ADFCST

Period indicator M

Forecast horizon Define a future period for your forecast horizon,for example from the current date until sixmonths in the future

History horizon Define a period in the past for your historyhorizon, for example, starting twelve months inthe past until one month in the past

3. On the Univariate prfl tab, enter the following values:

Field name User action and values Comment

Profile VMI_UNI_PROFILE

Description VMI Univariate ProfileKey figure 9AADDKF1

Version 000

Forecast strategy 11

Alpha 0,20

Beta 0,30

4. Choose Save Single Profile .

5. On the Master prfl. tab, select Univariate forecast and enter the following values:

Field name User action and values Comment

Univariate forecast VMI_UNI_PROFILE

6. Choose Save and go back.

© SAP AG Page 24 of 46

Page 25: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 25/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

3.7 Creating Macros (SAP APO)

Use

You can use advanced macros to perform complex calculations quickly and easily. Macros areexecuted either directly by the user or automatically at a predefined point in time. When definingadvanced macros, you work in a special desktop environment known as the MacroBuilder.

In total, four macros are created in the Demand Planning building block. They are all defined for the planning book DP_001. You create three macros for forecast calculation according to thefollowing instruction. The chapter Creating the Macro for Consensus-Based Planning describeshow to create the alert macro for consensus-based planning.

In the DP_STANDARD view of the planning book DP_001, you create two macros:

The first macro is used for the standard and consensus-based planning. The system calculatesthe arithmetic average of Statistical Forecast, Sales Forecast and Logistics Forecast, the result of average forecast data plus Promotion Data is inserted in the Final Forecast cell. It enables theuser to consider the forecast input and the promotion plan from different departments within thecompany. The planner can make manual adjustments and enter the final agreed forecast into theFinal Forecast cell. All of this information can be shown in the planning book screen.

The second macro multiplies the Final forecast data with the Planned price to calculate the salesvolume. The third macro is an alert macro used for highlighting exceptional situations inconsensus-based planning.

In the DP_SALES view of the planning book DP_001, you create the fourth macro. This macromultiplies the Final forecast data with the Planned price to calculate the sales volume, which is thesame as the one in the standard view.

3.7.1 Creating Macros for the Standard View1. 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

2. Enter the name of the planning book: DP_001

3. Select Data view DP_standard.

4. Choose Edit .

5. Choose MacroBuilder → MacroBuilder → Data view .

© SAP AG Page 25 of 46

Page 26: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 26/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

3.7.1.1 Creating the Macro for Consensus-Based Planning1. Right-click the macro node below the planning table and choose Create New Macro → Add

macro . In the APO Macro Builder dialog box, enter a descriptive text for the macro, for example, Forecast + Promotion → Final Forecast. Choose Continue .

2. Right-click the macro and choose Add macro Element → Step .In the APO Macro Builder dialog box, in the descriptive text section, enter a name for themacro step, for example, First Step and choose Continue .

3. Right-click the macro step and choose Add Element (Result Level) Add results row .In the APO Macro Builder dialog box, choose Final Forecast in the Row field. Choose Adopt.

4. Right-click the result row you have just created and choose Add Element (Argument Level) Add Operator/Function .In the APO Macro Builder dialog box, choose “ ( “ .

5. Right-click the operator/function you have just created and choose Add Element (Argument Level) Planning Table Element Append argument row .

In the APO Macro Builder dialog box, choose Statistical Forecast in the Row field .6. Right-click the argument row you have just created and choose

Add Element (Argument Level) Append Operator/Function .In the APO Macro Builder dialog box, choose “ +” .

7. Right-click the operator/function you have just created and choose Add Element (Argument Level ) → Planning Table Element → Append argument row .In the APO Macro Builder dialog box, choose Sales Forecast in the Row field.

8. Right-click the argument row you have just created and choose Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box, choose “ +”.

9. Right-click the operator/function you have just created and choose Add Element (Argument Level ) → Planning Table Element → Append argument row .In the APO Macro Builder dialog box choose Logistics Forecast in the Row field.

10. Right-click the argument row you have just created and choose Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box, choose “ )”.

11. Right-click the operator/function you have just created and choose Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box, choose “ / ”.

12. Right-click the operator/function you have just created and choose Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box, enter “ ( ”.

13. Right-click the operator/function you have just created and choose Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box, choose “ SIGN() ” and change it to “ SIGN( “.

14. Right-click the operator/function you have just created and choose Add Element (Argument Level ) → Planning Table Element → Append argument row .In the APO Macro Builder dialog box, choose Statistical Forecast in the Row field .

15. Right-click the argument row you have just created and choose Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box, choose “ ) ”.

16. Right-click the operator/function you have just created and choose

Append Operator/Function .In the APO Macro Builder dialog box, choose “ +”.

© SAP AG Page 26 of 46

Page 27: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 27/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

17. Right-click the operator/function you have just created and choose Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box, choose “ SIGN() ” and change it to “ SIGN( “.

18. Right-click the operator/function you have just created and choose Add Element (Argument Level ) → Planning Table Element → Append argument row .

In the APO Macro Builder dialog box, choose Sales Forecast in the Row field.19. Right-click the argument row you have just created and choose

Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box, choose “ ) ”.

20. Right-click the operator/function you have just created and choose Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box, choose “ +”.

21. Right-click the operator/function you have just created and choose Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box choose the character “SIGN()” and change to “ SIGN( “.

22. Right-click the operator/function you have just created and choose Append argument row .In the APO Macro Builder dialog box, choose Logistics Forecast in the Row field.

23. Right-click the operator/function you have just created and choose Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box, choose “ ) ”.

24. Right-click the operator/function you have just created and choose Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box, choose “ ) ”.

25. Right-click the operator/function you have just created and choose Add Element (Argument Element) → Append Operator/Function .In the APO Macro Builder dialog box, enter “ +”.

26. Right-click the operator/function you have just created and choose Append argument row .In the APO Macro Builder dialog box, choose Promotion in the Row field.

27. Select the macro and choose Check to check it. Generate the macro by choosingGenerate .

28. Move the macro by using drag and drop to the Events section and to the Default folder in theupper right screen area.

29. If you want to continue with the configuration, proceed with the next activity to create theSales Volume Macro (see below).If you want to discontinue the configuration at this point, we recommend that you save your settings. To do this, go back to the Planning book Design screen and choose Save . Choose

All Functional Areas when the confirmation prompt appears .

3.7.1.2 Creating the Sales Volume Macro

1. Right-click the macro node below the planning table and choose Create New Macro → Add macro In the APO Macro Builder dialog box, enter a descriptive text for the macro, for example,Sales Revenue Forecast.Choose Continue.

2. Right-click the macro and choose Add Macro Element → Step .

In the APO Macro Builder dialog box, in the descriptive text section, enter name for the macrostep for example, First Step .

© SAP AG Page 27 of 46

Page 28: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 28/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

3. Right-click the macro step and choose Add Element (Result Level) → Add results row .In the APO Macro Builder dialog box, choose Sales Revenue Forecast in the Row field.

4. Right-click the results row you have just created and choose Add Element (Argument Level) → Planning Table Element → Add argument row .In the APO Macro Builder dialog box, choose Final Forecast in the Row field .

5. Right-click the argument table row you have just created and choose Add Element (Argument Level) → Append operator/function .In the APO Macro Builder dialog box, enter * .

6. Right-click the operator/function and choose Add Element (Argument Level) → Planning Table Element → Append argument row .In the APO Macro Builder dialog box, choose Planning Price in the Row field .

7. Select the macro and choose Check to check it. Choose Generate to generate themacro.

8. Using drag and drop, move the macro to the Events section and to the Default folder in theupper right corner screen area.

9. Go back to the Planning book design screen and choose Save .

10. Choose All Functional Areas when the confirmation prompt appears and go back to the mainmenu path.

3.7.1.3 Creating an Alert Macro

UseIn this section, you create an alert macro. The alert is used to highlight exceptional situations inthe consensus-based planning. In this case, the alert macro compares the figure of the LogisticsForecast data with that of Sales Forecast data. If the deviation is more than 10 percent, an alert isgenerated.

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

2. Enter the name of the planning book: DP_001.

3. Select the DP_Standard data view.Choose Edit. The Planning Book: Design Demand Planning Book /Demand_Planner screen isdisplayed.

4. Select the Forecast Deviation row, right-click it and choose Selected rows → Hide.

5. Choose MacroBuilder → MacroBuilder → Data view .

6. Right-click the macro node below the planning table and choose Create a New Macro →

Add macro .

© SAP AG Page 28 of 46

Page 29: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 29/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

In the APO MacroBuilder dialog box, in the Description section, enter a name for the macro,for example, Forecast Deviation, and choose Continue.

7. Right-click the macro and choose Add macro element → Step . In the APO MacroBuilder dialog box, in the Description section, enter a name for the macro step, for example, CalculateDifference, and choose Continue .

8. Right-click the macro step and choose Add Element (Result Level ) → Add results row .In the APO MacroBuilder dialog box, in the Row field, choose Forecast Deviation and chooseContinue .Right-click the result row you have just created and choose Add Element (Argument Level)→ Append operator/function .In the APO MacroBuilder dialog box, choose an open bracket “ ( “ and choose Continue.

9. Right-click the operator/function you have just created and choose Add Element (Argument Level) → Planning Table Element → Append argument row .In the APO MacroBuilder dialog box, in the Row field, choose Sales Forecast and chooseContinue.Right-click the argument row you have just created and choose Add Element (Argument Level) → Append operator/function . In the APO MacroBuilder dialog box, choose a minus

- and choose Continue.10. Right-click the operator/function you have just created and choose Add Element (Argument

Level ) → Planning Table Element → Append argument row .In the APO MacroBuilder dialog box, in the Row field, choose Logistics Forecast and chooseContinue.Right-click the argument row you have just created and choose Add Element (Argument Level ) → Append operator/function .In the APO MacroBuilder dialog box, enter “ ) * 100 / ” (separated by blanks) and chooseContinue.

11. Right-click the operator/function you have just created and choose Add Element (Argument Level) → Planning Table Element → Append argument row .In the APO MacroBuilder dialog box, in the Row field, choose Logistics Forecast and chooseContinue.

12. Right-click the macro and choose Add macro element → Step .In the APO MacroBuilder dialog box, in the Description section, enter a name for the macrostep, for example, Alert, and choose Continue.

13. Right-click the macro step and choose Add Element (Result Level) → Add Control Statement .In the APO MacroBuilder dialog box, in the Statement field, choose IF and choose Continue .

14. Right-click the control statement row you have just created and choose Add Element (Result Level) → Append Condition .In the APO MacroBuilder dialog box, enter “Condition: Forecast Deviation > 10%” and chooseContinue.

15. Right-click the condition row you have just created and choose Add Element (Argument Level) → Planning Table Element → Append argument row .In the APO MacroBuilder dialog box, in the Row field, choose Forecast Deviation and chooseContinue.Right-click the argument row you have just created and choose Add Element (Argument Level) → Append operator/function .In the APO MacroBuilder dialog box, enter > 10 (separated by blanks) and chooseContinue.

16. Right-click the IF control statement you have created in step 13 and choose Add Element (Result Level) → Planning Table Element → Append results row .

In the APO MacroBuilder dialog box, in the Row field, choose Sales Forecast in the Row fieldand Attribute change in the Change mode field. Choose Continue.

© SAP AG Page 29 of 46

Page 30: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 30/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

Right-click the result row you have just created and choose Add Element (Argument Level)→ Add operator/functio n.In the APO MacroBuilder dialog box, enter CELL_BG( 6 ) (with a blank before and after thefigure “6”) and choose Continue.

17. Right-click the result row and choose Add Element (Result Level) → Append Control

Statement .In the APO MacroBuilder dialog box, choose ELSE in the Statement field and chooseContinue .

18. Right-click the control statement you have just created and choose Add Element (Result Level) → Planning Table Element → Append result row .In the APO MacroBuilder dialog box, choose Sales Forecast in the Row field and Attributechange in the Change mode field.

19. Right-click the result row you have just created and choose Add Element (Argument Level)→ Add operator/function .In the APO MacroBuilder dialog box, enter CELL_BG( 2 ) (with a blank before and after thefigure “2” and choose Continue.

20. Right-click the result row you have just created and choose Add Element (Result Level)→

Append Control Statement .In the APO MacroBuilder dialog box, in the Row field, choose ENDIF and choose Continue.

21. Select the macro and choose Check to check it. Choose Generate to generate themacro.

22. Move the macro to the right upper corner of the screen to the Events section and into theDefault folder by using drag and drop.

23. Go back to the Planning book Design screen and choose Save .

© SAP AG Page 30 of 46

Page 31: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 31/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

3.7.2 Creating the Sales Volume Macro for the Sales View

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

2. Enter the name of the planning book: DP_001

3. Choose Data view DP_Sales .

4. Choose Edit .

5. Choose MacroBuilder .

6. Choose MacroBuilder Data view .

To create the macro, perform the following steps:

7. Right-click the macro node below the planning table and choose Add macro.

8. In the APO Macro Builder dialog box, in the descriptive text section, enter a name for themacro, for example, Sales Revenue Forecast

9. Choose Continue.

10. Right-click the macro and choose Add macro element → Step.

11. In the APO Macro Builder dialog box, in the descriptive text section, enter a name for themacro step, for example, First Step .

12. Right-click the macro step and choose Add results row . In the APO Macro Builder dialog box,choose Sales Revenue Forecast in the Row field.

13. Right-click the results row you have just created and choose Add element (Argument Element) → Planning Table Elements → Add argument row. In the APO Macro Builder dialogbox, choose Final Forecast in the Row field .

14. Right-click the argument table row you have just created and choose Append operator/function. In the APO Macro Builder dialog box, enter *.

15. Right-click the operator/function and choose Append argument row. In the APO Macro Builder dialog box, choose Planning Price in the Row field .

16. Select the macro and use the Check pushbutton to check it. Choose Generate to generate themacro.

17. Move the macro by using drag and drop to the Events section and to the Default folder in theupper right screen area.

18. Go back to the Planning book design screen and choose Save .

19. Choose Save All and go back to the main menu.

© SAP AG Page 31 of 46

Page 32: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 32/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

3.8 Promotion Specific Settings (SAP APO)

3.8.1 Maintain Promotion Key Figures

UseIn this step, you define the lowest level of detail in which promotions are saved.

Procedure1. Access the activity using one of the following navigation options:

SAP SCM menu Advanced Planning and Optimization Demand Planning Planning Promotion Settings Maintain Promotion Key Figures

Transaction code /SAPAPO/MP33

2. On the Maintain Promotion Level screen, maintain the following entry

Planning Area Promotion Key Figures Char. for promotion Level

DP_001 9APROM1 9AMATNR

3. Choose Save.

3.9 Assigning User to Planning Book (SAP APO)

UseYou need to assign the default planning book to each DP user. When a planner opens thedemand planning desktop, he or she sees the planning book assigned to them. Note that you canassign only one planning book to a user.

You can restrict the users’ authorization so that they can only navigate to a specified planningbook or a specific data view.

Procedure1 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 Choose New Entries.

3 Change the following two lines, the first without the transaction code as shown in the table:

Name Trans. Code Plng book Data view Specific book FixedView

username DP_001 DP_Standard

username /SAPAPO/SDP94 DP_001 DP_Standard

© SAP AG Page 32 of 46

Page 33: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 33/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

If you set an indicator in the Specific book column, the user whose name you have entered inthe left column can only navigate to the specified planning book in interactive demandplanning (the user can access all the data views for this planning book).

If you set an indicator in the Specific View column, the user you have entered in the leftcolumn can use this planning book and the planning view only and cannot navigate to other planning books and views in the interactive demand planning.

4. To restrict a person’s authorization (for example, for a sales person), so that they can only useplanning book DP_001 and data view DP_Sales, you have to maintain the table as follows:

Name Trans. Code Plng book Data view Specificbook

FixedView

Salesperson

DP_001 DP_SALES

Salesperson

/SAPAPO/SDP94 DP_001 DP_SALES X X

5. Choose Save . If a system prompt appears, choose or create a customizing request and goback.

6. Repeat the same procedure for all other users.

© SAP AG Page 33 of 46

Page 34: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 34/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

4 Loading Historical Data

If you are installing the Vendor-Managed Inventory scenario (VMI) , only thefollowing activities from this section need to be configured:

• Maintaining Characteristics Combinations: VMI (SAP APO)

• Initializing the Planning Area (SAP APO)

4.1 Loading Historical Data from Excel (SAP APO)

UseIn this step, you upload historical data from an Excel sheet.

ProcedureThe file that contains the sample historical data is calledDP_Upload_HIST_DATA_<IndustryName>.csv. . The sample file is located on the BestPractices Documentation CD.

If you want to run Demand Planning with your own data, open the sample file and replace thesample data with your data. The file is laid out as follows:

Column 1 Column 2 Column 3 Column 4 Column 5 Column 6 Column 7 Column 8

Plant Product Brand Sold-toparty(customer)

Salesorganization Month (for example,012006)

Quantity Unit of measure

The CSV file provided on the CD is just an example for your reference. You must editthe data (for example, the plants, products, brand, customers, etc.) according to your data before you can make the upload.

You can only change or edit this file in a text editor , for example, in MicrosoftNotepad . Otherwise, special characters could be added to the file that prevent youfrom importing the data into the SAP APO System.

Note that MS Excel may cause leading zeros (for example, in dates, such as 012005)

to disappear, which prevents a successful data import. To ensure all dates or other figures that require a leading zero have this figure in the Excel file, open the file byright-clicking on the file and choose Open with.

1. Open the file and enter all the relevant historical data.

2. Choose Save and close the file.

3. Access the Data Warehousing Workbench in SAP SCM using one of the following navigationoptions:

SAP SCM menu Advanced Planning and Optimization → Demand Planning →

Environment → Data Warehousing Workbench

Transaction code RSA1

© SAP AG Page 34 of 46

Page 35: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 35/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

4. In the left part of the Data Warehousing Workbench, in the Modeling section, chooseInfoSources .

5. Look for the relevant InfoSource, for example, Demand Planning InfoSource.

6. Expand the InfoSource DP_IS and double-click the InfoPackage .

7. Choose the External Data tab page. In the File name field, enter the path to the Excel filewhich contains the data to be uploaded.

8. On the Schedule tab page, specify when the data is to be uploaded (either immediately, or asa batch job).

9. Choose Start to execute the upload schedule.

10. Confirm all messages that are displayed.

11. If the Delete Entire Contents of Infocube dialog box is displayed, choose Fact tble and dims .If the Delete InfoCube/ODS content dialog box is displayed, choose Delete entries .

The message Data was requested is displayed.

The Data Warehousing Workbench offers a monitor, which enables you to getinformation about data transfer. To use the monitor, choose Monitor in the upper leftscreen area or choose Goto → Monitoring .

4.2 Testing the Data Upload (SAP APO)

UseThe following section describes different ways of checking the historical data loading process, dataprocessing, analyzing errors and displaying the uploaded data.

ProcedureBy using the Monitor within the Data Warehousing Workbench, you can keep monitor the datarequest and data processing in the background. In the different levels of the detail display, you cancheck the status of the data processing.

Action: Right after the data upload, choose Monitor or choose Goto → Monitor.

You can find the most important markers for localizing an error that was not logged inthe error message in the Detail screen of the Monitor under the Environment menu

option.

Display Uploaded Data in InfoCube1. After the data upload, go back to the Data Warehousing Workbench: Modelling screen.

2. Choose InfoProvider in the left screen area.

3. Expand the node of your InfoArea, for example, Demand Planning InfoArea.

4. Right-click your InfoCube (for example, DP_IC) and choose Manage.

5. In the Manage Data Targets screen, select the line with the name and the technical name of your InfoCube and choose Contents.

6. Choose Field selection for output to define which data is to be displayed.

7. Choose Select all and choose Execute twice.

© SAP AG Page 35 of 46

Page 36: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 36/46

Page 37: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 37/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

If the message “No new characteristics combinations were loaded” is displayed, please check theDate from / to – they must correspond to the period covered by the data source.

You have generated the master data for Demand Planning.

To check the characteristics combination you have just generated, choose Display characteristics combinations in the Maintain characteristic combinations relevant to

planning view.

4.4 Maintaining Characteristics Combinations: VMI (SAPAPO)

UseIn order to run Demand Planning , you need to determine the master data that you will use for creating demand plans for the planning area.

This activity is only required for the Vendor-Managed Inventory scenario (VMI).

Procedure1. Access the transaction using one of the following navigation options:

SAP SCM role menu Maintaining Characteristic Combinations

SAO SCM menu path Advanced Planning and Optimization → Master Data →

Application-Specific Master Data → Demand Planning → MaintainCharacteristic Values

Transaction code /SAPAPO/MC62

2. In the Maintain Planning-Relevant Characteristic Combinations screen, enter the followingdata:

Field name User action and values Note

Master plnng object structure 9ADPBAS -

3. Under Maintain Characteristic Combinations , choose Create Single Characteristic Combination.

4. In the Create Characteristic Value Combinations screen, make the following entries:

Field name User action and values Note

Brand e.g. 1 -

APO - Location e.g. PLBP01/ES7031 “ ES7031” stands for your ECC system and client

APO Destination Location e.g. C6111 -

Product e.g. APO-FERT-03 -

Sales organization e.g. BP01 - Adjust time series objects Select indicator -

© SAP AG Page 37 of 46

Page 38: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 38/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

immediately

5. Choose Execute .

The message Background job scheduled successfully appears .

In the Maintain Planning-Relevant Characteristic Combinations screen, you can checkthe characteristics combination that you have generated. To do this, choose Display characteristics combinations .

4.5 Initializing the Planning Area

UseThe purpose of this activity is to initialize the planning area and to create time series objects.

Procedure1. 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, DP_001).

3. Choose Create time series objects.

4. Make the following entries :

Field name Description User action and values Notes

Plng Version 000

Start Date for example, current date – oneyear

End Date for example, current date + twoyears

5. Choose Execute .

6. Go back.

© SAP AG Page 38 of 46

Page 39: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 39/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

4.6 Creating Selection Profiles for the Planning Book

UseFor your planning process, you need to make a selection that restricts the range of products andlocations. 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

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.

3. From the possible entries list in the Show field, select APO Product .

4. Enter the planning version 000 in the field to the right of the APO Planning Version field.

5. In the second row, restrict the range of products by specifying only those products that youactually need for your planning task. To do this, select APO Product and use the multipleobject selection :

For the Make-to-Stock scenario, for example, select APO-FERT-01 and APO-FERT-02, for other scenarios, specify the respective products.

6. Choose Save selection in the Objects Selection dialog box.

7. Enter for example, MTS_CPG or VMI_CPG as the selection description and choose Save .

8. Choose Adopt

9. To store the saved selection in your selection profile, choose Maintain selection profile inthe left screen area. In the Maintain Selection Profiles for Users dialog box, use drag and dropto transfer the saved selection from the right area to your selection profile on the left.

10. Choose Save and Copy .

11. To display objects that belong to a selection profile, double-click the selection. The systemdisplays the objects in the upper left screen area.

© SAP AG Page 39 of 46

Page 40: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 40/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

5 Setting up the Release of the Demand Forecast

5.1 Release to SNP

Use A demand plan is a plan that is free of restrictions. This means, it is created from adistribution/marketing viewpoint, considering the input from these departments. However, it doesnot consider any real production, storage, or transportation capacities. These aspects areconsidered during Supply Network Planning. By releasing the demand plan to Supply NetworkPlanning, the plan can be processed further and decisions about sourcing, deployment andtransportation based on it can be made.From a technical point of view, you copy the data from the liveCache time series objects into aforecast 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 demandplanning and generated a forecast.

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

valuesNote

Planning area

DP_001

Planning version

000 Active version

Key figure Key figure from whichyou want to copy therequirements data.

9AMANUP For all Non-VMI Scenarios

Key figure 9ADFCST VMI Scenario (if you want totransfer the forecast based onthe historical data)

Key figure 9AADDKF2 VMI Scenario (to transfer aforecast the customer hasalready created)

Choose this key figure if youwant to test the SAP BestPractices VMI scenario

© SAP AG Page 40 of 46

Page 41: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 41/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

3. In the Target area, make the following entries:

Field name Description User action and values Note

Planning version 000 Active version

Category FA

4. In the Horizon area, define the future period to be covered by your demand plan:

Field name User action and values Note

From date beginning of the next month as of the current date, e.g.01.10.2007

To date For example, six months as of your start date,31.03.2008

5. In the Periodicity area, make the following entries:

Field name Description User action and values Note

Daily buckets profile DP_20DAYS6. In the Object Selectn area, make the following entries:

Field name Description User action and values Note

Product APO-FERT-01

or

APO-FERT-03

Scenario MTS

Scenario VMI

7. Activate the Results Log option if you want a log to be generated when the demand plan isreleased.

8. Choose Goto Variants Save as Variant to be able to use these settings again. In thenew screen, enter the variant name and a description:

Variant Name Description Scenario

MTS_CPG Release to SNP MTS Make-to-Stock

VMI_CPG Release to SNP VMI Vendor-Managed Inventory

9. Choose Save and go back.

© SAP AG Page 41 of 46

Page 42: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 42/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

5.2 Release to SAP ECC

UseThe following section describes the necessary settings that enable the user to transfer the demandplanning results back to the SAP ECC System. The forecast results and planned independentrequirements are transferred to the Demand Management and can be further processed there.

Prerequisites• The materials and locations that exist in SAP ECC also exist in the SAP APO system. They

have been transferred during data replication. For these materials, a planning strategy isdefined in the SAP ECC system.

A location split, which is the split of the product demand to locations, has beendefined. In this case, the location split has already been defined through thecalculation type of the key figures. All key figures in the planning area aredisaggregated by using the calculation type “P” – based on different key figures. For further information about the APODPDANT key figure and relevant disaggregationlogic, refer to chapter Setting Up Planning Area .

You can confirm the calculation type of the key figures by opening transaction/SAPAPO/MSDP_ADMIN or by double-clicking your planning area. Confirm thewarning message and go to the KeyFig Aggregation tab. For more information onaggregation and disaggregation, refer to the respective chapter of the SAP APOOnline Help.

• A product split is optional and is not considered in this document. If you wish to define aproduct split, read the relevant section in the SAP APO Online Help.

• The Release data view has been created.• When defining the planning book, refer to chapter Setting Up Planning Book for further

information.

© SAP AG Page 42 of 46

Page 43: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 43/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

5.2.1 Creating the Transfer Profile

UseYou have to create a transfer profile, which is to be used for transferring your forecast results to

SAP ECC Demand Management. In the transfer profile, you also define which key figure is to betransferred. Depending on your requirements, you can define several transfer profiles.

Procedure1. Access the activity using one of the following navigation options:

SAP SCM menu Advanced Planning and Optimization Demand Planning Environment Maintain Transfer Profiles

Transaction code /SAPAPO/MC8U

2. Enter a name for your transfer profile (example: TP_DP) and choose Create .

3. Make the following entries:

Field name User action and values Comment

Planning Area DP_001

Key Figure 9AMANUP alternatively you can use the key figure9ADFCST

Planning version 000

APO Extras

Char. Product optional If you do not make an entry, the systemuses the characteristic 9AMATNR

Char. Location optional If you do not make an entry, the systemuses the characteristic 9ALOCNO

R/3

Requirements Type optional You can leave the field empty if your materials are assigned to an MRP groupwhich is included in a strategy group

Version 00 ID of the SAP ECC demand program towhich you wish to transfer

00 : Requirements Plan

4. Select the Active box if you want the independent requirements to be included in the MRP runin the SAP ECC system.

5. Choose Save and go back twice.

© SAP AG Page 43 of 46

Page 44: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 44/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

5.2.2 Creating an Activity

UseWith this step you define which action takes place, for example, a transfer to the SAP ECC

system, when you create and schedule the respective job (see also the next two steps).

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

2. Enter a name for the activity (example: DP_ECC) and a short description for the planningactivity.

3. Choose Create .

4. Make the following entries:

Field name User action and values Comment

Planning Book DP_001

Data View DP_Release

5. Select the R/3 Transfer Prfl. Tab page in the lower screen area.

6. Enter the name of your transfer profile (TP_DP) and choose Enter . The settings of your transfer profile are displayed.

7. Choose Save . The action “R/3 Transfer” with action counter 1 is automatically inserted in theactivity.

8. Go back twice.

© SAP AG Page 44 of 46

Page 45: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 45/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

5.2.3 Creating a Planning Job

UseYou create a planning job to transfer the forecast data to the SAP ECC system. The actual

transfer takes place when you actually schedule the planning job (see next step). You create aplanning job after having created an additional data view, a transfer profile and an activity profile.This step is usually performed by the user. Nevertheless, it is recommended that you also performit during the installation process, to test the data transfer to SAP ECC.

Procedure1. 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 → CreateDemand Planning in the Background

Transaction code /SAPAPO/MC8D

2. Enter a name (TRANSFCAST) and a short description (Planning Job Transfer Forecast) for the planning job.

3. Choose Planning job Execute . The initial Create Planning Job screen appears.

4. Select the planning book and the data view you specified in the activity, and as the name of the planning version for which you want to run the job.

Field name User action and values Note

Planning book DP_001

Data view DP_Release

Version 000 Active version

5. Choose Planning job Execute . The second Create Planning Job screen appears.

6. Enter the activity DP_ECC.

7. Specify whether the system should generate a job log.

8. In the Chars section, choose Select All .

9. Choose Aggregation Level .

10. In the dialog box, choose Deselect All.

11. Select the fields 9ALOCNO (APO – Location) and 9AMATNR (APO Product).

12. Choose Continue .13. Save the planning job.

ResultYou have created a planning job for transferring the demand plan to Demand Management in SAPECC.

© SAP AG Page 45 of 46

Page 46: APO DP_ConfigGuide_EN_DE[1]

8/2/2019 APO DP_ConfigGuide_EN_DE[1]

http://slidepdf.com/reader/full/apo-dpconfigguideende1 46/46

SAP Best Practices Building Block DPL Demand Planning: Configuration Guide

5.2.4 Scheduling the Planning Job

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

ResultThe system carries out the planning job at the time specified. To check the job status, chooseDemand Planning Planning Demand Planning in the Background Job Overview of Demand Planning in the Background or open transaction code SM37. You can also view the joblog using transaction /SAPAPO/MC8K.

In SAP ECC Demand Management ( Logistics Production Production Planning Demand Management Planned Independent Requirements Display) , planned independentrequirements are created in the same buckets as those of the data view on which the massprocessing job is based.

For information on how to process the results in SAP ECC Demand Management, see thedocument PP Demand Management in the SAP Library of your SAP ECC System.