HTTP Return Response for Outbound Scenario

Hi,
I am working on a scenario, where the sender is sending a HTTP request with SOAP envelope.
I have configured the SOAP adapter for this. And my service interface is setup as ASYNCHRONUS.
However the sender want a standrad HTTP respone in return for the request.
My guess is making the Service Interface as SYNCHRONUS would not resolve the issue.
I think this can be done though BPM.
Is this possible without BPM?? But in our landscape we do not follow BPM.
So is there any way to do this?
Thanks
Sanjaya

Will they automatically they get a resonse code of 200 if the request reaches XI in case of the asynchronus scenario?
yes...remember that http 200 OK is an indication that the message was passed to XI/ PI.....it is not an indication that the message is successfully processed by XI/ PI
http://help.sap.com/saphelp_nw04/helpdata/en/5e/164442c1a1c353e10000000a1550b0/content.htm
from above help section:
If the SOAP client then receives an empty SOAP message in HTTP 200 as a response, this means that the message has been
successfully persisted and will be processed exactly once.
Regards,
Abhishek.

Similar Messages

  • PO 7.4: NW BPM: HTTP Error response for SOAP request or invalid content-type.HTTP 200 OK

    Hi Experts
    I am trying to call NW BPM scenario(File to BPM) from PI, and using below adapter config.
    I am getting below error.
    Failed to call the endpoint: Error in call over HTTP: HTTP 200 OK
    SOAP: Call failed: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
    SOAP: Error occurred: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
    MP: exception caught with cause com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
    Transmitting the message to endpoint <local> using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.; HTTP 200 OK
    Any idea how to fix this issue?
    Thanks,
    Sandeep Maurya.

    Hi Sandeep,
    Test the URL from your browser and check the proxy settings as well.
    Refer the below links
    SOAP: call failed: java.io.IOException: invalid content type for SOAP: TEXT
    SOAP: Call failed: java.io.IOException: Failed to get the input stream from socket: java.net.SocketException: Connection…
    Regards
    Bhargava Krishna

  • SOAP Receiver Error: HTTP Error response for SOAP Request

    Hi gurus,
    I'm facing a weird error in File --> PI 7.31 java only --> soap receiver proxy.
    The other interfaces runs well. just one get the the following error:
    Exception caught by adapter framework: java.io.IOException: Error receiving or parsing request message: java.io.IOException: HTTP Error response for SOAP request or invalid content-type.
    I check the payload and test in the inbound proxy. on error.
    Any hints?
    Thanks a lot!
    regards
    Christine

    Hello Christine,
    I faced the same issue,
    You can use the beans below to overcome the error.
    And charset should be utf-8

  • AIF Value mapping for outbound scenario

    Hello All,
    Is there any possibility of using same value mapping which is defined for Inbound scenario can be reused for outbound scenario as well ?
    Since, AIF value mapping can be defined based on Sending system but there is no option of creating value mapping pair between sending system and receiving system (similar to SAP PI value mapping) , is it only defined to use for Inbound scenarios ?
    Thanks & Regards,
    Dijesh Tanna

    Michael
    -->>>>you cannot have the same target value for two source values ?
    What does this mean? Can't we have If name =  A1, then value in the target should be  Sales consultant
    and if name =  A2 then value in the target should be  sales consultant?
    My question was :
    If name = A1, then value in the target should be  sales consultant
    If surname = A1, then value in the target should be purchase consultant
    In the same graphical message mapping, can this be achieved using value mapping?
    Thanks

  • Choosing the Return code for a scenario

    Hi,
    I execute an ODI scenario "AAA" from Unix with the command startscen.sh
    Can I control the return code of called screnario?
    IN the scenario "AAA" (=package) i have different path with ko/ok. I would like to choose a specific return code for each ko path. Is it possible ?
    Thank you very much.
    Best regards,

    How you creating this file? Why you couldn't create without enter?
    But, however, see solution in that case:
    File 1.sql:
    select 1 from dual;File 2.sql:
    select 2/0 from dual;File 3.sql:
    select 3 from dual;File exec_sql.sql:
    WHENEVER SQLERROR EXIT
    @&1
    @&2
    @&3And you need to generate file as this "test.sql":
    define f1 = 1.sql
    define f2 = 2.sql
    define f3 = 3.sql
    @exec_sql &f1 &f2 &f3Regards,
    Malakshinov Sayan

  • Please help: DataInputStream doesn't return response for remote device

    Hi all,
    Please advise what is my mistake.
    I am about to send a command to and get respond from my embedded kit (Arduino Wiznet Wifi Kit)
    I can send command and get respond through a Telnet.
    But i can only send command but not getting respond if i am about to write a java program to do the same thing with socket programming.
    Below is my code, please advise for my mistake.
    Many thanks!
    public static void startTCPCommunication(String ip) throws UnknownHostException, IOException{
         InetAddress thoseIp = InetAddress.getByName(ip);
         // IO streams
         DataOutputStream toServer;
         DataInputStream fromServer;
         String entered=""; // Declare & initialize a String to hold input.
         Scanner input=new Scanner(System.in); // Decl. & init. a Scanner.
         try {
              System.out.println("Socket created");
              Socket socket = new Socket(ip, 5000);
              // Create an input stream to receive data from the server
              fromServer = new DataInputStream(socket.getInputStream());
              // Create an output stream to send data to the server
              toServer = new DataOutputStream(socket.getOutputStream());
              while(true){
                   System.out.println("Please enter : ");
                   entered=input.nextLine(); // Get what the user types.
                   // Then say something trollish and use their name.
                   System.out.println("You have entered : " + entered + "!");
                   // Send the command to the server
                   toServer.writeUTF(entered);
                   System.out.println("Done with Send");
    // Get the response from server
                   String response = fromServer.readUTF();
                   System.out.println("Retruned : " + response);
         catch (IOException ex) {
         System.out.println("Unable to create socket.");
    The returned result only reaches System.out.println("Done with Send");
    The function stucked and not going to loop for second time.
    Please advise how can i modify my code and pin point my mistake please.
    Thanks a lot!

                       // Send the command to the server
                       toServer.writeUTF(entered);
                       System.out.println("Done with Send");
    // Get the response from server
                       String response = fromServer.readUTF();
                       System.out.println("Retruned : " + response);Check the Javadoc. writeUTF() doesn't send anything a Telnet server will understand, and a Telnet doesn't send anything that readUTF() will understand. They only understand each other. Use write(), and append a newline.

  • Facing problem for inserting the  RFC return response in JDBC

    Hi
    Can any one  share views for resulting my problem,
    This is my scenrio(JDBC>RFC>JDBC) logic follows like this:
    Design:
    1. MT--X(request from JDBC(A))
    2. MT--Y(Response to JDBC(A))
    3. Defined Outbound Sync MI(Z) and given request as 'X' and response as 'Y'
    4. Imported BAPI--B
    5. Done MM between X and B-->request mapping(Zmap1)
    6. Done MM between B.Response and Y--->response mapping(Zmap2)
    7. Defined the IM between Z and B
        a. Zmap1 given as request
        3. Zmap2 given as response
    And according to that i have confgured CCs,SA,RA,RD,ID. 
    It seems to be working fine..request map posting data properly in BAPI and also getting response as payload only, but it is not updating in JDBC column, which i mapped as response!it seems to be everry thing is ok..but i dint understand why it is not updating the return response in JDBC side?
    Note: Here i'm not using BPM, without BPM i made synchronous.
    In SxMB_MONI ..i'm getting response as E or S based on rfc return structure.
    Regards
    Rambarki

    Hi,
    I think there is a mistake in your messaage type to insert into JDBC. The format should be,
    <MT>
      <statement>
         <test action="insert">
              <table> </table>
         </test>
         <access>
              <row1>  </row1>
              <row2>  </row2>
         </access>
      </statement>
    </MT>
    Your action is an attribute of <test>.
    Likewise in your case, you Message should be something like,
    <root>
         <statement>
              <Invoice action="insert">
              <table> nameoftable <table>
              <access>
                   <f1> </f1>
                   <f2>     </f2>
              </access>
         </statement>
    </root>
    Check out these links on the various options avaiable for the JDBC adapetr and how the action attribute can be used,
    http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
    Also, check this simple file to jdbc blog for your reference on JDBS adapter,
    /people/sap.user72/blog/2005/06/01/file-to-jdbc-adapter-using-sap-xi-30
    Hope this clarifies and solves a part of your problem,
    Regards,
    Bhavesh

  • Exchange 2007 Active sync error An HTTP 500 response was returned from Unknown.

    I tested using Microsoft Remote connectivity analyzer tool and getting following error. Please help me to fix the issue
    An ActiveSync session is being attempted with the server.
    Errors were encountered while testing the Exchange ActiveSync session.
    Additional Details
    Elapsed Time: 394 ms.
    Test Steps
    Attempting to send the OPTIONS command to the server.
    Testing of the OPTIONS command failed. For more information, see Additional Details.
    Additional Details
    An HTTP 500 response was returned from Unknown. Headers received: Content-Length: 3745 Cache-Control: private Content-Type: text/html; charset=utf-8 Date: Wed, 05 Mar 2014 18:09:36 GMT Server: Microsoft-IIS/6.0 X-AspNet-Version: 2.0.50727 X-Powered-By:
    ASP.NET HTTP Response Headers: Content-Length: 3745 Cache-Control: private Content-Type: text/html; charset=utf-8 Date: Wed, 05 Mar 2014 18:09:36 GMT Server: Microsoft-IIS/6.0 X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET
    Elapsed Time: 394 ms.

    Hi Shadab,
    I have recreated the active sync virtual directory but didnt fix the issue. I have set the logging level for active sync to high and getting below event logs in apps log
    Event Type: Warning
    Event Source: ASP.NET 2.0.50727.0
    Event Category: Web Event 
    Event ID: 1310
    Date: 08/03/2014
    Time: 17:50:29
    User: N/A
    Computer: HP-01
    Description:
    Event code: 3008 
    Event message: A configuration error has occurred. 
    Event time: 08/03/2014 17:50:29 
    Event time (UTC): 08/03/2014 17:50:29 
    Event ID: 5ff3055057084fb49978442a86866e50 
    Event sequence: 15 
    Event occurrence: 14 
    Event detail code: 0 
    Application information: 
        Application domain: /LM/W3SVC/1/ROOT/Microsoft-Server-ActiveSync-1-130384798306406250 
        Trust level: Full 
        Application Virtual Path: /Microsoft-Server-ActiveSync 
        Application Path: C:\Program Files\Microsoft\Exchange Server\ClientAccess\sync\ 
        Machine name: HP-01 
    Process information: 
        Process ID: 1972 
        Process name: w3wp.exe 
        Account name: NT AUTHORITY\SYSTEM 
    Exception information: 
        Exception type: ConfigurationErrorsException 
        Exception message: Could not load file or assembly 'Microsoft.Exchange.Clients.Owa' or one of its dependencies. The system cannot find the file specified. (C:\Program Files\Microsoft\Exchange Server\ClientAccess\Owa\web.config line 64) (C:\Program
    Files\Microsoft\Exchange Server\ClientAccess\Owa\web.config line 64) 
    Request information: 
        Request URL: https://mail.itech-it.co.uk:443/Microsoft-Server-ActiveSync/default.eas 
        Request path: /Microsoft-Server-ActiveSync/default.eas 
        User host address: 157.56.138.141 
        User:  
        Is authenticated: False 
        Authentication Type:  
        Thread account name: NT AUTHORITY\SYSTEM 
    Thread information: 
        Thread ID: 8 
        Thread account name: NT AUTHORITY\SYSTEM 
        Is impersonating: False 
        Stack trace:    at System.Web.Configuration.HttpModuleAction.get_Entry()
       at System.Web.Configuration.HttpModulesSection.CreateModules()
       at System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers)
       at System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context)
       at System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context)
       at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
    Custom event details: 
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Thanks!
    Rajeesh

  • Response for Async to Async scenario

    Hi Experts,
    Is it possible to get response for Async to Async scenario?
    For example: Response for File to File sceanrio.
    Regards
    Sara

    Thanks for the info.
    For the webservice to JDBC scenario, I have to use two way Asynchronous business process. Is it possible?
    Scenario : Webservice to JDBC -> Async Call
                    JDBC to Webservice -> Async Call
    I have already done with two way Synchronous. Here I would like to know about only Async call. Please provide your suggestions
    Regards
    Sara
    Edited by: Sara D on Dec 18, 2007 7:55 AM

  • How to provide credentials for outbound HTTP connection

    Hi all,
    My outbound request requires basic authentication How to provide credentials within xsjs for outbound request.
    My .xshttpdest file has authType=basic:
    host = "host";
    port = 80;
    description = "decription";
    pathPrefix = "/geoserver/";
    authType = basic;
    useProxy = false;
    proxyHost = "proxy";
    proxyPort = 8080;
    timeout = 0;
    Correspondent xsjs class create request:
    var request = new $.net.http.Request($.net.http.GET, "");
    Is any possibility to provide request with credentials?
    Thanks.
    Slava

    You provide credentials by configuring for the HTTP destination via the XSAdmin tool. Directly supplying credentials in the XSJS code itself would not be sure.

  • Input parameters for BAPI_GOODSMVT_CREATE --MIGO--GR for Outbound Delivery

    Hi Friends,
      We have to create a Goods Receipt against an Outbound Delivery ( movement type "101" ) using the BAPI <b>BAPI_GOODSMVT_CREATE</b>.
    In online the user is using <b>MIGO</b> transaction for the same. There he will choose the GOODS RECEIPT for OUTBOUND DELIVERY and enters the delivery number. The movement type "101" is used.
      Could you please tell me the GM code and the required fields to be passed for the above scenario.
    I have gone through the example program in the link...
    http://www.sap-img.com/abap/bapi-goodsmvt-create-to-post-goods-movement.htm
    <b>but unable to find how to use this BAPI for simulating MIGO transaction.</b>
    <b>The fields available are with us are...</b>
    Delivery. No. --- Doc. Date - Posting Date-Quantity-Storage Location-
    Reason for movement-External qty-External qty unit-Goods recipient-Excise Selection
    Are these fields sufficient for doing MIGO with this BAPI or do we require more fields???
    Thanks and Regards,
    Bharat

    see the following code. it may be useful.
      LOOP AT I_TAB.
          count = sy-tabix.
          SELECT SINGLE * FROM ZMM_GR_UPLOAD1
                                    WHERE SOLOMON_GR = I_TAB-SOLOMON_GR AND
                                    SOLOMON_GRDAT = I_TAB-SOLOMON_GRDAT.
          IF SY-SUBRC = 0.
            I_TAB-FLAG = 'C'.
            modify i_tab index count.
            concatenate 'File Name : ' name into i_msg1.
            append i_msg1.
            CONCATENATE 'ERROR  PO : ' I_TAB-SOL_PONO
                '  WAS ALREADY UPLOADED' INTO I_MSG1.
            APPEND I_MSG1.
            CLEAR I_TAB-FLAG.
            CONTINUE.
          ELSE.
            REFRESH I_ITEMS.
            CLEAR I_ITEMS.
            CONCATENATE I_MAIN-SOLOMON_GRDAT+4(4)
                        I_MAIN-SOLOMON_GRDAT+2(2)
                        I_MAIN-SOLOMON_GRDAT+0(2) INTO G_DATE.
            gmhead-pstng_date = G_DATE.
            gmhead-doc_date = sy-datum.
            gmhead-pr_uname = sy-uname.
    "01 - MB01 - Goods Receipts for Purchase Order
            gmcode-gm_code = '01'.
            refresh itab.
            clear itab.
            SORT I_MAIN BY SOLOMON_GR.
            LOOP AT I_MAIN WHERE SOLOMON_GR = I_TAB-SOLOMON_GR.
              itab-move_type  = '101'.
              itab-mvt_ind    = 'B'.
              itab-plant      = I_MAIN-WERKS.
              itab-material   = I_MAIN-MATNR.
              itab-entry_qnt  = I_MAIN-ERFMG.
             itab-stge_loc   = 'OMR1'.
    itab-move_stloc = pcitab-recv_loc.
             itab-REF_DOC = 'exnum123'.
              itab-NO_MORE_GR = 'X'.
              itab-WITHDRAWN = ''.
              itab-stge_loc   = I_MAIN-LGOBE.
              itab-po_number  = I_MAIN-EBELN.
              itab-po_item    = I_MAIN-EBELP.
              itab-unload_pt  = I_MAIN-ABLAD2.
              append itab.
            ENDLOOP.
            if not itab[] is initial.
              call function 'BAPI_GOODSMVT_CREATE'
               exporting
                   goodsmvt_header             = gmhead
                   goodsmvt_code               = gmcode
                 *   TESTRUN                     = ' '
              IMPORTING
                  goodsmvt_headret            = mthead
             *   MATERIALDOCUMENT            =
      MATDOCUMENTYEAR             =
               tables
                 goodsmvt_item               = itab
      GOODSMVT_SERIALNUMBER       =
                return                      = errmsg.
              clear errflag.
              loop at errmsg.
                if sy-tabix = 1.
                  concatenate 'File Name : ' name into i_msg1.
                  append i_msg1.
                  concatenate 'Sol PO : ' I_TAB-SOL_PONO ' '
                   I_TAB-SOL_PODT into i_msg1.
                  append i_msg1.
                endif.
                if errmsg-type eq 'E'.
                  write:/'Error in function', errmsg-message.
                  errflag = 'X'.
                else.
                  write:/ errmsg-message.
                endif.
                move errmsg-message to i_msg1.
                append i_msg1.
              endloop.
              if errflag is initial.
                CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
              EXPORTING
                WAIT          =
              IMPORTING
                RETURN        =
               commit work and wait.
                if sy-subrc ne 0.
                  write:/ 'Error in updating'.
                  exit.
                else.
                  concatenate 'File Name : ' name into i_msg1.
                  append i_msg1.
                  concatenate 'Sol PO : ' I_TAB-SOL_PONO ' '
                   I_TAB-SOL_PODT into i_msg1.
                  append i_msg1.
                  write:/ mthead-mat_doc, mthead-doc_year.
                  ZMM_GR_UPLOAD1-SOLOMON_GR = I_TAB-SOLOMON_GR.
                 CONCATENATE I_TAB-SOLOMON_GRDAT+4(4)
                       I_TAB-SOLOMON_GRDAT+2(2)
                       I_TAB-SOLOMON_GRDAT+0(2) INTO
                        ZMM_GR_UPLOAD1-SOLOMON_GRDAT.
                  ZMM_GR_UPLOAD1-SOLOMON_GRDAT = I_TAB-SOLOMON_GRDAT.
                  INSERT ZMM_GR_UPLOAD1.
                  COMMIT WORK.
                  I_TAB-FLAG = 'C'.
                  MODIFY I_TAB INDEX COUNT.
                  CONCATENATE mthead-mat_doc  mthead-doc_year
                             into i_msg1.
                  append i_msg1.
                 perform upd_sta.
                endif.
              endif.
            endif.
          ENDIF.
        ENDLOOP.

  • Recorded for outbound processing in SXMB_MONI???

    Hi XI friends,
    in my file to abap proxy,
    in sxmb_moni i am getting message like "recorded for outbound processing" and Q status is stopped.
    please help me.
    thanks and regards
    ram

    Hi friends..
    Trace is like this
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Call Adapter --> <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
    <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
    <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
    <Trace level="1" type="T">Sender party external = </Trace>
    <Trace level="1" type="T">Sender party normalized = </Trace>
    <Trace level="1" type="T">Party normalization: receiver </Trace>
    <Trace level="1" type="T">Receiver scheme external = </Trace>
    <Trace level="1" type="T">Receiver agency external = </Trace>
    <Trace level="1" type="T">Receiver party external = </Trace>
    <Trace level="1" type="T">Receiver party normalized = </Trace>
    <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
    <Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
    <Trace level="2" type="T">Host = dcexi0605.aaaa.com:8030</Trace>
    <Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
    <Trace level="2" type="T">Remote address = 10.161.20.123</Trace>
    <Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
    <Trace level="3" type="T">Getting type of XMB... </Trace>
    <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
    </Trace>
    <Trace level="2" type="T">XMB kind = CENTRAL</Trace>
    <Trace level="3" type="T">Start pipeline found </Trace>
    <Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
    <Trace level="3" type="T">No triggers found. OK. </Trace>
    </Trace>
    <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="3" type="T">system-ID = BGX</Trace>
    <Trace level="3" type="T">client = 100</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = XIAFUSERBGX</Trace>
    <Trace level="1" type="Timestamp">2007-02-28T10:29:00Z 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><!-- ************************************ -->
    <Trace level="1" type="T">Message-GUID = D5951F70C64311DBB7213A3BFF6537A2</Trace>
    <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
    <Trace level="1" type="T">QOS = EO</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">QOS = EO</Trace>
    <Trace level="3" type="T">Message-GUID = D5951F70C64311DBB7213A3BFF6537A2</Trace>
    <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
    <Trace level="3" type="T">External PLID = CENTRAL</Trace>
    <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
    <Trace level="3" type="T">Generate prefixed queue name </Trace>
    <Trace level="1" type="T">Queue name : XBTI0006</Trace>
    <Trace level="1" type="T">Generated prefixed queue name = XBTI0006</Trace>
    <Trace level="1" type="T">Schedule message in qRFC environment </Trace>
    <Trace level="3" type="T">Setup qRFC Scheduler </Trace>
    <Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
    <Trace level="3" type="T">Call qRFC .... MsgGuid = D5951F70C64311DBB7213A3BFF6537A2</Trace>
    <Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
    <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
    <Trace level="3" type="T">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="3" type="T">Version number = 000</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Persisting message Status = 001</Trace>
    <Trace level="3" type="T">Message version 000</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
    <Trace level="3" type="T">Trace object available again now. OK. </Trace>
    <Trace level="3" type="T">Message was read from persist layer. OK. </Trace>
    <Trace level="3" type="T">Message properties in XMB object were setup. OK. </Trace>
    <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read </Trace>
    <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
    </Trace>
    <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
    <Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
    <Trace level="2" type="T">Increment log sequence to 001</Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
    <Trace level="3" type="T">system-ID = BGX</Trace>
    <Trace level="3" type="T">client = 100</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = XIAFUSERBGX</Trace>
    <Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET  </Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
    <Trace level="3" type="T">External PLID = CENTRAL</Trace>
    <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline attributes </Trace>
    <Trace level="3" type="T">PID        = SAP_CENTRAL</Trace>
    <Trace level="3" type="T">ENABLE     = 1</Trace>
    <Trace level="3" type="T">TRACELEVEL = 0</Trace>
    <Trace level="3" type="T">EXEMODE    = A</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline elements </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0001</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0002</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0003</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0004</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0007</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0008</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = =SWITCH=</Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0009</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_RESPONSE</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    <Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">ADRESSMOD  = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_RD_PLSRV</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
    <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:  - SAP_ERP_aaaa_PPR </Trace>
    <Trace level="2" type="T">No Receiver found behaviour: 0  </Trace>
    <Trace level="2" type="T">Number of Receivers:1  </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call </Trace>
    <Trace level="3" type="T">Message-Version = 001</Trace>
    <Trace level="3" type="T">Message version 001</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    <Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">ADRESSMOD  = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_ID_PLSRV</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
    <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)  SAP_ERP_aaaa_PPR MI_IN_S_StockAdj </Trace>
    <Trace level="2" type="T">...valid InbIf without Condition: MI_IN_S_StockAdj </Trace>
    <Trace level="2" type="T">Number of receiving Interfaces:1  </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call </Trace>
    <Trace level="3" type="T">Message-Version = 002</Trace>
    <Trace level="3" type="T">Message version 002</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT"></Trace><!-- ************************************ -->
    <Trace level="1" type="Timestamp">2007-02-28T10:29:00Z CET Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">ADRESSMOD  = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="2" type="T">got property produced by receiver determination </Trace>
    <Trace level="1" type="T">number of receivers: 1 </Trace>
    <Trace level="1" type="T">Single-receiver split case </Trace>
    <Trace level="1" type="T">Post-split internal queue name = XBTOG___0002</Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="T">Persisting single message for post-split handling </Trace>
    <Trace level="1" type="T"> </Trace>
    <Trace level="1" type="T">Going to persist message + call qRFC now... </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">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><!-- ************************************ -->
    <Trace level="3" type="T">Persisting message Status = 012</Trace>
    <Trace level="3" type="T">Message version 003</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Trace object available again now. OK. </Trace>
    <Trace level="3" type="T">manual Restart Flag X</Trace>
    <Trace level="3" type="T">Message Guid D5951F70C64311DBB7213A3BFF6537A2</Trace>
    <Trace level="3" type="T">Version 000</Trace>
    <Trace level="3" type="T">Pipeline ID CENTRAL</Trace>
    <Trace level="3" type="T">EOIO Force I</Trace>
    <Trace level="3" type="T">Restart Trace </Trace>
    <Trace level="3" type="T">Message was read from persist layer. OK. </Trace>
    <Trace level="3" type="T">Message properties in XMB object were setup. OK. </Trace>
    <Trace level="3" type="T">Error of the prevous version: </Trace>
    <Trace level="3" type="T">Area </Trace>
    <Trace level="3" type="T">Error ID </Trace>
    <Trace level="3" type="T">Restart of Queue? </Trace>
    <Trace level="1" type="T">Persisting message with status ManualRestart, version: 003</Trace>
    <Trace level="1" type="T">*************************************** </Trace>
    <Trace level="1" type="T">*   Setup of qRFC Scheduler OK!!! </Trace>
    <Trace level="1" type="T">*************************************** </Trace>
    <Trace level="3" type="T">Call qRFC .... MsgGuid = D5951F70C64311DBB7213A3BFF6537A2</Trace>
    <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
    <Trace level="3" type="T">OK. </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Persisting message Status = 016</Trace>
    <Trace level="3" type="T">Message version 005</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Trace object available again now. OK. </Trace>
    <Trace level="3" type="T">manual Restart Flag X</Trace>
    <Trace level="3" type="T">Message Guid D5951F70C64311DBB7213A3BFF6537A2</Trace>
    <Trace level="3" type="T">Version 005</Trace>
    <Trace level="3" type="T">Pipeline ID CENTRAL</Trace>
    <Trace level="3" type="T">EOIO Force I</Trace>
    <Trace level="3" type="T">Restart Trace </Trace>
    <Trace level="3" type="T">Message was read from persist layer. OK. </Trace>
    <Trace level="3" type="T">Message properties in XMB object were setup. OK. </Trace>
    <Trace level="3" type="T">Error of the prevous version: </Trace>
    <Trace level="3" type="T">Area </Trace>
    <Trace level="3" type="T">Error ID </Trace>
    <Trace level="3" type="T">Restart of Queue? </Trace>
    <Trace level="1" type="T">Persisting message with status ManualRestart, version: 005</Trace>
    <Trace level="1" type="T">*************************************** </Trace>
    <Trace level="1" type="T">*   Setup of qRFC Scheduler OK!!! </Trace>
    <Trace level="1" type="T">*************************************** </Trace>
    <Trace level="3" type="T">Call qRFC .... MsgGuid = D5951F70C64311DBB7213A3BFF6537A2</Trace>
    <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
    <Trace level="3" type="T">OK. </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Persisting message Status = 016</Trace>
    <Trace level="3" type="T">Message version 006</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
    <Trace level="3" type="T">Trace object available again now. OK. </Trace>
    <Trace level="3" type="T">Message was read from persist layer. OK. </Trace>
    <Trace level="3" type="T">Message properties in XMB object were setup. OK. </Trace>
    <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read </Trace>
    <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
    </Trace>
    <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
    <Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">message version successfully read from persist version= 006</Trace>
    <Trace level="2" type="T">Increment log sequence to 007</Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
    <Trace level="3" type="T">system-ID = BGX</Trace>
    <Trace level="3" type="T">client = 100</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = saa_aaa</Trace>
    <Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET  </Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
    <Trace level="3" type="T">External PLID = CENTRAL</Trace>
    <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline attributes </Trace>
    <Trace level="3" type="T">PID        = SAP_CENTRAL</Trace>
    <Trace level="3" type="T">ENABLE     = 1</Trace>
    <Trace level="3" type="T">TRACELEVEL = 0</Trace>
    <Trace level="3" type="T">EXEMODE    = A</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline elements </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0001</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0002</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_INTERFACE_DETERMINATION</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0003</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0004</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0007</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0008</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = =SWITCH=</Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">ELEMPOS    = 0009</Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_RESPONSE</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
    <Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_MAPPING_REQUEST</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">ADRESSMOD  = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_MAPPING_XMS_PLSRV3</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
    <Trace level="2" type="T">......attachment XI_Context not found </Trace>
    <Trace level="3" type="T">Mapping is already determined in the interface determination </Trace>
    <Trace level="3" type="T">Object ID of Interface Mapping 7344EE703ACE3FE5AB19EDA1D3F48BBC </Trace>
    <Trace level="3" type="T">Version ID of Interface Mapping B2CF8EF067FF11DBA742D7830A967135 </Trace>
    <Trace level="1" type="T">Interface Mapping http://aaaa.com/xi/PROCESS/PPE/ERP_MES IM_MES_StockAdj_TO_SAP </Trace>
    <Trace level="3" type="T">Mapping Steps 1  JAVA com/sap/xi/tf/_MM_MES_StockAdj_To_SAP_ </Trace>
    <Trace level="3" type="T">Dynamic configuration is empty </Trace>
    <Trace level="2" type="T">Mode 0  </Trace>
    <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_MES_StockAdj_To_SAP_. </Trace>
    <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_MES_StockAdj_To_SAP_ </Trace>
    <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_MES_StockAdj_To_SAP_ completed. (executeStep() of com.sap.xi.tf._MM_MES_StockAdj_To_SAP_ </Trace>
    <Trace level="3" type="T">Dynamic configuration is empty </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call </Trace>
    <Trace level="3" type="T">Message-Version = 007</Trace>
    <Trace level="3" type="T">Message version 007</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
    <Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_OUTBOUND_BINDING</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = </Trace>
    <Trace level="3" type="T">ADRESSMOD  = LOCAL</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_XMS_PLSRV_OUTBINDING</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
    <Trace level="2" type="T">O U T B O U N D - B I N D I N G </Trace>
    <Trace level="2" type="T"> Cache Content is up to date </Trace>
    <Trace level="2" type="T">determine  OUTBOUND BINDING  for: </Trace>
    <Trace level="2" type="T">-BS_FTP_MES_GeneralServices </Trace>
    <Trace level="2" type="T">-SAP_ERP_aaaa_PPR </Trace>
    <Trace level="2" type="T">http://aaaa.com/xi/PROCESS/PPE/ERP_MES.MI_IN_S_StockAdj </Trace>
    <Trace level="2" type="T">Channel found:  - SAP_ERP_aaaa_PPR - CC_IN_SAP_XI_StockAdj </Trace>
    <Trace level="2" type="T">no header mapping defined </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call </Trace>
    <Trace level="3" type="T">Message-Version = 008</Trace>
    <Trace level="3" type="T">Message version 008</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER"></Trace><!-- ************************************ -->
    <Trace level="1" type="Timestamp">2007-02-28T11:28:10Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = =SWITCH=</Trace>
    <Trace level="3" type="T">ADRESSMOD  = SD</Trace>
    <Trace level="3" type="T">P_CLASS    = </Trace>
    <Trace level="3" type="T">P_IFNAME   = </Trace>
    <Trace level="3" type="T">P_METHOD   = </Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Channel for Integration Engine: XI</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV) </Trace>
    <Trace level="3" type="T">PLSRVID    = PLSRV_CALL_ADAPTER</Trace>
    <Trace level="3" type="T">PLSRVTYPE  = IENGINE</Trace>
    <Trace level="3" type="T">ADRESSMOD  = SD</Trace>
    <Trace level="3" type="T">P_CLASS    = CL_XMS_PLSRV_IE_ADAPTER</Trace>
    <Trace level="3" type="T">P_IFNAME   = IF_XMS_PLSRV</Trace>
    <Trace level="3" type="T">P_METHOD   = ENTER_PLSRV</Trace>
    <Trace level="3" type="T">FL_LOG     = </Trace>
    <Trace level="3" type="T">FL_DUMMY   = 0</Trace>
    <Trace level="3" type="T"> </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
    <Trace level="3" type="T">Channel for Integration Engine: XI</Trace>
    <Trace level="1" type="T">Sender: Header mapped to</Trace>
    <Trace level="1" type="T">Party = </Trace>
    <Trace level="1" type="T">Agency = </Trace>
    <Trace level="1" type="T">Scheme = </Trace>
    <Trace level="1" type="T">Service = BS_FTP_MES_GeneralServices</Trace>
    <Trace level="1" type="T">Receiver: Header mapped to</Trace>
    <Trace level="1" type="T">Party = </Trace>
    <Trace level="1" type="T">Agency = </Trace>
    <Trace level="1" type="T">Scheme = </Trace>
    <Trace level="1" type="T">Service = SAP_ERP_aaaa_PPR</Trace>
    <Trace level="1" type="T">Party denormalization: sender </Trace>
    <Trace level="1" type="T">Sender target scheme = </Trace>
    <Trace level="1" type="T">Sender target agency = </Trace>
    <Trace level="1" type="T">Sender party normalized = </Trace>
    <Trace level="1" type="T">Sender party external = </Trace>
    <Trace level="1" type="T">Party denormalization: receiver </Trace>
    <Trace level="1" type="T">Receiver target scheme = </Trace>
    <Trace level="1" type="T">Receiver target agency = </Trace>
    <Trace level="1" type="T">Receiver party normalized = </Trace>
    <Trace level="1" type="T">Receiver party external = </Trace>
    <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
    <Trace level="2" type="T">Addressing mode: url</Trace>
    <Trace level="3" type="T">Host = dceaaaa08.aaaa.biz</Trace>
    <Trace level="3" type="T">Port = 8010</Trace>
    <Trace level="3" type="T">Transport protocol = HTTP      1.0</Trace>
    <Trace level="3" type="T">Message protocol = </Trace>
    <Trace level="3" type="T">Path = /sap/xi/engine?type=receiver</Trace>
    <Trace level="2" type="T">Auth mode: basicSAP</Trace>
    <Trace level="3" type="T">Conversion of language from char2 to char1 EN</Trace>
    <Trace level="3" type="T">User = SAPJSF</Trace>
    <Trace level="3" type="T">Client = 400</Trace>
    <Trace level="3" type="T">Language = E</Trace>
    <Trace level="3" type="T">Creating HTTP-client </Trace>
    <Trace level="3" type="T">HTTP-client: creation finished</Trace>
    <Trace level="3" type="T">Security: Basic authentication SAP </Trace>
    <Trace level="3" type="T">Serializing message object... </Trace>
    <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
    <Trace level="3" type="T">HTTP-client: request sent</Trace>
    <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
    <Trace level="3" type="System_Error">HTTP-Client: exception during receive: HTTP_COMMUNICATION_FAILURE</Trace>
    </Trace>
    <Trace level="2" type="T">Switch back to normalized party (HTTP response)</Trace>
    <Trace level="1" type="T">Sender scheme external = </Trace>
    <Trace level="1" type="T">Sender agency external = </Trace>
    <Trace level="1" type="T">Sender party external = </Trace>
    <Trace level="1" type="T">Sender party normalized = </Trace>
    <Trace level="1" type="T">Party normalization: receiver </Trace>
    <Trace level="1" type="T">Receiver scheme external = </Trace>
    <Trace level="1" type="T">Receiver agency external = </Trace>
    <Trace level="1" type="T">Receiver party external = </Trace>
    <Trace level="1" type="T">Receiver party normalized = </Trace>
    <Trace level="2" type="T">Undo header mapping (HTTP response) </Trace>
    <Trace level="1" type="T">Sender: Header before undo of mapping</Trace>
    <Trace level="1" type="T">Party = </Trace>
    <Trace level="1" type="T">Agency = </Trace>
    <Trace level="1" type="T">Scheme = </Trace>
    <Trace level="1" type="T">Service = BS_FTP_MES_GeneralServices</Trace>
    <Trace level="1" type="T">Receiver: Header before undo of mapping</Trace>
    <Trace level="1" type="T">Party = </Trace>
    <Trace level="1" type="T">Agency = </Trace>
    <Trace level="1" type="T">Scheme = </Trace>
    <Trace level="1" type="T">Service = SAP_ERP_aaaa_PPR</Trace>
    <Trace level="2" type="T">Sender: Header after undo of mapping</Trace>
    <Trace level="2" type="T">Party = </Trace>
    <Trace level="2" type="T">Agency = </Trace>
    <Trace level="2" type="T">Scheme = </Trace>
    <Trace level="2" type="T">Service = BS_FTP_MES_GeneralServices</Trace>
    <Trace level="2" type="T">Receiver: Header before undo of mapping</Trace>
    <Trace level="2" type="T">Party = </Trace>
    <Trace level="2" type="T">Agency = </Trace>
    <Trace level="2" type="T">Scheme = </Trace>
    <Trace level="2" type="T">Service = SAP_ERP_aaaa_PPR</Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    <Trace level="3" type="T">Persisting message after plsrv call </Trace>
    <Trace level="3" type="T">Message-Version = 009</Trace>
    <Trace level="3" type="T">Message version 009</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </Trace>
    <Trace level="3" type="System_Error">Error exception return from pipeline processing! </Trace>
    <Trace level="1" type="T">Persist Message in Retry State </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    <Trace level="3" type="T">Persisting message Status = 009</Trace>
    <Trace level="3" type="T">Message version 010</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </SAP:Trace>
    please guide me..
    ram

  • Return Delivery for In-House Repair Order

    When I create an In-House Repair order in CRM and replicate it to ECC, the return delivery does contain the special stock indicator "E", hence the stock is posted to unrestricted.  This only happens with replicated orders.
    Any ideas?

    Hello Peter,
    Regarding Posting of Goods Issue for Spare Parts in SAP R/3 Materials Management,
    The data posted depends on the logistics scenario(s) that you use. The system therefore first determines the logistics scenario defined for the combination of transaction type, item category, service organization, and other relevant information required for the scenario (for example, movement type or special stock indicator in SAP R/3).
    Availability information informs you whether the service parts are currently in stock. Each service part item generates a reservation in the back end system, which can be used to trigger an early procurement process.
    To know more about the same refer the below link:
    http://help.sap.com/search/highlightContent.jsp
    http://help.sap.com/saphelp_crm50/helpdata/en/cb/f876d513c56e4e864c15517ff67e92/frameset.htm
    Hope this helps!
    Thanks and Best Regards,
    Shanthala Kudva.

  • PI alert issue for synchrounous scenarios

    Hi
    I created alerts for synchronous scenario for mapping and adapterfailures but while testing its not triggering. however alerts triggered in Alert inbox when i test via 'rsalerttes't report.
    if there is a mapping failure in request messag mapping alerts triggerring fine, but if there is a failure in response mapping alerts not triiggreing.
    can some body explain how to create alert rule for respnse message mapping failures.
    Regards,
    Rajesh

    Hi Aamir,
    Thanks for information.
    I checked in SLG1 it shows green symbol. and ALRTDISP it shows closed envelope.
    In SXMB_MONI the mesage shows red symbol.
    we are gettign below error in MONI in response SOAP Header but the alert not triggered.
    <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">PARSE_APPLICATION_DATA</SAP:Code>
      <SAP:P1>Request Message</SAP:P1>
      <SAP:P2>CX_ST_DESERIALIZATION_ERROR</SAP:P2>
      <SAP:P3>/1SAI/TXS00000000000000000035</SAP:P3>
    if there is a fialure in request message pipeline steps the alert get triggered. how to trigger alerts for failures in SOAP Header, which is happening before pipeline steps started.
    we tried No restriction option in Alert rule in RWB, but still PI is not able to trigger alert for this kind of error.
    Regards,
    Rajesh

  • Error in Outbound scenario : AE_DETAILS_GET_ERROR

    Hello Experts,
    Need your help urgently
    right now i am doing outbound scenario, in that R/3 -> XI -> Oracle.
    Here when i trigger 1 outbound IDOC then it is working fine... but when i try to send 100s of idocs at a time then half of them i getting through and half of them are going into error saying
      <?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"><b>AE_DETAILS_GET_ERROR</b></SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText><b>Error while reading from the secure store: ERROR_U: No service user password found for Adapter Engine</b></SAP:AdditionalText>
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack><b>Error while reading access data (URL, user, password) for the Adapter Engine</b></SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    When i try to restart them into the SXMB_MONI at that time they are getting through.
    I am not able to trace that y it is happening like this....
    Some of them are going into the "System Error - Manual Restart Possible" and some of them are going in to the "System Error - Restart Not Possible".
    Can anybody please help me out in this problem? I am not able to understand that y it is happening.
    Regards,
    Hetal

    Hi Hetal,
    Check ur adapterframework service username,password in the exchange profile are given correctly.
    Also check in the Business system of the XI server, please verify the URL in the pipeline.It should be:
       http://<servername>:<HTTP Port>/sap/xi/engine?type=entry.
    Regards,
    Prasanthi.

Maybe you are looking for

  • Showing Keyfigures  error for result and overall result in the Query output

    Hi All, when executing  query results show correct figures for qty & value but with ERROR  instead of uom(Unit of Measurement) & currency; Can anybody help? Rgds, C.V.

  • Photos Sync Out Of Order

    Why are the photos I sync in a different order on my ipod than the folder? I don't have the shuffle option on for slideshow settings. I renamed all photos to make sure they were alphabetized. Anyone have any thoughts?

  • Adobe plug in error

    I get an error message "no plug in" when trying to download with Adobe Reader. 

  • Can I connect a Power Mac G5 monitor to a Macbook pro?

    I still have my Power Mac G5 monitor that still works. I wanted to know if I can connect the monitor to my Macbook pro. I'm not sure what adapters, if any, I should use. Thanks in advance. Scilla

  • ORACLE 9I SQL Exam Validity

    One of my friend cleared Oracle 9i SQL paper in November 2005 and now wants to take PLSQL paper. Will the SQL exam cleared in 2005 be valid still ? Are there any timeliness within which we have to clear the papers ? to get OCA