Config Guide - Demand Planning

mySAP SCMSAP APO 3.10

Configuration Guide

SAP AGNeurottstr. 1669190 WalldorfGermany

Demand Planning

Configuration Guide: Demand Planning

2 October 2001

Copyright© Copyright 2001 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purposewithoutthe express permission of SAP AG. The information contained herein may be changed withoutprior notice.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registeredtrademarks of Microsoft Corporation.

IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®,AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation.

ORACLE® is a registered trademark of ORACLE Corporation.

INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks ofInformix Software Incorporated.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World WideWeb 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 fortechnology invented and implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow,SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.comare trademarks or registered trademarks of SAP AG in Germany and in several other countries allover the world. All other products mentioned are trademarks or registered trademarks of theirrespective companies.


3 October 2001

Contents1 Purpose..................................................................................................................................... 5

2 Configuration Steps .................................................................................................................. 5

2.1 General Settings............................................................................................................. 5

2.2 Connectivity .................................................................................................................... 5

2.3 Replication...................................................................................................................... 8

2.4 Business Configuration................................................................................................. 16


4 October 2001

Typographic Conventions

Type Style Represents

Interface Text Words or characters that appear on the screen. Thisincludes system messages, field names, screen titles,pushbuttons, menu names, and menu options.

Document Title Cross-references to other documentationUser Entry Exact user entry. These are words and characters that

you enter exactly as they appear in the documentation.File Name File names, batch files, paths or directories, and screen

messages<Variable UserEntry>

Variable user entry. Pointed brackets indicate that youreplace these words and characters with appropriateentries.

NAME Names of elements in the SAP System. These includereport names, program names, transaction codes, tablenames, and ABAP language elements.

KEY Keys on your keyboard. These include function keys (forexample, F2) and the ENTER key.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Tip


5 October 2001

1 PurposeThe purpose of this document is to describe the general configuration steps required to set up theDemand Planning scenario within the system landscape that has already been installed using thecorresponding mySAP Supply Chain Management Master Guide for installation.

2 Configuration StepsThis section provides an overview of the configuration steps needed to implement the scenario.

If the available standard documentation is sufficient to carry out the required step, a replication isomitted in this document and instead a link to the corresponing documentation is specified.

2.1 General SettingsThis section gives the general settings, necessary to carry out the setup.

a) Create a User in the APO and R/3 system with the same name and password:

Tools -> Administration -> User Maintenance -> Users (TA: SU01):

1. The user in the APO system should have the following profiles:

a. SAP_ALL

b. S_RS_ALL (for the Administrator Workbench)

c. S_BI-WHM_RFC (for data transmission)

2. The user in the R/3 system should have the following profiles:

a. SAP_ALL

b. S_BI-WHM_RFC

2.2 ConnectivityThis section describes the setting necessary to enable the data transfer between an SAP R/3Logistics Information System (LIS) and the SAP APO.

See also the corresponding SAP APO documentation:

Supply Chain Management (SCM) Business Scenarios -> Integration of APO and R/3 -> APOCore Interface -> Setting up the System Infrastructure and Data Transfer

2.2.1 SAP R/3a) Define logical system:

1. Tools -> Accelerated SAP -> Customizing -> Edit Project (TA: SPRO)


6 October 2001

2. Press Button SAP Reference IMG

3. Implementation Guide for R/3 Customizing (IMG) -> BasicComponents -> Application Link Enabling (ALE) -> Sending andReceiving Systems -> Logical Systems -> Define Logical System

4. A logical system is indicated by the 3 character system code followed by CLNT and the 3digit client number (e.g. DEOCLNT800). Check if the logical R/3 and APO systemsalready exist for the clients you want to work with, or create the entry in the table pressingthe button New entries

Comment: Alternatively to steps 1 to 3 select the table V_TBDLS using the transaction SE16 andcarry out step 4

b) Assign client to logical system:

1. Tools -> Accelerated SAP -> Customizing, and choose Edit Project(TA: SPRO)


3. Implementation Guide for R/3 Customizing (IMG) -> BasicComponents -> Application Link Enabling (ALE) -> Sending andReceiving Systems -> Logical Systems -> Assign Client to LogicalSystem

4. Check if the defined logical R/3 system is already connected to the corresponding client.If necessary, mark the row and press the button Details. Maintain the necessaryinformation using the default settings

Comment: Alternatively to steps 1 to 3 use Tools -> Administration ->Administration -> Client Administration -> Client Maintenance (TA:SCC4) and carry out step 4

c) Define RFC destination:1. Tools -> Administration -> Administration -> Network ->RFC

Destinations (TA: SM59) and exand R/3 connections

2. Double click on the corresponding logical APO system and maintain the following:

a. Connection type: 3

b. Load distrib: No

c. Target host: Use the Message Server information available on SAP Logon underServer or Groups for the corresponding system

d. System Number: Use the information available on SAP Logon under Propertiesfor the corresponding system

e. Save as: IP address

f. Trusted system: No

g. Logon: Include the information for the user created under 2.1

d) Set target system:

1. Logistics -> Central Function -> Supply Chain Planning Interface-> Core Interface Advanced Planner and Optimizer -> Settings ->Target Systems (TA: CFC1)


7 October 2001

2. Check if the corresponding logical APO system is already maintained and include it ifnecessary. The OpMode is set automatically

e) Maintain the APO Release:

1. Logistics -> Central Function -> Supply Chain Planning Interface-> Core Interface Advanced Planner and Optimizer -> Settings ->APO Releases (TA: NDV2)

2. Check if the corresponding logical APO system is already maintained and include it withSyst.type SAP_APO and Release 3.1A if necessary

2.2.2 SAP APOa) Define logical system:

1. Tools -> Business Engineer -> Customizing (TA: SPRO)


3. APO Implementation Guide -> R/3 Basis Customizing -> ApplicationLink Enabling (ALE) -> Sending and Receiving Systems -> LogicalSystems -> Define Logical System

4. A logical system is indicated by the 3 character system code followed by CLNT and the 3digit client number (e.g. DEOCLNT800). Check if the logical R/3 and APO systemsalready exist for the clients you want to work with, or create the entry in the table pressingthe button New entries

Comment: Alternatively to steps 1 to 3 select the table V_TBDLS using the transaction SE16 andcarry out step 4

b) Assign client to logical system:



3. APO Implementation Guide -> R/3 Basis Customizing -> ApplicationLink Enabling (ALE) -> Sending and Receiving Systems -> LogicalSystems -> Assign Client to Logical System

4. Check if the defined logical APO system is already connected to the corresponding client.If necessary, mark the row and press the button Details. Maintain the necessaryinformation using the default settings

Comment: Alternatively to steps 1 to 3 use Tools -> Administration ->Administration -> Client Administration -> Client Maintenance (TA: SCC4)and carry out step 4

c) Define RFC destination:

1. Tools -> Administration -> Administration -> Network ->RFCDestinations (TA: SM59) and exand R/3 connections

2. Double click on the corresponding logical R/3 system and maintain the following:

a. Connection type: 3


8 October 2001

b. Load distrib: No

c. Target host: Use the Message Server information available on SAP Logon underServer or Groups for the corresponding system

d. System Number: Use the information available on SAP Logon under Propertiesfor the corresponding system

e. Save as: IP address

f. Trusted system: No

g. Logon: Include the information for the user created under 2.1

d) Maintain Business System Group:



3. APO Implementation Guide -> Advanced Planner and Optimizer ->Basic Settings -> Integration -> Business System Group ->Maintain Business System Group (TA: /SAPAPO/C1)

4. Create a Business System Group, if necessary

e) Assign Logical System to Business System Group:



3. APO Implementation Guide -> Advanced Planner and Optimizer ->Basic Settings -> Integration -> Business System Group -> AssignLogical System (TA: /SAPAPO/C2)

4. Assign both logical systems (SAP APO and SAP R/3) to a business system group (theydon´t need to be the same)

2.3 ReplicationThis section describes the process the setup the transfer of data from the SAP R/3 LIS to theSAP APO via the SAP BW.

2.3.1 Configuration ReplicationThis section gives the settings necessary in SAP R/3 - LIS. It is not the purpose of this documentto give all details how to setup an R/3 planning environment.

See for all steps also the corresponding SAP R/3 documentation.

2.3.1.1 SAP R/3 - LISa) Create / Maintain Information Structure:



9 October 2001


3. Implementation Guide for R/3 Customizing (IMG) -> Logistics -General ->Logistics Information System (LIS) -> Logistics DataWarehouse -> Data Basis -> Information Structures -> MaintainSelf-Defined Information Structures (TA: MC21)

4. Create an Information Structure or use an existing one (e.g. S628). Please use TypeStandard and set the Flag Plng. possible

b) Create / Maintain Parameters:



3. Implementation Guide for R/3 Customizing (IMG) -> Logistics -General ->Logistics Information System (LIS) -> Planning ->Master Data -> Set parameters for info structures and keyfigures (TA: MC7F)

4. Set the planning parameters and define the key figures to be updated

c) Setup Update Rules:



3. Implementation Guide for R/3 Customizing (IMG) -> Logistics -General ->Logistics Information System (LIS) -> Logistics DataWarehouse -> Updating -> Updating Controle -> Activate Update (TA:MC21)

4. An Update Group has to be assigned to the Update Rules (e.g. Z0001 to S628). Thissecures that in case of a Customer Order or an Invoice, the data is updated. Thisincludes routines for Requirements for Statistics Updating

d) Activate Update:



3. Implementation Guide for R/3 Customizing (IMG) -> Logistics -General ->Logistics Information System (LIS) -> Logistics DataWarehouse -> Updating -> Updating Definition -> SpecificDefinition Using Update Rules -> Maintain Update Rules (TA: OMO1)

4. Choose Activity: Sales and Distribution

5. Double click on the corresponding Information Structure to maintain the settings

For the period split it is important that the SAP APO and the Info Cube should onlyinclude this periodicity

In order to update data in the SAP BW (of the SAP APO) the update of the initial dataupload has to be deactived (No update)


10 October 2001

2.3.2 Master Data ReplicationFor the SAP APO Demand Planning no Master Data like Location Master of Material Master isnecessary. Therefore the transfer of these object using the Plug In can be omitted.

If this scenario is extended by a Supply Network Planning environment, these steps have to beadded.

2.3.3 Transaction Data ReplicationThis secion describes how to load data from an SAP R/3 Info Structure to an Info Cube in theSAP BW system of the SAP APO.


Demand Planning -> Demand Planning Process -> Planning Area Administration -> DP Data Mart-> Loading Data from an R/3 Info Structure

2.3.3.1 SAP BW of SAP APO (initial data load)a) Maintain the source system in the Administrator Workbench of the APO system:

1. Demand Planning -> Environment -> Current Settings ->Administrator Workbench (TA: RSA1)

2. On the source system tab, click with the right mouse button on Source systems andchoose Create source system

3. Select the source system type SAP R/3, manual creation

4. Select the RFC destination for the R/3 system via the F4 help and insert a description

5. Choose Enter

6. On the RFC destination screen, choose Remote logon.

a. This logs you on to the R/3 system

7. Click the yellow arrow twice

a. The source system is now created

8. To return to the Source system tab of the APO Administraotr Workbench, click the greenarrow twice

b) Customize the R/3 extractors (initial data upload):

1. In the Administrator Workbench of the APO system (the Source system tab), click withthe right mouse button on the source system and choose Customizing for extraction…

2. A Customizing structure for the Business Information Warehouse appears

3. From this structure, choose Settings for Application-Specific DataSources -> Logistics -> Logistics Information System -> ConnectInformation Structures


11 October 2001

4. On the Connection for LIS Information Structures to SAP BW screen, enter the name ofthe information structure (e.g. S628)

5. Select Set up LIS environment

6. Choose Execute

7. A message appears informing you that the LIS environment has been installedsuccessfully. Note: Two tables (e.g. S628BIW1 and S628BIW2) and a structure (e.g.S628BIWS) were generated

8. Go back to the Connection for LIS Information Structures to SAP BW screen

9. Enter again the name of the self-defined information structure

10. Select Generate Data Source

11. Choose Execute

12. An Assignment window appears for the generated Data Source. The name of the DataSource is made up of the prefix 2LIS_01_ followed by the name of the informationstructure (e.g. 2LIS_01_S628)

13. Check the automatic mapping between the R/3 fields and the APO InfoObjects

14. If necessary, you can remove an assignment and enter a different InfoObject

15. In the right column, select the fields whose ranges you want to be able to limit whendoing the data upload (for example, just one sales organization or a range of products orjust one version)

16. Choose Save

c) Replicate Data Source:

1. In the APO Administrator Workbench (the Source system tab), click with the right mousebutton on the source system and choose Replicate Data Source (Be patient: The processcan take some minutes)

2. In the APO Administrator Workbench (the Source system tab), click with the right mousebutton on the source system and choose Data Source Overview

3. The Data Source can be found under SAP Application Components -> Salesand Distribution

d) Create Application Component:

1. Switch to the InfoSources tab of the APO Administrator Workbench

2. Click with the right mouse button on the InfoSources node and choose Create AppliactionComponent

3. A popup appears. Insert a Name and a Long description for the Application Componentto be created

e) Create Info Source:

1. Click with the right mouse button on created Application Component and choose CreateInfo Source


12 October 2001

2. A popup appears. Choose Transactional Data. A second popup appears. Insert a Nameand a Long description for the Info Source to be created

3. Click with the right mouse button on the created Info Source and choose Assign DataSource

4. A popup appears. Select the Source System using the F4 help and choose the logicalR/3 system. Choose Enter

5. A popup appears with the available Data Sources. Choose the corresponding DataSource (e.g. 2LIS_01_S628) and confirm the appearing popup

6. The system automatically leads you to the maintenance screan for the transfer rules andcommunication structure

7. Expand the Communication Structure

8. Transfer the InfoObjects you want to upload (i.e. normally all) from the template on theright to the communication structure on the left

9. Verify that the sequence of the InfoObjects in the communication structure on theTransfer rules tab is the same as in the metadata (see step c) )

10. If desired, create local conversion routines; for example, in order to update an additionalperiod type.

The conversion is done for all InfoCubes that are updated via this InfoSource. To apply aconversion routine to only one InfoCube, use an update rule

11. In the Technical details tab under Transfer Rules, verify the mapping of the fields in thetransfer structure to the InfoObjects in the communication structure. Make sure that thekey figure 9AVERSION is used to write the version

12. Choose Activate

Note: If the activation of the communication structure or the transfer rules fails, check tosee that updating has been activated in the R/3 system. If necessary, deactivate updatingwith transaction OMO1

f) Create InfoPackage:1. Still on the InfoSources tab, click with the right mouse button on the source system and

choose Create InfoPackage

2. Enter a description of the InfoPackage

3. Choose Enter

4. If necessary, restrict the ranges for which data is uploaded on the Select data tab. TheInfoObjects for which you can specify a range depend on which ones you selected in stepb) 15.

5. On the Processing tab, select Only PSA (Persistant Staging Area). Data uploading viaPSA stores the data per upload in flat tables that can be modified. This enables a datacheck before uploading in one or several Info Cubes. Moreover, you do not have tocreate an InfoCube before you load data; if necessary, certain decisions about theInfoCube design can be left until you can see the uploaded data in PSA


13 October 2001

6. On the Date Targets tab select Update in all data targets for which active rules exist

7. On the Update parameters tab, select Initialize delta process and Always update dataeven if no master data exists for the data

To really upload the data (see 2.4.3.1.) continue as follows:

8. On the Schedule tab, select Start data load immediately and click Start

9. Choose Goto -> Monitor to check the upload results

g) Check the results of the data upload into PSA:1. Switch to the PSA tab of the APO Administrator Workbench

2. Click with the right mouse button on the request ID and choose Edit data. Perhaps youhave to click with the right mouse on PSA first and choose Insert lost node(s)

3. Select the data packet(s) you wish to view and choose Enter. Note that the version is notyet filled

h) Create InfoCube:1. Switch to the Data Targets tab of the APO Administrator Workbench

2. If necessary create an Info Area by clicking with the right mouse button on the DataTargets node and choose Create InfoArea. A popup appears. Enter a name and a longdescription for the Info Area to be created

3. Click with the right mouse button on the Info Area in which you want to group yourInfoCubes for Demand Planning and choose Create InfoCube

4. A popup appears. Enter a name and a description for the InfoCube. Choose Info Cubetype Basic Cube and press Create

5. In the Edit InfoCube: Characteristics screen, click on the Info Source icon , double-click on your Info Source (e.g. 2LIS_01_S628), and confirm that the Info Objects in thereference should be transferred to the structure. In other words, you are using the InfoSource as a template

6. Insert 9AVERSION in the structure. You can get it from the All objects template

7. Click on Dimensions

8. Create at least one dimension. Dimensions allow you to group your characteristicsaccording to different business perspectives

Note: You do not need to create dimensions for time characteristics, units or datapackets; these are created automatically

9. Click on the Assign tab

10. Select the characteristic(s) you want to assign, and the dimension to which you wish toassign it (them), and click on Assign

Note: Make sure you assign the characteristic Version (9AVERSION) to the Versiondimension


14 October 2001

11. Choose Continue

12. Click on the Time characterstics tab.

13. Some InfoObjects are already in the structure. Select from the template any additionaltime characteristics that correspond to the buckets in which you want to plan

Note: 0CALDAY, 0CALMONTH and 0CALWEEK are fully supported. If you select0CALQUARTER and/or 0CALYEAR, you must - in a separate Customizing step - createa fiscal year variant. Likewise, if you select 0FISCPER, you must create a fiscal yearvariant; moreover, by selecting 0FISCPER you automatically select 0FISCPER3,0FISCVARNT and 0FISCYEAR as well

14. Click on the Key fiures tab

15. Some Key Figures are already in the structure. Select from the template any additionalthat you want to plan on

16. Choose Activate and go back

i) Create the update rules for the InfoCube:1. In the Data Targets tab of the APO Administrator Workbench, click with the right mouse

button on the Info Cube you have just created and choose Create update rules

2. Specify the Info Source (e.g. 2LIS_01_S628) and choose Continue

3. If the status of a key figure is red, double-click on it. In the Update rule: Detail screen youspecify one of the following update options:

a. If you are not uploading data for this key figure, select the update type Noupdate. Then choose Transfer

b. If you are uploading data for this key figure and the update is straightfoward (thatis, you do not wish the data to be modified in this process), choose the updatetype Update and the update method Source key figure. Then choose Transfer

c. If you are uploading data for this key figure and you do want the data to bemodified in this process (see step 17f), select the update method Routine andcreate a routine by clicking on the Create icon. Once you have created theroutine, choose Transfer

4. Press Details. A popup appears. Switch to the Characteristics tab and press the Blancbutton for the characteristic APO – Planning Version (i.e. 9AVERSION). A popupappears. Select Constant and insert the version you want to plan with. Press Transferand confirm to copy the result to all key figures

5. When all the statuses are green, activate the update rules

j) Load the data from PSA into the InfoCube:1. In the PSA tab of the APO Administrator Workbench, click with the right mouse button on

the request and choose Schedule the update

2. On the Processing tab, select From PSA into data targets

3. On the Data Targets tab, choose Select data targets and select the InfoCube


15 October 2001

4. On the Update parameters tab, select Always update data even if no master data existsfor the data

To really upload the data continue as follows:

5. On the Schedule tab click Start

6. Wait until you are informed that a batch job with a job number has been activated, andthen choose Goto -> Monitor

7. Refresh the monitor output list until the output status shows a green light

8. Verify that all the traffic lights in the Monitor Assistant are green

k) Check the results of the data load into the InfoCube:1. In the APO Administrator Workbench, click on the Data Targets tab

2. Click on the Icon on the InfoCube

3. On the Manage Data Targets screen mark the corresponsing row in the upper grid andpress Contents

4. This starts the InfoCube Browser transaction (TA: LISTCUBE) to check the content of theInfo Cube

2.3.3.2 SAP BW of SAP APO (delta upload)a) Customize the R/3 extractors (1):




4. On the Connection for LIS Information Structures to SAP BW screen, enter the name ofthe information structure (e.g. S628). Alternatively you can start the Report RMCSBIWCin R/3 using transaction SE38.

5. Select Generate Updating

6. Choose Execute

7. A message appears informing you about the generation results

b) Activate the Update in R/3:

1. Start in R/3 the transaction SBIW

2. Choose Business Information Warehouse -> Settings for Application-Specific Data Sources -> Logistics -> Logistics InformationSystem -> Activate Update


16 October 2001

3. A popup appears. Choose Sales and Distribution and Choose

4. Select the Information structure

5. Choose Parameters

6. A popup appears.

7. Select Asynchronous Updating

8. Copy

9. Save

c) Customize the R/3 extractors (2):




4. On the Connection for LIS Information Structures to SAP BW screen, enter the name ofthe information structure (e.g. S628). Alternatively you can start the Report RMCSBIWCin R/3 using transaction SE38.

5. Select Activate/deactivate

6. Choose Execute

7. A message appears informing you about the activation

d) Create Info Package:

1. Choose the Info Package created under 2.3.3.1. f)

2. On the Update parameters tab, select Delta Update

To really upload the data (see 2.4.3.3.) continue as follows:

3. On the Schedule tab, select Start data load immediately and click Start

4. Choose Goto -> Monitor to check the upload results

e) Load the data from PSA into the InfoCube as given under 2.3.3.1. j)

2.4 Business ConfigurationThis section describes:

1. The configuration settings that you need to make in the SAP APO system. Not all detailswill be given but a reference to the corresponding APO documentation.

2. The Planning Process


17 October 2001

2.4.1 Master Data ConfigurationThis section describes how to set up a Demand Planning environment in SAP APO.

2.4.1.1 Model and VersionCreate a Model and a Planning Version:

See the corresponding SAP APO documentations:

• APO Master Data -> Model/Planning Version -> Creating Models

• APO Master Data -> Model/Planning Version -> Creating Planning Versions

2.4.1.2 Master Planning Object Structurea) Create a Master Planning Object Structure:

1. Demand Planning -> Environment -> Current Settings ->Administration of Demand Planning and Supply Network Planning (TA:/SAPAPO/MSDP_ADMIN)

2. Change view to Plng. object structures

3. Right click on Planning Object Structures and choose Create master plng object struct

4. Enter a name and Enter

5. Enter a text

6. Select the characteristics on the right grid and move them to the left grid (e.g. 9AMATNR,9ALOCNO, DIVISION, CUST, PRODH, SALESORG)

Note: This definition has to fit to the structure transferred from R/3 and the data in theInfo Cube

7. Activate and go back


Demand Planning -> Demand Planning Process -> Planning Area Administration-> MasterPlanning Object Structure

b) Create aggregates (optional step):

1. Right mouse click on the created Master Planning Object Structure and choose Createaggregate

2. A popup appears. Enter a name and Enter

3. Enter a text

4. Select the characteristics on the right grid and move them to the left grid


5. Activate and go back



18 October 2001

Demand Planning -> Demand Planning Process -> Planning Area Administration->Aggregate

c) Maintain Characteristic Combinations:

1. Right mouse click on the created Master Planning Object Structure and choose Maintainchar. combinations

2. Choose Genereate characteristic combination

3. Include the Info Cube the Version and a Start and End Date for the generation

4. Execute


APO Master Data -> Master Data for Demand Planning -> Generating Master Data forDemand Planning

2.4.1.3 Planning Areaa) Create Storage Bucket Profile:

1. Demand Planning -> Environment -> Current Settings ->Periodicities for Planning Area (TA: /SAPAPO/TR32)

2. Enter a name

3. Select the periodicities you want to plan on


4. Enter a Start & End Date

5. Enter a Time Stream ID (optional)

6. Save and go back


Demand Planning -> Demand Planning Process -> Planning Area Administration-> StorageBuckets Profile

b) Create Planning Area:

1. Demand Planning -> Environment -> Current Settings ->Administration of Demand Planning and Supply Network Planning (TA:/SAPAPO/MSDP_ADMIN)

2. Change view to Planning Area

3. Right click on Planning Area and choose Create Planning Area

4. Enter a name

5. Enter the corresponding Master Planning Object Structure defined in 2.4.1.2

6. Enter the Storage Buckets profile defined under a)

7. (Optional) Enter the Statistical Currency and Exchange Rate Type

8. Enter the Unit of Measure

9. Press OK


19 October 2001

10. On the Key Figures tab select the key figures on the right grid and move them to the leftgrid. You have to choose the key figures with data stored in the Info Cube (e.g.INORDQTY, INORDVAL, INVQTY, INVVAL) as well as some key figures used forplanning (e.g. 9ADFCST, 9ADMDTOT, etc.)


11. Press Details

12. For the key figures with data stored in the Info Cube (and the corresponing aggregates)enter the Info Cube in the coloum Info Cube

Alternatively the data can be loaded from the Info Cube to the Time Series Live Cache (inthis case the coloum Info Cube has to remain empty).

Demand Planning -> Environment -> Load Planning Area Version (TA:/SAPAPO/TSCUBE)

Note that for this step, the Planning Area has to exist already. This will increase theperformance for all planning activities. See also the corresponding SAP APOdocumentation:

Demand Planning -> Demand Planning Process -> Planning Area Administration-> DataStorage in Demand Planning and Supply Network Planning

13. On the Key fig. aggregatn tab define the aggregation and disaggregation rules for eachkey figure

14. On the Key fig. assgmt tab define the key figures for which the aggregate should becalculated

15. Save and go back


Demand Planning -> Demand Planning Process -> Planning Area Administration-> PlanningArea

c) Create Time Series Objects:

1. Right mouse click on the created Planning Area and choose Create Time Series Objects

2. Choose Genereate characteristic combination

3. Enter a Planning Version and Press ENTER (on the keyboard). The system automaticallyadds the Start and End Date (which can be maintained)

4. Execute

2.4.1.4 Planning Book / Data Viewa) Create Time Bucket Profiles:

1. Demand Planning -> Environment -> Current Settings -> MaintainTime Buchets Profile for Demand Plng and Supply Network Plng (TA:/SAPAPO/TR30)

2. Enter an ID and a Short Text

3. Enter the number and the type of periodicities you want to display. Start with the longestperiodicity and prees ENTER (on the keyboard) after each line entry. In the following line


20 October 2001

enter the number of periods (at the beginning of the time stream) to be displayed in asmaller periodicity

4. Save


Demand Planning -> Demand Planning Process -> Planning Books Design-> PlanningBuckets Profile

b) Create Planning Book & Data View(s):

See the corresponding SAP APO documentation:

Demand Planning -> Demand Planning Process -> Planning Books Design-> Planning Book -> Planning Book Maintenance

c) Assign User to Planning Book (only neccesary if you work the first time with Demand Planningin this APO system):

1. Demand Planning -> Environment -> Current Settings -> Assign Userto Planning Book (TA: /SAPAPO/SDPPLBK)

2. New Entries

3. Enter your User (under Name) the Planning book and the Data View

4. Save

2.4.1.5 Forecast ProfileCreate a Master Forecast Profile and a Univariate Forecast Profile:


Demand Planning -> Demand Planning Process -> Definition/Redefinition of Forecast Models ->Creating a Master Forecast Profile

2.4.1.6 Release to R/3a) Maintain Distribution Definition:



3. APO Implementation Guide -> Advanced Planner and Optimizer ->Basic Settings -> Integration -> Publication -> MaintainDistribution Definition

4. Setup via New Entries per Location that Planned Indpendent Requirements (Publ. Type)are released to the logical R/3 system

b) Setup the Release of Planned Independent Requirements from Demand Planning to SAP R/3:


Demand Planning -> Demand Planning Process -> Transfer of Demand Plan to R/3 DemandManagement

Note: The materials are planned in R/3 with Strategy Group 40 (Planning with final assembly).The Requirement Type for this in R/3 is VSF for Planned Independent Requirements (to be used


21 October 2001

in SAP APO in the Release Profile) and KSV for Customer Requirements. This setting can bechecked in R/3 under:Logistics -> Materials Managements -> Material Master -> Material ->Display -> Display Current (TA: MM03) on the MRP3 tab

2.4.2 Planning ProcessThis section describes the process flow of this Scenario

1. The first step is carried out once in order to load the complete data

2. The steps 2 to 6 represent the regular planning cycle

2.4.2.1 Initial data loada) Load the complete data from the SAP R/3 LIS system to the PSA of the SAP BW of SAP APO:

Carry out the steps given under 2.3.3.1. f) and g)

b) Load the data from PSA to the Info Cube:

Carry out the steps given under 2.3.3.1. j) and k)

c) If necessary, copy the data from the Info Cube to the Time Series Live Cache:

Carry out the steps given under 2.4.1.3 b) 12.

d) Change the settings to data upload as given under 2.3.3.2. a) to c)

2.4.2.2 Order creation in SAP R/3Create a Sales Order:

1. Logistics -> Sales and Distribution -> Sales -> Order -> Create(TA: VA01)

2. Choose Order Type OR

3. Enter the Organizational data

4. Enter

5. Enter the neccesary information on the Order Overview screen

6. Save

2.4.2.3 Data uploada) Load the new data from the SAP R/3 LIS system to the PSA of the SAP BW of SAP APO:

Carry out the steps given under 2.3.3.2. d)

b) Load the data from PSA to the Info Cube:

Carry out the steps given under 2.3.3.2. e)

c) If necessary, copy the data from the Info Cube to the Time Series Live Cache:

Carry out the steps given under 2.4.1.3 b) 12.


22 October 2001

2.4.2.4 Demand PlanningCarry out Demand Planning, i.e. create a forecast:

Demand Planning -> Planning -> Interactive Demand Planning (TA:/SAPAPO/SDP94)


Demand Planning -> Demand Planning Process -> Creation of the Demand Forecast

2.4.2.5 Release planning results to R/3Start the backgroud job created under 2.4.1.6. b)

2.4.2.6 Continue Planning in R/3Check the Planning Situation:Logistics -> Logistics Execution -> Information System -> Goods Receipt-> List of Material Stock -> Current Requirements and Stock List (TA:MD04)

Documents

Config Guide - Demand Planning