SAP BW

Interview Questions

Q. What are the differences between OLAP and OLTP applications

OLAP

OLTP

a. Summarized data

Detailed

b. Read only

Read write

c. Not optmized

Optimized for data applications

d. Lot of historical data

Not much old data

Q. What is a star schema?

A fact table at the center and surrounded (linked) by dimension tables.

Definitions of some Objects in BI/BW

Info Area:
Element for grouping meta-objects in the BI system.
Each InfoProvider is assigned to an InfoArea. The resulting hierarchy is displayed in
the Data Warehousing Workbench.
In addition to their properties as an InfoProviders, InfoObjects can also be assigned
to different Info Areas.
Info Area is a Top Level Object, which contains the data models in it .
In general, Info Areas are used to organize InfoCubes and InfoObjects. Each
InfoCube is assigned to an Info Area. Through an InfoObject Catalog, each Info
Object is assigned to an Info Area as well.
The Info Area contains all objects used to evaluate for a business logical process.
Info Area in which Info Providers are stored.
Info Object Catalogs:

An Info Object catalog is a collection of InfoObjects grouped according to

application-specific criteria.
There are two types of InfoObject catalogs: Characteristic and Key figure.
Info Objects, (characteristics and key figures) are the basic data model of SAP
Business information warehouse(BW/BI).
And the Info objects are stored in folders, it also called the InfoObject catalogs, the
infoobject catalogs are also stored in a folder called Info Areas.
InfoObjects:
Business evaluation objects are known in BI/BIW as InfoObjects. They are divide into
characteristics (for example, customers), key figures (for example, revenue), units (for
example, currency, amount unit), time characteristics (for example, fiscal year) and technical
characteristics (for example, request number).
InfoObjects are the smallest information units in BI/BW.
They structure the Information needed to create the data targets.

Application Component
Application Components are used to organize Data Sources. They are analogous to
the Info Areas.
Info Package:
An InfoPackage specifies when and how to load data from a given source system. BW
generates a 30-digit code starting with ZPAK as an InfoPackage's technical name.

PSA

Persistent Staging Area is a data staging area in BW. It allows us to check data in an
intermediate location, before the data are sent to its destinations in BW.
The PSA stores data in its original source system format. In this way, it gives us a
chance to examine / analyse the data before we process them to further destinations.
Most probably it is a temporary storage area, based on the client data specifications
and settings.

Surrogate ID -- Master Data Tables

Standard Info cube consists of fact table surrounded by many dimension table. SID
table links these Dimension tables to master data tables.
SID is surrogate ID generated by the system. The SID tables are created when we
create a master data IO. In SAP BI Extended star schema, the distinction is made
between two self contained areas: Info cube & Master data tables and connecting SID
tables.
The master data doesn't reside in the Extended Star schema but resides in separate
tables which are shared across all the star schemas in SAP BI.
An Unique Numeric ID , the SID is generated which connects the dimension tables of
the infocube to that of the master data tables.
The dimension tables contain the DIM IDs and SIDs of a particular Characteristic
Info Object. Using this SID Table the Master data ( attributes and texts of Info
Object) is accessed.

SID
SID (Surrogate-ID) translates a potentially long key for an InfoObject into a short four-byte
integer, which saves I/O and memory during OLAP.

Star schemaA star schema is a technique used in the data warehouse database design to
help data retrieval for online analytical processing(OLAP).

List of Technical Tables

F - Fact Table - Uncompressed Fact Table - Contains Direct data for cube Request
wise ( Based on B-Tree Index )
E - Fact Table - Compress cube - Contains compressed data without Request
IDs( Request ID would be 'zero') ( based on Bitmap Index )
M - View of Master Data Table - /BI0/MMATERIAL
P - Time Independent Master Data Table - /BI0/PMATERIAL
Q - Time Dependent Master Data Table - /BI0/QMATERIAL
H - Hierarchy table - /BI0/HMATERIAL
J - Hierarchy interval table - /BI0/JMATERIAL
K - Hierarchy SID table - /BI0/KMATERIAL
I - SID Hierarchy structure - /BI0/IMATERIAL
S - SID table - /BI0/SMATERIAL
X - Time Independent SID table for Attr - /BI0/XMATERIAL
Y - Time Dependent SID table fir Attr - /BI0/YMATERIAL
T - Text Table - /BI0/TMATERIAL
Q. What is a slowly changing dimension?

A dimension containing a characteristics which changes over a time; for example take
employee job title; this changes over a period of times with different job titles.

Q. What are the advantages of Extended star schema of BW vs. the star schema

In Classic 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 resides inside Infocube).
In Classic star 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.

Classic Star Schema

BW Star Schema

Fact

Key Figure

Dimension Attribute

Characteristic

Described Attribute

Attribute
Text

Dimension
(Contain Master Data)

External Hierarchies

Tables

Dimension = Dimension Table

Dimension
Tables
(do not contain Master data

Dimension
=
Dimension
Table
(optional),
SID
Tables,
Master Data Tables (optional)

use of generated keys (numeric) for faster access

external hierarchy
multi language support
master data common to all cubes
slowly changing dimensions supported
aggregates in its own tables for faster access

Q. What is the namespace for BW?

All SAP objects start with 0 and customer is A-Z; all tables begin with /BIO for
SAP and /BIC for customers; All generated objects start with l-8 (like export
data source); prefix 9A is used in APO.

Q. What is APO ?
SAP Advanced Planner and Optimizer is a planning tool which is used to plan and
optimize supply chain processes by making use of various modules viz. Demand Planning,
Supply Network Planning, Production Planning and Detailed Scheduling, Global Available to
Promise and Transportation management & vehicle Scheduling or Transportation Planning &
Vehicle Scheduling.
According to SAP literature, Advanced Planner and Optimizer is designed to help a company
improve production planning, pricing, scheduling, and product shipping. APO works by
getting real-time updates from retailers about customer demand. The updates are used to
create APO "demand triggers" that take into account many complex variables, such as the
delivery schedule of raw materials and productions cycles, to forecast the right amount of
product mix the company will need to meet future customer demands. APO can be integrated
with the SAP R/3 and legacy enterprise resource planning (ERP) systems.
APO consists of eight application levels: network design, demand planning, supply network
planning, production planning and detailed scheduling, global availability, transportation
planning and vehicle scheduling, and supply chain collaboration.

Q. What are the data types supported by characteristics?

NUMC, CHAR (up to 60), DATS and TIMS

Q. What is an external hierarchy?

A hierarchy is a method of displaying a characteristic structured and grouped according to
individual evaluation criteria. Hierarchies are created for basic characteristics
Hierarchies are stored in special master data tables. They behave in a similar way to
master data, and can therefore be used and modified in all Info Cubes. You can
define several hierarchies for a single characteristic. A hierarchy can have a maximum of
98 levels.

Q. What are time dependent text / attribute of characteristics?

If the text (for example a name of the product /person over time) or if the attribute changes
over time (for example job title) then these must be marked as time dependent. In the
InfoObject Maintenance, make sure that the relevant InfoObject is flagged as timedependent in the Master Data/Texts tab.

Q. Can you create your own time characteristics?

No
Why ?
SAP BI doesnt support this. I presume SAP don't want you to create custom time
characteristics to keep the integrity of the time dimension.
You can create your own time characteristics this way:
1) create a normal characteristic, say ZTIME
2) SE16 >> table RSDIOBJ >> change ZTIME from a CHA to a TIM characteristic
3) SE16 >> table RSDTIM >> create a new entry for ZTIME
go back to RSD1 and your characteristic will now be a time characteristic.

Q. What are the types of attributes?

Display only and navigational;
Display attributes - You can display these attributes of the main info object in the query but
cannot drill down beyond these attributes and apply some formula's.
Navigational attributes - You can display these attributes in the query as well as apply drill
down beyond these attributes and apply formula's and do some calculation.
For query performance, it is recommendable to keep attributes of main info object as display
until user specifically request for it. System default for attributes is display until you change it
to navigational.
Imp Note:

While Creating the Info Object -- Attributes Tab Page -- Nav Attributes 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.

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/1a63e7e07211d2acb80000e82
9fbfe/frameset.htm

Display only attributes are only for display and

no analysis can be done; navigational attributes behave like regular characteristics; for
example assume that we have a customer characteristics with country as a navigational
attribute; you can analyze the data using customer and country.

Q. What is Alpha conversion?

Alpha conversion is used to store data consistently by storing any numeric values with
prefixing with Os; for example if you defined material as 6 Numc then number 1 is stored as
000001 but displayed as 1; this removes inconsistencies between 01 vs. 001.

Q. What is the alpha check execution program?

This is used to check consistency for BW 2.x before upgrading the system to
3.x; the transaction is RSMDCNVEXIT

Q. What is the attributes only flag?

If the flag is set, no master data is stored; this is only used as attribute for other
characteristics; for example comments on a AR document.

Q. What is compounding?
This defines the superior info object which must be combined to define an
object; for example when you define cost center then controlling area is the
compounding (superior) object.

Compounding Info Object

In Compounding a Field or another Object is attached to an Info Object. A
Compounding Characteristic is when object's definition is incomplete
without the definition of another Characteristic Info Object.
For the better understanding the Info Object - Location (0PP_LOCAT) has
to be assigned with a Compound Info Object - Plant (0PLANT).
Here Plant(0PLANT) is the Superior Info Object of the
Location(0PP_LOCAT)
The Info Object 0Plant has to be Installed/Created/ Activated first, later
followed by Location(0PP_LOCAT)
While creating the Info Object itself we need to assign the Superior Object
like below at Compounding Tab Page of Info Object.

Compounding Info Object Acts as a compounding Primary Key at the

Master Data Table.

When a compounded Info object is included in an Info cube, all

corresponding info objects are added to the Info cube.
If Location(0PP_LOCAT) is to be included in the Info Cube , Plant (0Plant)
is automatically added to the Info Cube.
When a Compounded Info object is included in the DSO , all

corresponding Objects are added to the DSO Key fields/Data Fields.

If Location(0PP_LOCAT) is to be included in the DSO , Plant (0Plant) is
automatically added to the DSO.

Q. What is the Bex options for characteristics like F4 help for query definition and
execution?
This defines how the data is displayed in query definition screen or when query
is executed; options are from the data displayed, from master data table (all
data) and from dimension data; for example let us assume that you have 100
products in all, 10 products in a cube; in bex you display the query for 2
products; the following options for product will display different data
a. selective data only - will display 2 products
b. dimension data - will display 10 products
c. from master data - will display all 100 products

Q. What are the data types allowed for key figures?

Amount, Quantity, number, integer, date and time.

Q. What is the difference between arnount/quantity and number ?

amount/quantity always comes with currency/units; for example sales will be amount and
currency and inventory is quantity with units.

Q. What are the aggregation options for key figures?

If you are defining prices then you may want to set no aggregation or you can
define max, min, sum; you can also define exception aggregation like first, last,
etc; this is helpful in getting headcount; for example if you define a monthly
inventory count key figure you want the count as of last day of the month.

Q. What is the maximum number of key figures you can have in an info cube?
233

Q. What is the maximum number of characteristics you can have per dimension?
248

Q. What are the nine decision points of data warehousing?

a. Identify fact table
b. Identify dimension tables
c. Define attributes of entities
d. Define granularity of the fact table (how often
e. Pre calculated key figures
f. Slowly changing dimensions
g. Aggregates
h. How long data will be kept
i. How often data is extracted

Q. How many dimensions in a cube

Total 16 out of which 3 are predefined time, unit and request; customer is left
with 13 dimensions

Q. What is a SID table and advantages

The SID table (Surrogate ID table) is the interface between master data and the
dimension tables; advantages :a. uses numeric as indexes for faster access
b. master data independent of into cubes
c. language support

d. slowly changing dimension support

Q. What are the other tables created for master data?

a. P table - Time independent master data attributes
b. Q table - Time dependent master data attributes
c. M view - Combines P and Q
d. X table - Interface between master data SIDS and time independent
navigational attributes SIDS ( P is linked to the X table)
e. Y table - Interface between master data SIDS and time dependent
navigational attributes SIDS (Q is linked to the Y table)

Q. What is the transfer routine of the info object?

It is like a start routine; this is independent of the data source and valid for all
transfer routines; you can use this to define global data and global checks.

Q. What is the DIM ID?

Dim ids link dimensions to the fact table

Q. What is table partition?

SAP is using fact table partitioning to improve performance; you can partition
only on OCALMONTH or OFISCPER;

Q. How many extra partitions are created and why?

Usually 2 extra partitions are created to accommodate data before the begin date
and after the end date

Q. Can you partition a cube which has data already?

No; the cube must be empty to do this; one work around is to make a copy of
the cube A to cube B; export data from A to B using export data source; empty
cube A; create partition on A; re-import data from B; delete cube B

Q. What is the transaction for Administrator work bench?

RSA1

Q. What is a source system?

Any system that is sending data to BW like R/3, flat file, oracle database or
external systems.

Q. What is a data source?

The source which is sending data to a particular info source on BW; for
example we have a 0CUSTOMER_ATTR data source to supply attributes to
OCUSTOMER from R/3

Q. What is an info source?

Group of logically related objects; for example the OCUSTOMER info source
will contain data related to customer and attributes like customer number,
address, phone no, etc

Q. What are the types of info source?

Transactional, attributes, text and hierarchy

Q. What is communication structure?

Is an independent structure created from info source; it is independent of the
source system/data source

Q. What are transfer rules?

The transformation rules for data from source system to info
source/communication structure

Q. What is global transfer rule?

This is a transfer routine (ABAP) defined at the info object level; this is
common for all source systems.

Q. What are the options available in the transfer rule

Assign info object, assign a constant, ABAP routine or a Formula (From version
3.x); example are :
a. Assign info object - direct transfer; no transformation
b. Constant- for example if you are loading data from a specified country in a
flat file, you can make the country as constant and assign the value
c. ABAP routine - for example if you want to do some complex string
manipulation; assume that you are getting a flag file from legacy data and
the cost center is in a field and you have to massage the data to get it; in
this case use ABAP code
d. For simple calculations use formula; for example you want to convert all
lower case characters to upper case; use the TOUPPER formula

Q. Give some important formula available

Concatenate, sub string, condense, left/light (n characters), l_t1im, r_trim,
replace, date routines like DATECONV, date_week, add_to_date, date_diff,
logical functions like if, and;

Q. When you do the ABAP code for transfer rule, what are the important variables
you use?
a. RESULT - this gets the result of the ABAP code
b. RETURNCODE - you set this to 0 if everything is OK; else this record is
skipped
c. ABORT - set this to a value not 0, to abort the entire package

Q. What is the process of replication?

This copies data source structures from R/3 to BW

Q. What is the update rule?

Update rule defines the transformation of data from the communication
structure to the data targets; this is independent of the source systems/data
sources

Q. What are the options in update rules?

a. one to one move of info objects
b. constant
c. lookup for master data attributes
d. formula
e. routine (ABAP)
f. initial value

Q. What are the special conversions for time in update rules?

Time dimensions are automatically converted; for example if the cube contains
calendar month and your transfer structure contains date, the date to calendar
month is converted automatically.

Q.What is the time distribution option in update rule?

This is to distribute data according to time; for example if the source contains
calendar week and the target contains calendar day, the data is split for each
calendar day. Here you can select either the normal calendar or the factory
calendar.

Q. What is the return table option in update rules for key figures?
Usually the update rule sends one record to the data target; using this option you
can send multiple records; for example if we are getting total telephone
examples for the cost center, you can use this to return telephone expenses for
each employee (by dividing the total expenses by the number of employees in
the cost center) and creating cost record for each employee in the ABAP code.

Q. What is the start routine?

The first step in the update process is to call start routine; use this to fill global
variables to be used in update routines;

Q. How would you optimize the dimensions?

Use as many dimensions as possible for performance improvement; for example
assume that you have 100 products and 200 customers; if you make one
dimension for both, the size of the dimension will be 20,000; if you make
individual dimensions then the total number of rows will be 300. Even if you
put more than one characteristic per dimension, do the math considering worst
case scenario and decide which characteristics may be combined in a
dimension.

Q. What is the conversion routine for units and currencies in the update rule?

Using this option you can write ABAP code for unit/currency conversion; if you
enable this flag, then unit of the key figure appears in the ABAP code as an
additional parameter; for example you can use this to convert quantity in
pounds to kilo grams.

Q. How do you add an entry in the monitor log from the update rules?
This is added in the intemal table MONITOR; the following fields describe the
MONITOR structure
a. MONITOR-MSGID -> gives an ID
b. MONITOR-MSGTY -> message type
c. MONITOR-MSGNO -> message number
d. MONITOR-MSGV1 -> monitor messagel
e. MONITOR-MSGV2 -> monitor message 2
f. Append it to the MONITOR table; this will show up in the monitor

Q. What is a data mart?

The bw system can be a source to another BW system or to itself; the
ODS/cube/infoprovider which provide data to another system are called data
marts.

Q. What is the myself data mart?

The BW system feeding data to itself is called the myself data mart; this is
created automatically; uses ALE for data transfer

Q. How do you create a data mart?

a. Right click and create the export data source for the ODS/cube
b. In the target system replicate the data source
c. Create transfer rules and update rules
d. Create info package to load

Q. Can you make multi providers and master data as data marts?
Yes

Delta update
The Delta update option in the InfoPackage definition requests BI/BW to load only
the data that have been accumulated since the last update. Before a delta update
occurs, the delta process must be initialized.

Examples of multi-dimensional analysis worked on in Argos:

1. Show me the Sales Amount by Sales Department by Material Group by Month
2. Show me the Sales Amount for a specific Sales Department X by Material by Month
Turnover reports by Market
Market hierarchy in Rows, QTD YTD, QTG, YTG, in columns
Turnover Reports by Product
Profit and Loss Statements
Income Statement QTD / QTG
Rows have
Total Turnover ,Gross Sales , Discounts, Invoiced Sales, Rebates, Returns , Total Sales after
Deductions, % Gross Sales based on TSD, Other Income, Cost of Sales, Gross Profit, %Turnover
based on Gross Profit , %Turnover based on Advertising Costs, % Turnover based on Promotion
Costs % Turnover based on Medical Trials Cost, % Turnover based on Brand Profit , % warehouse
distribution and Selling costs out of turnover, % of Turnover on R&D costs
Columns
QTD Actuals
QTD Plan
QTD Actuals vs Plan
QTD Actuals vs Plan %
QTD Actuals @ LYAR
QTD LY Actuals @ LYAR
QTD vs LY
Similarly for QTG and Full YEAR

Q. What are the benefits of data marts? Simple to use

b. Hub and spoke usage
c. Distributed data
d. Performance improvement in some cases

Q. What are events and how you use it in BW?

Events are background signal to tell the system that certain status has been
reached; you can use events in batch jobs; for example after you load data to the
cube you can trigger an event which will start another job to run the reporting
agent. Use SM62 to create and maintain events.

Q. What is an event chain?

This is a group of events which complete independently of one another; use this
to check the successful status of multiple events; for example you can trigger a
chain event if all loads are successful.

Q. How do you create event chains?

AWB -> Tools -> Event collector

Q. What is PSA?
Persistent staging area -is based on the transfer structure and source system
dependent.

Q. What are the options available for updates to data target?

a. PSA and data targets in parallel - improves performance
b. PSA and data target in sequence
c. PSA only - you have to manually load data to data targets

d. Data targets only - No PSA

Q. Why if one request fails, all the subsequent requests are tumed to red?
This is to avoid inconsistency and make sure that only verified data is entered
into the system

Q. What are the two fact tables?

There are two fact tables for each info cube; it is the E table and the F table;

Q. What is compression or collapse?

This is the process by which we delete the request 1Ds; this saves space; all the
regular requests are stored in the F table; when you compress, the request H) is
deleted and data is moved from F table to E table; this saves space and improves
performance but the disadvantage is that you can not delete the compressed
requests individually

Q. What is reconstruction?
This is the process by which you load data in to the same cube or to a different
cube.

Q. What is a remote cube?

Remote cube is a logical cube where the data is extracted from an external
source; usually it is used to report real time data from an r/3 system instead of
dlilling down from BW to R3

Q. What is virtual info cube with services?

In this case a user defined function module is used as data source

Q. What are the restrictions/recommendations for using remote cube?

These are used for small volume of data with few users; no master data allowed

Q. Give examples of data sources that support remote cubes?

0FI_AP_3 - vendor line items, 0FI_AR_3 - customer line items

Q. What is a multi provider?

Using multi provider you can access data from different data sources like cubes,
ODS, infosets, master data

Q. What is an info set?

An info provider giving data by joining data from different sources like ODS,
master data, etc

Q. What is the difference between multi provider and infoset?

Multi provider is a Union whereas infoset is a Join (intersection)

Advantages of Multiprovider
MultiProviders
These are the advantages of MultiProviders:
o Local queries (on each basic InfoProvider) versus global queries (on MultiProvider, parallel
execution).
o Independent (and parallel) data load into the basic InfoProviders.
o Small total data volumes: basic InfoProvider have less redundant data; they are sparsely filled and
less complex.

Q. Can you create an info set with info cube?

No; only ODS and master data are allowed

Q. What is a line item (or degenerate dimensions) If the size of a dimension of a cube is more than the normal (more than 20%) of
the fact table, you define that dimension as a line item dimension; for example if
you store sales document number in one dimension in a sales cube, usually the
dimension size and the fact table size will be the same; when you add the
overhead of look ups for DIMID/SIDS the performance will be very slow; by
flagging it as a line item dimension, the system puts the SID in the fact table
instead of DIMID for the sales document number; this avoids one look up into
dimension table (the dimension table is not created in this case)

Q. What are the limitations of line item dimension?

Only one characteristic is allowed per line item dimension.

Q. What is a transactional infocube?

These cubes are used for both read and write; standard cubes are optimized for
reading. The transactional cubes are used in SEM.

Q. What is the cache monitoring transaction?

RSRCACI-IE

Q. What are the profile parameters for cache?

rdsb/esm/buffersize_kb (max size of cache) and rsdb/esm/max_objects (max
number of entries in cache)

Q. Can you disable cache?

Yes either globally or using query debug tool RSRT

Q. What does the program RSMDCNV EXIT check?

a. all characteristics with conversion exit ALPHA, NUMC and GJAI-IR
b. all characteristics which are compounded to the earlier

Q. Can you restart the conversion?

Yes

Q. When should you do the alpha conversion?

If you are upgrading you must do it before PREPARE phase of upgrade

Q. Can you make an info object as info provider and why?

Yes; when you want to report on characteristics or master data, you can make
them as an info provider; for example you can make OCUSTOMER as an info
provider and do bex reporting on OCUSTOMER; right click on the info area and
select Insert characteristic as data target

Info Set ( Join )

Info Set is a Virtual Provider. Info Sets allow you to analyze the data in several Info Providers
by using combinations of master data-bearing characteristics, Info Cubes and Data Store
objects. The system collects information from the tables of the relevant Info Providers. If you
are joining large sets of data from the master data or from DSO objects, SAP recommends
that you use an Info Set. This improves performance as fewer temporary tables are required
and the join is executed in the database itself.
Joins are 4 types
: 1) Left outer Join
2) Right outer Join.
3) Temporary Join...based on any Date field.
4) Equal Join
Inner Join:
In case of inner join there should be an entry in all the tables use in the view.
Outer Join:

With the use of outer join you can join the tables even there is no entry in all the tables used
in the view. Inner join between table 1 and table 2, where column D in both tables in the join
condition is set the same:
Q. What are the control parameters for data transfer?
This defines the maximum size of packet, max no of records per packet, the
number of parallel processes, etc

Q. What is number range object?

This defines the characteristic attributes; for example the object MATERIALNR
defines the attributes of material master like the length, etc

Q. How do you set up the permitted characters?

Using transaction RSKC.

Q. What is aggregate realignment run maintenance?

Defines the level of percentage change for realignment run will cause a
reconstruction of aggregates.

Q. What is update mode for master data?

Defines whether the master data (auto sid) is added automatically for non
existing master data when you load transaction data.

Q. What is the ODS object settings?

Defines number of parallel processors in activation, min number of data records
and wait time.

Q. What are the settings for flat files?

Defines thousand separator, decimal pointer, field separator (default is ;) and

field delimiter (default )

Q. Which transaction defines the background user in source system?

RSCUSTV3

Non Cumulative Key Figures

Q. What are non cumulative key figures?

These kinds of key figures are not summarized (unlike sales, etc); examples are
head count, inventory amount; these are always in relation to a point in time; for
example we will ask how many employees we had as of last quarter. We dont
add up the head count.
Give an example - the content key figure OTOTALSTCK (Quantity Total Stock)
Is a non cumulative key figure. It has exception aggregation as Last value and
inflow as receipt qty total stock and outflow as issue qty total stock.

Q. What is standard and exception aggregation?

Standard aggregation -> specifies how a key figure is compressed using all
characteristics except time; exception aggregation -> specifies how key figure is
compressed using time characteristics.

Q. What is inflow and outflow?

These are non cumulative changes used to get the right quantity

Q. What is a Marker?
Non cumulatives are stored using a Marker for the current period.

Q. What is a time reference characteristic?

Is a time characteristic which determines all other time characteristic;
OCALDAY, OCALMONTH, OCALWEEK, OFISCPER

Q. Give example data sources supporting this?

2LIS_03_BF and 2LIS_03_UM

Q. What is the opening balance?

When you start loading inventory data from R/3 you start with a certain point in
time; this is what is called opening balance; assume that you have inventory
since Jan 2002; you are loading data on J an 2003 and the opening balance for
the product is 200; the data before Jan 2003 is Historic data; any data loaded
after J an 2003 is a delta load.

Q. What is No Marker Update?

If you choose this option when compressing Non cumulative cube, the reference
point is not updated but the requests are moved to Request O (usual
compression); you must do this for compressing historical data; for example use
this option to compress data before Jan 2003;

Q. What are the steps to load non cumulative cube?

a. initialize opening balance in R/3 (S278)
b. activate extract structure MC03BFO for data source 2LIS_03_BF

c. set up historical material documents in R/3

d. load opening balance using data source 2LIS_03_BX
e. load historical movements and compress without marker update.
f. set up V3 update
g. load deltas using 2LIS_03_BF

Q. How does the query calculated?

Qty = Ref point in time Qty - Non compressed delta qtys - deltas for backward
qty

Q. What is a validity determining characteristic?

That determine validity period of non cumulative cube; example plants opening
and closing different time periods

Q. What are the dos and donts?

a. use few validity objects
b. compress the cube ASAP

Authorizations

Q. What is ar1 authorization object?

Defines the fields for authorization checks

Q. What is the role maintenance transaction?

PFCG

Q. What is a role?

Usually defines the responsibility of a user with proper menu and authorization
- example receiving clerk

Q. Give some examples of the roles delivered with SAP BW?

All the BW roles start with S_RS; S_RS__ROPAD- Production system
administrator; S_RS_RREPU - bex user

Q. What are the different authorization approaches available in BW?

a. infocube based approach - use this in conjunction with Infoarea to limit access
b. query name based approach - many customers use this to limit access; for z queries are
read only, Y queries are read/write; FI* query names for FI use, etc
c. Dataset approach - limitation of characteristics and keyfigures; you can use reporting
authorization for this.

Q. What are the two object classes of BW authorization?

BW Warehouse authorization - SAP standard; BW Reporting - Not delivered by SAP - user
has to create

Q. How many fields you can assign to authorization object?

10

Q. What are the values for ACTVT?

Create, change and display

Q. Give some examples of standard authorization objects delivered for BW?

a. S_RS_IOMAD - Master data
b. S_RS_ADMWB - AWB objects
c. S_RS_ODSO - ODS objects

d. S_RS_TOOLS - Bex tools

e. S_RS_ICUBE - info cube
f. S__RS_H1ER - hierarchy
g. S_RS_COMP, S_RS_COMP1 - reporting authorization
h. S_RS_FOLD - folders
i. S_RS_IOBJ - info object
j. S_RS_ISOUR -info source (transaction data)
k. S_RS_ISRCM -info source (master data)
(workbooks)

l. S_GUI - GUI

Activities

m. S_BDS_DS - document set (for workbooks)

n. S_USER_AGR - role check for saving workbook in a role
o. S_USER_TCD - transaction in roles for saving workbook in a role

Q. What is an reporting object?

This is used for BW reporting to check authorizations by the OLAP processor

Q. Give a step by step approach to create an authorization object; let us assume

that we want to restrict the report by cost center. A

a) Make the info object as Authorization relevant (flag ) and activate it; in this example
OCOSTCENTER
b) Create an authorization object using transaction RSSM
c) Assign the object to one or more info providers
d) Create role(s) with different values for cost centers; for example you can create a role
called IT Manager and assign all IT cost centers
e) Assign the role to users
f) Create a query; create a variable within the query for OCOSTCENTER of type
Authorization and include in the query; if the IT manager runs the query it shows only the
cost centers assigned to him/her.

Q. How to implement structural authorization in BW?

a. create profile using transaction
OOSP
b. assign user to profile using transaction OOSB
c. update T77UU table
d.
run the program RI-IBAUS00
e. activate the data source and related components
0HR_PA_2 in BW f. load ODS from R/3
g. activate target info objects as Authorization relevant
h. run the function module RSSB to generate BW authorization.

Q. What are the new BW 3.x authorizations?

S_RS_COMP1 checks for authorization depending on the owner; S_RS_FOLD info area
view of Bex elements (to suppress); S_RS_ISET for info sets; S_GUI - new activity code 60
loaded for upload.

Q. What is the use : as an authorization value?

a. it enables queries that do not contain a
authorization relevant
object that have been checked in info cube
b. it allows
summary data to be displayed if the user does not
have access to detailed data; for
example if you create 2 authorizations for one user one with Sales Org * and
customers : and second with sales org 1000 and customers *,
the user sees all customers for sales org 1000 and only summarized report for other sales org.

Q. What is $ as an authorization value?

You use S followed by a variable name (values populated in user exit for bex); this avoids
having too many roles

Q. What is info object OTCTAUTHH?

This is used in hierarchy authorization

KPIT interview:
1. Overlapping requests in Process Chain
2. Why will use Compounding
What is Delta?
Delta is a feature of the extractor, which refers to the changes (new/modified entries),
occurred in the Source System 0Recordmode The record mode describes the type of change
that a data record contains.

If a datasource is delta capable, the field ROCANCEL which is part of the datasource, holds
the changes from R/3 side.
This field for the DataSource is assigned to the InfoObject 0RECORDMODE in the BI
system.
ROCANCEL serves the same purpose at R/3 side which its counterpart 0RECORDMODE does at
BW side.
The values for 0recordmode
Figure 1 The following 6 Record Mode types are available, which identify how a delta record is
updated to the data target:
After im

3. 0record
4. Match X OR COPY: MatchX or Copy is a function provided by SAP to prevent your
customizations to be overwritten when reactivating the BI content.
For example you installed the 0material info object and added some Z attrbites to it.
Again you are installing the Infocube 0IC_C03 it contains the 0material. At the time of
Infocube installation if you don't select the match X copy it will simply overwrite the
0material. You will lose the Z attributes.
If you select the match X copy it will merge the properties. You don't lose the Z
attributes. E.g.: Actual length 20, 0material installed and changed length to 40.
Again you are installing the 0IC_C03 if don't select the match X copy it will overwrite
the 0material and make length to 20.
If you select the match X copy it will merge the properties.

LO Extraction
Logistics
refer to
process of
getting a
product or
service to its
desired
location upon
request
which
involves
transportatio
n,
purchasing,
warehousing,
etc.

Main Areas in Logisitics are :

Sales and Distribution
(2LIS_11_VA*) Application 11, 13,
08 (LBWE)
Materials Management (MM):
Application 02, 03
Quality Management(QM):
Application 05

Extraction

Full Update

Delta

Full Load In case of Logistics Extraction, Full load/ Initialization will extract the data
from Setup tables (contains only historical data)
Why need to do Delta Update - So in order to capture the changes, you would need to fill
the setup tables every time, which will be a laborious task. So its always suggestible to go
for delta loads which makes loading life easier.
Initialization: Data will be fetched from application tables to setup tables using OLI*BW
T-Code or SBIW T-Code. In LO-Extraction, the extractor wont allow the direct
communication with the application tables.

5.
6.
7.
8.
9.

DB Connect vs UD Connect
Is Delta load possible with DB Connect
Blueprint document
FI Old GL vs New GL?
Steps for reports development from requirements gathering till final development?

References:
10. Multi-Dimensional data modelling in SAP BI
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-001052ac-a6e813c35a84?quicklink=index&overridelayout=true
11. http://letuslearnsapbi.blogspot.co.uk
http://letuslearnsapbi.blogspot.co.uk/search?updated-min=2010-0101T00:00:00%2B05:30&updated-max=2011-01-01T00:00:00%2B05:30&max-results=6

12. http://sapbifolks.blogspot.co.uk/