RFC Sender error - lookup of alternativeServiceIdentifier

Hi,
I am trying to configure an R/3-XI-Java proxy scenario using the RFC adapter as sender. When I execute the RFC on the R/3 system using the RFC destination, I get the exception SYSTEM_FAILURE. In the RFC adapter monitor, the error message is "com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel". I have verified the settings mentioned in SAP note 730870 (Q. 15), but am still getting the same error. Please let me know how to resolve this error.
Thanks,
Sumanth.

Hi Sumanth,
Check the Adapter Specific Identifiers in the Business sytem which contians RFC adapter.
Make sure that R/3 System ID is equal to the one specified in the SLD.
You can also "compare" the same with that in the SLD.
You should concider clearing the SLD data cache before comparison
Cheers,
Rashmi

Similar Messages

RFC sender error

Hi,
I created RFC at SAP . RFC Sender.
SM59 registered progam ID
i am suing same program id and gateway server, host in XI
when i execute the FM from se37 using the RFC DEST it is showing the error
"JCO.Server could not find server function 'Z_BANK_RECONCILIATION'"
same program id has been defined in Visual admin JCO Serivce.
Could u locate where is the errore
jeff

hi Jeff,
>>>>Same program id i registered in JCORFC server in Visual admin.
what for ??
why didn't you follow my blog that I gave you in
which I show RFC configuration ? I don't mention anything
about Visual admin in it...
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

RFC Sender error could not create function template for...

Hi,
I am trying to send an async RFC to XI. Since I use IN BACKGROUND TASK and COMMIT WORK I got following error in the SM58 of the back end system
Server repository could not create function
template for 'XYZ'
In the XI, I see nothing (no message, no error)
How can I fix this problem?
Thanks
Thomas

Hi Thomas,
You may need to have logical destinatio types for sender RFC. (and in the refernce entry you need to provide the actual destination)
may be some other errors also, Check this link and see if you have followed all the steps.
http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/frameset.htm
Hope this fixes your issue.
Regards
Vishnu

RFC Sender Error - R/3 4.6C

Hi,
I try to do a RFC -> XI -> JDBC. When I execute the FM in my R/3 4.6C the following error show up:
"connection to partner broken" / "CPI-C error
CM_PRODUCT_SPECIFIC_ERROR".
An error occurred when executing a Remote Function Call.
"CPI-C error CM_PRODUCT_SPECIFIC_ERROR"
Status of connection.... "CODE=CM_PRODUCT_SPECIFIC_ERROR CM_NO_STATUS_RECEIVED
CM_NO_DATA_RECEIVED SAPCODE=223 CONV=66899296"
Internal error code.... "RFC_IO5"
There is an error in the communication system. To clarify
and resolve the error, contact your system administrator.
Last error logged in SAP kernel
Component............ "NI (network interface)"
Place................ "SAP-Gateway on host zulia / sapgw00"
Version.............. 34
Error code........... "-6"
Error text........... "connection to partner broken"
Description.......... "NiPRead"
System call.......... "recv"
Module............... "ninti.c"
Line................. 1130
Regards,
Luis Diego

Hi Luis,
There is a SAP note on this.. Please check note 634362.
Hope this solves ur problem..
cheers
Prashanth
P.S Please mark helpful answers

RFC Sender - lookup of alternativeServiceIdentifier via CPA-cache failed

Hello,
I am using RFC Sender for a scenario and while sending message I got following error. I found this error while monitoring communication channel. I looked at several posting on this issue and tried with both checking and not checking check box of advanced mode (RFC sender communication channel configuration). I am getting the same "lookup of alternativeServiceIdentifier via CPA-cache failed" error. How did you resolved?, please let meknow.
Did any one come across error
Server 0 0_50478 Sender channel 'CC_GET_CUSTOMER_RFC_SENDER' for party '', service 'SAP_DFR' (internal name 'RfcServer[CC_GET_CUSTOMER_RFC_SENDER]')
Server data: {jco.server.gwhost=XXXXXXXXXX, jco.server.progid=DFX_XI_00, jco.server.gwserv=sapgw00, XI_RFC_USER=*****, jco.server.unicode=0}
Repository data: {jco.client.lang=EN, jco.client.snc_mode=0, jco.client.client=120, jco.client.passwd=******, jco.webas.ignore_jdsr_error=1, jco.client.user=XI_RFC_USER, jco.client.sysnr=00, jco.client.ashost=XXXXXXXXXX}
Current pool size: 1, maximum pool size : 1
Channel History
- Error: 2007-09-20 10:32:14 CDT: com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'CC_GET_CUSTOMER_RFC_SENDER' (bee9e190f51f3687b1072bf3f5446a70, party '', schema 'TechnicalSystem', identifier 'DFR#120')
Thank you,
Balaji

run tc SXI_cache on the XI
on that screen press Shift+f6, it will start the refresh....and also do the CPAcahe manually trough the link
http://itmisapxi:50000/CPACache/refresh?mode=full
with PIRDIRUSER and then check the interfce....

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

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

Lookup of alternativeServiceIdentifier via CPA-cache failed for channel

Hi,
In RFC(ECC) to File(PI) scenaio i am facing the following error in sender CC:
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel SND_RFC
-CC' (f455868123qq3bba4c3dc3dbf93ed1b, party '', schema 'TechnicalSystem', identifier 'ECC#110')
I have done the following for RFC to File scenario:
ECC side:
1. Created a RFC and tagged it to BAPI
2. In the ABAP program, i am calling the RFC like below:
CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
EXPORTING
INTERFACE =
IMPORTING
FILENAME = FILENAME
RETURN = RETURN
TABLES
ITAB10 = ITAB10
P_STATUS = P_STATUS
COMMIT WORK.
3. Created a RFC destination using SM59
RFC detination : Z_HR_OUTBOUND_DATA2
Connection type : TCP/IP
Enabled Registered Server Program
Program ID : ECCTOPI_OUTBOUND
Gateway host : ECC's host number
Gateway service : ECC's service number.
In PI side:
I have created :
1 DT for File Rcvr
1 MT for File Rcvr
1 SI for File Rcvr (async)
1 MM (sender RFC and receiver File)
1 OM
1 CC with RFc as sender with the following parameters:
Communication component : ECC's component
application server (gateway) : ecc's gateway
application server service(Gateway) : ecc's service number
Program id : ECCTOPI_OUTBOUND
inital connections 1
max. connections 1
And also gave ecc's details in application server , s/y number, auth. mode, logon user ,
pwd, ecc's client number
1 CC with File adapter and file content conversion
1 receiver determination
1 interface determination
1 sender agreement
1 receiver agreement
When i am executing the ABAP program in R/3 I am getting the following error:
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: lookup of alternativeServiceIdentifier via CPA-cache failed for channel SND_RFC
-CC' (f455868123qq3bba4c3dc3dbf93ed1b, party '', schema 'TechnicalSystem', identifier 'ECC#110')
Please let me know if any of my steps are wrong and how to rectify this error and make
the scenario working.
Thanks for your help.

I have mentioned the Adapter specific parameters properly.
It contains :
For ECC s/y(i.e for RFC)
   Logical system : DECCLNT120
   R/3 system ID : DEC
   Client 120
For PI (i.e for File)
   Logical system : DPICLNT100
   R/3 system ID : DPI
   Client 100
Since i am sending the Response of the RFc to the file, i have used a Service interface where i am passing the RFC.Response as Request.
if i am passing the RFC directly as i/p in Source operation of Operation mapping then it doesn't pick up the response in the souce message of the mapping program present in Operation mapping.
So i am passing the same SI_Sender_RFC in the Sender Agreement and it gives the error:
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 'DEC_RFC', toParty '', toService '', interface 'Z_HR_OUTBOUND_DATA2', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_LOTUSNOTES_OUTBOUND_SND_RFC' (channelId c78f5a88787131a09384c07c2db0e93b)
why is it so?

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

Errors in RFC sender Adapter

Hi Guys,
I am configuring a RFC sender Adapter in a newly installed system.
I configured the adapter as per the parematers given in SAP help in the exact way and started getting the error
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 'RD1CLNT020', toParty '', toService '', interface 'Z_TEST', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'RD1CLNT020_IN' (channelId 897afca12ee93b86a5bfcd738c037099)
If I go into SXI_CACHE of the PI system I can see the entry.
My gut feeling is that the adapter is not fetching the metadata properely.
Because I switched the metadata loging from the ECC system to PI system and I got the error
JCO.Server could not find server function 'Z_TEST'
I think in the basis setup we have missed something The version on which we are working is the Latest PI 7.1
If somebody has a document at the the config for JCO or a solution for this problem will be much appreciated.
Thanks & Regards
Gagan Kasana

Hi,
there is no magic with this error - it's a common one
1. my blog - RFC sedenr adapter config -
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
then is still does not work:
2.check out OSS note 730870 - FAQ RFC Adapter
"Question 19:
While sending a RFC call to the RFC Adapter I get a error message like "com.sap.aii.af.rfc.afcommunication.RfcAFWException: lookup of binding via CPA-cache failed..." or "com.sap.aii.af.rfc.afcommunication.RfcAFWException: senderAgreement not found: lookup of binding via CPA-cache failed...". What is missing?"
and you have it working
please let me know if this helped
Regards,
Michal Krawczyk

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

RFC 2 File Error in RFC sender: java.lang.ArrayIndexOutOfBoundsException

Hello,
I'm sending data asynchronously from R3 to a file through XI, I've got the RFC destination (in R3) and sender RFC channel (in XI) configured and tested. Working fine.
Then in my report I've got the following code that sends 1 string and 4 internal tables 2 to XI:
CALL FUNCTION 'Z_RFC_ENVIAR_DATOS_PSP'
    IN BACKGROUND TASK DESTINATION 'SAP_2_XI'
    EXPORTING
      RUTA                       = p_ruta
    TABLES
      IT_DEMANDA           = p_gt_demanda
      IT_STOCKS              = lt_stocks
      IT_CUARENTENAS   = lt_cuarent
      IT_COMPRAS           = lt_repartos.
COMMIT WORK.
I've done that king of connection several times and allways worked but now I've got that error in the communication channel monitoring at RWB:
Error in processing caused by: java.lang.ArrayIndexOutOfBoundsException
And no message is created in XI. What can it be?
Thanks for your help

Hi Chen Lin,
The problem is with the adapter but no message is generated yet in XI, so I don't have XML yet.
The RFC sends the data to XI through the RFC destination and at this point something is wrong because that error is produced. The error is visible in both sides, In transaction SM58 at R3 I can see the error that tRFC hasn't been precessed because the ArrayIndexOutOfBoundsException.
But if I go to communication channel monitoring I can see the same error too, so that confirms that the communication between R3 and XI works fine but something is wrong and the error don't give me more details

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...

Communication Channel RFC Sender getting error suddenly

Hello gurus,
I'd like to ask you about a problem, we have many interfaces from RFC to SOAP synchronous, the CC RFC sender, in an average of once per day, gets into red colour with this error:
Sender channel 'CC_RFC_SENDER_L0_MAESTROS' for party '', service 'BS_LD0_100'
Error can not instantiate RfcPool caused by:
com.sap.aii.adapter.rfc.RfcAdapterException: error
initializing RfcServerPool:com.sap.aii.adapter.rfc.core.repository.RfcRepositoryException:
can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION:
Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=10.1.4.191 SYSNR=00 GWHOST=10.1.4.191 GWSERV=sapgw00 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner 'XX.X.X.XXX:sapgw00' not reached
TIME Thu May 27 03:56:04 201
RELEASE 711
COMPONENT NI (network interface)
VERSION 39
RC -10
MODULE nixxi.cpp
LINE 3151
DETAIL NiPConnect2: 10.1.4.191:3300
SYSTEM CALL connect
ERRNO 111
ERRNO TEXT Connection refused
COUNTER 5
I don't know the reason of this.. but simply just stopping and starting the CC it gets into green colour again..
Does anyone know how to solve this?
Regards,
Juan.

Hi,
This happens if the RFC connection pool is not instantiated or may be cache failed to auto-refresh....And manual restart of RFC channel resolves it.
Refer page 8 in the RFC troubleshooting guide.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f3f93ee7-0c01-0010-2593-d7c28b5377c2?quicklink=index&overridelayout=true
Thanks
Swarup

Error in RFC Sender

Hi,
We are implementing a BAPI to send data to PI. We have created the following
IN R\3
In SM59 create a new RFC connection type T (TCP/IP).
Technical settings:
Activation type: registered server program
PROGRAM_ID: test_program_id
Gateway options:
GAteway host: Host of your R\3 system
Gateway service: Gateway of your R\3 system
In XI
In your RFC Sender Communication Channel:
RFC Server Parameter:
Application Server: Host of your R\3 system
Application Server Service: Gateway of your R\3 system
PROGRAM ID: test_program_id
RFC Metadata Repository parameter
Message Serer: Your R/3 host.
Message Server Service...
SystemmID...
Use a user with authorization to do RFC calls.
Client...
Language...
After we finish setting up your CC, save and Activate.
Now check the RFC in R/3
When we run the program in SAP( which contains the BAPI ) for the first time, it runs & send the data but for next run it gives error in SAP side(SM58) : Commit fault: com.sap.aii.adapter.rfc.afcommunicat ion.RfcChannelMismatchE
Message no. SR053
Can any one help us to solve the RFC connection issue
Thanks

make sure your program id is unique.try changing it.
Ref:
RFC adapter - /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
trouble shooting rfc/soap -
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

RFC Sender error - lookup of alternativeServiceIdentifier

Similar Messages

Maybe you are looking for