Introduction to EDI

1 1 1
Document Control
Change Record
Date Author Version Change Reference
10th Mar 2010 Pranav Salvi 1.0

Reviewers

Name Role

2 2 2
Unit II – EDI Overview

3 3
Unit Objectives
• At the end of this unit, you would be able
– To showcase basic understanding on EDI (Electronic Data Interchange).

4 4 4
Understanding EDI
 What is EDI?
 Types of EDI Standards
 How EDI Looks?
 Constitutes of EDI X12
 EDI Data Segments & Elements
 Illustration
 Where EDI Used?
 Advantages Of EDI
 Appendix

5 5 5
What is EDI?

Electronic Data Interchange is the exchange of

standardized business documents from computer
to computer.
• Exchange of Data (File)
• Standard Format
• Automated – No human Interventions

6 6 6
Types of EDI Standards
• UN/EDIFACT - the main standard supported by the
UN
• ANSI X12 - common in USA, Canada and Australia
• TRADACOMS - predominantly used in the UK

7 7 7
How EDI Looks?
X12

8 8 8
Sample X12
ISA*00* *00* *ZZ*TOSHIBA-ISA_P *14*0060765250728 *091014*2045*U*00401*000001040*0*P*|
GS*PO*TOSHTEGP*0060765250728*20091014*2045*1035*X*004010
ST*850*1035
BEG*00*SS*G1779272**20091014
REF*EV*SAPR01
REF*VX*CZ680517284
REF*VN*80T806395001
REF*PO*PO20046_G1779272
REF*OQ*7206116719
REF*9H*CLCEAE
REF*4B*FGICUS
CSH*BK
TD5*Z*2*GEBW
N9*L1*SHIPPING INSTRUCTIONS
N1*ST*TAQA Britani Limited*91*0500116706
N2*IT Department*TAQA House
N3*Prospect Road*Aberdeenshire
N4*Aberdeen**AB32 6FE*GB*CC*Great Britain
N1*BT*Hewlett Packard International SARL*91*ZHPS5RR
N3*Route du Nant-d'Avril 150
N4*Meyrin/Geneva**1217*CH*CC*Switzerland
N1*BG*Hewlett-Packard Caribe B.V.*91*HP00G1CZ
N2*Czech VAT Registration
N3*Startbaan 16
N4*Amstelveen**1187 XR*NL*CC*Netherlands
N1*PL*TOSHIBA EUROPE GMBH*91*0020277233
SE*25*1035
GE*1*1035
IEA*1*000001040

9 9 9
EDIFACT

10 10 10
Sample EDIFACT
UNA:+.? '
UNB+UNOC:3+SENDERID:ZZ+RECEIVERID:ZZ+080212:1815+10267++ORDERS++1'
UNG+ORDERS+SENDERID+RECIEVERID+080212:1815+10267+UN+D:97A'
UNH+1+ORDERS:D:97A:UN:EDPO04'
BGM+220+798405-48+9'
DTM+4:20080212:102'
RFF+AEM:DIRECT'
NAD+BY+SIDDU++HOSPET+DHARWAD+KA+94039+IN'
CTA+PD+:Barath, JAMES, L'
COM+X69591/970/:TE'
CUX+2:USD:9'
PAT+1++5:3:CD:45'
TDT+12++++EXEL GLOBAL LOGIS:172:92'
TOD+6+CC+EXW'
LIN+1++003-2383-02:BP::92'
IMD++3+:::STK, , 314831203 , N,SL8500 DR'
QTY+21:1:EA'
PRI+INF:82.08:CT'
RFF+LI::113'
SCC+1'
UNS+S'
UNT+24+1'
UNE+1+10267'
UNZ+1+10267’

11 11 11
TRADACOMS

12 12 12
Sample Tradacoms
STX=ANAA:1+5000116000123:RETAIL STORES LTD+5013546110456:RETAIL
SERVICES+051123:134748+358767+ +ORDHDR'
MHD=1+ORDHDR:9'
TYP=0430+NEW-ORDERS'
SDT=5021839054321+RETAIL SERVICES'
CDT=5000119012345+RETAIL STORES LTD++220430231'
FIL=513+1+051123'
MTR=6'
MHD=2+ORDERS:9'
CLO=5000116001234:0100821'
ORD=LM82191329029::051123'
DIN=051130+++ANY PROBS CALL LISA 01234 123783:EMAIL?: LISA.JONES@UK.RETAIL.COM'
OLD=13+::05000462909700++:8173854+4+336++++RETAIL C53 BLACK INK'
OTR=13'
MTR=18'
MHD=4+ORDTLR:9'
OFT=3'
MTR=3'
MHD=5+RSGRSG:2'
RSG=358767+5013546110456'
MTR=3'
END=5'

13 13 13
EDI X12 Structure
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID
*080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*OO*SA*212347**20080211^
REF*CT*CONTRACT^
REF*CO*800888-119^
REF*ZZ*827028^
TAX*13-3460176***********0^
FOB*PP***02*FOB*FO*SLR TERMS^
N1*BT*ANIL*ANCON SYSTEMS^
N2*ANCON OFFICE^
N3*1320 BTM II STAGE*SEVENTH CRS^
N4*BLORE*KA*560076*IN^
N1*ST*INFY*92*GATE4^
N2*HOSU ROAD^
N4*BLORE*KA*560100*IN^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SCH*2*EA**A540-6574-01*002*20080211*000000****1*PST^
SE*17*0001^
GE*1*100013642^
IEA*1*100013642^

14 14 14
15 15 15
16 16 16
17 17 17
Fig [1]*

18 18 18
 Transaction Set*
A transaction set is a single business document such as a Purchase Order, Invoice, or Shipment Notice.
There are hundreds of Transaction Sets available in the ANSI ASC X12 standards. Each set of transaction
data is identified by a three digit code number.

Data Segments
Each transaction set is made up of a collection of data segments- the 2 or 3 character abbreviation used as
reference in the Segment Directory. Data segments, also known as Segment Tags, begin each line or record
in an EDI data string. Similar to a postal address, NAD would be an example data segment, reporting
geographic location, and including the data elements for a city name, a state or province code, a postal
code, and a country code. Data segments logically relate data elements in a defined se

Data Elements
Data elements, the smallest unit of information in a transaction set/message, represent a qualifier, a value,
or text and are identified by a reference number in the Data Element Dictionary, defining the specifications
for each.
Data elements have three principal attributes:
• Condition designator (mandatory, conditional, optional)
• Type of data element (ID, alphanumeric, numeric or decimal, etc.)
• Character length (minimum/maximum length)

Composite/Component Data Structures

UN/EDIFACT and newer versions of ASC X12 may use two separate pieces of data in a single data element.
The complete data element is called a composite data element. The pieces of the composite are called
components. The structure of many data segments includes one data element for a value and a second data
element for a qualifier. A composite data structure, on the other hand, contains within a single data element
both a qualifier and a value. A data dictionary would be required to define the qualifier. When composites
are used with variable type data, the First component is typically the value being qualified. The second
component is typically the qualifier, which defines what the first component (the value) means.

* Source of Information - www.ansi.org

19 19 19
Envelopes

Interchange (ISA-IEA) Envelope

Functional group (GS-GE) Envelope
Transaction Set (ST-SE) Envelope

ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^

GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^

20 20 20
 Interchange (ISA) Envelope should always end with interchange
trailer (IEA) Envelope
 Functional Group (GS) Header Envelope should always end with
Functional Group (GE) trailer Envelope
 Transaction Set (ST) Header Envelope should always end with
Transaction Set (SE) trailer Envelope
ISA*00* *00* *ZZ*CELORGC02 *ZZ*IBMIRLPROD *021018
GS*IN*CELITALY*IBMIRELAND*20021018*0229*8899*X*004010¬
ST*810*88990001¬

SE*22*88990001¬

GE*1*8899¬

IEA*1*000008899¬

21 21 21
EDI Envelope Structure
ISA Interchange header
GS Functional Group header
ST Transaction Set header
BEG
DTM
Example ASC X12 850 Purchase Order

PO1
REF
CTT
AMT
SE Transaction Set trailer
ST Transaction Set header
BEG
DTM
PO1
REF
CTT
AMT
SE Transaction Set trailer

GE Functional Group trailer Purchase Order

GS Functional Group header
ST Transaction Set header
Data Segments
BEG
DTM
PO1
REF
CTT
AMT
SE Transaction Set trailer
ST Transaction Set header
BEG
DTM
PO1
REF
CTT
AMT
SE Transaction Set trailer

GE Functional Group trailer

IEA Interchange trailer

22 22 22
EDI Envelope Structure
ISA Interchange header
GS Functional Group header
BEG
ST Transaction Set header One ISA can have multiple
DTM GS
Example ASC X12 850 Purchase Order

PO1
REF
CTT
AMT
SE Transaction Set trailer
ST Transaction Set header
BEG
DTM
PO1
REF
CTT
AMT
SE Transaction Set trailer
Purchase Order
GE Functional Group trailer Data Segments
GS Functional Group header
ST Transaction Set header
BEG
DTM
PO1
REF
CTT
AMT
SE Transaction Set trailer
ST Transaction Set header
BEG
DTM
PO1
REF
CTT
AMT
SE Transaction Set trailer

GE Functional Group trailer

IEA Interchange trailer

23 23 23
EDI Envelope Structure
ISA Interchange header
GS Functional Group header
ST Transaction Set header Each GS can belong to
BEG
DTM different transactions
PO1
Example ASC X12 850 Purchase Order

REF
CTT
AMT
SE Transaction Set trailer
ST Transaction Set header
BEG
DTM
PO1
REF
CTT
AMT
SE Transaction Set trailer Purchase Order
GE Functional Group trailer Data Segments
GS Functional Group header
ST Transaction Set header
BEG
DTM
PO1
REF
CTT
AMT
SE Transaction Set trailer
ST Transaction Set header
BEG
DTM
PO1
REF
CTT
AMT
SE Transaction Set trailer

GE Functional Group trailer

IEA Interchange trailer

24 24 24
25 25 25
EDI Envelope Structure
ISA Interchange header
GS Functional Group header
BEG
ST Transaction Set header Each GS can have multiple
DTM ST
Example ASC X12 850 Purchase Order

PO1
REF
CTT
AMT
SE Transaction Set trailer
ST Transaction Set header
BEG
DTM
PO1
REF
CTT
AMT
SE Transaction Set trailer

GE Functional Group trailer Purchase Order

GS Functional Group header Data Segments
ST Transaction Set header
BEG
DTM
PO1
REF
CTT
AMT
SE Transaction Set trailer
ST Transaction Set header
BEG
DTM
PO1
REF
CTT
AMT
SE Transaction Set trailer

GE Functional Group trailer

IEA Interchange trailer

26 26 26
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*OO*SA*212347**20080211^
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
ST*850*0001^
BEG*OO*SA*212347**20080211^
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
GE*1*100013642^
GS*PS*SENDERID*RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
GE*1*2^
IEA*2*100013642^

27 27 27
28 28 28
29 29 29
30 30 30
31 31 31
32 32 32
33 33 33
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^

X12 Version
Segment ID

SenderID

Sender ID
Qualifier

ReceiverID

ReceiverID
Qualifier

X12 EDI release versions

34 34 34
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^

X12 Version
Segment ID

SenderID

Sender ID
Qualifier

ReceiverID

ReceiverID
Qualifier

X12 EDI release versions

35 35 35
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^

EDI Version
Segment ID

SenderID

Sender ID
Qualifier

ReceiverID

ReceiverID
Qualifier

Control Number

36 36 36
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^

EDI Version
Segment ID

SenderID

Sender ID
Qualifier

ReceiverID

ReceiverID
Qualifier

Control Number

Control Number is the unique one which

helps in finding duplicate in EDI data

37 37 37
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^

EDI Version
Segment ID

SenderID

Sender ID
Qualifier

ReceiverID

ReceiverID
Qualifier

Control Number

Indicator denotes whether the file

is Production (P) or Test (T) or
Information(I) Indicator

38 38 38
 Acknowledge

ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^

EDI Version
Segment ID

SenderID

Sender ID
Qualifier

ReceiverID

ReceiverID
Qualifier

Control Number
1- Send an EDI file to Sender saying that
Receiver has received EDI file
0-Don’t send on EDI file to Sender saying that
Receiver has received EDI file
Indicator

39 39 39
Interchange Control Header (ISA)
Element ID Element Number   Element Name   Attributes  Comments
ISA0 744 Authorize Info Qualifier M ID 02/02 Use "00"
ISA02 745 Authorize Info M AN 10/10 Use ten spaces
ISA03 746 Security Info. Qualifier M ID 02/02 Use "00" for no password
ISA04 747 Security Info. M AN 10/10 Use ten spaces
ISA05 704 Interchange ID Qualifier M ID 02/02 Use "01", "12", or "ZZ"
DUNS number if
ISA06 705 Interchange Sender ID M ID 15/15 ISA05="01".
Left justify, space fill.
ISA07 704 Interchange ID Qualifier M ID 02/02 Use "01".
ArvinMeritor DUNS number
ISA08 706 Interchange Receiver ID M ID 15/15
"006414361".
ISA09 373 Date M DT 06/06 Date of creation (YYMMDD).
ISA10 337 Time M TM 04/04 Time of creation (HHMM).
ISA11 726 Interchange Standards ID M ID 01/01 Use "U" for USA.
ISA12 703 Interchange Version ID M ID 05/05 Use "00200".
Sequential number starting
with 000000001 and
ISA13 709 Interchange Control Number M NO 09/09 incremented by 1 for each
subsequent ISA between
sender and receiver.
ISA14 749 Acknowledge M ID 01/01 Use "0" for no Ack. Req.
Use "T" for test data and "P"
ISA15 748 Test Indicator M ID 01/01
for production data.
ISA16 701 Sub-element Separator M AN 01/01 Use "*".

40 40 40
 IEA*2*100013642

Segment ID

Control Number

Number of GS
segments

Control Number should be same as ISA

Control Number

41 41 41
Interchange Control Trailer (IEA)
Element ID Element Number  Element Name  Features   Comments

Number of GS
segments included
IEA01 405 Number of Included Groups M NO 01/05
between ISA and this
IEA.

IEA02 709 Interchange Control M AN 04/09 Must match ISA13.

42 42 42
 GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010

Segment ID

Type Of Business
Transaction

43 43 43
 GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010

Segment ID

Type Of Business
Transaction

PO – Purchase Order, Sender can place

order for buying goods from Receiver
using this transaction

44 44 44
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010

Segment ID SenderID

ReceiverID

Type Of Business
Transaction Control Number

Control Number is the unique one which

helps in finding duplicate in EDI data
(Group Segment)

45 45 45
 GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010

Segment ID SenderID

ReceiverID

Type Of Business
Transaction Control Number

Control Number increments for each entry

of EDI data with the same
Sender/Reciever ID

46 46 46
 GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010

X12 Version

Segment ID SenderID

ReceiverID

Type Of Business
Transaction Control Number

X12 EDI release versions

47 47 47
Functional Group Header (GS)

Element ID Element Number   Element Name Features   Comments

"PO", "QG", "IN", "SH",

GS01 479 Functional ID M ID 02/02
"AG", "RC" or "FA"
GS02 142 Application Sender Code M ID 02/12 Use DUNS number
GS03 124 Application Receiver Code M ID 02/12 Use "006414361".
GS04 29 Data Interchange Date M DT 06/06 Date created (YYMMDD)
GS05 30 Data Interchange Time M TM 04/04 Time created (HHMM)
Start with 1 and increment
by 1
for each subsequent GS
GS06 28 Data Interchange Control number M NO 01/09 segment between
interchange and application
sender and receiver
combinations.
Use "X" for ANSI X12 code
GS07 455 Responsibility M ID 01/02
format

GS08 480 Version M ID 01/12 X12 version ID’s

48 48 48
 GE*1*100013642

Segment ID

Control Number

Number of ST
segments

Control Number should be same as GS

Control Number

49 49 49
Functional Group Trailer (GE)

Element ID Element Number Element Name Features  Comments

Total count of
GE01 97 Number of Included Transaction Sets M NO 01/06 transaction sets in
functional group.

Must be identical to the

same data element in
GE02 28 Data Interchange Control Number M AN 01/09
the associated group
header (GS).

50 50 50
 ST*850*0001

Segment ID

Type Of Business
Transaction

850 (PO) – Purchase Order, Sender can

place order for buying goods from
Receiver using this transaction

51 51 51
 ST*850*0001

Segment ID Control Number

Type Of Business
Transaction

52 52 52
 ST*850*0001

Segment ID Control Number

Type Of Business
Transaction

Control Number is the unique one which

helps in finding duplicate in EDI data
(Group Segment)

53 53 53
 ST*850*0001

Segment ID Control Number

Type Of Business
Transaction

Control Number increments for each entry

of EDI data with the same
Sender/Reciever ID

54 54 54
Transaction Set Header (ST)

Element ID Element Number Element Name Features  Comments

Code uniquely
ST01 143 Transaction Set Identifier Code M ID 3/3 identifying a Transaction
Set

Identifying control
number that must be
unique within the
transaction set
ST02 329 Transaction Set Control Number M AN 4/9
functional group
assigned by the
originator for a
transaction set

55 55 55
 SE*10*0002

Segment ID Control Number

Number of segments
between SE & ST

56 56 56
Transaction Set Trailer (SE)

Element ID Element Number Element Name Features  Comments

Total number of
segments included in a
SE01 96 Number of Included Segments M N0 1/10 transaction set including
ST and SE
segments

Identifying control
number that must be
unique within the
transaction set
SE02 329 Transaction Set Control Number M AN 4/9
functional group
assigned by the
originator for a
transaction set

57 57 57
 Apart from basic segment of EDI (Envelope
Segments – ISA-IEA, GS-GE , ST-SE), Other
segments will be depends upon type of transaction
which will be discussed with the help of EDI Tools
later

58 58 58
Illustration 1

Is this EDI file (EDI Compliance) ?

59 59 59
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*OO*SA*212347**20080211^
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
GE*1*100013642^
GS*PS*SENDERID*RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
GE*1*2^
IEA*2*100013642^

60 60 60
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*OO*SA*212347**20080211^
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
GE*1*100013642^
GS*PS*SENDERID*RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
GE*1*2^
IEA*2*100013642^

61 61 61
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*OO*SA*212347**20080211^
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
GE*1*100013642^
GS*PS*SENDERID*RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
GE*1*2^
IEA*2*100013642^

62 62 62
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*OO*SA*212347**20080211^
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^ Transaction ST 830 cannot be in
ST*830*0002^
Group Segment (PO – Purchase
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^ Order - 850)
FST*12000*C*D*20071214^
SE*5*0002^
GE*1*100013642^
GS*PS*SENDERID*RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
GE*1*2^
IEA*2*100013642^

63 63 63
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*OO*SA*212347**20080211^
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
ST*850*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
GE*1*100013642^
GS*PS*SENDERID*RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
GE*1*2^
IEA*2*100013642^

64 64 64
Illustration 2

Is this EDI file (EDI Compliance) ?

65 65 65
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*00*SA*212347**20080211^
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
ST*850*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*8*0002^
GE*1*100013642^
GS*PS**RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0012^
GE*1*2^
IEA*2*100013642^

66 66 66
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*00*SA*212347**20080211^
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
ST*850*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*8*0012^
GE*1*100013642^
GS*PS**RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0012^
GE*1*2^
IEA*2*100013642^

67 67 67
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*00*SA*212347**20080211^
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
ST*850*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*8*0012^
GE*1*100013642^
GS*PS**RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0012^
GE*1*2^
IEA*2*100013642^

68 68 68
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*00*SA*212347**20080211^
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
ST*850*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*8*0002^
GE*1*100013642^
GS*PS**RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^ Number of segments between ST
FST*12000*C*D*20071214^ & SE is only 5
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0012^
GE*1*2^
IEA*2*100013642^

69 69 69
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^ Number of ST = 2 between GS
BEG*00*SA*212347**20080211^ and GE
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
ST*850*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*8*0002^
GE*1*100013642^
GS*PS**RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0012^
GE*1*2^
IEA*2*100013642^

70 70 70
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*00*SA*212347**20080211^ Sender ID is missing
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
ST*850*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*8*0002^
GE*1*100013642^
GS*PS**RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0012^
GE*1*2^
IEA*2*100013642^

71 71 71
ISA*00* *00* *01*SENDERID *ZZ*RECIEVERID *080211*1318*U*00400*100013642*0*P*:^
GS*PO*SENDERID*RECIEVERID*20080211*1318*100013642*X*004010^
ST*850*0001^
BEG*00*SA*212347**20080211^
N1*ST*INFY*92*GATE4^
PO1*1*2*EA*247.953*CP*BP*F140-6574-01*****ZZ*A540-6574-01*EL*1^
SE*5*0001^
ST*850*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*8*0002^
GE*1*100013642^
GS*PS**RECIEVERID*20071025*0510*2*X*004010^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^
FST*12000*C*D*20071214^
SE*5*0002^
ST*830*0002^
BFR*05*708261452471446**DL*A*20071214*20071214*20070826***H600001-TMM^
LIN*001*BP*M16658140JQ***VP*C0805B106K010T^ Control Number is not as same as
FST*12000*C*D*20071214^ ST
SE*5*0012^
GE*1*2^
IEA*2*100013642^

72 72 72
Paper Exchange vs.
EDI

Paper Exchange

73 73 73
Paper Exchange vs.
EDI

EDI Exchange

74 74 74
Paper Exchange vs.
EDI

75 75 75
Paper Exchange vs.
EDI

76 76 76
Paper Exchange vs.
EDI

77 77 77
Paper Exchange vs.
EDI

78 78 78
Paper Exchange vs.
EDI

79 79 79
Paper Exchange vs.
EDI

80 80 80
Advantages of EDI

Manage huge volumes of transactions

Less operating cost

Eliminates delay

Eliminates data entry errors

81 81 81
Advantages of EDI

Manage huge volumes of transactions

Less operating cost

Eliminates delay

Eliminates data entry errors

82 82 82
Advantages of EDI

Manage huge volumes of transactions

Less operating cost

Eliminates delay

Eliminates data entry errors

83 83 83
Advantages of EDI

Manage huge volumes of transactions

Less operating cost

Eliminates delay

Eliminates data entry errors

84 84 84
Advantages of EDI

Manage huge volumes of transactions

Less operating cost

Eliminates delay

Eliminates data entry errors

85 85 85
Complete Procurement Process
Vendor- manufacturer Re-Seller
864 Text Message
Client file list of codes
832 Sales Catalog
Available products Product data Base
867 Product transfer Report
Sales Forecasting Inventory and Sales
System 846 Inventory Report System
846 Inventory Report
Available inventory Client services
856 Advance Ship Notice
Order processing 856 Advance Ship Notice Purchasing
system 856 Advance Ship Notice
system
856 Advance Ship Notice
Client services 856 Advance Ship Notice
856 Advance Ship Notice
Distribution system Receiving
832 Sales Catalog
Invoice Processing Product data Base
832 Sales Catalog
Receivables Product data Base

86 86 86
Standard Terminalogy

Business Document X12 Transaction Sets EDIFACT Messages

Price/Sales Catalog 832 PRICAT

Purchase Order 850 ORDERS

PO Change 860 ORDCHG

PO Acknowledgement 855/865 ORDRSP

Invoice 810 INVOIC

Payment order 820 PAYORD

Request For Quotation 840 REQOTE

Forecast 830 DELFOR

87 87 87
List of transactions sets used in X12

EDI X12
Transaction Sets

88 88 88
HOW DOES EDI WORK

Fig [2]*

89 89 89
Value Added Network - VAN
A Value Added Network, also referred to as an EDI VAN, is a private network for connectivity and exchange of
EDI data between enterprises. Using a value-added network (VAN) for the transmission of files is traditionally
seen as the most secure way of communication. Unlike the Internet, which is public VANs are privately run;
companies pay to be registered users and for services. VANs offer services such as EDI packet transportation,
conversion between different EDI versions and standards, audit trails, security, trading partner identification,
education, and consulting. Multiple VAN providers are in existence and bridges are in place between these in
order to enable the subscribers of one to do business with the subscribers of another. Connectivity options to the
VAN itself from any enterprise vary depending on the VAN provider and connectivity software vendor.

Apart from pure communication, a VAN also provides value-adds such as:
• Built-in security features that help protect against unauthorized access to customer data
• Restart and recovery facilities that help to reduce or eliminate the impact of communications
interruptions.
• Archive capability for the online retention of data copies
• 24x7 availability
• Notification of message arrivals that meet predefined criteria, such as a message from a specific trading
partner.

The VAN Gateway software will drop off and pick up EDI documents via the mailbox. The VAN provides store-
and-forward mailbox services. The physical communication system between the VAN Gateway and the VAN
network can vary from dial-up to FTP, or some proprietary communication technology.[2]*

90 90 90
Applicability Statement - AS
AS1, AS2, and AS3 security standards ensure the authentication, message integrity, no repudiation, and privacy of
EDI data sent over the Internet. AS2, in particular, is being embraced by companies across many industries,
notably grocery and retail, because it allows companies to take advantage of inexpensive HTTP communications as
an alternative to more costly third-party value-added networks (VANs). 

Applicability Statement 1 AS1 uses email attachments with S/MIME (Secure/Multipurpose Internet Mail
(AS1) for SMTP protocol, Extensions) encryption and security over SMTP (Simple Mail Transfer
asynchronous Protocol) in batch mode.

Applicability Statement 2
AS2 provides S/MIME encryption over HTTP (Hyper Text Transfer Protocol)
(AS2) for HTTP protocol,
and is real-time peer-to-peer
synchronous

Applicability Statement 3
AS3 provides S/MIME encryption over FTP (File Transfer Protocol) in a
(AS3) for FTP protocol,
server/client paradigm
synchronous

91 91 91
Relationship Between B2B, EAI AND EDI
 B2B is the exchange of business docs between 2 enterprises or organizations
 EAI is the exchange of Business docs with in an organization
 EDI is one of the industrial standard format in which the documents are exchanged
 EAI is morphing with B2B to become simply application integration.
 While EAI and B2B application integration share many of the same approaches and
technologies, they do have unique characteristics.
 EAI typically deals with the integration of applications and data sources within an enterprise
to solve a local problem.
 EAI lacks the pure B2B features (such as community management, profile management, and
sophisticated security mechanisms), and deep support for B2B standards, such as Open
Buying on the Internet (OBI), Extensible Markup Language (XML), Commerce XML
(cXML),and Electronic Data Interchange (EDI).

92 92 92
Unit Summary
• In this unit, you have learnt the following:
– 1. What is EDI?
– 2. Types of EDI Standards
– 3. How EDI Looks?
– 4. Constitutes of EDI X12
– 5. EDI Data Segment & Elements
– 6. Envelopes
– 7. Comparison and Benefits of EDI

93 93 93
Sources of Information

• Content in this presentation have been compiled solely by using

information from following sources:
i. www.x12.org

ii. www.ansi.org

References :
[1] http://www.redbooks.ibm.com/redbooks/pdfs/sg246906.pdf

[2] http://www.redbooks.ibm.com/redbooks/pdfs/sg246906.pdf

94 94 94
Thank You

95 95 95