EHP5 for SAP ERP
6.0
June 2011
English
BI Retail: Merchandise
and Assortment Planning
(764)
Building Block Configuration Guide
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Copyright
© 2011 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 BusinessObjects Explorer, StreamWork,
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 Software Ltd. Business
Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks of
Sybase, Inc. Sybase 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
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
Page 2 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Icons
Icon
Meaning
Caution
Example
Note or Tip
Recommendation
Syntax
Typographic Conventions
Type Style
Description
Example text
Words or characters that appear on the screen. These include 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
Page 3 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Contents
Merchandise and Assortment Planning: Configuration Guide ........................................................ 7
1
Purpose .................................................................................................................................... 7
2
Preparation ............................................................................................................................... 7
3
Budget Customizing ................................................................................................................. 7
4
3.1
Define PPW Budget Levels – SAP BI ............................................................................ 7
3.2
Define OTB Budget Levels – SAP BI ............................................................................. 8
3.3
Define PPW Key Figures - SAP BI ................................................................................ 9
3.4
Define OTB Key Figures - SAP BI ............................................................................... 10
3.5
Define PPW Budget Type - SAP BI ............................................................................. 11
3.6
Define OTB Budget Types - SAP BI ............................................................................ 12
3.7
Activate Budget Types - SAP BI .................................................................................. 14
3.8
Create RFC Destinations - SAP BI .............................................................................. 15
3.9
Transfer Budget Types to SAP ECC – SAP BI ............................................................ 17
3.10
Assign PPW Budget IDs – SAP ECC .......................................................................... 18
3.11
Activate PPW Budget Type – SAP ECC ...................................................................... 19
3.12
Check and Extend OTB Budget Types – SAP ECC .................................................... 20
3.13
Activate OTB Budget Types – SAP ECC ..................................................................... 21
3.14
Reorganization of OTB Budgets – SAP ECC .............................................................. 22
3.14.1
Determine the Generated Budget Plan Table ......................................................... 22
3.14.2
Compare Corresponding Structure with Budget DataStore Object ......................... 23
3.14.3
Delete Structure and Table Type for the Generated Plan Table ............................. 24
3.14.4
Reorganize Budget Types ....................................................................................... 26
Transactional Data Extraction via Flatfiles – SAP BI ............................................................. 27
4.1
Create Application Components .................................................................................. 27
4.2
Merchandise Planning .................................................................................................. 28
4.2.1
Create InfoSources and Transfer Rules .................................................................. 28
4.2.2
Assign Update Rules to InfoProviders ..................................................................... 29
4.2.3
Execute Info packages for Real Time InfoProvider ................................................. 30
4.2.4
Release PPW Budget .............................................................................................. 34
4.2.5
Release OTB Budget ............................................................................................... 36
4.2.6
Assign Price Planner Groups to Budget – SAP ECC .............................................. 38
4.3
Assortment Planning .................................................................................................... 39
4.3.1
Define Key Figures – SAP BI ................................................................................... 39
4.3.2
Maintain Values for Key Figure 0RT_KEYFIG ........................................................ 41
© SAP AG
Page 4 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.3.3
Create InfoProviders ................................................................................................ 43
4.3.4
Create InfoSources and Transfer Rules .................................................................. 48
4.3.5
Assign Update Rules to InfoProviders ..................................................................... 49
4.3.6
Assign InfoPackage to InfoSources and Loading Data ........................................... 50
4.3.7
LOG ON to the Query Designer ............................................................................... 55
4.3.8
Create Queries ......................................................................................................... 56
4.3.9
Define Message Types and Selections Options for Releasing Assortments .......... 63
4.3.10
BADI UPARI_ASRTPLN .......................................................................................... 64
4.3.11
Release Assortment Plan ........................................................................................ 70
4.3.12
Create Purchasing List – SAP ECC ......................................................................... 72
4.3.13
OTB Check: Maintain Document-Type Dependent Settings – SAP ECC ............... 73
4.4
4.4.1
Generate Export DataSources ................................................................................. 76
4.4.2
Install Interface “Goods Receipt Date” ..................................................................... 78
4.4.3
Load Goods Receipt Dates into 0MAT_PLANT ...................................................... 83
4.4.4
Install Interface “ POS and Stock Data SSM“ .......................................................... 85
4.4.5
Loading POS and Stock Data into ODS Objects ................................................... 107
4.4.6
Load POS and Stock Data into InfoProviders ....................................................... 110
4.4.7
Reloading POS and Stock Data SSM .................................................................... 112
4.4.8
Apply Hierarchy/Attribute Change ......................................................................... 113
4.5
5
Slow Seller Management ............................................................................................. 75
Allocation .................................................................................................................... 114
4.5.1
Create InfoAreas .................................................................................................... 114
4.5.2
Create InfoProviders .............................................................................................. 114
4.5.3
Create Application Components ............................................................................ 117
4.5.4
Create InfoSources and Transfer Rules ................................................................ 118
4.5.5
Assign Update Rules to InfoProviders ................................................................... 119
4.5.6
Assign InfoPackage to InfoSources and Loading Data ......................................... 120
4.5.7
Log on to the Query Designer ................................................................................ 123
4.5.8
Create Queries ....................................................................................................... 124
4.5.9
Allocation Settings – SAP ECC ............................................................................. 134
Appendix A: Helpful BI Actions............................................................................................. 141
5.1
Activate InfoProviders ................................................................................................ 141
5.2
Activate Update Rules ................................................................................................ 141
5.3
Activate Transfer Rules .............................................................................................. 142
5.4
Replicate DataSources .............................................................................................. 144
5.5
Delete Data Requests ................................................................................................ 145
5.5.1
© SAP AG
Basic InfoProvider .................................................................................................. 145
Page 5 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
5.5.2
5.6
6
Real Time InfoProvider .......................................................................................... 146
Apply Hierarchy/Attribute Change .............................................................................. 147
Appendix B: Year Change Tasks ......................................................................................... 148
6.1
Maintain Fiscal Year Variant ...................................................................................... 148
6.2
Delete Data Requests ................................................................................................ 148
6.3
Adjust Flatfiles ............................................................................................................ 148
6.4
Load Updated Flatfiles ............................................................................................... 148
© SAP AG
Page 6 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Merchandise and Assortment Planning:
Configuration Guide
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 located on the Documentation DVD
on the Content Library page under Technical Information (on the left navigation pane).
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 Define 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.
1. Access the activity using one of the following navigation options:
Transaction Code
© SAP AG
SPRO
Page 7 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
SAP Customizing Implementation Guide  SAP NetWeaver 
Business Intelligence  Settings for BI Content  Trade
Industries  Retailing  Budget Planning Budget Type
Define Budget Levels
IMG Menu
2. Left-Mouse-Click on the Button
.
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 on
6. Left-Mouse-Click on the Button
7.
.
On the New Entries: Overview of Added Entries screen make the following entries:
InfoObject
Long description
0CM_CDT3
Segment
0CM_HIEID
Hierarchy ID
0FISCPER
Fiscal year / period
0FISCVARNT
Fiscal year variant
0RT_SEASON
Season Category
8. Choose the Button
Save.
9. Choose the Button
Back.
10. Choose the Button
Back.
Hierarchy
Fiscal Year Variant
B1
K0
3.2 Define OTB Budget Levels – SAP BI
Procedure
1. Left-Mouse-Click on the Button
.
2. On the New Entries: Overview of Added Entries screen make the following entries:
Level
InfoCube
Long description
OTB
0RMP_C05
Merchandise Planning, Plan
3. Mark the entry OTB.
4. Double-Click on
© SAP AG
Page 8 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
5. Left-Mouse-Click on the Button
6.
.
On the New Entries: Overview of Added Entries screen make the following entries:
InfoObject
Long description
0CM_CDT3
Segment
0CM_HIEID
Hierarchy ID
0FISCPER
Fiscal year / period
0FISCVARNT
Fiscal year variant
0RT_SEASON
Season Category
7. Choose the Button
Save.
8. Choose the Button
Back.
9. Choose the Button
Back.
Hierarchy
Fiscal Year Variant
B1
K0
3.3 Define 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.
1. Access the activity using one of the following navigation options:
Transaction Code
SPRO
IMG Menu
SAP Customizing Implementation Guide  SAP NetWeaver 
Business Intelligence  Settings for BI Content  Trade
Industries  Retailing  Budget Planning Budget Type
Define Key Figures
© SAP AG
Page 9 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Procedure
1. Left-Mouse-Click on the Button
.
2. On the New Entries: Overview of Added Entries screen make the following entries:
Set keyfig
InfoCube
Long description
PPW
0RMP_C05
Merchandise Planning, Plan
3. Mark the entry PPW.
4. Double-Click on
5. Left-Mouse-Click on the Button
6.
.
On the New Entries: Overview of Added Entries screen make the following entries:
InfoObject
Long description
0RTSPRENSV
Revaluation at Retail (Negative)/ Retail Value
7. Choose the Button
Save.
8. Choose the Button
Back.
9. Choose the Button
Back.
3.4 Define OTB Key Figures - SAP BI
Procedure
1. Left-Mouse-Click on the Button
.
2. On the New Entries: Overview of Added Entries screen make the following entries:
Set keyfig
InfoCube
Long description
OTB
0RMP_C05
Merchandise Planning, Plan
3. Mark the entry OTB.
4. Double-Click on
.
5. Left-Mouse-Click on the Button
.
6. On the New Entries: Overview of Added Entries screen make the following entries:
InfoObject
© SAP AG
Long description
Page 10 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
InfoObject
Long description
0RTTPRQUOTA
Planned Open-To-Buy (Purchase Price)
7. Choose the Button
Save.
8. Choose the Button
Back.
9. Choose the Button
Back.
3.5 Define 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.
1. Access the activity using one of the following navigation options:
Transaction Code
SPRO
IMG Menu
SAP Customizing Implementation Guide  SAP NetWeaver 
Business Intelligence  Settings for BI Content  Trade
Industries  Retailing  Budget Planning Budget Type
Define Budget Types
Procedure
2. Left-Mouse-Click on the Button
© SAP AG
.
Page 11 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
3. On the New Entries: Details of Added Entries screen make the following entries:
The start date is always the today’s date.
4. Choose the Button
Save.
5. Choose the Button
Back.
3.6 Define OTB Budget Types - SAP BI
Procedure
1. Left-Mouse-Click on the Button
.
2. On the New Entries: Details of Added Entries screen make the following entries for Budget
Type B1:
© SAP AG
Page 12 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
The start date is always the today’s date.
3. Choose the Button
Save.
4. Choose the Button
Back.
5. Left-Mouse-Click on the Button
6. On the New Entries: Details of Added Entries screen make the following entries for Budget
Type B2:
© SAP AG
Page 13 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
The start date is always the today’s date.
7. Choose the Button
Save.
8. Choose the Button
Back.
3.7 Activate 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.
© SAP AG
Page 14 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
1. Access the activity using one of the following navigation options:
Transaction Code
UPARI_BUDG01
IMG Menu
SAP Customizing Implementation Guide  SAP NetWeaver 
Business Intelligence  Settings for BI Content  Trade
Industries  Retailing  Budget Planning Budget Type
Activate Budget Types
Procedure
2. On the Activation of Budget Type screen make the following entries:
Application
Budget Type
Start Date
01
01
Creation Day
3. Choose the Button
4. Choose the Button
Execute
Back.
5. On the Activation Budget Type screen make the following entries:
Application
Budget Type
Start Date
02
B1
Creation Date
6. Choose the Button
7. Choose the Button
Execute
Back.
8. On the Activation Budget Type screen make the following of entries:
Application
Budget Type
Start Date
02
B2
Creation Date
9. Choose the Button
10. Choose the Button
Execute
Back.
3.8 Create RFC Destinations - SAP BI
Use
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.
© SAP AG
Page 15 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
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.
1. Access the activity using one of the following navigation options:
Transaction Code
SPRO
IMG Menu
SAP Customizing Implementation Guide  SAP NetWeaver 
Business Intelligence  Settings for BI Content  Trade
Industries  Retailing  Budget Planning Transfer to SAP
ERP  Create ERP RFC Destinations
Procedure
2. Left-Mouse-Click on the Button
.
3. On the New Entries: Details of Added Entries screen make the following entries
Appl.
Characteristic
Value
InfoObject /
Field
RFC Destination SAP ERP
PPW (Price Planning Workbench)
4. Choose the Button
Back.
5. Open a new transaction > Goto 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 RFC Destination SAP ERP:
8.
9. Choose the Button
Save.
10. Choose the Button
Back.
11. Left-Mouse-Click on the Button
.
12. On the New Entries: Details of Added Entries screen make the following entries
Appl.
Characteristic
Value
InfoObject /
Field
RFC Destination SAP ERP
OTB (Open to Buy)
© SAP AG
Page 16 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
13. Choose the Button
Back.
14. On the Change View “Assignment RFC Destination to SAP ECC”: Overview screen make
the following entries with your ERP System > XXXCLNTXXX:
15. Choose the Button
Save.
16. Choose the Button
Back.
3.9 Transfer 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.
1. Access the activity using one of the following navigation options:
Transaction Code
UPARI_BUDG02
IMG Menu
SAP Customizing Implementation Guide  SAP NetWeaver 
Business Intelligence  Settings for BI Content  Trade
Industries  Retailing  Budget Planning Transfer to SAP
ERP  Transfer Budget Types to ECC
Procedure
2. On the Transfer of Budget Type screen make the following entries:
Application
Budget Type
Start Date
01
01
Creation Day is displayed
3. Choose the Button
4. Choose the Button
© SAP AG
Execute.
Back.
Page 17 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
5. On the Transfer of Budget Type screen make the following entries:
Application
Budget Type
Start Date
02
B1
Creation Day is displayed
6. Choose the Button
7. Choose the Button
Execute.
Back.
8. On the Transfer of Budget Type screen make the following entries:
Application
Budget Type
Start Date
02
B2
Creation Day is displayed
9. Choose the Button
10. Choose the Button
Execute.
Back.
3.10 Assign 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.
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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
SPRO
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:
© SAP AG
Page 18 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
3. Choose the Button
Save.
4. Choose the Button
Back.
3.11 Activate 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
Logistics - General  Price Planning Budget Planning 
Activate Budget Types
IMG Menu
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 screen activate budget type, make the following entries:
Field name
Description
User values
Note
Application
PPW (Price Planning Workbench)
01
Use F4
Budget type
01
Use F4
Valid from
Data create
Use F4
3. Choose the Button
Execute to activate the budget.
The log will be displayed with the message: Budget Type 01 was activated.
4. Choose the Button
© SAP AG
Back twice
Page 19 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
3.12 Check and Extend 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
SPRO
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 the Button
Details.
4. On the screen “Budget Types" Details make the following entries:
Field name
User values
Addin implementation
WRF_BUDG_TYPE_001
Priority
5
Condition Type
WOTB
5. Choose the Button
Save
6. Choose the Button
Back.
© SAP AG
Page 20 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
7. Choose the budget type for OTB B2
8. Choose the Button
Details.
9. On the screen "Budget Types" Details make the following entries:
Field name
User values
Addin implementation
WRF_BUDG_TYPE_003
Priority
4
Condition Type
WOTB
10. Choose the Button
11. Choose the button
Save
Back twice
3.13 Activate 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
SPRO
IMG Menu
Material Management  Purchasing  Seasonal Procurement
 Open-To-Buy(OTB)  Budget Planning  Activate Budget
Types
2. On the screen Activate Budget Types make the following entries:
Field name
Description
User values
Budget Application
OTB (Open-To-Buy)
02
Budget Type
© SAP AG
B1
Note
Use F4
Page 21 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Field name
Description
Valid from
3. Choose the Button
User values
Note
Date Create
Use F4
Execute to activate the budget.
The log will be displayed with the message: Budget Type B1 was activated.
4. Choose the Button
Back
5. On the screen Activate Budget Types make the following entries:
Field name
Description
User values
Budget Application
OTB (Open-To-Buy)
02
Budget Type
6. Choose the Button
B2
Note
Use F4
Execute to activate the budget.
The log will be displayed with the message: Budget Type B2 was activated.
7. Choose the Button
Back twice
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
Determine the Generated Budget Plan Table
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
SE16
SAP Menu
Tools  ABAP Workbench  Overview  Data Browser
2. On the screen Data Browser: Initial Screen make the following entries:
Field name
User value
Table Name
WRFT_BUDG_TYPE
© SAP AG
Page 22 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
3. Choose the Button
Table Contents
4. On the screen Data Browser: Table WRFT_BUDGET_TYPE: Selection Screen make the
following entries:
Field name
User values
APPL
02
TYPE
B1
5. Choose the Button
Execute
6. On the screen Data Browser: Table WRFT_BUDGET_TYPE: Select Entries make the
following entries:
Field name
User value
Flag the entry
7. Choose the Button
Choose
8. Write down or copy the TABNAME PLAN. It could be like /1WRF/01002AB1P.
3.14.2 Compare Corresponding Structure with Budget
DataStore Object
Procedure
1. Choose the Button
Create New Session to open a second session.
2. Access the activity using one of the following navigation options:
Transaction Code
SE11
SAP Menu
Tools  ABAP Workbench  Development  ABAP
Dictionary
3. Flag the entry
4. On the screen ABAP Dictionary: Initial Screen make the following entries:
Field name
User value
Database Table
The name of the Plan Table from the
previous chapter enlarged with “S”.
For example: /1WRF/01002AB1PS
© SAP AG
Page 23 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
5. Choose the Button
6. Choose the Button
Create New Session to open a third session
7. Access the activity using one of the following navigation options:
Transaction Code
SE11
SAP Menu
Tools  ABAP Workbench  Development  ABAP
Dictionary
8. On the screen ABAP Dictionary: Initial Screen make the following entries:
Field name
User value
Comment
Database Table
*OTBB1*
*Use F4 Help
A database table like /BIC/AOTBB100 is automatically found.
9. Choose the Button
10. Now compare the components of the structure /1WRF/01002AB1PS with the fields of the
budget DataStore Object /BIC/AOTBB100.
The best way to compare them is to compare the column Short Description. The field order
must be the same.
3.14.3 Delete 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, then delete the structure.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
SE11
SAP Menu
Tools  ABAP Workbench  Development  ABAP
Dictionary
© SAP AG
Page 24 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
2. Flag the entry
3. On the screen ABAP Dictionary: Initial Screen make the following entries:
Field name
User value
Database Table
The name of the Plan Table from the first
subchapter enlarged with “T”.
For example: /1WRF/01002AB1PT
4. Choose the Button
Delete
5. Choose the Button
Continue in the upcoming Information dialog box
6. Choose the Button Yes in the next screen
7. Flag the entry
8. On the screen ABAP Dictionary: Initial Screen make the following entries:
Field name
User value
Database Table
The name of the Plan Table from the first
subchapter enlarged with “S”.
For example: /1WRF/01002AB1PS
9. Choose the Button
Delete
10. Choose the Button Yes in the next screen
© SAP AG
Page 25 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
3.14.4
Reorganize 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
SPRO
IMG Menu
Material Management  Purchasing  Seasonal Procurement
 Open-To-Buy(OTB)  Budget Planning  Reorganize
Budget Types
2. On the screen Activate Budget Types make the following entries:
Field name
Description
User values
Budget Application
OTB (Open-To-Buy)
02
Budget Type
3. Choose the Button
B1
Note
Use F4
Execute to reorganize the budget.
A log will be displayed
4. Choose Button Enter
5. Choose the Button
© SAP AG
Back
Page 26 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
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 Create 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoSources.
3. Follow the application path SAP Application Components  SAP Sectors  Trade Industries
 Retailing  Merchandise and Assortment Planning.
4. Right-Mouse-Click on the component Merchandise and Assortment Planning.
© SAP AG
Page 27 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
5. Choose Create application component …
6. Enter the following data in the upcoming dialog box:
Field name
User values
Application comp.
ZRT_MAPN_TD
Long Description
MAP Transactional Data
7. Choose the Button
Continue.
4.2 Merchandise Planning
4.2.1 Create 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
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling screen choose InfoSources.
3. Follow the application path SAP Application Components  SAP Sectors  Retailling 
Merchandise and Assortment Planning  MAP Transactional Data.
4. Right-Mouse-Click on 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:
Field name
User values
InfoSource
RT_IS_0RMP_C05
Long description
InfoSource 0RMP_C05
7. Choose the Button
© SAP AG
Continue.
Page 28 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
8. Right-Mouse-Click on the InfoSource RT_IS_0RMP_C05.
9. Choose Change.
10. Choose the Button
11. Choose the Button
12. Flag
13. Enter as InfoCube 0RMP_C05.
14. Choose the Button
Transfer
15. Choose the Button
Transfer all InfoObjects
16. Choose the Button
Activate.
17. Choose YES in the upcoming dialog box.
18. Choose the Button
Back.
19. Choose the Button
Collapse to close the
20. Choose the Button
Expand to open the
21. Enter the following data:
Field name
User action and values
Source System
FILE by Choosing the Button
22. Choose YES in the upcoming screen Save Changes ?
The system will automatically propose the transfer rules.
23. Choose the Button
24. Choose the Button
Activate.
Back.
4.2.2 Assign Update Rules to InfoProviders
Use
This chapter describes the creation of Update Rules.
The steps described under Procedure must be executed concerning the InfoProviders:
© SAP AG
Page 29 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
InfoProvider
Description
0RMP_C05
Merchandise Planning, Plan
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling screen choose InfoProvider.
3. Choose the Button
Search and enter the following data:
Field name
User value
Find
0RMP_C05
4. Choose the Button
5. Right-Mouse-Click on the InfoProvider 0RMP_C05
6. Follow the context menu path Additional Functions  Create Update Rules.
7. Flag
on the screen Update rules create: Start
8. Enter as InfoSource RT_IS_0RMP_C05
9. Choose the Button
10. Choose the Button
11. Choose the Button
12. Choose the Button
Continue.
Activate on the screen Update rules create: Rules
Back.
to refresh the application component.
4.2.3 Execute Info packages for Real Time InfoProvider
Use
You must customize nfoProvider 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.
The steps described under Procedure must be executed for InfoProvider:
© SAP AG
Page 30 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
InfoProvider
Description
Flatfiles to Load
0RMP_C05
Merchandise Planning,
Plan is a Real Time
InfoCube
Flatfile_0RMP_C05_MCP_2010_BU_0001.csv
Flatfile_0RMP_C05_MCP_2010_BU_0002.csv
Flatfile_0RMP_C05_MCP_2011_0001.csv
Flatfile_0RMP_C05_MCP_2011_0002.csv
Flatfile_0RMP_C05_MCP_2011_oSeg.csv
Flatfile_0RMP_C05_MCP_2012_BU_0001.csv
Flatfile_0RMP_C05_MCP_2012_BU_0002.csv
Flatfile_0RMP_C05_MCP_2013_BU_0001.csv
Flatfile_0RMP_C05_MCP_2013_BU_0002.csv
Flatfile_0RMP_C05_MP1_2011.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.
Please check the Season code in the Files before loading the data. The Season code must ‘0001’
or ‘0002’. If the Season Code is ‘1’ or ‘2’ in the files please replace them to ‘0001’ or ‘0002’.
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\US\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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoProvider.
3. Choose the Button
Search.
4. Enter the following data in the upcoming screen:
Field name
User value
Find
0RMP_C05
5. Choose the Button
6. Right-Mouse-Click on 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.
© SAP AG
Page 31 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
9. Choose the Button
Continue.
Create InfoPackage to load the data:
1. Expand
2. Expand
3. Expand
4. Right-Mouse-Click on
5. Choose Create InfoPackage.
6. In the Create InfoPackage dialog box, enter the following data:
Field name
User value
InfoPackage Description
Flatfile Load: Transactional Data 0RMP_C05
7. Select the line for RT_IS_0RMP_C05 in the section DataSource.
8. Press the Button
9. for the InfoProviders 0RMP_C05 you may have the following screen
Monitor:Mesages appears.
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. Press the Button
11. Press the Button
to close the screen and continue with the next step.
Hide/Show Navigator
12. Choose the tab page External data and make the following entries:
Field
Values
Load external data from
 Client
workstation
File type
Name of file
© SAP AG
Notes
The flatfiles are csv files.
Use F4,
input help to
open the
See the comments in the prerequisites
paragraph of this chapter. Choose the first
flatfile
Page 32 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide


folder for
your flatfiles
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
Choose the tab page Processing and make the following entry:
Field
Value
PSA and then into Data Targets

Choose the tab page Data targets and set
Select the InfoProvider

Choose the tab page the Update tab page and make the following entries:
Field
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
13. Press the Button
14. Choose the Button
Save.
Hide/Show Navigator
15. Go to the External Data tab
16. Choose the first flatfile Flatfile_0RMP_C05_MCP_2010_BU_0001.csv.
© SAP AG
Page 33 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
It should already have been chosen from the previous chapter.
17. Go to the Schedule tab
18. Choose the Button
You get the status message Data was requested.
19. Choose the Button
Monitor in the board
20. Choose the Button
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.
21. Choose the Button
Back
22. Load the other flatfiles for the InfoProvider 0RMP_C05 the same way.
23. Choose the Button
Back
24. Right-Mouse-Click on 0RMP_C05
25. Choose Real-Time Info Cube Load Behavior.
26. Flag the entry Real-Time Data Target can be planned; data loading not allowed.
27. Choose the Button
Continue
Result
Check if there are data requests with a red traffic light by using a Right-Mouse-Click
on 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 Release 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
© SAP AG
UPAR
Page 34 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
2. Access the activity using one of the following navigation options:
Transaction Code
UPARI_BUDGA
SAP BI Menu
Merchandise Planning  Budget Monitor
3. On the Budget type tab enter the following data:
Field
Value
Comment
Application
01 PPW (Price Planning Workbench)
Use F4-Help
Budget Type
01
Use F4-Help
Created Date
Use F4-Help
InfoObjects of Budget type
Start Date
4. On the InfoObjects of Budget type tab enter the following data:
Field
Value
Comment
Segment
must not be filled
Fiscal year/period from
XXX.2011
Fiscal year/period to
001.2013
Season from
0001
Season to
0002
XXX is the current month
5. On the Additional Filter tab enter the following data:
Field
Value
Past
Current
Future
No difference
Difference with tolerance
Difference exceeds tolerance
Planned value not yet released
Version
6. Choose the Button
MCP
Execute
7. Choose the Button
to select all records
8. Choose the Button
Release budget
© SAP AG
Page 35 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
9. Choose the Button
Continue in the upcoming dialog box
10. Choose the Button
Display Current log
A log similar to the following one is displayed:
4.2.5 Release 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 tab page Budget type enter the following data:
Field
Values
Comment
Application
02 OTB (Open to Buy)
Use F4-Help
Budget Type
B1
Use F4-Help
InfoObjects of Budget type
3. On the tab page InfoObjects of Budget type enter the following data:
Field
Values
Segment
Optional, must not be filled
Fiscal year/period from
XXX.2011
© SAP AG
Note
XXX is the current month
Page 36 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Fiscal year/period to
012.2013
Season from
0001
Season to
0002
4. On the Additional Filter tab enter the following data:
Field
Values
Past
Current
Future
No difference
Difference with tolerance
Difference exceeds tolerance
Planned value not yet released
Version
5. Choose the Button
6. Choose the Button
7. Choose the Button
MCP
Execute
to select all records
Release budget
8. Choose the Button
Continue in the upcoming dialog box
9. Choose the Button
Display Current log to see the log.
© SAP AG
Page 37 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.2.6 Assign 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:
Transaction Code
WRF_PPW10
IMG Menu
Logistics  Retailing  Master Data  Price Planning 
Budgets  Authorization Administration for Budget Access 
Assign Price Planner Groups to Budget
2. Maintain the following entries:
Key fields of Budget Data
Values
Hierarchies node
Blank
Hierarchy
B1
Season
0001 and
0002
Price planner group
PPW1
Add Budgets without Price planner Group to the selection
flag
3. On the next screen you can maintain the tolerances.
4. Mark the whole screen.
5. Choose the Button 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.
© SAP AG
Page 38 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.3 Assortment Planning
4.3.1 Define 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:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoObjects
Follow the application path Industry Sectors  Trade Industries  Retailing  Merchandise and
Assortment Planning
3. Right-Mouse-Click on Assortment Planning
4. Choose Create InfoObject Catalog
5. Enter the following data:
Field name
User Values
InfObjCat
RT_AP_KEYF
Description
MAP Assortment Planning Key Figures
InfoObjext Type
6. Choose the Button
Create
7. Choose the Button
Activate
8. Right-Mouse-Click on the InfoObject Catalog MAP Assortment Planning Key Figures
9. Choose Create InfoObject
10. Enter the following data on the screen Create Key Figure:
Field name
User Values
KeyFig.
RT_GRNNPV
Long Description
Goods Receipt Cost Value, Net Net
© SAP AG
Page 39 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
11. Choose the Button
Continue
12. Enter the following data on the screen Create Key Figure RT_GRNNPV: Detail:
Field name
User Values
Short Description
GR CV/NN
13. Enter the following data on the tab page Type/unit:
Field name
User Values
Type/Data Type
Data Type
CURR – Currency field, stored as DEC
Unit / currency
0LOC_CURRCY
14. Enter the following data on the tab page Aggregation:
Field name
User Values
Aggregation
SUM
Exception Aggregat.
Summation
Cumulatative val
15. Enter the following data on the tab page Additional Properties:
Field name
User Values
Decimal Places
Not defined
Display
Not defined
Bex description
Short description
16. Choose the Button
Activate
17. 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
Page 40 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
18. In exact the same manner create the key figures with the key figure type Integer:
Long
Description
Short
Description
RT_NUMAT
Number of
Article
RT_NUMST
Number of
Stores
Key Figure
Type
Unit/Currency
Number of
Article
Integer
empty
Number of
Stores
Integer
empty
19. 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
20. 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 Maintain 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:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoObjects
3. Choose the Button
Search.
4. Enter the following data in the upcoming screen:
Field name
User value
Find
0RT_KEYFIG
© SAP AG
Page 41 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
5. Choose the Button
6. Right-Mouse-Click on the InfoObject 0RT_KEYFIG
7. Choose Maintain Master Data.
8. Enter the following data:
Field name
User value
Language
EN
9. Choose the Button
Execute
10. Choose the Button
Create
11. Enter the following data:
Field name
User values
Key Figure ID
IF
Short Description
Initial Fix
12. Choose the Button
Continue
13. Choose again the Button
Create
14. Enter the following data:
Field name
User values
Key Figure ID
IV
Short Description
Initial Variable
15. Choose the Button
Continue
16. Choose the Button
Save.
17. Choose the Button
Back.
For German localization you have to maintain the German descriptions.
18. Enter the following data:
Field name
User value
Language
DE
19. Maintain for every entry from above a German description.
20. Choose the Button
© SAP AG
Save.
Page 42 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.3.3 Create InfoProviders
4.3.3.1
Create 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoProvider.
Follow the application path Industry Sectors  Trade Industries  Retailing  Merchandise
and Assortment Planning
3. Right-Mouse-Click on the InfoArea
4. Choose Create InfoCube.
5. Enter the following data:
Field name
User Values
InfoCube
RT_C35
Description
Assortment Planning Plan, Month
InfoArea
0RT_MAPN_AP
Copy from
InfoProvider Type
Real Time
Flag
6. Choose the Button
Create
In the next window you create the following characteristics, time characteristics and key
performance indicators for the InfoProvider:
●
© SAP AG
Characteristics:
○
0CM_HIEID
Hierarchy ID
○
0CM_CDT1
Material group
○
0CM_CDT2
Hierarchy ID
○
0CM_CDT3
Segment
Page 43 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
●
●
○
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:
© SAP AG
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 %
o
RT_SPTAX
Target at Sales with TAX
Page 44 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
7. Open the folder Demension and Right-Mouse-Click on Dimension
8. Follow the menu path Properties.
9. Enter the following data in the upcoming screen:
You can do it by copy and paste.
Field name
User value
Description
Consumer Decision Tree
10. Choose the Button
Continue.
11. Right-Mouse-Click on
12. Follow the context menu path Create New Dimensions:
13. Enter the following data in the screen Create Dimensions:
You can do it by copy and paste.
Field name
User value
Description
Version
14. Choose the Button
Create Another Dimension
Enter the following data in the screen Create Dimensions:
Field name
User value
Description
Season
You can do it by copy and paste.
15. Choose the Button
Create Another Dimension
16. Enter the following data in the screen Create Dimensions:
You can do it by copy and paste.
Field name
User value
Description
Assortment
You can do it by copy and paste.
17. Choose the Button
Create Another Dimension
Enter the following data in the screen Create Dimensions:
Field name
User value
Description
Key Figure ID
You can do it by copy and paste.
18. Choose the Button
Continue.
19. Right-Mouse-Click on the dimension Time
20. Choose InfoObject Direct Input
© SAP AG
Page 45 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Insert the following characteristics into the dimension Time:
You can do it by copy and paste.
InfoObject
Description
0FISCPER
Fiscal Year/Period
0FISCPER3
Posting Period
0FISCVARNT
Fiscal Year Variant
0FISCYEAR
Fiscal Year
21. Choose the Button
Continue
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.
22. Insert the following characteristics into the dimension
Consumer Decision Tree. You can do it by copy and paste.
InfoObject
Description
0CM_HIEID
Hierarchy ID
0CM_CDT1
Category
0CM_CDT2
Subcategory
0CM_CDT3
Segment
0DISTR_CHAN
Distribution Channel
0SALESORG
Sales Organization
0CM_MCATDIV
Industry
23. Insert the following characteristics into the dimension Version.
You can do it by copy and paste.
InfoObject
Description
0VERSION
Version
24. Insert the following characteristics into the dimension Season.
You can do it by copy and paste.
InfoObject
Description
0RT_SEASON
Season Category
0RT_SKUROLL
Rollout
0RT_SEASYR
Season Year
25. Insert the following characteristics into the dimension Assortment.
You can do it by copy and paste.
© SAP AG
Page 46 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
InfoObject
Description
0RT_ASORT
Assortment
0RF_ASTYP
Assortment Type
26. Insert the following characteristics into the dimension Key Figure ID.
You can do it by copy and paste.
InfoObject
Description
0RT_KEYFIG
Key Figure ID
To assign key figures to the InfoProvider proceed as follows.
27. Right-Mouse-Click on
28. Choose InfoObject Direct Input
29. Insert the following key figure. You can do it by copy and paste.
InfoObject
Description
0CPBAINSABU
Sales / Base Unit of Measure
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 %
30. Choose the Button
© SAP AG
Continue.
Page 47 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
31. Choose the Button
Activate
4.3.4 Create InfoSources and Transfer Rules
4.3.4.1
Create 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoSources.
Follow the application path SAP Application Components  SAP Sectors  Trade Industries
 Retailing  Merchandise and Assortment Planning  MAP Transactional Data
3. Right-Mouse-Click on the Application Component MAP Transactional Data
4. Follow the context menu path Additional Functions  Create InfoSource 3.x
5. In the Create InfoSource dialog box enter the following data:
Field name
User values
InfoSource
RT_IS_RT_C35
Long description
InfoSource RT_C35
6. Choose the Button
Continue.
1. Right-Mouse-Click on the InfoSource RT_IS_RT_C35.
2. Choose Change.
3. Choose the Button
4. Choose the Button
5. Flag
and enter RT_C35.
6. Choose the Button
© SAP AG
on the right hand side
Transfer
Page 48 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
7. Choose the Button
8. Choose the Button
Transfer all InfoObjects
Activate.
9. Choose YES in the upcoming dialog box.
10. Choose the Button
Back.
11. Choose the Button
Collapse to close the
12. Choose the Button
Expand to open the
13. Enter the following data:
Field name
User action and values
Source System
FILE by Choosing the Button
25. Choose YES in the upcoming screen Save Changes ?
The system will automatically propose the transfer rules.
14. Choose the Button
Choose the Button
Activate.
Back.
4.3.5 Assign Update Rules to InfoProviders
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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling screen choose InfoProvider.
3. Choose the Button
© SAP AG
Search and enter the following data:
Page 49 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Field name
User value
Find
RT_C35
4. Choose the Button
5. Right-Mouse-Click on the InfoProvider RT_C35
6. Follow the context menu path Additional Functions  Create Update Rules.
7. Flag
on the screen Update rules create: Start and enter RT_IS_RT_C35
8. Choose the Button
Continue.
9. The next screen will show the update rule on the right hand side.
10. Choose the Button
11. Choose the Button
Activate on the screen Update rules create: Rules
Back.
4.3.6 Assign 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.
InfoProvider
Description
Flatfiles to Load
RT_C35
Assortment Planning
Plan, Month
Flatfile_RT_C35_Fashion_2011
Please check the Season code in the Files before loading the data. The Season code must ‘0001’
or ‘0002’. If the Season Code is ‘1’ or ‘2’ in the files please replace them to ‘0001’ or ‘0002’.
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\US\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
Page 50 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.3.6.1
Assign 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:
InfoProvider
Description
Flatfiles to Load
RT_C35
Assortment Planning
Plan, Month
Flatfile_RT_C35_Fashion_2011
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
Procedure
1. Access the activity using one of the following navigation options:
2. Transaction Code
3. RSA1
4. SAP BI Menu
5. Information Systems  Business Information
Warehouse Modeling  Data Warehousing
Workbench: Modeling
6. On the Data Warehousing Workbench: Modeling view choose InfoProvider.
7. Choose the Button
Search.
8. Enter the following data in the upcoming screen:
Field
name
User value
Find
RT_C35
9. Choose the Button
10. Right-Mouse-Click on RT_C35
11. Choose Change Real-Time Info Cube Load Behavior.
12. Flag the entry Real-Time Data Target can be loaded with data; planning not allowed.
13. Choose the Button
© SAP AG
Continue.
Page 51 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
14. Expand
15. Expand
16. Expand
17. Right-Mouse-Click on
18. Follow the menu path
19. Enter the following data:
Field name
User values
InfoPackage Description
Flatfile_RT_C35_Fashion_2011
20. Select the line for RT_IS_RT_C35 in the section DataSource.
21. Press the Button
22. Press the Button
Hide/Show Navigator
23. for the InfoProviders RT_C35 you may have the following screen
Monitor:Mesages appears.
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.
24. Choose the tab page External data and make the following entries:
Field
Values
Load external data from
 Client
workstation
File type
Name of file
© SAP AG
Notes
The flatfiles are csv files.
Use F4,
input help to
open the
folder for
See the comments in the
prerequisites paragraph of this
chapter. Choose the first flatfile
Flatfile_RT_C35_Fashion_2008.csv
Page 52 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
your flatfiles
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
25. Choose the tab page Processing and make the following entry:
Field
Value
PSA and then into Data Targets

26. Choose the tab page the Update tab page and make the following entries:
Field
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
27. Press the Button
Save.
28. Go to tab tab page Schedule.
29. Press the Button
You get the status message Data was requested.
In case of short dump UNCAUGHT_EXCEPTION that indicates missing info object
0REQUEST, please activate Business Content for Info Object 0REQUEST. You may refer to
the Building Block 762 Configuration Guide Section 8.3 for the process of the activation and
select Group Only Necessary Objects in step 5.
30. Press the Button
© SAP AG
Monitor in the board
Page 53 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
31. Press the Button
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.
32. Press the Button
Back
33. 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-Mouse-Click on 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
Page 54 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.3.7 LOG 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.
4.3.7.1
Transaction RRMX
Procedure
1. One possibility to access the Query Designer is using the following navigation:
Transaction Code
RRMX
SAP BI Menu
A menu entry for this activity is not available in the system.
Please access this activity through its transaction code.
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 the Button
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 the Button
4. Follow the menu path
5. Set the flag
6. Repeat step (1) and (2).
7. Choose the Button
Tools
8. Choose
© SAP AG
Page 55 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.3.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
 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.3.8 Create 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.
© SAP AG
Page 56 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Procedure
1. Choose the Button
2. Choose the Button
New Query in the board
Technical Name on/off in the board
3. Follow the path Industry SectorsTrade Industries  Retail  Merchandise and Assortment
Planning  Assortment Planning
4. Double-Click on the InfoProvider
4.3.8.1
Create Query RT_RTC35_Q0001
The following two steps explain how you Drag and Drop:
1. Expand for example, the Dimension Consumer
the
by clicking on
symbol in front of it. You see several characteristics, choose
2. Now click and hold down the Left-Mouse-Button on the
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
Description
0CM_HIEID
Hierarchy ID
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
0BASE_UOM
Base Unit
6. Insert via Drag and Drop into the frame Filters:
Field
Description
0VERSION
Version
© SAP AG
Page 57 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
0REQUID
Request ID
7. Insert via Drag and Drop into the frame Columns:
Field
Description
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-Mouse-Click on
in the frame Filters
9. Choose Restrict.
10. Select the tab
11. Right-Mouse-Click on
12. Choose Technical Names.
13. Choose the Button
Add
14. Choose the Button
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
Selection Option
Mandatory
16. Restrict in this way the InfoObject 0CM_HIEID in the frame Rows with the following variable:
Variable
Description
Variable Represents
Variable entry is
0CMHIEID
CDT Hierarchy ID
Single Value
Mandatory
17. Restrict in this way the InfoObject Category in the frame Rows with the following variable:
Variable
Description
Variable Represents
Variable entry is
0S_CATG
Category List
Multiple Single Value
Optional
© SAP AG
Page 58 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
18. Restrict in this way the InfoObject Subcategory in the frame Rows with the following variable:
Variable
Description
Variable Represents
Variable entry is
0S_SCAT
Subcategory List
Multiple Single Value
Optional
19. Restrict in this way the InfoObject Segment in the frame Rows with the following variable:
Variable
Description
Variable Represents
Variable entry is
0P_SEGM
Category
Management:
Segment
Multiple Single Value
Optional
20. Restrict in this way the InfoObject Season in the frame Rows with the following variable:
Variable
Description
Variable Represents
Variable entry is
0P_SEASO
Required Entry Field:
Single Value for
Season Category
Single Value
Mandatory
21. Restrict in this way the InfoObject Season Year in the frame Rows with the following variable:
Variable
Description
Variable Represents
Variable entry is
0P_SEAY1
Season Year
Single Value
Mandatory
22. Restrict in this way the InfoObject Assortment in the frame Rows with the following variable:
Variable
Description
Variable Represents
Variable entry is
0S_ASRT
Assortment
Selection Option
Optional
23. Restrict in this way the InfoObject Base Unit in the frame Rows with the following variable:
Variable
Description
Variable Represents
Variable entry is
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:
Variable
Description
Variable Represents
Variable entry is
RT_PER
Posting Period
Selection Option
Optional
© SAP AG
Page 59 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
25. Execute the following steps to create the variable RT_PER for Posting Period.
26. Right-Mouse-Click on
and choose restrict
27. Go to the tab page Variables
28. Right-Mouse-Click on
29. Choose New Variable
30. Should the following screen appear, flag the message Do not display this step in the future
31. Enter the following data :
32. Choose the Button
33. Change the default values as shown in the screen shot.
© SAP AG
Page 60 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
34. Choose the Button
35. Choose the Button
36. Choose the Button
37. Mark the just created variable.
38. Choose the Button
Add
39. Choose the Button
40. 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
41. The Filter and Column frame of the query should be now as shown in the screen shot.
© SAP AG
Page 61 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
42. 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.
43. Choose the Button
Save Query as
44. Enter the following data:
Field Name
Value
Description
Key Figures Assortment Planning
Technical Name
RT_RTC35_Q0001
45. Choose the Button
© SAP AG
Page 62 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.3.9 Define 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
Define 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.
4.3.9.2
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
UPARI_MSGTYPE
SAP BI Menu
SAP Business Information Warehouse  Business Planning
and Simulation  Planning Content  Retail Analytics 
Release Workbench  Settings  Define message types
2. Enter the following data for message type ASRTPLN:
Field name
User value
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 the Button
4.3.9.3
Save.
Define Selection Options
Use
Because the rollout should be mapped to the fiscal period you must replace the entry in the
Selection Options.
© SAP AG
Page 63 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.3.9.4
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
UPARI_SELOP
SAP BI Menu
SAP Business Information Warehouse  Business Planning
and Simulation  Planning Content  Retail Analytics 
Release Workbench  Settings  Define Selection Options
2. Scroll down to the following entry:
3. Replace the value 0RT_SKUROLL in the column InfoObject/Field Data by 0FISCPER3 for
the entry S49_SERO. Message type is ASRTPLN.
Field name
Value
User value
Info Object/Field
0RT_SKUROLL
0FISCPER3
4. Choose the Button
4.3.10
Save.
BADI UPARI_ASRTPLN
Please 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.
5. Access the activity using one of the following navigation options:
Transaction Code
SE19
SAP BI Menu
SAP Menu  Tools  ABAP Workbencht  Utilities 
Business Add-Ins  Implementations
© SAP AG
Page 64 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
© SAP AG
Page 65 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Please 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 in query) has to
* be filled
data:
l_langu
lv_report_id
ls_appl_message
ls_bw_varsel
lt_bw_query
lt_bw_varsel
lt_return
lv_ofiscper3(3)
field-symbols:
<lfs_return>
<lfs_selopt>
type
type
type
type
type
type
type
type
sy-langu,
rscrmstatus-reportuid value 'RT_C35/RT_RTC35_Q0001',
upari_ys_appl_msg,
upari_ys_rscrmvarp,
upari_yt_wrex_query,
upari_yt_rscrmvarp,
table of bapiret2,
n.
type bapiret2,
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
© SAP AG
Page 66 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
*
*
*
*
*
*
*
*
*
#
#
#
#
#
?
?
#
#
0CM_HIEID
0CM_CDT3
0RT_ASORT
0RT_SEASON
0RT_SEASYR
0FISCPER3
RT_EQUIPB
0BASE_UOM
0LOC_CURRCY
* Key Figures
* # RT_NUMAT
* # RT_NUMST
* ? RT_SQUBST
* ? RT_GRNNPV
* ? 0CPGRPDVPV
* ? 0RTGRPDVST
* ? 0RTGRPDVSV
*
*
*
*
*
*
*
*
*
Hierarchy ID
Segment
Assortment
Season Category
Season Year
Posting period
Basic Equipment OAPC
Base Unit of Measure
Local currency
Number of Article
Number of Stores
Sales Quantity by Store
Goods Receipt Cost Value, Net Net
Goods Receipt Posting Date / Vendor Cost Value
GR Posting Date / Vendor RtlT
Goods Receipt Posting Date/Vendor Retail Value
Selection criteria in release
Hierarchy Id
Article Hierarchy Node
Assortment type
Season Year
Season Category
Posting Period
Assortment
Key Figure ID
workbench UPARI_REL
0CM_HIEID
--> 0CMHIEID
0CM_CDTND
--> 0P_SEGM
0RF_ASTYP
--> RT_ATYP
0RT_SEASYR --> 0P_SEAY1
0RT_SEASON --> 0P_SEASO
OFISCPER3
--> RT_PER
0RT_ASORT
--> 0S_ASRT
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'.
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
ls_bw_varsel-varsign
© SAP AG
= '0P_ASSP'.
= 'I'.
Page 67 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
ls_bw_varsel-varoption
ls_bw_varsel-varlow
ls_bw_varsel-varhigh
append ls_bw_varsel to
= 'EQ'.
= 'ASP'.
= ''.
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.
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
ls_asrtpln_content
lv_rollout(2)
type i,
type upari_ys_asrtpln_msg,
type n.
field-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?
* Characteristics
© SAP AG
(see for reference structure /BIC/VRT_C312)
Page 68 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
* # 0RT_KEYFIG
* # 0FISCPER3
* ? 0CM_CDT1
* ? 0CM_CDT2
* # 0CM_CDT3
* # 0RT_ASORT
* Key Figures
* # RT_GRNNPV
* # 0CPGRPDVPV
* # 0RTGRPDVST
* # 0RTGRPDVSV
* ? RT_QUAN
* # RT_NUMAT
* # RT_NUMST
Kennzahl ID
Posting period
Category
Subcategory
Segment
Assortment
Goods
Goods
Goods
Goods
Receipt
Receipt
Receipt
Receipt
Cost Value, Net Net
Posting Date / Vendor Cost Value
Posting Date / Vendor Retail Tax(?)
Posting Date / Vendor Retail Value
Number of Article
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
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.
© SAP AG
Page 69 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
*
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
ls_asrtpln_content-target_sales_cost_net-currency_code
ls_asrtpln_content-target_sales_retail-currency_code
ls_asrtpln_content-target_sales_retail_tax-currency_code
=
=
=
=
<lfs_asrtpln>-value.
<lfs_asrtpln>-value.
<lfs_asrtpln>-value.
<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.
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.
Please check if BADI is active, otherwise activate it by pressing
4.3.11
.
Release 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).
© SAP AG
Page 70 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Procedure
1. Access the transaction choosing one of the following navigation options
Transaction code
UPARI_REL
SAP Menu
SAP Menu  Business Planning and Simulation  Planning Content
 Retail Analytics  Release Workbench  Start Release
Workbench
Business role
Retail Markdown Planner
2. Set the flag Assortment Plan in the subscreen Message Types. A new Assortment Plan tab
with status red appears.
3. Set the flag “Release Related Messages” in the subscreen Message Types.
4. Enter the following on the tab page General Data in the subscreen General Selection Criteria:
Field name
User value
Hierarchy ID
B1
Article Hierarchy Node
B11120
Assortment Type
FASH
5. Press the ENTER key. The status of the tab page General Data changes to green.
6. Go to the Assortment Plan tab. The data from the subscreen General Selection Criteria are
taken over.
7. Enter the following data in the subscreen Assortment Plan Specific Selection Criteria:
Field
Value from
Value to
Comment
Season Year
2011
Season Category
0002
Posting Period
08
Assortment
B11100_11
B11100_22
B11100_22
Key figure ID
IF
IV
IV
This is the period you
planned with in the
Assortment Planning
scenario.
8. Press the ENTER Key. The status of the tab Assortment Plan switches to green.
9. Choose the Release Messages Immediately button.
After some time you get the information Release run started. You can find the results in the
application log.
10. Choose the
Continue button.
11. Choose the
Application Log button.
© SAP AG
Page 71 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
12. Choose the
Execute button.
If your transfers were successful you will get a log with status green. With a double click on
your log you will see the number of successfully created objects and errors/warnings.
13. Choose the
Exit button.
14. Choose the
Exit button.
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
Create 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:
Transaction
WRFAPC01
SAP ECC Menu
Logistics  Retailing  Master Data  Assortment/Listing
 Operational Assortment Planning and Control  Create
Purchasing List
Business role
Retail Seasonal Purchaser
3. Enter the following data on the subscreen Assortment.
Field name
User values
Hierarchy
B1
Hierarchy Node
B11120
Assortment Type
FASH
...
4. Enter the following data on the subscreen Season.
Field name
User values
Season year
2011
Season Category
0002
© SAP AG
Page 72 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Rollout
08
5. Press the ENTER Key.
6. Enter the following data in the next screen:
Field name
User values
Purchasing Org.
1000
Purch. Group
101
Sales Org.
1000
Distr. Channel
10
1. Choose
Enter.
2. Choose the Target Values tab.
3. Choose
in the middle of the screen to close the Overview Area.
4. You see in the first subscreen 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
5. You see in the second subscreen Target Value Description the following key figures for each
assortment:

Number of stores in assortment

Number of different articles

Target Totals in Units
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.
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.
4.3.13
© SAP AG
OTB Check: Maintain Document-Type Dependent
Page 73 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
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.
2. Access the activity using one of the following navigation options:
Transaction Code
SPRO
IMG Menu
Material Management  Purchasing  Seasonal Procurement
 Open-To-Buy(OTB)  OTB Check: Maintain DocumentType Dependent Settings
3. Choose
to define the "OTB Check Settings"
4. Choose the document Category from the list: Purchase Order.
5. On the screen "New Entries: Detail of Added Entries" make the following entries:
first line:
Field name
User action and values
Note
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
7. Choose
8. Choose
Description
to save the entries.
or F3 on the keyboard.
to define the second line.
9. Choose the document Category from the list: Contract and make the following entries:
© SAP AG
Page 74 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Field name
Description
Document
Type
10. Choose
User action and values
Note
MK
Choose from list
to save the entries
11. Choose
or F3 on the keyboard
12. Choose
to define the third line.
13. Choose the document Category from the list: Contract and make the following entries:
Field name
Description
Document
Type
14. Choose
15. Choose
User action and values
Note
WK
Choose from list
to save the entries
or F3 on the keyboard
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
© SAP AG
Page 75 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
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.
Procedure
1.
Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling screen choose InfoProvider.
4.4.1 Generate Export DataSources
Procedure
1. Choose the Button
Search and enter the following data:
Field name
User value
Find
0RMP_DS01
2. Choose the Button
3. Right-Mouse-Click on
4. Follow the context menu path Additional Functions  Generate Export DataSource
5. Search for 0RMP_DS02, as described before.
6. Right-Mouse-Click on
7. Follow the context menu path Additional Functions  Generate Export DataSource
© SAP AG
Page 76 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
© SAP AG
Page 77 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.4.2 Install Interface “Goods Receipt Date”
4.4.2.1
Create 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 view choose InfoSources.
2. Follow the application path SAP Application Components  SAP Sectors Trade
Industries Retailing  Merchandise and Assortment Planning  MAP Transactional Data
3. Right-Mouse-Click on the Application Component MAP Transactional Data
4. Follow the context menu path Additional Functions  Create InfoSource 3.x
5. In the Create InfoSource dialog box enter the following data:
Field name
User values
InfoSource
RT_FIRST_GR
Long description
Change of the first GR Date to actual
minus 23 Days
6. Choose the Button
Continue.
7. Right-Mouse-Click on the InfoSource RT_FIRST_GR.
8. Choose Change.
9. Enter the following InfoObject in the Communication Structure frame:
InfoObject
Description
0MATERIAL
Article
0PLANT
Store
0RT_SSMFGR
Date of First GR
10. Choose the ENTER key.
11. Choose the Button
Activate.
12. Choose YES in the upcoming dialog box.
13. Choose the Button
© SAP AG
Back.
Page 78 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
14. Choose the Button
Collapse to close the
15. Choose the Button
Expand to open the
16. Enter the following data:
Field name
User action and values
Source System
FILE by Chooseing the Button
26. Choose YES in the upcoming screen Save Changes ?
The system will automatically propose the transfer rules.
27. Double-Click on
in the row for InfoObject 0RT_SSMFGR
28. Flag
29. Choose the Button
30. Enter the following data:
Field name
User value
Transfer Routine
Goods Receipt Date
31. Flag
32. Choose the Button
Continue.
33. Browse down until you see the coding line RESULT = .
34. Replace this line by RESULT = sy-datum - 23.
35. Choose the Button
36. Choose the Button
Check.
Save if there are no syntax errors
37. Choose the Button
Continue.
17. Choose the Button
Activate.
18. Choose the Button
© SAP AG
Back.
Page 79 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.4.2.2
Assign Update Rules to InfoObject
Use
In this chapter the creation of a new update rule for InfoObject 0MAT_PLANT is described.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling screen choose InfoProvider.
3. Choose the Button
Search and enter the following data:
Field name
User value
Find
0MAT_PLANT
4. Choose the Button
5. Expand
6. Right-Mouse-Click on
7. Follow the context menu path Additional Functions  Create Update Rules.
8. Flag
on the screen Update rules create: Start and enter RT_FIRST_GR
9. Choose the Button
Continue in the up coming screen.
The following screen will show the update rule on the right hand side.
10. Double-Click on a key figure, for example
11. Choose the tap page Key Fields
12. Choose
in the row for Store Article
13. Flag
14. Choose 0MATERIAL by using the F4 Help
15. Choose the Button
Transfer
16. Choose the Buttom YES in the upcoming screen
© SAP AG
Page 80 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
17. Choose the Button
18. Choose the Button
19. Choose the Button
4.4.2.3
Transfer
Activate on the screen Update rules create: Rules
Back.
Assign 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
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\US\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 the flatfiles for Merchandise Planning. They are stored in the csv folder
within the folder SSM.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoSources.
© SAP AG
Page 81 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
3. Choose the Button
Search.
4. Enter the following data in the upcoming screen:
Field name
User value
Find
RT_FIRST_GR
5. Open the folder
6. Open the folder
7. Right-Mouse-Click on
8. Follow the menu path Create InfoPackage
9. Enter the following data:
Field name
User value
InfoPackage Description
Flatfile Load: RT_FIRST_GR
10. Select the line for RT_FIRST_GR in the section DataSource.
11. Choose the Button
12. Choose the Button
Hide/Show Navigator
13. Choose the External data tab and make the following entries:
Field
Values
Load external data from
 Client
workstation
File type
Notes
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_MATPLANT_GR_DAT
_Fashion.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
© SAP AG
Page 82 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Field
Values
Notes
!
Character used for Decimal
Point
.
See remark for Data Seperator
!
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
Value
PSA and then into Data Targets

15. Choose the Data targets tab and set
16. Select the InfoProvider
17. Choose the Update tab and make the following entries:
Field
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
18. Choose the Button
Save.
4.4.3 Load 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
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\US\Flatfiles. They must be
installed on your hard disk or any of your file server. An installation in this way is important
© SAP AG
Page 83 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
because you have defined in the InfoPackage that an external load takes place from a client
workstation.
In this chapter you load the flatfiles for Merchandise Planning. They are stored in the csv folder
within the folder SSM.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoSources.
3. Choose the Button
Search.
4. Enter the following data in the upcoming screen:
Field name
User value
Find
RT_FIRST_GR
5. Expand
6. Expand
7. Expand
8. Double-Click on
9. Choose the Button
Hide/Show Navigator
10. Go to the External Data tab
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.
13. Choose the Button
You get the status message Data was requested.
14. Choose the Button
© SAP AG
Monitor in the board
Page 84 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
15. Choose the Button
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.
16. Choose the Button
Back
17. In this way load the other flatfile for the InfoObject 0MAT_PLANT.
18. Choose the Button
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.
Prerequisites
Check the computer’s regional language setting. It must be English (United States).
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.
In this chapter you load the flatfiles for Merchandise Planning. They are stored in the csv folder
within the folder SSM.
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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. Move to the
© SAP AG
area in the modeling navigation in the left hand frame.
Page 85 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
3. Choose the Button
Choose Source System
4. Follow the path
5. Choose the application path SAP Application Components  SAP Sectors  Trade
Industries  Retailing
6. Right-Mouse-Click on the application component Retailing
7. Choose
8. Enter the following data in the dialog box Create Application Components:
Field name
User value
Application Comp.
ZRT_SSM
Long Description
Transactional Data SSM
9. Select the Button
4.4.4.2
Continue to create the application component.
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
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. Move to the
area in the modeling navigation in the left hand frame.
10. Choose application path SAP Application Component  SAP Sectors  Trade Industries 
Retailing
3. Right-Mouse-Click on the application component Transactional Data SSM.
4. Choose
5. Enter the following data in the dialog box Create DataSource:
© SAP AG
Page 86 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Field name
User value
DataSource
RT_DS_0RMP_DS02
Source System
FILE
Data Type DataSource
Transaction Data
Notes
automatically filled
6. Select the Button
Transfer
7. Select the Button
Hide/Show Navigator.
8. Enter the following data on the tap page General Info:
Field name
User value
Short description
POS Data SSM
Medium description
POS Data SSM
Long description
POS Data SSM
9. Enter the following data on the tap page Extraction :
Field name
User value
Delta Process
Direct Access
Real Time
Adapter
Name of File
Flatfile_0RMP_DS02_POS_Fashion.csv
Header Rows to be ignored
2
Character Set Settings
Default Settings
Data Format
Data Seperator
,
Escape Sign
“
Convers. Language
User Master Record
Number Format
User Master Record
10. Enter the following data on the tap page Proposal:
Field name
User value
No. of Data Record
3
11. Choose the Button
12. Go to to the Fields tab
13. Flag the message Do not Show This Question Again in This Session and choose the Button
Yes in the upcoming screen
© SAP AG
Page 87 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
14. Enter in the column InfoTemplate the values you find in the following table
by copy&paste :
Pos
Fields
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
15. Choose the ENTER Key
16. Replace RPA_BDD by BUSINESSDAYDATE
17. Choose the ENTER Key
18. Choose the Button
Template is empty
Next Page and Click on
to get a view in which the column Info
19. Enter in the column InfoTemplate the values you find in the following table
by copy&paste :
Pos
Fields
InfoTemplate
15
TRANSACTIONINDEX
0RPA_TIX
16
TRANSTYPEGROUP
0RPA_TRG
© SAP AG
Page 88 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Pos
Fields
InfoTemplate
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
20. Choose the ENTER Key
21. Choose the Button
Template is empty
Next Page and Click on
to get a view in which the column Info
22. Enter in the column InfoTemplate the values you find in the following table
by copy&paste :
Pos
Fields
InfoTemplate
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
23. Choose the ENTER Key
© SAP AG
Page 89 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
24. Choose the Button
Template is empty
Next Page and Click on
to get a view in which the column Info
25. Enter in the column InfoTemplate the values you find in the following table
by copy&paste :
Pos
Fields
InfoTemplate
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
26. Choose the ENTER Key
27. Choose the Button
Template is empty
Next Page and Click on
to get a view in which the column Info
28. Enter in the column InfoTemplate the values you find in the following table
by copy&paste :
Pos
Fields
InfoTemplate
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
© SAP AG
Page 90 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Pos
Fields
InfoTemplate
68
RPA_ADT2
0RPA_ADT2
69
RPA_MID
0RPA_MID
70
RPA_ACD
0RPA_ACD
29. Choose the ENTER Key
30. Choose the Button
Template is empty
Next Page and Click on
to get a view in which the column Info
31. Enter in the column InfoTemplate the values you find in the following table
by copy&paste :
Pos
Fields
InfoTemplate
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
32. Choose the ENTER Key
33. Choose the Button
Template is empty
Next Page and Click on
to get a view in which the column Info
34. Enter in the column InfoTemplate the values you find in the following table
by copy&paste :
Pos
Fields
InfoTemplate
85
RPA_RQU
0RPA_RQU
86
RPA_OQU
0RPA_OQU
87
RPA_RDF
0RPA_RDF
88
RPA_DDI
0RPA_DDI
© SAP AG
Page 91 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Pos
Fields
InfoTemplate
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
35. Choose the ENTER Key
36. Choose the Button
Template is empty
Next Page and Click on
to get a view in which the column Info
37. Enter in the column InfoTemplate the values you find in the following table
by copy&paste :
Pos
Fields
InfoTemplate
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
106
RPA_PA1
0RPA_PA1
107
RPA_PA2
0RPA_PA2
108
RPA_ITI
0RPA_ITI
109
RPA_IT0
0RPA_IT0
110
RPA_IT2
0RPA_IT2
111
RPA_IT3
0RPA_IT3
112
RPA_IT4
0RPA_IT4
38. Choose the ENTER Key
39. Choose the Button
© SAP AG
Next Page
Page 92 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
40. Enter in the column InfoTemplate the values you find in the following table
by copy&paste :
Pos
Fields
InfoTemplate
113
RPA_IT5
0RPA_IT5
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
41. Choose the ENTER Key
42. Choose the Button
Activate
43. Ignore the yellow warnings and choose the Button
Continue
44. Choose the Button
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.
ODS Object
Description
Flatfiles to Load
0RMP_DS01
Stock Consolidation
Flatfile_0RMP_DS01_GR_Fashion.csv
Flatfile_0RMP_DS01_GR_Hardgoods.csv
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. Move to the
© SAP AG
area in the modeling navigation in the left hand frame.
Page 93 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
3. Choose application path SAP Application Component  SAP Sectors  Trade Industries 
Retailing
4. Right-Mouse-Click on the application component Transactional Data SSM.
5. Choose
6. Enter the following data in the dialog box Create DataSource:
Field name
User value
DataSource
RT_DS_0RMP_DS01
Source System
FILE
Data Type DataSource
Transaction Data
Notes
automatically filled
7. Select the Button
Transfer
8. Select the Button
Hide/Show Navigator.
9. Enter the following data on the tap page General Info:
Field name
User value
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 :
Field name
User value
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
“
Convers. Language
User Master Record
Number Format
User Master Record
45. Enter the following data on the tap page Proposal:
© SAP AG
Page 94 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Field name
User value
No. of Data Record
3
11. Choose the Button
12. Change to the tab page Fields:
13. Enter in the column Fields and InfoTemplate the values you find in the following table
by copy&paste and overwriting existing values in the column Field:
Pos
Fields
InfoTemplate
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
14. Choose the ENTER Key
15. Choose the Button
Template is empty
Next Page and Click on
to get a view in which the column Info
16. Enter in the column Fields and InfoTemplate the values you find in the following table
by copy&paste and overwriting existing values in the column Field:
Pos
Fields
InfoTemplate
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
Page 95 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Pos
Fields
InfoTemplate
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
17. Choose the ENTER Key
18. Choose the Button
Next Page and Click on
column Info Template is empty
so often until you get a view in which the
19. Choose the Button
Insert Row so often until you get a view in which only lines exist that
can be filled with data
20. Enter in the column Fields and InfoTemplate the values you find in the following table
by copy&paste and overwriting existing values in the column Field:
Pos
Fields
InfoTemplate
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
21. Choose the ENTER Key
22. Choose the Button
Insert Row 14 times
23. Choose the Button
Template is empty
Next Page and Click on
© SAP AG
to get a view in which the column Info
Page 96 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
24. Enter in the column InfoTemplate the values you find in the following table
by copy&paste :
Pos
Fields
InfoTemplate
43
MOVE_PLANT
0MOVE_PLANT
44
RECORDMODE
0RECORDMODE
45
RT_RMAPIDA
0RT_RMAPIDA
46
BWCOUNTER
0BWCOUNTER
47
INDSPECSTK
0INDSPECSTK
48
GN_R3_SSY
0GN_R3_SSY
If you have an error when adding the InfoObject 0RT_RMAPIDA Please install first this InfoObject
from the BI Content
25. Choose the ENTER Key
26. Choose the Button
Activate
27. Ignore the yellow warnings and choose the Button
Continue
28. Choose the Button
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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. Move to the
area in the modeling navigation in the left hand frame.
3. Choose application path SAP Application Component  SAP Sectors  Trade Industries 
Retailing  Transactional Data SSM
4. Right-Mouse-Click on the DataSource POS Data SSM
5. Choose
6. In the Create InfoPackage dialog box, enter the following data:
© SAP AG
Page 97 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Field name
User value
InfoPackage Description
Flatfile Load: Transactional Data 0RMP_DS02
7. Select the line for
in the section DataSource.
8. Choose the Button
9. Select the Button
Hide/Show Navigator.
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 the Button
14. Go back to the tab page Extraction
15. Select the other flatfile
16. Go to the tab page Schedule
17. Choose the Button
18. Choose the Button
Back.
19. Right-Mouse-Click on DataSource
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 the Button
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.
Procedure
© SAP AG
Page 98 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling screen choose InfoProvider.
4.4.4.6
Creating Transformation for ODS Objects
0RMP_DS02
Procedure
1. Choose the Button
Search and enter the following data:
Field name
User value
Find
0RMP_DS02
2. Choose the Button
3. Expand
4. Expand
5. Right- Mouse-Click on
11. Choose
12. Enter the following data in the subscreen Target of the Transformation:
Field name
User value
Object Type
Name
0RT_PA_TRAN_CONTROL_TR
13. Enter the following data in the subscreen Source of the Transformation:
Field name
User value
Object Type
DataSource
DataSource
RT_DS_0RMP_DS02
Source System
FILE
14. Select the Button
Create Transformation
15. Choose the Button
Save
16. Select the Button
Hide/Show Navigator.
© SAP AG
Page 99 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Maintain Start Routine
17. Choose the Button
18. 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.
19. Choose the Button
20. Choose the Button
Check to be sure that there are no syntax errors
Save
Maintain Routine for INFOOBJECT 0FISCPER
21. Double-Click on
22. Choose the Button
Add Source Fields in the sub screen Source Fields of Rule
23. Select the field BUSINESSDAYDATE
24. Choose the Button
Copy
25. Select in the line Rule Type the rule type Routine
26. Replace the coding template by
*$*$ 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_FIELDS-BUSINESSDAYDATE
IMPORTING
e_fper1
= RESULT
CHANGING
ct_monitor = MONITOR.
CATCH /rtf/cx_time.
RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
ENDTRY.
27. Choose the Button
28. Choose the Button
*-*
Check to be sure that there are no syntax errors
Save
29. Enter as description Routine: Fiscal Year/Period from BUSINESSDAYDATE
30. Choose the Button
© SAP AG
in the upcoming screen
Page 100 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Maintain Routine for INFOOBJECT 0FISCVARNT
31. Double-Click on
32. Choose the Button
Add Source Fields in the sub screen Source Fields of Rule
33. Select the field BUSINESSDAYDATE
34. Choose the Button
Copy
35. Select in the line Rule Type the rule type Routine
36. Replace the coding template by
*$*$ 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_FIELDS-BUSINESSDAYDATE
IMPORTING
e_fiscyv1 = RESULT
CHANGING
ct_monitor = MONITOR.
CATCH /rtf/cx_time.
RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
ENDTRY.
37. Choose the Button
38. Choose the Button
*-*
Check to be sure that there are no syntax errors
Save
39. Enter as description Routine: Fiscal Year Variant from BUSINESSDAYDATE
40. Choose the Button
Maintain Routine for INFOOBJECT 0FISCPER3
41. Double-Click on
42. Choose the Button
Add Source Fields in the sub screen Source Fields of Rule
43. Select the field BUSINESSDAYDATE
44. Choose the Button
Copy
45. Select in the line Rule Type the rule type Time Characteristic
46. Enter as description Routine: Posting Period from Start Routine
47. Choose the Button
© SAP AG
Page 101 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
© SAP AG
Page 102 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Maintain Routine for INFOOBJECT 0FISCYEAR
48. Double-Click on
49. Select the field BUSINESSDAYDATE
50. Choose the Button
Copy
51. Select in the line Rule Type the rule type Time Characteristic
52. Enter as description Routine: Fiscal Year from Start Routine
53. Choose the Button
Maintain Routine for INFOOBJECT 0RT_MTFYVRN
54. Double-Click on
55. Choose the Button
Add Source Fields in the sub screen Source Fields of Rule
56. Select the field BUSINESSDAYDATE
57. Choose the Button
Copy
58. Select in the line Rule Type the rule type Routine
59. Replace the coding template by
*$*$ 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_FIELDS-BUSINESSDAYDATE
IMPORTING
e_fiscyv2 = RESULT
CHANGING
ct_monitor = MONITOR.
CATCH /rtf/cx_time.
RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
ENDTRY.
60. Choose the Button
61. Choose the Button
*-*
Check to be sure that there are no syntax errors
Save
62. Enter as description Routine MAP: Approximate Fiscal Year Variant from BDD
63. Choose the Button
© SAP AG
Page 103 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Maintain Routine for INFOOBJECT 0RT_QTFYVRN
64. Double-Click on
65. Choose the Button
Add Source Fields in the sub screen Source Fields of Rule
66. Select the field BUSINESSDAYDATE
67. Choose the Button
Copy
68. Select in the line Rule Type the rule type Routine
69. Replace the coding template by
*$*$ 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_FIELDS-BUSINESSDAYDATE
IMPORTING
e_fiscyv3 = RESULT
CHANGING
ct_monitor = MONITOR.
CATCH /rtf/cx_time.
RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
ENDTRY.
70. Choose the Button
71. Choose the Button
*-*
Check to be sure that there are no syntax errors
Save
72. Enter as description Routine: Approximate Fiscal Year Variant from BDD
73. Choose the Button
© SAP AG
Page 104 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Maintain Routine for INFOOBJECT 0RT_MTFPER
74. Double-Click on
75. Choose the Button
Add Source Fields in the sub screen Source Fields of Rule
76. Select the field BUSINESSDAYDATE
77. Choose the Button
Copy
78. Select in the line Rule Type the rule type Routine
79. Replace the coding template by
*$*$ 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_FIELDS-BUSINESSDAYDATE
IMPORTING
e_fper2
= RESULT
CHANGING
ct_monitor = MONITOR.
CATCH /rtf/cx_time.
RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD.
ENDTRY.
80. Choose the Button
81. Choose the Button
*-*
Check to be sure that there are no syntax errors
Save
82. Enter as description Routine: Approximate Fiscal Year Period from BDD
83. Choose the Button
84. Choose the Button
Activate
85. Choose the Button
Back.
4.4.4.7
Creating Transformation for ODS Objects
0RMP_DS01
Procedure
1. Choose the Button
Search and enter the following data:
Field name
User value
Find
0RMP_DS01
© SAP AG
Page 105 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
2. Choose the Button
3. Expand
4. Expand
5. Right- Mouse-Click on
86. Choose
87. Enter the following data in the subscreen Target of the Transformation:
Field name
User value
Object Type
Name
2LIS_03_BF_TR
88. Enter the following data in the subscreen Source of the Transformation:
Field name
User value
Object Type
DataSource
DataSource
RT_DS_0RMP_DS01
Source System
FILE
89. Select the Button
Create Transformation
90. Choose the Button
Save
91. Select the Button
Hide/Show Navigator.
Maintain Start Routine
92. Choose the Button
93. 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-DOC_DATE = sy-datum - 21.
wa_SOURCE_PACKAGE-PSTNG_DATE = sy-datum - 21.
modify SOURCE_PACKAGE from wa_SOURCE_PACKAGE.
ENDLOOP.
94. Choose the Button
95. Choose the Button
© SAP AG
Check to be sure that there are no syntax errors
Save
Page 106 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
96. Choose the Button
Activate
97. Choose the Button
Back
4.4.5 Loading POS and Stock Data into ODS Objects
4.4.5.1.1 Creating Data Transfer Process for ODS Objects
0RMP_DS02
Procedure
1. Right-Mouse-Click on
2. Choose
3. Execute the F4 Help of the field DataSource
4. Choose the DataSource RT_DS_0RMP_DS02 as shown in the following screenshot:
5. Choose the Button
Continue
6. Enter the following data on the tab page Extraction:
Field name
User value
Extraction Mode
Full
7. Go to the tab page Execute
8. Choose the Button
Activate
9. Choose the Button
10. Choose the Button Yes in the upcoming screen if you want to enter the monitor, otherwise
No.
© SAP AG
Page 107 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
11. Choose the Button
Refresh to see that there is a green data transfer process.
12. Choose the Button
Back
13. Right-Mouse-Click on
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 step as often you want.
14. Choose
15. Select the green data request
16. Choose the Button
17. Choose the Button
request list.
4.4.5.2
Refresh to see that the request is disappeared from the data
Creating Data Transfer Process for ODS Objects
0RMP_DS01
Procedure
1. Right-Mouse-Click on
2. Choose
3. Execute the F4 Help of the field DataSource
4. Choose the DataSource RT_DS_0RMP_DS01 as shown in the following screenshot:
© SAP AG
Page 108 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
5. Choose the Button
Continue
6. Enter the following data on the tab page Extraction:
Field name
User value
Extraction Mode
Full
7. Go to the Execute tab
8. Choose the Button
Activate
9. Choose the Button
10. Choose the Button Yes in the upcoming screen if you want to enter the monitor, otherwise
No.
11. Choose the Button
Refresh to see that there is a green data transfer process.
12. Choose the Button
Back
13. Right-Mouse-Click on
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
15. Select the green data request
16. Choose the Button
17. Choose the Button
request list.
© SAP AG
Refresh to see that the request is disappeared from the data
Page 109 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.4.6 Load 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.
Procedure
1. Choose the Button
Search and enter the following data:
Field name
User value
Find
0RMP_DS01
2. Choose the Button
3. Right-Mouse-Click on
4. Follow the context menu path Additional functions  Update 3.x Data to Targets
5. Flag
6. Choose the Button
7. Go to the tab page
8. Flag
9. Select the InfoProvider as shown in the screen shot:
Note: If the Update Rule
is not active please remove the
Routine on the characteristics 0RF_ASTYP - 0RT_COLCR - 0RT_SIZCR
10. Go back to the
tab
11. Choose the Button
12. Choose the Button
© SAP AG
Monitor in the board
Page 110 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
13. Choose the Button
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.
14. Choose the Button
Back.
15. Search for 0RMP_DS02, as described before.
16. Right-Mouse-Click on
17. Follow the context menu path Additional functions  Update 3.x Data to Targets
18. Flag
19. Choose the Button
20. Go to the tab page
21. Flag
22. Select the InfoProvider as shown in the following screen shot:
23. Go back to the
tab
24. Choose the Button
25. Choose the Button
Monitor in the board
26. Choose the Button
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.
27. Choose the Button
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
© SAP AG
Page 111 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
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
and
.
© SAP AG
Page 112 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.4.8 Apply 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
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 the Button
5. There could be entries like
6. Choose the Button
7. Choose the Button
Save InfoObject List
8. Choose the button Execute
9. Choose the Button
Finished”
© SAP AG
Refresh until you get the message “Hierarchy/Attribute Change Is
Page 113 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.5 Allocation
4.5.1 Create 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoProvider.
3. Follow the application path Industry Sectors  Trade IndustriesRetailing
4. Right-Mouse-Click on the InfoArea Retailing
5. Choose
6. Enter the following data in the dialog box Transaction Data – InfoSource: Assign Source
System:
Field name
User value
Info Area
RT_ALLOC
Long Description
Allocation
7. Select the Button
Continue to create the InfoArea.
4.5.2 Create InfoProviders
Use
The purpose of this activity is to create an InfoProvider in which the data from a source system
will be stored.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoProvider.
© SAP AG
Page 114 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
3. Follow the path Industry SectorsTrade Industries  Retailing
4. Right-Mouse-Click on the InfoArea Allocation - RT_ALLOC
5. Choose Create InfoCube.
6. Enter the following data:
Field name
User values
InfoCube
RT_C01
Description
Allocation Strategy
InfoArea
RT_ALLOC
InfoProvider Type
7. Choose the Button
Create
In the next window you create the following time characteristics, unit characteristics,
characteristics and key performance indicators for the InfoProvider:
●
●
Characteristics:
○
0MATERIAL
○
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:
○
●
Material
0CALMONTH
Calendar year/Month
Key performance indicators:
○
0CPSAEXCUSU Absolute Sales / SUn
8. Right-Mouse-Click on Dimension 1
9. Follow the menu path Properties.
10. Enter the following data in the upcoming screen:
Field name
User value
Description
Article
11. Choose the Button
© SAP AG
Continue.
Page 115 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
12. Right-Mouse-Click on
13. Follow the context menu path Create New Dimensions.
14. Enter in the screen Create Dimensions the following data:
Field name
User value
Description
Store
15. Choose the Button
Create Another Dimension
16. Enter in the screen Create Dimensions the following data:
Field name
User value
Description
Consumer
17. Choose the Button
Create Another Dimension
18. Enter in the screen Create Dimensions the following data:
Field name
User value
Season
Season
19. Choose the Button
Continue.
20. Right-Mouse-Click on the dimension Time
21. Choose InfoObject Direct Input
22. Insert the following characteristics into the dimension Time:
InfoObject
Description
0CALMONTH
Calendar Year / Month
23. Choose the Button
Continue
24. 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:
InfoObject
Description
0MATERIAL
Material
0MATL_GROUP
Material Group
Insert the following characteristics into the dimension Store:
InfoObject
Description
0PLANT
Store
© SAP AG
Page 116 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Insert the following characteristics into the dimension Consumer:
InfoObject
Description
0CM_HIEID
Hierarchy ID
0RT_PRBAND
Price Band Category
0CM_CDT3
Segment
0CM_CDT4
Subsegment
Insert the following characteristics into the dimension Season:
InfoObject
Description
0RT_SEASON
Season category
To assign key figures to the InfoProvider proceed as follows.
25. Right-Mouse-Click on
26. Choose InfoObject Direct Input
27. Insert the following key figure:
InfoObject
Description
0CPSAEXCUSU
Absolute Sales / SUn
28. Choose the Button
Continue.
29. Choose the Button
Activate.
4.5.3 Create Application Components
Use
The purpose of this activity is to create an Application Component as a structure element in the
InfoSources tree.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoSources.
© SAP AG
Page 117 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
3. Follow the application path SAP Application Components  SAP Sectors Trade
Industries Retailing
4. Right-Mouse-Click on the application component Retailing
5. Choose
6. In the following screen, enter the following data:
Field name
User values
Application Component
ZRT_ALLOC
Long Description
Allocation
7. Select the Button
Continue.
4.5.4 Create InfoSources and Transfer Rules
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
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoSources.
3. Follow the application path SAP Application Components  SAP Sectors  Retailing
4. Right-Mouse-Click on the Application Component Allocation
5. Follow the context menu path Additional Functions  Create InfoSource 3.x
6. In the Create InfoSource dialog box enter the following data:
Field name
User values
InfoSource
RT_IS_RT_C01
Long description
InfoSource RT_C01
7. Choose the Button
Continue.
8. Right-Mouse-Click on the newly created InfoSource RT_IS_RT_C01.
9. Choose Change.
10. Choose the Button
11. Choose the Button
12. Flag
© SAP AG
on the right hand side
and enter RT_C01.
Page 118 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
13. Choose the Button
Transfer
14. Choose the Button
Transfer all InfoObjects
15. Choose the Button
Activate.
16. Choose YES in the upcoming dialog box.
17. Choose the Button
Back.
18. Choose the Button
Collapse to close the
19. Choose the Button
Expand to open the
20. Enter the following data:
Field name
User action and values
Source System
FILE by Chooseing the Button
46. Choose YES in the upcoming screen Save Changes ?
The system will automatically propose the transfer rules.
21. Choose the Button
22. Choose the Button
Activate.
Back.
4.5.5 Assign Update Rules to InfoProviders
Use
The purpose of this activity is to assign update rules in order to prepare the data transfer into the
InfoProvider.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling screen choose InfoProvider.
© SAP AG
Page 119 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
3. Choose the Button
Search and enter the following data:
4. Enter the following data:
Field name
User value
Find
RT_C01
5. Choose the Button
6. Right-Mouse-Click on the InfoProvider RT_C01
7. Follow the context menu path Additional Functions  Create Update Rules.
8. Flag
on the screen Update rules create: Start
9. Enter as Info Source RT_IS_RT_C01
10. Choose the Button
Continue
The next screen shows the update rule on the right hand side.
11. Choose the Button
12. Choose the Button
Activate on the screen Update rules create: Rules
Back
4.5.6 Assign 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.
InfoProvider
Description
Flatfiles to Load
RT_C01
Allocation Strategy
Flatfile_RT_C01_2011.csv
Please check the Season code in the File before loading the data. The Season code must ‘0001’
or ‘0002’. If the Season Code is ‘1’ or ‘2’ in the files please replace them to ‘0001’ or ‘0002’.
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
Doku CD SAP Best Practices in the folder \Misc\Retail\US\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.
© SAP AG
Page 120 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling view choose InfoProvider.
3. Choose the Button
Search.
4. Enter the following data in the upcoming screen:
Field name
User value
Find
RT_C01
13. Choose the Button
5. Expand
6. Expand
7. Expand
8. Right-Mouse-Click on
9. Choose Create InfoPackage.
10. Enter the following data:
Field name
User values
InfoPackage Description
Flatfile Load: Transactional Data RT_C01
11. Select the line for RT_IS_RTC01 in the section DataSource.
12. Choose the Button
13. Choose the Button
Hide/Show Navigator
14. Choose the External data tab and make the following entries:
Field
Values
Load external data from
 Client
workstation
File type
Name of file
© SAP AG
Notes
The flatfiles are csv files.
Use F4,
input help to
open the
folder for
See the comments in the
prerequisites paragraph of this
chapter. Choose the first flatfile
Flatfile_RT_C01_2011.csv
Page 121 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
your flatfiles
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
14. Choose the Processing tab and make the following entry:
Field
Value
PSA and then into Data Targets

15. Choose the Data targets tab and set
16. Select the InfoProvider
17. Choose the Update tab and make the following entries:
Field
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
18. Choose the Schedule tab
19. Choose the Button
You get the status message Data was requested.
20. Choose the Button
© SAP AG
Monitor to monitor the request.
Page 122 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
21. Choose the Button
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.
22. Choose the Button
Back twice
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 Log 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
Procedure
1. One possibility to access the Query Designer is using the following naviagtion:
Transaction Code
SAP BI Menu
© SAP AG
RRMX
A menu entry for this activity is not available in the system.
Please access this activity through its transaction code.
Page 123 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
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 Button
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 the Button
4. Follow the menu path
5. Set the flag
6. Repeat step (1) and (2).
7. Choose the Button
Tools
8. Choose
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
 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 Create 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
© SAP AG
Page 124 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
The variable used in the query must be activated. Refer to chapter Activating Business Content,
Query Variables.
Procedure
1. Choose the Button
2. Choose the Button
New Query in the board
Technical Name on/off in the board
3. Follow the path Industry Sectors Trade Industries Retailing  Allocation
4. Double-Click on the InfoProvider
5. You enter the following screen:
6. Choose the Button
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 Dimension Consumer
symbol in front of it. Then you see several characteristics, choose
by clicking on the
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
Page 125 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.5.8.1
Create Query RT_RTC01_Q001
Procedure
1.
Insert via Drag and Drop into the frame Free Characteristics:
Field
Description
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:
4.
Field
Description
0PLANT
Store
0CALMONTH
Calendar year/Month
0MATERIAL
Article
Insert via Drag and Drop into the frame Columns:
Field
Description
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-Mouse-Click on
6.
Choose Restrict.
7.
Select the
8.
Right-Mouse-Click on
9.
Choose Technical Names.
tab
10. Restrict the InfoObject Price Band Category with the following variable that you have to
create:
© SAP AG
Page 126 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Variable Name
Description
Variable Represents
Variable entry is
RT_PBC
Price Band
Category
Single Value
Optional
11. Right-Mouse-Click on
12. Choose New Variable
13. Enter the values as shown in the screen shot:
14. Choose the Button
15. Change the default values as shown in the screen shot.
16. Choose the Button
17. Choose the Button
18. Choose the Button
19. Mark the just created variable.
20. Choose the Button
Add
21. Choose the Button
22. Restrict the InfoObject Season with the following Variable:
Variable Name
Description
Variable Represents
Variable entry is
0P_OSAIS
Season
Single Value
Optional
© SAP AG
Page 127 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
23. Restrict the InfoObject Plant with the following Variable:
Variable Name
Description
Variable Represents
Variable entry is
0S_PLANT
Plant
(Selection
Options,
Optional)
Selection option
Optional
24. Restrict the InfoObject Calendar Year/Month with the following Variable:
Variable Name
Description
Variable Represents
Variable entry is
0S_CALMO
Month
Selection option
Optional
25. Restrict the InfoObject Material with the following Variable:
Variable Name
Description
Variable Represents
Variable entry is
0S_MAT
Material
(Selection
Options,
Optional)
Selection option
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 the Button
Save Query as
28. Enter the following data:
Field Name
Value
Description
Allocation - Article/Month
© SAP AG
Page 128 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Technical Name
RT_RTC01_Q001
29. Choose the Button
4.5.8.2
Create Query RT_RTC01_Q002
Procedure
1.
Being in the first query Choose the Button
Save Query as
Field Name
Value
Description
Allocation – Material Group/Month
Technical Name
RT_RTC01_Q002
2.
Exchange Material against Material Group in the frame Rows.
3.
Restrict the InfoObject Material Group with the following Variable:
Variable Name
Description
Variable Represents
Variable entry is
0S_MATGR
Material
Group
Selection option
Optional
4.
Choose the Button
5.
Now that you have restricted the characteristics the query should be equal to the one
shown in the screen shot.
© SAP AG
Save Query
Page 129 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.5.8.3
Create Query RT_RTC01_Q003
Procedure
1.
2.
Being in the second query Choose the Button
Save Query as
Field Name
Value
Description
Allocation - Subsegment/Month
Technical Name
RT_RTC01_Q003
Add via Drag and Drop into the Free Characteristics frame:
Field
Description
0CM_HIEID
Hierarchy ID
3.
Exchange Material Group against SubSegment in the frame Rows.
4.
Restrict the InfoObject Hierarchy ID with the following Variable:
5.
Variable Name
Description
Variable Represents
Variable entry is
0CMHIEID
CDT
Hierarchy ID
Single Value
Mandatory
Restrict the InfoObject Subsegment with the following Variable:
Variable Name
Description
Variable Represents
Variable entry is
RT_SSEG
Subsegment
Selection option
Optional
6.
Right-Mouse-Click on
7.
Choose Restrict.
8.
Select the
9.
Right-Mouse-Click on
tab
10. Choose Technical Names.
11. Right-Mouse-Click on
12. Choose New Variable
13. Enter the values as shown in the screen shot:
© SAP AG
Page 130 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
14. Choose the Button
15. Change the default values as shown in the screen shot.
16. Choose the Button
17. Choose the Button
18. Choose the Button
19. Select the just created variable.
20. Choose the Button
Add
21. Choose the Button
22. Choose the Button
Save Query
23. Now that you have restricted the characteristics. The query should be equal to the one
shown in the next screen shot.
© SAP AG
Page 131 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.5.8.4
Create Query RT_RTC01_Q004
Procedure
1.
Being in the first query Choose the Button
Save Query as
Field Name
Value
Description
Allocation - Segment/Month
Technical Name
RT_RTC01_Q004
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:
Variable Name
Description
Variable Represents
Variable entry is
RT_SEG
Segment
Selection option
Optional
5.
Right-Mouse-Click on
6.
Choose Restrict.
7.
Select the
8.
Right-Mouse-Click on
9.
Choose Technical Names.
tab
10. Right-Mouse-Click on
11. Choose New Variable
12. Enter the values as shown in the screen shot:
13. Choose the Button
© SAP AG
Page 132 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
14. Change the default values as shown in the screen shot.
15. Choose the Button
16. Choose the Button
17. Choose the Button
18. Mark the just created variable
19. Choose the Button
Add
20. Choose the Button
21. Choose the Button
Save Query
22. Now that you have restricted the characteristics. The query should be equal to the one
shown in the next screen shot.
© SAP AG
Page 133 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4.5.9 Allocation Settings – SAP ECC
4.5.9.1
Field Mappings BW <–> ECC
Use
The purpose of this activity is to define the integration of the allocation process. That means a
field mapping must take place.
Prerequisites
The necessary queries must be created.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
SAP Menu
2. Choose the Button
MCW_AA
A menu entry for this activity is not available in the system.
Please access this activity through its transaction code.
IMG-Activity in front of the entry
3. In the following screen select the Button
4. Enter the following data:
Target System
Analyt. Appl. Query
Query Name
The logical name of
your BI System
RT_C01/RT_RTC01_Q001
Allocation - Article/Month
The logical name of
your BI System
RT_C01/RT_RTC01_Q002
Allocation - Material
Group/Month
The logical name of
your BI System
RT_C01/RT_RTC01_Q003
Allocation - Subsegment/Month
The logical name of
your BI System
RT_C01/RT_RTC01_Q004
Allocation - Segment/Month
5. Mark the entry Allocation – Article/Month
6. Double-click on
7. Choose the Button
8. Map the BI Fields with the ECC Fields according to the following screen shot. The value is
not necessary an entry that you find within the F4-Help.
© SAP AG
Page 134 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
9. Choose the Button
Save.
10. Choose The Button
Back
11. Choose The Button
Back
12. Mark the entry Allocation - Material Group/Month
13. Double-click on
14. Choose the Button
15. Map the BI Fields with the ECC Fields according to the following screen shot. The value is
not necessary an entry that you find within the F4-Help.
16. Choose the Button
Save.
17. Choose The Button
Back
© SAP AG
Page 135 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
18. Choose The Button
Back
19. Mark the entry Allocation – Subsegment/Month
20. Double-click on
21. Choose the Button
22. Map the BI Fields with the ECC Fields according to the following screen shot. The value is
not necessary an entry that you find within the F4-Help.
23. Choose The Button
Back
24. Choose The Button
Back
25. Mark the entry Allocation – Segment/Month
26. Double-click on
27. Choose the Button
28. Map the BI Fields with the ECC Fields according to the following screen shot. The value is
not necessary an entry that you find within the F4-Help.
© SAP AG
Page 136 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
MCW_AA
SAP Menu
2. Choose the Button
A menu entry for this activity is not available in the
system. Please access this activity through its transaction
code.
IMG-Activity in front of the entry
3. In the screen Determine Work Area: Entry enter the following data:
Field name
User value
Analytical Appl.
001
Choose button continue
Choose the button
to add a new method and add at the table:
Field name
User values
Method
RTAL01
Method description
Allocation Article/Month
4. Choose the ENTER key on the keyboard
© SAP AG
Page 137 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
5. Mark the new line and Double-Click on
6. Choose the Button
to add a new method step
7. Enter the following data:
Field name
User values
Meth. Step
1
Target system
The logical name for BI System
Analyt. Appl. Query
RT_C01/RT_RTC01_Q001
8. Choose the ENTER key on the keyboard
9. Choose the Button
Back.
10. Choose the Button
Back.
11. Choose the button
to add a new method and add at the table:
Field name
User values
Method
RTAL02
Method description
Allocation - Material Group/Month
12. Choose the ENTER key on the keyboard
13. Mark the new line and Double-Click on
14. Choose the Button
to add a new method step
15. Enter the following data:
Field name
User values
Meth. Step
1
Target system
The logical name for BI System
Analyt. Appl. Query
RT_C01/RT_RTC01_Q002
16. Choose the ENTER key on the keyboard
17. Choose the Button
Back.
18. Choose the Button
Back.
19. Choose the button
to add a new method and add at the table:
Field name
User values
Method
RTAL03
© SAP AG
Page 138 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Field name
User values
Method description
Allocation - Subsegment/Month
20. Choose the ENTER key on the keyboard
21. Mark the new line and Double-Click on
22. Choose the Button
to add a new method step
23. Enter the following data:
Field name
User values
Meth. Step
1
Target system
The logical name for BI System
Analyt. Appl. Query
RT_C01/RT_RTC01_Q003
24. Choose the ENTER key on the keyboard
25. Choose the Button
Back.
26. Choose the Button
Back.
27. Choose the button
to add a new method
28. Enter the following data:
Field name
User values
Method
RTAL04
Method description
Allocation - Segment/Month
29. Choose the ENTER key on the keyboard
30. Mark the new line and Double-Click on
31. Choose the Button
to add a new method step
32. Enter the following data:
Field name
User values
Meth. Step
1
Target system
The logical name for BI System
Analyt. Appl. Query
RT_C01/RT_RTC01_Q004
33. Choose the ENTER key on the keyboard
34. Choose the Button
© SAP AG
Back.
Page 139 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
35. Choose the Button
4.5.9.3
Save
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.
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.
Procedure
1. Access the next activity using one of the following navigation options:
Transaction Code
SPRO
IMG Menu
SAP Customizing Implementation Guide  Logistics - General
 Article Hierarchy  BW Extraction
2. Choose the Button
IMG_Activity for the entry
3. Choose the Button
4. Select the following entry by choosing the Button
5. Choose the Button
© SAP AG
:
Save.
Page 140 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
5 Appendix A: Helpful BI Actions
5.1 Activate 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling screen choose InfoProvider.
3. Choose the Button
Search.
4. Enter the following data in the upcoming screen:
Field name
User value
Find
0RMP_C05
5. Choose the Button
6. Right-Mouse-Click on 0RMP_C05
7. Choose Change
8. Choose the Button
Activate
5.2 Activate 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
© SAP AG
Page 141 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling screen choose InfoProvider.
3. Choose the Button
Search.
4. Enter the following data in the upcoming screen:
Field name
User value
Find
0RMP_C05
5. Choose the Button
6. Expand
7. Right-Mouse-Click
8. Choose Change
9. Choose the Button
Activate
5.3 Activate 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
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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling screen choose InfoProvider.
3. Choose the Button
© SAP AG
Search.
Page 142 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
4. Enter the following data in the upcoming screen:
Field name
User value
Find
0RMP_DS01
5. Choose the Button
6. Right-Mouse-Click on 0RMP_C05
7. Choose Real-Time Info Cube Load Behavior.
8. Flag the entry Real-Time Data Target can be planned; data loading not allowed.
9. Choose the Button
© SAP AG
Continue
Page 143 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
5.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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling screen choose DataSources.
3. Choose the Button
Choose Source System
4. Select your ECC System
5. Choose the Button
Search.
6. Enter the desired DataSource in the upcoming screen:
Field name
User value
Find
0MATERIAL, for example
7. Choose the Button
8. Right-Mouse-Click on 0MATERIAL
9. Choose Replicate DataSource
10. On the Data Warehousing Workbench: Modeling screen choose InfoSources.
11. Choose the Button
Search.
12. Enter the desired DataSource in the upcoming screen:
Field name
User value
Find
0MATERIAL, for example
13. Choose the Button
14. Activate the corresponding transfer rules and Update Rules again.
© SAP AG
Page 144 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
5.5 Delete 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
2. On the Data Warehousing Workbench: Modeling screen choose InfoProvider.
5.5.1 Basic InfoProvider
1. Choose the Button
Search.
2. Enter the following data in the upcoming screen:
Field name
User value
Find
0RMP_C22
© SAP AG
Page 145 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
3. Choose the Button
4. Right-Mouse-Click on 0RMP_C22
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 on the red or yellow traffic light in the corresponding data request
7. Choose
8. Choose the Button
For a green data request execute the following steps to delete it.
9. Select the data request like
10. Choose the Button
11. Choose the Button
12. Choose the Button
to check the deletion of the request.
Exit to close the right hand frame.
5.5.2 Real Time InfoProvider
1. Choose the Button
Search.
2. Enter the following data in the upcoming screen:
Field name
User value
Find
0RMP_C05
3. Choose the Button
4. Right-Mouse-Click on 0RMP_C05
5. Choose Real-Time Info Cube Load Behavior.
6. Flag the entry Real-Time Data Target can be loaded with data; planning not allowed.
7. Choose the Button
Continue.
By executing these steps a data request with a yellow traffic light is changed to a data
request with a green traffic light.
© SAP AG
Page 146 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
8. Right-Mouse-Click on 0RMP_C05
9. Choose Manage
For a green data request execute the following steps to delete it.
10. Select the data request like
11. Choose the Button
12. Choose the Button
13. Choose the Button
to check the deletion of the request.
Exit to close the right hand frame.
10. Right-Mouse-Click on 0RMP_C05
11. Choose Real-Time Info Cube Load Behavior.
12. Flag the entry Real-Time Data Target can be planned; data loading not allowed.
13. Choose the Button
Continue
5.6 Apply 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.
Procedure
1. Access the activity using one of the following navigation options:
Transaction Code
RSA1
SAP BI Menu
Information Systems  Business Information Warehouse
Modeling  Data Warehousing Workbench: Modeling
© SAP AG
Page 147 of 148
SAP Best PracticesBI Retail: Merchandise and Assortment Planning (764): Configuration Guide
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 the Button
5. There could be entries like
6. Choose the Button
7. Choose the Button
8. Choose the Button
Save InfoObject List
Refresh until you get the message
6 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.
6.1 Maintain Fiscal Year Variant
You must maintain the fiscal year variant for the new plan year in your planning environment.
6.2 Delete Data Requests
You must delete the data requests in the InfoProviders 0RMP_C05, RT_C01, RT_C31, RT_C35.
6.3 Adjust 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.
6.4 Load Updated Flatfiles
You have to reload the flatfiles. See Chapter 4.
© SAP AG
Page 148 of 148