cancel
Showing results for 
Search instead for 
Did you mean: 

RFC Destination unavailable XI_IDOC_DEFAULT_DESTINATION_<SID> with Commit fault: ASJ.ejb.005043

former_member187447
Participant
0 Kudos

Hi Folks,

I know the "Commit fault: ASJ.ejb.005043" is a known issue as the IDOCs get stuck in sm58 in ECC when triggered from ECC. I have the Sender IDOC channel showing the RFC Destination unavailable XI_IDOC_DEFAULT_DESTINATION_<SID>. Infact we have a different name RFC Destination unavailable XI_IDOC_DEFAULT_DESTINATION for our destination in both NWA destiantions and also in the communication channel. Not sure why this other destination is being taken. Is there any other place we could missing? Please suggest.

Regards

Kalyan.

Accepted Solutions (1)

Accepted Solutions (1)

former_member184720
Active Contributor
0 Kudos

What is the destination name that you have configured in InboundRA?

Compare your configuration with the below document and validate all the steps..

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5050119d-9c47-3110-eab0-d90ebd211...

Answers (2)

Answers (2)

former_member187447
Participant
0 Kudos

Was trying use service interface with IDOC as external definition and trying to pass an IDOC in the iflow. That was the issue for this error. Thanks guys for the inputs.

Former Member
0 Kudos

Did you win?

Regards,

Jannus Botha

former_member187447
Participant
0 Kudos

Yes, I changed the service interface to use IDOC directlty

Former Member
0 Kudos

Hi Kalyan,

Have you done all these steps specified in the blog?

http://scn.sap.com/docs/DOC-34155

Regards,

Jannus Botha