SAP Business Intelligence

Business Blueprint
Submitted to

For

By

August, 2010
Version 1.0

SAP BI Business Blue Print

__________________

___________________

Mr. Saravana Kumar

Mr. Raghu Kumar

Team Lead PP
Lanco Industries Limited

Team Lead - MM
Lanco Industries Limited

__________________

__________________

Mr. Shanmuga Rajan

Mr. R S N Datta

Team Lead - MM
Lanco Industries Limited

Team Lead - SD
Lanco Industries Limited

___________ ______

__________________

Mr. Kodandapani

Mr. Kamal Kanodia

Team Lead - FI
Lanco Industries Limited

Team Lead FI/SD

Lanco Industries Limited

___________________

___________________

Mr. CA. Niranjan .M.N

Mr. Ramesh Babu .M

Coordinator - BI
Lanco Industries Limited

Project Manager
Lanco Industries Limited

___________________
Mr. A R Surana
GM Finance & IT
Lanco Industries Limited

__________________

__________________

Mr. Shashidhar Kothapally

Mr. Uthant Yaram

Project Manager
vCentric Technologies Pvt Ltd

BI Team Lead
vCentric Technologies Pvt Ltd

vCentric & Lanco Industries Confedential

Page 2 of 24

SAP BI Business Blue Print

Document Information
Project Name
Aarohan

Document Name
SAP BI Business Blueprint

Document History
Version
1.0

Document Name Date

SAPBI_BBP_V1.0 3rd Sep 2010

vCentric & Lanco Industries Confedential

Author
Mr. Shashidar K
Mr. Uthant Y

Reviewed by

Page 3 of 24

SAP BI Business Blue Print

Table of Contents
1.
1.2.
1.3.

2.
2.1.
2.2.

3.
3.1.
3.2.

Executive Summary.........................................................................................................7
Objective........................................................................................................................................7
Benefits..........................................................................................................................................7

Project Scope...................................................................................................................7
Deliverables Considered In Scope..............................................................................................7
Deliverables Considered Out of Scope.......................................................................................8

Introduction and Project Goals......................................................................................8

Introduction....................................................................................................................................8
Goals..............................................................................................................................................8

4.

Approach...........................................................................................................................9

5.

KPI Dimension Matrix...................................................................................................9

5.1.
5.2.
5.3.
5.4.
5.5.

6.
6.1.
6.2.
6.2.1.
6.2.2.
6.2.3.
6.3.
6.3.1.
6.3.2.
6.3.3.
6.3.3.1.
6.3.3.2.

7.
7.1.

8.
8.1.

9.
9.1.

Key Performance Indicator (KPI):..................................................................................................9

Dimension:.....................................................................................................................................9
KPI Dimension Matrix:................................................................................................................9
KPI Dimension Matrix (Layout):..................................................................................................9
Constraints & Considerations:.....................................................................................................10

System Landscape Strateg...........................................................................................10

System Names.............................................................................................................................10
The BI Environment:....................................................................................................................11
Development (BID).......................................................................................................................11
Quality Assurance (BIQ), i.e. Testing...........................................................................................11
Production (BIP)...........................................................................................................................11
Source Systems for BI:................................................................................................................11
ECC 6.0:.......................................................................................................................................11
SAP BI (My Self Data Mart).........................................................................................................11
File Interface:...............................................................................................................................11
Supported File Formats:..........................................................................................................12
Source Locations:...................................................................................................................12

SAP BI Transport Management System......................................................................12

Overview......................................................................................................................................12

ETL / Scheduling Strategy.............................................................................................13

Process Chain:.............................................................................................................................13

Appendix A KPI Dimension Matrices........................................................................14

Finance........................................................................................................................................14

vCentric & Lanco Industries Confedential

Page 4 of 24

SAP BI Business Blue Print

9.2.
9.3.
9.4.

10.
10.1.
10.1.1.
10.2.
10.3.
10.3.1.
10.3.2.
10.4.
10.4.1.
10.4.2.
10.5.
10.5.1.
10.5.1.
10.6.
10.6.1.
10.6.2.

11.
11.1.
11.2.
11.3.
11.4.

12.
12.1.
12.2.
12.3.
12.4.
12.5.
12.6.
12.7.
12.8.
12.9.
12.10.
12.11.
12.12.

Material Management..................................................................................................................14
Sales & Distribution......................................................................................................................14
Production Planning.....................................................................................................................14

Appendix B - SAP BI Objects........................................................................................14

Master Data.................................................................................................................................14
Master Data Objects....................................................................................................................14
Tansaction Data...........................................................................................................................15
Finance (FI):.................................................................................................................................15
FI InfoProviders............................................................................................................................15
FI DataSources............................................................................................................................15
Sales & Distribution (SD).............................................................................................................16
SD InfoProvidors..........................................................................................................................16
SD DataSources..........................................................................................................................16
Material Management (MM).........................................................................................................16
MM InfoProviders.........................................................................................................................16
MM Data Sources........................................................................................................................16
Production Planning (PP).............................................................................................................16
PP Infoproviders..........................................................................................................................16
PP Data Source...........................................................................................................................17

Appendix C SAP BI Data Flow...................................................................................17

Finance........................................................................................................................................17
Material Management..................................................................................................................18
Sales & Distribution......................................................................................................................19
Production Planning.....................................................................................................................19

Appendix D - SAP BI Glossary.....................................................................................20

Administrator Workbench.............................................................................................................20
Business Explorer........................................................................................................................20
Characteristic...............................................................................................................................20
Data Extraction............................................................................................................................20
Data Mapping...............................................................................................................................20
Data Transformation....................................................................................................................20
Data Warehouse..........................................................................................................................20
Dimension Table..........................................................................................................................21
Fact Table....................................................................................................................................21
Favorites......................................................................................................................................21
InfoCatalog...................................................................................................................................21
InfoCube......................................................................................................................................21

vCentric & Lanco Industries Confedential

Page 5 of 24

SAP BI Business Blue Print

12.13.
12.14.
12.15.
12.16.
12.17.
12.18.
12.19.
12.20.
12.21.
12.22.
12.23.
12.24.
12.25.
12.26.
12.27.
12.28.

InfoObject.....................................................................................................................................21
InfoPackage.................................................................................................................................22
InfoSource....................................................................................................................................22
Key Figure....................................................................................................................................22
Master Data.................................................................................................................................22
Meta Data....................................................................................................................................22
Monitor.........................................................................................................................................22
OLAP...........................................................................................................................................23
OLTP............................................................................................................................................23
Operational Data Store................................................................................................................23
Primary Key.................................................................................................................................23
Query...........................................................................................................................................23
Relational Integrity.......................................................................................................................23
Scheduler.....................................................................................................................................23
Source System.............................................................................................................................23
Star Schema................................................................................................................................24

Table of Pictures
Picture 1: Layout of KPI Dimension Matrix................................................................................10
Picture 2: SAP BI ECC System Landscape Strategy................................................................12
Picture 3: Sample Process Flow....................................................................................................13
Picture 4: Finance Data Flow in BI.................................................................................................17
Picture 5: Material Management Data Flow in BI..........................................................................18
Picture 6: Sales & Distribution Data Flow in BI............................................................................19
Picture 7: Productin Planning Data Flow in BI.............................................................................19

vCentric & Lanco Industries Confedential

Page 6 of 24

SAP BI Business Blue Print

1. Executive Summary
1.1. Overview
Lanco Industries has started the Business Intelligence Proof of Concept (BI POC)
Implementation with vCentric Technologies to evaluate the Business Analysis, Reports, KPIs
and performance management of ECC by using the Business Intelligence. So by using the BI
the entire organisation will get End to End Solution
1.2. Objective
Objective of this SAP BI POC Implementation is to introduce the best practices of SAP BI to
the management team of Lanco.
1.3. Benefits
The value of SAP Business Intelligence is best demonstrated by applying it to real
business problems. The SAP BI POC jumpstarts your evaluation, while at the same time
giving you a better understanding of your performance management needs.
Our goal with the BI POC is to provide you with measurable and rapid results for a defined
investment, both in terms of time and money. At the end of approximately 12 elapsed
weeks (consisting of an estimated Four week of preparation time and Eight week of
implementation), we will have:
A realistic understanding of how Business Intelligence can represent our KPIs , Business
Analysis, Complex Reports and overall performance management requirements
A review of your POC with our experienced consultant will give your organization a better
understanding of the monitoring and analytics components of Performance Point Services.
The opportunity to see the analytical view of SAP ECC data
o With the BI POC you can also evaluate the SAP ECC Functional problems and
you can also increase the ECC system performance by using the BI Reports.
A complete BI Proof of Concept
o At the completion of this effort, you will have a POC that demonstrates how a BI
solution can provide value to your organization and customers. The POC can also
be used as the starting point for further design.

2. Project Scope
2.1. Deliverables Considered In Scope
The following actions and deliverables are considered within the scope of the BI-POC project:
1.
Functional Areas Involved:
a. Material Management
b. Production Planning
c. Finance

vCentric & Lanco Industries Confedential

Page 7 of 24

SAP BI Business Blue Print

d. Sales & Distribution
2.
3.
4.
5.
6.
7.

Identifying the Key Performance Indicator (KPI) metrics and the dimensions with
the functional areas involved.
The extraction and one time load from Lancos ECC systems of all relevant detail
and master data from the different data sources, to a historical depth subject to
data availability or other project team defined constraints.
The design and development of BI-POC InfoCubes that will provide efficient and
effective end users access to the identified KPIs in each functional area.
Define ETL Strategy for the SAP BI Info Providers and the respective Master / Text
Data.
Performance Tuning of the SAP BI the defined data model and the ETL flow.
The establishment of a technical environment supporting Business Intelligence
processing, including the client landscape, transport management processes,
desktop client management, naming conventions, distributed printing, security
administration and end user and technical standards and procedures.

2.2. Deliverables Considered Out of Scope

The follow actions and deliverables are considered to be out of the scope of the BI-POC
project, but may be considered for inclusion in a subsequent phase or project:
1.
2.
3.

Development in the functional areas other than MM, PP, FI and SD.
Devolopment of BEx reports on top of the InfoProviders that are built.
Training on SAP BI Developments.

3. Introduction and Project Goals

3.1. Introduction
It is critical to understand that the BI-POC projects success is dependent not only on the
delivered effort of the BI Project Team (both functional and technical) but also on support and
delivered effort from the ABAP Team, the Basis Team and the Security Team
3.2. Goals
The Business Intelligence POC Implementation project has two major goals designed to
support and compliment the decision making of the top management of Lanco Industries
Limited.
These are:
1.
To identify the KPIs in four functional areas i.e. SD, MM, FI and PP. For the
identified KPIs, identifying the metrics that are measured against various
dimensions within or cross functional area.

vCentric & Lanco Industries Confidential

Page 8 of 24

SAP BI Business Blue Print

2.

Building the InfoCubes in SAP BI according to the KPI-Dimension Matrix that is

identified and finalized by Functional Team.

4. Approach

SAP BI team will conduct workshop to Lanco Industries senior management introducing
the advantages and the best practices.
Meeting the heads of each department along with their Module Leads building the
understanding on SAP BI and its features.
Understanding the requirement of HODs with the help of respective Module Leads.
Identifying the KPIs and the Dimensions in each functional area with the help of the
requirements given by Module Leads
On receiving the initial requirement from the departments, prepare the KPI-Dimension
Matrix for each department.
Review of KPI-Dimension Matrix along with respective Module Leads and finalize.
Review of KPI-Dimension Matrix with the Process Owner of Lanco Industries
For the identified KPI-Dimension Matrix, collect the source field information and the
formulae to build the data model in SAP BI.
Bridge the gaps and freeze the requirements with the help of Module Leads.
Develop the InfoCubes in SAP BI according to the finalized requirements.

5. KPI Dimension Matrix

5.1. Key Performance Indicator (KPI):
KPI is the term used for a Key Perfomance Indicator i.e. is to measure the performance of an
organization with some measures defined within a KPI. These KPI Metrics are measured
against the meaningful dimensions pertaining to a particular functional area.
5.2. Dimension:
Dimension is a point of view to measure the organizational performance with the help of KPI
Metrics in various areas of an organization.
5.3. KPI Dimension Matrix:
KPI Dimension Matrix is the consolidation and mapping of the entire KPI Metrics applicable
to their respective dimensions. This document covers the entire KPI Metrics so that it can be
the unique reference for building SAP BI Data Model for a particular functional area. This also
helps us to identify the metrics that are measured across the other functional areas.

vCentric & Lanco Industries Confidential

Page 9 of 24

SAP BI Business Blue Print

5.4. KPI Dimension Matrix (Layout):
This document divided into Rows and Columns. Each row represents a KPI Metric within a
particular subject area (Module/Sub Module). Each KPI Metric can be either directly available
in SAP ECC or it may be retrived through a defined formulae.

Picture 1: Layout of KPI Dimension Matrix

5.5. Constraints & Considerations:
Identify the KPI Metrics which are the key for top managements decision making
Eliminate the transactional level elements (both KPI Metrics & Dimensions) so that we
can avoid duplication of detailed data in SAP BI.
Ensure that we are going to maintain the aggregated level information rather than the
detailed level data in BI.
Business justification is mandatory for all KPI Metrics & Dimensions given in the
document.
Define the Sources / Business Logic for the identified KPI Metrics and Dimensions so
that the same can be incorporated into SAP BI. Otherwise it is not possible to
accommodate it in SAP BI. (Ex: Source Fields in SAP, Formulae, etc..)

6. System Landscape Strateg

6.1. System Names
The following system names may be found in other SAP documentation. This section provides
a cross-reference of the standard R/3 terminology and the System names used throughout this
document.
System
Name

Purpose

Logical System
Name

Source System

BID

Development (DEV)

BIDCLNT444

ECC DEV (CLNT 430)

BIQ

Quality Assurance (QAS)

BIQCLNT555

ECC QAS (CLNT 500)

BIP

Production (PRD)

BIPCLNT666

ECC PRD (CLNT 600)

vCentric & Lanco Industries Confidential

Page 10 of 24

SAP BI Business Blue Print

6.2. The BI Environment:
6.2.1.Development (BID)
All customizing and development work is performed in this system, (see above). Once all
the changes have been unit tested, these changes can be transferred to the QAS system
for further system testing. The customizing and development changes are transported
using transport requests.
6.2.2.Quality Assurance (BIQ), i.e. Testing
After unit testing the customizing and development changes in the DEV system, the
changes are transported to the QAS system. Here, the configuration is further tested and
checked to ensure that it does not adversely affect other modules. When the configuration
has been thoroughly tested in this system, and signed off by the Quality Assurance team,
it can be copied to other system clients and to the PRD system.
6.2.3.Production (BIP)
The PRD is the system that a company uses for its production work. This system contains
the company's live data and where the real business processes are performed. The other
systems in the landscape must guarantee that defective programs or incorrect customizing
configurations do not affect the production work.
6.3. Source Systems for BI:
SAP BI extracts the data from any of its source systems. Once the data arrives into SAP BI
system, it will be stored in PSA (Persistant Staging Area). Data will be loaded from PSA to the
data targets through required transformation mechanism. Current SAP BI system has the
following three types of sources systems.
6.3.1.ECC 6.0:
As SAP ECC 6.0 is playing vital role in transactional data processing for Lanco Industries,
this will act as a primary source of data. Data Extractors (Data Sources) will be built in
ECC 6.0 to extract the data from the source tables in ECC system. These data sources will
be replicated into SAP BI system for further mapping and transformations in BI system.
6.3.2.SAP BI (My Self Data Mart)
SAP BI acts like a source system for it self for internal data transfers. Ex: Data Loads from
DSO to InfoCube, InfoCube to InfoCube, etc.
In this scenario, SAP BI source system is also called as SAP BIs My Self Data Mart.
6.3.3.File Interface:
Data can be uploaded into SAP BI in form of Flat Files. There is no physical existence
maintained out of SAP BI. Rather, the File Interface Source System can be logically
maintained in SAP BI.

vCentric & Lanco Industries Confidential

Page 11 of 24

SAP BI Business Blue Print

6.3.3.1.
Supported File Formats:
Any structured file format which is in CSV or Text File Format.
6.3.3.2.

Source Locations:

Applicaton Server: There is a provision given in SAP BI to maintain the Flat Files.

Respective file path should be identified while loading a particular file into the data
targets. Files located in the application server can also be loaded in background.
Also the files can be globally accessible from any client work station.
Client Work Station: Other than the application server, we can also maintain them in the
clients work station. But the background scheduling is not possible in this scenario.

Moreover, files located in the client work station are not globally accessible.

Picture 2: SAP BI ECC System Landscape Strategy

7. SAP BI Transport Management System

7.1. Overview
The SAP BI Transport Management system (formerly the Correction and Transport System)
provides options for data transfer between and within R/3 Systems. The tool can be used, for
example, to transport tuned and tested customizing settings between systems and clients.

vCentric & Lanco Industries Confidential

Page 12 of 24

SAP BI Business Blue Print

The integration of the Transport Management System with customizing ensures that only
individual table entries are transported, so that no unintentional transfer of test data will occur.
Using transport requests and customizing settings, development work developed in a separate
DEV system can be automatically recorded in change requests and then transported into a
quality assurance client and then into a production client. Once the change request has been
released from the source system, it becomes a transport request.
If you do not want to record every change in a system (e.g. in a test client), the recording of
customizing settings can be activated or deactivated for each client.

8. ETL / Scheduling Strategy

Regular data feeds to SAP BI system will be taken care by process chains that are developed by
SAP BI team and scheduled with regular intervals as required.
8.1. Process Chain:
Process Chain is a sequence of the data oploads and subsequent proceses that can be
scheduled in background in SAP BI system. Process Chain takes care of the end to end data
upload process until the information is ready for reporting.

Picture 3: Sample Process Flow

vCentric & Lanco Industries Confidential

Page 13 of 24

SAP BI Business Blue Print

9. Appendix A KPI Dimension Matrices
9.1. Finance
LIL_SAPBI_KPI_FI.xl
s

9.2. Material Management

LIL_SAPBI_KPI_MM.
xls

9.3. Sales & Distribution

LIL_SAPBI_KPI_SD.xl
s

9.4. Production Planning

LIL_SAPBI_KPI_PP.xl
s

10. Appendix B - SAP BI Objects

Data in SAP BI is divided majorly into two parts.
10.1.Master Data
Master data is globally unique which serves the entire reporting needs throughout the system.
Following are the Important Master Data objects that are maintained in Current SAP BI system.
10.1.1. Master Data Objects
Sl No
1
2
3
4
5
6
7
8
9
10

Object Name
0CUSTOMER
0MATERIAL
0VENDOR
0PLANT
0SALESORG
0SOLD_TO
0CUST_GROUP
0STOR_LOC
0COMP_CODE
0MATL_GROUP

vCentric & Lanco Industries Confidential

Description
Customer
Material
Vendor
Plant
Sales Organization
Sold to Party
Customer group
Storage Location
Company Code
Material group

Page 14 of 24

SAP BI Business Blue Print

Sl No
11
12
13
14
15
16
17
18
19
20

Object Name

Description

0GL_ACCOUNT
0CHRT_ACCTS
0PRODORDER
0S_OPERAT
0WORKCENTER
0WAGEGR
0PERSON
0DT_ELEMENT
0PRODORDER
0DOC_NUMBER

G/L Account
Chart of accounts
Manufacturing Order
Suboperation
Work Center/Resource
Wage Group
Person
Downtime Element
Manufacturing Order
Sales document

10.2.Tansaction Data
Transaction data is also called as historical data about the facts with respect to a functional area.
Ex: Sales Orders, Material Movements, Payments, Rceipts etc..
Transaction data is maintained in various InfoProviders in SAP BI. Data to loaded to these
InfoProviders from the DataSources that exist in the Source System.
10.3.Finance (FI):
10.3.1. FI InfoProviders
Sl No
1
2
3
4
5
6
7
8

Object Type

Object Name

InfoCube
InfoCube
InfoCube
DSO
InfoCube
InfoCube
InfoCube
InfoCube

0FIGL_C10
0FIGL_V10
0FIAP_C03
0FIAP_O03
0FIAR_C03
0FIAR_C05
0FIAR_C02
0FIAA_C03

Description
General Ledger (New): Transaction Figures
G/L (New): Balance Sheet and Profit and Loss
FIAP: Line Item
FIAP: Line item
FIAR: Line Item
FIAR: Payment History
FIAR: Transaction Data
FIAA: Transactions

10.3.2. FI DataSources
Sl No
1
2
3
4
5
6
7
8

Object Name
0FI_AR_3
0FI_AR_4
0FI_AR_5
0FI_AR_6
0FI_AR_1
0FI_GL_10
0FI_AP_3
0FI_AP_4

vCentric & Lanco Industries Confidential

Description
Customers: Line Items
Customers: Line Items with Delta Extraction
Customers: Payment History
Customer Sales Figures via Delta Extraction
Customers: Transaction figures
General Ledger: Leading Ledger Balances
Vendors: Line Items
Vendors: Line Items with Delta Extrcation

Page 15 of 24

SAP BI Business Blue Print

10.4.Sales & Distribution (SD)
10.4.1. SD InfoProvidors
Sl No
1
2
3
4
5

Object Type

Object Name

InfoCube
InfoCube
InfoCube
DSO
DSO

0SD_C01
0SD_C02
0SD_C03
0SD_O01
0SD_O06

Description
Customer
Deliveries
Sales: Overview
Order Items
Billing: Condition Data

10.4.2. SD DataSources
Sl No
1
2
3
4
5
6
7
8

Object Name

Description

2LIS_11_VAHDR
2LIS_11_VAITM
2LIS_12_VCHDR
2LIS_12_VCITM
2LIS_13_VDHDR
2LIS_13_VDITM
2LIS_11_VAKON
2LIS_13_VDKON

Sales Document Header Data

Sales Document Item Data
Delivery Header Data
Delivery Item Data
Billing Doc. Header Data
Billing Document Item Data
Sales Document Condition
Billing Document Condition

10.5.Material Management (MM)

10.5.1. MM InfoProviders
Sl No
1
2
3

Object Type

Object Name

InfoCube
MultiProvider
InfoCube

0IC_C03
0IC_MP04
0PUR_C01

Description
Material Stocks/Movements (as of 3.0B)
Material Stocks/Movements
Purchasing Data

10.5.1. MM Data Sources

Sl No
1
2
3
4
5

Object Name

Description

2LIS_03_BF
2LIS_03_BX
2LIS_03_UM
2LIS_02_SCL
2LIS_02_HDR

Goods Movements From Inventory Management

Stock Initialization for Inventory Management
Revaluations
Purchasing Data (Schedule Line Level)
Purchasing Data (Document Header Level) as of 2.0B

10.6.Production Planning (PP)

10.6.1. PP Infoproviders
Sl No
1
2

Object Type

Object Name

InfoCube
InfoCube

L1CBPP001
0PP_C05

vCentric & Lanco Industries Confidential

Description
Production Analysis
Plan/Actual Comparison Material Consumption

Page 16 of 24

SAP BI Business Blue Print

10.6.2. PP Data Source
Sl No
1
2

Object Name
2LIS_04_P_MATNR
2LIS_04_P_ARBPL

Description
Material View from PP/PP-PI
Work Center View from PP/PP-PI

Note: Objects in the above mentioned list are subject to customization or change during
realization.

11. Appendix C SAP BI Data Flow

11.1.Finance

Picture 4: Finance Data Flow in BI

vCentric & Lanco Industries Confidential

Page 17 of 24

SAP BI Business Blue Print

11.2.Material Management

Picture 5: Material Management Data Flow in BI

vCentric & Lanco Industries Confidential

Page 18 of 24

SAP BI Business Blue Print

11.3.Sales & Distribution

Picture 6: Sales & Distribution Data Flow in BI

11.4.Production Planning

Picture 7: Productin Planning Data Flow in BI

vCentric & Lanco Industries Confidential

Page 19 of 24

SAP BI Business Blue Print

12. Appendix D - SAP BI Glossary
12.1.Administrator Workbench
The Administrator Workbench is the tool that you use to control how the data gets from the
source systems into the InfoCubes of the Business Information Warehouse. The parts of the
Administrator Workbench that you will need for the requesting and managing of the data
include: Source system, InfoSource, InfoCube, InfoObject, Scheduler, and Monitor.
12.2.Business Explorer
The Business Explorer (BEx) is SAP Business Information Warehouse reporting tool.
In the Business Explorer Analyzer (BEx Analyzer) you define queries that are based on a
selection of characteristics and key figures (InfoObjects) or of predefined query templates of an
InfoCube. You analyze the selected InfoCube data by navigating in the query, where you
generate different views of the data. You save the queries in workbooks and can assign these
to one or more channels.
Using the Business Explorer Browser (BEx Browser) you access workbooks, that are assigned
to you in channels. You select the workbooks with which you wish to work. You manage those
workbooks with which you work frequently in your favorites.
12.3.Characteristic
A criterion to which data can be selected such as company code, product, material, customer
group, fiscal year, period or region.
Characteristics provide classification possiBIlities for the dataset. The master data
encompasses the permitted values of a characteristic, the so-called characteristic values.
Characteristic values are discrete names. The characteristic region could, for example, have
the values "North", "Central" and "South".
12.4.Data Extraction
Data Extraction is the process of loading data from source systems into the BI for reporting.
12.5.Data Mapping
This is the process of assigning source system data elements to target data elements in the
Data Warehouse.
12.6.Data Transformation
Transformation is the process of modifying data for accuracy and completeness in BI.
Transformations that are derived from business rules can be applied to elementary data in BI
to prepare it for end-user reporting.
12.7.Data Warehouse
A database that contains summarized data from transactional data found in the OLTP
system(s), ECC system(s) or other sources. The data store in the BI is designed for the
efficient retrieval of data and for decision support reporting. The data are organized by subject

vCentric & Lanco Industries Confidential

Page 20 of 24

SAP BI Business Blue Print

area, and the data are time dependent. The data store contains figured quantities and
dimensional data.
12.8.Dimension Table
A table in a star schema with a single part primary key is called Dimension Table
(e.g., customer key, product key, time key).
12.9.Fact Table
The fact table is at the center of the star schema of an InfoCube. The data part contains all key
figures (also called "Facts") of the InfoCube and the key is formed by links to the entries of the
dimensions of the InfoCube.
12.10. Favorites
Channel for workbooks with which a user works frequently. Users can copy workbooks with
which they frequently work from the channels into their favorites. Users manage their favorites
themselves and can individually name or group their content. Users can save modified or new
workbooks in their favorites.
12.11.InfoCatalog
This is a tree-like structure in the Administrator Workbench that displays Business Information
Warehouse workbooks and queries. The various InfoCatalog trees contain workbooks that SAP
delivers, workbooks that can be used in an enterprise, workbooks that are used by certain user
groups, workbooks that an individual user is allowed to use, and Favorite workbooks (user
favorites), that a user has put together. The structure of the sub-trees can be freely defined by
the administrator. A user accesses his or her queries of the InfoCatalog using the Business
Explorer Browser.
12.12. InfoCube
This is the central data container for queries and evaluations. InfoCubes contain two types of
data, namely key figures and characteristics.
An InfoCube is a number of relational tables, which are put together according to the star
schema: a large fact table in the center, surrounded by several dimension tables. The fact table
is set up in order to save all key figures on the lowest level of detail while the dimension tables
are used to save the characteristics that are required both in reporting and in the evaluations of
these key figures. Dimension tables are seen as being independent of one another. Only the
fact table connects the dimensions with the key figures. Therefore all of the data is stored
multi-dimensionally in the InfoCubes.
12.13. InfoObject
Generic term in the Business Information Warehouse for characteristics and key figures.
InfoObjects are used in InfoCubes and the three structures relevant for the data request
(extract structure, transfer structure and communication structure).
Names for InfoObjects can only be given once.

vCentric & Lanco Industries Confidential

Page 21 of 24

SAP BI Business Blue Print

Within the characteristic a distinction is made between time and unit characteristics. Examples
for characteristics would be evaluation groups such as cost center or product group.
Key figures are currency, quantity or number fields such as sales revenue, revenue or number
of employees. Key figures usually refer to unit InfoObjects.
12.14. InfoPackage
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, only
controlling area 001 in period 10.1997).
An InfoPackage can request transaction data or attributes or hierarchies for master data.
12.15. InfoSource
An InfoSource is a quantity of information for a unit. This information has been grouped
together 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, and
hierarchies). An InfoSource is always a quantity of InfoObjects.
12.16. Key Figure
Values or quantities such as sales revenue, fixed costs, sales quantity or number of
employees.
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 are
calculated using a formula from the key figures of the InfoCube. Examples of derived key
figures are sales revenue per employee (sales revenue divided by number of employees), or
variance as a percentage or the contribution margin.
12.17. Master Data
This is data that remains unchanged over a long period of time. Master data contains
information that is needed again and again in the same way.
12.18. Meta Data
Meta data is data about data. This means that meta data describes the origin, history and
further aspects of the data. The information that is stored in the SAP Business Information
Warehouse can be effectively used for reporting and analysis via the meta data.
There are different classes of meta data: technical or business-oriented.
12.19. Monitor
Monitoring tool of the Administrator Workbench. Using the Monitor you can oversee the data
request and processing in the Administrator Workbench. You will be shown the status of the
IDoc processing in the various levels of the detail display. A distinction is made between two
types of IDoc: Data IDoc and Info IDoc.

vCentric & Lanco Industries Confidential

Page 22 of 24

SAP BI Business Blue Print

12.20. 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 analysis of that
data for decision support processes.
12.21. OLTP
On-Line Transaction Processing (OLTP) is used for operational data e.g. data in the R/3
software.
12.22. Operational Data Store
The Operational Data Store (ODS) is an integrated database that contains a copy of extracted
data from source systems.
12.23. Primary Key
Key field or group of fields which form the unique identification of a record (a line) in a table.
12.24. Query
Collection of a selection of characteristics and key figures (InfoObjects) for the analysis of the
data of an InfoCube. A query always refers to exactly one InfoCube, whereas you can define as
many queries as you like per InfoCube.
You define a query by selecting InfoObjects or predefined query templates of an InfoCube and
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 then create further views
of the InfoCube data via navigation. You can save data for the current navigational state of the
query in the workbook.
12.25. Relational Integrity
The observation of integrity rules governing the relational data model. These include primary
key integrity, value range integrity, and foreign key integrity (referential integrity).
12.26. Scheduler
The Scheduler is the nexus between the source systems and the InfoCubes. With the
Scheduler you determine which data is to be requested from the source system and at which
point in time. The principle of the Scheduler relies on the functionality of the R/3 background
job. The data request can either be started at once or with a background job and automatically
at a later date.
12.27. Source System
All systems that 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 (for
example, so-called third party tools or files).

vCentric & Lanco Industries Confidential

Page 23 of 24

SAP BI Business Blue Print

12.28. Star Schema
A data structure that combines fact tables and dimension tables in a way that provides easy
and efficient access to the data.

vCentric & Lanco Industries Confidential

Page 24 of 24