1. EDI For Administration, Commerce and Transport
EDIFACT
EDI For Administration, Commerce and Transport

2. Electronic Data Interchange
EDI was first developed by the automobile / transportation industry in the 1970s.
the software or system used by companies to exchange business documents
a set of protocols
VAN/Internet- Networking.

3. Traditional Vs EDI

4. BENEFITS DRAWBACKS Mutual understanding Security Saves Time
Reduces Cost
Improves Customer Service
Strengthens Supplier Relationships
Can Increase Sales
Reduces human error
DRAWBACKS
Mutual understanding
Security

5. Basic Steps of EDI Sender Document preparation
Outbound translation (mapping)
Outbound communication (network)
Receiver
Inbound communication
Inbound translation
Document processing

6. Two standards Other standards In US ANSI X12. UN EDIFACT standard
EANCOM
Health Insurance Portability and Accountability Act (HIPAA)
Organisation for Data Exchange by Tele Transmission in Europe (ODETTE)
RosettaNet
Society of Worldwide Interbank Financial Telecommunication (SWIFT)

7. EDIFACT an international EDI standard a set of syntax rules
data elements, segments and codes
Messages
Envelopes

8. EDIFACT
Data elements
Segments
Message
Envelope

9. Message a single business document identified by a six character name
a collection of sequenced segments within defined areas
Begins with the Message Header (UNH) Segment
End with the Message Trailer (UNT) Segment.

10. Extended Payment Order (PAYEXT)

11. Seller-side
• IFTMAN—Arrival Notice
• CUSRES—Custom Response
• INVOIC—Invoices
Buyer-side
• ORDERS—Purchase Orders
• CUSDEC—Customs Declaration
• IFTMIN—Instruction Message
• REMADV—Remittance Advice
• PAYORD—Payment Order

12. Message Structure segment tables - ‘rules’ of the message
Requirements Designator field
Repetition field

13. Segment Groups- collections of segments repeat as a group

14. Segments
a collection of logically-related data elements in a fixed, defined sequence
three-character alphanumeric code
segment tag
Variable length data elements
simple or composite.
data element separator (+ and : )
data element terminator ‘
All segments are documented in the United Nations Trade Data Interchange Directory (UNTDID).

16. In EDIFACT, there are two kinds of segments:
Service Segments
Generic Segments
Envelopes (UNB-UNZ, UNG-UNE, UNH-UNT)
Delimiter String Advice (UNA)
Section Separator (UNS)
DOC to identify and specify documents
MOA for monetary amounts
DTM for dates and times
NAD for name and address data

17. Data Elements Simple - one piece of information
Composite - more than one piece of information, usually containing qualifiers
data elements must be accounted for by their position – use appropriate no of data element sep. to ‘skip over’ the empty field
Numeric

18. Alphabetic
Alphanumeric

19. Composite Data Elements
Value - first data element
Qualifier - gives additional definition

20. Electronic Enveloping
EDIFACT has two required levels of envelopes:
Interchange (UNB/UNZ): a set from one sender’s mailbox address to another sender’s mailbox address
Message (UNH/UNT): the envelope around one particular message

22. Message Envelope UNH segment has four data elements
Message Reference Number(M)
Message Identifier(M)
Common Access Reference Number(C)
Status of the Transfer(C)
UNT segment has two data elements
Number of Segments in a Message(M)

24. Common Access Reference Number
For Message #1: UNH+2348+ORDERS:D:94B:UN :C’
For Message #2: UNH DESADV:D:94B:UN ’
For Message #3: UNH INVOIC:D:94B:UN ’
For Message #4: UNH+2451+REMADV:D:94B:UN :F’

25. Interchange Envelope UNA segment UNB segment Delimiter String Advice
Examples of included data elements
UNB segment
Date/Time Stamp (M)
Interchange Control Numbers (M)
Password and Application Reference (C)
Processing Priority Reference (C)
Acknowledgment Request Indicators (C)
Communications Agreement ID (C)
Test Indicators (C)

26. EDI mapping UNZ segment
Interchange Control Numbers (M)
Counts of Messages or Groups in the Interchange (M)
EDI mapping
software allows for the automated movement of data received through (EDI) to in-house systems (also know as "back-end" systems).