FILE 2 FILE SCENARIO

Hi All..
In file to file scenario I want to send the data from a flat file.
I used File content conversion perameters for the same.
My flat file has more than 1 record.
I have given all the file content conversion parameters as per the BLOG file 2 file Part#2.
But It will take only the first record.
I used transfer protocal type NFS not ftp
Can any one plz expalin where I am wrong.
Regards
Diva

Hi..Jai
I will keep row occurence as 1.1.
No I will make it to 1..unbounded.
And let u know if any problem occurs...
Assigned full points for that..
thanks & Regards
Diva

Similar Messages

  • PI 7.1 scenario -- File to File , File to IDOC  and IDoc to File Scenario

    Hi All,
    *I have PI 7.0 . I have in that File to File , File to IDOC  and IDoc to File Scenarios*
    File to File -- This scenario is working fine.
    File to IDOC   --  Setting done in PI 7.0 like SM59,  IDXI, IDX2  and in R/3 like SALE (logical system)---  This scenario is working fine.
    IDoc to File  --  Seeting done in R/3 like SALE (Logical system, Distrubtion Model (Port, Partner Profile)) -- This scenario is working fine.
    Now I need to move to PI 7.1  -- for File to File , File to IDOC  and IDoc to File Scenarios.
    Please let me know do I require to make any changes in Design and Configuration and settings in PI 7.1 and R/3 for above scenarios or it will work fine as it is already working for PI 7.0
    If changes are required please let me know what changes to do for each scaenario and pls also send blogs for that.
    Regards

    >
    Rickkk wrote:
    > Hi,
    >
    > Idoc metadeta is updated through idx2?
    >
    > Regards
    If there is no metadata maintained for an idoc type, the metadata for that idoc type gets loaded when an idoc of that type is received by PI for the first time. If you are looking at loading metadata of all idoc types before the first run, its really not required. Just make sure that the port is configured properly. Although, there is no harm in preloading the metadata using IDX2.
    You need to use IDX2 mandatorily when the the metadata changes and the metadata in ECC and PI is different. In that case, you need to delete metadata for the changed IDoc type and then either you can update the metada through IDX2 or let the system take care of.

  • File-to-File/RFC scenario with reading filename

    Hi,
    i have a File-to-File/RFC scenario which causes some problems in desining it correctly. Maybe some of you has an idea how to do this.
    Scenario:
    - A file is picked up by a File-Adapter. The files are different: pdf, doc, tiff, jpg, txt, ...
    - The file must now go through a business process (not necessary the file, but i need the filename in the business process).
    - The process has to contact several backend systems (SAP R/3) to collect some data. To achieve this the filename has to be send to this systems.
    - The collected data are send via SOAP to a receiver system
    - The file itself has to be stored in a directory via File-Adapter.
    Here's my problem:
    - Is it possible to transport the binary file content within a message which contains other elements (e.g. filename)?
    - Is it possible to do graphical mappings with such a payload (only 1 to 1)? Or must i use Java Mappings only?
    - How to generate a Message from the sender File Adapter which contains binary file content AND filename? Is this possible with a Module?
    - Is it better to create 2 messages with an adapter module? One with the image the other with the filename. Or is it better to split them later in a Mapping?
    Thanks in advance,
    ms

    If all that you need is the file name, use adapter specific settings in the sender file adapter. Then you can access the file name in mapping runtime in UDFs. If you want to have content of the pdf, jpg etc images, i do not think there are ready modules available except for reading pdfs ( you might have to research on this).
    For look ups etc with R3 systems, you can use the file name that you got from the adapter and store it in mapping fields.
    VJ

  • Error in file-file scenario: HTTP response contains status code 503

    Hi folks,
    I've encountered the foll error in file-file scenario:
    Testing file-file scenario (followed the blog: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/flatFILETOFLATFILE&)
    Initially i was hving problems with recvr comm channel, which are now resolved. File is sent successfully but not recvd. I tried to modify the scenario above and change the file type to 'Text' but still got the same error.
    I've checked SICF -->default_host/xi/engine , we dont maintain logon data there. when i test the default_host/xi/engine service, it resolves into an ip addr as follows:
    http://<hostname>.<domain.com>:8001/sap/xi/engine?sap-client=<clientNo>
    (Also, we hv a BW system running on the same server ,which uses a fully qualified domain, while we dont which is why we get the above domain. Im not sure if there are any issues with that.)
    and we get the foll error:
    Error Code 10060: Connection timeout
    If i remove the domain manually, im prompted for userid/pwd and get the foll result:
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP:Header />
    - <SOAP:Body>
    - <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <faultcode>SOAP:Client</faultcode>
      <faultstring>Pipeline specified in URL attribute (type) not existing</faultstring>
      <faultactor>http://sap.com/xi/XI/Message/30</faultactor>
    - <detail>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="MESSAGE">URL_PIPELINE_NOT_FOUND</SAP:Code>
      <SAP:P1>/sap/xi/engine?sap-client=<clientNo></SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Pipeline ID , which is expected as value of attribute &quot;type&quot; in the URL, does not exist in the Integration Engine (URL = /sap/xi/engine?sap-client=811)</SAP:Stack>
      </SAP:Error>
      </detail>
      </SOAP:Fault>
      </SOAP:Body>
      </SOAP:Envelope>
    also, we dont hv any overload issues as this is dev env and not many of us are using the xi server. Would really appreciate if any of you can share your inputs on how to resolve this. Thanks!!
    cheers
    Prachi

    Hi ,
    Look in to this for all errors
    /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
    The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
    Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
    Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
    • Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
    • The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
    • Refer SAP Note 803145,807000,791655
    <b>Award Points if found usefull.</b>

  • N:1 file merging scenario in bpm

    Hi friends,
    Can anybody send me link of blog for file merging scenario in BPM. i hav two files and i hav to merge it into one single file. I am new to XI, plz help me.
    Thanks in advance,
    Shweta

    Hi,
    Check this blogs...
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    /people/narendra.jain/blog/2005/12/30/various-multi-mappings-and-optimizing-their-implementation-in-integration-processes-bpm-in-xi
    http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
    Merging using corelation -
    /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
    Example using correlation:
    http://help.sap.com/saphelp_nw04/helpdata/en/08/16163ff8519a06e10000000a114084/content.htm
    Please reward points if it helps
    Thanks
    Vikranth

  • XI is not able to archive file in file-idoc scenario

    Hello friends,
    I have an issue in my file->idoc scenario. When a file is placed to XI's filesystem using FTP, it is placed under xiftpuser user. Owner of all directories in this structure wher the file is placed is xiftpuser. XI is not able to archive the file because of the permissions on the archive directory. But the problem is, permissions on this directory are 775 and xiftpuser and xipadm user are in the same group. So this should work. But it doesn't. When I change permissions to 777 everything works fine.
    Do you have any idea what could be wrong?
    Does it matter, that xipadm user has been added to the common group with xiftpuser "later", when XI was up a long time before? Do we need to restart j2ee to take these new permissions into account?
    Thank you,
    Olian
    Edited by: Olian Saludew on Sep 23, 2008 11:46 AM

    Hi,
    If archive directory Path is d:\archive
    Put a '\' after it.
    e.g. "D:\archive\"
    It will work.
    Regards,
    Akshay.

  • ATTRIBUTE_IDOC_RUNTIME error in File-IDOC Scenario

    Hi,
    I got this error in FIle-IDOC scenario.
    ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>Transaction IDX1: Port SAPMMX, client , RFC destination contain errors
    There are many threads on same issue. Almost in all threads, the suggestion given was, we need to check the Channel Definition(Port should be SAP<SYSID> and not SAP<SYSID>_<CLIENT>)
    I have given the proper values for RFC desitnation and port. Even then, I m getting this error.
    Is there any other suggestions?

    Hi aarthi,
    I suggest u chk all d settings dat u hav done..
    Steps for ALE settings:-
    Steps for XI
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the R3 system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto IDX1.
         Create a new port.
         Give the port name.
         Give the client number for the R3 system.
         Select the created Rfc Destination.
    Step 3)
         Goto IDX2
         Create a new Meta data.
         Give the Idoc type.
         Select the created port.
    Steps for R3.
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the XI system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto WE21.
         Create a port under transactional RFC.(R3->XI)
         Designate the RFC destination created in prev step.
    Step 3)
         Goto SALE.
         Basic settings->Logical Systems->Define logical system.
         Create two logical systems(one for XI and the other for R3)
         Basic settings->Logical Systems->Assign logical system.
         Assign the R3 logical system to respective client.
    Step 4)
         Goto WE20.
         Partner type LS.
         Create two partner profile(one for XI the other for R3).
         Give the outbound or inbound message type based on the direction.
    Step 5)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    Step 6)
         Goto WE19
         Give the basic type and execute.
         fill in the required fields.
         Goto IDOC->edit control records.
         Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
         Click outbound processing.
    Step 7)
         Go to SM58
         if there are any messages then there is some error in execution.
         Goto WE02.
         Check the status of the IDOC.
         Goto WE47.
         TO decode the status code.
    BD87 to check the status of IDOC.
    In case if not authorized then go to the target system and check in SU53, see for the missing object
    and assign it to the user.
    SAP r3
    sm59(status check)(no message)
    WE02(status check)
    WE05(status check)
    BD87(status check)
    Xi
    IDx5(Idoc check)
    SU53(authorization check)
    reward points if helpful...
    MenoN

  • File - File integration scenario in SAP XI 3.0

    I am trying a simple file <-> file scenario in XI 3.0 . I am reading file content from an FTP server , having a simple mapping program in XI and then writing it to another foler on the FTP server.
    I am completely new to XI , however worked on TIBCO EAI extensively.
    I have created the following DESIGN TIME Objects  and NOTHING ELSE
    1) Two DataTypes , Two Message Types & Two Message Interfaces
    2) An interface mapping & a message mapping object( mapping program) to convert b/w the above two message types 
    I have created the  following CONFIGURATION TIME objects and NOTHING ELSE
    1) Two Business Services ( Under Service without Party )  , and ve created a communication channel ( adapter type FILE ) under each business service
    I am trying to use the Configuration Assistant under Tools menu , the doc says , i just need to select the message types & the rest will be genrated by the wizard. I choose the Business Service , but then what is the "INTERFACE" i have to choose , since nothin appears in the drop down. I tried "Internal Communication" & "Partner Communication" options but got stuck in both when choosing the "interface" object. Ideally i think i need to choose the "internal communication".
    Any pointers to what am i missing will be helpful . What are the objects i need to create at Design Time & Config time to achieve the above scenario.

    The Configuration Assistant does not work for business services without party. Go to the SLD and create one or two Business Systems and add them to the Integration Directory, then it should work.
    Regards
    Stefan

  • FILE - FILE Scenario - output file is not available

    Hi
    I'm doing simple file - file scenario based on the weblog
    /people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1
    In RWB >> msg monitor shows, the message status is successful. But I'm unable to find output file in the directory as I mentioned.
    Pls help me where to find.. what is the problem
    - Govind J

    Hi Govind,
    These are a few things you can do:
    Check the permissions of the folder where the file is being generated by XI.
    If you are doing Content conversion, please can you just remove it and see if the XML file is getting generated.
    Also, please check if it's picked up by any other application when you place it on the server.
    I am assuming out here that you are speaking abt the file that is give by SAP XI after processing the incomming file.
    Also check default .trc log file in visual admin.it will tell u if there any errors
    and also check the permissions of the files generated by XI
    Regards,
    Abhy

  • Problem in File-File Scenario

    Hi All,
    I am doing File->File Scenarios. There is no Recrod set also. I want to rename the file using XI. No mapping required. To rename the File name we can do the coding related to Dynamica configuration in one UDF and will map to the top node of the target. But i don't have the mapping here, So How can i execture this UDF or Do i need to write the Module in File adapter CC.
    I tried with dummy mapping , But I am getting the following error
    </SAP:Category>
    <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE
    </SAP:Code>
    <SAP:P1>com/sap/xi/tf/_MM_Target_File_determined_
    </SAP:P1>
    <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException
    </SAP:P2>
    <SAP:P3>Fatal Error: com.sap.engine.lib.xml.parser.Parser~
    </SAP:P3>
    <SAP:P4/>
    <SAP:AdditionalText/>
    <SAP:ApplicationFaultMessage namespace=""/>
    <SAP:Stack>During the application mapping com/sap/xi/tf/_MM_Target_File_determined_ a com.sap.aii.utilxi.misc.api.BaseRu
    ntimeException was thrown: Fatal Error: com.sap.engine.lib.xml.parser.Parser~
    </SAP:Stack>
    The mapping part is correct. There is no doubt on that. I don;t know why i am getting this error. Can you please tell me what could be the reason or any solution to resolve my problem.
    Points will be rewarded for helpful answers.
    Thanks in advance,
    Best Regards,
    Vijay

    Bhaskarudu,
    Option 1: If you only want to rename the file then pick the file and rename the file in receiver communicatin channel and write. Check this weblog for some help:
    /people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-without-using-the-integration-repository
    Option 2: If you want to rename the file dynamically then you should do the mapping. Check this weblog for this:
    /people/sravya.talanki2/blog/2005/08/16/configuring-generic-sender-file-cc-adapter
    Option 3: If you are picking the file within your organisation which is shared on NFS then you use OS commands in the file adapterd to rename the file.
    Regards,
    ---Satish

  • Simplified Chinese format problem in File-File Scenario.

    Hi,
    I have configured File(FTP) - > File(FTP) Scenario.
    I am expecting a Chinese File from Source system which is AS400. I am using the file encoding format UTF-8 while the chinese characters are in GB2312 format. My sender file adapter picks up the file correctly, but SXMB_MONI gives Mapping related Parser error. Kindly Suggest.
    Do i need to change some character set or code page? if yes, where should it be done?
    Thanks Charu.

    Hi,
    Under File Encoding, specify a code page.
    The default setting is to use the system code page that is specific to the configuration of the installed operating system. The file content is converted to the UTF-8 code page before it is sent.
    Permitted values for the code page are the existing charsets of the Java runtime. According to the SUN specification for the Java runtime, at least the following standard character sets must be supported:
    US-ASCII
    Seven-bit ASCII, also known as ISO646-US, or Basic Latin block of the Unicode character set
    ISO-8859-1
    ISO character set for Western European languages (Latin Alphabet No. 1), also known as ISO-LATIN-1
    UTF-8
    8-Bit Unicode Character Format
    UTF-16BE
    16-bit Unicode character format, big-endian byte order
    UTF-16LE
    16-bit Unicode character format, little-endian byte order
    UTF-16
    16-bit Unicode character format, byte order
    Check which other character sets are supported in the documentation for your Java runtime implementation.
    XML text documents generally contain their own code page description and should be treated as binary data type.
    If it is not there the you need write the Adapter module for sender side .
    Or you can use the XSLT mapping using CDATA.
    see the below link
    http://help.sap.com/saphelp_nw2004s/helpdata/en/e3/94007075cae04f930cc4c034e411e1/content.htm
    Regards
    Chilla

  • Data tuncated in file adapter scenario

    Hi,
    File adapter scenario - Sender systems passes a file (csv format) to PI which has one of field as 0001. This field is received at PI without the prefix 000. But, the target systems requires the data to be in the same format as the sender. How to solve this?
    Thanks

    Satish,
    It is the behaviour of the CSV files that it trims leading zeros in the columns with numeric values, try this open the CSV file and select the column and right click it in the context menu you would find FORMAT CELLS and change the type of the column to TEXT so that whatever values you enter in that column remain as it is without truncating.
    Also, the trick at following link would help
    [http://www.howtogeek.com/howto/microsoft-office/how-to-import-a-csv-file-containing-a-column-with-a-leading-0-into-excel/]
    Hope this resolves your issue!!
    Regards,
    Amit

  • Idoc to File Split Scenario..

    HI Experts,
    My scenario is Idoc to File split scenario..
    Idoc will be triggered from the SAP ECC system and at the target side we need to drop two text files at the ftp directory.
    so Idoc data needs to be splitted and to be dropped in two differient files in the target FTP directory..
    So can any one suggest how to go ahead with the scenario..
    Thanks,
    --Kishore.

    Hi,
    In the idoc, some of the data will go to onefile and some goes to other files..
    the structures of the two files are differient..
    There is no condinal spliting here every idoc contents should be mapped according to the requirement and dropped as two files.. at the target end.
    for ex:
    Idoc
    field1
    fileld2
    field3
    field4
    in the out put side
    file1 should contain
    field1
    field3
    field4
    file2 should contain
    field1
    field2
    fileld3
    This is what the requirement, if you are not getting reply back with your queries..
    Thanks,
    --Kishore..

  • HTTP-FILE synchronous scenario

    Hi,
    I want to configure a Http to file synchronous scenario.
    Message will be sent through the HTTP test tool. I have selected BestEffort as the QoS.
    We do not want to use the repository objects.
    Sample file say(<tag>this is a sample file</tag>) will be sent through HTTP test tool.
    This file should be received by the File Receiver channel and dumped on the FTP.
    In response, a file from some other folder on FTP should be sent.
    How can this be achieved?
    Regards,
    Pratibha.

    Hi Pratibha,
    the standard sap help side is here very good
    [Integration Processes (ccBPM)|http://help.sap.com/saphelp_nw2004s/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm]
    You need a receive step (synchronous) for for your http request.  For this you need 3 abstract interfaces: 1 synchr IF, 1 async for request container, 1 async for resp container. You need to correlate with a unique number which the http sender has to send (f.e. date/time stamp)
    Next may be a transformation (mapping) but not required.
    Then a async send step to send the file.
    The response file need to be created, the corresponding adapter should have a short poll intervall. The response file need to send the unique id as well.
    The BP correlates the second receive step, next you can - like before optional - execute a transformation step.
    Finally u close the sync/async bridge and send the response back. This will take assumedly a minute or more.
    The whole design is may be not sufficient. Better ask if the requierments are changeable.
    Regards,
    Udo

  • Payload missing in File-File scenario

    Hi,
    I have created a scenario which is a combination of File-IDoc and File-File scenario.
    First scenario is working fine.IDoc is getting generated and posted to SAP R/3.
    I could see messages for these two as child messages in sxmb_moni with same message ID.
    But in the second message,payload is missing in Call Adapter block and Response block in sxmb_moni.
    Also,output file is not getting generated though the message is successful in sxmb_moni.
    Could anyone please let me know what could be the reason for this.
    Thanks.
    Best Regards,
    Shweta

    this is the full trace:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>47A1A2FD-9F90-0066-E100-80028928A9DC</SAP:MessageId>
      <SAP:TimeSent>2008-01-31T10:34:40Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Logitec_Test</SAP:Party>
      <SAP:Service>POS_MAIL</SAP:Service>
      <SAP:Interface namespace="http://pan.eu/ORDERS/LOGITEC_ORDRS_09">MI_ORDERS_EDIFACT_D96A_AS_OB</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Logitec_Test</SAP:Party>
      <SAP:Service>BS_FILE_RECEIVER</SAP:Service>
      <SAP:Interface namespace="http://pan.eu/ORDERS/LOGITEC_ORDRS_09">MI_ORDERS_EDIFACT_D96A_AS_IB</SAP:Interface>
    - <SAP:Mapping notRequired="M">
      <SAP:ObjectId>s0jXwORWMKCNyteX7/7ysA==</SAP:ObjectId>
      <SAP:SWCV>ftfEkNt0EdqTpexmiSip3w==</SAP:SWCV>
      <SAP:SP>-1</SAP:SP>
      </SAP:Mapping>
      </SAP:Receiver>
      <SAP:Interface namespace="http://pan.eu/ORDERS/LOGITEC_ORDRS_09">MI_ORDERS_EDIFACT_D96A_AS_IB</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2008-01-31T10:34:40Z" wasRead="false">
      <SAP:Engine type="AE">af.pxe.pandpxe</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
      <SAP:MessageId>2100B8D2-CFE8-11DC-CDAA-001125A5DEBE</SAP:MessageId>
      <SAP:Info />
      </SAP:Hop>
    - <SAP:Hop timeStamp="2008-01-31T10:34:40Z" wasRead="false">
      <SAP:Engine type="IS">is.00.pandpxe</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>47A1A2FD-9F90-0066-E100-80028928A9DC</SAP:MessageId>
    - <SAP:Branch>
      <SAP:MessageId>47A1A2FC-9F90-0066-E100-80028928A9DC</SAP:MessageId>
      <SAP:Service>PAECLNT020</SAP:Service>
      </SAP:Branch>
    - <SAP:Branch>
      <SAP:MessageId>47A1A2FD-9F90-0066-E100-80028928A9DC</SAP:MessageId>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Logitec_Test</SAP:Party>
      <SAP:Service>BS_FILE_RECEIVER</SAP:Service>
      </SAP:Branch>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20080131</SAP:Date>
      <SAP:Time>113441</SAP:Time>
      <SAP:Host>pandpxe</SAP:Host>
      <SAP:SystemId>PXE</SAP:SystemId>
      <SAP:SystemNr>00</SAP:SystemNr>
      <SAP:OS>AIX</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>003</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>XIAFUSER</SAP:User>
      <SAP:TraceLevel>3</SAP:TraceLevel>
      <SAP:Logging>1</SAP:Logging>
      <SAP:LogSeqNbr>004</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId />
      <SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
      <SAP:PipelineService />
      <SAP:QIdInternal>XBTOW___0002</SAP:QIdInternal>
      <SAP:CommitActor>X</SAP:CommitActor>
      <SAP:ParentId ChildNo="0" ChildTotal="0">2100B8D2CFE811DCCDAA001125A5DEBE</SAP:ParentId>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="010">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID">8928A9DC00C947A1A441092F</SAP:EOReferenceRuntime>
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>4272</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>8041</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>4272</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>2874</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
      <SAP:AdapterOutbound>AENGINE</SAP:AdapterOutbound>
      <SAP:InterfaceAction>DEL</SAP:InterfaceAction>
      <SAP:RandomNumber>35</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      <SAP:Sender_Agreement_GUID>C14103EF96A93EF7A416B17522666D3A</SAP:Sender_Agreement_GUID>
      <SAP:Receiver_Agreement_GUID>4E2837E24B083A33A77C5043CBB15379</SAP:Receiver_Agreement_GUID>
      <SAP:Serialize_Children>X</SAP:Serialize_Children>
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103440.920981</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103440.934955</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103440.935459</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103440.945085</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103440.945102</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.062247</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.064953</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.069988</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.096849</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.102084</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.11954</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.170827</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.170842</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.343581</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.346447</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.388572</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.414031</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.418165</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.447064</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.589866</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    - <SAP:OutboundBindingEntry version="30">
      <SAP:OutboundBindingObjectId>4E2837E24B083A33A77C5043CBB15379</SAP:OutboundBindingObjectId>
      <SAP:FromPartyName>Logitec_Test</SAP:FromPartyName>
      <SAP:FromServiceName>POS_MAIL</SAP:FromServiceName>
      <SAP:ToPartyName>Logitec_Test</SAP:ToPartyName>
      <SAP:ToServiceName>BS_FILE_RECEIVER</SAP:ToServiceName>
      <SAP:ToInterfaceName>MI_ORDERS_EDIFACT_D96A_AS_IB</SAP:ToInterfaceName>
      <SAP:ToInterfaceNamespace>http://pan.eu/ORDERS/LOGITEC_ORDRS_09</SAP:ToInterfaceNamespace>
    - <SAP:OutboundBindingAttributes>
      <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:OutboundBindingAttributes>
    - <SAP:HeaderMapping>
      <SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:HeaderMapping>
    - <SAP:ChannelEntry version="30">
      <SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30">Logitec_Test</SAP:PartyName>
      <SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">BS_FILE_RECEIVER</SAP:ServiceName>
      <SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CC_FILE_RECEIVER_EDIFACT_ORDERS</SAP:ChannelName>
      <SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">File</SAP:AdapterName>
      <SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
      <SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
      <SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">AE</SAP:AdapterEngineType>
      <SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">File</SAP:MessageProtocol>
      <SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0.0527</SAP:MessageProtocolVersion>
      <SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">FTP</SAP:TransportProtocol>
      <SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
      <SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30">Seeburger</SAP:FromPartyAgency>
      <SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30">AS2ID</SAP:FromPartySchema>
      <SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30">AS2ID</SAP:ToPartySchema>
      <SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30">Seeburger</SAP:ToPartyAgency>
    - <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:ChannelAttributes>
      </SAP:ChannelEntry>
      </SAP:OutboundBindingEntry>
      </SAP:OutboundBinding>
    - <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 = Logitec_Test</Trace>
      <Trace level="1" type="T">Sender party normalized = Logitec_Test</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="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
      <Trace level="2" type="T">Host = pandpxe.pan.eu:8000</Trace>
      <Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
      <Trace level="2" type="T">Remote address = 137.40.169.220</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="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 = 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 = PXE</Trace>
      <Trace level="3" type="T">client = 010</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:40Z 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 = 2100B8D2CFE811DCCDAA001125A5DEBE</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 level="3" type="T">QOS = EO</Trace>
      <Trace level="3" type="T">Message-GUID = 2100B8D2CFE811DCCDAA001125A5DEBE</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 : XBTI0008</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0008</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 = 2100B8D2CFE811DCCDAA001125A5DEBE</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 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 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 = PXE</Trace>
      <Trace level="3" type="T">client = 010</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET</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 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 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 level="3" type="T" />
      <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 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 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 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 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 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 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 level="3" type="T" />
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z 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 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 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: Logitec_Test - BS_FILE_RECEIVER</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 2</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: - PAECLNT020</Trace>
      <Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
      <Trace level="2" type="T">Number of Receivers:2</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z 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">2008-01-31T10:34:41Z 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 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 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) PAECLNT020 ORDERS.ORDERS05</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: ORDERS.ORDERS05</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) Logitec_Test BS_FILE_RECEIVER MI_ORDERS_EDIFACT_D96A_AS_IB</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: MI_ORDERS_EDIFACT_D96A_AS_IB</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:2</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z 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 level="1" type="Timestamp">2008-01-31T10:34:41Z 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 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 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 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: 2</Trace>
      <Trace level="1" type="T">Multi-receiver split case</Trace>
      <Trace level="1" type="T">Persisting initial (pre-split) message</Trace>
      <Trace level="1" type="T">Persisting split messages (split kids)</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Splitting loop start</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="3" type="T">Split kid MessageGuid: 47A1A2FC9F900066E10080028928A9DC</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTO3___0001</Trace>
      <Trace level="1" type="T">Persisting split kid = 47A1A2FC9F900066E10080028928A9DC</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 012</Trace>
      <Trace level="3" type="T">Message version 000</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="T">Split kid MessageGuid: 47A1A2FD9F900066E10080028928A9DC</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTOW___0002</Trace>
      <Trace level="1" type="T">Persisting split kid = 47A1A2FD9F900066E10080028928A9DC</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 012</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 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 = PXE</Trace>
      <Trace level="3" type="T">client = 010</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET</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 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 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 level="3" type="T" />
      <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 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 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 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 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 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 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 level="3" type="T" />
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z 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">2008-01-31T10:34:41Z 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 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 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 B348D7C0E45630A08DCAD797EFFEF2B0</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping 7ED7C490DB7411DA93A5EC668928A9DF</Trace>
      <Trace level="1" type="T">Interface Mapping http://pan.eu/ORDERS/LOGITEC_ORDRS_09 IM_ORDERS_EDIFACT_to_ORDERS_EDIFACT</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_</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_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_.</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_ completed. (executeStep() of com.sap.xi.tf._MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_</Trace>
      <Trace level="3" type="T">Dynamic configuration is empty</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z 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 = 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_OUTBOUND_BINDING">
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z 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 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 level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <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">Logitec_Test-POS_MAIL</Trace>
      <Trace level="2" type="T">Logitec_Test-BS_FILE_RECEIVER</Trace>
      <Trace level="2" type="T">http://pan.eu/ORDERS/LOGITEC_ORDRS_09.MI_ORDERS_EDIFACT_D96A_AS_IB</Trace>
      <Trace level="2" type="T">Channel found: Logitec_Test - BS_FILE_RECEIVER - CC_FILE_RECEIVER_EDIFACT_ORDERS</Trace>
      <Trace level="2" type="T">no header mapping defined</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z 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 = 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_CALL_ADAPTER">
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <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 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 level="3" type="T">Unknown channel type: File</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_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = AENGINE</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 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="3" type="T">Channel for adapter engine: File</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="2" type="T">return fresh values from cache</Trace>
      <Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
      <Trace level="3" type="T">URL = http://pandpxe:50000/MessagingSystem/receive/AFW/XI</Trace>
      <Trace level="3" type="T">User = XIISUSER</Trace>
      <Trace level="3" type="T">Cached = X</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</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="T">HTTP-client: response received</Trace>
      <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
      <Trace level="3" type="T">HTTP-client: status code = 200</Trace>
      <Trace level="3" type="T">Deserializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: closing...</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</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 = 003</Trace>
      <Trace level="3" type="T">Message version 003</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="T">Async processing: skip mapping of response</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 = PXE</Trace>
      <Trace level="3" type="T">client = 010</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET</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 004</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
      <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
      </SOAP:Body>
      </SOAP:Envelope>

  • Exceptions in file-idoc scenario

    Hi Folks,
    I am developing a file-idoc scenario. What are the different exceptions I would be needed to handle apart from the following two identified?
    1. Mapping issue
    2. Problem in posting the idoc (SAP system may be down and others)
    Thank you

    Hi Raja,
    The errors an happen at following steps:
    1. Error while picking the file:File adapter error
    2. Error in mapping: error due to incorrect data, incorrect format, corrupt file etc.
    3. While posting Idoc: due to Incorrect userId password, due to structure not matching, destination system being down.
    Hope this helps.
    Regards
    Vijaya

Maybe you are looking for