XI3.0 Sender RFC Adapter fails

Hello,
I get the following error message with RFC Sender Adapter (R/3 4.6C to XI):
"lookup of binding via CPA-cache failed for AdapterType RFC, AdapterNS".
Has anybody seen this before ?
Regards,

I am running SP12 and was having this same issue. Here is the reply I received from SAP. It did fix my problem.
can you please try refreshing the cache, i.e.,
http://<host>:<J2EE-Port>/CPACache/refresh?mode=full
<host> is the Adapter Engine host
<J2EE-Port> is the HTTP port of the J2EE engine (The following naming
convention applies: 5<J2EE_instance_number>00. e.g. 50000, for example,
if your J2EE instance is 00
Log on with the XIDIRUSER user
If refreshing the cache does not resolve the issue then please check
the SAP Basis SWC in the Integration Repository for Adapter Metadata,
i.e.,
SAP BASIS
=> SAP BASIS 6.40
=> http://sap.com/xi/XI/System
=> Adapter Objects
=> Adapter Metadata

Similar Messages

Sender RFC Adapter-- XI-- File Receiver Adapter ?

Dear Expert,
we are on PI 7.0 & R/3 system 4.7E WAS < 6.20. We have a scenario where in there are some huge downloads are required from R/3 to FTP File Location. For such scenarios Normally Poxy is suggested but Due to WAs Version limitation we cannot use Proxy. The other alternative is to use SENDER RFc adapter using RFC destination with XI. we have configured the RFC destination it is working fine.
I am able to receive the message also in XI. But whenever i am running this RFC in R/3 it is giving me the shot dump as follows. :
call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:
The File is also getting written to the destination properly. But in XI also i get the following error.
 <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>http://Test/Zbilldwd ZBILLDWD_FILE_IM</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Interface mapping http://Test/Zbilldwd ZBILLDWD_FILE_IM does not exist in runtime cache</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
What could be the reason of this.? As well i am geting 3 error messages in XI.
I have defined this interface as Inbound / Async Message interface with input message as output file structure. ( Is this configuration is OKAY ?)
pl. help me to solve this error.
Regards,
Umesh

HI,
Check your configuration from the message it states that it can not find out the mapping program.
Check the configuration Receiver and interface determination whether you are using the same which is designed in repository.
Thanks and Regards,
Chirag Gohil

Sender RFC Adapter - Data to be sent from R/3

I am working on a scenario where I have to send data from an RFC-enabled function module from R/3 to a file server via XI. The entire scenario is asynchronous.
Sender: RFC Adapter
Receiver: File Adapter
I have done all design and the configuration. Both communication channels are working. I have the RFC destination also set up correctly in R/3.
However, when I run my ABAP program where the RFC-enabled function module is called, I get a shortdump with the message "senderAgreement not found: lookup of binding via CPA-cache failed for".
Plus: " The error occurred during an RFC call to another system."
Could someone kidly help?

Hi,
Follow these steps :
1. import the ECC_ Server into ID if not done
2. Refresh Cache : Tcode SXI_CACHE
3. Please check for Sender agreement config
4. Check out the parameters when R/3 calls back XI, it passes the SYS-ID and client number and checks the same in the Integration Configuration Under Business System Service-> Adapter Specific Identifiers. The R/3 System ID and the client Number
Also check out these blogs..
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
regards
Aashish Sinha
PS : Reward points if helpful

Sender RFC Adapter , Sender File Adapter - Payload Compression

Sender RFC Adapter or the Sender File Adapter compress the payload of any spaces in between the tags or remove any spaces at the start and end of the payload.
We need to pass the spaces as is in the message payload to the receiving system?
Is there a way to do it in PI 7.1.

Hi Vikrant,
Preserving white spaces while reading a file from FTP
NameA.fieldContentFormatting
- Enter trim to remove all the leading and subsequent blanks for a value found. This is the default.
- Specify nothing to ensure that the value remains unaltered.
For RFC you need to check your payload to see whether spaces are coming from R/3 itself or not.
Regards
joel

Problem in Sender RFC adapter

Hi all,
Our scenarion is like this
RFC -> XI -> File
When we are calling the RFC ( inside a program ) from the client we are getitng a shortdump with the error ...
'JCO.Server could not find server function 'STOCK_ENQUIRY_OUT'
any idea where is the exact problem '?
regards
Goutam

Have these basic checks;
1. Import the RFC and activate the same in XI.
2. Configuring of RFC adapter - /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
3. Troubleshooting - /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009

Sender RFC Adapter AND Rec. File Adapter

Hi
Workflow of my scenario is like this :
SAP R/3 ---> Sender RFC Adapter ---> XI Server -
> Rec. File Adapter -
> Legacy System
I am using Async Inbound interface for this as I dont need any response back & I just need to create file.
I am just picking some data from BAPI & creating a file on a folder in Legacy System.
Now during execution, file is getting created but I am getting dump on SAP R/3 and even when I am using Async communication, response is coming back from Legacy Business System ( service ) & giving an error " No Mapping Program Found " in sxmb_moni.
Kindly suggest how can I avoid getting response from Legacy System. Pls. take note again I am using Async Inbound Interface.
Regards
- Lalit -

Hi Lalit,
When your RFC is called from R/3 by default it would be in Sync mode. When this is in Sync mode it obviously will expect a response and where as in your scenario XI dose'nt give any response and there is no mapping for that and I think that is the reason you are getting that error.
So when your Sender RFC is triggered it will like this in ABAP
CALL Function "Function Name" <SM59 Destination>
and this is Sync call. To make it Async i should be
CALL Function "Function Name" IN BACKGROUND TASK <SM59 Destination>
Hoep this helps
Thanks,
Prakash

XI scenarios using Sender RFC Adapter

Hi Forum,
I am eager to know what kind of XI scenarios use sender RFC Adapter, can u give an example,
does this mean........executing a RFC in a R/3 system and the result of the execution goes to XI.....or,
does this means, like a sender JDBC Adpter, from XI, triggering execution of a RFC on a R/3, and getting back the result into XI............
can i have a step by step blog to create such a scenario....
thanks and regards

Hi Sudeep,
Sorry for late reply.
Yes the 2nd reply was for receiver RFC.
1. As i mentioned To configure Sender RFC you need TCP\IP connection. in that connection you will use the option registered server program and will mention a program ID there.
2. Sudeep just remember, please configure RFC sender on XI side first and give a Program ID there, gateway service, host and login of your R3 system. Program id can be any string your name also. and please dont forget to activate the channel before going to R3 side.
3. Then configure RFC in R3 side, and mention that same program id. mention your gateway host as R3 name or IP and you can get the gateway service from Tcode smgw. it must be something like smgw<xx>.
and for ur information the program id is nothing but an identity on which basis the R3 system will search that which server object is active using that program id.
4. when you will write a report to execute that RFC in background, use Commit work as last statement.
Please let me know if you want any further information.
Rewrds if found helpful,
Regrds,
Alok

Sender RFC adapter High volume messaging

Hi,
This question is related to this thread:RFC connection problem
ERP system is sending through 1 RFC dest. (program ID) 20 requests in a minute. And PI starts to hang. ERP is not able tp sent the messages and after a while the request sent from ERP starts to get cancelled. This is a synchonous scenario. How can I handle such a high volume through 1 sender RFC adapter?

Hello
You can monitor the load on RFC adapter queues/threadsin the RWB
-> Component Monitoring
-> Adatper Engine XIP
-> Engine Status
-> Additional Data
See note #791655 Documentation of the XI Messaging System Service Properties, for an explaination of the queues.
To increase the number of threads/queues, see the blog:
1) /people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
2) /people/kenny.scott/blog/2008/12/05/xipi-file-and-jdbc-receiver-adapter-performance-and-availability-improvements - this shows how to prevent a problem on one RFC channel blocking other RFC channels that you may be using.
Also, ensure note #937159 XI Adapter Engine is stuck, has been applied to help overall system performance.
Regards
Mark

Sender RFC Adapter only processes first message

Hi there,
we have a R/3 - XI - 3rd party scenario, where the R/3 - XI communication will be established through a RFC.
The RFC destination was properly configured in SM59 in R/3 and also was the XI's sender RFC adapter, with the same program ID.
We called the RFC in R/3 Abap code and the message succesfully arrived at XI (it could be found in SXMB_MONI). However, any other call from R/3 would not result in a message arriving at XI (no new entry in SXMB_MONI nor in Message Monitoring, at RWB). New messages only appear again if we set the status of the adapter to inactive and then active again. Then the message arrives, but again, only the first one.
Can anyone help with this?
Is there any misconfiguration in XI or RFC Destination?
Or is it the abap calling that should be processed in another way?
Thanks in advance,
Henrique.

Hi,
>>>Or is it the abap calling that should be processed in another way?
the important thing is the commit work
which must be done after call function
and you can only have one call function
before the commit work
do you see any other errors in SM58?
>>>Is there any misconfiguration in XI or RFC Destination?
Or is it the abap calling that should be processed in another way?
one or the other - no doubt about that
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Sender RFC adapter Error- request was null while trying to extract it.

Hi All,
I have a scenario running in Production(PI 7.0 system) where SAP ECC sends RFC request through sender RFC adapter. The scenario was working fine but now I am getting the below error in default trace and I couldn't see any error in communication channel monitoring.
java.lang.Exception: RfcServer[BAS_ECC_RFC_Snd]1[AFSenderD] request was <null> while trying to extract it.
I have gone through the below thread and performed a full cache refresh but it didn't help :
[NULL]
I have gone through SAP note:730870 and I couldn't get any help on this error. Can you please suggest your ideas to solve this issue.
Thanks & Regards,
Laawanya

Hi Lawanya,
Check you RFC and input data , whether the RFC call is able to get the data from ECC or not.
you can test the same RFC in ECC with input data and you can check whether the RFC in ECC is return the value or not.
I gues in your case the RFC in ECC is not return any data to PI.

Sender RFC adapter - Tight coupling to an SAP client

Hi ,
We are using a sender RFC adapter to receive a RFC request from SAP , process the request in XI and then send back a response to SAP.
Our requirement is that , this request may come from different SAP clients(client 100, 130 , 200 etc). Looks like RFC adapter configured under a Business System in XI cannot listen to calls from multiple clients and works for only one client. We get dumps in SAP when invoking this RFC from other clients.
Also i hear that the same program id cannot be used in two different RFC sender adapters, meaning i have to create a different RFC destination , create a different program id for each client in SAP.
Is there a way around for this issue ?
Thanks
Saravana

Hi Saravana,
you may try a little workaround:
configure your rfc adapter only with client 100
and try invoking RFC from clients: 130 , 200
on the client 100 first (with a dummy RFC on client 100)
and then from this dummy RFC on client 100 you can start your standard RFC with your rfc adapter
don't know any other way:)
Regards,
michal

Problem with sender RFC adapter

Hi All
I have created one RFC adapter for which i have created wrong business system and all then i have deleted that and i have created on more RFC adapter but when i am testing my scenario its taking the old one which i have deleted from the Integration directory. I have refreshed the cache using sxi_cache and also in RWB. But still i m getting the same error...
Could you please tell me how to resolve this error

Hi
Yes i have configured RFC as sender communication channel. I have deleted the old one including the business system. but still in adapter monitoring i m getting the error "com.sap.aii.af.rfc.afcommunication.RfcAFWException: alternativeServiceIdentifier: party/service from channel configuration are not equal to party/service from lookup of alternativeServiceIdentifier (CPA party/service/channel ''/'Whirlpool_BS1'/'RFC_Source_CC', lookup of alternativeServiceIdentifier for party '', schema 'TechnicalSystem' with 'QN9#800' returned party/service of ''/'QN9')"
but i have deleted the whirlpool_bs1 business system.
Why still i m getting this error.
Thanks & Regards
SUN

Calling RFC Adapter fails - convert error

Hi,
I have a problem with calling RFC Adapter. I'm using JDBC->XI->RFC scenario. JDBC does just "select 'W' from dual". In the destination SAP system RFC function is created for test purposes. This function has one parameter - string type. After calling it, it should write a sysdate into the SAP Z_ table. The XI should call the function with the 'W' parameter. But this fails. Everything is ok, but calling the RFC returns following error (copied from the Runtime Workbench -> Message Monitoring :
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$Exception: (130) JCO_ERROR_XML_PARSER: Expecting a tag to begin with '<' instead of 'W', in "u
(Yes, this is thw whole error message. I don't know what u should be...)
Did someone get this error?
Thanx 4 answers, Peter

Hello all,
Let me reopen the topic of my colleague. I'm facing the same error though with bit different symptoms. Here it is.
ERROR msg:
Exception caught by adapter framework: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: could not convert request from XML to RFC:com.sap.mw.jco.JCO$Exception: (130) JCO_ERROR_XML_PARSER: Expecting a tag to begin with '<' instead of 'Z', in "T
The XML message (MainDocument):
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Z_BAPI_ACCESSIBILITY_TEST_XI xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
<BAPI1008 />
<PARAM>Z_XID_500_ACC</PARAM>
<ZTTOTH_BAPI1008 />
- <ZTTOTH_STRUCT>
<PARAM1>Z_XID_500_ACC</PARAM1>
</ZTTOTH_STRUCT>
</ns0:Z_BAPI_ACCESSIBILITY_TEST_XI>
According to the error message the parser expects behind string ...<ZTTOTH_STRUCT><PARAM1> another tag, but the question is why.
To make all this more funny here I paste another XML message of BAPI calling which works fine (without the error described above):
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:Z_BAPI_PARAMETERS_TEST_XI xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
<PARAM>Z_XID_500</PARAM>
- <ZTTOTH_STRUCT>
<PARAM1>Z_XID_500</PARAM1>
</ZTTOTH_STRUCT>
</ns0:Z_BAPI_PARAMETERS_TEST_XI>
The BAPI functions are absolutely the same except those other two import-pramater structures (BAPI1008 and ZTTOTH_BAPI1008). I'm gonna to try to add those import-parameter structures into Z_BAPI_PARAMETERS_TEST_XI, but anyway - this is weird.
Does anybody have an idea, what should be wrong ?
Thx. Tom
Message was edited by: Tomas Toth

Sender RFC Adapter Issue

Hi ,
I am using the following scenarion (SAP ECC)Sender RFC>PI 7.1->Receiver JDBC(ThirdParty).
The issue is whenever the the ECC system is down and is up again , the RFC sender messages are getting struck in SM58(tRFC queue).What I manually do is , go the RFC Sender communication channel in PI and reactivate it again, by making a small change in the description of the communication channel.
So, my question is , whether there is a automatical ways to handel this issue.
Any other suggestions would be highly appreciated.
Thanks,
Venu

There is no standard way to perform this automatically. I think restart of ECC is not a frequent practice in any business, therefore ideally you should add this as one of the post processing procedures after ECC restart.
Technically, there is possibility of creating a scenario which can run through a job on ECC running once after each restart. This can call webservice in PI to fetch communication channel information and reactivate it. Not a solution I would recommend.
Regards,
Prateek

Doubt Regarding Sender Rfc adapter calls

Hi Experts,
When we call RFC in R3 system by giving destination as XI system,
1) where exaxtly RFC cal executes either in R3 or XI?
In case of sender RFC syncronouse call? where exaxtly RFC cal executes either in R3 or XI?
In case of sender RFC asyncronse call? where exaxtly RFC cal executes either in R3 or XI?
2) In case of Recever RFC syncronouse call, where exactly RFC call executes, is it in XI or R3 system?
Please help me out.
thanks
siva

1) where exaxtly RFC cal executes either in R3 or XI? 
It is at R3 for bothe sync and asyn sender scenario.
2) In case of Recever RFC syncronouse call, where exactly RFC call executes, is it in XI or R3 system?
RFC is called from XI. The call is actually executed at R3 receiver
Regards,
Prateek

XI3.0 Sender RFC Adapter fails

Similar Messages

Maybe you are looking for