Sie sind auf Seite 1von 21

DB Connect Usage in SAP BI 7.

0
Introduction In SAP Net weaver BI 7.0, well study how to implement DB Connect, rather than common usage of flat files. Using DB Connect, BI offers flexible options for extracting data directly into BI from tables and views in database management systems that are connected to BI using connections other than default connection. The DB Connect enhancements to database interface allow you to transfer data straight into BI from the database tables or views of external applications. You can use tables and views in database management systems that are supported by SAP to transfer data. You use Data Sources to make the data known to BI. The data is processed in BI in the same way as data from all other sources. Its to be noted that SAP DB Connect only supports certain Database Management systems (DBMS) The following are the list of DBMS Max DB [Previously SAP DB] Informix Microsoft SQL Server Oracle IBM DB2/390, IBM DB2/400, IBM DB2 UDB

There are 2 types of classification. One is the BI DBMS & the other is source DBMS. The main thing which is, both these DBMS are supported on their respective operating system versions, only if SAP has released a DBSL. If not, they dont meet the requirements & hence cant perform DB Connect. In this process we use a Data source, to make the data available to BI & transfer the data to the respective Info providers defined in BI system. Further, using the usual data accusation process we transfer data from DBs to BI system. Using this SAP provides options for extracting data from external systems, in addition to extracting data using standard connection; you can extract data from tables/views in database management systems (DBMS)

Loading data from SAP Supporting DBMS into BI Steps are as follows:1. 2. Connecting a database to Source system -- Direct access to external DB Using Data source, the structure for table/view must be known to BI.

Process Description Go to RSA1 Source Systems DB Connect Create

Now, create the source system using 1. 2. 3. Logical System Name MSSQL Source System Name MS SQL DB Connect Type & Release

Now, Under DB Connect, we can see the name of our Source System (MS SQL DB Connect) The logical DB Connect name is MSSQL

In Data sources we need to create an Application Component area to continue with the export Goto RSA1 Data sources Create Application Component

After creating an Application Component Area called ac_test_check, we now have to create a Data source in the component area. So right click the Application component area Create Data source (as in below figure).

The Data source name here is ds_ac_tech The Source System here is the defined MSSQL The type of data type data source that we have here is Master Data Attributes

The below screen shot describes how to perform extraction or loading using a Table/View. As the standard adapter is Database Table (by default), we can specify the Table/View here

Now, choose the data source from the DB Object Names.

Now, we have selected the EMPLOYEES as the Table/View.

Or we can choose the Table/View REGION

We have 2 database fields Region ID Region Description

Now that the Data source has to be activated before it is loaded, we ACTIVATE it once.

After activation, the data records (4) are displayed. Eastern, Western, Northern & Southern

Right click the Info package DS_AC_TEST Create Info package

We now create an Info package called IP_DS_AC_TECH, with Source system as MSSQL

Once

done

we

perform

schedule

on

the

Info

package

Start

Now, we need to create an Info Area to create an Info provider (like Info Cube)

After creating the info cube we check for the data in the PSA by Manage the PSA This can be also done using the Key controls (Ctrl + Shift + F6)

The

number

of

records

displayed:

Nos

Using the PSA Maintenance, we can view the following factors 1. 2. 3. 4. 5. Status Data Packet Data records REGION ID REGION Description

The Table/View CUSTOMERS is now chosen for Extraction. In the next tab we have PROPOSAL, which describes all the Database fields, and we have to specify the Data source fields, types & length.

Now, we create an Info package IP_TEST_CUST

Now, go to RSA1 Info objects Info object (Test) Create Info Object Catalog

Now, we can preview the Region ID & Region Description.

We now create 2 Info objects & pass the Region ID & Region Description to the 2 objects. 1. Region Description Region2 (Region)

2.

Region Description reg_id (Region ids)

Now, these are the 2 variables created under the Info object test2 Region (REGION2) Region ids (REG_ID)

We create Characteristic as Info Provider for the Master Data loading in the Info Provider section Insert Characteristic as Info Provider

Now, we create a transformation using Create Transformation on the Region ids (Attributes)

We now choose the Source System after this MSSQL MS SQL DB CONNECT

After checking the Transformation mappings on the Region ID, we now perform a DTP Creation on the same Region ID (Attribute)

We choose the Target system (default) as Info object Region ID REG_ID & the Source Type as Data source with the Source System MSSQL

After this step, we proceed with creating an Info package IP_DS_TEDDY which has the source system as MSSQL. Further we start the scheduling of the Info package. Once the info package has been triggered we can go to Maintain PSA & monitor the status of data in PSA

Further, we EXECUTE the DTP. And, we can monitor transfer of data from PSA Info cube

Results Thus, the DB Connect process has been successfully demonstrated in SAP BI 7.0

Das könnte Ihnen auch gefallen