Download as pdf or txt
Download as pdf or txt
You are on page 1of 34

Introduction to ANSI

X12 EDI
Standards
COURSE OBJECTIVES

Introduce the participants to X12


Standards

Introduce the participants to the


concepts of mapping a paper
document to an EDI transaction.

© 2002 Computing Technology Industry Association, All rights reserved 2


COURSE OUTLINE
Electronic Commerce vs
Traditional Commerce
What is EDI ?
Costs and Benefits
EDI Standards
Implementation Issues
X12 Standards and mapping

© 2002 Computing Technology Industry Association, All rights reserved 3


EDI STANDARDS

Standards define the vocabulary, the


syntax rules as well as the structure of
electronic documents.
Standards include an extensive list of
codes.
Standards are developed in collaboration
with interested parties and approved by
recognized organizations.
Standards are periodically updated.

© 2002 Computing Technology Industry Association, All rights reserved 4


EDI STANDARDS
Standards Industrial The main organizations Countries
standards involved in standards
development
North American
Multiple • Data Interchange Standards Association United States,
ANSI X12 Inc. (DISA) Canada
• American National Standards Institute (ANSI)

Transportation These three standards are still in use. They United States,
TDCC Grocery are now or will be integrated into the Canada
UCS Warehousing ANSIX12 standard.
WINS

European
Multiple • Article Number Association (ANA) U.K.
TRADACOM
Automobile • Organisation de Données Échangées par About 10
ODETTE Télé Transmission en Europe (ODETTE) European
countries
International
Multiple • United Nations Economic Commission for
EDIFACT Europe (UN/ECE), Working Party on the Many countries
Facilitation of International Trade (UN WP4)
• International Standards Organization (ISO)

© 2002 Computing Technology Industry Association, All rights reserved 5


ORGANIZATIONS INVOLVED IN THE DEVELOPMENT AND
DISTRIBUTION OF ANSI X12 STANDARDS
Belong to Data
Users
Interchange
Standards
Users Involved in the Association
groups development of Secretariat for the
development of

Involved in the ANSI X -12


development of
STANDARDS Data
Editor of
Interchange
Distributor
Standards
Association
Data Interchange
Standards
Association

© 2002 Computing Technology Industry Association, All rights reserved 6


ELECTRONICS INDUSTRY
ORGANIZATIONS
? Electronics Industry Data Exchange Association (EIDX)
» Industry guidelines and recommendations on the use of the standard
?Computing Technology Industry Association (CompTIA)
»Industry guidelines and recommendations on the use of the standards

?EDIFICE (EDI For companies Interested in Computing and Electronics)


»European counterpart to EIDX
?EDIMAN (EDI for MANufacturing)
»Singapore counterpart to EIDX
?EIAJ (Electronics Industry Association Japan)
»Japanese counterpart to EIA and EIDX
© 2002 Computing Technology Industry Association, All rights reserved 7
IMPLEMENTATION GUIDELINES
Implementation guidelines contain information which
ensures a uniform standard interpretation for any given
industry or organization. These guidelines specify the use of
transaction sets, segments and codes.

Industry Sector
Trading Partner
EDI Implementation
Guidelines
Standards Guideline

© 2002 Computing Technology Industry Association, All rights reserved 8


EIDX GUIDELINES
? NARROWS DOWN THE GENERAL X12 TRANSACTION FOR
USE WITHIN THE ELECTRONICS INDUSTRY
?SEGMENTS:
Required, Recommended, Not Used, Used
?DATA ELEMENTS:
Required, Recommended, Not Used, Used
?SPECIFIC CODES FOR DATA ELEMENTS
? TRANSACTION EXAMPLES
? RECOMMENDATION SUPPORT DOCUMENTS
? BUSINESS PROCESS MODELS

© 2002 Computing Technology Industry Association, All rights reserved 9


STANDARDS TERMINOLOGY
Business Documents X12 Transaction Sets EDIFACT Messages

Price/Sales Catalog 832 PRICAT


Purchase order 850 ORDERS
PO Change 860 ORDCHG
PO Acknowledgment 855/865 ORDRSP
Invoice 810 INVOIC
Payment Order 820 PAYORD
Request for Quotation 840 REQOTE
Forecast 830 DELFOR

© 2002 Computing Technology Industry Association, All rights reserved 10


HOW EDI IS INTEGRATED
TO PROCESS FLOW
SYSTEMS ?

© 2002 Computing Technology Industry Association, All rights reserved 11


PURCHASING SYSTEM

Vendor - Manufacturer Re-Seller


(Supplier) (Customer)
850 - Purchase Order

Order 855 - Purchase Order


Acknowledgement
Processing 860 - Purchase Order
Change Purchasing
System
869 - Order Status Inquiry
System
Customers 870 - Order Status Report

Services

© 2002 Computing Technology Industry Association, All rights


Source: Using reserved
EDI in the Retailing Environment EDI World March 1991
1991 12
DISTRIBUTION SYSTEM
Vendor - Manufacturer Re-Seller
(Supplier) (Customer)

Distribution Receiving
856 - Advance Ship Notice
System

© 2002 Computing Technology Industry Association, All rightsSource:


reserved 131991
Using EDI in the Retailing Environment EDI World March 1 991
PAYMENT SYSTEM
Vendor - Manufacturer Re-Seller
(Supplier) (Customer)
Invoice 810 - Invoices

Processing Accounts
Payable
Receivables

820 - Payment Advice 820 - Payment Order

Financial Institution
© 2002 Computing Technology Industry Association,Source:
All rights
Using EDIreserved
in the Retailing Environment EDI World March 1991
1991 14
PROCESS SUPPORTING SYSTEMS
Vendor - Manufacturer Re-Seller
Client 864 Text List of
Message
File Codes
832 Price/Sales
Available Catalog Product Data
Products 867 Product Base
Transfer Report
Sales Inventory
846 Inventory
Forecasting Inquiry/Adv
and Sales
System System
ice
846 Inventory
Available Inquiry/Advi Client
Inventory ce Services
(response)
Source: Using EDI in the Retailing Environment EDI World March 1991
1991

© 2002 Computing Technology Industry Association, All rights reserved 15


COMPLETE PROCUREMENT PROCESS
Vendor-Manufacturer Re-Seller
Client 864 Text Message List
Client List of
of Codes
Codes
File
File
Available 832 Sales Catalog
Available Products
Products Product
Product Data
Data
Base
Base
867 Product Transfer report
Sales
Sales Forecasting
Forecasting Inventory
Inventory and
and Sales
Sales
846 Inventory report
System
System System
System
Available
Available 846 Inventory report Client
Client
Inventory
Inventory services
services
850 Purchase Order
Order
Order Processing
Processing 855 Acknowledgement
System
System 860 Purchase Order Change
Purchasing
Purchasing System
System
869 Order Status Inquiry
Client
Client
Services
Services 870 Order Status Report

Distribution
Distribution 856 Advance Ship Notice
Receiving
Receiving
System
System

Invoice
Invoice Processing
Processing 810 Invoice
820 Payment Order Payables
Payables
Receivables
Receivables
© 2002 Computing Technology Industry Association, All Source:
rights reserved
Using EDI in the Retailing Environment EDI World March 1991
1991 16
ANSI X12 STANDARDS

© 2002 Computing Technology Industry Association, All rights reserved 17


X12 STANDARDS
Standards releases

? A release is published each year in December.


The 4030 release was published in December
1999.
? Twice a year (in February and in June) a sub-
release is published. In 1999, sub-releases
4031 and 4032 will be/were be published.
? The use of one or more releases will depend
on your business partners choices.

© 2002 Computing Technology Industry Association, All rights reserved 18


X12 STRUCTURE ISA*00*0000000000*01*PASSWORD *12*4086554000
GS*PO*4086554000*INST*970227*0943*1*X*003020!
ST*850*0001!
*... !

BEG* ..................
N1* ....................
SHH* ..................
P01* ....................
SCH* ..................
APPLICATION INTERFACE
SCH* ..................
APPLICATION
PO1* ..................
SCH* ..................
PO1* ..................
PO1* ..................
CTT*4* ...............
SE*13*0001!
ST*850*0002!
BEG* .................
.....
.....
.....
SE*20*0002!
ST*850*0003!
BEG* .................
INTERFACE .....
FILE .....
.....
.....
SE*16*0003
GE*3*1!
GS*PC*4086554000*INST*970227*0958*2*X*003020!

TRANSLATION ST* .....................


.....
.....
.....

SOFTWARE EDI
FILE
SE* .....................
ST* .....................
.....
.....
.....
SE* .......................
GE*2*2!
IEA*2*000000032!

© 2002 Computing Technology Industry Association, All rights reserved 19


PAPER VS EDI DOCUMENT
Business document or Electronic Document
PURCHASE ORDER form
Header BEG * 00 * SA * 00239 ** 970517 ...
Ordered : May 17, 1997

Ship to : Our Company


300 Our Street
Our City, Our State 55555 N1* ST * Our Company
N3 * 300 Our Street
N4 * Our City * Our State
Bill to : Our Company
attn Mr. Smith N1 * BT* Our Company
250 Our Street
N3 * 250 Our Street
Our City, Our State 55555
N4 * Our City * Our State
PER * attn.: Mr Smith

Qty Part No Description Price PO1 * 01* 200* EA* 59.00* CA* BP*
200 ABC321 Blue Gadget $59.00 Detail ABC321

100 BZX321 Yellow Gadget $61.00 PO1 * 02* 100* EA* 61.00* CA* BP*
BZX321

Total : $179.00 Summary CTT * 2* 17900

© 2002 Computing Technology Industry Association, All rights reserved 20


850 Purchase Order
Functional Group = PO
This standard provides the format and establishes the data contents
conte nts of a purchase order transaction set
Table 1
POS. REQ.
LOOP NOTES &
NO. SEG. ID NAME DES. MAX USE
REPEAT DM# COMMENTS

010 ST Transaction Set Header M 1


020 BEG Begin. Seg
Seg.. for Purchase M 1
Order
030 NTE Note/Special Instruction F 100
040 CUR Currency O 1
...
310 N1 Name O 1
N1/200
320 N2 Additional Name Information O 2
330 N3 Address Information O 2
...
420 PKG Marking, Packaging, Loading O 200

Table 2

010 PO1 PO Baseline Item


Data M 1 PO1/100000
020 CUR Currency O 1
...
050 PID Product/Item
Description O 1 PID/1000....
060 MEA Measurements O 10
070 PWK Paperwork O 25
...
460 PKG Marking, Packaging, Loading O 200

© 2002 Computing Technology Industry Association, All rights reserved 21


DATA SEGMENTS

BEG Beginning Segment for Purchase Order 1. Segment name


BEG01 353 BEG02 92 BEG03 324 BEG04 328
2. Segment identifier
1
Trans. set P.O. Type P.O. Release 3. Data elements
BEG * purpose Cd
* Code
* Number
* Number
* 4. Data element reference
designator
M ID 02/02 M ID 02/02 M AN 01/22 O AN 01/30 10
5. Element Name
2
BEG05 323 BEG06 367 BEG07 587 BEG08 1019
3
P.O. Contract Ack.Type Invoice 6. Data element number
4 N/L
5
Date
* Number
* * Type Code 7. Presence indicator
M DT 06/06 O AN 01/30 O ID 02/02 O ID 03/03 11 8. Data element type
6 9 9. Number of characters
Notes & Comments ** 8 permitted
SEQ TYPE TEXT 7 (minimum/maximum)
01 COM Commentary 10. Data element separator
03 SEM Semantic note (Ex.: BEG03 is a Purchase Order number usually
assigned by the software application) 11. Data segment terminator
06 SYN Syntax Note (Ex:: If the BEG06 element is present,
then the BEG07 is required)

** Notes and comments are fictional for the BEG segment

© 2002 Computing Technology Industry Association, All rights reserved 22


DATA ELEMENTS

1. Data dictionary
reference number
2. Data element name
92 Purchase Order Type Code TYPE= ID MIN= 2 MAX=2 3. Element attribute
Code specifying the type of Purchase Order
specification
1 2 4 3
SEGMENT USED IN: 4. Data element
5 BCA BCH BEG BQT G50 description
6
7 5. Possible values of
CODE DEFINITION & EXPLANATION element code
NOTE 6. Possible code
AB Assortment Against Blanket definition of data
AC AOG (Aircraft on Ground) Critical elements
AO AOG (Aircraft on Ground) Service
BD Bidding 7. Data element
... ... reference designator
... ...
ZZ Mutually Defined

© 2002 Computing Technology Industry Association, All rights reserved 23


DATA ELEMENT TYPES
? AN = Alpha Numeric
? ID = Identification Code
? DT = Date (YYMMDD)
? TM = Time (HHMM)
? R = Real Number - Decimal is explicit
example : 1.23 = 1.23
? N0 = Numeric / # Decimal places - Decimal is implied
examples : N1 123 = 12.3
N2 123 = 1.23
N3 123 = .123
© 2002 Computing Technology Industry Association, All rights reserved 24
WHAT MAKES EDI POSSIBLE
CODES
CODES
AND MORE CODES

CODE QUALIFIERS
CODE QUALIFIERS
AND MORE CODE QUALIFIERS
If you don’t codify, you don’t EDI!

© 2002 Computing Technology Industry Association, All rights reserved 25


CODE: PURCHASE ORDER TYPE CODE
Sometimes a code qualifies an entire transaction.

Data Element (DE) 92


Code specifying the type of purchase order.
45 codes altogether, including:
BK Blanket Order
CF Confirmation
CP Change to Purchase Order
RE Reorder
SA Stand Alone Order
© 2002 Computing Technology Industry Association, All rights reserved 26
CODE: DATE/TIME QUALIFIER
Codes usually qualify a data value.
Data Element (DE) 374
Code specifying type of date or time, or both date
and time.
230 codes altogether, including:
001 Cancel After
002 Delivery Requested
003 Invoice
004 Purchase Order
005 Sailing
007 Effective
219 Plugged and Abandoned
© 2002 Computing Technology Industry Association, All rights reserved 27
DATA ELEMENT QUALIFIERS
N103 66 N104 67 66 List of codes
ID CODE 1 = DUN & BRADSTREET
QUALIFIER ID CODE 9 = Duns plus 4 digits
91 = Assigned by Buyer
X ID 1/2 X AN 2/20 92 = Assigned by Seller

DTM01 374 DTM02 373 374 List of codes


DATE/TIME 002 = Delivery Requested
QUALIFIER DATE 010 = Requested Ship
017 = Estimated Delivery
M ID 3/3 X DT 6/6 069 = Promised for Delivery

PO106 235 PO107 234 235 List of codes


PROD/SERV PROD/SERV BP = Buyer part
ID QUALIFIER ID EC = Engineering Change
DR = Drawing
X ID 2/2 X AN 1/40 VP = Vendor Part

© 2002 Computing Technology Industry Association, All rights reserved 28


PAPER & X12 TERM COMPARISON
BUSINESS EQUAL TRANSACTIONS
DOCUMENTS
INVOICES 810 INVOICE
PURCHASE ORDER 850 PURCHASE ORDER
GROUPS OF DATA EQUAL SEGMENTS
BASIC PO DATA BEG SEGMENTS
PO LINE ITEM PO1 SEGMENT
SCHEDULES SCH SEGMENT
INDIVIDUAL DATA EQUAL DATA ELEMENTS
PO NUMBER BEG03 PO NUMBER
PO DATE BEG06 PO DATE
PART NUMBER PO107 PROD/SERVC ID CD
ITEM QTY PO102 QTY ORDERED
SCHEDULE QTY SCH01 (SCHEDULE) QTY
SCHEUDLE DATE SCH07 (SCHEDULE) DATE

© 2002 Computing Technology Industry Association, All rights reserved 29


CONTROL SEGMENTS
X12 Standards (3020)
ISA Interchange Control Header
ISA01 I01 ISA02 I02 ISA03 I03 ISA04 I04 ISA05 I05 ISA06 I06 ISA07 I05 ISA08 I07
Authorization Auth. Security Security Interchange Interchange Interchange Interchange
ISA * Information
* Information
*
Information
* Information
* ID Qualifier
* Sender ID
* ID Qualifier Receiver ID
Qualifier
M ID 02/02 M AN 10/10
Qualifier
M ID 02/02 M AN 10/10
* *
M ID 02/02 M AN 15/15 M ID 02/02 M AN 15/15

ISA09 I08 ISA10 I09 ISA11 I10 ISA12 I11 ISA13 I12 ISA14 I13 ISA15 I14 ISA16 I15
Interchange Interchange Interchange
Interchange Interchange Acknowled. Test Subelement
Control Control Control N/L
Date
* Time
* Standards ID * Version # * Number * Requested
* Indicator
* Separator

M DT 06/06 M TM 04/04 M ID 01/01 M ID 05/05 M N0 09/09 M ID 01/01 M ID 01/01 M AN 01/01

IEA Interchange Control Trailer


IEA01 I16 IEA02 I12
Interchange
Number of
N/L
IEA * FGs
*
Control
Number
M N0 01/05 M N0 09/09

Number of included Interchange Control


Functional Groups Number (must be the
same as ISA13)
© 2002 Computing Technology Industry Association, All rights reserved 30
GROUP SEGMENTS
X12 Standards (3060)
GS Functional Group Header
GS01 479 GS02 142 GS03 124 GS04 373 GS05 337 GS06 28
Functional Application Application Group
Date Time
GS * ID Code
* Sender’s Cd
* Recever’s Cd
* * *
Control No. *
M ID 02/02 M AN 02/15 M AN 02/15 MIZ DT 06/06 MIZ TM 04/06 MIZ N0 01/09

GS07 455 GS08 480


Responsible Version/Rel
Agency Ind. N/L
M
Code
ID 01/02
* M
ID Code
AN 01/12

GE Functional Group Trailer


GE01 97 GE02 28
Number of Group
N/L
GE * Included
Sets * Control No.
M N0 01/05 M N0 01/09

Number of Group Control Number (must


Transaction Sets be the same as GS06)
included in this
Functional Group

© 2002 Computing Technology Industry Association, All rights reserved 31


TRANSACTION SET BEGINNING AND
ENDING SEGMENTS
X12 Standards (3060)

ST Transaction Set Header


ST01 143 ST02 329
Transaction
ST * Transaction
Set ID Code
* Set Control
Number
N/L
MIZ ID 03/03 M AN 04/09

Transaction Set Transaction Set


Identifier Code Control Number

SE Transaction Set Trailer


SE01 96 SE02 329
Number of Transaction
SE * Included
Segments * Set Control
Number
N/L
M N0 01/10 M AN 04/09

Number of included Transaction Set Control


Segments in this Number (must be the
Transaction Set (including same as ST02)
Segments “ST” and “SE”)

© 2002 Computing Technology Industry Association, All rights reserved 32


ISA*00*000000000*01*PASSWORD *12*4086554000 *01*205415573 *970525*1032*U*00302*000000032*0*P*<!
GS*PO*4086554000*INST*970525*0943*1*X*003020!
ST*850*0001!
BEG* ..................
N1* ....................
SHH* ..................
P01* ....................
SCH* ..................
SCH* ..................
PO1* ..................
SCH* ..................
PO1* ..................
PO1* ..................
CTT*4* ...............
SE*13*0001!
ST*850*0002!
BEG* .................
.....
.....
.....
.....
SE*16*0002!
GE*2*1!
GS*PC*4086554000*INST*970525*0958*2*X*003020!
ST* .....................
.....
.....
.....

CONTROL SEGMENTS (EXAMPLE)


SE* .....................
ST* .....................
.....
.....
.....
SE* .......................
GE*2*2!
IEA*2*000000032!

© 2002 Computing Technology Industry Association, All rights reserved 33


ISA*00*000000000*01*PASSWORD *12*4086554000 *01*205415573 *970525*1032*U*00302*000000032*0*P*<!
GS*PO*4086554000*INST*970525*0943*1*X*003020!
ST*850*0001!

SE*13*0001!
ST*850*0002!

SE*16*0002!
GE*2*2!
GS*PC*4086554000*INST*970525*0958*2*X*003020!
ST* .....................

SE* .....................

CONTROL SEGMENTS (EXAMPLE)


ST* .....................

SE* .......................
GE*2*2!
IEA*2*000000032!
© 2002 Computing Technology Industry Association, All rights reserved 34

You might also like