Sender RFC Adapter

[Former Member]

Hi all,

where will be input for following values for RFC Sender Adapter?

RFC Server Adapter :-

Application Server ( Which server IP is required here ( SAP 4.6 or SAP XI)?

Application server service : Where do i find this service name?

Program Id ? This program will be created in which server ( SAP 4.6 or SAP XI)?

RFC Metadata repository parameter :-

Application server ( Which server IP is required here ( SAP 4.6 or SAP XI)?

please do the needful.

Regards

Dragon

[Former Member · Accepted solution]

I was following this blog.

according to blog , i have done all configuration :....

/people/peng.shen2/blog/2010/06/07/rfc-to-jdbc-synchronous-scenario-guide-part-i

On Source Code in RFC ..it is blank, as said in blog ...source code deleted.

but on executing the RFC from 4.6 System from se37 it is giving me following error .

"senderAgreement not found: lookup of binding via CPA-cache failed for

What happened?

Error in ABAP application program.

The current ABAP program "ZBAPI_BANK_GETLIST============FT" had to be

terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

The error occurred in an RFC call to another system.

The target system has also written a short dump.

Consult this short dump for more precise information about

the cause of the error.

[former_member183908 · Accepted solution]

Hi Dragaon,

-->If you are executing the end-to-end scenario by triggering RFC, maintain the RFC destination name of Type T which you had created, in the Function Module while executing.

Thanks

[Former Member · Accepted solution]

Hi

Create the RFC destination as mentioned in Michaels blog.

For testing Import the STFC_connection Fm to XI and configure the scenarios

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f83deb90-0201-0010-189c-8d3ff8757...

After configuration execute the RFC FM.

Note:

if not working

1. clear the full cache

2. Stop and activate the sender channel.

Regards

Ramg

[Former Member · Accepted solution]

Hi,

Error sender agreement...for RFC will occur if you have not associated the logical system name to the business system/service used as a sender..make sure that the logical system name is associated to the same...

check the below thread ...search sdn if still need more info..

HTH

Rajesh

[Former Member · Accepted solution]

i was following this blog.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f83deb90-0201-0010-189c-8d3ff8757...

according to blog , i have done all configuration :....

but on executing the RFC from 4.6 System from se37 it is giving me following error .

:

:

:

:

:

Now .... I am getting following error :-

"lookup of alternativeServiceIdentifier via CPA-cache failed for channel.

Now what is this /?

[Former Member]

Hi all,

thanks for your all comments:

______________________________________________________________________________________

Problem 1 : senderAgreement not found: lookup of binding via CPA-cache failed for

Error is resloved

Error was due to :----

In sender agreement , i had used my made Service Interface name and namespace instead of

RFC NAME :STFC_CONNECTION

NameSpace : urn:sap-com:document:sap:rfc:functions

By correcting this problem has been resolved.

_____________________________________________________________________________________________

Problem 2 : lookup of alternativeServiceIdentifier via CPA-cache failed for channel.

Error is resloved

Error was due to :----

Sender Buisness System - adapter-Specific identifiers -System ID and Client was not correctly maintained

Problem @ actually it was not same as actually Sender System's(4.7D) SystemID from where i was executing RFC by se37.

_____________________________________________________________________________________________

Regards

Dragon

[Shabarish_Nair]

refer - /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

[Former Member]

After doing following changes in sender aggrement

(

INTERFACE : ZBAPI_BANK_GETLIST

NAMESPACE : urn:sap-com:document:sap:rfc:functions

)

earlier i was using sender service interface name and name space

:

:

:

:

:

Now .... I am getting following error :-

"lookup of alternativeServiceIdentifier via CPA-cache failed for channel.

Now what is this /?

[Former Member]

Hi KOMODO,

Please check this link,it will give u clear understanding of RFC sender channel

/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step

Nidhi

[Former Member]

Hi,

Refer: /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step

>> Application Server ( Which server IP is required here ( SAP 4.6 or SAP XI)?

In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)

>> Program Id ? This program will be created in which server ( SAP 4.6 or SAP XI)?

You need to create program ID in ECC (remember it's case-sensitive) and the same program ID you need to pass in Sender RFC Comunication channel.

>> Application server ( Which server IP is required here ( SAP 4.6 or SAP XI)?

SAP 4.6

Note: As soon as you create Sender RFC communication channel, save and activate it. Immediately now create a RFC destination in R/3 System of type TCP/IP with server registered program in this communication channel against Program ID.

Remember first activate then create RFC destination in R/3 system.

Regards,

Abid

[Former Member]

Application server service (gateway) ?

where do i find the above service name in sap ecc or 4.6 system?

[Former Member]

Application server service (gateway) ?

where do i find the above service name in sap ecc or 4.6 system?

[Former Member]

Application server service (gateway) ?

where do i find the above service name in sap ecc or 4.6 system?

[Former Member]

Application server service (gateway) ?

where do i find the above service name in sap ecc or 4.6 system?

[former_member10771]

Hi,

You can use the gateway service which you have created in the RFC destination over there.

Thanks

Amit