SAP BW 7.3 & BI 7.0: Over View of

KESHAV BW 7.
3 / BI 9642123434 1
SAP BW 7.3 & BI 7.0
OVER VIEW OF
MODELLING, EXTRACTION, REPORTING
(BW 7.3 / BI VOLUME 4)
SRI SAI TECHNOLOGIES

33,GAYATRI NAGAR, SAP LANE, BEHIND MYTRI RESTURANT/ MYTRIVANAM
VOLUME 1 (MODELLING)
VOLUME 2 (EXTRACTION)
VOLUME 3 (REPORTING, P CHAIN, P TUNING)
VOLUME 4 (OVERVIEW OF MODELLING, EXTRACTION, REPORTING)
________________________________________________________________________
WE PROVIDE ONLINE & OFFLINE (CLASSROOM) TRAING FOR SAP
MODULES (BW 7.3, BO, BODS, HANA, EHS, ABAP, CRM(TECH & FUN), HR-ABAP, FICO,,WORK FLOW, BI-
ABAP, BASIS, SECURITY, SD, HR, MM, WM, PP, PM,PS,PI, BPC)ORACLE( FI &TECH)
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 2
INDEX
TOPIC PNO
Importance of BW 3
Types of sap systems 5
Oltp vs olap 5
IMPORTANCE OF BW / BI FOR AN ENTERPRIZE / ORGANIZATION
An Enterprise can be seen in this way.
BUSINESS TRIANGLE
Strategic layer  CEO, MD, CIO

Managerial layer  MANAGERS, TEAM LEADS
Transaction layer  USERS
Main challenge of any business is decision making.

TO DO ( or) NOT TO DO,WHEN TO DO, HOW TO DO and WHY TO DO
The people belonging to Strategic layer are the decision makers.

How do they make decision?
They depend on historical data to make decisions.
They will compare the historical reports with current reports.
We will be having millions of rows and thousands of columns in database tables.
So it is not practical to directly look into the database tables to get our required data
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 3
So it is better data to represented in the form of graphs, charts… etc.
BI means Business Intelligence. In other words we can define as "Graphical representation

of historical data".
The role of a BI Consultant is to Extract data from the transaction system, load it into BI
system, and prepare the reports.
We can call it as ETL ( Extraction, Transformation and Loading) & OLAP(Online Analytical
& Processing ).
some reports:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 4
Source file means data at transaction system. It can be a flat file, SAP ECC, or any other
database.
DataSource is a set of logically-related fields that are provided to transfer data into BI in a
flat structure (the extraction structure), or in multiple flat structures (for hierarchies).
Infopackage is used to pull data from source system to datasource.
Target is also known as Infoproviders. There are different types of info providers depending
upon the type of data. InfoObject, DSO, Infocube
The transformation process allows us to consolidate, cleanse, and integrate data. We can
semantically synchronize data from heterogeneous sources.
When we load data from one BI object into a further BI object, the data is passed through a
transformation. A transformation converts the fields of the source into the format of the
target.
DTP is used to pull data from DataSource to Target (InfoProviders).
BI means graphical representation of DATA.

We have two types of data.
1. Transaction Data
2. Master Data
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 5
AC Kes hav
TABLES RELATIONSHIP
Cus tome r Id Cus tome r Cus tome r Cus tome r
(PK) Na me Age Addre ss
C1000 Mr. Pa ul 30 CA Ma ste r da ta

Ta ble
PK: Prima ry Ke y
Cus tome r Id
Qty Price (USD) Re ve nue
(FK)
C1000 1000 100 100000 Tra nsa ction

da ta Ta ble
FK: Fore ign Ke y
Re la tionship: Associa tion be twe e n 2 or more ta ble s 28
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 6
MODELLING
BI - Business Intelligence (Reporting and Analysis)

o BI is a data warehousing tool
o ETL: Extraction > Transform > Load (Informatica)
o ETTL: Extraction > Transfer >Transform > Load (BI)
o BI is used by middle level and high level management
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 7
o OLAP: Online Analytical Process (SAP BI)

o OLTP: Online Transaction Process (SAP SD, MM, FICO, ABAP, HR)
DIFFERENCE BETWEEN OLTP & OLAP

OLTP
 Current data
 Changeability: Frequent data changes
 Priority: High availability, High data volume
 Database Operation: Online update/insert/delete and read
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 8
 Normalization is very high
 Data Structure: Relational (flat tables)
 Integration: Minimal
 Data Set: 6-18 months
OLAP

OLAP stands for On Line Analytical Processing used mainly for business reporting.
Using OLAP, businesses can analyze data in different ways, including budgeting, planning,
simulation, data warehouse reporting, and trend analysis
 Current and historical data
 Changeability: Data frozen
 Priority: Simple to use, flexible access to data
 Database Operation: Read
 Less Normalization due to data staging and less performance
 Data Structure: Multi Dimensional format
 Integration: Comprehensive
 Data Set: 2-7 years
OLAP and OLTP are two different system & used for different purposes and environments.
OLAP for analytical (compare) to OLTP for transactional.
Difference between OLAP and OLTP
Target
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 9
OLTP is used in operative environment to get efficiency through automation of business

processes. OLAP is used in informative environment, usually used by management to
support in decisions making.
Priorities
As transactional system, OLTP has high availability and higher data volume. OLAP as
analytical system is very simple data and has flexible data access.
Level of detail
OLTP stores data in a very high level of detail, whereas OLAP stores data in aggregation.
Age of data
OLTP data are current data. It means the data stored in OLTP with minimal history. OLAP
current & historical data.
Database operation
Frequent data changes are a feature of operative system. So, in OLTP system we can
read, add, change, delete or refresh data. In OLAP, we only can read the data.
Integration of data from various applications (system)
Since the OLTP system is for operation, it has minimal integration with other applications.
In contrast to the OLTP system, OLAP need high integration of information from many
application or system because it used for analysis.
Normalization in database
Due to reduction in data redundancy, normalization is very high requirement in OLTP. In

OLAP, typically de-normalized with fewer tables; use of extended star schema and lower
performance.
OLTP OLAP
Two dimensional Multi dimensional
Normalized De-normalized
Using for Transaction purpose Using for Analysis purpose
Based on ER data model Based on Schemas & Multi dimensional
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 10
Not allowed duplicates Allows duplicates

It contain current data It contains historical data
Ex:- ECC6 Ex:-BI/BW
ESS: An extended star schema is an enhancement of the star schema. In the extended
star schema, the InfoCube itself doesn’t hold any master data of the characteristics. The
master data information is stored in separate tables in the InfoObjects, called master data
tables. Thus, the master data tables “extend” the star schema—hence the name “extended
star schema.
Star Schema and Extended Star Schema Comparisons

In star schema, dimension and master data table are same. But in Extend star schema,
dimension and master data table are different. (Master data resides outside the Infocube
and dimension table, inside Infocube).
Instar schema we can analyze only 16 angles (perspectives) whereas in extended star
schema we can analyze in 16*248 angles. Plus the performance is faster to that extent.
Below are some of the basic differences between the two.
Star Schema Extended (BW) Star Schema
Cube InfoCube
Fact Table Key Figure or KPI
Dimension Attribute Characteristic, Attributes, Hierarchis
Dimension Table Dimension Table, Master Data Table, SID Table
Advantages of Classic Star Schema
Data access runs performantly due to the small number of joining operations.
There are only join operations between the fact tables and the involved dimension tables.
Disadvantages of Classic Star Schema
Redundant entries exist in the dimension tables
Advantages of the SAP BW Star Schema
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 11
Faster access to data than via long alpha-numeric keys. SAP BW use automatically
generated INT4 keys for SID and Dimension ID
Can model in easy way: Historizing, multi-lingual, and shared dimensions. It is happen
because of the excavation of master data from the dimension tables using the SID
technique.
The query performance is improved here as aggregated key figures can be stored in their
own fact tables.
For interview point of view we can explain as below:
STAR SCHEMA (SS) : Representation of a cube

CUBE contains fact table & dim tables (md tables).
Fact table contains key figures & dimid’s.
Star Schema is a data model in which Fact table surrounded by dimension tables.
Dimension tables master data tables are Same and Master data resides inside the fact
table & dimension tables also reside inside the cube, appears as a star like in diagram or
graphical representation.
We can analyze the data in 16 angles and has two common dimensions, Unit dimension &
time dimension, with two keys (primary key) PK for Fact table: and FK (foreign key) for
Dimension table. Actually the size of the Fact table is huge and the size of Dimension table
is small.
Data retrieval and performance is slow as degraded because of alphanumeric keys in the
fact table.
So the query performance also will be slow.
In SAP terminology, it is simply called CUBE.
Important point here to consider in star schema is data redundancy or data duplication
occurs, i.e. dimension tables are specific to a fact table, i.e. Dimensions are not shared
across other fact tables and Cubes.
When another fact table needs the same dimension data, another dim table that’s specific
to a new fact table is needed. So this situation leads to slower performance, because data
will be duplicated in several dim tables instead of sharing data from one single table.
The major drawbacks include, star schema doesn’t support aggregates, hierarchies,
multiple languages, slowly changing dimensions, and master data is not reusable and no
drill down capabilities supported.
Extended Star Schema (ESS): Representation of an InfoCube:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 12
Extended Star Schema is a model in which the fact table is surrounded by dimension
tables, dimension tables connected by SID tables, SID tables are connected to Master
data tables ( Data attributes, texts and hierarchies).
Dimension tables & master data tables are different, I.e. master data tables reside outside
the InfoCube and dimension tables resides inside the InfoCube., appears not as a star like,
rather it looks like scattered in diagram or graphical representation.
We can analyze the cube in 16 into 248 (SID tables) and has three common dimensions
like packaged dimension, time dimension & unit dimension, with PK (primary key), SID
tables which provide the links between the master data and the dimension table.
Actually the size of fact table is small and dimension table is big.
Here in the E S S apart from F, E, P, T, U, N tables, extra tables that are SID tables master
data tables that are P, Q, T, X, Y are formed.
Data retrieval and performance is fast as SIDs has numeric key in the fact table. So the
query performance will be faster.
In SAP terminology it is simply called InfoCube and the master data ESS is reusable. And
there will be no data redundancy because dimension tables are shared from one single
table.
Importance of ESS is that it supports aggregates as it has aggregates in its own table,
supports Hierarchies, supports Multiple language, supports slowly changing dimensions,
supports drill down capabilities & the master data is reusable.
DIFFERENCE BETWEEN STAR SCHEMA & EXTENDED STAR SCHEMA:
STAR SCHMA EXTENDED STAR SCHEMA

It is used to design the Cube It is used to design the Info cube
Master data cannot re-usable Master data is re-usable
Decreases the system Increases the system performance due to SID’s
performance due to Alpha-
Numeric in the infocube.
Less analysis because 1 dim More analysis due to 1 dm table = 248 m.data table
table = 1 md. Table (16 ways) (16*248 ways)
DEFINITION OF DWH:
 Mr. William Henry Inmon is father of DWH.
 He defined the DWH as “subject oriented, integrated, non-volatile and time
variant collection of data” in support of decision making.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 13
 Subject oriented: Data in DWH is organized around the major business areas
of application (SD, MM, PP, FI/CO).
 Integrated: Data from different subject areas are tightly integrated with each
other.
 Non-volatile: Data in DWH is not updatable i.e. once a record is properly
placed in DWH, it is not subject to change.
 Time variant: Data in DWH is specific to moment of time i.e. each record
maintains it’s own time.
TYPES OF DATA IN SAP:
 Data: All real raw facts and figures are called data.
 In a standard business process, there are 2 types of data.
 1. Master data: It represents all real type activities such as customers,
materials, vendors and plants.
 2. Transaction data: It represents all business events such as sales
transaction data or purchasing transaction data.
 With reference to time, data can be further classified into
1. Actual data, 2. Planned data and 3. Historical data.
FUNCTIONS OF DWH (BI):
1. Extraction: It is the process of pulling the data from source system by using
an interface.
2. Modelling: It is the place where we model/design the objects by using star
schema or extended SS.
3. Reporting: It is the place where we generate the reports from the
modelled/designed objects as per the customer requirement.
DB Design in OLTP: ER MODELLING (Entity Relationship Modelling).
 Entity: All real life objects are called entities.
Ex: Customers, vendors, materials and plants etc.
 Every entity maintains its own attributes.
Ex: Customer is an entity with certain attributes like name, address, age,
phone no, email, etc.
 These entities are mapped to DB table.
 A table is a structure consisting of set of rows and columns.
 The intersection of rows and columns are called cells.
 The attribute in the table cell is called field.
 The sequence of field is called header of the table.
TABLE STRUCTURE
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 14
AC Kes hav
TABLE STRUCTURE
Prima ry Ke y Columns
(PK)
He a de r Cus tome r Cus tome r Cus tome r Cus tome r

Cus tomer Id
Na me Age Addre ss Pho ne no
Rows
Body
He a de r
+ = Ta ble
Body
20
DB Design OLTP: ERM (Entity relationship modeling)

DB Design OLAP: MDM (Multi dimensional modeling)
In MDM: We have Star Schema & Extended (BW) Star schema
STAR SCHEMA:
 A fact table is at the centre & this fact table is surrounded by several
dimensional tables.
 The fact table is usually very large. Dimensional tables are small(only 1-5 % of
the fact table size).
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 15
AC Kes hav
PICTORIAL VIEW OF STAR SCHEMA
CUBE
Cus tome r ID (PK)

Cus tome r ID (FK)
Custome r Na me Sa le s Rep ID (FK)
Custome r Addre ss Sa le s Rep ID (PK)
Ma te rial Numbe r (FK)
Sa le s Pric e / unit Sa le s Re p Na me
Custome r Dime nsion
Unit of Me asure Sa le s Office
Qty Sold Sa le s Re gion
Sa le s Reve nue
Ma te rial Numbe r (PK) Sa le s Re p Dime nsion
Tra ns action Date
Ma te ria l Na me
Ma te ria l De scription Fa ct Ta ble
Ma te ria l Dime nsion
In sta r sche ma , fa ct ta ble a nd dime nsiona l ta ble s / m a re existing within cube 35
LIMITATIONS (DEMERITS) IN STAR SCHEMA:

1. MD is not reusable, because MD is in side cube.
2. We can analyze the datain 16 ways (angles)only.
3. Due to Aplha numeric values in FACT TABLE decreases the performance.
TO OVER COME THE ABOVE DEMERITS WE GO TO EXTENDED STAR SCHEMA
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 16
EXTENDED STAR SCHEMA (ESS)/(BW STAR SCHEMA):

ESS: STAR SCHEMA + SID TECHNOLOGY
SID: SURROGATE ID
Extended Star Schema

BW extended star schema differs from the star schema, in case of extended star schema,
we will have Fact table connected to the Dimension table and the Dimension table is
connected to the SID table and SID table is connected to the master data tables.
Fact Table and Dimension table will be inside the cube.
SID table and Master data tables are outside the cube.
One Fact table can get connected to 16 Dimension tables, one Dimension table can be
assigned with maximum of 248 SID tables (248 characteristics).
When we load Transaction data into InfoCube, System generates DIM ID based on the
SID’s and uses the Dim ID’s in the Fact Table.
Each Characteristic can have its own master data tables (ATTR, TEXT, HIER). Attribute
Table is used to store all the attribute data, Text table is used to store the description in
multiple languages, Hier table is used to store the Parent-Child data.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 17
Fact Table
Fact Table will have Dimension ID’s and Key figures.
Maximum DIM ID’s – 16
Maximum KeyFigure – 233
The Dimension ID’s in the Fact Table is connected to the Dimension Table.
Fact Table must have at least one Dimension ID.
Dimension Table
Dimension Table contains Dimension ID and SID columns.

One column is used for Dimension ID.
We have maximum of 248 SID Columns.
We can assign maximum of 248 characteristics to one dimension.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 18
AC Kes hav
PICTORIAL VIEW OF EXTENDED (BW) STAR SCHEMA

CI D CN a m e CAd d r
S MI D S MN a me S MAd d r
C1 0 0 John SJ Ma ste r Data Ta ble s
SM3 0 0 Peter SJ
C2 0 0 Paul CA
SM4 0 0 William CA
INFOCUBE
SID1 CI D
C1 0 0
2
c2 0 0
3 D K3 S ID3
D K1 S ID1 SID3 S MI D
21 2 41 4
4 SM3 0 0
MI D MN a m e MGrp DK 1
DK 2
M2 0 0 MS1 Steel DK 3
M3 0 0 MS2 Steel S a le s Price/ u nit
U n it of Mea s ure
Q t y S old
S a le s Revenue
Tr a n s action Date
D K2 S ID2
SID2 MI D Fa ct Ta ble
31 3
3 M2 0 0
Exte nde d Sta r Sche ma = Sta r Sche ma + SID (Surroga te ID) Te chnology 36
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 19
vvv imp
INFO OBJECTS:
InfoObject: Business evaluation objects are known in BI as InfoObjects. These play

important role in modeling. Everything is based on InfoObjects. Business evaluation objects
( ex: customers, and sales) are referred to as InfoObjects in BI. InfoObjects are the
smallest components in BI. Ex: Business Object like customer, product, etc....
USE: They are used to structure the information that is needed to create (build) larger BI
objects, such as InfoCubes or DSO Objects or InfoProviders.
Types Of InfoObjects: 5 TYPES

Characteristic InfoObjects
KeyFigure InfoObjects
SAP defined infoobjects
TimeCharacteristics
TechnicalCharacteristics
UnitCharacteristics
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 20
Characteristic InfoObjects: Objects that are used to calculate and analyze present Key
Figures.
Eg. Sales Office: 0 SALESOFFICE,
Customer: 0CUSTOMER,
Material: 0MATERIAL)
Key Figure InfoObjects: Data part of an InfoObject. They are quantifiable values.
(provides the values to be evaluated)
Eg. Quantity Sold: 0QUANTITY,
Revenue: 0REVENUE)
Time Characteristic InfoObjects : Characteristics that are assigned to the dimension of
time.
Time characteristics form the time reference frame for many data analyses and
evaluations. they are delivered with Business Content & its not possible to define
your own Time Characteristics.
Eg: calendarday: 0CALDAY: Time characteristics with largest granularity
calendaryear:0CALYEAR : Time characteristics with smallest
granularity
Fiscal Year: 0FISCYEAR : Time characteristics with smallest
granularity)
Unit InfoObjects: Units for the Key Figures. They enable keyFigure values to be partnered
with
the corresponding units in evaluations.
Eg: currency: 0CURRENCY
amount 0AMOUNT
unit: 0UNIT
Technical Characteristic InfoObjects: Only of structural use within BI. These have an
organizational function within SAP.
Eg. requestid: 0REQID
Changeid: 0CHNGID
(infoobject changeid delivers the numbers allocated during change runs)
(infoobject 0reqid delivers the numbers the system allocates when loading requests)
InfoArea is used to organize InfoCubes & InfoObjects.

Each InfoCube is assigned to an InfoArea.
Through IOC, each InfoObject is assigned to an InfoArea.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 21
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 22
TIME CHARACTERISTICS:
SNO TIME CHAR LONG DES I/P FORMAT O/P FORMAT
1. 0CALDAY CALLANDERDAY YYYYMMDD(8) DD.MM.YYYY

2. 0CALMONTH CALYEAR/MONTH MMYYYY(6) MM.YYYY
3. 0CALMONTH2 CALANDER MONTH MM MM
4. 0CALQUART1 QUARTER
5. 0CALQUARTER CALANDERYEAR/QUARTER
6. 0CALWEEK CALANDERYEAR/WEEK
7. 0CALYEAR CALANDER YEAR
8. 0FISCPER FISCALYEAR/PERIOD
9. 0FISCPER3 POSTING PERIOD
10. 0FISCVARIANT FIACAL YEAR VARIANT
11. 0HALFYEAR1 HALFYEAR
12. 0FISCYEAR FISCAL YEAR
13. 0WEEKDAY1 WEEKDAY
0FISCPER (FISCAL YEAR/PERIOD): YYYYMMM (7)/ MMM.YYYY (8).

An YEAR is divided into no of periods (MAX 16(12 + 4))
Regular posting s are 12 & SPL posting 4 (audit, bonus etc).
For Indian companies V3 (APRIAL - MARCH)& OTHERS K4 (JAN - DEC).
WE can define our own fiscal year variant.
0fiscper & fiscal year are compounding object.
fiscper will be followed by fiscal year variant.
NEED OF FISC PER : Every company has to submit their posting details () every
month according to companies law. For this purpose we need it. Companies will
declare their result according to fiscal year period.
IN ESS WE HAVE INTERMEADIATE TABLE CALLED SID TABLE BETWEEN MD & DIM
TABLE.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 23
TYPES OF DATA IN SAP BI: 2 TYPES

SAP BI has two types of data.
1. MASTER DATA(MD): The data that does not change frequently/over a period of
time.
2. TRANSACTION DATA(TD): The data that changes very frequently
MD:
Ex: customer master data(CMD), CMD is having complete information about customer
(custid,cname, caddr, creg ..etc)
VENDOR MD(VMD): VMD is having complete information about vendor (vendor
id,vname, vaddr, vpno ..etc)
PLANT MD(PMD): PMD is having complete information about plant ( plant id,pname,
paddr, ppno ..etc)
EMPLOYEE MD(EMD): EMD is having complete information about empoly ( employ
id,ename, eaddr, epno ..etc)
ROLE OF BI COSULTANT: As SAP BI consultant we will extract data (business
transactions)from SOURCE SYSTEM(ECC) every day after the business hours.
We will load MD once in a project. We will load TD daily .
AC Kes hav
TABLES RELATIONSHIP
Cus tome r Id Cus tome r Cus tome r Cus tome r
(PK) Na me Age Addre ss
C1000 Mr. Pa ul 30 CA Ma ste r da ta

Ta ble
PK: Prima ry Ke y
Cus tome r Id
Qty Price (USD) Re ve nue
(FK)
C1000 1000 100 100000 Tra nsa ction

da ta Ta ble
FK: Fore ign Ke y
Re la tionship: Associa tion be twe e n 2 or more ta ble s 28
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 24
 PSA (Persistent Storage Area): Used to correct errors.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 25
TRANSFORMATIONS:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 26
SAP BW has multiple transformation options for the consolidation of data acquired from a
wide variety of sources in different formats:
Direct Assignment: It is 1:1 transformations; this is used when source data is moved to
target without any changes.
Constant: This is used when source doesn't give a value for a specific field, and you want
to supply a constant value for that filed.
Formula: This is used when target value is derived using a formula. ex: value = price X
quantity.
Initial: This is used if you aren't interested in supplying values for a field . Numerical values
will be populated with zero, and character fields will be populated with a blank space.
Read Master Data: Consider a target with 2 fields... MATERIAL and COLOR OF
MATERIAL, assume that source data has a value for only MATERIAL field. But we have
data for COLOR OF MATERIAL in master data of that MATERIAL.. In this scenario, we can
use read master data type of transformation. and COLOR OF MATERIAL will read from
master data.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 27
Read from DSO: This is similar to Read Master Data, but data is read from the DSO.
Routine: This type of transformation is an ABAP code based transformation.
Transformation options for key figures:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 28
INFOCUBE:
It is a set of relational tables arranged according to the extended star schema. InfoCubes
are filled with data from one or more datasources or other InfoProviders., the Fact table is
the central table of the InfoCube and stores the combinations of dimension IDs and key
figures that make up the transactional data. It is a data target for the data which we are
extracting source system and info provider quires.
The structure of the InfoCube was set up specifically to be able to execute and run query
processes as quickly as possible.
InfoCubes can answer numerous questions such as
 How much product am I selling in a specific region during a specific period of time?
 What is the total P&L and balance sheet information for a company code during a
specific year?
 How much has a customer purchased of a group of materials and how does that
amount for the current period differ from the previous period?
To create an info cube we require minimum of 1 fact table surrounded by 4

dimensions. Out of which 3 are fixed dimensions
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 29
1. TIME
2. UNIT
3. DATA PACKAGE
A cube can have maximum of 1 fact table surrounded by 16 dimensions (13+3)
In this 3 are fixed dimensions
13 are custom defined dimensions
NOTE: In SAP a Table can have maximum of 16 primary keys
NOTE: In any Business scenario we request to maintain more than 16 dimensions in an

Info cube we can use Snowflake Schema

Facts: Measurement:- used to measure transactions & can be called as “facts”, these
facts in BW terminology ‘key figures’ [KEY FIGURES].
Fact Table: Will be used to maintain transaction data in an info cube, It consist of
dimension tables we called as DIM ID’s and key figures,Dim Id’s will be join fact table with
dimension table.
A fact table can have maximum of 16 dim id’s and 233 key figures.
Fact table: 255 columns =16 dim ids+ 233 key figures+ 6 (Reserved for SAP)
Dimension: Given description of business object, this description will be maintain using
proportions are attributes in BW terminology “Characteristics” [CHAR] mean properties.
In the context of Extended Star schema a dimension consist of dimension tables, SID
tables and master data tables.
Dimension Table: It is system generated table will get generated along with tact table
for every dimension defined in Info cube definition.
It consists of dimension table keys ( Dim ID’s) & Sid’s of characteristics organize in the
dimension. It will be used to join fact table with master data table using SID table it will get
populated automatically when every time we load transaction data into info cube.
SID TABLES: Will get generated automatically along with master data tables, when we
activate structure of characteristics, it structure consist of characteristics and SID of
characteristic. It will be used to join master data tables with fact table via dimension table.
NOTE:
In case of line item dimension type, dimensions SID table will be used to join
master data tables directly with fact table. Without using dimension table in Joins.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 30
SID table will get populated automatically whenever we load master data into characteristic
master data table.
A dimension can have maximum of 248 characteristics.

255 columns= 6 reserved+ 1 DIM ID + 248 characteristics.
TYPES OF INFOCUBES:

In BI 7.0 we are having 3 types Infocubes .

The Infocube which is used for STORING Summarized Transactional data. The Infocube
which is a Physical Storage Device which is used to store the data.

The Infocube is used for Transactional data only. The Infocubes are used to create
Summarized reports

The 3 types of Infocubes are:

1. Standard Infocube.
2. Virtual Infoproivder (or) Virtual Infocube.
3. Real-Time Infocube.

Standard Infocube:
Standard Infocube Stores The Physical Data, Data is Stored in the Standard Infocube. The
Structure of the Standard Infocube is One Fact Table surrounded by the Dimension
Tables.

Virtual Infoprovider

Virtual Infoprovider doesn't store any physical data at the time of the query execution it
receives data directly from the source system. These are mainly used for validating the
source system data with BI data (data reconciliation).

In you don't have the Sufficient Transaction codes (or) source system reports to perform
the data reconciliation during during integration testing we create virtual infoprovider.

Types of Virtual Infoproviders:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 31

The types of virtual infoproviders are defines based on the data loading mechanisms

1. Virtual Infoproviders with Direct Access DTP.
2. Virtual Infoproviders with Function Module.
3. Virtual Infoproviders with BAPI's(business app programing interface)
which is used for Non-SAP.

Real-Time Infocube
In real-time infocube, we can write the data into the cube, Real-time infocubes are used for
planning purposes.

For Standard cubes, we can load the data into the cube where as in real-time infocube we
can load the data into the cube and we can write the data into the cube, That means while
loading the data into the real-time infocube Planning is not possible. Similarly while writing
that data (Planning the data) into the real-time infocube loading is not possible.
Real-Time InfoCubes differ from Standard InfoCubes in their ability to support parallel write
accesses. Standard InfoCubes are technically optimized for read accesses to the detriment
of write accesses, whereas Real-Time InfoCubes are technically optimized for writing
access. The Real-Time InfoCubes are used in connection with the entry of planning data.
They are used in the BI-IP (Integrated Planning) and BW-BPS

How to make the real-time infocube as Load behavior?

Select InfoArea → Right Click → Create Infocube → Select Real-time

Select Infocube → Right Click → Change Real-time load runner
Infocubes are infoproviders but not necessarily data targets ( they are only data targets if
data is physically stored in them ).An infocube whether data target or infoprovider,
describes a self-contained data set. This could be used for reporting purpose .
Infocubes are supplied with data from one or more DSO’s or with data from different
systems.
TYPES OF INFOCUBES
Data targets are objects that store data physically. Some infocubes are data targets,
these are physical data stores. Other Infocubes are not data targets, because there is no
data physically stored in them. Infocubes that are not data targets are virtual providers.
Physical data stores:
· Basic infocubes stores data physically. There are two fact tables per infocube E and F.
data initially get loaded in to F table. During SAP compression this will be moved to the E
fact table.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 32
· Real time infocubes are both readable and writable, supporting parallel write access.
Real time info cubes are used for planning data .standard infocubes can be converted to
real-time infocubes if so required.
Real time infocubes store data physically in two ways: by the transaction used for entering
planning data and by BI staging.
VIRTUAL PROVIDERS
· Remote cube is an infocube whose transaction data is not managed in the business
warehouse, but rather externally. Only the structure of the remote cube is defined in BI .the
data is read using BAPI from another system.
· SAP Remote cube data is stored in another SAP system
· Virtual infocube with services is an infocube that does not have its own physical data
source. The properties of the data source can be defined more precisely using a number of
options.
DataStore Objects (DSO):
A DataStore object serves as a storage location for consolidated and cleansed transaction
data on a document (operational) data level, or it can be used for the storage of master
data for analysis. A DataStore object contains key fields (Ex document number/item) and
data fields that contain both character fields (Ex order status, customer) as well as key
figures. Another task that the DataStore object can be used for is the update of the current
data in another object. This uses the delta updating functionality and can update data into
an InfoCubes and/or other DataStore objects or master data tables (attributes or texts) in
the same system or across different systems. Unlike multidimensional data storage using
InfoCubes, the data in DataStore objects is stored in transparent, flat database tables.
The system does not create fact tables or dimension tables for the DataStore object. The
cumulative update of key figures is supported for DataStore objects, just as it is with
InfoCubes, but with DataStore objects it is also possible to overwrite data fields. This is
particularly important with document-related structures. If documents (for example, sales
orders transactions) are changed in the source system, these changes include both
numeric fields, such as the order quantity, and nonnumeric fields, such as the ship-to party,
status, and delivery date, can be updated into the DataStore object and the change
statuses can be tracked by the “change log” in the DataStore object. To reproduce these
changes in the DataStore objects in the BI system, we have to overwrite the relevant fields
in the DataStore objects and set them to the current value. Furthermore, you can use an
overwrite of the existing change log to render a source delta enabled. This means that the
delta that is further updated to the InfoCubes, for example, is calculated from a delta
process. This is a very basic outline of the back-end functionality of the DataStore object.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 33
when we load data to DSO.

the data will be available only in New data table (Activation Queue) and will not be
available for reporting or for any other needs..
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 34
After activation request the data is moved from new data table to active data table &
change log table by deleting the data in new data table.
If data is available in active data table and change log table

when we do query on DSO. data is actually taken from active table.
One of the main plus point of DSO is.. its overwriting capability.
We can see the overwriting functionality of DSO.
New request id is copied in new data table.
Activate new request RQ2.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 35
We can see change log table has all track of all records.
0RECORDMODE:
Upon activation of Standard DSO, BW adds the 0RECORDMODE InfoObject to the
definition of the Standard DSO and to all the three tables of the standard DSO.
This InfoObject is used internally by BW. We can overwrite the existing record for the same
semantic key field combination, in addition to adding key figure values for the record with
same semantic key field combination.
SAP Business Content offers DataSources for a number of standard business processes.
The DataSource field ROCANCEL, for example is mapped to the 0RECORDMODE
InfoObject in BW. The combination of the Update mode set in transformation, along with
the value of the 0RECORDMODE
Value Meaning
BLANK - after image The record provides an after image.
X - before image The record provides a before image.
A - additive image The record provides an additive image.
D - deleted The record must be deleted.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 36
R - reverse image The record provides a reverse image.

N - reverse image The record provides a reverse image.
DSO SETTINGS:
SID Generation upon Activation :

When checked(by default), the SIDs Generation Upon Activation box causes the system to
generate an integer number known as a Surrogate ID (SID) for each master data value.
These SIDs are stored in separate tables called SID tables. For each characteristic
InfoObject BW checks the existence of an SID value for each value of an InfoObject in the
SID table. The system then generates a new value of SID if an existing value is not found.
The SID is used internally by BW when a query is based on a DSO.
In cases where the Standard DSO is not used for reporting and is just used for staging
purposes, it is recommended to uncheck this checkbox.
Unique Data Records :
This setting is used when there is no chance that the data being loaded to a standard DSO
will create a duplicate record. It improves performance by eliminating some internal
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 37
processes. If this box is checked and it turns out that there are duplicate records, you will
receive an error message Because of this, we should select this box only when we sure
that you won’t have duplicate data.
Set Quality Status to “OK” Automatically:

The Set Quality Status to „OK‟ automatically flag results in the quality status of the data
being set to “OK” after being loaded without any technical errors; the status must be set to
this to activate newly loaded data in the standard DSO. Only activated data can be passed
to further data targets.
Activate Data Automatically:

Data loaded into standard DSOs first get sorted in the Activation Queue table, which is
activated using the activation process. To make this process automatic, you should check
this flag.
Update Data Automatically:

Activated data available in a standard DSO can be passed to other data targets, such as
another DSO or an InfoCube. This process can be automated by setting this flag.
The DSO contains 2 kinds of fields namely, the key field and the data field.
The combination of key fields is responsible for uniquely identifying the data.
All other objects can be included as data fields.
There are two ways to provide input InfoObjects into the DSO:
 Using Templates
 Using Direct Input
DataStore Object Types and Attributes
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 38
If you want to use the data in lookup of other infoprovider then also you need
DSO.
DSO offers flexibility in storage as you can use a WDSO and Direct update DSO
for different type of requirements.
USE OF CUBE:
Cube is good for reporting .
If we have huge amount of data and need multidimensional reporting then for
best reporting performance cube is only solution.
Cube allows aggregates and compression which DSO does not have .
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 39
Cube is good for line item level of data as it provides line item and high
cardinality dimensions.
So use a cube when data amount is large and good reporting performance is
required .
Use DSO when more granular data is required or you have delta requirements
Best way is use 3 layer architecture .
WDSO->DSO->CUBE .
When we use write optimized DSO?

Write optimized DSO used to pull large volume of data
Used where fast loads are essential. Example: multiple loads per day (or) short source
system access times (world wide system landscapes).
i) If the Data Source is not delta enabled. In this case, you would want to have a Write-
Optimized DataStore to be the first stage in BI and then pull the Delta request to a cube.
ii) Write-optimized DataStore object is used as a temporary storage area for large sets of
data when executing complex transformations for this data before it is written to the
DataStore object. Subsequently, the data can be updated to further InfoProviders. You only
have to create the complex transformations once for all incoming data.
b. Write-optimized DataStore objects can be the staging layer for saving data. Business
rules are only applied when the data is updated to additional InfoProviders.
c. If we want to retain history at request level. In this case you may not need to have PSA
archive; instead you can use Write-Optimized DataStore.
d. If a multi dimensional analysis is not required and you want to have operational reports,
you might want to use Write Optimized DataStore first, and then feed data into Standard
Datastore.
e. Probably you can use it for preliminary landing space for your incoming data from diffrent
sources.
f. If you want to report daily refresh data with out activation.In this case it can be used in
reporting layer with InfoSet (or) MultiProvider.
Functionality of Write-Optimized DataStore
Only active data table (DSO key: request ID, Packet No, and Record No):
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 40
No change log table and no activation queue.
Size of the DataStore is maintainable.
Technical key is unique.
Every record has a new technical key, only inserts.
Data is stored at request level like PSA table.
No SID generation:
Reporting is possible(but you need make sure performance is optimized )
BEx Reporting is switched off.
Can be included in InfoSet or Multiprovider.
Performence improvement during dataload.
Fully integrated in data flow:
Used as data source and data target
Export into info providers via request delta
Uniqueness of Data:
Checkbox “Do not check Uniqueness of data”.
If this indicator is set, the active table of the DataStore object could contain
several records with the same key.
Allows parallel load.
Can be included in Process chain with out activation step.
Supports Archiving.
Direct Update DataStore Objects The DataStore object for direct update differs from the
Standard DataStore object in terms of processing. In a standard DataStore object, data is
stored in different versions (active, delta, modified), whereas a DataStore object for direct
update contains data in a single version. Therefore, data is stored in precisely the same
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 41
form in which it was written to the DataStore object for direct update by the application. In
the BI system, you can use a DataStore object for direct update as a Data Target for an
analysis process such as for use with the Analysis Process Designer for data mining.. The
DataStore object for direct update is also required by diverse applications, such as SAP
Strategic Enterprise Management (SEM). DataStore objects for direct update ensure that
the data is available quickly. The data from this kind of DataStore object is accessed
transactionally. The data is written to the DataStore object (possibly by several users at the
same time) and reread as soon as possible. It is not a replacement for the standard
DataStore object. It is an additional function that can be used in special application
contexts. The DataStore object for direct update consists of a table for active data only. It
retrieves its data from external systems via fill or delete APIs. One of the advantages to the
way it is structured is that it is easy to access data. Data is made available for analysis and
reporting immediately after it is loaded.
Application programming interface (API)

It is important to understand the concept of APIs before understanding a Direct
Update DSO. An application programming interface (API) is a particular set of rules
and specifications that software programs can follow to communicate with each
other. It serves as an interface between different software programs and facilitates
their interaction, similar to the way the user interface facilitates interaction between
humans and computers.
An API can be created for applications, libraries, operating systems, etc.
It may include specifications for routines, data structures, object classes, and
protocols used to communicate between the consumer program and the
implementer program of the API.
The DataStore object for direct update consists of a table for active data only. It
retrieves its data from external systems via fill or delete APIs.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 42
The following APIs exist:

 RSDRI_ODSO_INSERT: Inserts new data (with keys not yet in the system).
 RSDRI_ODSO_INSERT_RFC: see above, can be called up remotely
 RSDRI_ODSO_MODIFY: inserts data having new keys; for data with keys already
in the system, the data is changed.
 RSDRI_ODSO_MODIFY_RFC: see above, can be called up remotely
 RSDRI_ODSO_UPDATE: changes data with keys in the system
 RSDRI_ODSO_UPDATE_RFC: see above, can be called up remotely
 RSDRI_ODSO_DELETE_RFC: deletes data
Analysis Process Designer :

Use
In SAP BW, data from various databases systems available in the company are
collected, consolidated, managed and prepared for evaluation purposes. There is
often further, valuable potential in this data.
The Analysis Process Designer (APD) makes it possible to find and identify these
hidden or complex relationships between data in a simple way. Various data
transformations are provided for this purpose, such as statistical and mathematical
calculations, and data cleansing or structuring processes.
The analysis results are saved in BW data targets or in a CRM system. They are
available for all decision and application processes and thus can be decisive
(strategically, tactically, and operatively).
Comparison of DataStore Object and InfoCube
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 43
Master data consist of;

1. Master data Attributes table.
2. Text data table.
3. Hierarchy table.
Info objects:
Characteristics and Key figures will be called as Info objects. Info objects are
similar to fields of source system using which we organize data in different info
provider in BW.
The properties of info objects will be always determine based on the source field properties
of which, we want to maintain data in info object.
Data types of characteristic:

CHAR-60
NUMC-60
DATS-8
TIMES-6
Key figure: Quantity, Amount, Number, Integer, Date, Time
Naming convention of BW objects:

0: Standard delivered object
Z/Y: User or Custom defined object
Technical name: Alpha Numeric, length- 3 to 8
Data dictionary naming convention:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 44
Standard objects: /BIO/<XXXXXX>

Custom objects : / BIC/<XXXXXX>
There are two types of data in SAP
They are Master Data (MD), Transaction Data (TD)
Master Data (MD): It does not change frequently.(Or) it is fixed over period of
time. It always assigned to characteristic. A characteristic is called MD
characteristic if it has attributes, text, hierarchies eg : CNO
ATTRIBUTES:
TYPES OF ATTRIBUTES:-
We have 7 types of attributes.
These are info objects which will explain a characteristic in detail.
Attributes are nothing but the fields or properties of the master data.These are
1. Display attribute
2. Navigational attribute
3. Time dependent attribute
4. Time dependent attribute navigational attribute
5. Exclusive attribute
6. Compounding attribute
7. Transitive attribute
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 45
1)Display Attr.
It completely depends on Master characteristic in reporting. We can access in any
Attr Table. It is available in /BIC/P table. When ever we select ATTR ONLY that will
b display attr.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 46
In query
Cust name,income will appear in query design when cno is in qd Otherwise they won’t
appear in qd
In report
Cust name,income will appear in result set when cno is in drill down
Key Figures
CUST NUM
CUST NUM CUST'S NAME CUST'S INCOME Number of Records
C100 VISH 100,000.00 1
C101 SOM 200,000.00 1
C102 CHAN 300,000.00 1
C103 DAYA 400,000.00 1
Otherwise they won’t appear in result set

Key Figures
CUST NUM
Number of Records
17
2)Navigational Attr
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 47
It is not depends on Master characteristic in reporting. We can access in any Attr

Table. It is available in /BIC/X table. When ever we de-select ATTR ONLY that will
be nav attr Where ever we want to use cno in any obj like(cube/ods) sys will take
nav_attr in nav part. And kf cann’t a nav attr .The naming convention of nav_attr is ”
M_CNO__M_CNAME(attr tab_attr name)”
De-select attr-only
switch on nav_attr and select text to get description
we will get nav_attr under obj
if we use cno in any obj(CUBE/ODS) sys will take nave attr.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 48
In query
In report
Key Figures
STATE
REGION
CNO
CNO REGION STATE INCOME
#/# # # 0.00 INR
Result 0.00 INR
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 49
Result 0.00 INR
Overall Result 0.00 INR
Key Figures
STATE
REGION
CNO
REGION STATE INCOME
# # 0.00 INR
Result 0.00 INR
Overall Result 0.00 INR
3)Time Dependent Attr

When we have an attr’s val is changing over period of time.And we want to maintain
the historical data.It is depends/not depends on Master characteristic in reporting.
We can access in any Attr Table. It is available in /BIC/Q table. When ever we
select/de-select ATTR ONLY that will be TD attr.For this attr we will get 2 more objs
(DATE_TO , DATE_FROM)
We need to select Time-dependent
Table 4 time dependent attr
data
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 50
In reporting it shows diff data based on time
ADDR
CNO
CNO ADDR
P1/C100 VIJ
P1/C200 VIJN
P2/C300 BAN
P2/C400 DEL
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 51
ADDR
CNO
CNO ADDR
P1/C100 VIJ
P1/C200 VIJN
P2/C300 BAN1
P2/C400 NDEL
4)Time Dependent Navigational Attr

When we have an attr’s val is changing over period of time.And we want to maintain
the historical data.It is depends/not depends on Master characteristic in reporting.
We can access in any Attr Table. It is available in /BIC/Y table. When ever we
select/de-select ATTR ONLY that will be TD attr.For this attr we will get 2 more objs
(DATE_TO , DATE_FROM).. It is not depends on Master characteristic in reporting.
We can access in any Attr Table. When ever we de-select ATTR ONLY that will be
nav attr Where ever we want to use cno in any obj like(cube/ods) sys will take
nav_attr in nav part. And kf cann’t a nav attr .The naming convention of nav_attr is ”
We need to select Time-dependent Nav-attr.
Table for time dependent nav attr
In reporting
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 52
CNO
STATE
CNO STATE
P1/C100 AP1
P1/C200 AP4
P2/C300 KA1
P2/C400 DEL1
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 53
CNO
STATE
CNO STATE
P1/C100 AP1
P1/C200 AP4
P2/C300 KA2
P2/C400 DEL2
5)Exclusive Attr.
It is not depends on Master characteristic in reporting. We can access in any Attr
Table oand obj like(cube/ods). It is available in /BIC/P table.When ever we de-select
ATTR ONLY that will be exclusive attr.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 54
CNO
Key Figures
CNO INCOME
P1/C100 0.00 INR
P1/C200 0.00 INR

________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 55
P2/C300 0.00 INR
P2/C400 0.00 INR
6)Compound Attr.
It is superior info obj. One value of info obj depends on value of other obj.It will act
as other primary key to attr table
Here cno is differed by plant number.
CNO
PLANT
CNO PLANT
P1/C100 P1
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 56
P1/C200 P1
P2/C100 P2
P2/C200 P2
7)Transitive Attr.
It is 2nd level of navigational attr. And it is Nav-attr of Nav-attr. It is not
depends on Master characteristic in reporting. We can access in any Attr Table. It is
available in /BIC/X table. When ever we de-select ATTR ONLY that will be nav attr
Where ever we want to use cno in any obj like(cube/ods) sys will take nav_attr in
nav part. And kf cann’t a nav attr .The naming convention of nav_attr is ”
FINALLY WE WILL GET 10 TABLES FOR MASTER TABLE:
/BIC/S- SID table for obj
/BIC/M- Master table for obj
/BIC/T- Text table for obj
/BIC/H- The hierarchical relationships of the characteristic values are stored in

this table, if external hierarchies are used for the characteristic
/BIC/K- The conversion of hierarchy nodes into SIDs is stored in this table.
Contrary to characteristic values, hierarchy nodes get negative SIDs
/BIC/I- The hierarchy structure is stored in this table
/BIC/P- All attributes will store in
/BIC/X- Table for Navigational attr
/BIC/Q- Table for Time Dependent attr
/BIC/Y- Table for Time Dependent Navigational attr.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 57
Navigational Attributes
A Navigational Attribute is an attribute of a Characteristic which is very similar to
Characteristic while Query Designer. We can perform drilldowns, filters etc on the same
while Query designing.
Note: While Creating the Info Object -- Attributes Tab Page -- Nav Attri butes to be
switched on . While Designing the Cube we need to Check mark for the Nav. Attributes to
make use of them.
Features / Advantages
 Nav. Attr. acts like a Char while Reporting. All navigation functions in the OLAP
processor are also possible
 Filters, Drilldowns, Variables are possible while Reporting.
 It always hold the Present Truth Data .
 Historic Data is not possible through Nav. Attributes.
 As the data is fetching from Master Data Tables and Not from Info Cube.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 58
Disadvantages:
 Leads to less Query Performance.
 In the enhanced star schema of an InfoCube, navigation attributes lie one join further
out than characteristics. This means that a query with a navigation attribute has to run an
additional join
 If a navigation attribute is used in an aggregate, the aggregate has to be adjusted
using a change run as soon as new values are loaded for the navigation
attribute.http://help.sap.com/saphelp_nw04s/helpdata/EN/80/1a63e7e07211d2acb80000e8
29fbfe/frameset.htmExclusive Attributes / Attributes Only/ Display Attribute
If you set the Attribute Only Indicator (General Tab page for Chars / Addl Properties
tabpage for Key Figs) for Characteristic while creating, it can only be used as Display
Attribute for another Characteristic , & it cannot be included in Info Cubes
 It can be used in DSO, Infoset and Char as InfoProviders. In this Info Provider , the
char is not visible during read access (at run time)
 This means, it is not available in the query. If the Info Provider is being used as
source of Transformation or DTP the characteristic is not visible.
 It is just for Display at Query and cannot be used for Drill downs while reporting.
Exclusive attributes:
If we choose exclusively attribute, then the created key figure can only be used as an
attribute for another characteristic, but cannot be used as a dedicated key figure in the
InfoCube.
Transitive Attributes
A Navigational attribute of a Navigational Attributes is called Transitive Attribute.
(Or) Second level of Navigational Attribute.
If a Nav Attr Has the further more Nav. Attributes ( as its Attributes ) in it those are called
Transitive Attributes .
 For Example Consider there exists a characteristic ‘Material’ .It has ‘Plant’ as its
navigational attribute. ‘Plant’ further has a navigational attribute ‘Material group’. Thus
‘Material group’ is the transitive attribute. A drilldown is needed on both ‘Plant’ and ‘Material
group’.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 59
Open Hub Destination: It enables us to distribute data from an SAP BW system into
external Data Marts, analytical applications, and other applications. We can ensure
controlled distribution using several systems. We can define the source and the target
object for the data. BW becomes a hub of an enterprise data warehouse. The distribution of
data becomes clear through central monitoring from the distribution status in the BW
system.
Data Transformation:
The InfoPackage (IP) and the Data Transfer Process (DTP) are used to execute the
transfer of data through the transformation process. These two items can be used to
manage the data loads by filtering the data uploaded (EX: only upload the data from North)
. The PSA (Persistent Staging Area) is the physical storage level that holds a set of data
that is exactly what the source system has, and it can therefore be used for a number of
tasks, such as a consistency checks against the data in the source system table to validate
the accuracy of the uploaded data.
Transformation Rule: The basic process is to map the fields from the source system to the
fields in the target system.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 60
The source and target fields can be combinations of a number of different systems,
including other BI systems. The portion in the middle of the screen is called the Standard
Group, and it can be used in a situation where common rules are used for a number of
different source and target combinations.
In above we can see the different options that can be used to work with the data
during the upload. . The Rule Types go from the basic direct assignment
between fields to the use of ABAP routines to create complex calculations before the data
reaches the InfoCube for reporting. In addition to this, the currency can be converted during
the upload, the key figures can be aggregated or adjusted to hold the maximum or
minimum of a range .
Data Targets:
Data Targets are InfoProviders that hold data. The Data Targets that can store data and
are generally used here include the DataStore objects (commonly referred to as the
Operational Data layer), InfoCubes (generally the Reporting layer), and InfoObjects (used
to store the master data from the source systems).
Non–Data Targets:
Non–Data Targets are those InfoProviders that are created to be used as a view of the data
from other sources. these InfoProviders do not hold any data but rather create a union or
join of the data during the query executionprocess. The types of Non–Data Targets are
MultiProviders, InfoSets, Virtual InfoProviders, and InfoSet Queries.
Data Targets Non–Data Targets
InfoCubes Standard and Real Time MultiProviders

InfoObjects—Characteristic InfoSets
DataStores—Standard, Direct Update,
and Write-Optimized Virtual InfoCubes—Data Transfer Process,
BAPI, and function module
Aggregate Levels—Integrated Planning
Objects (specific to BW-IP) InfoSet Queries
Rsa1 or rsa11: Infoprovider
Rsa12: Infosource
Rsa13: Source Systems
Rsa14: Info objects

________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 61
Rsa15: Datasources
Rsa16:Favorites
Rsa17: Find
Rsa18: Open hub destination
BI USEFUL TABLES
Customer Info objects Tables /BIC/S- SID table for obj
/BIC/M- Master table for obj
/BIC/M - View of Master data Tables /BIC/T- Text table for obj
/BIC/P - Master data (all attributes) Table, Time Independent attributes

/BIC/H- The hierarchical relationships of the
characteristic values are stored in this
/BIC/Q - Master data (all attributes) Table, Time Dependent attributes table, if external hierarchies are used
for the characteristic
/BIC/X - SID Table, Time Independent - Navigational attr /BIC/K- The conversion of hierarchy nodes
/BIC/Y - SID Tabel, Time Dependent - Navigational attr into SIDs is stored in this table.
Contrary to characteristic values,
/BIC/T - Text Table hierarchy nodes get negative SIDs
/BIC/H - Hierarchy Table /BIC/I- The hierarchy structure is stored in this table
/BIC/K - Hierarchy SID Table /BIC/P- All attributes will store in
/BIC/X- Table for Navigational attr
/BIC/Q- Table for Time Dependent attr
Standard Info objects Tables (Business Content): /BIC/Y- Table for Time Dependent Navigational attr.
Replace "C" with "0" in above tables.

Ex: /BI0/M - View of Master data Tables
Standard Infocube Tables :
/BI0/F - Fact Table(Before Compression)

/BI0/E - Fact Table(After Compression)
/BI0/P - Dimension Table - Data Package
/BI0/T - Dimension Table - Time
/BI0/U - Dimension Table - Unit
/BI0/1, 2, 3, .......A,B,C,D : - Dimension Tables
BW Tables:
BTCEVTJOB - To check List of jobs waiting for events

ROOSOURCE - Control parameters for Data source
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 62
ROOSFIELD - Control parameters for Data source

ROOSPRMSC - Control parameters for Data source
ROOSPRMSF - Control parameters for Data source
RSOLTPSOURCE - Replicate Table for OLTP source in BW
RSDMDELTA - Data mart Delta Management
RSSDLINITSEL, RSSDLINITDEL - Last valid Initialization to an OLTP Source
RSUPDINFO - Infocube to Info source correlation
RSUPDDAT - Update rules key figures
RSUPDENQ - Removal of locks in the update rules
RSUPDFORM - BW: Update Rules - Formulas - Checking Table
RSUPDINFO - Update info (status and program)
RSUPDKEY - Update rule: Key per key figure
RSUPDROUT - Update rules - ABAP routine - check table
RSUPDSIMULD - Table for saving simulation data update
RSUPDSIMULH - Table for saving simulation data header information
RSDCUBEIOBJ - Info objects per Infocube
RSIS – Info source Info
RSUPDINFO - Update Rules Info
RSTS - Transfer Rules Info
RSKSFIELD - Communication Structure fields
RSALLOWEDCHAR - Special Characters Table(T Code : RSKC, To maintain)
RSDLPSEL - Selection Table for fields scheduler(Info package's)
RSDLPIO - Log data packet number
RSMONICTAB - Monitor, Data Targets(Infocube/ODS) Table, request related info
RSTSODS - Operational data store for Transfer structure
RSZELTDIR - Query Elements
RSZGLOBV - BEx Variables
RXSELTXREF, RSCOMPDIR - Reports/query relevant tables
RSCUSTV - Query settings
RSDIOBJ – Info objects
RSLDPSEL - Selection table for fields scheduler(Info package list)
RSMONIPTAB – Info Package for the monitor
RSRWORKBOOK - Workbooks & related query genuine id's
RSRREPDIR - Contains Genuine id, Report Name, Author, etc...
RSRINDEXT - Workbook ID & Name
RSREQDONE - Monitor: Saving of the QM entries
RSSELDONE - Monitor : Selection for expected requests
RSLDTDONE - Texts on the requested info packages & groups
RSUICDONE - BIW: Selection table for user-selection update Infocubes
RSSDBATCH - Table for Batch run scheduler
RSLDPDEL - Selection table for deleting with full update scheduler
RSADMINSV - RS Administration
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 63
RSSDLINIT - Last Valid Initializations to an OLTP Source

BTCEVTJOB -To check event status(scheduled or not)
VARI - ABAP Variant related Table
VARIDESC - Selection Variants: Description
SMQ1 - QRFC Monitor(Out Bound)
SM13 - Update Records status
What is the impact on existing routines if we create expert routine?

Automatically existing routines will be deleted or de actived.
We have following types of routines in BI 7.
Start Routine:The start routine is run for each data package at the start of the
transformation. The start routine has a table in the format of the source structure as input
and output parameters. It is used to perform preliminary calculations and store these in a
global data structure or in a table. This structure or table can be accessed from other
routines. You can modify or delete data in the data package.
Routine for Key Figures or Characteristics:This routine is available as a rule type; you
can define the routine as a transformation rule for a key figure or a characteristic. The input
and output values depend on the selected field in the transformation rule.
End Routine:An end routine is a routine with a table in the target structure format as input
and output parameters. You can use an end routine to post process data after
transformation on a package-by-package basis. For example, you can delete records that
are not to be updated, or perform data checks.
Expert Routine:This type of routine is only intended for use in special cases. You can use
the expert routine if there are not sufficient functions to perform a transformation. The
expert routine should be used as an interim solution until the necessary functions are
available in the standard routine.
Types of characteristics InfoObject tables:
When we activate the char infoobject based on settings we choose while

creating the char infoobject the following tables will be generated.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 64
1) Master data table

2) Text table
3) SID Table
4) Attribute tables
5) Hierarchy tables.
Masterdatatable: M-View
While creating characteristic if we select the option “with master data” in “master
data/text” tab, then a master table will be generated for that info object upon
activation.
TexTable: T Table
A text table is created if we flag the “With text” check box while creating and
activating the characteristic info object. We can choose how text should look like
from the below properties.
SID Table: S Table
The SID table is generated when a characteristic is activated unless it is defined as

exclusively attribute (Display attribute only).
Attribute Tables:
If we have selected the option “With master data” (The check box is checked by
default) on the “Master data/Texts” tab page, then we can maintain attributes for the
master data bearing characteristic on the Attribute tab page. We can define
attributes as Display attributes or navigational attributes and we can make this
attributes as time independent or time dependent using the settings available on the
Attribute tab page.
If we have Display attributes (Time independent), then we will get P Table.

If we have Display attributes (Time dependent), then we will get Q Table.
If we have Navigational attributes (Time independent), then we will get X Table.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 65
If we have Navigation attributes (Time dependent), then we will get Y Table.
Hierarchies Tables: H Table
Hierarchies are used in analysis to describe alternative views of the data.

Hierarchies comprise a series of nodes that are joined to one another in a tree
structure. Usually, the leaves of a hierarchy are represented by characteristic values.
K Table: If we select “with hierarchies” option, then this table will be generated.
J Table: If we select “Intervals Permitted in Hierarchy” option, then this table will be
generated.
I Table: If we select “Time-Dependent Hierarchy Structure” option, then this
table will be generated.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 66
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 67
AGGREGATES
An aggregate is a materialized, summarized view of the data in an Info Cube. In other

words, it consolidates and stores a subset of Info Cube data into a database. This subset of
data is redundant and persistent. When we execute a query on an Info Cube with
appropriate aggregates, the query reads the summarized data directly from the database
thus eliminating the need to perform any processing related to summarization during query
runtime.
Aggregates creation is highly recommended when :
 Query execution and navigation requires speeding up.

 Navigational attributes are required to be used in the queries.
 Hierarchies used in the queries need to be speed up & we can aggregate
on specific hierarchy levels.
There are a few disadvantages
They increase load time

 through data packages uploads;
 through the hierarchy/attribute change run after loading master data;
 through adjusting time-dependent aggregates.
Roll up
If the InfoCube has aggregates that have aggregates already filled, then data that has been
recently loaded into an InfoCube is not visible for reporting, from the InfoCube or
aggregates, until an aggregate roll-up takes place.
During this process you can continue to report using the data that existed prior to the recent
data load. The new data is only displayed by queries that are executed after a successful
roll-up.
Change Run
A Change Run is executed only in the event of change in the master data. As changes in
the master data also trigger changes in navigational attributes or hierarchies, it is
recommended that data in the aggregates is adjusted after master data load. This ensures
consistency in Reporting results.
The change run adjusts the data in the aggregates and turns the modified version of the
navigational attributes and hierarchies into an active version. During the change run
process, you can carry out Reporting on old master data and hierarchies.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 68
BUSINESS CONTENT:
INTRODUCTION: Business Content is a pre-configured set of role and task-

relevant information models based on consistent metadata in the SAP BI. This
information model includes integral roles, workbooks, queries, InfoSources,
InfoCubes, DSO ,objects, key figures, characteristics, update rules, and
extractors for SAP R/3.
Business Content can be used in particular industries without being
modified ,be modified, meaning we can work with it to any degree of detail &
serve as a template or an example for customer-defined Business Content
Business Content includes:
R/3 extractor programs
DataSources
Process chains
InfoObjects
InfoSources
Data targets (InfoCubes & DSO)
Variables
Queries
Workbooks
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 69
Web templates
Roles
Business Content Versions:
SAP delivers Business Content in the SAP Delivery Version (D version). We need to
transfer the Business Content objects in the active version (A version) in order to be able
to work with them.
SAP delivers the Business Content objects in the D Version.
Changes are saved in the M version.
Active Business Content is saved in the A version.
Only those objects that were stored in the A version are exported from the development
system. When importing into the target system, these objects, dependent on object type,
are either imported directly into the active version or in a modified version.
SAP Delivery (Business Content upgrade):

SAP delivers the Business Content objects in a new D Version.
We can compare the new Business Content with his/her active customer version,
and either adopt the new version or merge it with his/her version.
Adopt: The customer version is deleted and replaced by the new Business
Content version.
Merge: The “total” is made from both objects and saved as a new customer
version.
NOTE:- When activating Business Content, the SAP delivery version is adopted and the
active customer versions are overwritten if you do not execute a match-up.
Installing Business Content :

Before working with Business Content objects, we have to convert them from the SAP
delivery version (D version) into the active version (A version).
We will install Business Content objects in the following cases:
After a Content release upgrade
After installing a Content Support Package
Procedure to Install Business Content :

The following are the steps for installing Business Contents
T. code: RSORBCT
Group Objects to Be Included, Determine Mode of Collection for Objects
Grouping : Choose the objects that we want the system to include.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 70
The groupings combine the objects from a particular area.
We have the following options:

Only necessary Objects: Collects only the necessary objects needed for activation
Data Flow before: Collects all the objects under the Current object. In our case, Our object
is Cube.. all the underlying objects like Datasource, Transformations, All infoobjects
needed for this will be activated
Data Flow Afterwards: Collects all the objects coming above, our case... Multi providers,
Queries....
Dataflow Before and Afterwards: All the objects above and below will be collected.
Collection Mode: how we want to collect the objects:

Collect Automatically (default setting): The data is collected directly when the objects
are selected.
Start Manual Collection: The data is collected only when we click on the Gather
Dependent Objects.
Install:
In Install tab we have 4 options..
Simulate Installation : To check for possible errors while activation.
Install : Installation of the selected objects in foreground
Install In Background : Installation in Background
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 71
Installation And Transport : Install and Transport Object to next System ( Production,
Quality)
The following Business Content objects are highlighted in this column by default:
Objects that are being transferred for the first time. There is not an active version of
these objects in the system.
Business Content objects that have been redelivered in a new version. These
objects are identified by the Content time stamp in the corresponding object tables.
Check on the install checkboxes for all the dependants.
In the context menu, the following two options are available for the installation:
Install all Below :The object in the selected hierarchy level and all objects in the lower
levels of the hierarchy are selected as to Install.
Do Not Install All Below: The Install indicators are removed for the object in the selected
hierarchy level and all objects in the lower levels of the hierarchy.
Match (X) or Copy :
If the SAP delivery version and the active version can be matched, a checkbox is
displayed in this column.With the most important object types, the active version and the
SAP delivery version can be matched.
When a match is performed, particular properties of the object are compared in the A
version and the D version. First it has to be decided whether these properties can be
matched automatically or whether this has to be done manually.
A match can be performed automatically for properties if you can be sure that the object
is to be used in the same way as before it was transferred from Business Content.
When performing matches manually you have to decide whether the characteristics of a
property from the active version are to be retained, or whether the characteristics are to
be transferred from the delivery version.
The Match indicator is set as default in order to prevent the customer version being
unintentionally overwritten. If the Content of the SAP delivery version is to be matched to
the active version, you have to set the Installindicator separately.
The active version is overwritten with the delivery version if the match indicator is not set
and the install indicator is set.
Active Version Available:

In this column, the following display options are available:
 The object is available in an active version. You decide whether you want to
retain this version or reinstall the latest version of the object.
 Date symbol: The object is already available in an active version. However, the
active version belongs to an older Content release. SAP recommends that you
install the latest version.
 Gray symbol : An activated version of the object is available in the system.
However, the object status is inactive. If an object version is activated, this
indicates that all metadata for the object can be created successfully. The inactive
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 72
object status indicates that the processed object is inconsistent and cannot
currently be used for processing data.
 No indicator: The object is not available in an active version.
Installation Type:
Simulate installation: The system runs a test to see whether any errors are likely to occur
during the installation.
Install: The selected objects are installed immediately.
Install in background: The selected objects are installed in the background.
Install and transport : The selected objects are installed immediately and then written to a
transport request.
Remodeling:
INFO CUBE:
Prerequisites
We have created an Infocube and loaded data into it. If we need to perform Key
figure operation (Add, Replace or Delete) and InfoCube contains few compressed
and few uncompressed requests we need to compress all of the requests before we
proceed. Remodeling cannot be performed on a partially compressed InfoCube.
We can select one of the following options from the dialog box:
Add characteristic/key figure
Delete characteristic/key figure
Replace characteristic/key figure
 For the Add Characteristic and Replace Characteristic options, we have to specify
how you want to fill the new characteristic with data:
Constant: The system fills the new characteristic with a constant.
Attribute: The system fills the new characteristic with the values of an attribute of a
characteristic that is contained in the same dimension.
1:1 mapping for characteristic: The system fills the new characteristic with the values of
another characteristic in the same dimension. You replace one characteristic with another
for example, thereby adopting the value of the original characteristic.
Customer exit: The system fills the new characteristic using a customer exit. More
information.
For key figures, Constant and Customer exit filling methods are supported for Add Key
figure and only Customer exit for Replace Key Figure.
Data Store Object :
Prerequisites
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 73
For Data Store Object, we recommend deleting the change log data before remodeling. If
the change log data is not deleted then the filling methods would not be supported for any
of the operations.
MultiProviders:
A MultiProvider is a type of InfoProvider that combines data from a number of InfoProviders
and makes it available for analysis purposes. The MultiProvider itself does not contain any
data. Its data comes entirely from the InfoProviders on which it is based. These
InfoProviders are connected to one another by a union operation.
A MultiProvider allows you to analyze data based on several InfoProviders.
Ex: List of Slow-Moving Items, Plan-Actual Data, Sales Scenario
A MultiProvider can consist of different combinations of the following InfoProviders:

InfoCube, DataStore object, InfoObject, InfoSet, VirtualProvider, and aggregation level.
Infoset
Infoset is a special kind of Infoprovider which doesn't store data physically. Infoset collects
data from the tables of InfoProviders used to build it.InfoSet describes data sources that
are defined as a rule of join on DataStore objects, standard InfoCubes and/or InfoObjects
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 74
(characteristics with master data).
Some times we come across the scenarios where we have to build a report on two/more
different data targets.In this cases we can use Infosets which joins two/more data
targets,and we can bulid Query on Infoset,which gets data from tables of Infoproviders
used to build it lets create Infoset on Infocube and InfoObject
Virtual InfoCubes:
Virtual InfoCubes are InfoProviders with transaction data that is not stored in the objects
themselves, but is read directly for analysis and reporting purposes. The relevant data can
be from the BI system or from other SAP or non- SAP systems. Virtual Providers only allow
read access to data. The different Virtual Providers are based on the data transfer process,
on a BAPI (Business Application Program Interface), or on the function module. Each has a
specific responsibility and use in the view of data and may be used in the process of a
specific application involved with BI.
Based on Data Transfer Process Data Transfer Process (DTP) Virtual Providers are
those whose transaction data is read directly from an SAP system using a DataSource or
an InfoProvider for analysis and reporting purposes. The DTP Virtual InfoCube allows you
to define the queries based on direct access to transaction or master data in other source
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 75
systems. This Virtual Provider is used if we require up-to-date information from an SAP
source system, but it is suggested that we can access a small set of data and that you only
use this process for a specific set of users. This Virtual Provider is not meant to be used for
accessing large amounts of data, or having large numbers of users accessing data via this
approach.
Based on BAPI: This Virtual Provider is different from the DTP Virtual Provider because
the transaction data is read for analysis and reporting from an external system using a
BAPI (Business Application Program Interface) and not specifically from an SAP source.
The BAPI-based option allows reporting using data from non-SAP systems. The external
system transfers the requested data to the OLAP processor via the BAPI. This could be
used by a company that wants to provide an access solution to its data for its SAP
customers. When you start a query with a Virtual Provider, you trigger a data request with
characteristic selections. The source structure is dynamic and is determined by the
selections. For this type of Virtual Provider, a non-SAP system transfers the requested data
to the OLAP processor using the BAPI. This Virtual Provider allows you to connect non-
SAP systems that are not relational in nature. The uses of this Virtual Provider include
carrying out analyses on data in external systems without having to physically store
transaction data in the BI system.
When we use a Virtual Provider to analyze data, the data manager calls the Virtual
Provider BAPI instead of an InfoProvider filled with data, and it transfers the parameters
for the selections, characteristics, and key figures. The external system transfers the
requested data to the OLAP processor.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 76
Based on Function Module: The Virtual Provider with a user-defined function module
reads the data in the Virtual Provider for analysis and reporting purposes. We have a
number of options for defining the properties of the datasource more precisely.
According to these properties, the data manager provides various function module
interfaces for converting the parameters and data. These interfaces have to be
implemented outside the BI system. You use this Virtual Provider if we want to display data
from non-BI datasources in BI without having to copy the dataset into the BI structures. The
data can be local or remote.
This Virtual Provider is used primarily in the SAP Strategic Enterprise Management (SEM)
application for SEM-BCS reporting purposes. In comparison to other
Virtual Providers, this one is more generic. It offers more flexibility, but also requires a
higher implementation effort.
PROCESS CHAIN:
A process chain is a sequence of processes that are scheduled to wait in the

background for an event. Some of these processes trigger a separate event that
can, in turn, start other processes. It looks similar to a flow chart. We define the
list of Infopackages / DTPs that is needed to load the data, say delta or Full load.
Then we schedule the Process chain as hourly, daily, monthly, etc, depending on
the requirement
RECONCILIATION:
Reconciliation is nothing but the comparison of the values between BW target data with the
Source system data like R/3.
In general this process is taken at 3 places one is comparing the info provider data with R/3
data, Compare the Query display data with R/3 or DSO data and Checking the data
available in info provider kefigure with PSA key figure values.
Important Transaction Codes in SAP BI
Tcode Description
DB02 Tables and Indexes Monitor
DB04 DB Performance Monitor
DB14 Display DBA Operation Logs
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 77
DB16 Display DB Check Results
DB20 Update DB Statistics
KEB2 DISPLAY DETAILED INFO ON CO-PA DATA SOURCE R3
LISTCUBE List viewer for InfoCubes
RSORBCT Show InfoCube schema
LBWE LO Data Extraction: Customizing Cockpit
LBWF BW Log
LBWG To Delete Setup Tables
NPRT To see setup log
OLI*BW To fill Setup Tables (* Application Component) [i.e. 7 for SD Sales

Orders]
OS06 Local Operating System Activity
OB08 Currency Exchange Rates
PFCG Authorization
RRMX Business Analyzer Loader
RS12 Overview of Master Data Locks
RSA1 Administrator Work Bench
RSA2 OLTP Metadata Repository
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 78
RSA3 Extractor Checker
RSA5 Install Business Content
RSA6 Maintain Data Sources
RSA7 BW Delta Queue Monitor
RSA8 Data Source Repository
RSA9 Transfer Application Components
RSA11 Calling up AWB with the IC tree
RSA12 Calling up AWB with the IS tree
RSA13 Calling up AWB with the LG tree
RSA14 Calling up AWB with the IO tree
RSA15 Calling up AWB with the ODS tree
RSBBS Maintain Query Jumps (RRI Interface)
RSBICA Modeling BI Integrated Planning
RSCUSTA Maintain BW Settings
RSCUSTA2 ODS Settings
RSCUSTV4 BEx Values(To View/Change Global BEx Settings)
RSD1 Characteristic maintenance
RSD2 Maintenance of key figures
RSD3 Maintenance of units
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 79
RSD4 Maintenance of time characteristics
RSD5 Edit InfoObjects
RSDBC DB connect
RSDCUBE Start: InfoCube editing
RSDCUBED Start: InfoCube editing
RSDCUBEM Start: InfoCube editing
RSDDBIAMON BI Accelerator Monitor
RSDDV Maintaining Aggregates
RSDIOBC Start: InfoObject catalog editing
RSDIOBCD Start: InfoObject catalog editing
RSDIOBCM Start: InfoObject catalog editing
RSDL DB Connect - Test Program
RSDMD Master Data Maintenance w.Prev. Sel.
RSDMD_TEST Master Data Test
RSDMPRO Initial Screen: MultiProvider Proc.
RSDMPROD Initial Screen: MultiProvider Proc.
RSDMPROM Initial Screen: MultiProvider Proc.
RSDMWB Customer Behavior Modeling
RSDODS Initial Screen: ODS Object Processing
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 80
RSDS Data Source Repository
RSIMPCUR Load Exchange Rates from File
RSINPUT Manual Data Entry
RSIS1 Create InfoSource
RSIS2 Change InfoSource
RSIS3 Display InfoSource
RSISET Maintain InfoSets
RSKC Maintaining the Permitted Extra Chars
RSLGMP Maintain RSLOGSYSMAP
RSMO Data Load Monitor Start
RSMON BW Administrator Workbench
RSO2 Generic Data Extraction Tools. Maintain /Create data source
RSOR BW Metadata Repository
RSORBCT BI Business Content Transfer
RSORMDR BW Metadata Repository
RSPC Process Chain Maintenance
RSPC1 Process Chain Display
RSPCM Monitor daily process chains
RSPLAN Modeling BI Integrated Planning
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 81
RSPLSE BI Planning Lock Management
RSRCACHE OLAP: Cache Monitor
RSRT Start of the report monitor
RSRT1 Start of the Report Monitor
RSRT2 Start of the Report Monitor
RSRTRACE Set trace configuration
RSRTRACETEST Trace tool configuration
RSRV Analysis and Repair of BW Objects
RSSM Authorizations for Reporting
RSZDELETE To Delete Query Elements
RZ20 To see log for Process Chains
SCC4 Client Overview
SE03 Transport Organizer Tools
SE06 Set Up Transport Organizer
SE07 CTS Status Display
SE09 Transport Organizer
SE10 Transport Organizer
SE11 ABAP Dictionary
SE18 Business Add-Ins: Definitions
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 82
SE18_OLD Business Add-Ins: Definitions (Old)
SE19 Business Add-Ins: Implementations
SE19_OLD Business Add-Ins: Implementations
SE21 Package Builder
SE24 Class Builder
SE80 Object Navigator
SE93 to view Transaction Codes
SM04 User List
SM12 Display and Delete Locks
SM21 Online System Log Analysis
SM37 Overview of job selection
SM50 Work Process Overview
SM51 List of SAP Systems
SM58 Asynchronous RFC Error Log
SM59 RFC Destinations (Display/Maintain)
SM66 Global work process Monitor
SMQ1 qRFC Monitor (Outbound Queue)
SMQ2 qRFC Monitor (Inbound Queue)
SQ02 Infoset Query
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 83
ST02 Tune Summary
ST03 Work load: Statistical Records
ST04 DB Performance Monitor
ST22 ABAP Runtime Error (Dumps)
ST14 BW Evaluation Application Analysis
STMS Transport Manager
SU01 Create new user
SOME OF THE INTERVIEW QUESTIONS:
1. What is your role & responsibilities in current project?

2. Tell me about yourself?
3. How many reports you have generated?
4. What is your team size?
5. What is your system landscape?
6. What is your ticketing tool?
7. What is your latest ticket that you have resolved?
8. What are the different issues in support & maintenance?
9. In which environment are you working?
10. Which type of support are you giving?
11. Who is your reporting manager?
12. What activities you perform every day?
13. What are the t- codes you are using in support & maintenance?
14. What are the different data load issues?
15. What are the different process chain issues?
16. How many process chains you have created?
17. How to kill a job?
Etc….
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 84
TOPIC PNO
SAP BI LAND SCAPE

T CODES (EXTRACTION)
EXTRACTOR TYPES
EXTRACTOR
EXTRACT STRUCURE (ES)
TRANSFOR STRUCTURE (TS)
TYPES OF DATA SOURCES
SAP DEFINED DATA SOURCES (DS)
LO EXTRACTION
TYPES OF LOADS (UPDATE MODES) (FULL, INIT, DELTA)
DELTA UPDATE METHODS (DIRECT, QUEUE DELTA, UN SERIALISED)
UPDATE MODES (V1, V2)
V3 UPDATE
IMP TRANSACTION DATA DS’S (LO)
ES’S
DIFFERENCE BETWEEN HDR, ITM, SCL
SEP UP TABLES
SEP UP TABLES FILLING (T.CODES)
FINDING DELTA CAPABLE OF DS
SD DS’S
PURCHASING DS’S
INVENTORY DS’S
IMP MD DS’S
TABLES RELATED TO MD DS’S
IMP FI DS’S
TABLES RELATED TO FI DS’S
WHY WE USE DSO BEFORE IC(WHEN WE ARE LOADING DATA FROM FI DS’S)
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 85
LANDSCAPE OF SAP BI:
IMPORTANT T.CODES IN EXTRACTION

SBIW: DISPLAY IMG
RSA3: EXTRACTOR CHECKER S - API
RSA5: INSTALLATION OF DATA SOURCE FROM BUSINESS CONTENT
RSA6: POST PROCESS DATA SOURCES
RSA7: BW DELTA QUEUE MAINTENANCE
RSA9:
LBWE:
LBWQ: QRFC MONITOR (OUT BOUND QUEUE)
LBWG:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 86
SM13 : UPDATE REQUEST INITIAL SCREEN

OLI*BW : FILLING SET UP TABLES
RSO2 : MAINTAIN GENERIC DATA SOURCE
SE11
ROOSOURCE - Table to find out delta update methods.
RODELTAM - Finding for modes of records (i.e. before image & after image)
SMOD – SYSTEM MODIFICATIONS
CMOD – CUSTOMER MODIFICATIONS
SE09 - Transport Organizer (workbench organizer)
SE10 - Transport Organizer (Extended View)
SBIW - Implementation guide
LBWQ -> QRFC related Tables (TRFCQOUT, QREFTID, ARFCSDATA)
TYPES OF EXTRACTORS (DATA SOURCES):

Extractors are two types:
1. Application specific: These are specific to an applications (i.e Specific to SD, MM,
PP, PM, QM, …. ETC)
Again Application specific DS’S are divided into SAP defined (Business content
Extractors) & Customer Defined extractors.
a. Business content: These are given by SAP & are available in D Version.
b. Customer defined : These are generated by Customer (ex: FI-SL, CO-PA). DS
is not created ,where as it is generated based on some other objects.
2. Cross application: These can combination of different applications. (i.e when we
want to generate a DS based on different fields from different applications ).
These are also called Generic DS’S (GDS). Here we create our own DS.
When we do not have any business content DS available we go for GDS.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 87
EXTRACTOR:: It is a program or a simple terminology is used for extracting the data from
various sources to BW.
TYPES OF TABLES:
1. TRANSPARENT TABLE
2. POOLED TABLE
3. CLUSTER TABLE
Transparent table: One to one relation

One table in data dictionary equal to one table in data base.
When we create one transparent table in ABAP dictionary one table will be created in
Database with same name(Both table and fields). Basically used to hold application data.
Ex: EKKO,VBAK etc.

Pooles tabel: Many to one relationship
Many tables in ABAP dictionary equal to one table pool in database. Basically used to hold
system data and customization data. One table pool contains large number of pooled
tables having data of around 100 records each.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 88

Cluster tables: Many to one relationship
Many tables in ABAP dictionary equal to one table cluster in database. Basically used to
hold application data. One table cluster contains few number of cluster tables having data
of around large quantities.(In lakhs )
Ex: CDPOS, BSEG etc.

Incase of pooled and cluster tables ABAP data dictionary table name and Data base table
and field names differs unlike same in case transparent table.

There are some limitations on cluster tables like we can't use joins on these tables, Select
on cluster table is always very slow.

When ever we write query on any cluster table in the table cluster data will be fetched for all
he table as data for all the tables in the cluster stores as a single record.

Business content extractors: These are ready made DS’S given by SAP (Ex: LO, FI, CO,
HR …etc) & are available in Deliver (D) version. We can find these DS’S in T. Code RSA5.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 89
What is RSA5: INSATALATION OF DS FROM BUSINESS CONTENT (BC).
IN RSA5, the DS’S are available in D VERSION we will not work on these DS’S. If we want
use or work on any DS first we have to activate the DS. For this select the DS (EX:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 90
2LIS_11_VAHDR) which we want to use & click on activate DS. Now this DS
(2LIS_11_VAHDR) is available in RSA6 in active version.
Customer - Defined DS: These are Defined (Generated by customer). Ex: FI-SL (Financial
– Spl Ledger ), CO-PA (Controlling & profitability analysis) & LIS (Logistic Information
System (500 to 999) ).
WHAT IS DATA SOURCE (DS)?

A DS is a set of fields that provide the data for a business unit for data transfer into BI.
From a technical viewpoint, the DataSource is a set of logically-related fields that are
provided to transfer data into BI.
(OR)
EXTRACT STRUCTURE & TRANSFER STRUCTURE IN SOURCE SYSTEM &
TRANSFER STRUCTURE IN BI SYSTEM
There are four types of DS’S:
1. DataSource for transaction data
2. DataSource for master data attributes
3. DataSource for master data texts
4. DataSource for master data hierarchies
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 91
Use
DataSources supply the metadata description of source data. They are used to extract data
from a source system and to transfer the data to the BI system.
SOURCE SYSTEM (SS): The system which is supplying data to Target System (BI).
EXTRACT STRUCTURE (ES): Grouping of fields indicating what will be extracted from
Source System.
TRANSFER STRUCTURE (TS): Out of extracted fields which fields are send to BI.
We can determine the DataSource fields in which we hide extraction structure fields from
the transfer. This means filtering the extraction structure and/or enhancing the DataSource
fields, meaning completing the extraction structure.
NOTE: ES & TS in SS can be different. But TS in SS & BI will be the same.
Application specific BW content extractors (Data sources):
LLo Extraction:
Logistics refers to the process of getting a product or service to its desired location upon
request which involves transportation, purchasing, warehousing etc.
Main areas in logistics are: SD, MM, PP, QM, PM, PS, CS ETC
T.code : LBWE
APPLICATION APPLICATION NO
Sales and Distribution (SD) : 11, 13, 08

Materials Management (MM) : 03, 02
Logistics Execution (LE) : 12
Quality Management : 05
Plant Maintenance (PM) : 04, 17
Customer Service (CS) : 18
Project System (PS) : 20
SAP Retail : 40,43,44,45

How the data extraction happens?
Extraction can be done using either Full update/delta update.

________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 92
Full load: Incase of logistic application, Full/Initialization will extract the data from setup
tables (contains only historical data). For full update the data will be taken from setup
tables
Initialization: Data will be fetched from application table to setup tables (In Lo extraction, the
extractor won't allow the direct communication with the application tables) from here, data
finally reaches the target (info cube/ODS).Remember this process is for onetime.
Pre-requisites: Prior to initialization make sure the following steps are completed:
1. Maintain Extract Structure
2. Maintain data sources
3. Activate Extract Structure
4. Delete Setup tables
5. Fill setup tables

Delta load: Once after successful initialization, we can use delta update to capture the
changed /new records. Once a new transaction happens/an existing record is modified,
upon saving it goes to the respective application table. From here depending on the update
mode the data will be populated in delta queue (RSA7) and finally reaches to BW.

Pre-requisites: Prior to delta loads make sure the following steps are completed:
1. Define periodic V3 update jobs

2. Setting up the update mode (direct/queued/Un serialized v3 update)

LO- Delta Mode:
Info object 0Recordmode helps in identifying the delta
Check the field "delta "in ROOSOURCE /RODELTAM table
In case of Lo extraction it is "ABR"
ABR: An after image shows the status after the change, a before image the status before
the change with a negative sign and the reverse image also shows the negative sign next
to the record while indicating it for deletion. This serializes the delta packets.This process
supports an update in an DSO as well as in an Info Cube.
SOME OF THE IMPORTANT DS’S IN LO:

SD
DS NAME DESCRIPTION ES NAME
2LIS_11_VAHDR SALES DOC HEADER MC11VA0HDR

2LIS_11_VAITM SALES DOC ITEM MC11VA0ITM
2LIS_11_VASCL SALES DOC SCHEDULINE MC11VA0SCL
2LIS_11_VASTH SALES DOC HEADER STATUS MC11VA0STH
2LIS_11_VASTI SALES DOC ITEM STATUS MC11VA0STI
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 93
DELIVERY
2LIS_12_VCHDR DELIVERY DOC HEADER MC12VC0HDR
2LIS_12_VCITM DELIVERY DOCITEM MC12VC0ITM
2LIS_12_VCSCL DELIVERY DOCSCHEDULINE MC12VC0HDR
BILLING
2LIS_13_VDHDR BILLING DOC HEADER MC12VC0HDR
2LIS_13_VCITM BILLING DOCITEM MC12VC0ITM
SD DS’S TABLES
2LIS_11_VAHDR VBAK, VBUK, T001
2LIS_11_VAITM VBAP, VBUP, VBAK, VBKD, VBAJP, T001, VBUK, PRPS.
2LIS_11_VASCL VBAP, VBUP, VBAK, VBEP, VBKD, T001, PRPS
2LIS_11_VASTH VBUK
2LIS_11_VASTI VBUP, VBUK
2LIS_11_V_ITM VBAP, VBAK, VBKD, VBUP, T001, PRPS, VBUK.
2LIS_11_V_SCL VBUP, VBEP, VBKD, VBAP, VBAK, T001, PRPS.
MM
PURCHASING
2LIS_02_HDR PUR DOC HEADER MC02M_0HDR
2LIS_02_ITM PUR DOC ITEM MC02M_0ITM
2LIS_02_SCL PUR DOC SCHEDULINE MC02M_0SCL
INVENTORY
2LIS_03_BX STOCK INITIALIZATION MC03BX0
2LIS_03_BF GOODS MOVEMENT MC03BF0
2LIS_03_UM STOCK REVALUATION MC03UM0
SD DS’S TABLES
2LIS_11_VAHDR VBAK, VBUK, T001
2LIS_11_VAITM VBAP, VBUP, VBAK, VBKD, VBAJP, T001, VBUK, PRPS.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 94
2LIS_11_VASCL VBAP, VBUP, VBAK, VBEP, VBKD, T001, PRPS

2LIS_11_VASTH VBUK
2LIS_11_VASTI VBUP, VBUK

MM
PURCHAGING
2LIS_02_HDR EKKO, EKBE, T001, EKPA.
2LIS_02_ITM EKKO, EKBE, T001, T001W, EKPO, TMCLVBW, T027C,
ESSR, T147K, T147
2LIS_02_SCL EKKO, EKBE, T001, T001W, EKET, EKPA.
INVENTORY
2LIS_03_BX MCHA, MARA, T001, T001W,
CALCULATED FROM MBEW, EBEW, QBEW.
2LIS_03_BF MSEG, MBEW, MKPF.
2LIS_03_UM BKPF, MBEW, QBEW, EBEW, BSEG.
MM
PURCHASING CUBE
0PUR_C09 0PUR_O02, 80PUR_O01: 2LIS_02_HDR
0PUR_C04: 2LIS_02_SCL, 2LIS_02_ITM, 2LIS_02_HDR
0PUR_C01 : 2LIS_02_S012, 2LIS_02_ITM, 2LIS_02_SCL
INVENTORY MANAGEMENT CUBE
0IC_C03 2LIS_03_BX, 2LIS_03_BF, 2LIS_03_UM
IMP TABLES:
Data dictionary tables
DD02L : Tables in SAP
DD02T Tables description
DD03L Field names in SAP

________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 95
DD03T Field description in SAP
T009 Fiscal year variants
T005 Countries
T880 Company
T001 Company code
TKA01 Controlling area
T001W Plant / sales organisation
T001L Storage locations
T499S Locations
TSPA Division
T024E Purchasing organization
TVKO Sales organisation / company code
TVTW Distribution channel
TVBUR Sales office
TVTA Sales area
TVKGR Sales group
Data dictionary tables
DD02L Tables in SAP
DD02T Tables description
DD03L Field names in SAP
DD03T Field description in SAP
Sales and Distribution (SD):
VBFA Document flow (alg.)
VTFA Flow shipping documents
Sales order:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 96
VBAK Header data
VBAP Item data
VBPA Partners in sales order
VBKD Sales business data
VBEP Data related to line items, delivery lines
Billing document :
VBRK header data
VBRP Item data
Shipping :
VTTK Shipment header
VTTP Shipment item
VTTS Stage in transport
VTSP Stage in transport per shipment item
VTPA Shipment partners
VEKP Handling Unit - Header Table
VEPO Packing: Handling Unit Item (Contents)
Delivery :
LIKP Delivery header
LIPS Delivery item
Pricing :
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 97
KONH Conditions header
Material Management (MM) :
Material document
MKPF material document
MSEG material document (item level)
Purchasing
EKKO Purchase document
EKPO Purchase document (item level)
EKPA Partner functions
EIPO Item export / import data
EINA Purchase info record (main data)
EINE Purchase info record (organisational data)
EORD Source list
EBAN Purchase requisition
EBKN Purchase Requisition Account Assignment
Inventory documents in WM
LINK Inventory document header
LINP Inventory document item
LINV Inventory data per quant
MASTER DATA :
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 98
Material master :
MARA Material master
MAKT Material text
MARC Material per plant / stock
MVKE Material master, sales data
MARD Storage location / stock
Customer master data
KNA1 Customer master
KNB1 Customer / company
KNVV Customer sales data
KNBK Bank details
KNVH Customer hierarchy
KNVP Customer partners
KNVS Shipment data for customer
KNVK Contact persons
Vendor
LFA1 Vendor master
LFB1 Vendor per company code
LFB5 Vendor dunning data
LFM1 Purchasing organisation data
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434 99
LFM2 Purchasing data
LFBK Bank details
Customer – material info record
KNMT Customer material info record
Bank data
BNKA Master bank data
FI :
Master data
SKA1 Accounts
BNKA Bank master record Accounting documents // indices
BKPF Accounting documents
BSEG item level
BSID Accounting: Secondary index for customers
BSIK Accounting: Secondary index for vendors
BSIM Secondary Index, Documents for Material
BSIP Index for vendor validation of double documents
BSIS Accounting: Secondary index for G/L accounts
BSAD Accounting: Index for customers (cleared items)
BSAK Accounting: Index for vendors (cleared items)
BSAS Accounting: Index for G/L accounts (cleared items)
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
100
STEP BY STEP PROCEDURE FOR LO EXTRACTION:

ACTIVATE DATA SOURCE (DS)IN ECC(R/3) RSA5
CHECK THE DS RSA6
DE ACTIVATE UPDATE LBWE
MAINTAIN EXTRACT STRUCTURE(ES) LBWE
MAINTAIN DS LBWE
TRANSFER THE DS TO BI RSA6
REPLICATE DS RSA13
CHECK FOR DS
ACIVTE ES
MAINTAIN TRANFORMATIONS
MAINTAIN IC
DELETE SETUP TABLES LBWG
FILL THE SETUP TABLES OLI*BW
ACTIVATE UPDATE LBWE
CHECK THE DATA THROUGH EXTRACT CHECKER RSA3
CREATE IP FOR FULL UPDATE RSA12
CREATE DTP RSA11
SETUP V3 UPDATE SETTINGS LBWE
CREATE IP FOR DELTA UPDATE RSA15
CREATE DTP FOR DELTA UPDATE RSA11
ABAP TABLES & RELATED FIELDS

EKKO (table): PURCHASING DOC HEADER
Fields: EBELN: PO DOC NO
BSART: PO DOC TYPE
EKORG: P. ORG
BUKRS: COCODE
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
101
LIFNR: VENDOR NO
EKPO: PURCHASING DOC ITEM
EBELN: PO DOC NO
EBELP: PO DOC ITEM NO
MENGE: QUANTITY
MEINS: UNIT OF MEASURE
NETPR: NET PRICE
KNA1: CUSTOMER MASTER TABLE
KUNNR: CUST NO
NAME1: NAME OF THE CUSTOMER
ORT01: CITY
LAND1: COUNTRY
SPRAS: LANGUAGE
KNB1: CUSTOMERS UNDER COMPANY
BUKRS: COCODE
KUNNR: CUST NO
AKONT: RECON ACCOUNT
PERNR: PERSONAL NO
KNBK: CUSOMER BANK DETAILS
KUNNR: CUST NO
BANKS: BANK COUNTRY KEY

________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
102
BANKL: BANK KEY
BANKN: ACCONT NO
LFA1: VENDOR MASTER TABLE
LIFNR: VENDOR NO
NAME1: NAME OF THE VENDOR
ORT01: CITY
LAND1: COUNTRY
SPRAS: LANGUAGE
LFB1: VENDORS UNDER COMPANY
BUKRS: CO CODE
LIFNR: VENDOR NO
AKONT: RECON ACCOUNT
PERNR: PERSONAL NO
LFBK: CUSTOMER BANK DETAILS
LIFNR: VENDOR NO
BANKS: BANK COUNTRY KEY
BANKL: BANK KEY
BANKN: ACCONT NO
MARC: MATERIAL PLANT TABLE
MATNR: MATERIAL NO
WERKS: PLANT NO
T001: COCODES TABLE
BUKRS: COCODES
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
103
BUTXT: NAME OF THE COMPANY
ORT01: CITY NAME
LAND1: COUNTRY NAME
SPARS: LANGUAGE
ADRNR: ADDRESS
T001L: STORAGE LOCATIONS
WERKS: PLANT
LGORT: STORAGE LOCATION
LGOBE: DESCRIPTION OF STORAGE LOCATION
SPART: DIVISION
T001W: PLANT DESCRIPTION TABLE
WERKS: PLANT NO
NAME1: NAME OF THE PLANT
MARA: MATERIAL MASTER DATA
MATNR: MATERIAL NO
MTART: MATERIAL TYPE
MATKL: MATERIAL GROUP
BISMT: OLD MATERIAL NO
MAKT: MATERIAL DESCRIPTION TABLE
MATNR: METERIAL NO
MAKTX: MATERIAL DESCRIPTION
SPRAS: LANGUAGE
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
104
VBAK: SALES DOC HEADER TABLE
VBELN: SALES DOC NO
VBTYP: SALES DOC CATEGORY
AUART: SALES DOC TYPE
VKORG: SALES ORG
KUNNR: CUST NO
VBAP: SALES DOC ITEM TABLE
VBELN: SALES DOC NO
POSNR: ITEM NO
MATNR: MATERIAL NO
ZMENG: QUALITY
NETWR: NET VALUE
BKPF: ACCOUNTING DOC HEADER
BUKRS: COCODE
BELNR: ACCOUNTING DOC NO
GJAHR: FINANCIAL YEAR
BLART: DOC TYPE
BUDAT: POSTING DATE
BSEG: ACCOUNTING DOC ITEM (SEGMENT)
BUKRS: COCODE
BELNR: ACCOUNTONG DOC NO
GJAHR: FINCIAL YEAR

________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
105
BUZEI: ITEM NO
LIKP: DEL DOC HEADER
VBELN: DEL DOC NO
LIPS: DEL DOC ITEM
VBELN: DEL DOC NO
POSNR: ITEM
VBRK: BILLING HEADER
VBELN: BILLING DOC NO
VBRP: BILLING DOC ITEM
VBELN: BILLING DOC NO
POSNR: ITEM NO
Bank tables start with B, say "BKNF , BKPF".

Customer tables start with K , say "KNA1,KONV".
Material tables start with M, say "MARA , MAKT , MARC".
Master data tables start with T, say "T001, T001W".
Purchasing tables start with E, say "EKKO, EKPO"
Sales table start with V, say "VBAK,VBAP".
Vendor tables start with L, say "LFA1".
Six important FI tables.
They contain an I if it is an open item.

They contain an A if it is a closed item.
They contain an S if a GL account say "BSIS , BSAS".
Important table names of Billing, Delivery, Sales and Purchasing.
Each table had a K if it is a header data, say "VBAK, LIKP, VBRK, EKKO".
Each table had a P if it is an item data, say "VBAP, LIPS , VBRP , EKPO".
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
106
sno field name description
1. VBELN VBELN_VA(CHAR 10) Sales Document No

2. ERDAT ERDAT (DATS 8) Date on Which Record Was Created
3. ERZET ERZET (TIMS 6) Entry time
4. ANGDT ANGDT_V (DATS 8) Quotation/Inquiry is valid from
5. AUDAT AUDAT (DATS 8) DOCUMENT DATE
6. AUART AUART (CHAR 4) SALES DOCUMENT TYPE
7. NETWR NETWR_AK (CURR 15,2) Net Value of the Sales Order in doc
8. WAERK WAERK (CUKY 5) SD Document Currency
9. VKORG VKORG (CHAR 4) Sales Organization
10. VTWEG VTWEG (CHAR 2) Distribution Channel
11. SPART SPART (CHAR 2) Division
12. VKGRP VKGRP (CHAR 4) Sales Group
13. VKBUR VKBUR (CHAR 4) Sales Office
14. GSBER GSBER (CHAR 4) BUSINESS AREA
15. VSBED VSBED (CHAR 2) Shipping Conditions
16. KUNNR KUNNR (CHAR 10) CUSTOMER (SOLD TO PARTY)
17. KOSTL KOSTL (CHAR 10) cost center
18. KOKRS KOKRS (CHAR 4) controlling area
19. KKBER KKBER (CHAR 4) credit control area
20. AUFNR AUFNR (CHAR 12) order no
21. POSNR POSNR_VA (numc 6) Sales Document Item
22. MATNR MATNR (CHAR 18) material no
23. MATKL MATKL (CHAR 10) material grp
24. PSTYV PSTYV (CHAR 4) Sales document item category
25. POSAR POSAR (CHAR 1) Item type
26. MEINS MEINS (unit 3) Base Unit of Measure
27. WERKS WERKS (CHAR 4) plant
28. LGORT LGORT (CHAR 4) storage location
29. VSTEL VSTEL (CHAR 4) shipping point
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
107
TYPES OF LOADS:
Consider that transaction system (ECC) have 100 records & we moved data from ECC to
BW/BI using an Info package (full load). In ECC we have 100 records. After loading data to
BW, Now 100 records are available in BW also.
Again 10 new records are getting posted in ECC So we should move that new records to
BW also.
If we run that Info package again entire 110 records available in ECC will be again moved
to BW which we don't want. As we already have moved the previous 100 records, We want
to move only new records to BW, For this we use a delta mechanism.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
108
We initialize a delta queue in the source system. All the new records will be moved to target
system from this delta queue.
DELTA MECHANISM:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
109
In the scheduler screen under update tab we have update mode we find the following
options:
Full update (F)
Delta update (D)
Initialize Delta Process (Under this we have ) (C)
1. Initialization with data transfer
2. Initialize without data transfer
3. Early Delta Initialization
We can select Full update, Initialization or Delta Update.
We can also check this in the RSA3. If you say 'F' in update mode of RSA3, it means full
update which is same as InfoPackage full update. If you select 'C' in RSA3, it means
Initilization in InfoPackage and 'D' in RSA3 means Delta update in InfoPackage
Full Update: When we run the using Full Upload, what ever data is there in source
everything will be pulled to BW. If we use this, we can't run the Delta. If you want to run the
Delta further, we need to run the Init without Data then next time onwards it will allow you
to run the Delta upload.
A full update requests all data that corresponds to the selection criteria we can determined
in the scheduler. In a certain period of time specified in the scheduler, 100,000 data
records are accumulated. With a full update, all 100 000 data records are requested.
Using the Scheduler menu, we can indicate a request with full-update mode as c. This
request can be updated into every data target, even if the data target already contains data
from an initialization run or delta for this DataSource / source system combination, and has
overlapping selection criteria.
Using the full repair request to reload the data into the Data Store object after selectively
deleting data from the DataStore object can result in inconsistencies in the data target.
Updating this request can lead to duplicate data records in the data record when the repair
request selections do not agree with the selections from selectively deleting from the
DataStore object.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
110
Delta Update
 A delta update only requests data which has appeared since the last delta.
Before you can request a delta update, you must first initialize the delta process.
A delta update is only possible for loading from SAP source systems.
If a delta fails (status ’red’ in the monitor) or the overall status of the delta request has
been set to red manually, the next data request will be performed in repeat mode.
Repeat request extracts the incorrect or incompletely loaded data from the failed delta
request, along with any new data since the original request. A repeat can only be
requested in the dialog.
If data from the failed delta request has already been updated to the data targets, delete
the data from the data targets affected. If you cannot delete the data from the data targets,
duplicate data records may be produced when the repeat request is performed.
Delta type is one of the key property for SAP Data Source. there are four types of delta
types. F, A, D, E
F: Flat File Provides Delta
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
111
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
112
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
113
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
114
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
115
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
116
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
117
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
118
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
119
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
120
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
121
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
122
A: Use ALE Change log delta
D: Application determines the delta Ex: LO, FI-AR/AP
E: Extractor determines the delta Ex:- LIS, CO-PA, CUBE
We can know the delta properties from ROOSOURCE table in the source system .
Initialization (Init) of the Delta Process:
Init is nothing with Full upload + Delta Enables. Once you run this it will fetch entire records
from the Source, delta will be automatically enables, so next time onwards only delta will be
coming to BW.
To request deltas, you need to have initialized the delta process.
For selection criteria that do not overlap, several initialization criteria are possible for
initializing the delta process when scheduling InfoPackages for data from an SAP system.
This gives you the option of loading the relevant data for the delta process, step by step
into the Business Informa tion Warehouse.
A delta requested after several initializations, contains the super set of all the successful
initial selections as a selection condition. This selection condition can then no longer be
changed for the delta.
The selections for initialization are made in the scheduler of Infopackage on the Select
Data tab page.
/You can display all initializations for a DataSource in the scheduler by choosing Scheduler
à Initialization Selection for Source System.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
123
You can see whether an initialization selection has been executed and what the status of
the initialization request is. From this dialog box, you can also transfer initialization
selections into the scheduler, and delete selected initializations again.
Choosing the pushbutton Initialization Request Status brings you to the monitor, where you
can check the data request.
Delta initialization can only be simulated for DataSources from SAP source systems if the
DataSource supports this.
Generic DataSources, for which you have set a generic delta, also support the simulation of
delta initialization.
The option of simulating delta initialization is generally offered for loading processes from
other source systems (for example, file or non-SAP systems).
Initialize Delta Process
To get the delta records, one must initialize the delta process. While initializing the delta
process, the system will generate a flag: Initialize option for the source system in
(scheduler menu of info package) BI and BW delta queue per the data source in the source
system (RSA7). This enables the time stamp mechanism.
Initialize with data transfer
If we select this option, It extracts the init data from source system to BI system and allows
delta functionality.
Steps for initialize with data transfer

Lock the users in the source system
Delete the contents of the setup tables for the specific application component in source
system(T code: LBWG).
Fill the setup tables (SBIW or OLI*BW, use 1,2,3...in place of * according to the
application ).
Run the info package with initialize with data transfer.
unlock the users in the system
Note: This is very time consuming process, because we need to lock the users until data
reaches to the BI system. This effects the client business.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
124
Initialize without data transfer
In some cases, init is successful but someone has deleted the init flag. In order to set the
flag again to perform the delta load without disturbing the data, we execute IP with this
option.
Steps for initialize without data transfer
Lock the users in the source system

Delete the setup tables content for the specific application component.
Fill the setup tables
Run the IP with the option: Initialize without data transfer.
Unlock the users in the source system
Load data to BI system using repair full request info package
Note: In this method, after data is loaded to setup tables we can unlock the users in source
system. this is better option than initialize with data transfer option.
Early Delta Initialization
In this option, we can do the delta initialization before filling the setup tables.So that users
can post the documents when we are filling the setup tables.We will get the posted records
in the next delta run
With early delta initialization, we have the option of writing the data into the delta queue or
into the delta tables for the application during the initialization request in the source system.
This means that we are able to execute the initialization of the delta process (the init
request), without having to stop the updating of data in the source system.
Extractors that support early delta initialization were delivered with Plug-Ins as of Plug-In (-
A) 2002.1 We cannot run an initialization simulation together with an early delta initialization
.
Steps for early delta initialization

Run the Info package with early delta initialization option.This will enable the BW delta
queue and setup the time stamp for delta in the source system.
Delete the setup tables for the application component
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
125
Fill the setup tables

Load the setup table data using repair full request (scheduler menu option of info package)
info package
LO DATA EXTRACTION:
IF WE WANT WORK WITH LO DATA SOURCE EX: 2LIS_11_VAHDR

In LO every DS is pre fixed with 2LIS
11: Application number (sales)
VA: Event
HDR: Level of information
LO Events
Event VA means creating, changing or deleting orders.
Event VB means creating, changing or deleting quotations.
Event VC means creating, changing or deleting deliveries.
Event VD means creating, changing or deleting billing documents.
Example
VA01 : Create sales order
VA02 : Change sales order

________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
126
VA03: Display sales order
To get all details relevant to datasource, we can check the table ROOSOURCE
DELTA UPDATE MODES (METHODS):
Unserialized V3 Update
The extraction data of the application being viewed is written to the Update
Queue with anV3 update module and is kept there until the data is read with
an update collection run and processed. With this update mode, the extraction
data of the application in question continues to be written to the update tables
using a V3 update module and is retained there until the data is read and
processed by a collective update run.
Note: In this mode, the delta records may not arrive in the same order in the
BW as they were generated in the OLTP system. In particular, this can cause
problems in the BW when using DSO objects.
The method “Unserialized V3 Update” does not ensure serialization of the
document data. Update to the DataStore objects is not recommended if
serialization is desired.
When to use this?
Due to the design of the data targets in BW and for the particular application in
question, it is irrelevant whether or not the extraction data is transferred to BW
in exactly the same sequence in which the data was generated in R/3.
.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
127
Queued Delta
The extraction data from the concerned application is collected in an
Extraction Queue. Then the data will be transferred to Delta queue, in a
similar manner to the V3 update, with an update Collections run. With this
update mode, the extraction data for the affected application is compiled in an
extraction queue (instead of in the update data) and can be transferred to the
BW delta queues by an update collective run, as previously executed during
the V3 update. Up to 10,000 delta extractions of documents to an LUW in the
BW delta queues are cumulated in this way per DataSource, depending on
the application.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
128
Note: If we use this method, it is also necessary to schedule a job to regularly

transfer the data to the BW delta queues ("update collective run"). However,
we should note that reports delivered using the logistics extract structures
customizing cockpit are used during this scheduling.
When to use this method?

More than 10,000 document changes (creating, changing or deleting a
documents) are performed each day for the application in question.
• LUW: LUW stands of Logical Unit of Work. When we create a new
document it forms New image ‘N’ and whenever there is a change in the
existing document it forms before image ‘X’ and after Image ‘ ‘ and these
after and before images together constitute one LUW.
Table TRFCQOUT and ARFCSSTATE:

________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
129
Status READ means that the record was read once either in a delta request or in a
repetition of the delta request. However, this does not mean that the record has
successfully reached the BW yet.
The status READY in the TRFCQOUT and RECORDED in the ARFCSSTATE means that
the record has been written into the DeltaQueue and will be loaded into the BW with the
next delta request or a repetition of a delta. In any case only the statuses READ, READY
and RECORDED in both tables are considered to be valid. The status EXECUTED in
TRFCQOUT can occur temporarily. It is set before starting a DeltaExtraction for all
records with status READ present at that time. The records with status EXECUTED are
usually deleted from the queue in packages within a delta request directly after setting the
status before extracting a new delta. If we see such records, it means that either a
process which is confirming and deleting records which have been loaded into the BW is
successfully running at the moment, or, if the records remain in the table for a longer
period of time with status EXECUTED, it is likely that there are problems with deleting the
records which have already been successfully been loaded into the BW. In this state, no
more deltas are loaded into the BW. Every other status is an indicator for an error or an
inconsistency.
The value 'U' in field 'NOSEND' of table TRFCQOUT is discomforting.
Update Method (ECC OR R/3 RELATED) :
Synchronous update (V1 update)

Statistics updates is carried out oat the same time as the document update in
the application table, means whenever we create a transaction in R/3, then
the entries get into the R/3 table and this takes place in v1 update.
Asynchronous update (V2 update)
Document update and the statistics update take place in different tasks. V2
update starts a few seconds after V1 update and this update the values get
into statistical tables from where we do the extraction into BW.
V1 and V2 updates do not require any scheduling activity.
Collective update (V3 update)
• V3 update uses delta queue technology is similar to the V2 update. The
main differences is that V2 updates are always triggered by applications
while V3 update may be scheduled independently.
Difference between V1, V2, V3 updates
V1 Synchronous update - Used for LIVE tables, after the records get updated system will
send an acknowledgement. This degrades processing performance.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
130
V2 Asynchronous update – LUW's will be Updated in front end without any

acknowledgement.
V3 Asynchronous with background updating – Updating happens in Background.
We use this concept in LO Extraction update modes.
Direct delta update mode uses V2 update. Recommended only when less number of
records are there.
Queued delta is recommended for most of the cases and it will use V3 update. LUW’s will
be updated to Extractor queue (LBWQ) in the form of tokens (pointers). We need to run a
background job (V3 collective run) to push the data to delta queue from LIVE tables. All the
records will be moved at once so no problem with sequence.
Unserialized V3 update also uses V3 update, only recommended when sequence of data

is not important. DSO is not recommended as target when we use this update.
Direct Delta:
The extracted data is transferred directly to the delta queue with the
Document Posting.With this update mode, extraction data is transferred
directly to the BW delta queues every time a document is posted. In this way,
each document posted with delta extraction is converted to exactly one LUW
in the related BW delta queues.
If we are using this method, there is no need to schedule a job at regular
intervals to transfer the data to the BW delta queues.
Note: If we are using this update mode, note that we cannot post any
documents during delta initialization in an application from the start of the
recompilation run in the OLTP until all delta init requests have been
successfully updated in BW. Otherwise, data from documents posted in the
meantime will be lost.
When we can use this?
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
131
A maximum of 10,000 document changes (creating, changing or deleting

documents) are occrued between two delta extractions for the application. A
larger number of LUWs in the BW delta queue can result in terminations
during extraction.
Tables for update methods

The update methods are stored in the new customizing table
TMCEXUPD: LO Data Extraction: Update Control of Applications
The field MCAPP denotes application and Update Mode gives details on
update mode
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
132
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
133
• SOME DS’S SUPPORTS DELTAS, & SOME OTHER DS’S DOES NOT SUPPORT
DELTAS.
• IN REAL TIME WE WILL EXTRACT THE FROM R/3 (ECC) TO PSA(DS) à PSA à
DSO à IC . HERE WE CAN DSO AS STAGING DSO. FROM THIS DSO WE CAN
NOT GENATATE THE REPORT.
HOW TO FIND WHETHER THE DS IS DELTA CAPABLE OR NOT?
TO FIND DELTA PROCESS FOR DS 2LIS_11_VAHDR
T.CODE SE11: DB TABLE: ROOSOURCE à DISPLAY à CONTENTS à DS :

2LIS_11_VAHDR à EXCUTE
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
134
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
135
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
136
NOW TAKE FI DS
DS : 0FI_AP_04
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
137
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
138
SETUP TABLE: EXTRACT STRUCTURE (ES) + SETUP

If the DS name is 2LIS_11_VAOHDR
Then ES name is MC11VA0HDR
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
139
MC:
11: Application number
VA: Event
0: Hierarchy
HDR: Level
T. CODE FOR FILLING THE SET UP TABLES: OLI*BW
APPLICATION T.CODE
------------------------------------------------------------
PLANT MAINTAINANCE : OLIIBW
MATERAIL MOVEMENTS : OLI1BW
INVENTORY : OI2BW
PURCHASING : OLI3BW
PRODUCTION : OLI4BW
SALES ORDER : OLI7BW
DELIVERY : OLI8BW
BILLING : OLI9BW
INVOICE VERIFICATION : OLIZBW
Why we delete the setup tables (LBWG) & fill them (OLI*BW)?
Initially we don't delete the setup tables but when there is a change in extract structure we
will delete setup table. WheN ever we are changing the extract structure there are some
newly added fields in that which are not there before & same may be some unwanted
fields. So to get the required data ( i.e.; the data which is required is taken and to avoid
redundancy) first we delete & then we will fill the setup tables.
• Statistical Setup: Statistical Setup is a program, which is specific to

Application Component. Whenever we run this program it extracts all the
data from database table and put into the Setup Table.
Activating update,Controlling update:
Activating update:By Setting as active, data is written into extract structures

both online as well as during completion of setup tables or restructure table or
LO initialization tables. Depending on the update mode a job has to be
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
140
scheduled with which the updated data is transferred in the background into
the central delta management (Delta Queue).
Controlling update:This talks about the delta update mode we are using and
how do we control the data load based on the volume of data. LO Cockpit
supports 4 types of update modes ( delta modes):Serialized V3 update,Direct
Delta,Queued Delta,Unserialized V3 update.
MM DATA SOURCES:
MM is divided into 2 sections
1. Purchasing
2. Inventory
PURCHASING:
INVENTORY:
The data load process in Inventory data sources is different from other scenarios. If
we miss even one step during loading, we may get
wrong entries.
In Inventory management, the most important cube to load data to is 0IC_C03. Here
we load data from three data sources namely 2LIS_03_BX, 2LIS_03_BF and
2LIS_03_UM.
• 2LIS_03_BX: This structure is used to extract the stock data from MM Inventory
Management for initialization to a BW system.
• 2LIS_03_BF: This structure is used to extract the material movement data from MM
Inventory Management (MM-IM) consistently to a BW system.
• 2LIS_03_UM: This structure is used to extract the revaluation data from MM
Inventory Management (MM-IM) consistently to a BW system.
INVENTORY MANAGEMENT
Initial setup from R/3 :

1. T. CODE: SBIW
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
141
Define industry sector as standard (check the standard mark)
Go to T. CODE BF11 & Click the check mark ND1 (New Dimension Integration,
BW).
2. Follow the steps to load data into an inventory cube

Ensure Cube contents are deleted
3. In R/3 go to T- code LBWG and delete contents of set-up table.

Choose the correct application area 03
4. Ensure all other users except self and ALEREMOTE or BW RFC users are locked
out.
(We need an outage time in R/3 when we are loading data from R/3)
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
142
5. Activate the extract structure MC03BF0 for the corresponding DataSources

2LIS_03_BX/2LIS_03_BF in the LO cockpit (transaction code in R/3: LBWE) before
initializing the opening balance .
Run T-Code MCNB to set - up stocks.
DataSource: - 2LIS_03_BX, all materials including non-valuated stock
Table Name: MC03BX0SETUP

6. Load the set - up table with history data if needed.
· T-Code OLI1BW for Material Movements

· T-Code OLIZBW for Revaluations
7. From BW load initialization for 2LIS_03_BX to set the initial stock. Compress this load
with a marker update
7. Run an initialization without data transfer from BW for DataSource 2LIS_03_BF and
2LIS_03_UM
8. Load the historical data as full updates for 2LIS_03_BF and 2LIS_03_UM into the cube.
Compress these two loads without a marker update.
9. Make sure that, Job control has already been set - up in R/3.
Deltas can now be loaded and compressed with a marker update
STEP BY STEP Guide for Inventory Management:-

T-code – SBIW
Settings: Logistics -> Inventory Controlling -> Determine Industry Sector
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
143
In T-code – BF11 Checking the Following – Application – BW and NDI - Mandatory
Stock Initialization: Tcode – MCNB
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
144
Note – Important - Select: - All Stocks including (Non-Valuated stock)
RSA 3 – Checking for 2LIS_03_BX
RSA3 MAT: CUTTER, BUDAT: 29.09.2007
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
145
R/3 Dev T-code – MMBE for confirming the Unrestricted, Quality Inspected and
Reserved Stock
Replicate Metadata in BW
InfoCube in BW:- Material Stock/Movements –> 0IC_C03
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
146
Data source:-
Info package for bringing data into PSA
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
147
Transformation for 2LIS_03_BX
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
148
Data Transfer Process:- 2LIS_03_BX
For BX Update – after DTP go to Collapse - No TICK in No marker Updat e
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
149
Compression of Historical Transaction Data Records
If we have selected the No Marker Updating indicator, during the compression no

markers are adjusted. This function is used to make changes to non-cumulative that have
yet to be initialized visible at a later point in time. When loading and compressing
historical transaction data records, note the following:
 Before compression, InfoCubes into which historical transaction data records were
loaded, show potentially incorrect results. These inconsistencies are resolved
during the compression process.
 After historical transaction data records are loaded into an InfoCube, the
corresponding aggregates contain incorrect data. All incorrect aggregates are
therefore deactivated and rebuilt during a compression run. For performance
reasons, we recommend deactivating aggregates before a compression run with
historical data, and rebuilding them after the compression run.
 Handling non-cumulative initializations as historical transaction data is not permitted

and results in the termination of the compression run.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
150
No update of the non-cumulative marker

 If this option is switched on, the non-cumulative marker is not updated when loading
non-cumulative value changes.
 We can use this option to load past non-cumulative value changes into an InfoCube
after a successful initialization with the current non-cumulative.
 In this instance, we have to carry out a summarization with this option before we can
report from this data.
 The InfoCube must be a non-cumulative InfoCube. If not, this flag is ignored.
Summary – BF with Historical data should have No Marker Update Tick Mark
because it shouldn’t get added with Initial Stock (BX data load)
02LIS_03_BF
Logistics - > Application-Specific Setup of Statistical Data -> Inventory Management
- Perform Setup. ( T-Code OLI1BW for Material Movements)
Execute in Background
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
151
Checking for Extracted Data – RSA3
For Set Up Log in – T-Code NPRT
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
152
Path: - Logistics - > Initialization - > LIS Setup Log
Replicate Metadata in BW
Same Info provider - InfoCube in BW:- Material Stock/Movements – >: 0IC_C03
Info package for bringing data into PSA –> 2LIS_03_BF
Transformation for 2LIS_03_BX
Data Transfer Process:- 2LIS_03_BF
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
153
For 2LIS_03_BF – after DTP into Info Provider we have to compress the cube
Summary – BF with Historical data should have No Marker Update Tick Mark
because it shouldn’t get added with Initial Stock (BX data load)
2LIS_03_UM
Logistics - > Application-Specific Setup of Statistical Data -> Inventory Management

- Perform Setup. (T-Code OLIZBW for Invoice Verification /Revaluation)
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
154
Same Info provider - InfoCube in BW: - Material Stock/Movements – 0IC_C03
Data source:-
Info package for bringing data into PSA –> 2LIS_03_UM
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
155
Transformation for 2LIS_03_UM
IPACK LEVEL SELECT GENERATE INIT(BX)

IPACK LEVEL INITDELTA(BF,UM)
BX WITH MARKER
BF WITHOUT MARKER
UM WITHOUT MARKER
DELTALOAD
BX Wont Support Delta.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
156
BF WITH MARKER
UM WITH MARKER
SD DS:
First we will check the steps in ECC system followed by steps in BI system. Assume
that you need to load cube 0SD_C05. For this you need two datasource
2LIS_11_VAHDR and 2LIS_11_VAITM. As the name depicts, it is of application
component 11 and it belongs to VA (Sales) and HDR, ITM represents header and Item
data.
Steps in ECC system side
Activate datasource
Go to.RSA5 & activate datasource
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
157
The datasource will be activated from D version to A version. We can check this in table
ROOSOURCE.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
158
To check whether the source supports delta: check in table RODELTAM
We can see that DELTA is ABR, It means, this datasource supports delta and the Type
is ABR (After, before, reverse image). This is compatible with DSO and cube.
Once datasource is activated, for any post processing actions like enhancements etc
.we can check in RSA6
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
159
Activate extract structure

Before filling setup table you need to activate the extract structure.
LBWE
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
160
We can see that the extract structure is inactive and the events are those will is used to
populate the data. You can know more about events in my previous article versions.
The update is showing as inactive, now click on that ‘inactive’.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
161
Now schedule the V3 job
Filling setup table
Once the activation is done, we can fill setup table from SBIW.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
162
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
163
This invokes the report as shown below; the same screen can be called by transaction
OLI7BW
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
164
Now provide the name of run and give the date in future. Selections can be provided.
Execute
Checking Extracted Data
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
165
Since the extract table is cluster table, it is meaningless to see in data dictionary, so we
have some other method to read data from extract structure.
.RSA3 Give the datasource name to check the data that is extracted. Execute
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
166
Select Display list
Double click on record
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
167
So 11 records are extracted.
Steps in BI side.
Replicate the datasource from source system and follow the dataloading process.
Upload the data from setup table
Need to migrate this datasource, you can see datasource with square, this is 3.x
datasource icon.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
168
Do this for both the datasource, now you can see the datasource like this
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
169
Create an Infopackage to load the data from setup table
For BI the processing of Infopackage is by default only to PSA
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
170
The update is full upload; this will fetch data from setup table. For more info read my
previous articles
Start the extraction
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
171
Once you get this, go to monitor, check for data in PSA
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
172
Loading to cube
To load data to cube you need to create a DTP from datasource to cube.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
173
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
174
Similarly load the 2LIS_11_VAITM datasource from Infopackage
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
175
Now create transformation for that too
Create a DTP for each datasource
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
176
Activate and start the execution
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
177
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
178
Similarly load for 2LIS_11_VAITM also
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
179
Now you can check the contents of the cube context menu ‘Manage’ from cube
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
180
Delta Update :Check RSA7 in source system, you will not find entries for this datasource
as of now.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
181
Now from Infopackage do and ‘Init without data transfer’, this will initialize the delta.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
182
Similarly do for 2LIS_11_VAITM Infopackage also.
Now check RSA7 in source system
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
183
Now create a Delta Infopackage for both the datasource and schedule it. You can group all
these things in a process chain and monitor the loads daily.
Now any change in the ECC system will trigger a delta record which will be picked by the
delta Infopackage and from there the DTP will send the delta data to cube.
This completes the LO extraction implementation methodology, this is very short

overview, do read all the previous articles to know in detail about each process.
LO EXTRACTION (interview purpose):

Depending on the client report requirement, first we need to check which data source suits
for report requirement.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
184
Check whether the DS is in active version / modified version. If it is in M version goto RSA5
& click on activate DS. Now goto RSA6 & Check DS has been transferred or not .
If the DS is already in active version then we have check whether the DS is already
extracting data in to BI.
If the Ds is extracting the data we need to check the data existence in setup tables &
extractor queue (LBWQ), Update tables (SM13), Delta Queue (RSA7). If data exists in any
of these T codes we have to decide whether we need the data in BI or not. If we need data
we will extract it by LO Extraction. If we do not want , we will delete the data.
We use se11 to check the data in setup tables.
For every Es one & only one setup table is generated whose technical name is ES name +
setup.
EX: If ES name is MC11VAOHDR then setup table name is MC11VAOHDR + setup.
Data flow from ECC to BI.
We have to generate the Es by selecting fields from CS in LBWE.
Generate DS & select the field selections, hide fields, cancellation fields that we want.
Replicate Ds into Bi.
Business content (BCT): BCT automatically proposes the transformation. We do not have
to do anything manually.
Application proposal: proposals are done automatically, but some objects will be missing
which we need to assign.
Others: here we have to create from scratch.
We will model data targets (ic, dso).
Activte ds (es).
Filling the setup table for the first time loading. Infilling setup tables we can select between
full load, delta initialization loads.
For filling setup tables tcode : oli*bw
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
185
First we have to decide whether we want delta loads to be performed in the future. If we
want to do delta loads then we have to for initialization process or else do full load.
When we perform setup tables extraction, since setup tables are cluster tables, we cannot
see the data in setup tables. So we have to go for extractor checker (rsa3) to see the setup
table data (full / delta initialization)
Create ip & select full or delta initialization in update tab & schedule it.
Delete setup tables data (lbwg)
Now we will do delta loads
Delta load data differs with various delta update methods.
We have three delta update methods
If we select queue delta update method then data moves to extractor queue (lbwq). Then
run collective update (v3) to move the data from lbwq to delta queue (rsa7). Then schedule
the data using the ip by selecting delta load in the update tab.
If we select un serialized v3 delta update method then data moves to update tables
(sm13). Then run collective update (v3) to move the data from sm13 to delta queue (rsa7).
Then schedule the data using the ip by selecting delta load in the update tab.
If we select direct delta the delta data moves to rs7 directly. Then schedule the data using
the ip by selecting delta load in the update tab.
FI extraction:
FI Module deals with accounting and financial needs of an organization.

Financial Accounting is divided into the following sub-modules:

 Accounts Receivables
 Accounts Payable
 Asset Accounting
 Bank Accounting
 Consolidation
 Funds Management
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
186
 General Ledger
 Special Purpose Ledger
 Travel Management …etc
We can extract the financial data at totals level / line item level.
In general, we will use R/3 line item tables as the data source for extracting the data to
allow drill down capability from summarized data to line-item details.
Financial Accounting data can be extracted directly from the tables.
Depending on the business requirement we can use either FI-SL or standard BW content
extractors (FI-AR, FI-AP, and FI-GL) to fetch FI data.

Note: FI-SL will be discussed under which explains about Application specific customer
generated extractors

FI-AR, FI-AP, and FI-GL:
General Ledger: All accounting postings will be recorded in General Ledger. These
postings are real time to provide up-to-date visibility of the financial accounts.
Account Receivable (AR): Accounts Receivables record all account postings generated
as a result of Customer sales activity. These postings are automatically updated in the
General Ledger
Accounts Payable (AP): Accounts Payables record all account postings generated as a
result of Vendor purchasing activity. Automatic postings are generated in the General
Ledger as well.

Standard FI data sources:
0FI_GL_4 (G/L Accounts- line items): Takes the data from the FI document tables
(BKPF/BSEG) that are relevant to general ledger accounting (compare table BSIS).
0FI_AP_4 (AP-line items): Selections are made from tables BSID/BSAD (AP)
0FI_AR_4 (AR- line items): Selections are made from tables BSIK/BSAK (AR)
How the data extraction happens?
In FI extraction 0FI_AR_4 and 0FI_AP_4 are linked with 0FI_GL_4 in order to maintain
consistent data transfer from OLTP system (it is called coupled data extraction
0FI_GL_4 writes the entries into the time stamp table BWOM2_TIMEST in the SAP R/3
System with a new upper limit for the time stamp selection.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
187
And now, 0FI_AP_4 and 0FI_AR_4 will copy this new upper limit for the time stamp
selection during the next data extraction in the SAP R/3 System. This ensures the proper
synchronization of accounts payable and accounts receivable accounting with respect to
G/L accounting.
Full load: Not a valid choice because of large volumes of detailed R/3 transaction
data.

Delta load:
Note: Here the delta identification process works differently for new financial
records and for changed financial records.
New Financial accounting line items which are posted in SAP R/3 system will be identified
by the extractor using the time stamp in the document header (Table BKPF-(field) CPUDT).
By scheduling an initialization IP all the historical data can be loaded into BW from the
application tables and it also sets "X" indicator in field LAST_TS (Flag: 'X' = Last time
stamp interval of the delta extraction).That means after the last delta, initialization was
done.

OLTPSOURCE AEDAT/AETIM UPD DATE_LOW DATE_HIGH LAST_TS
0FI_GL_4 16 May 2007/20:15 Init 01 Jan 1990 15 May 2007
0FI_GL_4 24 May 2007/16:59 delta 16 May 2007 23 May 2007
0FI_GL_4 21 June 2007/18:12 delta 15 June 2007 20 June 2007 X
0FI_AP_4 18 May2007/21:23 Init 01 Jan 1990 15 May 2007
After this, daily delta loads can be carried out depending on timestamp by scheduling delta
info packages. During the delta load , the SAP R/3 system logs two time stamps that delimit
a selection interval for a Data Source in table BWOM2_TIMEST(fields TS_LOW and
TS_HIGH).
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
188
In case of changed FI documents, selections will be based on tables:

BWFI_AEDAT and (timestamp table) BWOM2_TIMEST.
Delta extraction using delta queue method can also be possible incase if we want,
 Serialization of the records
 To distribute delta records to multiple BW systems.

FI -Delta Mode:
A time stamp on the line items serves to identify the status of the delta. Time stamp
intervals that have already been read are then stored in a time stamp table
(BWOM2_TIMEST).
(Info object 0Recordmode plays vital role deciding delta's .Check the field "delta "in
ROOSOURCE /RODELTAM table to identify the image)
The Financial Accounting line items are extracted from the SAP R/3 system in their most
recent status (after-image delta method).
AIE: This delta method is not suitable for filling Info Cubes directly in the BW system. To
start with therefore, the line items must be loaded in the BW system in anDSO object that
identifies the changes made to individual characteristics and key figures within a delta data
record. Other data destinations (Info Cubes) can be provided with data from this DSO
object.
It uses delta type E(pull) means the delta data records are determined during the delta
update by the data source extractor, updated to the delta queue and passed on to BI
directly from there.:

________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
189
GENERIC DS (GDS):
A Generic datasource is created when no standard business content datasource is
available that meets client’s reporting requirements .
We can create GDS by using table, view, info set query & Function module (FM).
T. code : RSO2 (To create GDS)
We can create GDS in ways.
1. Transaction Data
2. Master data Attributes
3. Master data Text
If we creating GDS by using VIEW ES is automatically created. But in FM we have to

create ES explicitly.
SELECTION: What ever the fields we select here those fields will appear in BI side at
DATA SELECTION TAB of INFO PACKAGE.
HIDE: What ever the fields we select here those fields will not appear in BI side.
INVERSION: This option is available for Key Figures.
FIELD ONLY KNOWN IN CUSTOMER EXIT: It is used in enhancement of DS.
DELTA METHODS:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
190
There are 3 options.
1. CALDAY: We can run delta only once per day that to at the end of the clock to
minimize the missing of delta records.
2. NUMERIC POINTER: It is suitable When we are extracting from table which

supports only creation of new records, but not change of existing records.
3. TIME STAMP: By using this we can run delta multiple times per day but we need to
use safety lower limit & safety upper limit with minimum 5 minites.
We can see the delta in RSA7.
When we are setting up the delta , we canset up two types of images.
1. New status for changed records
2. Additive delta.
LO COCKPIT: (Interview purpose)

Logistic Cockpit (LC) is the technique to extract logistics transaction data from R/3.
All the Data Sources belonging to logistics can be found in the LO Cockpit (Transaction
LBWE) grouped by their respective application areas.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
191
The Data Sources for logistics are delivered by SAP as a part of its standard business
content in the SAP ECC 6.0 system and has the following naming convention. These are in
D version. A logistics transaction DataSource is named as follows:
2LIS_<Application>_<Event><Suffix> where,
 Every LO Data Source starts with 2LIS.

 Application is specified by a two digit number that specifies the application relating to
a set of events in a process. e.g. application 11 refers to SD sales.
 Event specifies the transaction that provides the data for the application specified,
and is optional in the naming convention. e.g. event VA refers to creating, changing or
deleting sales orders. (Verkauf Auftrag stands for sales order in German).
 Suffix specifies the details of information that is extracted. For e.g. ITM refers to item
data, HDR refers to header data, and SCL refers to schedule lines.
Up on activation of the business content Data Sources, all components like the extract
structure, extractor program etc. also gets activated in the system.
The extract structure can be customized to meet specific reporting requirements at a later
point of time and necessary user exits can also be made use of for achieving the same.
An extract structure generated will have the naming convention, MC <Application>

<Event>0 <Suffix>. Where, suffix is optional. Thus e.g. 2LIS_11_VAITM, sales order item,
will have the extract structure MC11VA0ITM.
Delta Initialization:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
192
 LO Data Sources use the concept of setup tables to carry out the initial data
extraction process.
 The presence of restructuring/setup tables prevents the BI extractors directly access
the frequently updated large logistics application tables and are only used for initialization
of data to BI.
 For loading data first time into the BI system, the setup tables have to be filled.
Delta Extraction:
 Once the initialization of the logistics transaction data Data Source is successfully
carried out, all subsequent new and changed records are extracted to the BI system using
the delta mechanism supported by the Data Source.
 The LO Data Sources support ABR delta mechanism which is both DSO and
InfoCube compatible. The ABR delta creates delta with after, before and reverse images
that are updated directly to the delta queue, which gets automatically generated after
successful delta initialization.
 The after image provides status after change, a before image gives status before the
change with a minus sign and a reverse image sends the record with a minus sign for the
deleted records.
 The type of delta provided by the LO Data Sources is a push delta, i.e. the delta data
records from the respective application are pushed to the delta queue before they are
extracted to BI as part of the delta update. The fact whether a delta is generated for a
document change is determined by the LO application. It is a very important aspect for the
logistic Data Sources as the program that updates the application tables (V1) for a
transaction triggers/pushes the data for information systems (V2), by means of an update
type, which can be a V1 or a V2 update.
 The delta queue for an LO Data Source is automatically generated after successful
initialization and can be viewed in transaction RSA7, or in transaction SMQ1 under name
MCEX<Application>.
Update Method
The following three update methods are available
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
193
Statistics updates is carried out at the same time as the document update in the application
table, means whenever we create a transaction in R/3, then the entries get into the R/3
table and this takes place in v1 update.
Document update and the statistics update take place in different tasks. V2 update starts a
few seconds after V1 update and this update the values get into statistical tables from
where we do the extraction into BW.
V1 and V2 updates do not require any scheduling activity.
V3 update uses delta queue technology is similar to the V2 update. The main differences is
that V2 updates are always triggered by applications while V3 update may be scheduled
independently.
Update modes
Direct Delta
Queued Delta
Direct Delta
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
194
 With this update mode, extraction data is transferred directly to the BW delta queues
with each document posting.
 Each document posted with delta extraction is converted to exactly one LUW in the
related BW delta queues.
 In this update mode no need to schedule a job at regular intervals (through LBWE
“Job control”) in order to transfer the data to the BW delta queues. Thus additional
monitoring of update data or extraction queue is not require.
 This update method is recommended only for customers with a low occurrence of
documents (a maximum of 10000 document changes - creating, changing or deleting -
between two delta extractions) for the relevant application.
Queued Delta
 With queued delta update mode, the extraction data is written in an extraction queue
and then that data can be transferred to the BW delta queues by extraction collective run.
 If we use this method, it will be necessary to schedule a job to regularly transfer the
data to the BW delta queues i.e extraction collective run.
 SAP recommends to schedule this job hourly during normal operation after
successful delta initialization, but there is no fixed rule: it depends from peculiarity of every
specific situation (business volume, reporting needs and so on).
 With this Unserialized V3 Update, the extraction data is written in an update table
and then that data can be transferred to the BW delta queues by V3 collective run.
Setup Table
 Setup table is a cluster table that is used to extract data from R/3 tables of same
application.
 The use of setup table is to store your data in them before updating to the target
system. Once you fill up the setup tables with the data, you need not go to the application
tables again and again which in turn will increase your system performance.
 LO extractor takes data from Setup Table while initialization and full upload.
 As Setup Tables are required only for full and init load we can delete the data after
loading in order to avoid duplicate data.
 We have to fill the setup tables in LO by using OLI*BW or also by going to SBIW à
Settings for Application à Specific Data Sources à Logistics à Managing Extract Structures
à Initialization à Filling in Setup tables à Application specific setup table of statistical data.
 We can delete the setup tables also by using LBWG code. You can also delete
setup tables application wise by going to SBIW -> Settings for Application Specific Data
Sources -> Logistics -> Managing Extract Structures -> Initialization -> Delete the
Contents of the Setup Table.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
195
 Technical Name of Setup table is ExtractStructure-setup, for example suppose Data

source name 2LIS_11_VAHDR. And extract structure name is MC11VA0HDR then setup
table name will be MC11VA0HDRSETUP.
LUW
 LUW stands of Logical Unit of Work. When we create a new document it forms New
image ‘N’ and whenever there is a change in the existing document it forms before image
‘X’ and after Image ‘ ‘ and these after and before images together constitute one LUW.
Delta Queue (RSA7)
 Delta queue stores records that have been generated after last delta upload and not
yet to be sent to BW.
 Depending on the method selected, generated records will either come directly to
this delta queue or through extraction queue.
 Delta Queue (RSA7) Maintains 2 images one Delta image and the other Repeat
Delta. When we run the delta load in BW system it sends the Delta image and whenever
delta loads and we the repeat delta it sends the repeat delta records.
Statistical Setup
 Statistical Setup is a program, which is specific to Application Component.
Whenever we run this program it extracts all the data from database table and put into the
Setup Table.
REPEAT DELTA: We do a repeat delta when the original delta load fails or the delta
request gets deleted from the infoprovider.

In terms of repeat delta we don't have to do anything on the R3 side. As mentioned above
just follow the steps and rerun the delta infopackage for the repeat delta.
We have table ROOSPRMSC which stores the successful last delta request time stamp for
each data source(if it is delta enabled).
Whenever the delta IP got successful, the time stamp will get update in the table (it doesn't
bother about whether request is there in target or not). If the over all status of IP comes to
green, then time stamp will get updated to system table.
So when ever you have any failed delta request or if you want to load the previous delta
request again, follow the below steps.
1) Open the failed request or request we want to run again by going into manage tab of
target and click on monitor of request, then change the over all status to red.(Open the
delta IP in RSA1 --> on top click on monitor --> in left side we will get all requests).
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
196
Here system will prompt you message saying that" you have to perform repeat delta". Click
on "Repeat Delta"
2) Now goto target and make the request red and delete it.
Now run delta IP, it will pick earlier and present delta records.
Note: If we are already deleted the request from target, then open the request in RSRQ
and make the request to Red. This is the way to get the last delta records.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
197
LO EXTRACTION (interview purpose):

Depending on the client report requirement, first we need to check which data source suits
for report requirement.
Check whether the DS is in active version / modified version. If it is in M version goto RSA5
& click on activate DS. Now goto RSA6 & Check DS has been transferred or not .
If the DS is already in active version then we have check whether the DS is already
extracting data in to BI.
If the Ds is extracting the data we need to check the data existence in setup tables &
extractor queue (LBWQ), Update tables (SM13), Delta Queue (RSA7). If data exists in any
of these T codes we have to decide whether we need the data in BI or not. If we need data
we will extract it by LO Extraction. If we do not want , we will delete the data.
We use se11 to check the data in setup tables.
For every Es one & only one setup table is generated whose technical name is ES name +
setup.
EX: If ES name is MC11VAOHDR then setup table name is MC11VAOHDR + setup.
Data flow from ECC to BI.
We have to generate the Es by selecting fields from CS in LBWE.
Generate DS & select the field selections, hide fields, cancellation fields that we want.
Replicate Ds into Bi.
Business content (BCT): BCT automatically proposes the transformation. We do not have
to do anything manually.
Application proposal: proposals are done automatically, but some objects will be missing
which we need to assign.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
198
Others: here we have to create from scratch.
We will model data targets (ic, dso).
Activte ds (es).
Filling the setup table for the first time loading. Infilling setup tables we can select between
full load, delta initialization loads.
For filling setup tables tcode : oli*bw
First we have to decide whether we want delta loads to be performed in the future. If we
want to do delta loads then we have to for initialization process or else do full load.
When we perform setup tables extraction, since setup tables are cluster tables, we cannot
see the data in setup tables. So we have to go for extractor checker (rsa3) to see the setup
table data (full / delta initialization)
Create ip & select full or delta initialization in update tab & schedule it.
Delete setup tables data (lbwg)
Now we will do delta loads
Delta load data differs with various delta update methods.
We have three delta update methods
If we select queue delta update method then data moves to extractor queue (lbwq). Then
run collective update (v3) to move the data from lbwq to delta queue (rsa7). Then schedule
the data using the ip by selecting delta load in the update tab.
If we select un serialized v3 delta update method then data moves to update tables
(sm13). Then run collective update (v3) to move the data from sm13 to delta queue (rsa7).
Then schedule the data using the ip by selecting delta load in the update tab.
If we select direct delta the delta data moves to rsa7 directly. Then schedule the data using
the ip by selecting delta load in the update tab.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
199
INDEX
INTRODUCTION
BEx COMPONENTS
BEx ANALYZER
BEx QUERY DEIGNER
BEx BROUSER
BEX WEB APPLICATION DESIGNER
CHARACTERISTIC PROPERTIES
KEY FIGURE PROPERTIES
QUERY PROPERTIES
RESTRICTION
FILTER
CALCULATED KEYFIGURE
NEW FORMULA
CONSTANT SELECTION
RESTRICTED KEY FIGURE
NEW SELECTION
STRUCTURE
CELL DEFINITION
CONDITION
EXCEPTION
RRI
VARIABLES
1. CHARACTERISTIC VALUE VARIABLE
2. TEXT VARIABLE
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
200
3. FORMULA VARIABLE
4. HIERARCHY VARIABLE
5. HIERARCHY NODE VARIABLE
PROCESSING TYPES:
1. USER ENTRY / DEFAULT VALUE
2. REPLACEMENT PATH
3. AUTHORIZATION
4. CUSTOMER EXIT
5. SAP EXIT
WAD
In BI , BEx is a reporting tool

BEx (Business Explorer]
It consists of 4 components
BEx Query Designer:
= To Design BEx Query (Question)

= Info Provider (Info Cube, ODS, Multiprovider, InfoSet, Master Data)
= Navigation ( How to design a Bex Query using Query Designer?)
= Query Execution Process
BEx Analyzer:
= Ms Excel + Add-On Components

= To Design BEx Workbooks (Formatted Excel Report)
= VB Macros
BEx WAD[Web Application Designer):
= To Design Web reports / Web templates by using Web Items

= Navigation
= Data Provider (Query / Query View)
BEx Query Designer:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
201
- Desigining Simple Query
- Characteristic Properties
- Key figure Properties
Query Properties
- Restriction
select f1 f2 f3 ...... from <table name> where <f11 eq "South ">
Conditions:
Restricted Key Figure

:
select f1 f2 (select qty where office = "hyd") as f3 from cube
Calculated Key figure:

New Selection:
New Formula:
Structures:
Cell Definetions:
Exceptions:
Other Options in the Query Designer:

----------------------------------------------
- Variables:
--------------
- To Parametrizating the query
- To MAke the query dynamic
- Types of Variables:
------------------------
- Characteristic Value Variable
- Text Variable
- Formula Variable
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
202
- Hierarchy Variable
- Hierarchy Node Variable
- Processing Types:
-----------------------
- User Entry / Default
- Replacement Path
- Customer Exit
- Authorization
- SAP Exit
- Case 1: Characteristic Value Variable with User Entry / Default

---------------------------------------------------------------------------
- Case 2: Characteristic Value Variable with Replacement Path

-------------------------------------------------------------------------
- When we want the Characteristic Value Variable to be replaced with the query result of
other query
- RRI [Report-to-Report] Interface:

-------------------------------------------
- RSBBS
- Case 3: Characteristic Value Variable with Authorization

-------------------------------------------------------------------
- When we want the Characteristic Value Variable to take in the values based on the
authorizations of the user.
- Steps:
----------
1. Enable the Info Object - KCISREG as "Authorization Relevant"
2. Create the Authorization Object by using the Info Object - KCISREG - [RSSM /
RSECADMIN]
3. Enable the Authorization Object on to Info Provider - KCI_CTD
4. Create Roles & Generate Profiles - PFCG
Info Area:ZIA_KCI
Info Cube:KCI_CTD
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
203
Query :*
5. Create User & Assign the roles - SU01
6. In the BEx Query Designer, Create Characteristic Value Variable with Authorization as
the processing type on the Info Object - KCISREG
- Case 4: Characteristic Value Variable with Customer Exit

-------------------------------------------------------------------
- RSR00001
- Example 1:
---------------
0CALDAY - Current Date
Steps:
--------
1. Create Characteristic Value Variable with Customer Exit as the processing type on
"0CALDAY" in the BEx query designer.
2. Implement the ABAP/4 code to populate values to the variable by using the
enhancement RSR00001.
2.1 Create a Project - CMOD
2.2 Assign the enhancement RSR00001 to the project - CMOD
2.3 Check the components - CMOD
2.4 Implement the ABAP/4 code within the component EXIT_SAPLRRS0_001 - CMOD
SIGN
OPT
LOW
HIGH
- Eample - 2:
---------------
I_STEP = 2
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
204
DATA : LVV_DATE LIKE SY-DATUM,

LVV_MONTH(6) TYPE N.
WHEN 'ZLV_602'.
CLEAR L_S_RANGE.
IF I_STEP = 2.
* Fetch the user entry value for the variable
* ZLV_601 from the Internal table I_T_VAR_RANMGE
READ TABLE I_T_VAR_RANGE INTO intern_range WITH KEY VNAM = 'ZLV_601'.
LVV_DATE = intern_range-LOW.
LVV_MONTH = LVV_DATE+0(6).
L_S_RANGE-SIGN = 'I'.
L_S_RANGE-OPT = 'EQ'.
L_S_RANGE-LOW = LVV_MONTH.
APPEND L_S_RANGE TO E_T_RANGE.
ENDIF.
- Examples to practice:
---------------------------
- MTD
- YTD
- CW
DATE_GET_WEEK
- Previous work day
- WTD
- CQ
The BEx suite consists of the following tools:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
205
 BEx Query Designer

 BEx Report Designer
 BEx Web Application Designer (WAD)
 BEx Web Analyzer (Web-based tool)
 BEx Analyzer (Excel-based tool)
BEx Analyzer (Business Explorer Analyzer): The BEx Analyzer is integrated with
Microsoft Excel and is accessible by installing the SAP Graphical User Interface (GUI) add-
on for BI. Data is embedded into Microsoft Excel workbooks providing users with drag-and-
drop capabilities to drill down and filter the data using SAP BI OLAP functions.
The tools that make up the BEx suite provide solutions for enterprise reporting, ad hoc
OLAP analysis, and dashboarding.
Bex QUERY DESIGNER:
We can analyze the dataset of the BI by defining queries for InfoProviders using the BEx
Query Designer . By selecting and combining InfoObjects (characteristics and key figures)
or reusable structures in a query, we can determine the way in which we navigate through
and evaluate the data in the selected InfoProvider.
It is one of the front ends to the SAP BI system. It provides flexible reporting and analytical
tools for the analysis of reports, consistent information to develop dashboard reporting, and
it supports much of the decision-making activities within a business. The Business Explorer
Analyzer offers querying, reporting, and analysis functions.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
206
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
207
The initial location of data used for querying is in the InfoProviders. We analyze the dataset
of the BI system by defining queries for InfoProviders in the Query Designer. By selecting
and combining InfoObjects (characteristics and key figures) or reusable structures in a
query., we determine the way in which we navigate through and evaluate the data in the
selected InfoProvider. Analyzing data on the basis of a relational database (OLAP
reporting) makes it possible to analyze several dimensions at the
same time (for example, time, customer, and product).
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
208
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
209
FIND: We can search by description and/or technical name using the appropriate
check box in the dialog box.
HISTORY: The History folder offers the most direct and easy access to queries,
InfoProviders, and workbooks we have been reviewing or using in the recent past.
This list of objects is collected based on our activities in the Open dialog box over a
period of time. To be able to use this functionality, wehave tot do some initial setup.
We need to activate the option for the BEx History to collect the information on the queries
and other objects we have used.
To do this, we have to go to ECC
Path to use to activate the History folder  SPRO  REF IMG 
SAP Customized Implementation Guide | SAP Net Weaver | Business Intelligence |
Settings for Reporting and Analysis | General Settings for Reporting and Analysis |
Activate Personalization in BEx.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
210
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
211
FAVORITES: By default a query will be saved to Favorites. If the query will be located only
in Favorites folder, it will not be available to anyone else, the Favorites folder gives you
additional time to analyze your query.
ROLES: We can also save the queries to Roles folder. The reason for doing so depends
on the strategy for saving and allowing access to our queries.
INFO AREA: The InfoAreas folder is the access point for all the queries available for review
and execution based on the InfoProvider to which they are attached. Therefore, if we are
searching for a specific query and we know the InfoProvider to which it is attached, this is
another avenue for us to research and/or execute the query.
OPEN: We can open workbooks or queries in BEx Analyzer. The Open tool has two
submenus, and two Open items appear on the BEx Analyzer menu.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
212
To open a query, choose Open | Query from the Analysis toolbar, or select BEx
Analyzer | Open Query from the menu bar. When we open a query, it is embedded
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
213
into the workbook you have currently defined as the default. The query is
automatically executed and the current state of the result is returned from the server.
Typically, a power user will open a query and work in design mode to customize it,
and then save the query to a workbook that the business user can use for analysis.
To open a workbook: Select Open Workbook from the Analysis toolbar or select BEx
Analyzer  Open Workbook from the menu bar. A workbook delivers the interface for our
query.
SAVE: We can save workbooks or views in BEx Analyzer, either under existing
names or with new names. The Save tool has three submenus, and three Save items
appear on the BEx Analyzer menu.
To save a workbook: Select Save  Save Workbook As from the Analysis toolbar, or
select BEx Analyzer  Save Workbook As from the menu bar.
To save a workbook with a new name, select Save  Save Workbook As from the
Analysis toolbar, or select BEx Analyzer  Save Workbook As from the menu bar.
.
NOTE To save a workbook to your local file system, choose File | Save or choose File |
Save As from the menu bar in Microsoft Excel.
Refresh/Pause Automatic Refresh: We can control the refresh status (to enable or
disable the request of current valid data from the server) with the Refresh function,
which is a toggle function.
To enable refreshing, requesting the current valid data from the server, choose Refresh
from the Analysis toolbar, or select BEx Analyzer  Refresh from the menu bar.
If you have already activated the Refresh function and you wish to pause automatic
refreshing of current valid data, choose Pause Automatic Refresh from the Analysis
toolbar, or select BEx Analyzer  Pause Automatic Refresh from the menu bar. This
allows you to navigate the query without having to wait for it to update with the
current data. The Pause Automatic Refresh state is recommended for performance
reasons. A query can only be refreshed if a connection exists between BEx Analyzer
and the BI system. When a query is refreshed, the data, format, rows, and column widths of
the analysis grid (in which the results display) automatically adjust to the updated query
data. You can adjust this display using the properties for the analysis grid.
NOTE: When you activate a Refresh operation, variables are not automatically processed
by default (in other words, you don’t get the chance to change variable values). You can
change this behavior so that you are always prompted to enter new variable values when
you activate Refresh by selecting Process Variables on Refresh in the properties for the
workbook.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
214
Change Variable Values : We can change the variable values associated with the
queries in our workbooks. When we initially refresh our workbook, all queries
embedded in it are processed. We use this function to change values for all variables
associated with queries in our workbook. All variables saved in any of the queries
must at that time be replaced by concrete values, which are then saved in a session
on the server.
Choose Change Variable Values from the Analysis toolbar, or select BEx Analyzer |
Change Variable Values from the menu bar. When the Select Values for Variables
dialog box appears, select a value to assign to the variable.
Tools: We can launch other tools from within BEx Analyzer via the Tools function
and its submenu. To launch BEx Query Designer and create a new query, choose Tools 
Query Designer from the Analysis toolbar, or select BEx Analyzer  Tools  Query
Designer from the menu bar.
Global Settings: We can configure global settings, which are defaults valid for the
whole application rather than for individual workbooks. We can configure global
settings in four different areas using this option  the trace file, behavior, statistics, and
default workbook.
Characteristic Properties:
In the Characteristic Properties dialog box for a specific characteristic, we can set a
range of functions. These settings affect all the key figures for this characteristic in a query
drilldown.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
215
General tab: The name of the characteristic appears automatically. We can overwrite this
text. The new text is different from the text provided in InfoObject maintenance and is used
in the query display.
The check box Use Standard Text offers you the ability to indicate that the default
value is always used. In this case, the standard text is the text from the characteristic
determined in InfoObject maintenance. The technical name of the characteristic is also
displayed in this tab.
Display tab: It offers a number of options.

In the Value Display section we have
Display As: Here we can determine whether and in which format we want to present the
individual values of the characteristic.
We have the following options:
No Display: The characteristic display is hidden. This function is useful,
with the currency/unit characteristic because the currencies are also
shown in the key figures.
Key and Text: The characteristic values are displayed by their technical key
and text.
Text: The characteristic values are displayed by their text.
Key: The characteristic values are displayed by their technical key.
Text and Key: The characteristic values are displayed by their text and technical key.
If we set a display type that contains text, we can choose which text type we want to
set under Text View. The following options are available:
Standard: The shortest available text for the characteristic values is used as the text.
Short text: The short text for the characteristic values is used as the text.
Long text: The long text for the characteristic values is used as the text.
Medium text :The medium text for the characteristic values is used as the text.
Sorting section: We can set the sorting within the characteristic according to the key or
text in ascending or descending order. If a characteristic has attributes, we can sort the
characteristic by attribute. The attribute involved does not have to be selected
for the display. Under Sort Characteristic we can choose the characteristic or the required
attribute. Under Sort By, choose Key or Text. Choose Ascending or Descending under Sort
Direction.
key figure properties:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
216
Display tab:
Hide: We can hide key figures that you only need for calculating formulas and do not want
to display. If you hide the key figure, we can still select it in the navigational process and
display the results.
Highlight: We can choose whether the key figure is to be highlighted in the report. This will
allow the presentation tools to identify the key figures that need additional formatting so that
the values are clearly shown in the results.
Number of Decimal Places: We can define the number of decimal places here.
Scaling Factor: We can set the scaling factor here. This is used if the values in your key
figure are large (ex: Billions). Identify the scaling factor in the query and reduce the actual
display to millions (six zeroes versus nine).
Sign Change: We have the ability to remove the sign or reverse the sign here.
Status of Node: Defaults to Not Expandable.
Extended tab:
Enterprise ID: ID for the Enterprise location for the key figure. RKF and CKF have system-
generated numbers, whereas the base key figures have a virtual ID. This field is only used
for information purposes.
Constant Selection: We can set Constant Selection here.
Conversions tab:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
217
Currency Translation: In the query, we can set a currency conversion key and a target
currency. We can also use a variable to allow the translation setting to be determined at
runtime.
Unit Conversion: In the Query Designer, we can set a unit of measure (UOM) conversion
key and a target unit. We can also use variables to allow the translation setting to be
determined at runtime.
QUERY DESIGNER:
The BEx Query Designer is having t three partitions ( InfoProvider, Filter, and Properties).
Within these partitions we have additional options, and we will review all of them. We can
also see that you have some toolbars available at the very top of the screen: Query,
Standard, and View. These toolbar functions are involved in all of the activities of the BEx
Query Designer. Some of the options include Copy, Save, and Create, as well as the ability
to change the view of the Query Designer.
.
Once we access the BEx Query Designer, we need to find a query to work with or
create a new query.
Initial view of the BEx Query Designer/ Query Designer
INFO PROVIDER: Once we select the specific InfoProvider, all the objects
associated with this InfoProvider will appear in this section. This includes both the objects
included in the architecture of the InfoProvider and those structures that are or will be
created in the Query Designer and connected to the InfoProvider, such as structures,
restricted key figures (RKF), and calculated key figures (CKF).
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
218
FILTER (Characteristic Restriction): Here we drag and drop characteristics that will be
filtered and applied to the entire results set for the query. For example, you might want to
filter all the queries based on a specific sales organization, company code, or division.
FILTER (Default Values): Here we define the characteristic filter values used for the initial
view of the results set for the query. The user may decide to modify these filters in the
result.
PROPERTIES: This section is used to display the current settings for an

object highlighted in another section. We can make changes to these settings here. There
are multiple tabs in this section for all the settings, and we will investigate these based on
characteristics and key figures.
MESSAGES: This section is for information purposes. This is a place to indicate whether
query has been built correctly and, if not, where the error is located. We can also provide
some additional information like what to do to fix the error.
Query Designer with rows/columns displayed:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
219
Definition of the Panes in the Query Designer Screen:
Free Characteristics: The characteristics that appear in this section do not appear in the
initial view of the query result and therefore help with the initial query execution against the
database, which in turn helps with query performance. These are not, in their current state,
filters for the query but rather navigational options used during the
analysis of the data in the query.
Columns: We drag and drop The key figures here & these will appear in the columns of the
query.
Rows: We drag & drop characteristics here are & these will appear in the rows of the query.
Preview: This section is a view of what the query will look like once executed. It gives us a
better idea of the information that will appear in the rows and columns. We can then
realign, if necessary.
Toolbars of the Query Designer:
1. Standard Toolbar:
Components of the Standard Toolbar of the BEx Query Designer:
New Query: This function allows to create a new query.

Open Query: This function allows to open an existing query for changes and review.
Save Query: This function offers the ability to save the query.
Save All: This function offers the ability to save not only the query but also other objects
and structures that are not specific to the query but are assigned to the InfoProvider, such
as the RKFs and CKFs created for use by all queries assigned to this InfoProvider.
Execute: This function executes the query via the Web view, not the BEx Analyzer view.
To see the BEx Analyzer view, you have to execute the BEx Analyzer and open the query.
Check Query: This option allows the user to execute a check on the query to validate the
different functions and objects built.
Query Properties: This function switches the pane to the far right of the Query
Designer Tool to the Query Properties view.
Cut: You can use this function to remove an object from a specific area in the query. It can
then be placed in another portion of the query using the Paste function.
Copy: This function inserts an object into a particular section of the query in the Query
Designer. Unlike the Cut function, this function only copies the object and doesn’t affect its
current position in the query.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
220
Paste: This function is used to insert the copied or cut object in the query definition (be
sure to mark the place you want the query object.
2. View Toolbar:
The View toolbar is responsible for all the different dialog boxes for additional functionality
in the Query Designer. It also manages the view of the different sections of the Query
Designer.
Components of the View Toolbar of the BEx Query Designer:

InfoProvider: This function opens the InfoProvider section of the Query Designer.
Filter: This function opens the Filter section of the Query Designer.
Rows/Columns: This function opens the Rows/Columns view of the Query Designer.
Cells: This function is only available and highlighted for queries with two structures. We
can define formulas and selection conditions for cells explicitly. In this way, we control the
values of cells that appear at the intersections of structural components. This function
enables you to access individual cells in queries or to assign special values to individual
cells. We can use this function to create unique formulas for each cell. It is important to
remember that using this function will impact the performance of the query, so be sure to
use this function wisely.
Conditions: We use this function to define conditions for a query. For each characteristic,
we can give limit conditions to the key figure values in order to determine, for example, all
sales revenue above or below a specific amount. This function is used to identify groups of
values—for example, the top 5% of all customers in sales revenue or the bottom 10% of all
customers for total sales in this quarter.
Exceptions: We can use this function to create or define exception reporting in the query.
Exceptions are variances from a specific norm that you define. Nine different levels are
standard with exceptions to define.
Properties: This function displays the properties of the object being highlighted in the Query
Designer. We can then change/adjust or display the parameters for each item.
Tasks: Using this function,we can display the activities available for a unique object in the
Query Designer.
Messages: This function opens the Message pane. In the Message pane is a list of
outstanding messages relating to the status of the query and the objects used or created.
These messages are normally informative in nature. Use the Check Query function to
display a list of messages in the Message pane
Where-Used List : Using this function, we can identify other objects where the query is
being used.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
221
Documents: This option adds an additional tab onto the Query Designer to display all
documents assigned to the objects. It also displays the Application Help functionality.
Technical Names: This function allows to display the technical name and text of the
objects being used in the Query Designer. This allows to hide/ display the technical names.
Query Toolbar:
The Query toolbar is responsible for all functionality surrounding the activities of the query,
including Save, Copy, Edit, View, and Application Help. Some of the functionality in the
Query toolbar is redundant with respect to the Standard and View toolbars
Restriction of Characteristics: The restriction process has different results

depending on where we set up the restriction. Filters or restrictions in the Characteristic
Restriction section are always applied to the query result, which cannot be modified by the
user. These are often regarded as global or static filters. The filters or restrictions in the
Default Values section are applied immediately once the query is executed.
Query Properties for the Query Designer:
Components of the Query Properties in the Query Designer:
General tab:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
222
Description: We can change or adjust the description of the query here. We can use a text
variable in the description. This allows us to customize the text to reflect some thing in the
query or allow manual text entry. We can also enter the query description when we save
the query.
Technical Name: The technical name of the query is displayed.

InfoProvider: The technical name of the InfoProvider on which the query is based is
displayed.
Key Date: Every query has a key date. For time dependent data, the key date determines
the time for which the data is selected. The default value for the key date is the date on
which the query is executed (that is, today’s date). The Select Values for
Date dialog box appears. Choose a date from the calendar and use the arrow
button to add it to the selection window on the right. You can also select a variable
key date. In the Select Values for Date dialog box, choose the Variables tabbed
page. Choose a variable and use the arrow button to add it to the selection window
on the right.
Last Changed Information: Displays details of the owner of the structure, the person who
last changed the structure, and the date and time when the query was changed.
Variable Sequence tab:

List of Variables: Any entry variables the query contains are listed here. We can use the
two arrow buttons to determine the sequence in which the variables appear in the variables
screen when the query is executed. This is purely for display of the variables, not for
creating or changing them.
Display tab:
Display Options:
1. Adjust Formatting After Refresh  This setting is useful in the BEx Analyzer
and is therefore the default setting. The formatting for the query underlines the type of data
contained in a cell and highlights the structure of the delivered results. The position and
size of the cell area in the analysis grid changes when the query is refreshed. The Adjust
Formatting After Refreshing function guarantees that the format is adjusted when the
updated query data is refreshed. You can deactivate the function for adjusting
the format, for example, if we want to display the data more quickly, or if we use a
workbook with your own format template. This should be deactivated if you are formatting
workbook for specific column widths, sizing of the rows, or using other formatting options.
2. Hide Repeated Key Values  We can specify whether identical key figures
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
223
are to be displayed more than once in the query. The Hide Repeated Key Values
setting is active by default, such that only the first key value is displayed for each
characteristic; additional, identical key values are suppressed. We may want to
deactivate this function if you are using the data in the query for a flat file to be
uploaded in another data warehouse. In this way, we will have all the cells filled in and
available for uploading. This parameter must be set again to be functional on the Web.
3. Display Scaling Factors for Key Figures  Key figures can have scaling factors and
units or currencies. Units or currencies aredisplayed for every key figure, but not the
scaling factors. If you activate the Display Scaling Factors for Key Figures setting, an
additional header row is added to the row or column header in the query. Information
about the scaling factor and unit or currency appears in this additional header row,
as long as it is consistent (for example, EUR 1,000). This setting is deactivated by
default. This parameter must be set again to be functional on the Web.
4.
Rows /Columns tab:
Result Position – Rows and Columns  Here you specify where the result (that is,
total) is displayed. Rows: Above or Below. Columns: Left or Right.
By default, the results are displayed at the bottom right.
.
Suppress Zeros: We can use this setting to specify whether columns or rows
containing zeros are to be displayed. The following options are available under
Suppression:
Do Not Suppress: The rows or columns with zeros are displayed.
Active: If characteristics are in the rows and columns, any row or column with a result of zero is
not displayed.
If the rows or columns include, for example, the values 1, −1, 1, −1, the result is 0. If we
select this setting, the whole row or column is hidden.
Active (all values = 0): If this is set, the columns or rows containing zero values in all cells
are not displayed.
Effect On: Defines whether suppression of zero values should be applied to rows and
columns, only to rows, or only to columns.
Value Display tab:
Display of +/− Signs Before, After, in Parentheses Here we specify how the
minus sign (−) is displayed. Either before the number or after the number or the
number isDisplayed in parentheses.
Zero Value Display - Display Zeros, Show Zeroes as  The following options
are available for displaying zeros.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
224
Zero with Currency/Unit  Zeros are displayed with the currency or unit
(ex, EUR 0.00). This is the default setting.
Zero Without Currency/Unit Zeros  are displayed without a currency or
Unit entry.
Zero as Space  Cells containing a zero value remain empty.
• Zero as Default Text  If we choose this setting, the Show Zeros As field is activated.
BASIC KEY FIGURE: It refers to infoobject in the infoprovider which is storing

quanties, amounts, numbers.
Constant Selection: It basically allows to “freeze” the values within a column or RKF,
no matter what the filtering process is during the drilldown into the query. This is helpful if
we need to make sure a calculation is using the same value every time a process executes.
We are able to freeze the denominator so we can have a consistent calculation.
Calculated Key Figures (CKF):

A CKF is a combination of key figures, RKFs, other pre calculated key figures, and
characteristics using a mathematical calculation to derive a formula definition. This formula
definition can be saved at the InfoProvider level and reused by anyone creating queries
against that InfoProvider.
Operators Available for the Formula Editor for Calculated Key Figures:
Operators:
Percentage Function:
1. (%) Percentage Variance: Gives the percentage variance between Operand 1 and
Operand 2. Plan Sales % Actual Sales provides the percentage difference between
the plan sales and actual sales.
2. (%A) Percentage Share: Generates the percentage share of Operand 1 and
Operand 2. Fixed Costs %A Costs provides the proportion of the total cost of a
product that is the fixed cost.
3. (%CT) Percentage Share of Result: Generates the percentage share of the subset
of the total amounts. %CT Sales Volume (the query will have division
and customer data) provides the percentage at the Division/Customer level,
not the T otal/Customer level.
4. (%GT): Percentage Share of Overall Result Generates the percentage share of the
overall results. If the query has a filter, this percentage ignores that filter.
5. %GT Sales Volume: (same scenario as the previous item) generates the
percentage of Customer/Total, ignoring any filters in the query.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
225
6. (%RT) Percentage Share of Report Result: Generates the percentage share of the
query results. Therefore, if the query has a filter, this percentage will pick it up. %RT
Sales Volume (same scenario as before, but Division is restricted) generates the
percentage of Customer/Total and uses the filtered value for Division.
Data Functions:
1. COUNT: Delivers the value 1 if the expression named in <expression> is not 0.
Otherwise, it delivers the value 0. COUNT<expression>
2. DATE: Delivers the values in a Date format. DATE<Expression> mmddyy
3. DELTA: Delivers the value 1 if the change is 0. Otherwise, it delivers the value 0.
DELTA <Expression>
4. NDIV0 : Delivers the value 0 if the division results in a DIV/0 expression.
NDIV0<expression>
5. NODIM : Delivers the quantity without units. NODIM<Expression>
6. TIME: Displays the results of the expression in TIME. TIME<Expression>
hhmmss
.
Boolean Logic: These functions allow you to make comparisons within the formulas
and use conditional calculations. The most popular example of Boolean logic is the
statement IF, THEN, ELSE.
. The following operators are available:
1. Less than <
2. Less than or equal to <=
3. Not equal to <>
4. Equal to =
5. Greater than >
6. greater than or equal to >=
7. AND :The result is 1 if both expressions do not equal 0. If this is not the case, the
result is 0.
8. NOT :The result is 1 if the expression is 0. Otherwise, the result is 0.
9. OR: The result is 1 if one or the other expression does not equal 0. If both equal 0,
the result is 0.
10. exclusive OR The result is 1 if one or the other expression—but not both—does not
equal 0. If both do, the result is 0.
Structures:
A structure forms the basic framework of the axes in a table (rows or columns). It
consists of structural components. We differentiate between key figure structures and
characteristic structures. Structural components of key figure structures are always based
on the key figure selections (basic key figures, restricted key figures, and calculated key
figures). These are structures with key figures.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
226
Characteristic structural components cannot contain key figure selections (structures

without key figures).
The setup of the structure determines the sequence and number of key figures or
characteristic values in the columns and rows of the query. If we are using two structures
(for example, a key figure structure in the columns and a characteristic structure in the
rows), a table with fixed cell definitions is created.
NOTE: We have to use two structures as a prerequisite for defining exception cells. You
can override the value of cell values created implicitly at the intersection of two structural
components.
Structures and their structural components are complex objects. Structural components
can be formulas or selections. Within a query definition, we can use either no structures or
a maximum of two structures. Of these, only one can be a key figure structure. We can
combine structures freely with other characteristics on the axes. The key figure structure
appears in the Query Designer automatically if we move a key figure from the InfoProvider
screen area into the rows or columns of the query definition. The structure that the system
creates automatically is identified by the key figure symbol and contains the default name
Key Figures. We can change this default name.
Characteristic structures are used in the query with several characteristic values. We
have to create a structure and then insert the required characteristic values. To accomplish
this, use the right mouse button to choose New Structure from the context menu in the
columns or rows directory. The default name for the structure is Structure. We can change
this default name. Drag the required characteristic values from the InfoProvider screen area
into the structure.
Cell Editor:
A cell is an intersection of two structures in a query definition.
In certain situations where we need to define each specific cell of a query, we may need to
use the Cell Editor. Cell Editor allows us to directly define specific cells in the query via the
Query Designer. If we define selection criteria and formulas for structural components and
there are two structural components of the query, generic cell definitions are created at the
intersection of the structural components that determine the values to be presented in the
cells.
Variables in the BEx Query Designer
A variable is a parameter of a query that we define in the Query Designer that is filled
with values whenwe execute the query or web application. Variables serve as placeholders
for characteristic values, hierarchies, hierarchy nodes, texts, and formula elements, and
they can be processed in different ways.
We use variables to make a query reusable
Ex: creating one query with variables so that we can use it as a rolling 12 month report;
therefore, regardless of the month we enter at execution, we can see a 12 month analysis.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
227
Types of Variables:
The different types of variables depend on the object for which you want to define them.
These types specify where you can use the variables. Variables enable us to customize
queries flexibly (i.e, parameterize the queries). If we variables in the Query Designer, we
will not select any fixed characteristic values, hierarchies, hierarchy nodes, texts, or formula
elements in the configuration. Instead, set up variables as placeholders. These are then
filled with values during query runtime (when you insert the query into a workbook, when
you refresh the workbook, or when you execute the query on the Web).
.
There are the five types of variables:
• Characteristic values
• Formula
• Texts
• Hierarchies
• Hierarchy nodes
.
If we create a characteristic variable, you will be working in the characteristic screens. Text
variables will be create wherever we use text for column headings, query headings.
The Variables Editor is available in the Query Designer for designing and changing
variables. The Variable Editor is the toolset used for creating variables.
Reference Characteristic: If a reference characteristic is involved, we will be able to identify

it from this section. Ex: The reference characteristic for Sold-To Party is Customer.
The individual options for the settings vary, depending on the variable type and processing
type.
Characteristic Variables: Characteristic value variables represent characteristic values

and can be used wherever characteristic values can be used in a query. We can also
create them directly in the same area where the characteristic values are sho
Variable Represents:
Single Value: The variable represents one value only.

Multiple Single Values: The variable represents a number of single values. This
setting is useful in hierarchy nodes.
Interval: The variable represents a specific “from” value and a specific “to”
value, thus the interval.
Selection Option: The variable represents any combination of single values and
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
228
intervals. In the variable screen where you select values for variables, we can
also work with operators (>, <, =).
Precalculated Value Set The variable represents a set of values that were
precalculated with a query by the BEx Broadcaster. The available values are those
that were precalculated for the characteristic of the variable (such as 0SOLD_TO
Sold-To Party) or its basic characteristic (such as 0CUSTOMER Customer). Such a
variable can also be input-ready. You can select various value sets in the variable
screen at runtime.
NOTE: For technical reasons, you cannot use variables that represent a precalculated
value set in restricted key figures or in selection structure elements.
Variable Is:
Optional: If we select this setting, the variable does not have to be filled with a
value at runtime.
Mandatory: If we select this setting, at least one value has to be specified for
the variable at runtime. The initial value (#) is permitted explicitly. The initial
value # means “unassigned” (that is, you can use it to explicitly select all data
records in which this characteristic has no instances).
Mandatory, Initial Value Not Allowed: If you select this setting, at least one
value has to be specified for the variable at runtime. The initial value (#) is not
permitted. We must enter one or more concrete values in the variable screen to
be able to execute the query.
Variable Is Ready for Input: Using this option, we specify whether the variable is
to be ready for input when the query or web application is executed. If the Variable
Is Ready for Input option is selected (this is the default setting delivered with the
initial set up), when you execute the query or web application, a dialog box appears
(the variable screen). We can either specify the value(s) you want to use, confirm
the default value(s), or change the default value(s). We can deactivate the Variable
Is Ready for Input option if you want to assign a value to the variable beforehand.
When you execute the query or the web application, it is filled automatically
with a value.
NOTE: If you set the variable as being not ready for input, but have set the variable value
as mandatory and have not specified a default value, the system cannot execute the query
and an error message is displayed.
The Variable Is Ready for Input option is available for the processing types
Manual Input/Default Value, Customer Exit, SAP Exit, and Authorization.
• Variable Is Without Context If you select the Variable Is Without Context
option, we are specifying that the variable can be filled with values
independent of an executed query. Examples are Current Day and Current
Year. You can set this indicator for exit variables only. This indicator is
generally not set for all other variable types; the field is therefore deactivated
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
229
(that is, all other variables are treated as context specific).

• Copy Personalization Data from This Variable Users can personalize variable
values for input-ready variables. The personalized values are saved for each
variable and each user.
Characteristic Variables: Characteristic value variables represent characteristic values

and can be used wherever characteristic values can be used in a query. We can also
create them directly in the same area where the characteristic values are shown.
USER CUSTOME SAP AUTHORIAZATIO REPLACEMEN

ENTRY R EXIT EXI N T PATH
DEFAUL T
T
CHARACTARESTI YES YES YES YES YES

C VALUE
VARIABLE
TEXT VARIABLE YES YES YES NO YES
FORMULA YES YES NO YES

VARIBLE
HIERARCHY YES YES YES NO NO

VARIABLE
HIERARCHY YES YES YES YES NO

NODE VARAIBLE
Text Variables: Text variables represent text used in descriptions of queries, calculated
keyfigures, and structural components. We can use text variables when we create
calculated key figures, restricted key figures, selections, and formulas in the description of
these objects. Therefore, we can find text variables anywhere text can be replaced or used.
We will be using a text variable to help with the heading of the columns for key figures and
calendar months.
Formula Variables: It is specifically used in the calculations with key figures. This is a very
powerful tool used for analysis purposes. Formula variables represent numerical values.
Numerical values are also used for calculating exceptions and condition. Formula variables
are used for additional analysis for “what-if” statements: What if the revenue was 10%
higher? What if my costs were 5% lower? What are the average costs for my divisions? We
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
230
can use the formula variable to fill in the number of stores, and including a formula variable
in the CKF.
Hierarchy Variables: Hierarchy variables represent hierarchies and can be used wherever
hierarchies can be selected. If we restrict characteristics to hierarchies or select
presentation hierarchies, we can also use hierarchy variables. Hierarchy node variables
represent a node in a hierarchy and can be used wherever hierarchy nodes can be used.
• Hierarchy node variables are created from the Restrict screen of the InfoObject
• Hierarchy variables are created from the Properties screen of the InfoObject
or from within the restriction of the node variable.
PROCESSING TYPES: The process types determine how the variable is filled at the time
of execution.
There are five processing types.
1. Manual Input/Default Values: This option allows the business user to manually enter
the values they are interested in viewing. Alternatively, a default value has been set
and therefore this is the initial value that shows up in the entry field.
2. Replacement Path: This is used for specific cases.
3. Customer Exit: If we need to create a company-specific exit program to generate
a list of values that are not generally used, you would create an ABAP program and
assign it using this type of processing.
4. Authorizations: If we have created, configured, and set up your authorizations within
BW against the specific characteristic we are reporting on, we can use that
Authorization process within the variable.
5. SAP Exits: SAP offers BC user exits delivered with the system for certain
variables, mostly in the area of time characteristics. These can be accessed using
the transaction code CMOD. Then go to the Utilities|SAP Enhancements option to
view the SAP exit for variables.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
231
SAP EXIT:
The SAP Exit processing type is contained in variables delivered within the BI Content. We
can find the delivered variables in the Metadata Repository. The technical names of SAP
delivered objects begin with a number. We have to activate the delivered variables before
we use them. SAP delivers a number of variables. Some variables are processed via
automatic replacement using a predefined replacement path (SAP Exit processing type). A
large majority of these are in the area of time characteristics.
CUSTOMER EXIT: The Customer Exit processing type for variables enables
us to determine values for variables by means of a function module exit. The standard
function module used is EXIT_SAPLRRS0_001. We create a project in transaction CMOD
by selecting the SAP enhancement RSR000001 and assign this to the enhancement
project. Activate the project.
AUTHORIZATION: This enables variables to be filled with values automatically from the
authorization of a user. The processing type Authorization can be used with characteristic
value variables and hierarchy node variables.
We maintain the authorizations in transaction RSSM or the new Analysis
Authorization. If we choose Process with Authorization when we create a variable, the
variable is automatically filled with the values of the user’s authorization. When the user
opens a query, the data is selected automatically according to the authorizations.
NOTE: When variables are filled automatically no need to have ready for input (i.e the
variable screen does not need to appear when we execute query.) when the user opens
the query with authorization variable, only the data that corresponds to their authorization is
displayed.
IN THE INTERVIEW POINT OF VIEW:
Variables are used in Query Designer to give flexibility to the users when they execute
reports.
We have 5 types of variable in SAP BI:
These variables usage varies based on its processing types.
1) Characteristics Variables 2) Text variables 3) Formula Variables 4) Hierarchy Variable

and 5) Hierarchy node variable.
Same as variables we have 5 processing types.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
232
1) Manual Entry / Default value 2) Replacement path 3) Authorizations 4) Customer Exit

5) SAP Exit.
Characteristic value Variable: This is used to give selections to the user(ex: if user
should be able to enter month for which he wants to see the sales orders)
Text Variable: This is used to provide flexibility in displaying text in the report/fields in
reports. Say when user executes report for 2008 sales data, then he wants to display
revenue key figure as '2009 sales revenue'. In this scenario we can use this.
Hierarchy Variable: This is in query to restrict a characteristic or to display query result

using hierarchy.
Hierarchy Node Variables: This is used to whenever a characteristic is restricted using a

specific hierarchy node. say if customer has hierarchy has region and division, then using
hierarchy node variables, customer can select for which region he wants to display the
result.
Formula Variable: This is used whenever we want to calculate something. We can use
this formula variables to create CKF,RKF, exceptions and conditions also.
BEx Variables using Customer Exit

For some kind of business scenario’s there will be requirement to control the Variable
Value based on certain criteria . These Variable values could be Default values to be filled
on Selection screen for example giving range for Calendar Month Interval or single entry
value for Month.
The second kind of requirement will be deriving the input value of second variable based
User Input on the selection screen . The typical scenario could be getting the previous year
month based on the input Month entered by user in the selection screen.
The third one will be modifying the values of all the Variables either entered by User or
derived dynamically.
Most of the time we will be working first two kind of scenarios. These are controlled based
on the time of execution step of the Query. The details are..
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
233
The customer exit for variables is called three times maximally.
These three steps are called under I_STEP.
The first step (I_STEP = 1) is before the processing of the variable pop-up and gets called
for every variable of the processing type “customer exit”. We can use this step to fill your
variable with default values.
The second step (I_STEP = 2) is called after the processing of the variable pop-up. This
step is called only for those variables that are not marked as “ready for input” and are set to
“mandatory variable entry”.
The third step (I_STEP = 3) is called after all variable processing and gets called only once
and not per variable. Here w can validate the user entries
First we have to create a project for Custom changes for Reporting.

Go to T code: CMOD
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
234
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
235
A project ZBW220 is created
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
236
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
237
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
238
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
239
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
240
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
241
The import parameter I_VNAM holds the variable (i.e name of the variable)
The import parameter I_T_VAR_RANGE holds all the variables and its values that were
created in the BEx report
The import parameter I_STEP can hold values 1 or 2 or 3. This is a very important
parameter, as this identifies, the step in which the required variable is to be processed,
If I_STEP = 1, the variable needs to be processed before the report’s selection screen
appears, an example for this would be like, if some default values are to be populated to
the selection screen variables before user input, I_STEP = 1 can be used. This would
be explained in scenario 2
If I_STEP = 2, the variable is to be processed after the report’s selection appears (ie
after user input). An example for this step is explained in scenario 1 of this document
I_STEP = 3, is used for validation purpose, error messages can be raised here
The export parameter E_T_RANGE is the one to which the calculated value needs to
be passed
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
242
EXCEPTIONS:
Exception functionality allows us to pinpoint information, whether good or bad, and act on it
quickly. It allows the business user to notice and make more responsible decisions and to
identify events that deviate from expected values. This can be an initial warning system
within a report. In exception reporting, we select and highlight objects that are in some way
different or critical. Results that fall outside a set of predetermined threshold values
(exceptions) are highlighted in color or designated with symbols. This enables you to
identify immediately any results that deviate from the expected results.
Settings for Exception Definition in the BEx Query Designer

General tab:
Exception Is Active: Here we can activate or deactivate the condition with Activate
Exception.
Description: Here we can change the description of the exception.
Define Exception Values: Here we enter our values. Alert-level rows are available
at the bottom of the screen, and you identify the alert level, operator,
and value fields for the exception. We can also use a variable for your
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
243
exception and allow the business user to define the exception at the
time of query execution.
Alert Level: There are nine alert levels: Bad 1, 2, 3 (shades of red), Critical
1, 2, 3 (shades of yellow), and Good 1,2,3 (shades of green). These levels
are internally numbered and ranked. These colors can be modified. It is not
required that you use all nine colors; you can use as many or as few as you
require.
Operator: Operators for the assignment of ranges or single values. These operators
Are Equal To, Not Equal To, Less Than, Greater Than, Less Than or Equal
To, Greater Than or Equal To, Between, and Not Between.
Value: The values assigned by the business users. Depending on the values—
percentages, absolute numbers, and so on, this will change.
Conditions:
A condition is defined as the use of threshold values and ranking lists in the Query
Designer to increase the usefulness of the query results and make data analysis more
efficient. In the results area of the query, the data is filtered according to the conditions so
that only the part of the results area you are interested in is displayed.
If we apply conditions to a query, we are not changing any numbers. Instead, we are
just hiding the numbers that are not relevant.. For this reason, conditions have no
effect on the values displayed in the results row. The results row of a query with an active
condition corresponds to the results row of a query without this condition. We can define
multiple conditions for a query. Conditions are evaluated independently of each other.
Thus, the results quantity for the evaluation sequence is independent. The result is the
intersection of the individual conditions. Multiple conditions are linked logically with AND.
A characteristic value is only displayed when it fulfills all (active) conditions of the query.
Settings for the General Tab of the Change Conditions:
Key Figures: Identify the key figure you are going to assign the condition. This will control
the level and positioning of the condition against the data.
Operators:
Equal To
Not Equal To
Less Than
Greater Than
Less Than or Equal To
Greater Than or Equal To
Between
Not Between: Ex: sales revenue from & to is excluded from the display.
Top N: Top number of values.
Bottom N: Bottom number of values.
Top %: Top percentage you identify in this field.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
244
Bottom %: Bottom percentage you identify in this field.

Top Sum: The calculation of this value uses the highest amount of a given object/value (Ex:
highest revenue of a specific customer). The system then sums up the other customers
until the threshold of the highest amount is surpassed; at that point those customers are
listed and displayed. Note that the summation goes from the highest level downward.
Therefore, the top customers, in this example, are used in the calculation.
Bottom Sum: The same calculation as Top Sum, but the weakest customers are used in
the calculation first.
Report-to-Report Interface:
The ability to perform RRI is known as “drilling through” into another query or another
system for information. This enables us to use additional information from another
InfoProvider or even another system to get what we need for business decisions.
Web Application Designer (WAD):

The BEx Web Application Designer is a desktop application for creating Web applications
with BI-specific content. Using the BEx Web Application Designer, We can create an
HTML page containing BI-specific content such as various tables, charts, or maps. This
HTML page (Web application) forms the basis of Web applications with complex
interaction, as well as Web cockpits and iViews.
The initial view of the BEx Web Application Designer has four different screen areas in
addition to the menu and toolbars.
● Web Items Screen Area
● Web Template Screen Area
● Properties Screen Area
● Errors and Warnings Screen Area
WEB ITEM: The Web Items window is a component of the BEx Web Application Designer.
The Web Items window offers a pool of Web items that we can use to create our Web
application. A Web item is the display type (for example, tables, maps, charts) used to
display data from a data provider.
Structure
The Web Items window is made up of two areas:
In the top part of the window, divided onto two tabstrips, are the selection option
categories for Web items.
The Standard tab page contains a selection of master Web items.
The Library tab page contains a list of Web items that are saved in the library.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
245
Web Application Designer allows us to use generic OLAP navigation for our BI data in Web
Applications as well as in Business Intelligence.
We can use the Web Application Designer to generate HTML pages that contain BI specific
content such as tables, charts, and maps. Web Applications are based
on web templates we create and edit in the Web Application Designer. We can save the
web templates and access them from a web browser or a portal. Once they have been
executed on the Web, web templates are known as Web applications. The Web Application
Designer also allows us to create highly individual scenarios with user-defined interface
elements by using standard markup languages and the Web Design API. The BEx Web
Applications that are generated are used for data analysis, reporting, and analytical
applications on the web.
BEx Web Analyzer has been provided as an independent Web Application that can be
used to analyze data on an ad-hoc basis. The WAD is another option in the portfolio of
reporting tools known as Enterprise Reporting, which allows us to create reports for
customized presentation.
WAD results delivered through BI portal or through EP.
The final results of WAD reports are not just about the data, but also about the
presentation. A dashboard may not be well received due to issues with coloring or the
look and feel.
Overview of the WAD:
In the WAD, the BI sources are linked into the Web Framework through Data Providers. A
Data Provider creates a logical connection to the data supplied by a BI source. There is
usually a one-to-one relationship between the BI source and the Data Provider. Each Data
Provider is independent, so it is possible to use the same BI source for multiple Data
Providers if necessary. Web items are responsible for formatting the data received
from a Data Provider.A Chart web item would show the data as a chart, whereas the
Navigation Pane web item would list the components of the Data Provider in the format of a
navigation window. The assignment of a data provider to a web item is known as data
binding.
Not every web item formats data for the user of the Web Application. The XML Data
Provider Information web item makes the data and metadata of the Web Application
available in XML format for use with JavaScript routines. There are other web items, such
as Containers and Context Menus, that do not supply data but are used for formatting. Web
items serve as the building blocks of the web template due to their ability to represent the
Data Provider datain many different formats. A web template is the collection of web items,
formatting objects, texts, images, and parameters that define a web page. Web templates
can be very basic or
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
246
Web Application Designer Components:

The BEx Web Application Designer is a desktop application for creating Web Applications
with BI-specific content. The BEx Web Application Designer allows you to create highly
individual scenarios with user-defined interface elements by using standard markup
languages and the Web Design API. We can adjust and enhance the web templates (the
XHTML pages that determine the structure of Web Applications) on an individual basis.
These XHTML pages are the basis not only for Web Applications with complex interaction,
but also for Web Cockpits and iViews.
To access the WAD: select Start  Programs  Business Explorer  WAD.
Initial screen for the Web Application Designer
To see all the different sections of the WAD, click the Create New Web Template button to
open a new template screen. View of the WAD with the New Template screen open.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
247
The initial view of the BEx Web Application Designer has four different screen areas in
addition to the menu and toolbars:
• Web Items
• Web Template
• Properties
• Errors and Warnings
We can adjust the appearance of the Web Application Designer to your requirements. The
object on which we are working namely the web template is handled differently from the
Tools and Help windows. You can show and hide the individual screen areas and toolbars
using the View menu option. The location of this option is shown here.
We can move the three toolbars and the Web Items and Properties windows as you
require. Depending on where we move an object to, it is anchored or floats freely as a
toolbox. The Web Application Designer is a Multiple Document Interface (MDI) application,
we can open and manage different windows with web templates at the same time. We can
use the Window menu option to arrange the windows differently: cascading (overlapping),
vertically, or horizontally.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
248
Web Item Screen Area The Web Item screen area provides access to all the available
web items and Data Providers as well as a small help section. The web items are
segmented into three groupings: Standard, Advanced, and Miscellaneous. Clicking the
group heading displays the contents of that group. The web items are the basic building
blocks of the web templates, this is a commonly used section and really almost a
requirement to get anything to show up in the WAD.
A web item describes the way in which the data from a Data Provider is displayed, such
as in a table (Analysis web item), map (Map web item), or graphic (Chart web item).
Under the Data Provider section, we can create Data Providers of type Filter or type
Query View. We can drag the required Data Provider type into your web template. The
dialog box for creating Data Providers opens. Underneath the selection for Web Items and
Data Provider Maintenance, you see the help area, which provides explanations for the
web items and the Data Providers. To display the texts for the respective web item, double-
click the web item. To hide the texts, double-click the web item again. Once you have
hidden thedisplay of texts and selected a web item by single-clicking, some quick info is
displayed for the web item
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
249
Properties Screen Area: The Properties screen area provides access to all the
properties of the selected web item or the web template itself. The component you select
determines the number of properties associated with the web item. Also, all the parameters
are set here. The Properties screen area uses two tabs to segment the properties. The
General tab provides access to the Data Provider assignment, if required. The Web Items
tab is, in most cases, the more important portion of the screen and shows a listing of the
configuration settings of the component. The Properties screen area, which is shown next,
is very important to developers.
This is where you will spend most of your time configuring the WAD template.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
250
General tab: Use the Create New symbol next to the dropdown box to create a Data
Provider and assign it to the web item.
Web Item Parameters tab: Here we can set the parameters for the selected web item.
Context sensitive help is available in the lower area of the Web Item Parameters
tabbed page (or the Web Template Parameters tabbed page).
Web Template Screen Area: The Web Template screen area is where the actual web
template is constructed. Basically the web items are dragged and dropped into this area,
and from here the parameters associated with each web item are configured. In the
following illustration, an Analysis web item has been dropped onto the Web Template area.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
251
OVER VIEW OF SD, MM, FI:
SD OVERVIEW
Introduction
This article addresses the requirement and significance of SD application in LO extraction.
This article gives you a brief overview of SD application module relevant for BI. The first
part deals with Functional flow, Transaction, Tables and their relations.
In SD overview we learn 3 important areas of SD where we do OLAP analysis. Those are.
Sales
Sales allow you to execute different business transactions based on sales documents
defined in the system.
Four groups of sales documents are differentiated:
Customer inquiries and quotations
Sales orders
Outline agreements, such as contracts and scheduling agreements
Complaints, such as free of charge deliveries, credit and debit memo requests and
returns
Shipping
Shipping is an important part of the logistics chain in which guaranteed customer service
and distribution planning support play major roles.
In shipping processing, all delivery procedure decisions can be made at the start of the
process by
Taking into account general business agreements with your customer
Recording special material requests
Defining shipping conditions in the sales order
The result is an efficient and largely automatic shipping process in which manual changes
are only necessary under certain circumstances.
Billing
Billing represents the final processing stage for a business transaction in Sales and
Distribution. Information on billing is available at every stage of order processing and
delivery processing.
This component includes the following functions:
Creation of:
1. Invoices based on deliveries or services
2. Issue credit and debit memos
3. Pro forma invoices
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
252
Cancel billing transactions

Comprehensive pricing functions
Issue rebates
Transfer billing data to Financial Accounting (FI)
Organization Structure in Sales and Distribution
CLIENT:
Client is the highest level in SAP.
Client is representing group Companies or corporate identity and
Under which the SAP system runs normal business
Common data base for the client
Data of one client cannot be accessed from other client
Company: Company signifies a legal unit under the client level that produces its own
financial documents, balance sheet and profit and loss statement
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
253
Plant : Plant is a production facility or a group of storage locations where stocks are
kept.Planning and inventory management take place at plant level.
Sales Organization: A Legal unit responsible for selling materials and services for one or
more plants and for negotiating Prices and terms of delivery with the Customer.
Distribution Channel: Products, services selling channel to customer
Division: A way of grouping Materials, Products or services.
Sales Area
Combination of
Sales Organization
Distribution Channel
Division
Master Data in Sales and Distribution

The source of master data for sales order includes
 Customer master data : Info about customers
 Material Master data : Has info about material
 Conditions master data : For automatic pricing
 Output : Information that is sent to customer using various media
 Control tables : Tables maintained in customizing
Customer Master data has these details

General Data
Company Code data
Sales area Data
Excise details
Partner Functions in customer master
Partner functions are terms that describe the people and organizations with whom you
do business, and who are therefore involved in transactions. For example, when you
create an Activity, based on Customizing settings, it automatically includes the partner
functions activity partner, contact person, and person responsible. Partner functions are
always assigned to partner function categories, which are hard-coded in the system.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
254
In general
Sold-to-party : Places the order
Ship-to-party : Receives the goods or services
Bill-to-party : Receives the invoices for goods or services
Payer : Responsible for paying the amount
Main functions of Sales and Distribution (SD) are

 Inquiries & Quotes
 Sales Orders
 Sales Returns
 Consignment
 Contracts & Scheduling Agreements
 Credit & Debit Memo Requests
 Rush Orders & Cash Sales
 Back Orders & Subsequent Deliveries
SAP SD ( Sales & Distribution) process
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
255
Sales Process
SD: Structure for Sales Order Processing
Client 410
Sales Area
Company Code Sales Org

C100 S100
Distribution Division
Channel (RE) (01)
Plant P100 Plant P101
January 2007 (v1.0) The Rushmore Group, LLC 5
Sales and Distribution Process Overview
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
256
Presales activity: Enquiry and Quotations.

Sales order processing : Acceptance of customer’s Sales order.
Important type of Sales orders are
Scheduling agreement
Order
Rush order
Stock transport order
Free of cost order
Order Creation
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
257
Delivery:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
258
Out bound Delivery Creation > A document created with reference to Sales order
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
259
A delivery document will have header and item
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
260
Post Goods issue
Once this is done the outbound delivery status is updated. The billing due list is
updated. Material stock will be reduced.
Billing
Bills can be created with reference to
Order
Delivery
Previous bill
After creating billing

Customer accounted debited
Cost of goods sold account credited
Tax & Duties GL account posted
Billing types:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
261
Invoce creation:
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
262
A billing document has header and item
A billing document creation has following effects
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
263
Tables Involved
Sales order
VBAK -SD header
VBAP -SD item
Billing
VBRK -Billing header
VBRP -Billing item
Shipping
VTTK -Shipment header
Delivery
LIKP -Delivery header
LIPS -Delivery item
Pricing
KONH -Conditions header
KONP -Conditions item
Transactions
 MM01-Create material
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
264
 VA01-Create sales order

 VA32-Scheduling agreement
 VF02-Change billing document
 VL01 -Create delivery
 VK01 -Create sales order
 VD01 -Create sales area
 FD01 -Create accounting
 VA21-Create quotation
 VA11-Create inquiry
 VA41-Create contract
 VA05-List of sales order
The complete SD flow
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
265
MM OVERVIEW:
Organizational Structure
Organizational Levels in the Procurement

Process
Client
Company code
Plant
Storage location
Purchasing organization/
purchasing group
R
 SAP AG
Generally any P2P cycle to start with the Requirement arises in the Industry so it starts with
for stock materials
(1) Purchase Requisition (PR)
(2) Requst for quotaion (RFQ)
(3) Maintain Quoatation (after recieving quoattion from different vendors)
(4) Comparing Quotation (to select the best suitable vendor for purchasing the materials)
(5) Purchase Order (PO)
(6) Goods Reciept (GR)
(7) Invoice Verification (IVR) comparing the items and cost in the invoice with the PO and
GR we will clear it for payment where vendor will be credited.

This is the general flow of P2P for stock materials. If we maintain source list (vendor
records) we can compare the different vendors available at PR it self and thje steps 2,3,4
will not be there if we satisfy with the vendor prices available in the source list.

If the P2P is for services In step 6 instead of GR we will do Service Entry.
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
266
External procurement in the MM System centers around a general cycle of activities.
Process Flow (purchase):
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
267
Process Flow Chart:
Procurement Environment
Requisition
8 Payment Requirements determination

1
Vendor Purchase
invoice order
? 10
20
7 Invoice Verification
30
2 Source determination
Procurement
6 Goods receipt
3 Vendor selection
Purchase
order
10
10
20
20
30
30
5 Purchase order monitoring 4 Order processing R
 SAP AG
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
268
The typical procurement cycle for a service or material consists of the following phases:
1. Determination of Requirements
Materials requirements are identified either in the user departments or via materials
planning and control. (This can cover both MRP proper and the demand-based
approach to inventory control. The regular checking of stock levels of materials
defined by master records, use of the order-point method, and forecasting on the
basis of past usage are important aspects of the latter.) You can enter purchase
requisitions yourself, or they can be generated automatically by the materials
planning and control system.
2. Source Determination
The Purchasing component helps you identify potential sources of supply based on
past orders and existing longer-term purchase agreements. This speeds the process
of creating requests for quotation (RFQs), which can be sent to vendors
electronically via SAP EDI, if desired.
3. Vendor Selection and Comparison of Quotations
________________________________________________________________________
WWW.SRISAITECH.COM
KESHAV BW 7.3 / BI 9642123434
269
The system is capable of simulating pricing scenarios, allowing you to compare a

number of different quotations. Rejection letters can be sent automatically.
4. Purchase Order Processing
The Purchasing system adopts information from the requisition and the quotation to
help you create a purchase order. As with purchase requisitions, you can generate
Pos yourself or have the system generate them automatically. Vendor scheduling
agreements and contracts (in the SAP System, types of longer-term purchase
agreement) are also supported.
5. Purchase Order Follow-Up
The system checks the reminder periods you have specified and - if necessary -
automatically prints reminders or expediters at the predefined intervals. It also
provides you with an up-to-date status of all purchase requisitions, quotations, and
purchase orders.
6. Goods Receiving and Inventory Management
Goods Receiving personnel can confirm the receipt of goods simply by entering the
Po number. By specifying permissible tolerances, buyers can limit over- and
underdeliveries of ordered goods.
7. Invoice Verification
The system supports the checking and matching of invoices. The accounts payable
clerk is notified of quantity and price variances because the system has access to
PO and goods receipt data. This speeds the process of auditing and clearing
invoices for payment.
MASTER DATA IN MM:
1. Material Master
2. Vendor Master
________________________________________________________________________
WWW.SRISAITECH.COM

SAP BW 7.3 & BI 7.0: Over View of

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP BW 7.3 & BI 7.0: Over View of

Uploaded by

Copyright:

Available Formats

KESHAV BW 7.

SAP BW 7.3 & BI 7.0

(BW 7.3 / BI VOLUME 4)

SRI SAI TECHNOLOGIES

IMPORTANCE OF BW / BI FOR AN ENTERPRIZE / ORGANIZATION

An Enterprise can be seen in this way.

Strategic layer  CEO, MD, CIO

Main challenge of any business is decision making.

The people belonging to Strategic layer are the decision makers.

So it is better data to represented in the form of graphs, charts… etc.

BI means Business Intelligence. In other words we can define as "Graphical representation

Infopackage is used to pull data from source system to datasource.

BI means graphical representation of DATA.

C1000 Mr. Pa ul 30 CA Ma ste r da ta

C1000 1000 100 100000 Tra nsa ction

FK: Fore ign Ke y

Re la tionship: Associa tion be twe e n 2 or more ta ble s 28

BI - Business Intelligence (Reporting and Analysis)

o OLAP: Online Analytical Process (SAP BI)

DIFFERENCE BETWEEN OLTP & OLAP

 Changeability: Frequent data changes

 Priority: High availability, High data volume

 Database Operation: Online update/insert/delete and read

 Normalization is very high

 Data Structure: Relational (flat tables)

 Data Set: 6-18 months

 Changeability: Data frozen

 Priority: Simple to use, flexible access to data

 Database Operation: Read

 Less Normalization due to data staging and less performance

 Data Structure: Multi Dimensional format

 Data Set: 2-7 years

Difference between OLAP and OLTP

OLTP is used in operative environment to get efficiency through automation of business

Integration of data from various applications (system)

Due to reduction in data redundancy, normalization is very high requirement in OLTP. In

Not allowed duplicates Allows duplicates

Star Schema and Extended Star Schema Comparisons

Below are some of the basic differences between the two.

Star Schema Extended (BW) Star Schema

Fact Table Key Figure or KPI

Dimension Attribute Characteristic, Attributes, Hierarchis

Dimension Table Dimension Table, Master Data Table, SID Table

Advantages of Classic Star Schema

Disadvantages of Classic Star Schema

Redundant entries exist in the dimension tables

Advantages of the SAP BW Star Schema

For interview point of view we can explain as below:

STAR SCHEMA (SS) : Representation of a cube

Extended Star Schema (ESS): Representation of an InfoCube:

DIFFERENCE BETWEEN STAR SCHEMA & EXTENDED STAR SCHEMA:

STAR SCHMA EXTENDED STAR SCHEMA

He a de r Cus tome r Cus tome r Cus tome r Cus tome r

DB Design OLTP: ERM (Entity relationship modeling)

PICTORIAL VIEW OF STAR SCHEMA

Cus tome r ID (PK)

Ma te ria l Dime nsion

In sta r sche ma , fa ct ta ble a nd dime nsiona l ta ble s / m a re existing within cube 35

LIMITATIONS (DEMERITS) IN STAR SCHEMA:

TO OVER COME THE ABOVE DEMERITS WE GO TO EXTENDED STAR SCHEMA

EXTENDED STAR SCHEMA (ESS)/(BW STAR SCHEMA):

Extended Star Schema