EDIFACT Sample Converted to XML

This shows a sample EDIFACT document before and after conversion to XML, displaying markup and full automatically-generated internal documentation.

Sample EDIFACT Document

UNA:+.? '
UNB+UNOA:3+STYLUSSTUDIO:1+DATADIRECT:1+20051107:1159+6002'
UNH+SSDD1+ORDERS:D:03B:UN:EAN008'
BGM+220+BKOD99+9'
DTM+137:20051107:102'
NAD+BY+5412345000176::9'
NAD+SU+4012345000094::9'
LIN+1+1+0764569104:IB'
QTY+1:25'
FTX+AFM+1++XPath 2.0 Programmer?'s Reference'
LIN+2+1+0764569090:IB'
QTY+1:25'
FTX+AFM+1++XSLT 2.0 Programmer?'s Reference'
LIN+3+1+1861004656:IB'
QTY+1:16'
FTX+AFM+1++Java Server Programming'
LIN+4+1+0596006756:IB'
QTY+1:10'
FTX+AFM+1++Enterprise Service Bus'
UNS+S'
CNT+2:4'
UNT+22+SSDD1'
UNZ+1+6002'

(The original raw EDIFACT sample file edifact-sample.txt is here).

Equivalent EDIFACT XML Document as Converted by Stylus Studio®

Why is the XML so much bigger than the EDI?

The EDI omits almost all of the markup, so that an independent processor doesn't know the meaning of each element. XML includes that, so engines like XSLT and XQuery can do their magic. What you don't see in the EDI is the megabytes of dictionary information you need to decode it, and the megabytes of code necessary to alter in case on little element is inserted or removed. That is where XML shines. And you can use it in your own programs, thanks to the data conversion API.

<EDIFACT>
    <UNB>
        <UNB01>
            <UNB0101><!--0001: Syntax identifier-->UNOA<!--UN/ECE level A--></UNB0101>
            <UNB0102><!--0002: Syntax version number-->4<!--Version 4--></UNB0102>
        </UNB01>
        <UNB02>
            <UNB0201><!--0004: Interchange sender identification-->STYLUSSTUDIO</UNB0201>
            <UNB0202><!--0007: Identification code qualifier-->1<!--DUNS (Data Universal Numbering System)--></UNB0202>
        </UNB02>
        <UNB03>
            <UNB0301><!--0010: Interchange recipient identification-->DATADIRECT</UNB0301>
            <UNB0302><!--0007: Identification code qualifier-->1<!--DUNS (Data Universal Numbering System)--></UNB0302>
        </UNB03>
        <UNB04>
            <UNB0401><!--0017: Date-->20051107</UNB0401>
            <UNB0402><!--0019: Time-->1159</UNB0402>
        </UNB04>
        <UNB05><!--0020: INTERCHANGE CONTROL REFERENCE-->6002</UNB05>
    </UNB>
    <ORDERS>
        <UNH>
            <UNH01><!--0062: MESSAGE REFERENCE NUMBER-->SSDD1</UNH01>
            <UNH02>
                <UNH0201><!--0065: Message type-->ORDERS</UNH0201>
                <UNH0202><!--0052: Message version number-->D</UNH0202>
                <UNH0203><!--0054: Message release number-->03B</UNH0203>
                <UNH0204><!--0051: Controlling agency, coded-->UN</UNH0204>
                <UNH0205><!--0057: Association assigned code-->EAN008</UNH0205>
            </UNH02>
        </UNH>
        <BGM>
            <BGM01>
                <BGM0101><!--1001: Document name code-->220<!--Order--></BGM0101>
            </BGM01>
            <BGM02>
                <BGM0201><!--1004: Document identifier-->BKOD99</BGM0201>
            </BGM02>
            <BGM03><!--1225: Message function code-->9<!--Original--></BGM03>
        </BGM>
        <DTM>
            <DTM01>
                <DTM0101><!--2005: Date or time or period function code qualifier-->137<!--Document/message date/time--></DTM0101>
                <DTM0102><!--2380: Date or time or period text-->20051107</DTM0102>
                <DTM0103><!--2379: Date or time or period format code-->102<!--CCYYMMDD--></DTM0103>
            </DTM01>
        </DTM>
        <GROUP_2>
            <NAD>
                <NAD01><!--3035: Party function code qualifier-->BY<!--Buyer--></NAD01>
                <NAD02>
                    <NAD0201><!--3039: Party identifier-->5412345000176</NAD0201>
                    <NAD0203><!--3055: Code list responsible agency code-->9<!--GS1--></NAD0203>
                </NAD02>
            </NAD>
        </GROUP_2>
        <GROUP_2>
            <NAD>
                <NAD01><!--3035: Party function code qualifier-->SU<!--Supplier--></NAD01>
                <NAD02>
                    <NAD0201><!--3039: Party identifier-->4012345000094</NAD0201>
                    <NAD0203><!--3055: Code list responsible agency code-->9<!--GS1--></NAD0203>
                </NAD02>
            </NAD>
        </GROUP_2>
        <GROUP_28>
            <LIN>
                <LIN01><!--1082: LINE ITEM IDENTIFIER-->1</LIN01>
                <LIN02><!--1229: ACTION REQUEST/NOTIFICATION DESCRIPTION CODE-->1<!--Added--></LIN02>
                <LIN03>
                    <LIN0301><!--7140: Item identifier-->0764569104</LIN0301>
                    <LIN0302><!--7143: Item type identification code-->IB<!--ISBN (International Standard Book Number)--></LIN0302>
                </LIN03>
            </LIN>
            <QTY>
                <QTY01>
                    <QTY0101><!--6063: Quantity type code qualifier-->1<!--Discrete quantity--></QTY0101>
                    <QTY0102><!--6060: Quantity-->25</QTY0102>
                </QTY01>
            </QTY>
            <FTX>
                <FTX01><!--4451: TEXT SUBJECT CODE QUALIFIER-->AFM<!--Title--></FTX01>
                <FTX02><!--4453: FREE TEXT FUNCTION CODE-->1<!--Text for subsequent use--></FTX02>
                <FTX04>
                    <FTX0401><!--4440: Free text-->XPath 2.0 Programmer's Reference</FTX0401>
                </FTX04>
            </FTX>
        </GROUP_28>
        <GROUP_28>
            <LIN>
                <LIN01><!--1082: LINE ITEM IDENTIFIER-->2</LIN01>
                <LIN02><!--1229: ACTION REQUEST/NOTIFICATION DESCRIPTION CODE-->1<!--Added--></LIN02>
                <LIN03>
                    <LIN0301><!--7140: Item identifier-->0764569090</LIN0301>
                    <LIN0302><!--7143: Item type identification code-->IB<!--ISBN (International Standard Book Number)--></LIN0302>
                </LIN03>
            </LIN>
            <QTY>
                <QTY01>
                    <QTY0101><!--6063: Quantity type code qualifier-->1<!--Discrete quantity--></QTY0101>
                    <QTY0102><!--6060: Quantity-->25</QTY0102>
                </QTY01>
            </QTY>
            <FTX>
                <FTX01><!--4451: TEXT SUBJECT CODE QUALIFIER-->AFM<!--Title--></FTX01>
                <FTX02><!--4453: FREE TEXT FUNCTION CODE-->1<!--Text for subsequent use--></FTX02>
                <FTX04>
                    <FTX0401><!--4440: Free text-->XSLT 2.0 Programmer's Reference</FTX0401>
                </FTX04>
            </FTX>
        </GROUP_28>
        <GROUP_28>
            <LIN>
                <LIN01><!--1082: LINE ITEM IDENTIFIER-->3</LIN01>
                <LIN02><!--1229: ACTION REQUEST/NOTIFICATION DESCRIPTION CODE-->1<!--Added--></LIN02>
                <LIN03>
                    <LIN0301><!--7140: Item identifier-->1861004656</LIN0301>
                    <LIN0302><!--7143: Item type identification code-->IB<!--ISBN (International Standard Book Number)--></LIN0302>
                </LIN03>
            </LIN>
            <QTY>
                <QTY01>
                    <QTY0101><!--6063: Quantity type code qualifier-->1<!--Discrete quantity--></QTY0101>
                    <QTY0102><!--6060: Quantity-->16</QTY0102>
                </QTY01>
            </QTY>
            <FTX>
                <FTX01><!--4451: TEXT SUBJECT CODE QUALIFIER-->AFM<!--Title--></FTX01>
                <FTX02><!--4453: FREE TEXT FUNCTION CODE-->1<!--Text for subsequent use--></FTX02>
                <FTX04>
                    <FTX0401><!--4440: Free text-->Java Server Programming</FTX0401>
                </FTX04>
            </FTX>
        </GROUP_28>
        <GROUP_28>
            <LIN>
                <LIN01><!--1082: LINE ITEM IDENTIFIER-->4</LIN01>
                <LIN02><!--1229: ACTION REQUEST/NOTIFICATION DESCRIPTION CODE-->1<!--Added--></LIN02>
                <LIN03>
                    <LIN0301><!--7140: Item identifier-->0596006756</LIN0301>
                    <LIN0302><!--7143: Item type identification code-->IB<!--ISBN (International Standard Book Number)--></LIN0302>
                </LIN03>
            </LIN>
            <QTY>
                <QTY01>
                    <QTY0101><!--6063: Quantity type code qualifier-->1<!--Discrete quantity--></QTY0101>
                    <QTY0102><!--6060: Quantity-->10</QTY0102>
                </QTY01>
            </QTY>
            <FTX>
                <FTX01><!--4451: TEXT SUBJECT CODE QUALIFIER-->AFM<!--Title--></FTX01>
                <FTX02><!--4453: FREE TEXT FUNCTION CODE-->1<!--Text for subsequent use--></FTX02>
                <FTX04>
                    <FTX0401><!--4440: Free text-->Enterprise Service Bus</FTX0401>
                </FTX04>
            </FTX>
        </GROUP_28>
        <UNS>
            <UNS01><!--0081: SECTION IDENTIFICATION-->S</UNS01>
        </UNS>
        <CNT>
            <CNT01>
                <CNT0101><!--6069: Control total type code qualifier-->2<!--Number of line items in message--></CNT0101>
                <CNT0102><!--6066: Control total quantity-->4</CNT0102>
            </CNT01>
        </CNT>
        <UNT>
            <UNT01><!--0074: NUMBER OF SEGMENTS IN A MESSAGE-->22</UNT01>
            <UNT02><!--0062: MESSAGE REFERENCE NUMBER-->SSDD1</UNT02>
        </UNT>
    </ORDERS>
    <UNZ>
        <UNZ01><!--0036: INTERCHANGE CONTROL COUNT-->1</UNZ01>
        <UNZ02><!--0020: INTERCHANGE CONTROL REFERENCE-->6002</UNZ02>
    </UNZ>
</EDIFACT>

Using Stylus Studio's Database-to-XML Editor to Query and Update Relational Databases using SQL/XML

Watch and learn how easy it is to define relational-to-XML mappings for getting XML out of relational databases and updating databases from XML using industry-standard SQL/XML extensions and Stylus Studio's DB-to-XML data-source editor.

X12 Standards Available Across All Releases

The complete X12 Standards Grid, listing all X12 EDI releases across the top, and the corresponding transaction sets down the left side.

XML Schema Library

The Stylus Studio XML Schema Library provides a detailed reference of many of the world's most commonly used XML vocabularies in an easy-to-read format.

Text File to XML

Stylus Studio provides several easy-to-use document wizards that allow you to quickly convert text files to XML. Create XML from text and EDI, create XML Schema from EDIFACT, and more!

Stylus Most Wanted

PURCHASE STYLUS STUDIO ONLINE TODAY!!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Cast Your Vote

We need your help – Vote for DataDirect XML Products!

  • Best SOA or XML site

Winners and finalists announced at SOA World Conference in November.

Try Stylus EDI Tools

Simplify working with Electronic Data Interchange (EDI) with Stylus Studio®'s award-winning EDI Tools — Download a free trial of our today!

Stylus Studio® EDIFACT Zone

Simplify your next legacy data integration project with the help of the EDIFACT Zone, the world's largest, free online reference covering all EDIFACT and UN/CEFACT versions.

Learn Stylus Studio in 6 Minutes

Can six minutes change your life? A new action-packed online video demonstration covers how to use Stylus Studio in just six minutes! Watch this video and change the way you develop XML applications forever!

Ask Someone You Know

Does your company use Stylus Studio? Do your competitors? Engineers from over 100,000 leading companies use Stylus Studio, and now you can ask someone from your own organization about their experiences using Stylus Studio.
 
Free Stylus Studio XML Training:
W3C Member

RSS Blogs Newsletter

Site Map | XML Converters | XQuery | XML Editor | DataDirect Technologies

Privacy | Trademarks | Terms of Use

Copyright © 2005-2008 Progress Software Corporation. All Rights Reserved