Generic Extraction

RAJ ESH BUSI NESS I NTELLI GENCE
GENERI C EXTRACTI ON
CHAPTER 4
EXTRACTIONS

It is mainly used for extracting the data form other Source Systems
like R/3 etc.

DataSource: Defines as extract structure and transfer structure from
source system (like SAP R/3) and transfer structure from BW side.
ES -> What data to be extracted from source system
TS -> What data to be extracted from source system to BW. TS is a
group of fields which indicated how the data is coming from the source
system

BW R/3
L ES
E

TS T TS

SAP BW FLAT FILE

SAP R/3

SAP BW

1

TYPES OF EXTRACTIONS

APPLICATION SPECIFIC CROSS APPLICATION

BW CONTENT CUSTOMER GENERIC
EXTRACTOR GENERATED EXTRACTOR
EXTRACTOR

FI LIS DB VIEW
HR, CO FI-SL INFOSET
SAP CRM CO-PA FUNCTION
LO COCKPIT MODULE

APPLIACTION APPLICATION VARIOUS SAP
SPECIFIC SPECIFIC DB TABLES
DB TABLES DB TABLES

BASICS DELTA METHOD ENHANCEMENTS

2

GENERIC EXTRACTION

1. Why do you go for Generic extraction?
- When the data source is not readily available in the Business content
- Even if the Business content data source is available and it is already
being used up. And if we want to simulate the same kind of extractor,
we can go for generic extraction.
2. The T-code for creating Generic Extraction is RSO2.
3. We can create 3 types of data sources using generic extraction
- Transaction data
- Master data attribute
- Text
4. We can generate generic datasource using the following
- Table
- View
- Function module
- Infoset Query

STEPS TO CREATE GENERIC EXTRATION: (MASTER DATA)

1. Go to T-Code SBIW otherwise go to T-Code RSO2.

3

-> Select the radio button Master data Attribute, give name and click
on CREATE

-> Select the Application Component by pressing F4 (depending up on
the table which we are extracted). It is just like infoarea.
-> Give the Master data table name like MARA etc.
-> Give short, medium, long descriptions and click on SAVE.

4

-> It shows 4 options like
- SELECTION - > What ever the fields we select here those
fields can appear at DATA SELECTION tab of
INFOPACKAGE.
- HIDE -> What ever the fields we select here those fields
cant be appear in BW side.
- INVERSION -> This option is available for Key figures. It
takes ve sign to the existing values.
- FIELD ONLY -> This option also available for Key figures. If
there is any Enhancement for a particular field at that time
this is enabled.
So select whatever the fields we want as data selection and also to
transfer rules otherwise hide other fields and click on SAVE. Then it
says, Data source has been saved successfully.

(Here I selected some fields like MATNR, ERSDA, MATKL,MEINS)
5

-> Then go to BW side -> Create all the Infoobjects that we want to
extract to BW system.
-> Go to source system -> select R/3 to BW connection -> select your
application component which we selected while creating the generic
datasource and click on Replicate datasource.

6
-> Select your datasource, which we are extracted and select Assign
infosource

7

8

9

10

When we are seeing in the monitor it shows error. It shows the error
essage like the following.

m

Error message when processing in the Business Warehouse
occurred in the SAP BW when processing the data. The
error message.
r message(s) was/were sent by:
e dialog box and select the
ng text for further information.
ollow the instructions in the message.

Diagnosis
An error
error is
Documented in an
System response
The erro
Update
Procedure
Check the error message (pushbutton below the text).
Select the message in the messag
lo

F

11
When we click on ERROR MESSAGE it shows the following.

First see in the DETAILS tab in monitor then go to PSA and see in
which places the error may occur.

Record 1: Value '00107 ' for characteristic YMATKL does not
have the right internal format
Record 1: YMATKL: Data record 1 ('000000000000000038
'): Version '00107 ' is not valid

Record 4: Value '013 ' for characteristic YMATKL does not
have the right internal format
Record 4: YMATKL: Data record 4 ('000000000000000068
'): Version '013 ' is not valid

LIKE THIS IT SHOWS.

12
-> Go and see in the PSA also it shows like this if we select only error
records in PSA.

-> By seeing this error in PSA and error message in DETAILS tab, I
think that the variable YMATKL must start with a letter. So then go to
the Transfer rule for YMATKL and write the ROUTINE.

-> Click on change to infosource -> select transfer rule for YMATKL ->
select ROUTINE ->Click on CREATE -> write the code and click on
SAVE. The code is as follows.

DATA : NUM (20) TYPE C.
DATA : A TYPE C VALUE 'C'.
CONCATENATE A TRAN_STRUCTURE-MATKL INTO
NUM.
RESULT = NUM.

And again click on ACTIVATE.

13

-> And again SCHEDULE the infopackage. Then see the MONITOR.

***** THI S I S THE PROCESS OF LOADI NG THE DATA
USI NG FULL UPDATE *****
14

ALE DELTA

Now see loading data using DELTA UPLOAD. For this upload, if we
change any data that changes will be effected in BW while scheduling
the DELTA update. For that also first we can INIT delta. Now see the
procedure of ALE DELTA. First go to MM02 (Change the material
management) and do some changes.

-> Select the MATERIAL by pressing F4
15

-> Click on SELECT VIEWS and then select some views like BASIC
DATA1 etc.

16

-> Modify the records from the fields, which we extracted already to
BW side like BASIC UNIT OF MEASUREMENT, Material Group etc

17

-> After all modifications are done click on SAVE.
18

-> Go to RSO2 and select your data source for master data and click
on CHANGE

Go to DATASOURCE menu tab and select ALE DELTA
option.
19

-> Then it asks the TABLE NAME and CHANGE DOC OBJECT.

-> Here TABLE NAME is the table, which we extracted already.
-> And CHANGE DOC OBJECT is nothing but a field in that table. How
can we know that is the field that we are giving in the place of
CHANGE DOC OBJECT? [Go to SE11 and give the table name as
TCDOB and click on DISPLAY. Then click on CONTENTS.
20

21

-> Whatever the object shows here that can be taken here as CHANGE
DOC OBJECT.
22

-> Click on TRANSFER tab. Click on SAVE and again SAVE.

23

24
->Go to BW side and select the DATASOURCE and click on REPLICATE
DATASOURCE again.

-> Go to Infosource and double click on your transfer rules and click
on ACTIVATE transfer rules

25

-> Go to infopackage and SCHEDULE again by selecting the UPDATE
as INIT DELTA without data transfers.

26

27

-> It shows 1 from 1 record after init delta. That means that one
record is used for simulation means in order to enable delta we can
run the init delta option.

28

-> After completion of init delta successfully come back again and see
now DELTA option is enabled. Select the DELTA option and again
SCHEDULE the infopackage.

29

30

31

***** THIS IS THE ALE DELTA FOR GENERIC
EXTRATION FOR MASTER DATA *****

32
GENERI C EXTRATI ON FOR TRANSATI ON DATA

1. Go to T-CODE SE11 and select the radio button TRANSACTION
DATA and give the some technical name and click on CREATE button.

2. Give APLICATION COMPONENT, TABLE NAME and give Descriptions.
Then click on SAVE button.

33

3. Select the fields like master data otherwise click on hide. For
transaction data KEY FIGURES and REFERENCE are compulsory.
So select some key figures along with the reference values. And
then click on SAVE button.
34

-> Go to BW side and Replicate your datasource by selecting the
application component, which we already assigned in R/3 side, in the
source system tab.
35

-> Click on Assign infosource by the context menu of the your
replicated datasource

36
-> Create the infosource as flexible updated

37
-> Assign the transfer rules by selecting necessary infoobject related
to the object, which we extracted by clicking F4 for each and every
infoobject. And then click on ACTIVATE

-> Go to info provider and create infocube.

38

39

40

41

-> After the creating of infocube, create update rules for that infocube.

42

43
-> Go to infosource and select your datasource and create
infopackage.

44

45

46

47

***** THIS IS THE WAY TO CREATE GENERIC EXTRACTION
USING TRANSACTI ON DATA *****

48

TRANSACTI ON DATA USI NG GENERI C DELTA

1. In order do this transaction data using generic delta, first go to the
T-CODE VA02 in order to change sales orders related to SD (VBAK
etc). Select the order by pressing F4 and do some changes that field
may be the field, which we extracted already, or the other filed, but
the effect can occur on the extracted fields.

2. Go to ORDER QUANTITY and change the value. Normally price and
quantity gets net value. So change ORDER QUANTITY value and then
click on SAVE.
49

50

51
-> Go to RSO2 select your datasource and click on CHANGE. Then
select GENERIC DELTA

-> Give the time field in Field Nm and select Time stamp, click on
SAVE.

52
-> Click on SAVE and SAVE.

53

-> Go to BW side again replicated your datasource, ACTIVATE your
transfer rules and SCHEDULE your infopackage.

54

55

56

57
-> After SCHEDULING the INIT DELTA, Then select the option DELTA
UPDATE and SCHEDULE again.

58

59

THIS IS THE CREATING OF TRANSACTION DATA
USING GENERIC DELTA

60
GENERI C DATASOURCE USI NG TEXTS

Till now we created GENERIC DATASOURCE using MASTER DATA and
TRANSACTION DATA. Now see how to create GENERIC DATASOURCE
using TEXTS. For creating either MASTER DATA or TRANSACTION
DATA there are mainly 4 options to extract data. Those are
- Table
- View
- Function module
- Infoset
While creating the TEXTS, including these 4 another option is available
i.e.,
- Domain

-> We know normally TEXT contains LANGUAGE and DESCRIPTION.
So here also select the language and description and click on save and
upload that text datasource to BW side like MASTER DATA. Form here
onwards all steps are same. Nothing difference is there. We can upload
the data using DOMAIN also.

61

GENERI C DATASOURCE

62
Overview:

1. How many types of Exactions are there?
2. What is meant by Extraction?
3. What is the T-CODE for creating GENERIC DATASOURCE?
4. Why do you go for GENERIC DATASOURCE?
5. How many ways did you create Generic datasource?
6. How many ways did you extract generic datasource?
7. What is the difference between creating GENERIC DATASOURCE
using VIEW and FUNCTION MODULE?
8. When do you go for creating VIEW and FUNCTION MODULE?
9. What is the importance of SELECTION, HIDE, INVERSION and FIELD
ONLY check boxes?
10. Did you create Generic Extraction? If yes tell me the scenario?
11. Why do you go for ALE DELTA? And for which type of datasources
we are going for ALE DELTA?
12. How do you find CHANGE DOC OBJECT field for master data?
13. In which T-CODE did you change the data for MATERIAL MASTER
DATA?
14. What is the use of GENERIC DELTA? And when do you go for
GENERIC DELTA?
15. What are the different ways of setting up the delta in generic
extraction for transaction data?
16. When you setup delta for generic datasource, where does data
come from?
17. When you are setting up the delta in generic datasources, what
are the different images we can setup?
18. When I am setting up the delta for the generic datasource if I
select the update method a NEW ATATUS for changed records can I
load the data directly to the cube?
19. What is the difference between BUSINESS CONTENT
DATASOURCES and GENERIC DATA SOURCE?
20. What is DATA SOURCE?
21. When does the Transfer structure at SAP R/3 side get generated?
22. Steps to generate GENERIC EXTRACTION METHOD?

63
ANSWERS:

1. Two types
- Application Specific
- Cross Application
2. Extraction is nothing but loading up of the data from one source
system to the other source system.
3. RSO2
4. There are mainly two reasons for going GENERIC EXTRACTION.
- When we dont have any business content data source
readily available.
- Even if a business content datasource is available, and it is
already being used up and if we want to simulated the
same kind of datasource, we go for generic extraction.
5. Three ways.
- Transaction data
- Master data
- Texts
6. 4 ways
- Table
- View
- Function Module
- Infoset
- Domain (for TEXTS datasources only).

7. In VIEW the EXTRACT STRUCTURE is automatically created, but in
FUNCTION MODULE we must created the EXTRACT STRUCTURE
explicitly.

8. If there is 1:1 relationships then go for creating VIEW and if there is
1:M relationship go for creating FUNCTION MODULE.

9.
- SELECTION - > What ever the fields we select here those
fields can appear at DATA SELECTION tab of
INFOPACKAGE.
- HIDE -> What ever the fields we select here those fields
cant be appear in BW side.
- INVERSION -> This option is available for Key figures. It
takes ve sign to the existing values.
- FIELD ONLY -> This option also available for Key figures. If
there is any Enhancement for a particular field at that time
this is enabled.

64
10. 1. FUNCTION MODULE

To Extract Open deliveries: The datasource 2LIS_12_VAITM is
available as a part of business content extractor, all the delivery item
level information. So to extract only open deliveries we have built
generic datasource with function module. We used 3conditions to
identify an open delivery.
If delivery is consider to bean open delivery, if it has no PGI
(post goods issue) document.
If delivery is consider to bean open delivery, if it has PGI (post
goods issue) documents, and if this PGI document doesnt
contain billing document.
If delivery is consider to bean open delivery, if it has PGI (post
goods issue) documents, and if this PGI documents contain
billing document, and this billing document is not yet to be
posted.
We have a database table LIPS, which contains all delivery item level
information. So we collect all the records from this LIPS table and
cross check whether give delivery is open delivery or not. If it is open
delivery insert the record into E_T_DATA (internal table).

LIPS Delivery item level information.
VBFA sales Document Flow
VBRP Billing Document Item data.

2. VIEW
In SAP R/3 3.1v there is no business content datasource to extract
FI_AR information so we went about building the generic datasource
using the view built on two tables BSID and BSAD.
BSID Accounting: Secondary index for customers
BSAD - Accounting: Secondary index for customers (cleared items)
Some common fields in these two tables are COMPANY CODE,
CUSTOMER NUMBE etc).
11. When we are generating MASTER DATA delta we go for ALE delta.
If there is any changes in MASTER DATA those effects can also occurs
in BW side.
12. Go to SE11 Data Dictionary and see the table TCDOB by
selecting corresponding table.
13. MM01 creation of Material master data
MM02 Change
MM03 Display

65
14. When we are generating TRANSACTION DATA for delta we go for
GENERIC delta. If there is any changes in TRANSACTION DATA those
effects can also occurs in BW side.
VA01 Creation of SALES and DISTRIBUTION
VA02 change
VA03 Display
15. There are mainly 3 options available for generic delta. Those are

Calday if we setup delta on base of calday we can run delta
only once per day that to at the end of the clock to minimize the
missing of delta records.
Numeric pointer This type of delta is suitable only when we
are extracting data from a table which supports only creation of
new records, but not change of exiting records
Time stamp Using timestamp we can run delta multiple times
per day but we need to use the safety lower limit and safety
upper limit with minimum of 5 minutes.
16. RSA7 (DELTA QUEUE)
17. We can setup 2 types of images,
- New status for changed records
- Additive delta
18. NO. If the update type is setup to NEW STATUS for changed
records then it becomes mandatory for us to load data into ODS and
then ODS to CUBE.

66

19. In the case of business content datasource the datasource is ready
madely available in delivered version. In order to use it we have to
install that particular datasource to create a copy of the datasource in
active version by using RSA5 t-code, select the data source and click
on transfer data source. In case of generic datasource we are creating
our own datasources. We prefer business content data sources with
specific to performance.
20. Datasource defined ES and TS at source system and TS at BW
system.
21. When you activate transfer rules in BW, it creates a transfer
structure at SAP R/3 side.
22. Go to RSO2 -> selected the type of extractor to extract the data
from R/3 to BW- > click on create -> select Application Component
based on which type of data we are extracting -> give the name from
which we are extracting the data like table/view, function module,
infoset etc. -> give short, medium, long descriptions and click on save
-> select the field here and again click on SAVE-> go to BW side
replicate your datasource based on the type of application component
to which you are extracted.-> Assign transfer rules and activate->
create cube and updated rules -> go to source system and create
infopackage and schedule the infopackage.

GENERI C DATASOURCE

Converted to PDF for SAP Database.
67

Generic Extraction

Uploaded by

Document Information

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

Generic Extraction

Uploaded by

Copyright:

Available Formats

RAJ ESH BUSI NESS I NTELLI GENCE

You might also like