Download as pdf or txt
Download as pdf or txt
You are on page 1of 51

Overview BW Retail Master Data

Overview Retail
Master Data

Overview Retail Master Data Extractors

Article Hierarchy
Article List

Price Level Group

Structured article

Attributes Product + Location

Other enhancements of Master Data

Additional information

© SAP 2009 Overview BW Retail Master data / Page 2


Overview Retail
Master Data

Overview Retail Master Data Extractors

Article Hierarchy
Article List

Price Level Group

Structured article

Attributes Product + Location

Other enhancements of Master Data

Additional information

© SAP 2009 Overview BW Retail Master data / Page 3


Installation of DataSource from Business
Content

Transaction
SBIW or RSA5

© SAP 2009 Overview BW Retail Master data / Page 4


Example MD Data Extraction from table MARA
into SAP BW InfoObject 0MATERIAL

Source table Extract structure


MARA
BIW_MARA_S

MATNR Article attributes

BI Master data Table Data Source


/BI0/PMATERIAL
0ARTICLE_ATTR

0MATERIAL

0MATERIAL_ATTR

© SAP 2009 Overview BW Retail Master data / Page 5


Retail relevant DataSources in different app.
components
Application Component
Mat. Manage. (MM-IO) Logistics (LO-IO)
Retail (IS-R-IO)
- Stock Type - Sold to Party
- Ass. Grade - Customer
- Order reason
- Assortment - Supplying plant
- Purchasing group
- Depart. No. - Article
Financial (FI-IO) - Purchasing Org.
- Price band - Ship to party
- Merchandise Cat.
- Promotion - Company code
- Storage Location - Site
- Promotion type
- Vendor
- Season
- Supplier
- Store group Sales & Distrib (SD-IO)

- rejection Reason
- Comp: - Product catalog
Merch Cat/Article - Consumer

InfoObjects
Promotion/Article - Article type
- Prod. Hierarchy
- Sales group

© SAP 2009 Overview BW Retail Master data / Page 6


Retail specific DataSources - Part I

DataSource InfoSource Remarks


0ARTICLE_ATTR 0MATERIAL for loading general material
data

0RT_SALES_ATTR 0MAT_SALES for loading sales data for the


article

0RT_PLANT_ATTR 0MAT_PLANT for loading plant data for the


article

0RT_ST_LOC_ATTR 0MAT_ST_LOC for loading storage location


data for the article.

© SAP 2009 Overview BW Retail Master data / Page 7


Retail specific DataSources - Part I

DataSource InfoSource Remarks


0PLANT_ATTR 0PLANT_ATTR to determine
0LOC_CURRCY if initial from
0SALESORG
0PLANT_TEXT 0PLANT_TEXT for loading sales data for the
article

0PLANT_LKLS_HIER

0RT_WRF1_ATTR 0RT_WRF1_ATTR to supply attributes store


opening date, store closing
date and lock dates

Recommended changes on delivered version:


The hierarchies should be changed to not
time-dependent

© SAP 2009 Overview BW Retail Master data / Page 8


Loading sequence for InfoObject 0PLANT

Loading Sequence should be:

Material (0MATERIAL)
Company Code (0COMP_CODE)
Sales Organization (0SALES_ORG)
Plant (0PLANT)

see note 750322

© SAP 2009 Overview BW Retail Master data / Page 9


Overview Retail Master
Data

Overview Retail Master Data Extractors

Article Hierarchy
Article List

Price Level Group

Structured article

Attributes Product + Location

Other enhancements of Master Data

Additional information

© SAP 2009 Overview BW Retail Master data / Page 10


Business Concept of Article Hierarchy

An Article Hierarchy in ERP Retail can be used to hold any given hierarchical
Article Grouping e.g. a combination of articles in groups from a sales perspective
The Article Hierarchy can be linked to shops to portray the presentation of certain
sub-ranges on the sales floor (physical and logical segmentation of a shop)
Optional Integration to Planning, Operations and Reporting on different levels of
aggregation
The Article Hierarchy is designed to serve Category Management purposes. It
focuses on customer needs, whereas Merchandise Categories observe physical
attributes of the goods.

© SAP 2009 Overview BW Retail Master data / Page 11


Merchandise Category Hierarchy and Article
Hierarchy

Examples of Characteristics Values


Article Hierarchies active MCH-level 4 red
planned
Company Color blue
Company Company
green

planned MCH-level 3 10

Area Size 12
Category Area
14
Profile
MCH-level 2

Theme
Subcategory Theme

MCH-level 1

Brand
Segment Item 123456789
Brand

Basic MC

Article group
Sub segmentArticle group

Example of
Assignment MC Hierarchy
Shop/Department
© SAP 2009 Overview BW Retail Master data / Page 12
Article Hierarchy: General Introduction

Key Message: For any new customer project it is strongly recommended


to use the new article hierarchy solution available starting with ERP 2005

Decisions to take before using the article hierarchy


Usage of a time dependent Article hierarchy necessary higher complexity in SAP ERP und SAP BW
Usage of multiple assignment
Define the category level in the Article Hierarchy customizing
Usage of the shop concept (together with the multiple assignment)
Usage of new attributes like price level group, strategy, role …
Usage of one chain wide AH or multiple distribution chain article hierarchies
BW Extraction necessary
The last and final step must be the activation of the Article Hierarchy

© SAP 2009 Overview BW Retail Master data / Page 13


Objects of the Article Hierarchy

ERP DataSources:
0RF_HIEID_ATTR, 0RF_HIEID_TEXT
DataSources 0RF_ARTHIERx_ATTR (x = 1 until 10), 0RF_ARTHIERx_TEXT (x = 1 until 10)
0RF_PRODUCT_ATTR, 0RF_PRODUCT_TEXT
BW DataSources:
0RF_ARTHIER_ACT

0CM_MCATDIV_ATTR, 0CM_MCATDIV_TEXT, 0CM_CDTx_ATTR (x = 1 until 7), 0CM_CDTx_TEXT (x = 1 until 7)


InfoSources 0RF_SKU_ATTR, 0RF_SKU_TEXT
0RF_ACT_HIER

0CM_HIEID, 0CM_MCATDIV, 0CM_CDT1, 0CM_CDT2, 0CM_CDT3, 0CM_CDT4, 0CM_CDT5, 0CM_CDT6,


DataTargets 0CM_CDT7, 0CM_SKU or 0RF_SKU, 0RF_DS01

© SAP 2009 Overview BW Retail Master data / Page 14


Article Hierarchy in SAP ERP

1. external number assignment

2. Client-wide or distribution
chain-dependent?
3. Use Reference Hierarchy? 7. Maintain description for
several languages

4. Upload to BI?

5. Allow multiple article assignment?


6. Time-phased article hierarchy?

Transactions WMATGRP01 (02-08)

© SAP 2009 Overview BW Retail Master data / Page 15


Definition of a Category

The category defines the highest assortment-forming node

If multiple article assignment is used, the category is the node used for the shop
assignment

If multiple article assignment is used, the article is always assigned uniquely


within one category

© SAP 2009 Overview BW Retail Master data / Page 16


Overview Retail Master
Data

Overview Retail Master Data Extractors

Article Hierarchy
Article List

Price Level Group

Structured article

Attributes Product + Location

Other enhancements of Master Data

Additional information

© SAP 2009 Overview BW Retail Master data / Page 17


Article List: General Introduction

Dynamic article lists


Consist of stored selection criteria, with which the actual article data
can be determined each time
Static article lists
Consist of both the selection criteria and the dependent articles,
show those articles, that have been assigned uniquely
Article list hierarchy
To create and maintain article lists, the creation of exactly one article
list hierarchy is necessary.
Each article list is assigned to exactly one end node in the hierarchy
The hierarchic grouping is concise and facilitates the selection of a
specific article list
Article lists can be exchanged with a BI
E.g. use a query for bestseller/slowseller articles and export this list
to SAP ERP
© SAP 2009 Overview BW Retail Master data / Page 18
Objects of the Article List

ERP DataSources:

DataSources 0RF_ARTLIST_ATTR, 0RF_ARTLIST_TEXT, 0RF_ARTLIST_HIER


BW Business Server page for Back posting from a query:
RSBCT_RFASH_ALI

InfoSources 0RF_ARTLIST_ATTR

DataTargets 0RF_ARTLIST, 0RF_DS02

© SAP 2009 Overview BW Retail Master data / Page 19


Article/Material List in SAP ERP

Article List (0RF_ARTLIST)


Object for grouping of articles („My favorite Articles“)
Can be created in ERP and in SAP BI Transaction WRF_AL

Usage
Maintenance of „personal“
groups of articles
Reporting of „personal“ groups
of articles in SAP BI

© SAP 2009 Overview BW Retail Master data / Page 20


Article List Closed Loop

0RF_DS02

© SAP 2009 Overview BW Retail Master data / Page 21


Article List Creation in SAP BW and Transfer
to SAP ERP

Export Article List to R/3

Customizing of
Web Template

© SAP 2009 Overview BW Retail Master data / Page 22


Overview Retail Master
Data

Overview Retail Master Data Extractors

Article Hierarchy
Article List

Price Level Group

Structured article

Attributes Product + Location

Other enhancements of Master Data

Additional information

© SAP 2009 Overview BW Retail Master data / Page 23


Price Level Group: General Introduction

Price Level Group

allows analysis of sales data in BW

consists of Price Patterns with validity timeframe

Price Patterns consist of Price Levels with Price Threshold


and Price Band Category

Usage of Price Level Groups


can be assigned to levels
(nodes) of the article hierarchy
can be assigned to
Merchandise categories

The price pattern can be


used for reporting sales
data in BI.

© SAP 2009 Overview BW Retail Master data / Page 24


Objects of the Price Level Group

DataSources ERP DataSources:


0RF_PRGRP_ATTR, 0RF_PRGRP_TEXT

InfoSources 0RF_PRGRP_ATTR

DataTargets 0RF_PRC_GRP, 0RF_PRC_GTP, 0RF_PRC_PAT

© SAP 2009 Overview BW Retail Master data / Page 25


Overview Retail Master
Data

Overview Retail Master Data Extractors

Article Hierarchy
Article List

Price Level Group

Structured article

Attributes Product + Location

Other enhancements of Master Data

Additional information

© SAP 2009 Overview BW Retail Master data / Page 26


Structured articles: General Introduction

In order to simplify the logistic handling of goods, there are so called


“structured articles “ in a retail environment, a combination of several
homogeneous single articles, which only differentiate in certain
characteristics (sizes, colors etc..).
As the single articles represent the sold units, it may be necessary to get
information on single article basis (components) in reports although it is not
present in all logistic process steps.
An additional dissolution of
structured articles was not
possible in SAP BI until
now.

© SAP 2009 Overview BW Retail Master data / Page 27


Objects for structured Article handling

ERP Master DataSources:


0RF_STRUKMAT_ATTR, 0RT_SPSTRTP_TEXT, 0RT_SPSTRUC_ATTR
DataSources ERP Movement DataSources>
2LIS_03_BX, 2LIS_03_BF, 2LIS_02_SCL

InfoSources 2LIS_03_BF_TR, 2LIS_03_BX_TR, 2LIS_02_SCL

DataTargets 0RT_DS02 and all logic Data Targets connected to 2LIS_03_BX, 2LIS_03_BF and 2LIS_02_SCL

© SAP 2009 Overview BW Retail Master data / Page 28


Prerequisites: Customizing
in SAP ERP – Part I

In Customizing in ERP under


Logistics - General Material Master Retail-Specific Settings
Settings for Structured Materials Structured Article in Logistics
Process,
you have made settings for the purchase order and for goods receipt
to determine if, and for which levels (for example, site), structured
articles are to be broken down into their components.

© SAP 2009 Overview BW Retail Master data / Page 29


Prerequisites: Customizing
in SAP ERP – Part II

Material Transaction key Plant category Splitting type,


Transaction key 100 (order) category structure

10 100 B 0
It's specified per material type of
structured articles whether they are 10 100 A 1

broken down into their components in 10 200 B 0


the display options of the purchasing 10 200 A 1
documents of a order or not ( only
11 100 B 0
display option see ME23N)
11 100 A 1
This information is not transferred to 11 200 B 0
BI so far! 11 200 A 1

Transaction key 200 ( goods receipt ) 12 100 B 0

12 100 A 1
It's specified per material type of
12 200 B 0
structured articles whether they are
12 200 A 1
broken down physically into their
components in DC or store.

Table TWZLA

© SAP 2009 Overview BW Retail Master data / Page 30


Extraction of the Movement Data from Structured
Articles

SAP ERP explodes document items that contain a structured article into additional items
for the components of a prepack ( possible for DataSources 2LIS_02_SCL, 2LIS_03_BF
and 2LIS_03_BX ).

The extraction occurs by means of a standard implementation of


WRF_BWEXT_STRUKTART of BAdIs RS05_SAPI_BADI (BW Service APIs with Business
Add-Ins). This implementation takes account of the Customizing settings mentioned
under Prerequisites above.

This implementation is only available in systems with Enterprise Add- On Retail.

Important Note:
The Standard implementation is delivered as active, that means each customer how is
not interested in the explosion could switch of the implementation and increase the
performance.

© SAP 2009 Overview BW Retail Master data / Page 31


Splitting Structured Articles into Components
stored into Foundation DSO 0RT_DS02

This DataStore object is used to consistently store data from DataSource


0RT_SPSTRUC_ATTR which contains the customizing information about explosion/ non-
explosion of articles.

The information is required to balance the article movements from ERP (DataStore object
0RSL_DS51) with the sales data (DataStore object 0RT_DS54) for the stock ledger.

© SAP 2009 Overview BW Retail Master data / Page 32


Note 846106: Exploding structured articles

In order not to falsify business content in BI with additional data from explosion of
structured articles, this data is deleted in the start routines of InfoSources
2LIS_02_SCL, 2LIS_03_BF und 2LIS_03_BX (Which means you can analyze only
the unexploded structured article in this case).

If the data should be used to analyze both the unexploded structured article and
the exploded structured article please follow procedure described in note 846106.

Please also refer to note 1240567, 1325650

© SAP 2009 Overview BW Retail Master data / Page 33


Overview Retail Master
Data

Overview Retail Master Data Extractors

Article Hierarchy
Article List

Price Level Group

Structured article

Attributes Product + Location

Other enhancements of Master Data

Additional information

© SAP 2009 Overview BW Retail Master data / Page 34


Objects for Product/Location handling

Key Message: SAP recommends to use 0RT_DS01 instead of InfoObject 0MAT_PLANT. Please also
refer to note 1119196.

ERP DataSources for InfoObject 0MAT_PLANT


0MAT_PLANT_ATTR, 0MAT_PLANT_TEXT
ERP DataSources for DSO 0RT_DS01
0RT_MAT_PLANT_ATTR
DataSources
ERP DataSources for additional information
0RT_MBEW_PRICE_ATTR, 0RT_MBEW_ATTR, 2LIS_03_BF, 0SCM_FRE_MAT_PLANT_ATTR,
0RT_ORGPRICE_ATTR

InfoSources 2LIS_03_BF_TR, 0RT_MAT_PLANT_ATTR, 0SCM_FRE_MAT_PLANT_ATTR

DataTargets 0RT_DS01, 0MAT_PLANT

© SAP 2009 Overview BW Retail Master data / Page 35


DataSources of Foundation DSO 0RT_DS01

DSO 0RT_DS01
Product/Location

0RT_MBEW_PRICE_ 0RT_MBEW 0RT_ORGPRICE 2LIS_03_BF 0RT_MAT_PLANT_ATTR 0SCM_FRE_MAT_PLANT_ATTR


ATTR _ATTR _ATTR

ERP SCM

VPNEU BWKEY VPR_BT 0RT_SSMFGR MAABC 0FRE_SELCLS

VRKME BWTAR VWEAR_BT SERVG 0FRE_PLNPUR

VRKPE VERPR VRKPE_BT EKGRP 0FRE_MINSTK

VWEAR PEINH VKMEIN_BT 0BASE_UOM


DISMM
WAERS VPR_NT 0FRE_SERLEV
BWSCL
VWEAR_NT 0FRE_REPLST
VRKPE_NT

VKMEIN_NT

© SAP 2009 Overview BW Retail Master data / Page 36


Moving Average Price Handling in Trading
Content – Part I

Business Context: the missing Moving Average Price

Whether it is the inventory manager, a replenishment specialist, a category manager or


an assortment specialist, the success of most of the retailer’s key role owners will be
measured against their investment.

The success of the investment can be ensured by tickling consumer demand, keep the
costs low and keep the inventory low throughout the considered time frames.

This is typically monitored by analyzing the sales at retail, sales at cost, the gross margin
(percentage), average inventory and ultimately the GMROI, which expresses the overall
success of your investment.

The Moving Average Price plays an important role in this formula since the gross margin,
the numerator of the GMROI formula, is the difference of sales at retail and sales at cost.

The sales costs are evaluated by taking the sales units and multiplying this by the moving
average price.

This means that the moving average price has to be available in BI.

© SAP 2009 Overview BW Retail Master data / Page 37


Moving Average Price Handling in Trading
Content – Part II

1. ERP does the job 2. New challenges


Retail Analytical Application
Data Marts
Retail Analytical Application

Data Marts
Sales units Inventory units
Sales at cost Inventory at cost
Sales at retail Inventory at retail
Sales at retail w/tax Inventory at retail w/tax Sales units Inventory units
Sales at cost Inventory at cost
SAP BW Sales at retail Inventory at retail
Sales at retail w/tax
(Staging)
Retail BI Foundation
POS movements Material movements

Sales units Inventory units Pipe MAP


SAP ERP Sales at cost Inventory at cost
Sales at retail Inventory at retail
Sales at retail w/tax Inventory at retail w/tax Sales units Inventory units
Sales at retail Inventory at retail
POS Inventory Sales at retail w/tax
SAP ERP
management MAP
management
POS LIME
Inventory
management
POS

Needed
Needed e.g.
e.g. for
for
current
current scenario
scenario of
of F&R
F&R
Analytics,
Analytics, POS
POS DMDM

© SAP 2009 Overview BW Retail Master data / Page 38


MAP Customizing in SAP BW

© SAP 2009 Overview BW Retail Master data / Page 39


Customer Calculation of the Moving Average
Price in SAP BW

Customer Calculation of the Moving Average in SAP BW:


Starting BI Content 704 it is possible to implement an own customer logic to calculate the moving average.
Please use the method GET_MOVING_AVERAGE of BADI RSBCT_RPA_GET_MOVING_AVERAGE.

There exits a sample implementation GET_MOVING_AVG_FROM_MATL_GROUP that reads a


High level Margin from the InfoObject 0MATL_GROUP. This sample will not be executed and
can be used as a template for a customer implementation.

Please refer to Notes:


-1159498
-1159170

© SAP 2009 Overview BW Retail Master data / Page 40


Overview Retail Master
Data

Overview Retail Master Data Extractors

Article Hierarchy
Article List

Price Level Group

Structured article

Attributes Product + Location

Other enhancements of Master Data

Additional information

© SAP 2009 Overview BW Retail Master data / Page 41


Trade Foundation DataStore Objects – Part I

Technical Name Remarks


name
0RT_DS01 Product and Location Please see chapter Product and Location Attributes for details
Attributes
Used in F&R, POS Scenario
0RT_DS02 Splitting Structured Articles Please see chapter Structured Article for details.
into Components
0RT_DS03 Valuation Area This DSO is used to consistently store data from DataSource
0RT_VALAREA_ATTR. This information is required to balance
the sales data (DSO 0RT_DS54) with the revaluation at retail
data (DSO 0RT_DS53) for the stock ledger.

0RT_DS04 Value-Only Article for Each This DSO is used to consistently store data from DataSource
Merchandising Group and 0RT_MGR_VALART_ATTR. This information is currently
Plant required to balance the sales data (DSO 0RT_DS54) with the
article movements and revaluations from ERP (DSO
0RSL_DS51, 0RT_DS52, and 0RT_DS53) for the stock ledger.

0RT_DS05 Identification of Article This DSO is used to store data consistently from DataSource
Type (Retail) 0RT_MATTYPE_ATTR. This information is currently required to
filter movement data from ERP for the stock ledger.

© SAP 2009 Overview BW Retail Master data / Page 42


Trade Foundation DataStore Objects – Part II

Technical Name Remarks


name
0RT_DS06 Purchase This DSO is used to store purchasing conditions at the material and site
Conditions at Site levels. Together with DataStore object 0RT_DS07, you can maintain the
Level availability of purchase prices in SAP BI. This allows for the sales data to
be enhanced with cost information for easy margin analysis, for example.

Used in Demand Management Scenario


0RT_DS07 Purchase This DSO is used to store purchase conditions at material and purchasing
Conditions at organization level. Together with DataStore object 0RT_DS06, you can
Purchasing maintain the availability of purchase prices in SAP BI. This allows you to
Organization enhance sales data with cost information for example, so that you can
Level analyze margins more easily. Service class /RTF/CL_PURCH_PRICE
provides you with read access to the purchase conditions. Note that
DataStore object 0RT_DS11 is also required to determine purchase prices.

Used in Demand Management Scenario


0RT_DS08 Promotion Offers This DSO is used to store offers within a promotion. Together with DSO´s
0RT_DS09 and 0RT_DS10, you can access article information about a
retail promotion in the BI system. Service class /RTF/CL_PROMOTION
provides read access to the promotion information.

Used in Demand Management Scenario

© SAP 2009 Overview BW Retail Master data / Page 43


Trade Foundation DataStore Objects – Part III

Technical Name Remarks


name
0RT_DS09 Promotion Offer This DSO is used to store the respective product groups for promotion
Product Groups offers. Using DataStore objects 0RT_DS08 and 0RT_DS10, you can access
article information on a retail promotion in the BI system.

Used in Demand Management Scenario


For more information about the structure of the promotion information, see the
documentation for the relevant DataSources (0RT_PROMO_OFFER,
RT_PROMO_OFFERGROUP, and 0RT_PROMO_OFFER_PRODASSIGN).
0RT_DS10 Promotion This DSO is used to store the assignments of individual articles to product
Product groups within a promotion. This is the case if the respective product group
Assignment to has the "individual combination" type. Together with DataStore objects
Offer Groups 0RT_DS08 and 0RT_DS09, you can access article information about a
retail promotion in the BI system.

Used in Demand Management Scenario


0RT_DS11 Supplying This DSO is used to store the supplying plants (distribution centers) for a
Plants for store to reflect the contents of table WRF3. Information about the supplying
Stores plants for a store is especially required to determine the purchase prices of
articles.

Used in Demand Management Scenario

© SAP 2009 Overview BW Retail Master data / Page 44


Overview Retail Master
Data

Overview Retail Master Data Extractors

Article Hierarchy
Article List

Price Level Group

Structured article

Attributes Product + Location

Other enhancements of Master Data

Additional information

© SAP 2009 Overview BW Retail Master data / Page 45


Important: Customize Material Number Display
in BI

© SAP 2009 Overview BW Retail Master data / Page 46


Retail Terminology – Activating Retail Short
Text Replacement

Many business processes in Retail use SAP BI to evaluate data that comes from
various different components, for example, from SAP ERP or SAP R/3 but also from
SAP Forecasting and Replenishment (SAP F&R), which is part of mySAP SCM.
While SAP ERP or SAP R/3 uses terms that are linked to its industry sectors
(material and plant in production, article and site in SAP Retail), in other components
you will find the more universally-employed terms product and location.
When evaluating data from different sources it is best to use consistent terminology.
It is therefore possible to convert the screen in your SAP BI system to display the
more universal terms product and location in several languages. This conversion is
performed with short text replacement.

In the SAP Service Marketplace, you can find out the languages and components for
which short text replacement is available and how you activate it
( http://service.sap.com/retail) under Expert Knowledge Corner Across
Components Short Text Replacement in Retail Short Text Replacement.
Please see also Note 897714 - Activating Retail Short Text Replacement

© SAP 2009 Overview BW Retail Master data / Page 47


Master Data InfoSources Used from Other
Application Components - Part I

InfoObject Name Apllication Component

0PUR_REASON Customer Number LO-IO

0RT_MGRAIW Material Number LO-IO

0RT_REGVEND Plant Material LO-IO

0STOCKCAT Material Number Compounded to Sales LO-IO

0STOR_LOC Receiving/Issuing Site LO-IO

0SUPPLIER Plant LO-IO

0VENDOR Ship-To Party LO-IO

0CONSUMER Sold-To Party LO-IO

0DISTR_CHAN Supplying Plant LO-IO

0DIV_HEAD Credit/Debit Indicator MM-IO

0DOC_CATEG Invoicing Party MM-IO

0DOC_TYPE Material Category MM-IO

0ITEM_CATEG Merchandise Category MM-IO

0MATL_TYPE Stock Planner MM-IO

0PRODCAT Purchasing Organization MM-IO

0PROD_HIER Purchasing Group MM-IO

© SAP 2009 Overview BW Retail Master data / Page 48


Master Data InfoSources Used from Other
Application Components - Part II

InfoObject Name Apllication Component

0CUSTOMER Order Reason MM-IO

0ARTICLE Merchandise Category (IS) MM-IO

0MAT_PLANT Account Number of Regular Vendor MM-IO

Stock Categories in the Logistics Information


0MAT_SALES MM-IO
System

0MOVE_PLANT Storage Location MM-IO

0PLANT Goods Supplier MM-IO

0SHIP_TO Vendor Number MM-IO

0SOLD_TO Consumer SD-IO

0SUPP_PLANT Distribution Channel SD-IO

0DCINDIC Division in Order Header SD-IO

0INV_PARTY Sales Document Category SD-IO

0MATL_CAT Sales Document Type SD-IO

0MATL_GROUP Sales Document Type SD-IO

0MRP_CONTRL Material Type SD-IO

0PURCH_ORG Catalog Number SD-IO

0PUR_GROUP Product Hierarchy SD-IO

© SAP 2009 Overview BW Retail Master data / Page 49


Master Data InfoSources Used from Other
Application Components - Part III

InfoObject Name Apllication Component

0REASON_REJ Reason for Rejection of Offers and Orders SD-IO

0SALESDEAL Sales Deal SD-IO

0SALESORG Sales Organization SD-IO

0SALES_GRP Sales Group SD-IO

0SALES_OFF Sales Office SD-IO

0COMP_CODE Company Code FI-IO

0COSTELMNT Cost Type CO-IO

0CO_AREA Controlling Area CO-IO

0REPTT Time Type for Reporting PT-IO

0WAGETYPE Wage Type PY-IO

0COUNTRY_ID Country Grouping PY-IO

0VERSION Version SAP-R/3-IO

© SAP 2009 Overview BW Retail Master data / Page 50


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.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge 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 in several other countries all over the world. All other product and service names mentioned and associated logos displayed
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document
contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,
and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or
other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of
merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation
shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these
materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch
SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.
Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.
SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, SAP Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Services sowie die
dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähnten Namen
von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu
Informationszwecken. Produkte können länderspezifische Unterschiede aufweisen.
Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen
Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmten
Geschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht die
Richtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder
ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zweck
sowie für die Gewährleistung der Nichtverletzung geltenden Rechts.
SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendung
dieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.
Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinks
zugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über
Internetseiten Dritter ab.
Alle Rechte vorbehalten.

© SAP 2009 Overview BW Retail Master data / Page 51

You might also like