Synch RFC

Hello,
I am doing an interface - R3-XI-File. The R3 RFC is called synchronously. I am checking if the file is posted at the receiver side or not by using Transport ackin BPM. In exception handling, deadline handling - I am returning the response to R3.
These are the steps I did,
1. I have rfc dest of type TCP/IP - in R3 - used that program id and defined RFC sender adapter in XI. - checked if rfc dest works - works fine. I have used the same rfc desc for Asynch process which works fine.
2. I have called the RFC inside a fm like this
call function 'ZFM_RFC_SYNCH'
      destination 'XIRFC'
      tables
        FT_table1  = ITWA_table1
        FT_BAPIRET2 = FT_BAPIRET2.
3. I am getting the following error in the sxmb_moni
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIAdapter</SAP:Category>
  <SAP:Code area="BPE_ADAPTER">SYNCHONOUS_MESSAGE</SAP:Code>
  <SAP:P1 />
  <SAP:P2 />
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>This process does not support the specified synchronous interface or does not support any synchronous messages The exception occurred (program: SAPMHTTP, include , line: 0)</SAP:Stack>
  <SAP:Retry>N</SAP:Retry>
  </SAP:Error>
4. Audit log shows me this
Success RFC adapter received sRFC for 'ZFM_RFC_SYNCH' from R3/010. Attempting to send message synchronously
Success - Application attempting to send an XI message synchronously using connection AFW.
Success - Trying to put the message into the call queue.
Success - Message successfully put into the queue.
Success - The message was successfully retrieved from the call queue.
Success - The message status set to DLNG.
Error - Received XI System Error. ErrorCode: SYNCHONOUS_MESSAGE ErrorText: ErrorStack: This process does not support the specified synchronous interface or does not support any synchronous messages The exception occurred (program: SAPMHTTP, include , line: 0) 
Error - Returning synchronous error notification to calling application: XIAdapter:SYNCHONOUS_MESSAGE:.
Error - Transmitting the message using connection http://host:port/sap/xi/engine?type=entry failed, due to: XIAdapter:SYNCHONOUS_MESSAGE:.
Error - The message status set to FAIL.
Anyone knows where the problem is exactly???
My BPM has receive step - opens SA bridge - then mapping to file message type - block with send step to file adapter - which has deadline and exception handling - for transport ack - and then send step to RFC resp - close SA bridge...
Anyhelp is greatly appreciated.
Thanks
Thilothama

I found what I missed. The BPM had a wrong interface in Config side. Previously I had async scenario and changed to sync..so didnt change to sync interface....Now its working.
I have one more question...For File transport ack - can we check the particular return message and do the processing?? instead of deadline and exception branches??
If the transport is successful, I see this message
  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!--  Response
  -->
  <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7
If its negative, I get
  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!--  Response
  -->
- <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.MessagingException: Channel 'File_Receiver', Service 'File', Party '': File Adapter configuration not activated: com.sap.aii.af.ra.ms.api.RecoverableException: Channel 'File_Receiver', Service 'File', Party '': File Adapter configuration not activated</SAP:AdditionalText>
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack />
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>
the reason is, for negative ack I use the exception brach and send the resp to R3 - saying the file was not processed. But if its success..I shold have another dummy mapping which should say successful....which I am not very much happy to do...is there any other way you can think of?? or worked on???
Thank you for all your great suggestions...

Similar Messages

  • Synch RFC--BPM --Sync JDBC

    Hi All,
    I am doing a schenario where in im using BPM.
    Synch RFC from XI box will trigger the interface, then i will make a synch call to sql server & synch call(RFC) to R/3.
    Can anyone please letme know the steps required in BPM.
    Do i need synch-async bridge?
    And also lemme know if i can map a ASyncronous Message Interface to a Syncronous Message Interface.
    Can i Map source as Synch RFC & target as synch sql & synch rfc R/3.If not how do i map
    Thanks
    Sumit
    Message was edited by: Sumit Khetawat

    Sumit,
    I just looked upo into one of my SYNCH AYNCH Scenarios and i have created my interfaces exactly like i mentioned in these steps,
    <i>1. RECEIVE step ==> Opens SYNCH ASYNCH bridge and receives RFC request message.
    ( This will have a synchronous message interface associated with it. A synch abs interface and will be used for the PROPERTY ~~Synchrnous Message in the BPM) We would also need an ABS ASYNCH Message Interface created for the Request Message and this should be used in the MESSAGE ( after creating CONTAINER element) for the same. )
    2. Transfrom step ==> Map RFC request message to JDBC request message. Mappinng between 2 abs Aynch Interfaces
    ( You will have container elements created for REq RFC as stated in the step 1 and another for JDBC request )
    3. SEND synchronous ==> to send JDBC request and get the JDBC response.
    ( You will use a SYNCH ABS against MESSGAE INTERFACE , and also, a separate ABS ASYCNH for request and response )
    4. TRANSFORM step==> Map JDBC response to RFC response . Mapping between ABS Interfaces
    ( same as step 2)
    5. SEND ==> Closes SYNCH ASYNCH bridge and Send's response back to the RFC.</i>
    Use the Container element created for the mapping in step 4.
    In case of Split mapping, again you will need ABS ASYNCH Message interfaces.
    Drop me a mail if you need screen shots.
    Regards,
    bhavesh
    All you mapping in the BPM is between Asynch Abs Interfaces.

  • Synch rfc to file

    hi
    is synch asynch bridge used in synchronous rfc to file please? if so how does it work?

    >>Is there a scenario like synchronous rfc to file?
    >>Do we use synch asynch bridge for that?
    Yes. Follow this Blog Demonstrating Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi By Sriram Vasudevan. It demonstrate a scenario of Sync Http and file in you case the sender is an SAP RFC function.
    Thanks
    SaNv...

  • Synch RFC error

    Hello,
    in one of our BPMs we have to use a synchronous RFC to avoid that a server error is thrown due to a timeout. The RFC triggers an IDOC to be created (we use correlations) but under some conditions there might be no IDOC created and our BPM throws a server error with timeout.
    We have already set the <b>xiadapter.inbound.timeout.default</b> to a higher value to avoid the MessageExpired (INBOUND) error. But now we have this error:
    <b>com.sap.aii.af.ra.ms.api.RecoverableException: com.sap.aii.af.ra.ms.api.MessageExpiredException: Message be79b430-aad3-11db-cf2b-001185eb2336(OUTBOUND) expired</b>
    Unfortunately the <b>xiadapter.outbound</b>-Parameters are only for asynch calls. Now, is there another parameter which has to be increased?
    Regards.
    Oliver.

    try implementing this blog - /people/community.user/blog/2006/09/21/xi-rfcadapter-reconnect-issue
    Should help you solve the reconnect issue. I assume time out should be a direct interferance with the same.

  • JDBC to RFC synch RFC call not executing.

    Hi,
    I am working on the synchronous JDBC to RFC without BPM. After completing design and config when I test the complete scenario the data from databse is not getting updated in R/3. And I do not see any errors in MONI. But when compared the moni logs I observed the following between the working scenario and not working scenario.
    <u>Working scenario log in MONI:</u>
    <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>ECS300</SAP:Service>
      <SAP:Interface namespace="<b>http://sap.com/xi/XI/System</b>">InterfaceCollection</SAP:Interface>
    - <SAP:Mapping notRequired="S">
      <SAP:ObjectId>YYgNVKC9PTCW4JlMapfxZQ==</SAP:ObjectId>
      <SAP:SWCV>IrmTYNPLEdqKItGjlusuXw==</SAP:SWCV>
    <u>Not working log from the MONI:</u>
    ++++++++++++++++++++++++
    <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>ECS300</SAP:Service>
      <SAP:Interface namespace="<b>http://my_Own_namespace</b>">JDBC_Rfc_Synch_MI</SAP:Interface>
    - <SAP:Mapping notRequired="M">
      <SAP:ObjectId>28ZZbGggOw6UcnigDXMD7A==</SAP:ObjectId>
      <SAP:SWCV>IrmTYNPLEdqKItGjlusuXw==</SAP:SWCV>
      <SAP:SP>-1</SAP:SP>
      </SAP:Mapping>
    Could some body point me where I am doing wrong ?
    Thaks
    Steve.

    Hi Steve,
    I think the error is because your database table is expecting some kind of input and the input you are passing has some error in it.Just cross check the table using DESCRIBE <tablename> with the data you are trying to enter.
    Also Just look at Query SQL Statement part ubnder this link,
    http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm
    Regards,
    abhy

  • Dispay RFC sync payload in SXMB_MONI

    Hi all,
    I hava a synchronous scenario RCF-TO-SOAP (RFC sender is R3 client).
    On XI I want that the parameter LOGGING_SYNC is set to 0, but at the same time I want
    to see the inbound payload in SXMB_MONI. I want to see it only for this specific scenario.
    How to achive this ? (maybe to do some setting or programming on R/3 before making a synch rfc call ?)
    Thanx, Janos

    Thanx for the answers, but I wonder if it is possible to set up logging just for one type of messages -
    when RFC sync sender is R/3, as it is stated in the link below:
    http://help.sap.com/saphelp_nw70/helpdata/EN/d6/49543b1e49bc1fe10000000a114084/content.htm
    Set logging in the message header. This means that this message is logged even if logging
    is deactivated explicitly in the configuration. The logging information is part of the message
    header:
    <SAP:Logging>1</SAP:Logging>
    Thanx, Janos

  • Adapter Engine monitoring doesn't show messages

    I have 2 scenarios
    1. Synch HTTP -> Synch RFC
    2. Synch HTTP -> Synch BPM -> Synch RFC
    In case 1 Adapter Engine monitoring shows all messages correctly
    In case 2 there is no entry for HTTP Sender system only BPM->SAP System.
    Could you help me why RWB doesn't show it?

    denis,
    just to add to what moorthy has told. IDOC and HTTP adapters interact directly with the INTEGRATION ENGINE on the ABAP STACK while, the other adapters interact with the ADAPTER ENGINE available on the J2EE STACK.
    That is why, you do not gind the same on the RWB --> ADAPTER MONITORING.
    Also, the reason why you do not have a SENDER HTTP and IDOC adapter.
    Regards,
    bhavesh

  • Performance header in message monitoring

    Hello
    I have scenario XI -> synch RFC Receiver.
    In message monitoring I select response message and performance header part.
    There are entries:
    INBOUND, Request MAPPING, OUTBOUND, CALL ADAPTER, Response MAPIING
    Does this time include RFC call through RFC Adapter?
    Or it includes only IE processing like mapping.
    What will include the time: <b>last time entry - first time entry</b>?
    Whill it equal: request mappingRFC callresponse mapping?

    Hi Denis,
    the best way to monitor the performance
    is the performance monitor tab in RWB
    have you tried it?
    you can monitor single interfaces and
    also aggeregated
    Regards,
    michal

  • Fault message mapping

    Hello,
    I have following scenario.
    Synch, RFC Sender -
    > XI----
    >JDBC receiver.
    Also I have defined Fault message data type, message type and also createed Message Interface in which I specified Fault Message type. Now my question is.
    When an error occurs I want to get error message to be captured in fault message and map the fault message elements to RFC ---> Rerutn item elements. I was wondering how would I accomplish this?
    Thank you,
    Balaji

    For sender RFC:
    http://help.sap.com/saphelp_nw04/helpdata/en/67/6d0540ba5ee569e10000000a155106/frameset.htm
    You must to create a in sm59 in R/3 and XI an R3 conection.
    You can see this very interesting blog: /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    Regards.

  • Error in IDOC Distribution Model

    HI all ;
    Please Help me in this Issue!!
    am  working with standard IDOC  Using MATMAS (Material Master Transfer)
    LS_800 - Outbound.
    LR_810 - Inbound.
    --> BD54.
    --> SCC4.
    -->SM59.
    -->WE21.
    -->WE20.
    --> WE20 ( in inbound side) Clear Up to this level.
    After that the Problem in Distributing the Model,,,,
    In Bd64 t-code Distribution Model.
    while Generating the Partner Profiles in BD64 ;
    its giving the blank message like below.
    No message has been defined for the selection conditions in the model.
    when we distribute(in BD64) 2 Errors (red) Like Below;
    RFC destination for Syncronous Communication (Message type SYNCH)
    Partner Profile LS LR_810 SYNCH does Not Exits.
    Generate Partner Profile.
    or Specify outbound partner Profile for message type SYNCH
    RFC destination for Syncronous Communication (Message type SYNCH)
    Partner Profile LS LS_810 SYNCH does Not Exits
    Generate Partner Profile.
    or Specify outbound partner Profile for message type SYNCH
    Thannks;
    Upender.

    In Bd64 t-code Distribution Model.
    create the model view ,
    add message type Matmas to it.
    -> select the model view
    ->environment-> generate partner profiles
    In Partner Profiles u hv to maintain the Outbound parameters in Both LS_800 &
    LR_810 .
    in receiver port, double click & make sure that the rfc destination assigned connects successfully..
    Regards.

  • Calling Remote Functions Locally Triggers any Database commit(Implicit)

    Hello,
    Am making use of RFC enabled function module as normal function module (Calling remote function module locally).
    My question is does it trigger any implicit database commit or not. Since synchronous RFC triggers database commit.
    Regards,
    Tenzin Choegyen

    I057200 wrote:
    Since synchronous RFC triggers database commit.
    Let me correct the statement both synchronous as well as asynchronous RFCs trigger an implicit DB commit.
    SAP documentation on synch-RFCs states:
    If the content of dest is equal to the constant space, then the addition DESTINATION is ignored and a normal call CALL FUNCTION func is executed.
    Please note that you should not use the DESTINATION addition or use DESTINATION space. DESTINATION none will start the FM as an RFC in the same app server.

  • RFC destination for synchronous communication (message type SYNCH)

    Hi experts,
    I am trying to configuare ALE settings.waht i did is
    My sending & receiving systems are one server with different clients.By using SALE transaction
    1.crated logical systems.(LS_800 &LR_810)
    2.Assigned those to clients.
    3.Created RFC destination
    4. Created modelview assign sending & receiving
    systems and message type.saved it.
    4.generated Partner profile.Here i am getting below problem
    Target system LR_810
    RFC destination for synchronous communication (message
    type SYNCH)
    Partner profile LR_810 SYNCH does not exist
    Generate partner profile or
    specify outbound partner profiles for message type
    SYNCH
    Target system LS_800
    RFC destination for synchronous communication (message
    type SYNCH)
    Partner profile LS_810 SYNCH does not exist
    Generate partner profile or
    specify outbound partner profiles for message type
    SYNCH
    Regards;
    Upender.

    Hi Shital;
    Thanks for your replay;
    Still am getting the Same Error;
    Thanks;
    Upender.

  • Error in SAOP adapter : RFC to SOAP Synch Scenario

    Hi Experts,
    Scenario is "RFC to SOAP Synch".
    For creating this following this link : **************** - Scenario on RFC to SOAP
    Trying to send XML to SOAP receiver.
    Using Below details for SOAP:
    Website : http://www.webservicex.net/WS/WSDetails.aspx?WSID=59&CATID=4
    Target URL : http://www.webservicex.net/SendSMS.asmx?WSDL
    SOAP Action: http://www.webserviceX.NET/SendSMSToIndia
    But when I try to send showing this error:
    "Error in processing caused by: com.sap.aii.af.lib.mp.module.ModuleException: call to messaging system failed: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: unable to create a socket".
    Any one please suggest how resolve this issue?
    Is there any setup necessary in PI server to send message through SOAP?
    Thanks,
    Arthita

    Is there any setup necessary in PI server to send message through SOAP?
    No
    Solution
    Check if there are any firewall rules in place which are restricitng the PI system to connect with the URL
    : http://www.webservicex.net/SendSMS.asmx?WSDL
    Suggestion
    Copy paste this URL in browser and verify if it is accessible
    Sourabh

  • SOAP to RFC scenario (SFDC - ECC synch)

    Working on a SFDC to ECC synch scenario using SOAP to RFC interface. I generated the WSDL for SFDC team and tested on soapUI, I am able to see the successful request/response structure in sxmb_moni.
    However, when the SFDC team is sending the request in real time from SFDC, the request is successful in SFDC but not reaching PI and hence there is no response. The error I see in sxmb_moni for this  is
    <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="INTERNAL">PROXY_NOT_ALLOWED_ON_IS</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Proxy calls are not permitted on sender or receiver side on the IS (client)</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
      </SAP:Error>
    Are there any additional setting need to be done.
    Please guide on this issue . Thanks
    Edited by: jbagga on Nov 14, 2011 7:42 AM

    SFDC sending request to PI. SFDC Request is not hitting PI, neither traceable in MONI or RWB.
    SFDC request is not hitting PI . The ForeFront has allowed the SFDC IP range to target PI using reverse proxy rules. But SFDC and Forefront both get the "HTTP 500 internal server error"
    The question is , I am helpless until the request is monitored anywhere in MONI or RWB_communication channel
    Also SFDC receives some fault message error along with HTTP 500 i.e. Header Missing in Soap Message Header. In this case, also if its PI related error there should be at least some track of request hitting PI in MONI or RWB. also tried creating a WSDL with PI username and password in the WSDL under Header tags, still the same situation
    ALL Ports are open by BASIS team.
    Can someone point out any helpful solution. URGENT !! Thanks a ton in advance.
    EVERYTHING , THE ENTIRE REQUEST/RESPONSE STRUCTURE WORKS PERFECT WITH SOAPUI.

  • BPM RFC synch send step

    Hi
    I am using RFC synch send step with in parforeach block in BPM. do I need to activate correlation to correlate synchronous request and synchronous response for RFC synch send step ?
    Please let me know if you have any ideas on this.
    Thanks
    Anand

    Hi Michal,
    Thanks for the reply.
    In SAP help I found the statement made below.
    Activating a Correlation
    An asynchronous or synchronous send step can activate correlations. This can be useful in the following cases:
    ·        Synchronous send step
    A synchronous send step waits for a reply message to be received. On receipt of this reply message,
    correlations can be activated to correlate additional messages.**********************************Any idea on highlighted sentence...
    Thanks
    Anand

Maybe you are looking for

  • How to share iTunes with my wife ? (i'm a noob)

    Hello all. i'm a noob in Mac world and iTunes also (i'm coming from PC world so...) so sorry in advance if i don't use the correct Mac vocabulary... So here is my problem: my wife and i share a Mac Pro. we also share one iTunes. Let's say that  our w

  • External Hard Drive will not mount

    My external hard drive that I been storing all my aperture files on is not mounting to the desktop. I can see the hard drive when I use my disk utility, but it doesn't show up in the desktop. When I purchased the hard drive originally I didn't format

  • Clips from FCP are not appearing in MOTION!!!

    Sorry to bother but I'm doing the tutorial... and I'm following every step and what I'm trying to do is open up my timeline into Motion. These are the steps: Highlight the clips from my timeline go to FILE, SEND TO "Motion" Project A SAVE dialog box

  • Itunes fails to install and repair cannot fix

    I have tried to download new version of itunes and it will not work and repair fails to remedy this

  • 11.2 cluster database instances crashed..

    Hi all, we have a two node 11.2 cluster on OL 5.7. Today our cluster database instances on node two all crashed. I found several log entry´s. There are all addicted to network. _____Alert log Thu Mar 22 09:15:31 2012 Errors in file /u01/app/oracle/di