Académique Documents
Professionnel Documents
Culture Documents
SD
MM
FICO
HR
PP
In r/3 extraction unlike flat file , data source is created at the r/3 side and
then its getting replicated to the bw side.
for flat file we will have for datasource : transfer structure of BI(psa)
EXTRACT Structure : Grouping of logically related fields in which format data has
to be extracted to BI from the source system.
TRANFER strucutre of Source system: Grouping of logically realted fields in which
format data has to be transferred to BI system.
Extract strcture - hide fields = Transfer structure of
source system.
Only step of creating the datasource is done in the r/3 system , rest all are done
at the BI side.
Step 3: Once data source is created an extract structure (100 fields) will be
created.
Step 4: I will hide 10 fields in the extract structure and will replicate it( will
be done in BI system)
This replication will create transfer structure in the BI.
with 90 fields.
Step 5: Activate the transfer strcture. This activation will lead to creation of
trasnfer strcutre at the source system level.
Transfer strcture
Extract structure
VBAK
Step 6: Next step is create the data target or use the BI content to activate the
data target required.
============================================
TYPES OF r/3 extraction
============================================
1) Generic extraction
A) Based on table
R/3 has around 4,50,000 tables.
Its based on any one of the table. Here you cannot use more than one
table.
The table can be customer defined or sap provided.
ex: VBAK etc.
B) Based on view
If we want to extract sales header and items data , these data are
stored in different tables at the r/3 side.
VBAK and VBAP.
In that case if we want to extract the data from more than one table,
we go for view.
To join tables there should be common field( primary key) if not its
not possible to join.
All event related tables will have a primary field. I mean to say if we
are going for sales all sales table will have
common field.
Production planning is one more event but sales and production tables
may not have common fields which makes joining them
impossible.
Def:
Whenever we want to extract the data by writing some abap code(by
implementing logic) we use function module.
When we pull the data using info package the information structure table
doesn't has data to give it to BI.
For information structure table to get data we need to do the statistical
setup i.e if we do like that entire order related data
and delivery related data come and store in the Information structure table.
In LIS we can extract total event data ( sales, orders) not particular level
3) LO extraction
Logisitics extraction
The link to the ready made extraction structure is given from something
called as setup tables.
4) CO-PA extraction
Unlike other department, finance department has integrations with all the
departments.
==================================================================================
r/3
R/3 has ready made tables and fields.R/3 comes with almost 4 and half lakh
ready made tables
ECC 6 is the later version of r/3.
KNA1 : customer master data table : 0CUSTOMER ( ready made infoojbect which
we can use in BI side whenever we want to extract the data from
the KNA1 table)
How this gets updated is it is done by the end user. May be by BPO
employees.
Transaction tables
------------------
==========================================================================
Usually u use generic when the ready made tables does not satisify the
customer requirement.
or
select tranaction data and give datasource name.Give name which starts
with Y or Z.
ex: YDAS_SOH ( sales order header) and click on create.
Step 5: select option as extraction from view and give the table name VBAK.
Whether we are extracting for the first time or second time data is
coming from the VBAK table i.e the source table.
Here in the source table records with versions are not maintained like
modified,deleted etc. So we should always update our
data to a DSO from there to the cube.
a) calendar day
b) Time stamp
c) numeric pointer
Step 7:
A) Selection
This selection is not for your transfer structure.
This selection is for selective loading.
In infopackage there is tab called as data
selection,that is where this will help.
By default if u dont select any field at the
datasource level u will not have any option of giving values
at the infopackage level.If you do selection
then u will get the option of giving values.
B) Hide fields
Extract structure - hide fields = trasnfer structure.
C) Inversion
Inversion will be enabled only for key figures.
The value of before image will be multiped by -1 when
u select this check box for the key figure.
WHen this gets mulitplied is when u transfer the data
froom r/3 to BI.
D) Field only
This is used for coding person like in customer exit.
Now u will not find your datasource over here as its not
replicated yet.
So right click on the application component and click on
replicate metadata.
A) as datasource
This is for 7.0
B) as 3.x datasource
If i give this option then i will not be able
to use the datasource without migrating it to 7.0
You can also see that this datasource looks
different from 7.0 datasources.It will have a small
box in front of it. This datasource is
also called as emulated datasource.
Means it can be used only for older
versions.
If it is emulated datasource u have to perform
migration.
Steps to migrate it are very simple. Just
select the datasource right click and click on migrate.
W/O export
this is used if u dont want to make
it get migrated back to 3.5
Go to BI content tab
First select grouping options
Then collection mode
Other way instead of drag and drop is click on the infoboject which is
at the right side of the transformation and then
click on add fields and u will get a window with the list of all
fields. select the required fields and click on transfer values.
Automatically line will be drawn from the infoojbect to the field.
Step 6:
Full update
Initialize delta process
Initialization with data transfer
We will get the data and also time stamp will be
maintained at the table level
Init simulation without data transfer
No data will be trasnferred only time stamp will be
maintained
Early delta initialization
Real time we use Initialzation with data transfer for the first time.
First time when we run we will not see the option of
delta update. Only when we run the infopackage with above option and in
the second time we get the option of delta update.
Again if u go with intialization with data transfer again all data will
be loaded hehe.
Tcode to check time stamp is RSA7 -- obviosouly in the source system r/3
Find your pointer and click on the status symbol it will show the current
status i.e day.month.year hh.mm.ss
That is this was the last time data was extracted from the source system.
========================== LO EXTRACTION
=================================================================
Using LO we can extract entire logistics related data i.e sales, production,
inventory i.e where all materail moves.
The link to ready made extract structure is given from setup tables.
Setup tables are also readymadely given. They are application specific
tables. For sales one setup table will be there and for
production one setup table will be there.
Setup tables will have 3 partitions, header part , item part and schedule
line, based on what data is required choose the datasource.
VBAK -->
Setup tables --> Extract structure
VBAP -->
When we trigger the info package the data has to be extracted from the setup
tables , but will there be data in the setup tables ? no
Data has to be pushed from the base tables (VBAK , VBAP etc) into setup
tables this is called as staistical setup.
Data source:
Any LO datasource starts with
2LIS_<APPLICATION COMPONENT NUMBER>_<events><HDR>(each
event will have levels like HRD , ITM , SCL)
2LIS_<APPLICATION COMPONENT NUMBER>_<events><ITM>
2LIS_<APPLICATION COMPONENT NUMBER>_<events><SCL>
Extract structure:
Any extract structure starts with MC<Applcn component
number><event>0<HDR or ITM or SCL>
Ex: MC11VA0HDR
Setuptables:
<Name of E.S>SETUP
Ex: MC11VA0HDRSETUP
SITUATION 1:
Standard table assume has 100 fields and extract structure
given is having 10 fields.
I am not satisified with number of fields in the extract
strucutre and i want to add few more fields.
To do that I have to go with an option called maintaining
extract structure and that is done in LO COCKPIT.
SITUATION 2:
As we know that standard table fields are giving by sap
readymadely. If we feel that they are not enough
and we want to add few more fields to THE SAP GIVEN TABLE
ITSELF
Tcode is RSA7.
2) V2 (Asychronous update)
Data gets update and u will not get any feedback.
Here the updation happens in the front end(not in the
background) so performance issue.
Create transformations
Create infopackage
Create DTP
===================================================================================
===============
LO EXTRACTION PRACTICALS
Scenario over here is to loading to the cube which gives sales overview
which includes sales header and item
billing header and item
delivery header and item
STEP 2 : LBWE
Click on maintainence and select the fields for your extract strucutre
if needed.
After this you can see that extract strucutre status is red, because
it has been modified and not informed to the datasource.
Also by default the field only column will be ticked for those
enhanced fields, what SAP thinks is u will be adding some code
to those fields, u can uncheck it
Next comes the main thing inversion, by default for the key figures
the inversion will be enabled, and if u have added a new
key figures and if inversion is not enabled, click on unhide first and
then scroll up and scroll down then u see the check box
allowing you to check it.
FINAL STEP SAVE UR datasource, now u can see it has become RED to
Yellow.
There might arise a question of how to add the fields to the already
existing database table.That is done using append structure
and when u click on the extract structure enhancement, what u can find
is not the field names but the append structure name.
Then we write the customer exit to populate the values to those
fields.
OR
Give the name of the run, you can give any name you want. Give some
date and time in the future.
Dont click on the execute button, it will be executed in front end if u
do so. What u have to remember is the front end
execution is V2 update, that is it makes the application idle, so go to
programs and click on execute in the background.
That is what is done all the time.
You have to give the output device name, what this window means is if u
want to print your sales order u can print it, but
we are not printing the hard copy of the sales orders we are instead
transferring it into the setup table, so what has to be done
is we should ask the basis consultant for the output device name and
enter it.
In the demo systems it will be LP01, but not in real time.
Next pop up windows ask when you want to run it , the normal scheduler
windower, i.e you want to run it some point of the time
or immediately.
Now when u give immediately and save, u can see at the bottom where it
specifies the background job name. Double click on it
and copy the job name.
Go to tcode sm37(background job log) give the job name and see the
status.
Once this job is done the process at the R/3 side is over.
Next we can also see that there will be delta update button
option in the info package, so next load on we go with delta
update.
DELTA QUEUE
Before executing the info package if u check at the r/3 side at
the RSA7 u will not have a delta queue for the datasource
for which u are running.
Delta queue will have 2 partitions, one is delta part and other
is delta repetation.
When delta records are updated to the delta queue they are kept
in both delta and delta repeation partition.
When we run the info package the data records are moved from the
delta partition into the PSA ( they are emptied from
there), still the delta repetation partion will have delta
records in it
a) delta
b) delta repetation
If the first run is succesfull and in the second run, new delta
records are added to the delta partition part and
delta repeatation partition.
Ex:
Delta repetation Delta
Now above what we can see is how the delta recors are stored.
In the first delta update, both partitions will have records and
after the infopackage run, delta partition will have
0 records but delta repetation partition will have 5 records.
On the second delta update, delta partition will get new delta
records i.e 10 records, whereas now delta repetation
partition will get new records i.e 10 records also it wil retain
its old 5 records of the last delta update.
Now the job is to update this to delta queue so that delta queue
will have the record.
How to do that is through the V3 job.
Start date
When u want it like immediate, hourly, daily etc give that
parameters
Print parameters
Same as old thing LA01 is for dummy system, this u will get
from basis team
Schedule job
click on it to schedule the job
Job overview
click on it see the overview of the job. Here u will see
job has been finished
That means earlier delta queue was empty , now it will have 1 entry.
Now if u check the extractor queue it will be having
no pointers.
U can look at the data by clicking on the RSA7 queue name and click
on delta part or delta repetation part.
Now create a delta infopackage and select the option delta update and
see the records in BI system.
===========================================================================
Datasource enhancement comes into picture when we want to add fields to the
ready made SAP table.
STEP 1:
When we want to add a field to a table we should first go to the
communication structure.
Click on append structure. Now click on append new in the window which
has opened
The fields which u add always start with zz. here we are adding profit
centre ZZPCTR.
Give the fields and data type and descripiton. Then click on save and
activate it.
Once the object has been activated, the append strucutre will be
visible at the bottom in the communication structure which we
used to create the append structure.
The field which we have added that data will be avialble in some other
table, we should go and look for the code and
populate from that table.
STEP 2:
Create a project - tcode is CMOD
Give some project name and select the checkbox enhancement assignment
and click create
One will be for transaction data, master data texts, master data
hierarchies.
The names will be like EXIT_SAPLRSAP_001 [transaction data]
EXIT_SAPLRSAP_002
===================================================================================
==============================================
CO-PA EXTRACTION
Unlike other departments, finance departmenet will have interaction with all the
departments.
Operating concern :
Finance people will be using this.Its the top most legal entity where
all the finance data is updated.
Visualize the operating concern as cube, all the normalized data coming
and sit here
A) cost based
Product based industry use cost based
B) Accounting based
Service based industry use account based.
For dummy systems the Operating concern name will be IDEA. So CE1IDEA
is the first table name.
Then select the radio button create also give operating concern
also select the radio button either cost based or account
based
Finally click on execute.
Below also find all the fields. Which fields you want for extract
strucutre select it and then click on info catalog button
what happens whatever the fields selected there will come to the
extract structure.
===================================================================================
================================
go to se11 --> ROOSOURCE and give the datasource name, and check your
delta process.
===================================================================================
==================================
BI CONTENT