RSARFCSE job triggered automatically

[Former Member]

I am running an outbound Idoc. It is getting posted properly but it is also triggering 2 RSARFCSE jobs. I am not sure why this is being done.

Does anyone have any idea as to what might be the reason behind this? Also kindly let me know the use of RSARFCSE program.

Thanks,

Ameya

[Former Member]

Hi,

RSARFCSE Program is triggerred to execute failed trfc communications, so when ur working an IDOC since its a trfc call, the program would`ve been triggerred.

Reward if helpful.

Regards

[Former Member]

The problem exists only for a single outbound Idoc and not for all outbounds. The ALE IDE settings are similar for all of them. Any idea why this is happening?

[laxmanakumar_appana]

Hi,

If the remote system is unavailable, the SAP System schedules the report RSARFCSE for background processing with the relevant transaction ID as variant. This report, which forwards asynchronous calls for execution, is called repeatedly until it succeeds in connecting with the desired system.

Check this link for more details :

http://help.sap.com/saphelp_nw04/helpdata/en/22/042578488911d189490000e829fbbd/content.htm

Regards

Appana

[Former Member]

Hi,

Following documentation is maintained in SE38 tranx for this report,

This report is scheduled by the function 'ARFC_BP_REQUEST' to run in the

background. It transfers all the CALL FUNCTION IN BACKGROUND TASK

objects to the target systems and runs them there. If no connection is

established, it is scheduled again later. If another error occurs, the

report RSARFCDL is scheduled to delete the error log later. This avoids

the need to reorganize ARFC files.

Hope this helps,

Rgds,

[Former Member]

hi,

is the dest. system reachable otherwise does it involve any ale calls

????

regards

[Former Member]

Yes... the Idoc is being sent to the trfc port. All other Idocs are getting posted. Even this one's getting posted but its creating 2 ARFC calls per idoc. The configuration seems proper. Am not very sure why this is happening.

Sorry for the delay. Was busy with something else.