Enveloping using Seeburger adapter

For the ones using Seeburger adapters...
How are you coding you envelope tempate (ISA/GS envelope template) using Seeburger adapter as EDI tool. Do you code each and every one of your transaction type / trading partner?
And how do you, for example, send or configure 1 transaction per envelop used for 820s or 100 transactions per envelop for 814s?
Can one you tell how are accomplishing these functions?
Thank you,
Pam

reposting....
Thanks, Pam

Similar Messages

  • EDI Integration---Using Seeburger Adapter

    Hi All,
    I have a below requirement.
    EDI----->XI--
    >SAP and vice versa.
    I am new to EDI integration,i would like to know the procedure steps to do the above scenario.
    Thanks in advance,
    AVR

    Hi,
    How you want to communicate with the EDI system... If it is using AS2 adapter, then you need to purchase it from seeburger and configure it in the sender side and receiver side it'll be Idoc adapter. And in the ESR you need to import the xsd of EDI document under external definitions and map it to the idoc.Please refer the below links it may help you.
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22
    http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=221354005
    http://wiki.sdn.sap.com/wiki/display/XI/SeeburgerSuiteforSAPPI
    Handling EDI interfaces using Seeburger BIC modules
    Regards,
    Priyanka

  • Error in Oubound message using Seeburger Adapter

    Hi,
    I'm getting this error on the Adapter engine when trying to generate an outbound EDI message with Seeburger adapter:
    2007-01-24 13:33:29      Error      Unable to forward message to JCA adapter. Reason:
    Fatal exception: com.seeburger.xi.connector.queue.QueueEntryRejectedException:
    Entry rejected due to error in resource management: null, Entry rejected due to
    error in resource management: null     
    2007-01-24 13:33:29      Error      MP: exception caught with cause
    javax.resource.ResourceException: Fatal exception:
    com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
    to error in resource management: null, Entry rejected due to error in resource
    management: null     
    2007-01-24 13:33:29      Error      Exception caught by adapter framework: Fatal
    exception: com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry
    rejected due to error in resource management: null, Entry rejected due to error
    in resource management: null     
    2007-01-24 13:33:29      Error      Delivery of the message to the application using
    connection File_http://sap.com/xi/XI/System failed, due to:
    com.sap.aii.af.ra.ms.api.RecoverableException: Fatal exception:
    com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
    to error in resource management: null, Entry rejected due to error in resource
    management: null: javax.resource.ResourceException: Fatal exception:
    com.seeburger.xi.connector.queue.QueueEntryRejectedException: Entry rejected due
    to error in resource management: null, Entry rejected due to error in resource
    management: null.     
    Any ideas?
    Rgds,
    Yves

    Yves,
    I think there is some problem in invoking the seeburger adapter. Have you installed the adapter? Also after installing you have to import the metadata. Check this document for further help:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6dc02f5d-0601-0010-cd9d-f4ff9a7e8c33
    ---Satish

  • Without using Seeburger Adapter can we convert EDI 864 TC to XML

    Hello Friends,
                            Can we convert 864 Transaction code (Text Message) to XML with out an External adapter like Seeburger Adapter? I mean can we write a code in JAVA for conversion? If so, what should i use in that Java code?

    Hi
    These blog can help u....
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    /people/srinivas.vanamala2/blog/2006/12/11/edi-basics
    Already discussed thread:
    EDI Conversion
    Re: Seeburger Splitter adapter!!
    Regards
    Santhosh
    Remember to set the thread to solved when you have received a solution

  • EDI on XI without using SeeBurger Adapter

    We're about to begin a project to do EDI on XI. We'd like to know about all options we have in addition to just using the recommended SeeBurger EDI adapter. We have a 3rd party middleware tool we could use as well. We'd like to leverage the knowledge we already have in this product. Let me know if this is a feasible architecture.
    - XI handles all the SAP communication.
    - 3rd party middleware vendor tool handles all EDI mappings, and also handles all communication with partners via AS2, FTP, etc.
    - Communication between XI and 3rd party middleware is accomplished thru SOAP/web services or direct HTTP calls.
    Under this architecture, i'm not exactly sure what XI buys us as we could communicate directly to SAP without XI but lets leave it as is for now.
    Is this a feasible option?? Assume the extra development of the maps is not a major consideration since our business requirements would cause us to modify any out of the box mappings SeeBurger would provide anyway.
    Has anyone else implemented EDI via an adapter outside of SeeBurger's??

    hello
    ur architecture seems to be ok becuase as of now i have'nt heard of XI supporting AS2 features..i guess u can configure a partner in XI in configuration builder and then  create a communication channel for the same with the transport protocol as HTTP or SOAP.u can apply security over here by configuring necessary certificates..
    regarding XI usage goes what third party middleware ur using..check whether it offers flexible mapping capabilities like XI (with GUI maps, XSLT or Java maps etc) or BPM capabilities (which u may require in future) and message persistence capabilities etc..
    also now XI is free with NetWeaver 2004s licence.
    Regards
    Rajeev

  • Additional Attributes in AS2 Header using Seeburger Adapter

    Hello,
    our business partner required that we include some additional attributes in the AS2 mime header that are used for internal routing purposes (in addition to the AS2 ID).
    Attributes for example include a submissionType etc. Is it somehow possible to add this attributes? According to the documentation I can only add dynamicAttributes for standard fields, such as content type etc.
    Thank you for your support.
    Edited by: Florian Guppenberger on Oct 6, 2009 7:14 PM

    Hi,
    I think you can.. but not recommended to modify standard Adapters.
    Check the below blog.
    http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417500)ID0328214750DB00705897531357746266End?blog=/pub/wlg/4645
    Why dont you use Message subject or Content type ?
    Thanks
    Deepthi.

  • EDI SEEBurger Adapter

    We are evaluating  XI for ANSI X12 EDI , Have some  EDI Quesitions using SEEBurger Adapter.
    1) Does SEEBurger Adpater has ANSI X12 Enveloping and De-Enveloping capabilities ???  If Yes,how this is configured /Developed.
    2) Does SEEBurger Adapter has capability of generating sequential ISA control numbers by Trading Partner ??? If Yes,how this is configured /Developed.
    3) Can It perform  EDI Structure validation based on the  EDI standard  rules (For eg: Looping structures, Element qualifier restriction list .....)

    Hi,
    Seeburger is a tool which will conver any type of standard EDI format into XML.
    All standard EDi mappings are predefined in seburger,we have to install in XI Server and use that standard mappings.
    Check this links
    SEEBURGER
    http://www.seeburger.com
    Please see the below blogs
    /people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
    /people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
    /people/paul.medaille/blog/2005/11/17/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
    Check this for Conversions-
    /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://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
    Regards,
    Phani
    Reward Points if Helpful

  • Bsi mapping in seeburger adapter

    hi experts,
    i want to know about bic mapping in idoc to edi scenarios in which i am using seeburger adapter.please help me and provide me some documentation.

    Hi,
    BIC is mapping tool which converts EDIFACT to EDI_XML.
    You will be accepting EDI flat file i.e. csv file and using BIC you will map it 1:1 mapping ....this flat file will be converted into EDI_XML after mapping.
    Check this for Conversions-
    /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/AS2_General_Overview.pdf
    SAP Adapters
    EDI with XI
    http://www.seeburger.com
    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://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
    Regards,
    Akshay Jamgaonkar.
    Don't forget to reward points.
    Message was edited by:
            Akshay Jamgaonkar

  • EDI TRADACOM through Seeburger Adapter into PI

    Has anybody configured communication channel in PI using Seeburger Adapter to convert EDI TRADACOM into xml ?
    Is there a useful tutorial to have a look at ?

    >>Has anybody configured communication channel in PI using Seeburger Adapter to convert EDI TRADACOM into xml ?
    Yes
    >>Is there a useful tutorial to have a look at ?
    Well, there is nothing specific avauilable for TRADACOM. TRADACOM is just a type of format as we have EDIFACT OR X12. You can search for EDIFACT related articles/blogs on SCN (there are many). The only thing you then need is to use TRADACOM related mapping name in BIC module wherever you see EDIFACT mapping name.
    One more thing, for using TRADACOM, there is a separate licence where Seeburger provides the TRADACOM related SWC with all the formats. So talk to Seeburger about this as well.
    Regards,
    Prateek Raj Srivastava

  • EDI using seeburger

    Hi Friends,
    Recently I have worked on EDI scenarios using Seeburger adapter.
    there are so many in and outs for EDI / Seeburger ,
    out of that I need some inputs on finalization of  error handling framework for EDI implementation using Seeburger.
    Please give your thoughts on error handling in EDI /Seeburger.

    Beside my two cents above, your question can't really be answered without defining some business rules around it. So for the sake of discussion i am going to make up a scenario. And the cycle upto Despatch advice.
    So business rules are:
    1) Over supply not do able. Which implicitly means no manual changes in the incoming ORDER.
    2) Under supply allowed as in the real world this will always happen as at the time of ORDER, the supplier side could be out of stock on a particular item ordered.
    Message Cycle:
    1) Order (Inbound)
    2) Order confirmation (Outbound)
    3) Dispatch advice (outbound) - DESADV
    So briefly speaking based on how the Order confirmation is setup (based on business guidelines) will determine what we are suppose to handle.
    If order confirmation is allowed to change the Order i.e. If no stock available and hence line item rejected it would update the original Order in the sending partners system hence no issues at the time of desadv (this is situation one). However if due to some human error more stock shipped than agreed upon in the DESADV then 'excess stock' process can be invoked and based on business rule it can be returned e.g.. This wouldn't require any message amendment. However if short delivered then what was agreed in DESADV partner can always request amends and new DESADV (corrected) can be issued.
    I will stop here; I am hoping that i am making sense above? Will continue if i am making sense and then we can talk about technical side for addressing different situations.
    regards,

  • Sender / Receiver ID mapping for EDI interfaces and Type of seeburger adapt

    We need to set up a interface using Seeburger adapter for Purchase order IDOC to 850 EDI mapping.. After reading from SDN,
    1) We can use the standard mapping in BIC MD to do E2X and X2E mapping..
    2) We can use any of the AS2, EDI generic adapter, Seeburger FTP adapter or Seeburger SFTP adapter...
    How do we decide which adapters should be chosen? I can see that it makes sense to use SFTP adapter or AS2 adapter for security...
    Also how do we map Sender and Receiver IDs on the EDI message.. Should this be hardcoded as part of mapping or is there any facility in seeburger adapter to do this? I saw some references to Party Identifiers and not sure how it is used in setting up Sender/ Receiver ID
    Also the graphical mapping to convert IDOC XML to EDI XML, Do we have standard mapping defined or do we need to create our own graphical mapping.

    Hi Kris,
    I had worked in the somehow same scenario, It was IDOC to EDIFACT file.
    I can give you few clues which might be helpful
    In BIC MD you have to create your own mapping if the standard mapping is not available (First check all the standard mappings in BIC). For your reference you need X2E mapping, as your scenario is IDOC to 850 EDI.
    "the graphical mapping to convert IDOC XML to EDI XML, Do we have standard mapping defined or do we need to create our own graphical mapping."
    In graphical mapping i created my own mapping, Seeburger has given some sample mappings you can check those for your reference (SEEBURGER_GENERIC_EDI software component). Mostly you have to create your own. You need a document from your functional consultant so that you are able to map correct fields and constants.
    "how do we map Sender and Receiver IDs on the EDI message.. Should this be hardcoded as part of mapping or is there any facility in seeburger adapter to do this? I saw some references to Party Identifiers and not sure how it is used in setting up Sender/ Receiver ID"
    This has been generally hardcoded in message mapping (In my case i hardcoded). If any of ur IDOC field contains that data you can map that field. But better Idea is ask your functional expert.
    "How do we decide which adapters should be chosen? I can see that it makes sense to use SFTP adapter or AS2 adapter for security... "
    You can choose adapter according to your requirement. In my case i used File adapter as i have to create file in PI server only. My suggestion you can use SFTP for seeburger
    Hope these points are helpfu for u
    Regards,
    Shradha

  • Re:  Hi friends How to use sseeburger adapter in SAP PI

    I am newly in sap pi.
    can any one explain Seeburger adapter briefly

    Hi Ranga,
        Welcome to SCN.
    As you are new around here, i suggest you to please search the forum before posting your question.
    To answer to your question, Seeburger is the name of the company which provides its set of adapters for SAP PI.
    I assume that you are talking about the Seerburger AS2 adapter, as it is the mostly used seeburger adapter.
    The Seeburger AS2 adapter is capable of translating an EDIFACT/ ANSIX12 message/file into a format that is understood by PI and vice versa.
    It is also capable of handling the AS2 transport protocol (EDI Over internet).
    Best Regards,
    Ravi

  • Problem Encountered in JMS adapter using SEEBURGER module

    While testing the receiver JMS adapter for XML to EDI conversion using Seeburger module, I am facing errors.
    <b>1. The error encountered is</b> :
    Error while processing message '4720bc32-2dfc-03d8-0000-00000a2050d3';  detailed error description: java.lang.NullPointerException at com.sap.aii.adapter.jms.core.connector.SendContextImpl.send(SendContextImpl.java:43) ...
    <u>SEEBURGER BICXIADAPTER</u> --- Conversion of synchronous request from module chain ended with errors ---Error: [Error:ID=2061;LEVEL=1] XMLDocReader moveNext(): Cannot move to next trigger : Error in line 1: <u>XML file should begin with white spaces or <. (Found char :U(Hex :85</u>). DESCRIPTION: XMLDocReader Exception: Not able to move to next trigger [not specified] - trigger may not right set.
    <b>2. The targer PAYMUL xml is as follows</b> :
    ( At receiver channel, the above should be converted to EDI-Paymul using the Seeburger Module)
    <u>PAYMUL XML</u>
      <?xml version="1.0" encoding="UTF-8" ?>
    - <LIST>
    - <S_UNA>
      <D_DELIMITER>:+.? '</D_DELIMITER>
      </S_UNA>
    - <S_UNB>
    - <C_S001>
      <D_0001>UNOA</D_0001>
      <D_0002>2</D_0002>
      </C_S001>
    - <C_S002>
      <D_0004>SAPDM</D_0004>
      <D_0007>ZZ</D_0007>
      </C_S002>
    - <C_S003>
      <D_0010>000000000000</D_0010>
      <D_0007>55</D_0007>
      </C_S003>
    - <C_S004>
      <D_0017>070201</D_0017>
      <D_0019>1150</D_0019>
      </C_S004>
      <D_0020>01945678912345</D_0020>
    - <S_UNH>
      <D_0062>1</D_0062>
    - <C_S009>
      <D_0065>PAYMUL</D_0065>
      <D_0052>D</D_0052>
      <D_0054>96A</D_0054>
      <D_0051>UN</D_0051>
      <D_0057>FUN01G</D_0057>
      </C_S009>
    - <S_BGM>
    - <C_C002>
      <D_1001>452</D_1001>
      </C_C002>
      <D_1004>01945678912345</D_1004>
      <D_1225>9</D_1225>
      </S_BGM>
    - <S_DTM>
    - <C_C507>
      <D_2005>137</D_2005>
      <D_2380>20070201</D_2380>
      <D_2379>102</D_2379>
      </C_C507>
      </S_DTM>
    - <G_SSG4>
    - <S_LIN>
      <D_1082>1</D_1082>
    - <S_DTM>
    - <C_C507>
      <D_2005>203</D_2005>
      <D_2380>20070201</D_2380>
      <D_2379>102</D_2379>
      </C_C507>
      </S_DTM>
    - <S_RFF>
    - <C_C506>
      <D_1153>ACK</D_1153>
      <D_1154>01945678912345</D_1154>
      </C_C506>
      </S_RFF>
    - <S_RFF>
    - <C_C506>
      <D_1153>AEK</D_1153>
      <D_1154>01945678912345</D_1154>
      </C_C506>
      </S_RFF>
    - <S_BUS>
      <D_3279>IR</D_3279>
    - <C_C551>
      <D_4383>UGI</D_4383>
      </C_C551>
      </S_BUS>
    - <G_SSG5>
    - <S_MOA>
    - <C_C516>
      <D_5025>9</D_5025>
      <D_5004>5000</D_5004>
      <D_6345>EUR</D_6345>
      </C_C516>
      </S_MOA>
      </G_SSG5>
    - <G_SSG6>
    - <S_FII>
      <D_3035>OR</D_3035>
    - <C_C078>
      <D_3194>ES921998500000000012</D_3194>
      <D_6345>EUR</D_6345>
      </C_C078>
    - <C_C088>
      <D_3433>ABNAES17000</D_3433>
      <D_1131>25</D_1131>
      <D_3055>5</D_3055>
      </C_C088>
      <D_3207>ES</D_3207>
      </S_FII>
      </G_SSG6>
    - <G_SSG7>
    - <S_NAD>
      <D_3035>OY</D_3035>
    - <C_C080>
      <D_3036>XYZ CORPORATION LTD</D_3036>
      </C_C080>
    - <C_C059>
      <D_3042>XX</D_3042>
      </C_C059>
      <D_3164>XX</D_3164>
      <D_3207>ES</D_3207>
      </S_NAD>
      </G_SSG7>
    - <G_SSG11>
    - <S_SEQ>
    - <C_C286>
      <D_1050>1</D_1050>
      </C_C286>
    - <S_MOA>
    - <C_C516>
      <D_5025>9</D_5025>
      <D_5004>5000</D_5004>
      <D_6345>EUR</D_6345>
      </C_C516>
      </S_MOA>
    - <S_DTM>
    - <C_C507>
      <D_2005>227</D_2005>
      <D_2380>2007-02-01</D_2380>
      <D_2379>102</D_2379>
      </C_C507>
      </S_DTM>
    - <S_RFF>
    - <C_C506>
      <D_1153>AIK</D_1153>
      <D_1154>01901234567890</D_1154>
      </C_C506>
      </S_RFF>
    - <S_RFF>
    - <C_C506>
      <D_1153>CR</D_1153>
      <D_1154>01901234567890</D_1154>
      </C_C506>
      </S_RFF>
    - <S_FCA>
      <D_4471>13</D_4471>
      </S_FCA>
    - <G_SSG12>
    - <S_FII>
      <D_3035>BF</D_3035>
    - <C_C078>
      <D_3194>AT921998500000000011</D_3194>
      <D_6345>EUR</D_6345>
      </C_C078>
    - <C_C088>
      <D_3433>ABNAAT14000</D_3433>
      <D_1131>25</D_1131>
      <D_3055>5</D_3055>
      </C_C088>
      <D_3207>ES</D_3207>
      </S_FII>
      </G_SSG12>
    - <G_SSG13>
    - <S_NAD>
      <D_3035>BE</D_3035>
    - <C_C080>
      <D_3036>ABC CORPORATION 1</D_3036>
      </C_C080>
    - <C_C059>
      <D_3042>XX</D_3042>
      </C_C059>
      <D_3164>XX</D_3164>
      <D_3207>ES</D_3207>
      </S_NAD>
      </G_SSG13>
    - <G_SSG16>
    - <S_PRC>
    - <C_C242>
      <D_7187>11</D_7187>
      </C_C242>
    - <S_FTX>
      <D_4451>PMD</D_4451>
    - <C_C108>
      <D_4440>SENDERPN1</D_4440>
      </C_C108>
      </S_FTX>
      </S_PRC>
      </G_SSG16>
      </S_SEQ>
      </G_SSG11>
      </S_LIN>
      </G_SSG4>
    - <S_CNT>
    - <C_C270>
      <D_6069>2</D_6069>
      <D_6066>1</D_6066>
      </C_C270>
      </S_CNT>
    - <S_UNT>
      <D_0074>1</D_0074>
      <D_0062>1</D_0062>
      </S_UNT>
      </S_UNH>
    - <S_UNZ>
      <D_0036>1</D_0036>
      <D_0020>01945678912345</D_0020>
      </S_UNZ>
      </S_UNB>
      </LIST>
    <b>3. The module parameters for Seeburger inputs :</b>
    ( In receiver communication channel)
    <b>Processing Sequence</b>
    localejbs/CallBicXIRaBean               Local Ent Bean     x2e_bic_paymul
    SAP XI JMS Adapter/ConvertMessageToBinary     Local Ent Bean     convert_XI2Bin
    SAP XI JMS Adapter/SendBinarytoXIJMSService     Local Ent Bean     
                    exit
    <b>Module Key</b>
    x2e_bic_paymul     destSourceMsg     MainDocument
    x2e_bic_paymul     destTargetMsg     MainDocument
    x2e_bic_paymul     logAttID          ConverterLog
    x2e_bic_paymul     mappingName     See_X2E_PAYMUL_UN_D96A
    x2e_bic_paymul     newLine          true
    x2e_bic_paymul     saveSourceMsg     XMLEDI

    Hi,
    Check Below links,
    /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
    Regards,
    Phani

  • How do we do File content conversion using SFTP SEEBURGER Adapter

    HI All,
              Can we do FCC using SFTP SEEBURGER adapter. If yes how?
    XIer

    Dynamic attributes are part of the XI message. They provide options for dynamical configuration of SFTP receiver channels (Outbound direction) using parameters that have been dynamically added or set by modules and mappings before the SFTP adapter. These attributes can be set using the Attribute Mapper module for example. Besides, the SFTP adapter dynamically adds specific parameters to the XI message on Inbound case, which can be used by the modules and mappings after SFTP adapter.
    Check also
    /people/william.li/blog/2006/04/18/dynamic-configuration-of-some-communication-channel-parameters-using-message-mapping
    /people/daniel.graversen/blog/2006/10/05/dynamic-configuration-in-adapter-modules
    Regards
    Naycho

  • AS2 system integration without using Seeburger AS2 adapter

    Hi, All:
    One of business partner need to have AS2 transport protocol to communicate with, my question is, can we integrate with business partner without going Seeburger AS2 adapter ?
    Thanks
    Liang

    I think that is not possible. If it were, we wouldn't need anymore the Seeburger adapter and could write our own modules...
    Here have a look at this.
    /people/prateek.srivastava3/blog/2009/08/01/seeburger--part-1--the-basics
    And this.
    https://websmp202.sap-ag.de/~sapidb/012006153200000124082007E/SAPXI30_AS2Adapter.pdf
    AS2 adapter
    Edited by: Arman Eker on Apr 7, 2010 5:19 PM

Maybe you are looking for