IBM Support

Locating a DataStage job name in the SAP BW environment to troubleshoot BW Pack data processing issues

Question & Answer


Question

Where on the SAP BW side can I find the DataStage job name associated with the BW Pack data load or extract?

Cause

Data is not processed. It could occur when there are two jobs designed to run the process using the same Source system and InfoSource or Open Hub Destination

Answer

  1. Open Hub Interface - Open Hub Destination carries a DataStage job name. For the BW extract process, the 3rd Party Open Hub Destination (OHD) object carries a DataStage job name as a value for the DSJob parameter.
    The other two parameters defined in OHD are RFCPROCESSCHAIN and 3RDPARTYSYSTEM. These 3 parameters define the unique set of the values for a particular data extract.

    To verify the DataStage job name that actually is assigned to run the data extract, connect to an SAP client, type RSA1 for the transaction code, select 'Open Hub Destination' in Modeling window on the left hand side. Find the OHD in question, right click to select 'Display'. Then select 'Parameters' button next to the 'RFC Destination' field. Check the DataStage job name.
  2. InfoSpoke Interface - InfoSpoke carries a DataStage job name.
    For the BW extract process, the unique set of parameters is defined on the InfoSpoke object. To navigate, use transaction code /nRSBOH1. Choose 'InfoSpoke' button. Select the InfoSpoke in question, click Display icon. Select 'Destination' tab and 'Parameters' button, next to the 'RFC Destination' field. Verify the DataStage job name.

    Troubleshooting: The job name is missing or the wrong job name is assigned.
    How did the DataStage job name get assigned to the Open Hub Destination or to the InfoSpoke? Only from within the DataStage job. Use the 'Update BW' button under the 'Open Hub Destination' tab in the BW extract stage of the job.

    Note: The same RFC destination (as a Source System port) can be used by many BW extract jobs. What makes the extract process unique is the set of the above described parameter values, therefore only one OHD/InfoSpoke is defined per DataStage job. In other words, two different jobs can use the same RFC destination/Source system, but cannot use the same OHD.
  3. Staging BAPI Interface
    For the BW Load process, the InfoPackage object carries a DataStage job name. The DataStage job name is assigned to the InfoPackage for PULL jobs only.
    To verify the DataStage job name, connect to an SAP client, type RSA1 for the transaction code, select 'InfoSource' in Modeling window on the left hand side. Find the InfoSource in question and navigate ( drill down) from the Communication to the Transfer structure, then to the DataSource and to the InfoPackage. Double click on the latter to open it. Select '3rd Party Selections' tab. Check the DataStage job name.

    Troubleshooting: While in the '3rd Party Selections' tab, if the DataStage job is missing, you can assign the DataStage job to the InfoPackage by clicking on the radio button next to the 'Input Value' field. To refresh the job name, use 'Check' or 'Refresh' button.

    Also, it helps if in the BW Load stage of the job you verify the Information Server details for running the job under the 'InfoPackage Options' tab in the Source System Properties window.

    Note: The same RFC destination/Source system can be used by many BW load jobs, but only one InfoPackage can be invoked per DataStage job.

Note: Usually all the above navigations inside the SAP application are performed by SAP basis folks. The support engineer could request their assistance to verify the data flow regarding the DataStage job name involved in the data transfer.

[{"Product":{"code":"SSZJPZ","label":"IBM InfoSphere Information Server"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Pack for SAP BW","Platform":[{"code":"PF033","label":"Windows"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21509631