1

Business Content

1) what is business content? How is it installed?

Business content is used only for implementation projects.

Basically business content is a preconfigured set of rows, queries , IC’s , DSO’s ,

dtp , transformations etc.

The content has to be activated and installed if its matching customer

requirement.

For example after installing IC’s, how does the data get into it?
Answer: We need to move data from R/3 to the IC specified in business
content.

The content are delivered in version D. We should change from version D

to version A.

Installation of business content:

Note: This is related to sales distribution. SD

rsa1  BI Content  Click on InfoProviders by infoarea

 Identify the infoarea customer relationship mgmt OCRM
 Expand ERP analytics
 Expand OSD(technical name)

Observe content like IC’s,DSO’s,MP ,tables.etc.

Business content does not contain datasources .So activate this datasource in
R/3, replicate datasource in BW,create transformations on IC of BI and then
create dtp.

How to install IC from business content:

Assume that we dealing with SD data and we want to load Customers Infocube
i.e OSD_C01

Drag and drop OSD_C05 into the collected objects area

Observe the grouping options as below:

Grouping = Install Only Necessary Objects

This option will install only the necessary objects i.e

 2
infoarea and related infoobjects.

For example list of infoobjects is sales quantity

(OINCVD_QTY) , Material(OMATERIAL)

In Data Flow Before

This option transfer transformations , transfer rules &

infopackages.

For example, transformation OSD_C01 2LIS_01_S001

In Data Flow Afterwards

This option will transfer queries , templates , workbooks ,

MP’s,infosets etc that are available on top of IC.

For example query TopCustomers (technical name =

OSD_C01_Q023)

In Data Flow Before And Afterwards

This option will transfer all objects covered in all of the

above steps.

Now observe Install and Match Columns checkboxes while installing the business
content.

Install = Simulate Installation

Install

Install In Background

Installation And Transport

Match & Copy : If checked then the system takes care that our object(in
system) is not being overwritten by our enhancement.
 3
Collection mode = Collect Automatically (Default)

Start Manually

Display = Hierarchy (Default)

List

2) What is Match & Copy in business content?

Basically sap delivered business content is in version D which needs to be

changed to version A.

There are 2 types of Match a) Automatic Match and b) Manual Match.

Example of automatic match:

When u are installing business content (ex. sales content) and a particular object
of that content is already existing in your system then a tick mark can be seen
against it.

So the system takes care that the object is not being overwritten so that our
enhancement is not lost.

Example of Manual Match:

While installing business content, we have to manually tick mark the Match &
copy column in case the infoobject has different text in version A than version D.

NOTE: THE MATCH INDICATOR IS SET(CHECKED) BY DEFAULT TO

PREVENT ACTIVE VERSON A TO BE OVERRIDEN BY THE DELIVERY
VERSION D .

IF THE MATCH INDICATOR IS NOT SET THEN THE FOLLOWING HAPPENS:

A) Active version A is overwritten by delivery version D
B) When the install indicator is set.

i.e the delivery version is entirely copied into the active version.

3) Install Option (checkbox column)

If this column is checked then it means business content is already installed.

 4
Also if this column is checked and then we check the Match & Copy column then
it has no effect.

4) SD related sales content

(INTRVW)

IC’s used in Sales and Distribution.

Customers: OSD_C01

Deliveries: OSD_C02

Billing: OSD_006

Customers: OSD_C01:
Info Area: Sales and distribution analyses – sap R/3 SD(technical name = OSD)

InfoObjects: Base Unit of measure (technical name = OBASE_UOM)

Cost of incoming orders (technical name = OINCORDCST)
NetValue of incoming orders (technical name =
OINCORDVAL)

Material (technical name = OMATERIAL)

Queries: Sales Volume (technical name = OSD_C01_Q013)

a)restricted kf: Material
Distribution channel

b)Variable: sales volume

sold to party

Customer Statistics (OSD_C01_Q0030)

a) restricted kf: sold to party

Datasources: 2LIS_11_VA0HDR
 5
5) material management in business content
(INTRVW)

rsa1  BI content  supply chain management(OSCM)  Purchasing

IC’s used in MM Flow

Purchasing Data: OPUR_C01

Info Area : Purchasing (technical name = OMMPUR)

InfoObjects:

Characteristic IO:
 Business partner (technical name = 0VENDOR__0BPARTNER). It is a
navigational attrb
 Country (technical name = 0VENDOR__0COUNTRY). It is a
navigational attrb.
 Material Group (0MATL_GROUP)

Keyfigure IO’s.
 Actual goods receipt quantity (technical name =
0VENDOR__0BPARTNER).


c) Queries: Vendor comparison (technical name = 0PUR_C01_Q0013).

-- Vendor number

d) Multiprovider : Purchasing data (technical name = OSBO_MC11)

if reqd do queries given in multiprovider OSBO_MC11

e) Update rules:
0PUR_C01 2LIS_02_ITM
0PUR_C01 2LIS_02_S012

Vendor Evaluation : OPUR_C02

a) Info Area : Purchasing (technical name = OMMPUR)

b) InfoObjects:

Characteristic IO:
 Business partner (technical name = 0VENDOR__0BPARTNER). It is a
navigational attrb
 Indicator data to be can celled(technical name = 0REVERSEDOC).
 6
 Material (0MATERIAL)

Keyfigure IO’s.
 Point score 2 for compliance with shipping instructions (technical
name = 0SHP_INS_2).

c) Queries: Vendor comparison based on vendor evaluation (technical name

= 0PUR_C02_Q0022).

Variables used: Plant (OS_PLANT)

Purchasing Orgz

Restricted key figure: Purchasing orgn

Plant
d) Update Rules: Datasources: as given in BI, see in rsa5 / lbwe
for example : 2LIS_02_S013 , 0PUR_C02 2LIS_02_S013

6) Open Hub Destination.

It allows us to distribute data from BI systems to non sap data marts, analytical
applns & other applns.

It ensures controlled distribution across multiple systems.

OHD defines thee target to which data is transferred.

DB tables and flat files can also acts as OHD’s.

We can extract the data from DB to non-sap systems using API’s & third party
tools.

OHD contains information about data target—type of destination,the name of the

flat file/DB & its properties , field list & its properties.

BI objects like IC,DSO,IO,Infosets,data source can function as open hub data

sources(don’t confuse with data source).

i.e we can extract data from IC,DSO,Data sources,InfoSources,InfoSets,IO etc.

Note: water board , electricity board can be considered as marts which supply
data to GHMC.

So IO,IC,DSO etc send information to data marts.

 7
7) Procedure to work with open hub

rsa1  modeling  open hub destination  select IA  create open hub

destination  object type = infocube / data source / info source / IO

destination type = File / Database table / Third party tool

Database Table = /BIC/OH<Name of OHD>

In Field defn tab, I can see fields in my IC.

save & activate

8) R/3 Extraction

8-1 R/3 extraction is a process of extracting data from tables or applications like
SD/MM/RM or from third party tools into the BW system.

Each application will have its own setup tables to store day to day business
transaction data of your enterprise.

As part of extraction, sap has provided communication structures on standard

sap tables to enable data extraction.

8-2) Areas of R/3 Extraction:

 8
a) LO Cockpit extraction(In this we can do extraction for a variety of different
applications)

b)Generic extraction

c)FI extraction

d)COPA extraction

e)HR extraction.

Sap has provided communication structures on top of R/3 tables to enable

LOCockpit extraction.i.e nothing but SAP Tables for e.g VBAK

The basic steps are as follows:

R/3 tables  communication structures  datasource(extract structures) 
replicate datasource in BW  create transformation and dtp on IC.

The above shows the actual flow in R/3 to BW.

8-3) why do we replicate datasources ?

Ans: we replicate datasources so that they can be assigned to the infosources in

BW system.

8-4) what is Logical unit of work?

Logical unit of work (LUW) means a transaction must fully perform its database
operations or not at all.
For a database system, this constitutes a UNIT.

LUW helps in guarantee database integrity.i.e if a LUW is successful then the

database is in the correct state.
However if LUW fails then changes made to the database are rolled back.

A LUW will end when the following occurs:

a) When the database changes have been confirmed by database commit.

b) When the database changes have been canceled by using rollback .

A LUW will start when the following occurs:

a). Each time you start a transaction

b) When the database changes of the previous LUW have been confirmed
(database commit)
 9
c) When the database changes of the previous LUW have been cancelled
(database rollback)

Update Mechanism(V1 , V2 & V3)

V1 Update(synchronous update)

This is the first update which takes place.

For example when we create a sales order (VA01) and click save the underlying
tables are immediately updated.

This is possible because of V1 update. i.e data is posted to the application

specific tables using V1 update.

It is a synchronous job i.e it requires acknowledgement. i.e another user cannot

post a job until current record is processed.

V2 Update( Asynchronous update)

Here records do not follow an chronological order and underlying tables are not
immediately updated.

V3 Update( Batch Asynchronous Update)

This update is specifically used for BW extraction.
We have to schedule a job to perform V3 extraction
Here the data is collected in the order it was created and transferred into
the BW as a batch job.

Using V2 update record posted to extraction queue.

Now a collection run scheduled to post the records to delta queue using
v3 update.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/804165a5-
c081-2d10-39b4-af09a680f591?QuickLink=index&overridelayout=true

1-1)what is a data source w.r.t to R/3 extraction?

(IMP)

Datasource resides in source system. It contains fields that are waiting to be

transferred into the BW system.
Data is transferred from source system to BW through structures.
 10

A datasource contains the following:

Extract structures

Extractor Method

Extractor

Here Extract structure means a structure containing all the fields that are
available for Extraction.

Extraction method signifies the type of extraction whether Full or Delta. Extractor
will have the required logic for extraction purpose.

The Extractors can be categorized into

 Standard extractor
 Generic Extractor.

8-5) what are extract structures?

Ans :
Extract structures are basically sap structures that contain fields from R/3 tables.

The extract structures are basically present in R/3 system. Extract structures are
same as data sources.

For sales Header related data.

For e.g tcode LBWE  For example SD Sales BW  Extract structure =
MC11VA0HDR
Data source =
SLIS_11_VAHDR

se11  database table = MC11VA0HDR. This structure will contains list of fields
from underlying tables.
 11
8-6) Naming conventions asked in interview

2LIS _ Application component _ Event _ Suffix

LIS = Logistics

Application Component = 11 [ SD sales ]

12 [ Sales shipping ]
13 [ Sales Billing ]

Event = VA [Event VA means creating, changing or deleting orders ]

VB [ Event VB means creating, changing or deleting quotations ]

VC [ Event VC means creating, changing or deleting deliveries ]

VD [ Event VD means creating, changing or deleting billing

documents ]

Suffix = It details the datasource, what level of data is extracted etc.

HDR represents Header data,

ITM represents Item data,
SCL represents Schedule line data,
KON represents Conditions data

Extraction Structure = Extraction structure MC<Application><Event/group of

events>0<Suffix>;
where MC is derived from the associated
communication structures and <Suffix>
is optional

for example : MC11VA0HDR

Here M Indicates the following

MA (order)
MD (delivery schedule)
ME (contact)
MF (request)
 12
Setup Table = Restructuring table (= setup table) <Extraction Structure>SETUP

Example: Extraction structure : MC11VA0ITM

table: MC11VA0ITMSETUP
2LIS_11_VAHDR - MC11VA0HDRSETUP

8-7) what are setup tables? Or restructure tables.

Every extract structure has an associated setup table(also known as restructure

table).

It is a cluster table.

In the LO extraction process the setup table is filled with application specific data
(lbwe  11. SD sales) after the data source is activated and extract structures
are maintained.

For ex.

Lbwe  11 SD sales BW extraction structure = MC11VA0HDR

Data source = 2LIS_11_VAHDR

Setup table = MC11VA0HDRSETUP

Structure = MCVBAK

IN LO EXTRACTION PROCESS, SETUP TABLE HAS TO BE DELETED FIRST BEFORE

PERFORMING DELTA UPDATES.

THE TCODE TO DELETE SETUOP TABLE IS = lbwg. [Provide input application

number .i.e 11 for SD].

8-8) Why do we require to delete the setup tables?

(DELOITTE)

Setup tables by default contain preloaded data.

If we want to load our application specific data then we need to delete the setup
tables.

While performing LO Cockpit extraction(FULL LOAD) , setup tables are to be

deleted after the datasource is activated and extract structures are maintained.
 13
8-9) what is data source and what fields are there in data source maintenance
screen related to LO extraction?

A BW data source is a structure, which is created in the source system and

replicated to the BW system.

In the data source we can add/edit fields. If the data source is in LO Cockpit, we
can enhance the data source by adding custom fields using the tcode = RS02.

There are four types of Datasource:

1. Datasource for transaction data
2. Datasource for master data
i. Datasource for attributes
ii. Datasource for texts
iii. Datasource for hierarchies

Fields in Data source maintenance screen(LO Cockpit)

Data source name = 2LIS_11_VAHDR

Extract structure = MC11VA0HDR

Direct Access = D (Direct access not possible)

**Note: The data source maintenance screen contains the following

fields:
1) Field Name
2) Field Descp
3) Selection (The fields checked will appear in RSA3 )
4) Hide field (The fields checked will not be a part ofextractor )
5) Inversion – ( This is used in reverse posting . It is set to -1 )
6) Field only known in customer exit .

8-10) datasources you have used in R/3 extraction

Appln comp = 02 [purchasing (related to MM)]

Purchasing data header

DS = 2LIS_02_HDR

Extract structure = MC02M_HDR

Tables : MCEKKO
 14
Purchasing data item level

DS = 2LIS_02_ITM

Extract structure = 202M_HDR

Tables : MCEKKO , MCEKPA (purchasing partner roles) , MCEKPO

Appln comp No = 11 [SD sales]

Sales Header data

DS = 2LIS_11_VAHDR

Extract structure = MC11VA0HDR

Setup table = MC11VA0HDRSETUP

Tables : MCVBAK , MCVBAP

Sales Item data

DS = 2LIS_02_VAITM

Extract structure = MC11VA0ITM

Setup table = VAITMSETUP

Tables : MCVBAP

Appln comp No = 13 [Sales Billing document item]

Sales Item data

DS = 2LIS_13_VDOTM

Extract structure = MC13VD0ITM

Setup table = MCVD0ITMSETUP

Tables : MCVBRK
 15
8-11) LO Extraction process or LOCockpit process.
(VVIMP)

“ IN THE LO EXTRACTION PROCESS FIRST WE NEED TO PERFORM A FULL

LOAD.

BEFORE PERFORMING FULL LOAD WE NEED TO DELETE DATA FROM

SETUP TABLE(RESTRUCTURE TABLE).

REMEMBER SETUP TABLE IS USED ONLY ONCE IN LO EXTRACTION

PROCESS I.E DURING FULL LOAD. IT IS NOT USED IN THE DELTA
UPDATES.

AFTER FULL LOAD, WE SHOULD PERFORM DELTA UPDATES.

DELTA UPDATES CAN BE PERFOMED ONLY IN BW INFOPACKAGE

IRRESPECTIVE OF WHATEVER UPDATE MODE YOU SELECT IN R/3.”

Basically it consists of 2 different servers A) R/3 server B) BW server.

Tcodes used in R/3 server

LBWE  LO data extraction cockpit

rsa5  installation of data sources from business contents(select and

activate data sources.)

LBWG  delete data in set up table

rsa3  data source extract checker(used to test the data source i.e
standard / generic)

OLI7BW 

rsa6  data source enhancement.

rsa2  data source repository.

Steps a) to g) are done in R/3 system.

a) First install(activate) required data sources from business content. tcode

rsa5.
 16
Basically rsa5 is used to activate the desired data sources from business
content.
Here we have to activate 2 datasources. i.e one for header and
other for item.

rsa5  expand sap-R/3  Expand SD  Expand SD-IO(sales master data)

 position the cursor on the data source
 click activate data source

Now for sales item data follow the same process.

 Expand ur data source (for ex. 2LIS_11_VAHDR)
 position the cursor on the data source
 click activate data source

Note: when this step is performed the data sources will be activated
from D version to A version.

b) observe the datasources(extract structures) & application numbers provided

by sap related to SD.

11 = SD sales BW
12 = Shipping/Delivery BW
13 = Billing BW.

c) Maintain communication structures and extract structures. Tcode = LBWE.

There are 3 columns.

a) Structure Column [ contains Maintenance icon ]

b) Datasource column [ contains ds name ex. 2LIS_11_VAHDR ]
c) Update column [ specifies delta mode ]

FIRST OF ALL DEACTIVATE THE EXTRACT STRUCTURE BY CLICKING

ACTIVE BUTTON IN UPDATE COLUMN.

Note: when we deactivate the extract structure the type of request is

customizing.

In structure column , Click maintenance icon

 right side observe the communication structures and tables involved
 Select All from the dropdown list
 Select the fields reqd for Extraction and transfer to selections
(transfer to extract structures)
 click continue
 17

d) Datasource maintenance screen.

In datasource Column , click icon 2LIS_11_VAHDR  Specify the Transport

Request

Datasource = 2LIS_11_VAHDR

Extract Structure = MC11VA0HDR

Direct Access = D (Direct access not possible)

**Note: Observe the data source maintenance screen which consists of

the following fields:
1) Field Name

2) Short Text

3)selection

4)Hide field – unhide the fields we transferred from communication structure into
extract structure.

5)Inversion – record no considered

6)Field only known in customer exit : If field in present in customer-exit then

Uncheck i.e if the datasource is Enhanced by adding a extra field then check
this flag for the enhanced field. Then the system will not give dumps or
runtime error.

Save and generate the datasource.

e) now activate the extract structure which was deactivated in the step c).

In Update column , click Inactive button.

So this makes the extract structure again active.

f) Delete the setup table . Tcode = LBWG

specify application number . for example 11

 18
g) Fill the setup table using tcode OLI7BW (for sales) i.e setup table is only for
FULL Mode.
Provide salesorgn, company code etc.

Specify the name of the run , termination date and time(i.e when we want to
complete the process)

NOTE: while filling up the set up table, we must block our transaction so
that it is no affected.

Check the box “Block all Orders”

h) check the datasource in tcode = rsa3 (extractor checkor)

here we just check whether our datasource has the right fields with data.

specify the datasource name ( one for header and other for sales)

Requestid = <specified by system>

Data record / calls = 1000 <we can specify any value > i.e 100 * 10

Display Extr.Calls = 100 <we can specify any value>

Update mode = F(Transfer all requested data)

Click Extraction Button.

Note: data comes in form of packets.

Steps to be done in BW system.

Replicate The datasource(s).

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00c1f726-
1dc2-2c10-f891-ddfbffdb1a46?
QuickLink=index&overridelayout=true&46059229327085
 19

8-12) Various Update modes in LO Extraction process.

(VVIMP)

There are 3 updates modes in LO Extraction process.

a) Direct delta
b) SQueued delta
c) Unserialized V3

You explain based on the above diagram. Note the

sequence of numbers.

In R/3 system:

1) The billing documents are posted in V1 udpate to R/3 application tables.

2) Setup table is filled with data from application tables.

3) Now in FULL mode , the datasource is filled with data .

 20

In BW system:

5) The data source is replicated from R/3 into BW system. Now transformations
are created on the replicated datasource.

6) Now data transfer processes is created between the IC and the data source.

In R/3 System

7) Now for delta initialization(or delta load) we select any one of the
update method. In BW we set extraction mode= DELTA for the
infopackage.

8) Now the delta records are pushed into the delta queue based on the
update method we select in lbwe.

9) The data source is once again replicated from R/3 to BW.

Direct delta [ V1 update ]

Where do I set this mode:?

In the Tcode LBWE .

For example : lbwe  11 SD sales , Update mode = Direct delta

In this mode each document posted is transferred directly to the delta queue. i.e
extracted data(data extracted through communication structures) is posted
directly to delta queue using an V1 update.

The extracted data follows a chronological order i.e synchronous

process. i.e it uses V1 update.

So every document posted to delta queue results in one LUW which

results in overhead.

No need to schedule a job in direct delta update to transfer data to delta

queues.
 21
In between two successive delta initializations , we cannot post any
document. Only when the data is fully updated in BW only then we can
post the documents.

Benefits of direct delta (when to use this mode)

a) serialization of documents is ensured because records are transferred to
delta queue using V1 update.
b) For customers posting low volume of data this option is the best.
c) Extraction is independent of V2 update.

Disadvantages of Direct delta:

a) So every document posted to delta queue results in 1 LUW. If 10,000
documents are posted then 10,000 LUW’s are created and this can
terminate the application.

Queued Delta: ( V1 + V3 )
Unlike direct delta, in queued delta , 10,000 records are considered as 1
LUW.

Using V1 update mode, records are transferred from transaction to the extraction
queue.

Now the delta records are transferred from extraction queue to delta
queue using V3 update( job run).
So this is clearly and advantage as compared to direct delta.

New data can be posted during delta initialization so the downtime for
the init request is considerable reduced.

Benefits and Features of the “Queued Delta”:

a) Documents posted follow V1 update. So this ensures serialization.

b) For customers having high volume of data, this method is recommended

because hourly jobs can be
scheduled to push data into the delta queues(also known as update collective
run).

Unserialized V3: [ V1 / V2 + V3 Update ]

 22
Data is updated to underlying tables using the V1 update.

Now the extracted data is written to the update queue with an V3 update
module.
Now it is kept there until a collective job run transfers the data to the delta queue

This mode does not guarantee serialization of records posted to the delta queue
i.e order of records coming into delta queue is not the same in which they were
posted.

So when this mode is used one should not load data into ODS.

When to use this option:?

When the order of data is not important one can use this option.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5039632a-
c398-2d10-0aaf-97167a3de753?QuickLink=index&overridelayout=true

8-13) I have a standard datasource but it is not displaying the records?

(INTRVW)

Assume the ds is activated from tcode rsa5.

Ans: a) Make sure the setup table is deleted by running tcode lbwg.
b) Fill the setup tables.
c) Check the type of update mode being used.

After completing the above still the extractor is showing 0 records the
a) check if the timestamp is initialized properly.

8-14) what exactly happens when we activate the extract structure?

(IMP)

Note: Extract structures and data source both mean the same.

It creates a transport request.

The data source(restructure table) gets activated and is filled with data.
 23

8-15) what is significance of table ROOSOURCE in R/3 extraction?

(INTRVW)

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d07aa007-
84ab-2d10-46ba-a5a2679f0d7b?QuickLink=index&overridelayout=true

Note: The delta process (how the data is transferred) for the DataSource is
determined in the following tables
a) ROOSOURCE .
b) RSDS
c) RSOLTPSOURCE

Main purpose of this table

a) Identify whether datasource is capable of handling delta.(Field

DELTA)
b) Identify the extract structure is being used for the OLTP
datasource.(Field EXTRSUCT)
c) Identify whether the extractor supports early initialization (field
ZADD_ABLE)

In R/3 system , se11  database table  ROOSOURCE

When we activate the data sources from business content (tcode RSA5), the data
sources are activated from D(delivery version) to A(active version).

To check relevant details of the activated datasource, we check the entry in table
ROOSOURCE.

This table has the following fields:

a) OLTPSOURCE = data source (when activated its displayed in this field)

for ex. 2LIS_11_VAHDR

b) OBJVERS = oltp source version.(A after data source is activated )

c) Delta = ABR (after activation – complete delta with deletion flag via
delta queue)
 24
We will get DELTA = ABR once the data source has been successfully
activated. i.e this datasource is capable of handling delta’s.

[ABR = after before reverse image]

d) EXSTRUCT = shows the extract structure name for the corresponding
datasource.

e) ZADD_ABLE = ‘X’ means the extractor supports early initialization.

NOTE: Possible Modes of delta are as follows:

(INTRVW)

a) ABR = after before image

b) AIE / AIM = After Image
c) ADD = additive extraction(delta)

Consider following example. We have this record in db table.

Order Status Quantity

1111 Y 30

Now assume Quantity is changed from 30 to 40.

If DELTA = ABR,

Order Status Quantity Recordmode

1111 Y -30 ‘X’ (before Image)
1111 Y 40 ‘<blank>’ (after
image)

Q: If DELTA = ABR what are supported by the keyfigures. ?

Ans : Addition & Overwrite.

Q: Does it support loading to both infocube and DSO?

Ans : YES
If DELTA = AIE/AIM

11111 Y 40 ‘A’ After Image

 25
Q: If DELTA = AIE what supported by the keyfigures. ?

Ans : Overwrite.

Q: If DELTA = AIE does it support loading to both infocube and DSO?

Ans : Only to DSO

If DELTA = ADD (additive)

11111 Y 10 ‘A’ Additive Image Note: 40 – 30 = 10

Q: If DELTA = ADD what supported by the keyfigures. ?

Ans : Addition only

Q: If DELTA = AIE does it support loading to both infocube and DSO?

Ans : YES (in case of DSO Update Type = Addition )

If the sales order is deleted then we will get the below records as delta

11111 Y -30 ‘R’ Reverse Image

11111 ‘D’ Delete Image

Note : where do we find the ADDITIVE delta option while creating

generic delta?

rs02  click generic delta button  (radio button ) additive delta

8-16) tmxexfcs table.

(INTRVW)

Table TMEXFCS = Lo Cockpit : field data for communication structures.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1094e790-
1d93-2d10-17ba-8b559bf0f75b?QuickLink=index&overridelayout=true
 26
The interaction of communication structures and extract structures is controlled
by the table TMCEXCFS.

TMCEXCFS contains fields we selected in the communication structures. Also the

additional fields we select are also present.
This table has following fields.: CSTRUC – < source table name for e.g VBAK >
ESTRUC -- < extract structure name >

8-17) In which table are the update modes stored?

(IMP)

Table TMCEXUPD

Fields = MCAPP = Number of application = 11

Update_mode = O [ Serialized V3 update]

A [direct delta ]

B [ Queued Delta ]

C [ Unserialized V3 update ]

8-18) How to enhance datasource? Assume I want to add an extra field.

(VVVIMP)

Note: The process of enhancing standard datasources and generic datasources

remains the same.

After creating a generic ds, it will go and sit in rsa6. Then from there we can
enhance it.

Now lets assume we are enhancing standard ds 2LIS_11_VAHDR [appln no =

11 , sales doc header]

Steps In R/3 system:

 27
Scenario: Assume we are enhancing 2LIS_11_VAITM (sales doc item level data)
by adding MTART field(Material Type) from MARA Table.

a) check in LBWE(lo cockpit customize) whether the field is available

Under structure column, click Maintenance icon, check if the field exists.

If it exists then add the field to the communication structure.

Now no need to perform coding.

b) If the field is not available then do the following.

1) rsa6 --> double click on ds 2LIS_11_VAHDR

2) double click on extract structure --> MC11VAITM

3) Now add the custom ZFields

i.e click append structure and add the custom ZZfields

4) Now write custom code in customer exit

cmod --> ZQuery --> click create

provide description --> click save

It will ask for Package name and transport request

Now enter enhancment = RSAP0001

function-exit = exit_saplrsap_001

sample code is as follows:

Import parameters of FM [exit_saplrsap_001]

i_datasource = datasource name

i_isource = infosource name

 28

i_upmode = full / delta

Export parameters
Not available

Source Code:

Tables : MARA

Data : wa_2LIS_VAITM like MC11VAITM,

L_tabix type sy-tabix.

Case : i_datasource

When ‘2LIS_11_VAITM’.

L_tabix = sy-tabix.

Select single * from MARA where MATNR = wa_2LIS_VAITM-MATNR.

If sy-subrc eq 0.

wa_2LIS_VAITM-MTART = MARA-MTART.

Modify itab from wa_2LIS_VAITM index L_tabix.

Endif.

Endloop.

5) Now in datasource maintenance screen do the following.

In the selection column , check the custom field

In Hide column , Unhide the custom field.

In column Field known only in customer exit , check the box with
custom field

6) Generate the datasource.

7) Delete the setup tables i.e tcode lbwg  application component = 11

 29

8) Fill the setup table using tcode = OLI7BW

9) check whether ds contains data. Tcode rsa3 (extractor checkor)

In BW system

10) replicate ds

11) create transformations and DTP.

8-19) Update Types in BI

(VVIMP)

To perform delta updates we need to initialize the infopackage.

The following shows the various update types :

a) Early Delta initialization.

b) Full Update.

c) Delta Update.

d) Full Repair.

e) Build Initial Cumulative.

The update type is set in the Update Parameters tab page of

InfoPackage.

8-20) Concept of early initialization.

(VVIMP)

 Only specific datasources support early initialization . e.g. LO Cockpit

extractors

a) In regular initialization , while loading the setup tables we need to stop the
posting on R/3 side.
 30
But in case of early initialization we need not stop the postings on the R/3 side.
i.e using early initialization users can post records while filling data into the
setup tables.

i.e data is written to the delta tables / delta queue using early initialization.

The records posted will be available in the next delta run.

b) Early initialization is same as init without data transfer i.e it enable delta
queue and establishes the timestamp for the delta.

c) where to check for this option:?

 In Update Tab of infopackage

d) How to determine whether the extractor supports this option?

se11 (database table)  ROOSOURCE

 Fieldname = ZADD_ABLE

If this field has value ‘X’ only then the datasource supports early
initialization.

e) Steps to perform early initialization.

1) Run the infopackage with the option “ Early Initialization “.

2) Delete the setup table for the specific application component.
3) Fill the setup tables.
4) Now run the FULL REPAIR load in BW with year wise
selections for better performance and quick loading to BW.

Schedule Tab  schedule  repair with full request

Advantages of early initialization:

a) Downtime required to complete the initialization process is considerably

reduced.

Extractors supporting early initialization:

a) 2LIS_11_VAHDR
 31
8-21) FULL Update

When u run the infopackage with FULL update mode all the data from source
system will be pulled from ECC to BI.

8-22)Init without data transfer

(VVIMP)

Init without data transfer:

This is used only in the case where we need to perform delta.

It will initialize (create timestamp) for the delta.

This option takes very less time.

Timestamp is nothing but telling the system to start delta from here on.

Use this option when u want to load data historical data or don’t want to load
historical data.

8-23) Init with data transfer:

It will start picking the delta records from R/3 system..

This option is normally not recommended because it takes lot of time.

Also we cannot run init with data transfer after executing init without data
transfer. The system won’t allow us to do it.

Note: Initialization is a 1 time job. After we complete

the initialization process the delta radio button is
enabled.

8-24) DELTA PROCESS:

Create another infopackage , choose delta radio button in the update tab.
 32
Now execute the infopackage to pull the data which is changed after initialization.

8-25) FULL REPAIR OR FULL LOAD

To pull historical data after initialization without data transfer this option is
selected.
Where to see this option:?

In Infopackage(Main menu) schedule  repair with full

request

By specifying year wise selection criteria in data selection tab we can

pull partial historical records

If we don’t specify year wise options then it is assumed that we are

pulling the entire historical data.

NOTE: WHENEVER AN INIT IS DONE WITH /

WITHOUT DATA TRANSFER AN ENTRY IS
CREATED IN RSA7 (delta queue)

These records will be treated as delta records.

8-26) Build Initial Non-Cumulative

This update method is only available when you want to load data into a data
target that contains a noncumulative key figure.

8-27) Steps to perform initialization of extractor(datasource)

(VVIMP)
a) Stop posting on R/3 side.
b) Fill the setup tables for the specific application component.
c) Run init without data transfer.
d) Run the delta infopackage by choosing radio button delta in Update Tab of
infopackage.
e) Now run the FULL REPAIR load in BW with year wise selections for better
performance and quick loading to BW.
Infopackage(Main Menu)  schedule  repair with full request
 33

NOTE: INITIALIZATION CAN FAIL IF THE ODS REQUEST IS RED.

8-28) Reinitialization of delta

(VVIMP)

Reinitialization is done in the following circumstances.

a) when the datasource(extractor) is enhanced (by adding extra fields)

b) When we want to send data from ODS to cube.
c) When the init is corrupted (i.e it is showing old time stamp)
d) In ds maintenance screen, in the selection column , we made changes.
e) Source system upgrade.

IN REAL TIME WE DO NOT USE THE OPTION “ INIT

WITH DATA TRANSFER” BECAUSE IT TAKES A VERY
LONG TIME TO EXECUTE.

Steps to perform Reinitialization for datasource

a) Delete all active initializations

Schedule Tab  (Main menu) Scheduler  Initialization option for
source system
 select and delete the
existing init.

b) Now do the following

 Fill the setup tables.

 Run init without data transfer
 Run the delta infopackage by choosing radio button delta in Update Tab
of infopackage.
 Now run the FULL REPAIR load in BW with year wise selections for better
performance and quick loading to BW.
Schedule Tab  schedule  repair with full request
 34

generic extraction
8-29) why do we go for generic extraction?

Ans : we go for generic extraction when standard extractors are not available to
support our functionality.

So when we have custom tables and want to join data from several custom tables
then we go for generic Extraction.

generic datasource
There is no concept of setup table.
8.30) We can create generic datasource on the following data

Master data

Transaction data

Text Data.

8-31) what are the delta specific fields for generic extractor?
(INTRVW)

Timestamp
Calendar day
Numeric Pointer

Create a field in R/3 table of timestamp / Calendar day.

8.31) Various types of generic extractors(data source)

(INTRVW)
 35

Tcode for creating a generic data source is rso2.

There are three options to create generic DataSource. They are :-

a. View/Table

b. SAP Query

c. InfoSet

d. Function Module

If the extractor is delta capable then in R/3 it is

identified with the help of the field
“ ROCANCEL “.

delta in r/3 extraction

8-33) What is ROCANCEL?
(INTRVW)

ROCANCEL in R/3 is similar to ORECORDMODE in BW.

ROCANCEL is automatically part of datasource and its value is mapped to

ORECORDMODE in BW.

Possible values for ROCANCEL are: [same as values in 0recordmode].

‘’ after image
X before image
D Deletes the record
R denotes a reverse image
A blank character represents a record’s after image

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5080c337-
81e5-2c10-97af-8929424f3a4b?QuickLink=index&overridelayout=true

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a080ea68-
fba2-2e10-8cb7-d42d5bfba09c?QuickLink=index&overridelayout=true
 36
8.34) How to create a generic extractor(data source)? (FULL LOAD)
(VVIMP)

Assume we are creating a generic ds for customer i.e KNA1 table. We create a
view on KNA1(zbi_kna1) and then use generic ds to extract from view.

Also assume in BW it is FULL LOAD.

Steps in R/3 side:

a) create a view in se11 (table KNA1—select a few fields)

b) tcode rs02  Master Data Attributes = KNA1  click create

Application Comp = SAP R/3 IO

Provide descp

Provide View Name = zbi_kna1.

c) Click SAVE by specifying the package name and TR. So now the extract
structure is created.

Now observe the generic datasource maintenance screen

which is same as standard datasource maintenance
screen.

d) select the fields which we require. Click SAVE

**Note: Observe the generic datasource maintenance screen which

consists of the following fields:

This is same as standard data source.

1) Field Name

2) Short Text

3)selection

4)Hide field -- unhide the fields

5)Inversion – record is not considered

6)Field only known in customer exit : If field in present in customer-exit then

 37
Uncheck i.e if the datasource is
Enhanced by adding a extra field then
check this flag for the enhanced
field. Then the system will not give dumps
or runtime error.

Save and generate the datasource.

f) Test the ds.

Tcode is RSA3(Extractor checkor) . Provide ds name  click extraction button

g) Check if generic ds is available for replication . tcode RSA6  expand SAP R/3
IO  <find ur ds>

Steps in BW side:

Replicate the datasource.

8-35) when using generic extractor it is updating the table but not displaying the
records?
(INTRVW)

Ans : Make sure the timestamp is proper.

Make sure the delta safety upper limit is properly initialized.

8-36) How to setup delta in for generic extractor(data sources)

(INTRVW)

rso2  click generic delta button.

8-37) what is safety upper limit for generic extractor?

(INTRVW)

This field is used for delta specific records.

Suppose R/3 table contains a timestamp field based on which we are retrieving
delta specific records.
 38

Assume last delta extraction was at 12:00:00.

The next delta extraction begins at 12:30:00.

Now if is record updated at 11:30:00 but not saved until 12:35:00. In such a
case if the field ‘safety upper limit” is not set then this record is lost.

So in order to capture such records we set the field “safety upper limit” to large
value in order to accommodate delta records.

For example set the “Safety Upper Limit” field = 40 mins. So the next extraction
will began at 12:40:00.

8-38) How to get extractor name from tcode = se16.

(BELLSOFT)

Ans : tcode = se16

Tablename = ROOSOURCE

There is a column called EXSTRUCT which will show the extract structure name.

In table ROOSOURCE , to identify whether the extractor supports early

initialization
there is a field = ZADD_ABLE

8-39) Where I can see the field ROCANCEL for a particular datasource.?
(IMP)

OR

what is the use of tcode rsa2?

Ans: ROCANCEL is visible in the tcode RSA2 [ OLTP datasource repository ]

The column is “ Can.Field name “

It shows properties of the datasource.

For example : zpurchasedata (gemeric ds)

Extraction method = Q [extraction using abap query ]

 39

Extractor = INF_EKKO_EKPO [ I used an infoset in generic extraction ]

Extract Structure = < >

For example : 2LIS_11_VAHDR

Extraction method = F1 [ Function Modulerface ]

Extractor = < >

Extract Structure = < >

Can.Field name = ROCANCEL

Delta process = ABR

ZADD_ABLE = ‘X’ [ for early initialization ]