Seeburger + SAP XI

Hi chirag
With your answers I learned some thing about seeburger adapters , will expect any projects....on this combination.
We are expecting internal training thats what?
any prerequisites before moving to SEEBURGER
Thanks
Sushma .

Hello Sushma,
Sushma First of all you have to update your EDI Concepts..
This link can be helpfull go through that
http://en.wikipedia.org/wiki/Electronic_Data_Interchange
We have the following Formats in EDI
Supported EDI formats include:
• ANSI
• EDIFACT
• INHOUSE
• IDOC
• XML Schema
• XML DTD
• CSV
• Delimited Data
• positional data
• SWIFT
• EANCOM
SEEBURGER Upgrades EDI Adapter for SAP XI, Providing Advanced EDI Functions Embedded in SAP NetWeaver
--- SEEBURGER Inc. announced today that it has upgraded its EDI adapter for the SAP Exchange Infrastructure (SAP XI) to equip users with new tools for mapping, tracking and archiving EDI messages.  The new Version 1.5 of the adapter is currently the only comprehensive EDI solution embedded in the SAP NetWeaver™ technology stack.
New features of SEEBURGER’s EDI adapter include:
Message tracking tools enabling business and/or IT users to instantly determine whether purchase orders, invoices and other trading documents have been sent or delivered to external business partners.  Users can search by different criteria including a specific message as well as groups of messages (e.g. all shipment notices that left the company between 8 and 10 am).  Results are viewable from a portal framework built into the adapter.
An expanded library of default messages that reduces implementation time and expense by allowing more EDI processes to be set up without creating messages and their corresponding syntax definitions from scratch.  The new version provides a six-fold increase in the number of general and industry-specific ANSI, EDIFACT, ODETTE and VDA messages supplied with the adapter. 
Message archiving support allowing users to maintain a complete audit trail to meet international tax regulations and other information or compliance requirements.  Messages transmitted through the SEEBURGER adapter can now be forwarded to any third-party archiving system through a file share.  Each document is indexed for easy retrieval through the search function of the organization’s archiving system.
Other upgrades include expanded VAN compatibility that gives users a greater choice of data carriers, and technical improvements for faster and easier adapter setup.
The SEEBURGER adapter utilizes the XI toolsets to handle the EDI configuration, workflow, mapping and communications necessary to convert business documents from industry standards into the XML/SOAP-based format used by SAP NetWeaver.  Like the SEEBURGER B2B Gateway on which it is based, it accommodates all industry and regional-specific data standards and communications protocols to automate business processes with customers, partners and suppliers for organizations in virtually every industry sector and global geographic location.
Version 1.5 of the SEEBURGER SAP XI adapter is available immediately from both SAP and SEEBURGER sales and services organizations.
About SEEBURGER
SEEBURGER is a leading provider of global business integration solutions designed to optimize transactions throughout the extended enterprise by automating trading relationships with all partners regardless of their size and technical resources.  Launched in 1986 to provide integration solutions to the automotive industry in Germany, the company today is ranked among the top business-to-business gateway providers by industry analysts, and serves more than 6,500 customers in 35 countries and more than 15 industries through its flagship B2B Gateway and related products and services.  SEEBURGER has global offices in Europe, Asia Pacific and North America, including a U.S. office that opened in 1998. 
Thanks,
Satya Kumar..
Reward points if it is useful..
Edited by: SATYA KUMAR AKKARABOYANA on Apr 16, 2008 11:40 AM

Similar Messages

  • Seeburger AS2 - connectivity

    Hello,
    is it possible to have one single certificate for both AS2 and SSL, using HTTPS protocol.
    if yes should we upload the certificates twice (AS2 & SSL)?
    Also when we sent some messages via AS2, the seeburger AS2 server seems to be closing the connection abruptly. are there any logs generated on the seeburger side in order to check what actually happened?

    Hi,
    AS/2 details:
    http://www.seeburger.com
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    http://www.seeburger.com
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
    Seeburger thread:
    Refer this forum which talk about the configuration which need to be done for AS2 adapter. This is very helpful:
    Re: Pls.. Help Needed.. Seeburger Mapping Names..!!
    Re: Seeburger AS2 adapter...
    Re: AS2 Module tab.. Mapping Names for modified Standard Msg types ? ? BIC ??
    AS2 adpater-- Configuration details for both SND and RCV.
    AS2 Sender Adapter -- Need few details.
    Flow of data:
    EDI-SEEberger-XI-IDOc-R/3
    Seeburger info:
    Re: seeburger adapter
    Re: SEEBURGER's VAN Adapter
    AS2 info:
    Re: Regarding Seeburger AS2 Adapter
    SEEBURGER EDI adapter
    Wanna Party ?
    Wanna Party ?
    How to Set up an SAP XI Integration Directory Scenario with Party to Support EDI Partner Processing
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
    Here is the link for your reference:
    EDIFACT to XML - Stylus Studio Solution
    The steps to convert EDI to XML / XSD can be found at the following link:
    http://www.stylusstudio.com/edifact_to_xml.html
    Stylus studio download link: http://www.stylusstudio.com/xml_download.html
    Or
    Using the Conversion agent
    How to get started using Conversion Agent from Itemfield
    Conversion Agent a Free Lunch?
    Integrate SAP Conversion Agent by Itemfield with SAP XI
    More on the SAP Conversion Agent by Itemfield
    SAP XI supports EDIFACT
    How to get started using Conversion Agent from Itemfield
    More on the SAP Conversion Agent by Itemfield
    http://www.stylusstudio.com/edi/XML_to_X12.html
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
    Details on XI EDI adapter from seeburger
    SAP XI supports EDIFACT
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    SAP Adapters
    EDI with XI
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
    http://www.seeburger.com
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    Regards,
    Nithiyanandam

  • 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>

  • Any one know about EDI interfaces..

    Hi,
    i don't know about EDI knowledge...any one help me out about EDI interfaces..
    thanks,
    rajesh

    HI
    EDI:
    An inter-company, application-to-application communication of data in standard format for business transactions, Electronic Data Interchange (EDI) is a set of standards for structuring information that is to be electronically exchanged between and within businesses, organizations, government entities and other groups. The standards describe structures that emulate documents
    Refer the below links for furtehr assistance on EDI
    https://www.sdn.sap.com/irj/sdn/advancedsearch?query=edi+interfaces&cat=sdn_all
    http://www.tradanet.intnet.mu/Tutorial/EDItutorial.htm
    http://www.tradanet.intnet.mu/Tutorial/EdiTutIx.htm
    http://www.icc.net/en_US/oc/icc.net/Resources/EDITutorial/
    http://www.edi-solution-info.com/
    Handling EDI interfaces using Seeburger BIC modules
    SAP XI supports EDIFACT
    How to get started using Conversion Agent from Itemfield
    More on the SAP Conversion Agent by Itemfield
    http://www.stylusstudio.com/edi/XML_to_X12.html
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
    Details on XI EDI adapter from seeburger
    SAP XI supports EDIFACT
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    SAP Adapters
    EDI with XI
    http://www.seeburger.com
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
    http://www.seeburger.com
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    EDI Adapter by SeeBurger
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/206e2b65-2ca8-2a10-edad-f2d1391644cb
    B2B(EDI) Integration using SAP Netweaver XI and Seeburger AS2 Adapter
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00f9cdf5-d812-2a10-03b4-aff3bbf792bf
    Integrating XI with SeeBurger
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
    AS2 vs OFTPS:
    AS2 & OFTPS
    EDIFACT to XML - Stylus Studio Solution  tool 4 EDI
    cheers

  • How can I use Seeburger java functions on SAP XI's user defined functions?

    Hi All,
    As my title implies; how can I use Seeburger java functions on SAP XI's user defined functions?  I've tried searching over the net in tutorials regarding this topic but I failed to find one; can someone provide me information regarding my question? thanks very much.
    best regards,
    Mike

    Hi Mike !
    You should check your documentation about which java classes you need to reference in the "import" section of your UDF. And also deploy the java classes into the java stack or include them as a imported archive in integration repository...it should be stated in the seeburger documentation.
    What kind of functions are you trying to use?
    Regards,
    Matias.

  • SAP XI Seeburger and X.400 Adpater

    Hello,
    We are trying to implement Seeburger X.400 Adapter in our XI 3.0 landscape for the first time.
    I went through Seeburgers config documentation and did all the setup and still getting errors. Not sure what I missed.
    At the log it seems to be complaining about "Resource". I did create a logical resource and assigned it to the channels.
    Following error is what I see in Comm.Channel Monitoring for both Sender and Receiver Channels:
    2009/04/21 - 14:45:34:368 Retryable fault in 'Channel:CC_NL_Receiver_Test'. Description: P7 error occured! Details: trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet. [4/21/09 2:44 PM]
    Error type: trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet. >> Error date: 4/21/09 2:45 PM >> Description: : trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet. [4/21/09 2:45 PM]
    Following is the error log I see in the log files (seeburger-x400p7-readable.2.trc):
    Apr 21, 2009 3:21:47 PM    com.seeburger.p7.statemachine.TransportLayer.disconnect()                                                                                [SAPEngine_Application_Thread[impl:3]_20] # Error # Error while disconnecting! The transport layer is not connected.
    Apr 21, 2009 3:21:47 PM    com.seeburger.p7.MessageStore.bind()                                                                                [SAPEngine_Application_Thread[impl:3]_20] # Error # Failed to establish a connection. Caused by: com.seeburger.p7.exceptions.P7ConnectException: connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet.
         at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:262)
         at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:138)
         at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:553)
         at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:157)
         at com.seeburger.p7.statemachine.serviceelements.AssociationControl.associate(AssociationControl.java:132)
         at com.seeburger.p7.statemachine.serviceelements.RemoteOperations.bind(RemoteOperations.java:98)
         at com.seeburger.p7.statemachine.serviceelements.Bind.invoke(Bind.java:76)
         at com.seeburger.p7.MessageStore.bind(MessageStore.java:366)
         at com.seeburger.p7.orders.P7Order.run(P7Order.java:81)
         at com.seeburger.p7.P7Processor.execute(P7Processor.java:241)
         at com.seeburger.frame.core.FrameWorkListener.syncNewData(FrameWorkListener.java:429)
         at com.seeburger.xi.connector.fw.SynchronousTaskExecutor.executeTask(SynchronousTaskExecutor.java:40)
         at com.seeburger.xi.connector.queue.QueueProcessorImpl.doInboundTransmission(QueueProcessorImpl.java:1181)
         at com.seeburger.xi.connector.queue.QueueProcessorImpl.process(QueueProcessorImpl.java:585)
         at com.seeburger.xi.connector.queue.QueueProcessorImpl.run(QueueProcessorImpl.java:227)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Apr 21, 2009 3:21:47 PM    com.seeburger.p7.P7Processor.handleP7Exception()                                                                                [SAPEngine_Application_Thread[impl:3]_20] # Error # trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isnt connected yet. Caused by: com.seeburger.p7.exceptions.P7Exception: trying to open a connection --> connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet.
         at com.seeburger.p7.MessageStore.bind(MessageStore.java:379)
         at com.seeburger.p7.orders.P7Order.run(P7Order.java:81)
         at com.seeburger.p7.P7Processor.execute(P7Processor.java:241)
         at com.seeburger.frame.core.FrameWorkListener.syncNewData(FrameWorkListener.java:429)
         at com.seeburger.xi.connector.fw.SynchronousTaskExecutor.executeTask(SynchronousTaskExecutor.java:40)
         at com.seeburger.xi.connector.queue.QueueProcessorImpl.doInboundTransmission(QueueProcessorImpl.java:1181)
         at com.seeburger.xi.connector.queue.QueueProcessorImpl.process(QueueProcessorImpl.java:585)
         at com.seeburger.xi.connector.queue.QueueProcessorImpl.run(QueueProcessorImpl.java:227)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: com.seeburger.p7.exceptions.P7ConnectException: connecting to remote session service --> com.seeburger.p7.exceptions.P7ConnectException: writing to network --> The transport layer isn't connected yet.
         at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:262)
         at com.seeburger.p7.statemachine.SessionLayer.connect(SessionLayer.java:138)
         at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:553)
         at com.seeburger.p7.statemachine.PresentationLayer.connect(PresentationLayer.java:157)
         at com.seeburger.p7.statemachine.serviceelements.AssociationControl.associate(AssociationControl.java:132)
         at com.seeburger.p7.statemachine.serviceelements.RemoteOperations.bind(RemoteOperations.java:98)
         at com.seeburger.p7.statemachine.serviceelements.Bind.invoke(Bind.java:76)
         at com.seeburger.p7.MessageStore.bind(MessageStore.java:366)
         ... 11 more
    Apr 21, 2009 3:21:47 PM    com.seeburger.xi.connector.fw.XICommunicator.reservationReleased(String)                                                                               [SAPEngine_Application_Thread[impl:3]_27] # Error # Error while releasing resource in resource-management:Cannot create reservation, reason: Cannot find reservation with id X400-Seeburger49; affected object : null
    Thanks in advance for your help,
    Sumant.

    Hi Prateek,
    Thanks for your quick response.
    As you said, there was a reservation entry and I deleted it. But still having the same issue.
    Do you know what this error means. I see this in the comm.channel monitor:
    Alert: Polling failed, caused by: Task final state is RETRY or ERROR [4/21/09 3:45 PM]
    2009/04/21 - 15:45:16:341 Retryable fault in 'Channel:CC_PollingX400'.
    Description: P7 error occured!  Details:
    trying to open a connection -->
    connecting to remote session service -->
    com.seeburger.p7.exceptions.P7ConnectException: writing to network -->
    The transport layer isn't connected yet. [4/21/09 3:44 PM]
    Error type:
    trying to open a connection -->
    connecting to remote session service -->
    com.seeburger.p7.exceptions.P7ConnectException: writing to network -->
    The transport layer isn't connected yet.
    >> Error date: 4/21/09 3:45 PM
    >> Description: : trying to open a connection -->
    connecting to remote session service -->
    com.seeburger.p7.exceptions.P7ConnectException: writing to network -->
    The transport layer isn't connected yet. [4/21/09 3:45 PM]
    Regards,
    Sumant.

  • Seeburger FTP Adapter And SAP PI 7.1

    Hi Everyone,
    Just a few questions about Seeburger FTP adapter please. Bit of background for clarity, we are doing an implementation using Seeburger FTP and sap PI 7.1 picking up EDIFACT (Orders) and returning (DESADV, ORDERSP, INVOICES). However we are not using any BIC, using another tool for EDIFACT -> EDIFACT-XML conversion (conversion agent) and in-house mapping development using graphical mapping.
    So couple of things which I haven't been able to figure out from the standard documentation for Seeburger FTP adapter:
    1) First is the functional ACK which we are meant to send back to the VAN is that a STANDARD FUNCTIONALITY with Seeburger FTP adapter?
    2) Because we are receiving a mix bag EDIFACT interchange on the way IN, I need to split messages accordingly and pass them on to the relevant channels and mappings. By using the standard module Splitter can I achieve that?
    3) Lastly some of the standard validations which are applicable to EDIFACT are they supported within the FTP adapter automatically? e.g. Counting number of messages in one interchange etc.
    Any help in this regard will be really great.
    regards

    Now a Good news.
    If you are using Seeburger version 2.1 (which you should be as you want it for PI 7.1), then there is an Internal Classifier and Split option for FTP adapter. You just need to tick checkbox "Use built-in splitting" and you are done. Then I believe there won't be any need for considering all these problems. The earlier version of Seeburger with PI 7.0 doesn't have such option and that could be the reason you haven't received any appropriate response yet.
    Still I will reply all your questions considering that "your case is of PI 7.0". -> remember PI 7.0
    >>even with just splitter we should be able to break it up?????? or am I wrong in thinking this?
    No. You even need BIC or an equivalent custom module for achieving this.
    >>I can't visualize where to handle the overall message count in one Interchange any suggestions?
    You need to write an adapter module for this. Not sure about the code but this module has to be added before the split happens.
    >> seeburger ftp adapter it does talk about a lot of reports which are available on sender/reciever actions. e.g. delivered, despatched etc. Are these reports not essentially ACKs?
    These reports are the ones used at the receiver side for getting the ACKs from the receiver. Your requirement is at present for sender scenario.
    Regards,
    Prateek

  • How to import seeburger adapter and mdm adapter in sap pi 7.3

    Hi all,
    how to import seeburger adapter and mdm adapter in sap pi 7.3

    Hello
    To import the Seeburger adapters, follow the instructions in the Master Installation guide and the individual guides for each of the adapters. These are available with the Seeburger software downloads.
    Regarding the MDM adapter, this is the wrong forum for that question. Try the MDM forum (but first, try searching the forum as this is a very basic question).
    Regards
    Mark

  • SAP GTS------- SAPPI with Seeburger BIC----- ATLAS using with SAP PI

    Hi All,
    I have scenario this SAP GTS----->SAPPI with Seeburger BIC--->ATLAS(German customs system)
    1)Inbound flow: SAP GTS will send the customs declaration message to ATLAS(German customs system)
    2)outbound flow: response messages from ATLAS(German customs system) approved the customs declaration message and send to SAP GTS
    How to achieve using with SAP PI with Seeburger modules. What are adapter is required for this scenario.
    Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send to Atlas systeam.
    For mapping  Source is Idoc (CCECUS02) and Target is EDIFACT(CUSDEC_UN_D96B).
    Regards,
    Ramesh

    >
    Ramesh Gulipalli wrote:
    > Hi All,
    >
    > I have scenario this SAP GTS----->SAPPI with Seeburger BIC--->ATLAS(German customs system)
    >
    > 1)Inbound flow: SAP GTS will send the customs declaration message to ATLAS(German customs system)
    > 2)outbound flow: response messages from ATLAS(German customs system) approved the customs declaration message and send to SAP GTS
    >
    > How to achieve using with SAP PI with Seeburger modules. What are adapter is required for this scenario.
    >
    > Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send to Atlas systeam.
    >
    > For mapping  Source is Idoc (CCECUS02) and Target is EDIFACT(CUSDEC_UN_D96B).
    >
    > Regards,
    > Ramesh
    > .
    for converting an XML to EDI or vice versa you can use the seeburger adapter.
    http://www.seeburger.com/xi-pi-adapters/

  • Seeburger Adapter - SAP PI

    Hi Experts,
    I am doing quite a few scenarios reagrding Seeburger Adapters but I am very new to it. I tried searching the Net but could not get satisfying blogs regarding it for a noviced person.
    Can you please provide me with suitable blogs so that I can learn it and apply it in working.
    Regards,
    Aniruddha

    Hi,
    Did you checked the below blog of mine..
    Wanna implement seeburger for EDI -find the booster
    good luck..
    HTH
    Rajesh

  • How can I generate IDOC(WPUUMS) from XML file in POSDM or in SAP Retail

    Hallo Retail expert,
                                I have following scenario,
    I have Retail Store who send me their daily sales report through Wincor Nixdorf Point of sale. There i am using standard POSLOG2 to SEEBURGER(its a middleware which act as Converter) xml format and then i post that data first in POSDM and then with BAPI i transfer or book that data to SAP Retail.
    Above is the one scenario which is working.
    This is the Second scenario.......
    I have some external Retail store, they dont have Wincor Nixdorf POS, so they send me their Sales Report through SEEBURGER(its a middle Hardware which act as Converter) and SEEBURGER Convert that Sales data to XML format. My question is....
    How can i upload or Convert a XML File into IDOC (WPUUMS)in SAP or in POSDM?
    any new suggestion are welcome.
    Thank you all in advance.
    regards,
    Niel

    Hi,
    1. To get the required XML Schema, use transaction code WE60 to go to the IDoc documentation -> enter the IDoc type you want to use (WPUUMS01). Flag control and data record. Then display the XSD by choosing Documentation -> XML Schema from the menue bar. Now you can donwload the XSD for usage in Seeburger.
    2. Create your mapping from the POS format into the IDoc XML format in Seeburger.
    3. Create an XML File Port in ERP or POS DM using transaction code WE21.
    3. To inbound the XML file from Seeburger into POS DM or SAP Retail Seeburger should trigger the function module EDI_DATA_INCOMING. Parameters for this FM are the Pathname to the XML file and the Portname you just created. Based on the port name the FM can derive the port type xml and the data will be handled as XML data.
    Regards Carsten

  • Issue with JMS Receiver Comm. Channel using Seeburger AttribMapper

    Hello,
    I'm using a JMS_RECEIVER Comm. Channel on which the Seeburger AttribMapper is configured (I need to use the DCJMSCorreleationID dynamic attribute).
    In the module tab, I added a new module:
    Module Name Module Type Module Key
    localejbs/Seeburger/AttribMapper Local Enterprise Bean map
    And I added the following parameter:
    Module Key Parameter Name Parameter Value
    map http://sap.com/xi/XI/System/JMS/DCJMSCorreleationID "TEST"
    When processing a message, I get the following error on the Communication Channel Monitoring:
    Message processing failed. Cause: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of AttribMapper.
    Does anyone has an idea on how to fix this problem?
    Thanks for your help!
    Benoit

    HI,
    Refer the discussion of
    Setting DCJMSCorreleationID in JMS RECEIVER using Seeburger AttribMapper
    Dynamic subject in AS2 receiver
    Thanks
    Swarup

  • [SAP XI] EDI orders posting job to SAP R/3

    Hi everyone!
    I would like to know if SAP XI has the capability to directly post EDI orders in SAP R/3 wherein IDocs are placed. If yes, how? (Please describe the process in detail)
    In normal EDI implementation (AI, 3rd party translator used), batchjobs are created to be able to post EDI orders. The AI/3rd party translator are sending the IDocs after conversion from customer format order file to the specified UNIX directory in SAP and batchjobs will post these as EDI orders that can be viewed in WE02/WE05.
    In SAP XI direct connection case, all IDocs received are automatically posted in SAP R/3 without having a batchjob executing this. However, orders are not successfully posted as there is an authorization issue** (user/system/technology posting EDI orders are not allowed to create an EDI order) so we need to determine which user/system/technology are executing the job (posting of IDocs to an EDI order).
    Please advise. Thank you very much!
    Fred

    Hi,
    U can do the send EDI data into SAP using third party tool or adapter(Seeburger) or by using the conversion agant.
    U need to have the XSD for the EDI structure and EDI data should be flat file.
    Check some links on Conversionagant and Seeburger.
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    SAP Adapters
    EDI with XI
    http://www.seeburger.com
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
    http://www.seeburger.com
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
    http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
    http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
    http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
    http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
    http://help.sap.com/saphelp_nw04/helpdata/en/43/6d95e0ac846fcbe10000000a1553f6/CMGetStart.pdf
    http://help.sap.com/saphelp_nw04/helpdata/en/43/4c38c4cf105f85e10000000a1553f6/content.htm
    /people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
    /people/alexander.bundschuh/blog/2006/03/14/integrate-sap-conversion-agent-by-itemfield-with-sap-xi
    /people/paul.medaille/blog/2005/11/18/conversion-agent-a-free-lunch
    /people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
    Regards,
    Phani
    Reward points if Helpful

  • SFTP to AS2(non-seeburger): How to get sender Filename to be used in AS2 Receiver Channel

    Hi Experts,
    I have this scenario,
    SFTP > Process Orchestration > AS2(non-seeburger)
    My interface is not using Message Mapping and I want to use the source Filename as my Receiver Filename.
    Sender
    orders_1234 - source filename
    Receiver
    orders_1234 - target filename
    How to do it in Process Orchestration without Seeburger.
    Thanks and Best Regards,
               Orlan

    Hi Orlan - So are you using SAP AS2 adapter?
    If you so i think you can make use of dynamic configuration bean.
    Unknown use case of DynamicConfigurationBean: Store file name to JMS header without mapping
    Enable adapter specific attributes in sender SFTP channel and in the receiver AS2 channel use the above module to swap the dynamic attributes.
    Dynamic attributes
    http://sap.com/xi/XI/System/SFTP ,FileName 
    http://sap.com/xi/XI/AS2/AS2:  AS2Filename

  • Variable substitution error while using Seeburger module parameter

    Hi Freinds,
    I would like to use the variable substitution in a receiver file adapter to add the invoice no.
    (which is contained in the XML file) to the target filename.
    In addition I have to convert the XML file to an X12 EDI format using the seeburger module "localejbs/CallBicXIRaBean".
    As soon as this entry is made in the modules the following error message occurs:
    "com.sap.aii.adapter.file.configuration.DynamicConfigurationException:
    Error during variable substitution: com.sap.aii.adapter.file.varsubst.VariableDataSourceException:
    Caught SAXException while parsing XML payload: Fatal Error: com.sap.engine.lib.xml.parser.ParserException:
    XMLParser: No data allowed here: (hex) 53, 4f, 48(:main:, row:1, col:3)"
    My problem is that the conversion from XML to X12 EDI is done before the variable substitution is started.
    That`s why the reference for the variable is no longer valid as the file is already converted to a X12 EDI (=flatfile) format.
    If I disable one of the two steps (either 1:1-mapping or variable substitution) the other step runs properly.
    Has anybody an idea how to solve this topic?
    Is it possible to specify the variable substitution as module?
    If this is possible I could solve it by just reordering the two steps in the module chain.
    Regards
    Venkatesh

    Use Dynamic Configuration Bean to set this value. You have to use this well before "localejbs/CallBicXIRaBean".
    Check SAP note : 974481 for more information.
    Blog: [/people/jin.shin/blog/2007/04/27/sap-netweaver-xi-variable-substitution-with-adapter-specific-message-attributes-via-dynamicconfigurationbean|/people/jin.shin/blog/2007/04/27/sap-netweaver-xi-variable-substitution-with-adapter-specific-message-attributes-via-dynamicconfigurationbean]
    Second Approach if the above approach doesnt work.
    Use Dynamic Configuration concept in UDF to set the filename under message Mapping.
    Thanks,
    - Gujjeti.
    Edited by: Praveen Gujjeti on Feb 25, 2009 11:25 AM

Maybe you are looking for

  • T400, Backslash appearing as #, all the regional settings are correct though

    hi I have a T400 laptop, its regional settings are set for english (ireland) and i have also tried the Irish(ireland) settings, but for what ever reason, the Backslash, which is located just above the "enter" key, when pressed brings back the hash# s

  • Lost bookmark button and favorites tab. How do I get them back?

    I had problems with my NEW Dell computer and had to have everything removed and had to start over again. (not by me, by a professional) After all was done and my info was replaced, my favorites and bookmark button disappeared. I called Dell and had a

  • Runtime error during video calls - "pure virtual f...

    When I video call someone, about 10-30 seconds into the call my video freezes and subsequently vanishes on the other end of the call, and I get a popup error titled "Microsoft Visual C++ Runtime Library" with the body: "Runtime Error! Program: C:\Pro

  • Field "Rejection For Reason" is in disble status at sales order item level

    Hi, I am trying to reject the items in a sales order by entering "Rejection Reason" at item level. But the problem is, this field is in disable status in WEB UI only for my user. However, If I use any other user, it is in enable status. Could you ple

  • Bundle Import in CC&B - need help

    Hi, I am trying to create Bundle import to import the configurations of BO, ZONE, Portal zone etc,. When I click on save, I am getting an Java.lang.ClassNotFoundExeception : CIPTUSEF and looks like this is coming base. I am doing this on the upgraded