PI 7.3 Bean IDOC_INBOUND_ASYNCHRONOUS not found on host

[Former Member]

Hi All,

We have recently installed PI 7.3 and we try to use java IDOC adapter. We follow steps described in this blog:

we try to send IDOCs from our ERP system to PI.

Error message in SM58:

Bean IDOC_INBOUND_ASYNCHRONOUS not found on host xxx

Steps we did for setup:

1. Create communication channel for sender idoc like in blog

2. NWA setting from blog (step 2)

3. RFC settings in ERP system (step 3 from blog)

4. port setup in ERP system for new RFC destination

5. partner profile setup for specific idoc and port (DEBMAS / RFC dest)

Are thre any steps missing? There is only one OSS note for this issue that does not apply to PI system.

Thanks in advance for any help.

br

Dawid

[Former Member]

Hi Dawid,

Remove the JCO RFC provider. If you use the DEFAULT DESTINATION there is no need of RFC PROVIDER

Regards,

Ashok R

[Former Member]

Hi

I was facing the same issue ..

Is there any exact solution ..

Regards,

Raj

[suman_saha]

Have you maintained outboundRA_CF configuration properties?

[Former Member]

Are you resending the failed message from SM58?

Just try to generate a new IDOC via WE19 after you have made sure that the JAVA RFC XI_IDOC_DEFAULT_DESTINATION points to a System with the IDOC metadata (this cannot be XI)

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

Configuring the IDoc Adapter (Advanced Adapter Engine)

You use this procedure to configure an IDoc adapter (AAE) that transfers information between SAP or non-SAP systems using IDocs (intermediate documents).

Prerequisites

u2022 You have created an RFC destination with a name XI_IDOC_DEFAULT_DESTINATION, and you have configured it on the adapter engine using the NWA

Recommendation

The destination must point to an SAP application system that contains metadata for frequently used IDoc types as the RFC destination.

More information: Maintaining RFC Destinations

[Former Member]

Hi David,

Error messge tells that., corresponding java idoc adapter bean (EJB) is not found in the J2EE engine. It means that, java idoc adapter content is not properly installed or some problem while deploying this content. You can check whether this EJB bean is present in the J2EE engine or not with the help of EJB Container service present in the NWA.

In EJB Container service you will find all the java EJBs deployed and which are running. Just try to search in this service whether this idoc adapter EJB is deployeed properlly or not. Another service called JNDI registry in the NWA also helps you to find the deployed EJB's JNDI name.

Please check these two services it may help you.

Thanks,

RK