RFC adapter as sender

[Former Member]

Hi,

I want to configure a scenario to use an RFC in R/3 as sender to XI. The process should trigger from R/3 by executing an RFC. The RFC destination given is a XI system maintained in SM59 as a TCP/IP connection type. But after executing the RFC no message is sent out from R/3 and I'm getting the following exception :

"com.sap.aii.af.rfc.afcommunication.RfcAFWException: alternativeServiceIde"

Can anyone help me in this regard?

Thanks in advance,

Dipankar

[Former Member · Accepted solution]

Dipankar,

Here is what you need to do in the following scenario:

R3_BACKEND --> RFC_ADAPTER --> XI --> SOME_SYSTEM

In order to configure the rfc adapter which in this case would be an inbound rfc adapter, you need to:

1. Register program id Rfc2XmbService in XI. This can be done using the J2ee administration tool and usually Basis does this.

2. Setup at TCP/IP RFC Destination in the R3 system with the following parameters:

Select "Registration" Button.

Program Id: Rfc2XmbService

Hit enter.

Menu->Gateway Options:

Gateway host: appropriate value

Gateway service: sapgw<system_number> For ex: sapgw00

3. Configure the rfc_apapter per the documentation. Start it and make sure its "Started" not just "initialized".

4. After this, go back to R3 and test the TCP/IP RFC Destination. You should get a successful test.

I think that's about it.

- Ravi

Message was edited by: ravi kumar

[Former Member · Accepted solution]

Ravi/Anyone,

Here are my questions. I appreceiate for any response.

1)Should the Program ID be "Rfc2XmbService"? Can it be any other name?

2)If the it can be any, then what difference does the J2EE engine see between

"Rfc2XmbService" and "Xmb2RfcService" id all the setup info are identical?

3) In the "call function Zfunction", what excatly is this Zfunction pointing to? Is it the Inbound Interface of the Sender system on XI?

Please let me know

THX

[Former Member]

HI all,

I am doing File to RFC scenario after completing my comfiguration my data is not moving to R/3. I dint get any error in the XI point of view but my data is not getting posted into r/3 will there be some mandatory fields to be mapped here to transfer data to R/3(No errors found even after executing the mapping).

Please suggest

Regards,

Naveen.

[Former Member]

Pls. check in RWB for the message which is not successful from XI to R/3. I think that should go to 'System Error' status.

[Former Member]

Eighth out that you build a TCP / IP Connection to your XI system. Have you entered the right program-ID in the communication channel of XI? Displays SMGW transaction this program-ID on your R/3 machine? Can you ping this ID from SM59 on R/3 site locally? You have to address this program-ID on your local R/3 machine! Do not forget it!

Have you actually solved the problem?

Best Regards,

Hüdayi Mengus

[Former Member]

Hi,

Check this Link:

Regards,

Hüdayi

[Former Member]

Hi,

I assume you use XI 3.0.

An error like com.sap.aii.af.rfc... says, that you are at least in the adapter framework of XI. 'No binding found in CPA-Cache' says, that the adapter framework doesn't know what to do with the call. The binding needs to be set in the directory in the communication channel and sender contract which links the channel to an interface. If there is no sender contract/agreement, the adapter framework doesn't know how to handle the request (which business system, which scenario).

If you have configured all of this there may be a problem with the cache update. In the directory go to the menu environment->cache update. If there is anything red you have a problem with the connection from your directory to the adapter framework. Every time you change the channel, the directory notifies the adapter framework, which starts to pull the new configuration from the directory. If one way is broken down, the adapter framework doesn't get the binding.

It could be a security problem. We needed to undeploy an redeploy the directory using SDM.

I never get the message ...alternativeServiceIde

Check if you have only one receiver agreement for this interface and business system/partner. Unfortunately the error messages in the tRFC log (Sm58) are cut, so you won't see the full information. Maybe you get more information from the xi log using the visual administrator.

The ProgramId names Rfc2XmbService and Xmb2RfcService (used for the external XI 2.0 adapter engine) are just identifiers. They need to be the same on both sides (XI directory and R/3 Sm59 Destination), thats all.

The XI Outbound RFC Adapter registers to the gateway of the R/3 system. The R/3 findes the connection using the ProgramId. If it's not the same you get an 'ProgramId not registered' error in SM58. Notice that there can register more than one external server with the same ProgramId. You will get LoadBalancing or you get confused because some messages work and others not (because both registered servers get some messages).

Hope that helps.

Regards

Christian

[Former Member]

The error "com.sap.aii.af.rfc.afcommunication.RfcAFWExceptionlookup of alternativeServiceIdentifier via CPA-cache failed for channel" Could occur if XI plugin are missing on R3 system. Get help of the guy who installed the system for you and make sure that link between XI and SAP is set up.

[Former Member]

Hi,I check 1 and 3 no problem,but 2:

2)If the it can be any, then what difference does the J2EE engine see between

"Rfc2XmbService" and "Xmb2RfcService" id all the setup info are identical?

I can't know to do, can you tell me? thanks!

and today , I find Server Log in SLD administratortion,error log with red color:

#151 12/30/2004 09:34:34.562 [RfcServer[RfcP08_800SenderNPR]1] ERROR com.sap.lcr.sagent.SAPProxyServer: JCO Server exception raised: CPIC-CALL: SAP_CMACCPTP

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR internal error

TIME Thu Dec 30 09:34:34 2004

RELEASE 640

COMPONENT NI (network interface)

VERSION 37

RC -1

COUNTER 34

Thrown:

RfcException:

message: CPIC-CALL: SAP_CMACCPTP

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR internal error

TIME Thu Dec 30 09:34:34 2004

RELEASE 640

COMPONENT NI (network interface)

VERSION 37

RC -1

COUNTER 34

Return code: RFC_FAILURE(1)

error group: 102

key: RFC_ERROR_COMMUNICATION

at com.sap.mw.rfc.api.RfcApi.RfcAbort(RfcApi.java:918)

at com.sap.mw.jco.MiddlewareJRfc.abort(MiddlewareJRfc.java:448)

at com.sap.mw.jco.MiddlewareJRfc$Server.abort(MiddlewareJRfc.java:1552)

at com.sap.mw.jco.JCO$Server.abort(JCO.java:6502)

at com.sap.mw.jco.JCO$Server.listen(JCO.java:6828)

at com.sap.mw.jco.JCO$Server.run(JCO.java:6660)

at java.lang.Thread.run(Thread.java:534)

#150 12/30/2004 09:34:34.562 [RfcServer[RfcP08_800SenderNPR]1] ERROR com.sap.lcr.sagent.SAPProxyServer: JCO Server exception raised: CPIC-CALL: SAP_CMACCPTP

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR internal error

TIME Thu Dec 30 09:34:34 2004

RELEASE 640

COMPONENT NI (network interface)

VERSION 37

RC -1

COUNTER 34

Thrown:

RfcException:

message: CPIC-CALL: SAP_CMACCPTP

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR internal error

TIME Thu Dec 30 09:34:34 2004

RELEASE 640

COMPONENT NI (network interface)

VERSION 37

RC -1

COUNTER 34

Return code: RFC_FAILURE(1)

error group: 102

key: RFC_ERROR_COMMUNICATION

at com.sap.mw.rfc.api.RfcApi.RfcAbort(RfcApi.java:918)

at com.sap.mw.jco.MiddlewareJRfc.abort(MiddlewareJRfc.java:448)

at com.sap.mw.jco.MiddlewareJRfc$Server.abort(MiddlewareJRfc.java:1552)

at com.sap.mw.jco.JCO$Server.abort(JCO.java:6502)

at com.sap.mw.jco.JCO$Server.listen(JCO.java:6828)

at com.sap.mw.jco.JCO$Server.run(JCO.java:6660)

at java.lang.Thread.run(Thread.java:534)

#149 12/30/2004 09:34:34.562 [RfcServer[RfcP08_800SenderNPR]1] ERROR com.sap.lcr.sagent.SAPProxyServer: JCO Server exception raised: CPIC-CALL: SAP_CMACCPTP

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR internal error

TIME Thu Dec 30 09:34:34 2004

RELEASE 640

COMPONENT NI (network interface)

VERSION 37

RC -1

COUNTER 34

Thrown:

RfcException:

message: CPIC-CALL: SAP_CMACCPTP

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR internal error

TIME Thu Dec 30 09:34:34 2004

RELEASE 640

COMPONENT NI (network interface)

VERSION 37

RC -1

COUNTER 34

Return code: RFC_FAILURE(1)

error group: 102

key: RFC_ERROR_COMMUNICATION

HELP ME!!!!!!

Message was edited by: zeng lyh

[Former Member]

Now,I find a new phenomenon&#65292;

Description of the business scenario to be implemented:

Send message from R/3 system to XI system using the RFC adapter.

We have been successful in development(DEV) and test system(QA), but in our production(PRD), we is unsuccessful.

In the production(PRD), the host name of R/3 system is "cl0_1svc" , Call transaction SM51, we see the following information:

Server names : cl0_1svc_P04_00

Host name: cl0_1svc

(Note: This host_name include the character "_", but DEV and QA no include the character "_")

We face two problems:

1. When we import RFC in the Integration Builder of XI, appearing a "Differant System" warning windows,

message:

System 1svc is running on the specified application server. However,

source system P04 is specified in software component version

E_PROCUREMENT_PR, 4.0 of Sinopec ec Do you want to disconnect?

Ask:

Separate or Continue

2. In SAP R/3 system, we running the program call the RFC, the RFC is successfully finished,

but Call transaction SM58, we see the following error information:

com.sap.aii.af.rfc.afcommunication.RfcAFWException : lookup of binding via

Can you help us?

Thanks

[Former Member]

Hi,I have big problem and i don't know what can i do.

the same problem and the same error I got.

I can't get something by see SAP Notes 730870 and 775765 ,

Please help me.

Thanks in Advance.

lhb

[former_member185751]

Hi,

I'm also facing a similar problem.

I did a "Test connection" from my R/3 system and its working fine. but when i'm executing my RFC program it fails throwing the following error

"com.sap.aii.af.rfc.afcommunication.RfcAFWException : lookup of binding via"

I checked the DEV_RFC trace file and it has the following info:

• Trace file opened at 20041028 101803 EDT SAP-REL 620,0,1422 RFC-VER 3 647244

======> com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http:/

ABAP Programm: SAPLARFC (Transaction: )

Called function module: ARFC_DEST_SHIP

User: 12345 (Client: 300)

Destination: XI (handle: 2, convid , {417F9E21-0E35-00B2-0000-00008ADC0385})

SERVER> RFC Server Session (handle: 1, convid 73113364, {417F19DA-0E24-00B8-0200-00008ADC0385})

SERVER> Caller host: sapss01_CFG_03

SERVER> Caller transaction code: (Caller Program: SAPLQOWK)

SERVER> Called function module: ARFC_RUN_NOWAIT

• Trace file opened at 20041028 101803 EDT SAP-REL 620,0,1422 RFC-VER 3 647244

======> CPIC-CALL: 'ThSAPECMINIT'

Transaction program not registered

ABAP Programm: SAPLARFC (Transaction: )

User: 12345 (Client: 300)

Destination: XI (handle: 3, convid , )

SERVER> RFC Server Session (handle: 1, convid 73113364, {417F19DA-0E24-00B8-0200-00008ADC0385})

SERVER> Caller host: sapss01_CFG_03

SERVER> Caller transaction code: (Caller Program: SAPLQOWK)

SERVER> Called function module: ARFC_RUN_NOWAIT

Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1453

CPIC-CALL: 'ThSAPECMINIT'

Transaction program not registered

DEST =XI

HOST =%%RFCSERVER%%

PROG =INTEGRATION_SERVER_XID

GWHOST =sapss01

GWSERV =3303

Can anyone please help?

Thanks

Sridhar

Message was edited by: Sridhar Rajan Natarajan

[former_member185751]

Hi,

I found that both

com.sap.aii.af.rfc.afcommunication.RfcAFWException : lookup of alternativeServiceIdentifier via CPA-cache failed

AND

com.sap.aii.af.rfc.afcommunication.RfcAFWException : lookup of binding via CPA-cache failed

are documented bugs which are fixed in patch level 5 of AFC SP5

Please refer to SAP Notes 730870 and 775765 for the resolution.

Regards,

Sridhar

[former_member4529]

Hi Ravi,

what do exactly mean by configuring the adapter? Is it configuring the RFC adapter communication channel as sender in the Integration Directory? I've configured the configuration channel in the Integration Directory and the SM59 in R/3 side. The test connection from SM59 is working fine. But when I execute the RFC I'm getting the same error msg "com.sap.aii.af.rfc.afcommunication.RfcAFWException" as before.

Do you have any suggestion regarding this?

Thanks

Dipankar

[Former Member]

Dipankar,

Do you at least see the message in SXMB_MONI when u execute ur RFC or the message doesnt even show up in XI ?

Where exactly do you see the error "com.sap.aii.af.rfc.afcommunication.RfcAFWException"

- Ravi

[former_member4529]

Hi Ravi,

No I can't see the message in sxmb_moni of the R/3 system itself and not also in XI system. I see the error message in the tRFC log.