Program Id in RFC sender channel

Hi Experts,
Can the same Program ID be used in 2 different RFC sender channels? I do not want to use the existing RFC sender channel. Please le me know.
Thanks
Suma

Hello.
I can't understand what are you trying to implement here, but here is the correct way to work with RFC CC
1. every sender CC should have the XI as the gateway server. the program ID is then registered on the xi server.
2. If you want to call the same interface from different ECC systems, you will create an RFC destination in each of them, containing the XI as the gateway and the same program ID. in that case you fill the RFC Metadata Repository Parameter with one of the ECC systems (as the RFC have the same metadata in both servers - it doesn't matter which one is written there) look here for more information: [Configuring the Sender RFC Adapter |http://help.sap.com/saphelp_dimp50/helpdata/EN/67/6d0540ba5ee569e10000000a155106/frameset.htm]" and focus on the sentence: "The RFC metadata repository parameters identify the SAP system containing the repository for the RFC metadata. This does not necessarily have to be the sender system" (:
3. If you want to use different interfaces - you will use 2 program IDs, 2 sender channels, 2 sender agreements.
hope it helps.

Similar Messages

Program id in RFC sender

Hi Experts,
Please confirm if the same program id can be used in different RFC sender channels?
Thanks and Regards
Suma

Suma S wrote:
Please let me know what is the impact or result if I use the same program id in 2 rfc sender channel for 2 different scenarios
>
> Thanks and Regards
> Suma
Program ID of the registered server program. The selected program ID must uniquely describe the RFC sender channel in the configured gateway (Application Server (Gateway) and Application Server Service (Gateway) parameters).
Quoting from sAP help docs
So, the impact of using the same program id wll lead to havoc
Regards
Krishna

RFC Sender Channel Issue : STFC_CONNECTION

Hi All,
There has been an issue with the RFC sender channels. When SAP triggers the data, we see an error in the RFC sender channel as below
Error in processing caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '', fromService '<ServiceName>', toParty '', toService '', interface 'STFC_CONNECTION', NS 'urn:sap-com:document:sap:rfc:functions' for channel '<ChannelName>' (channelId 7f84f67e7efe39949dc12a2f569236fb)
But the data gets processed at the very next moment.
Program ID used in the channel is same as the ID registered in SAP. Is there some configuration missing either at SAP PI or SAP R/3 system?
Regards,
Prajeet

Hi Prajeet,
please refer this wiki [link |https://wiki.sdn.sap.com/wiki/display/XI/RFC+Faqs?showChildren=false]Q19,hope this helps.
Check if you are using the same program ID in multiple scenarios. May be if you keep different the program ID names in different RFC adapters, it should resolve the error.
also check here :/people/danny.deroovere/blog/2008/02/26/change-client-in-scenarios-with-sap-business-system
Regards,
Srinivas

How many RFC Destinations / RFC Sender Channels

Hello everybody!
I have several RFC --> XI --> JDBC/FILE/SOAP integration scenarios. For each scenario I have one RFC Destination created (pointing to XI) in SM59 in R/3. For each RFC Destination I have created one RFC Sender Channel in XI.
But this doesn't make sense, don't you agree? I should have only one RFC Destination in R/3 to XI, right?
If that is the case:
1) Should I also have only on RFC Sender Channel in XI?
2) What about load balance? What about concurrence? With only one RFC Sender Channel I have to set "Initial Connection" propertie to a big value to be able to handle several RFC calls (to different RFC Functions) in parallel. Is there a limit (a maximum value) I can use in "Initial Connection" propertie?
Thanks
Julio

hi julio,
Yes. We can have only one RFC to point to Same XI System and in the XI, we need only one RFC Sender too.
For LoadBalancing and concurrence, refer the links:
1) https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/c3d9d710-0d01-0010-7486-9a51ab92b927
Limitations regarding RFC Sender
http://help.sap.com/saphelp_nw04/helpdata/en/58/11e6418b7eca17e10000000a155106/content.htm
Bonus Link: 
Re: RFC Adapter as Sender
regards,
nikhilbos

SOAP ACTION IN SOAP ADAPTER and PROGRAM IF IN RFC COMMUNICATION CHANNEL

Hi Gurus,
Please Explain me what is SOAP action in soap adapter what is the use of it.
What is the Program ID in the RFC communication channel and what is the use of it.
Please tell me in Detail.
Thanks and Regards,
RAM.

Hi,
Please Explain me what is SOAP action in soap adapter what is the use of it.
As of W3C definition:
The SOAPAction HTTP request header field can be used to indicate the intent of the SOAP HTTP request. The value is a URI identifying the intent. SOAP places no restrictions on the format or specificity of the URI or that it is resolvable. An HTTP client MUST use this header field when issuing a SOAP HTTP Request.
The presence and content of the SOAPAction header field can be used by servers such as firewalls to appropriately filter SOAP request messages in HTTP. The header field value of empty string ("") means that the intent of the SOAP message is provided by the HTTP Request-URI. No value means that there is no indication of the intent of the message.
Putting things simple, this is an identifier of an operation that you want to execute in the web service (as one web service can offer multiple actions).
What is the Program ID in the RFC communication channel and what is the use of it.
Again, this is an identifier for both: RFC sender and receiver systems. It tells the receiver where to listen for connections, and the sender - where to send the data. It works a little bit like a port number in HTTP communication, but with less restrictions.
Hope this helps,
Greg

RFC Sender Channel

Hi Experts,
I am dealing with RFC channel(sender). How can we incorporate Qos in RFC??
It's taking BE by default. But how to make it EO and EOIO?
Please suggest
T& R
Sushama

For EO, see this
/people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
EOIO is not supported for standard RFC sender. An adapter module may help. It would be better to achieve EOIO behavior using ABAP Proxy.
Regards,
Prateek

Random error IN RFC sender channel

Hi all,
Please note that in two different scenarios Same busness system is used but different Sender RFC channels and different Functional modules. In spite of this a random error is occuring. At times scenario works fine and some times it gives error.
"Wrong Sender Agreement:The Sender agreement doe
ot have channel Func_sender_cc"
No error report in SXMP_MONI.
Any clue please.
Regards
venkat

Hi,
Now it is clear very much there is no need of registaring programID specifically any where. Any programID first mentioned in Comunication channel and actived and then defined rfc destination using SM59 with same programID gives successfull test result.
Also for different RFC senders Different ProgramID shall be used to avoid the type errors faced by me.
Hope this helps all
cheers
Venkat

Regarding RFC Sender Communication Channel

Hi All,
I am working on RFC sender channel, need some important information.
1). Can i use single RFC Sender Channel in Multiple Sender Agreements.
2). Can i use Program ID in Multiple Sender RFC Channels. I am having one RFC to File interface and another RFC to JDBC interface.
Do i need to create 2 sender channels and 2 RFC destinations with 2 Program Ids????.
Please give me clarifications.
Regards,
Balu

If i will use single sender RFC channel and Single Program ID for my all sender agreements, how that Single RFC channel
will identify the information like
In our sender agreement we configure not only the channel but also the Sender Interface (in your case RFC)......this is the factor which defines what to accept......in broader term we use the same concept of channel re-use in other cases also and the same work fine because of this Sender Interface.
I found Q28 interesting: https://service.sap.com/sap/support/notes/730870
In first read it may sound confusing...but after some more rreads you will know what the answer means in the SAP note.
Regards,
Abhishek.

Rfc sender problem(sap r/3 -se37) 'alternativeServiceIdentifier: party/serv

Rfc sender problem: While executing the rfc in sap r/3 system
It is showing abap run time errors are
'alternativeServiceIdentifier: party/service from channel
configuration are not
(i have taken hint from this weblog /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step)
These are the configuration at sap xi and sap r/3 system
1) SAP XI (ID)
I have created rfc sender commuication channel in I.D.
 Rfc server Parameters->
 A.S.(Gateway)-> server {sap r/3 server name}
 A.S.S.(Gateway) -> sapgw00
 program id -> PDPT
 AND RFC Metadata repository parameter
2)SAP R/3 (SM59)
 Rfc destination -> PPPP
 Connection type -> T
 Technical Settings->
 (*) Registered Server Program
 Program ID -> PDPT
Gate way options
 Gateway host -> server
 gateway service -> sapgw00
Testconnection-> connected
3) testing rfc at sap r/3(se37)
But when i am executing a rfc in sap system
Rfc target system -> PPPP
and some import parameters
and it is showing the error message as
'alternativeServiceIdentifier: party/service from channel
configuration are not '
4)SAP R/3( SMGW)
CONNECTION TO CLIENT FOR PDPT(TP NAME) REGISTER STATUS IS WAITING
Please help me how to solve this problem

Hi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek

RFC Sender problem between 46D and RFC adapter

Hi,
I have this simple integration scenario where I want to send data to a archiving system;
SAP -> (tRFC) -> XI -> (MQ) -> BizTalk -> (MQ) Arch.syst.
SAP side ***
A Z-program using a Z func. like;
 CALL FUNCTION 'ZSD_DCF_SEND_TAG'
 IN BACKGROUND TASK
 DESTINATION 'XISYSTEM_TRFC_DCF'
 EXPORTING
 pt_filing_info = gt_filing.
 COMMIT WORK AND WAIT.
XI side ***
Both IR and ID is configured correctly, in the development environment everything works just great. I have created a test program where I can define how many calls I will do, looping over the func. call with a commit inside the loop - 500 or more msgs are ok.
The integration scenario is transported to quality enviroment using CMS, and the RFC sender comm.ch. is configured accordingly.
The problem in quality ***
When sending just 1 msg, everything is just fine, message received and delivered to MQ.
When sending >= 2 msgs, the 1 msg is always ok, BUT all others fails due to the following from Adapter monitor;
RFC_HISTORY
- Error: 2006-01-19 10:55:18 CET: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'RFCSender_XI0002' (02d4d30de3593874942ed0659add0827, party '', schema 'TechnicalSystem', identifier 'Q93#120')
- OK: 2006-01-19 10:55:17 CET: Message processed for interface ZSD_DCF_SEND_TAG
My sending system is Q93 CLI 505 so I can understand the error, BUT I cannot understand why the RFC adapter is saying the TechnicalSystem is Q93#120 - it should be Q93#505. My Q XI has client 120...
It seems to me that the RFC adapter is kind of confused about the sender..
I have created a OSS message and SAP has looged on and looked into it with both a XI expert and RFC expert without being able to answer - all is configured correctly.
- The SLD config. for bus.system Q93 is ok -
- The bus.system in ID is showing correct vaues for
Adapter Specific Identifiers (SID Q93, client 505)
- Both Dev. and Qual. environment are running on XI 3.0 SP 14 latest patch, RFC component version on the SAP side is identical between dev. and qual. SAP systems
- It doesn't matter which gw I use (Q93 gw or XI gw), the error is persistent
- It doesn't matter if I increase initial conn, max conn.
I have also tried to use qRFC instead, but with the same result.
Anyone using tRFC for asynch. communication from SAP to XI seeing something similar?
Meanwhile, I will do RFC trace on GW and RFC Adapter on AE....
Please, do not say SP15, oss msg for FAQ RFC adapter or links to RFCAdapter config....
best regards
Torstein

Hi,
SAP Note 730870 FAQ: XI 3.0 RfcAdapter Q.no 15
Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".
- Give correct appserver and gateway service details in XI.
- Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek

Error in RFC Sender Adapter

Hello Experts,
Right now i m working on the scenario SRM -> XI -> 3rd party system.
Here i want to send data from SRM to XI, and for that i m using Sender RFC Adapter.
I have configured RFC Sender channel in XI and created RFC Destination into the SRM system, and when i m trying to test the RFC Destination at that time it is giving me error saying that "program POACK_GEE not registered".
Can anyone help me out in this issue... its very urgent...
so waiting for your replies...
Thank you very much,
hetal

Hi Michal,
I already had a look into that... but i didnt find the solution
The error coming is like this....
ERROR program POACK_GEE not registered
LOCATION SAP-Gateway on host <host name> / <service name>
DETAIL TP POACK_GEE not registered
COMPONENT SAP-Gateway
COUNTER 1270
MODULE gwr3cpic.c
LINE 1609
RETURN CODE 679
SUBRC 0
RELEASE 640
TIME Mon May 7 16:45:48 2007
VERSION 2
I have followed all the steps then also i dont know y it is not working...

Program ID in RFC destination-XI

Hi
can any one tell me
for RFC sender channel purpose i'm creating RFC destination in SM59. through sap help and some other weblogs i'm trying create Program iD,but i'm getting some doubts on this:
1. How do i know corrosponding programID for this register server program?
2.How do i know sender system is Unicode system is or not?
Auctully my scenrio is RC--->JDBC, thats the reason i'm trying to create RFC destination in r/3 side..
regards
rambarki

Hi Rambarki,
Is your scenario sysnchronous or asynchronous ?
if your scenario is asynchronous then from ABAP program you can call your RFC using the following syntax...
CALL FUNCTION 'RFCNAME'
DESTINATION 'RFCDESTNAME'
EXPORTING ...
IN BACKGROUND TASK .
for synchronous scenarios use this
CALL FUNCTION 'RFCNAME'
DESTINATION 'RFCDESTNAME'
EXPORTING ...
IMPORTING ...
You also try using SE37..
In SE37 enter name of your RFC and press on execute..
then enter your RFC destination name , input parameters..and execute.
Is test connection working fine in SM59 ?
Take look at this thread aswell
Re: How to test the RFC to Flat File scenario
Regards
Anand

Doubts in RFC sender Adapter

Hi XI Gurus,
Can any body plz explain me about the parameters used in RFC Sender Adapter (like RFC Server Parameters: Program ID, Gateway, etc..)
Thanks in advance.

Hi,
Refer this link there they have given everything clearly
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/frameset.htm
Application Server (Gateway) : host name of the sender system.
Application Server Service (Gateway): Gateway service of the sender system. This can be the numeric description of the service port in the sender system or the alphanumeric equivalent (for example, sapgwXX, where XX is the system number of the sender system).
Program ID: Program ID of the registered server program. The selected program ID must uniquely describe the RFC sender channel in the configured gateway (Application Server (Gateway) and Application Server Service (Gateway) parameters).
For Program id: In sender R/3 system Tcode SM59
1.Create RFC Destination with connection type: T
2.Choose Registered server program
3.Give program id(you can give any name here, the program id you give in sender RFC adapter and here should be same )
4. Give Gateway host and Gateway value.
You can also check this blog
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
Regards,
Sakthi

RFC Sender adapter error

Hi Folks,
Am trying an RFC to SOAP sync interface.
Hav configured the Adapter, registered the program at PI, created RFC using registered server program.
When I trigger the FM as Call Function '..' DESTINATION <rfc dest> i get a system failure.
IN RWB Channel monitoring I see the error as "Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS http://sap.com/xi/XI/System, direction INBOUND, fromParty '*', fromService 'SAPECC_SHD', toParty '', toService '', interface 'ZBAPI_WEBSERVICE1', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_SAP_ZUMMATION_RFC_S' (channelId af2f451f1b473ac28063768416ba8a72)"
Have checked for errors such as * in sender agreement, header data in Receiver agreement note 730870..
Kindly guide if there is anything to be checked.

Hi,
Clear the cache (SXI_CACHE) and stop and restart the RFC sender channel in RWB.
Cheers,
André
Edited by: André Schillack on Mar 30, 2010 5:09 PM

Problem RFC sender

Hello,
I have a new Problem about a sending RFC in XI.
Once I send a test-RFC from R/3 se37 it reaches the rfc sender channel but there I get an error in cc-monitoring(the same is displayed in R/3 then as well).
The error says:
Processing error caused by: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'CC_RFC_sender_RFC2JDBC' (104238c5fe4c345e8e85752a84330c5c, party '', schema 'TechnicalSystem', identifier 'E10#400')
Can you help me?
I don't understand the error.
CPA-Cache Refreshs do not work.

Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?
A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".
* Give correct appserver and gateway service details in XI.
* Open the service holding the RFC adapter you are trying to use. On the top menu, goto Service -> Adapter Specific Identifiers..
Regards,
Prateek

Program Id in RFC sender channel

Similar Messages

Maybe you are looking for