system
January 16, 2014, 1:14pm
1
Hello Everybody,
We have set up the connection between BODS and SAP BW via OpenHub.
The RFC server seems to be ok side BW and BODS.
But when I launch my BODS Job, my process chain in BW doesn’t start.
I have this trace from BODS:
(12.2) 01-15-14 15:56:34 (2208:3368) JOB: Reading job <ff81e166_084b_4fd8_ae64_8f5f6e0ea330> from the repository; Server version is <12.2.3.4>; Repository version is
<12.2.2.0000>.
(12.2) 01-15-14 15:56:34 (2208:3368) JOB: Current directory of job <ff81e166_084b_4fd8_ae64_8f5f6e0ea330> is <I:\Business Objects\BusinessObjects Data Services\bin>.
(12.2) 01-15-14 15:56:34 (2208:3368) JOB: Starting job on job server host , port .
(12.2) 01-15-14 15:56:34 (2208:3368) JOB: Job <JOB_HUB_DW> of runid <2014011515563422083368> is initiated by user .
(12.2) 01-15-14 15:56:34 (2208:3368) JOB: Processing job <JOB_HUB_DW>.
(12.2) 01-15-14 15:56:35 (2208:3368) JOB: Optimizing job <JOB_HUB_DW>.
(12.2) 01-15-14 15:56:35 (2208:3368) JOB: Job <JOB_HUB_DW> is started.
(12.2) 01-15-14 15:56:35 (2208:3368) WORKFLOW: Work flow <WF_HUB_DW> is started.
(12.2) 01-15-14 15:56:35 (0336:3232) DATAFLOW: Process to execute data flow <DF_HUB_BW> is started.
(12.2) 01-15-14 15:56:36 (0336:3232) DATAFLOW: Data flow <DF_HUB_BW> is started.
(12.2) 01-15-14 15:56:36 (0336:3232) DATAFLOW: Cache statistics determined that data flow <DF_HUB_BW> uses <0> caches with a total size of <0> bytes. This is less than(or
equal to) the virtual memory <1608515584> bytes available for caches. Statistics is switching the cache type to IN MEMORY.
(12.2) 01-15-14 15:56:36 (0336:3232) DATAFLOW: Data flow <DF_HUB_BW> using IN MEMORY Cache.
(12.2) 01-15-14 15:56:36 (0336:3232) TAB_READ: <|Data flow DF_HUB_BW|Reader ZCC3_SO> has sent request to execute process chain <PC_SD_CC3_BO_SO_2> at Data Services
Administrator http://XXX.XXX.XX.XX :XXXX/DataService and is waiting for Open Hub <ZCC3_SO> read request id from SAP system
<XXXX_BID_80>.
(12.2) 01-15-14 15:58:36 (0336:3232) TAB_READ: Process Chain <PC_SD_CC3_BO_SO_2> of Open Hub <ZCC3_SO> is being processed by RFC Server DI_SOURCE@xxbid_BID_80 at Data
Services Administrator http://XXX.XXX.XX.XX :XXXX/DataServices.
(12.2) 01-15-14 16:00:36 (0336:3232) TAB_READ: Process Chain <PC_SD_CC3_BO_SO_2> of Open Hub <ZCC3_SO> is being processed by RFC Server DI_SOURCE@xxbid_BID_80 at Data
Services Administrator http:// XXX.XXX.XX.XX:XXXX /DataServices.
(12.2) 01-15-14 16:02:36 (0336:3232) TAB_READ: Process Chain <PC_SD_CC3_BO_SO_2> of Open Hub <ZCC3_SO> is being processed by RFC Server DI_SOURCE@xxbid_BID_80 at Data
Services Administrator http:// XXX.XXX.XX.XX:XXXX /DataServices.
At the end, I must abort the BODS Job.
Do you have any hint?
Regards
Etienne (BOB member since 2014-01-16)
system
January 16, 2014, 3:15pm
2
When you created the open Hub table, did you check the box to “execute Process chain before reading data”?
We had such jobs, and prior to let DS fetch the data, the open hub must be filled with data, which you usually do by executing a SAP Process chain.
This can be checked when looking at the OH table in a DF:
Ticke the box “execute process chain before reading” and specifiy the processchainname
Bajiman (BOB member since 2011-05-19)
system
January 16, 2014, 4:05pm
3
Thanks for your reply.
My parameter are in this attachment.
I already checked this box and I selected my Process Chain.
But I have the same issue.
Etienne (BOB member since 2014-01-16)
system
January 17, 2014, 6:59am
4
How did you define the process chain in BW?
Will it be schduled/triggered by “Start Using Meta-Chain or API”?
Is the chain activated?
Bajiman (BOB member since 2011-05-19)
system
January 17, 2014, 8:42am
5
Hi,
Yes I have created a process chain with a Start Variant with option “Start Using Meta Chain or API”. It runs just the DTP of the Openhub.
The chain is activated. I have checked the BW RFC trace when I run the job in Data Services and I see my CPIC user connecting and giving RFC commands:
VMSAP26 xxbid_BID_80 Server RFCPING 110 50
VMSAP26 xxbid_BID_80 Server RFC_GET_FUNCTION_INTERFACE 1.452 176
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 1.183 156
VMSAP26 ? RFCPING 313 50
VMSAP26 xxbid_BID_80 Server RFCPING 110 50
VMSAP26 xxbid_BID_80 Server RFC_GET_FUNCTION_INTERFACE 1.452 176
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 1.183 156
VMSAP26 ? RFCPING 313 50
VMSAP26 xxbid_BID_80 Server RFCPING 110 50
VMSAP26 xxbid_BID_80 Server RFC_GET_FUNCTION_INTERFACE 1.452 176
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 1.183 156
VMSAP26 xxbid_BID_80 Server RFC_GET_FUNCTION_INTERFACE 1.022 176
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 1.847 156
VMSAP26 xxbid_BID_80 Server RFC_SYSTEM_INFO 478 58
VMSAP26 xxbid_BID_80 Server RFC_GET_FUNCTION_INTERFACE 1.237 176
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 2.262 156
VMSAP26 xxbid_BID_80 Server RSPC_API_CHAIN_GET_PROCESSES 1.226 228
VMSAP26 xxbid_BID_80 Server RSPC_API_PROCESS_GET_INFO 426 185
VMSAP26 xxbid_BID_80 Server RFC_GET_FUNCTION_INTERFACE 3.172 176
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 1.349 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 1.100 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 353 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 1.432 156
VMSAP26 xxbid_BID_80 Server RSB_API_OHS_DEST_GETDETAIL 3.427 349
VMSAP26 xxbid_BID_80 Server RFC_GET_FUNCTION_INTERFACE 185 176
VMSAP26 xxbid_BID_80 Server RFC_GET_FUNCTION_INTERFACE 1.237 176
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 1.349 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RFC_GET_STRUCTURE_DEFINITION 270 156
VMSAP26 xxbid_BID_80 Server RSAR_GET_PROGID_FOR_DEST 2.851 124
But in sm37 no job runs. In sm50 no process. The Process chain doesn’t start …
Best Regards
Etienne
Etienne (BOB member since 2014-01-16)
system
January 17, 2014, 12:15pm
6
ohhh…I’m running out of ideas.
Now…
the chain runs, when you start it from BW side?
Have you checked wether there are shortdumps in BI?
Does the DS user have enough privileges to execute a process chain in BI?
Now, back on DS side:
Can you view data in the open hub?
Have you installed the necessary function groups?(Z_AW*)
furthermore:
BO Data service uses in SAP BW an open hub (type 3rd party) to retrieve data. Thereby data services uses the function module RSB_API_OHS_REQUEST_SETSTATUS to confirm the request and set the overall status of the DTP to green. It may happen that data service cant set the overall status. E.g. the system connection is broken. So the overall status stays in status yellow and no further DTPs on the open hub can be executed.
The status of a DTP transferred to a 3rd party tool can not be changed in the display button in the DTP monitor, because SAP BW setup expects, that the status is set exclusively by the 3rd party tool.
Thus the status has to be set to red manually with the function module RSB_API_OHS_ RE-QUEST_SETSTATUS. The function module changes the status solely for DTPs of open hubs of type 3rd party tool. This procedure is described as a solution in SAP Note 1180294.
Hope this will help you finding a solution…
Bajiman (BOB member since 2011-05-19)
system
January 21, 2014, 3:24pm
7
Hi Bajiman, thanks for your help.
I can start the Process Chain directly in BW. There are no short dumps. The DS has SAP ALL (we checked also by adding S_RS_OHDST )
From BODS we can see the Openhub’s data.
The function group ZAW0 with the Z_AW* function modules exist in BW.
The DTP doesn’t have status yellow because it never starts. The Process chain doesn’t start
Best Regards
Etienne
Etienne (BOB member since 2014-01-16)
system
January 21, 2014, 4:50pm
8
Hi Again,
in Data services management console → SAP Connections I have checked the RFC Server log and I got the next messages:
Any Idea of what the problem could be?
Best Regards,
Etienne
Etienne (BOB member since 2014-01-16)
system
January 22, 2014, 12:08pm
9
Salut Etienne,
I have googled a little bit.
It points to something that I think might be the reason for your error.
Check the following thread:
http://scn.sap.com/thread/1646452
Hope this will help you.
Bajiman (BOB member since 2011-05-19)