RFC adapter in XI 3.0 not working properly with BAPI in R/3 4.6C

[Former Member]

Here is the scenario.

An XML file is received from our customer. This file contains purchase order information that is used to create a sales order in our SAP 4.6C system. Once the sales order is created an acknowledgement is generated and this is returned back to our customer in an XML format. This scenario is working perfectly fine in our XI 2.0 system but is not working properly in our XI 3.0 test environment. Our custom function module in R/3 is a wrapper function that uses a standard SAP BAPI to create the sales order. Part of the function module does use the statement

call function 'BAPI_TRANSACTION_COMMIT'

The last thing the BAPI does is call another function module that using an RFC destination that will return and order acknowledgement.

Here is what happens within XI and our SAP system.

The XML file is received and mapped to our imported RFC. The RFC adapter is called and the information is passed onto SAP where our customer function module executed. The sales order is created within SAP without any problems and the second function module is called which references an RFC destination assigned to our XI 3.0 system. The information is sent back to XI and an appropriate file is created for our customer. All seems to be working properly except that when the original RFC is sent from XI to SAP, SAP creates a short dump stating

"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:" Then it is put back into the que where 5 minutes later it executes again and trys to recreate the sales order in SAP. (again, this same function module executing from XI 2.0 works fine)

I believe I have everything configured properly because the SAP side is being executed and I am successfully passing information back from SAP to XI. However the original function module in SAP is failing with the above error message. It appears that the original function module cannot communicate back with XI. I have had SAP looking at this issue and they have not been successful yet in solving this problem.

Any ideas.

Thanks,

Jim d'Hulst

[ravi_raman2]

Did this ever get fixed...........or are there any updates on it.

[bhavesh_kantilal]

Think this issue was because this question was posted before SP 14 was release and RFC adapters did not have Commit for BAPI 's before SP14.

After SP 14 , RFC adapter has a setting where you can commit BAPI calls and that should help.

Read the online help of the receive RFC adapter that talks abt the option to commit BAPI's,

Regards

Bhavesh

[Former Member]

Hi,

I think the problem is with the send back of acknowledgement to XI. Does the DeliveryException state something about the sender agreement? I guess you are using a statement like below:

CALL FUNCTION 'ZABCD'

destination <tcp/ip destination>

exporting

input = ack.

In that case, check whether the TCP/IP destination is working fine. Also, to be able to exchange message, the structure of the Function Module ZABCD needs to be identified as the sender in XI Configuration (Integration Directory).

Also, check your config with the blog mentioned below:

<a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit">/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit</a>

Regards,

Amitabha