Bi 1003 - Data Extraction - V2

BI1003 Data Extraction v2.
India SAP CoE, Slide 1
Data Extraction
1 2 3 4 5
PrepareMe TellMe ShowMe LetMe HelpMe
Data Extraction
1 2 3 4 5
PrepareMe
In this course, we will cover 3 main sub-topics : - Purpose - Use - Challenges
Purpose
This course demonstrates the various data extraction methods. Extraction Methods covered Business Content Extraction from SAP R/3 LIS & LO Extraction from SAP R/3 CO-PA and FI-SL Extraction Generic Extractors Flat File Extraction UD Connect, DB Connect, SOAP Based and Open Hub Extraction DataSource Enhancement
Use
In many organizations, data is fragmented and spread across many databases and applications. To be useful, data must be integrated, standardized, synchronized, and enriched typically through ETL (extraction, transformation, and loading) processes. SAP BI provides a broad set of ETL capabilities that support data extraction. With the open interfaces of SAP BI, data can be loaded from virtually any source and can handle the huge amounts of transactional data typical of the enterprise landscape. Thus extraction deals with extracting the data into the BW system for analysing and reporting.
Challenges
To extract large volumes of data from SAP R/3 by defining delta management Modifying the already available Business content and satisfying user needs Integrating data from non SAP systems into BW
Data Extraction
1 2 3 4 5
PrepareMe TellMe ShowMe ShowMe LetMe HelpMe
Data Extraction : Overview

BI Content Extractors Datasource Enhancement
LO Cockpit
DB Connect, UD Connect and SOAP based
FI-SL Extractors Flat File Extraction CO-PA Extractors
Generic Extractors
Process Flow
InfoCube
Update Rules
ODS
Order-Deliv. Order Delivery
Update Rules Transfer Rules
PSA
DataSource
Order
Delivery
DataSource
OLTP System Data extract

Data extract
Process Flow
The data flows from the OLTP system to the PSA tables without any transformation. If any transformation or filtration is required in the data it can be done in the update rules and transfer rules. Then the data is loaded in the data targets like ODS. An ODS object acts as a storage location for consolidated and cleaned-up transaction data. The data from multiple ODS is then loaded into InfoCube and thus available to generate reports. In this example, Order and Delivery Data are extracted separately, and populate separate PSA and ODS tables. The data is then merged within the ODS to form a new ODS object storing combined Order Delivery data. The data then updates the InfoCube with Order Delivery data.
Multiple Source Systems
Types of Extractors
Types of Extractors
Application Specific
Cross Application
BW Content Extractors HR CO SAP CRM SAP CRM LO COCKPIT Application Specific DB Tables
Customer Generated Extractors LIS FISL COPA Application Specific DB Tables
Generic Extractors DB View Infoset Function Module Various SAP DB tables
FI FI
Types of Extractors
Extractors mainly are of two types: Application Specific Cross Application Application Specific Extractors consist of BI Content Extractors (LO Cockpit) Customer Generated Extractors (CO-PA, FI-SL and LIS) Cross Application Extractors consist of generic extractors (based on Database table, Infoset and Function module)
Business Content Extraction

Types of Extractors
Cross Application
Customer Generated Extractors
Generic Extractors
FI FI
LIS DB View Business Content Extractors: FISL Infoset Application Specific Extractors that are activated when COPA Function business content datasources Module are Application transferred Various SAP DB tables Specific DB Tables
Business Content Extractors

SAP provides extractors for almost all applications. They are provided as an add on with the Business Content. For each application like FI,CO and HR there are specific tables in the OLTP system. BI Content extractors consist of extract structures which are based upon these tables and thus can be used to fetch the data in BW. Hence when any company implements application like FI, CO it can directly use the already available BI Content Extractors without the need to create their own. SAP delivers these objects in Delivery version (D) and we need to convert them in the active version (A). Business content DataSources from a Source System are available in BW for transferring data only after you have converted them into the active versions in the source system and replicated them.
Uses of BI Content Extractors

Built in Extractors High coverage (Applications and Industries) Available for both Transaction and Master data Ready to use Reduce implementation Costs and efforts Delta capable
LO Data Extraction : Overview

Types of Extractors
Cross Application
FI FI
LO Cockpit
Logistics Customizing Cockpit provides a simplified way to extract logistics data and transfer it to SAP Business Information Warehouse.
LO Data Extraction : Data Flow

As shown in the figure the document data for various applications like Customer order, delivery and billing is first transferred to various Communication Structures. These communication structures are used to form various extract structures in R/3 which consist of various DataSources like 2LIS_11_VAHDR, 2LIS_11_VAITM etc. These DataSources then can be replicated to BW and assigned to Infosources. Then by creating transfer rules and update rules and defining the transformation the data is loaded into various data targets like InfoCube and ODS, thus available for reporting.
V1 and V2 Updates
V1 Update Synchronous Update If you create/change a purchase order (me21n/me22n), when you press 'SAVE' and see a success message (PO.... changed..), the update to underlying tables EKKO/EKPO has happened (before you saw the message). This update was executed in the V1 work process. V2 Update Asynchronous Update If you create/change a purchase order (me21n/me22n), when you press 'SAVE' it takes few seconds to update to underlying tables EKKO/EKPO depending on system load. This update was executed in the V2 work process. V3 Update has now replaced V1 and V2 updates.
V3 Update Modes in LO Cockpit

There are four Update Modes in LO Extraction
Serialized V3 Update Direct Delta Queued Delta Un-serialized V3 Update
Serialized V3 Update
R3 system SM 13 Application specific customer exits Update Tables Periodic Job BW System
RSA7
Transaction tables
BW Delta queue
Delta Load
Staging Engine
Serialized V3 Update
Transaction data is collected in the R/3 update table Data in the update tables is transferred through a periodic update process to BW Delta queue Delta loads from BW retrieve the data from this BW Delta queue Transaction postings lead to:
Records in transaction tables and in update tables A periodically scheduled job transfers these postings into the BW delta queue This BW Delta queue is read when a delta load is executed.
Direct Delta
R3 system Application specific customer exits BW System
BW Delta queue
Delta Load
Transaction tables
Staging Engine
Direct Delta
Each document posting is directly transferred into the BW delta queue Each document posting with delta extraction leads to exactly one LUW in the respective BW delta queues Transaction postings lead to:
Records in transaction tables and in update tables A periodically scheduled job transfers these postings into the BW delta queue This BW Delta queue is read when a delta load is executed.
Queued Delta
R3 system LBWQ Application specific customer exits Extraction queue Periodic Job BW System
RSA7
Transaction tables
BW Delta queue
Delta Load
Staging Engine
Queued Delta
Extraction data is collected for the affected application in an extraction queue Collective run as usual for transferring data into the BW delta queue Transaction postings lead to:
Records in transaction tables and in extraction queue A periodically scheduled job transfers these postings into the BW delta queue This BW Delta queue is read when a delta load is executed.
Un-Serialized V3 Update
R3 system SM 13 Application specific customer exits Update Tables Periodic Job BW System
RSA7
Transaction tables
BW Delta queue
Delta Load
Staging Engine
Un-Serialized V3 Update
Extraction data for written as before into the update tables with a V3 update module V3 collective run transfers the data to BW Delta queue In contrast to serialized V3, the data in the updating collective run is without regard to sequence from the update tables Transaction postings lead to:
Records in transaction tables and in update table A periodically scheduled job transfers these postings into the BW delta queue This BW Delta queue is read when a delta load is executed.
New LO Data Extraction : Why ?

Performance and Data Volume Detailed extraction: You can deactivate the extraction of, for example, scheduling data ('thin extractors' lead to small upload volumes) Document changes: only BW-relevant data changes are updated (smaller upload volumes) LIS tables are not updated: Reduced data volumes due to removed redundant data storage Update with batch processes: No overload of everyday work'

Simple Handling BW Customizing Cockpit: Central, single, maintenance tool for Logistics applications No LIS functionality: No knowledge of LIS Customizing update settings, etc, required Function enhancement: Creating simply and without modifications Others Delta tables (SnnnBIW1/-2): duplicated update, duplicated
data storage

Types of Extractors
Cross Application
FI FI

In response to demands from the customers, SAP has designed the reporting facility in certain parts of the R/3 system in such a way that it can be easily customized to meet customers requirements. The Business Information Warehouse must be able to process this data, with the result that it must be possible to define generic extractors in certain applications. These applications are the
Logistics Information System Profitability analysis Special Ledger
LIS Extraction
Types of Extractors
Cross Application
FI FI
LIS Data Extraction
LIS Data Extraction

The LIS data flow can be described as follows: Operative transaction data (sales orders, billing) is stored in application data tables (for example VBAK/VBAP for sales orders) The information is transferred from an operative document to the Communication Structures (for example MCVBAK,MCVBAP) to update the data in the LIS). These R/3 Communication perform the same function as the BW Communication Structures, but they fill LIS InfoStructures in R/3 with data and not cubes in BW. The update rules write the information from the Communication Structure to the corresponding Information Structures.
LIS Data Extraction

Although the term InfoStructure is used in R/3, the InfoStructure is a real transparent table and not the structure which contains data only at run time. LIS has many reporting tools like ABC analysis, correlation, graphical displays but the limitations of the schema with only one table makes reporting slower than it would be in BW. Thus in the LIS Extractor the data is transferred from the LIS InfoStructure in BW. LIS extractors are now obsolete and replaced by LO Cockpit.
FI-SL Extractors
Types of Extractors Application Specific Cross Application
FI FI
FI-SL Extractors
FI-SL is an application in which data (planned and actual) from different levels of OLTP applications is combined to measure business performance. FI-SL includes planning functions and reporting tools. FI-SL reporting in SAP R/3 is however restricted by the following :
Cross application reporting is not diverse The OLTP system is optimized for transaction processing and a high reporting workload would have a negative impact on the overall performance of the system
The solution to the above limitation is FI-SL Reporting in BW.
Uses of FI-SL Extractors

In FI-SL one is able to use alternate chart of accounts (operative, group specific, country specific charts of accounts) Adjustment postings (direct data entry) can be made in the FI-SL system Various fiscal year variants enables one to create a weekly or monthly report Validations or substitutions allow one to check or modify the data whenever it enters the FI-SL system. Up to three currencies and two quantities can be run in parallel in FI-SL Selective data retrieval - the assignment of transactions to particular company code or ledgers determines which ledgers are to be updated.
FI-SL Data Flow
CO-PA Extractors
Types of Extractors
Cross Application
FI FI
CO-PA Extractors
Profitability Analysis (PA) is an integrated component in the SAP R/3 system. All of the data related to profitability from the other SAP R/3 applications is mapped in CO-PA in accordance with the corresponding business transactions. This allows you to transfer into CO-PA billing document data from SD, cost object costs from CO-PC, and overall costs from overall cost controlling. CO-PA collects all of the OLTP data for calculating contribution margins (sales, cost of sales, overhead costs) CO-PA also has powerful reporting tools and planning functions
CO-PA Extractors
CO-PA Extractors
During billing SD, revenues and payments are transferred to profitability segments in Profitability Analysis. At the same time, sales quantities are valuated using the standard cost of goods manufactured, as specified in the cost component split from COPC. One of the typical questions that can be answered with CO-PA module is what are the top products and customers in our different divisions. The wide variety of analysis and planning functions in CO-PA allow you to plan, monitor and control the success of your company in terms of product-oriented, customer-oriented and organizational dimensions of multidimensional profitability segments.
Generic Extractors
Types of Extractors
Cross Application
FI FI
Generic Extractors
Generic Extractors are Cross Application Extractors used in scenarios where the other type of extractors are unavailable. Generic extractors are of three types:
Based on Database view/Table Based on InfoSet Based on Function Module
Generic Extractors
When should you use generic extractors? Business Content does not contain a DataSource for your application. The application does not feature its own generic delta extraction method You are using your own programs in SAP R/3 to populate the tables The tools for generic data extraction can be used to generate an extractor for all applications.
Flat file Extraction

BW provides facility to load data from flat files (CSV or ASCII files). It supports the following types of data :
Transaction data Master data, either directly or flexibly
Attributes Text Hierarchies
Flat file can be stored either on a local system or Application Server.
But from performance point of view we store the file on the applications server and then load it into BW.
UD Connect Overview
With the help of the SAP Web AS J2EE connectivity, UD Connect (Universal Data Connect) enables reporting and analysis of both SAP and non-SAP data. Using UD Connect, you can access just about all relational and multi-dimensional data sources. UD Connect transfers the data as flat data. Multidimensional data is converted to a flat format when UD Connect is used.
UD Connect Overview
For the connection to DataSources (in BW), UD Connect uses the J2EE Connector Architecture. BI Java Connectors that are available for various drivers, protocols and providers as resource adapters.
BI JDBC Connector BI ODBO Connector BI SAP Query Connector BI XMLA Connector
DB Connect Overview
SAP BW
Foreign Application Unix ORACLE DataBase
Purchasing
DB-Connect
MS SQL DataBase
NT
DB Connect Overview
A purchasing application runs on a legacy system based on an ORACLE database. To analyze the data from the purchasing application, the data needs to be loaded into the BW System (possibly installed on a different database, e.g. MS SQL-Server). DB-Connect can be used to connect the DBMS of of the purchasing application and extract data from tables or views.
Data Transfer with DB Connect

By default, when a BW application server is started by the SAP kernel, the system opens up a connection to the database on which the SAP system runs. All SQL commands (irrespective of whether they are Open or Native SQL) that are submitted by the SAP kernel or by ABAP programs, relate automatically to this default connection, meaning that they run in the context of the database transaction that is active in this connection.

Connection data, such as database user name, user password, or database name are taken either from the profile parameters or from the corresponding environment variables (this is database-specific). Thus DB Connect can be used to open up other database connections in addition to the default connection and use these connections to transfer data from tables or views into a BW system.
SOAP-Based Transfer of Data
SOAP-Based Transfer of Data

As a rule, data transfer in BW takes place using a data request that is sent from BW to the Source System (pull from the scheduler). You can also send the data to SAP BW using external control. This is a data push in the SAP BW. Data push is possible for multiple scenarios:
Transferring Data Using the SOAP Service SAP Web AS Transferring Data Using Web Service Transferring Data Using SAP XI
In all three scenarios, data transfer takes place via transfer mechanisms that are sufficient for Simple Object Access Protocol (SOAP) and are XML based.
Open Hub Service
Open Hub Service

The open hub service enables you to distribute data from an SAP BW system into external data marts, analytical applications, and other applications. With this, you can ensure controlled distribution using several systems. The central object for the export of data is the InfoSpoke. Using this, you can define the object from which the data comes and into which target it is transferred. Through the open hub service, SAP BW becomes a hub of an enterprise data warehouse. The distribution of data becomes clear through central monitoring from the distribution status in the BW system.
Datasource Enhancement
Need for DataSource enhancement
When we require an additional field from a database table and it is not directly available from the datasource, then we can append the field in the extract structure of the datasource. Then the logic to populate that field can be written in the customer exit.
Data Extraction
1 2 3 4 5
BI Content Extractors
LO Cockpit
Generic Extractors
BI Content Extractors Steps

7. Carry Out Delta Update 6. Initialize Delta Process 5. Create InfoPackage 4. Maintain InfoCube and Update Rules 3. Assign InfoSource and maintain communication structure and transfer rules 2. Replicate the Datasource in BW System 1. Activate Datasources
Step 1 - Activate DataSources
In SAP R/3, go to transaction Code SBIW Display IMG Business Content DataSources Execute Transfer Business Content DataSources
Step 1 - Activate DataSources

Select the DataSource from Application Component Hierarchy. Click on the button Transfer DataSources/ Activate the DataSource. Assign to a transport request.
Activate datasources
Step 2 - Replicate datasources

Tcode RSA1 Modelling Source Systems Context Menu Replicate DataSources.
Step 3- Assign the InfoSource

Maintain the communication structure and Activate the transfer rules.
Step 4 - Maintain InfoCube and Update rules
Infocube Update rules
Step 5 - Create InfoPackage

Go to InfoSources, Select the InfoSource Right click on the Source System and say create InfoPackage
Scheduler screen
Monitor
Step 6 - Initialize the delta process

Go to InfoPackage and select the update type as initialize delta process. And click on start to schedule the process
Monitor Scheduling Initialize the delta process
Initializing the Delta Process (Scheduler)

If you want to transfer data in the delta process, the process must be initialized in the first data request. In this process, the selection conditions for connecting delta uploads are set and its complete dataset is loaded into BW from the R/3 System. To do this, you must select the checkbox Initialize delta process for the Info Package under the update parameters of the Scheduler. Once the data is requested message appears after scheduling, Go to Monitor to view the status and details of the data load.
Monitoring the Upload Procedure
Delta Update (Scheduler)

Only the data since last upload is requested
Delta Update (Scheduler)

For high volume of transaction data, a full update here is mostly only justified for the first time data is transferred or if the statistics data has to be rebuilt following a system failure. Delta update mechanisms that restrict the volume of data to within realistic limits, therefore, are required to implement a performance-oriented, periodical data transfer strategy.
For e.g. when sales figures are updated every week in the Business Information Warehouse, only the sales document information that has been added or changed in the last week should be extracted.
LO Cockpit
LO Cockpit
Generic Extractors
Logistics Customizing Cockpit

The LO Cockpit contains the following functionality, as specified in the procedure sequenced below: Maintaining extract structures Maintaining DataSources Activating the update Controlling V3 update
LO Data Extraction (SBIW)
BW Logs (LBWF)
LO customizing cockpit lbwe Perform set up Application wise
Delete set up tables (LBWG)
Logistics Extract Structure Cockpit (LBWE)

Set up V3 update Maintain extract structure
Activate datasources
Individual Steps in LO Extraction

9. Carry Out Delta Update 8. Initialize Delta Process 7. Set Up periodic V3 update 6. Delete setup tables/Perform Extraction 5. Activate Extract Structure 4. Maintain InfoCube and Update Rules 3. Assign InfoSource and maintain communication structure and transfer rules 2. Replicate the Datasource in BW System 1. Maintain Extract Structure
Step 1 - Maintaining the Extract Structure
Maintain extract structure
Maintaining the Extract Structure

The extract structure is filled with the assigned communication structures. You can only use selected fields from the communication structures (SAP internal control fields, for example, are not offered). SAP already delivers extract structures, which you can enhance (by connecting to the communication structure). Every extract structure can be maintained by you and by SAP. After you set up the extract structure, the system automatically generates it. This completes missing fields (their units and characteristics). The extract structure is created hierarchically according to the communication structures. Every communication structure leads to the generation of a substructure that belongs to the actual extract structure.
Maintaining DataSources
Maintain datasources
Maintaining DataSources : Procedure

There exists a DataSource (for e.g. 2LIS_11_VAITM) for each extract structure that is made available (for example, MC11VA0ITM) in the OLTP System. A maintenance screen is displayed in which you can to assign other properties to the fields of the extract structure
Selection fields Hide fields Cancellation fields
(field is inverted when canceled (*-1))
Step 2 Replicating DataSources
Step 3 - Maintaining Communication Structure
All the fields in the extract structure are shown with the assigned info objects in the template
Step 4 - Maintaining Transfer Rules
Step 5 - Maintaining InfoCubes and Update Rules
Step 6 - Activating Extract Structures
Activate extract structure
Step 7 - Delete set up tables
In transaction LBWG enter the application number for which you want to delete the set up tables. For e.g. For 2LIS_11_VAITM enter the number 11 and execute.
Step 8 - Initialization/Simulation (OLI*BW)

Initializing ('build') the dataset for the respective extract structures is to be done before data can be extracted from the R/3 System. The initialization is set up in the OLTP. The restructuring process fills restructuring tables that are read during the initialization. It is recommended to carry this out before, in the simulation mode. The option of checking the extract structure update, without actually updating the data is available. The results are recorded in a detailed simulation log.
Give a name to the job
Step 8 - Creating Infopackages
Step 9 - Initializing the Delta Process
V3 Update- Settings
Set up V3 update Set the start time and print parameters. Schedule batch jobs
V3 Update Settings
In Start Date Select immediate scheduling
Give the print parameters
Schedule the job and check the job overview in SM37
Delta Queue Maintenance

Go to transaction RSA7. You can see that the delta queue has been successfully filled.
Step 10 -Delta Update (Scheduler)
Only the data since last upload is requested
FI-SL Extractors
LO Cockpit
Generic Extractors
FI-SL extraction Step-by-Step

8. Carry Out Delta Update 7. Initialize Delta Process 6. Create InfoPackage 5. Maintain InfoCube and Update Rules 4. Assign InfoSource and maintain communication structure and transfer rules 3. Replicate the Datasource in BW System 2. Define or Assign a DataSource for Ledger 1. Generate an extract structure for summary table
Step 1 - Setting up an FI-SL DataSource

Go to SBIW Settings for Application specific data sources Generate transfer structure for totals table
Step 2 - Setting up an FI-SL datasource :

Go to SBIW Settings for application specific datasources Financial accounting create infosource for Ledger

The status column shows whether a DataSource is assigned to the ledger already. (Traffic light green) You select the ledger to which you want to assign the DataSource
FI-SL Extractors
After generating the FI-SL DataSource rest of the steps are same as explained earlier. Replicate the DataSource and then assign it to the infosource. Create transfer rules and update rules Create InfoPackage and initialize the delta process
CO-PA Extractors
LO Cockpit
Generic Extractors
CO-PA Extraction (Steps)

7. Carry Out Delta Update 6. Initialize Delta Process 5. Create InfoPackage 4. Maintain InfoCube and Update Rules 3. Assign InfoSource and maintain communication structure and transfer rules 2. Replicate the Datasource in BW System 1. Generate DataSource in OLTP
Step 1 - Generate CO-PA DataSource

Go to Transaction KEB0. Define the DataSource for the current client of your SAP R/3 System on the basis of one of the operating concerns. A standard name is always generated. For e.g. 1_CO_PA %CL%ERK with prefix 1_CO_PA is mandatory.
Select the operating concern
Step 1 - Generate DataSource
Maintain CO-PA datasource

You can then specify which fields are to be applied as the selection for the COPA extraction.
Providing required fields for selection
CO-PA Extractors
After generating the CO-PA DataSource rest of the steps are same as explained earlier. Replicate the DataSource and then assign it to the infosource. Create transfer rules and update rules Create InfoPackage and initialize the delta process
Generic Extractors
LO Cockpit
Generic Extractors
Generic Data Extraction

Steps for transaction Data
8. Carry Out Delta Update 7. Initialize Delta Process 6. Create InfoPackage 5. Maintain InfoCube and Update Rules 4. Assign InfoSource and maintain communication structure and transfer rules 3. Replicate the Datasource in BW System 2. Create InfoSet/enhance table 1. Create DataSources for transaction Data

Steps for Master Data
7. Schedule InfoPackages 6. Create InfoPackage for texts 5. Create InfoPackage for Master Data 4. Assign InfoSource and maintain communication structure and transfer rules 3. Replicate the Datasource in BW System 2. Create DataSources for texts 1. Create DataSources for Master Data (attr)
Step1 - Create generic DataSource

Go to Transaction RSO2 Here you can select whether you want to create a datasource for transaction data, Attributes or texts. Give a technical name to the datasource and choose create
Create Generic DataSource

Create a Generic DataSource. Choose an application component to which the DataSource is to be assigned. Enter the description texts. You can choose whether you want to create the DataSource based on View, Function Module or InfoSet query. Choose Generic delta

Specify the delta specific field and its type. Maintain the settings for generic delta. Specify the safety interval. NOTE: safety interval should be set so that no document is missed even if it was not stored in the DB table when extraction took place. Select delta type : New status for changed records (i.e. after image) This can be used with data target ODS (AIE). Additive delta i.e. aggregated data records (ADD) and then choose save.
Only one attribute can be defined as delta attribute

Now choose save again. This will generate the DataSource. After generating the DataSource you will see the delta update flag selected. Select the fields in the selection which you want to appear in the Infopackage selection.

Transport the DataSource to BW in Tcode RSA6(Post Processing of DataSources). The steps in BW : Replicate the DataSources. Create necessary Info objects Generate Info source in BW, Maintain Communication Structure and Transfer Rules Create Info package and schedule it.
Flat File Extraction

LO Cockpit
Generic Extractors

7. Schedule Flat file using extractor 6. Create InfoPackage 5. Maintain InfoCube and Update Rules 4. Assign InfoSource and maintain communication structure and transfer rules 3. Define fields of InfoSource as InfoObjects 2. Define Source System in AWB 1. Identify the data
Step 1 Identify the Data

Go to MS Excel. Create a flat file and enter the records to be updated in the file. Save the file as a .CSV file. NOTE: The order of the fields in the flat file should be same as that in the communication structure of the InfoSource.
Step 2 - Create a Source System

RSA1 Modelling Source Systems Context Menu Create Select the Source System as File System .

After creating the Source System, create the Infoobjects in the BW system. Create an InfoSource and assign the flat file Source System to it and maintain the transfer rules. Create and ODS and maintain update rules. Now create an infopackage and load the data.
Hints while loading flat file

Give the name of the CSV file which you have created in the infopackage. Use the data separator as ;
File in CSV format
Data separator

Be sure the delimiter in the InfoPackage is given as ;
You might get an error on alpha conversion. Take in mind the option in transfer rule to convert the data from external format into internal.

Calendar day should be of the format yyyymmdd (SAP requires this format). Sometimes you might get an error like the system cannot open the file. Try keeping the file in My Documents or in C drive. View the preview option in the InfoPackage before loading the file Set the number of header rows to be ignored to 1. This ignores the heading row in the flat file
DB Connect, UD Connect and SOAP Based

BI Content Extractors LO Cockpit
Datasource Enhancement
Generic Extractors
Steps involved for DB Connect

7. Initialize Delta Update 6. Create InfoPackage 5. Maintain InfoCube and Update Rules 4. Maintain communication structure and transfer rules 3. Create InfoSource and assign Source System 2. Create a DataSource 1. Create a DB Connect Source System
Steps involved for DB Connect

Create a DB Connect Source System Create a DataSource Create InfoSource and assign the Source System created to it. Create InfoPackage and load the data.
Step 1 - Create a DB Connect source system the name of the DB Connection : Give
connection. DBMS : Enter the database type to which you want to connect in this field. (i.e. Oracle, DB2 etc) Enter the username and password. Conn. Info : This field contains the technical information that is analyzed in native SQL in the CONNECT statement in order to open the database connection. e.g. In Oracle enter the name of the database you want to connect
Step 2 - Generate You use the context menu for a DataSource database Source System
Select Database Tables to generate a DataSource for database source systems. First, you choose a selection of tables for a database source system and create a connection to the database source system. Next, you select the table fields for a specific table of the database Source System, and specify whether you want these table fields to be available for selection in the BW system.
Taking over Metadata via DB Connect
Step 3 - Assign the DataSource to the InfoSource

Based on the generated DataSources for external DB views/tables InfoSources in BW can be established as usual. Dataflow is now possible!
DataSource Enhancement
LO Cockpit
Generic Extractors
Datasource Enhancement via Customer Exit

The different customers exits for enhancements of transaction data, master data attributes, texts and hierarchy DataSources are
EXIT_SAPLRSAP_001 : Transaction data DataSource EXIT_SAPLRSAP_002 : Master data DataSource EXIT_SAPLRSAP_003 : Text DataSource EXIT_SAPLRSAP_004 : Hierarchy DataSource
Datasource enhancement Steps involved

6. Write appropriate customer exit for enhancement 5.Unhide the custom field 4. Enhance extract structure with append structure 3. If not available proceed with enhancement 2. If available include the same in extract structure 1. Check whether required field is available in extract structure
Step 1 - Check for availability in Extract Structure

Applicable for DataSources where required field is available but not included by default Pre-requisite is empty delta queue and set-up tables
Step 2 - Enhance Extract Structure

Find the name of the extract structure for DataSource Namespace for custom field is YY or ZZ Activate append structure For currency/quantity fields, the reference field should also be present in the extract structure
Step 3 - Unhide the added field

Note that Field Only is checked Incase field is required for selection, check Selection
Step 4 - Write the logic

Go to CMOD Enter Project name and select component Select appropriate Customer Exit
Write the Logic

Write the ABAP code for populating the custom field Test Enhancement in RSA3 Replicate DataSource in BW
Data Extraction
1 2 3 4 5

Create the InfoObjects document number, order no, name of the material, cost, currency, order creation date in the BW system. Create a flat file containing data for above InfoObjects Save the file in the CSV format. Now create a flat file source system and InfoSource and assign the Source System to the InfoSource. Create an ODS with document number as key field and include the above InfoObjects. Create the update rules from the InfoSource you have created. Create an InfoPackage and load the file.
BI Content Extraction
In the Source system go to transaction RSA5, activate the DataSource 2LIS_11_VAITM. Go to BI Content select the grouping as data flow before and install the InfoSource 2LIS_11_VAITM. Now replicate the DataSource in BW and assign it to the InfoSource and maintain transfer rules Create an ODS and update rules Create the InfoPackage and load the ODS
LO Cockpit
Go to transaction SBIW. Check out the various options to delete and fill the set up tables and simulate the batch jobs Go to transaction LBWE, check the option to maintain the datasources and to activate them as well as to simulate the V3 update
Transactions
RSA1 RRMX RSO2 RSA3 RSA7 RSA6 RSQ02 RSBOH1 Administrator Workbench Business Explorer ( BEX ) Maintain Generic Datasource Extractor Checker Delta Queue Status Maintain Datasources Maintain InfoSets Open Hub Destination
Transactions
RSMO SBIW OLI*BW SM50 RSA5 RSA6 LBWE LBWG LBWF SM37 KEB0 Monitoring BW Config. Statistical Setup Process Overview Install Business Content Post Processing of DataSources Logistics Cockpit Deleting Setup tables BW Log Job Overview Create the COPA Data Source
Course Name
1 2 3 4 5
Tips & Tricks

Before starting an SAP BW project, analyze the reporting requirements against the standard DataSources available. Zero-in on the standard DataSources satisfying the requirement. If data that cannot be supplied by the standard sources, we can: - Create a generic DataSources. - Enhance the standard DataSource.
Some Useful sites

www.sdn.sap.com www.help.sap.com www.service.sap.com

Bi 1003 - Data Extraction - V2

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Bi 1003 - Data Extraction - V2

Загружено:

Авторское право:

Доступные форматы

BI1003 Data Extraction v2.

India SAP CoE, Slide 1

PrepareMe TellMe ShowMe LetMe HelpMe

PrepareMe TellMe ShowMe LetMe HelpMe

India SAP CoE, Slide 4

India SAP CoE, Slide 5

India SAP CoE, Slide 6

India SAP CoE, Slide 7

PrepareMe TellMe ShowMe ShowMe LetMe HelpMe

Data Extraction : Overview

DB Connect, UD Connect and SOAP based

FI-SL Extractors Flat File Extraction CO-PA Extractors

India SAP CoE, Slide 9

Order-Deliv. Order Delivery

Update Rules Transfer Rules

OLTP System Data extract

India SAP CoE, Slide 11

Multiple Source Systems

India SAP CoE, Slide 12

Customer Generated Extractors LIS FISL COPA Application Specific DB Tables

Generic Extractors DB View Infoset Function Module Various SAP DB tables

India SAP CoE, Slide 14

Business Content Extraction

Customer Generated Extractors

Business Content Extractors

Uses of BI Content Extractors

India SAP CoE, Slide 17

LO Data Extraction : Overview

Customer Generated Extractors LIS FISL COPA Application Specific DB Tables

Generic Extractors DB View Infoset Function Module Various SAP DB tables

India SAP CoE, Slide 19

LO Data Extraction : Data Flow

India SAP CoE, Slide 20

V3 Update Modes in LO Cockpit

India SAP CoE, Slide 22

India SAP CoE, Slide 23

India SAP CoE, Slide 24

India SAP CoE, Slide 25

India SAP CoE, Slide 26

India SAP CoE, Slide 27

India SAP CoE, Slide 28

India SAP CoE, Slide 29

India SAP CoE, Slide 30

New LO Data Extraction : Why ?

India SAP CoE, Slide 31

New LO Data Extraction : Why ?

India SAP CoE, Slide 32

New LO Data Extraction : Why ?

India SAP CoE, Slide 33

Customer Generated Extractors

Customer Generated Extractors LIS FISL COPA Application Specific DB Tables

Generic Extractors DB View Infoset Function Module Various SAP DB tables

Customer Generated Extractors

India SAP CoE, Slide 35

Customer Generated Extractors LIS FISL COPA Application Specific DB Tables

Generic Extractors DB View Infoset Function Module Various SAP DB tables

LIS Data Extraction

India SAP CoE, Slide 37

LIS Data Extraction

India SAP CoE, Slide 38

LIS Data Extraction

India SAP CoE, Slide 39