training edi basics ii

8/14/2019 Training Edi Basics II

1/130

1

Please Read

This slide show automatically advances, but you can still control the slides withthe following keys:

PgDn : advances to the next slidePgUp : reverses to the previous slide

It also has sound. So please have the speakers on your computer turned on before proceeding to the next screen.

Now sit back, learn and enjoy the show


2/130

2


3/130

3


4/130

4


5/130

5


6/130

6


7/130

7

EDI VALIDATION

EDI FileCompanion Guide

Companion Guide Detail


8/130

8

EDI VALIDATION

EDI FileCompanion Guide Overview

Companion Guide Detail


9/130

9

EDI File

Companion Guide


10/130

10

EDI File

Companion Guide

Segment ID is BEG


11/130

11

EDI File

Companion Guide

BEG segment must be used


12/130

12

EDI File

Companion Guide


13/130

13

EDI File

Companion GuideElement is type ID


14/130

14

EDI File

Companion GuideElement must have 2 characters


15/130

15

Companion Guide

EDI File


16/130

16

Companion Guide

EDI File

00 is a valid code value


17/130

17

Position NumbersRequirements

User RequirementsMinimum and Maximum Length

Maximum UsageLoop RepeatsSyntax Rules

Code ListExternal Code List

Value ListValue Reference

Semantic ReferencesObject Variables

Triggers/InstancesIndustry/Trading Partner Specific


18/130

18

User readable

Machine readable


19/130

19

User readable

Machine readable


20/130

20

User readable

Machine readable


21/130

21

An example of a SEF file viewed with a text editor


22/130

22

SEF file viewed with the SEF Manager


23/130

23


24/130

24


25/130

25


26/130

26


27/130

27


28/130

28

An EDI Validation Program

oEdiDoc.LoadSchema "850_4010.SEF, 0

oEdiDoc.LoadEdi "850.X12"

Set oWarnings = oEdiDoc.GetWarnings

For i = 1 To oWarnings.CountSet oWarning = oWarnings.Warning(i)List1.AddItem oWarning.Description

Next


29/130

29




30/130

30





31/130

31






32/130

32




For i = 1 To oWarnings.CountSet oWarning = oWarnings.Warning(i)List1.AddItem oWarning.Description

Next



33/130

33

EDIVALIDATION

PASSEDTEST?

INBOUND EDI

ACCEPT EDI

REJECT EDI

YES

NO


34/130

34

EDIVALIDATION

PASSEDTEST?

INBOUND EDI

ACCEPT EDI

REJECT EDI

YES

NO

SEND BACK EDIACKNOWLEDGMENT


35/130

35

Two types of acknowledgment:

1. Receipt of Interchange

2. Receipt of Functional Group

TA1 segment

997 Functional Group EDI file


36/130

36




TA1 segment



37/130

37




TA1 segment



38/130

38




TA1 segment



39/130

39




TA1 segment



40/130

40




TA1 segment



41/130


42/130

42

The Interchange Acknowledgment

TA1* 000000085 *030798*1738*R*021

Interchange Control Number


43/130

43


TA1*000000085* 030798 *1738 *R*021

Interchange Date

Time


44/130

44


TA1*000000085*030798*1738* R *021

Acknowledgment Code

R = RejectedA = Accepted


45/130

45


TA1*000000085*030798*1738*R* 021

Note Code

021 = Invalid number of included Groups value


46/130

46

1. Acknowledging Receipt of

Functional Group


47/130

47


48/130

48

Acknowledgesone Functional Group


49/130

49


50/130

50


51/130

51


52/130

52


53/130

53


54/130

54


55/130

55


56/130

56


57/130


58/130

58


59/130

59

Generating an EDI Acknowledgment


60/130

60


oAck = oEdiDoc.GetAcknowledgmentoAck.EnableFunctionalAcknowledgment = TrueoAck.EnableInterchangeAcknowledgment = True


oAck.Save Ack_850.X12

oEdiDoc.LoadSchema(850_4010.SEF, 0)oEdiDoc.LoadSchema(997_4010.SEF, 0)



61/130

61


oEdiDoc.LoadSchema(850_4010.SEF, 0)



62/130

62





63/130

63






64/130

64







65/130

65




oAck.Save Ack_850.X12


TA1 / 997 A k l dg t


66/130

66

ISA*00* *00* *ZZ*ABC12345678 *ZZTA1*000005001*061218*0902*A*000~GS*FA*ABC123 *XZY987*20061218*1231*1*X*004010~ST*997*0001~

AK1*PO*1~AK2*850*00001~AK5*A~AK9*A*1*1*1~SE*6*0001~GE*1*1~IEA*1*000000258~

TA1 / 997 Acknowledgment

EDI MAPPING


67/130

67

EDI MAPPING

07/23/200401010023

Delivery DatePO No.Message No

987 AvenueRoad

Inc XYZ0101

AddressCompany Name

PO No

ST*850*00023~BEG*00*SA*0101~DTM*002*20040723~

N1*BT*COMPANY ABC~ N3*123 DRIVE STREET~ N4*STARCITY*CA*76503~ N1*ST*INC XYZ~ N3*987 AVENUE ROAD~ N4*RANCHCITY*TX*30603~SE*30*00023~

EDI file

Existing system

Ship To Table

Message Table

EDI MAPPING


68/130

68

07/23/200401010023


987 AvenueRoad

Inc XYZ0101

AddressCompany Name

PO No

ST*850* 00023 ~BEG*00*SA* 0101 ~DTM*002* 20040723 ~

N1*BT*COMPANY ABC~ N3*123 DRIVE STREET~ N4*STARCITY*CA*76503~ N1*ST* INC XYZ ~ N3* 987 AVENUE ROAD ~ N4*RANCHCITY*TX*30603~SE*30*00023~

EDI file

Existing system

Ship To Table

Message Table

EDI MAPPING

EDI MAPPING


69/130

69

07/23/200401010023


987 AvenueRoad

Inc XYZ0101

AddressCompany Name

PO No

ST*850* 00023 ~BEG*00*SA* 0101 ~DTM*002* 20040723 ~

N1*BT*COMPANY ABC~ N3*123 DRIVE STREET~ N4*STARCITY*CA*76503~ N1*ST* INC XYZ ~ N3* 987 AVENUE ROAD ~ N4*RANCHCITY*TX*30603~SE*30*00023~

EDI file

Existing system

Ship To Table

Message Table

EDI MAPPING

Database schema


70/130

70

07/23/200401010023


ST*850*00023~BEG*00*SA*0101~DTM*002*20040723~

N1*BT*COMPANY ABC~ N3*123 DRIVE STREET~

N4*STARCITY*CA*76503~ N1*ST*INC XYZ~ N3*987 AVENUE ROAD~ N4*RANCHCITY*TX*30603~PO1*1*16*EA*12.00~PO1*2*13*EA*30.00~

SE*30*00023~

EDI file

Database schema

Ship To Table

Message Table

Bill To Table

76503CAStarCity123 DriveStreet

Company ABC0101

ZipStateCityAddressCompanyPO No

30603TXRanchCity987Avenue Rd

Inc XYZ0101


Items

12.00EA160101

30.00EA130101

PriceUnitQtyPO No

D S


71/130

71

07/23/200401010023


ST*850*00023~BEG*00*SA*0101~DTM*002*20040723~



SE*30*00023~

Data Exchange

Data Storage

Ship To Table

Message Table

Bill To Table


Company ABC0101



Inc XYZ0101


Items

12.00EA160101

30.00EA130101

PriceUnitQtyPO No

Database schema


72/130

72

07/23/200401010023


ST*850*00023~BEG*00*SA*0101~DTM*002*20040723~



SE*30*00023~

EDI file

Database schema

Ship To Table

Message Table

Bill To Table


Company ABC0101



Inc XYZ0101


Items

12.00EA160101

30.00EA130101

PriceUnitQtyPO No

Normalized Database


73/130

73

07/23/200401010023


ST*850*00023~BEG*00*SA*0101~DTM*002*20040723~



SE*30*00023~

Normalized File

Normalized Database

Ship To Table

Message Table

Bill To Table


Company ABC0101



Inc XYZ0101


Items

12.00EA160101

30.00EA130101

PriceUnitQtyPO No

Database schemaEDI file


74/130

74

07/23/200401010023


Database schema

Ship To Table

Message Table

Bill To Table


Company ABC0101



Inc XYZ0101


Items

12.00EA160101

30.00EA130101

PriceUnitQtyPO No

Database schemaEDI file


75/130

75

07/23/200401010023


Ship To Table

Message Table

Bill To Table


Company ABC0101



Inc XYZ0101


Items

12.00EA160101

30.00EA130101

PriceUnitQtyPO NoQualifiers andCodes omitted

EDI file Database schema


76/130

76

07/23/200401010023


Ship To Table

Message Table

Bill To Table


Company ABC0101



Inc XYZ0101


Items

12.00EA160101

30.00EA130101

PriceUnitQtyPO No



77/130

77

07/23/200401010023


Ship To Table

Message Table

Bill To Table


Company ABC0101



Inc XYZ0101


Items

12.00EA160101

30.00EA130101

PriceUnitQtyPO No



78/130

78

07/23/200401010023


Ship To Table

Message Table

Bill To Table


Company ABC0101



Inc XYZ0101


Items

12.00EA160101

30.00EA130101

PriceUnitQtyPO No



79/130

79

07/23/200401010023


Ship To Table

Message Table

Bill To Table


Company ABC0101



Inc XYZ0101


Items

12.00EA160101

30.00EA130101

PriceUnitQtyPO No



80/130

80

07/23/200401010023


Ship To Table

Message Table

Bill To Table


Company ABC0101



Inc XYZ0101


Items

12.00EA160101

30.00EA130101

PriceUnitQtyPO No



81/130

81

07/23/200401010023


Ship To Table

Message Table

Bill To Table


Company ABC0101



Inc XYZ0101


Items

12.00EA160101

30.00EA130101

PriceUnitQtyPO No

Programming Outbound Mapping


82/130

82

g g pp g

Set oSegment = oTransactionset.CreateDataSegment("N1\N1")

oSegment.DataElementValue(1) = "ST"oSegment.DataElementValue(2) = sShipToCompany

'Creating the N1 data segment in the N1 loop (group)



83/130

83




g g pp g



84/130

84




g g pp g



85/130

85

Set oSegment = oTransactionset. CreateDataSegment ("N1\N1")



g g pp g

N1


86/130



87/130

87




g g pp g

N1*ST*INC XYZ~



88/130

88




N1*ST*INC XYZ~

Inbound Mapping


89/130

89

Do while not oSegment is Nothing

oSegment = oSegment.NextLoop

Loop until no

more segments

Inbound Mapping


90/130

90

Do while not oSegment is Nothing

oSegment = oSegment.NextLoop

Get next segment

Inbound Mapping


91/130

91

Do while not oSegment is NothingIf oSegment.Area = 1 then

End If oSegment = oSegment.Next

Loop

Inbound Mapping


92/130

92


If oSegment.LoopSection = N1 then

End If End If oSegment = oSegment.Next

Loop

Inbound Mapping


93/130

93


If oSegment.LoopSection = N1 thenIf oSegment.ID = N1 then

End If End If

End If oSegment = oSegment.Next

Loop

Inbound Mapping


94/130

94



If oSegment.DataElementValue(1) = ST then

End If End If


Loop

Inbound Mapping


95/130

95



If oSegment.DataElementValue(1) = ST then

sShipToCompany = oSegment.DataElementValue(2)End If End If


Loop


96/130


97/130

97

ANEDI FILE

IS ACOMPUTER FILE


98/130

98

The traditional method of sending anEDI file is over a VAN

or Value Added Network

VAN

WORKSTATION WORKSTATION


99/130

99

TraditionalValue Added Network

upload& download

EDI files


100/130

100

EDIFile

s Data

Building 1

Building 2

ClearingHouse

Trading Partner ASends and receives

EDI files

Trading Partner BReceives & sendsdata in proprietary

format

ProcessesEDI files


101/130

101

EDIFile

s Data

Building 1

Building 2

ClearingHouse


EDI files


format

ProcessesEDI files


102/130

102

EDIFile

s Data

Building 1

Building 2

ClearingHouse


EDI files


format

ProcessesEDI files


103/130

103

EDIFile

s Data

Building 1

Building 2

ClearingHouse


EDI files


format

ProcessesEDI files


104/130

104

INTERNET

FTP,HTTP,SMTP

SERVER

FTP,HTTP,SMTP

SERVER

VAN

FTP


105/130

105

FTP Server FTP Server

..\INBOUND\

..\OUTBOUND\

FOLDERS

..\INBOUND\..\OUTBOUND\

FOLDERS

EDI filesuploaded or downloaded

to folders

foldersfolders


106/130

HTTP Server - Destination Application


107/130

107

EDI File

EDIAcknowledgment

ASP Program

Framework EDIcomponent

Validate EDI file andcreate acknowledgment



108/130

108

EDI File

EDIAcknowledgment



ASP Program



109/130

109

EDI File

EDIAcknowledgment



ASP Program

AS2 Protocol


110/130

110

HTTP or WebServer

HTTP or WebServer

EDI filesuploaded to a

AS2Application

HTTP Server


111/130

111

MDN

AS2 Application


Process EDI file

AS2 Message


112/130

112

EDI Myths& Facts


113/130

113

Myth

An EDI File is a text file.


114/130

114

Myth

FACT

An EDI File is a text file.

An EDI file is a binary file.


115/130

115


116/130

116

Myth

An EDI File is a flat file.


117/130


118/130

118


119/130

119

Myth

EDI is difficult.


120/130

120

Myth

FACT

EDI is difficult.

EDI is only difficult withoutthe correct tools.

ISA*00* *00* *ZZ*SENDERISA *14*0073268795005 *960807*1548*U*00401*000000020*0*T*>~GS*PO*SENDERGS*007326879*19960807*1548*000001*X*004010~ST*850*000000001

EDI file viewed with a text editor


121/130

121

~BEG*00*SA*A99999-01**19971207~REF*VR*54321~ITD*01*3*1**15**16~DTM*002*19971219~N1*BT*BUYSNACKS INC.*9*1223334444~N3*P.O. BOX 0000~N4*TEMPLE*TX*76503~N1*ST*BUYSNACKS PORT*9*1223334445~N3*1000 N. SAMPLE HIGHWAY~N4*ATHENS*GA*30603~PO1**16*CA*12.34**CB*000111111*UA*002840022222~PID*F****CRUNCHY CHIPS LSS~PO4*48*7.89*LB~PO1**13*CA*12.34**CB*000555555*UA*002840033333~PID*F****NACHO CHIPS LSS~PO4*48*8.9*LB~PO1**32*CA*12.34**CB*000666666*UA*002840044444~PID*F****POTATO CHIPS~PO4*72*6.78*LB~PO1**51*CA*12.34**CB*000874917*UA*002840055555~PID*F****CORN CHIPS~PO4*48*8.9*LB~PO1**9*CA*12.34**CB*000874958*UA*002840066666~PID*F****BBQ CHIPS~PO4*48*4.5*LB~PO1**85*CA*12.34**CB*000874990*UA*002840077777~PID*F****GREAT BIG CHIPS LSS~PO4*48*4.56*LB~PO1**1*CA*12.34**CB*000875088*UA*002840088888~PID*F****MINI CHIPS LSS~PO4*48*4.56*LB~CTT*7~SE*34*000000001~GE*1*000001~IEA*1*000000020~

.SETS850=^[ST,M][BEG,M]+20[CUR]+10[REF,,>1][PER,,3][TAX,,>1][FOB,,>1][CTP,,>1]+5[PAM,,10]+15[CSH,,5]+5[TC2,,>1]{:25[SAC][CUR]}[ITD,,>1]+10[DIS,,20]+5[INC][DTM,,10]+10[LDT,,12]+20[LIN,,5]+5[SI,,>1][PID,,200]+10[MEA,,40][PWK,,25][PKG,,200][TD1,,2][TD5,,12][TD3,,12][TD4,,5][MAN,,10]+6[PCT,,>1]+4[CTB,,5]+5[TXI,,>1]{:>1+2[AMT][REF,,>1]+1[DTM]+2[PCT,,>1]{:>1+1[FA1][FA2,M,>1]}}{:1000[N9]+2[DTM,,>1]+3[MSG,,1000]}{:200+10[N1][N2,,2][N3,,2][N4,,>1]+5[NX2,,>1][REF,,12]+10[PER,,>1]+5[SI,,>1][FOB]+10[TD1,,2][TD5,,12][TD3,,12][TD4,,5][PKG,,200]}{:>1[LM][LQ,M,>1]}{:>1[SPI][REF,,5][DTM,,5][MSG,,50]{:20[N1][N2,,2][N3,,2][N4][REF,,20][G61][MSG,,50]}{:>1[CB1][REF,,20][DTM,,5][LDT][MSG,,50]}}{:>1[ADV]

SEF file viewed with a text editor


122/130

122

Myth

EDI implementation is expensive.


123/130


124/130

124

Myth

EDI is rigid and inflexible.


125/130

125

Myth

FACT

EDI is rigid and inflexible.

EDI itself is flexible.Its a standard that allows your

own requirements.


126/130

126

EDI Applicationshave been

rigid and inflexible.


127/130

127


128/130

128

THE END

Contact Info:


129/130

129

Copyright 2007 EDIdEv LLC, Burbank, California. All rights reserved.

EDIdEv LLC239 W. Olive Ave.Burbank, CA 91502

Tel: (818) 569-4542

Fax: (818) 846-8937

Email: [email protected]
mailto:[email protected]://www.edidev.com/http://www.edidev.com/mailto:[email protected]


130/130

training edi basics ii

Documents