Step By Step Procedure of Data Extraction:
Data Extraction:
Extractor in a simple
terminology is used for extracting the data from various sources to BW. For
this purpose we have SAP pre-defined extractors LO extraction and customized extractors (Generic extractors).
Lo Extraction:
Logistics is an important
aspect in an enterprise and forming a core part of ERP Application. For every
application above started in table the applications such as Purchasing,
inventory controlling, Finance and Controlling, Sales and Distribution,
Material management, HR Management etc...
Generic Extraction:
Generic extractors are of 3 types:
1. Based on
table/view
2. Based on Infoset
Query [ sap query ]
3. Based on
Function module
If you have to get data from more than 1
table and also incorporate some logic then you would use a functional module
extractor. It is like a program where you would code using ABAP and have all
your logic incorporated.
Let us see the step by step procedure of LO Extraction:
First of all
Extraction can be used over in ECC.
The difference
of using SAP BI and ECC is that varies little interfaces differences namely
Client ID
differs, Information prescribed over is that differs.
Now Go to ECC.
Transaction code: “/nrsa5”
Installation of Data Source from
Business Content
The Installation of Business Content is
described that entire data sources of each and every module are presented here.
Each module represents the transaction and master data objects are represented.
As per Technical Specification, client or customer prefers what kind of specs
they need, we have to fetch that data sources to extract it to the report as
possible.
Here we have to check the module and
take the particular data source.
We have to check whether it active or
not. And we have to activate the data sources.
While completing the Activate data
sources we have to move the next Process.
Transaction
Code: “/RSA6”
Post process Data
sources and Hierarchy:
The Post process data sources and
hierarchy is used to check whether the activated data sources are available
here or not.
Now we have to check the data sources
are displaying or not. To view or display the data source we have to go to the
transaction code: “/nrsa2”
After displaying the data source, the BI Service API: Display Data Source has
been viewed. Then we shall analyze this interface how the data entities are
fetched in a data source.
The Next Step is to Process the
Transaction
Code: “/nrsa3”
It is the “Data Extractor Checker” ---- Here we can extract the data from the
data source object. And we shall check the data’s in a Grid View too which is
used to analyze the data also.
After selecting the “Correction Mark” the
Extraction has been generated automatically.
Extraction: Will Show the How many
records are selected.
Alv Grid:
List: List view displays the entire
records totally.
Log: Log view which represents the
log report for the user. It shows the Log information message.
Hence, the Extraction has completed we
need to go to “DATABASE WORKBENCH” BI SERVER. And then
Transaction
CODE: “/nrsa1”.
After Going to “DATABASE WORKBENCH”. We
have to go to Data Sources and “replicate
the data” in present module of data sources available.
Therefore after replicating data source
module part. Then we must “Migrate” the particular data source. Hence while
migrating the data source, and then it is easy to fetch it for an Info Package
properly.
After Migrating particular data source
name, the window will appear to ask whether we need the data’s in
Without
Export (or) With Export
We shall select the “With Export”. So
that the data can exported in timely manner. And then Data source was migrated
to the source systems.
After Migration, we must create the Info Package.
--------
After the “check” Entries, move to the extraction,
Processing, update, scheduling step by step.
While Scheduling the Info Package, it
will match the metadata [PSA –
Persistant Staging Area] to the data request. Hence the Info Package was created.
Finally we have find particular data
source, Data Store Object. Finding the data store object name. Have to create
the Transformations.
The same Process is to find the Info Cube, and create the Info Cube and
Transformations for it.
Hence while creating the Info Cube, as
like architecture of BI. Multiprovider must be created. Multiprovider can be
created accordingly from the Info cubes.
In Multiprovider, in orderwise DSO,
Infocubes are been generated.
As like the architecture of BI / BW, we
must create proceed accordingly to that. The Next step we must go ahead to the
Report Generation from the BEX Query Designer and BEX Report Designer.
