Sunteți pe pagina 1din 17

How to use Microsoft Connector 1.

0 in
MS SQL Server Integration Services
packages with Open Hub services to
export data from SAP BI to MS SQL?

Applies to:
BI 7.0. For more information, visit the EDW homepage.

Summary
This article describes the step by step procedure to transfer the data from SAP BI to Microsoft SQL using
Open hub services. It also covers the details of how to establish the connection between the source (SAP BI)
and the target (Microsoft SQL).

Author: Hemant Khemani


Company: Wipro Technologies
th
Created on: 11 Feb 2011

Author Bio
Hemant Khemani is a SAP BI Consultant with Wipro Technologies. He has more than 4 years of
experience in SAP BI.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 1
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

Table of Contents
Introduction ......................................................................................................................................................... 3
Why Open Hub? ................................................................................................................................................. 3
Prerequisites ....................................................................................................................................................... 3
Mechanism used ................................................................................................................................................. 4
Step by Step procedure ...................................................................................................................................... 5
Step 1: Creating RFC Destination in Transaction code SM59 ....................................................................... 5
Step 2: Create Open Hub destination and Relevant Data Flow in BW. .......................................................... 7
a. Create Open Hub Destination .................................................................................................................................. 7
b. Transformation between Source Object and open hub Destination ......................................................................... 8
c. DTP to load Data from Info object to open hub Destination ..................................................................................... 8
Step 3: Business Intelligence Development Studio ........................................................................................ 9
Step 4: Setting up the Connection Manager for SAP BI. ................................................................................ 9
Step 5: Adding and Configuring the SAP BI Source ..................................................................................... 11
Step 6: Columns in SAP BI source (i.e., Fields coming from BW) ............................................................... 12
Step 7: Adding and Configuring the Destination ........................................................................................... 12
Step 8: Data flow in SSIS .............................................................................................................................. 13
Step 9: Control Flow in SSIS ........................................................................................................................ 14
Step 10: Triggering the data load from SAP BI ............................................................................................. 14
Step 11: Checking the data in SQL ............................................................................................................... 15
Related Content ................................................................................................................................................ 16
Disclaimer and Liability Notice .......................................................................................................................... 17

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 2
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

Introduction
Open hub service is one of the easiest ways to export data from SAP BI.
In this document we will see the following –
 Why to use open hub to export data to Microsoft SQL server?
 Detailed procedure on how to set up connection between SAP BI and Microsoft SQL server.
 How to use open hub services to export the data from BI to Microsoft SQL server?

Why Open Hub?


There are several ways to export data from SAP BI:

 Analytical Process Designer (APD)


 Open Hub
 Third Party ETL tools
 Custom build processes with ABAP

Then, why do we prefer Open hub?

1. SAP promotes the Open Hub technology as the standard tool for data export from SAP BI.
2. The target technology, Microsoft SQL Server provides standard ETL services with SQL Server
Integration Services (SSIS) that is able to communicate with the Open Hub services.

Prerequisites

1. Install SSIS 2008 MS Connector for SAP BI.


2. Make sure the BI system is SAP BI 7.x with at least SAP BI SP17.
3. Install SAP librfc32.dll

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 3
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

Mechanism used
The basic principle of the extraction process is identical for all source objects i.e., Info objects, DSO, Info
cubes etc from BI. The export process is triggered by standard loading and scheduling tooling of SAP BI.
The communication with the external system will make use of standard application interfaces (APIs) that are
delivered with the Open Hub service:

1. A so-called data transfer processes (DTP) fills the intermediate table. The table is cleared in the
beginning of the process.
2. Open Hub will notify SSIS (SQL server integration services) that it is ready for data retrieval.
3. SSIS will read the data from the intermediate table using the API to read data.
4. SSIS will send the status with an API to Open Hub, which is recorded in a status table for monitoring
purposes.

Scheduler

Process
chain start

1. Fill data

DTP
Table /BIC/OHYYY 3. Read data
Execute

2. Notification sent MSSQL


Open Hub
Start
Server

Status
Table
4. Send data read status

/BIC/OHYYY is the intermediate table in BW where YYY refers to the Open hub destination name.

Note: Some of the APIs are RSB_API_OHS_3RDPARTY_NOTIFY, RSB_API_OHS_REQUEST_SETSTATUS and


RSB_API_OHS_DEST_READ_DATA.
For more details on the APIs used, please read
http://help.sap.com/saphelp_nw04/helpdata/en/a8/a6eae34c9e9b4cbd8fbc7acd2845d0/content.htm

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 4
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

Step by Step procedure


Step 1: Creating RFC Destination in Transaction code SM59

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 5
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 6
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

Step 2: Create Open Hub destination and Relevant Data Flow in BW.

a. Create Open Hub Destination

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 7
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

b. Transformation between Source Object and open hub Destination

c. DTP to load Data from Info object to open hub Destination

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 8
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

Step 3: Business Intelligence Development Studio


The Microsoft Connector components are not available in the Toolbox until you add them manually. To add
them, right click Data Flow Sources in the Toolbox, click Choose Items, and then on the SSIS Data Flow
Items tab, select the SAP BI Source check box.

Step 4: Setting up the Connection Manager for SAP BI.


In the Integration Services package, add a new connection and choose SAPBI.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 9
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

After the connection is created, in the SAP BI connection manager dialog box, edit the connection and fill
the system and logon information. Click Test Connection to verify successful configuration.

Host: IP of your BI system.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 10
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

Step 5: Adding and Configuring the SAP BI Source


In Business Intelligence Development Studio, drag the SAP BI source to the data flow of the package.

Edit the source by choosing the appropriate SAP BI connection manager, specifying the RFC destination.

Choose the open hub destination from the dropdown box.

Note: If the user id used for connection in the previous step doesn’t have authorization for Open hub destination in SAP
BI; then you will not be able to see open hub destinations in the dropdown list.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 11
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

Step 6: Columns in SAP BI source (i.e., Fields coming from BW)

Step 7: Adding and Configuring the Destination


An OLE DB destination is commonly used as destination in the SSIS package.

Connect SAP BI source and OLE DB Destination.

Direct mapping for field with same names in source and target would be there by default.

Note: The below screenshot shows how the mapping between source and target fields would look like in general.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 12
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

If you want to do any conversions then you can use Data Conversion task between source and destination
and do manipulations there.

Step 8: Data flow in SSIS

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 13
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

Step 9: Control Flow in SSIS


Based on the wait time set for the SSIS package, it will wait for a notification from BI system for that duration
only. To keep the above SSIS package in listening mode continuously, we will keep the data flow task in a
FOR loop container with a condition which is always true.
Now when the SSIS package will run, it will wait for the notification from the BI system for the wait time
mentioned in the package and after the wait time gets elapsed without receiving any notification from the BI
system then the SSIS package will execute again automatically as the FOR condition is true.

Step 10: Triggering the data load from SAP BI


When we execute the DTP in the BI system, the data first flow to the intermediate table /BIC/OHZOTEST.
This will make the technical status in the DTP monitor to green. Then a notification is sent to SSIS package
automatically using the API. After the data is received in SQL the overall status in DTP monitor will turn to
green.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 14
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

Step 11: Checking the data in SQL


Go to the Microsoft SQL server management studio, and check the contents of the relevant table.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 15
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

Related Content
Using SQL Server 2008 Integration Services with SAP BI 7.0
Loading data from SAP BW into Microsoft Analysis Services using Open Hub Service
SAP help on Open Hub Destination
For more information, visit the EDW homepage

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 16
How to use Microsoft Connector 1.0 in MS SQL Server Integration Services packages with Open Hub services to export data from SAP BI to MS SQL?

Disclaimer and Liability Notice


This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not
supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,
and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or
code sample, including any liability resulting from incompatibility between the content within this document and the materials and
services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this
document.

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com
© 2011 SAP AG 17

S-ar putea să vă placă și