An InfoCube contains integrated data from multiple sources and is optimized for analysis. It contains dimensions such as material, time, and sales organization, and key figures like sales quantity, revenue, and discount. An InfoCube allows users to analyze relationships between different data points for better business decisions.

1. Data Warehouse :
A place where you integrate subject-oriented, integrated, non-volatile, time variant
collection of data which helps to take decisions in Organization is called Data Warehouse
(DWH). E.g. SAP BW
Subject-Oriented – Customer, Sales, Deliveries etc. are Subjects of SD Application.
Data Warehouse Basics

2. Data Warehouse Environment Architecture
Contains Integrated Data From Multiple Legacy Applications

3. Function of Data warehouse
1) Modeling
2) Extraction (ETL – Extraction, Transformation, Loading)
3) Reporting

4. You need to integrate many different sources of data in near real-time. This will allow for
better business decisions because users will have access to more data.
You have tons of historical data that you need to gather in one easily accessible place in
which it will have common formats, common keys, common data model, and common
access methods
You need to use master data management to consolidate many tables, such as customers,
into one table
Data warehouse is optimized for the read access, resulting in faster report generation.
A data warehouse is a convenient place to create and store metadata
Having one version of the truth, so each department will produce results that are in line
with all the other departments, providing consistency
Companies that have implemented data warehouses and complementary BI systems
have generated more revenue and saved more money than companies that haven’t invested
in BI systems and data warehouses
Reason to use data warehouse instead of direct access

5. OLTP system vs. OLAP system

6. SAP BI (Business Intelligence)
Definition:
BI is a concept that is usually implemented by tools that can help the users analyse
the data that is stored in data warehouses (like SAP BW and others).
Data warehouses and BI tools are different concepts that are usually used together
to provide a business solution.
During all business activities, companies create data. In all departments of the
company, employees at all levels use this data as a basis for making decisions.
Business Intelligence (BI) collates and prepares the large set of enterprise data. By
analysing the data using BI tools, you can gain insights that support the decision
making process within your company.
BI makes it possible to quickly create reports about business processes and their
results and to analyse and interpret data about customers, suppliers, and internal
activities.

7. SAP BW Basic Architecture

8. SAP BW Basic Architecture

9. The Administrator Workbench (AWB) is the tool for data warehouse management in SAP BW
(Business Information Warehouse).
Using AWB we can manage, control and monitor all relevant objects and processes in SAP
BW including scheduling, data load monitoring and metadata maintenance.
Following are the functions that we can perform using AWB:
 Modeling
 Monitoring
 Transport connection
 Documents
 Business content
 Translation
 Metadata repository
Data Warehouse Workbench

10. Data Warehouse Workbench
Modeling:
Here we can create and maintain objects relevant to the data staging process in SAP BW. For
example, create InfoProvider, InfoObject, InfoSource, maintenance and define source system
and PSA.
Transaction code (T-Code): RSA1

11. Data Warehouse Workbench
Monitoring:
In monitoring Function area, we can monitor and control data loading process and other data
process in SAP BW.
Transaction code (T-Code): RSMON

12. Data Warehouse Workbench
Transport Connection:
This function is used to maintenance and move object between SAP systems: development to
quality assurance (QA/Test) and QA to production.

13. Data Warehouse Workbench
Document:
The document function area, we can maintain links for one or more documents in various
formats, versions and languages for SAP BW Objects.

14. Data Warehouse Workbench
Business Content:
Pre-configured information models based on metadata is maintenance in this area. Business
Content Function are provides us a selection of information that we can use to fulfil our tasks.
Transaction code (T-Code): RSORBCT.

15. Data Warehouse Workbench
Translation:
The use of translation function area is to translate short and long texts belonging to SAP BW-
objects.

16. Data Warehouse Workbench
Metadata Repository:
In the HTML-based SAP BW- Metadata Repository, all SAP BW meta objects and the
corresponding links to each other are managed centrally. Together with an integrated
Metadata Repository browser, a search function is available enabling a quick access to the
meta objects. In addition, metadata can also be exchanged between different systems, HTML
pages can be exported, and graphics for the objects can be displayed.
Transaction code: RSOR.

17. Source Systems in SAP BW
All systems that provide BI with data are described as source systems.
Source systems are the systems in which the original data is created. Data is uploaded from
the source system into SAP BW.
The connections to these systems have to be created in SAP BW.

18. Types of Data
Master data :
Masterdata is the core data that is used as a base for any transactions.
Masterdata created centrally and is valid for entire application.
The data which is not going to change frequently and maintain uniqueness(no duplicate).
It Represents all real life entities.
E.g. Material master data
Customer master data
Vendor master data
Pricing/conditions master data

19. Types of Data
Transaction data :
Data that is associated with processing of business transaction.
The data which is going to change very frequently and allows duplication.
E.g. Sales data
Bank Transaction data
ATM Transaction data

20. InfoProviders in SAP-BW
An ‘InfoProvider’ is an object for which Queries can be created.
InfoProvider is physical objects or sometimes logical ‘Views’.
Available InfoProviders in BW:
1) Characteristics Info Object
2) DSO (DataStore Object) Physically contains data
3) InfoCube
4) MultiProvider
5) InfoSet Doesn’t physically contain data
6) Virtual Providers

21. InfoObject
InfoObject is the smallest available information modules or fields in BI. They can be uniquely
identified by their technical name.
Business evaluation objects are known in BI as InfoObjects.
They are divided into :
Characteristics (for example, customers)
Key figures (for example, revenue)
Units (for example, currency or amount unit)
Time characteristics (for example, fiscal year)
Technical characteristics (for example, request number)
InfoObjects are grouped in InfoObjects Catalogs under InfoArea.

22. InfoObject
Importance of InfoObject :
InfoObjects are used throughout the system to create structures and tables where data is
stored.
They enable information to be modeled in a structured form.
They are also used to define reports and to evaluate master and transaction data

23. InfoObject
Classification of InfoObject:
InfoObjects are primarily divided into the major types Keyfigures or Characteristics.
The characteristics type is further divided into time characteristics, technical characteristics,
and units.
Key figures - Quantity (0QUANTITY), Amount (0AMOUNT), etc.
Characteristics - Cost center (0COSTCENTER), Material (0MATERIAL), etc.
Time characteristics - Calendar day (0CALDAY), Calendar year (0CALYEAR).
Technical characteristics - Request ID (0REQUID), Change ID (0CHNGID), etc.
Units - Currency unit (0CURRENCY), Value unit (0UNIT), etc.

24. InfoObject
Characteristics InfoObject:
Characteristics InfoObjects are used to analyze key figures, for example, Customer
(characteristic) Sales (key figure)
E.g. Material Number
Customer Number
Vendor Number
Material Type
Employee department
Store
Country
Region

25. InfoObject
KeyFigure InfoObject:
Key Figures are operational attributes, which indicates numerical measures such as amount
related, Weight related, quantity related, etc. These represent how much and how many
scenario.
E.g. Sales quantity
Sales value
Employee salary
Material unit price

26. InfoObject
Masterdata infoobject:
Characteristic infoobject could be a masterdata object OR
It could be a normal characteristic infoobject.
We can define masterdata object in following three ways,
Masterdata attribute
Masterdata text
Masterdata hierarchy

27. InfoObject
Masterdata infoobject:

28. InfoObject
Masterdata infoobject:
Attribute:
Attributes are used to describe a other Characteristics in greater detail.
An Attribute is an infoonject or masterdata infoobject.
Display Attribute:
When an attribute is defined as a Display attribute they can only be used in reports in
conjunction with their linked characteristic.
Navigational Attribute:
When an attribute is defined as Navigational the attribute can be used in queries to filter data

29. InfoObject
Masterdata infoobject:
Text:
It maintains and stores large text descriptors. It may contain the following information,
Short text (20 characters)
Medium Text (40 Characters)
Long Text (60 characters)
Text as Language Dependent
Text as Time Dependent
When text as Language Dependent is selected an extra language field is appended to the
primary key of the text table
When Text as Time Dependent is selected two extra fields are appended to the primary key of
the text table Dateto and Datefrom

30. InfoObject
Masterdata infoobject:
Hierarchy:
A hierarchy table is used to store the hierarchical relationships between Characteristics

32. Characteristic list for example

33. Keyfigure list for example

34. Keyfigure list for example
Keyfigure Name Technical Name Description Data Type Fixed Currency
Cost of good sold <root>CGnnn <root> nnn Cost of goods (Bike company) Amount USD
Discount <root>DSnnn <root> nnn Discount (Bike company) Amount 0Currency
Discount % <root>DPnnn <root> nnn Discount % (Bike company) Number Dec
Net Sales <root>NSnnn <root> nnn Net Sales (Bike company) Amount 0Currency
Product Price <root>PRnnn <root> nnn Product Price(Bike company) Amount 0Currency
Transfer Price <root>TPnnn <root> nnn Transfer price(Bike company) Amount USD
Revenue <root>RVnnn <root> nnn Revenue(Bike company) Amount 0currency
Sales Quantity <root>QTnnn <root> nnn Sales Quantity(Bike company) Quantity 0Buase_UOM

35. Characteristic list for example
Characteristic
Name
Technical
Name Description
Data
Type Length Masterdata Attribute D/N
Material Group <root>MGnnn <root> Material Group (Bike Company) CHAR 9 Attribute & Text 0PROD_CATEG Display
Material <root>Mnnn <root> Material (Bike Company) CHAR 18 Attribute & Text 0BASE_UOM Display
0DIVISION Nav
ZVUIMG299 Nav
ZVUITP299 Display

36. InfoProviders in SAP-BW
An ‘InfoProvider’ is an object which provide an information for reporting.
InfoProvider is physical objects or sometimes logical ‘Views’.
Available InfoProviders in BW:
1) Characteristics Info Object
2) DSO (DataStore Object) Physically contains data
3) InfoCube
4) MultiProvider
5) InfoSet Doesn’t physically contain data
6) Virtual Providers

37. InfoProviders in SAP-BW
Data Store Object (DSO):
A DataStore object serves as a storage location for consolidated and cleansed transaction data
or master data on a document (atomic) level. This data can be evaluated using a BEx query.
A DataStore object contains key fields (for example, document number/item) and data fields
that can also contain character fields (for example, order status, customer) as key figures.
The data in DataStore objects is stored in transparent, flat database tables.
Major difference between InfoCube and DSO is that DSO have the Option of ADD/Overwrite
records where Infocube supports only Addition.
DSO Types :
- Standard DSO
- Write-Optimized DSO
- Direct Update DSO

38. InfoProviders in SAP-BW
Data Store Object (DSO): Integration in dataflow

39. InfoProviders in SAP-BW
Data Store Object (DSO): Settings
Type Structure Data
Supply
Delta capability SID Generation
Standard Active queue,
Table of active
data and Change
log
DTP Delta
determination
from after images
on record level
YES
For Direct
update
Table of active
data only
APIs No delta
capability
NO
Write-
Optimized
Table of active
data only
DTP On request level NO

40. InfoProviders in SAP-BW
Data Store Object (DSO): Settings
• SIDs Generation upon Activation:
Improves Query performance
Queries are also possible even if SID
values are not generated.
• Unique Data Records:
Available only if ‘SIDs Generation upon
Activation’ is set.
Activation Process is optimized.

41. InfoProviders in SAP-BW
Data Store Object (DSO): Standard DSO
Contains Three Tables :
1. Activation Queue
2. Active Data
3. Change Log

42. InfoProviders in SAP-BW
Data Store Object (DSO): Standard DSO
• Activation Queue:
Used to store the data to be updated in the Data Store Object which has not been
activated.
After activation data is deleted from this table.
• Active Data Table:
Structure same as the Data Store Object definition. Also called as ‘A-Table’.
Technical Key – Key fields defined in the DSO.
When the request is activated data moves from Activation Queue to this table
• Change Log:
Change history for delta mechanism from the Data Store Object into other info provider.

43. InfoProviders in SAP-BW
Data Store Object (DSO): Standard DSO

44. InfoProviders in SAP-BW
Data Store Object (DSO):
Key Fields
Sales Organisation (Bike Company) MU0SALORG
<root>nnn Material (Bike Company) <root>Mnnn
Distribution Channel 0DISTR_CHAN
Calendar Day 0CALDAY
Data Fields
<root>nnn Sales Quantity (Bike Company) <root>QTnnn
Base Unit of Measure 0BASE_UOM
<root>nnn Revenue (Bike Company) <root>RVnnn
Currency Key 0CURRENCY
Discount (Bike Company) <root>DSnnn
Navigational
Attributes Division
Material Group
Company Code
Country Key

45. InfoProviders in SAP-BW
Data Store Object (DSO):

46. InfoProviders in SAP-BW
Infocube : <root>R1nnn (<root> nnn Bike company reporting)
Dimensions Dimension Name Characteristics
Material <root>nnn Material (Bike Company) - <root>Mnnn
Sales Distribution Channel - DISTR_CHAN
Sales Organisation (Bike Company) - MU0SALORG
Time Calendar Year/Month - 0CALMONTH
Calendar month - 0CALMONTH2
Calendar Year - 0CALYEAR
Key Figures <root>nnn Sales Quantity (Bike Company) - <root>QTYnnn
<root>nnn Revenue (Bike Company) - <root>REVnnn
<root>nnn Discount (Bike Company) - <root>DSCnnn
<root>nnn Net Sales (Bike Company) - <root>NSAnnn
<root>nnn Cost of Goods Sold (Bike Company) - <root>COGnnn