Wednesday, August 10, 2011

EDIFACT - EDI for Administration, Commerce and Trade Envelop Structure (EDIFACT Standard)

EDIFACT - EDI for Administration, Commerce and Trade
Envelop Structure (EDIFACT Standard)



EDIFACT Interchange Header (UNB)
Pos
Segment
M/C
Repeat
010

S001
SYNTAX IDENTIFIER
M
1


0001
Syntax identifier
M



0002
Syntax version number
M



0080
Service code list directory version number
C



0133
Character encoding, coded
C

020

S002
INTERCHANGE SENDER
M
1


0004
Interchange sender identification
M



0007
Identification code qualifier
C



0008
Interchange sender internal identification
C



0042
Interchange sender internal sub-identification
C

030

S003
INTERCHANGE RECIPIENT
M
1


0010
Interchange recipient identification
M



0007
Identification code qualifier
C



0014
Interchange recipient internal identification
C



0046
Interchange recipient internal sub-identification
C

040

S004
DATE AND TIME OF PREPARATION
M
1


0017
Date
M



0019
Time
M

050

0020
Interchange control reference
M
1
060

S005
RECIPIENT'S REFERENCE/PASSWORD DETAILS
C
1


0022
Recipient reference/password
M



0025
Recipient reference/password qualifier
C

070

0026
Application reference
C
1
080

0029
Processing priority code
C
1
090

0031
Acknowledgement request
C
1
100

0032
Interchange agreement identifier
C
1
110

0035
Test indicator
C
1

EDIFACT Interchange Trailer (UNZ)
Pos
Segment
M/C
Repeat
010

0036
Interchange control count
M
1
020

0020
Interchange control reference
M
1




EDIFACT Functional Group Header (UNG)
Pos
Segment
M/C
Repeat
010

0038
Message group identification
C
1
020

S006
APPLICATION SENDER IDENTIFICATION
C
1


0040
Application sender identification
M



0007
Identification code qualifier
C

030

S007
APPLICATION RECIPIENT IDENTIFICATION
C
1


0044
Application recipient identification
M



0007
Identification code qualifier
C

040

S004
DATE AND TIME OF PREPARATION
C
1


0017
Date
M



0019
Time
M

050

0048
Group reference number
M
1
060

0051
Controlling agency, coded
C
1
070

S008
MESSAGE VERSION
C
1


0052
Message version number
M



0054
Message release number
M



0057
Association assigned code
C

080

0058
Application password
C
1

EDIFACT Functional Group Trailer (UNE)

Pos
Segment
M/C
Repeat
010

0060
Group control count
M
1
020

0048
Group reference number
M
1



EDIFACT Message Header (UNH)
Pos
Segment
M/C
Repeat
010

0062
Message reference number
M
1
020

S009
MESSAGE IDENTIFIER
M
1


0065
Message type
M



0052
Message version number
M



0054
Message release number
M



0051
Controlling agency, coded
M



0057
Association assigned code
C



0110
Code list directory version number
C



0113
Message type sub-function identification
C

030

0068
Common access reference
C
1
040

S010
STATUS OF THE TRANSFER
C
1


0070
Sequence of transfers
M



0073
First and last transfer
C

050

S016
MESSAGE SUBSET IDENTIFICATION
C
1


0115
Message subset identification
M



0116
Message subset version number
C



0118
Message subset release number
C



0051
Controlling agency, coded
C

060

S017
MESSAGE IMPLEMENTATION GUIDELINE IDENTIFICATION
C
1


0121
Message implementation guideline identification
M



0122
Message implementation guideline version number
C



0124
Message implementation guideline release number
C



0051
Controlling agency, coded
C

070

S018
SCENARIO IDENTIFICATION
C
1


0127
Scenario identification
M



0128
Scenario version number
C



0130
Scenario release number
C



0051
Controlling agency, coded
C


EDIFACT Message Trailer (UNT)

Pos
Segment
M/C
Repeat
010

0074
Number of segments in a message
M
1
020

0062
Message reference number
M
1


EDI X12 vs UN/EDIFACT
The table below highlights the difference between the EDI X12 standard and EDIFACT standard.
Topic
ANSI X12
UN/EDIFACT
Application
- Mostly  used in U.S and North America
- Mostly used in Europe and Asia
Terminologies Equivalence 
- Transaction Sets
- Messages
     - Loops
    - Groups
     - Terminators
    - Separators
Interchange
Header/Trailer Segments
 - ISA/IEA
- UNB/UNZ
Group
Header/Trailer Segments
 - GS/GE
- UNG/UNE (optional)
Transaction Set, (Message) 
Header/Trailer Segments
 - ST/SE
- UNH/UNT
Separators Specification Segment 
 - None
-  UNA (optional)
Commonly used Terminators, (Separators)
Segment
~
'
Element
*
+
Composite
>
:
Release Indicator 
 - Not supported
- Supported
    Composite Elements
     - Rarely used
    - Commonly Used
Acknowledgment 
 - TA1 and 997
- CONTRL
Binary support
 - BIN, BDS segments
-  ISO 9735-8 - Associated data in EDI
? Security
 - ASC X12.58 - Security Structures

-  ISO 9735-5 - Security rules for batch EDI (authenticity, integrity and non-repudiation of origin)
-  ISO 9735-6 - Secure authentication and acknowledgement message (message type - AUTACK)
-  ISO 9735-7 - Security rules for batch EDI (confidentiality)
-  ISO 9735-9 - Security key and certificate management message (message type - KEYMAN)


The main difference between EDIFACT and X12 are

1.EDIFACT uses composite data elements

2.Looping and nesting procedures are different

3.There are 6 data elements types are defined in ANSI X12 while only three are defined in EDIFACT

4.There is no provision in EDIFACT for optional fields

5.EDIFACT allows for two levels of syntax

6.And ofcourse the message structure in both standards is different for different messages.









1 comment:

  1. Here below an INVOIC D97B sample:

    UNB+UNOA:1+005435656:1+006415160:1+060515:1434+00000000000778'
    UNH+00000000000117+INVOIC:D:97B:UN'
    BGM+380+342459+9'
    DTM+3:20060515:102'
    RFF+ON:521052'
    NAD+BY+792820524::16++CUMMINS MID-RANGE ENGINE PLANT'
    NAD+SE+005435656::16++GENERAL WIDGET COMPANY'
    CUX+1:USD'
    LIN+1++157870:IN'
    IMD+F++:::WIDGET'
    QTY+47:1020:EA'
    ALI+US'
    MOA+203:1202.58'
    PRI+INV:1.179'
    LIN+2++157871:IN'
    IMD+F++:::DIFFERENT WIDGET'
    QTY+47:20:EA'
    ALI+JP'
    MOA+203:410'
    PRI+INV:20.5'
    UNS+S'
    MOA+39:2137.58'
    ALC+C+ABG'
    MOA+8:525'
    UNT+23+00000000000117'
    UNZ+1+00000000000778'

    ReplyDelete

Introducing a rate limiter feature in IBM Sterling Integrator allows for comprehensive API functionality without the need to invest in additional API tools.

To activate and integrate the rate limiter feature in Sterling Integrator for comprehensive API functionality, follow these steps. To ...