NFS Sender - No action in SXMB_MONI

Hello,
I've created an interface using the File Adapter (NFS) and I'm able to place files into a folder using the NFS File Adapter but when I create my sender Adapter it is unable to read files.
I am not getting any attempts (error or otherwise) in SXMB_MONI.  It should be polling every 60 seconds.
All parts have been activated and the folder has wide open access for Read/Write.
Thanks,
Matt

Rajesh - The file/folder names appear to be working.  When I change them I get an error.
Sarvesh - I changed the case on one letter in the folder and immediately had an error in RWB.  Also I am looking into the possibility of a problem with file authorization after the file is written.
Aamir - I put the exact file name in the channel with no luck. I also tried both methods you suggested.
I'm really not sure what could cause this sender agreement not to find the file.  This is a UNIX system.  Is there some requirement that changes when it is a UNIX system?
Do any of these settings look wrong?
Adapter Engine:  Central Adapter Engine
Source Directory:  /usr/PI_Fileadapter/MBItest
File Name:  POX*.XML
Quality of service:  Exactly Once
Poll Interval:  60
Processing Mode:  Archive
Add Time Stamp:  Yes
Archive Directory:  /usr/PI_Fileadapter/MBItest/Archives/POX
Processing Sequence:  By Name
File type: Binary
I appreciate the assistance. 
Matt

Similar Messages

  • How to attach two files in the send mail action

    Hi experts
    I want to attach two files in the send mail action . I tried using ; as a separator but it did not work .
    Regards,
    Antonio R . Rubalcaba

    Thanks Jeremy,  
    Yes I am contemplating the another threat .  I still want to send two files because the two files have very distinct type of information .  The first one is operational and the second one is about statistics .  Of course that I can send both type of inforrmation in only one file . I just want to save time to the end user and let him select what infomation he wants to see .
    Thanks and my best wishes for you and your family ,
    Antonio

  • Make send email action open in a different tab or window

    Made text a link in a smart shape with Cp7.Due to a shortcoming in the Google Chrome browser the email client doesn't open. So, I click the back button and it goes back to the first slide of the project. I am not looking for a resolution of the Chrome browser issue (but it would be nice to have:), I am wondering if the send email action can open a new tab or window to avoid the back-arrow-to-first-slide issue.
    thanks.
    Michael

    When you say: "Click the Back button", I'm assuming you're referring to the Back button in the browser, not a button in your Captivate slide, correct?
    If so, this will happen in all browsers when playing Captivate SWFs.  Clicking the browser back button essentially reloads the page, not just the slide.

  • BLS Send Mail Action Block Requires SMTP Mail Server Mail Account

    My SMTP Mail Server does NOT require authentication.  It appears as if MII Ver 12 requires a mail account to be filled in on the BLS Send Mail Action Block.  If the mail account field is left empty the transaction fails (error - mail account cannot be blank).  Transaction works without the mail account on Ver 11.5 but Ver 12 requires the field to filled in.  Please advise whether this is a new requirement in Ver 12 or a bug that needs to be addressed.

    Hi Sam,
    What I think is, it requires one mail account to send the mail and one to receive it.
    There is no restriction on receiver that can be anyone. But the sender needs to be known that some mail has been sent from his mail account. So may be because of this the added authentification is required. It will use that mail account to send the mails.

  • Send mail Action : Body

    Hi ,
    Can we bold few letters in BRF send mail action in the body of the mail.
    I have this requirement But I am not sure whether its feasible or not.
    Could You Please help me.
    Thanks,
    Ishani

    self

  • Smartform Mail Sending via Action profile

    Hi,
    we have a big problem, because our sended emails going into customers spam filter. We hava SAP CRM 5.0 and we send the emails via action profile.
    For that we use the standard for sending smartforms via action profile. Follwing problems are occured:
    1) email recipient is fill only in the cc field, not in the to field of an email
    2) the subjet ist the sam as the dcument name
    3) the emial is sended without text only whith attachment
    So my question are:
    how can i customize that the email is wirtten in the to field and how i can change the subject of this mail.
    Is ist possible to add a text to the email? Maybe not, but than we could add a disclaimer in the mail hub - so my firts questions are more importent for me.
    Thank you for your help
    Stefan

    Hi,
    To manipulate the subject Refer   Note 895550 - Name of Smart Form used as e-mail subject 
    Im not sure why the email recipient is in CC instead of To. Please check your Action settings. How are you determining the recipient? if it's by partner function, it should automatically be filled in To field.
    Smartforms can be sent either as Text or pdf attachment. This is controlled globally in SMTP settings in SCOT. I believe you can choose attachment option and also add some text by manipulating the Action class.
    HOpe this helps.
    Shaik

  • How to Hardcode sender JDBC action node as EXECUTE

    Hi ,
    I have JDBC to File scenario ,please suggest me how to hardcode sender JDBC structure nodes <b>action</b> as "EXECUTE" and <b>table</b> as "ST_PROS.Get_Table" while designing the message mapping.

    Raju,
    In the ase of sendrer JDBC adapters you need to provide the SQL Query in the adapter.
    Also, the document name and document namespace will be the values for the Message Type Name and MessageTypeNamespace.
    The Messagetype youcreate will have to be of this format,
    <MESSAGETYPENAME>
    <row> <b> 0 to unbounded</b>
    <ColumnName1> </ColumnName1>
    <ColumnName2> </ColumnName2>
    </row
    </MESSAGETYPENAME>
    if your select query is
    Select name,empno from emptable;
    the datatype will be,
    <MESSAGETYPENAME>
    <row> <b> 0 to unbounded</b>
    <name> </name>
    <empno> </empno>
    </row
    </MESSAGETYPENAME>
    Regards
    Bhavesh

  • Is there anyway to send a action/command to all tabs? Like clicking the same button on 100+ tabs all at once?

    I'm wanting to send a certain command to all tabs simultaneously.
    Can it be done?

    What kind of action? A Greasemonkey userscript can detect certain browser global events and take action across all tabs. For example, it can detect when Firefox has gone "offline" using the Work Offline feature. See: [http://userscripts.org/topics/91003 WORK OFFLINE mode warning - Userscripts.org].

  • NFS Sender File Adapter Source Directory

    Hello everybody,
    I have the next problem cause company politics I can't put some files that I need in the XI Server, so I sould take them from another server directory, and cause compañy politics too I can't use FTP so I need to use NFS, but I've been reading some threads about it and some of them says I can't do it and some of them says that I can do it and even give come paths, now the file system is in a Unix Server, how can I do this????? should I put the server an path direclty in de cc or should I map the directory and how do I do this, any help would be appreciated, thanks in advance.
    Regards,
    Julio

    Hello Julio,
    If your lacation is as follows:
    server01\path1\path2
    Then put *
    server01\path1\path2* as your source directory.
    Important
    For Linux ensure that the <sid>adm user can access the specific location.
    For Windows ensure that the sapservice<sid> user can access the specific location.  (Will probably have to be on the domain to achieve this).
    Regards,
    Yaghya

  • Regarding Send Email action in SharePoint designer

    Hi All,
    In one of my Designer workflow, I want to send email with all the list items field in a tabular format. Is it Possible.?

    Check :
    http://social.msdn.microsoft.com/Forums/sharepoint/en-US/f936a724-5f84-4f51-a3cd-dae328b37b21/sharepoint-designer-2010-workflows-html-email-deformed?forum=sharepointcustomizationprevious
    http://social.technet.microsoft.com/Forums/en-US/457393c8-fe7d-4fcf-85e0-e464a74267e8/issue-with-tables-in-the-workflow-email?forum=sharepointgeneralprevious
    http://blogs.technet.com/b/praveenh/archive/2010/12/11/set-up-your-workflow-to-send-an-e-mail-message.aspx

  • Need send button action change

    I have the latest iPhone5c with the iOS of last month.
    I'm frustrated by the iPhone randomly sending out unfinished emails I'm writing without my telling it to send. As I'm writing, the message is often suddenly sent without my asking it to be sent.
    This could be stopped if only the phone would give me a pop-up asking me if I wanted to send the message.
    I suspect this mis-fire of the send-message is caused by the cover screen of the Otter-box protective case, it seems to happen from different points on the screen as I'm writing.
    I wish I could persuade an iPhone programer to make this change in their iOS. It's a very annoying bug to live with..........
    Is this in the iOS settings somewhere and i can just turn it on ???? If not, can someone tell anyone that can effect this in Apple iPhone programing that it would be a very good thing to add to the system? I doubt I'm the only user with this vexing problem.
    Still, is there a current fix for we users ????

    Please submit your feature request to Apple at this link: http://www.apple.com/feedback

  • SXMB_MONI: no interface action for sender or receiver found

    Hi Experts,
    I try to integrate PI and BI 7.0 using XI adapter (feel doubts about type).
    I used 2 giudes: "How to Push Data into BW from XI" and "How to Send XML Data to BW".
    SLD check is ok. Proxy is active at BW side. Quality of Service - Exactly Once.
    RWB and SXMB_MONI at PI side show that test message was successfully sent. But I cant see it in DQ (RSA7).
    xml from SXMB_MONI at PI and reciever part:
      <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 data_tobw</Trace>
      <Trace level="1" type="T">select interface namespace http://integrate/xi/bw</Trace>
      <Trace level="1" type="T"><b>--no interface action for sender or receiver found</b></Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
    Help me to send xml to BW please.
    Thanx in advance,
    Alex

    >
    Alexander Rychkov wrote:
    > Hi Experts,
    > I try to integrate PI and BI 7.0 using XI adapter (feel doubts about type).
    > I used 2 giudes: "How to Push Data into BW from XI" and "How to Send XML Data to BW".
    > SLD check is ok. Proxy is active at BW side. Quality of Service - Exactly Once.
    >
    > RWB and SXMB_MONI at PI side show that test message was successfully sent. But I cant see it in DQ (RSA7).
    >
    > xml from SXMB_MONI at PI and reciever part:
    >   <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 data_tobw</Trace>
    >   <Trace level="1" type="T">select interface namespace http://integrate/xi/bw</Trace>
    >   <Trace level="1" type="T"><b>--no interface action for sender or receiver found</b></Trace>
    >   <Trace level="1" type="T">Hence set action to DEL</Trace>
    >
    > Help me to send xml to BW please.
    >
    > Thanx in advance,
    > Alex
    confirm if interface data_tobw with namespace http://integrate/xi/bw is present in IR and also if it is activated.
    Also do a cache refresh from sxi_cache

  • XML Monitor: no interface action for sender or receiver found

    Hi,
    I am new to XI and currently working on Supplier Network Collaboration ( SNC) to Integrate PO's from ECC to SCM system via XI. I have successfully triggered PORDCR1 message for which I was able to see the XML message in XI. The message is stuck on the Inbound of SCM system ( seen in SMQ2 with error message "Internal error, calling address update without address ID Message no. SR053).
    When i double click on Inbound queue (SMQ2) in SCM system it takes me to SXI_Monitor
    Below is the log from bottom screen for Trace. Can you please check and see if you could help to resolve the issue?
    Thanks,
    Tejinder
    Below is the Trace bottom screen details
    <?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="T">http content length 7569</Trace> 
    <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">Process ID: 27633</Trace> 
    <Trace level="1" type="T">Work Process ID: 0</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 = AM2</Trace> 
    <Trace level="1" type="T">client = 001</Trace> 
    <Trace level="1" type="T">language = E</Trace> 
    <Trace level="1" type="T">user = ALE_SNC</Trace> 
    <Trace level="1" type="Timestamp">2014-09-10T15:06:15Z CST</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 = 005056B61D0E1ED48E9F7E70255B98CE</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 : XBTR0005</Trace> 
    <Trace level="1" type="T">Generated prefixed queue name = XBTR0005</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 ReplenishmentOrderNotification_In</Trace> 
    <Trace level="1" type="T">select interface namespace http://sap.com/xi/SNC/Global</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>

    Hi Tejinder
    Check this link
    NO INTERFACE ACTION FOR SENDER OR RECEIVER FOUND
    SXMB_MONI: no interface action for sender or receiver found
    Error: no interface action for sender or receiver found
    no interface action for sender or receiver found - SMQ2 SYSFAIL
    Regards
    Osman
    Message was edited by: Osman Jabri

  • 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

  • NO INTERFACE ACTION FOR SENDER OR RECEIVER FOUND

    Hi Masters of SRM
    Into SRM/SUS client received an message XML across XI the  SXMB_MONI  in trace section show the next message
    <!-- ************************************
    -->
    <Trace level="3" type="T">Persisting message Status = 003</Trace>
    <Trace level="3" type="T">Message version 002</Trace>
    <Trace level="3" type="T">Pipeline SENDER</Trace>
    <Trace level="1" type="T">--start determination of sender interface action</Trace>
    <Trace level="1" type="T">select interface PurchaseOrderRequest_Out</Trace>
    <Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/Procurement/Global</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</Trace>
    <Trace level="1" type="T">select interface namespace</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
    NO INTERFACE ACTION FOR SENDER OR RECEIVER FOUND
    what can I do ?
    thanks.

    Hi Nikhil .
    yes the Receiver Determination is Active.
    I can see other message into message in SUS  client these is the complete message.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">Work Process ID: 884922</Trace>
      <Trace level="1" type="T">COMMIT is expected by application !</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="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 level="2" type="T">XMB kind = SND_CENTR</Trace>
      <Trace level="3" type="T">Start pipeline found</Trace>
      <Trace level="2" type="T">Switch to external start pipeline PID = SENDER</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 = SRD</Trace>
      <Trace level="3" type="T">client = 009</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = WF-BATCH</Trace>
      <Trace level="1" type="Timestamp">2011-03-08T02:25:46Z CST</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 = 4D71A759FF9E00D8E1008000B9F06E02</Trace>
      <Trace level="1" type="T">PLNAME = SENDER</Trace>
      <Trace level="1" type="T">QOS = EOIO</Trace>
      <Trace level="1" type="T">Queue-Id = ORD4000000482</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">QOS = EOIO</Trace>
      <Trace level="3" type="T">Message-GUID = 4D71A759FF9E00D8E1008000B9F06E02</Trace>
      <Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = SENDER</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_SENDER</Trace>
      </Trace>
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>
      <Trace level="3" type="T">Generate prefixed queue name</Trace>
      <Trace level="1" type="T">Queue name : XBQSORD4000000482</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBQSORD4000000482</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 = 4D71A759FF9E00D8E1008000B9F06E02</Trace>
      <Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
      <Trace level="3" type="T">Call qRFC .... Pipeline = SENDER</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 level="3" type="T">Persisting message Status = 001</Trace>
      <Trace level="3" type="T">Message version 000</Trace>
      <Trace level="3" type="T">Pipeline SENDER</Trace>
      <Trace level="1" type="T">--start determination of sender interface action</Trace>
      <Trace level="1" type="T">select interface PurchaseOrderRequest_Out</Trace>
      <Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/Procurement/Global</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">Work Process ID: 725194</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">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline SENDER</Trace>
      <Trace level="3" type="T">system-ID = SRD</Trace>
      <Trace level="3" type="T">client = 009</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = WF-BATCH</Trace>
      <Trace level="1" type="Timestamp">2011-03-08T02:25:46Z CST</Trace>
      <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
      <Trace level="1" type="T">Get definition of external pipeline SENDER</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
      <Trace level="3" type="T">External PLID = SENDER</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_SENDER</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_SENDER</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_SENDER</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 level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_INTEGRATION_SERVER</Trace>
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2011-03-08T02:25:46Z CST Begin of pipeline processing PLSRVID = SENDER</Trace>
    - <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
      <Trace level="1" type="Timestamp">2011-03-08T02:25:46Z CST Start of pipeline service processing PLSRVID= PLSRV_CALL_INTEGRATION_SERVER</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_INTEGRATION_SERVER</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_INTEGRATION_SERVER</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_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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
      <Trace level="1" type="T">URL for integration server read from global configuration</Trace>
      <Trace level="1" type="T">URL= dest://SAP NETWEAVER XI</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="2" type="T">Addressing mode: CallIntegrationServer</Trace>
      <Trace level="3" type="T">URL = dest://SAP NETWEAVER XI</Trace>
      <Trace level="3" type="T">Host =</Trace>
      <Trace level="3" type="T">Port =</Trace>
      <Trace level="3" type="T">Transport protocol = HTTP</Trace>
      <Trace level="3" type="T">Message protocol = 003000</Trace>
      <Trace level="3" type="T">Path =</Trace>
      <Trace level="3" type="T">Attributes of destination: SAP NETWEAVER XI</Trace>
      <Trace level="3" type="T">Type = H</Trace>
      <Trace level="3" type="T">Pipeline =</Trace>
      <Trace level="3" type="T">Action = EXECUTE</Trace>
      <Trace level="3" type="T">Host = mxwpides</Trace>
      <Trace level="3" type="T">Port = 50000</Trace>
      <Trace level="3" type="T">Client = 001</Trace>
      <Trace level="3" type="T">User = PIAPPLUSER</Trace>
      <Trace level="3" type="T">Language =</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">SSL not active</Trace>
      <Trace level="1" type="T">----
    </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">Serializing message object...</Trace>
      <Trace level="1" type="T">HTTP Multipart document length: 8089</Trace>
      <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
      <Trace level="1" type="T">HTTP-client: request sent</Trace>
      <Trace level="3" type="T">HTTP-client: request sent</Trace>
      <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
      <Trace level="1" type="T">HTTP-client: response received</Trace>
      <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
      <Trace level="1" type="T">sap-xi-messageid 4D71A759FF9E00D8E1008000B9F06E02</Trace>
      <Trace level="1" type="T">HTTP-client: status code = 200</Trace>
      <Trace level="3" type="T">Deserializing message object...</Trace>
      <Trace level="1" type="T">HTTP-client: parsed & response message object created</Trace>
      <Trace level="3" type="T">HTTP-client: closing...</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2011-03-08T02:25:47Z CST End of pipeline service processing PLSRVID= PLSRV_CALL_INTEGRATION_SERVER</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 SENDER</Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Async processing completed OK.</Trace>
      <Trace level="3" type="T">system-ID = SRD</Trace>
      <Trace level="3" type="T">client = 009</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = WF-BATCH</Trace>
      <Trace level="1" type="Timestamp">2011-03-08T02:25:47Z CST</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 003</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline SENDER</Trace>
      <Trace level="1" type="T">--start determination of sender interface action</Trace>
      <Trace level="1" type="T">select interface PurchaseOrderRequest_Out</Trace>
      <Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/Procurement/Global</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</Trace>
      <Trace level="1" type="T">select interface namespace</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>
    Thanks. 
    best regards

Maybe you are looking for