Professional Documents
Culture Documents
Abstract: This chapter covers the basic aspects and concepts of data modeling with SAP Business Information Warehouse (SAP BW).
SAP UA
Agenda
2010 SAP AG
Page 2
SAP UA
2010 SAP AG
Page 3
SAP UA
2010 SAP AG
Page 4
SAP UA
What is an InfoObject?
InfoObjects are the bricks to build data structures inside SAP BW. InfoObjects represent business objects from an end users view. The most important InfoObject types used for business analysis are Characteristics and Key Figures.
Page 5
2010 SAP AG
SAP UA
InfoObject: Characteristics
A Characteristic represents a business object (or concept, business term, business entity). A Characteristic may have attributes which describes the business object in more detail. Example: InfoObject Customer is a characteristic with attributes such as Customer Number, ZIP Code, Region, , , g , etc. The attributes Customer Number, ZIP Code, Region, etc. are also managed as Characteristics and may have their own attributes. Note: What SAP calls a Characteristic is often referred to in the data warehouse community as a Dimension.
2010 SAP AG
Page 6
SAP UA
A Key Figure (or variable, measure) is oftenly used to document the performance of a business process over time. It can be found in document records such as invoice, delivery note, purchase order, or goods receipt. Example: InfoObject Revenue or Sales Amount, etc. Note: InfoObjects are unique inside SAP BW, and they are used to build the data structures for analysis requirements. Conceptually unique: the semantics (meaning) of an InfoObject is uniquely defined system-wide inside SAP BW. Logically unique: the data type, value range or field length is uniquely defined system-wide inside SAP BW. From the technical point of view, an InfoObject can viewed as a database field.
2010 SAP AG Page 7
SAP UA
SAP BW InfoObjects
R/3
SAP ERP
CO
Accounting
Table Costcenter
COSTC
...
InfoObject
"0COSTCENTER"
Mapping
HR
Human Ressources
Table Employee
EMPLO COST_CENTER ...
2010 SAP AG
SAP UA
2010 SAP AG
Page 9
SAP UA
InfoProviders: Are data storage inside SAP BW May store data records physically (persistent) May also be used to access data stored outside SAP BW virtually (transparent views) May be accessed with front end tools such as SAP BusinessExplorer
Note: A query is a view to data within an InfoProvider and does not contain physical data.
2010 SAP AG
Page 10
SAP UA
InfoProviders
DataStore Objects
Contain detailed data. Used for high data volumes stored in normal database tables. Oft used as data source for InfoCubes. Often d d t f I f C b
VirtualProviders
Data stored somewhere outside SAP BW. Some ERP systems provide data storage which may be accessed directly by SAP BW without changing the end user s view to the data.
2010 SAP AG Page 11
SAP UA
InfoCubes
Provide data storage used for reporting and online analysis. Consist of Key Figures and Characteristics. Contain data stored multi-dimensionally and often aggregated (week, month). Use star database schema, consisting of a fact table surrounded schema by dimension tables. Use a maximum of 3 + 13 dimension tables. 3 dimension tables are pre-defined by SAP.
Time, Unit and DataPackage (for technical information)
13 dimensions may be used by InfoCube developers. Note: In practice, good InfoCube design should not exceed 6-8 dimensions (+ the 3 above) so 13 dimensions are plenty.
2010 SAP AG Page 12
SAP UA
DataStore Objects
Contain single data records such as invoices, purchase orders or customer order items. Consist of key fields (such as order number, order position number) and data fields (Key Figures and Characteristics such as sales amount, net value, customer id, material number). Store data records in relational database tables. Often contain massive volumes of data.
2010 SAP AG
Page 13
SAP UA
Data Warehouse, Operational Data Store and Data Marts are general layers in a Data Warehouse Architecture.
BI1-M2-01-Data Warehouse
Data Warehouse and Operational Data Store may be implemented with DataStoreObjects. Data Marts will be implemented with InfoCubes.
2010 SAP AG
Page 14
SAP UA
Agenda
2010 SAP AG
Page 15
SAP UA
InfoObjects
Characteristics
Customer, Region, Zip Code,
Units
Unit of Measurement, Currency,
Time
Calender Year, Fiscal Year, Month, Day, Quarter, .
2010 SAP AG
Page 16
SAP UA
Amount, Quantity, ..
2010 SAP AG
SAP UA
515
Mar
Apr
May
Jun
Aggregation: Last Value, gg g , Maximum, Average Reference Characteristic, e.g. Quarter Aggregation: Summation, Minimum, Maximum The reference characteristic allows the use of a function to aggregate data instead of summation. Example: Number of Employees at the end of the quarter. Sum does not make sense!
Page 18
2010 SAP AG
SAP UA
If the Key Figure is noncumulative (e.g., warehouse stock), this field defines an InfoObject representing noncumulative change. This InfoObject is either positive or negative. So, the stock amount can be calculated from it.
Two fields are used to calculate the noncumulative amounts. Inflow is the InfoObject which represents the stock inflow amount. Outflow is vice versa.
Page 19
2010 SAP AG
SAP UA
2010 SAP AG
Page 20
SAP UA
2010 SAP AG
Page 21
SAP UA
Conversion Routine
Database values Are stored in internal format appropriate to the database Date as YYYYMMDD Are presented to a user in external format according to his local settings, e.g., in g, Europe Date: DD.MM.YYYY Numbers: 1.234,56 US Date: MM/DD/YYYY Numbers: 1,234.56 Transformation external internal format is performed by a conversion routine
2010 SAP AG Page 22
SAP UA
Alphanumeric database fields Datatype CHAR in SAP Can store character and number values Have conversion exit ALPHA as default Eliminates leading blanks after user input User input of RB0010 and RB0010 refers to same object p j Stores numbers with leading 0s in database Numeric values are stored in natural order in database, e.g. 0002 first, then 0010 Material Group in SAP Business Content has numerical values with trailing blanks Conversion exit ALPHA must not be used
2010 SAP AG
Page 23
SAP UA
Database field Material often requires special treatment. Datatype CHAR in SAP Conversion exit MATN1 is used Edit format can be defined in transaction OMSL E.g. _ _-_ _ _ _ User Input RB-0010 is stored as RB0010
Since the OMSL format setting is system-wide, we do not use it in the Bike Company Curriculum.
2010 SAP AG
Page 24
SAP UA
2010 SAP AG
Page 25
SAP UA
SAP UA
Time Characteristics
Time characteristics are always necessary and define the timerelated reference point for data analysis purposes. Time characteristics are predefined by SAP and cannot be changed.
2010 SAP AG
Page 27
SAP UA
Units/Currencies
Units and Currencies are used to define Key Figures in more detail. A Unit may be an InfoObject which defines the Unit of a Key Figure. A Currency may be an InfoObject which defines the Currency of a Key Figure Examples:
0CURRENCY 0BASE_UOM
2010 SAP AG
Page 28
SAP UA
Agenda
2010 SAP AG
Page 29
SAP UA
2010 SAP AG
Page 30
10
SAP UA
2010 SAP AG
Page 31
SAP UA
2010 SAP AG
Page 32
SAP UA
2010 SAP AG
Page 33
11
SAP UA
A dimension is a group of characteristics which belong to the same business object (semantically). Each characteristic may contain additional attributes which are relevant for data analysis or not!!!
Navigational attributes are InfoObjects which are used to perform data analysis. Display attributes are InfoObjects for which data analysis does not make sense (e.g. a house number or a family name) This has an impact to cube design!
Note: In data warehouse community, the term Dimension is used for what SAP calls Characteristic .
2010 SAP AG
Page 34
SAP UA
Dimension
NAV
NAV NAV
2010 SAP AG
SAP UA
2010 SAP AG
Page 36
12
SAP UA
1. 1 Dimension
2. Characteristic
2010 SAP AG Page 37
SAP UA
Define which Characteristics may be chosen to create a semantic cluster for semantic dimensions.
Examples are: Sales, Production, Material Management, Finance, etc.
2010 SAP AG
Page 38
SAP UA
Summary
Key Figures and Characteristics are defined as InfoObjects. InfoObjects are the smallest bricks to define InfoProviders within SAP BW. InfoProviders are used to store data within SAP BW or allow SAP BW to access data stored somewhere else. The most important InfoProviders are InfoCubes and DataStore Objects. The definition of an SAP BW InfoCube is no Witchery!
2010 SAP AG
Page 39
13