FIM job fails after transfer to Target system

[phadke_manas]

Hi All,

We're using FIM10 SP17 PL03. We created a standard FIM job with a custom SAP datasource from a S4 system as the source and FC 10.1 as the target. After testing it successfully in Dev env, since its a standard FIM job we moved it to target env by exporting the job as an xml alongwith the dependencies and importing it into the target env. However after importing, the job fails when executed in target env with the below error message.

We have checked the datastores being used by this job in the target FIM env and they test successfully. Any ideas on what might be causing this issue and how to resolve this?

Regards,

Manas Phadke

(14.2) 10-06-20 10:13:09 (E) (4032:1428) R3C-150301: |Dataflow DF_EXPORT_XXXYYYZZ
Error opening file <C:/ProgramData/SAP BusinessObjects/Data Services/abap/XXXYYYZZ>.
(14.2) 10-06-20 10:13:09 (E) (4032:1428) R3C-150301: |Dataflow DF_EXPORT_XXXYYYZZ
Error opening file <*****>. This message contains some internal system details which have been hidden for security. If you need to see the full contents of the original message, ask your administrator to assign additional privileges to your account.
(14.2) 10-06-20 10:13:09 (E) (4900:9496) SYS-050604: |Session XXXYYYZZ|Data flow DF_EXPORT_XXXYYYZZ
Cannot write pipe, due to error <The pipe has been ended. >.
(14.2) 10-06-20 10:13:09 (E) (4900:9496) RUN-050409: |Session XXXYYYZZ
The job process could not communicate with the data flow <DF_EXPORT_XXXYYYZZ> process. For details, see previously logged error <50604>.
(14.2) 10-06-20 10:13:09 (E) (4900:9496) RUN-050316: |Session XXXYYYZZ
Cannot write pipe, due to error <The pipe has been ended. >.
(14.2) 10-06-20 10:13:09 (E) (4900:9496) RUN-050304: |Session XXXYYYZZ
Function call <raise_exception ( Cannot write pipe, due to error <The pipe has been ended. >. ) > failed, due to error
<50316>: <Cannot write pipe, due to error <The pipe has been ended. >.>.
(14.2) 10-06-20 10:13:09 (E) (4900:9496) RUN-050304: |Session XXXYYYZZ
Function call <*****> failed, due to error <*****>: <*****>. This message contains some internal system details which have been hidden for security. If you need to see the full contents of the original message, ask your administrator to assign additional
privileges to your account.
(14.2) 10-06-20 10:13:09 (E) (4900:9496) RUN-050316: |Session XXXYYYZZ
Cannot write pipe, due to error <The pipe has been ended. >.

[phadke_manas · Accepted solution]

There was a difference in the generated ABAP directory path in the FIM Admin console in the source and target FIM environment. Correcting the path in the exported atl file as per the target system setting to the desired value and reimporting resolved the issue.

[pierre_bournaveas]

Dear Manas,

Regarding the log you have attached, your job is failing during the EXPORT, so during the extraction of the data in S4 system.

Be sure that your new environement have acces to this S4 system and check if you have configure the same way the 'ABAP Execution option' in the FIM Administration console.

Moreover, it seems to be related more to a DataServices issue than FIM..

Thank you

Best Regards,

Pierre

[phadke_manas]

Many thanks for your prompt reply Pierre. I have checked the datastore which connects to the S4 system in FIM alongwith the RFC Server interface in DS which is being used in the datastore and both are working. Also the ABAP execution option in the FIM Admin console as well as in the JOBNAME_ECC_EXPORT_DS are as expected. Do you have any other pointers?