Reg N sender 1 receiver scenario

Hi Experts,
i have one basic doubt ,is it possible to have a scenario with multiple senders and one receiver without using BPM in a single interface..
Say  we have a common sender  structure for all N system. and one sender message interface,MM,IM  and which can be resused  by all the system.
Regards,
srinivas

Hi all,
i did an extensive search in sdn.closing this thread. Below are the useful links for the same topics.
using wild card char * may be a bit risky as multiple interfaces might be runnig for the same receiver, would prefer a simple BPM, rest depends on the requirement.
Multiple Senders - One receiver
Regarding Multiple senders to single receiver
Multiple Senders on A2A
How can i have multiple Sender agreements in a single interface suggested not to use wild card "*" instead create 3 receiver determination with same channel
Multiple Senders to Inbound Proxy Scenario
Multiple  sender file may be useful.
Having multiple sender components send to one receiver component ?
WSDL based on multiple sender interfaces: Re: WSDL based on multiple sender interfaces   Very helpful
Approach for Multiple Sender? links
Multiple Sender to one Receiver links
Regarding Senders And Receivers
regards,
srinivas

Similar Messages

  • Missed data JDBD Sender- RFC Receiver Scenario

    Hello,
    I simulated a JDBC synchronous scenario by developed a JDBC Sender-RFC Receiver Scenario to retrieve data from an Oracle Database and inside the RFC , ECC executed a Proxy-JDBC scenario to mark the retrieved items in the Oracle Database.
    Sometimes, in my productive system, some of the items retreived from de JDBC sender seems to be missed. In TA sxmb_moni i saw the message from the JDBC sender channel but the ECC don´t send the message from de proxy request inside the RFC, wich means that RFC doesn´t execute. And a time after without any kind of action, the complete scenario work fine.
    We found this trace log in the NWA stack :
    "Catching com.sap.aii.af.service.cpa.CPAException: Couldn't retrieve outbound binding for the given P/S/A values: "
    Thanks in advance.

    Hi Mariluz,
    Make a full CPACache refresh using the following url:
    http://XIhost:port/CPACache/refresh?mode=delta
    http://XIhost:port/CPACache/refresh?mode=full
    note: use PIDIRUSER for refreshing CPA CACHE for the above uri's
    Also Check the note #1057990 for more details
    there might be other reason that below services might abruptly stop check this also:
    - XPI Adapter: File
    - XPI Adapter: JDBC
    Regards,
    Naveen

  • Mail sender and receiver scenario

    Hi All,
    I want to create one MAIL-MAIL scenario,in which I want to send mail message from one mail server and receive the transferred massage in same mail server.
    But I am confused regarding XI's inbound and outbound message for this scenario.
    What should be my outbound and inbound message type in this scenario?(if i want just to send one line from my mail)
    And who will trigger this mail transfer?Do I need to create some settings on mail server?
    please help me.

    Hi Michal,
    >>it will have to look the same as your XML message that you will send via mail
    Can you elaborate on this?
    Means will it refer to the mail content in my my email?
    bcoz I searched on help.sap i got following payload format:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns:Mail xmlns:ns="http://sap.com/xi/XI/Mail/30">
      <Subject>Subject</Subject>
      <From>[email protected]</From>
      <To>[email protected]</To>
      <Reply_To />
      <Content_Type>text/plain</Content_Type>
      <Content>
       This is the content.
      </Content>
    </ns:Mail>
    Please help me.

  • SOAP Scenario-Sender and receiver having same structure- Mapping Required?

    Hi,
    We are having a SOAP to SOAP scenario. In that the sender and receiver are having same structure. Is it possible to by-pass mapping and just do the configuration from ID
    Thanks and regards,
    Siji Anup

    Hi Siji,
    AFAIK you can skip ESR development. Check the example in this blog When and how to create an scenario in SAP PI without mapping objects.
    Regards.

  • Proxy to Proxy Scenario with sender and receiver on same instance

    Hi,
    I have a scenario to integrate Erecruit to HR system usng standard content. Both the Erecruiting and HR are on same instance so my sender and receiver is the same system. Standard ABAP proxies are provided.
    Now I need some help in how to configure the channels and the agreements as both the sender and receiver are on same instance. Do i need to use parties?
    do i have to create a sender communication channel?
    Please let me know the stps required in configuration for this scenario.
    Thanks in advance.

    Hey
    It does not matter if your sender and receiver are same system or different systems,the configuration steps will be the same.
    In your case you would need
    1 Receiver determination
    1 interface determination
    1 receiver agreement
    1 receiver communication channel(of type XI adapter,this will connect to HR system).
    No party or sender communication channel or sender agreement are required.
    You need to have configured 1 business system for HR system in SLD though.
    Thanx
    Aamir
    Edited by: Aamir Suhail on Jul 23, 2008 7:36 PM

  • Need to use only one sender and receiver communication channel.

    Hello Experts.
    I have a scenario where in I have to use only one sender and receiver communication channel to push files from different source directories to different receiver directories.
    For Eg;
    Sender                              
    D://dir1/file1 --->                  E://dir1/File1
    F://dir2/file2 ---->                 G://dir2/file2
    H://dir3/file3----->                 I://dir3/file3.
    Can this be achieved by using pass through scenario?
    Please let me know if the requirement is not clear.     
    Thanks in advance.
    Advit Ramesh

    Hi Advit,
    I think it is possible. You have to use the Advanced Selection for Source file in the sender channel to define multiple files to be picked up. Also, the Dynamic configuration must also be enabled and used in the mapping so you can manipulate the target directory and target file name based on your source files.
    For Polling from multiple directories:
    http://wiki.scn.sap.com/wiki/display/XI/File+Sender+Adapter+-+Polling+Multiple+Directories
    Dynamic Configuration:
    Dynamic file name and directory in Receiver File Adapter - summary of possibilities - Process Integration - SCN Wiki

  • Sender and receiver agreement not cerated

    Hi .
    I am creating configuration scenario in ID by importing the integration scenario which i created in the IR.
    I crated communication channel template also and i added it to the integration scenario in connections.
    Query 1?
    do i have to create Communication channels also.....even After creating communication channel template (because it is not seen the ID below communication channel )
    Query 2 ?
    once i transfer this integration scenario from IR to ID and cerate the configuration scenario (sender and receiver agreements are not getting created automatically)peace tell me what is the reason???.
    and how can i resolve this...
    thanks
    shakif

    Hi Mohamed,
    <b>Query 1?</b>
    <i>do i have to create Communication channels also.....even After creating communication channel template</i>
    Yes You have to create as it's just a template that u created in IR. But u can use the same for creating CC.
    Check this link for what's the Diff. B/w CCT in IR and CC in ID
    Re: Communication Channels
    <b>Query 2 ?</b>
    <i>once i transfer this integration scenario from IR to ID and cerate the configuration scenario</i>
    Yes. it will create automatically.
    Just check my posting in Wiki for simple File to IDOC scenario might be u missing something
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/fileToIDOC&
    and check my reply in this thread
    Re: Doubt in transfering integration scenario from IR
    Regards
    Sachin

  • Error in BPM: "no interface action for sender or receiver found"

    hello,
    i configured a interface scenario SOAP - PI - Idoc using a BPM sync/async bridge.
    i followed the document
    when i try to call interface with my soap client i have the follow error in SXMB_MONI:
    Timeout condition of pipeline reached
    if i check the detail in trace i can found the follow message:
    <Trace level="1" type="T">select interface SI_MATREQ_ABS</Trace>
    <Trace level="1" type="T">select interface namespace http://pmf/orders</Trace>
    <Trace level="1" type="T">--no interface action for sender or receiver found</Trace>
    <Trace level="1" type="T">Hence set action to DEL</Trace>
    in BPM monitor i cannot see any interesting logs for determine the problem.
    I clear cache many time and reimported Integration Process more time.
    Have u some suggestion?
    thanks in advance

    Hi,
      Check whether this thread help you or not....
    SXMB_MONI: no interface action for sender or receiver found
    Regds,
    Pinangshuk.

  • IDOC - BPM - IDOC  Error --no sender or receiver interface definition found

    I have an integration scenario, IDOC - BPM - IDOC. SAP will send ACC_GL_POSTING IDOC to XI, a BPM will start and then the BPM will send an IDOC to another SAP system.
    I have read instructions on weblogs:
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    /people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm
    The scenario has been successfully tested in the Test Configuration Tool. However, when I try send IDOC from the source, I received the message below in the trace.
      <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_BPE-ENTER_PLSRV">
      <Trace level="3" type="T">Processing mode is</Trace>
      <Trace level="3" type="T">created BPE proxy for message B45CB0079DFA814BAD22CD1ED64CA6AB</Trace>
      <Trace level="1" type="B" name="interface activity determination">
      <Trace level="1" type="T">Version 000</Trace>
      <Trace level="1" type="T">Message status 000</Trace>
      <Trace level="1" type="T">Interface action INIT</Trace>
      <Trace level="1" type="T">(must be INIT for a new determination)</Trace>
      <Trace level="1" type="T">start CHECK_INTERFACE</Trace>
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface ACC_GL_POSTING.ACC_GL_POSTING01*</Trace>
      <Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface ACC_GL_POSTING_abs*</Trace>
      <Trace level="1" type="T">select interface namespace http://summaryFinancial.sap.dominofoods.com</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      <Trace level="1" type="T">end CHECK_INTERFACE</Trace>
      <Trace level="1" type="T">Set interface action DEL into MAST</Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA" />
      <Trace level="3" type="T">inserted message into pipeline PE_ADAPTER</Trace>
      <Trace level="1" type="Timestamp">2007-04-30T18:32:30Z EST qRFC raised on XBQO$PE_WS91000003</Trace>
      </Trace>
    Thanks,
    Sergio

    Rajeev,
    The source system in the receiver determination is connected to R3. Other IDOCs are coming across the XI system.
    Below is some trace information in the Receiver Determination.
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Start without given receiver</Trace>
      <Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: - IP_GeneralLedger</Trace>
      <Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
      <Trace level="2" type="T">Number of Receivers:1</Trace>
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) IP_GeneralLedger ACC_GL_POSTING_abs</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: ACC_GL_POSTING_abs</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
    Thanks,
    Sergio

  • Prerequisites for Sender and Receiver FTP adapter

    Hi Experts,
    I am new to PI and configuring simple file to file scenario. I need to know the prerequsites for sender and receiver FTP adapter. Scenario is System A -> XI -> System B .
    What I want to know is:
    1> What ports need to be opened?
    2> Any service that I need to activate?
    3> Do I need to install FTP server in any of the machine?
    If I have missed something, please add.
    Br,
    Nilz

    Hi,
    1> What ports need to be opened?
    mentioned in below link as said its 21.
    2> Any service that I need to activate?
    No
    3> Do I need to install FTP server in any of the machine?
    THere are two ways by which u can pick ur file.
    1) NFS by which u can put the file on XI appplication directory and pick up ur file.
    2) FTP u have to put ur file on FYP server and XI will pick up the file from there. U can use freeware FTP and install it on ur Desktop search on goolge u will get ti FTP installtion.
    refer the below configuration requirement for FIle adapter.
    http://help.sap.com/saphelp_nw04/helpdata/en/69/a6fb3fea9df028e10000000a1550b0/frameset.htm
    ALso refer the end to end file to file scenario.
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/flatFILETOFLATFILE&
    chirag

  • Reg:IDOC Sender side settings

    Dear All,
    My scenario is IDOCPIMDM
    I have created all the basic ALE settings and they are,
    SAP R/3:
    1)RFC Destination (SM59)
    2)Logical system
    2)Port (We21)
    3)Partner Profile (WE20) name same as logical system
    SAP XI:
    1) RFC Destination (SM59)
    2) Create Port (IDX1)
    3) Load Meta Data for IDOC (IDX2) 
    In Integration Directory,Adapter-Specific identifiers,its shows the logical system that was created in R/3 server.
    Could anyone suggest me on the following queries,
    1)Whether I have to create anymore steps other than this.
    2)Should I need to create Logical system in PI
    3)Should I need to create a distribution model.
    4)What are the details ,I should enter in sender/receiver details ,while we use WE19 transaction code for triggering the idoc.
    Thanks in Advance,
    Lavanya.B

    Hi Lavanya,
    The steps are the standard steps.
    I hope it should work.
    In PI, you need to create on LS (Business Service) or Business System.
    If you are creating Business Service, it would be mapped via SLD otherwise the Business service needs to be mapped to the indoc(Go to Business Service--> Edit to add Outbound interface as Idoc name)
    Regarding Triggering Idoc,
    You need to provide the sender and receiver details
      Receiver Port
      Receiver Partner no
      Partner Type
    Sender Port  
    Sender Partner no
    Part type
    Hope this helps you.
    Regards,
    Sushama

  • XI3 SOAP sender and Receiver

    Hi
    I am stuck with a connecting to scenarios using SOAP channel. In short there is one business scenario that based on some conditions must start other scenarios (each one built around one business process). I am trying to send asynchronous SOAP message within the same XI and treat it as a External XI system to start another Business Scenario (using XI adapter does not work as the system discovers the message as being in a loop).
    Everything would be fine if there would be 1 target scenarios but I have 1:n. For asyncronous transport I have defined different Message Interfaces to be used for on each case. So XI should determine the right business process based on the message interface that uses the communication channel.
    So I have configured a SOAP sender and a receiver channel. As I understood from SOAP adapter FAQ I checked "Use Encoded Headers" and "Use Query String" for both - sender and receiver channel. And ofcourse receiver channel is pointed to http://:/XISOAPAdapter/MessageServlet?channel=:{system name}:{receiver channel name} but when I start the initiating scenario the asyncronous message is sent of but nobody is catching it.
    In RWB Message monitoring / adapter engine I found the the message receives an exeception:
    SOAP: response message contains an error XIServer/UNKNOWN/ModuleUnknownException -
    com.sap.aii.af.mp.module.ModuleException: either no channelID
    specified or no channel found for the specified party, service, and channel name,
    MessageServlet(Version $Id: //tc/aii/30_REL/src/_adapters
    /_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#15 $) at
    com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:427) at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
    javax.servlet.http.HttpServlet.service(HttpServlet.java:853) 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:266) at
    com.sap.engine.services.httpserver.server.RequestAnalizer....
    startServlet(RequestAnalizer.java:387) at
    com.sap.engine.services.httpserver.server.RequestAnalizer....
    startServlet(RequestAnalizer.java:365) at
    com.sap.engine.services.httpserver.server.RequestAnalizer....
    invokeWebContainer(RequestAnalizer.java:944) at
    com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at
    com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at
    com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160) 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)
    Any ideas... how to make XI to send SOAP messages so that the same XI system would be able to pick them up?
    Or what have I done wrong?
    Best wishes,
    Heiko

    hi,
    What is the format that u are using for the sender URL....The error message you are getting either because the names that you have mentioned in the sender URL are wrong or the URl format itslef is wrong.....if the format is the one that you have mentioned in the first post then it is not the desired format.
    Use the following format to create the URL to send the request:
    http://<servernameORserverIPaddress>:<portNumber>/XISOAPAdapter/MessageServlet?channel=:<senderservice>:<snederCCname>&version=3.0&Sender.Service=<senderservice>&Interface=<IRnamespace>%5E<senderMI>
    Replace
    with
    & amp;
    (no space inbetween the two words) in the above URL.
    How to configure SOAP communication channels (sender and receiver) so that two XI instances could communicate and (more important) use different message interfaces on the same channel?
    While creating a Receiver communication channel there is no need to specify the interface name and hence it can be used in different scenarios....however a sender communication needs the sender interface to be specified (as in SAP XI.....not in SAP PI).....so a sender channel can be used in different scenarios but with only the same interface.....
    Regards,
    Abhishek
    Edited by: abhishek salvi on Feb 17, 2009 2:50 PM

  • Message protocol is different for sender and receiver JDBC

    In File adapter the message protocol can be either FTP or NFS for both sender as well as receiver. but for JDBC adapter the message protocol is JDBC and for receiver adapter the message protocol is XML SQL Format or native sql string only. Why this is different ? Why cant we use JDBC as message protocol for receiver also ?
    I thought JDBC is the message protocol for JDBC adapters irrespective of whether they are sender or receiver. Can someone throw light on this ?

    Hi,
    You can find more about JDBC scenario at following links:
    Configuring the Sender JDBC Adapter
    [http://help.sap.com/saphelp_nw04/helpdata/en/7e/5df96381ec72468a00815dd80f8b63/content.htm|http://help.sap.com/]
    [http://help.sap.com/saphelp_nw04/helpdata/en/1d/756b3c0d592c7fe10000000a11405a/content.htm|http://help.sap.com]
    Configuring the Receiver JDBC Adapter
    [http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/676b3c255b1475e10000000a114084/content.htm|http://help.sap.com]
    [http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm|http://help.sap.com]
    [https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6d36d51d-0b01-0010-b3aa-9cb313b63cf4|https://help.sap.com]
    Regards,

  • Code to retrive the sender and receiver interface names using custome adapter module

    Hello Team,
    I want to develop an custom adapter module which could retrieve the names of the sender and receiver interfaces of the scenario and for that i am trying to use com.sap.aii.af.service.administration.api.monitoring.ProcessContextFactory.ParamSet but i don't know whether this API will support or not and also i don't know how to develop the code using this API so please suggest me some code for it so that i could retrieve the names.
    Thanks you all in advance.
    Regards,
    Avinash.   

    Hi,
    Just ASMA setting will do the needful. Are you planning to rename your target file name. If yes then only you will require UDF.
    Update: Since your directory name will be taken from source file name then you have to use mapping for this, else it will not be possible.
    I don't know if creating a new module for this will help you solve the issue, but in that case rather creating adapter module, mapping will be easier.
    Regards,
    Sarvesh
    Edited by: Sarvesh Singh on Dec 7, 2009 3:04 PM

  • Error: no interface action for sender or receiver found

    Hello,
    I have configured a asynchronous RFC to JDBC scenario.
    When i try to execute the end to end scenario , the message in SXMB_MONI is with a green flag(scheduled)  and queue status is yellow and when i double the message , the trace shows following message:
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Inbound Message
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
      <Trace level="1" type="T">Work Process ID: 25711</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = HXD</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2010-05-24T12:23:09Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 3CA00D0C20460CD10B3CA18E3C804118</Trace>
      <Trace level="1" type="T">PLNAME = RECEIVER</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
      <Trace level="1" type="T">Queue name : XBTR0004</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTR0004</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">--start determination of sender interface action</Trace>
      <Trace level="1" type="T">select interface</Trace>
      <Trace level="1" type="T">select interface namespace</Trace>
      <Trace level="1" type="T">--start determination of receiver interface action</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface Z_SD_HP_SALESORG</Trace>
      <Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:rfc:functions</Trace>
      <Trace level="1" type="T">--no interface action for sender or receiver found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      </SAP:Trace>
    The pipeline steps on the left hand side in sxmb_moni shows only inbound Message i.e remaining steps are not executed.
    When i try the execute message by directly sending message from Runtime Workbench , the scenario is executed successfully.
    Please help.
    Thanks & Regards,
    Loveena

    Hello,
    The problem was with the Client. Our Xi is running on Client 200 wheras at runtime it was picking up the default client 001.
    So after changing the default Client 001 to 200.
    The scenario was working fine.
    But from the third time onwards again it is taking the default Client and I am facing the issue.
    I guess it is some Cache problem. Can anybody tell me how to refresh the cache.
    Thanks ,
    Loveena

Maybe you are looking for