Limitations of RFC Adapter XI 3.0

In this presentation ( https://www.sdn.sap.com/content_documents/.../SAP%20XI%202.0%20-%20Features.pdf page 20), the following limitations are listed for the RFC Adapter for XI 2.0:
Functionality
Synchronous RFC
  No support forRFMsthat use update task without COMMIT WORK
  No SAP GUI
  No callbacks
  No session handling
  No RFCs to non-SAP systems (using RFC client or server libraries)
tRFC: Support for exactly-once delivery for one message/call
  Not all tRFC functionality
  No „bundling“ of multiple calls
With version 3.0, what are the current limitations??

SAP Documentation states the following:
Constraints
Note the following restrictions:
·        Assignment is only guaranteed for transactional RFCs (tRFCs), that is, for messages with quality of service Exactly Once (EO).
·        There is no transactional context for more than one RFC call for each LUW (Logical Unit of Work).
·        Not provided: SAPGUI, callbacks, and qRFC (quality of service Exactly Once In Order (EOIO)).
·        RFC library clients (RFC SDK) are not supported.
·        The context in the called system is not kept open over multiple calls (calls are stateless; there is no session).
·        Only the payload of a received message is evaluated. Additional attachments are ignored and not forwarded.
·        The receiver adapter can only process valid RFC XML documents, for example, those generated by the sender adapter or by the SAP JCo.
available at: http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
best Regards
Christien

Similar Messages

  • RFC adapter limitations

    Current limitations of RFC adapter are: No SNC, No Call-Back, no RFC-GUI-Debug, no qRFC.
    Could you please tell me what they mean ?? especially SNC ??
    thanks
    kumar

    Kumar,
    No SNC: SNC is secure network communications. Check this sap help for further information on this palnati:
    http://help.sap.com/saphelp_nw04/helpdata/en/ff/7932e4e9c51c4fa596c69e21151c7d/frameset.htm
    No Call-Back:
    http://help.sap.com/saphelp_nw04/helpdata/en/22/0425ac488911d189490000e829fbbd/content.htm
    No qRFC:
    Check this help:
    http://help.sap.com/saphelp_nw04/helpdata/en/0b/40693c1b331c6ae10000000a11405a/content.htm
    ---Satish

  • 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. :
    <b>call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:</b>
    The File is also getting written to the destination properly. But in XI also i get the following error.
    <b>  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <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></b>
    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

  • Queries on RFC adapter

    Hi,
      Reading up on RFC adapter at the moment
      Read that RFC has limitations such as No Call-Back, no RFC-GUI-Debug, no qRFC and no SNC.
      Is there any link that will give a more detailed explaination on the above items?
      Thanks.

    Hi,
      These links provide more information
    http://help.sap.com/saphelp_nw04/helpdata/en/11/028417f9f8b24cbe1b0b398e1cb76a/frameset.htm
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    /people/sravya.talanki2/blog/2006/12/27/aspirant-to-learn-sap-xiyou-won-the-jackpot-if-you-read-this-part-iii (search for RFC adapter)
    SAP note : 730870
    Regards
    Vishnu

  • Monitoring of older RFC Adapter messages - RFC API

    Hi,
    I have successfully implemented a number of scenarios (File to rfc & File to Idoc)that required external data lookup - using the RFC API (calling a customer RFC FM) (and parsing the response with DOM).
    I am also using Global variables to store my lookup responses to help minimize the number of RFC calls invoked.
    When trouble shooting - as expected the log in the communication channel for the RFC adapter shows the BAPI response. However the number of records is always restricted to 25.
    If I process a message with 30 records, and lets say the first RFC Lookup fails but the remaining 29 are successfully - because the log is limited to 25 I lose a record of this error.
    Am I missing another method of search?
    Is this just a display restriction and perhaps I could report over the underlying tables myself?
    Regards
    Andrew

    Communication channel monitoring is as i understood primarily für monitoring the module chain a message is eventually running through. Did you try monitoring via RWB->Message Monitoring or sxmb_moni? There also should be a reference to the response. Maybe I didn´t get you right, but as far as I remember RFC Calls are also listed there with a bigger history.
    Thomas

  • FILE-RFC ADAPTER problem

    Hi all,
    I am trying file->xi->rfc adapter scenario.
    My scenario is employee information is written to flat file n  will be kept on ftp server.THe file adapter will pickup the file and sends it to rfc adapter through pipeline service.
    This is going well. The problem is the data is not being updated into receiving sap system.
    in SXMB_MONI transaction the messages are successully processed . But there are no messges in rfc adapter when i gone through idx5 transaction???
    Any one have idea??
    Thanks in advance.
    Rgds,
    Ram Sri

    sxmb_moni only shows the status of the integration engine's processing, not the result of what happened in the rfc call.  First, you can check if the adapter framework successfully passed the message to the destination system (not on moni, thru RWB)
    as far as did the rfc succeed - it's as difficult as always with internal processing.  We did a lot of testing by debugging modules on the destination side (manually putting in the data as the adapter would've to step thru & see where the message is "lost") - have not yet found a better way, sorry.  It's not so much a problem with XI, just in general the difficulty to debug rfc's

  • 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

  • Error while calling RFC adapter(FILE-XI-RFC scenario)

    Hi,
    I am trying for FILE-XI-RFC scenario. I am getting the following error. I have checked in message monitoring. The error is coming while calling the RFC adapter. Can any body tell what problem is this?
    Regards,
    Dhana
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">AE_DETAILS_GET_ERROR</SAP:Code>
      <SAP:P1>af.f23.sofd00001530a</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText>2: Unable to find URL for Adapter Engine af.u7a.us4296</SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error while reading access data (URL, user, password) for the Adapter Engine af.f23.sofd00001530a</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>

    Hi,
    I did SLD check.
    The status says 'Summary: Connection to SLD works correctly'.
    But it fails while checking the access to XI profile.
    Here is the status
    Summary: Connection to SLD works correctly
    Now checking access to the XI Profile
    Properties of RFC destination LCRSAPRFC
      RFC host:
    %%RFCSERVER%%
      program id:      LCRSAPRFC_DZ1
      gateway host:
      gateway service:
    Testing the RFC connection to the SLD java client...
    RFC ping returned exception with message:
    / CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=679#Transaction program not registere

  • Error while doing commint from RFC Adapter

    Hi,
    We have a SOAP-PI-RFC synchronous scenario. Through this Soap request comes to PI and passed on to BAPI via RFC adapter. This BAPI saves the transaction & return the document number. We are using " PI PI parameter u201CCommit Handling for single BAPI' in RFC receiver Channel.
    While this setup works for 1 posting, when we do the mass load ( Say 20 Documents) half of the documents are not able to Save. Although BAPI, returns the document number but on checking the document does not exists in SAP. To do further test, we created a program in ECC and try calling BAPI in loop and calling BAPI Commit.
    This way program works fine and there is no error
    So in nutshell, when we PI do the commit, half of the documents are not saving where as when the ABAP program commits no error. Is there any  special way that PI calls this commit work.
    PS: We created a wrapper BAPI which calls the orgirnal BAPI and Commit BAPI & called this from PI but still the same problem is coming.
    Appreciate help on this.
    Regards,
    Harish

    Are there any error messages in the RFC Reciever channel in Runtime Workbench?
    RWB -> Component monitoing -> Adapter Engine -> Comm Channel -> filter for type RFC
    Please try to give some more details on why the system says the messages are failing.

  • RFC Adapter Problem: Necessary Roles?

    Hi XI Gurus,
    Our team is working with a File-to-RFC scenario. We are using a custom RFC, which uses BAPI_GOODSMVT_CREATE within it, to post data for Goods issue, Goods receipt and Transfer Posting. We are using the credemtials of a user, <b>sapxiuser</b>, within the RFC adapter. <b>Can anyone please tell me what are the roles that are to be maintained for this particular user at the R/3 end?</b>
    Points will be rewarded!
    Thanking in anticipation,
    Amitabha

    Hi,
    Remember to add explicit commit in the communication channel:
    <i>"
    <b>Commit Control for Individual BAPI Calls</b>
    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.
    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.
    The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values “”, “S”, “I”, and “W” are displayed. All other values are regarded as errors.
    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.
    "</i>
    Regards,
    Wojciech

  • Restrict messages in RFC adapter or in source/sending (SAP R/3) system

    Hi All,
    I have SAP R/3 to web service scenario via XI (RFC to SOAP). In that scenario RFC caries the attachments, some time the attachments size is more than 5mb. Due to that java stack of XI becomes unresponsive. Due to that SMQ2 gets filled up with the entries and other scenarios are also severely effecting.
    Is there any way to restrict the message, if itu2019s size is more than 5mb in RFC adapter of XI or can we stop the processing/sending of such a messages in source system itself (SAP R/3).
    I welcome all your suggestions.
    Thanks & Regards,
    Venu V

    Hi Praveen,
    The attachments to the tickets in source system. The RFC caries that data, once that data size is more than 5mb then it affecting the server.
    I am getting following errors
    u201Ccom.sap.aii.af.ra.ms.api.DeliveryException: Could not create Message from TransportMessage. Reason: com.sap.aii.af.ra.ms.api.MessagingException: com.sap.aii.af.ra.ms.api.MessagingException: Could not parse XMBMessage due to Read timeout. The client has disconnected or a synchronization error has occurred. Read [45434] bytes. Expected [101981].u201D
    u201CJCO_COMMUNICATION_FAILURE
    Error opening an RFC connection
    &quot;COMMUNICATION FAILURE&quot; during JCo call. Error opening an RFC connectionu201D
    Thanks & Regards,
    Venu V

  • RFC adapter in XI 3.0 not working properly with BAPI in R/3 4.6C

    Here is the scenario.
    An XML file is received from our customer. This file contains purchase order information that is used to create a sales order in our SAP 4.6C system. Once the sales order is created an acknowledgement is generated and this is returned back to our customer in an XML format.  This scenario is working perfectly fine in our XI 2.0 system but is not working properly in our XI 3.0 test environment. Our custom function module in R/3 is a wrapper function that uses a standard SAP BAPI to create the sales order. Part of the function module does use the statement
    call function 'BAPI_TRANSACTION_COMMIT'
    The last thing the BAPI does is call another function module that using an RFC destination that will return and order acknowledgement.
    Here is what happens within XI and our SAP system.
    The XML file is received and mapped to our imported RFC. The RFC adapter is called and the information is passed onto SAP where our customer function module executed. The sales order is created within SAP without any problems and the second function module is called which references an RFC destination assigned to our XI 3.0 system. The information is sent back to XI and an appropriate file is created for our customer.  All seems to be working properly except that when the original RFC is sent from XI to SAP,  SAP creates a short dump stating
    "call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:" Then it is put back into the que where 5 minutes later it executes again and trys to recreate the sales order in SAP. (again, this same function module executing from XI 2.0 works fine)
    I believe I have everything configured properly because the SAP side is being executed and I am successfully passing information back from SAP to XI. However the original function module in SAP is failing with the above error message. It appears that the original function module cannot communicate back with XI. I have had SAP looking at this issue and they have not been successful yet in solving this problem.
    Any ideas.
    Thanks,
    Jim d'Hulst

    Hi,
    I think the problem is with the send back of acknowledgement to XI. Does the DeliveryException state something about the sender agreement? I guess you are using a statement like below:
    CALL FUNCTION 'ZABCD'
    destination <tcp/ip destination>
    exporting
    input = ack.
    In that case, check whether the TCP/IP destination is working fine. Also, to be able to exchange message, the structure of the Function Module ZABCD needs to be identified as the sender in XI Configuration (Integration Directory).
    Also, check your config with the blog mentioned below:
    <a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit">/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit</a>
    Regards,
    Amitabha

  • Dynamic user in RFC Adapter

    I configure a RFC Receiver adapter to communicate with R/3. In my client application  (via Webdynpro) I send the message that use this communication, but I need to call the RFC using a dynamic user/password, that is, the user credentials that is logged. Is it possible? How I do it?
    thanks.

    Hi Elton,
    I don't think so, it is possible to have dynamic user ID and password for the RFC adapter. As of now...
    Because you need to enter the user id and password while configuring adapter itself.
    But if you want , you can call different RFCs based on the Condition etc.
    Hope this helps,
    Regards,
    Moorthy

  • 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

Maybe you are looking for

  • Problems with RX300se on Nforce4

    Hi guys and gals I own a msi rx300se td128e (pcx) and am having alot of trouble with it on my ECS Nforce4-A939 motherboard ,amd64 3200+processor . I install the card and then installed the drivers and all seems to be fine and the computer tells me to

  • Automatically Delete Troubled Files

    You know those stupid files that have those stupid exclamation marks next to them is there a way to simply delete those without having to click multiple times on the song and manually do it?

  • POSSIBLE BUG on page 0 in 3.1.2 and 3.0

    Hi, Could one of the APEX developers have a look into this bug for me? How to replicate it? 1. Create an application with 2 pages and one page zero 2. On page zero create a html region and create a button and select "Create a button in a region posit

  • Sql Developer and Data Guard enabled instance

    I have version 1.1.2.25 SQL Developer and when I try to connect to Oracle 10gR2 instance which is data guard enabled and its logical standby it spits few message, and then connects, but data is not visible from any table. Is there any way to see data

  • How can I open a file I created in CC InDesign in CS 6 InDesign?

    My workplace purchased Creative Cloud license last year, so I created a 60 pages catalog using CC InDesign about 1 month ago.  Now my department has migrated CS 6 instead of CC version.  None of my CC files can be open by CS 6 InDesign.  How can I so