PI 7.3 Java Stack - iDoc AAE not processed - IDOC_INBOUND_ASYNCHRONOUS

[Former Member]

Hi all,

We are migrating from PI 7.0 to PI 7.3 Single Stack and I am trying to configure an iDoc interface.

I have followed and read some blogs for this purpose:

http://help.sap.com/saphelp_nw73/helpdata/en/c2/91865252c84716b3b8be394851c9c0/frameset.htm

http://scn.sap.com/community/pi-and-soa-middleware/blog/2010/10/21/pixi-pi-73-new-java-based-idoc-ad...

http://scn.sap.com/thread/2078780

However when I try to send the iDoc from backend to PI it is stucked on SM58.

IDOC_INBOUND_ASYNCHRONOUS

TPICLNT001_AAE

03.06.2013 09:44:23 Commit fault: ASJ.ejb.005043 (Failed in component:

I've checked the RFC and it is working properly. The iDoc does not arrive to the iDoc monitor but I can see a trace on the PI log that says the following:

JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT_PID, Managed_Application_Thread_27, connectionId=2-|sapgw00|XI_IDOC_DEFAULT_PID, Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.adapter.idoc.app, BC-XI-CON-IDO) Exception raised from invocation of public void com.sap.aii.af.idoc.inbound.IDocReceiverBean.onCommit(java.lang.String) method on bean instance com.sap.aii.af.idoc.inbound.IDocReceiverBean@646c65ef for bean sap.com/com.sap.aii.adapter.idoc.app*xml|com.sap.aii.adapter.idoc.ejb.jar*xml|IDocReceiverBean in application sap.com/com.sap.aii.adapter.idoc.app.; nested exception is: com.sap.conn.idoc.IDocRuntimeException (raised by system madarrsipit01|TPICLNT001_AAE)

I tried to make a Stop & Start of the service, checked the inboundRA, JCO, Destinations... but nothing is working. Commication channels are green and running.

Any idea why this is not working?

Thanks for any advice.

Kr,

Joaquín.

[Former Member · Accepted solution]

Hello all,

Thanks for your help.

I've fixed the issue. The Logical System Name of the backend on Bussiness System was missing.

Once I changed the name, the iDoc has arrived properly to PI and then it has been also processed.

Thanks,

Joaquín.

[former_member191435]

Hi,

Can you please check ur rfc destination with PI gateway host and service details.

And make sure that u have to maintain programid in InboundRA and dont use thsis program ID in JCA Resource adapter.

and maintain local as true.

Please let me know if you face any issues.

Cheers,

Cnu

[Former Member]

Hi Joaquín,

This maybe due to two reasons:

1. ICO Configuration missing for the Sender SAP System, IDOC Interface (same as what you are triggering from SAP system) and IDOC namespace?

2. The Program ID used in RFC destination to send IDOC to PI system is being used in more than one Java resource adapter in NWA.

I hope this will be helpful in resolving your issue...

Thanks

Rakesh

[Former Member]

Hi, 

@Loordh; Yes, the default destination is already stablished in the communication channel.

@Bhargava Krishna; I also read that post but nothing.

Still not working.

Any other idea?

Thanks!

Joaquín.

[Bhargavakrishna]

Hi,

Refer this link and check your configuration accordingly..

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

Regards

Bhargava krishna

[allamudi_loordh]

Hi ,

Did you give the Default Desination XI_IDOC_DEFAULT_PID in IDoc Sender Channel.

Regards,

Loordh