EDI format

[Former Member]

what is the format of EDI Messages,

[Former Member · Accepted solution]

refer:

http://www.ifla.org/VI/5/reports/rep4/42.htm

Sample EDI ANSI x12 file

ISA00 00 1204428210387 01070169594 0802211408U0040110T><0x85>

GSSH044282103870701695942008022114081X004010<0x85>

ST8560001<0x85>

BSN00008705080420080221140841*0004<0x85>

HL11*S<0x85>

TD1*0*MAA-4040 8562 DT.30.G0KG<0x85>

TD3TL*123456<0x85>

TD5*****AIR FREIGHT<0x85>

N1STORCHARD HILL LTD92326155<0x85>

N3*12345 Street<0x85>

N4BELCHER TOWNIL01007US<0x85>

HL21*O<0x85>

PRF*3108<0x85>

HL32*I<0x85>

LIN00002BP*W200<0x85>

SN1*5EA<0x85>

HL41*P<0x85>

MANW0087050804<0x85>

CTT*4<0x85>

SE170001<0x85>

GE11<0x85>

IEA11<0x85>

Edited by: preethi Prabhu RadhaKrishnan on Sep 5, 2008 6:46 AM

[Former Member]

Hi,

EDI message follow its own standard as you have in XML.

You have various EDI formats like

ANSI X12

EDIFACT

TRADACOM

COPS

INTF

Regards,

Nithiyanandam

[Former Member]

Hi,

The two main EDI standards that are currently used. the ASC X12 group of standards supported by the American National Standards Institute (ANSI) and the EDIFACT standards supported by the United Nations Economic Commission for Europe (UN/ECE).

The ANSI X12 standards specify:

1.the segments used in a transaction set,

2.the sequence in which the segments must appear

3.whether segments are mandatory or optional,

4.when segments can be repeated

5.how loops are structured and used

X12 message formats:

Interchange Control Structures

Functional Groups

Transaction Sets

Segments

Data elements

EDIFACT Message Structure:

There are also a number of "service" segments that must be included in all EDIFACT transmission. These are:

Interchange Header: UNB

Message Header: UNH

Message Trailer: UNT

Interchange Trailer: UNZ.

Regards,

Prakasu

[former_member750652]

hi Teja,

Segment Types

ISA Interchange Control Header

GS Function Group Header

ST Transaction Set Header

SE Transaction Set Trailer

GE Function Group Trailer

IEA Interchange Control Trailer

Segment Formats

Segment Formats

ISA*fields^

GS*fields^

ST*fields^

SE*fields^

GE*fields^

IEA*fields^

Note: * = Field Separator; ^ = Segment Separator

Segment Fields

ISA Segment

ISA01 Authorization Information Qualifier

ISA02 Authorization Information

ISA03 Security Information Qualifier

ISA04 Security Information

ISA05 Interchange ID Qualifier

ISA06 Interchange Sender ID

ISA07 Interchange ID Qualifier

ISA08 Interchange Receiver ID

ISA09 Interchange Date

ISA10 Interchange Time

ISA11 Interchange Control Standards ID

ISA12 Interchange Control Version Number

ISA13 Interchange Control Number

ISA14 Acknowledgement Requested

ISA15 Test Indicator

ISA16 Subelement Separator

GS Segment

ISA*fields^

GS01 Functional ID code

GS02 Application Sender's Code

GS03 Application Receiver's Code

GS04 Date

GS05 Time

GS06 Group Control Number

GS07 Responsible Agency Code

GS08 Version/Rel. Ind. ID Code

ST Segment

ST01 Transaction set ID code

ST02 Transaction set control number

SE Segment

SE01 Number of included segments

SE02 Transaction set control number (same as ST02)

GE Segment

GE01 Number of Transaction Sets Included in this Function Group

GE02 Group Control Number (same as GS06)

IEA Segment

IEA01 Number of Included Functional Groups

IEA02 Interchange Control Number (same as ISA13)

This output file uses the X12 EDI standard.

The segment delimiter is a backslash ("").

The element delimiter is an asterisk ("*").

Sample File

Note: Linefeeds and "(Continued)" notes inserted for clarity

ISA00 00 01123454321 *01(Continued)

*012341234 0310162359U004019876001110P:

GSRA1234543210123412340310162359987600111X004010

ST820987600111

BPRC77.77CACHCTX01234056789DA0099109999(Continued)

12345432101045678099DA1008973899031016

TRN10310162359

REFAAEDI6

N1PRWHIZCO OF AMERICA INC

N355 MEGAPLEASANT ROADSUITE 999

N4SUPERVILLENY*10954

N1PEYOWZACO

ENT*1

RMRAP1111111111111111PO11.11

RMRAP2222222222222222PO22.22

RMRAP4444444444444444PO44.44

DTM055031016

SE000000014987600111

GE1987600111

IEA1987600111

Header Section

ISA u2014 Interchange Control Header

Example (with element number marked above each one):

-

-

---

01 02 03 04 05 06 07

ISA00 00 01123454321 *01(Continued)

·································································

08 09 10 11 12 13 14 1516

*012341234 0310162359U004019876001110P:

-

-

---

All elements as shown, except:

ISA09 Date from the date_entered field of the input file

ISA10 End-of-day time (2359)

ISA13 Interchange Control Number

This is a sequential number that goes up by one with each file

GS u2014 Functional Group Header

Example (with element number marked above each one):

-

-

---

01 02 03 04 05 06 07 08 GSRA1234543210123412340310162359987600111X004010

-

-

---

All elements as shown, except:

GS04 Date from the date_entered field of the input file

GS05 End-of-day time (2359)

GS06 Interchange Control Number u2014 value matches ISA13

Note: GS08 ("004010") resembles but is not the same as ISA12

ST u2014 Transaction Set Header

Example: ST820987600111

ST01 As shown (820 = "Electronic Funds Transfer")

ST02 Interchange Control Number u2014 value matches ISA13

BPR u2014 Beginning Segment for Payment Order / Remittance Advice

Example (with element number marked above each one):

-

-

---

01 02 03 04 05 06 07 08 09 10 BPRC99.99CACHCTX01234056789DA0099109999(Continued) ·································································

11 12 13 14 15 16 12345432101045678099DA1008973899031016

-

-

---

All elements as shown, except:

BPR02 Total of the amount fields from the input file

BPR03 Credit/Debit flag (C or D u2014 normally C)

BPR16 Date from the date_entered field of the input file

TRN u2014 Trace Segment

Example: TRN10310162359

TRN01 As shown

TRN02 Date from the date_entered field of the input file, plus 2359

REF u2014 Reference Numbers

Example: REFAAEDI6

Transmitted as shown

Nx u2014 Name Segments

Examples:

N1PRWHIZCO OF AMERICA INC

N355 MEGAPLEASANT ROADSUITE 999

N4SUPERVILLENY*10954

N1PEYOWZACO

Transmitted as shown

ENT u2014 Entity Loop

Example: ENT*1

Transmitted as shown

Detail Section

RMR u2014 Remittance Advice Accounts Receivable Open Item Reference

Example: RMRAP1111111111111111PO11.11

RMR01 As shown

RMR02 Customer's YowzaCo Account Number

RMR03 As shown

RMR04 Amount paid

Trailer Section

DTM u2014 Date/Time Reference

Example: DTM055031016

DTM01 As shown

DTM02 Date from the date_entered field of the input file

SE u2014 Transaction Set Trailer

Example: SE000000014987600111

SE01 Number of RMRs + 11

SE02 Interchange Control Number u2014 value matches ISA13

GE u2014 Functional Group Trailer

Example: SE000000014987600111

Example: GE1987600111

GE01 As shown

GE02 Interchange Control Number u2014 value matches ISA13

IEA u2014 Interchange Control Trailer

Example: IEA1987600111

IEA01 As shown

IEA02 Interchange Control Number u2014 value matches ISA13

Trailing backslash marks end of data transmission envelope

Thanks,

Raj.

Edited by: Ramakrishna kopparaju on Sep 5, 2008 7:02 AM

[Former Member]

HI,

Go through the below links to understand the EDI strucutre of different message type.

http://www.edifactory.de/index.php?p=unedifact/main

http://www.edifactory.de/messages.php?s=D96A

chirag

[Former Member]

A valuable source of information is http://www.edigenie.com/