Skip to Content
0
Former Member
Aug 29, 2007 at 09:25 AM

RFC -> XI Commit Fault error

350 Views

Hi All

I have created an RFC (from R/3) that I am using to trigger a BPM in XI (3.0).

<b>RFC Destination - SM59</b>

I have set up the RFC Destination in R/3 as follows:

Connection Type = T

Activation Type = Registration

Program ID = zabfcxi

GatewayHost = Trx SMGW -> HostName = R/3 system (i.e. NOT the XI server)

GatewayService = sapgw00

<b>XI Sender Communication Channel - CC_RFC_SENDER</b>

In XI I have configured a RFC Sender communication channel as follows:

<i>RFC Server Parameter</i>

Application Server = Trx SMGW -> HostName = R/3 system (i.e. NOT the XI server)

Application Server Service = sapgw00

Program ID = zabfcxi

<i>RFC Metadata Repository Parameter</i>

Application Server = Trx SMGW -> HostName = R/3 system (i.e. NOT the XI server)

System Number = 00

Logon User/Password = myUser and myPassword

Logon Language = EN

Logon Client = 041

<b>Sender Agreement</b>

I have also set up a sender agreement:

Service = R3_DEV_030

Interface = Z_RFC_GET_SO_REQUESTS2 (name of RFC imported to XI)

Sender Comm channel = RFC Sender adapter defned above

When I run the test connection in SM59 it works without any problems.

I have written a small ABAP that calls the RFC:

CALL FUNCTION 'Z_RFC_GET_SO_REQUESTS'
  IN BACKGROUND TASK
  DESTINATION 'Z_ABFC_XI'
  EXPORTING
    REQUEST_SALES_ORDERS = export.
COMMIT WORK.

When I run this it completes with no errors. However, nothing appears to be getting through to XI. I have checked the log in SM58 and find that it is failing with this error:

Commit fault: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup

I have followed the SAP note "FAQ XI 3.0 RFC Adapter" qu.19 which states this is caused by incorrect Sender agreement but it all looks OK to me - hence why I have posted the details of it. I have also performed a full refresh of the cache but this has not fixed it either.

Is anybody able to help...?

Thanks

Andy