SAP BI Extraction Through Open Hub Destination
You can use the Open Hub Destination (OHD) to extract data from SAP BI. If you extract data through SAP BI version 7.0, you can extract through the open hub destination. The open hub destination is an independent object that you can integrate into the data flow. You can configure InfoCubes, DataStore Objects, InfoObjects, and InfoSets as open hub data sources.
PowerCenter data extraction from SAP BI occurs in the following sequence:
1. A process chain directs an open hub destination to extract data. The process chain can also help you identify the point of failure in case of a system failure.
2. Use the ZPMSENDSTATUS ABAP program or pmsaputil to configure the third-party parameters. Use pmsaputil to start the process chain.
3. The open hub destination extracts data and loads it to a into a database table in the BI system.
4. The open hub destination notifies the RFC destination that is specified in the open hub destination that data extraction is complete.
5. The SAP BW Service initiates the PowerCenter workflow that the Integration Service uses to extract data from SAP BI.
6. The Integration Service extracts data from the SAP BI.
When the data extraction begins, you can view log events to track the interactions between PowerCenter and SAP BI.
Extracting Data from SAP BI Complete the following steps to configure the SAP BI system and PowerExchange for SAP NetWeaver BI to extract data from SAP BI:
1. Create an open hub destination and a data transfer process in the SAP BI system to extract the data from SAP BI and write it to an SAP transparent table.
2. Create a mapping with an SAP BW OHS source definition that you import from an open hub destination.
3. Start the SAP BW Service in PowerCenter.
4. Configure a PowerCenter workflow to extract data from SAP BI.
5. Create and start a process chain to extract data.
Step 1. Create an Open Hub Destination >> Create an open hub destination to extract data from SAP BI. You can configure SAP BI objects such as InfoCubes, DataStore Objects, InfoObjects, and InfoSets as open hub destination data sources.
1. In the SAP Menu screen, enter RSA1 in the Transaction field.
The Administrator Workbench opens.
2. Select Open Hub Destination in the left pane.
3. Right-click an InfoArea in the right pane and then select Create Open Hub Destination.
The Create Open Hub Destination dialog box appears.
4. On the General tab in the Create Open Hub Destination dialog box, select a data source from which to extract data.
5. Enter an open hub destination name and description.
6. Select the ObjectType from which you want to update the data to the open hub destination.
7. Select the object listed for the selected object type and click enter. The open hub destination is added to the InfoArea.
8. Select Third-Party Tool as the destination in the Destination tab.
9. Enter an RFC destination.
10. Save and activate the open hub destination.
Create a Data Transfer Process >> Create a data transfer process (DTP) to transfer data from source objects to target objects in SAP BI.
1. Right-click the open hub destination and select Create Data Transfer Process.
The Creation of Data Transfer Process dialog box appears.
2. Enter a name for the DTP in the Data Transfer Proc field.
3. Select the object type and the name of the source for the DTP.
Note: Use the same object type and the name that you selected for the open hub destination.
4. Save and activate the DTP. Step 2. Create an SAP BW OHS Source Definition
>> Create a mapping with an SAP BW OHS source definition. When you create an SAP BW OHS source definition, use a connection string or a host name to connect to SAP. To connect to SAP using a connection string, use a connection string specified as a DEST entry in saprfc.ini.
The following table lists the connection parameters you enter to connect to SAP:
Connection Parameter >> Description Connection String Required. Type A or Type B DEST entry in saprfc.ini. User Name Required. SAP source system connection user name. Password Required. Password for the user name. Client Required. SAP client number. Language Optional. Language you want for the mapping. Must be compatible with the PowerCenter Client code page. If you leave this option blank, PowerCenter uses the default language of the SAP system.
To connect to SAP using a host name, use a host name and a system number that you specify in the Connection Properties window.
The following table lists the connection parameters you enter to connect to SAP:
Connection Parameter >> Description Host Name Required. Host name of the machine where the SAP application is running. System Number Required. SAP system number. User Name Required. SAP source system connection user name. Password Required. Password for the user name. Client Required. SAP client number. Language Optional. Language you want for the mapping. Must be compatible with the PowerCenter Client code page. If you leave this option blank, PowerCenter uses the default language of the SAP system.
When you connect to SAP, the Import InfoSpokes from SAP BW wizard displays the InfoSpokes that you can import as SAP BW OHS source definitions. You can enter a filter condition to filter the InfoSpokes you want to appear.
The format of InfoSpokes depends on the DataSource they belong to. You can import an InfoSpoke from one of the following DataSources:
DataStore InfoCube InfoObject(Texts) InfoObject(Attributes)
Note: Previous versions of SAP NetWeaver BI refer to DataStore as ODS Object. When you import multiple InfoSpokes, the Designer creates separate SAP BW OHS source definitions for each InfoSpoke. You can import multiple InfoSpokes at a time. Each mapping can include only one SAP BW OHS source definition.
When you import an SAP BW OHS source definition, Designer client replaces the slash (/) in the business name of the Source Qualifier with an underscore (_).
You can filter InfoSpokes based on the name or the description of the InfoSpoke. When you enter a filter condition, you can enter an exact name or description. Or, you can perform wildcard search. Use the following filter syntax rules and guidelines:
If you want to filter on a description, enter a filter condition of 20 characters or fewer. Use the percent sign (%) as a wildcard search for multiple characters. For example, to find an InfoSpoke whose name begins with the letter “I”, enter I% as the filter criterion. Use an underscore (_) as a wildcard search for single characters.
When you select an InfoSpoke, the wizard displays the following information in the Field Information pane:
Field >> Description Name Name of the record. A record can be user-defined or SAP defined. An SAP-defined record is uniquely identified by a Request ID, Data Packet ID, or Record ID. Description Description of the field. Datatype Datatype of the object. Precision Precision of the object. Scale Scale of the object.
To create an SAP BW OHS source definition:
1. In the Source Analyzer, click Sources > Import InfoSpoke from SAP BW.
The Import InfoSpoke from SAP BW Wizard appears.
2. Enter the information in the Connection Properties page and click Next.
The InfoSpoke Selection window appears.
3. Enter a filter condition to filter InfoSpokes based on the name or description.
4. Click Get Objects.
The wizards displays a list of InfoSpokes based on the filter criteria you entered.
5. Select the InfoSpokes you want to import.
6. Optionally, select Show Selected Objects Only to view only the selected InfoSpokes in the Objects pane.
7. Click Next.
The InfoSpoke Summary Page appears.
8. Click Finish.
Step 3. Start the SAP BW Service Start the SAP BW Service from the Administrator tool. The SAP BW Service is an application service that listens for RFC requests from the SAP BI system, initiates workflows to extract from or load to the SAP BI system, and sends log events to the PowerCenter Log Manager.
Step 4. Configure and Start a PowerCenter Workflow To configure a PowerCenter workflow to extract data from SAP BI, configure the workflow with an SAP BW OHS source definition. Assign and SAP_BWOHS_Reader application connection to the source. Schedule the workflow to run on demand.
Next step will be Configure and Start a Process Chain .. soon will be post.
Mehboob MCTS & MCITP