Anda di halaman 1dari 6


-> SAP BW and SAP ECC are 2 different Products or Applications which are indepen
-> Please do remember SAP BW is not one of the module on ECC like SD, MM, FI, CO
, HR, QM, PP...
-> Basically ECC is an OLTP system where we can process the Transactional Data.
-> We have many modules in ECC and it depends on the client to go with what modu
le they require as part of their business requirements.
-> All the modules in ECC are tightly integrated, because for example in SD when
we do the Goods Issue to the Customer automatically the Stock is reduced in IM.
-> In general depending on the requirements the customer will buy the license fr
om the SAP and try to implement the ECC system. As part of this the SD consultan
will try to configure the SD module and MM Consultant configure the MM m
odule like wise each module consultant configures the ECC systems as per their r
equirements. Once the configurations are done then the end user will enter the t
ransactions or postings in SAP ECC where in the data will be saved and stores in
ECC database. We as part of BW consultant we need to extract the data which was
entered by End users, Transform the data as required and load the data into SAP
BW system. Then we can do the reporting on the data loaded in to BW system.
-> In general Scenario(70%) there might be one ECC system for the small scale In
dustries, then it is enough to extract the data from the single ECC system alone
But there might be some situations where clients will have different ECC
systems based on the Business they have for example Plant wise, Region wise. Th
en we need to extract the data from different ECC systems into BW system.
-> Data is extracted from the source system(SAP R/3) and updated using a DataSou
-> When we extract the data from the Flat File or DB connect the procedure for e
xtraction will be same. But it is not the case with ECC extraction because
each module may have different procedures or diff types of extractors ba
sed on data centric to extract the data.
1. SAP R3 and SAP BW should be in a network(LAN, WAN...)
2. Source System Connection between SAP R3 and SAP BW. (SAP Connection Automatic
or Manual)
-> The main difference between the Flat File Extraction and SAP R3 Extraction...
- In case of Flat File when we assign the Data Source the Dataso
urce gets created automatically by defining the Transfer Structure.
- But In case of SAP R3 we have to login to SAP R3 application a
nd create a DataSource and bring(Replicate) the datasource to SAP BW and assign
datasource to the Infosource.
Note: SAP R3 is an OLTP appliation and have different functional modules like SD
, MM, FI-CO, HR, PP, QM....
But all these Functioanl Modules are broadly brought under three Funct
ional Areas like FI, HR and Logistics.
Depending on the type of Data you are trying to extract will be differ
ent for different functional areas.

Different types of Extractions from SAP R3 to SAP BW system:
Extractor: Extractor is nothing but the DataSource which is used for Extracting
the Data from Source System. Extraction is nothng but process to extract data.
There are 2 types of Extractors.
1. Application Specific - Data will be extracted based on
specific module or application.
2. Cross-Application Specific - Data will be extracted from different mo
dules based on requirement.
-> 1st preference we have to check if for Application Specific Extractors. If we
cannot find the Extractors in Application specific then we go for Cross-Appl.
(1). Application Specific:- Extractors developed by SAP or by customers themselv
es extract data from specific tables that are connected to a corresponding
application area. In Application Specific we have 2 types.
I. BW CONTENT EXTRACTORS: These are nothing but
Extractors that are delivered by SAP. But we cannot directly use them because th
ey will be in
delivered status and we need to convert them
into Active Status if want to use them. Applications that are included here are
SRM, LO Cockpit... The data will be extracted
from Application Specific DB Tables. (FI-AA, FI-AP, FI-AR, FI-GL, CCA, PCA, PC,
Extractors that are generated by the Customers based on some other Object. Here
SAP will not give the DataSource but there will be environment where we can gen
erate the datasource. Applications that are included here are LIS(Outdated), FI-
SL, CO-PA(Based on Operating Concern).The data will be extracted from Applicatio
n Specific DB Tables.
(2). Cross-Application Specific:- The data in generic extractors can come from v
arious sources, such as logical databases, cluster tables, and transparent
tables. This tool is not application-specific and can be used in
situations where the other types of extractor are unavailable. Cross-Applicatio
n Specific have 5 types.
V. DOMAIN (We use only for Text DataSource)
-> For any type of Extraction we have to follow the below process(aspects).
1. Procedure for Generating(Customer Generated)/Createing(Generic)/Istal
ling(Business Content) DataSource.
2. Delta Mechanism
- For any datasource we create, generate we have to identify whe
ther the datasource can be Delta Capable. Can we implement the logic for this da
ta source to return the delta records..? There might be some datasources such th
at there is no way they can support the delta or we can implement the logic for
the Extractor so that they can extract the delta records, in such cases we canno
t go with delta mechanism. Suppose if there is the Extractor that suports Delta
mechanism, then what is the logic of the extractor to identify the Deltarecords(
newly added or changed).
- If we do the Full, in IP it will be full because the IP will b
e based on the DataSource. If datasource supports delta then IP we can see INIT
DELTA and Delta. i.e If the IP is Delta capable means the DataSource should be d
elta enabled. If the datasource is Delta enabled there should be some logic behi
nd to identify the delta(new and changed) records. This is called Delta Mechanis
3. Delta Process (ABR, AIE)
- Once the delta records are identified how the delta records ar
e processed in the Delta process.
4. Initializing the data.
5. How to Enhance the DataSource(Only when required we go for enhancemen

-> DataSource is an object that defines the following objects.
1. Extract Structure(ES) - Source System(SAP ECC)
2. Transfer Structure(TS) - Source System(SAP ECC)
3. Transfer Structure in BW(TS) - SAP BW System
-> Also for any DataSource it should have ES, TS(SAP ECC), TS(BW), Source of dat
a, Delta Mechanism, Delta process.
-> When we say the Extraxt Structure, fields that has to be extracted from the d
-> When we say Transfer Structure, out of fields that are extracted what are the
fields that are transferred to BW.
- For example in the table we may have hundres fields but we may not req
uire all those fields, then we select the fields which are reqired for extractio
n. This defines the Extract Structure. Also the fields which are extracted may n
ot be required to transfer to BW, these fields define the Transfer Structure. Th
is can be done by Hide check box to exclude or hide the fields that are not requ
ired in Transfer Structure.
-> TS may be Subset of ES. But TS in ECC and TS in BW should be exact if not we
will get the errors.
Types of Data Sources:
1. DataSource for Transaction Data
2. DataSource for Master Data Texts
3. DataSource for Master Data Attributes
4. DataSource for Master Data Hierarchies
-> It would make sence to go with Generic first because we are creating everythi
ng and we can analyse how it is done then we can understand the Standard data
sources delivered by SAP.
-> Most of the Standard DataSources are based on the Function modules concept.
Why we are going for extracting the data in this method is we have the data in S
AP R3 tables and we need to extract them in to our SAP BW DataSource.

Login into SAP R3 -> SE11 -> VABK(Table)
-> Any Table which contains MANDT filed as mandatory then that is the Client Dep
endent Table. i.e Different clients will have different types of data.
-> SAP BW does not contain any Client Dependent Table, so we will never extract
the field MANDT into the SAP BW System.
Req: I need to extract the daata from VBAK table from SAP R3.
VABK(Sales Document: Header Data)
VBELN - Sales Doc Number
ERDAT - Date on Which Record Was Created
AUART - Sales Document Type
NETWR - Net Value of the Sales Order in Document Currency
WAERK - SD Document Currency

Step1: Field to Info Object Mapping.
- In this step we have to create the InfoObjects in the BW corre
sponding to R3 fields.
Step2: Make the InfoObjects ready.
yc_vbeln(Sales Doc Number)
- Char(10)
0calday(Date on Which Record Was Created) - dats(8)
yc_auart(Sales Document Type) -
yk_netwr(Net Value of the Sales Order) - Amount(1
5) - Currency
- currency
Step3: Create a DSO
Properly assign the Key fields and Data Fields.
The InfoObjects corresponding to the Primary Keyfields should be
placed as Keyfields in the DSO.
Step4: Create a InfoCube
Step5: Create an Application Component.
Step6: Create InfoSource. Create Communication Structure and connect this to DSO
with Update Rules.
Step7: Create the Generic DataSource in SAP R3 based on Transparent Table.
Creating a Generic DataSource in SAP R3:
Step7.1: Goto SAP R3 and the Tcode RSO2(Maintain Generic DataSource) or SBIW ->
Generic DataSource -> Maintain Generic DataSource
Step7.2: Here we have to use the Transaction Data type of DataSource
- Here we can expect a question like in RSO2 we have different t
ypes of DataSources i.e Transaction, Master Data Text and Master Data Attr.
Why are we not having Hierarchies here..? The Answer is since
SAP R3 is an OLTP system and it does not support any Heirarchies and hence we ar
e not having any option to create a DataSource of type Hierarchies.
Step7.3: When we create the DataSource we have different tabs available.
- Here we need to mention all three types of Descriptions i.e Sh
ort, Medium and Long Text. Where as when defining the Hierarchies it is mandatir
y to
give only short text.
- Application Component: What ever the Generic DataSource we are
creating we should assign(Designating) to the particular Application Component.
Step7.4: Since we are creating the Generic DataSource based in Table we select t
he View/Table and notice that all other methods(InfoSet, FM) are greyed out.
- Also here we notice that the 'EXTRACT STRUCTURE' is greyed out
which means that we don't create the extract structure and system automatically
- EXTRACT STRUCTURES is nothing but group of fields what we are
extracting from the Source System.
- Now the EXTRACT STRUCTURE is created automatically when ever w
e save the DataSource but with all fields initially. Since we have mentioned the
VBAK then the system automatically thinks that we are extracti
ng the fields from the table.
- DELTA UPDATE: Here Delta Update Check box indicates whether th
is DataSource is Delta update enabled or not.
- Here for every field there will be Selection and Hide Field op
- SELECTION - If want to extract the data based
in some selections. What ever the fields we want them in the data selection of
for those fields we have to select this
- HIDE FIELD - Hide plays on Transfer Structure.
All the fields for which we select the Hide Field check box, those fields will
not be available
in the Source System and Transfer struct
ure in BW also. We can customize the Transfer structure using this field.
- Now we have seen the Extract Sturcture in Source System.
Step8: Now Replicate the DataSource in SAP BW system.
-> RSA1 -> Modeling -> Source System -> Select the R3 co
nnection -> Right Click -> Data Source Overview.
- We cannot find the DataSource here bec
ause we have just created the DataSource in R3 System and has not yet replicated
it in BW.
-> Search for SAP Application Component and expand it. S
elect the Application Component where we actually designated our DataSource.
-> Now Right Click on it and Replicate the DataSource. I
t will Replicate all the DataSources in that Application Component.
-> When it is Replicating the DataSources it reads the M
ETADATA(Data about Data) or detailed information of the DataSource.
-> It also sets up parameterised Timestamp for the DataS
Note: We cannot assign a DataSource to multiple InfoSources. But one Inf
oSource can have Multiple DataSources.
Step9: Assing the DataSource to Infosource. (Select InfoSource and assign dataso
-> We can see the Transfer Structure in the R3 System only when we activate the
Transfer Rules in SAP BW.
Step10: Create the InfoPackage.
-> How can we make sure that the number of records that have come from R3 and re
cords received in SAP BW are same...?
- Search for the number of records in the table and the records
received in BW datasource.
-> RSA3 - Extractor Checkor - which is used for checking the number of records t
he data source has extracted.
-> The steps for creating the Generic Data Source from Table and View are same.
But we need to know in which scenario we use what.
-> We want to Extract certain data from R3 is available in single table then we
go for creating DataSource based on Table else if we want data to be
extracted from different table then we create a view on those ta
bles and we create the DataSource based in View.
-> If we need to join the tables with the help of a view atleast 1 field should
be common that may be key or non key field.
-> Also we can create a view on the single table also. This is advantageous over
creating the datasource on table directly.
-> There is nothing much difference between the View and Infoset Query. But tech
nical people use the view and functional people prefer Infoset.
-> Tcode that is used to create Infoset is SQ02.