INTRODUCTION TO EDIFACT

presented by EIDX

1

CONTENTS
! ! ! ! ! !

Definitions Data Mapping Organizations X12/EDIFACT Differences Basic Components
(Messages, Segments, Composites, Data Elements)

Codes and Qualifiers
2

Electronic Data Interchange

Definitions

The Cornerstone of Electronic Commerce EDI is the Computer to Computer Exchange of Routine Business Documents in a Standard Format.
Payments Purchase Orders Invoices Bills of Lading

Ship Notices

3

Definitions

DATA MAPPING
The logical and physical process of defining the relationship between proprietary application data & counterparts in EDI standard transactions / messages.
It is only one aspect of new transaction implementation.

4

Definitions

LOGICAL MAPPING
The Process of Identifying and Documenting the Relationship between Application Data and its EDI Standard Segment and Data Element Counterpart.
Requires thorough understanding of: 3Internal Application & EDI Standard Format Architecture 3Data or Code Definitions & Purpose 3Identification of All Essential Source/Destination Fields Applicable to the Standard Message 3Data Rules for Inbound vs. Outbound Processing
5

Translator 3Standards Architecture Knowledge 3Code Conversions 6 . Reformats. Requires : 3Interfaces.Definitions PHYSICAL MAPPING Actual Process of Moving Application Data to/from Standards Formats.

Definitions DATA MAPPING For INBOUND documents: Moving Data FROM Standard Segments & Elements TO Internal Proprietary Records & Data Fields For OUTBOUND documents: Moving Data FROM Internal Proprietary Records & Data Fields TO Standard Segments & Elements Data may need cross-referencing 7 .

Organizations STANDARDS ORGANIZATIONS American National Standards Institute (ANSI) ! Approves Standards (1983. Commerce and Trade (UN-EDIFACT) ! Develops International Standards 8 . Does Not Develop Standards ANSI Accredited Standards Committee X12 (ASC X12) ! ! Develops U. 1992). Standards for Trial Use Representation from Many Industries United Nations .EDI For Administration.S. 1986.

Organizations INDUSTRY ORGANIZATIONS EIDX (Electronics Industry Data Exchange Association) 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 9 .

EDIFACT Basics EDIFACT BASICS ! ! ! ! ! Messages Segments & Segment Groups Data Elements Composites Control Characters 10 .

UN/EDIFACT Building Blocks ! ! ! ! ! ! EDIFACT Basics ! ! ! ! UN/EDIFACT Trade Data Interchange Directory (UNTDID) UN Standard Message Types (UNSMs) UN/EDIFACT Message Directory (UNEDMD or EDMD) UN/EDIFACT Segment Directory (UNEDSD or EDSD) UN/EDIFACT Composite Directory (UNEDCD or EDCD) UN/EDIFACT Data Element Directory (UNEDED or EDED) (Subset of ISO 7273) within UN Trade Data Element Directory (UNTDED) UN/EDIFACT Code Lists Directory (UNCL) EDIFACT Syntax Rules (ISO 9735) Syntax Implementation Guidelines Message Design Guidelines 11 .

92. Version New Notation: Status.93A. 92.2.96A. D. etc.1. etc.2.EDIFACT Data Directories EDIFACT Basics Old Notation: Year (YY).93B … D.96B. Status: D = Draft (contains trial messages) S = Standard (contains UNSMs) Version: A = First edition for that year B = Second edition for that year 12 .1. D. 90. Year (YY). New Notation: D. Version Old Notation: 90.

ASC X12/ EDIFACT ORDERS COMPARISON ASC X12 PURCHASE ORDER TRANSACTION ST~850~0001@ BEG~00~SA~P54356+~~960626~~CN2345@ N1~BT~ACME CORP.99:CT::1’ SCC+1+DD’ QTY+133:200’ DTM+2:960715:101’ QTY+133:300’ DTM+2:960820:101’ CNS+S’ CTN+2:1’ CNT+19+1800 UNT+19+0001’ 13 .~92~AC9876@ PO1~01~500~2.99~CT~BP~18200232~EC~C~VP~GF9876@ SCH~200~EA~~~~002~960715@ SCH~300~EA~~~~002~960820~ CTT~1~500@ SE~9~0001@ Differences and Similarities EDIFACT ORDERS MESSAGE UNH+0001+ORDERS:2:921:UN:EIVER1’ BGM+105+P54356+9’ DTM+4+960626:101’ RFF+CT:CN2345’ NAD+BT+AC323:92’ NAD+ST+AC9876:92’ LIN+01++1820-0232:BP’ PIA+1+C:EC+GF9876:VP’ QTY+21:500:PCE’ PRI+1:2.~92~AC323@ N1~ST~ACME CORP.

ENVELOPES ASCX12/EDIFACT X12 ISA GS ST SE GE IEA EDIFACT UNB UNG UNH UNT UNE UNZ 14 .

Differences and Similarities X12/EDIFACT DIFFERENCE Segments ASC X12 SEGMENTS ! UN/EDIFACT SEGMENTS ! Specific Function Generic Function (Data Element Qualifiers define specific meanings) ! Long Segments ! Short Segments 15 .

Differences and Similarities UN/EDIFACT 80+ SEGMENTS 100+ COMPOSITE ELEMENTS 130+ DATA ELEMENTS 1 1 BEGINNING SEG. DATA/TIME DATA ELEMENT 100 + DATA/TIME DATA ELEMENT 16 .X12/EDIFACT DIFFERENCE Number of Components ASC X12 1000+ SEGMENTS FEW COMPOSITE ELEMENTS 1100+ DATA ELEMENTS 60 + BEGINNING SEG.

X12/EDIFACT DIFFERENCE REUSABLE SEGMENTS ! Differences and Similarities X12 SEGMENT BEG = Function + Type + Identification + Date + Time BIA = Function + Type + Identification + Date + Time EDIFACT SEGMENT BGM segment = (Identification + Function + Type + Response) DTM segment (Date/Time) 17 .

SAMPLE BEGINNING SEGMENTS X12 Segment Txn Description Differences and Similarities BIG BEG BAK BSN 810 850 855 856 Invoice Header Data PO Header Data PO Ack Header Data Ship Notice Header Data EDIFACT Segment BGM All Beginning of all Messages 18 .

BCH) l BCH = Function + Type + ID + Ref + Ref + Date + Ref + Ref + Ref + Date + Date EDIFACT SEGMENT (REUSABLE SEGMENTS) l BGM + DTM + DTM + DTM + RFF + RFF + RFF + RFF 19 .Differences and Similarities X12/EDIFACT DIFFERENCE LONG VS SHORT SEGMENTS X12 (A SINGLE SEGMENT .

Differences and Similarities CONTROL CHARACTERS ! ! ! SEGMENT TERMINATORS => Default DATA ELEMENT SEPARATOR => Default DATA ELEMENTS WITHIN A COMPOSITE => Default : RELEASE CHARACTER ? ‘CARGO:AIR’ ‘WHAT?’ Send as Send as ‘CARGO?:AIR’ ‘WHAT??’ ‘ + ! 20 .

Many Same/Similar Segment Names X12 TAX DTM QTY REF SCH CUR EDIFACT TAX DTM QTY RFF SCC CUX Description Tax Date/Time Quantity Reference Schedule Currency X12/EDIFACT Differences and Similarities 21 .

PAPER & MESSAGE TERM COMPARISON EQUAL B U S IN E S S DOCUM ENTS IN V O IC E S PURCH ASE O RDER EQUAL GROUPS OF DATA P O L IN E IT E M SC H ED U LES D A TES SC H ED U LE Q TY EQUAL IN D IV ID U A L D A T A PO NUM BER PO DATE PART NUM BER IT E M Q T Y SCH EDULE Q TY SCH EUDLE DATE M ESSA G E Paper to EDI IN V O IC ORDERS SEG M EN TS L IN S E G M E N T S DTM SEG M ENT Q TY SEG M ENT DATA ELEM ENTS 1 0 0 4 D O C U M E N T (Q u : 1 0 5 ) 2 3 8 0 D A T E ( Q u a l: 4 ) 7 1 4 0 L IN E IT E M 6 0 6 0 Q T Y ( Q u a l: 2 1 S c h d ) 6 0 6 0 Q T Y ( Q u a l: 1 3 3 S c h d ) 2 3 8 0 D A T E ( Q u a l: 2 S c h d ) 22 .

BUSINESS DOCUMENTS to TRANSACTIONS / MESSAGES X12 Txn 810 830 832 850 855/865 860 856 852 813 BAPLIE EDIFACT Msg INVOIC DELFOR PRICAT ORDERS ORDRSP ORDCHG DESADV CUSDEC Transactions & Messages Business Paper Document Invoice Forecast Price Catalog Purchase Order. Blanket Order PO Acknowledgment PO Change Shipment Notice Product Activity Data Customs Declaration Electronic Filing of Tax Return Bayplan/Stowage Plan Occupied and Empty Locations 23 .

No.(Header: Header. 005 010 015 035 Seg. Segment Groups 1-5) Must Use Must Use Must Use Pos. ID UNH BGM DTM FTX Name Message Header Beginning of Message Date/Time/Period Free Text Segment Group 1: RFF-DTM Must Use 040 045 RFF DTM Reference Date/Time/Period Segment Group 2: NAD-LOC-FII-SG3-SG4SG5 Name and Address Segment Group 3: RFF-DTM Must Use 065 RFF Reference Segment Group 4: DOC-DTM Must Use 075 DOC Document/Message Details Segment Group 5: CTA-COM Must Use 085 090 CTA COM Contact Information Communication Contact Req. Use 1 1 35 5 10 Group Repeast Notes ORDERS (Purchase Orders) Message Must Use 050 NAD 24 . Des M M M C C M C C M C M C M C M C 1 5 1 5 1 5 1 10 1 5 20 Max.

ID TAX Name Segment Group 6: TAX-MOA-LOC Duty/Tax/Fee Details Segment Group 7: CUX-PCD-DTM Must Use 110 CUX Currencies Segment Group 9: TDT-SG10 Must Use 145 TDT Details of Transport Segment Group 10: LOC-DTM Must Use 150 155 LOC DTM Place/Location Identification Date/Time/Period Segment Group 11: TOD-LOC Must Use 160 165 TOD LOC Terms of Delivery Place/Location Identification Segment Group 18: ALC-ALI-DTM-SG19SG20-SG21-SG22-SG23 Allowance or Charge Req. Use Group Repeast 5 Notes ORDERS (Purchase Orders) 1 5 Must Use 260 ALC 25 . No. Must Use 095 Seg.Message (Header: Segment Groups 6-18) Pos. Des C M C M C M C M C C M C C M 1 1 2 15 1 5 5 1 10 1 10 Max.

Seg.36) Pos. No. Use Group Repeast 200000 Notes ORDERS (Purchase Orders) Message Must Use 005 010 015 025 LIN PIA IMD QTY M C C C C M C M C C M C M C 1 25 10 10 25 1 10 1 5 10 1 5 1 5 Must Use 135 PAC 26 . ID Name Segment Group 25: LIN-PIA-IMD-MEA-QTYPCD-ALI-DTM-MOA-GIN-GIR-QVA-DOCPAI-FTX-SG26-SG27-SG28-SG29-SG32SG33-SG34-SG38-SG44-SG46-SG47-SG48SG50 Line Item Additional Product Id Item Description Quantity Segment Group 27: PRI-CUX-API-RNG-DTM Must Use 100 PRI Price Details Segment Group 28: RFF-DTM Must Use 125 130 RFF DTM Reference Date/Time/Period Segment Group 29: PAC-MEA-QTY-DTMSG30-SG31 Package Segment Group 36: DOC-DTM Must Use Not Used 235 240 DOC DTM Document/Message Details Date/Time/Period Req.(Detail Section: Segment Group 25 . Des C Max.

Use Group Repeast 15 Notes ORDERS (Purchase Orders) Message Must Use 255 ALC 1 10 27 .(Detail: Segment Groups 38 . No. ID Name Segment Group 38: ALC-ALI-DTM-SG39SG40-SG41-SG42-SG43 Allowance or Charge Segment Group 44: TDT-SG45 Must Use 320 TDT Details of Transport Segment Group 45: LOC-DTM Must Use 325 330 LOC DTM Place/Location Identification Date/Time/Period Segment Group 46: TOD-LOC Must Use 335 340 TOD LOC Terms of Delivery Place/Location Identification Segment Group 48: SCC-FTX-RFF-SG49 Must Use 365 SCC Scheduling Conditions Segment Group 49: QTY-DTM Must Use 380 385 QTY DTM Quantity Date/Time/Period Req.49) Pos. Seg. Des C M C M C M C C M C C M C M C 1 5 1 10 1 2 100 1 5 5 1 10 Max.

Use 1 10 1 Group Repeast Notes Must Use 035 28 . ID UNS CNT UNT Name Section Control Control Total Message Trailer Req. Des M C M Max. 005 015 Seg. No.(Section Control and Summary Section) ORDERS (Purchase Orders) Message Must Use Pos.

! ! ! ! Message Segments that make up a Message The Sequential Order of Segments/SG Maximum Times a Segment/SG may Repeat Whether a Segment/SG is Mandatory or Conditional SG = Segment Group 29 ...UN/EDIFACT MESSAGE DEFINES.

Quantities SUMMARY SECTION (Control Totals) 30 . Contracts. Schedules. Addresses. References DETAIL SECTION (Multiple Occurrences) ! Each Line Item.EDIFACT MESSAGE COMPOSITION ! Transactions & Messages HEADER SECTION (One Occurrence) Codes.

DESIGN RULES MESSAGE SECTIONS HEADER SECTION ! Transactions & Messages SEGMENTS relate to ENTIRE MESSAGE SEGMENTS relate to DETAILS where it is written Data OVERRIDES similar data in the HEADER Section SEGMENTS with TOTALS or CONTROL data 31 DETAIL SECTION ! ! SUMMARY SECTION ! .

Identify. Msg Type Identifier Msg Type Version No. Controling Agent Association Assigned Code 32 . Msg Type Release No. and Specify a Message UNH+1234+ORDERS:1:921:UN:EIVER1’ Combines functions of ASC X12 GS and ST Segments UNH+ 1234+ ORDERS: 1: 921: UN: EIVER1 UNH Segment Msg Reference No.EDIFACT ‘UNH’ Message Header Segment To Head.

EDIFACT SAMPLE ORDERS UNH+0001+ORDERS:2:921:UN:EIVER1’ BGM+105+P54356+9’ DTM+4+960626:101’ RFF+CT:CN2345’ NAD+BT+AC323:92’ NAD+ST+AC9876:92’ LIN+01++1820-0232:BP’ PIA+1+C:EC+GF9876:VP’ QTY+21:200:PCE’ PRI+1:2.99:CT::1’ SCC+1+DD’ QTY+133:200’ DTM+2:960715:101’ CNS+S’ CTN+2:1’ CNT+17+200 UNT+17+0001’ 33 .

PA 17016 IT 1 PART PD34 Schedule 500 500 2 L2678 Schedule 500 500 500 1500 PO 53436 Contract # 95-276 QTY 1000 PRICE 1.RFF (Contract) .QTY (Quantity) .NAD (Name & Address) DETAIL (Items) .LIN (Item Data) .PRI (Price) .142 12/05/95 01/05/96 5.17 12/05/95 12/12/95 12/19/95 HEADER .DTM (Dates) 34 .BGM (PO number) .Segments GROUPS OF DATA to SEGMENTS Acme Corp 5400 Acme Pkwy Acme.QTY (Quantity) DETAIL (Delivery Schedules) .

On-Hand Quantity) LIN Item ID RFF Reference DTM Date/Time QTY Quantity 35 . name) LINE ITEM Line Item Number.Segments EDIFACT COMMONLY USED SEGMENTS Segment Description NAD Name Contents NAME & ADDRESS (Location type. Release Number) DATE/TIME Any type of date (Expiration date. Part Number REFERENCE Any reference (Quote Number. Ship Date) QUANTITY Any type of quantity (Minimum Order.

DESIGN RULES SEGMENT GROUPS Design Rules SEGMENT GROUP (SG) is an ASSEMBLY of ! ! ! Trigger Segments (First Segment in SG) Related Segment(s) and/or Related Segment Group(s) Trigger Segment’s Data must be Used Other Mandatory Segments or Segment Groups must be Used 36 MANDATORY SEGMENT GROUPS ! ! .

DESIGN RULES SEGMENT SEQUENCE SEGMENTS ! Design Rules RELATED DATA ELEMENTS DEFINED TO A RECORD ! ! SPECIFIC PLACE IN MESSAGE SAME SEGMENT MAY BE IN MULTIPLE PLACES 37 .

Currencies. and Rates of Exchange that Pertain to the Whole Commercial Document 38 .Segments Group SEGMENT GROUPS A Set of Segments which are Needed to Satisfy the Defined Purpose. Segment Group 11 in CUSDEC: A Group of Segments Identifying Various Monetary Amounts.

DESIGN RULES MAXIMUM USE OF SEGMENTS SEGMENT consists of: ! ! Design Rules SEGMENT A TAG BGM. CODED ! COMPOSITE DATA ELEMENTS C506 REFERENCE C507 DATE/TIME/PERIOD 39 . DTM. RFF. etc SIMPLE DATA ELEMENTS and/or 3035 PARTY QUALIFIER 3139 CONTACT FUNCTION.

O) and Maximum number of repetitions of a given segment are indicated in the Segment Table 40 .DESIGN RULES MAXIMUM USE OF SEGMENTS ! Design Rules ! SEGMENTS may be REPEATED several times at SPECIFIC locations in a given message The Requirements Designator (M.

CODED ITEM NUMBER IDENTIFICATION Item number Item number type.6 an.3 41 ...2 an.3 an.. CODED C C n.3 an. coded Data Elements Requirements Representation Designator C C C C C C C n.EDIFACT DATA ELEMENTS Date Element Tag (DE Number) 010 020 030 1082 1229 C212 7140 7143 1131 3055 LINE ITEM NUMBER ACTION REQUEST/NOTIFICATION..3 an... coded Code list qualifier Code list responsible agency...3 … 050 060 1222 7083 CONFIGURATION LEVEL CONFIGURATION.35 an.

Data Elements DIRECTORY NOTATION Requirements Designators M = Mandatory C = Conditional (Optional is a Condition) Data Types a = Alpha Character n = Numeric (Integers & Real) an = Alphanumeric Characters id = Identifier (Code) Data Lengths a3 = Fixed Length.6 = Variable Length. 6 digits an4 = Fixed Length.4 = Variable Length. alphabetic 3 characters n6 = Fixed Length... alphanumeric. alphabetic (1 to 3 Characters) n.. numeric.3 = Variable Length. numeric (1 to 6 digits) an. alphanumeric (1 to 4 characters) 42 . 4 characters a.

or Originators Discretion 43 .DATA ELEMENT STATUS MANDATORY ! MUST be Used in a Segment CONDITIONAL ! Usage Depends on Certain Conditions ! Relevant Conditions for Required Conditions of the D/E may be part of the Segment Definition NO CONDITION SPECIFIED ! Use per Trading Partner Agreement.

DATA ELEMENT PRINCIPLES X12 EDIFACT SPECIFIC Data Element GENERIC Data Element EXAMPLES: EXAMPLES DESIGN RULES Design Rules ‘ PO Date’ DE323* ‘Invoice Date’ DE245* * Always Format: YYMMDD Qualifier :Date:Format 4:Date:102 = PO Date # 3:Date:102 = Invoice Date # # 102 Format: CCYYMMDD 44 .

one odd) DATA ELEMENTS BEGINNING WITH ‘C’ Composite Data Elements 45 . one even.DATA ELEMENT TAGS ODD NUMBER DATA ELEMENTS Coded Data Elements from a Directory DESIGN RULES Design Rules EVEN NUMBER DATA ELEMENTS Non-Coded Data Elements User Defined Data (IDs are Received as pairs.

you can’t do EDI! 46 .Codes and Qualifiers WHAT MAKES EDI POSSIBLE CODES CODES AND MORE CODES CODE QUALIFIERS CODE QUALIFIERS AND MORE CODE QUALIFIERS If you don’t codify.

.3 in NAD Data Elements with length greater 3 Have Data Elements names ending in ‘IDENTIFICATION’ ‘Party ID Identification’ an. CODED’ ‘Code List Responsible Agency.. Coded’ an.17 in NAD 47 .Data Elements CODE ELEMENTS Data Elements with length 1-3 (an.3) Have Data Element names ending in ‘..

3 PARTY QUALIFIER 1154 an.Design Rules DATA ELEMENT GENERIC DATA + QUALIFIERS (Order of Qualifier) REFERENCE QUALIFIER REFERENCE NUMBER DE1153 Code List (Sampling) ACP = Hot Roll Number CT = Contract Number IV = Invoice Number UCN = Unique Consignment Number DE3055 Code List (Sampling) BT = Bill To FW = Freight Forwarder SF = Ship From ST = Ship To 1153 an.35 PARTY IDENTIFICATION DETAILS 3035 an..3 C082 48 ...

. Requested 101 = YYMMDD 3 = Invoice Date/Time 102 = CCYYMMDD 10 = Shipment D/T.35 2379 an.Design Rules DATA ELEMENT GENERIC DATA + QUALIFIERS (Order of Qualifier) DATE/TIME/ PERIOD QUALIFIER DATE/TIME/PERIOD DATE/TIME/ PERIOD FORMAT QUALIFIER 2380 an.35 7143 DE7143 Code List (Sampling) BP = Buyer's Part Number EC = Engineering Change Level VP = Vendor's Part Number an.3 DE2005 Code List (Sampling) DE2379 Code List (Sampling) 2 = Delivery Date.3 49 ...3 2005 an. Requested 804 = (Number of) Days 158 = Horizon Start Date ITEM NUMBER ITEM NUMBER TYPE.. CODED 7140 an..

. ! ! ! ! REFERENCE NUMBER NAME DESCRIPTION PREDEFINED STRUCTURE OF DATA ELEMENTS 50 ..DESIGN RULES COMPOSITES (Cnnn) Design Rules COMPOSITE DATA ELEMENT is an ASSEMBLY of CLOSELY RELATED Data COMPOSITE CONSISTS of .

DESIGN RULES COMPOSITES (Cnnn) C507 DATE/TIME/PERIOD 2005 DATE/TIME/PERIOD QUALIFIER 2380 DATE/TIME/PERIOD 2379 DATE/TIME/PERIOD FORMAT QUALIFIER Design Rules M M AN 1/3 C AN 1/35 C AN 1/3 Segment Tag Qualifier Generic Qualifier (DTM) + 79 : 19960626 : 102 | | | | DTM + ship : date/ : format date/time time CCYYMMDD 51 .

END OF PRESENTATION 52 .

Sign up to vote on this title
UsefulNot useful