Stylus studio convert edifact message

What is EDIFACT message?

EDIFACT (Electronic Data Interchange for Administration, Commerce, and Transport) is an international standard developed by the United Nations for electronic data interchange (EDI) between trading partners. It standardizes the format and structure of messages for various business transactions, such as orders, invoices, and shipping notices.

EDIFACT Message Structure

Service String Advice UNA Conditional

_____ Interchange Header UNB Mandatory

| ___ Functional Group Header UNG Conditional

| | _ Message Header UNH Mandatory

| | | User Data Segments As required

| | |_ Message Trailer UNT Mandatory

| |___ Functional Group Trailer UNE Conditional

|_____ Interchange Trailer UNZ Mandatory

Key Components of an EDIFACT Message

An EDIFACT message consists of segments, each of which contains data elements. Segments are grouped into sections, and sections form the entire message. Here are the main components:

UNA (Service String Advice): Specifies the separators used in the message (optional).
UNB (Interchange Header): Identifies the start of the message interchange and includes sender/receiver information.
UNH (Message Header): Identifies the start of a message and contains message type and version.
BGM (Beginning of Message): Provides the type and purpose of the message.
DTM (Date/Time/Period): Specifies date and time information.
NAD (Name and Address): Contains information about the parties involved.
LIN (Line Item): Details about line items in the transaction.
QTY (Quantity): Specifies quantities related to line items.
UNS (Section Control): Separates logical sections within a message.
UNT (Message Trailer): Marks the end of a message and provides a control count.
UNZ (Interchange Trailer): Marks the end of an interchange.

Example EDIFACT Message

Here is a simplified example of an EDIFACT message for an order (ORDERS message type):

UNA:+.? '

UNB+UNOC:3+SENDERID+RECEIVERID+210101:1200+123456'

UNH+1+ORDERS:D:96A:UN:EAN008'

BGM+220+BKOD99+9'

DTM+137:20020910:102'

NAD+BY+5412345000176::9'

LIN+1++1234567890123:SRV'

QTY+47:1020:EA'

UNT+7+1'

UNZ+1+123456'

Detailed Breakdown of the Example

UNA Segment:

UNA:+.? '

Specifies the separators used in the message.
+ is the component data element separator.
. is the decimal mark.
? is the release character.
' is the segment terminator.

UNB Segment:

UNB+UNOC:3+SENDERID+RECEIVERID+210101:1200+123456'

UNOC:3 specifies the syntax identifier and version number.
SENDERID and RECEIVERID are the identifiers for the sender and receiver.
210101:1200 is the date and time of the interchange (YYMMDD).
123456 is the interchange control reference.

UNH Segment:

UNH+1+ORDERS:D:96A:UN:EAN008'

1 is the message reference number.
ORDERS:D:96A:UN:EAN008 specifies the message type (ORDERS), version (D), release (96A), controlling agency (UN), and association assigned code (EAN008).

BGM Segment:

BGM+220+BKOD99+9'

220 is the document/message name code.
BKOD99 is the document/message number.
9 is the message function code.

DTM Segment:

DTM+137:20020910:102'

137 is the date/time/period qualifier.
20020910 is the date.
102 is the date format qualifier.

NAD Segment:

NAD+BY+5412345000176::9'

BY is the party qualifier (buyer).
5412345000176 is the party identification.
9 is the code list qualifier.

LIN Segment:

LIN+1++1234567890123:SRV'

1 is the line item number.
1234567890123 is the item number.
SRV is the item number type.

QTY Segment:

QTY+47:1020:EA'

47 is the quantity qualifier.
1020 is the quantity.
EA is the measure unit qualifier.

UNT Segment:

UNT+7+1'

7 is the number of segments in the message.
1 is the message reference number.

UNZ Segment:

UNZ+1+123456'

1 is the number of messages in the interchange.
123456 is the interchange control reference.

Parsing EDIFACT Messages

To parse EDIFACT messages programmatically, you typically follow these steps:

Read the EDIFACT file: Load the EDIFACT message into your program.
Split the message into segments: Use the segment terminator (') to split the message.
Split segments into data elements: Use the data element separator (+) to split each segment.
Split data elements into component elements: Use the component data element separator (:) to split complex data elements.
Map segments to data structures: Map the parsed segments to your data structures for further processing.

Example Code to Parse EDIFACT in Java

Here's an example of how you might start parsing an EDIFACT message in Java:

java

package com.kartik;

import java.io.FileOutputStream;

import java.io.OutputStream;

import javax.xml.transform.stream.StreamResult;

import javax.xml.transform.stream.StreamSource;

import com.ddtek.xmlconverter.ConvertFromXML;

import com.ddtek.xmlconverter.ConvertToXML;

import com.ddtek.xmlconverter.ConverterFactory;

public class XmlToEdi {

public static void main(String[] args) throws Throwable {

ConverterFactory cf = new ConverterFactory();

OutputStream os = null;

try {

ConvertToXML c2x = cf.newConvertToXML("EDI");

os = new FileOutputStream("d:\\SCC\\flight_edi.xml");

c2x.convert(new StreamSource("d:\\SCC\\flight_edi.edi"), new StreamResult(os));

os.close();

System.out.println(" Converted ");

} catch (Exception e) {

}

try {

ConvertFromXML c2x = cf.newConvertFromXML("EDI");

os = new FileOutputStream("d:\\SCC\\flight_edi_new.edi");

c2x.convert(new StreamSource("d:\\SCC\\flight_edi_edi.xml"), new StreamResult(os));

os.close();

System.out.println(" Converted ");

} catch (Exception e) {

}

Input File: flight_edi.edi

UNA:+.? '

UNB+UNOB:4+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'

Output File: flight_edi.xml

<?xml version="1.0" encoding="UTF-8"?>

<UNB>

<UNB01>

</UNB01>

<UNB02>

<UNB0201>STYLUSSTUDIO</UNB0201>

</UNB02>

<UNB03>

<UNB0301>DATADIRECT</UNB0301>

</UNB03>

<UNB04>

</UNB04>

</UNB>

<UNH>

<UNH02>

<UNH0201>ORDERS</UNH0201>

</UNH02>

</UNH>

<BGM>

<BGM01>

</BGM01>

<BGM02>

</BGM02>

</BGM>

<DTM>

<DTM01>

</DTM01>

</DTM>

<GROUP_2>

<NAD>

<NAD02>

</NAD02>

</NAD>

</GROUP_2>

<GROUP_2>

<NAD>

<NAD02>

</NAD02>

</NAD>

</GROUP_2>

<GROUP_28>

<LIN>

<LIN03>

</LIN03>

</LIN>

<QTY>

<QTY01>

</QTY01>

</QTY>

<FTX>

<FTX04>

<FTX0401>XPath 2.0 Programmer's Reference</FTX0401>

</FTX04>

</FTX>

</GROUP_28>

<GROUP_28>

<LIN>

<LIN03>

</LIN03>

</LIN>

<QTY>

<QTY01>

</QTY01>

</QTY>

<FTX>

<FTX04>

<FTX0401>XSLT 2.0 Programmer's Reference</FTX0401>

</FTX04>

</FTX>

</GROUP_28>

<GROUP_28>

<LIN>

<LIN03>

</LIN03>

</LIN>

<QTY>

<QTY01>

</QTY01>

</QTY>

<FTX>

<FTX04>

<FTX0401>Java Server Programming</FTX0401>

</FTX04>

</FTX>

</GROUP_28>

<GROUP_28>

<LIN>

<LIN03>

</LIN03>

</LIN>

<QTY>

<QTY01>

</QTY01>

</QTY>

<FTX>

<FTX04>

<FTX0401>Enterprise Service Bus</FTX0401>

</FTX04>

</FTX>

</GROUP_28>

<UNS>

</UNS>

<CNT>

<CNT01>

</CNT01>

</CNT>

<UNT>

</UNT>

</ORDERS>

<UNZ>

</UNZ>

</EDIFACT>

How to Convert EDIFACT messages using Stylus Studio

Converting EDIFACT messages using Stylus Studio involves a series of steps, as Stylus Studio is a comprehensive tool for XML, XSLT, and other data integration tasks. Here is a general outline of the process:

Open Stylus Studio:

Launch the Stylus Studio application. XMl to Java object and java object to xml creation using JAXB So download
stylus-studio-enterprise-16-x64.exe

Create a New Project:

Go to File > New > Project.
Name your project and save it.

Import the EDIFACT File:

In your project, right-click and select Import File.
Navigate to your EDIFACT message file and import it.

Convert EDIFACT to XML:

Stylus Studio provides built-in support for converting EDIFACT messages to XML.
Right-click on the EDIFACT file in your project and select Convert to XML.
Stylus Studio will prompt you to choose an EDIFACT message format. Choose the appropriate format that matches your EDIFACT message.
The conversion wizard will guide you through the process, and the output will be an XML representation of the EDIFACT message.

Editing the XML:

Once converted to XML, you can edit the XML as needed within Stylus Studio using its XML editor.

Convert XML Back to EDIFACT (if needed):

If you need to convert the edited XML back to an EDIFACT message, Stylus Studio also supports this.
Right-click on the XML file and select Convert to EDIFACT.
Follow the wizard to convert the XML back to the EDIFACT format.

Example EDIFACT to XML Conversion

Below is a simplified example of how an EDIFACT message might look and how you could process it:

Example EDIFACT Message:

UNH+1+ORDERS:D:96A:UN:EAN008'

BGM+220+BKOD99+9'

DTM+137:20020910:102'

NAD+BY+5412345000176::9'

LIN+1++1234567890123:SRV'

QTY+47:1020:EA'

Converted XML (simplified example):

xml

<UNH>

<MessageType>ORDERS</MessageType>

</UNH>

<BGM>

</BGM>

<DTM>

</DTM>

<NAD>

</NAD>

<LIN>

</LIN>

<QTY>

</QTY>

Notes

The conversion to XML helps in making the data readable and easier to manipulate.
Ensure that you select the correct EDIFACT format during the conversion process.
Stylus Studio’s documentation and support can provide more detailed guidance specific to your needs and EDIFACT message types.

Additional Resources

Stylus Studio Documentation: For detailed steps and features.
EDIFACT Standards Documentation: To understand the specific segments and elements in your EDIFACT messages.
Stylus Studio Support and Community: For assistance and troubleshooting.

Conclusion

EDIFACT is a structured and standardized format for EDI, used widely in various industries. Understanding its segments and data elements is crucial for correctly interpreting and processing EDIFACT messages. The provided example demonstrates how to parse an EDIFACT message in Java, serving as a starting point for more complex processing and integration tasks.