Receiver RFC Adapter

Hi All,
I am getting this error in communication channel monitoring for receiver RFC Adapter.
Delivering the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.aii.adapter.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.adapter.rfc.core.client.RfcClientException: JCO.Exception while calling Z_CRM_LEAD_CREATEMULTI in remote system (RfcClient[S10440_RFC_CallOutComes_Out]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Illegal move of the field symbol of a LOOP ... ASSIGNING.
Have gone through lots of links on SDN but not able to solve it out.
Any inputs will be greatly appreciated.
Thanks,
Venkat

Hi,
this one seems pretty simple
>>illegal move of the field symbol of a LOOP ... ASSIGNING.
this suggests that your error is inside FM Z_CRM_LEAD_CREATEMULTI
so correct the code (probably the table you try to loop is empty)
and try once more
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

Similar Messages

How to enable viewing of payload for receiver RFC adapter in RWB

HI All,
We can see the payload of all adapters in RWB by clicking on the message link under component >> adapter monitoirng. However when i click on message link for receiver RFC adapter, it does not show any payload. How can I enable this payload?
Regards

Hey
Sync messages are Cached rather than persisted in RWB to save memory.
You need to change the following parameter in Visual admin to see sync messages in RWB
Service SAP XI AF Messaging:
messaging.syncMessageRemover.removeBody = false
its set to True by default hence it does not stores the messages.
You may have to restart the Java stack after the changes (but first try without restarting the Java stack).
Thanks
Aamir
Pl:You will see the sync messages in Message Monitoring in RWB (not sure if it will show up in Communication channel monitoring as well)

Configuring receiver RFC adapter to use RFC destination

Hello,
   I have been doing some digging, but I can't find a solid answer on how to configuring a receiver RFC adapter to use an existing RFC destination to call a 4/6C R/3 backend system... Our scenario is to WS --> SOAP --> RFC which is up and running in production just fine on NW 7.0, SP12.
   I ask this question because we, as a company, do not like to maintain passwords in multiple systems. That is necessary when we use the receiver RFC adapter now since SNC is a distant pipe dream for us and we would like to use an existing RFC destination that is set up to call the backend system using a logon ticket.
   I checked the relevant links I could find below, but I can not resolve the answer from them. Has anyone set this up successfully? This link (RFC Destination type RFC Receiver Adapter?) mentions it briefly, but it does not go into any length on how to set it up.
Thanks!
John
http://help.sap.com/saphelp_srm40/helpdata/fr/33/c6e63b60c25767e10000000a11402f/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
Re: Asynchronous RFC call

Hi John !!
I suggest you to create a new user, without dialog access in your ECC system to be used exclusively by the XI system to access ECC. And then, always use this user in all RFC receiver adapter communication channels.
Regards,
Matias.

Receiver RFC Adapter -Advance Mode option

Hi Experts
I want Execute the commite transaction after Trigeering the Standred BAPI through XI.
We haveAdvance Mode option in Reciver RFC Adapter . Any one explain me how to implment this.
Regards
Upendra.V
Edited by: upendra v on Jan 26, 2009 1:47 PM

Hmmmm.. I guess you are just practising & exploring all the featers of RFC.. isn't it?
Anyway upto what I know is here..
>If you want to use this communication channel to call BAPIs as remote-enabled function modules that change data in the database, set the indicator.
First of all you need to write an ABAP program in R3, there you will call your RFC/BAPI to update the database entries.
In XI, under your receiver RFC adapter check the box "Commit Handiling for Single BAPI Calls". Once you click you will get another check box called "BAPI Advanced Mode".
>If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK.
Once you send the data from XI to R3, then in R3 function module BAPI_TRANSACTION_COMMIT will be called explicitly (you need to define/call this BAPI after the ABAP code for database update). This will commit the work and return the result success or failur in a parameter called RETURN.
And after this BAPI you should call BAPI_TRANSACTION_ROLLBACK, so that in case of errors the transaction will be rolled back.
>The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values u201Cu201D, u201CSu201D, u201CIu201D, and u201CWu201D are displayed. All other values are regarded as errors.
As described above.
>To change this setting, set the indicator BAPI Advanced Mode.
In the Successful RETURN-TYPE Values table, enter the values that should lead to a successful execution.
Once you check the box "BAPI Advanced Mode" a table will appear, there you can write your own values e.g.u201Cu201D, u201CSu201D, u201CIu201D, and u201CWu201D.
I can not provide a better solution then this... you have to do a work around, but above are the basic steps which can be considered before implementing the solution.
Regards,
Sarvesh

Receiver RFC adapter issue! Please help!

Hi Experts,
I have 4 XI interfaces. All of these are Webservice to RFC scenarios. Moreover all of them are synchronous.
Request message: Webservice (SOAP Adapter) ---> XI -
> RFc Adapter ---> ECC Function modules
Response message: Webservice (SOAP Adapter) <- XI < RFc Adapter <- ECC Function modules
As you can see above, external system calls XI web service via SOAP Adapter. The input data is then sent from SOAP Adapter to RFC adapter to call RFC function module in the receiving side. The receiving system is SAP ECC system.
The receiver ECC system has two instances. For example SP0 ad SP1.
In the receiver determination step we have maintained a rule such that if the Plant value in the input message is XYZ then send data to SP0. But if the plant value in ABC then send data to SP1.
This Conditional rule is working fine.
However we are getting couple of issues with only one instance of ECC (SP0).
1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-001cc495e48a(INBOUND) expired
2. NO_MAPPINGPROGRAM_FOUND. Mapping program is not available in runtime cache: Object ID C2B41FFDFD4635BAB1E41AE53C0D10CE Software Component 5394F420463611DAC1CFFBBC0A01BC16
3. com.sap.engine.interfaces.messaging.api.exception.MessagingException: No response available
The above listed errors are generated occasionally. Sometimes no errors are generated even when the same input data is sent again and message is successfully processed.
I have verified the input data and everything is OK with that.
Mapping object is available in XI and cache was also refreshed. I additionally reactivated the objects in XI as well.
So what could be the real root cause of this? Please help!
Thanks
Gopal

1. com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message badfa070-b163-11de-a4c1-
001cc495e48a(INBOUND) expired
Check the Timeout parameter of your adapter.....for requests which expire with this error confirm from the SAP end that the message processing is done well within the Timeout period of the adapter.
Refer this note for more info on the above occuring error and the possible way to avoid it: https://service.sap.com/sap/support/notes/791379
Update:
Even problem 3 seems to be occuring due to insufficient Timeout specified for the adapter.....if possible try increasing the Timeout in VA
Regards,
Abhishek.
Edited by: abhishek salvi on Oct 6, 2009 1:42 PM

Receiver RFC Adapter Error

Hi All,
I have a file to RFC scenario. I keep getting the below error: Any Ideas?
Danny,
Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: failed to parse BAPI response due to: com.sap.aii.af.rfc.util.bapi.BapiException: Parameter with name RETURN not found..

is this BAPI an SYNC one
check this link
RFC adapter Call BAPI error
Re: Invoice Not getting posted

Dynamic User for Receiver RFC adapter

Hi,
I have a soap to rfc scenario. Any solution to use PI login user as RFC user to connect SAP backend?
Thanks

YOu might want to know about the concept of principal propagation.
http://help.sap.com/saphelp_nw04/helpdata/en/45/0f16bef65c7249e10000000a155369/frameset.htm
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/808d3048-638c-2a10-35a6-faa48e50ad59
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1a65a5a7-0d01-0010-1b9d-df02d5666791
Regards,
Ravi

Error in RFC adapter

Hello All,
I am working on File to RFC Asynchronous Scenario. I am getting Error in M receiver RFC adapter. It is displaying in Adapter Monitoring as
<b>- Error: 2007-10-03 05:28:38 EDT: Message processed for interface BAPI_CUSTOMER_CREATEFROMDATA1: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: functiontemplate from repository was</b>
Can any help how to resolve this.
Regards

Hi,
The RfcAdapter trys to find a Sender Agreement for this RFC call but the lookup failes. The values used for this lookup are:
     Sender Party/Sender Service: The values from Party and Service belonging to the sender channel.
     Sender Interface: The name of the RFC function module.
     Sender Namespace: The fix RFC namespace urn:sap-com:document:sap:rfc:functions
     Receiver Party/Receiver Service: These fields are empty. This will match the wildcard '*'.
Chilla

How does RFC adapter with EO/EOIO work? Kindly help!

Hi Experts,
How does a sender or receiver RFC adapter works when QOS is EO or EOIO (Async)? In other words, for EOIO, are the messages are queued? How does this queueing work? Does it use FIFO logic? where do we specify the max limit of messages that can be queued?
Also what is the significance of 'Initial connection' and 'maximum connections' in communication channel? I have given the default value 1 for both. What should be the ideal value and why?
In my Async RFC - XI scenario sometimes XI is able to receive the messages but sometimes it doesnot even though the sender system is UP and running.
I cannot see any messages in SXMB_MONI even though the sender has sent the messade.
Why RFC adapter is behaving like this? What could be the issue?
Kindly help!

EOIO: How does this queueing work? Does it use FIFO logic?
>> yes it uses FIFO logic in EOIO.
Also what is the significance of 'Initial connection' and 'maximum connections' in communication channel? I have given the default value 1 for both. What should be the ideal value and why?
>>>noof rfc connections we are using for connecting to XI to RFC minmum is 1 maximum is 50 bydefault. you increase this value by changing the default setting.
How does RFC adapter with EO/EOIO work? Kindly help!
Posted: Mar 21, 2007 4:15 AM
Hi Experts,
How does a sender or receiver RFC adapter works when QOS is EO or EOIO (Async)? In other words, for EOIO, are the messages are queued? How does this queueing work? Does it use FIFO logic? where do we specify the max limit of messages that can be queued?
Also what is the significance of 'Initial connection' and 'maximum connections' in communication channel? I have given the default value 1 for both. What should be the ideal value and why?
Why RFC adapter is behaving like this? What could be the issue?
>>check ur sender RFC adapter. chekc whether data is sent from RFC . see logs in R/3.

Schedule Receiver RFC communication channel to call R3 RFC-FM.

Hi,
I have requirement that I need to schedule/trigger from PI to RFC call R3 function module. Wonder if anyone here has done similar thing before? I tried to use ATP (Availability time planning) in RWB. But this seem does not success for me as there is no response and error message for this.
Below is my configuration detail:
Configured:
1. Receiver communication channel - RFC
2. Receiver agreement with the RFC message type assigned.
3. Scheduled receiver RFC communication channel via ATP daily
*(It is possible to make scheduling job in R/3 but we are not considering this way)
Please let me know if anyone has done this before or any other suggestion to do the scheduling from PI.
Thanks!
Regards,
SP

Hi SP,
As you mentioned, ATP would allow adapter to be open and in start state. Adapter's RFC, SOAP, JMS would need some other application to trigger the message processing because these are not like pooling adapter's File, JDBC and Mail. RFC adapter channel always listening to the RFC port and FM execution. Once FM from R/3 executed then the RFC adapter would trigger it's message processing.
For Sender RFC channel: In order to trigger the RFC adapter execution at particular time then you should write a simple ABAP code which would act a batch application and which does the triggering the FM and Sender RFC channel.
For Receiver Channel: For Receiver RFC channel it's bit trichy because here you have force Receiver RFC adapter to connect backend the execute or initialize the variables without having any XI message triggered from Sender PI channel.
I have 2 ideas:
1. A little difficult approach, similar to the ABAPbatch code, you need to write a java adapter module which can trigger RFC receiver channel to connect and do an initialisation at FM at regular interval.
2. Simple approch configure a File-> 2-> RFC receiver scenario, configure File sender adapter to pick a dummy file at regular interval and RFC receiver channel does the rest.
Please let me know still you have any doubts,
Thanks,
RK

Jco error RFC adapter field PT F not defined

Hi Experts,
I am in a strange situation as I have become clue less on this issue
It is a file to XI to RFC scenario.. runs fine in dev environment
When I change the parameters in teh rfc communication channel to point to QAS it throws
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling Z_TRAX_PO_CHG_IV in remote system (RfcClient[CC_QAS]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Field selection PT F not defined:
There is no such field as PT F and besides the version of the bapi in QAS is in sync with the dev..
pls help me ou ton this
Edited by: Ravindra Teja on Feb 27, 2011 8:45 AM

Hi,
First of all, can you please elaborate what you want?
secondly, why don't you transport your developments to QAS?
Third, what is the reason behind changing the receiver RFC adapter parameter to QAS?
4th, do you want to post data to QAS, if yes, did you transported the RFC to QAS ? Please re import the rfc to your swcv from QAS system.
Please check communication channel if you getting any error?
Regards
Aashish Sinha

Difference In RFC Adapter and XI proxy

I am using RFC adapter for master data and XI proxy for transaction data , can anyone tell me what is major difference and what is negative point in using RFC adapter
Thanking you
sridhar

Hi,
Adapters enable the Integration Engine and the Partner Connectivity Kit (PCK) to communicate with different applications.Adapters connect the Integration Engine to SAP legacy systems, as well as to external systems.
In this way, adapters integrate existing SAP components with SAP Exchange Infrastructure, for example. In the process, XML and HTTP-based documents are converted to IDocs (IDoc adapter) and RFCs (RFC adapter) and the other way around. This enables you to integrate your existing SAP infrastructure with the new SAP infrastructure, which is based on system integration and the exchange of XML messages.
The plain HTTP adapter gives application systems the option of communicating with the Integration Engine and exchanging business data in a simple format, using an HTTP connection.
RFC Adapter :
The RFC adapter enables you to use the functions of the Integration Engine or the PCK in existing SAP landscapes. It is used by SAP systems to connect to the Integration Engine or the PCK by using the RFC interface. It supports SAP systems as of version 3.1x.
For FAQs about the RFC adapter, see SAP Note 730870
The RFC adapter is provided by the Adapter Engine and the PCK. It essentially comprises two parts, namely a sender adapter at the Integration Engine inbound channel, and a receiver adapter at the Integration Engine outbound channel.
The adapters are configured in the configuration part of the Integration Builder, or in the configuration part of the PCK. You use the SAP Java Connector (JCo), which enables you to manage metadata. This in turn enables you to map RFC data generically to RFC XML and the other way around.
The receiver RFC adapter can be used for mapping lookups.A communication channel with a receiver RFC adapter can be created automatically for business systems that are defined in the System Landscape Directory.
The RFC adapter maps the following RFC calls to XML messages and the other way around:
Synchronous RFC calls (sRFCs) in messages with quality of service Best Effort (BE)
●     Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
●     The receiver RFC adapter can also process messages with quality of service Exactly Once In Order (EOIO). They are mapped to transactional RFC calls (tRFC).
You require the sender adapter if you want to use the Integration Engine or the PCK to process RFCs. The RFC adapter converts the incoming RFC data to XML message format (RFC XML) so that it can be processed by the Integration Engine or the PCK.
You require the receiver adapter if the determined receiver system expects the data from the Integration Engine or the PCK to arrive in RFC format. In this case, the Integration Engine or the PCK must transfer the received XML message (RFC XML) to the RFC adapter. The RFC adapter converts the RFC XML message to a valid RFC call and executes the call.
Proxy :
Generally speaking, interfaces are where functions in a system can be executed. In the context of SAP Exchange Infrastructure, only the following interfaces are relevant:
·        Interfaces designed for message exchange between application systems
·        Interfaces used by a cross-component integration process to receive or send messages, or both
Starting with a cross-system integration process, you can then derive the corresponding interfaces required. SAP Exchange Infrastructure supports this process by using an integration scenario to describe the collaborative process. The integration scenario summarizes the interfaces required for this collaborative process.
You can use SAP interfaces that already exist in systems, non-SAP interfaces that are connected to SAP Exchange Infrastructure using adapters, or define new interfaces called message interfaces in the Integration Repository. Both worlds can also be interconnected in a collaborative process.
Interfaces are an essential component of SAP Exchange Infrastructure:
·        You define the interfaces to be used in an integration scenario.
·        Cross-component integration processes use interfaces to exchange messages.
·        You define the XML transformations for messages that are to be exchanged between two interfaces in a mapping.
·        You assign an interface in a sender system to one or more interfaces in a receiver system in logical routing.
·        You generate proxies to implement your scenario based on message interfaces.
You save interface descriptions (message interfaces, BAPIs, RFCs, and IDocs) in the Integration Repository so that they can be referenced throughout SAP Exchange Infrastructure. However, adapters for external systems do not normally use interfaces; instead they access files or database tables in order to function, for example. For this reason, it is not necessary to import these interfaces into the Integration Repository. If the structure of the message is described using a WSDL, XSD, or DTD schema, you can import the schema as an external definition.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

RFC adapter with load balacing

Hi Guys,
I have configured RFC adapter for load balancing and i am getting 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>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: RfcAdapter: receiver channel has static errors: can not instantiate RfcPool caused by: com.sap.aii.af.rfc.RfcAdapterException: error initializing RfcClientPool:com.sap.aii.af.rfc.core.repository.RfcRepositoryException: can not connect to destination system due to: com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=sapdev02 GROUP=PUBLIC R3NAME=EDV MSSERV=sapmsEDV PCS=1 ERROR service 'sapmsEDV' unknown TIME Mon Jun 4 17:11:55 2007 RELEASE 700 COMPONENT NI (network interface) VERSION 38 RC -3 MODULE niuxi.c LINE 1725 DETAIL NiPGetServByName2: service 'sapmsEDV' not found SYSTEM CALL getservbyname_r COUNTER 1</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
any help would be appreciated
Thanks,
srini

Hi,
check out these:
1) SM59 - test connection
2) look all the parameters of Receiver RFC adapter configuration
Proper authentication details etc
3) Save the RFC adapter channel and activate the same
4) Refresh the cache for the Adapter metadata. Go to Integration BuilderAdmin>Cache Overview-->Directory -->Adapter Metadata
5) Probably the problem may be becuase of RFC Adapter is not active. Restarting the RFC adapter at J2EE admin level may solve your problem
Hope this helps,
Regards,
Moorthy

RFC adapter not responding

Hi guys,
We are facing the following problem:
We have a receiver RFC adapter that executes some RFC functions on a SAP R/3 system connected to XI. When the R/3 system is down (e.g. for maintenance reasons) the RFC adapter (communication channel) has a red "error" status in Communication channel monitor (that could not connect to R/3), which is ok. However, when the R/3 system goes up, the RFC communication channel remains in the same error status, irrespective of the fact that the R/3 is now up. Morever, it needs some manual stop and start from CC monitor in order to be able to "see" that the R/3 is now up. This has an impact on our interfaces that it may be the case that sometimes the administrators, fail to notice this and the corresponding interfaces that make us of the RFC adapter, fail for no reason.
Is there a way to avoid this undesirable situation?
Best Regards
Evaggelos Gkatzios

Hi Gkatzios,
we also facing same problem as your,,when the R3 system is down for some maintenance reason at the same time XI expects something from R3 ,in this situation RFC adapter is going to error state,when R3 is up RFC adapter works fine but CC still shows error status.but some times we have to stop and start CC manually.
everytime when we open the CC monitoring particular CC always in error state eventhough it is working fine..
If you find any solution for this please let me know.
Thanks for your time.
Regards
Rao

Using RFC adapter as TRFC call

Hi Folks,
    My requirement is to use the RFC adapter as a TRFC call. Can anyone guide me how to do that ?
Regards,
   Santosh

Hi,
   Is your RFC at the sender side or at the receiving side?
If it is at sender side, you can call the rfc function module in UPADTE task .
Sample Code:
CALL FUNCTION <FM Name> IN UPDATE TASK EXPORTING ......
If it is at receiver side, you can specify the QoS as EO(Exactly once in the sender adapter)
Re: How to make an asynchronous RFC call using the receiver RFC adapter?
Regards,
Ravi Kanth Talagana

Receiver RFC Adapter

Similar Messages

Maybe you are looking for