764: bi retail: merchandise and assortment...

EHP3 for SAP ERP 6.0

September 2009

English

764: BI Retail: Merchandise and Assortment Planning

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

Building Block Configuration Guide

SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide

© SAP AG of 116

Copyright

© Copyright 2009 SAP AG. All rights reserved.

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

Microsoft, Windows, Excel, Outlook, and PowerPoint

are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

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 invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document 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 its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of


© SAP AG of 116

any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.


© SAP AG of 116

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include Field names, screen titles, pushButtons as well as menu names, paths and options.

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, program names, Transaction codes, table names, and individual key words of a programming 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 as names of installation, upgrade and database tools.

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

ENTER key.

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

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


© SAP AG of 116

Contents

1 Purpose .................................................................................................................................... 8

2 Preparation ............................................................................................................................... 8

3 Budget Customizing ................................................................................................................. 8

3.1 Defining PPW Budget Levels – SAP BI ......................................................................... 8

3.2 Defining OTB Budget Levels – SAP BI .......................................................................... 9

3.3 Defining PPW Key Figures - SAP BI ............................................................................ 10

3.4 Defining OTB Key Figures - SAP BI ............................................................................ 10

3.5 Defining PPW Budget Type - SAP BI .......................................................................... 11

3.6 Defining OTB Budget Types - SAP BI ......................................................................... 12

3.7 Activating Budget Types - SAP BI ............................................................................... 13

3.8 Creating RFC Destinations - SAP BI ........................................................................... 13

3.9 Transferring Budget Types to SAP ECC – SAP BI ...................................................... 15

3.10 Assigning PPW Budget IDs – SAP ECC ...................................................................... 15

3.11 Activating PPW Budget Type – SAP ECC ................................................................... 16

3.12 Checking and Extending OTB Budget Types – SAP ECC .......................................... 17

3.13 Activating OTB Budget Types – SAP ECC .................................................................. 18

3.14 Reorganization of OTB Budgets – SAP ECC .............................................................. 19

3.14.1 Determining the Generated Budget Plan Table ....................................................... 19

3.14.2 Comparing Corresponding Structure with Budget DataStore Object ...................... 19

3.14.3 Deleting Structure and Table Type for the Generated Plan Table .......................... 20

3.14.4 Reorganizing Budget Types .................................................................................... 21

3.15 Changing Type Group /MAP/ - SAP BI ........................................................................ 21

3.16 Changing Function Module /MAP/SSM_CREATE_WORK_ITEMS_RFC ................... 22

4 Transactional Data Extraction via Flatfiles – SAP BI ............................................................. 23

4.1 Creating Application Components ............................................................................... 23

4.2 Merchandise Planning .................................................................................................. 24

4.2.1 Creating InfoSources and Transfer Rules ............................................................... 24

4.2.2 Assigning Update Rules to InfoProviders ................................................................ 25

4.2.3 Executing Info packages for Real Time InfoProvider .............................................. 25

4.2.4 Releasing PPW Budget ........................................................................................... 28

4.2.5 Releasing OTB Budget ............................................................................................ 29

4.2.6 Assigning Price Planner Groups to Budget – SAP ECC ......................................... 30

4.3 Assortment Planning .................................................................................................... 31

4.3.1 Defining Key Figures – SAP BI ................................................................................ 31

4.3.2 Maintaining Values for Key Figure 0RT_KEYFIG .................................................... 33

4.3.3 Creating InfoProviders ............................................................................................. 34



4.3.6 Assigning InfoPackage to InfoSources and Loading Data ...................................... 40

4.3.7 Logging on to the Query Designer ........................................................................... 44

4.3.8 Creating Queries ...................................................................................................... 45

4.3.9 Defining Message Types and Selections Options for Releasing Assortments........ 49


© SAP AG of 116

4.3.10 BADI UPARI_ASRTPLN .......................................................................................... 50

4.3.11 Releasing Assortment Plan ..................................................................................... 57

4.3.12 Creating Purchasing List – SAP ECC ...................................................................... 58

4.3.13 OTB Check: Maintaining Document-Type Dependent Settings – SAP ECC .......... 60

4.4 Slow Seller Management ............................................................................................. 61

4.4.1 Generating Export DataSources .............................................................................. 62

4.4.2 Install Interface “Goods Receipt Date” ..................................................................... 62

4.4.3 Loading Goods Receipt Dates into 0MAT_PLANT .................................................. 66

4.4.4 Install Interface “ POS and Stock Data SSM“ .......................................................... 67

4.4.5 Loading POS and Stock Data into ODS Objects ..................................................... 83

4.4.6 Loading POS and Stock Data into InfoProviders ..................................................... 84

4.4.7 Reloading POS and Stock Data SSM ...................................................................... 85

4.4.8 Applying Hierarchy/Attribute Change ....................................................................... 85

4.5 Allocation ...................................................................................................................... 86

4.5.1 Creating InfoAreas ................................................................................................... 86

4.5.2 Creating InfoProviders ............................................................................................. 87

4.5.3 Creating Application Components ........................................................................... 89



4.5.6 Assigning InfoPackage to InfoSources and Loading Data ...................................... 91

4.5.7 Logging on to the Query Designer ........................................................................... 93

4.5.8 Creating Queries ...................................................................................................... 94

4.5.9 Allocation Settings – SAP ECC ............................................................................. 103

5 Adjust Steps Concerning Personalization ............................................................................ 108

5.1 Changing Merchandise Planning Flatfiles .................................................................. 108

5.1.1 InfoProvider 0RMP_C05 ........................................................................................ 108

5.2 Changing Assortment Planning Flatfiles .................................................................... 109

5.2.1 InfoProvider RT_C35 ............................................................................................. 109

5.3 Changing Allocation Flatfiles ...................................................................................... 110

5.3.1 InfoProvider RT_C01 ............................................................................................. 110

6 Appendix A: Helpful BI Actions............................................................................................. 110

6.1 Activating InfoProviders ............................................................................................. 110

6.2 Activating Update Rules ............................................................................................. 111

6.3 Activating Transfer Rules ........................................................................................... 111

6.4 Replicate DataSources .............................................................................................. 112

6.5 Deleting Data Requests ............................................................................................. 113

6.5.1 Basic InfoProvider .................................................................................................. 113

6.5.2 Real Time InfoProvider .......................................................................................... 114

6.6 Applying Hierarchy/Attribute Change ......................................................................... 115

7 Appendix B: Year Change Tasks ......................................................................................... 115

7.1 Maintaining Fiscal Year Variant ................................................................................. 115

7.2 Deleting Data Requests ............................................................................................. 115

7.3 Adjusting Flatfiles ....................................................................................................... 115

7.4 Loading Updated Flatfiles .......................................................................................... 116


© SAP AG of 116

BI Retail: Merchandise and Assortment Planning

1 Purpose This configuration guide provides the information you need to set up the configuration of this building block manually.

The configuration guide contains a lot of dependencies between the different sections. So it is very important that you go step by step through the configuration guide. Otherwise a correct installation of the BI System is not guaranteed.

2 Preparation Before you start installing this building block, you must install prerequisite building blocks. For more information, see the building block prerequisite matrix (Prerequisites_Matrix_[xx]_EN_IN.xls; the placeholder [xx] depends on the SAP Best Practices version you use, for example, Retail refers to the SAP Best Practices for Retail Package: Prerequisites_Matrix_RET_EN_IN.xls). This document can be found on the SAP Best Practices documentation DVD in the folder..\BBLibrary\General\.

3 Budget Customizing

Use The purpose of this activity is to define the Budget Customizing for the OTB and PPW. The customizing is done in the BI system and then transferred to the ECC system. When finishing the transfer process the budget types in ECC must be activated.

Prerequisites The following Configuration Guides must be completed:

- 761: BI Retail: Connectivity

- 762: BI Retail: Integration and Content Activation

- 763: BI Retail: Customizing and Master Data Extraction

3.1 Defining PPW Budget Levels – SAP BI

Use You must define budget levels and budget key figures. Within the budget level definition you select from an InfoProvider the characteristics that determine the budgets.

Procedure 1. Access the activity using one of the following navigation options:

IMG menu SAP Customizing Implementation Guide SAP NetWeaver

Business Intelligence Settings for BI Content Trade

Industries Retailing Budget Planning Budget Type Define Budget Levels


© SAP AG of 116

Transaction code SPRO

2. Choose New Entries.

3. On the New Entries: Overview of Added Entries screen, make the following entries:

Level InfoCube Long description

PPW 0RMP_C05 Merchandise Planning, Plan

4. Mark the entry PPW.

5. Double-click Level InfoObjects.



InfoObject Long description Hierarchy Fiscal Year Variant

0CM_CDT3 Segment

0CM_HIEID Hierarchy ID B1

0FISCPER Fiscal year / period

0FISCVARNT Fiscal year variant V3

0RT_SEASON Season Category

8. Choose Save.

9. Choose Back twice.

3.2 Defining OTB Budget Levels – SAP BI

Procedure 1. Choose New Entries.


Level InfoCube Long description

OTB 0RMP_C05 Merchandise Planning, Plan

3. Mark the entry OTB.

4. Double-click Level InfoObjects.



InfoObject Long description Hierarchy Fiscal Year Variant

0CM_CDT3 Segment

0CM_HIEID Hierarchy ID B1

0FISCPER Fiscal year / period

0FISCVARNT Fiscal year variant V3


7. Choose Save.



© SAP AG of 116

3.3 Defining PPW Key Figures - SAP BI

Use Within the key figure definition you select from the InfoProvider the key figures for which budgets are planned.

Exactly one key figure must be defined for the OTB application. In the PPW, a maximum of three key figures may be used because the Slow Seller Management process consists of three processes. You can have one budget for each process. You can also have one budget for all the three processes. This is the way we realized the PPW in the best practice environment.




Industries Retailing Budget Planning Budget Type Define Key Figures




Set keyfig InfoCube Long description

PPW 0RMP_C05 Merchandise Planning, Plan

4. Mark the entry PPW.

5. Double-click InfoObjects of Set.



InfoObject Long description

0RTSPRENSV Revaluation at Retail (Negative)/ Retail Value

8. Choose Save.


3.4 Defining OTB Key Figures - SAP BI



Set keyfig InfoCube Long description

OTB 0RMP_C05 Merchandise Planning, Plan

3. Mark the entry OTB.

4. Double-click InfoObjects of Set.





© SAP AG of 116


0RTTPRQUOTA Planned Open-To-Buy (Purchase Price)

7. Choose Save.


3.5 Defining PPW Budget Type - SAP BI

Use

You also have to define the characteristics of the budget type. To do this, you assign a budget level, a key figure set and the name of a transactional ODS object that is generated when the budget type is activated to each budget type.

The active budget type and the assigned budget level and key figure can then be transferred to SAP ECC.




Industries Retailing Budget Planning Budget Type Define Budget Types



3. On the New Entries: Details of Added Entries screen, make the following entries:

Field name Value

Application 1

Budge Type 01

Description Budge Type with PPW Check

Start Date Today

Finish date 9999.12.31

Budget Level PPW

Set of keyfigures PPW

DataStore Object PPW1

InfoArea 0TI_RT_MAP

Status budget type 1(automatically set)

Currency INR

4. Choose Save.

5. Choose Back.


© SAP AG of 116

3.6 Defining OTB Budget Types - SAP BI


2. On the New Entries: Details of Added Entries screen, make the following entries for Budget Type B1:

Field name Value

Application 2

Budge Type B1

Description Budge Type with OTB Check

Start Date Today


Budget Level OTB

Set of keyfigures OTB

DataStore Object OTBB1

InfoArea 0TI_RT_MAP


Currency INR

Delta activ Flag

Check Type OTB Complete check

3. Choose Save.

4. Choose Back.


6. On the New Entries: Details of Added Entries screen, make the following entries for Budget Type B2:

Field name Value

Application 2

Budge Type B2

Description Budget type with no OTB check

Start Date Today


Budget Level OTB

Set of keyfigures OTB

DataStore Object OTBB2

InfoArea 0TI_RT_MAP


Currency INR

Delta activ Deflag


© SAP AG of 116

Check Type OTB No check

7. Choose Save.

8. Choose Back.

3.7 Activating Budget Types - SAP BI

Use

The budget level, the key figure set and the name of a transactional DataStore Object that is defined for a budget type is generated when the budget type is activated.

The active budget type and the assigned budget level and key figure can then be transferred to SAP ECC.




Industries Retailing Slow Seller Management Budget

Planning Budget Type Activate Budget Types

Transaction code UPARI_BUDG01

2. On the Activation of Budget Type screen, make the following entries:

Application Budget Type Start Date

01 01 Creation Day

3. Choose Execute.

4. Choose Back.

5. On the Activation Budget Type screen, make the following entries:


02 B1 Creation Date

6. Choose Execute.

7. Choose Back.

8. On the Activation Budget Type screen, make the following of entries:


02 B2 Creation Date

9. Choose Execute.

10. Choose Back.

3.8 Creating RFC Destinations - SAP BI

Use


© SAP AG of 116

For the applications PPW and OTB you use this section to define the RFC connections to the ECC systems to which the Customizing settings for the budget types and the planned budgets are transferred using the Release Workbench or the budget monitor.

These settings are not transported. These settings must therefore also be made in a productive BW system to specify the RFC destination to a productive ECC system for the plan data transfer using the Release Workbench or the budget monitor.




Industries Retailing Budget Planning Transfer to SAP

ERP Create ERP RFC Destinations



3. On the New Entries: Details of Added Entries screen, make the following entries

Appl. Characteristic Value

InfoObject / Field name

RFC Destination SAP ERP

PPW (Price Planning Workbench)

4. Choose Back.

5. Open a new transaction. Go to transaction Sale Basic Settings Logical Systems Define Logical System.

6. Find out your ERP System > XXXCLNTXXX Logical System Best Practices.

7. Go back to Change View “Assignment RFC Destination to SAP ECC”: Overview screen, make the following entries manually into Field name RFC Destination SAP ERP:

Appl. Characteristic Value InfoObject / Field name


PPW (Price Planning Workbench)

The logical name of the ECC system

8. Choose Save.

9. Choose Back.


11. On the New Entries: Details of Added Entries screen, make the following entries

Appl. Characteristic Value

InfoObject / Field name


OTB (Open to Buy)

12. Choose Back.

13. On the Change View “Assignment RFC Destination to SAP ECC”: Overview screen, make the following entries with your ERP System > XXXCLNTXXX:

Appl. Characteristic Value InfoObject / Field name


OTB (Open to Buy) The logical name of the ECC system


© SAP AG of 116

14. Choose Save.

15. Choose Back.

3.9 Transferring Budget Types to SAP ECC – SAP BI

Use The purpose of this activity is transfer an active budget type and the assigned budget level and key figure set to SAP ECC. A corresponding RFC destination must be maintained.

A corresponding RFC destination must be maintained.




Industries Retailing Budget Planning Transfer to SAP

ERP Transfer Budget Types to R/3

Transaction code UPARI_BUDG02

2. On the Transfer of Budget Type screen, make the following entries:


01 01 Creation Day is displayed

3. Choose Execute.

4. Choose Back.



02 B1 Creation Day is displayed

6. Choose Execute.

7. Choose Back.



02 B2 Creation Day is displayed

9. Choose Execute.

10. Choose Back.

3.10 Assigning PPW Budget IDs – SAP ECC

Use Within the key figure definition for PPW you can have up to three Key Figures. It must be 3 different InfoObjects. For every key figure you defined you must assign a Budget ID. You can have up to three Budgets IDs.

There are three processes in the PPW. Three budgets are necessary if you want to assign the processes Markdown Price Plans, Manual Price Plans and Promotion Price Plans a different budget.


© SAP AG of 116

In the Best Practice environment there is only one budget defined for all the three process.

Prerequisites Customizing Tables were transferred successfully from SAP BI into SAP ECC.


IMG menu Logistics - General Price Planning Budget Planning Assign Budget Ids to Key Figures


2. Assign Budget ID 1=Key Figure 0RTSPRENGSV the number 1 as shown in the screen shot:

KeyFig.Set Name of Info Object Budget ID Description

PPW 0RTSPRENSV 1 Budget ID 1

3. Choose Save.

4. Choose Back.

3.11 Activating PPW Budget Type – SAP ECC

Use In this activity you activate the budget types to use the connected budgets in the operational applications.

Requirements

The budget types must be transferred from SAP BI. For price planning you assigned the required budget IDs to the key figures connected with the current budget.

Activities

Select the budget type that you want to activate and carry out activation. During activation the system automatically generates the database tables connected with the budget applications.


IMG menu Logistics - General Price Planning Budget Planning Activate Budget Types


The Budget Type has to be activated for the PPW. If the budgets have been activated, you can’t activate them again.

2. On the activate budget type screen, make the following entries:

Field name Description User action and values Note

Application PPW (Price Planning Workbench)

01 Use F4

Budget type 01 Use F4

Valid from Data create Use F4


© SAP AG of 116

3. Choose Execute to activate the budget. The log will be displayed with the message: Budget Type 01 was activated.


3.12 Checking and Extending OTB Budget Types – SAP ECC

Use In this activity you check the budget type data transferred from SAP BI. In addition you enhance the budget types of the OTB application with the budget determination settings.

Since you can use several budget types at the same time for the OTB application, enter in the budget types how you want the system to determine the correct budget type in budget determination. To do so, enter an implementation name of the Business Add-In WRF_BUDG_X_TYPE_E. The implementation checks if a particular budget type is relevant for the activity in question in the procurement process. By entering this prioritization you create a unique budget in case the system, in line with the checks in the implementation, determines several usable budget types.

To determine the budget value in the OTB check, you can enter a condition type from the costing sheet for the purchasing price determination in the purchase order. The system adopts the condition value that results from price determination for this condition type as a budget type.

Requirements

The budget types must be transferred from SAP BI. You must have created suitable implementation for the Business Add-In WRF_BUDG_X_TYPE_E.

Activities

Check the budget types transferred from SAP BI. Enhance the budget types for the OTB application with the budget determination settings.


IMG menu Material Management Purchasing Seasonal Procurement

Open-To-Buy(OTB) Budget Planning Check and Extend Budget Types


2. Choose the budget type for OTB B1.

3. Choose Details.

4. On the “Budget Types" Details screen, make the following entries:

Field name User action and values

Addin implementation WRF_BUDG_TYPE_001

Priority 5

Condition Type WOTB

5. Choose Save.

6. Choose Back.

7. Choose the budget type for OTB B2.

8. Choose Details.


© SAP AG of 116

9. On the "Budget Types" Details screen, make the following entries:


Addin implementation WRF_BUDG_TYPE_003

Priority 4

Condition Type WOTB

10. Choose Save.


3.13 Activating OTB Budget Types – SAP ECC

Use In this activity you activate the budget types to use the connected budgets in the operational applications.

Requirements

The budget types must be transferred from SAP BI. You completed the mapping for the info objects of the budget levels. You enhanced the settings for budget determination for the budget types of the OTB application.

Activities

Select a budget type that you want to activate and carry out activation. Repeat this for all required budget types. During activation the system automatically generates the database tables connected with the budget applications.



Open-To-Buy(OTB) Budget Planning Activate Budget Types


2. On the Activate Budget Types screen, make the following entries:

Field name Description User action and values

Note

Budget Application OTB (Open-To-Buy) 02

Budget Type B1 Use F4

Valid from Date Create Use F4

3. Choose Execute to activate the budget. The log will be displayed with the message: Budget Type B1 was activated.

4. Choose Back.



Budget Application OTB (Open-To-Buy) 02



© SAP AG of 116

6. Choose Execute to activate the budget. The log will be displayed with the message: Budget Type B2 was activated.


3.14 Reorganization of OTB Budgets – SAP ECC

Use

Only execute this step if errors occurred during transferring OTB types in the ECC System.

Then the only way to solve them is to reorganize the incorrect OTB budget types B1 and B2.

3.14.1 Determining the Generated Budget Plan Table


SAP ECC menu Tools ABAP Workbench Overview Data Browser

Transaction code SE16

2. On the Data Browser: Initial Screen, make the following entries:


Table Name WRFT_BUDG_TYPE

3. Choose Table Contents.

4. On the Data Browser: Table WRFT_BUDGET_TYPE: Selection Screen, make the following entries:


APPL 02

TYPE B1

5. Choose Execute.

6. On the Data Browser: Table WRFT_BUDGET_TYPE: Select Entries screen, make the following entries:


Flag the entry

7. Choose Choose.

8. Write down or copy the TABNAME PLAN. It could be like /1WRF/01002AB1P.

3.14.2 Comparing Corresponding Structure with Budget DataStore Object

Procedure


© SAP AG of 116

1. Choose Create New Session to open a second session.

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

SAP ECC menu Tools ABAP Workbench Development ABAP Dictionary


3. Flag the entry Database table.

4. On the ABAP Dictionary: Initial Screen, make the following entries:


Database Table The name of the Plan Table from the previous chapter enlarged with “S”.

For example: /1WRF/01002AB1PS

5. Choose Display.

6. Choose Create New Session to open a third session.





Field name User action and values Comment

Database Table *OTBB1* *Use F4 Help

A database table like /BIC/AOTBB100 is automatically found.

9. Choose Display.

10. Now compare the components of the structure /1WRF/01002AB1PS with the Field names of the budget DataStore Object /BIC/AOTBB100.

The best way to compare them is to compare the column Short Description. The Field name order must be the same.

3.14.3 Deleting Structure and Table Type for the Generated Plan Table

Use If the result of the comparison of the previous subchapter is negative then you must delete the structure and the table type of the plan table you found in the first subchapter.

First delete the table type, and then delete the structure.





© SAP AG of 116

2. Flag the entry Data type.



Database Table The name of the Plan Table from the first subchapter enlarged with “T”.

For example: /1WRF/01002AB1PT

4. Choose Delete.

5. Choose Continue in the upcoming Information dialog box.

6. Choose Yes in the next screen Delete Table Type /1WRF/01002AB1PT.

7. Flag the entry Database table.



Database Table The name of the Plan Table from the first subchapter enlarged with “S”.

For example: /1WRF/01002AB1PS

9. Choose Delete.

10. Choose Yes on the Delete Structure /1WRF/01002AB1PS screen.

3.14.4 Reorganizing Budget Types

Use Now you have to reorganize the budget types B1 and B2 in the SAP ECC Customizing. That means table contents concerning the definition of budget types will be deleted.



Open-To-Buy(OTB) Budget Planning Reorganize Budget Types




Budget Application OTB (Open-To-Buy)

02


3. Choose Execute to reorganize the budget. A log will be displayed.

4. Choose Enter.

5. Choose Back.

3.15 Changing Type Group /MAP/ - SAP BI

Use


© SAP AG of 116

The purpose is to change the type group /MAP/.




2. On the ABAP Dictionary: Initial Screen, select Type Group.

3. Maintain the Type Group with value /MAP/.

4. Choose Change.

5. Confirm the information.

6. On the upcoming screen, choose Maint. In logon lang.

7. Choose the SourceCde tab.

8. ReplaceTYPES: /map/_t_rscrmvarp_t TYPE STANDARD TABLE OF /map/_s_rscrmvarp WITH NON-UNIQUE DEFAULT KEY with TYPES: /map/_t_rscrmvarp_t TYPE STANDARD TABLE OF RSCRMVARP WITH NON-UNIQUE DEFAULT KEY.

9. Choose Save.

10. Choose Active.

11. Choose Back.

3.16 Changing Function Module /MAP/SSM_CREATE_WORK_ITEMS_RFC

Use The purpose is to change the function module /MAP/SSM_CREATE_WORK_ITEMS_RFC.



SAP ECC menu Tools ABAP Workbench Development Function Builder

2. On the Function Builder: Initial Screen, maintain the Function Module with /MAP/SSM_CREATE_WORK_ITEMS_RFC.

3. Choose Change.

4. Confirm the information.

5. On the upcoming screen, choose Maint. In logon lang.

6. Choose Tables tab.

7. Replace the value /MAP/_S_RSCRMVARP in the column Associated Type by RSCRMVARP for the parameter I_T_BW_VARSEL.

8. Choose Save.

9. Choose Active.

10. Choose Back.


© SAP AG of 116

4 Transactional Data Extraction via Flatfiles – SAP BI

Use The planning process Merchandise Planning and Assortment Planning are based on transactional data that are stored in different InfoProviders.

The actual transactional data would be coming from the ECC system. Because in the Best Practice environment there is no transactional actual data from an ECC system data will be loaded via flatfiles. To start in the planning environment with reasonable data, transactional plan data will also be loaded via flatfiles. So the whole transactional data base for planning is simulated by flatfiles.

InfoProviders for actual data must be InfoProviders of type Standard. They can only be filled with data from a source system.

InfoProviders for plan data must be InfoProviders of type Real Time. They can only be filled with data in planning layouts.

Loading data via flatfiles into the BI System presupposes that the interface has been installed. Parts of the interface definition are Update Rules, InfoSources, Transfer Rules and InfoPackages. If the interface installation has been finished the different flatfiles for an InfoProvider can be loaded.

The data loading process is described for Standard and Real Time InfoProviders because it is a different one. You can load the flatfiles repeatedly. However you must delete the data requests in the different InfoProviders before you load the flatfiles again. Otherwise the data will be duplicated in the InfoProviders.

4.1 Creating Application Components

Use The purpose of this activity is to create an application component as a method to structure InfoSources. Here the need for the MAP transactional data is realized.


SAP BI menu Information Systems Business Information Warehouse

Modeling Data Warehousing Workbench: Modeling

Transaction code RSA1

2. On the Data Warehousing Workbench: Modeling screen, choose InfoSources.

3. Follow the application path SAP Application Components SAP Sectors Trade Industries

Retailing Merchandise and Assortment Planning.

4. Right click the component Merchandise and Assortment Planning.

5. Choose Create application component …

6. Enter the following data in the upcoming dialog box:


Application comp. ZRT_MAPN_TD

Long Description MAP Transactional Data


© SAP AG of 116

7. Choose Continue.

4.2 Merchandise Planning

4.2.1 Creating InfoSources and Transfer Rules

Use Loading data via flatfiles into the BI System presupposes the definition of an interface.

In this chapter the creation of InfoSources and Transfer Rules is described. We create 3.x InfoSources because the Business Content is based on SAP BI Version 3.5.

The steps described under Procedure must be executed concerning the InfoProvider:

InfoProvider Description

0RMP_C05 Merchandise Planning, Plan







Retailling Merchandise and Assortment Planning MAP Transactional Data.

4. Right click MAP Transactional Data.

5. Follow the context menu path Additional Functions Create InfoSource 3.x.

6. In the Create InfoSource dialog box enter the following data:


InfoSource RT_IS_0RMP_C05

Long description InfoSource 0RMP_C05

7. Choose Continue.

8. Right click the InfoSource RT_IS_0RMP_C05.

9. Choose Change.

10. Choose Transefer.

11. Choose Template.

12. Flag in the Field name of InfoCube.

13. Enter as InfoCube 0RMP_C05.

14. Choose Transfer.

15. Choose Transfer all InfoObjects.

16. Choose Activate.

17. Choose Yes in the upcoming dialog box.

18. Choose Back.

19. Choose Collapse to close the Communication_Sturct.

20. Choose Expand to open the Transfer_structure/Transfer_Rules.


© SAP AG of 116

21. Enter the following data:


Source System FILE by Choosing the Button

22. Choose Yes in the upcoming screen Save Changes ? The system will automatically propose the transfer rules.


24. Choose Back.

4.2.2 Assigning Update Rules to InfoProviders

Use This chapter describes the creation of Update Rules.

The steps described under Procedure must be executed concerning the InfoProviders:

InfoProvider Description

0RMP_C05 Merchandise Planning, Plan





2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.

3. Choose Search and enter the following data:


Find 0RMP_C05

4. Choose Search.

5. Right click the InfoProvider 0RMP_C05

6. Follow the context menu path Additional Functions Create Update Rules.

7. Flag in the Field name of InfoSource on the Update rules create: Start screen.

8. Enter as InfoSource RT_IS_0RMP_C05.

9. Choose Continue.

10. Choose Activate On the Update rules create: Rules.

11. Choose Back.

12. Choose Refresh subtree to refresh the application component.

4.2.3 Executing Info packages for Real Time InfoProvider

Use You must customize infoProvider 0RMP_C05 so that it can be loaded with data.

Normally a Real Time InfoProvider can’t be loaded with data. It is filled with data only in the planning environment. To have plan data in the planning layouts the InfoProvider must also be provided with transactional data via flatfiles.


© SAP AG of 116

The steps described under Procedure must be executed for InfoProvider:

InfoProvider Description Flatfiles to Load

0RMP_C05 Merchandise Planning, Plan is a Real Time InfoCube

Flatfile_0RMP_C05_MCP_2008_BU_0001.csv Flatfile_0RMP_C05_MCP_2008_BU_0002.csv Flatfile_0RMP_C05_MCP_2009_0001.csv Flatfile_0RMP_C05_MCP_2009_0002.csv Flatfile_0RMP_C05_MCP_2009_oSeg.csv Flatfile_0RMP_C05_MCP_2010_BU_0001.csv Flatfile_0RMP_C05_MCP_2010_BU_0002.csv Flatfile_0RMP_C05_MCP_2011_BU_0001.csv Flatfile_0RMP_C05_MCP_2011_BU_0002.csv Flatfile_0RMP_C05_MP1_2009.csv

You can load the flatfiles repeatedly. However before you load them again you must delete the data request from the InfoProvider. How to do this you find in the chapter 6.5 Delete Data Requests.

Prerequisites Check the computer’s regional language setting. It must be English (United States).

For the creation of an InfoPackage you need to enter a csv-file. The flatfiles are stored on the Documentation SAP Best Practices CD in the folder \Misc\Retail\IN\Flatfiles. They must be installed on your hard disk or any of your file server.

In this chapter you load in this the flatfiles for Merchandise Planning. They are stored in the csv folder within the folders Plan_Merch.






3. Choose Search.

4. Enter the following data in the upcoming screen:


Find 0RMP_C05

5. Choose Search.

6. Right click 0RMP_C05

7. Choose Change Real-Time Info Cube Load Behavior.

8. Flag the entry Real-Time Data Target can be loaded with data; planning not allowed.

9. Choose Continue.

Create InfoPackage to load the data:

1. Expand 0RMP_C05RT_IS_0RMP_C05.

2. Expand InfoSource 0RMP_C05.

3. Expand from RT_IS_0RMP_C05 for FILE.

4. Right click RT_IS_0RMP_C05.

5. Choose Create InfoPackage.

6. In the Create InfoPackage dialog box, enter the following data:


© SAP AG of 116


InfoPackage Description Flatfile Load: Transactional Data 0RMP_C05

7. Select the line for RT_IS_0RMP_C05 in the section DataSource.

8. Choose Save.

9. For the InfoProviders 0RMP_C05 you may have the Monitor:Mesages creen

The InfoProvider isn’t loadable with data because it is a Real Time InfoProvider and is in planning mode. You can ignore thes message at this point, because you don’t want to load data. You only want to create InfoPackages.

10. Choose Close to close the screen and continue with the next step.

11. Choose Hide/Show Navigator.

12. Choose the tab page External data and make the following entries:

Field name Values Notes

Load external data from Client workstation

File type

The flatfiles are csv files.

Name of file Use F4, input help to open the folder for your flatfiles

See the comments in the prerequisites paragraph of this chapter. Choose the first flatfile Flatfile_0RMP_C05_MCP_2008_BU_0001.csv

Data Separator , The data seperator depends on the computer’s Regional and Languages Options. The used data separator is defined for English (United States). Using not this seperator requires to recreate the flatfiles with your current regional settings. Then you have to enter this Data Seperator here.

Escape Sign " See remark for Data Seperator !

Separator for Thousands , See remark for Data Seperator !

Character used for Decimal Point

. See remark for Data Seperator !

Currency Conversion for External Systs

unflag

Number of Header Rows to be Ignored

1

13. Choose the Processing tab page and make the following entry:

Field name Value

PSA and then into Data Targets

14. Choose the tab page Data targets and set the indicator in the Field name of Select Data Targets.

15. Select the InfoProvider 0RMP_C05 under the Field name Updating the data target.

16. Choose the tab page the Update tab page and make the following entries:


© SAP AG of 116

Field name Values

Update Mode Mark Full update

Data Update Type in the Data Target Mark Always update data, even if no master data exists for the data

17. Choose Save.

18. Choose Hide/Show Navigator .

19. Go to the External Data tab

20. Choose the first flatfile Flatfile_0RMP_C05_MCP_2008_BU_0001.csv. It should already have been chosen from the previous chapter.

21. Go to the Schedule tab.

22. Choose Start. You get the status message Data was requested.

23. Choose Monitor in the board.

24. Choose Refresh tree on the Monitor - Administrator Workbench screen until the status of your request is successful. That means your request obtained a green traffic light.

25. Choose Back.

26. Load the other flatfiles for the InfoProvider 0RMP_C05 the same way.

27. Choose Back.

28. Right click 0RMP_C05.

29. Choose Real-Time Info Cube Load Behavior.

30. Flag the entry Real-Time Data Target can be planned; data loading not allowed.

31. Choose Continue.

Result

Check if there are data requests with a red traffic light by using a Right click the InfoProvider and choosing Change. If there are such data requests you must change them to data requests with green traffic lights and delete them. You will find how to do this you find in Appendix C, chapter Deleting Data Requests.

4.2.4 Releasing PPW Budget

Use The purpose of this activity is to release the budget needed for the Slow Seller Management Process.

Procedure 1. First execute the following transaction to get the menu for Slow Seller Management:

Transaction code UPAR


SAP BI menu Merchandise Planning Budget Monitor

Transaction code UPARI_BUDGA

3. On the Budget type tab enter the following data:

Field name Value Comment


© SAP AG of 116

Application 01 PPW (Price Planning Workbench) Use F4-Help

Budget Type 01 Use F4-Help

InfoObjects of Budget type

Start Date Created Date Use F4-Help

4. On the InfoObjects of Budget type tab enter the following data:

Field name Value Comment

Segment must not be filled

Fiscal year/period from XXX.2009 XXX is the current month

Fiscal year/period to 001.2011

Season from 0001

Season to 0002

5. On the Additional Filter tab enter the following data:

Field name Value

Past

Current

Future

No difference

Difference with tolerance

Difference exceeds tolerance

Planned value not yet released

Version MCP

6. Choose Execute.

7. Choose Select all to select all records.

8. Choose Release budget.

9. Choose Continue in the upcoming dialog box.

10. Choose Display Current log. A log displayed.

4.2.5 Releasing OTB Budget

Use The purpose of this activity is to release the budget needed for the Open to Buy Process.

Procedure 1. In the same way as in the previous chapter release the budget type B1 for OTB.

2. On the Budget type tab page, enter the following data:

Field name Values Comment

Application 02 OTB (Open to Buy) Use F4-Help

Budget Type B1 Use F4-Help


© SAP AG of 116

InfoObjects of Budget type

3. On the InfoObjects of Budget type tab page, enter the following data:

Field name Values Note

Segment Optional, must not be filled

Fiscal year/period from XXX.2009 XXX is the current month

Fiscal year/period to 012.2011

Season from 0001

Season to 0002

4. On the Additional Filter tab, enter the following data:

Field name Values

Past

Current

Future

No difference

Difference with tolerance

Difference exceeds tolerance

Planned value not yet released

Version MCP

5. Choose Execute.

6. Choose Select all to select all records.

7. Choose Release budget.

8. Choose Continue in the upcoming dialog box.

9. Choose Display Current log to see the log.

4.2.6 Assigning Price Planner Groups to Budget – SAP ECC

Prerequisites If you use Markdown Budgets, you have to use Price Planner Groups. If a user is not assigned to a Price Planner Group he cannot work in PPW Procedure.

Procedure 1. Access the activity in the SAP ECC System using one of the following navigation options:

IMG menu Logistics Retailing Master Data Price Planning

Budgets Authorization Administration for Budget Access Assign Price Planner Groups to Budget

Transaction code WRF_PPW10

2. Maintain the following entries:

Key Field names of Budget Data Values

Hierarchies node Blank


© SAP AG of 116

Key Field names of Budget Data Values

Hierarchy B1

Season 0001 and 0002

Price planner group PPW1

Add Budgets without Price planner Group to the selection flag

3. Choose Execute.

4. Mark the whole screen.

5. Choose Mass change.

6. Select the budget attributes and define the following values:

Select Budget attributes Entries

Flag Price planner group PPW1

Flag Tolerance Type 01

Flag Tolerance % 10

Flag Tolerance abs blank

7. Execute and save your result.

4.3 Assortment Planning

4.3.1 Defining Key Figures – SAP BI

Use The purpose of this activity is to define new key figures that are needed in the assortment planning scenario.

Procedure 1. Access the activity in the SAP BI System using one of the following navigation options:




2. On the Data Warehousing Workbench: Modeling screen, choose InfoObjects

3. Follow the application path Industry Sectors Trade Industries Retailing Merchandise and Assortment Planning.

4. Right click Assortment Planning.

5. Choose Create InfoObject Catalog.



InfObjCat RT_AP_KEYF

Description MAP Assortment Planning Key Figures

InfoObjext Type Key Figure


© SAP AG of 116

7. Choose Create.

8. Choose Activate.

9. Right click the InfoObject Catalog MAP Assortment Planning Key Figures.

10. Choose Create InfoObject.

11. Enter the following data On the Create Key Figure:


KeyFig. RT_GRNNPV

Long Description Goods Receipt Cost Value, Net Net


13. On the Create Key Figure RT_GRNNPV: Detail screen, enter the following data


Short Description GR CV/NN

14. Enter the following data on the Type/unit tab page:


Type/Data Type Amount

Data Type CURR – Currency Field name, stored as DEC

Unit / currency 0LOC_CURRCY

15. Enter the following data on the Aggregation tab page:


Aggregation SUM

Exception Aggregat. Summation

Cumulatative val Selected

16. Enter the following data on the Additional Properties tab page:


Decimal Places Not defined

Display Not defined

Bex description Short description


18. In exact the same manner create the key figures with the key figure type Amount:

Key Figure Long Description Short Description Type Unit/Currency

RT_AVP Average Price Average Price Amount 0LOC_CURRCY

RT_PP Purchase Price Purchase Price Amount 0LOC_CURRCY

RT_PPNET Purchase Price Net Purchase Price Net Amount 0LOC_CURRCY

RT_SP Target Sales Target Sales Amount 0LOC_CURRCY

RT_SPTAX Target Sales with TAX

Target Sales with TAX

Amount 0LOC_CURRCY


© SAP AG of 116

19. In exact the same manner create the key figures with the key figure type Integer:

Key Figure Long Description Short Description Type Unit/Currency

RT_NUMAT Number of Article Number of Article Integer empty

RT_NUMST Number of Stores Number of Stores Integer empty

20. In exact the same manner create the key figures with the key figure type Number:

Key Figure Long Description

Short Description Type Unit/Currency

RT_TAX Tax % Tax % Number empty

21. In exact the same manner create the key figures with the key figure type Quantity:

Key Figure Long Description

Short Description Type Unit/Currency

RT_QUAN Sales Quantity Sales Quantity Quantity 0BASE_UOM

RT_SQUBST Sales Quantity by Store

Sales Quantity by St

Quantity 0BASE_UOM

4.3.2 Maintaining Values for Key Figure 0RT_KEYFIG

Use The purpose of this activity is to manually maintain values for the key figure 0RT_KEYFIG. These values are needed within the assortment planning scenario.

Procedure 1. Access the activity in the SAP BI System using one of the following navigation options:




2. On the Data Warehousing Workbench: Modeling screen, choose InfoObjects.

3. Choose Search.



Find 0RT_KEYFIG

5. Choose Search.

6. Right click the InfoObject 0RT_KEYFIG.

7. Choose Maintain Master Data.



Language EN

9. Choose Execute.

10. Choose Create.



© SAP AG of 116


Key Figure ID IF

Short Description Initial Fix


13. Choose Create.



Key Figure ID IV

Short Description Initial Variable


16. Choose Save.

17. Choose Back.

4.3.3 Creating InfoProviders

4.3.3.1 Creating Real Time InfoProviders

Use The purpose of this activity is to create the Real Time InfoProvider in which the actual and plan transactional data are stored.






3. Follow the application path Industry Sectors Trade Industries Retailing Merchandise and Assortment Planning

4. Right click the InfoArea of Assortment Planning.

5. Choose Create InfoCube.



InfoCube RT_C35

Description Assortment Planning Plan, Month

InfoArea 0RT_MAPN_AP

Copy from

InfoProvider Type Standard InfoCube

Real Time Flag

7. Choose Create.


© SAP AG of 116

In the next window you create the following characteristics, time characteristics and key performance indicators for the InfoProvider:

● Characteristics:

○ 0CM_HIEID Hierarchy ID

○ 0CM_CDT1 Material group

○ 0CM_CDT2 Hierarchy ID

○ 0CM_CDT3 Segment

○ 0DISTR_CHAN Subsegment

○ 0SALESORG Store

○ 0CM_MCATDIV Industry

○ 0VERSION Version

○ 0RT_SEASON Season Category

○ 0RT_SKUROLL Rollout

○ 0RT_SEASYR Season Year

○ 0RT_ASORT Assortment

○ 0RF_ASTYP Assortment Type

○ 0RT_KEYFIG Key Figure ID

● Time characteristics:

o 0FISCPER Fiscal year / Period

o 0FISCPER3 Posting Period

o 0FISCVARNT Fiscal Year Variant

o 0FISCYEAR Fiscal Year

● Key performance indicators:

o 0CPBAINSABU Sales / Base Unit of Measure

o 0CPBAINSAPV Sales / Cost Value

o 0CPBAINSASV Sales / Retail Value

o 0RTMARGPERC Margin %

o RT_NUMAT Number of Article

o RT_NUMST Number of Store

o RT_PP Purchase Price

o RT_PPNET Purchase Price Net

o RT_QUAN Sales Quantity

o RT_SP Target at Sales

o RT_SQUBST Sales Quantity at Store

o 0CPGRPDVBU Goods Receipt Posting Date / Vendor BUn

o 0CPGRPDVPV Goods Receipt Posting Date / Vendor Cost Value

o 0RTGRPDVST GR Posting Date / Vendor RtIT

o 0RTGRPDVSV Goods Receipt Posting Date / Vendor Retail Value

o RT_GRNNPV Goods Receipt Cost Value, Net Net

o RT_AVP Average Price

o RT_TAX Tax %


© SAP AG of 116

o RT_SPTAX Target at Sales with TAX

8. Open the folder Demensions and right click Dimension 1.

9. Follow the menu path Properties.


You can do it by copy and paste.


Description Consumer Decision Tree


12. Right click Dimensions..

13. Follow the context menu path Create New Dimensions:

14. Enter the following data in the screen Create Dimensions:



Description Version

15. Choose Create Another Dimension.

Enter the following data in the screen Create Dimensions:


Description Season





Description Assortment




Description Key Figure ID


21. Right click the dimension Time.

22. Choose InfoObject Direct Input and insert the following characteristics into the dimension Time:

InfoObject Description

0FISCPER Fiscal Year/Period

0FISCPER3 Posting Period

0FISCVARNT Fiscal Year Variant

0FISCYEAR Fiscal Year



© SAP AG of 116

To fill the dimensions Consumer Decision Tree, Version, Season and Assortment with characteristics act in the same way as you did it for the dimension Time.

24. Insert the following characteristics into the dimension Consumer Decision Tree. You can do it by copy and paste.


0CM_HIEID Hierarchy ID

0CM_CDT1 Category

0CM_CDT2 Subcategory

0CM_CDT3 Segment

0DISTR_CHAN Distribution Channel

0SALESORG Sales Organization

0CM_MCATDIV Industry

25. Insert the following characteristics into the dimension Version. You can do it by copy and paste.


0VERSION Version

26. Insert the following characteristics into the dimension Season. You can do it by copy and paste.



0RT_SKUROLL Rollout

0RT_SEASYR Season Year

27. Insert the following characteristics into the dimension Assortment. You can do it by copy and paste.


0RT_ASORT Assortment

0RF_ASTYP Assortment Type

28. Insert the following characteristics into the dimension Key Figure ID. You can do it by copy and paste.


0RT_KEYFIG Key Figure ID

To assign key figures to the InfoProvider proceed as follows.

29. Right click Key Figures.

30. Choose InfoObject Direct Input.

31. Insert the following key figure. You can do it by copy and paste.


0CPBAINSABU Sales / Base Unit of Measure


© SAP AG of 116


0CPBAINSAPV Sales/Cost Value

0RTBAINSASV Sales / Retail Value

0RTMARGPERC Margin %

RT_NUMAT Number of Article

RT_NUMST Number of Stores

RT_PP Purchase Price

RT_PPNET Purchase Price Net

RT_QUAN Sales Quantity

RT_SP Target Sales

RT_SPTAX Target Sales with TAX

RT_SQUBST Sales Quantity by Store

0CPGRPDVBU Goods Receipt Posting Date / Vendor BUn

0CPGRPDVPV Goods Receipt Posting Date / Vendor Cost Value

0RTGRPDVST GR Posting Date / Vendor RtlT

0RTGRPDVSV Goods Receipt Posting Date/Vendor Retail Value

RT_GRNNPV Goods Receipt Cost Value, Net Net

RT_AVP Average Price

RT_TAX Tax %




4.3.4.1 Creating InfoSources and Transfer Rules for RT_C35

Use The purpose of this activity is to install the transfer rules for the loading of transactional data in the InfoProvider RT_C35 Assortment Planning Plan, Month via flatfiles.







Retailing Merchandise and Assortment Planning MAP Transactional Data.


© SAP AG of 116

4. Right click the Application Component MAP Transactional Data.




InfoSource RT_IS_RT_C35

Long description InfoSource RT_C35

7. Choose Continue.

8. Right click the InfoSource RT_IS_RT_C35.

9. Choose Change.


11. Choose Templete on the right hand side.

12. Flag in the field of InfoCube and enter RT_C35.


14. Choose Transfer all InfoObjects.



17. Choose Back..

18. Choose Collapse to close the Communication_Struct.

19. Choose Expand to open the Transfer_strucutre/Transfer_Rules



Source System FILE by Choosing



27. Choose Back.


Use The purpose of this activity is to install update rules in order to prepare the data transfer into the InfoProvider 0RT_C35 Assortment Planning Plan, Month.








Find RT_C35


© SAP AG of 116

4. Choose Search.

5. Right click the InfoProvider RT_C35.


7. Flag in the field of InfoSource on the Update rules create: Start screen and enter RT_IS_RT_C35.

8. Choose Continue.

9. The next screen will show the update rule on the right hand side.


11. Choose Back.

4.3.6 Assigning InfoPackage to InfoSources and Loading Data

Use Loading data via flatfiles into the BI System presupposes that the interface has been defined. In this chapter the last step, the creation of an InfoPackage, and the loading of transactional data is described.

The steps listed under Procedure must be executed concerning the InfoProviders in the table below. In the table you find also the flatfiles that must be loaded.


RT_C35 Assortment Planning Plan, Month

Flatfile_RT_C35_Fashion_2008 Flatfile_RT_C35_Fashion_2009


For the creation of an InfoPackage you need to enter a csv-file. The flatfiles are stored on the Documentation SAP Best Practices CD in the folder \Misc\Retail\IN\Flatfiles. They must be installed on your hard disk or any of your file server. An installation in this way is important because you have defined in the InfoPackage that an external load takes place from a client workstation.

In this chapter you load in this the flatfiles for Assortment Planning. They are stored in the csv folder within the folder Plan_Assort.


© SAP AG of 116

4.3.6.1 Assigning InfoPackage to InfoSources and Loading Data for RT_C35

Use Working with the InfoProvider RT_C35 you must customize that the InfoProvider can be loaded with data.

Normally a Real Time InfoProviders can’t be loaded with data, but is filled with data only in the planning environment.

The steps described under Procedure must be executed for this InfoProvider:


RT_C35 Assortment Planning Plan, Month

Flatfile_RT_C35_Fashion_2008 Flatfile_RT_C35_Fashion_2009

You can load the flatfiles repeatedly. However before you load them again you must delete the data request from the InfoProvider. How to do this you find in the chapter 6.5 Delete Data Requests.






3. Choose Search.



Find RT_C35

5. Choose Search.

6. Right click RT_C35.

7. Choose Change Real-Time Info Cube Load Behavior.


9. Choose Continue.

10. Expand RT_C35RT_IS_RT_C35.

11. Expand InfoSource RT_C35.

12. Expand from RT_IS_RT_C35 for FILE.

13. Right click RT_IS_RT_C35.

14. Follow the menu path Create InfoPackage.



InfoPackage Description Flatfile_RT_C35_Fashion_2008


© SAP AG of 116

16. Select the line for RT_IS_RT_C35 in the section DataSource.

17. Choose Save.

18. Choose Hide/Show Navigator

19. For the InfoProviders RT_C35 you may have the Monitor:Mesages screen

The InfoProvider isn’t loadable with data because it is a Real Time InfoProvider and is in planning mode. You can ignore thes message at this point, because you don’t want to load data. You only want to create InfoPackages.

20. Choose the External data tab page and make the following entries:



File type



See the comments in the prerequisites paragraph of this chapter. Choose the first flatfile Flatfile_RT_C35_Fashion_2008.csv




Character used for Decimal Point . See remark for Data Seperator !

Currency Conversion for External Systs unflag

Number of Header Rows to be Ignored 1

21. Choose the Processing tab page and make the following entry:

Field name Value


22. Choose the tab page the Update tab page and make the following entries:

Field name Values




© SAP AG of 116

23. Choose Save.

24. Go to tab tab page Schedule.


26. Choose Monitor in the board

27. Choose Refresh tree on the Monitor - Administrator Workbench screen until the status of your request is successful. That means your request obtains a green traffic light.

Be aware that if you have data requests with a red or yellow traffic light there will be no data selected in a query. You must change them to data requests with green traffic lights.

28. Choose Back

29. In this way load step by step the other flatfiles for the InfoProvider RT_C35.

Result

Be aware that if you have data requests with a red traffic there will be no data selected in a query. That means the Query RT_RTC35_Q0001 Key Figures Assortment Planning will not provide any result.

Check if there are data requests with a red traffic light by using a Right click the InfoProvider and choosing Change. If there are such data requests you must change them to data requests with green traffic lights and delete them. How to do this you find in Appendix C, chapter Deleting Data Requests.


© SAP AG of 116

4.3.7 Logging on to the Query Designer

Use You have to use the Query Designer SAP BW 3.x. To preferred method to access the Query Designer is described in the chapter Microsoft Office Start Menu 4.3.7.2. Microsoft Office Start Menu.

4.3.7.1 Transaction RRMX

Procedure 1. Access the activity using the following navigation:

Transaction code RRMX

That means you create a query using transaction RRMX - Analyzer and the SAP BI front end Excel from which the Query Designer can be started. You must verify that you are working with the 3.x Query Designer.

2. Choose and choose About.

If you find a screen with the following information you are working with the right version.

Otherwise you have to change settings for the BEX Analyzer. Therefore execute the next steps.

3. Choose BEx Analyzer.

4. Follow the menu path Global Settings.

5. Set the flag in the field of Launch legacy version from RRMX.

6. Repeat step (1) and (2).

7. Choose Tools.

8. Choose Query Designer.

4.3.7.2 Microsoft Office Start Menu


Microsoft Office Start Menu

Start All Programs Business Explorer Business Explorer

(SAP BW 3.x) Query Designer (SAP BW 3.x)


© SAP AG of 116

2. Log on with your user in the upcoming SAP Logon screen to the BI System.

4.3.8 Creating Queries

Use Plan values of assortment key figures can be accessed in the ECC system. Therefore a BADI has to be utilized. The BADI itself uses a query to get data from the InfoProvider RT_C35. Assortment Planning Plan, Month.

Prerequisites The variable used in the query must be activated. Refer to chapter Activating Business Content, Query Variables.

Procedure 1. Choose New Query.

2. Choose Technical Name on/off in the board.

3. Choose from the menu Industry SectorsTrade Industries Retailing Merchandise and

Assortment Planning Assortment Planning

4. Double-click the InfoProvider of Assortment Planning Plan, Month RT_C35.

4.3.8.1 Creating Query RT_RTC35_Q0001

Procedure The following two steps explain how you Drag and Drop:

1. Expand for example, the hierarchy tree of Consumer Dimension Tree. You can see several characteristics, choose Hierarchy ID.

2. Now click and hold down the Left-Mouse-Button on the node of Hierarchy ID.

3. Move the mouse into the desired frame, in our case the frame Rows.

4. Release the Left-Mouse-Button.

5. Insert via Drag and Drop the further InfoObjects into the frame Rows:

Field name Description


0CM_CDT1 Category

0CM_CDT2 Subcategory

0CM_CDT3 Segment

0RT_SEASON Season

0RT_SEASYR Season Year

0FISCPER3 Posting period

0RF_ASTYP Assortment Type

0RT_ASORT Assortment

0RT_KEYFIG Key Figure ID

0LOC_CURRCY Local Currency


© SAP AG of 116

0BASE_UOM Base Unit

6. Insert via Drag and Drop into the frame Filters:


0VERSION Version

0REQUID Request ID

7. Insert via Drag and Drop into the frame Columns:


RT_GRNNPV Goods Receipt Cost Value, Net Net

0CPGRPDVPV Goods Receipt Posting Date / Vendor Cost Value

0RTGRPDVST GR Posting Date / Vendor RtlT

0RTGRPDVSV Goods Receipt Posting Date/Vendor Retail Value

RT_SQUBST Sales Quantity by St

RT_NUMAT Number of Article

RT_NUMST Number of Stores

Now restrictions must be set in form of variables for the frames Filter, Free Characteristics, Rows and Columns.

8. Right click the node of Version in the frame Filters.

9. Choose Restrict.

10. Select the tab of Variables.

11. Right click Assortment Plan Plan Version.

12. Choose Technical Names.

13. Choose Add.

14. Choose OK.

15. Restrict in this way the InfoObject Request ID in the frame Filter with the following variable:

Variable Description Variable Represents Variable entry is

0S_RQMRC Most current data Single Value Mandatory

16. Restrict in this way the InfoObject 0CM_HIEID in the frame Rows with the following variable:


0CMHIEID CDT Hierarchy ID Single Value Mandatory

17. Restrict in this way the InfoObject Category in the frame Rows with the following variable:


0S_CATG Category List Multiple Single Value Optional

18. Restrict in this way the InfoObject Subcategory in the frame Rows with the following variable:


0S_SCAT Subcategory List Multiple Single Value Optional


© SAP AG of 116

19. Restrict in this way the InfoObject Segment in the frame Rows with the following variable:


0P_SEGM Category Management: Segment

Single Value Mandatory

20. Restrict in this way the InfoObject Season in the frame Rows with the following variable:


0P_SEASO Required Entry Field name: Single Value for Season Category


21. Restrict in this way the InfoObject Season Year in the frame Rows with the following variable:


0P_SEAY1 Season Year Single Value Mandatory

22. Restrict in this way the InfoObject Assortment in the frame Rows with the following variable:


0S_ASRT Assortment Selection Option Optional

23. Restrict in this way the InfoObject Base Unit in the frame Rows with the following variable:


0I_AMNT Unit of Measure ( Selection )

Selection Option Optional

24. Restrict in this way the InfoObject Posting Period in the frame Rows with the following variable you have to create:


RT_PER Posting Period Selection Option Optional

Execute the following steps to create the variable RT_PER for Posting Period.

25. Right click Posting period and choose Restrict.

26. Go to the tab page of Variables.

27. Right click No Entries Found.

28. Choose New Variable.

29. Should the screen SAP BW Variables Wizard appear, flag the message Do not display

this step in the future.

30. Enter the following data :

Field names Name Value

Variable Name RT_PER

Description Posting Period

Processing by User Entry/Default Value

Characteristic Posting period(default)


© SAP AG of 116

31. Choose Next.

32. Change the default values as shown in the screen shot.


Variable Represents Selection Option

Variable entry is Optional

Ready for Input Flag

33. Choose Next.

34. Choose Next.

35. Choose Exit.

36. Mark the just created variable.

37. Choose Add.

38. Choose OK.

39. Restrict the below listed InfoObjects in the frame Rows with variables that you have to create in the exact same manner as you did it in the previous steps. The properties of the variables you find here.

Variable Name Description Variable Represents Variable entry is

RT_ATYP Assortment Type Single Value Mandatory

RT_KEYF Key Figure ID Selection Option Optional

RT_LC Local Currency Selection Option Optional

40. The filter and Column frame of the query should be now as shown in the screen shot.


© SAP AG of 116

41. The different characteristics in the frame Rows should be restricted as shown in the screen shot below. Check if the order in the frame Rows is the same.

42. Choose Save Query as.


Field name Value

Description Key Figures Assortment Planning

Technical Name RT_RTC35_Q0001

44. Choose Save.

4.3.9 Defining Message Types and Selections Options for Releasing Assortments

Use If you want to transfer assortment planning data from the SAP BI System to the SAP ECC System you must fit some settings for message type ASRTPLAN. You must assign the RFC destination and then the rollout must be mapped to the posting period.

Prerequisites The step is only possible if the planning layouts are available in your BI System.

4.3.9.1 Defining Message Types

Use Before you can release the message type ASRTPLN you must check if a RFC destination is assigned. Also check message type LOCGRP.


© SAP AG of 116


SAP BI menu SAP Business Information Warehouse Business Planning and

Simulation Planning Content Retail Analytics Release

Workbench Settings Define message types

Transaction code UPARI_MSGTYPE

2. Enter the following data for message type ASRTPLN:


COM Meth O RFC

RFC Destination to <Logical system>, for example RTFCLNT100

3. Enter the same data for message type LOCGRP and OTB.

4. Choose Save.

4.3.9.2 Defining Selection Options

Use Because the rollout should be mapped to the fiscal period you must replace the entry in the Selection Options.


SAP BI menu SAP Business Information Warehouse Business Planning and

Simulation Planning Content Retail Analytics Release

Workbench Settings Define Selection Options

Transaction code UPARI_SELOP

2. Scroll down to the entry for Selection Field name is equal to S49_SERO.

3. Replace the value 0RT_SKUROLL in the column InfoObject/Field name Data by 0FISCPER3 for the entry S49_SERO. Message type is ASRTPLN.

Field name Value User action and values

Info Object/Field name 0RT_SKUROLL 0FISCPER3

4. Choose Save.

4.3.10 BADI UPARI_ASRTPLN

Use Make sure that the BADI UPARI_ASRTPLN is implemented (as mentioned in 4.3.8).

Plan values of assortment key figures can be accessed in the ECC system. Therefore a BADI has been realized. The BADI itself uses a query to get data from the InfoProvider RT_C35. Assortment Planning Plan, Month.

Procedure


© SAP AG of 116


SAP BI menu SAP ECC menu Tools ABAP Workbencht Utilities

Business Add-Ins Implementations


2. In the Edit Implementation section, choose Classic BADI, and enter UPARI_ASRTPLN in the Field name of Implementation.

3. Choose Change.

4. Choose Interface tab.

5. Double-click the methods to make sure that the following coding exits in the methods.

4.3.10.1 GET_DATA_ASRTPLN method if_ex_upari_asrtpln~get_data_asrtpln. * Query: RT_C35/RT_RTC35_Q0001 include upari_rel_c01. * Infoobject 0Version (var_name = 0P_ASSP, must-Field name in query) has to * be filled data: l_langu type sy-langu, lv_report_id type rscrmstatus-reportuid value 'RT_C35/RT_RTC35_Q0001', ls_appl_message type upari_ys_appl_msg, ls_bw_varsel type upari_ys_rscrmvarp, lt_bw_query type upari_yt_wrex_query, lt_bw_varsel type upari_yt_rscrmvarp, lt_return type table of bapiret2, lv_ofiscper3(3) type n. Field name-symbols: <lfs_return> type bapiret2, <lfs_selopt> type upari_ys_selopt. * initialization clear et_asrtpln[]. clear et_appl_message[]. clear lt_bw_varsel[]. * convert it_selopt into BW variable selection format loop at it_selopt assigning <lfs_selopt>. clear ls_bw_varsel. * # structure /BIC/VRT_C312 * Characteristics * # 0CM_HIEID Hierarchy ID * # 0CM_CDT3 Segment * # 0RT_ASORT Assortment * # 0RT_SEASON Season Category


© SAP AG of 116

* # 0RT_SEASYR Season Year * ? 0FISCPER3 Posting period * ? RT_EQUIPB Basic Equipment OAPC * # 0BASE_UOM Base Unit of Measure * # 0LOC_CURRCY Local currency * Key Figures * # RT_NUMAT Number of Article * # RT_NUMST Number of Stores * ? RT_SQUBST Sales Quantity by Store * ? RT_GRNNPV Goods Receipt Cost Value, Net Net * ? 0CPGRPDVPV Goods Receipt Posting Date / Vendor Cost Value * ? 0RTGRPDVST GR Posting Date / Vendor RtlT * ? 0RTGRPDVSV Goods Receipt Posting Date/Vendor Retail Value * Selection criteria in release workbench UPARI_REL

* Hierarchy Id 0CM_HIEID 0CMHIEID

* Article Hierarchy Node 0CM_CDTND 0P_SEGM

* Assortment type 0RF_ASTYP RT_ATYP

* Season Year 0RT_SEASYR 0P_SEAY1

* Season Category 0RT_SEASON 0P_SEASO

* Posting Period OFISCPER3 RT_PER

* Assortment 0RT_ASORT 0S_ASRT

* Key Figure ID 0RT_KEYFIG RT_KEYF case <lfs_selopt>-chanm. * '0CM_HIEID' when c_io_hieid. ls_bw_varsel-var_nam = '0CMHIEID'. when '0CM_CDTND'. ls_bw_varsel-var_nam = '0P_SEGM'. when '0RF_ASTYP'. ls_bw_varsel-var_nam = 'RT_ATYP'. * '0RT_SEASYR' when c_io_seasyr. ls_bw_varsel-var_nam = '0P_SEAY1'. * '0RT_SEASON' when c_io_season. ls_bw_varsel-var_nam = '0P_SEASO'. when '0FISCPER3'. ls_bw_varsel-var_nam = 'RT_PER'. * '0RT_ASORT' when c_io_assortment. ls_bw_varsel-var_nam = '0S_ASRT'. when '0RT_KEYFIG'. ls_bw_varsel-var_nam = 'RT_KEYF'.


© SAP AG of 116

endcase. if <lfs_selopt>-chanm = '0FISCPER3'. * since types do not match do a temporary move into a variable with the right type move <lfs_selopt>-low to lv_ofiscper3. move lv_ofiscper3 to ls_bw_varsel-varlow. move <lfs_selopt>-high to lv_ofiscper3. move lv_ofiscper3 to ls_bw_varsel-varhigh. else. ls_bw_varsel-varlow = <lfs_selopt>-low. ls_bw_varsel-varhigh = <lfs_selopt>-high. endif. ls_bw_varsel-varsign = <lfs_selopt>-sign. ls_bw_varsel-varoption = <lfs_selopt>-option. append ls_bw_varsel to lt_bw_varsel. endloop. ls_bw_varsel-var_nam = '0P_ASSP'. ls_bw_varsel-varsign = 'I'. ls_bw_varsel-varoption = 'EQ'. ls_bw_varsel-varlow = 'ASP'. ls_bw_varsel-varhigh = ''. append ls_bw_varsel to lt_bw_varsel. * get assortment data using query to access infocube RT_C35 call function 'WREX_GET_DATA' destination i_rfc_dest exporting i_reportid = lv_report_id i_no_check = 'X' importing e_bw_langu = l_langu tables e_bw_data = et_asrtpln e_return = lt_return i_bw_varsel = lt_bw_varsel i_bw_query = lt_bw_query exceptions not_found = 1 internal_error = 2 not_consistent = 3 no_data = 4. if sy-subrc ne 0. endif. * copy return messages to application log format loop at lt_return assigning <lfs_return>. clear ls_appl_message. ls_appl_message-msgty = <lfs_return>-type. ls_appl_message-msgid = <lfs_return>-id. ls_appl_message-msgno = <lfs_return>-number. ls_appl_message-msgv1 = <lfs_return>-message_v1.


© SAP AG of 116

ls_appl_message-msgv2 = <lfs_return>-message_v2. ls_appl_message-msgv3 = <lfs_return>-message_v3. ls_appl_message-msgv4 = <lfs_return>-message_v4. ls_appl_message-altext = <lfs_return>-message. ls_appl_message-param = <lfs_return>-parameter. append ls_appl_message to et_appl_message. endloop. endmethod.

4.3.10.2 MAPPING_DATA_ASRTPLN method if_ex_upari_asrtpln~mapping_data_asrtpln. * sample method to map data for message content data: l_recno type i, ls_asrtpln_content type upari_ys_asrtpln_msg, lv_rollout(2) type n. Field name-symbols: <lfs_asrtpln> type upari_ys_wrex_data. clear ls_asrtpln_content. * since there is no clue whether counting of records starts with 0 or 1 take the first entry read table it_asrtpln index 1 assigning <lfs_asrtpln>. if sy-subrc = 0. l_recno = <lfs_asrtpln>-recno. endif. loop at it_asrtpln assigning <lfs_asrtpln>. if <lfs_asrtpln>-recno <> l_recno. append ls_asrtpln_content to et_message_content. clear ls_asrtpln_content. l_recno = <lfs_asrtpln>-recno. endif. * What comes in? (see for reference structure /BIC/VRT_C312) * Characteristics * # 0RT_KEYFIG Kennzahl ID * # 0FISCPER3 Posting period * ? 0CM_CDT1 Category * ? 0CM_CDT2 Subcategory * # 0CM_CDT3 Segment * # 0RT_ASORT Assortment * Key Figures * # RT_GRNNPV Goods Receipt Cost Value, Net Net * # 0CPGRPDVPV Goods Receipt Posting Date / Vendor Cost Value * # 0RTGRPDVST Goods Receipt Posting Date / Vendor Retail Tax(?) * # 0RTGRPDVSV Goods Receipt Posting Date / Vendor Retail Value


© SAP AG of 116

* ? RT_QUAN * # RT_NUMAT Number of Article * # RT_NUMST Number of Stores case <lfs_asrtpln>-iobjnm. * key figure id when '0RT_KEYFIG'. ls_asrtpln_content-key_figure_id = <lfs_asrtpln>-value. * hierarchy id - Hiearchie ID when '0CM_HIEID'. ls_asrtpln_content-category_hierarchy_node-category_hierarchy_id = <lfs_asrtpln>-value. * hierarchy node - Hierachie Knoten, Ebene Segment wird zugewiesen when '0CM_CDT3'. ls_asrtpln_content-category_hierarchy_node-category_hierarchy_node_id = <lfs_asrtpln>-value. * season when '0RT_SEASON'. ls_asrtpln_content-season-season_category_code = <lfs_asrtpln>-value. * season year when '0RT_SEASYR'. ls_asrtpln_content-season-season_year = <lfs_asrtpln>-value. * assortment type when '0RF_ASTYP'. ls_asrtpln_content-assortment_type = <lfs_asrtpln>-value. * assortment - Sortiment when '0RT_ASORT'. ls_asrtpln_content-assortment_id = <lfs_asrtpln>-value. * Posting period when '0FISCPER3'. move <lfs_asrtpln>-value to lv_rollout. ls_asrtpln_content-season-season_rollout_code = lv_rollout. * quantity when 'RT_SQUBST'. ls_asrtpln_content-target_quantity-value = <lfs_asrtpln>-value. * base unit when '0BASE_UOM'. ls_asrtpln_content-target_quantity-unit_code = <lfs_asrtpln>-value. * number of stores when 'RT_NUMST'. ls_asrtpln_content-number_stores_number = <lfs_asrtpln>-value. * number of different articles


© SAP AG of 116

when 'RT_NUMAT'. ls_asrtpln_content-number_different_articles_nbr = <lfs_asrtpln>-value. * Vendor Retail Tax when '0RTGRPDVST'. ls_asrtpln_content-target_sales_retail_tax-value = <lfs_asrtpln>-value. * Cost Value, Net Net when 'RT_GRNNPV'. ls_asrtpln_content-target_sales_cost_net-value = <lfs_asrtpln>-value. * Vendor Cost Value when '0CPGRPDVPV'. ls_asrtpln_content-target_sales_cost_basic-value = <lfs_asrtpln>-value. * Vendor Retail Value when '0RTGRPDVSV'. ls_asrtpln_content-target_sales_retail-value = <lfs_asrtpln>-value. ** target quantities / planned totals in units * WHEN '0CPBAINSABU'. * ls_asrtpln_content-target_quantity-value = <lfs_asrtpln>-value. * local currency - Währungsschlüssel when '0LOC_CURRCY'. ls_asrtpln_content-target_sales_cost_basic-currency_code = <lfs_asrtpln>-value. ls_asrtpln_content-target_sales_cost_net-currency_code = <lfs_asrtpln>-value. ls_asrtpln_content-target_sales_retail-currency_code = <lfs_asrtpln>-value. ls_asrtpln_content-target_sales_retail_tax-currency_code = <lfs_asrtpln>-value. * base unit of measure - Einheit when '0BASE_UOM'. ls_asrtpln_content-target_quantity-unit_code = <lfs_asrtpln>-value. endcase. endloop. if not ls_asrtpln_content is initial. append ls_asrtpln_content to et_message_content. endif. endmethod.


© SAP AG of 116

4.3.10.3 MODIFY_MSG_ASRTPLN No coding.

4.3.10.4 SEND_RFC_ASRTPLN method if_ex_upari_asrtpln~send_rfc_asrtpln. call function 'UPARI_SEND_RFC_ASRTPLN' exporting it_content_rfc = it_content_rfc i_rfcdest_to = i_rfcdest_to i_extension = i_extension importing et_appl_message = et_appl_message. endmethod.

Check if BADI is active; otherwise activate it by choosing Activate.

4.3.11 Releasing Assortment Plan

Use After having completed the Assortment Planning the plan data will be transferred from the BI System to the ECC system. The transfer will be triggered by releasing the assortment plan in the Release Workbench.

The transferred key figures are Target GR at Cost Plan, Target GR at Cost net net Plan, Target GR at Retail Plan, Target GR at Retail with Tax Plan, Target Quantity Plan, Number of Stores Plan and Number of different Styles Plan. These data are then available in the operational assortment planning and control functionality (OAPC).

Procedure

1. Access the transaction choosing one of the following navigation options

SAP ECC menu SAP ECC menu Business Planning and Simulation Planning

Content Retail Analytics Release Workbench Start Release Workbench

Transaction code UPARI_REL

2. Set the flag Assortment Plan in the sub-screen Message Types. A new Assortment Plan tab with status red appears.

3. Set the flag in the field of Release Related Messages in the sub-screen Message Types.

4. On the General Data tab page make the following settings:


Hierarchy ID B1

Article Hierarchy Node B11120

Assortment Type FASH

5. Choose Enter. The status of the tab page General Data changes to green.


© SAP AG of 116

6. Go to the Assortment Plan tab. The data from the sub-screen of General Selection Criteria are taken over.

7. Enter the following data in the sub-screen of Assortment Plan Specific Selection Criteria:

Field name Value from Value to Comment

Season Year 2009

Season Category 0002

Posting Period 08 This is the period you planned with in the Assortment Planning scenario.

Assortment B11100_11 B11100_22 B11100_22

Key figure ID IF IV IV

8. Choose Enter. The status of the tab Assortment Plan switches to green.

9. Choose the Release Messages Immediately. After some time you get the information

Release run started. You can find the results in the application log.


11. Choose Application Log.

12. Choose Execute.

If your transfers were successful you will get a log with status green, double-click your log you will see the number of successfully created objects and errors/warnings.

13. Choose Exit..

Result You have transferred the key figures Target GR at Cost Plan, Target GR At Cost net net Plan, Target GR at Retail Plan, Target GR at Retail with Tax Plan, Target Quantity Plan, Number of Stores Plan and Number of different Styles Plan from SAP BI to SAP ECC.

4.3.12 Creating Purchasing List – SAP ECC

Use The Purchasing List shows the target key figures that you released in the Release Workbench. In order to see the released data you have to create a purchasing list.

You have to logon to the ECC system.

Procedure

1. Log on to the ECC system.

2. Access the transaction choosing one of the following navigation options:

SAP ECC menu Logistics Retailing Master Data Assortment/Listing

Operational Assortment Planning and Control Create Purchasing List

Transaction code WRFAPC01


© SAP AG of 116

3. Enter the following data on the sub-screen of Assortment.


Hierarchy B1

Hierarchy Node B11120

Assortment Type FASH

4. Enter the following data on the sub-screen of Season.


Season year 2009

Season Category 0002

Rollout 08

5. Choose Enter.

6. Choose Yes in the upcoming screen.

7. Check the following data in the next screen:


Purchasing Org. 1000

Purch. Group 100

Sales Org. 1000

Distr. Channel 10

8. Choose Enter.

9. Choose the Target Values tab.

10. Choose Collapse in the middle of the screen to close the Overview Area.

11. You see in the first sub-screen Target Value Description the following key figures for each assortment:

Target Totals in Basic Purchase Price

Target Totals in net/net Purch. Price

Target Totals in Retail Value with Tax

12. You see in the second sub-screen Target Value Description the following key figures for each assortment:

Number of stores in assortment

Number of different articles

Target Totals in Units

13. All these data can be found in the planning layouts Distribute to IF and IV and Plan Number of different Styles in the BI system.

14. Refer to the chapters Distribute to IF and IV and Plan number of different Styles with the Assortment Planning.

Result You created a purchasing list and the transferred key figures are shown.


© SAP AG of 116

4.3.13 OTB Check: Maintaining Document-Type Dependent Settings – SAP ECC

Use In this step you decide which document type is relevant for the OTB-Check.

You have to logon to the ECC system.

Procedure 1. Log on to the SAP ECC system.



Open-To-Buy(OTB) OTB Check: Maintain Document-Type Dependent Settings


3. Choose New Entries to define the OTB Check Settings.

4. Choose the document Category from the list: Purchase Order.

5. On the New Entries: Detail of Added Entries make the following entries: First Line:


Document Type NB Choose from list

OTB Check Level

Schedule Line Choose from list

Online selection "set flag"

Negative OTB Check (Online)

Display Dialog Box Choose from list

Negative OTB Check (Batch)

Entry in Worklist with Partial Reservation

Choose from list

Error Handling PO Without Contract Reference

Behavior analogous to the Neg. OTB-Check of Purchase Orders

Choose from list

6. Choose Save.

7. Choose Back.

8. Choose New Entries to define the second line.

9. Choose the document Category from the list: Contract and make the following entries:


Document Type MK Choose from list

10. Choose Save.

11. Choose Back.

12. Choose New Entries to define the third line.

13. Choose the document Category from the list: Contract and make the following entries:


© SAP AG of 116


Document Type WK Choose from list

14. Choose Save.

15. Choose Back.

No other Open-To-Buy Settings for Contracts, because there would be a conflict with other scenarios!

4.4 Slow Seller Management

Use The Slow Seller Analysis is based on the result of the query 0RMP_MC21_ Q0020 Slow Seller Management Analysis.

The query gets the data from the MultiProvider 0RMP_MC21 Assortment Planning Controlling which consists of the InfoProvider 0RMP_C22 Assortment Plan, POS Sales, Week, 0RMP_C24 Assortment Plan, Stock, Week and 0RMP_C25 Assortment Plan, Plan. Only the InfoProviders 0RMP_C22 and 0RMP_C24 must be provided with data. There is no need of plan data.

The InfoProviders 0RMP_C22 Assortment Plan, POS Sales, Week and 0RMP_C24 Assortment Plan, Stock get the data from the DataStore Objects 0RMP_DS01 Stock Consolidation and 0RMP_DS02 POS Consolidation.

The DataStore Object 0RMP_DS01 Stock Consolidation and 0RMP_DS02 POS Consolidation gets the data from flatfiles. The DataStore Object 0RMP_DS01 is updated by the update rule 0RMP_DS01_2LIS_03_BF. The DataStore Object 0RMP_DS02 is updated by the update rule 0RT_PA_TRAN_CONTROL.

The Slow Seller Analysis is also based on markdown profiles. The definition of a markdown profile includes periods, one period is one week. In our scenario the two profiles are defined for 10 weeks and one for 20 weeks.

To always have a Slow Seller Analysis that provides markdown proposals the data loading via flatfiles must be executed periodically. Normally the Transactional data would be coming from your ECC System. For a refresh of the Slow Seller Analysis data you have to load three flatfiles.

1. A flatfile which provides the records in 0MAT_PLANT with a goods receipt date. The goods receipt date to a date that lies three weeks in the past.

2. A flatfile that provides the DataStore Object 0RMP_DS02 with POS Data. The posting date is

set as to a date that lies three weeks in the past.

3. A flatfile that provides the DataStore Object 0RMP_DS01 with Stock Data. The posting date is set to a date that lies three weeks in the past.

Because the goods receipt date is set to a date three weeks in the past and two profiles are only defined for 10 weeks you must refresh the data at least every seven weeks.

The steps under Procedure describe the installation of the interface and the flatfile loading.






© SAP AG of 116


4.4.1 Generating Export DataSources

Procedure 1. Choose Search and enter the following data:


Find 0RMP_DS01

2. Choose Search.

3. Right click Stock Consolidation.

4. Follow the context menu path choose Additional Functions Generate Export DataSource.

5. Search for 0RMP_DS02, as described before.

6. Right click POS Consolidation.

7. Follow the context menu path choose Additional Functions Generate Export DataSource.

4.4.2 Install Interface “Goods Receipt Date”

4.4.2.1 Creating InfoSources and Transfer Rules

Use In this chapter the creation of an InfoSource and the Transfer Rules for the InfoObject 0MAT_PLANT is described.

Procedure 1. On the Data Warehousing Workbench: Modeling screen, choose InfoSources.

2. Follow the application path choose SAP Application Components SAP Sectors Trade

Industries Retailing Merchandise and Assortment Planning MAP Transactional Data.

3. Right click the Application Component MAP Transactional Data.




InfoSource RT_FIRST_GR

Long description Change of the first GR Date to actual minus 3 weeks

6. Choose Continue.

7. Right click the InfoSource RT_FIRST_GR.

8. Choose Change.

9. Enter the following InfoObject in the Communication Structure frame:


0MATERIAL Article

0PLANT Store

0RT_SSMFGR Date of First GR

10. Choose Enter.


© SAP AG of 116



13. Choose Back.

14. Choose Collapse to close the Communication_Struct.

15. Choose Expand to open the Trnasfer_structure/Transfer_Rules.



Source System FILE by Chooseing


18. Double-click in the row for InfoObject 0RT_SSMFGR.

19. Set flag in the field of Routine.

20. Choose Create..



Transfer Routine Goods Receipt Date

22. Set flag in the field of No Field name.


24. Browse down until you see the coding line RESULT = .

25. Replace this line by RESULT = sy-datum - 21.

26. Choose Check.

27. Choose Save if there are no syntax errors.



30. Choose Back.

4.4.2.2 Assigning Update Rules to InfoObject

Use In this chapter the creation of a new update rule for InfoObject 0MAT_PLANT is described.








Find 0MAT_PLANT

4. Choose Search.


© SAP AG of 116

5. Expand Store Article.

6. Right click Store Article (Attribute).

7. Follow the context menu path choose Additional Functions Create Update Rules.

8. Set flag in the field of InfoSource.

9. On the Update rules create: Start and enter RT_FIRST_GR.

10. Choose Continue in the up coming screen.

11. Double-click a key figure, for example ABC indicator.

12. Choose the tap page of Key Field names.

13. Choose Blank in the row for Store Article.

14. Set flag in the field of Source Chars.

15. Choose 0MATERIAL by using the F4 Help.

16. Choose Transfer

17. Choose Yes in the upcoming screen..



20. Choose Back.

4.4.2.3 Assigning InfoPackage to InfoSource

Use In this chapter the creation of the InfoPackage is described. In the following table you find the flatfiles you have to load. Use the first flatfile to enter when creating the InfoPackage.

InfoObject Description First Flatfiles to Load

0MAT_PLANT Article Store Flatfile_MATPLANT_GR_DAT_Fashion.csv Flatfile_MATPLANT_GR_DAT_Hardgoods.csv



In this chapter you load the flatfiles for Merchandise Planning. They are stored in the csv folder within the folder SSM.






3. Choose Search.



© SAP AG of 116


Find RT_FIRST_GR

5. Open the folder of Change of the first GR Date to actual minus 3 weeks.

6. Open the folder of from RT_FIRST_GR for FILE.

7. Right click RT_FIRST_GR.

8. Follow the menu path choose Create InfoPackage.



InfoPackage Description Flatfile Load: RT_FIRST_GR

10. Select the line for RT_FIRST_GR in the section DataSource.

11. Choose Save.


13. Choose the External data tab and make the following entries:



File type



See the comments in the prerequisites paragraph of this chapter. Choose the first flatfile Flatfile_MATPLANT_GR_DAT_Fashion.csv





Currency Conversion for External Systs

unflag

Number of Header Rows to be Ignored

1

14. Choose the Processing tab and make the following entry:

Field name Value


15. Choose the Data targets tab and set flag in the field of Select Data Targets.

16. Select the InfoProvider 0MAT_PLANT under the Field name Updating the data target.


© SAP AG of 116

17. Choose the Update tab and make the following entries:

Field name Values



18. Choose Save.

4.4.3 Loading Goods Receipt Dates into 0MAT_PLANT

Use The flatfiles you load here in the BI System update the first goods receipt attribute in the InfoObject 0MAT_PLANT. You have to load the following flatfiles to update all the necessary articles used in the Slow Seller Analysis.

InfoObject Description First Flatfiles to Load

0MAT_PLANT Article Store Flatfile_MATPLANT_GR_DAT_Fashion.csv Flatfile_MATPLANT_GR_DAT_Hardgoods.csv









3. Choose Search.



Find RT_FIRST_GR

5. Open the folder of Change of the first GR Date to actual minus 3 weeks.

6. Open the folder of from RT_FIRST_GR for FILE.

7. Right click RT_FIRST_GR.

8. Double-click Flatfile load: RT_FIRST_GR.


10. Go to the External Data tab.


© SAP AG of 116

11. Choose the first flatfile Flatfile_MATPLANT_GR_DAT_Fashion.csv. It should be already chosen from the previous chapter.

12. Go to the Schedule tab.


14. Choose Monitor in the board


16. Choose Back.

17. In this way load the other flatfile for the InfoObject 0MAT_PLANT.

18. Choose Back.

4.4.4 Install Interface “ POS and Stock Data SSM“

Use In this chapter the necessary installation steps for loading POS Data and Stock Data are described.


For the creation of a DataSources you need to enter a csv-file. The flatfiles are stored on the Documentation SAP Best Practices CD in the folder \InfoDev\CD_Production\Release_603\Misc\Retail\USy\Flatfiles. They must be installed on your hard disk or any of your file server. An installation in this way is important because you have defined in the InfoPackage that an external load takes place from a client workstation.


4.4.4.1 Creating Application Component

Use The purpose of this activity is to create an application component as a method to structure applications within the DataSource area.





2. Move to the DataSources area in the modeling navigation in the left hand frame.

3. Choose Choose Source System.

4. Follow the path choose File File (FILE).

5. From the application menu choose SAP Application Components SAP Sectors Trade

Industries Retailing.

6. Right click the application component Retailing.

7. Choose Create application component.

8. Enter the following data in the dialog box Create Application Components:


© SAP AG of 116


Application Comp. ZRT_SSM

Long Description Transactional Data SSM

9. Choose Continue to create the application component.

4.4.4.2 Creating POS DataSource

Use Loading data via flatfiles into the ODS Objects 0RMP_DS02 presupposes that the interface is defined. The creation of the necessary DataSource is described In this chapter.

The table below lists the flatfiles that must be loaded in the ODS Objects 0RMP_DS02. When creating the DataSource use the first flatfile listed in the table below.

ODS Object Description Flatfiles to Load

0RMP_DS02 POS Consolidation Flatfile_0RMP_DS02_POS_Fashion.csv Flatfile_0RMP_DS02_POS_Hardgoods.csv






3. From the application menu, choose SAP Application Component SAP Sectors Trade


4. Right click the application component Transactional Data SSM.

5. Choose Create DataSource.

6. Enter the following data in the dialog box Create DataSource:

Field name User action and values Notes

DataSource RT_DS_0RMP_DS02

Source System FILE automatically filled

Data Type DataSource Transaction Data

7. Choose Transfer.


9. Enter the following data on the tap page General Info:


Short description POS Data SSM

Medium description POS Data SSM

Long description POS Data SSM

10. Enter the following data on the tap page Extraction :


© SAP AG of 116


Delta Process Full upload (Delta from InfoPackage Selection Only)

Direct Access NO DTP Allowed for Direct Access

Real Time Real-Tile Data Acquisition is not supported

Adapter Load Text-Type File from Local Workstation

Name of File Flatfile_0RMP_DS02_POS_Fashion.csv

Header Rows to be ignored 2

Character Set Settings Default Settings

Data Format Separated with Separator (for example, CSV)

Data Seperator ,

Escape Sign “

Convers. Language User Master Record

Number Format User Master Record

11. Enter the following data on the tap page Proposal:


No. of Data Record 3

12. Choose Load Example Data.

13. Go to to the Field names tab.

14. Flag the message Do not Show This Question Again in This Session and

choose Yes in the upcoming screen.

15. Enter in the column InfoTemplate the values you find in the following table:

Pos Field names InfoTemplate

1 RT_LOCATIO 0RT_LOCATIO

2 BUSINESSDAYDATE 0RPA_BDD

3 RPA_TTC 0RPA_TTC

4 RPA_WID 0RPA_WID

5 RPA_TNR 0RPA_TNR

6 RPA_DEP 0RPA_DEP

7 RPA_OID 0RPA_OID

8 DOC_CURRCY 0DOC_CURRCY

9 RPA_PQU 0RPA_PQU

10 RPA_PAI 0RPA_PAI

11 MATERIAL 0MATERIAL

12 MATL_GROUP 0MATL_GROUP

13 BASE_QTY 0BASE_QTY

14 BASE_UOM 0BASE_UOM

16. Choose Enter.


© SAP AG of 116

17. Replace RPA_BDD by BUSINESSDAYDATE.

18. Choose Enter.

19. Choose Next Page and scoll down to get a view in which the column Info Template is empty



15 TRANSACTIONINDEX 0RPA_TIX

16 TRANSTYPEGROUP 0RPA_TRG

17 BUSINESSTRANSACT 0RPA_BTY

18 REVERSALINDICATO 0RPA_RFL

19 TRAININGTRANSACT 0RPA_TRF

20 SALESITEMNUMBER 0RPA_RSN

21 SALESITEMTYPE 0RPA_RTC

22 POSTRANSW/OPOST 0RPA_KOF

23 REASON 0RPA_RRC

24 QUALIFITEMIDENT 0RPA_IQU

25 EAN/UPC 0EANUPC

26 SALESQTYINSUN 0RPA_RLQ

27 SALESUNIT 0SALES_UNIT

28 SALESRETAILVALUE 0RPA_SAT

21. Choose Enter.

22. Choose Next Page and scoll down to get a view in which the column Info Template is empty.



29 RPA_NSA 0RPA_NSA

30 RPA_CST 0RPA_CST

31 RPA_BAI 0RPA_BAI

32 RPA_SNU 0RPA_SNU

33 RT_PROMO 0RT_PROMO

34 RPA_EMC 0RPA_EMC

35 RPA_DSN 0RPA_DSN

36 RPA_DTC 0RPA_DTC

37 RPA_DRC 0RPA_DRC

38 RPA_REA 0RPA_REA

39 RPA_DAC 0RPA_DAC

40 RPA_DID 0RPA_DID

41 RPA_DTG 0RPA_DTG

42 RPA_DRG 0RPA_DRG


© SAP AG of 116

24. Choose Enter.


26. Enter in the column InfoTemplate the values you find in the following table


43 RPA_TSN 0RPA_TSN

44 RPA_TAC 0RPA_TAC

45 RPA_TAM 0RPA_TAM

46 RPA_TIF 0RPA_TIF

47 RPA_TTG 0RPA_TTG

48 RPA_CSN 0RPA_CSN

49 RPA_EID 0RPA_EID

50 RPA_CAM 0RPA_CAM

51 RPA_TES 0RPA_TES

52 RPA_TCD 0RPA_TCD

53 RPA_TAT 0RPA_TAT

54 RPA_TCU 0RPA_TCU

55 RPA_TID 0RPA_TID

56 RPA_ANU 0RPA_ANU

27. Choose Enter.




57 RPA_RID 0RPA_RID

58 RPA_TYG 0RPA_TYG

59 RPA_PCA 0RPA_PCA

60 RPA_ANO 0RPA_ANO

61 RPA_CNS 0RPA_CNS

62 DATETO 0DATETO

63 RPA_CHN 0RPA_CHN

64 RPA_ACO 0RPA_ACO

65 RPA_ATI 0RPA_ATI

66 RPA_AMC 0RPA_AMC

67 RPA_ADT1 0RPA_ADT1

68 RPA_ADT2 0RPA_ADT2

69 RPA_MID 0RPA_MID

70 RPA_ACD 0RPA_ACD

30. Choose Enter.


© SAP AG of 116




71 RPA_LAM 0RPA_LAM

72 RPA_CSK 0RPA_CSK

73 RPA_HAT 0RPA_HAT

74 RPA_AUC 0RPA_AUC

75 RPA_PID 0RPA_PID

76 RPA_FOL 0RPA_FOL

77 RPA_ACH 0RPA_ACH

78 RPA_BCD 0RPA_BCD

79 RPA_BAC 0RPA_BAC

80 RPA_BTS1 0RPA_BTS1

81 RPA_BTS2 0RPA_BTS2

82 RPA_ETS1 0RPA_ETS1

83 RPA_ETS2 0RPA_ETS2

84 RPA_RTG 0RPA_RTG

33. Choose Enter.




85 RPA_RQU 0RPA_RQU

86 RPA_OQU 0RPA_OQU

87 RPA_RDF 0RPA_RDF

88 RPA_DDI 0RPA_DDI

89 RPA_DTA 0RPA_DTA

90 RPA_DTE 0RPA_DTE

91 RPA_DDF 0RPA_DDF

92 RPA_TAF 0RPA_TAF

93 RPA_TDF 0RPA_TDF

94 RPA_EVENT 0RPA_EVENT

95 RPA_EVQUAL 0RPA_EVQUAL

96 LOC_CURRCY 0LOC_CURRCY

97 RPA_TRD 0RPA_TRD

98 RPA_RSI 0RPA_RSI

36. Choose Enter..



© SAP AG of 116



99 RPA_TSA 0RPA_TSA

100 OI_ITEMS 0OI_ITEMS

101 OI_TRANS 0OI_TRANS

102 OI_PBLNR 0OI_PBLNR

103 RPA_OI0 0RPA_OI0

104 RPA_OI1 0RPA_OI1

105 RPA_PA0 0RPA_PA0



108 RPA_ITI 0RPA_ITI

109 RPA_IT0 0RPA_IT0




39. Choose Enter.

40. Choose Next Page.




114 RPA_EI0 0RPA_EI0

115 RPA_EI1 0RPA_EI1

116 RPA_EQU 0RPA_EQU

117 RECORDMODE 0RECORDMODE

118 RPA_RRG 0RPA_RRG

119 RPA_TRC 0RPA_TRC

42. Choose Enter.


44. Ignore the yellow warnings and choose Continue.

45. Choose Back.

4.4.4.3 Creating Stock DataSource

Use Loading data via flatfiles into the ODS Objects 0RMP_DS01 presupposes that the interface is defined. The creation of the necessary DataSource is described in this chapter.

The table below lists the flatfiles that must be loaded in the ODS Objects 0RMP_DS01. When creating the DataSource use the first flatfile listed in the table below.


© SAP AG of 116

ODS Object Description Flatfiles to Load

0RMP_DS01 Stock Consolidation Flatfile_0RMP_DS01_GR_Fashion.csv Flatfile_0RMP_DS01_GR_Hardgoods.csv





2. Move to DataSources area in the modeling navigation in the left hand frame.

3. Choose from the application path SAP Application Component SAP Sectors Trade


4. Right click the application component Transactional Data SSM.

5. Choose Create DataSource.

6. Enter the following data in the dialog box Create DataSource:

Field name User action and values Notes


Source System FILE automatically filled

Data Type DataSource Transaction Data

7. Choose Transfer.


9. Enter the following data on the tap page General Info:


Short description Stock Data SSM

Medium description Stock Data SSM

Long description Stock Data SSM

10. Enter the following data on the tap page Extraction :


Delta Process

Direct Access

Real Time

Adapter

Name of File Flatfile_0RMP_DS01_GR_Fashion.csv

Header Rows to be ignored 2

Character Set Settings Default Settings

Data Format

Data Seperator ,

Escape Sign “


© SAP AG of 116


Convers. Language User Master Record

Number Format User Master Record

11. Enter the following data on the tap page Proposal:


No. of Data Record 3

12. Choose Load Example Data.

13. Change to the tab page Field names:

14. Enter in the column Field names and InfoTemplate the values you find in the following table and overwriting existing values in the column Field name:


1 STORNO 0STORNO

2 RT_PROMO 0RT_PROMO

3 VAL_CLASS 0VAL_CLASS

4 DOC_DATE 0DOC_DATE

5 STOCKTYPE 0STOCKTYPE

6 STOCKCAT 0STOCKCAT

7 PSTNG_DATE 0PSTNG_DATE

8 COMP_CODE 0COMP_CODE

9 BWAPPLNM 0BWAPPLNM

10 MOVETYPE 0MOVETYPE

11 STOCKRELEV 0STOCKRELEV

12 CPPVLC 0CPPVLC

13 CPSVLC 0CPSVLC

14 CPSTLC 0CPSTLC

15. Choose Enter.




15 CPQUABU 0CPQUABU

16 VAL_TYPE 0VAL_TYPE

17 PROCESSKEY 0PROCESSKEY

18 BATCH 0BATCH

19 MATMREA 0MATMREA

20 BUS_AREA 0BUS_AREA

21 COSTCENTER 0COSTCENTER


© SAP AG of 116


22 SOLD_TO 0SOLD_TO

23 WHSE_NUM 0WHSE_NUM

24 STOR_LOC 0STOR_LOC

25 STRGE_BIN 0STRGE_BIN

26 STRGE_TYPE 0STRGE_TYPE

27 VENDOR 0VENDOR

28 MATERIAL 0MATERIAL

18. Choose Enter.

19. Choose Next Page and scoll down until you get a view in which the column Info Template is empty.

20. Choose Insert Row so often until you get a view in which only lines exist that can be filled with data.



29 DOC_NUM 0DOC_NUM

30 BASE_UOM 0BASE_UOM

31 DOC_YEAR 0DOC_YEAR

32 PROFIT_CTR 0PROFIT_CTR

33 DCINDIC 0DCINDIC

34 LOC_CURRCY 0LOC_CURRCY

35 PLANT 0PLANT

36 FISCVARNT 0FISCVARNT

37 CPNOITEMS 0CPNOITEMS

38 CO_AREA 0CO_AREA

39 DOC_ITEM 0DOC_ITEM

40 VALUE_LC 0VALUE_LC

41 COORDER 0COORDER

42 QUANT_B 0QUANT_B

22. Choose Enter.

23. Choose Insert Row 14 times

24. Choose Next Page and scoll down to get a view in which the column Info Template is empty



43 MOVE_PLANT 0MOVE_PLANT

44 RECORDMODE 0RECORDMODE

45 RT_RMAPIDA 0RT_RMAPIDA


© SAP AG of 116


46 BWCOUNTER 0BWCOUNTER

47 INDSPECSTK 0INDSPECSTK

48 GN_R3_SSY 0GN_R3_SSY

26. Choose Enter.


28. Ignore the yellow warnings and choose Continue.

29. Choose Back.

4.4.4.4 Loading Transactional Data into PSA

Use The creation of the InfoPackages with which you load the transactional data into PSA is described.In this chapter.






3. Choose from the application path SAP Application Component SAP Sectors Trade

Industries Retailing Transactional Data SSM.

4. Right click the DataSource POS Data SSM.


6. In the Create InfoPackage dialog box, enter the following data:


InfoPackage Description Flatfile Load: Transactional Data 0RMP_DS02

7. Select the line with the information of POS Data SSM RT_DS_ORMP_DS02 in the section of DataSource.

8. Choose Save.


10. Go to the tab page Extraction.

11. Check if you have chosen the right flatfile.

12. Go to the tab page Schedule.

13. Choose Start.

14. Go back to the tab page Extraction.

15. Select the other flatfile.

16. Go to the tab page Schedule.

17. Choose Start.

18. Choose Back.

19. Right click POS Data SSM.


© SAP AG of 116

20. Choose Manage. You can see the both data requests. If you want to reload the flatfiles you have to delete the both data requests.

21. Choose Cancel.

22. In the same way create the InfoPackage for the ODS Object 0RMP_DS01.

23. In the same way load the flatfiles for the ODS Object 0RMP_DS01.

4.4.4.5 Loading Transactional Data from PSA into ODS Objects

Use To transfer the transactional data from PSA to the ODS Objects 0RMP_DS01 and 0RMP_DS01 transformations must be created. Then via a data transfer process the transactional data will be loaded into the ODS Objects.






4.4.4.6 Creating Transformation for ODS Objects 0RMP_DS02



Find 0RMP_DS02

2. Choose Search.

3. Expand POS Consolidation.

4. Expand TRCS 0RT_PA_TRAN_CONTROL_TR -> ODSO 0RMP_DS02.

5. Right click POS Analytics: Retail Control.

6. Choose Create Transformation.

7. Enter the following data in the sub-screen of Target of the Transformation:


Object Type

Name 0RT_PA_TRAN_CONTROL_TR

8. Enter the following data in the sub-screen of Source of the Transformation:


Object Type DataSource


Source System FILE



© SAP AG of 116

10. Choose Save.


Maintain Start Routine

12. Choose Start Rountine

13. Replace the coding template by

*$*$ begin of routine - insert your code only below this line *-* DATA: wa_SOURCE_PACKAGE LIKE LINE OF SOURCE_PACKAGE. LOOP AT SOURCE_PACKAGE INTO wa_SOURCE_PACKAGE. wa_SOURCE_PACKAGE-BUSINESSDAYDATE = sy-datum - 21. modify SOURCE_PACKAGE from wa_SOURCE_PACKAGE.

ENDLOOP.

14. Choose Check to be sure that there are no syntax errors

15. Choose Save.

Maintain Routine for INFOOBJECT 0FISCPER

16. Double-click the row with the information below:

0FISCPER 151 0FISCPER Fiscal year/period

17. Choose Add Source Field names in the sub-screen of Source Field names of Rule

18. Select the field name of BUSINESSDAYDATE.

10. Choose Copy.

19. Select Routine in the field of Rule Type.


*$*$ begin of routine - insert your code only below this line *-* TRY. CALL METHOD /rtf/cl_time=>get_retail_fpers_from_date EXPORTING

i_date = SOURCE_FIELD NAMES-BUSINESSDAYDATE IMPORTING e_fper1 = RESULT CHANGING ct_monitor = MONITOR. CATCH /rtf/cx_time. RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD. ENDTRY.

21. Choose Check to be sure that there are no syntax errors.

22. Choose Save.

23. Enter as description Routine: Fiscal Year/Period from BUSINESSDAYDATE.

24. Choose Transfer Values in the upcoming screen.

Maintain Routine for INFOOBJECT 0FISCVARNT


0FISCVARNT 152 0FISCVARNT Fiscal year variant

26. Choose Add Source Field names in the sub-screen of Source Field names of Rule.


28. Choose Copy.

29. Select Routine in the field name of Rule Type.


*$*$ begin of routine - insert your code only below this line *-* TRY.


© SAP AG of 116

CALL METHOD /rtf/cl_time=>get_retail_fpers_from_date EXPORTING

i_date = SOURCE_FIELD NAMES-BUSINESSDAYDATE IMPORTING e_fiscyv1 = RESULT CHANGING ct_monitor = MONITOR. CATCH /rtf/cx_time. RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD. ENDTRY.


32. Choose Save.

33. Enter as description Routine: Fiscal Year Variant from BUSINESSDAYDATE.

34. Choose Transfer Values.

Maintain Routine for INFOOBJECT 0FISCPER3


0FISCPER 3 153 0FISCPER3 Posting period



38. Choose Copy.

39. Select Time Characteristic in the Field name of Rule Type.

40. Enter as description Routine: Posting Period from Start Routine.


Maintain Routine for INFOOBJECT 0FISCYEAR


0FISCYEAR 154 0FISCYEAR



45. Choose Copy.

46. Select Time Characteristic in the field name of Rule Type.

47. Enter as description Routine: Fiscal Year from Start Routine.


Maintain Routine for INFOOBJECT 0RT_MTFYVRN


0RT_MTFYVRN 155 0RT_MTFYVRN

50. Choose Add Source Field names in the sub screen Source Field names of Rule.

51. Select the Field name BUSINESSDAYDATE.

52. Choose Copy.

53. Select Routine in the field name of Rule Type.



i_date = SOURCE_FIELD NAMES-BUSINESSDAYDATE IMPORTING e_fiscyv2 = RESULT


© SAP AG of 116

CHANGING ct_monitor = MONITOR. CATCH /rtf/cx_time. RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD. ENDTRY.


56. Choose Save.

57. Enter as description Routine MAP: Approximate Fiscal Year Variant from BDD.


Maintain Routine for INFOOBJECT 0RT_QTFYVRN


0RT_QTFYVRN 156 0RT_QTFYVRN

60. Choose Add Source Field names in the sub screen Source Field names of Rule.


62. Choose Copy.

63. Select Routine in the Field name of Rule Type.



i_date = SOURCE_FIELD NAMES-BUSINESSDAYDATE IMPORTING e_fiscyv3 = RESULT CHANGING ct_monitor = MONITOR. CATCH /rtf/cx_time. RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD. ENDTRY.


66. Choose Save.

67. Enter as description Routine: Approximate Fiscal Year Variant from BDD.

68. Choose Transfer Values..

Maintain Routine for INFOOBJECT 0RT_MTFPER


Approximate Fiscal Year Period from BDD

157 0RT_MTFPER



72. Choose Copy.

73. Select Routine in the Field name of Rule Type..



i_date = SOURCE_FIELD NAMES-BUSINESSDAYDATE IMPORTING e_fper2 = RESULT CHANGING


© SAP AG of 116

ct_monitor = MONITOR. CATCH /rtf/cx_time. RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD. ENDTRY.


76. Choose Save.

77. Enter as description Routine: Approximate Fiscal Year Period from BDD.



80. Choose Back.

4.4.4.7 Creating Transformation for ODS Objects 0RMP_DS01



Find 0RMP_DS01

2. Choose Search.

3. Expand Stock Consolidation.

4. Expand TRCS 2LIS_03_BF_TR -> ODSO 0RMP_DS01.

5. Right click 2LIS_03_BF_TR.


7. Enter the following data in the sub-screen of Target of the Transformation:


Object Type

Name 2LIS_03_BF_TR

8. Enter the following data in the sub-screen of Source of the Transformation:


Object Type DataSource


Source System FILE


10. Choose Save.


Maintain Start Routine

12. Choose Start Routine.


*$*$ begin of routine - insert your code only below this line *-* DATA: wa_SOURCE_PACKAGE LIKE LINE OF SOURCE_PACKAGE. LOOP AT SOURCE_PACKAGE INTO wa_SOURCE_PACKAGE. wa_SOURCE_PACKAGE-DOC_DATE = sy-datum - 21. wa_SOURCE_PACKAGE-PSTNG_DATE = sy-datum - 21. modify SOURCE_PACKAGE from wa_SOURCE_PACKAGE.


© SAP AG of 116

ENDLOOP.


15. Choose Save.


17. Choose Back.

4.4.5 Loading POS and Stock Data into ODS Objects

4.4.5.1 Creating Data Transfer Process for ODS Objects 0RMP_DS02

Procedure 1. Right click POS Consolidation.

2. Choose Create Data Transfer Process.

3. Execute the F4 Help of the Field name DataSource.

4. Choose the DataSource RT_DS_0RMP_DS02 as shown in the following screenshot:

5. Choose Continue.

6. Enter the following data on the tab page Extraction:


Extraction Mode Full

7. Go to the tab page Execute.

8. Choose Activate.

9. Choose Execute.

10. Choose Yes in the upcoming screen if you want to enter the monitor, otherwise No.

11. Choose Refresh to see that there is a green data transfer process.

12. Choose Back.


Before you activate the data please check if the data request of the ODS Object has a green traffic. Otherwise delete the data request and execute the data transfer process again. You can repeat these steps as often you want.

14. Choose Activate Data.

15. Select the green data request.

16. Choose Start.

17. Choose Refresh to see that the request is disappeared from the data request list.

4.4.5.2 Creating Data Transfer Process for ODS Objects 0RMP_DS01

Procedure


© SAP AG of 116


2. Choose Create Data Transfer Process.

3. Execute the F4 Help of the Field name DataSource.

4. Choose the DataSource RT_DS_0RMP_DS01 as shown in the following screenshot:

5. Choose Continue.

6. Enter the following data on the tab page Extraction:


Extraction Mode Full

7. Go to the Execute tab.

8. Choose Activate.

9. Choose Execute.

10. Choose Yes in the upcoming screen if you want to enter the monitor, otherwise No.

11. Choose Refresh to see that there is a green data transfer process.

12. Choose Back.

13. Right click Stock Consolidation

Before you activate the data please check if the data request of the ODS Object has a green traffic light. Otherwise delete the data request and execute the data transfer process again. You can repeat these steps as often you want.

14. Choose Activate Data.

15. Select the green data request.

16. Choose Start.

17. Choose Refresh to see that the request is disappeared from the data request list.

4.4.6 Loading POS and Stock Data into InfoProviders

Use The update of the InfoProvider 0RMP_C22 and 0RMP_C24 is a manually step. Before you execute the update you must check that there is no data request in the InfoProviders

How to delete a data requests from the InfoProviders you can findout in in chapter 6.



Find 0RMP_DS01

2. Choose Search.


4. Follow the context menu path Additional functions Update 3.x Data to Targets.

5. Flag Full Update.


© SAP AG of 116

6. Choose Update.

7. Go to the tab page Data Targets.

8. Flag Select Data Targets.

9. Select the InfoProviders with the Technical name 0RMP_C24 under the Field name Updating the data target.

10. Go back to the Schedule tab.

11. Choose Start.



14. Choose Back.

15. Search for 0RMP_DS02, as described before.


17. Follow the context menu path Additional functions Update 3.x Data to Targets.

18. Flag Full Update.

19. Choose Update.

20. Go to the tab page Data Targets.

21. Flag Select Data Targets

22. Select the InfoProviders with the Technical name 0RMP_C22 under the Field name Updating the data target.

23. Go back to the Schedule tab.

24. Choose Start.



27. Choose Back.

Result

Be aware that if you have data requests with a red traffic there will be no data selected in a query. Check if there are such data requests. You must change them to data requests with green traffic lights and delete them. How to do this you find in Appendix C, chapter Deleting Data Requests.

If you have here data requests with red traffic light the Slow Seller Analysis that you execute by using the transaction /MAP/SSM2 would not provide any result because it is calling the query 0RMP_MC21_Q0020 Slow Seller Management Analysis.

4.4.7 Reloading POS and Stock Data SSM If you want to reload the flatfiles you have to delete the data request in the InfoProviders 0RMP_C24 and 0RMP_C22, in the ODS Objects 0RMP_DS01 and 0RMP_DS02 and in the DataSources of POS Data SSM and Stock Data SSM

4.4.8 Applying Hierarchy/Attribute Change

Use


© SAP AG of 116

If hierarchies and attributes for characteristics have changed, then it is necessary to make structural changes to the aggregates in order to adjust the data accordingly.






3. Follow the path choose Tools Apply Hierarchy/Attribute Change starting in the board

4. Choose InfoObjectList.

5. There could be entries like:

Description InfoObject

Store Article 0MAT_PLANT

6. Choose Save InfoObject List.

7. Choose Execute.

8. Choose Refresh until you get the message Hierarchy/Attribute Change Is Finished.

4.5 Allocation

4.5.1 Creating InfoAreas

Use The purpose of this activity is to create an InfoArea as a method to structure data containers like InfoProviders and their respective data paths.






3. Follow the application path choose Industry Sectors Trade IndustriesRetailing.

4. Right click the InfoArea Retailing.

5. Choose Create InfoArea.

6. Enter the following data in the dialog box Create InfoArea:


Info Area RT_ALLOC

Long Description Allocation

7. Choose Continue to create the InfoArea.


© SAP AG of 116

4.5.2 Creating InfoProviders

Use The purpose of this activity is to create an InfoProvider in which the data from a source system will be stored.






3. Follow the path choose Industry SectorsTrade Industries Retailing.

4. Right click the InfoArea Allocation - RT_ALLOC.

5. Choose Create InfoCube.



InfoCube RT_C01

Description Allocation Strategy

InfoArea RT_ALLOC

InfoProvider Type Standard InfoCube

7. Choose Create.

8. In the next window you create the following time characteristics, unit characteristics, characteristics and key performance indicators for the InfoProvider:

● Characteristics:

○ 0MATERIAL Material

○ 0MATL_GROUP Material group

○ 0CM_HIEID Hierarchy ID

○ 0CM_CDT3 Segment

○ 0CM_CDT4 Subsegment

○ 0PLANT Store

○ 0RT_SEASON Season category

○ 0RT_PRBAND Price Band Category

● Time characteristics:

○ 0CALMONTH Calendar year/Month

● Key performance indicators:

○ 0CPSAEXCUSU Absolute Sales / SUn

9. Right click Dimension 1.

10. Follow the menu path Properties.



© SAP AG of 116


Description Article


13. Right click Dimensions

14. Follow the context menu path Create New Dimensions.

15. Enter in the screen Create Dimensions the following data:


Description Store




Description Consumer




Season Season


21. Right click the dimension Time.


23. Insert the following characteristics into the dimension Time:


0CALMONTH Calendar Year / Month


25. To fill the dimension Article, Store, Consumer and Season with characteristics act in the same way as for the dimension Time.

Insert the following characteristics into the dimension Article:


0MATERIAL Material

0MATL_GROUP Material Group

Insert the following characteristics into the dimension Store:


0PLANT Store

Insert the following characteristics into the dimension Consumer:



0RT_PRBAND Price Band Category

0CM_CDT3 Segment

0CM_CDT4 Subsegment


© SAP AG of 116

Insert the following characteristics into the dimension Season:


0RT_SEASON Season category

To assign key figures to the InfoProvider proceed as follows.

26. Right click Key Figures.


28. Insert the following key figure:


0CPSAEXCUSU Absolute Sales / SUn



4.5.3 Creating Application Components

Use The purpose of this activity is to create an Application Component as a structure element in the InfoSources tree.








4. Right click the application component Retailing.

5. Choose Create application component.

6. In the following screen, enter the following data:


Application Component ZRT_ALLOC

Long Description Allocation

7. Select Continue.


Use The purpose of this activity is to create an InfoSource to provide the InfoCube with data from an external data source. For the allocation scenario this a csv file with comma separated values.

Procedure


© SAP AG of 116








4. Right click the Application Component Allocation.




InfoSource RT_IS_RT_C01

Long description InfoSource RT_C01

7. Choose Continue.

8. Right click the newly created InfoSource RT_IS_RT_C01.

9. Choose Change.


11. Choose Template on the right hand side.

12. Flag the field of InfoCube and enter RT_C01.

13. Choose Transfer

14. Choose Transfer all InfoObjects



17. Choose Back.

18. Choose Collapse to close the Communication_Struct

19. Choose Expand to open the Transfer_structure/Transfer_Rules.



Source System FILE by Chooseing

21. Choose Yes in the upcoming screen Save Changes? The system will automatically propose the transfer rules.


23. Choose Back.


Use The purpose of this activity is to assign update rules in order to prepare the data transfer into the InfoProvider.

Procedure


© SAP AG of 116









Find RT_C01

5. Choose Search.

6. Right click the InfoProvider RT_C01


8. Flag the field of InfoSource on the Update rules create: Start.screen.

9. Enter as Info Source RT_IS_RT_C01.



12. Choose Back.

4.5.6 Assigning InfoPackage to InfoSources and Loading Data

Use The purpose of this activity is to assign InfoPackages to InfoSources with which you can load data into the InfoProvider RT_C01. The table below lists the flatfiles that have to load.


RT_C01 Allocation Strategy Flatfile_RT_C01_2008.csv


For the creation of an InfoPackage you need to enter a csv-file. The flatfiles are stored on the Doku CD SAP Best Practices in the folder \Misc\Retail\IN\Flatfiles. They must be installed on your hard disk or any of your file server. An installation in this way is important because you have defined in the InfoPackage that an external load takes place from a client workstation.

You load in this chapter the flatfiles for Merchandise and Store Planning. They are stored in the csv folder within the folder Allocation.






3. Choose Search.



© SAP AG of 116


Find RT_C01

5. Choose Search.

6. Expand RT_C01RT_IS_RT_C01.

7. Expand InfoSource RT_C01.

8. Expand from RT_IS_RT_C01 for FILE.

9. Right click RT_IS_RT_C01.




InfoPackage Description Flatfile Load: Transactional Data RT_C01

12. Select the line for RT_IS_RTC01 in the section DataSource.

13. Choose Save.


15. Choose the External data tab and make the following entries:



File type



See the comments in the prerequisites paragraph of this chapter. Choose the first flatfile Flatfile_RT_C01_2008.csv





Currency Conversion for External Systs unflag

Number of Header Rows to be Ignored 1

13. Choose the Processing tab and make the following entry:

Field name Value


14. Choose the Data targets tab and set flag in the field of Select Data Targets.


© SAP AG of 116

15. Select the InfoProvider RT_C01under the Field name Updating the data target.

16. Choose the Update tab and make the following entries:

Field name Values



17. Choose the Schedule tab.


19. Choose Monitor to monitor the request.

20. Choose Refresh tree on the Monitor - Administrator Workbench screen until until the status of your request is successful. That means your request obtains a green traffic light.


Result

Be aware that if you have data requests with a red traffic there will be no data selected in a query. Check if there are such data requests. You must change them to data requests with green traffic lights and delete them. How to do this you find in Appendix C, chapter Deleting Data Requests.

If you have here data requests with red or yellow traffic light the queries you create in the next chapter would not provide any result.

4.5.7 Logging on to the Query Designer

Use You have to use the Query Designer SAP BW 3.x. To preferred method to access the Query Designer is described in the chapter Microsoft Office Start Menu 4.5.7.2.

4.5.7.1 Transaction RRMX


Transaction code RRMX


© SAP AG of 116

That means you create a query using transaction RRMX - Analyzer and the SAP BI front end Excel from which the Query Designer can be started. You have to verify that you are working with the 3.x Query Designer.

2. Choose the Question mark and choose About.

3. If you find a screen with the following information you are working with the right version.

Otherwise you have to change settings for the BEX Analyzer. Therefore execute the next steps

4. Choose BEx Analyzer.

5. Follow the menu path, choose Global Settings.

6. Set the flag Launch legacy version from RRMX.

7. Repeat step (1) and (2).

8. Choose Tools.

9. Choose Query Designer.

4.5.7.2 Microsoft Office Start Menu

Procedure 1. One possibility to access the Query Designer is using the following navigation option:

Microsoft Office Start Menu

Start All Programs Business Explorer Business Explorer

(SAP BW 3.x) Query Designer (SAP BW 3.x)

2. Log on with your user in the upcoming SAP Logon screen to the BI system.

4.5.8 Creating Queries

Use You can analyze the data in an InfoProvider using queries that are could be carried out as part of allocation strategies in the ECC System.

Prerequisites The variable used in the query must be activated. Refer to chapter Activating Business Content, Query Variables.

Procedure


© SAP AG of 116

1. Choose New Query in the board.

2. Choose Technical Name on/off in the board.

3. Follow the path Industry Sectors Trade Industries Retailing Allocation

4. Double-click the InfoProvider Allocation Strategy RT_C01.

5. You enter the following screen:

6. Choose Technical Name to de-/activate the technical names.

The following two steps explain How to Drag and Drop: as an example.

a) Expand for example, the hierarchy of Consumer. Then you see several characteristics, choose the node of Price Band Category

b) Now click and hold down the left button on the Price Band Category and move the mouse into the desired frame. In our case the Free Characteristics and release the mouse button.


© SAP AG of 116


Procedure 1. Insert via Drag and Drop into the frame Free Characteristics:


0RT_PRBAND Price Band Category

0RT_SEASON Season category

2. Make sure that you have the right order of the characteristics.

3. Insert via Drag and Drop into the frame Rows:


0PLANT Store

0CALMONTH Calendar year/Month

0MATERIAL Article

4. Insert via Drag and Drop into the frame Columns:


0CPSAEXCUSU Absolute sales/ SUn

Now restrictions must be set in form of variables for the characteristics in the frames free characteristics, rows and columns.

5. Right click Price Band Category.

6. Choose Restrict.

7. Select the tab page of Variables.


© SAP AG of 116



10. Restrict the InfoObject Price Band Category with the following variable that you have to create:


RT_PBC Price Band Category

Single Value Optional


12. Choose New Variable.

13. Enter the values as shown in table:


Variable Name RT_PBC

Description Price Band Category


Characteristic Price Band Category

14. Choose Next.

15. Change the default values as shown in table.


Variable Represents Single Value


Ready for Input Set flag

16. Choose Next.

17. Choose Next.

18. Choose Exit.


20. Choose Add.

21. Choose OK.

22. Restrict the InfoObject Season with the following Variable:


0P_OSAIS Season Single Value Optional

23. Restrict the InfoObject Plant with the following Variable:


0S_PLANT Plant (Selection Options, Optional)

Selection option Optional

24. Restrict the InfoObject Calendar Year/Month with the following Variable:


0S_CALMO Month Selection option Optional

25. Restrict the InfoObject Material with the following Variable:


© SAP AG of 116


0S_MAT Material (Selection Options, Optional)


26. Now that you have restricted the characteristics the query should be equal to the one shown in the next screen shot.

27. Choose Save Query as.


Field name Value

Description Allocation - Article/Month


29. Choose Save.


Procedure 1. Being in the first query choose Save Query as.

Field name Value

Description Allocation – Material Group/Month


2. Exchange Material against Material Group in the frame Rows.

3. Restrict the InfoObject Material Group with the following Variable:


© SAP AG of 116


0S_MATGR Material Group


4. Choose Save Query.

5. Now that you have restricted the characteristics the query should be equal to the one shown in the screen shot.


© SAP AG of 116


Procedure 1. Being in the second query choose Save Query as

Field name Value

Description Allocation - Subsegment/Month


2. Add via Drag and Drop into the Free Characteristics frame:



3. Exchange Material Group against SubSegment in the frame Rows.

4. Restrict the InfoObject Hierarchy ID with the following Variable:


0CMHIEID CDT Hierarchy ID


5. Restrict the InfoObject Subsegment with the following Variable:


RT_SSEG Subsegment Selection option Optional

6. Right click Subsegment

7. Choose Restrict.

8. Select the tab page Variables.




12. Choose New Variable

13. Enter the values as shown below:


Variable Name RT_SSEG

Description Subsegment


Characteristic Subsegment

14. Choose Next.

15. Change the default values:





16. Choose Next.

17. Choose Next.


© SAP AG of 116

18. Choose Exit.

19. Select the just created variable.

20. Choose Add.

21. Choose OK.


23. Now that you have restricted the characteristics. The query should be equal to the one shown in the next screen shot.


© SAP AG of 116


Procedure 1. Being in the third query choose Save Query as.

Field name Value

Description Allocation - Segment/Month


2. Delete the Hierarchy ID from the Free Characteristics frame.

3. Exchange SubSegment against Segment in the frame Rows.

4. Restrict the InfoObject Segment with the following Variable:


RT_SEG Segment Selection option Optional

5. Right click Segment.

6. Choose Restrict.

7. Select the tab page Variables.




11. Choose New Variable

12. Enter the values as shown in the table:


Variable Name RT_SEG

Description Segment


Characteristic Segment

13. Choose Next.

14. Change the default values as shown in the table:





15. Choose Next.

16. Choose Next

17. Choose Exit.


19. Choose Add.

20. Choose OK.


22. Now that you have restricted the characteristics. The query should be equal to the one shown in the next screen shot.


© SAP AG of 116

4.5.9 Allocation Settings – SAP ECC

4.5.9.1 Field Name Mappings BW <–> ECC

Use The purpose of this activity is to define the integration of the allocation process. That means a Field name mapping must take place.

Prerequisites The necessary queries must be created.

Procedure 1. Access the activity using the following navigation option:

Transaction code MCW_AA

2. Choose Execute IMG Activity in front of the entry Maintenance of Queries for Analytical Applications.

3. Choose New Entries in the following screen.


Target System Analyt. Appl. Query Query Name

The logical name of your BI System

RT_C01/RT_RTC01_Q001 Allocation - Article/Month


RT_C01/RT_RTC01_Q002 Allocation - Material Group/Month


RT_C01/RT_RTC01_Q003 Allocation - Subsegment/Month


© SAP AG of 116


RT_C01/RT_RTC01_Q004 Allocation - Segment/Month

5. Mark the entry Allocation – Article/Month.

6. Double-click the folder of Maintain Query Components.


8. Map the BI Field names with the ECC Field names according to the following screen shot. The value is not necessary an entry that you find within the F4-Help.

OLAP (BW) Field name Field name in OLTP (R3) PeTP

0PLANT WERKS

0CALMONTH CALMONTH MN

0MATERIAL MATNR

0CPSAEXCUSU CPSAEXCUSU

RT_PBC P_PBC

0P_OSAIS P_SEASON

0S_PLANT SL_WERKS

0S_CALMO CALMONTH MN

0S_MAT SL_MATNR

9. Choose Save.


11. Mark the entry Allocation - Material Group/Month.

12. Double-click the folder Maintain Query Components.




0PLANT WERKS


0MATL_GROUP MATKL


RT_PBC P_PBC

0P_OSAIS P_SEASON

0S_PLANT SL_WERKS


0S_MATGR SL_MATKL

15. Choose Save.

16. Choose Back twice..

17. Mark the entry Allocation – Subsegment/Month.

18. Double-click Maintain Query Components..



© SAP AG of 116



0PLANT WERKS


0CM_CDT4 ARTH05


RT_PBC P_PBC

0P_OSAIS P_SEASON

0S_PLANT SL_WERKS


0CMHIEID P_AHID

RT_SSEG SL_AH05


22. Mark the entry Allocation – Segment/Month.

23. Double-click Maintain Query Components.




0PLANT WERKS


0CM_CDT3 ARTH04


RT_PBC P_PBC

0P_OSAIS P_SEASON

0S_PLANT SL_WERKS


RT_SEG SL_AH04

4.5.9.2 Maintenance of Methods for Analytical Applications

Use The purpose of this activity is to define the methods for the integration of the allocation process. The queries must be already created.


Transaction code MCW_AA


© SAP AG of 116

2. Choose Execute Maintenance of Methods for Analytical Applications.

3. On the Determine Work Area: Entry screen, enter the following data:


Analytical Appl. 001

4. Choose Continue.

5. Choose New Entries to add a new method and add at the table:


Method RTAL01

Method description Allocation Article/Month

6. Choose Enter.

7. Mark the new line and double-click the folder of Maintain Method Steps.

8. Choose New Entries to add a new method step.



Meth. Step 1

Target system The logical name for BI System

Analyt. Appl. Query RT_C01/RT_RTC01_Q001

10. Choose Enter.




Method RTAL02

Method description Allocation - Material Group/Month

13. Choose Enter.





Meth. Step 1



17. Choose Enter .




Method RTAL03

Method description Allocation - Subsegment/Month

20. Choose Enter.


© SAP AG of 116





Meth. Step 1



24. Choose Enter.


26. Choose New Entries to add a new method.



Method RTAL04

Method description Allocation - Segment/Month

28. Choose Enter.





Meth. Step 1



32. Choose Enter.

33. Choose Back.

34. Choose Save.

4.5.9.3 Extraction Settings – SAP ECC

Use In this activity, you can configure BI extraction on the basis of two parameters:

CONCAT With this parameter, you can set whether the system should take account of a concatenation of the node ID with the hierarchy ID during extraction. There are two values:

keiko - concatenation not activated konka - concatenation activated

PACKSIZE With this parameter, you can define the packet size for saving the data to the extract tables. This significantly improves system performance when saving the article hierarchy.

Standard settings

CONCAT The default value of the parameter is KEIKO - Concatenation for the extraction is deactivated.


© SAP AG of 116

PACKSIZE If you do not make any settings, value 1 is set by default. The value of the parameter depends on the data volume of the particular scenario. The more data that is written, the more important it is that you select the parameter.


IMG menu SAP Customizing Implementation Guide Logistics - General

Article Hierarchy BW Extraction


2. Choose Customizing Extraction.


4. Select the following entry by choosing :

Customizing Object Value of Customizing Object

Concatenation During Extraction On/Off Concatenation for Extraction Inactive

5. Choose Save.

5 Adjust Steps Concerning Personalization

5.1 Changing Merchandise Planning Flatfiles

Use For using the delivered merchandise flatfiles in a local environment you have to do some flatfile changes concerning master data. The flatfiles you load in the BI System are csv-files. However the master data changes take place in the xls-files that are also part of the delivery. When finishing the changes you recreate the csv-files.

Within the flatfiles there is a random number generator for the calculation of the some key figures. When you enter the excel file every time new numbers will be generated for some key figures. If you exit the excel file you will be ask if you want to store the changes. You can say NO.

5.1.1 InfoProvider 0RMP_C05

Procedure 1. Open the excel-file Flatfile_0RMP_C05_MCP_2008.XLS

2. Replace within the worksheets Flatfile Flatfile 0001 0RMP_C05 2008, Flatfile 0002 0RMP_C05 2008 and Flatfile oSeg 0RMP_C05 2008 for 0DISTR_CHAN the cell Q2 with the new distribution channel. The other excel cells will be filled automatically.

3. Replace within the worksheets Flatfile 0001 0RMP_C05 2008, Flatfile 0002 0RMP_C05 2008 and Flatfile oSeg 0RMP_C05 2008 for 0SALESORG the cell BW2 with the new sales organization. The other excel cells will be filled automatically.

4. Save the excel file by choosing Save.

5. Choose the worksheet Flatfile 0001 0RMP_C05 2008

6. Follow the excel menu path File Save As …

7. In the Field name Save as type: search for CSV(Comma delimited)(*.csv)

8. Save the file under the name Flatfile_0RMP_C05_MCP_2008_0001.csv


© SAP AG of 116

9. Choose Save.

10. Replace the flatfile if it already exists.

11. Continue with OK in the next screen.

12. Continue with YES in the next screen.

13. Follow the excel menu path File Exit …

14. Continue with No in the next screen.

15. Execute the steps (6) – (15) for the Worksheet Flatfile 0002 0RMP_C05 2008 Name the flatfile Flatfile_0RMP_C05_MCP_2008_0002.csv.

16. Execute the steps (6) – (15) for the Worksheet Flatfile oSeg 0RMP_C05 2008 Name the flatfile Flatfile_0RMP_C05_MCP_2008_oSeg.csv.

17. Execute the steps in this subchapter also for the flatfile Flatfile_0RMP_C05_MCP_BUDGET_2008.XLS Name the flatfiles Flatfile_0RMP_C05_MCP_2008_0001.csv, Flatfile_0RMP_C05_MCP_2008_0002.csv



20. Execute the steps in this subchapter also for the flatfile Flatfile_0RMP_C05_MP1.XLS Name the flatfiles Flatfile_0RMP_C05_MP1_2009.csv.


5.2 Changing Assortment Planning Flatfiles

Use For using the delivered assortment flatfiles in a local environment you have to do some flatfile changes concerning master data. The flatfiles you load in the BI System are csv-files. However the master data changes take place in the xls-files that are also part of the delivery. When finishing the changes you recreate the csv-files.

5.2.1 InfoProvider RT_C35

Procedure 1. Open the excel-file Flatfile_RT_C35_Fashion_2008.xls

2. Replace within the worksheet Flatfile_RT_C35_Fashion_2008.xls for 0DISTR_CHAN the cell K2 with the new distribution channel. The other excel cells will be filled automatically.

3. Replace within the worksheet Flatfile_RT_C35_Fashion_2008.xls for 0SALESORG the cell AA2 with the new sales organization. The other excel cells will be filled automatically.



6. Save the file under the name Flatfile_RT_C35_Fashion_2008.csv

7. Choose Save.



© SAP AG of 116





5.3 Changing Allocation Flatfiles

Use For using the delivered allocation flatfiles in a local environment you have to do some flatfile changes concerning master data. The flatfiles you load in the BI System are csv-files. However the master data changes take place in the xls-files that are also part of the delivery. When finishing the changes you recreate the csv-files.

5.3.1 InfoProvider RT_C01

Procedure 1. Open the excel-file Flatfile_RT_C01.XLS

2. Replace within the worksheet Flatfile RT_C01 2008 for 0PLANT in column H the old stores by the new stores.




6. Save the file under the name Flatfile_RT_C01_2008.csv

7. Choose Save.






6 Appendix A: Helpful BI Actions

6.1 Activating InfoProviders

Use If you change anything on the definition of an InfoProvider respectively of an DataStore Object you must reactivate the BI Object. The necessary steps are described exemplary for the InfoProvider 0RMP_C05.





© SAP AG of 116



3. Choose Search.



Find 0RMP_C05

5. Choose Search.


7. Choose Change.

8. Choose Activate.

6.2 Activating Update Rules

Use If you change anything on the definition of an InfoProvider respectively DataStore Object the assigning Update Rule must be reactivated. The necessary steps are described exemplary for the InfoProvider 0RMP_C05.






3. Choose Search.



Find 0RMP_C05

5. Choose Search.

6. Expand the hierarchy with following information:

Merchandise Planning, Plan 0RMP_C05

7. Right click 0RMP_C05 RT_IS_0RMP_C05.

8. Choose Change.

9. Choose Activate .

6.3 Activating Transfer Rules

Use If you change anything on the definition of Transfer Rules you must reactivate them.

In the BI System there are a lot of programs which are generated when activating a BI Object. So to have all the dependent object in a valid version it is useful to reactivate them too. That means if


© SAP AG of 116

you change Transfer Rules you should also reactivate the Update Rule and the InfoProvider respectively the DataStore Object.

An inactive Transfer Rules looks like

An active Transfer rules looks like

The necessary steps are described exemplary for the DataStore Object 0RMP_DS02 and its transfer rules defined for data loading from the ECC system.






3. Choose Search.



Find 0RMP_DS01

5. Choose Search.




9. Choose Continue.

6.4 Replicate DataSources

Use If a version of a DataSource in the SAP BI System is not the same as in the SAP ECC System then you must replicate it again and activate the corresponding transfer rules again.





2. On the Data Warehousing Workbench: Modeling screen, choose DataSources.

3. Choose Choose Source System.

4. Select your ECC System.

5. Choose Search.

6. Enter the desired DataSource in the upcoming screen:


Find 0MATERIAL, for example


© SAP AG of 116

7. Choose Search.

8. Right click 0MATERIAL.

9. Choose Replicate DataSource.

10. On the Data Warehousing Workbench: Modeling screen choose InfoSources.

11. Choose Search.

12. Enter the desired DataSource in the upcoming screen:


Find 0MATERIAL, for example

13. Choose Search.

14. Activate the corresponding transfer rules and Update Rules again.

6.5 Deleting Data Requests

Use Within the Slow Seller Management Scenario you must reload the flatfiles in periodic time intervals if you want that the Slow Seller Analysis produces always markdown proposals. That means you must delete the data requests in the InfoProviders 0RMP_C22 and 0RMP_C24 respectively in the DataStore Objects 0RMP_DS01 and 0RMP_DS02.

If you want to reload the data in the Merchandise Planning environment you have to delete the data request in the InfoProvider 0RMP_C05.

A data request deletion requires always the same steps. It doesn’t matter if you want to do it for a Basic InfoProvider or DataStore Object. But if you want to do it for a Real Time InfoProvider you must execute additional steps.

Under Procedure you find the necessary steps for a data request deletion in a Basic InfoProvider and in a Real Time InfoProvider. The Basic InfoProvider is exemplary 0RMP_C22 and the Real Time InfoProvider is exemplary 0RMP_C05.






6.5.1 Basic InfoProvider

Procedure 1. Choose Search.



Find 0RMP_C22


© SAP AG of 116

3. Choose Search.


5. Choose Manage.

A red or yellow data request couldn’t be deleted. First you have to change the traffic light in a green one. To do this, execute the following steps.

6. Double-click the red or yellow traffic light in the corresponding data request

7. Choose Status OK.

8. Choose Save. For a green data request execute the following steps to delete it.

9. Select the data request like

10. Choose Delete.

11. Choose Refresh to check the deletion of the request.

12. Choose Exit to close the right hand frame.

6.5.2 Real Time InfoProvider

Procedure 1. Choose Search.



Find 0RMP_C05

3. Choose Search.




7. Choose Continue.

By executing these steps a data request with a yellow traffic light is changed to a data request with a green traffic light.


9. Choose Manage.

For a green data request execute the following steps to delete it.

10. Select the data request like

Choose Delete.

11. Choose Refresh to check the deletion of the request.

12. Choose Exit to close the right hand frame.





© SAP AG of 116


6.6 Applying Hierarchy/Attribute Change

Use If hierarchies and attributes for characteristics have changed, then it is necessary to make structural changes to the aggregates in order to adjust the data accordingly.





2. On the Data Warehousing Workbench: Modeling screen choose InfoProvider.

3. Follow the path Tools Apply Hierarchy/Attribute Change starting in the board.

4. Choose InfoObject List.

5. There could be entries like

Description InfoObject

Store Article 0MAT_PLANT

6. Choose InfoObject List.

7. Choose Save InfoObject List.

8. Choose Refresh until you get the message Hierarchy/Attribute Change Is

Finished.

7 Appendix B: Year Change Tasks When a new year starts and the plan year in your planning environment should be the next year this requires the following steps.

7.1 Maintaining Fiscal Year Variant You must maintain the fiscal year variant for the new plan year in your planning environment. You did it already until the year 2010.

7.2 Deleting Data Requests You must delete the data requests in the InfoProviders 0RMP_C05, RT_C01, RT_C31, RT_C35.

7.3 Adjusting Flatfiles You must change all the year stuff in the flatfiles for the Merchandise Plan, Store Plan and Assortment Plan. Then you have to recreate the csv-files.

764: bi retail: merchandise and assortment...

Documents