planet retail sap bi configuration documentdocshare02.docshare.tips/files/26353/263530925.pdf ·...
TRANSCRIPT
Planet Retail
SAP BI Configuration
Document
1
Created By: Akshat Bal DikshitConsultant - PricewaterhouseCoopers
Table of Contents
1. GENERAL EXPLANATIONS......................................................................................................3
2. POS ANALYTICS..........................................................................................................................7
2.1. SCENARIO OVERVIEW:...........................................................................................................72.2. POS ANALYTICS INFO PROVIDERS:......................................................................................7
2.2.1. Store/Article/Day......................................................................................................72.2.2. Data Flow for Info Cube 0RPA_C01....................................................................82.2.3. Data Modeling...........................................................................................................8
2.3. CAPTURING LYB NO. AND INVOICE NO.............................................................................102.4. OTHER DEVELOPMENTS......................................................................................................112.5. WALKINS CUBE....................................................................................................................12
2.5.1. Data Modeling.........................................................................................................122.5.2. Data Model for Walkins Cube.............................................................................142.5.3. Data Modeling.........................................................................................................14
3. RETAIL..........................................................................................................................................16
3.1. SCENARIO OVERVIEW..........................................................................................................163.2. RETAIL INFOPROVIDERS......................................................................................................16
3.2.1. Retail Cube..............................................................................................................163.2.2. Data Modeling.........................................................................................................16
3.3. INFOCUBE FOR PLANNED DATA..........................................................................................213.4. DATA MODELING..................................................................................................................213.5. MULTIPROVIDER FOR PLANNED/ACTUAL DATA.................................................................233.6. DATA MODELING..................................................................................................................23
4. INVENTORY.................................................................................................................................25
4.1. SCENARIO OVERVIEW..........................................................................................................254.2. INVENTORY INFOPROVIDERS...............................................................................................25
4.2.1. Inventory Cube.......................................................................................................254.2.2. Data Modeling.........................................................................................................25
5. ENHANCING MASTER DATA..................................................................................................28
5.1. MATERIAL MASTER..............................................................................................................285.2. PLANT MASTER....................................................................................................................32
APPENDIX A.........................................................................................................................................33
APPENDIX B.........................................................................................................................................37
APPENDIX C.........................................................................................................................................41
APPENDIX D.........................................................................................................................................42
2
1. General explanations
Datawarehousing Workbench
The Datawarehousing Workbench (DWB) is the tool that you use to control how the data getsfrom the source systems into the InfoCubes of the Business Information Warehouse. Theparts of the Administrator Workbench that you will need for the requesting and managing ofthe data include: Source system, InfoSource, InfoCube, InfoObject, Scheduler, and Monitor.
Business Explorer
The SAP Business Information Warehouse reporting tool.In the Business Explorer Analyzer (BEx Analyzer) you define queries, which are based on aselection of characteristics and key figures (Info Objects). You analyze the selected InfoCubedata by navigating in the query, where you generate different views of the data.
Characteristic
A criterion to which data can be selected such as company code, product, material, customergroup, fiscal year, period or region.Characteristics provide classification possibilities for the dataset. The master dataencompasses the permitted values of a characteristic, the so-called characteristic values.Characteristic values are discrete names. The characteristic region could, for example, havethe values "North", "Central" and "South".
Data Extraction
The process of loading data from source systems into the BW for reporting.
Data Mapping
The process of assigning source system data elements to target data elements in the DataWarehouse.
Data Transformation
The process of modifying data for accuracy and completeness in BW. Transformations thatare derived from business rules can be applied to elementary data in BW to prepare it forend-user reporting.
Data Warehouse
A database that contains summarized data from transactional data found in the OLTPsystem(s), legacy system(s) or other sources. The data store in the BW is designed for theefficient retrieval of data and for decision support reporting. The data are organized by subjectarea, and the data are time dependent. The data store contains figured quantities anddimensional data.
3
The architecture of the BI specific ETL process is depicted in the figure below:
Dimension Table
4
Update Rules
SD, PP, MM, QM, FI,IS -Retail
SAP R/3 OLTP
Business Information Warehouse Staging Area
InfoCube
Update Rules Update Rules
External Sources
Communication StructureCommunication Structure
Transfer Structure
ProductionExtractors
Transfer Structure
Flat Files
Plan and Target Data
Transfer Structure
ODS
Mapping & Transformation Rules Mapping & Transformation Rules
A table in a star schema with a single part primary key (e.g., customer key, product key, timekey).
Fact Table
The fact table is at the center of the star schema of an InfoCube. The data part contains allkey figures (also called "Facts") of the InfoCube and the key is formed by links to the entriesof the dimensions of the InfoCube.
Favorites
Channel for workbooks with which a user works frequently. Users can copy workbooks withwhich they frequently work from the channels into their favorites. Users manage their favoritesthemselves and can individually name or group their content. Users can save modified or newworkbooks in their favorites.
Info Catalog
This is a tree-like structure in the Administrator Workbench that displays Business InformationWarehouse workbooks and queries. The various Info Catalog trees contain workbooks thatSAP delivers, workbooks that can be used in an enterprise, workbooks that are used bycertain user groups, workbooks that an individual user is allowed to use, and Favoriteworkbooks (user favorites), that a user has put together. The structure of the sub-trees can befreely defined by the administrator. A user accesses his or her queries of the Info Catalogusing the Business Explorer Browser.
InfoCube
This is the central data container for queries and evaluations. InfoCubes contain two types ofdata, namely key figures and characteristics.An InfoCube is a number of relational tables, which are put together according to the starschema: a large fact table in the center, surrounded by several dimension tables. The facttable is set up in order to save all key figures on the lowest level of detail while the dimensiontables are used to save the characteristics that are required both in reporting and in theevaluations of these key figures. Dimension tables are seen as being independent of oneanother. Only the fact table connects the dimensions with the key figures. Therefore all of thedata is stored multi-dimensionally in the InfoCubes.
InfoObject
Generic term in the Business Information Warehouse for characteristics and key figures.InfoObject are used in InfoCubes and the three structures relevant for the data request(extract structure, transfer structure and communication structure).Names for Info Objects can only be given once.Within the characteristic a distinction is made between time and unit characteristics.Examples for characteristics would be evaluation groups such as cost center or productgroup.Key figures are currency, quantity or number fields such as sales revenue, revenue or numberof employees. Key figures usually refer to unit Info Objects.
5
Info Package
This describes which data in an InfoSource should be requested from a source system.Therefore, the data can be precisely selected using selection parameters (for example, onlycontrolling area 001 in period 10.1997).An Info Package can request transaction data or attributes or hierarchies for master data.
InfoSource
An InfoSource is a quantity of information for a unit. This information has been groupedtogether and can be said to belong together logically from a business point of view.InfoSources can either contain transaction data or master data (attributes, texts, andhierarchies). An InfoSource is always a quantity of Info Objects.
Key Figure
Values or quantities such as sales revenue, fixed costs, sales quantity or number ofemployees.In addition to the key figures saved on the database, there is a possibility of defining derived(calculated) key figures in the query definition in the Business Explorer. Such key figures arecalculated using a formula from the key figures of the InfoCube. Examples of derived keyfigures are sales revenue per employee (sales revenue divided by number of employees), orvariance as a percentage or the contribution margin.
Master Data
This is data that remains unchanged over a long period of time. Master data containsinformation that is needed again and again in the same way. Meta DataMeta data is data about data. This means that meta data describes the origin, history andfurther aspects of the data. The information that is stored in the SAP Business InformationWarehouse can be effectively used for reporting and analysis via the meta data. There are different classes of meta data: technical or business-oriented.
Monitor
Monitoring tool of the Administrator Workbench. Using the Monitor you can oversee the datarequest and processing in the Administrator Workbench. You will be shown the status of theIDoc processing in the various levels of the detail display. A distinction is made between twotypes of IDoc: Data IDoc and Info IDoc.
OLAP
On-Line Analytical Processing (OLAP) is software that is used to analyze summarized On-Line Transaction Processing (OLTP) data. OLAP allows multidimensional views and analysisof that data for decision support processes.
OLTP
On-Line Transaction Processing (OLTP) is used for operational data e.g. data in the R/3software.
Primary Key
Key field or group of fields which form the unique identification of a record (a line) in a table.
6
Query
Collection of a selection of characteristics and key figures (Info Objects) for the analysis of thedata of an InfoCube. A query always refers to exactly one InfoCube, whereas you can defineas many queries as you like per InfoCube.You define a query by selecting Info Objects or predefined query templates of an InfoCubeand distributing them to filters, rows, columns and free (user-defined or drilldown)characteristics to create a view of the data. You insert the query in a workbook and can thencreate further views of the InfoCube data via navigation. You can save data for the currentnavigational state of the query in the workbook.
Relational Integrity
The observation of integrity rules governing the relational data model. These include primarykey integrity, value range integrity, and foreign key integrity (referential integrity).
Scheduler
The Scheduler is the nexus between the source systems and the InfoCubes. With theScheduler you determine which data is to be requested from the source system and at whichpoint in time. The principle of the Scheduler relies on the functionality of the R/3 backgroundjob. The data request can either be started at once or with a background job andautomatically at a later date.
Source System
All systems those are available in the Business Information Warehouse for data extraction.These can be SAP R/3 Systems (from Release 3.0D) and so-called external systems (forexample, so-called third party tools or files).
Star Schema
A data structure that combines fact tables and dimension tables in a way that provides easyand efficient access to the data.
2. POS Analytics
2.1.Scenario Overview:
To analyze Invoice wise, Material wise, Brand wise, Merchandise Category wise Sales,Discounts and Taxes. Apart from Sales Scenario, Returns tracking, Store Credit NoteIssue/Redeem Tracking, Walkins is covered under POS Analytics. LYB (Love Your Body)Customer tracking is also done in the POS Analytics scenario. Data from POSDM is used toload POS Analytics Cube and carry out analysis on day-to-day store data. InfoCube used inPOS Analytics scenario is:
Info cube: 0RPA_C01 – Store/Article/Day
2.2.POS Analytics Info providers:
2.2.1.Store/Article/Day
Technical name: 0RPA_C01
7
The InfoCube contains POS data for daily evaluations relating to the recent past atstore/article/day level.Data must be loaded to the InfoCube as soon as possible, in otherwords, at least once a day. However, this also depends very much on the size of the system.
.
2.2.2.Data Flow for Info Cube 0RPA_C01
2.2.3.Data Modeling
InfoSources
POS Analytics: Retail Control 0RT_PA_TRAN_CONTROL
8
Requires
Object Type Name Technical Name
InfoObject Base Sales Quantity in Base Units of Measure 0BASE_QTY
InfoObject Base Unit of Measure 0BASE_UOM
InfoObject Calendar Day 0CALDAY
InfoObject Calendar Year/Month 0CALMONTH
InfoObject Calendar month 0CALMONTH2
InfoObject Quarter 0CALQUART1
InfoObject Calendar Year/Quarter 0CALQUARTER
InfoObject Calendar Year/Week 0CALWEEK
InfoObject Calendar Year 0CALYEAR
InfoObject Change Run ID 0CHNGID
InfoObject Consumer 0CONSUMER
InfoObject Document currency 0DOC_CURRCY
InfoObject Fiscal year / period 0FISCPER
InfoObject Posting period 0FISCPER3
InfoObject Fiscal year variant 0FISCVARNT
InfoObject Fiscal year 0FISCYEAR
InfoObject Halfyear 0HALFYEAR1
InfoObject Local currency 0LOC_CURRCY
InfoObject Material 0MATERIAL
InfoObject Material group 0MATL_GROUP
InfoObject Record type 0RECORDTP
9
Requires
Object Type Name Technical Name
InfoObject Request ID 0REQUID
InfoObject Number of Discount Items 0RPA_CCO
InfoObject Number of POS Receipts 0RPA_CNR
InfoObject Sales in Cost Value 0RPA_CST
InfoObject Discount Identification 0RPA_DID
InfoObject Discount Reason 0RPA_DRC
InfoObject Discount Reason Group 0RPA_DRG
InfoObject Discount Type 0RPA_DTC
InfoObject Discount Type Group 0RPA_DTG
InfoObject Sales Promotion Quantity 0RPA_PRMQTY
InfoObject Promotion Sales 0RPA_PRMSAL
InfoObject Promotion Sales (Local Currency) 0RPA_PSL
InfoObject Discount Value 0RPA_REA
InfoObject Return Sales 0RPA_RETSAL
InfoObject Sales Quantity in Sales Unit 0RPA_RLQ
InfoObject POS: Returns Quantity (BUn) 0RPA_RQTYB
InfoObject POS: Returns Quantity (Sales Unit) 0RPA_RQTYV
InfoObject Reason 0RPA_RRC
InfoObject Group for Reasons 0RPA_RRG
InfoObject Volume of Returns (Local Currency) 0RPA_RSL
InfoObject Sales at Retail Value 0RPA_SAT
10
Requires
Object Type Name Technical Name
InfoObject Sales at Retail Value (Local Currency) 0RPA_SLC
InfoObject Tender Value 0RPA_TAT
InfoObject Means of Payment 0RPA_TCD
InfoObject Transaction Type 0RPA_TTC
InfoObject Time of Day Class 0RT_DAYTCL
InfoObject Retail location 0RT_LOCATIO
InfoObject Promotion 0RT_PROMO
InfoObject Hour of Sale 0RT_SALHOUR
InfoObject Sales unit 0SALES_UNIT
InfoObject Weekday 0WEEKDAY1
2.3.Capturing LYB No. and Invoice No.
LYB No is captured in InfoObject 0RPA_DEP (Department Controller) and Invoice No iscaptured in InfoObject 0RPA_PAI (Partner Number).
Necessary setting in XI was done to capture LYB No and Invoice No in Department andPartner No respectively. Partner Number and Department are maintained under theDimension Invoice Number.
11
2.4.Other Developments
Getting Material from EAN No.
Article No (Material) doesn’t flow from POSDM to BW. From POSDM EAN No flowsinto BW. In order to get Article No for corresponding EAN No we wrote a routine inUpdate Rules of Material.
select single MATERIAL into RESULT from /BI0/PMATERIAL where EANUPC = COMM_STRUCTURE-EANUPC.
Tax Category and Tax Amount were not present in the BI Content cube. TaxCategory (0RPA_TAC) was added in the Tax dimension and Tax Amount(0RPA_TAM) was added in Key Figures.
Necessary changes were made in the Transfer Routine of 0RPA_C01
( wa_datapak-recordqualifier = 1000 OR wa_datapak-recordqualifier = 1100 OR
12
wa_datapak-recordqualifier = 1110 OR wa_datapak-recordqualifier = 1111 OR wa_datapak-recordqualifier = 1130 OR wa_datapak-recordqualifier = 1133 OR wa_datapak-recordqualifier = 1121 OR wa_datapak-recordqualifier = 1101 OR wa_datapak-recordqualifier = 1102 )
2.5. Walkins Cube
Technical Name: ZRPA_WALK
Walkins Cube is used to capture the Walkins data to be used in Walkins Report.Data is loaded from Flat File in the Walkins Cube.
2.5.1.Data Modeling
Walkins Cube
Technical Name: ZRPA_WALK
Infosources:
Walkins Info Source ZRPA_WALK
13
Data flow for InfoCube 0RPA_WALK
14
2.5.2.Data Model for Walkins Cube
Walkins Multiprovider
Technical Name: ZMP_WALK
2.5.3.Data Modeling
Walkins MultiProvider
Technical Name: ZMP_WALK
Basic Cubes Used:
Store/Article/Day 0RPA_C01 Walkins cube ZRPA_WALK
15
Data Flow for Walkins MultiProvider
Data Model for Walkins MultiProvider
16
3. Retail
3.1. Scenario Overview
To analyze Sales, Purchases at Retail Price and Landed Cost at Store, Merc Category,Brand, Material Group Level. This cube also gives position of stock. Data in this cube isloaded from multiple datasources to give Sales, Purchase and Stock positions. SourceSystem for data loading for this cube is ISR.
InfoCube: Retail Cube 0RT_C01
3.2.Retail InfoProviders
3.2.1.Retail Cube
Technical Name: 0RT_C01
This InfoCube was created to model the most important aspects of retailing in a
comprehensive manner. In other words, its purpose is to allow you to compare the key figures
from Purchasing, Inventory Management and Sales.
3.2.2.Data Modeling
Retail Cube
Technical Name: 0RT_C01
InfoSources
Purchasing Schedule Line 2LIS_02_SCL SD Billing Documents 2LIS_13_VDITM Stock Initialization 2LIS_03_BX Goods Movements 2LIS_03_BF
Revaluation Datasources not used currently
Stock Revaluation 2LIS_03_UM Revaluation at Retail 2LIS_40_REVAL
17
Data Flow for Info Cube 0RT_C01
Modeling
Object
Type Name Technical NameInfoObject GI / DC RtlT 0RTGOISDCSTInfoObject Goods Issue / DC Retail Value 0RTGOISDCSVInfoObject GR / DC / RtlT 0RTGOREDCSTInfoObject GR / DC Rtl 0RTGOREDCSVInfoObject GR Posting Date / Vendor RtlT 0RTGRPDVSTInfoObject Goods Receipt Posting Date/Vendor Retail Value 0RTGRPDVSVInfoObject Sales Deviation 0RTINSADISTInfoObject Merchandise Clearing Output / RtlT 0RTMCAODDST
InfoObject Outbound Merchandise Clearing / Rtl 0RTMCAODDSVInfoObject Merchandise Clearing Input / RtlT 0RTMCINDDSTInfoObject Merchandise Clearing Input / Retail Value 0RTMCINDDSVInfoObject Purchase Order Delivery Date/Vendor RtlT 0RTPODDVSTInfoObject PO Delivery Date / Vendor Retail Value 0RTPODDVSVInfoObject Returns Total / Vendor Cost Value 0CPTRETVPVInfoObject Issues from Valuated Stock Total / BUn 0CPTSTISBUInfoObject Total Issues from Valuated Stock / Cost Value 0CPTSTISPVInfoObject Receipts to Valuated Stock Total / BUn 0CPTSTREBUInfoObject Total Receipts to Valuated Stock / Cost Value 0CPTSTREPVInfoObject Local currency 0LOC_CURRCYInfoObject Material 0MATERIALInfoObject Plant Material 0MAT_PLANT
18
InfoObject Plant 0PLANTInfoObject Record type 0RECORDTPInfoObject Request ID 0REQUIDInfoObject Sales / Retail Value with Tax 0RTBAINSASTInfoObject Sales / Retail Value 0RTBAINSASVInfoObject Promotion Sales /Bun 0RTPRINSABUInfoObject Stock Correction Total (-) / Retail 0RTTINCONSVInfoObject Stock Correction Total (+) / RtlT 0RTTINCOPSTInfoObject Stock Correction Total (+) / Retail 0RTTINCOPSVInfoObject Total Valuated Stock - / RtlT 0RTTOTSTOSTInfoObject Total Valuated Stock / Rtl 0RTTOTSTOSVInfoObject Total Returns / Vendor Retail Value with Tax 0RTTRETVSTInfoObject Total Returns / Vendor Retail Value 0RTTRETVSVInfoObject Total Issues Valuated Stock / Retail Value with Tax 0RTTSTISSTInfoObject Total Issues from Valuated Stock / Retail Value 0RTTSTISSVInfoObject Total Receipts Valuated Stock / Retail Value with Tax 0RTTSTRESTInfoObject Total Receipts to Valuated Stock / Retail Value 0RTTSTRESVInfoObject Material Number linked to Retail_Activity 0RT_MAT_PRMInfoObject Promotion 0RT_PROMOInfoObject Promotion Sales / Number of Items 0RTPRINSANIInfoObject Promotion Sales / Cost Value 0RTPRINSAPVInfoObject Promotion Sales / Retail Value with Tax 0RTPRINSASTInfoObject Promotion Sales / Retail 0RTPRINSASVInfoObject Value-Based Sales, RtlT 0RTSALEEVSTInfoObject Sales Value at Retail 0RTSALEEVSVInfoObject Revaluation at Retail (Negative)/ Retail Value with
Tax
0RTSPRENST
InfoObject Revaluation at Retail (Negative)/ Retail Value 0RTSPRENSVInfoObject Revaluation at Retail (Positive)/ Retail Value with Tax 0RTSPREPSTInfoObject Revaluation at Retail (Positive) / Retail Value 0RTSPREPSVInfoObject Total GR / Vendor RtlT 0RTTGOREVSTInfoObject Total Goods Receipt / Vendor Retail Value 0RTTGOREVSVInfoObject Stock Correction Total (-) / RtlT 0RTTINCONSTInfoObject GR / DC Bun 0CPGOREDCBUInfoObject GR / DC Number of Items 0CPGOREDCNIInfoObject Goods Receipt /Distribution Center Cost Value 0CPGOREDCPVInfoObject Goods Receipt Posting Date / Vendor BUn 0CPGRPDVBUInfoObject GR Posting Date / Number of Vendor Schedule
Lines
0CPGRPDVNI
InfoObject Goods Receipt Posting Date / Vendor Cost Value 0CPGRPDVPVInfoObject Outbound Merchandise Clearing / BUn 0CPMCAODDBUInfoObject Outbound Merchandise Clearing / Number of Items 0CPMCAODDNIInfoObject Outbound Merchandise Clearing / Cost Value 0CPMCAODDPVInfoObject Inbound Merchandise Clearing / BUn 0CPMCINDDBU
19
InfoObject Inbound Merchandise Clearing / Number of Items 0CPMCINDDNIInfoObject Inbound Merchandise Clearing / Cost Value 0CPMCINDDPVInfoObject Open PO Quantity Delivery Date / Vendor BUn 0CPOPOQDVBUInfoObject Base Unit of Measure 0BASE_UOMInfoObject Calendar Day 0CALDAYInfoObject Calendar Year/Month 0CALMONTHInfoObject Calendar Year/Quarter 0CALQUARTERInfoObject Calendar Year/Week 0CALWEEKInfoObject Calendar Year 0CALYEARInfoObject Change Run ID 0CHNGIDInfoObject Sales / Base Unit of Measure 0CPBAINSABUInfoObject Sales /Number of Items 0CPBAINSANIInfoObject Sales/Cost Value 0CPBAINSAPVInfoObject GI / DC Bun 0CPGOISDCBUInfoObject GI / DC Number of Items 0CPGOISDCNIInfoObject GI / DC / Cost 0CPGOISDCPVInfoObject Open Order Stock Delivery Date / Vendor Cost Value 0CPOPOQDVPVInfoObject Stock Correction Total (Positive) / BUn 0CPTINCOPBUInfoObject Total Stock Correction (Positive) / Number of Items 0CPTINCOPNIInfoObject Total Stock Correction (Positive)/ Cost Value 0CPTINCOPPVInfoObject Last Valuated Stock Total/Bun 0CPTOTSTOBUInfoObject Last Valuated Stock Total/Cost Value 0CPTOTSTOPVInfoObject Total Cost Price Revaluation (Negative) /BUn 0CPTPPRENBUInfoObject Total Cost Price Revaluation (Negative) / Number of
Items
0CPTPPRENNI
InfoObject Total Revaluation at Cost (Negative)/ Cost Value 0CPTPPRENPVInfoObject Total Cost Price Revaluation (Positive)/BUn 0CPTPPREPBUInfoObject Total Cost Price Revaluation (Positive)/ Number of
Items
0CPTPPREPNI
InfoObject Total Cost Price Revaluation (Positive)/ Cost Value 0CPTPPREPPVInfoObject Total Returns / Vendor Bun 0CPTRETVBUInfoObject Total Returns / Vendor Number of Items 0CPTRETVNIInfoObject Purchase Order Delivery Date / Vendor BUn 0CPPODDVBUInfoObject Purch. Order Deliv. Date/SchLines 0CPPODDVNIInfoObject PO Delivery Date / Vendor Cost Value 0CPPODDVPVInfoObject Revaluation at Retail (Negative) / BUn 0CPSPRENBUInfoObject Revaluation at Retail (Negative) / Number of Items 0CPSPRENNIInfoObject Revaluation at Retail (Positive) / BUn 0CPSPREPBUInfoObject Revaluation at Retail (Positive) / No. of Items 0CPSPREPNIInfoObject Goods Receipt Total / Vendor BUn 0CPTGOREVBUInfoObject Goods Receipt Total / Vendor Number of Items 0CPTGOREVNIInfoObject Goods Receipt Total / Vendor Cost Value 0CPTGOREVPVInfoObject Total Stock Correction (Negative) / BUn 0CPTINCONBUInfoObject Total Stock Correction (Negative)/ Number of Items 0CPTINCONNI
20
InfoObject Total Stock Correction (Negative) / Cost Value 0CPTINCONPV
Changes in Update Rules of 2LIS_03_BX And 2LIS_03_BF
In the Update rules of Stock Initialization and Goods Movement we added the following lines ofcode to extract the data in BW.
IF COMM_STRUCTURE-PROCESSKEY = '103' AND COMM_STRUCTURE-BWAPPLNM EQ 'IS-R'.
Also in SBIW in ISR Prod “Industry Sector” was maintained as “Retail”
3.3. InfoCube for Planned Data
Technical Name: ZRT_PLAN
This InfoCube is used for Planned Sales and Purchase Data. Planned Sales and Purchase
data would be loaded through Excel File into ZRT_PLAN. This would then be used to analyze
Plan vs Actual Sales and Purchases.
3.4.Data Modeling
InfoCube for Planned Data
Technical Name: ZRT_PLAN
InfoSources
InfoSource for Planned Data : ZPLAN_IS
21
Data Flow for Info Cube ZRT_PLAN
22
Data Model for InfoCube for Planned Data
23
3.5.MultiProvider for Planned/Actual Data
Technical Name: ZMUL_PUR
This MultiProvider is used for Planned Sales and Purchase Data. Queries such as OTB and
Catalog Contribution are made from this MultiProvider
3.6.Data Modeling
MultiProvider for Planned/Actual Data
Technical Name: ZMUL_PUR
Basic Cubes:
Retail Cube 0RT_C01 InfoCube for Planned Data ZRT_PLAN
Data Flow for Planned/Actual Data MultiProvider
24
Data Model for Planned/Actual MultiProvider
Note: A MultiProvider cannot have a Non Cumulative Key Figure such as TotalStock Qty from both the Basic Cubes. Also SAP Note 1116174 is required toactivate the MultiProvider.
25
4. Inventory
4.1.Scenario Overview
To do Inventory Ageing and analyze Opening Stock, Receipts, Issues and Closing Stockquantities. Stock Overview and Stock Ageing reports are delivered from this report.
InfoCube: Inventory Cube ZIC_C03
4.2. Inventory InfoProviders
4.2.1.Inventory Cube
Technical Name: ZIC_C03
This InfoCube allows you to evaluate stocks from ERP.
A new feature in this InfoCube is the pre-existing stock key figure Valuated Stock Quantity(0VALSTKQTY) and the associated movement key figures Receipt Quantity Valuated Stock(0RECVALSTCK) and Issue Quantity Valuated Stock (0ISSVALSTCK).
4.2.2.Data Modeling
Retail Cube
Technical Name: ZIC_C03
InfoSources
Stock Initialization 2LIS_03_BX Goods Movements 2LIS_03_BF
Revaluation Datasources not used currently
Stock Revaluation 2LIS_03_UM
26
Data Flow for ZIC_C03 (Inventory Management) Cube
Modeling
InfoObject Description
0MATERIAL Material
0PLANT Plant
0STOR_LOC Storage Location
0BATCH Batch Number
0STOCKTYPE Stock Type
0STOCKCAT Stock Categories
0GN_VENDOR Vendor
0CALDAY Calendar Day
0CALMONTH Calendar Year/Month
0CALWEEK Calendar Year/Week
27
0CALYEAR Calendar Year
0RECVS_VAL Value Received - Valuated Stock
0VALSTCKVAL Value - Valuated Stock
0ISSVS_VAL Value Issued - Valuated Stock
0ISSBLOSTCK Issue Quantity - Blocked Stock
0ISSCNSSTCK Issue Quantity - Consignment Stock
0ISSQMSTCK Issue Quantity - Inspection Stock
0ISSTRANSST Issue Quantity - Stock in Transit
0RECBLOSTCK Receipt Quantity - Blocked Stock
0RECCNSSTCK Receipt Quantity - Consignment Stock
0RECQMSTCK Receipt Quantity - Inspection Stock
0RECTRANSST Receipt Quantity - Stock in Transit
0QMSTOCK Inspection Stock
0BLOCKEDSTK Blocked Stock
0CNSSTCKQTY Quantity - Consignment Stock
0TRANSSTOCK Stock in Transit
0ISSSCRP Issue Quantity - Scrap
0ISSVALSCRP Issue Value - Scrap
0RECTOTSTCK Receipt Quantity - Total Stock
0ISSTOTSTCK Issue Quantity - Total Stock
0TOTALSTCK Quantity - Total Stock
0ISSVALSTCK Issue Quantity - Valuated Stock
0RECVALSTCK Receipt Quantity - Valuated Stock
0VALSTCKQTY Quantity - Valuated Stock
0VENCONCON Consumption Value - Vendor ConsignmentStock
0LOC_CURRCY Local Currency
0BASE_UOM Base Unit of Measure
Note the following procedures when filling the InfoCube 0IC_C03 for the firsttime with non-cumulative data from ERP:...
1. Create non-cumulatives with the program BW: Initialization of Opening Non-Cumulatives in Transfer Structure (RMCBINIT_BW).
2. Initialize the movements/revaluations with the program RMCBNEUB/RMCBNERP.
3. Post in the InfoCube using the update method Creation of Non-Cumulatives fromthe InfoSource 2LIS_03_BX.
4. Post in the InfoCube using the update method Initialization of the Delta Processfrom the InfoSources 2LIS_03_BF and 2LIS_03_UM.
28
Refer to SAP Note 0643687 (Compression of Non-Cumulative InfoCubes)regarding the subsequent steps for compression.
5. Compression of the request from 2LIS_03_BX with update of the marker.
6. Because in this case you are posting movements and revaluations in theInfoCube that occurred before the non-cumulative creation and which lead to this non-cumulative creation, you must execute a compression without updating the marker. Formore information.
7. Thereafter, you can transfer new movements and revaluations to the BW systemas usual (for performance reasons, we recommend that you regularly compresswith updates of the marker.
5. Enhancing Master Data
5.1. Material Master
In order to capture MRP of the Material, Generic DataSource was created at ISR side. ThisGeneric DataSource was used to extract MRP data into Material Master.
Generic DataSource: ZMRP_MTL_ATTR
T-Code: RSO2
Click on Display to see the details of Generic DataSource.
29
Click on Generic Delta to see the Delta Mechanism for this DataSource
30
View upon which DataSource is built: Z_MRP_VIEW
Go to T-Code SE11
This View is created by joining Tables KONP and A073
31
On the BW side, Material Master:
Material master is loaded by following datasources:
0MATERIAL_ATTR ZMRP_MTL_ATTR
32
5.2. Plant Master
In order to capture City and Mall Information, Plant wise City and Mall data is loaded intoPlant (Store) Master through Excel File.
Plant Master Data is updated by the following two InfoSources:
Plant Attributes 0PLANT_ATTR Additional Plant Master ZSITE_MAS
33
Appendix A
BW CMOD Customer Exits
T-Code: CMOD
Click on Display to Enter the Next Screen
Click on EXIT_SAPLRRS0_001 to Continue
34
Click on ZSRSRU01 to enter the screen where Codes are written
Following Codes are used in Bill wise Analysis Report
*&--------------------------------------------------------------------**& Include ZXRSRU01*&--------------------------------------------------------------------*
DATA: L_S_RANGE TYPE RSR_S_RANGESID.DATA: LOC_VAR_RANGE LIKE RRRANGEEXIT.DATA: l_s_var LIKE RRRANGEEXIT.
data: l_text type rstxtsh.
35
CASE I_VNAM.
WHEN 'ZVTEXT1'.
IF I_STEP = 2.
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGEWHERE VNAM = 'VAR_20081010080528'.CLEAR L_S_RANGE.
*clear l_text.*l_text = LOC_VAR_RANGE-LOW.
l_s_range-low = LOC_VAR_RANGE-LOW.l_s_range-sign = 'I'.l_s_range-opt = 'EQ'.
append l_s_range to e_t_range.
EXIT.ENDLOOP.ENDIF.
WHEN 'ZVTEXT2'.
IF I_STEP = 2.
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGEWHERE VNAM = 'VAR_20081010081428'.CLEAR L_S_RANGE.
*clear l_text.*l_text = LOC_VAR_RANGE-LOW.
l_s_range-low = LOC_VAR_RANGE-LOW.l_s_range-sign = 'I'.l_s_range-opt = 'EQ'.
append l_s_range to e_t_range.
EXIT.ENDLOOP.ENDIF.
36
WHEN 'ZVTEXT3'.
IF I_STEP = 2.
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGEWHERE VNAM = 'VAR_20081010081452'.CLEAR L_S_RANGE.
*clear l_text.*l_text = LOC_VAR_RANGE-LOW.
l_s_range-low = LOC_VAR_RANGE-LOW.l_s_range-sign = 'I'.l_s_range-opt = 'EQ'.
append l_s_range to e_t_range.
EXIT.ENDLOOP.ENDIF.
WHEN 'ZVTEXT4'.
IF I_STEP = 2.
LOOP AT I_T_VAR_RANGE INTO LOC_VAR_RANGEWHERE VNAM = 'VAR_20081010081519'.CLEAR L_S_RANGE.
*clear l_text.*l_text = LOC_VAR_RANGE-LOW.
l_s_range-low = LOC_VAR_RANGE-LOW.l_s_range-sign = 'I'.l_s_range-opt = 'EQ'.
append l_s_range to e_t_range.
EXIT.ENDLOOP.ENDIF.
ENDCASE.
37
Appendix B
Relevant Screen Shots
1. Data Warehousing Workbench: Modeling
38
2. Retail Area
3. Inventory Area
39
4. Business Content
40
5 Transport Connection
41
Appendix C
C.1 Important T-Codes
C1.1 BW
RSA1 Data Warehousing Workbench: Modeling
RSA7 Delta Queue
SE09 Transport Organizer
STMS Transport Management System
SM37 Simple Job Selection
SM50 Process Overview
RSA5 Installation of DataSource from Business Content
RSA6 Postprocess DataSources
RSKC Maintenance of Permitted Extra Characters in BW
PFCG Role Maintenance
RSPC Process Chains
SU01 User Maintenance
RSMO Monitor Administrator Workbench
C1.2 ISR
LBWE LO Cockpit
RSA3 Extractor Checker
RSA5 Installation of DataSource from Business Content
RSA6 Postprocess DataSources
RS02 Maintain Generic DataSources
SE11 ABAP Dictionary: Initial Screen
SE16 Data Browser Initial Screen
42
Appendix D
Notes Implemented
SAP Note 1139547: Transport of InfoObjects RC = 8; follow-on note to 1100575
SAP Note 1116174: MultiProvider on non-cumulative cube
43