IDoc Sender Channel Error in PI 7.31 Single Stack (IDoc_AAE)

[Former Member]

Hi all,

we are facing a problem while sending IDoc from SAP ERP to PI. We use PI 7.31 SP05 single stack with all latest patches until 2012-06-12. In sender system we created RFC destination in SM59 type T with registered programm ID. Connection check is successful. In PI we created sender channel with adapter IDoc_AAE and Integrated Configuration for message processing. Test for channel in channel monitoring is successful.

IDoc gets stuck in ERP system in SM58 and shows error

Commit fault: ASJ.ejb.005043 (Failed in component:

After that also channel monitoring shows error

Processing error = null

In log of NWA it shows

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@7335379c 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 <domain>|EPICLNT000)

at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:664)

at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2443)

at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)

at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)

at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)

at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:8292)

at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:245)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Caused by: RfcException: [<domain>|EPICLNT000]

message: 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@7335379c 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

Return code: RFC_FAILURE(1)

error group: 104

key: RFC_ERROR_SYSTEM_FAILURE

Exception raised by <domain>|EPICLNT000

at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2698)

at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2537)

at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2358)

... 8 more

Error raises also if IDoc is sent to PI from other SAP system.

Do you have any ideas? You are very welcome for every hint.

Best regards

Philip

[nabendu_sen · Accepted solution]

Hi Philip,

As you mentioned you can see the error when sending IDocs from other systems also, can you please confirm you have maintained all the needed configuration mentioned in the below blog at PI side.

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

[Former Member · Accepted solution]

Hi Nabendu,

we checked configuration with blog you mentioned. Everything is configured as described except creation of JCo RFC Provider with name XI_IDOC_DEFAULT_ SID in PI, because this leads to another error. This blog does not mention creation of this JCo in PI:

http://scn.sap.com/people/william.li/blog/2011/05/04/configuring-pi-730-java-idoc-adapter

Best regards,

Philip

[Former Member · Accepted solution]

Philip, you're correct that you should not create the JCo RFC. The inboundRA will create and start the RFC Program automatically. If your connection test is working, then it shows the RFC is starting up properly.

As for the error, as you can imagine, there are many things that could be the cause. In the past, we've had that error a few times but the root cause was not the same every time. I would suggest you dig a bit deeper in the log to see if there is more detail on the error. I've found that sometimes the real error does not even mention IDOC processing and so can easily be overlooked.

Some examples of the issues we've had that resulted in the same error include:

1. In WE21 in ECC, 'Queue processing is supported' was checked, although we did not enable the Queue Handler in PI.

2. The inboundRA was missing the BindingKey (we missed this because in read-only mode, NWA does not let you scroll)

3. The inboundRA was missing the ECC system in the multiRepository value (the help docs are unclear when this is needed and when it is not, but we always add every SAP system to this)

4. The Business System we configured the Scenario was linked to the wrong Tech System in SLD so the inboundRA was not finding the Business System at runtime.

Hope one of these helps.

[Former Member · Accepted solution]

Hi Jonathan,

these are very helpful and professional hints and we checked every single one of them. But unfortunately none of them helped. But we also see this error:

Message: while trying to invoke the method com.sap.aii.af.service.cpa.Channel.getChannelName() of an object loaded from local variable 'channel'

Category: /Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/IDoc

Place: com.sap.aii.af.idoc.inbound.IDocReceiverBean.getRealCause(Exception)

Application: sap.com/com.sap.aii.adapter.idoc.app

Customer Message Component: BC-XI-CON-AFW

Runtime Component: com.sap.aii.af.lib

Maybe that help to find the cause for this error.

Thanks,

Philip

[Former Member · Accepted solution]

Hi Jonathan,

with help of SAP Development Support we now found the reason for this error. There is a bug in ESR when you copy an IDoc receiver channel template and only switch once from receiver to sender, then module does not change from "IDocOutboundModuleBean" to "CallSapAdapter". But if you switch to sender, back to receiver and again to sender, then module changes to correct one.

We used such a buggy configured channel template in IB and that is why there was the wrong module in it. We changed to correct module and all worked fine.

Best regards,

Philip

[Former Member]

Hello,

I hope you have created the ICO object (end to end interface) for the Idoc which you are triggering from SAP system??

Check this thread also :

http://scn.sap.com/message/13699610#13699610

Thanks

Amit Srivastava

[Former Member]

Hello Amit Srivastava,

sure, I wrote in PI we created sender channel and Integrated Configuration.

Best regards,

Philip

[Former Member]

Hi Philip,

Can you check the H type destination created for AAE in ECC and check the sxmb_adm for configuring the parameter IS_URL.

Thanks,

Satish.

[Former Member]

Hi Satish,

this is no proxy configuration. Type of RFC in ECC is T.

Best regards,

Philip

[Former Member]

Hi Philip,

Check the below blog.

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

Thanks,

Satish.

[nabendu_sen]

Hi Satish,

I think in Sender SAP system, you need to create connection type 'T' (TCP/IP), not 'H' (HTTP Connection to ABAP System).