Hi all,

We are facing an issue while receiving the idocs from SAP server.
When we check in sm58 screen, we could see the below error
‘Bean IDOC_INBOUND_ASYNCHRONOUS not found on host ss’

We are using SAP 6.5 adapter.

Thanks,
Ravi

Ravi,

Can you provide more details? what are you seeing in the transactions tab? can you see the IDOC? If you see it what is the status of it? Confirmed or Rollback? What do you see in the SAP log file under logging tab of the Adapter home page?

Cheers,
Akshith

HI Akshith,

Thanks a lot for the reply.

I am unable to see anything either in the transaction or in the adapter logs.

Please give me your mail id, i can mail you the screen shots.

Thanks,
Ravi

Ravi,

you can reach me at *******@yahoo.com

Cheers,
Akshith

Hi Akshith,
Below are the details:
JCo MiddlewaresapjcorfcJCo Version2.1.8 (2006-12-11)JCo Middleware Version2.1.8 (2006-12-11)jRFC Library Version2.1.8 (2006-12-11)jRFC Library LocationD:\webMethods712\IntegrationServer\lib\sapjcorfc.dllRFC Library VersionThis RFC library belongs to the SAP R/3 Release *** 640,0,165 *** MT-SL Versions of SAP internal libraries: dptr: 2 ni : 37 cpic: 3 rfc : 3 IDoc Library Version1.0.4 (2006-10-10)JCoIDoc Library Version

1.0.8 (2008-01-31)
SAP Connection details:
Connection AliasSSECVPIV User NameSRINIVASP Password****** Client700 LanguageEN Load BalancingOff Application Server172.18.139.210 System Number00 Logon GroupMessage ServerSystem IDExternal RFC ServerNo Program IDWEBMET Gateway Hostssecvpiv.corp.satyam.ad Gateway Servicesapgw00 Repository Serverssecvpiv.corp.satyam.ad SNC EnabledNo SNC Quality of ServiceUse global build-in default settings SNC NameSNC Partner NameSAP Router StringUse SAPGuiOff RFC TraceOn ABAP DebugOff Log transaction statusOn Store message bodyOn

SAP Listener :
Program IDWEBMET Gateway Hostssecvpiv.corp.satyam.adGateway Servicesapgw00 Number of Threads2 Repository ServerSSECVPIV SNC EnabledNo SNC Quality of ServiceUse global build-in default settings SNC NameAuthorization ServiceUnicode ListenerNo RFC TraceOn Log transaction statusOn Store message bodyOn
and i have created a routing notification.
with Sender:ECV700, Receiver:RCV_WEBMET,Msg type:DEBMAS
Transport:IS

Settings at SAP server:

Sender:ECV700
Receiver:RCV_WEBMET
Msg type: DEBMAS

They have created RFC destination ‘WEBMET’ and connection was successful.

When they are trying to send an Idoc, i am not seeing anything in Transactions, SAP logs or rfc trace files.

We could see the error, only in sm58 screen.

‘Bean IDOC_INBOUND_ASYNCHRONOUSnot found on host’.

In my SAP logs i could see

2009-06-10 10:39:54 IST [SAP.0104.0002D] SAP Listener started: WEBMET on 172.18.139.210(sapgw00)
2009-06-10 10:39:54 IST [SAP.0104.0001D] Starting Listener for WEBMET on 172.18.139.210(sapgw00)
2009-06-10 10:39:54 IST [SAP.0104.0003D] Accepting requests for WEBMET on 172.18.139.210(sapgw00)
nothing other than this.

I think, the listener is able to connect to SAP system, but while retreiving the idoc it may be searching for the bean IDOC_INBOUND_ASYNCHRONOUS to retreive the idoc.
I am not sure, where exactly its going wrong.

Thanks,
Ravi

Hi,

We have applied the fix

WmSAP_6-5_SP1_Fix14

Thanks,
Ravi

Is this issue resolved now after applying the fix?

Akshith

HI Akshith,

The issue was with RFC destanation. SAP team have registered the Program Id in Java Stack of SAP server.

Now they removed the registration from the java stack and they are able to send the idocs.

But, while receiving the idocs, i am getting errors

=======
Listener - Create AC128BD26D2C4A2FB4C32C11
2009-06-10 19:17:37 IST [SAP.0104.0010V5] Listener Thread state changed from [SL] to [SLT] (WEBMET on ssecvpiv.corp.satyam.ad)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.onCheckTID() with rc = RFC_OK leave, [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() enter, [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getServerObject() enter, [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getServerObject() with rc = RFC_OK leave, [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0104.0010V5] Listener Thread state changed from [SLT] to [SLTB] (WEBMET on ssecvpiv.corp.satyam.ad)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() before RfcIoCtl(8)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() after RfcIoCtl(8) = RFC_OK, parent_rfc_handle = 1
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() before RfcGetName(8,53A2EC9C)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() after RfcGetName(8,IDOC_INBOUND_ASYNCHRONOUS) = RFC_OK
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getAttributes() before RfcGetAttributes(8)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getAttributes() after RfcGetAttributes(8) = RFC_OK
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getCpcConverter() before RfcSetCodepage(8,“4103”)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getCpcConverter() after RfcSetCodepage(8,“4103”) = RFC_OK
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getCpcConverter() codepage-converter: 4103 (UnicodeLittle)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() before RfcSncMode(1)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() after RfcSncMode(1) = RFC_OK (off)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.createRecord(“TABLES”(4C383004),53A2EA94) enter [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.createRecord(“EDI_DC40”(4C383048),5386BBC8) enter [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getTypeHandle() before RfcInstallStructure2(“EDI_DC40”,538C7728,36,5386BC6C)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getTypeHandle() after RfcInstallStructure2(“EDI_DC40”,538C7728,36,5386BC6C) = RFC_OK
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.createRecord(“EDI_DD40”(4C3830E4),5386BC94) enter [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getTypeHandle() before RfcInstallStructure2(“EDI_DD40”,526499E0,7,5386BD38)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getTypeHandle() after RfcInstallStructure2(“EDI_DD40”,526499E0,7,5386BD38) = RFC_OK
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() before RfcGetData(8)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() after RfcGetData(8) = RFC_OK
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() before RfcGetClientIdEx(8)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() after RfcGetClientIdEx(8) = RFC_OK received length 185
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.reallocRecordBuffers() enter, [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.reallocRecordBuffers(“TABLES”(4C0E2050),53A2EA94) enter [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.reallocRecordBuffers() with rc = RFC_OK leave, [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() before dispatchRequest(“IDOC_INBOUND_ASYNCHRONOUS”)
2009-06-10 19:17:37 IST [SAP.0104.0024V5] Listener - Executing inbound request with IS user “SAPUser”.
2009-06-10 19:17:37 IST [SAP.0106.0004W] Error in inbound call for IDOC_INBOUND_ASYNCHRONOUS from SSECVPIV: java.lang.NullPointerException
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() caught the following exception: java.lang.NullPointerException
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() Exception.message = “java.lang.NullPointerException”
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.abort() enter, [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.abort() before RfcAbort(1,“java.lang.NullPointerException”)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.abort() after RfcAbort(1,“java.lang.NullPointerException”)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.abort() with rc = RFC_OK leave, [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler(): catch an application exception java.lang.NullPointerException
2009-06-10 19:17:37 IST [SAP.0104.0010V5] Listener Thread state changed from [SLTB] to [SL] (WEBMET on ssecvpiv.corp.satyam.ad)
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.incomingRequestHandler() with rc = RFC_FAILURE leave,
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.onRollback() enter, [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getServerObject() enter, [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0102.0001V3] [JNI-LAYER] RFC.getServerObject() with rc = RFC_OK leave, [SUCCESS]
2009-06-10 19:17:37 IST [SAP.0110.0004D] Listener - Rollback AC128BD26D2C4A2FB4C32C11

=====================

Please help me, if you have faced this kind of issue earlier.

Thanks,
Ravi

Ravi,

Check if the IDOC has any extension, If it does then you will have to include it in the Cim filed of the Adapter notification and reload the values. On the SAP side i think the name of this filed should be something like “IDOC extension” or “Basic Exension”. Even if this filed is same as the IDOC name, you will have to include the same in the cim Extension filed.

Cheers,
Akshith

Hi,

The Idoc we are using is a Basic type and doesnt have any extension.

In case of Routing Notification, we have specified the msg type. I think, it is not coming to routing part, getting failed at Listener itself.

Thanks,
Ravi

Ravi,

From the error message you posted earlier i beleive that the IDOC is coming to IS and then changing the status to Rollback instead of Confirmed. If you go to the transactions tab on the SAP Adapter admin page, what is the message type that you see for this IDOC? Is it same as the IDOC name that you mentioed in your Listener?

Hi Akshit,

I am just getting this in Transactions.
Transaction Status Current State Rolledback Received Message Body Message body not persisted…
Audit Log 2009-06-16 13:37:25.075 IST Listener - Create AC128BD21CCA4A374C04C748 2009-06-16 13:37:25.106 IST Listener - Rollback AC128BD21CCA4A374C04C748

Ravi,

Run the service pub.sap.transaction:getMessageBody from developer and see if you can see the IDOC in the results tab. The input will be the transaction ID “AC128BD21CCA4A374C04C748”

Thanks,
Akshith

ravi,

Did you check in the SAPAdapter page View Listener page in the properties section

Store message body - On

HTH,
RMG,

Hi,

Yes, I have set the property ‘Store message body - On’.

I have tried the service,
pub.sap.transaction:getMessageBody, giving tid as input.
But i did not get the idoc. I just got ‘$msgBodyNotFound’ value as true.

I have also checked the messages stored in ‘WmSAP\txStore’, but couldn’t find any msg.

I could see the below in rfc trace files.
=========================–
Received RFCHEADER [5]: 01/LIT/IEEE/SPACE-U2/4103
Error ab_RfcSetHeader> invalid compression value 5 received
Error in program ‘WEBMET’: <* RfcDispatch [5] : returns 1:RFC_FAILURE

RfcIsValidHandle [5] …
<* RfcIsValidHandle [5] : returns 0:RFC_OK

RfcAbort called by external program …
handle = 5
text = RFC_ERROR_SYSTEM_FAILURE: See RFC trace file or SAP system log for more details
===========================

Does it depend on the codepage?

Thanks,
Ravi

Hi,

Thanks for all your help. The issue was with RFC creation. After creating a new RFC destination in sm59, issue got resolved.

Thanks,
Ravi