Post on 26-Oct-2015
description
transcript
EHP3 for SAP ERP 6.0
September 2009
English
764: BI Retail: Merchandise and Assortment Planning
SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany
Building Block Configuration Guide
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Copyright
© Copyright 2009 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
© SAP AG Page 2 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
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 3 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
External Process
Business Process Alternative/Decision Choice
Typographic Conventions
Type Style Description
Example text Words or characters that appear on the screen. These include Field names, screen titles, pushButtons as well as menu names, paths and options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names of elements in the system. These include report names, program names, Transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.
Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
© SAP AG Page 4 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Contents
1 Purpose................................................................................................................................... 7
2 Preparation.............................................................................................................................. 7
3 Budget Customizing................................................................................................................. 7
3.1 Defining PPW Budget Levels – SAP BI.........................................................................7
3.2 Defining OTB Budget Levels – SAP BI..........................................................................8
3.3 Defining PPW Key Figures - SAP BI.............................................................................9
3.4 Defining OTB Key Figures - SAP BI............................................................................10
3.5 Defining PPW Budget Type - SAP BI..........................................................................10
3.6 Defining OTB Budget Types - SAP BI.........................................................................11
3.7 Activating Budget Types - SAP BI...............................................................................12
3.8 Creating RFC Destinations - SAP BI...........................................................................13
3.9 Transferring Budget Types to SAP ECC – SAP BI......................................................14
3.10 Assigning PPW Budget IDs – SAP ECC......................................................................15
3.11 Activating PPW Budget Type – SAP ECC...................................................................16
3.12 Checking and Extending OTB Budget Types – SAP ECC...........................................16
3.13 Activating OTB Budget Types – SAP ECC..................................................................18
3.14 Reorganization of OTB Budgets – SAP ECC..............................................................18
3.14.1 Determining the Generated Budget Plan Table.......................................................19
3.14.2 Comparing Corresponding Structure with Budget DataStore Object.......................19
3.14.3 Deleting Structure and Table Type for the Generated Plan Table...........................20
3.14.4 Reorganizing Budget Types....................................................................................21
3.15 Changing Type Group /MAP/ - SAP BI........................................................................22
3.16 Changing Function Module /MAP/SSM_CREATE_WORK_ITEMS_RFC....................22
4 Transactional Data Extraction via Flatfiles – SAP BI.............................................................24
4.1 Creating Application Components...............................................................................24
4.2 Merchandise Planning.................................................................................................25
4.2.1 Creating InfoSources and Transfer Rules...............................................................25
4.2.2 Assigning Update Rules to InfoProviders................................................................26
4.2.3 Executing Info packages for Real Time InfoProvider...............................................27
4.2.4 Releasing PPW Budget...........................................................................................30
4.2.5 Releasing OTB Budget............................................................................................31
4.2.6 Assigning Price Planner Groups to Budget – SAP ECC..........................................32
4.3 Assortment Planning...................................................................................................33
4.3.1 Defining Key Figures – SAP BI................................................................................33
4.3.2 Maintaining Values for Key Figure 0RT_KEYFIG....................................................35
4.3.3 Creating InfoProviders.............................................................................................36
4.3.4 Creating InfoSources and Transfer Rules...............................................................40
4.3.5 Assigning Update Rules to InfoProviders................................................................41
4.3.6 Assigning InfoPackage to InfoSources and Loading Data.......................................42
4.3.7 Logging on to the Query Designer...........................................................................46
4.3.8 Creating Queries.....................................................................................................47
© SAP AG Page 5 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
4.3.9 Defining Message Types and Selections Options for Releasing Assortments........52
4.3.10 BADI UPARI_ASRTPLN..........................................................................................53
4.3.11 Releasing Assortment Plan.....................................................................................60
4.3.12 Creating Purchasing List – SAP ECC......................................................................61
4.3.13 OTB Check: Maintaining Document-Type Dependent Settings – SAP ECC...........63
4.4 Slow Seller Management.............................................................................................64
4.4.1 Generating Export DataSources..............................................................................65
4.4.2 Install Interface “Goods Receipt Date”....................................................................65
4.4.3 Loading Goods Receipt Dates into 0MAT_PLANT..................................................69
4.4.4 Install Interface “ POS and Stock Data SSM“..........................................................71
4.4.5 Loading POS and Stock Data into ODS Objects.....................................................88
4.4.6 Loading POS and Stock Data into InfoProviders.....................................................89
4.4.7 Reloading POS and Stock Data SSM.....................................................................91
4.4.8 Applying Hierarchy/Attribute Change......................................................................91
4.5 Allocation..................................................................................................................... 91
4.5.1 Creating InfoAreas..................................................................................................91
4.5.2 Creating InfoProviders.............................................................................................92
4.5.3 Creating Application Components...........................................................................94
4.5.4 Creating InfoSources and Transfer Rules...............................................................95
4.5.5 Assigning Update Rules to InfoProviders................................................................96
4.5.6 Assigning InfoPackage to InfoSources and Loading Data.......................................97
4.5.7 Logging on to the Query Designer...........................................................................99
4.5.8 Creating Queries...................................................................................................100
4.5.9 Allocation Settings – SAP ECC.............................................................................109
5 Adjust Steps Concerning Personalization............................................................................114
5.1 Changing Merchandise Planning Flatfiles..................................................................114
5.1.1 InfoProvider 0RMP_C05........................................................................................115
5.2 Changing Assortment Planning Flatfiles....................................................................116
5.2.1 InfoProvider RT_C35.............................................................................................116
5.3 Changing Allocation Flatfiles.....................................................................................116
5.3.1 InfoProvider RT_C01.............................................................................................117
6 Appendix A: Helpful BI Actions............................................................................................117
6.1 Activating InfoProviders.............................................................................................117
6.2 Activating Update Rules............................................................................................118
6.3 Activating Transfer Rules...........................................................................................118
6.4 Replicate DataSources..............................................................................................119
6.5 Deleting Data Requests.............................................................................................120
6.5.1 Basic InfoProvider.................................................................................................120
6.5.2 Real Time InfoProvider..........................................................................................121
6.6 Applying Hierarchy/Attribute Change.........................................................................122
7 Appendix B: Year Change Tasks.........................................................................................123
7.1 Maintaining Fiscal Year Variant.................................................................................123
7.2 Deleting Data Requests.............................................................................................123
7.3 Adjusting Flatfiles......................................................................................................123
© SAP AG Page 6 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
7.4 Loading Updated Flatfiles..........................................................................................123
© SAP AG Page 7 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
BI Retail: Merchandise and Assortment Planning
1 PurposeThis 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 PreparationBefore you start installing this building block, you must install prerequisite building blocks. For more information, see the building block prerequisite matrix (Prerequisites_Matrix_[xx]_EN_IN.xls; the placeholder [xx] depends on the SAP Best Practices version you use, for example, Retail refers to the SAP Best Practices for Retail Package: Prerequisites_Matrix_RET_EN_IN.xls). This document can be found on the SAP Best Practices documentation DVD in the folder..\BBLibrary\General\.
3 Budget Customizing
UseThe 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.
PrerequisitesThe following Configuration Guides must be completed:
- 761: BI Retail: Connectivity
- 762: BI Retail: Integration and Content Activation
- 763: BI Retail: Customizing and Master Data Extraction
3.1 Defining PPW Budget Levels – SAP BI
UseYou must define budget levels and budget key figures. Within the budget level definition you select from an InfoProvider the characteristics that determine the budgets.
Procedure1. Access the activity using one of the following navigation options:
IMG menu SAP Customizing Implementation Guide SAP NetWeaver Business Intelligence Settings for BI Content Trade Industries Retailing Budget Planning Budget Type
© SAP AG Page 8 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Define Budget Levels
Transaction code SPRO
2. Choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Level InfoCube Long description
PPW 0RMP_C05 Merchandise Planning, Plan
4. Mark the entry PPW.
5. Double-click Level InfoObjects.
6. Choose New Entries.
7. On the New Entries: Overview of Added Entries screen, make the following entries:
InfoObject Long description Hierarchy Fiscal Year Variant
0CM_CDT3 Segment
0CM_HIEID Hierarchy ID B1
0FISCPER Fiscal year / period
0FISCVARNT Fiscal year variant V3
0RT_SEASON Season Category
8. Choose Save.
9. Choose Back twice.
3.2 Defining OTB Budget Levels – SAP BI
Procedure1. Choose New Entries.
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 Level InfoObjects.
5. Choose New Entries.
6. On the New Entries: Overview of Added Entries screen, make the following entries:
InfoObject Long description Hierarchy Fiscal Year Variant
0CM_CDT3 Segment
0CM_HIEID Hierarchy ID B1
0FISCPER Fiscal year / period
0FISCVARNT Fiscal year variant V3
0RT_SEASON Season Category
7. Choose Save.
© SAP AG Page 9 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
8. Choose Back twice.
3.3 Defining PPW Key Figures - SAP BI
UseWithin 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.
Procedure1. Access the activity using one of the following navigation options:
IMG menu SAP Customizing Implementation Guide SAP NetWeaver Business Intelligence Settings for BI Content Trade Industries Retailing Budget Planning Budget Type Define Key Figures
Transaction code SPRO
2. Choose New Entries.
3. On the New Entries: Overview of Added Entries screen, make the following entries:
Set keyfig InfoCube Long description
PPW 0RMP_C05 Merchandise Planning, Plan
4. Mark the entry PPW.
5. Double-click InfoObjects of Set.
6. Choose New Entries.
7. On the New Entries: Overview of Added Entries screen, make the following entries:
InfoObject Long description
0RTSPRENSV Revaluation at Retail (Negative)/ Retail Value
8. Choose Save.
9. Choose Back twice.
3.4 Defining OTB Key Figures - SAP BI
Procedure1. Choose New Entries.
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 InfoObjects of Set.
© SAP AG Page 10 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
5. Choose New Entries.
6. On the New Entries: Overview of Added Entries screen, make the following entries:
InfoObject Long description
0RTTPRQUOTA Planned Open-To-Buy (Purchase Price)
7. Choose Save.
8. Choose Back twice.
3.5 Defining PPW Budget Type - SAP BI
Use
You also have to define the characteristics of the budget type. To do this, you assign a budget level, a key figure set and the name of a transactional ODS object that is generated when the budget type is activated to each budget type.
The active budget type and the assigned budget level and key figure can then be transferred to SAP ECC.
Procedure1. Access the activity using one of the following navigation options:
IMG menu SAP Customizing Implementation Guide SAP NetWeaver Business Intelligence Settings for BI Content Trade Industries Retailing Budget Planning Budget Type Define Budget Types
Transaction code SPRO
2. Choose New Entries.
3. On the New Entries: Details of Added Entries screen, make the following entries:
Field name Value
Application 1
Budge Type 01
Description Budge Type with PPW Check
Start Date Today
Finish date 9999.12.31
Budget Level PPW
Set of keyfigures PPW
DataStore Object PPW1
InfoArea 0TI_RT_MAP
Status budget type 1(automatically set)
Currency INR
4. Choose Save.
© SAP AG Page 11 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
5. Choose Back.
3.6 Defining OTB Budget Types - SAP BI
Procedure1. Choose New Entries.
2. On the New Entries: Details of Added Entries screen, make the following entries for Budget Type B1:
Field name Value
Application 2
Budge Type B1
Description Budge Type with OTB Check
Start Date Today
Finish date 9999.12.31
Budget Level OTB
Set of keyfigures OTB
DataStore Object OTBB1
InfoArea 0TI_RT_MAP
Status budget type 1(automatically set)
Currency INR
Delta activ Flag
Check Type OTB Complete check
3. Choose Save.
4. Choose Back.
5. Choose New Entries.
6. On the New Entries: Details of Added Entries screen, make the following entries for Budget Type B2:
Field name Value
Application 2
Budge Type B2
Description Budget type with no OTB check
Start Date Today
Finish date 9999.12.31
Budget Level OTB
Set of keyfigures OTB
DataStore Object OTBB2
InfoArea 0TI_RT_MAP
© SAP AG Page 12 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Status budget type 1(automatically set)
Currency INR
Delta activ Deflag
Check Type OTB No check
7. Choose Save.
8. Choose Back.
3.7 Activating Budget Types - SAP BI
Use
The budget level, the key figure set and the name of a transactional DataStore Object that is defined for a budget type is generated when the budget type is activated.
The active budget type and the assigned budget level and key figure can then be transferred to SAP ECC.
Procedure1. Access the activity using one of the following navigation options:
IMG menu SAP Customizing Implementation Guide SAP NetWeaver Business Intelligence Settings for BI Content Trade Industries Retailing Slow Seller Management Budget Planning Budget Type Activate Budget Types
Transaction code UPARI_BUDG01
2. On the Activation of Budget Type screen, make the following entries:
Application Budget Type Start Date
01 01 Creation Day
3. Choose Execute.
4. Choose Back.
5. On the Activation Budget Type screen, make the following entries:
Application Budget Type Start Date
02 B1 Creation Date
6. Choose Execute.
7. Choose Back.
8. On the Activation Budget Type screen, make the following of entries:
Application Budget Type Start Date
02 B2 Creation Date
9. Choose Execute.
10. Choose Back.
© SAP AG Page 13 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
3.8 Creating RFC Destinations - SAP BI
UseFor the applications PPW and OTB you use this section to define the RFC connections to the ECC systems to which the Customizing settings for the budget types and the planned budgets are transferred using the Release Workbench or the budget monitor.
These settings are not transported. These settings must therefore also be made in a productive BW system to specify the RFC destination to a productive ECC system for the plan data transfer using the Release Workbench or the budget monitor.
Procedure1. Access the activity using one of the following navigation options:
IMG menu SAP Customizing Implementation Guide SAP NetWeaver Business Intelligence Settings for BI Content Trade Industries Retailing Budget Planning Transfer to SAP ERP Create ERP RFC Destinations
Transaction code SPRO
2. Choose New Entries.
3. On the New Entries: Details of Added Entries screen, make the following entries
Appl. Characteristic Value
InfoObject / Field name
RFC Destination SAP ERP
PPW (Price Planning Workbench)
4. Choose Back.
5. Open a new transaction. Go to transaction Sale Basic Settings Logical Systems Define Logical System.
6. Find out your ERP System > XXXCLNTXXX Logical System Best Practices.
7. Go back to Change View “Assignment RFC Destination to SAP ECC”: Overview screen, make the following entries manually into Field name RFC Destination SAP ERP:
Appl. Characteristic Value InfoObject / Field name
RFC Destination SAP ERP
PPW (Price Planning Workbench)
The logical name of the ECC system
8. Choose Save.
9. Choose Back.
10. Choose New Entries.
11. On the New Entries: Details of Added Entries screen, make the following entries
Appl. Characteristic Value
InfoObject / Field name
RFC Destination SAP ERP
OTB (Open to Buy)
12. Choose Back.
13. On the Change View “Assignment RFC Destination to SAP ECC”: Overview screen, make the following entries with your ERP System > XXXCLNTXXX:
© SAP AG Page 14 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Appl. Characteristic Value InfoObject / Field name
RFC Destination SAP ERP
OTB (Open to Buy) The logical name of the ECC system
14. Choose Save.
15. Choose Back.
3.9 Transferring Budget Types to SAP ECC – SAP BI
UseThe 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.
Procedure1. Access the activity using one of the following navigation options:
IMG menu SAP Customizing Implementation Guide SAP NetWeaver Business Intelligence Settings for BI Content Trade Industries Retailing Budget Planning Transfer to SAP ERP Transfer Budget Types to R/3
Transaction code UPARI_BUDG02
2. On the Transfer of Budget Type screen, make the following entries:
Application Budget Type Start Date
01 01 Creation Day is displayed
3. Choose Execute.
4. Choose Back.
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 Execute.
7. Choose 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 Execute.
10. Choose Back.
3.10 Assigning PPW Budget IDs – SAP ECC
Use
© SAP AG Page 15 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
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.
PrerequisitesCustomizing Tables were transferred successfully from SAP BI into SAP ECC.
Procedure 1. Access the activity using one of the following navigation options:
IMG menu Logistics - General Price Planning Budget Planning Assign Budget Ids to Key Figures
Transaction code SPRO
2. Assign Budget ID 1=Key Figure 0RTSPRENGSV the number 1 as shown in the screen shot:
KeyFig.Set Name of Info Object Budget ID Description
PPW 0RTSPRENSV 1 Budget ID 1
3. Choose Save.
4. Choose Back.
3.11 Activating PPW Budget Type – SAP ECC
UseIn 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:
IMG menu Logistics - General Price Planning Budget Planning Activate Budget Types
Transaction code SPRO
© SAP AG Page 16 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
The Budget Type has to be activated for the PPW. If the budgets have been activated, you can’t activate them again.
2. On the activate budget type screen, make the following entries:
Field name Description User action and values Note
Application PPW (Price Planning Workbench)
01 Use F4
Budget type 01 Use F4
Valid from Data create Use F4
3. Choose Execute to activate the budget. The log will be displayed with the message: Budget Type 01 was activated.
4. Choose Back twice.
3.12 Checking and Extending OTB Budget Types – SAP ECC
UseIn 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:
IMG menu Material Management Purchasing Seasonal Procurement Open-To-Buy(OTB) Budget Planning Check and Extend Budget Types
Transaction code SPRO
2. Choose the budget type for OTB B1.
© SAP AG Page 17 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
3. Choose Details.
4. On the “Budget Types" Details screen, make the following entries:
Field name User action and values
Addin implementation WRF_BUDG_TYPE_001
Priority 5
Condition Type WOTB
5. Choose Save.
6. Choose Back.
7. Choose the budget type for OTB B2.
8. Choose Details.
9. On the "Budget Types" Details screen, make the following entries:
Field name User action and values
Addin implementation WRF_BUDG_TYPE_003
Priority 4
Condition Type WOTB
10. Choose Save.
11. Choose Back twice.
3.13 Activating OTB Budget Types – SAP ECC
UseIn 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:
IMG menu Material Management Purchasing Seasonal Procurement Open-To-Buy(OTB) Budget Planning Activate Budget Types
Transaction code SPRO
2. On the Activate Budget Types screen, make the following entries:
Field name Description User action and values
Note
Budget Application OTB (Open-To-Buy) 02
© SAP AG Page 18 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name Description User action and values
Note
Budget Type B1 Use F4
Valid from Date Create Use F4
3. Choose Execute to activate the budget. The log will be displayed with the message: Budget Type B1 was activated.
4. Choose Back.
5. On the Activate Budget Types screen, make the following entries:
Field name Description User action and values Note
Budget Application OTB (Open-To-Buy) 02
Budget Type B2 Use F4
6. Choose Execute to activate the budget. The log will be displayed with the message: Budget Type B2 was activated.
7. Choose 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 Determining the Generated Budget Plan Table
Procedure 1. Access the activity using one of the following navigation options:
SAP ECC menu Tools ABAP Workbench Overview Data Browser
Transaction code SE16
2. On the Data Browser: Initial Screen, make the following entries:
Field name User action and values
Table Name WRFT_BUDG_TYPE
3. Choose Table Contents.
4. On the Data Browser: Table WRFT_BUDGET_TYPE: Selection Screen, make the following entries:
Field name User action and values
APPL 02
TYPE B1
© SAP AG Page 19 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
5. Choose Execute.
6. On the Data Browser: Table WRFT_BUDGET_TYPE: Select Entries screen, make the following entries:
Field name User action and values
Flag the entry
7. Choose Choose.
8. Write down or copy the TABNAME PLAN. It could be like /1WRF/01002AB1P.
3.14.2 Comparing Corresponding Structure with Budget DataStore Object
Procedure 1. Choose Create New Session to open a second session.
2. Access the activity using one of the following navigation options:
SAP ECC menu Tools ABAP Workbench Development ABAP Dictionary
Transaction code SE11
3. Flag the entry Database table.
4. On the ABAP Dictionary: Initial Screen, make the following entries:
Field name User action and values
Database Table The name of the Plan Table from the previous chapter enlarged with “S”.
For example: /1WRF/01002AB1PS
5. Choose Display.
6. Choose Create New Session to open a third session.
7. Access the activity using one of the following navigation options:
SAP ECC menu Tools ABAP Workbench Development ABAP Dictionary
Transaction code SE11
8. On the ABAP Dictionary: Initial Screen, make the following entries:
Field name User action and values Comment
Database Table *OTBB1* *Use F4 Help
© SAP AG Page 20 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
A database table like /BIC/AOTBB100 is automatically found.
9. Choose Display.
10. Now compare the components of the structure /1WRF/01002AB1PS with the Field names of the budget DataStore Object /BIC/AOTBB100.
The best way to compare them is to compare the column Short Description. The Field name order must be the same.
3.14.3 Deleting Structure and Table Type for the Generated Plan Table
UseIf the result of the comparison of the previous subchapter is negative then you must delete the structure and the table type of the plan table you found in the first subchapter.
First delete the table type, and then delete the structure.
Procedure 1. Access the activity using one of the following navigation options:
SAP ECC menu Tools ABAP Workbench Development ABAP Dictionary
Transaction code SE11
2. Flag the entry Data type.
3. On the ABAP Dictionary: Initial Screen, make the following entries:
Field name User action and values
Database Table The name of the Plan Table from the first subchapter enlarged with “T”.
For example: /1WRF/01002AB1PT
4. Choose Delete.
5. Choose Continue in the upcoming Information dialog box.
6. Choose Yes in the next screen Delete Table Type /1WRF/01002AB1PT.
7. Flag the entry Database table.
8. On the ABAP Dictionary: Initial Screen, make the following entries:
Field name User action and values
Database Table The name of the Plan Table from the first subchapter enlarged with “S”.
For example: /1WRF/01002AB1PS
9. Choose Delete.
10. Choose Yes on the Delete Structure /1WRF/01002AB1PS screen.
© SAP AG Page 21 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
3.14.4 Reorganizing Budget Types
UseNow 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:
IMG menu Material Management Purchasing Seasonal Procurement Open-To-Buy(OTB) Budget Planning Reorganize Budget Types
Transaction code SPRO
2. On the Activate Budget Types screen, make the following entries:
Field name Description User action and values Note
Budget Application OTB (Open-To-Buy)
02
Budget Type B1 Use F4
3. Choose Execute to reorganize the budget. A log will be displayed.
4. Choose Enter.
5. Choose Back.
3.15 Changing Type Group /MAP/ - SAP BI
UseThe purpose is to change the type group /MAP/.
Procedure 1. Access the activity using one of the following navigation options:
SAP ECC menu Tools ABAP Workbench Development ABAP Dictionary
Transaction code SE11
2. On the ABAP Dictionary: Initial Screen, select Type Group.
3. Maintain the Type Group with value /MAP/.
4. Choose Change.
5. Confirm the information.
6. On the upcoming screen, choose Maint. In logon lang.
7. Choose the SourceCde tab.
8. ReplaceTYPES: /map/_t_rscrmvarp_t TYPE STANDARD TABLE OF /map/_s_rscrmvarp WITH NON-UNIQUE DEFAULT KEY with TYPES: /map/_t_rscrmvarp_t TYPE STANDARD TABLE OF RSCRMVARP WITH NON-UNIQUE DEFAULT KEY.
9. Choose Save.
10. Choose Active.
11. Choose Back.
© SAP AG Page 22 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
3.16 Changing Function Module /MAP/SSM_CREATE_WORK_ITEMS_RFC
UseThe purpose is to change the function module /MAP/SSM_CREATE_WORK_ITEMS_RFC.
Procedure 1. Access the activity using one of the following navigation options:
Transaction code SE37
SAP ECC menu Tools ABAP Workbench Development Function Builder
2. On the Function Builder: Initial Screen, maintain the Function Module with /MAP/SSM_CREATE_WORK_ITEMS_RFC.
3. Choose Change.
4. Confirm the information.
5. On the upcoming screen, choose Maint. In logon lang.
6. Choose Tables tab.
7. Replace the value /MAP/_S_RSCRMVARP in the column Associated Type by RSCRMVARP for the parameter I_T_BW_VARSEL.
8. Choose Save.
9. Choose Active.
10. Choose Back.
© SAP AG Page 23 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: 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 Creating Application Components
Use The purpose of this activity is to create an application component as a method to structure InfoSources. Here the need for the MAP transactional data is realized.
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoSources.
3. Follow the application path SAP Application Components SAP Sectors Trade Industries Retailing Merchandise and Assortment Planning.
4. Right click the component Merchandise and Assortment Planning.
5. Choose Create application component …
6. Enter the following data in the upcoming dialog box:
Field name User action and values
Application comp. ZRT_MAPN_TD
© SAP AG Page 24 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name User action and values
Long Description MAP Transactional Data
7. Choose Continue.
4.2 Merchandise Planning
4.2.1 Creating InfoSources and Transfer Rules
Use Loading data via flatfiles into the BI System presupposes the definition of an interface.
In this chapter the creation of InfoSources and Transfer Rules is described. We create 3.x InfoSources because the Business Content is based on SAP BI Version 3.5.
The steps described under Procedure must be executed concerning the InfoProvider:
InfoProvider Description
0RMP_C05 Merchandise Planning, Plan
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoSources.
3. Follow the application path SAP Application Components SAP Sectors Trade Industries Retailling Merchandise and Assortment Planning MAP Transactional Data.
4. Right click MAP Transactional Data.
5. Follow the context menu path Additional Functions Create InfoSource 3.x.
6. In the Create InfoSource dialog box enter the following data:
Field name User action and values
InfoSource RT_IS_0RMP_C05
Long description InfoSource 0RMP_C05
7. Choose Continue.
8. Right click the InfoSource RT_IS_0RMP_C05.
9. Choose Change.
10. Choose Transefer.
11. Choose Template.
12. Flag in the Field name of InfoCube.
13. Enter as InfoCube 0RMP_C05.
14. Choose Transfer.
15. Choose Transfer all InfoObjects.
16. Choose Activate.
17. Choose Yes in the upcoming dialog box.
© SAP AG Page 25 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
18. Choose Back.
19. Choose Collapse to close the Communication_Sturct.
20. Choose Expand to open the Transfer_structure/Transfer_Rules.
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 Activate.
24. Choose Back.
4.2.2 Assigning Update Rules to InfoProviders
Use This chapter describes the creation of Update Rules.
The steps described under Procedure must be executed concerning the InfoProviders:
InfoProvider Description
0RMP_C05 Merchandise Planning, Plan
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Choose Search and enter the following data:
Field name User action and values
Find 0RMP_C05
4. Choose Search.
5. Right click the InfoProvider 0RMP_C05
6. Follow the context menu path Additional Functions Create Update Rules.
7. Flag in the Field name of InfoSource on the Update rules create: Start screen.
8. Enter as InfoSource RT_IS_0RMP_C05.
9. Choose Continue.
10. Choose Activate On the Update rules create: Rules.
11. Choose Back.
12. Choose Refresh subtree to refresh the application component.
4.2.3 Executing Info packages for Real Time InfoProvider
Use
© SAP AG Page 26 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
You must customize infoProvider 0RMP_C05 so that it can be loaded with data.
Normally a Real Time InfoProvider can’t be loaded with data. It is filled with data only in the planning environment. To have plan data in the planning layouts the InfoProvider must also be provided with transactional data via flatfiles.
The steps described under Procedure must be executed for InfoProvider:
InfoProvider Description Flatfiles to Load
0RMP_C05 Merchandise Planning, Plan is a Real Time InfoCube
Flatfile_0RMP_C05_MCP_2008_BU_0001.csvFlatfile_0RMP_C05_MCP_2008_BU_0002.csvFlatfile_0RMP_C05_MCP_2009_0001.csvFlatfile_0RMP_C05_MCP_2009_0002.csv Flatfile_0RMP_C05_MCP_2009_oSeg.csvFlatfile_0RMP_C05_MCP_2010_BU_0001.csvFlatfile_0RMP_C05_MCP_2010_BU_0002.csvFlatfile_0RMP_C05_MCP_2011_BU_0001.csvFlatfile_0RMP_C05_MCP_2011_BU_0002.csvFlatfile_0RMP_C05_MP1_2009.csv
You can load the flatfiles repeatedly. However before you load them again you must delete the data request from the InfoProvider. How to do this you find in the chapter 6.5 Delete Data Requests.
Prerequisites Check the computer’s regional language setting. It must be English (United States).
For the creation of an InfoPackage you need to enter a csv-file. The flatfiles are stored on the Documentation SAP Best Practices CD in the folder \Misc\Retail\IN\Flatfiles. They must be installed on your hard disk or any of your file server.
In this chapter you load in this the flatfiles for Merchandise Planning. They are stored in the csv folder within the folders Plan_Merch.
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Choose Search.
4. Enter the following data in the upcoming screen:
Field name User action and values
Find 0RMP_C05
5. Choose Search.
6. Right click 0RMP_C05
7. Choose Change Real-Time Info Cube Load Behavior.
8. Flag the entry Real-Time Data Target can be loaded with data; planning not allowed.
9. Choose Continue.
Create InfoPackage to load the data:
1. Expand 0RMP_C05RT_IS_0RMP_C05.
2. Expand InfoSource 0RMP_C05.
© SAP AG Page 27 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
3. Expand from RT_IS_0RMP_C05 for FILE.
4. Right click RT_IS_0RMP_C05.
5. Choose Create InfoPackage.
6. In the Create InfoPackage dialog box, enter the following data:
Field name User action and values
InfoPackage Description Flatfile Load: Transactional Data 0RMP_C05
7. Select the line for RT_IS_0RMP_C05 in the section DataSource.
8. Choose Save.
9. For the InfoProviders 0RMP_C05 you may have the Monitor:Mesages creen
The InfoProvider isn’t loadable with data because it is a Real Time InfoProvider and is in planning mode. You can ignore thes message at this point, because you don’t want to load data. You only want to create InfoPackages.
10. Choose Close to close the screen and continue with the next step.
11. Choose Hide/Show Navigator.
12. Choose the tab page External data and make the following entries:
Field name Values Notes
Load external data from Client workstation
File type The flatfiles are csv files.
Name of file Use F4, input help to open the folder for your flatfiles
See the comments in the prerequisites paragraph of this chapter. Choose the first flatfile Flatfile_0RMP_C05_MCP_2008_BU_0001.csv
Data Separator , The data seperator depends on the computer’s Regional and Languages Options. The used data separator is defined for English (United States). Using not this seperator requires to recreate the flatfiles with your current regional settings. Then you have to enter this Data Seperator here.
Escape Sign " See remark for Data Seperator !
Separator for Thousands , See remark for Data Seperator !
Character used for Decimal Point
. See remark for Data Seperator !
Currency Conversion for External Systs
unflag
Number of Header Rows to be Ignored
1
13. Choose the Processing tab page and make the following entry:
Field name Value
© SAP AG Page 28 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
PSA and then into Data Targets
14. Choose the tab page Data targets and set the indicator in the Field name of Select Data Targets.
15. Select the InfoProvider 0RMP_C05 under the Field name Updating the data target.
16. Choose the tab page the Update tab page and make the following entries:
Field name Values
Update Mode Mark Full update
Data Update Type in the Data Target Mark Always update data, even if no master data exists for the data
17. Choose Save.
18. Choose Hide/Show Navigator .
19. Go to the External Data tab
20. Choose the first flatfile Flatfile_0RMP_C05_MCP_2008_BU_0001.csv. It should already have been chosen from the previous chapter.
21. Go to the Schedule tab.
22. Choose Start. You get the status message Data was requested.
23. Choose Monitor in the board.
24. Choose Refresh tree on the Monitor - Administrator Workbench screen until the status of your request is successful. That means your request obtained a green traffic light.
25. Choose Back.
26. Load the other flatfiles for the InfoProvider 0RMP_C05 the same way.
27. Choose Back.
28. Right click 0RMP_C05.
29. Choose Real-Time Info Cube Load Behavior.
30. Flag the entry Real-Time Data Target can be planned; data loading not allowed.
31. Choose Continue.
Result
Check if there are data requests with a red traffic light by using a Right click the InfoProvider and choosing Change. If there are such data requests you must change them to data requests with green traffic lights and delete them. You will find how to do this you find in Appendix C, chapter Deleting Data Requests.
4.2.4 Releasing PPW Budget
Use The purpose of this activity is to release the budget needed for the Slow Seller Management Process.
Procedure 1. First execute the following transaction to get the menu for Slow Seller Management:
Transaction code UPAR
© SAP AG Page 29 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
2. Access the activity using one of the following navigation options:
SAP BI menu Merchandise Planning Budget Monitor
Transaction code UPARI_BUDGA
3. On the Budget type tab enter the following data:
Field name Value Comment
Application 01 PPW (Price Planning Workbench) Use F4-Help
Budget Type 01 Use F4-Help
InfoObjects of Budget type
Start Date Created Date Use F4-Help
4. On the InfoObjects of Budget type tab enter the following data:
Field name Value Comment
Segment must not be filled
Fiscal year/period from XXX.2009 XXX is the current month
Fiscal year/period to 001.2011
Season from 0001
Season to 0002
5. On the Additional Filter tab enter the following data:
Field name Value
Past
Current
Future
No difference
Difference with tolerance
Difference exceeds tolerance
Planned value not yet released
Version MCP
6. Choose Execute.
7. Choose Select all to select all records.
8. Choose Release budget.
9. Choose Continue in the upcoming dialog box.
10. Choose Display Current log. A log displayed.
4.2.5 Releasing OTB Budget
Use The purpose of this activity is to release the budget needed for the Open to Buy Process.
© SAP AG Page 30 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Procedure 1. In the same way as in the previous chapter release the budget type B1 for OTB.
2. On the Budget type tab page, enter the following data:
Field name Values Comment
Application 02 OTB (Open to Buy) Use F4-Help
Budget Type B1 Use F4-Help
InfoObjects of Budget type
3. On the InfoObjects of Budget type tab page, enter the following data:
Field name Values Note
Segment Optional, must not be filled
Fiscal year/period from XXX.2009 XXX is the current month
Fiscal year/period to 012.2011
Season from 0001
Season to 0002
4. On the Additional Filter tab, enter the following data:
Field name Values
Past
Current
Future
No difference
Difference with tolerance
Difference exceeds tolerance
Planned value not yet released
Version MCP
5. Choose Execute.
6. Choose Select all to select all records.
7. Choose Release budget.
8. Choose Continue in the upcoming dialog box.
9. Choose Display Current log to see the log.
4.2.6 Assigning Price Planner Groups to Budget – SAP ECC
PrerequisitesIf 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
© SAP AG Page 31 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
1. Access the activity in the SAP ECC System using one of the following navigation options:
IMG menu Logistics Retailing Master Data Price Planning Budgets Authorization Administration for Budget Access Assign Price Planner Groups to Budget
Transaction code WRF_PPW10
2. Maintain the following entries:
Key Field names of Budget Data Values
Hierarchies node Blank
Hierarchy B1
Season 0001 and 0002
Price planner group PPW1
Add Budgets without Price planner Group to the selection flag
3. Choose Execute.
4. Mark the whole screen.
5. Choose Mass change.
6. Select the budget attributes and define the following values:
Select Budget attributes Entries
Flag Price planner group PPW1
Flag Tolerance Type 01
Flag Tolerance % 10
Flag Tolerance abs blank
7. Execute and save your result.
4.3 Assortment Planning
4.3.1 Defining Key Figures – SAP BI
Use The purpose of this activity is to define new key figures that are needed in the assortment planning scenario.
Procedure 1. Access the activity in the SAP BI System using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
© SAP AG Page 32 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
2. On the Data Warehousing Workbench: Modeling screen, choose InfoObjects
3. Follow the application path Industry Sectors Trade Industries Retailing Merchandise and Assortment Planning.
4. Right click Assortment Planning.
5. Choose Create InfoObject Catalog.
6. Enter the following data:
Field name User action and values
InfObjCat RT_AP_KEYF
Description MAP Assortment Planning Key Figures
InfoObjext Type Key Figure
7. Choose Create.
8. Choose Activate.
9. Right click the InfoObject Catalog MAP Assortment Planning Key Figures.
10. Choose Create InfoObject.
11. Enter the following data On the Create Key Figure:
Field name User action and values
KeyFig. RT_GRNNPV
Long Description Goods Receipt Cost Value, Net Net
12. Choose Continue.
13. On the Create Key Figure RT_GRNNPV: Detail screen, enter the following data
Field name User action and values
Short Description GR CV/NN
14. Enter the following data on the Type/unit tab page:
Field name User action and values
Type/Data Type Amount
Data Type CURR – Currency Field name, stored as DEC
Unit / currency 0LOC_CURRCY
15. Enter the following data on the Aggregation tab page:
Field name User action and values
Aggregation SUM
Exception Aggregat. Summation
Cumulatative val Selected
16. Enter the following data on the Additional Properties tab page:
Field name User action and values
Decimal Places Not defined
Display Not defined
Bex description Short description
© SAP AG Page 33 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
17. Choose Activate.
18. In exact the same manner create the key figures with the key figure type Amount:
Key Figure Long Description Short Description Type Unit/Currency
RT_AVP Average Price Average Price Amount 0LOC_CURRCY
RT_PP Purchase Price Purchase Price Amount 0LOC_CURRCY
RT_PPNET Purchase Price Net Purchase Price Net Amount 0LOC_CURRCY
RT_SP Target Sales Target Sales Amount 0LOC_CURRCY
RT_SPTAX Target Sales with TAX
Target Sales with TAX
Amount 0LOC_CURRCY
19. In exact the same manner create the key figures with the key figure type Integer:
Key Figure Long Description Short Description Type Unit/Currency
RT_NUMAT Number of Article Number of Article Integer empty
RT_NUMST Number of Stores Number of Stores Integer empty
20. In exact the same manner create the key figures with the key figure type Number:
Key Figure Long Description
Short Description Type Unit/Currency
RT_TAX Tax % Tax % Number empty
21. In exact the same manner create the key figures with the key figure type Quantity:
Key Figure Long Description
Short Description Type Unit/Currency
RT_QUAN Sales Quantity Sales Quantity Quantity 0BASE_UOM
RT_SQUBST Sales Quantity by Store
Sales Quantity by St
Quantity 0BASE_UOM
4.3.2 Maintaining Values for Key Figure 0RT_KEYFIG
Use The purpose of this activity is to manually maintain values for the key figure 0RT_KEYFIG. These values are needed within the assortment planning scenario.
Procedure 1. Access the activity in the SAP BI System using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoObjects.
3. Choose Search.
4. Enter the following data in the upcoming screen:
© SAP AG Page 34 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name User action and values
Find 0RT_KEYFIG
5. Choose Search.
6. Right click the InfoObject 0RT_KEYFIG.
7. Choose Maintain Master Data.
8. Enter the following data:
Field name User action and values
Language EN
9. Choose Execute.
10. Choose Create.
11. Enter the following data:
Field name User action and values
Key Figure ID IF
Short Description Initial Fix
12. Choose Continue.
13. Choose Create.
14. Enter the following data:
Field name User action and values
Key Figure ID IV
Short Description Initial Variable
15. Choose Continue.
16. Choose Save.
17. Choose Back.
4.3.3 Creating InfoProviders
4.3.3.1Creating 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:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Follow the application path Industry Sectors Trade Industries Retailing Merchandise and Assortment Planning
4. Right click the InfoArea of Assortment Planning.
© SAP AG Page 35 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
5. Choose Create InfoCube.
6. Enter the following data:
Field name User action and values
InfoCube RT_C35
Description Assortment Planning Plan, Month
InfoArea 0RT_MAPN_AP
Copy from
InfoProvider Type Standard InfoCube
Real Time Flag
7. Choose Create.
In the next window you create the following characteristics, time characteristics and key performance indicators for the InfoProvider:
● Characteristics:○ 0CM_HIEID Hierarchy ID○ 0CM_CDT1 Material group○ 0CM_CDT2 Hierarchy ID○ 0CM_CDT3 Segment○ 0DISTR_CHAN Subsegment○ 0SALESORG Store ○ 0CM_MCATDIV Industry○ 0VERSION Version○ 0RT_SEASON Season Category○ 0RT_SKUROLL Rollout○ 0RT_SEASYR Season Year○ 0RT_ASORT Assortment○ 0RF_ASTYP Assortment Type○ 0RT_KEYFIG Key Figure ID
● Time characteristics:
o 0FISCPER Fiscal year / Period
o 0FISCPER3 Posting Period
o 0FISCVARNT Fiscal Year Variant
o 0FISCYEAR Fiscal Year
● Key performance indicators:
o 0CPBAINSABU Sales / Base Unit of Measure
o 0CPBAINSAPV Sales / Cost Value
o 0CPBAINSASV Sales / Retail Value
o 0RTMARGPERC Margin %
o RT_NUMAT Number of Article
o RT_NUMST Number of Store
o RT_PP Purchase Price
o RT_PPNET Purchase Price Net
o RT_QUAN Sales Quantity
o RT_SP Target at Sales
o RT_SQUBST Sales Quantity at Store
© SAP AG Page 36 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
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
8. Open the folder Demensions and right click Dimension 1.
9. Follow the menu path Properties.
10. Enter the following data in the upcoming screen:
You can do it by copy and paste.
Field name User action and values
Description Consumer Decision Tree
11. Choose Continue.
12. Right click Dimensions..
13. Follow the context menu path Create New Dimensions:
14. Enter the following data in the screen Create Dimensions:
You can do it by copy and paste.
Field name User action and values
Description Version
15. Choose Create Another Dimension.
Enter the following data in the screen Create Dimensions:
Field name User action and values
Description Season
You can do it by copy and paste.
16. Choose Create Another Dimension.
17. Enter the following data in the screen Create Dimensions:
Field name User action and values
Description Assortment
18. Choose Create Another Dimension.
19. Enter the following data in the screen Create Dimensions:
Field name User action and values
Description Key Figure ID
20. Choose Continue.
21. Right click the dimension Time.
22. Choose InfoObject Direct Input and insert the following characteristics into the dimension Time:
© SAP AG Page 37 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
InfoObject Description
0FISCPER Fiscal Year/Period
0FISCPER3 Posting Period
0FISCVARNT Fiscal Year Variant
0FISCYEAR Fiscal Year
23. Choose 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.
24. 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
25. Insert the following characteristics into the dimension Version.You can do it by copy and paste.
InfoObject Description
0VERSION Version
26. 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
27. Insert the following characteristics into the dimension Assortment.You can do it by copy and paste.
InfoObject Description
0RT_ASORT Assortment
0RF_ASTYP Assortment Type
28. Insert the following characteristics into the dimension Key Figure ID.You can do it by copy and paste.
© SAP AG Page 38 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
InfoObject Description
0RT_KEYFIG Key Figure ID
To assign key figures to the InfoProvider proceed as follows.
29. Right click Key Figures.
30. Choose InfoObject Direct Input.
31. Insert the following key figure. You can do it by copy and paste.
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 %
32. Choose Continue.
33. Choose Activate.
4.3.4 Creating InfoSources and Transfer Rules
4.3.4.1Creating 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
© SAP AG Page 39 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoSources.
3. Follow the application path SAP Application Components SAP Sectors Trade Industries Retailing Merchandise and Assortment Planning MAP Transactional Data.
4. Right click the Application Component 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 action and values
InfoSource RT_IS_RT_C35
Long description InfoSource RT_C35
7. Choose Continue.
8. Right click the InfoSource RT_IS_RT_C35.
9. Choose Change.
10. Choose Transfer.
11. Choose Templete on the right hand side.
12. Flag in the field of InfoCube and enter RT_C35.
13. Choose Transfer.
14. Choose Transfer all InfoObjects.
15. Choose Activate.
16. Choose Yes in the upcoming dialog box.
17. Choose Back..
18. Choose Collapse to close the Communication_Struct.
19. Choose Expand to open the Transfer_strucutre/Transfer_Rules
20. Enter the following data:
Field name User action and values
Source System FILE by Choosing
25. Choose Yes in the upcoming screen Save Changes ? The system will automatically propose the transfer rules.
26. Choose Activate.
27. Choose Back.
4.3.5 Assigning 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
© SAP AG Page 40 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Choose Search and enter the following data:
Field name User action and values
Find RT_C35
4. Choose Search.
5. Right click the InfoProvider RT_C35.
6. Follow the context menu path Additional Functions Create Update Rules.
7. Flag in the field of InfoSource on the Update rules create: Start screen and enter RT_IS_RT_C35.
8. Choose Continue.
9. The next screen will show the update rule on the right hand side.
10. Choose Activate On the Update rules create: Rules.
11. Choose Back.
4.3.6 Assigning InfoPackage to InfoSources and Loading Data
Use Loading data via flatfiles into the BI System presupposes that the interface has been defined. In this chapter the last step, the creation of an InfoPackage, and the loading of transactional data is described.
The steps listed under Procedure must be executed concerning the InfoProviders in the table below. In the table you find also the flatfiles that must be loaded.
InfoProvider Description Flatfiles to Load
RT_C35 Assortment Planning Plan, Month
Flatfile_RT_C35_Fashion_2008Flatfile_RT_C35_Fashion_2009
PrerequisitesCheck the computer’s regional language setting. It must be English (United States).
For the creation of an InfoPackage you need to enter a csv-file. The flatfiles are stored on the Documentation SAP Best Practices CD in the folder \Misc\Retail\IN\Flatfiles. They must be installed on your hard disk or any of your file server. 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 41 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
4.3.6.1Assigning 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_2008Flatfile_RT_C35_Fashion_2009
You can load the flatfiles repeatedly. However before you load them again you must delete the data request from the InfoProvider. How to do this you find in the chapter 6.5 Delete Data Requests.
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Choose Search.
4. Enter the following data in the upcoming screen:
Field name User action and values
Find RT_C35
5. Choose Search.
6. Right click RT_C35.
7. Choose Change Real-Time Info Cube Load Behavior.
8. Flag the entry Real-Time Data Target can be loaded with data; planning not allowed.
9. Choose Continue.
10. Expand RT_C35RT_IS_RT_C35.
11. Expand InfoSource RT_C35.
12. Expand from RT_IS_RT_C35 for FILE.
13. Right click RT_IS_RT_C35.
14. Follow the menu path Create InfoPackage.
15. Enter the following data:
Field name User action and values
InfoPackage Description Flatfile_RT_C35_Fashion_2008
© SAP AG Page 42 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
16. Select the line for RT_IS_RT_C35 in the section DataSource.
17. Choose Save.
18. Choose Hide/Show Navigator
19. For the InfoProviders RT_C35 you may have the Monitor:Mesages screen
The InfoProvider isn’t loadable with data because it is a Real Time InfoProvider and is in planning mode. You can ignore thes message at this point, because you don’t want to load data. You only want to create InfoPackages.
20. Choose the External data tab page and make the following entries:
Field name Values Notes
Load external data from Client workstation
File type The flatfiles are csv files.
Name of file Use F4, input help to open the folder for your flatfiles
See the comments in the prerequisites paragraph of this chapter. Choose the first flatfile Flatfile_RT_C35_Fashion_2008.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
21. Choose the Processing tab page and make the following entry:
Field name Value
PSA and then into Data Targets
22. Choose the tab page the Update tab page and make the following entries:
Field name Values
Update Mode Mark Full update
Data Update Type in the Data Target Mark Always update data, even if no master data exists for the data
© SAP AG Page 43 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
23. Choose Save.
24. Go to tab tab page Schedule.
25. Choose Start. You get the status message Data was requested.
26. Choose Monitor in the board
27. Choose Refresh tree on the Monitor - Administrator Workbench screen until the status of your request is successful. That means your request obtains a green traffic light.
Be aware that if you have data requests with a red or yellow traffic light there will be no data selected in a query. You must change them to data requests with green traffic lights.
28. Choose Back
29. In this way load step by step the other flatfiles for the InfoProvider RT_C35.
Result
Be aware that if you have data requests with a red traffic there will be no data selected in a query. That means the Query RT_RTC35_Q0001 Key Figures Assortment Planning will not provide any result.
Check if there are data requests with a red traffic light by using a Right click the InfoProvider and choosing Change. If there are such data requests you must change them to data requests with green traffic lights and delete them. How to do this you find in Appendix C, chapter Deleting Data Requests.
© SAP AG Page 44 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
4.3.7 Logging on to the Query Designer
UseYou have to use the Query Designer SAP BW 3.x. To preferred method to access the Query Designer is described in the chapter Microsoft Office Start Menu 4.3.7.2. Microsoft Office Start Menu.
4.3.7.1Transaction RRMX
Procedure1. Access the activity using the following navigation:
Transaction code RRMX
That means you create a query using transaction RRMX - Analyzer and the SAP BI front end Excel from which the Query Designer can be started. You must verify that you are working with the 3.x Query Designer.
2. Choose and choose About.
If you find a screen with the following information you are working with the right version.
Otherwise you have to change settings for the BEX Analyzer. Therefore execute the next steps.
3. Choose BEx Analyzer.
4. Follow the menu path Global Settings.
5. Set the flag in the field of Launch legacy version from RRMX.
6. Repeat step (1) and (2).
7. Choose Tools.
8. Choose Query Designer.
4.3.7.2Microsoft Office Start Menu
Procedure1. Access the activity using the following navigation:
Microsoft Office Start Menu
Start All Programs Business Explorer Business Explorer (SAP BW 3.x) Query Designer (SAP BW 3.x)
© SAP AG Page 45 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
2. Log on with your user in the upcoming SAP Logon screen to the BI System.
4.3.8 Creating Queries
UsePlan 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.
PrerequisitesThe variable used in the query must be activated. Refer to chapter Activating Business Content, Query Variables.
Procedure1. Choose New Query.
2. Choose Technical Name on/off in the board.
3. Choose from the menu Industry SectorsTrade Industries Retailing Merchandise and Assortment Planning Assortment Planning
4. Double-click the InfoProvider of Assortment Planning Plan, Month RT_C35.
4.3.8.1Creating Query RT_RTC35_Q0001
ProcedureThe following two steps explain how you Drag and Drop:
1. Expand for example, the hierarchy tree of Consumer Dimension Tree. You can see several characteristics, choose Hierarchy ID.
2. Now click and hold down the Left-Mouse-Button on the node of Hierarchy ID.
3. Move the mouse into the desired frame, in our case the frame Rows.
4. Release the Left-Mouse-Button.
5. Insert via Drag and Drop the further InfoObjects into the frame Rows:
Field name Description
0CM_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
© SAP AG Page 46 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
0BASE_UOM Base Unit
6. Insert via Drag and Drop into the frame Filters:
Field name Description
0VERSION Version
0REQUID Request ID
7. Insert via Drag and Drop into the frame Columns:
Field name 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 click the node of Version in the frame Filters.
9. Choose Restrict.
10. Select the tab of Variables.
11. Right click Assortment Plan Plan Version.
12. Choose Technical Names.
13. Choose Add.
14. Choose OK.
15. Restrict in this way the InfoObject Request ID in the frame Filter with the following variable:
Variable Description Variable Represents Variable entry is
0S_RQMRC Most current data Single Value Mandatory
16. Restrict in this way the InfoObject 0CM_HIEID in the frame Rows with the following variable:
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
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
© SAP AG Page 47 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
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
Single Value Mandatory
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 name: 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
Execute the following steps to create the variable RT_PER for Posting Period.
25. Right click Posting period and choose Restrict.
26. Go to the tab page of Variables.
27. Right click No Entries Found.
28. Choose New Variable.
29. Should the screen SAP BW Variables Wizard appear, flag the message Do not display this step in the future.
30. Enter the following data :
Field names Name Value
Variable Name RT_PER
Description Posting Period
Processing by User Entry/Default Value
Characteristic Posting period(default)
© SAP AG Page 48 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
31. Choose Next.
32. Change the default values as shown in the screen shot.
Field names Name Value
Variable Represents Selection Option
Variable entry is Optional
Ready for Input Flag
33. Choose Next.
34. Choose Next.
35. Choose Exit.
36. Mark the just created variable.
37. Choose Add.
38. Choose OK.
39. Restrict the below listed InfoObjects in the frame Rows with variables that you have to create in the exact same manner as you did it in the previous steps. The properties of the variables you find here.
Variable Name Description Variable Represents Variable entry is
RT_ATYP Assortment Type Single Value Mandatory
RT_KEYF Key Figure ID Selection Option Optional
RT_LC Local Currency Selection Option Optional
40. The filter and Column frame of the query should be now as shown in the screen shot.
© SAP AG Page 49 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
41. The different characteristics in the frame Rows should be restricted as shown in the screen shot below. Check if the order in the frame Rows is the same.
42. Choose Save Query as.
43. Enter the following data:
Field name Value
Description Key Figures Assortment Planning
Technical Name RT_RTC35_Q0001
44. Choose Save.
4.3.9 Defining Message Types and Selections Options for Releasing Assortments
Use If you want to transfer assortment planning data from the SAP BI System to the SAP ECC System you must fit some settings for message type ASRTPLAN. You must assign the RFC destination and then the rollout must be mapped to the posting period.
Prerequisites The step is only possible if the planning layouts are available in your BI System.
4.3.9.1Defining Message Types
Use
© SAP AG Page 50 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Before you can release the message type ASRTPLN you must check if a RFC destination is assigned. Also check message type LOCGRP.
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu SAP Business Information Warehouse Business Planning and Simulation Planning Content Retail Analytics Release Workbench Settings Define message types
Transaction code UPARI_MSGTYPE
2. Enter the following data for message type ASRTPLN:
Field name User action and values
COM Meth O RFC
RFC Destination to <Logical system>, for example RTFCLNT100
3. Enter the same data for message type LOCGRP and OTB.
4. Choose Save.
4.3.9.2Defining Selection Options
Use Because the rollout should be mapped to the fiscal period you must replace the entry in the Selection Options.
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu SAP Business Information Warehouse Business Planning and Simulation Planning Content Retail Analytics Release Workbench Settings Define Selection Options
Transaction code UPARI_SELOP
2. Scroll down to the entry for Selection Field name is equal to S49_SERO.
3. Replace the value 0RT_SKUROLL in the column InfoObject/Field name Data by 0FISCPER3 for the entry S49_SERO. Message type is ASRTPLN.
Field name Value User action and values
Info Object/Field name 0RT_SKUROLL 0FISCPER3
4. Choose Save.
4.3.10 BADI UPARI_ASRTPLN
Use Make sure that the BADI UPARI_ASRTPLN is implemented (as mentioned in 4.3.8).
Plan values of assortment key figures can be accessed in the ECC system. Therefore a BADI has been realized. The BADI itself uses a query to get data from the InfoProvider RT_C35. Assortment Planning Plan, Month.
© SAP AG Page 51 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Procedure1. Access the activity using one of the following navigation options:
SAP BI menu SAP ECC menu Tools ABAP Workbencht Utilities Business Add-Ins Implementations
Transaction code SE19
2. In the Edit Implementation section, choose Classic BADI, and enter UPARI_ASRTPLN in the Field name of Implementation.
3. Choose Change.
4. Choose Interface tab.
5. Double-click the methods to make sure that the following coding exits in the methods.
4.3.10.1 GET_DATA_ASRTPLNmethod if_ex_upari_asrtpln~get_data_asrtpln.
* Query: RT_C35/RT_RTC35_Q0001
include upari_rel_c01.
* Infoobject 0Version (var_name = 0P_ASSP, must-Field name in query) has to* be filled
data: l_langu type sy-langu, lv_report_id type rscrmstatus-reportuid value 'RT_C35/RT_RTC35_Q0001', ls_appl_message type upari_ys_appl_msg, ls_bw_varsel type upari_ys_rscrmvarp, lt_bw_query type upari_yt_wrex_query, lt_bw_varsel type upari_yt_rscrmvarp, lt_return type table of bapiret2, lv_ofiscper3(3) type n.
Field name-symbols: <lfs_return> type bapiret2, <lfs_selopt> type upari_ys_selopt.
* initialization clear et_asrtpln[]. clear et_appl_message[]. clear lt_bw_varsel[].
* convert it_selopt into BW variable selection format loop at it_selopt assigning <lfs_selopt>. clear ls_bw_varsel.
* # structure /BIC/VRT_C312* Characteristics* # 0CM_HIEID Hierarchy ID* # 0CM_CDT3 Segment* # 0RT_ASORT Assortment
© SAP AG Page 52 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
* # 0RT_SEASON Season Category* # 0RT_SEASYR Season Year* ? 0FISCPER3 Posting period* ? RT_EQUIPB Basic Equipment OAPC* # 0BASE_UOM Base Unit of Measure* # 0LOC_CURRCY Local currency
* Key Figures* # RT_NUMAT Number of Article* # RT_NUMST Number of Stores* ? RT_SQUBST Sales Quantity by Store* ? RT_GRNNPV Goods Receipt Cost Value, Net Net* ? 0CPGRPDVPV Goods Receipt Posting Date / Vendor Cost Value* ? 0RTGRPDVST GR Posting Date / Vendor RtlT* ? 0RTGRPDVSV Goods Receipt Posting Date/Vendor Retail Value
* Selection criteria in release workbench UPARI_REL* Hierarchy Id 0CM_HIEID 0CMHIEID* Article Hierarchy Node 0CM_CDTND 0P_SEGM* Assortment type 0RF_ASTYP RT_ATYP* Season Year 0RT_SEASYR 0P_SEAY1* Season Category 0RT_SEASON 0P_SEASO* Posting Period OFISCPER3 RT_PER* Assortment 0RT_ASORT 0S_ASRT* Key Figure ID 0RT_KEYFIG RT_KEYF
case <lfs_selopt>-chanm.* '0CM_HIEID' when c_io_hieid. ls_bw_varsel-var_nam = '0CMHIEID'.
when '0CM_CDTND'. ls_bw_varsel-var_nam = '0P_SEGM'.
when '0RF_ASTYP'. ls_bw_varsel-var_nam = 'RT_ATYP'.
* '0RT_SEASYR' when c_io_seasyr. ls_bw_varsel-var_nam = '0P_SEAY1'.
* '0RT_SEASON' when c_io_season. ls_bw_varsel-var_nam = '0P_SEASO'.
when '0FISCPER3'. ls_bw_varsel-var_nam = 'RT_PER'.
* '0RT_ASORT' when c_io_assortment. ls_bw_varsel-var_nam = '0S_ASRT'.
when '0RT_KEYFIG'.
© SAP AG Page 53 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
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 = '0P_ASSP'. ls_bw_varsel-varsign = 'I'. ls_bw_varsel-varoption = 'EQ'. ls_bw_varsel-varlow = 'ASP'. ls_bw_varsel-varhigh = ''. append ls_bw_varsel to lt_bw_varsel.
* get assortment data using query to access infocube RT_C35 call function 'WREX_GET_DATA' destination i_rfc_dest exporting i_reportid = lv_report_id i_no_check = 'X' importing e_bw_langu = l_langu tables e_bw_data = et_asrtpln e_return = lt_return i_bw_varsel = lt_bw_varsel i_bw_query = lt_bw_query exceptions not_found = 1 internal_error = 2 not_consistent = 3 no_data = 4.
if sy-subrc ne 0. endif.
* copy return messages to application log format loop at lt_return assigning <lfs_return>. clear ls_appl_message. ls_appl_message-msgty = <lfs_return>-type. ls_appl_message-msgid = <lfs_return>-id. ls_appl_message-msgno = <lfs_return>-number.
© SAP AG Page 54 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
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_ASRTPLNmethod if_ex_upari_asrtpln~mapping_data_asrtpln.* sample method to map data for message content
data: l_recno type i, ls_asrtpln_content type upari_ys_asrtpln_msg, lv_rollout(2) type n.
Field name-symbols: <lfs_asrtpln> type upari_ys_wrex_data.
clear ls_asrtpln_content.
* since there is no clue whether counting of records starts with 0 or 1 take the first entry read table it_asrtpln index 1 assigning <lfs_asrtpln>. if sy-subrc = 0. l_recno = <lfs_asrtpln>-recno. endif.
loop at it_asrtpln assigning <lfs_asrtpln>.
if <lfs_asrtpln>-recno <> l_recno. append ls_asrtpln_content to et_message_content. clear ls_asrtpln_content. l_recno = <lfs_asrtpln>-recno. endif.
* What comes in? (see for reference structure /BIC/VRT_C312)* Characteristics* # 0RT_KEYFIG Kennzahl ID* # 0FISCPER3 Posting period* ? 0CM_CDT1 Category* ? 0CM_CDT2 Subcategory* # 0CM_CDT3 Segment* # 0RT_ASORT Assortment* Key Figures* # RT_GRNNPV Goods Receipt Cost Value, Net Net* # 0CPGRPDVPV Goods Receipt Posting Date / Vendor Cost Value* # 0RTGRPDVST Goods Receipt Posting Date / Vendor Retail Tax(?)
© SAP AG Page 55 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
* # 0RTGRPDVSV Goods Receipt Posting Date / Vendor Retail Value* ? RT_QUAN* # RT_NUMAT Number of Article* # RT_NUMST Number of Stores
case <lfs_asrtpln>-iobjnm.
* key figure id when '0RT_KEYFIG'. ls_asrtpln_content-key_figure_id = <lfs_asrtpln>-value.
* hierarchy id - Hiearchie ID when '0CM_HIEID'. ls_asrtpln_content-category_hierarchy_node-category_hierarchy_id = <lfs_asrtpln>-value.
* hierarchy node - Hierachie Knoten, Ebene Segment wird zugewiesen when '0CM_CDT3'. ls_asrtpln_content-category_hierarchy_node-category_hierarchy_node_id = <lfs_asrtpln>-value.
* season when '0RT_SEASON'. ls_asrtpln_content-season-season_category_code = <lfs_asrtpln>-value.
* season year when '0RT_SEASYR'. ls_asrtpln_content-season-season_year = <lfs_asrtpln>-value.
* assortment type when '0RF_ASTYP'. ls_asrtpln_content-assortment_type = <lfs_asrtpln>-value.
* assortment - Sortiment when '0RT_ASORT'. ls_asrtpln_content-assortment_id = <lfs_asrtpln>-value.
* Posting period when '0FISCPER3'. move <lfs_asrtpln>-value to lv_rollout. ls_asrtpln_content-season-season_rollout_code = lv_rollout.
* quantity when 'RT_SQUBST'. ls_asrtpln_content-target_quantity-value = <lfs_asrtpln>-value.
* base unit when '0BASE_UOM'. ls_asrtpln_content-target_quantity-unit_code = <lfs_asrtpln>-value.
* number of stores when 'RT_NUMST'. ls_asrtpln_content-number_stores_number = <lfs_asrtpln>-value.
© SAP AG Page 56 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
* 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.
* Vendor Retail Value when '0RTGRPDVSV'. ls_asrtpln_content-target_sales_retail-value = <lfs_asrtpln>-value.
** target quantities / planned totals in units* WHEN '0CPBAINSABU'.* ls_asrtpln_content-target_quantity-value = <lfs_asrtpln>-value.
* local currency - Währungsschlüssel when '0LOC_CURRCY'. ls_asrtpln_content-target_sales_cost_basic-currency_code = <lfs_asrtpln>-value. ls_asrtpln_content-target_sales_cost_net-currency_code = <lfs_asrtpln>-value. ls_asrtpln_content-target_sales_retail-currency_code = <lfs_asrtpln>-value. ls_asrtpln_content-target_sales_retail_tax-currency_code = <lfs_asrtpln>-value.
* base unit of measure - Einheit when '0BASE_UOM'. ls_asrtpln_content-target_quantity-unit_code = <lfs_asrtpln>-value.
endcase.
endloop.
if not ls_asrtpln_content is initial. append ls_asrtpln_content to et_message_content. endif.
endmethod.
4.3.10.3 MODIFY_MSG_ASRTPLNNo coding.
© SAP AG Page 57 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
4.3.10.4 SEND_RFC_ASRTPLNmethod if_ex_upari_asrtpln~send_rfc_asrtpln.
call function 'UPARI_SEND_RFC_ASRTPLN' exporting it_content_rfc = it_content_rfc i_rfcdest_to = i_rfcdest_to i_extension = i_extension importing et_appl_message = et_appl_message.
endmethod.
Check if BADI is active; otherwise activate it by choosing Activate.
4.3.11 Releasing Assortment Plan
UseAfter 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).
Procedure1. Access the transaction choosing one of the following navigation options
SAP ECC menu SAP ECC menu Business Planning and Simulation Planning Content Retail Analytics Release Workbench Start Release Workbench
Transaction code UPARI_REL
2. Set the flag Assortment Plan in the sub-screen Message Types. A new Assortment Plan tab with status red appears.
3. Set the flag in the field of Release Related Messages in the sub-screen Message Types.
4. On the General Data tab page make the following settings:
Field name User action and values
Hierarchy ID B1
Article Hierarchy Node B11120
Assortment Type FASH
5. Choose Enter. The status of the tab page General Data changes to green.
6. Go to the Assortment Plan tab. The data from the sub-screen of General Selection Criteria are taken over.
7. Enter the following data in the sub-screen of Assortment Plan Specific Selection Criteria:
© SAP AG Page 58 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name Value from Value to Comment
Season Year 2009
Season Category 0002
Posting Period 08 This is the period you planned with in the Assortment Planning scenario.
Assortment B11100_11 B11100_22 B11100_22
Key figure ID IF IV IV
8. Choose Enter. The status of the tab Assortment Plan switches to green.
9. Choose the Release Messages Immediately. After some time you get the information Release run started. You can find the results in the application log.
10. Choose Continue.
11. Choose Application Log.
12. Choose Execute.
If your transfers were successful you will get a log with status green, double-click your log you will see the number of successfully created objects and errors/warnings.
13. Choose Exit..
ResultYou have transferred the key figures Target GR at Cost Plan, Target GR At Cost net net Plan, Target GR at Retail Plan, Target GR at Retail with Tax Plan, Target Quantity Plan, Number of Stores Plan and Number of different Styles Plan from SAP BI to SAP ECC.
4.3.12 Creating Purchasing List – SAP ECC
UseThe Purchasing List shows the target key figures that you released in the Release Workbench. In order to see the released data you have to create a purchasing list.
You have to logon to the ECC system.
Procedure 1. Log on to the ECC system.
2. Access the transaction choosing one of the following navigation options:
SAP ECC menu Logistics Retailing Master Data Assortment/Listing Operational Assortment Planning and Control Create Purchasing List
Transaction code WRFAPC01
3. Enter the following data on the sub-screen of Assortment.
Field name User action and values
© SAP AG Page 59 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Hierarchy B1
Hierarchy Node B11120
Assortment Type FASH
4. Enter the following data on the sub-screen of Season.
Field name User action and values
Season year 2009
Season Category 0002
Rollout 08
5. Choose Enter.
6. Choose Yes in the upcoming screen.
7. Check the following data in the next screen:
Field name User action and values
Purchasing Org. 1000
Purch. Group 100
Sales Org. 1000
Distr. Channel 10
8. Choose Enter.
9. Choose the Target Values tab.
10. Choose Collapse in the middle of the screen to close the Overview Area.
11. You see in the first sub-screen Target Value Description the following key figures for each assortment:
Target Totals in Basic Purchase Price
Target Totals in net/net Purch. Price
Target Totals in Retail Value with Tax
12. You see in the second sub-screen Target Value Description the following key figures for each assortment:
Number of stores in assortment
Number of different articles
Target Totals in Units
13. All these data can be found in the planning layouts Distribute to IF and IV and Plan Number of different Styles in the BI system.
14. Refer to the chapters Distribute to IF and IV and Plan number of different Styles with the Assortment Planning.
ResultYou created a purchasing list and the transferred key figures are shown.
© SAP AG Page 60 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
4.3.13 OTB Check: Maintaining Document-Type Dependent Settings – SAP ECC
UseIn 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:
IMG menu Material Management Purchasing Seasonal Procurement Open-To-Buy(OTB) OTB Check: Maintain Document-Type Dependent Settings
Transaction code SPRO
3. Choose New Entries to define the OTB Check Settings.
4. Choose the document Category from the list: Purchase Order.
5. On the New Entries: Detail of Added Entries make the following entries:First Line:
Field name Description 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 Save.
7. Choose Back.
8. Choose New Entries to define the second line.
9. Choose the document Category from the list: Contract and make the following entries:
Field name Description User action and values Note
Document Type MK Choose from list
10. Choose Save.
11. Choose Back.
12. Choose New Entries to define the third line.
13. Choose the document Category from the list: Contract and make the following entries:
© SAP AG Page 61 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name Description User action and values Note
Document Type WK Choose from list
14. Choose Save.
15. Choose Back.
No other Open-To-Buy Settings for Contracts, because there would be a conflict with other scenarios!
4.4 Slow Seller Management
Use The Slow Seller Analysis is based on the result of the query 0RMP_MC21_ Q0020 Slow Seller Management Analysis.
The query gets the data from the MultiProvider 0RMP_MC21 Assortment Planning Controlling which consists of the InfoProvider 0RMP_C22 Assortment Plan, POS Sales, Week, 0RMP_C24 Assortment Plan, Stock, Week and 0RMP_C25 Assortment Plan, Plan. Only the InfoProviders 0RMP_C22 and 0RMP_C24 must be provided with data. There is no need of plan data.
The InfoProviders 0RMP_C22 Assortment Plan, POS Sales, Week and 0RMP_C24 Assortment Plan, Stock get the data from the DataStore Objects 0RMP_DS01 Stock Consolidation and 0RMP_DS02 POS Consolidation.
The DataStore Object 0RMP_DS01 Stock Consolidation and 0RMP_DS02 POS Consolidation gets the data from flatfiles. The DataStore Object 0RMP_DS01 is updated by the update rule 0RMP_DS01_2LIS_03_BF. The DataStore Object 0RMP_DS02 is updated by the update rule 0RT_PA_TRAN_CONTROL.
The Slow Seller Analysis is also based on markdown profiles. The definition of a markdown profile includes periods, one period is one week. In our scenario the two profiles are defined for 10 weeks and one for 20 weeks.
To always have a Slow Seller Analysis that provides markdown proposals the data loading via flatfiles must be executed periodically. Normally the Transactional data would be coming from your ECC System. For a refresh of the Slow Seller Analysis data you have to load three flatfiles.
1. A flatfile which provides the records in 0MAT_PLANT with a goods receipt date. The goods receipt date to a date that lies three weeks in the past.
2. A flatfile that provides the DataStore Object 0RMP_DS02 with POS Data. The posting date is
set as to a date that lies three weeks in the past.
3. A flatfile that provides the DataStore Object 0RMP_DS01 with Stock Data. The posting date is set to a date that lies three weeks in the past.
Because the goods receipt date is set to a date three weeks in the past and two profiles are only defined for 10 weeks you must refresh the data at least every seven weeks.
The steps under Procedure describe the installation of the interface and the flatfile loading.
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
© SAP AG Page 62 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
4.4.1 Generating Export DataSources
Procedure 1. Choose Search and enter the following data:
Field name User action and values
Find 0RMP_DS01
2. Choose Search.
3. Right click Stock Consolidation.
4. Follow the context menu path choose Additional Functions Generate Export DataSource.
5. Search for 0RMP_DS02, as described before.
6. Right click POS Consolidation.
7. Follow the context menu path choose Additional Functions Generate Export DataSource.
4.4.2 Install Interface “Goods Receipt Date”
4.4.2.1Creating InfoSources and Transfer Rules
UseIn this chapter the creation of an InfoSource and the Transfer Rules for the InfoObject 0MAT_PLANT is described.
Procedure 1. On the Data Warehousing Workbench: Modeling screen, choose InfoSources.
2. Follow the application path choose SAP Application Components SAP Sectors Trade Industries Retailing Merchandise and Assortment Planning MAP Transactional Data.
3. Right click the Application Component MAP Transactional Data.
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 action and values
InfoSource RT_FIRST_GR
Long description Change of the first GR Date to actual minus 3 weeks
6. Choose Continue.
7. Right click the InfoSource RT_FIRST_GR.
8. Choose Change.
9. Enter the following InfoObject in the Communication Structure frame:
InfoObject Description
0MATERIAL Article
0PLANT Store
© SAP AG Page 63 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
InfoObject Description
0RT_SSMFGR Date of First GR
10. Choose Enter.
11. Choose Activate.
12. Choose Yes in the upcoming dialog box.
13. Choose Back.
14. Choose Collapse to close the Communication_Struct.
15. Choose Expand to open the Trnasfer_structure/Transfer_Rules.
16. Enter the following data:
Field name User action and values
Source System FILE by Chooseing
17. Choose Yes in the upcoming screen Save Changes ? The system will automatically propose the transfer rules.
18. Double-click in the row for InfoObject 0RT_SSMFGR.
19. Set flag in the field of Routine.
20. Choose Create..
21. Enter the following data:
Field name User action and values
Transfer Routine Goods Receipt Date
22. Set flag in the field of No Field name.
23. Choose Continue.
24. Browse down until you see the coding line RESULT = .
25. Replace this line by RESULT = sy-datum - 21.
26. Choose Check.
27. Choose Save if there are no syntax errors.
28. Choose Continue.
29. Choose Activate.
30. Choose Back.
4.4.2.2Assigning Update Rules to InfoObject
UseIn this chapter the creation of a new update rule for InfoObject 0MAT_PLANT is described.
Procedure1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Choose Search and enter the following data:
© SAP AG Page 64 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name User action and values
Find 0MAT_PLANT
4. Choose Search.
5. Expand Store Article.
6. Right click Store Article (Attribute).
7. Follow the context menu path choose Additional Functions Create Update Rules.
8. Set flag in the field of InfoSource.
9. On the Update rules create: Start and enter RT_FIRST_GR.
10. Choose Continue in the up coming screen.
11. Double-click a key figure, for example ABC indicator.
12. Choose the tap page of Key Field names.
13. Choose Blank in the row for Store Article.
14. Set flag in the field of Source Chars.
15. Choose 0MATERIAL by using the F4 Help.
16. Choose Transfer
17. Choose Yes in the upcoming screen..
18. Choose Transfer.
19. Choose Activate On the Update rules create: Rules.
20. Choose Back.
4.4.2.3Assigning 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.csvFlatfile_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\IN\Flatfiles. They must be installed on your hard disk or any of your file server. An installation in this way is important because you have defined in the InfoPackage that an external load takes place from a client workstation.
In this chapter you load 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:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
© SAP AG Page 65 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
2. On the Data Warehousing Workbench: Modeling screen, choose InfoSources.
3. Choose Search.
4. Enter the following data in the upcoming screen:
Field name User action and values
Find RT_FIRST_GR
5. Open the folder of Change of the first GR Date to actual minus 3 weeks.
6. Open the folder of from RT_FIRST_GR for FILE.
7. Right click RT_FIRST_GR.
8. Follow the menu path choose Create InfoPackage.
9. Enter the following data:
Field name User action and values
InfoPackage Description Flatfile Load: RT_FIRST_GR
10. Select the line for RT_FIRST_GR in the section DataSource.
11. Choose Save.
12. Choose Hide/Show Navigator.
13. Choose the External data tab and make the following entries:
Field name Values Notes
Load external data from Client workstation
File type The flatfiles are csv files.
Name of file Use F4, input help to open the folder for your flatfiles
See the comments in the prerequisites paragraph of this chapter. Choose the first flatfile Flatfile_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 !
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:
© SAP AG Page 66 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name Value
PSA and then into Data Targets
15. Choose the Data targets tab and set flag in the field of Select Data Targets.
16. Select the InfoProvider 0MAT_PLANT under the Field name Updating the data target.
17. Choose the Update tab and make the following entries:
Field name Values
Update Mode Mark Full update
Data Update Type in the Data Target Mark Always update data, even if no master data exists for the data
18. Choose Save.
4.4.3 Loading Goods Receipt Dates into 0MAT_PLANT
Use The flatfiles you load here in the BI System update the first goods receipt attribute in the InfoObject 0MAT_PLANT. You have to load the following flatfiles to update all the necessary articles used in the Slow Seller Analysis.
InfoObject Description First Flatfiles to Load
0MAT_PLANT Article Store Flatfile_MATPLANT_GR_DAT_Fashion.csvFlatfile_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\IN\Flatfiles. They must be installed on your hard disk or any of your file server. An installation in this way is important because you have defined in the InfoPackage that an external load takes place from a client workstation.
In this chapter you load 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:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoSources.
3. Choose Search.
4. Enter the following data in the upcoming screen:
Field name User action and values
Find RT_FIRST_GR
5. Open the folder of Change of the first GR Date to actual minus 3 weeks.
© SAP AG Page 67 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
6. Open the folder of from RT_FIRST_GR for FILE.
7. Right click RT_FIRST_GR.
8. Double-click Flatfile load: RT_FIRST_GR.
9. Choose 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 Start. You get the status message Data was requested.
14. Choose Monitor in the board
15. Choose Refresh tree on the Monitor - Administrator Workbench screen until the status of your request is successful. That means your request obtains a green traffic light.
16. Choose Back.
17. In this way load the other flatfile for the InfoObject 0MAT_PLANT.
18. Choose Back.
4.4.4 Install Interface “ POS and Stock Data SSM“
Use In this chapter the necessary installation steps for loading POS Data and Stock Data are described.
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.1Creating 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:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. Move to the DataSources area in the modeling navigation in the left hand frame.
3. Choose Choose Source System.
© SAP AG Page 68 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
4. Follow the path choose File File (FILE).
5. From the application menu choose SAP Application Components SAP Sectors Trade Industries Retailing.
6. Right click the application component Retailing.
7. Choose Create application component.
8. Enter the following data in the dialog box Create Application Components:
Field name User action and values
Application Comp. ZRT_SSM
Long Description Transactional Data SSM
9. Choose Continue to create the application component.
4.4.4.2Creating 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.csvFlatfile_0RMP_DS02_POS_Hardgoods.csv
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. Move to the DataSources area in the modeling navigation in the left hand frame.
3. From the application menu, choose SAP Application Component SAP Sectors Trade Industries Retailing.
4. Right click the application component Transactional Data SSM.
5. Choose Create DataSource.
6. Enter the following data in the dialog box Create DataSource:
Field name User action and values Notes
DataSource RT_DS_0RMP_DS02
Source System FILE automatically filled
Data Type DataSource Transaction Data
7. Choose Transfer.
8. Choose Hide/Show Navigator.
9. Enter the following data on the tap page General Info:
© SAP AG Page 69 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name User action and values
Short description POS Data SSM
Medium description POS Data SSM
Long description POS Data SSM
10. Enter the following data on the tap page Extraction :
Field name User action and values
Delta Process Full upload (Delta from InfoPackage Selection Only)
Direct Access NO DTP Allowed for Direct Access
Real Time Real-Tile Data Acquisition is not supported
Adapter Load Text-Type File from Local Workstation
Name of File Flatfile_0RMP_DS02_POS_Fashion.csv
Header Rows to be ignored 2
Character Set Settings Default Settings
Data Format Separated with Separator (for example, CSV)
Data Seperator ,
Escape Sign “
Convers. Language User Master Record
Number Format User Master Record
11. Enter the following data on the tap page Proposal:
Field name User action and values
No. of Data Record 3
12. Choose Load Example Data.
13. Go to to the Field names tab.
14. Flag the message Do not Show This Question Again in This Session and choose Yes in the upcoming screen.
15. Enter in the column InfoTemplate the values you find in the following table:
Pos Field names InfoTemplate
1 RT_LOCATIO 0RT_LOCATIO
2 BUSINESSDAYDATE 0RPA_BDD
3 RPA_TTC 0RPA_TTC
4 RPA_WID 0RPA_WID
5 RPA_TNR 0RPA_TNR
6 RPA_DEP 0RPA_DEP
7 RPA_OID 0RPA_OID
8 DOC_CURRCY 0DOC_CURRCY
9 RPA_PQU 0RPA_PQU
© SAP AG Page 70 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Pos Field names InfoTemplate
10 RPA_PAI 0RPA_PAI
11 MATERIAL 0MATERIAL
12 MATL_GROUP 0MATL_GROUP
13 BASE_QTY 0BASE_QTY
14 BASE_UOM 0BASE_UOM
16. Choose Enter.
17. Replace RPA_BDD by BUSINESSDAYDATE.
18. Choose Enter.
19. Choose Next Page and scoll down to get a view in which the column Info Template is empty
20. Enter in the column InfoTemplate the values you find in the following table:
Pos Field names InfoTemplate
15 TRANSACTIONINDEX 0RPA_TIX
16 TRANSTYPEGROUP 0RPA_TRG
17 BUSINESSTRANSACT 0RPA_BTY
18 REVERSALINDICATO 0RPA_RFL
19 TRAININGTRANSACT 0RPA_TRF
20 SALESITEMNUMBER 0RPA_RSN
21 SALESITEMTYPE 0RPA_RTC
22 POSTRANSW/OPOST 0RPA_KOF
23 REASON 0RPA_RRC
24 QUALIFITEMIDENT 0RPA_IQU
25 EAN/UPC 0EANUPC
26 SALESQTYINSUN 0RPA_RLQ
27 SALESUNIT 0SALES_UNIT
28 SALESRETAILVALUE 0RPA_SAT
21. Choose Enter.
22. Choose Next Page and scoll down to get a view in which the column Info Template is empty.
23. Enter in the column InfoTemplate the values you find in the following table:
Pos Field names 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
© SAP AG Page 71 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Pos Field names InfoTemplate
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
24. Choose Enter.
25. Choose Next Page and scoll down to get a view in which the column Info Template is empty.
26. Enter in the column InfoTemplate the values you find in the following table
Pos Field names 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
27. Choose Enter.
28. Choose Next Page and scoll down to get a view in which the column Info Template is empty.
29. Enter in the column InfoTemplate the values you find in the following table
Pos Field names 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
© SAP AG Page 72 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Pos Field names InfoTemplate
62 DATETO 0DATETO
63 RPA_CHN 0RPA_CHN
64 RPA_ACO 0RPA_ACO
65 RPA_ATI 0RPA_ATI
66 RPA_AMC 0RPA_AMC
67 RPA_ADT1 0RPA_ADT1
68 RPA_ADT2 0RPA_ADT2
69 RPA_MID 0RPA_MID
70 RPA_ACD 0RPA_ACD
30. Choose Enter.
31. Choose Next Page and scoll down to get a view in which the column Info Template is empty.
32. Enter in the column InfoTemplate the values you find in the following table
Pos Field names 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
33. Choose Enter.
34. Choose Next Page and scoll down to get a view in which the column Info Template is empty.
35. Enter in the column InfoTemplate the values you find in the following table
Pos Field names InfoTemplate
85 RPA_RQU 0RPA_RQU
86 RPA_OQU 0RPA_OQU
87 RPA_RDF 0RPA_RDF
88 RPA_DDI 0RPA_DDI
© SAP AG Page 73 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Pos Field names 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
36. Choose Enter..
37. Choose Next Page and scoll down to get a view in which the column Info Template is empty.
38. Enter in the column InfoTemplate the values you find in the following table
Pos Field names 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
39. Choose Enter.
40. Choose Next Page.
41. Enter in the column InfoTemplate the values you find in the following table:
Pos Field names InfoTemplate
113 RPA_IT5 0RPA_IT5
114 RPA_EI0 0RPA_EI0
115 RPA_EI1 0RPA_EI1
© SAP AG Page 74 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Pos Field names InfoTemplate
116 RPA_EQU 0RPA_EQU
117 RECORDMODE 0RECORDMODE
118 RPA_RRG 0RPA_RRG
119 RPA_TRC 0RPA_TRC
42. Choose Enter.
43. Choose Activate.
44. Ignore the yellow warnings and choose Continue.
45. Choose Back.
4.4.4.3Creating 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.csvFlatfile_0RMP_DS01_GR_Hardgoods.csv
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. Move to DataSources area in the modeling navigation in the left hand frame.
3. Choose from the application path SAP Application Component SAP Sectors Trade Industries Retailing.
4. Right click the application component Transactional Data SSM.
5. Choose Create DataSource.
6. Enter the following data in the dialog box Create DataSource:
Field name User action and values Notes
DataSource RT_DS_0RMP_DS01
Source System FILE automatically filled
Data Type DataSource Transaction Data
7. Choose Transfer.
8. Choose Hide/Show Navigator.
9. Enter the following data on the tap page General Info:
© SAP AG Page 75 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name User action and values
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 action and values
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
11. Enter the following data on the tap page Proposal:
Field name User action and values
No. of Data Record 3
12. Choose Load Example Data.
13. Change to the tab page Field names:
14. Enter in the column Field names and InfoTemplate the values you find in the following table and overwriting existing values in the column Field name:
Pos Field names 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
© SAP AG Page 76 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Pos Field names InfoTemplate
10 MOVETYPE 0MOVETYPE
11 STOCKRELEV 0STOCKRELEV
12 CPPVLC 0CPPVLC
13 CPSVLC 0CPSVLC
14 CPSTLC 0CPSTLC
15. Choose Enter.
16. Choose Next Page and scoll down to get a view in which the column Info Template is empty.
17. Enter in the column Field names and InfoTemplate the values you find in the following table and overwriting existing values in the column Field name:
Pos Field names 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
22 SOLD_TO 0SOLD_TO
23 WHSE_NUM 0WHSE_NUM
24 STOR_LOC 0STOR_LOC
25 STRGE_BIN 0STRGE_BIN
26 STRGE_TYPE 0STRGE_TYPE
27 VENDOR 0VENDOR
28 MATERIAL 0MATERIAL
18. Choose Enter.
19. Choose Next Page and scoll down until you get a view in which the column Info Template is empty.
20. Choose Insert Row so often until you get a view in which only lines exist that can be filled with data.
21. Enter in the column Field names and InfoTemplate the values you find in the following table and overwriting existing values in the column Field name:
Pos Field names InfoTemplate
29 DOC_NUM 0DOC_NUM
30 BASE_UOM 0BASE_UOM
31 DOC_YEAR 0DOC_YEAR
32 PROFIT_CTR 0PROFIT_CTR
© SAP AG Page 77 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Pos Field names InfoTemplate
33 DCINDIC 0DCINDIC
34 LOC_CURRCY 0LOC_CURRCY
35 PLANT 0PLANT
36 FISCVARNT 0FISCVARNT
37 CPNOITEMS 0CPNOITEMS
38 CO_AREA 0CO_AREA
39 DOC_ITEM 0DOC_ITEM
40 VALUE_LC 0VALUE_LC
41 COORDER 0COORDER
42 QUANT_B 0QUANT_B
22. Choose Enter.
23. Choose Insert Row 14 times
24. Choose Next Page and scoll down to get a view in which the column Info Template is empty
25. Enter in the column InfoTemplate the values you find in the following table
Pos Field names 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
26. Choose Enter.
27. Choose Activate.
28. Ignore the yellow warnings and choose Continue.
29. Choose Back.
4.4.4.4Loading 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:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. Move to the DataSources area in the modeling navigation in the left hand frame.
© SAP AG Page 78 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
3. Choose from the application path SAP Application Component SAP Sectors Trade Industries Retailing Transactional Data SSM.
4. Right click the DataSource POS Data SSM.
5. Choose Create InfoPackage.
6. In the Create InfoPackage dialog box, enter the following data:
Field name User action and values
InfoPackage Description Flatfile Load: Transactional Data 0RMP_DS02
7. Select the line with the information of POS Data SSM RT_DS_ORMP_DS02 in the section of DataSource.
8. Choose Save.
9. Choose 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 Start.
14. Go back to the tab page Extraction.
15. Select the other flatfile.
16. Go to the tab page Schedule.
17. Choose Start.
18. Choose Back.
19. Right click POS Data SSM.
20. Choose Manage. You can see the both data requests. If you want to reload the flatfiles you have to delete the both data requests.
21. Choose Cancel.
22. In the same way create the InfoPackage for the ODS Object 0RMP_DS01.
23. In the same way load the flatfiles for the ODS Object 0RMP_DS01.
4.4.4.5Loading 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 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
© SAP AG Page 79 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
4.4.4.6Creating Transformation for ODS Objects 0RMP_DS02
Procedure 1. Choose Search and enter the following data:
Field name User action and values
Find 0RMP_DS02
2. Choose Search.
3. Expand POS Consolidation.
4. Expand TRCS 0RT_PA_TRAN_CONTROL_TR -> ODSO 0RMP_DS02.
5. Right click POS Analytics: Retail Control.
6. Choose Create Transformation.
7. Enter the following data in the sub-screen of Target of the Transformation:
Field name User action and values
Object Type
Name 0RT_PA_TRAN_CONTROL_TR
8. Enter the following data in the sub-screen of Source of the Transformation:
Field name User action and values
Object Type DataSource
DataSource RT_DS_0RMP_DS02
Source System FILE
9. Choose Create Transformation.
10. Choose Save.
11. Choose Hide/Show Navigator.
Maintain Start Routine
12. Choose Start Rountine
13. Replace the coding template by *$*$ begin of routine - insert your code only below this line *-* DATA: wa_SOURCE_PACKAGE LIKE LINE OF SOURCE_PACKAGE.
LOOP AT SOURCE_PACKAGE INTO wa_SOURCE_PACKAGE. wa_SOURCE_PACKAGE-BUSINESSDAYDATE = sy-datum - 21. modify SOURCE_PACKAGE from wa_SOURCE_PACKAGE.
ENDLOOP.
14. Choose Check to be sure that there are no syntax errors
15. Choose Save.
Maintain Routine for INFOOBJECT 0FISCPER
16. Double-click the row with the information below:
0FISCPER 151 0FISCPER Fiscal year/period
17. Choose Add Source Field names in the sub-screen of Source Field names of Rule
18. Select the field name of BUSINESSDAYDATE.
© SAP AG Page 80 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
10. Choose Copy.
19. Select Routine in the field of Rule Type.
20. 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_FIELD NAMES-BUSINESSDAYDATE IMPORTING e_fper1 = RESULT CHANGING ct_monitor = MONITOR. CATCH /rtf/cx_time. RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD. ENDTRY.
21. Choose Check to be sure that there are no syntax errors.
22. Choose Save.
23. Enter as description Routine: Fiscal Year/Period from BUSINESSDAYDATE.
24. Choose Transfer Values in the upcoming screen.
Maintain Routine for INFOOBJECT 0FISCVARNT
25. Double-click the row with the information below:
0FISCVARNT 152 0FISCVARNT Fiscal year variant
26. Choose Add Source Field names in the sub-screen of Source Field names of Rule.
27. Select the field name of BUSINESSDAYDATE.
28. Choose Copy.
29. Select Routine in the field name of Rule Type.
30. 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_FIELD NAMES-BUSINESSDAYDATE IMPORTING e_fiscyv1 = RESULT CHANGING ct_monitor = MONITOR. CATCH /rtf/cx_time. RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD. ENDTRY.
31. Choose Check to be sure that there are no syntax errors.
32. Choose Save.
33. Enter as description Routine: Fiscal Year Variant from BUSINESSDAYDATE.
34. Choose Transfer Values.
Maintain Routine for INFOOBJECT 0FISCPER3
35. Double-click the row with the information below:
0FISCPER 3 153 0FISCPER3 Posting period
36. Choose Add Source Field names in the sub-screen of Source Field names of Rule.
37. Select the field name of BUSINESSDAYDATE.
© SAP AG Page 81 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
38. Choose Copy.
39. Select Time Characteristic in the Field name of Rule Type.
40. Enter as description Routine: Posting Period from Start Routine.
41. Choose Transfer Values.
Maintain Routine for INFOOBJECT 0FISCYEAR
42. Double-click the row with the information below:
0FISCYEAR 154 0FISCYEAR
43. Choose Add Source Field names in the sub-screen of Source Field names of Rule.
44. Select the field name of BUSINESSDAYDATE.
45. Choose Copy.
46. Select Time Characteristic in the field name of Rule Type.
47. Enter as description Routine: Fiscal Year from Start Routine.
48. Choose Transfer Values.
Maintain Routine for INFOOBJECT 0RT_MTFYVRN
49. Double-click the row with the information below:
0RT_MTFYVRN 155 0RT_MTFYVRN
50. Choose Add Source Field names in the sub screen Source Field names of Rule.
51. Select the Field name BUSINESSDAYDATE.
52. Choose Copy.
53. Select Routine in the field name of Rule Type.
54. 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_FIELD NAMES-BUSINESSDAYDATE IMPORTING e_fiscyv2 = RESULT CHANGING ct_monitor = MONITOR. CATCH /rtf/cx_time. RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD. ENDTRY.
55. Choose Check to be sure that there are no syntax errors.
56. Choose Save.
57. Enter as description Routine MAP: Approximate Fiscal Year Variant from BDD.
58. Choose Transfer Values.
Maintain Routine for INFOOBJECT 0RT_QTFYVRN
59. Double-click the row with the information below:
0RT_QTFYVRN 156 0RT_QTFYVRN
60. Choose Add Source Field names in the sub screen Source Field names of Rule.
61. Select the Field name BUSINESSDAYDATE.
62. Choose Copy.
63. Select Routine in the Field name of Rule Type.
64. Replace the coding template by
© SAP AG Page 82 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
*$*$ begin of routine - insert your code only below this line *-* TRY. CALL METHOD /rtf/cl_time=>get_retail_fpers_from_date EXPORTING i_date = SOURCE_FIELD NAMES-BUSINESSDAYDATE IMPORTING e_fiscyv3 = RESULT CHANGING ct_monitor = MONITOR. CATCH /rtf/cx_time. RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD. ENDTRY.
65. Choose Check to be sure that there are no syntax errors.
66. Choose Save.
67. Enter as description Routine: Approximate Fiscal Year Variant from BDD.
68. Choose Transfer Values..
Maintain Routine for INFOOBJECT 0RT_MTFPER
69. Double-click the row with the information below:
Approximate Fiscal Year Period from BDD
157 0RT_MTFPER
70. Choose Add Source Field names in the sub-screen of Source Field names of Rule.
71. Select the Field name BUSINESSDAYDATE.
72. Choose Copy.
73. Select Routine in the Field name of Rule Type..
74. 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_FIELD NAMES-BUSINESSDAYDATE IMPORTING e_fper2 = RESULT CHANGING ct_monitor = MONITOR. CATCH /rtf/cx_time. RAISE EXCEPTION TYPE CX_RSROUT_SKIP_RECORD. ENDTRY.
75. Choose Check to be sure that there are no syntax errors.
76. Choose Save.
77. Enter as description Routine: Approximate Fiscal Year Period from BDD.
78. Choose Transfer Values.
79. Choose Activate.
80. Choose Back.
4.4.4.7Creating Transformation for ODS Objects 0RMP_DS01
Procedure 1. Choose Search and enter the following data:
© SAP AG Page 83 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name User action and values
Find 0RMP_DS01
2. Choose Search.
3. Expand Stock Consolidation.
4. Expand TRCS 2LIS_03_BF_TR -> ODSO 0RMP_DS01.
5. Right click 2LIS_03_BF_TR.
6. Choose Create Transformation.
7. Enter the following data in the sub-screen of Target of the Transformation:
Field name User action and values
Object Type
Name 2LIS_03_BF_TR
8. Enter the following data in the sub-screen of Source of the Transformation:
Field name User action and values
Object Type DataSource
DataSource RT_DS_0RMP_DS01
Source System FILE
9. Choose Create Transformation.
10. Choose Save.
11. Choose Hide/Show Navigator.
Maintain Start Routine
12. Choose Start Routine.
13. Replace the coding template by *$*$ begin of routine - insert your code only below this line *-* DATA: wa_SOURCE_PACKAGE LIKE LINE OF SOURCE_PACKAGE.
LOOP AT SOURCE_PACKAGE INTO wa_SOURCE_PACKAGE. wa_SOURCE_PACKAGE-DOC_DATE = sy-datum - 21. wa_SOURCE_PACKAGE-PSTNG_DATE = sy-datum - 21. modify SOURCE_PACKAGE from wa_SOURCE_PACKAGE. ENDLOOP.
14. Choose Check to be sure that there are no syntax errors.
15. Choose Save.
16. Choose Activate.
17. Choose Back.
4.4.5 Loading POS and Stock Data into ODS Objects
4.4.5.1Creating Data Transfer Process for ODS Objects 0RMP_DS02
Procedure 1. Right click POS Consolidation.
2. Choose Create Data Transfer Process.
© SAP AG Page 84 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
3. Execute the F4 Help of the Field name DataSource.
4. Choose the DataSource RT_DS_0RMP_DS02 as shown in the following screenshot:
5. Choose Continue.
6. Enter the following data on the tab page Extraction:
Field name User action and values
Extraction Mode Full
7. Go to the tab page Execute.
8. Choose Activate.
9. Choose Execute.
10. Choose Yes in the upcoming screen if you want to enter the monitor, otherwise No.
11. Choose Refresh to see that there is a green data transfer process.
12. Choose Back.
13. Right click POS Consolidation.
Before you activate the data please check if the data request of the ODS Object has a green traffic. Otherwise delete the data request and execute the data transfer process again. You can repeat these steps as often you want.
14. Choose Activate Data.
15. Select the green data request.
16. Choose Start.
17. Choose Refresh to see that the request is disappeared from the data request list.
4.4.5.2Creating Data Transfer Process for ODS Objects 0RMP_DS01
Procedure 1. Right click Stock Consolidation.
2. Choose Create Data Transfer Process.
3. Execute the F4 Help of the Field name DataSource.
4. Choose the DataSource RT_DS_0RMP_DS01 as shown in the following screenshot:
5. Choose Continue.
6. Enter the following data on the tab page Extraction:
Field name User action and values
Extraction Mode Full
© SAP AG Page 85 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
7. Go to the Execute tab.
8. Choose Activate.
9. Choose Execute.
10. Choose Yes in the upcoming screen if you want to enter the monitor, otherwise No.
11. Choose Refresh to see that there is a green data transfer process.
12. Choose Back.
13. Right click Stock Consolidation
Before you activate the data please check if the data request of the ODS Object has a green traffic light. Otherwise delete the data request and execute the data transfer process again. You can repeat these steps as often you want.
14. Choose Activate Data.
15. Select the green data request.
16. Choose Start.
17. Choose Refresh to see that the request is disappeared from the data request list.
4.4.6 Loading POS and Stock Data into InfoProviders
Use The update of the InfoProvider 0RMP_C22 and 0RMP_C24 is a manually step. Before you execute the update you must check that there is no data request in the InfoProviders
How to delete a data requests from the InfoProviders you can findout in in chapter 6.
Procedure 1. Choose Search and enter the following data:
Field name User action and values
Find 0RMP_DS01
2. Choose Search.
3. Right click Stock Consolidation.
4. Follow the context menu path Additional functions Update 3.x Data to Targets.
5. Flag Full Update.
6. Choose Update.
7. Go to the tab page Data Targets.
8. Flag Select Data Targets.
9. Select the InfoProviders with the Technical name 0RMP_C24 under the Field name Updating the data target.
10. Go back to the Schedule tab.
11. Choose Start.
12. Choose Monitor in the board.
13. Choose Refresh tree on the Monitor - Administrator Workbench screen until the status of your request is successful. That means your request obtains a green traffic light.
14. Choose Back.
15. Search for 0RMP_DS02, as described before.
16. Right click POS Consolidation.
© SAP AG Page 86 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
17. Follow the context menu path Additional functions Update 3.x Data to Targets.
18. Flag Full Update.
19. Choose Update.
20. Go to the tab page Data Targets.
21. Flag Select Data Targets
22. Select the InfoProviders with the Technical name 0RMP_C22 under the Field name Updating the data target.
23. Go back to the Schedule tab.
24. Choose Start.
25. Choose Monitor in the board.
26. Choose Refresh tree on the Monitor - Administrator Workbench screen until the status of your request is successful. That means your request obtains a green traffic light.
27. Choose Back.
Result
Be aware that if you have data requests with a red traffic there will be no data selected in a query. Check if there are such data requests. You must change them to data requests with green traffic lights and delete them. How to do this you find in Appendix C, chapter Deleting Data Requests.
If you have here data requests with red traffic light the Slow Seller Analysis that you execute by using the transaction /MAP/SSM2 would not provide any result because it is calling the query 0RMP_MC21_Q0020 Slow Seller Management Analysis.
4.4.7 Reloading POS and Stock Data SSMIf you want to reload the flatfiles you have to delete the data request in the InfoProviders 0RMP_C24 and 0RMP_C22, in the ODS Objects 0RMP_DS01 and 0RMP_DS02 and in the DataSources of POS Data SSM and Stock Data SSM
4.4.8 Applying Hierarchy/Attribute Change
UseIf 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.
Procedure1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
© SAP AG Page 87 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Follow the path choose Tools Apply Hierarchy/Attribute Change starting in the board
4. Choose InfoObjectList.
5. There could be entries like:
Description InfoObject
Store Article 0MAT_PLANT
6. Choose Save InfoObject List.
7. Choose Execute.
8. Choose Refresh until you get the message Hierarchy/Attribute Change Is Finished.
4.5 Allocation
4.5.1 Creating InfoAreas
Use The purpose of this activity is to create an InfoArea as a method to structure data containers like InfoProviders and their respective data paths.
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Follow the application path choose Industry Sectors Trade IndustriesRetailing.
4. Right click the InfoArea Retailing.
5. Choose Create InfoArea.
6. Enter the following data in the dialog box Create InfoArea:
Field name User action and values
Info Area RT_ALLOC
Long Description Allocation
7. Choose Continue to create the InfoArea.
4.5.2 Creating InfoProviders
Use The purpose of this activity is to create an InfoProvider in which the data from a source system will be stored.
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse
© SAP AG Page 88 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Follow the path choose Industry SectorsTrade Industries Retailing.
4. Right click the InfoArea Allocation - RT_ALLOC.
5. Choose Create InfoCube.
6. Enter the following data:
Field name User action and values
InfoCube RT_C01
Description Allocation Strategy
InfoArea RT_ALLOC
InfoProvider Type Standard InfoCube
7. Choose Create.
8. In the next window you create the following time characteristics, unit characteristics, characteristics and key performance indicators for the InfoProvider:
● Characteristics:○ 0MATERIAL Material○ 0MATL_GROUP Material group○ 0CM_HIEID Hierarchy ID○ 0CM_CDT3 Segment○ 0CM_CDT4 Subsegment○ 0PLANT Store ○ 0RT_SEASON Season category○ 0RT_PRBAND Price Band Category
● Time characteristics:○ 0CALMONTH Calendar year/Month
● Key performance indicators:○ 0CPSAEXCUSU Absolute Sales / SUn
9. Right click Dimension 1.
10. Follow the menu path Properties.
11. Enter the following data in the upcoming screen:
Field name User action and values
Description Article
12. Choose Continue.
13. Right click Dimensions
14. Follow the context menu path Create New Dimensions.
15. Enter in the screen Create Dimensions the following data:
Field name User action and values
Description Store
16. Choose Create Another Dimension.
17. Enter in the screen Create Dimensions the following data:
© SAP AG Page 89 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name User action and values
Description Consumer
18. Choose Create Another Dimension.
19. Enter in the screen Create Dimensions the following data:
Field name User action and values
Season Season
20. Choose Continue.
21. Right click the dimension Time.
22. Choose InfoObject Direct Input.
23. Insert the following characteristics into the dimension Time:
InfoObject Description
0CALMONTH Calendar Year / Month
24. Choose Continue.
25. To fill the dimension Article, Store, Consumer and Season with characteristics act in the same way as for the dimension Time.
Insert the following characteristics into the dimension Article:
InfoObject Description
0MATERIAL Material
0MATL_GROUP Material Group
Insert the following characteristics into the dimension Store:
InfoObject Description
0PLANT Store
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.
26. Right click Key Figures.
27. Choose InfoObject Direct Input.
28. Insert the following key figure:
InfoObject Description
0CPSAEXCUSU Absolute Sales / SUn
© SAP AG Page 90 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
29. Choose Continue.
30. Choose Activate.
4.5.3 Creating Application Components
Use The purpose of this activity is to create an Application Component as a structure element in the InfoSources tree.
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoSources.
3. Follow the application path choose SAP Application Components SAP Sectors Trade Industries Retailing.
4. Right click the application component Retailing.
5. Choose Create application component.
6. In the following screen, enter the following data:
Field name User action and values
Application Component ZRT_ALLOC
Long Description Allocation
7. Select Continue.
4.5.4 Creating 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:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoSources.
3. Follow the application path choose SAP Application Components SAP Sectors Trade Industries Retailing.
4. Right click 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:
© SAP AG Page 91 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name User action and values
InfoSource RT_IS_RT_C01
Long description InfoSource RT_C01
7. Choose Continue.
8. Right click the newly created InfoSource RT_IS_RT_C01.
9. Choose Change.
10. Choose Transfer.
11. Choose Template on the right hand side.
12. Flag the field of InfoCube and enter RT_C01.
13. Choose Transfer
14. Choose Transfer all InfoObjects
15. Choose Activate.
16. Choose Yes in the upcoming dialog box.
17. Choose Back.
18. Choose Collapse to close the Communication_Struct
19. Choose Expand to open the Transfer_structure/Transfer_Rules.
20. Enter the following data:
Field name User action and values
Source System FILE by Chooseing
21. Choose Yes in the upcoming screen Save Changes? The system will automatically propose the transfer rules.
22. Choose Activate.
23. Choose Back.
4.5.5 Assigning 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.
Procedure1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Choose Search and enter the following data:
4. Enter the following data:
Field name User action and values
Find RT_C01
© SAP AG Page 92 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
5. Choose Search.
6. Right click the InfoProvider RT_C01
7. Follow the context menu path Additional Functions Create Update Rules.
8. Flag the field of InfoSource on the Update rules create: Start.screen.
9. Enter as Info Source RT_IS_RT_C01.
10. Choose Continue.
11. Choose Activate On the Update rules create: Rules.
12. Choose Back.
4.5.6 Assigning InfoPackage to InfoSources and Loading Data
Use The purpose of this activity is to assign InfoPackages to InfoSources with which you can load data into the InfoProvider RT_C01. The table below lists the flatfiles that have to load.
InfoProvider Description Flatfiles to Load
RT_C01 Allocation Strategy Flatfile_RT_C01_2008.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 Doku CD SAP Best Practices in the folder \Misc\Retail\IN\Flatfiles. They must be installed on your hard disk or any of your file server. An installation in this way is important because you have defined in the InfoPackage that an external load takes place from a client workstation.
You load in this chapter the flatfiles for Merchandise and Store Planning. They are stored in the csv folder within the folder Allocation.
Procedure 1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Choose Search.
4. Enter the following data in the upcoming screen:
Field name User action and values
Find RT_C01
5. Choose Search.
6. Expand RT_C01RT_IS_RT_C01.
7. Expand InfoSource RT_C01.
8. Expand from RT_IS_RT_C01 for FILE.
9. Right click RT_IS_RT_C01.
10. Choose Create InfoPackage.
11. Enter the following data:
© SAP AG Page 93 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Field name User action and values
InfoPackage Description Flatfile Load: Transactional Data RT_C01
12. Select the line for RT_IS_RTC01 in the section DataSource.
13. Choose Save.
14. Choose Hide/Show Navigator.
15. Choose the External data tab and make the following entries:
Field name Values Notes
Load external data from Client workstation
File type The flatfiles are csv files.
Name of file Use F4, input help to open the folder for your flatfiles
See the comments in the prerequisites paragraph of this chapter. Choose the first flatfile Flatfile_RT_C01_2008.csv
Data Separator , The data seperator depends on the computer’s Regional and Languages Options. The used data separator is defined for English (United States). Using not this seperator requires to recreate the flatfiles with your current regional settings. Then you have to enter this Data Seperator here.
Escape Sign " See remark for Data Seperator !
Separator for Thousands , See remark for Data Seperator !
Character used for Decimal Point . See remark for Data Seperator !
Currency Conversion for External Systs unflag
Number of Header Rows to be Ignored 1
13. Choose the Processing tab and make the following entry:
Field name Value
PSA and then into Data Targets
14. Choose the Data targets tab and set flag in the field of Select Data Targets.
15. Select the InfoProvider RT_C01under the Field name Updating the data target.
16. Choose the Update tab and make the following entries:
Field name Values
Update Mode Mark Full update
Data Update Type in the Data Target Mark Always update data, even if no master data exists for the data
17. Choose the Schedule tab.
18. Choose Start. You get the status message Data was requested.
© SAP AG Page 94 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
19. Choose Monitor to monitor the request.
20. Choose Refresh tree on the Monitor - Administrator Workbench screen until until the status of your request is successful. That means your request obtains a green traffic light.
21. Choose 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 Logging on to the Query Designer
UseYou 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.1Transaction RRMX
Procedure1. Access the activity using the following navigation:
Transaction code RRMX
© SAP AG Page 95 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: 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 Question mark and choose About.
3. If you find a screen with the following information you are working with the right version.
Otherwise you have to change settings for the BEX Analyzer. Therefore execute the next steps
4. Choose BEx Analyzer.
5. Follow the menu path, choose Global Settings.
6. Set the flag Launch legacy version from RRMX.
7. Repeat step (1) and (2).
8. Choose Tools.
9. Choose Query Designer.
4.5.7.2Microsoft Office Start Menu
Procedure1. One possibility to access the Query Designer is using the following navigation option:
Microsoft Office Start Menu
Start All Programs Business Explorer Business Explorer (SAP BW 3.x) Query Designer (SAP BW 3.x)
2. Log on with your user in the upcoming SAP Logon screen to the BI system.
4.5.8 Creating Queries
UseYou can analyze the data in an InfoProvider using queries that are could be carried out as part of allocation strategies in the ECC System.
PrerequisitesThe variable used in the query must be activated. Refer to chapter Activating Business Content, Query Variables.
Procedure
© SAP AG Page 96 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
1. Choose New Query in the board.
2. Choose Technical Name on/off in the board.
3. Follow the path Industry Sectors Trade Industries Retailing Allocation
4. Double-click the InfoProvider Allocation Strategy RT_C01.
5. You enter the following screen:
6. Choose Technical Name to de-/activate the technical names.
The following two steps explain How to Drag and Drop: as an example.
a) Expand for example, the hierarchy of Consumer. Then you see several characteristics, choose the node of Price Band Category
b) Now click and hold down the left button on the Price Band Category and move the mouse into the desired frame. In our case the Free Characteristics and release the mouse button.
© SAP AG Page 97 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
4.5.8.1Creating Query RT_RTC01_Q001
Procedure1. Insert via Drag and Drop into the frame Free Characteristics:
Field name 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:
Field name Description
0PLANT Store
0CALMONTH Calendar year/Month
0MATERIAL Article
4. Insert via Drag and Drop into the frame Columns:
Field name 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 click Price Band Category.
6. Choose Restrict.
© SAP AG Page 98 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
7. Select the tab page of Variables.
8. Right click No Entries Found.
9. Choose Technical Names.
10. Restrict the InfoObject Price Band Category with the following variable that you have to create:
Variable Name Description Variable Represents Variable entry is
RT_PBC Price Band Category
Single Value Optional
11. Right click No Entries Found.
12. Choose New Variable.
13. Enter the values as shown in table:
Field names Name Value
Variable Name RT_PBC
Description Price Band Category
Processing by User Entry/Default Value
Characteristic Price Band Category
14. Choose Next.
15. Change the default values as shown in table.
Field names Name Value
Variable Represents Single Value
Variable entry is Optional
Ready for Input Set flag
16. Choose Next.
17. Choose Next.
18. Choose Exit.
19. Mark the just created variable.
20. Choose Add.
21. Choose OK.
22. Restrict the InfoObject Season with the following Variable:
Variable Name Description Variable Represents Variable entry is
0P_OSAIS Season Single Value Optional
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
© SAP AG Page 99 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
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 Save Query as.
28. Enter the following data:
Field name Value
Description Allocation - Article/Month
Technical Name RT_RTC01_Q001
29. Choose Save.
4.5.8.2Creating Query RT_RTC01_Q002
Procedure1. Being in the first query choose 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.
© SAP AG Page 100 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
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 Save Query.
5. Now that you have restricted the characteristics the query should be equal to the one shown in the screen shot.
© SAP AG Page 101 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
4.5.8.3Creating Query RT_RTC01_Q003
Procedure1. Being in the second query choose Save Query as
Field name Value
Description Allocation - Subsegment/Month
Technical Name RT_RTC01_Q003
2. Add via Drag and Drop into the Free Characteristics frame:
Field name 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:
Variable Name Description Variable Represents Variable entry is
0CMHIEID CDT Hierarchy ID
Single Value Mandatory
5. Restrict the InfoObject Subsegment with the following Variable:
Variable Name Description Variable Represents Variable entry is
RT_SSEG Subsegment Selection option Optional
6. Right click Subsegment
7. Choose Restrict.
8. Select the tab page Variables.
9. Right click No Entries Found.
10. Choose Technical Names.
11. Right click No Entries Found.
12. Choose New Variable
13. Enter the values as shown below:
Field names Name Value
Variable Name RT_SSEG
Description Subsegment
Processing by User Entry/Default Value
Characteristic Subsegment
14. Choose Next.
15. Change the default values:
Field names Name Value
Variable Represents Selection Option
Variable entry is Optional
Ready for Input Set flag
16. Choose Next.
© SAP AG Page 102 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
17. Choose Next.
18. Choose Exit.
19. Select the just created variable.
20. Choose Add.
21. Choose OK.
22. Choose 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 103 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
4.5.8.4Creating Query RT_RTC01_Q004
Procedure1. Being in the third query choose 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 click Segment.
6. Choose Restrict.
7. Select the tab page Variables.
8. Right click No Entries Found.
9. Choose Technical Names.
10. Right click No Entries Found.
11. Choose New Variable
12. Enter the values as shown in the table:
Field names Name Value
Variable Name RT_SEG
Description Segment
Processing by User Entry/Default Value
Characteristic Segment
13. Choose Next.
14. Change the default values as shown in the table:
Field names Name Value
Variable Represents Selection Option
Variable entry is Optional
Ready for Input Set flag
15. Choose Next.
16. Choose Next
17. Choose Exit.
18. Mark the just created variable.
19. Choose Add.
20. Choose OK.
21. Choose Save Query.
© SAP AG Page 104 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
22. Now that you have restricted the characteristics. The query should be equal to the one shown in the next screen shot.
4.5.9 Allocation Settings – SAP ECC
4.5.9.1Field Name Mappings BW <–> ECC
Use The purpose of this activity is to define the integration of the allocation process. That means a Field name mapping must take place.
PrerequisitesThe necessary queries must be created.
Procedure 1. Access the activity using the following navigation option:
Transaction code MCW_AA
2. Choose Execute IMG Activity in front of the entry Maintenance of Queries for Analytical Applications.
3. Choose New Entries in the following screen.
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 RT_C01/RT_RTC01_Q002 Allocation - Material Group/Month
© SAP AG Page 105 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
your BI System
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 the folder of Maintain Query Components.
7. Choose New Entries.
8. Map the BI Field names with the ECC Field names according to the following screen shot. The value is not necessary an entry that you find within the F4-Help.
OLAP (BW) Field name Field name in OLTP (R3) PeTP
0PLANT WERKS
0CALMONTH CALMONTH MN
0MATERIAL MATNR
0CPSAEXCUSU CPSAEXCUSU
RT_PBC P_PBC
0P_OSAIS P_SEASON
0S_PLANT SL_WERKS
0S_CALMO CALMONTH MN
0S_MAT SL_MATNR
9. Choose Save.
10. Choose Back twice.
11. Mark the entry Allocation - Material Group/Month.
12. Double-click the folder Maintain Query Components.
13. Choose New Entries.
14. Map the BI Field names with the ECC Field names according to the following screen shot. The value is not necessary an entry that you find within the F4-Help.
OLAP (BW) Field name Field name in OLTP (R3) PeTP
0PLANT WERKS
0CALMONTH CALMONTH MN
0MATL_GROUP MATKL
0CPSAEXCUSU CPSAEXCUSU
RT_PBC P_PBC
0P_OSAIS P_SEASON
0S_PLANT SL_WERKS
0S_CALMO CALMONTH MN
0S_MATGR SL_MATKL
15. Choose Save.
© SAP AG Page 106 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
16. Choose Back twice..
17. Mark the entry Allocation – Subsegment/Month.
18. Double-click Maintain Query Components..
19. Choose New Entries.
20. Map the BI Field names with the ECC Field names according to the following screen shot. The value is not necessary an entry that you find within the F4-Help.
OLAP (BW) Field name Field name in OLTP (R3) PeTP
0PLANT WERKS
0CALMONTH CALMONTH MN
0CM_CDT4 ARTH05
0CPSAEXCUSU CPSAEXCUSU
RT_PBC P_PBC
0P_OSAIS P_SEASON
0S_PLANT SL_WERKS
0S_CALMO CALMONTH MN
0CMHIEID P_AHID
RT_SSEG SL_AH05
21. Choose Back twice.
22. Mark the entry Allocation – Segment/Month.
23. Double-click Maintain Query Components.
24. Choose New Entries.
25. Map the BI Field names with the ECC Field names according to the following screen shot. The value is not necessary an entry that you find within the F4-Help.
OLAP (BW) Field name Field name in OLTP (R3) PeTP
0PLANT WERKS
0CALMONTH CALMONTH MN
0CM_CDT3 ARTH04
0CPSAEXCUSU CPSAEXCUSU
RT_PBC P_PBC
0P_OSAIS P_SEASON
0S_PLANT SL_WERKS
0S_CALMO CALMONTH MN
RT_SEG SL_AH04
4.5.9.2Maintenance of Methods for Analytical Applications
Use
© SAP AG Page 107 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
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
2. Choose Execute Maintenance of Methods for Analytical Applications.
3. On the Determine Work Area: Entry screen, enter the following data:
Field name User action and values
Analytical Appl. 001
4. Choose Continue.
5. Choose New Entries to add a new method and add at the table:
Field name User action and values
Method RTAL01
Method description Allocation Article/Month
6. Choose Enter.
7. Mark the new line and double-click the folder of Maintain Method Steps.
8. Choose New Entries to add a new method step.
9. Enter the following data:
Field name User action and values
Meth. Step 1
Target system The logical name for BI System
Analyt. Appl. Query RT_C01/RT_RTC01_Q001
10. Choose Enter.
11. Choose Back twice.
12. Choose New Entries to add a new method and add at the table:
Field name User action and values
Method RTAL02
Method description Allocation - Material Group/Month
13. Choose Enter.
14. Mark the new line and double-click the folder of Maintain Method Steps.
15. Choose New Entries to add a new method step.
16. Enter the following data:
Field name User action and values
Meth. Step 1
Target system The logical name for BI System
Analyt. Appl. Query RT_C01/RT_RTC01_Q002
17. Choose Enter .
18. Choose Back twice.
© SAP AG Page 108 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
19. Choose New Entries to add a new method and add at the table:
Field name User action and values
Method RTAL03
Method description Allocation - Subsegment/Month
20. Choose Enter.
21. Mark the new line and double-click the folder of Maintain Method Steps.
22. Choose New Entries to add a new method step.
23. Enter the following data:
Field name User action and values
Meth. Step 1
Target system The logical name for BI System
Analyt. Appl. Query RT_C01/RT_RTC01_Q003
24. Choose Enter.
25. Choose Back twice.
26. Choose New Entries to add a new method.
27. Enter the following data:
Field name User action and values
Method RTAL04
Method description Allocation - Segment/Month
28. Choose Enter.
29. Mark the new line and double-click the folder of Maintain Method Steps.
30. Choose New Entries to add a new method step.
31. Enter the following data:
Field name User action and values
Meth. Step 1
Target system The logical name for BI System
Analyt. Appl. Query RT_C01/RT_RTC01_Q004
32. Choose Enter.
33. Choose Back.
34. Choose Save.
4.5.9.3Extraction Settings – SAP ECC
Use In this activity, you can configure BI extraction on the basis of two parameters:
CONCATWith 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 activatedkonka - concatenation activated
© SAP AG Page 109 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
PACKSIZEWith 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
CONCATThe default value of the parameter is KEIKO - Concatenation for the extraction is deactivated.
PACKSIZEIf 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 activity using one of the following navigation options:
IMG menu SAP Customizing Implementation Guide Logistics - General Article Hierarchy BW Extraction
Transaction code SPRO
2. Choose Customizing Extraction.
3. Choose New Entries.
4. Select the following entry by choosing :
Customizing Object Value of Customizing Object
Concatenation During Extraction On/Off Concatenation for Extraction Inactive
5. Choose Save.
5 Adjust Steps Concerning Personalization
5.1 Changing Merchandise Planning Flatfiles
UseFor using the delivered merchandise flatfiles in a local environment you have to do some flatfile changes concerning master data. The flatfiles you load in the BI System are csv-files. However the master data changes take place in the xls-files that are also part of the delivery. When finishing the changes you recreate the csv-files.
Within the flatfiles there is a random number generator for the calculation of the some key figures. When you enter the excel file every time new numbers will be generated for some key figures. If you exit the excel file you will be ask if you want to store the changes. You can say NO.
5.1.1 InfoProvider 0RMP_C05
Procedure1. Open the excel-file Flatfile_0RMP_C05_MCP_2008.XLS
2. Replace within the worksheets Flatfile Flatfile 0001 0RMP_C05 2008, Flatfile 0002 0RMP_C05 2008 and Flatfile oSeg 0RMP_C05 2008 for 0DISTR_CHAN the cell Q2 with the new distribution channel. The other excel cells will be filled automatically.
© SAP AG Page 110 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
3. Replace within the worksheets Flatfile 0001 0RMP_C05 2008, Flatfile 0002 0RMP_C05 2008 and Flatfile oSeg 0RMP_C05 2008 for 0SALESORG the cell BW2 with the new sales organization. The other excel cells will be filled automatically.
4. Save the excel file by choosing Save.
5. Choose the worksheet Flatfile 0001 0RMP_C05 2008
6. Follow the excel menu path File Save As …
7. In the Field name Save as type: search for CSV(Comma delimited)(*.csv)
8. Save the file under the name Flatfile_0RMP_C05_MCP_2008_0001.csv
9. Choose Save.
10. Replace the flatfile if it already exists.
11. Continue with OK in the next screen.
12. Continue with YES in the next screen.
13. Follow the excel menu path File Exit …
14. Continue with No in the next screen.
15. Execute the steps (6) – (15) for the Worksheet Flatfile 0002 0RMP_C05 2008Name the flatfile Flatfile_0RMP_C05_MCP_2008_0002.csv.
16. Execute the steps (6) – (15) for the Worksheet Flatfile oSeg 0RMP_C05 2008Name the flatfile Flatfile_0RMP_C05_MCP_2008_oSeg.csv.
17. Execute the steps in this subchapter also for the flatfile Flatfile_0RMP_C05_MCP_BUDGET_2008.XLSName the flatfiles Flatfile_0RMP_C05_MCP_2008_0001.csv, Flatfile_0RMP_C05_MCP_2008_0002.csv
18. Execute the steps in this subchapter also for the flatfile Flatfile_0RMP_C05_MCP_BUDGET_2010.XLSName the flatfiles Flatfile_0RMP_C05_MCP_2010_0001.csv, Flatfile_0RMP_C05_MCP_2010_0002.csv
19. Execute the steps in this subchapter also for the flatfile Flatfile_0RMP_C05_MCP_BUDGET_2011.XLSName the flatfiles Flatfile_0RMP_C05_MCP_2011_0001.csv, Flatfile_0RMP_C05_MCP_2011_0002.csv
20. Execute the steps in this subchapter also for the flatfile Flatfile_0RMP_C05_MP1.XLSName the flatfiles Flatfile_0RMP_C05_MP1_2009.csv.
21. Save the excel file by choosing Save.
5.2 Changing Assortment Planning Flatfiles
UseFor using the delivered assortment flatfiles in a local environment you have to do some flatfile changes concerning master data. The flatfiles you load in the BI System are csv-files. However the master data changes take place in the xls-files that are also part of the delivery. When finishing the changes you recreate the csv-files.
5.2.1 InfoProvider RT_C35
Procedure1. Open the excel-file Flatfile_RT_C35_Fashion_2008.xls
© SAP AG Page 111 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
2. Replace within the worksheet Flatfile_RT_C35_Fashion_2008.xls for 0DISTR_CHAN the cell K2 with the new distribution channel. The other excel cells will be filled automatically.
3. Replace within the worksheet Flatfile_RT_C35_Fashion_2008.xls for 0SALESORG the cell AA2 with the new sales organization. The other excel cells will be filled automatically.
4. Follow the excel menu path File Save As …
5. In the Field name Save as type: search for CSV(Comma delimited)(*.csv)
6. Save the file under the name Flatfile_RT_C35_Fashion_2008.csv
7. Choose Save.
8. Replace the flatfile if it already exists.
9. Continue with OK in the next screen.
10. Continue with YES in the next screen.
11. Follow the excel menu path File Exit …
12. Continue with No in the next screen.
5.3 Changing Allocation Flatfiles
UseFor using the delivered allocation flatfiles in a local environment you have to do some flatfile changes concerning master data. The flatfiles you load in the BI System are csv-files. However the master data changes take place in the xls-files that are also part of the delivery. When finishing the changes you recreate the csv-files.
5.3.1 InfoProvider RT_C01
Procedure1. Open the excel-file Flatfile_RT_C01.XLS
2. Replace within the worksheet Flatfile RT_C01 2008 for 0PLANT in column H the old stores by the new stores.
3. Save the excel file by choosing Save.
4. Follow the excel menu path File Save As …
5. In the Field name Save as type: search for CSV(Comma delimited)(*.csv)
6. Save the file under the name Flatfile_RT_C01_2008.csv
7. Choose Save.
8. Replace the flatfile if it already exists.
9. Continue with OK in the next screen.
10. Continue with YES in the next screen.
11. Follow the excel menu path File Exit …
12. Continue with No in the next screen.
© SAP AG Page 112 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
6 Appendix A: Helpful BI Actions
6.1 Activating InfoProviders
UseIf 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.
Procedure1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Choose Search.
4. Enter the following data in the upcoming screen:
Field name User action and values
Find 0RMP_C05
5. Choose Search.
6. Right click 0RMP_C05.
7. Choose Change.
8. Choose Activate.
6.2 Activating Update Rules
UseIf 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.
Procedure1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Choose Search.
4. Enter the following data in the upcoming screen:
Field name User action and values
Find 0RMP_C05
© SAP AG Page 113 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
5. Choose Search.
6. Expand the hierarchy with following information:
Merchandise Planning, Plan 0RMP_C05
7. Right click 0RMP_C05 RT_IS_0RMP_C05.
8. Choose Change.
9. Choose Activate .
6.3 Activating Transfer Rules
UseIf 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.
Procedure1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
3. Choose Search.
4. Enter the following data in the upcoming screen:
Field name User action and values
Find 0RMP_DS01
5. Choose Search.
6. Right click 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 Continue.
6.4 Replicate DataSources
UseIf 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.
© SAP AG Page 114 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Procedure1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose DataSources.
3. Choose Choose Source System.
4. Select your ECC System.
5. Choose Search.
6. Enter the desired DataSource in the upcoming screen:
Field name User action and values
Find 0MATERIAL, for example
7. Choose Search.
8. Right click 0MATERIAL.
9. Choose Replicate DataSource.
10. On the Data Warehousing Workbench: Modeling screen choose InfoSources.
11. Choose Search.
12. Enter the desired DataSource in the upcoming screen:
Field name User action and values
Find 0MATERIAL, for example
13. Choose Search.
14. Activate the corresponding transfer rules and Update Rules again.
6.5 Deleting Data Requests
UseWithin 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.
Procedure1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse
© SAP AG Page 115 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen, choose InfoProvider.
6.5.1 Basic InfoProvider
Procedure1. Choose Search.
2. Enter the following data in the upcoming screen:
Field name User action and values
Find 0RMP_C22
3. Choose Search.
4. Right click 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 the red or yellow traffic light in the corresponding data request
7. Choose Status OK.
8. Choose Save. For a green data request execute the following steps to delete it.
9. Select the data request like
10. Choose Delete.
11. Choose Refresh to check the deletion of the request.
12. Choose Exit to close the right hand frame.
6.5.2 Real Time InfoProvider
Procedure1. Choose Search.
2. Enter the following data in the upcoming screen:
Field name User action and values
Find 0RMP_C05
3. Choose Search.
4. Right click 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 Continue.
© SAP AG Page 116 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
By executing these steps a data request with a yellow traffic light is changed to a data request with a green traffic light.
8. Right click 0RMP_C05.
9. Choose Manage.
For a green data request execute the following steps to delete it.
10. Select the data request like
Choose Delete.
11. Choose Refresh to check the deletion of the request.
12. Choose Exit to close the right hand frame.
10. Right click 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 Continue.
6.6 Applying Hierarchy/Attribute Change
UseIf 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.
Procedure1. Access the activity using one of the following navigation options:
SAP BI menu Information Systems Business Information Warehouse Modeling Data Warehousing Workbench: Modeling
Transaction code RSA1
2. On the Data Warehousing Workbench: Modeling screen choose InfoProvider.
3. Follow the path Tools Apply Hierarchy/Attribute Change starting in the board.
4. Choose InfoObject List.
5. There could be entries like
Description InfoObject
Store Article 0MAT_PLANT
© SAP AG Page 117 of 118
SAP Best Practices 764: BI Retail: Merchandise and Assortment Planning: Configuration Guide
6. Choose InfoObject List.
7. Choose Save InfoObject List.
8. Choose Refresh until you get the message Hierarchy/Attribute Change Is Finished.
7 Appendix B: Year Change TasksWhen a new year starts and the plan year in your planning environment should be the next year this requires the following steps.
7.1 Maintaining Fiscal Year VariantYou must maintain the fiscal year variant for the new plan year in your planning environment. You did it already until the year 2010.
7.2 Deleting Data RequestsYou must delete the data requests in the InfoProviders 0RMP_C05, RT_C01, RT_C31, RT_C35.
7.3 Adjusting Flatfiles You must change all the year stuff in the flatfiles for the Merchandise Plan, Store Plan and Assortment Plan. Then you have to recreate the csv-files.
7.4 Loading Updated Flatfiles You have to reload the flatfiles. See Chapter 4.
© SAP AG Page 118 of 118