Generic EDI Adapters

Hi
Could you plz name some generic EDI Adapaters which work on EDI standards (ANSI X12 and EDIFACT)?? For example BIC Adapter is used to convert ANSI X12-XML Messages into ANSI X12 Messages. Similarly could you plz name some adapters which work on EDI standards ANSI X12 and EDIFACT ?
Thanks
Kumar

Ahmad,
Just for your information  ItemField is not a different company. Its already brought by SAP so it is SAP product only. When you buy the software you can buy this also from SAP but they will charge extra for this.
Kumar,
Also Iway have some EDI adapters. Please google them up.
Regards,
---Satish

Similar Messages

  • SEEBURGER AS2 and EDI adapters, PGP Avalanche adapter

    Hi,
    Kindly anybody can provide the information/links/documentation/PDFs on SEEBURGER AS2 and EDI adapters, PGP Avalanche adapter.
    Thanks in advance,
    Jogula Ramesh

    When u install SeeburgerBIC mapper on ur machine, the below location will contain all the required manuals..
    C:\Program Files\Seeburger\CPG EDI Adapter\manuals
    You can seach SDN weblogs for Seeburger Adapter details if u don't have the software..
    Below is the starting Seeburger Adapter Series weblogs..
    /people/prateek.srivastava3/blog/2009/08/01/seeburger--part-1--the-basics
    -SM

  • Integration Repository objects for EDI adapters

    Hi,
    We are currently evaluating EDI integration options, and I need some information.
    Does anybody know where I can find a list of Integration Repository (or any other) objects such as mappings, mapping templates, msg types, etc that are provided with the EDI adapters from Seeburger or iWay ?
    If you know where I could get my hands on some technical documentation of the adapters themselves, that would be great too!
    Thanks and Regards
    Manish

    hi,
    >>>>Does anybody know where I can find a list of Integration Repository (or any other) objects such as mappings, mapping templates, msg types, etc that are provided with the EDI adapters from Seeburger or iWay ?
    you get them if you buy the adapter
    >>>If you know where I could get my hands on some technical documentation of the adapters themselves, that would be great too!
    I have one presentation about the seeburger
    if you want check my e-mail in my business card
    and send me an e-mail
    I'll send you this presentation back
    Regards,
    michal

  • Generic power adapters

    Since the OEM power adapter for my new Zen Micro doesn't seem to be available any time soon, I'm thinking about getting one of the generic power adapters for it. Any one had experience with those, any recommendations? Thanks.

    I see that the Micro uses 000mA, and I am guessing its 5V too? If so the Dell Pocket DJ adapters will most likely work, given the similarity of the devices. And the chargers are rated exactly the same look exactly alike, just the DJ's are black....
    I haven't tried it because I dont know anyone with a Micro, but if someone wants to buy one.... You can get it <a href='http://accessories.dell.com/sna/ProductDetail.aspx?sku=30-5854&c=ca&category_id=686&cs=cadhs&l=en&s=dhs&page =productlisting.aspx' target=_blank>here[/url]Message Edited by DM on 06-02-2005 02:56 AM

  • Difference between Seeburger FTP and OFTP adapters

    hi,
    Can anybody tell me the difference between Seeburger FTP and OFTP adapters?
    On what basis should one make a business decision as to which adapter to go for?
    Kindly help urgently.
    Regards,
    Loveena

    Hi ! Loveena
    Seeburger EDI Adapter provides an EDI solution on internet via HTTP or AS2 to replace the expensive VAN. It provides some pre-built mappings for IDOC to ANSI X12(810,850,855,856 etc.,) and Idoc to EDIFACT(ORDERS,DESADV,INVOIC etc.,) and has the ability to build your own. These pre-defined mappings transform the IDOC-XML to EDI-XML format.
    Seeburger Adapters are used to Connect the applications which are using Message protocol/Transport protocol as CrossIndustry(payment), VAN, OFTP, AS2(EDIINT), Generic and EDI based applications.
    Re: Seeburger Adapter
    Reg seeburger seeburger
    installation
    https://forums.sdn.sap.com/click.jspa?searchID=2268965&messageID=3210111
    OFTP ist a communication protocol. This has nothing to do with the format you have to transfer.
    regards the format you have to clear at which standard you have to transfer the messages. This can be any EDI format. At OFTP area the standard are often VDA or ODETTE.
    You can create this messages using different EDI adapters (of course also the mendelson adapter ).
    Regards OFTP you need additional software which handle the transfer based on the OFTP standard. Mostly you also need an ISDN card for using this protocol.
    We can support you with this software for OFTP transport too.
    More info also available at http://www.mendelson-e-c.com/.
    have a look at the ACTIS OFTP Adapter
    Ref: http://www.actis.atosorigin.de/solutions/en/ACTIS_solutions/SAPXI.php
    refer this thread also
    When we need Seeburger AS2 & FTP?
    XI Seeburger adapters
    Adapter for OFTP?!
    Thanks !!

  • EDI ?

    Can someone advice me, How to integrate an EDI partner using XI3.0 . My requirement is to send/receive messages with partner systems by using the American National Standards Institute (ANSI) X-12 and Electronic Data Interchange for Administration, Commerce, and Trade (EDIFACT) standards.
    I understand that Seeburger has a Generic EDI adapter to acheive this. Is there any other way with the std set of adapters ? I also fails to understand the commn protocol to be used if there is an alternative, since am new to EDI.
    -Saravana

    Saravana,
    Your best bet would be to use an EDI adapter like Seeburger Adapter. There are many advantages out of which I am listing some below
    1) The mapping between IDOC and ANSI X12 for various industry segements are readily available from Seeburger. So you don't have to redo the mappings. The adapter also should build the interchanges (which are envolopes to your EDI message) taking out one more headache out of your way.
    2) EDI systems communicate either through a value added network or based on agreement, partners do communicate using secure FTP. Seeburger adapter has all these protocols available ready-made.
    I would suggest you to look in to the EDI adpater option instead of writing your own adapters.

  • Any EDI scenario example?

    Hi,
    Im in need of a edi scenario example, like a how-to guide.
    Any end to end scenario with EDI adapter like step by step is highly appreciated.
    Please help.

    Hi
    Available 3rd Party Adapters and Adapter Modules for SAP NetWeaver PI 7.1 provided by SAP via Reseller Agreement
    As in the past, SAP continues to rely also for SAP NetWeaver PI 7.1 on partners to provide connectivity solutions for other applications and certain industry standards. With regards to adapters and adapter modules SAP has currently reseller agreements with the companies Informatica, iWay, and SEEBURGER. The connectivity solutions that are covered by the reseller agreements are sold and delivered through SAP, and also technical support for these partner solutions is available via the SAP Support Portal.
    SEEBURGER
    From the company SEEBURGER all adapters that are covered by the reseller agreement between SAP and SEEBURGER are already certified for SAP NetWeaver PI 7.1; to be more specific, the following SEEBURGER adapters for SAP NetWeaver PI 7.1 that are covered by the reseller agreement are available:
    Technical EDI Adapters
    AS2 (EDIINT/HTTP(S))
    OFTP (OFTP / ISDN, OFTP / TCPIP)
    VAN Access (P7 / X.400, VAN FTP)
    Business EDI Adapters
    Generic EDI
    Protocol converter for OFTP / ISDN or VAN Access
    Data format converter for ANSI X12, EDIFACT
    Mapping templates for purchase order, invoice etc.
    Payment
    Protocol converter for OFTP / ISDN, VAN Access
    Data format converter for EDIFACT, SWIFT
    Mapping templates for payment orders, debit advice etc.
    Industry specific EDI Adapters
    Aerospace & Defense
    Automotive
    Chemicals
    Consumer Products
    High-Tech
    Paper
    Pharmaceutical
    Retail
    SAP NetWeaver Process Integration 7.1: Available Adapters and Adapter Modules
    Handling EDI interfaces using Seeburger BIC modules
    Handling EDI interfaces using Seeburger BIC modules
    Regards
    sandeep

  • Inbound EDI multiple customers using 1 partner profile

    I would think that it's possible to set up a single partner profile in WE20 through which you can process multiple idocs against multiple customers for order processing. Can anyone guide me on how to achieve this.
    Thanks, Mart

    Absolutely. You could have an EDI Partner called 'GENERIC' for example, and could use that to process inbound EDI Sales Orders. Obviously you would need an identifier to represent the correct Customer account, ideally this would be the Sold-to number. If it's not your Internal Sold-to, but another unique number, then you should be able to add mapping via transaction VOE4 to table EDPAR. I.e the Customers sends an external number 123 representing their Store Id, you map that back to your internal Customer Number. Only trouble with this is if two different Customers had the same external Id, as you would have no control over that. For our generic EDI Partners, the Customer Number is mandatory.
    Cheers, Paul.

  • Seeburger EDI adapter Vs Seeburger  BIC adapter

    hi,
    what is the difference between <b>Seeburger EDI adapter Vs Seeburger  BIC adapter</b>.any docs please.
    thank you,
    babu

    Hi,
    <i>Seeburger EDI adapter Vs Seeburger BIC adapter.</i>
    If your edi file converts with BIC mappers then you would have to use BIC adapter or BIC modules, i hope BIC modules, next EDI Adapters see the below links to get more details..
    /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.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
    Regards
    Chilla

  • SAP to 3rd party: EDI and XI: Needed advantages and disadvantages

    HI All,
    I have a requirement to sent PO data from SAP to 3rd party Vendors.(more than 30 vendors). Client insists on using EDI.!!
    I have completed the config on SAP R/3 side and IDOCS are created in SAP R/3.
    Since we have XI in the landscape, I have a few questions in my mind. Appreciate if you could give you feedback on these questions:
    1. Should we send data directly from SAP to 3rd party using EDI adapter and avoid XI.
    2. I assume EDI adapter will automatically convert IDOC to vendor format data and vice-versa.
    3. All 30+ vendors will need to access this EDI adapter system or do they all need to have a separate one installed in there landscape.
    4. If we use XI, will the adapter be able to communicate to XI. If yes what is the adapter name which connects to XI.
    5. All vendors need this data in a slightly different format, so will the EDI adapter do the format conversion for every vendor ?
    6. Since all vendors have a diff file format needed, I want to avoid doing extensive message mapping in XI. So can the EDI adapter handle it or is ther any easy way to do this mapping.
    7. If mapping is not possible, then does it mean I will have to create a separate IDOC for each vendor in R/3 ( in vendor specific format) and send that to them.
    Thanks in advance.
    Regards
    Shirin

    Hi,
    1) Should we send data directly from SAP to 3rd party using EDI adapter and avoid XI.
    A) For EDI integration u need to have the EDi adapters and for that u need to purchase the seeburger license and which is need to be installed on XI and after that only u can use EDi adapter with Xi.
    U can not ignore XI.
    2. I assume EDI adapter will automatically convert IDOC to vendor format data and vice-versa.
    A) Yes but only when u purchase the seeburger license. there are other ways as well either use conversion agent or module program which convert the XML to EDI format.
    3. All 30+ vendors will need to access this EDI adapter system or do they all need to have a separate one installed in there landscape.
    A) U have to use the EDI adapters with Xi and configure ur scenario in XI for all the vendors.
    4. If we use XI, will the adapter be able to communicate to XI. If yes what is the adapter name which connects to XI.
    A) Seeburger provide As2,X400,FTP,VAn adapters for EDi integration.
    5. All vendors need this data in a slightly different format, so will the EDI adapter do the format conversion for every vendor ?
    A) What EDI format ur vendor receivers the data it depends upon that.
    6. Since all vendors have a diff file format needed, I want to avoid doing extensive message mapping in XI. So can the EDI adapter handle it or is ther any easy way to do this mapping.
    A) Mapping is the part of desing and mapping changes accroding to the business requirement and mapping rule which is provided by Functional people.
    7. If mapping is not possible, then does it mean I will have to create a separate IDOC for each vendor in R/3 ( in vendor specific format) and send that to them.
    A) u need to do the mapping between IDOC and EDi then only the data will be mapped with the required target EDI strcuture.
    chirag

  • Comparison between split Adapter in Seeburger and EDI Separator

    Hello All,
    Currently we are designing EDI interfaces using B2B Add-On.
    I am trying to compare the split Adapter of Seeburger and EDI Separator of B2B Add-on.
    In Seeburger Splitter configuration:
    The additional split configuration helps to map the Sender ID, (EDIType,Transaction,Version) combination to split channel and sender agreement.
    I believe a List of Sender Id, Mappings (Standard, Transaction, Version) combinations can be added to the same Split channel and Sender Agreements.
    In B2B Add-On:
    The sender ids , EDI details are directly mentioned in the channel and it is bound to sender agreement.
    Does it reduce the flexibility in EDI Scenarios.Is that a correct point of view?
    Your inputs highly appreciated.
    Thanks.
    Regards,
    Sudharshan N A

    Dear Sudharshan,
    yes, I would say that this is a correct point/observation. When the Seeburger Adapters were introduced many years ago, one focus was put on the flexibility by keeping all functionality related to the "format conversion" (Classifier/Bic/Splitter) completely separated from the "data transmission" functionality directly in the channel.
    This way, the format conversion modules could be included in any adapter that was running on the AdapterEngine and not just to the See-Adapters.
    In a typical setup on client side, almost all inbound channels were using the "AUTO" functionality to detect all required parameters to select the right Split-Channel...so all channels had the same module-chains included (no matter if it was an AS2-Channel or a simple FILE/FTP-channel.
    This also allowed for easy reprocessing of any received file (via AS2, X400 , OFTP or else....) by just putting the file again to a file-channel with the same module-chain parameters.
    Kind Regards
    Stefan
    Btw... I am not very familiar with the B2B AddOn, but if you have additional questions regarding the Seeburger-EDI-Adapters, feel free to ask...

  • EDI from legacy systems......

    Hi frenz,
             I've got an object in which we get an incoming EDI (856) from our warehouse for updating picked quantity in delivery document.
            Here i got some doubts.
      1) Its not an IDoc we gotto recive, So how do i configure my XI to receive and recognise the EDI message?
      2) Shall i call a RFC enabled function module to update the picked quantity, from XI or shall post the EDI message as  IDoc in our R/3 and update it there?
        Which will be the optimized way?
      3) For this scenario, i'm not sure whether i would require just a message mapping or XSLT or Java Mapping.
        If someone had done this scenario already, help me how to approach this. I'm expectin a reply as early as possible, frenz.
    Thanks in advance.                      
    ---praveen.

    Hi Praveen,
    <i>>>>1) Its not an IDoc we gotto recive, So how do i configure my XI to receive and recognise the EDI message?</i>
    you can use EDI adapters:
    from iWay
    http://www.iwaysoftware.com/products/sap/SAP_XI.html
    or from:
    www.seeburger.com
    if this EDI message is a flat file then you can use fil/ftp adapter
    <i>>>>2) Shall i call a RFC enabled function module to update the picked quantity, from XI or shall post the EDI message as IDoc in our R/3 and update it there?</i>
    try using the idoc first - if something goes wrong you can always restart the idoc and it's not always the case with messages from XI Maybe you can use the idoc SDPIIOD - I used it once for picking & posting goods issues - but have a look at it's limitation first (he can only use base unit of measure as far as I remember)
    but you can also use RFC if you want - then you'll have to make sure that you can always resume the message (so for instance archive incomming EDI messages)
    <i>>>>3) For this scenario, i'm not sure whether i would require just a message mapping or XSLT or Java Mapping.</i>
    I'm sure java graphical mapping will be enough:)
    maybe you'll just have to write a few advanced java functions
    Regards,
    michal

  • Where to download EDI add-on for Business Connector 4.6?

    Where can I download the BC EDI add-on? I've looked under service.sap.com/connectors but I'm not finding it
    thanks-

    Hi Henry,
    Is this what you are looking for?
    https://websmp204.sap-ag.de/~iron/fm/011000358700001099992001E
    you can also read this (about standard edi adapters):
    http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci983342,00.html
    Regards,
    michal
    Message was edited by: Michal Krawczyk

  • SAP XI and EDI

    Hi all,
    I have some questions about SAP XI and EDI.
    We are planning to get the SAP XI to handle EDI message e.g. ANSI 850, but it looks like XI does not handle EDI out of the box. From what I read we still need to buy an EDI adaptor to handle the EDI-to-IDOC and IDOC-to-EDI processing. e.g. Seeburger adaptor.
    Actually I don't quite get this, isn't it XI contains a set of tools that allows us to do the mapping? Can we just use those tools to create EDI map without buying the seeburger adaptor? If we cannot create EDI map ourselves, then isn't it SAP XI is just an expensive message router??
    Any inputs are greatly appreciated. Thanks.

    XI has its own built-in message mapping tool (drag and drop GUI), upon which you can do "any-to-any" mapping. You can also do your mapping in ABAP, Java, or XSLT environments if you feel that the message (graphical) mapping tool doesnt enable you to do everything you want.
    So yes ... you can use XI's mapping functionality to map from iDoc to EDI format. However, this can be quite a complex exercise: you will need to setup the structure of the (target) EDI message/data type, and then carry out the mapping yourself - depending on the type of interface, this could be quite a complex exercise (typically EDI structures contain a very large number of fields).
    Once the iDoc has been mapped into the EDI format ... you will need to transmit (send) the EDI message to your (business) partner system, who is typically outside of your firewall (B2B). This means you need to communicate with them using a secure communication protocol (typically OFTP via VAN in EDI scenarios). And this is where the SeeBurger EDI adapters add value. They enable you to connect to VANs (Value Added Networks) using OFTP (or x.400), and also provide mappings for some EDI scenarios (which you can use).
    iWay also provide adapters for this purpose.

  • Edi messages

    what are the different edi messages that are widely used ?? Whether seeburger adapter is suitable for all edi messages or we got to use different edi adapters for each message type ??
    thanks
    kumar

    Hi,
    >>>the different edi messages that are widely used ??
    in logistics area:
    delivery documents, sales orders/purachse orders
    invoices
    >>>Whether seeburger adapter is suitable for all edi messages
    it all depends on your country EDI provider
    in somecountries you need to use old technologies
    like VAN networks and EDI messages
    in some you can use SOAP and XML edi messages (so no need to any seeburger)
    Regards,
    michal

Maybe you are looking for