Академический Документы
Профессиональный Документы
Культура Документы
This slide show automatically advances, but you can still control the slides with the following keys: PgDn : advances to the next slide PgUp : 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
- EDI Validation - EDI Acknowledgment - EDI Mapping - Transmitting EDI files - EDI Myths
- EDI Validation - EDI Acknowledgment - EDI Mapping - Transmitting EDI files - EDI Myths
- EDI Validation - EDI Acknowledgment - EDI Mapping - Transmitting EDI files - EDI Myths
- EDI Validation - EDI Acknowledgment - EDI Mapping - Transmitting EDI files - EDI Myths
EDI VALIDATION
EDI File Companion Guide
EDI VALIDATION
EDI File Companion Guide Overview
EDI File
Companion Guide
EDI File
Companion Guide
Segment ID is BEG
10
EDI File
Companion Guide
11
EDI File
Companion Guide
12
EDI File
Companion Guide
Element is type ID
13
EDI File
Companion Guide
14
EDI File
Companion Guide
15
EDI File
Companion Guide
16
Position Numbers Requirements User Requirements Minimum and Maximum Length Maximum Usage Loop Repeats Syntax Rules Code List External Code List Value List Value Reference Semantic References Object Variables Triggers/Instances Industry/Trading Partner Specific
17
User readable
Machine readable
18
User readable
Machine readable
19
User readable
Machine readable
20
21
22
23
24
25
26
27
oEdiDoc.LoadSchema "850_4010.SEF, 0
29
30
31
INBOUND EDI
NO REJECT EDI
YES
ACCEPT EDI
33
INBOUND EDI
NO REJECT EDI
ACCEPT EDI
35
36
37
38
39
40
TA1*000000085*030798*1738*R*021
41
TA1*000000085*030798*1738*R*021
42
Interchange Date
TA1*000000085*030798*1738*R*021
Time
43
Acknowledgment Code
TA1*000000085*030798*1738*R*021
R = Rejected A = Accepted
44
Note Code
TA1*000000085*030798*1738*R*021
021 = Invalid number of included Groups value
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
oAck.Save Ack_850.X12
60
61
62
63
64
oAck.Save Ack_850.X12
65
EDI MAPPING
Existing system
EDI file
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~
Message Table
Message No 0023 PO No. 0101 Delivery Date 07/23/2004
0101
67
EDI MAPPING
Existing system
EDI file
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~
Message Table
Message No 0023 PO No. 0101 Delivery Date 07/23/2004
0101
68
EDI MAPPING
Existing system
EDI file
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~
Message Table
Message No 0023 PO No. 0101 Delivery Date 07/23/2004
0101
69
Database schema
Message Table Message No 0023
EDI file
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~
PO No. 0101
City StarCity
State CA
Zip 76503
City RanchCity
State TX
Zip 30603
Qty 16 13
Unit EA EA
70
Data Storage
Data Exchange
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~
Message Table Message No 0023 PO No. 0101 Delivery Date 07/23/2004
City StarCity
State CA
Zip 76503
City RanchCity
State TX
Zip 30603
Qty 16 13
Unit EA EA
71
Database schema
Message Table Message No 0023
EDI file
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~
PO No. 0101
City StarCity
State CA
Zip 76503
City RanchCity
State TX
Zip 30603
Qty 16 13
Unit EA EA
72
Normalized Database
Message Table Message No 0023
Normalized File
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~
PO No. 0101
City StarCity
State CA
Zip 76503
City RanchCity
State TX
Zip 30603
Qty 16 13
Unit EA EA
73
EDI file
Message Table Message No 0023
Database schema
PO No. 0101
City StarCity
State CA
Zip 76503
City RanchCity
State TX
Zip 30603
Qty 16 13
Unit EA EA
74
EDI file
Message Table Message No 0023
Database schema
PO No. 0101
City StarCity
State CA
Zip 76503
City RanchCity
State TX
Zip 30603
Qty 16 13
Unit EA EA
75
EDI file
Message Table Message No 0023
Database schema
PO No. 0101
City StarCity
State CA
Zip 76503
City RanchCity
State TX
Zip 30603
Qty 16 13
Unit EA EA
76
EDI file
Message Table Message No 0023
Database schema
PO No. 0101
City StarCity
State CA
Zip 76503
City RanchCity
State TX
Zip 30603
Qty 16 13
Unit EA EA
77
EDI file
Message Table Message No 0023
Database schema
PO No. 0101
City StarCity
State CA
Zip 76503
City RanchCity
State TX
Zip 30603
Qty 16 13
Unit EA EA
78
EDI file
Message Table Message No 0023
Database schema
PO No. 0101
City StarCity
State CA
Zip 76503
City RanchCity
State TX
Zip 30603
Qty 16 13
Unit EA EA
79
EDI file
Message Table Message No 0023
Database schema
PO No. 0101
City StarCity
State CA
Zip 76503
City RanchCity
State TX
Zip 30603
Qty 16 13
Unit EA EA
80
EDI file
Message Table Message No 0023
Database schema
PO No. 0101
City StarCity
State CA
Zip 76503
City RanchCity
State TX
Zip 30603
Qty 16 13
Unit EA EA
81
82
83
84
N1
85
N1*ST
86
N1*ST*INC XYZ~
87
N1*ST*INC XYZ~
88
Inbound Mapping
Do while not oSegment is Nothing Loop until no more segments
Inbound Mapping
Do while not oSegment is Nothing
90
Inbound Mapping
Do while not oSegment is Nothing If oSegment.Area = 1 then
Inbound Mapping
Do while not oSegment is Nothing If oSegment.Area = 1 then If oSegment.LoopSection = N1 then
Inbound Mapping
Do while not oSegment is Nothing If oSegment.Area = 1 then If oSegment.LoopSection = N1 then If oSegment.ID = N1 then
Inbound Mapping
Do while not oSegment is Nothing If oSegment.Area = 1 then If oSegment.LoopSection = N1 then If oSegment.ID = N1 then If oSegment.DataElementValue(1) = ST then
Inbound Mapping
Do while not oSegment is Nothing If oSegment.Area = 1 then If oSegment.LoopSection = N1 then If oSegment.ID = N1 then If oSegment.DataElementValue(1) = ST then sShipToCompany = oSegment.DataElementValue(2) End If End If End If End If oSegment = oSegment.Next Loop
95
96
97
The traditional method of sending an EDI file is over a VAN or Value Added Network
VAN
WORKSTATION
WORKSTATION
98
Clearing House
EDI File s Data
Clearing House
EDI File s Data
Clearing House
EDI File s Data
Clearing House
EDI File s Data
VAN
INTERNET
FTP, HTTP, SMTP SERVER FTP, HTTP, SMTP SERVER
104
FTP
folders
folders
FTP Server
FOLDERS
FTP Server
FOLDERS
..\INBOUND\ ..\OUTBOUND\
..\INBOUND\ ..\OUTBOUND\
105
HTTP
EDI File
Framework EDI component
EDI Acknowledgment
107
EDI File
Framework EDI component
EDI Acknowledgment
108
EDI File
Framework EDI component
EDI Acknowledgment
109
AS2 Protocol
110
111
112
Myth
An EDI File is a text file.
113
Myth
An EDI File is a text file.
FACT
An EDI file is a binary file.
114
115
Myth
An EDI File is a flat file.
116
Myth
An EDI File is a flat file.
FACT
An EDI file is a normalized file.
117
118
Myth
EDI is difficult.
119
Myth
EDI is difficult.
FACT
EDI is only difficult without the correct tools.
120
121
Myth
EDI implementation is expensive.
122
Myth
EDI implementation is expensive.
FACT
EDI implementation can be expensive if you are unaware of your options.
123
Myth
EDI is rigid and inflexible.
124
Myth
EDI is rigid and inflexible.
FACT
EDI itself is flexible. Its a standard that allows your own requirements.
125
126
127
THE END
128
Contact Info:
EDIdEv LLC 239 W. Olive Ave. Burbank, CA 91502 Tel: (818) 569-4542 Fax: (818) 846-8937
Email: support@edidev.com www.edidev.com
130