XI 3 and EDIFACT

Hi there,
we think about using the XI for converting EDIFACT messages. More precisely we have to be able to receive INVOIC and REMADV messages (version D.99A) and to transform them into our inhouse text formats on the one hand and on the other hand to transform inhouse text messages into the INVOIC and REMADV format.
Can someone tell me if the schemas of these EDIFACT message types are already included within the XI or if there is any product (like the Covast EDI Accelerator for the Ms BizTalk server) which allows the XI to handle these EDIFACT message types?
Every help is appreciated.
Greetings,
Florian

Hi,
>>>>I think the option of using the Seeburger EDI Adapter fits best because (if I got it right) we don't have to do the EDIFACT-to-XML mappings by ourselves.
as I said also business connector can do it for you
(it's free for SAP customers but you need to check
the licence model too)
and also my second help (mapping tools)
can do the same (as they do edifact - xml ) for you
(in the xi with xslt or java) but you need to check it
if it fits your needs
>>>Can anybody tell me something about the licensing modell of the Seeburger EDI Adapter?
you can call any SAP sales offica and I believe
they should provide you with all details
if not contact seeburger directly
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Similar Messages

  • JCAPS 5.1.X and EDIFACT OTDs

    Is it possible to install UN/EDIFACT OTDs into JCAPS 5.1.X? I've installed JCAPS 5.1.2 (JCAPS) from JES 2007Q2 DVD, but the EDIFACT OTDs are on another DVD with eXchange Integrator. The installer on this DVD installs ICAN 5.0.5 and I can install desired OTDs into its repository (ICAN).
    I just need the OTDs, but the JCAPS won't allow me to install it. I've tried to add the OTDs to its Products.xml in ProductList, but when I try to upload them to the repository, it produces this error:
    Error Encountered While Uploading
    UN_EDIFACT_OTD_Lib_v4_D01A.sar has been tampered with or it was not produced by an authorized entity.
    Is it possible to install the OTDs somehow or is there another installation that will install JCAPS 5.1.X with the EDIFACT OTDs? I don't want to use the ICAN 5.0.5, because I have already installed JCAPS 5.1.2 and there is no LogicalHost for Windows plaftorm in ICAN 5.0.5 (?)

    JohanHellstrom wrote:
    You should not install ICAN functionality in CAPS. It simply would not work and tampering with the install XML files won't improve the situation.
    There are two ways you can go. One is simpler than the other:
    1. Become a Champions member by contacting your Sun representative. Sun might even decide to give you the Beta CAPS Edifact OTDs without your becoming a Champions member, but chances are very slim.I think I'll try that. Thanks.
    >
    2. Install ICAN from your DVD, including eXchange and the EDIFACT release(s) and message(s) you want. Export the corresponding .SEF file(s) for the relevant messages to the file system. Install the CAPS B2B 5.1.0 release, which can be acquired from Sun. Create the relevant CAPS OTDs using the SEF Wizard that comes with CAPS B2B 5.1.0. As long as all you want is OTDs and you are not interested in Protocol Managers this will work.
    Note that you will not be able to import ICAN projects into CAPS making use of ICAN EDIFACT OTDs, since the project path for these OTDs in ICAN is based on the SeeBeyond project, where you will not be allowed to place your newly created SEF Wizard EDIFACT OTDs in CAPS. However you will be able create EDIFACT integrations and the SEF files are supported, as is the CAPS B2B 5.1.0 SEF Wizard.
    IMHO it might be a better idea to take the SEF files from a recent EDIFACT ESR for ICAN instead (like esr96403.zip). In this case you don't even have to install ICAN to extract the associated .SEF file(s) since they can be extracted directly from the relevant .sar file, which you can open using your favorite .zip application. This would give you a more recent level of the .sef files and save you the effort of installing ICAN and eXchange.Thanks a LOT! This sounds like a very easy way to get what I need. I just need to extract data from an Edifact document, trasnform it to XML and based on its content choose a destination to send it to.
    Where can I get the EDIFACT ESR for ICAN? I was looking for it for a while without luck. But I will keep searching :)

  • B2B in PI 7.0 - EDIFACT format to IDOC and vice versa

    We need to establish B2B scenario in PI 7.0
    IDOC to EDIFACT and EDIFACT to IDOC.
    Please let me know the solution without using any third party adapter like seeburger.
    Any example scenario of the same case will be helpful

    Hi ,
    If you are decided to not using SeeBurger then its difficult to implement B2B Scenario
    Your requirement IDOC 2 EDIFACT or Vice VERSA, you have to do more analyzation about EDIFACT.
    You can acheive using Adapter module, you have to about EJB's stuff to write Adapter module to support EDIFACT Message, Search for info about Adapter Module in SDN you wil find some lot off stuff about Adapter MODULE.
    then coming to mapping its really challenging to do Mapping between IDOC TO EDIFACT.
    You have to alalyze the EDIFACT Structure .
    I implemented B2B scebario in my project SeeBurger.
    Regards,
    Raj

  • Converting INVOIC02 idoc to EDIFACT INVOIC message (Using Adapter Module

    Hi Friends,
    We are sending customer idoc (INVOIC02) from R/3 to external system through PI. We want to generate EDIFACT output file (message type : INVOIC).
    Is it possible to convert IDoc message to EDI file format through java adapter module ? Will adapter module support this  without using Seeburger adapter ?
    kindly clarify, friends.
    Kind regards,
    Jegathees P.

    There is an alternative to Seeburger.
    DataDirect also has complete EDI-XML conversion by way of deploying a module which is called from an adapter. The range of parameters with the conversion is also quite extensive, allowing tolerance for partners who may have included non-standard EDI qualifiers and such.  The XML tags make for easier mapping.  StylusStudio XML Suite includes the EDI<->XML adapter so you can try the conversions each way directly in that package.  If you are happy with it, you need to then purchase the package from DataDirect.  We did this and implemented EDI for X12 and EDIfact, including Orders and Invoices and some other messages.  The communications part was not included.  We wrote the EDI files and used a separate process to actually send and receive the files. The IDoc <-> EDI mapping  was done using the normal graphical mapping of SAP PI. The Stylus Studio package includes the functionality to generate the XSD, which we imported to SAP PI.

  • How to Use IDOC and ALE in SAP?

    Hi anybody,
                     I want Use Idoc and ALE in sap ABAP. What is inbound and outbout process of IDOC?
    Please give me sample code for Idoc . and Sample code for ALE.
    anybody Please tell me.
    Thanks
    Regards,
    S.Muthu.
    IT Dept.

    hi,
    Follow the link for step by step ALE/IDOC tutorials.
    http://www.sapmaterial.com/idoc_sample.html
    http://www.****************/Tutorials/ALE/ALEMainPage.htm
    An IDoc is not a process.
    The term IDoc stands for intermediate document. It is simply a data container used to exchange information between any two processes that can understand the syntax and semantics of the data. An IDoc is created as a result of executing an outbound ALE or EDI process. In an inbound ALE or EDI process, an IDoc serves as input to create an application document.
    IDocs are stored in the database.
    In the SAP system, they are stored in database tables. Several utilities are available to display the information contained in an IDoc and present it in different ways. For details, refer to Chapter 11, "Monitoring the Interface."
    Every IDoc has a unique number.
    When an IDoc is generated in the system, a unique number is assigned to it. This number is unique within a client.
    IDocs are independent of the sending and receiving systems. They can be used for SAP-to-SAP and SAP to non-SAP process communication as long as the participating processes can understand the syntax and semantics of the data.
    IDocs are based on EDI standards, ANSI ASC X12 and EDIFACT, but are closer to the EDIFACT standards. The size and format of data elements in an IDoc type are derived from these standards wherever applicable. For example, if a material number is represented by 20 characters in an EDIFACT message, the corresponding data element in the IDoc is also 20 characters. If there is a conflict in data size between standards, the one with greater length is adopted. This approach ensures compatibility with most standards.
    IDocs are independent of the direction of data exchange. An inbound and an outbound process can use an IDoc. For example, the ORDERS01 IDoc is used by the Purchasing module to send a purchase order, and is also used by the Sales and Distribution module to accept a sales order. Using this technique avoids creating redundant IDoc types for the same information.
    IDocs can be viewed in a text editor and do not contain any binary data. Data is stored in character format. When transferred to the operating system, an IDoc is stored in a file in text format and can be viewed using a regular text editor. However, the contents make sense only if you understand the structure and format of the data in that IDoc. In the Appendix, "FAQs, User Exits, and Miscellaneous Resources," you will find an example of an IDoc file.
    Hope this helps, Do reward.
    Edited by: Runal Singh on Mar 5, 2008 6:09 PM

  • Mapping EDIFACT to IDoc: IFTMIN to DELVRY / SHPMNT

    Hi,
    because we haven't done this before we want to ask if there is someone whos has done this before us.
    So our business case is that we have to map IFTMIN to any appropriate SAP-Format.
    We found that SHPMNT might be the best solution but as we checked the structure we saw that this IDoc contains so much overhead information that we thought we might map it to DELVRY - whereas this is included in SPHMNT.
    So has someone of you done this before and can give us a hand on how to map this? maybe there is a mapping template to offer?
    I know this sounds silly - but maybe someone might help.
    We are also open to any other suggestions on how to map IFTMIN - perhaps to a BAPI?!
    br

    Hi Fritz,
        This blog gives you the realtion between most EDIFACt messages and sap idocs:
    /people/community.user/blog/2009/10/12/mapping-idocs-to-x12-transactions-and-edifact-messages
    It says SHPMNT04 is the IDOC for Inbound Interfaces and DESADV.DELVRY03 for Outbound Idocs.
    Can you check how much of the overhead information is actually "mandatory" on the sap side?
    You can probably leave the information that you wont need.
    You can find the detailed documentation (filed level) in WE60 transaction of sap.
    Regards,
    Ravi Kanth Talagana

  • ??? EDI Multipartner Integration with Idoc- EDIFACT X.400P7 ???

    Hi all,
    can somebody please give me an idea of how to build a EDI-scenario on XI with X.400 adapter to connect 3000 customers?
    My actual point is, that I have the SAP system sent idocs, that need to me mapped to EDIFACT messages - D99B Invoice (12 different mappings - customerdependend) and then be sent via X.400 to the MTA.  How can I have the Customernumber from the Idoc set the identifier in my receiver X.400 channel, which defines the receiver adress dynamically - without building 3000 Parties, Business Services and Channels?
    Has one of you allready build something like that?
    Thanks in advance..
    Daniel

    Hi Leonardo,
    The Seeburger adapter license is based on data volumes through the adapter, plus a fixed percentage as maintenance costs.
    If you are using Seeburger, they will have some ready maps developed between the IDOC and EDIFACT messages.
    Cheers
    Manish

  • EDIFACT D96A for Delivery Note

    Hi Gurus,
    Which Standard is available in spectrum of EDIFACT D96A for Delivery Note?
    I can only find 2 for Delivery Note :-
    1. DELFOR : Delivery Schedule
    2. DELJIT : Delivery JIT
    Which one to use for Delivery Note or there is someone else for Delivery Note?
    Thanks

    I do not have any such doc. Anybody in your team/org having functional knowledge about electronic transaction flow and EDIFACT may provide you such doc/mapping. I just know it because I have worked with this EDIFACT message earlier.
    Regards,
    Anuj

  • Require sample files and xsd

    Hi All,
    I need sample files and its xsd for Invoice, Ack PO and Shipment for both X12 and EDIFACT. If anyone has it please share them.
    Basically, we are looking to convert OAG standard to X12 and EDIFACT and vice versa. For writing XSLT, we need the sample files...
    Regards,
    Praveen

    Hi Praveen,
    You can generate these using document editor for any required document revision/Type.
    http://www.oracle.com/technology/products/integration/b2b/pdf/edi_cookbook_oracle_b2b.pdf explains the steps to create using Document Editor
    Regards,
    Dheeraj

  • How to deal with digital signatures when converting messages?

    Hi there,
    this it not (yet) about the actual implementation. It's more of a logical problem that I'm facing.
    There are two partners A and B. A is sending an EDIFACT document which is digitally signed to B.
    B has a XI instance that is converting all incoming messages into IDocs, in this particular case INVOIC. This IDoc is received by the R/3 system.
    All invoices must be archived due to an eventual tax inspection.
    In order to fulfill the security requirements all archived data must be digitally signed.
    So far so good.
    I guess I'm not allowed to sign my invoices with my own private key due to the fact that i could alter the containing data and sign it again.
    It's obvious that I cant apply the digital signature from the EDIFACT message to my IDoc because the data has changed and therefore the signature is invalid.
    The only solution to this problem, that I can imagine, is to archive EDIFACT alongside IDoc.
    Have you experienced a similar problem or do you have any other idea in order to solve this issue?
    I hope my problem is well defined.
    Any comment is appreciated.
    Thanks in advance
    Bastian Stratmann

    Hi Bastian,
    it is not possible to separate the signature from the document signed.
    The system A generates and EDIFACT message -> A has the responsibility on this message and so A sign it.
    XI manipulate the message received from A, that means XI generates a new message. -> XI has the responsibility on it, so if you want a signature this should be generated by XI.
    As the IDoc was generated by XI it cannot be signed by A (neither technically nor logically) because A has no responsibility on it.
    XI <b>is</b> altering the message so XI is responsible for it.
    In this case you have to store both the EDIFACT message and the IDOC and maybe sign this new document (EDIFACT+IDOC) with XI signature .
    Kind Regards,
    Sergio

  • Seeburger EDI conversion Vs XI Conversion Agent EDI conversion?

    We have implemented Seeburger's EDI solution at a client, and our another client wants to an EDI solution for them.
    I cam across this weblog, and it is very interesting. I have some questions.
    1. Does Converstion Agent support the converstion of all versions of native EDI X12 and EDIFACT to the corresponding XML verions, and vice versa.
    2. What are the differences between Seeburger's and XI Conversion Agent's EDI soultions?
    Your feedback would be greatly appreciated.
    Thanks a lot.
    Karma

    Hi Karma,
    SAP Conversion Agent by Itemfield is a data conversion system that enables you to create interfaces between any data formats and XML-based systems. The Conversion Agent can convert unstructured, semi-structured, and structured formats to XML, and the other way around.
    Have a look at these links:
    /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
    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.
    These transformed EDI-XML messages are then converted to EDI specific format using the Seeburger's BIC(Business Integration Converter)adapter. In addition, Seeburger provides adapters like AS2,FTP(EDI specific) and so on to route these EDI messages to external EDI Partners.
    For more i would suggest you to go through these links:
    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
    Seeburger EDI Adapter leverages SAP XI's Adapter Framework. This Adapter is used to perform conversion between EDI and XML format. It also provides some canned EDI layouts and the ability to build your own. It is used to transfer the EDI message via HTTP or AS2 protocols.
    The most direct way of using the Seeburger adapters is to configure the BIC as a module. There is a software component from seeburger called bicmapper which will allow you to do the following:
    1. define or import the inbound message metadefinition in various formats ( edifact, xml,...)
    2. using a mapping create an xml variant as the output metadefinition or edifact in the other direction.
    3. create a one to one mapping between input en output.
    4. export the metadata in xsd or sda format for import in XI.
    5. generate an SDA which can be deployed in XI and used as a module.
    Please go through the following links which clearly explains what you want and it also helps you in understanding the same in depth:
    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
    There are also a few ways to use EDI with the ALE system of R3.
    inbound EDI to R3
    1.use a 3rd party adapter for the EDI protocol(eg.SEEBURDER) from the EDI system,send the produced XML to the XI ,map the xml message to a matching IDoc using the IDoc adapter.
    outbound ALE message from R3 to EDI system
    1. Configure the ALE system to point to the XI the relevant IDoc (SM59,WE21,WE20...)
    2.use a file adapter3rd party EDI adapter and map the fields to the target structure.
    have a look at this example:
    http://www.ean.se/EANCOM%202000/iftmin/example.htm
    Details on how to configure can be found on SDN
    I hope this helps....
    Regards,
    Abhy

  • Regarding seeburger adapter??

    Hello guys
    My client is going to implement EDI messages to SAP XI to SAP ERP .It would be great if you let me know the step by step proceedure ??
    wht is the use seeburger  BIC mapping tool here ??
    wht is the configuration should be done at sender side(seeburger as2) adapter??

    So this means your customer has purchased a Seeburger adapterlicense which will come with documentation for PI. Use that as first entry point. Such a general question you can not handle well in forum answer.
    General first hints:
    Seeburger delivers an EDI-adapter which will be deployed into PI. This adapter contains functionality to map between XML and EDIfact format. It also contains (normally) some standard mappings (e.g. for invoice). But be VERY careful with these standard mappings. Not all of them can be used without change. Make detailed tests and do not rely on them.
    The BIC mapping designer is not used in PI, but you can see it as a kind of external development or debugging tool in case of problems. You will surely use it, because there are many pitfalls regarding EDIFact and XML/PI. The topic is quite complex.
    CSY

  • Data migration from SAP to Oracle

    Can any one suggest best possible method for migrating master and transactional data from SAP to Oracle.
    Please suggest methods to get data in text file from SAP.

    Best approach would be to use Electronic Data Interchange (EDI) outbound from SAP inbound to Oracle. There are two widely used standards in EDI messages - ANSI X12 and EDIFACT; I'm pretty sure the Oracle system will be able to accept one of the two standards or both.
    In my last message, when I asked if Oracle is able to receive and process IDocs, I actually meant if Oracle will be able to accept and process EDI messages. IDocs are containers of the EDI message i.e. a data container - their formats are SAP proprietary formats which will not make sense to your target system (Oracle). EDI has been around for many years and is the standard way of electronically exchanging business documents between computer systems of business partners, using a standard format over a communication network.
    In regards to your question - I'm not really sure if you want to send master/transactional data real-time from SAP to Oracle or want to transfer the historical data i.e. download from SAP tables (thru SE16 - this will download the field labels as well) into text files and then upload it to Oracle by using a custom program which reads/maps the files then posts the transactional data/updates master data tables in Oracle as required by that system. So let me know as much details as possible.
    It would be nice to show appreciation by rewarding points.
    Cheers,
    Sougata.

  • EDI/XML translator in WLI 2.0

    are any translator for EDI to XML available in WLI 2.0, to allow
    developers to use EDI software as a service and/or integrate whole B2B solution
    based on WLI 2.0 with existing EDI systems ?
    thanx in advance ...

    In WLI 2.1 there will be full support for EDI including X12 and EDIFACT support. As
    part of the solution there is a mapping tool that you can use to create maps from
    EDI to XML.
    Sunil Raju
    Milan Krajnak wrote:
    are any translator for EDI to XML available in WLI 2.0, to allow
    developers to use EDI software as a service and/or integrate whole B2B solution
    based on WLI 2.0 with existing EDI systems ?
    thanx in advance ...

  • Java API for SOAP Messages

    Hi
    I need Java library for dealing with SOAP messages (e.g., serializing, deserializing, etc.). I don't actually need a complete server, only a library.
    Is SAAJ, http://java.sun.com/webservices/saaj/index.jsp, the right choice? Or JAXM, http://java.sun.com/xml/downloads/jaxm.html?
    In particular the SAAJ page says "SAAJ 1.3 EA (with support for SOAP 1.2) is included in the open-source Java E 5-compliant application server at Project GlassFish. " Does this mean that it is obsolete, and that I should use GlassFish?
    I'm actually a little bit confused by all these technologies...
    thanks in advance

    If you are interested in a commercial solution send me an e-mail. The company I'm working for actually offers a conversion tool which can among other things handle xml and edifact
    regards
    Spieler

Maybe you are looking for