RFC sender connect to PI results in ST22 error - CALL_FUNCTION_NOT_FOUND

Hello,
we are doing an RFC connect with a self defined RFC (simply a trigger, a report that calls a FM with a single value) to
PI.
The connectivity is working, sender channel in comm.channel monitoring is in green.
The function module is imported to PI and implemented in the related scenario.
But when we try to start the call to PI this will simply result in an ST22 error on PI with the message
CALL_FUNCTION_NOT_FOUND.
Does anybody here have an idea about that issue?
We are on SAP PI 7.0 SP 15.
Regards
Dirk

> Out implementation:
> We have a TCP IP connection in SM59 of the R/3 with host and service entries for the R/3 system and the registered server prg. name that is the same as in the comm.channel (know about case sensivity).
> The prog. is registered in SMGW on the R/3 now.
This looks perfect!
> In the report where we are calling the function module the destination is the PI connection added as a ABAP Type 3 connection in SM59 of the R/3 system.
Suppose you created TCP IP connection with a name R3_TO_XI, then in the report you have to code it as shown below.
CALL FUNCTION 'your RFC FM name here'
IN BACKGROUND TASK
DESTINATION 'R3_TO_XI'
TABLES
COMMIT WORK.
Update:-
You can also refer this wiki..
https://wiki.sdn.sap.com/wiki/display/XI/RFCtoFILE
Regards,
Sarvesh
Edited by: Sarvesh Singh on Mar 11, 2010 5:04 PM

Similar Messages

RFC Sender: Connection refused

Hi experts,
We are running a scenario with a RFC Sender communication channel.
When the RFC is executed this error occurs in the Runtime Workbench:
Transmitting the message using connection HOSTNAME failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: java.net.ConnectException: Connection refused: connect
Our basis reported that the HOSTNAME value is incorrect, but could not tell where this information is configurated.
Can anybody tell where is this hostname configurated?
Is there any transaction to check the error?
Thanks anyway.

David,
http://SERVER:8002/sap/xi/engine?type=entry is your integration pipeline URL which belongs to your XI box.
In trasaction SXMB_ADM there are two ways through which you can enter the pipeline URL for the corresponding IE of XI system.
1) By creating and RFC destination and referring that in field "Corresponding Integ. Server" and
2) By directlyspecifying the pipeline URL in above mentioned field
in your case the URL is entered using 2nd option that can be edited by an option Edit-> Change Global parameters.
it will allow you to change the server name.
Thanks,
Sunil Singh

Pls send me Real time SM21 and ST22 errors.at least 4

Hi,
       I am new guy in Basis .Pls send me SM21 and ST22 real time errors.I will give more reward points.
regards,
Jana

Hi janardan
Here I am sending the lists of some real time errors that i have encountered during my monitoring work:-
SM21
1) 06:14:20 DIA 001 010 ALEREMOTE         AB0 Run-time error "CALL_FUNCTION_SEND_ERROR"       occurred
2) 08:09:13 DIA 002 010 ASCHELVI     SA38 AB0 Run-time error "TIME_OUT" occurred
3) 05:45:03 BTC 003 000 SAPSYS            D01 Transaction Canceled BT 510 ( )
4) 10:32:55 DIA 003 010 WORKFLOW          H01 Enqueue of work item 000023517979 deleted by called   application.
ST22
1) 10.04.2008 11:34:17 sapbebr104 FFERNAND 010 C RAISE_EXCEPTION    1
2) 10.04.2008 12:47:23 sapbebr102 JIGOMEZ 010 C SYSTEM_CANCELED    4
3) 09.04.2008 12:48:13 sapbebr104 MLOLMEDO 010 C TIME_OUT    1
4) 01.04.2008 07:46:11 sapbebr042 BMARIQUE 010 C LOAD_PROGRAM_LOST    3
In SM21 u can look for messages like :
>Printer problems
>Signal 11
>Short dumps
>Time-outs
>Matchcode problems
>Aborted postings
>Runtime error analysis
ST22 is used for some abap dump analysis
Award points if found helpful.
Regards,
Abinash

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

Unable to create RFC iviews - connection test of the system failed

hello,
I always try to configure my system to run an RFC iView...
The connection of myt system is failed for 1 of the 4 tests.
i don't know why.
I have filled this fields :
- application host
- ITS host name
- ITS path
- ITS protocol
- Logical system name (not sure it's correct)
- Sap client
- Sap system ID
- SAP system number
- Server port (not sure it's correct)
- System type
- Web as host name
- Web as path
- Web as protocol
and i have this error :
SAP Web AS Connection
Test Details:
The test consists of the following steps:
1. Check the validity of the system ID in the system object
2. Check if the system can be retrieved
3. Check if a SAP system is defined in the system object
4. Validate the following parameters: WAS protocol; WAS host name
5. Check HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. Retrieval of the system was successful
3. The system object represents an SAP system
4. The following parameters are valid: Web AS Protocol (http) Web AS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)
5. HTTP/S connection successful
ITS Connection
Test Details:
The test consists of the following steps:
1. Check the validity of the system ID in the system object
2. Check if the system can be retrieved
3. Check if the system object has a valid system alias
4. Check if a SAP system is defined in the system object
5. Validate the following parameters: ITS protocol; ITS host name
6. Check the validity of any user mapping in the system object
7. Check HTTP/S connectivity to the defined back-end application
Results
1. The system ID is valid
2. Retrieval of the system was successful
3. Retrieval of the default alias was successful
4. The system object represents an SAP system
5. The following parameters are valid: ITS Protocol (http) ITS Host Name (wsapv49.dhcp.xxx.xx.xxxx:8045)
6. HTTP/S connection successful
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure user mapping is set correctly and all connection properties are correct.
Test Connection through the DQE
Test Details:
The test consists of the following steps:
1. Checks the existence of a backend admin user ID/password in the system properties.
2. Checks the existence of a default alias for the system.
3. Checks the DQE connection.
Results
1. DQE admin user ID or password is missing in the system properties. Make sure those properties exist for this system object.
2. Default alias of the system exists.
3. DQE connection successful. If you continue to experience problems, verify the DQE admin user ID and password properties for this system object.
can you help me to end this configuration?
thanks a lot.
(reward points for helful answers...)
Adrien

doesn't work, doesn't work... :o(
I found this in "analysis" -> "Debug"
error 3 mai 2007 16:49:32:168 Failed to get connection for system final
/System/Server com.sap.portal.ivs.connectorService sap.com/irj admin ITEM-31892 Server 0 0_33638
error 3 mai 2007 16:49:32:168 (R3/BW) Failed to get connection. Please contact your admin.
/System/Server com.sap.portal.connectors.R3 sap.com/irj admin ITEM-31892 Server 0 0_33638
i found too a -BIG- file in the directories, "last block" of the file
#1.5#000D56D8CEA2005D0000001500000FC400042F9201A5E5D2#1178204046283#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.
Exception id: [000D56D8CEA2005D0000001300000FC400042F9201A5E071]#
#1.5#000D56D8CEA2005D0000001600000FC400042F9201A76132#1178204046383#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.client.RequestInfoServer#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error##Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.)]. The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
 at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:209)
 at com.sap.engine.services.servlets_jsp.server.runtime.client.GzipResponseStream.write(GzipResponseStream.java:193)
 at com.sap.engine.services.servlets_jsp.server.runtime.client.HttpServletResponseFacade.writeError(HttpServletResponseFacade.java:952)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.sendError(HttpHandlerImpl.java:955)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleGeneralException(HttpHandlerImpl.java:860)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.processError(HttpHandlerImpl.java:851)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
#1.5#000D56D8CEA2005D0000001800000FC400042F9201A765B7#1178204046383#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#admin#1a943a10f98511dbc5d6000d56d8cea2#SAPEngine_Application_Thread[impl:3]_3##0#0#Error#1#/System/Server/WebRequests#Plain###Cannot send an HTTP error response [500 Application error occurred during request processing. (details: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.)].
The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.
Exception id: [000D56D8CEA2005D0000001600000FC400042F9201A76132]#
and with another test connector
#1.5#000D56D8CEA200600000001800000FC400042F921D02D625#1178204505301#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/tcwddispwda#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#SAPEngine_Application_Thread[impl:3]_14##0#0#Error#1#/System/Server/WebRequests#Plain###Processing HTTP request to servlet [dispatcher] finished with error.
The error is: com.sap.tc.webdynpro.clientserver.session.CloseResponseException: The connection is closed.
Exception id: [000D56D8CEA200600000001600000FC400042F921D02D1AE]#
#1.5#000D56D8CEA200560000001600000FC400042F921D39B77B#1178204508896#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoInit()-> enter#
#1.5#000D56D8CEA200560000001700000FC400042F921D3AE547#1178204508977#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###connectToSystem()->Selected Systemnull#
#1.5#000D56D8CEA200560000001800000FC400042F921D3BE964#1178204509037#com.sap.tc.lm.ctc.provider.configurationmanager.ConfigManagerReader#sap.com/tcwddispwda#com.sap.tc.lm.ctc.provider.configurationmanager.ConfigManagerReader#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###getElement(String, Filter, int):NamedLocatedElement!ConfigManagerReader.SEARCH_FOR!CTC#
#1.5#000D56D8CEA200560000001900000FC400042F921D414CF2#1178204509397#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoInit()-> leave success#
#1.5#000D56D8CEA200560000001A00000FC400042F921E69A639#1178204528816#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoModifyView()-> enter#
#1.5#000D56D8CEA200560000001B00000FC400042F921E69A953#1178204528816#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#sap.com/tcwddispwda#com.sap.tc.lm.ctc.ccl.templateinstaller.TemplateInstallerCompView#Administrator#49##ITEM4531892.dhcp_J2E_3363850#Administrator#fd2a66f0f98611dbcb21000d56d8cea2#ID\#(J2EE3363800)ID0180043050DB10318128463979236974End.32388e30f98711dba6e6000d56d8cea2##0#0#Info##Plain###wdDoModifyView()-> success#
#1.5#000D56D8CEA2006E0000010500000FC400042F9231C81C6F#1178204853786#com.sap.portal.connectors.R3#sap.com/irj#com.sap.portal.connectors.R3#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_9##0#0#Error#1#/System/Server#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
#1.5#000D56D8CEA204E70000000100000FC400042F9231C90EA8#1178204853846#com.sap.engine.services.dqe#sap.com/irj#com.sap.engine.services.dqe#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#Thread[Log_Worker_6,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error#1#/System/Server/DQE#Plain###mai 03, 2007 17:07:33.786 [SAP_HOST|4039|SAPEngine_Application_Thread[impl:3]_9] <CONNECTOR.ERROR> Error trying to establish connection to the EIS : final Connection Failed: Nested Exception. Failed to get connection. Please contact your admin. #
#1.5#000D56D8CEA200690000001E00000FC400042F92335B4C9E#1178204880215#com.sap.portal.connectors.R3#sap.com/irj#com.sap.portal.connectors.R3#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server#Plain###(R3/BW) Failed to get connection. Please contact your admin. #
#1.5#000D56D8CEA200690000002000000FC400042F92335B4FE3#1178204880215#com.sap.portal.ivs.connectorService#sap.com/irj#com.sap.portal.ivs.connectorService#admin#47##ITEM4531892.dhcp_J2E_3363850#admin#e91a07a0f98711db85f4000d56d8cea2#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Server#Java###Failed to get connection for system #1#final#
i happy to carry my life's number one goal with another guy
(thanks, again and again)
Adrien
Message was edited by:
 Adrien Loire

Problem in receiving messages via RFC Sender Adapter

Hi,
I have problems in receiving messages from SAP backens systems. Sometimes we are getting all messages sometimes not. Strange.
We are transfering report-results via asynchronous RFC calls. To avoid big message sizes we split them up in max. 1000 rows blocks.
Each RFC call on backend side is completed with COMMIT WORK!
We increased the number of connections in the RFC sender adapter. Then it was better, but the problem still exists! Not so often, but sometimes !?!?!
I hope everybody can help me. Thanks a lot!
best regards,
Hannes

hi,
when you don't receive messages what do you see in SM58
on the r3?
any errors over there?
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 Short dump

Hi,
I am carrying on a RFC(sender) to multi-file scenario. I have created RFC destination in SM59(in R/3) using a Registered ProgramID.
But while executing the corresponding program for sending the data, R/3 shows a short dump error. Some of the errors getting displayed in st22 are:
-> In the source code you have the termination line at line 174.
-> Internal notes
The termination was triggered in in function 'RfcExtendReceive' of the SAP Kernel...
The scenario configuration on XI part are perfectly fine, since i have tested it with a File Sender. The thing is even after displaying an exception in st22, the data reaches XI as shown by sxmb_moni. But the scenario doesnt work.
Regards
Arpil

Hi,
you need a wrapper RFC to do achive result.
Go tru the thread below you problem should be resolved,
RFC to FILE
You need to map the multi structured file to new RFC structure.
Hope this helps.
Prasad Babu.
Message was edited by:
PrasadBabu Koribilli

R/3 to PI using RFC Sender Adaptor as Asynchronous scenario

Hello Folks,
RFC Adp. SOAP Adp.
ECC-->XI--
>ARIBA
I am new to PI and doing a scenario mention above. we are using RFC sender adaptor to send the data to XI in asynchronous process.
I have config the Sender comm. channel as below.
Appl. Server(Gateway): My Ecc Server host name
Appl. Server Service (Gateway) : My Ecc server
Program Id : XYZ.
Note : while creating the the Service interface and Message mapping and Operation mapping I am using the RFCname.respone message type is that ok in asynchronous process?
And then I went to ECC in Tcode SM59 and created a RFC destination of type TCP/IP
and put the same information as given above and test the connection which is working fine.
I have created a FM at ECC end make it remote enabled. and calling the FM in back ground task using destination in a Work flow code.
When I run the Work flow code It ran successfully but i went to XI side there is no msg in the SXMB_MONI.
Then i went to the component monitoring->Adatptor engine>Comm. channnel Monitoring and found that under my RFC sender comm. channel there is an error msg saying
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 'BS_ECC', toParty '', toService '', interface 'YFPS_MM_I_0242_PO_APPROVAL_OUT', NS 'urn:sap-com:document:sap:rfc:functions' for channel 'CC_0242_PO_Approval_RFC_Sender' (channelId 19585252a58335ee871e4c3a771b027f)
Where as i have checked that in the sxi_cache t-code there is a sender agreement for my scenario under the sender agreement tab.
Please Help me in this to resolve the above error. I am totally stuck at this point.I would really appreciate a quick answer.

Appl. Server Service (Gateway) : My Ecc server
Confused with this statement.....
it should have the format sapgwXX ....
XX is the system number which comes from the j2ee port mentioned in the XI homepage URL
http://<hostName>:5XX00:rep/start/index.jsp
How to configure sender RFC adapter...check this blog:
https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/1438
Error in processing caused by: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException:
senderAgreement not found:
Sender Agreement is Expected in this communication which does not seem to be present in ID....create sender agreement using the RFC communication channel....
Regards,
Abhishek.
Edited by: abhishek salvi on May 2, 2009 1:24 AM

RFC Send could not be resolved against SAP system because its metadata could not be obtained...EXCEPTION FU_NOT_FOUND RAISED

Hello,
I am getting the following error in sending IDOC to SAP via WCF-SAP adapter in BizTalk Server 2009. I have the SOAP header in the adapter mentioned below. Also, wondering what is the convension for Action URL? Is it always "http://Microsoft.LobServices.Sap/2007/03/Rfc/"
+ Operation name mentioned in the Orchestration? I would appreciate if anyone could help me resolve this error.
The adapter failed to transmit message going to send port "SendReceive_PO_IDOC_TO_SAP" with URL "sap://CLIENT=111;LANG=EN;@a/123.456.789.101/00?GWHOST=123.456.789.101&GWSERV=sapgw00&ListenerProgramId=ABCDEF111&RfcSdkTrace=False&AbapDebug=False".
It will be retransmitted after the retry interval specified for this Send Port. Details:"Microsoft.ServiceModel.Channels.Common.MetadataException: RFC Send could not be resolved against SAP system because its metadata could not be obtained. ---> Microsoft.Adapters.SAP.RFCException:
Details: ErrorCode=RFC_EXCEPTION. ErrorGroup=RFC_ERROR_APPLICATION_EXCEPTION. SapErrorMessage=EXCEPTION FU_NOT_FOUND RAISED. AdapterErrorMessage=An error occurred while determining the function interface of the RFC Send.
at Microsoft.Adapters.SAP.RFCException.HelperThrow(Int32 retCode, String additionalErrorMessage)
at Microsoft.Adapters.SAP.RfcClientConnection.GetRfcFunctionInterface(String rfcName)
at Microsoft.Adapters.SAP.InternalRfcMetadata..ctor(String originalRfcName, SAPConnection sapConnection)
at Microsoft.Adapters.SAP.SAPMetadataContract.ResolveOperationMetadata(String operationId, TimeSpan timeout, TypeMetadataCollection& extraTypeMetadataResolved)
at Microsoft.ServiceModel.Channels.Common.Design.MetadataCache.GetOperationMetadata(String uniqueId, Guid clientId, TimeSpan timeout)
at Microsoft.ServiceModel.Channels.Common.MetadataLookup.GetOperationDefinition(String operationId, TimeSpan timeout)
at Microsoft.Adapters.SAP.SapFunctionMetadata.ResolveOperationMetadataUsingSdk(String absoluteName, String displayName, String funcName, String operationNamespace, SAPConnection sapConnection, Boolean isTrfc, MetadataLookup metadataLookup, TimeoutHelper
timeoutHelper)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
SOAP Header:
<BtsActionMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Operation Name="Send" Action="http://Microsoft.LobServices.Sap/2007/03/Rfc/Send" />
</BtsActionMapping>
Thanks,
Tarun

Hello Morten,
The Send is actually just the name of the operation in Orchestration and it does not exist in SAP. Hence, do I really need to have the SOAP header in WCF-SAP adapter or can I send the IDOC without any SOAP header info? When I try to send without
SOAP header I get the following error. Can you help me resolve this?
The adapter failed to transmit message going to send port "SendReceive_PO_IDOC_TO_SAP" with URL "sap://CLIENT=111;LANG=EN;@a/123.456.789.101/00?GWHOST=123.456.789.101&GWSERV=sapgw00&ListenerProgramId=ABCDEF111&RfcSdkTrace=False&AbapDebug=False". It
will be retransmitted after the retry interval specified for this Send Port. Details:"System.ArgumentNullException: Value cannot be null.
Parameter name: key
at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.CreateChannelFactory[TChannel](IBaseMessage bizTalkMessage)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.InitializeValues(IBaseMessage message)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2..ctor(IBaseMessage message, WcfTransmitter`2 transmitter)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfTransmitter`2.GetClientFromCache(String spid, IBaseMessage message)
at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfAsyncBatch`2.BatchWorker(List`1 messages)".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Thanks,
Tarun

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

Help with RFC sender, Program And RFC Destination

Hi!!
my scenary is asynchronous
 RFC Sender -> SAP-XI -> Oracle reciever
I have a problem with abap, especially rfc, program and rfc destination. The connection with SAP-XI exist and SAP-XI receive the message but the message is empty.
1. In my program on the line
 CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
 catch an error system_failure = 2 and it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC
2. I rewrite my program, that line to
 CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' STARTING NEW TASK 'NEW' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
 catch an error communication_failure = 1 but the rfc ZBAPI_SD_PED_ORD_SERVIC is executed but no send to SAP-XI
3. I rewrite my program, that line to
 CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' IN BACKGROUND TASK DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
 No error but it dont execute the rfc ZBAPI_SD_PED_ORD_SERVIC and the message in SAP-XI is empty, display the tables but not the row. i check the table PED_ORDEN and RETURN but the controls fields dont are afected.
What is my Error?
Where am i making a mistake?
RFC
FUNCTION zbapi_sd_ped_ord_servic.
*"Interfase local
*" TABLES
*" PED_ORDEN STRUCTURE ZSD_RFC_T04
*" RETURN STRUCTURE ZSD_RFC_R06
TABLES: zsd_ped_orden, zsd_rfc_r01.
DATA: tb_ped_orden LIKE zsd_ped_orden OCCURS 0 WITH HEADER LINE,
 tb_rfc_orden_error LIKE zsd_rfc_r01 OCCURS 0 WITH HEADER LINE.
*Get Pedido by Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_ped_orden
 FROM zsd_ped_orden
 WHERE estatus EQ space.
LOOP AT tb_ped_orden.
 MOVE-CORRESPONDING tb_ped_orden TO ped_orden.
 APPEND ped_orden.
 tb_ped_orden-estatus = 'X'.
 tb_ped_orden-fecha_actualiz = sy-datum.
 tb_ped_orden-hora_actualiz = sy-uzeit.
 MODIFY tb_ped_orden.
ENDLOOP.
MODIFY zsd_ped_orden FROM TABLE tb_ped_orden.
COMMIT WORK.
*Errors in Ordenes
SELECT * INTO CORRESPONDING FIELDS OF TABLE tb_rfc_orden_error
 FROM zsd_rfc_r01
 WHERE estatus EQ space.
LOOP AT tb_rfc_orden_error.
 MOVE-CORRESPONDING tb_rfc_orden_error TO return.
 APPEND return.
 tb_rfc_orden_error-estatus = 'X'.
 tb_rfc_orden_error-fecha_actualiz = sy-datum.
 tb_rfc_orden_error-hora_actualiz = sy-uzeit.
 MODIFY tb_rfc_orden_error.
ENDLOOP.
MODIFY zsd_rfc_r01 FROM TABLE tb_rfc_orden_error.
COMMIT WORK.
ENDFUNCTION.
PROGRAM
REPORT ZBAPI_SD_PED_ORD_SERVIC.
DATA: ped_orden LIKE ZSD_RFC_T04 OCCURS 0 WITH HEADER LINE,
 return LIKE ZSD_RFC_R06 OCCURS 0 WITH HEADER LINE.
CALL FUNCTION 'ZBAPI_SD_PED_ORD_SERVIC' DESTINATION 'ZXI_ENVIAR_PED_ORD_SERVIC'
 TABLES
 ped_orden = ped_orden
 return = return
EXCEPTIONS
 communication_failure = 1
 system_failure = 2
 OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE 'error' type 'I'.
ENDIF.
COMMIT WORK.
RFC DESTINATION
RFC Destination: ZXI_ENVIAR_PED_ORD_SERVIC
Connection TYpe: TCP/IP Connection
Register Server Program: ZBAPI_SD_PED_ORD_SERVIC
Gateway host: host00
Gateway service: sapgw00

hi
For rfc sender adapter we hv to do some settings .Please chk whether this settings are well configured or not.
a) RFC destination
b) RFC channel in the XI directory
This weblog is a response to a few question about the basic configuration of the RFC sender adapter
that were posted on the XI forum (and also on my e-mail)
So here we go, basically we have to configure 2 things:
a) RFC destination
b) RFC channel in the XI directory
RFC destination:
1. To create the RFC go to TCODE: SM59
2. Create new destination of type T (TCP/IP)
3. Make sure you select Registered Server Program option before writing your program ID
4. Write you program ID (remember it's case-sensitive)
5. In the gateway host and gateway service write the values of your "Application system" - business system (not the XI server)
7. No configuration in the J2EE administrator nessecary
Now we can proceed to RFC channel configuration:
1. Enter your Application Server
2. Your Application Server Service
3. Enter your Program ID from the RFC destination
And we're done:)
Now you can test the RFC destination in SM59 to see if it works.
Please chk this following link.
1. RFC Processing with the RFC Adapter
http://help.sap.com/saphelp_nw04/helpdata/en/25/76cd3bae738826e10000000a11402f/content.htm
2. Configuring the Sender RFC Adapter -
http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/content.htm
3. /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
regards
Manas

RFC Sender Adapter - MP: exception caught

Hi Friends,
We have one RFC to SOAP scenario in our PRD system.
When we execute an RFC in the R/3 side, the sender RFC CC receives the message. (The message id is generated). But, the message is not entered into SXMB_MONI.
When we checked the audit log. The error is as below:
RfcAdapter received sRFC for Z_RFC_SUPER_ACK from P88/300. Trying to send message synchronously.
MP: entering1
MP: processing local module localejbs/RfcAFBean
MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: Connection RFC_http://sap.com/xi/XI/System is currently not started.
We have checked Program ID, RFC Connections in R/3 system. It is correct. The standard module " localejbs/RfcAFBean - Local Enterprise Bean " is used in the sender CC, only this module.
We have few RFC receiver communication channels, all are working fine.
Only this Sender RFC CC, we are facing this problem.
We found the similar thread "RFC-Connection not started ?". The same problem we are facing. They suggested to bounce the system and restart.
Since it is PRD system, it is not able to do that immediately. Since all RFC receivers are working fine, we feel that it is not required to bounce.
Can you kindly help me friends, how to solve this problem.
Thanking you,
Kind regards,
Jegathees P.

Hi Sabarish
The RFC sender cc is active in ID and started.
The status of the channel in CC monitoring is red. (due to this error).

RFC Sender (XI 3.0, SP14) Load Balancing doesn't work

Hi all,
We're "desperately" trying to use the Load Balancing option of RFC Sender Adapter (XI 3.0, SP14). It doesn't work.
The Adapter can not register to the sender SAP server. But when we do not use the "Load Balancing" option, everything works well.
We did follow the XI guidelines step-by-step. All necessary configurations in XI and in SAP sender system (TA: SM59) are "properly" done and reviewed by different experts several times.
Do you have, by chance any running scenario using "Load Balancing" within a RFC Adapter? If yes, I would appreciate if you can share it with me.
Thanks a lot!
Regards,
Khaled

Hello Khaled,
the RFC sender adapter registers a program at the SAP Gateway. Load Balancing for the Sender Adapter means, that you have at least two J2EE server nodes within your XI installation. On all these server nodes the same RFC sender adapter is started and register the same program at the same gateway. The load balancing is then handled by the gateway. That means, that for the sender adapter the settings are the same, even if you use load balancing or not.
The settings are, e.g.
- SID=ABC
- hostname=abchost (central instance, message server)
- hostname=xyzhost (additional dialog instance of ABC)
- instance nr=00
application server (gateway): xi1host
application server service (gw-service): sapgw00
programm id: could be freely choosen
The Metadata Repository could be connected using load balancing. Here a user need to log on to the system.
The settings here must be:
Message-Server: abchost
Message-Server-Service: sapmsABC
System-ID: ABC
Logon-Group: e.g. PUBLIC; this logon group need to be created in system ABC using transaction SMLG
For the RFC-Receiver Adapter the same settings as for the Metadata could be used.
Keep in mind, that for the RFC Sender Adapter a RFC connection of type T must be created in transaction SM59 in system ABC.
Rgds.,
Andreas

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

Rfc Destination problem in RFC Sender Adapter

Hi experts
I created a Rfc destination type TCP/IP for Rfc Sender adapter.
while creating i passed following parameter:
1) I selected Activation Type option-> Registered Server
2)Given a Program id , same as i given in Rfc sender Adapter config.
3)Gateway option:
   i) Gateway Host:Server IP address where i created Rfc.
ii) Gateway Service:sapgw00
After making these entry, i m unable to receive message at XI end (I am executing Rfc at R/3 site due to Rfc sender)

Hi
please check for the following things.
1. check the RFC destination using the connection test tab in the R/3 system.
2. check whether the program id that u have given is registered or not.
to check the program id go to the transaction SMGW, in the menu select Goto-->LoggedonClients
check for ur program id name in the table.
3. when you configure the RFC sender adapter in XI then you have to give the same program id name that you will give while creating the RFC destination in the R/3 system.
if u still face the problem please reply me back.
Thanks
Rinku

RFC sender connect to PI results in ST22 error - CALL_FUNCTION_NOT_FOUND

Similar Messages

Maybe you are looking for