Major Difference between SAP BI 7
Data Warehousing
Data Warehouse (DW) is a concept where in data is stored in
database in summarised format and based on reporting requirements
of business. The data can then be analysed using data mining
techniques to gain advantages over business rivals.
DW provides a set of functionalities. DW can extract data from
various data sources (e.g. flat file, tables, etc.) and stored data
in its own databases. DW also provides functionalities for query
and analysis.
Business Warehousing is one of the concept which is used to
setup a data warehouse. DW is designed considering reporting and
analytical requirements of business. SAP BW provides solution
related to business warehousing where in data can be transformed,
cleansed, loaded, scheduled, monitor and reported based on business
reporting requirements
In Online Transaction Processing (OLTP, e.g. SAP R/3, ECC),
normalization is used as database design technique where in same
information is available only at one place. Objective of
normalization is to avoid data redundancy and data integrity
issues. Hence if an information is updated at one place, there is
no need to update it at another place and updated information is
available where ever it is retrieved.
Star Schema
To facilitate data retrieval from data warehouse, a special
database design technique is used which is called 'Star
Schema'.
Star Schema uses a Fact table and several Dimensional tables.
Fact table is a central table which is surrounded by many
dimensional tables. Hence the name Star Schema.
Following is an example of Star Schema:
Fact Table: At the centreDimensional Table: Surrounding
(Customer, Product and Location)
A star schema consists of many dimensions, hence term
Multidimensional Analysis is also used. One dimension can have many
attributes. These attributes allows to drill up and down to
analysis data.
In the example, dimension 'Location' has one of the attribute as
'Region'. Hence, reporting can be done at region level as well.
Customize SAP R/3 for SAP BW
SAP R/3 (OLTP) system needs to be customized so that data can be
extracted in SAP BW. To extract data, one needs to activate the
standard business content. For each application (e.g. SD, MM,
etc.), there are data sources for extracting Master and
Transactional data.
1) Log on to SAP R/3 system 2) Execute transaction SBIW3) Go to
'Business Content DataSources' 4) Click 'Transfer Application
Component Hierarchy'
5) In the confirm prompt: 'Do you want content application
Transfer Component Hierarchy', press 'Yes'6) Confirmation message
will appear realted to transfer component hierarchy7) Repeat step 2
& 3, click 'Business Content DataSources'
Data Sources are extraction structure. They have list of fields.
They are classified as Master Data Sources and Transactional Data
Sources. Master data sources are divided in Attributes, Texts and
Hierarchies.8) Select the SAP Application Component, mark the data
source and select Activate Data Source
Customize SAP BW for SAP R/3
SAP BW system needs to be customized for SAP R/3 so that data
can be smoothly extracted in SAP BW. Transfer of global setting,
exchange rates, replication of data sources are common setting need
to be done while setting up SAP BW system.
1) Create User ID for Source System Communication a) Execute
transaction SU01b) Create user ID RFCUSER, type SYSTEM with profile
S_BI-WHM_RFC and S_BI-WX_RFC
2) Set User ID for Source System Communication a) Transaction
RSCUSTAb) Set BW User ALE as RFCUSER
3) R/3 Source System a) Transaction RSA1b) Go to Source Systems
and Create source system for R/3 and Replicate DataSources
4) Copying Global Settings from R/3 a) Right-click R/3 Source
System and choose Transfer Global settings
5) Copying Exchange Rates from R/3 a) Right-click R/3 Source
System and choose Transfer Exchange rates
6) Flat file Source System a) Transaction RSA1b) Go to Source
Systems and Create source system for Flat file
7) BW Source System a) Transaction RSA1b) Go to Source Systems
and Create source system for BW and Replicate DataSources
8) Maintain Source System ID a) Transaction RSA1b) Menu Tools
-> Asgnmt of Srce Syst to Srce Syst IDXBPCLNT100 ->
BPXEPCLNT100 -> EPPCFLATFILE -> FT
9) Define source system mappings a) Transaction RSA1b) Menu
Tools -> Mapping of the Source System NamesXEDCLNT100 ->
XEPCLNT100XBDCLNT100 -> XBPCLNT100
10) Permitted Characters a) Transaction RSKC b) Maintain
permitted characters
11) Activate BEx History a) Transaction SPROb) Go to SAP
NetWeaver -> SAP Business Information Warehouse ->
Reporting-relevant Settings -> General Reporting Settings in
Business Explorer -> Activate Personalization in BEx) c) Choose
option Activate BEx History and Execute
12) Number ranges for Transfer Structure a) Transaction SNUM b)
Enter object name BI_TS and Click on Number Rangesc) Choose Change
Intervalsd) Add new interval 01 (Not 1), from number 0000000001 to
number 9999999999 Save and exit
13) Object Changeability Transaction RSA1a) Go to Transport
Connection) Click on button Object Changeabilityb) Set the
following objects as Changeable Original ISIP InfoPackage RSPC
Process Chain RSPT Process Chain Starter RSPV Process Variants
Define Source System
Source System is the system from where data is extracted and
stored in data warehouse.
Following are the steps to Define a Source System in SAP BW
1) Execute transaction RSA12) Select Source System as shown
below and right click to create
3) Select Source System Type as shown below. In this example, we
are creating a source system for a flat file. Using this, we can
load a .csv file to an infocube
Similarly, a SAP R/3 or SAP BW system can be defined as source
system. Server id, system id, background user, clients are some of
the information required to define SAP source system.
4) Enter a name and description for source system
5) Source system is created as shown
Create Data Source in SAP
Data Sources are extraction structure. Data Sources are used to
extract data from various source system.
In the below steps, we will see how to create a data source
using a SAP table VBAK.1) Execute transaction RSO2
2) Enter data source name to be created
3) Press Create
4) Enter description of the data source
5) Enter the name of table or view on which data source has to
be created. Data Source can also be created using a View, Info set
or a Function Module.
6) Save the data source7) Execute RSO2 again and click Change8)
Select VBELN field as selection
9) Save the Data Source
11) To check whether data is getting extracted, execute
transaction RSA3
12) Enter the name of data source as shown below and press
'Extraction'
13) An information message will appear stating no. of records
fetched
14) Additional button 'Display list' will appear, press
button
15) Select one of the data packet and double click to get
records fetched
16) Data Source is ready to be used!
Replicate Data Sources
Once the data source is created in source system, this has to be
replicated into data warehouse. This way data source will be
available for BW to extract data.
1) Execute transaction RSA12) Select Source System3) Right click
the source system where data source was created earlier
4) Select Replicate Data Sources
5) Status will appear at bottom-left with replication status as
shown
6) Once replication is done, a status message will appear
Naming Convention in SAP BW
SAP BW has a naming convention related to its objects.
SAP BW prefixes /BIO/ to the names of Business Content database
objects. It prefixes /BIC/ to the database objects created by
users.
If a user creates characteristics type info object ZPRODUCT and
activates it, information will be stored in following:
Data element: /BIC/IOZPRODUCTSID table: /BIC/SZPRODUCTMaster
data table: /BIC/PZPRODUCT Text table: /BIC/TZPRODUCTView:
/BIC/MZPRODUCT
When an info cube ZSALES is created and activated, information
will be stored in following:
View Fact table: /BIC/VZSALESFTransparent Fact table:
/BIC/FZSALESDimension tables: /BIC/DZSALES1 to /BIC/DZSALESN where
N being no. of dimensions/BIC/DZSALESP, /BIC/DZSALEST, /BICDZALESU
for Data Packet, Unit & Time (maximum 16 dimensions possible, 3
reserved for P, T & U)
If a hierarchy is used in an info object ZDATE, following tables
will be created:
Hierarchy table: /BI0/HZDATEHierarchy SID table: /BI0/KZDATESID
hierarchy structure: /BI0/IZDATEHierInterval table: /BI0/JZDATE
Common SAP BW Transactions
Following are most commonly used SAP BW Transactions
1) SBIW: Data Transfer to SAP BW2) RSA1: Admin Workbench
Modelling3) RSZV: Maintain Variable for BEx Analyser4) RSSM: BW
Authorization5) RSO2: Maintain Generic Data Sources6) RSA7: BW
Delta Queue Maintenance7) RSA3: Data Extractor Check8) RSA5:
Installation of Data Sources from Business Content9) LISTCUBE: To
display content of Info Providers10) RSCUSTA: Set User ID for
Source System Communication11) RSKC: Permitted Characters12) SNUM:
Number ranges for Transfer Structure13) SM62: Define Event 14)
RSMO: Evaluation of Requests
General SAP Transactions:
1) SE11: ABAP Dictionary (Create, Change, Display Table, View,
Data Elements, etc.)2) SE16: Data Browser for Table and View3)
SU01: User Maintenance4) PFCG: Role Maintenance5) SPRO:
Customizing6) SE80: Object Navigator7) SE93: To check transaction
codes available8) STMS: Transport Management9) SE09: Transport
Organiser
Major Difference between SAP BI 7.0 and SAP BW 3.5
1) Administrator Workbench is renamed as Data Warehousing
Workbench.
2) There are additional modeling options available at left hand
side panel in transaction RSA1 as shown below. The additions are
'DataSources' and 'Open Hub Destination'.
3) The functions of the InfoPackage tree are fully covered by
process chains.
4) Process Chains are used instead of Event Collector.
5) The 'Remodelling' transaction help you add Key Figures and
Characteristics in a Infocube while handling historical data
effectively.
6) Infocubes can be included in Infosets.
7) Transformation is used instead of update and transfer
rules.
8) ODS objects have been renamed as DataStore Objects.
9) You can access objects till InfoPackage directly from
InfoCube as shown below.
Infocube Creation using SAP BW 3.5 & BI 7.0
Infocube objects are widely used in any SAP Business Warehousing
implementation. Data is stored in Infocube from one or many
InfoSources. BEx Queries are used to analysis data available in
Infocube.
Standard Infocubes are optimised for there read-access
performance.
Infocube uses concept of star schema. Infocube is created using
Characteristics and Key Figures.
Characteristics are levels on which reporting has to be
performed. For example, Product, Customer and Location.
Key Figures are measures used for characteristics. For example,
sales quantity for a product, customer and location
combination.
As there is a significance difference between SAP BW 3.5 and SAP
BI 7.0, we are providing here steps of Infocube creation process
for both the versions.
Infocube Creation using SAP BW 3.5
1) Infocube Creation Step 1 using SAP BW 3.52) Infocube Creation
Step 2 using SAP BW 3.53) Infocube Creation Step 3 using SAP BW
3.5
Infocube Creation using SAP BI 7.0
1) Infocube Creation Step 1 using SAP BI 7.02) Infocube Creation
Step 2 using SAP BI 7.03) Infocube Creation Step 3 using SAP BI
7.04) Infocube Creation Step 4 using SAP BI 7.0Open Hub Service
using SAP BW 3.5 & BI 7.0
Open Hub Service functionality in SAP BW 3.5 is mainly used with
InfoSpoke. InfoSpoke is an object for exporting data. InfoSpoke is
defined using a data source (from which data is extracted),
extraction mode and destination (where data will be stored).
Open Hub Service functionality is used to distribute data from
SAP BI to other non-SAP data systems. In earlier version, it was
part of InfoSpoke but in SAP BI 7.0 this can be used
independently.
As there is a significance difference between SAP BW 3.5 and SAP
BI 7.0, we are providing here steps of Open Hub Service creation
process for both the versions.
Open Hub Service using SAP BW 3.5
Open Hub Service functionality in SAP BW is mainly used with
InfoSpoke. InfoSpoke is an object for exporting data. InfoSpoke is
defined using a data source (from which data is extracted),
extraction mode and destination (where data will be stored).
In this section, we will see, how data is extracted from SAP BW
InfoCube to a .csv file on a desktop.
1) Execute transaction RSA1, 'Tools' -> Open Hub Service
-> Edit InfoSpoke
2) Enter name of InfoSpoke and press 'Create'
3) Enter short description and select the Data Source as
'InfoCube'
4) Select Extraction Mode as 'Full'
5) Go to 'Destination' tab, enter short description. In this
example, we will be exporting data in a .csv file, select the
'File' and chose 'Directory'
6) Go to 'InfoObjects' tab, select the InfoObjects you would
like to have in your exported file
7) Go to 'Selection' tab, enter if you want a particular
selection criteria, in this example there is no selection used.
8) Activate the InfoSpoke by pressing 'Activate' button
9) After activation, source structure will appear as follows
10) Go back and display the InfoSpoke, press 'Dialog' button
11) Data will be exported to .csv file which will be stored at
desktop
12) Go to InfoSpoke Monitor to check status of export
13) Data is exported as the monitor status is green
14) Check the exported file at desktop
Open Hub Service using SAP BI 7.0
Open Hub Destination functionality is used to distribute data
from SAP BI to other non-SAP data systems. In earlier version, it
was part of InfoSpoke but in SAP BI 7.0 this can be used
independently.
In this section, we will see, how data is extracted from SAP BI
InfoCube to a .csv file on a desktop.
1) Execute transaction RSA1, Press 'Open Hub Destination'
2) Select InfoArea and right click to 'Create Open Hub
Destination
3) Enter Name and Description
4) Go to 'Destination' tab, enter Destination Type as 'File
type'. In this example, we will be exporting data in a .csv file,
select Directory to 'Desktop'
5) Go to 'Fields Def.' tab, select the InfoObjects you would
like to have in your exported file
6) Activate the Open Hub Destination by pressing 'Activate'
button
7) Select the Open Hub Destination and right click to 'Create
Transformation'
8) Enter source of transformation as InfoCube
9) Accept the proposed mapping and activate
10) Create Data Transfer Process for transfering data from
InfoCube to Desktop as .csv file
11) Enter source of DTP as InfoCube
12) Activate DTP and Execute, Data will be exported to .csv file
which will be stored at desktop
13) Press 'Yes' to check the status of request monitor
14) Data is exported as the monitor status is green
15) Check the exported file at desktop
Operational Data Store (ODS) using SAP BW 3.5
ODS consists of 'Key fields' and 'Data fields'. Data fields can
also contain characteristics e.g. customer, product etc..
ODS is not used for multi-dimensional analysis like Infocube.
The data from ODS can be updated with delta update into a Infocube.
The data in ODS is stored in a transparent table. There is no fact
or dimensional table created for ODS.
Following are the steps to create an ODS:
1) Execute transaction RSA1, select the InfoArea under which you
would like to create ODS. Right click the InfoArea, select 'Create
ODS Object'
2) Enter ODS Object 'Name' and 'Description', press 'Create'
3) Check the box against 'BEx Reporting' to enable ODS for BEx
reporting, press 'InfoObject Catalog' button to get the InfoObjects
which you would like to add to ODS
4) Select the characteristics (InfoObjects) which you would like
to add as 'Key fields' or 'Data fields', drag and drop the
InfoObjects in respective folders as shown below.
5) You can also insert an InfoObject into to fields folders by
right clicking the folder
6) Add '0CALMONTH' as 'Key field'
7) Add Key Figures as 'Data fields' as shown below, check and
activate the ODS, system will display message related to ODS
activation
8) Press 'Back', you can see ODS as shown
Now define InfoSources, Transfer Rules, Update Rules, Info
Package as discussed in Infocube Creation Steps.
9) Below is the Extraction Structure created based on ODS
We will see more details about ODS in coming sections... thanks
for your patience!
Process Chain Creation using SAP BW 3.5
Process chains are used extensively in SAP Business Warehousing
for executing loads, running reports etc. sequentially or
parallel.
There can be number of steps with in a process chain. You can
also decide what has to be done incase a particular step fails. In
case of failure you can decide to sent notification email to
concern person who can correct the issue.
In this section we will see how to create a process chain using
SAP BW 3.5. Using this process chain we will load data in
Infocube.
1) Execute transaction RSPC
2) Press 'Create', enter 'Name' and 'Description' of the process
chain, press 'Continue'
3) First step in the process chain will be a 'Start' step, press
'Create' to create a process variants
4) Enter 'Name' and 'Description' of the process variant
5) 'Save' process variant and go back, 'Change selections' is
used to schedule the process chain, we will revisit this again
later
6) Press 'Continue'
7) Select the InfoPackage which is used to load data in
Infocube, drag InfoPackage to right panel
8) Select the process variants as InfoPackage using fucntion key
F4
9) Select the InfoPackage ZAAA and press 'Continue'
10) Following steps will be added in the process chain
11) Join 'Start' step with step 'Indexes' by selecting 'Start'
step and dragging the line to 'Indexes'
12) Go back to 'Start' step and right click to 'Maintain
Variant'
13) Select 'Immediate' to schedule the process chain
immediately
14) 'Check' the process chain and 'Activate' the process
chain
15) Execute the process chain, enter the server name in the
following screen
16) Process chain will start executing, to check the status,
Press
17) Select 'Yesterday and Today' to check the status of the
process chain
18) Following screen shows that load is still not completed
19) Once completed, the status will appear as follows, incase
there is any failure, the status will appear as cancelled