Recadv Edi

EDI IMPLEMENTATION GUIDELINES FOR Delphi
EDIFACT RECADV / Receiving Advice
Delphi Vega
Supplier EDI Specification
Receipt Advice
EDIFACT RECADV D97.A
Delphi Version 1.1

Final
Implementation Guideline RECADV
Version: 1.1 - 09/20/01
II.M01 - 1

DOCUMENT CHANGE LOG
Version
Date
1.0
1.1
1.1
1.1
2001.02.08
2001.09.20
2001.09.20
2001.09.20
Description
Document issued.
UNB example corrected
RFF+VN example corrected - RFF+CR
QVR Overshipped qty qualifier changed from 120 to 121
Version: 1.1 - 09/20/01
II.M01 - 2
0. TABLE OF CONTENT
0. TABLE OF CONTENT............................................................................................................................. 3
1. INTRODUCTION .................................................................................................................................... 4
2. MESSAGE DEFINITION.......................................................................................................................... 4
2.1.
2.2.
2.3.
2.4.
FUNCTIONAL DEFINITION ................................................................................................................ 4

PRINCIPLES.................................................................................................................................... 4
REFERENCES................................................................................................................................. 4
FIELD OF APPLICATION .................................................................................................................. 6
3. MESSAGE DESCRIPTION...................................................................................................................... 6
3.1. INTRODUCTION .................................................................................................................................... 6
3.1.1. How to read the documentation.................................................................................................... 6
3.1.2. General remarks ........................................................................................................................ 7
3.2. SEGMENT TABLE............................................................................................................................ 8
3.3. MESSAGE STANDARD DESCRIPTION................................................................................................ 11
3.4. SERVICE SEGMENTS DESCRIPTION............................................................................................. 16
3.5. DATA SEGMENTS DESCRIPTION................................................................................................... 21
3.6. EXAMPLE OF MESSAGE............................................................................................................... 35
Version: 1.1 - 09/20/01
II.M01 - 3
1. INTRODUCTION
This document provides the specific description of the EDIFACT RECADV D97.A message.
2. MESSAGE DEFINITION
This document provides the definition of a Receiving Advice Message, based on the EDIFACT
RECADV D97.A, to be used in Electronic Data Interchange (EDI) between Delphi and its
Trading Partners.
This documentation is fully comprehensive and allows the implementation of the EDIFACT
RECADV without the necessity for any additional standard related documentation.
2.1. FUNCTIONAL DEFINITION

The Receipt Advice message is a message from Delphi to a Delphi supplier to address the
business needs related to the goods receipt. This message is used to report the physical
receipt of goods. The message allows the reporting of discrepancies in products, quantities,
terms, packages, etc. The message may inform about the discrepancies: - between the
received consignment and the consignment information given in the Shipping Notification
message between the received goods and the ordered goods in the ORDERS, DELFOR, or
DELJIT information.
2.2. PRINCIPLES
The Receipt Advice message is intended to:
Notify supplier of receipt quantity descrepancies

Define receipt quantity descrepancies
Define cumulative receipt quantity descrepancies
2.3. REFERENCES
The content of this message is based on:
The message structure as defined by EDIFACT for the Receipt Advice Message
RECADV as published in the UN/EDIFACT D97.A Directory.
Version: 1.1 - 09/20/01
II.M01 - 4
The agreement between the Trading Partners on the data elements to be used, their
unique definition, their representation and their values (coded or clear form) as
identified in this document.
Version: 1.1 - 09/20/01
II.M01 - 5
2.4. FIELD OF APPLICATION

The following definition of a Receipt Advice Message in EDIFACT format is applicable for the
interchange of receipt advice information issued by Delphi for material deliveries to one or
more Delphi operations.
3. MESSAGE DESCRIPTION
Following pages contain a full description of the EDIFACT RECADV D97. A message as
implemented by Delphi. All segments are included regardless whether used or not used in
the interchange with Delphi. The official EDIFACT segment description is complemented with
remarks pertaining to the specific requirements for an interchange with Delphi. Those
remarks contain specific code values used, additional information on the values shown in a
specific field, etc. The aim of those remarks is to simplify the implementation of the message.
3.1. INTRODUCTION
3.1.1. How to read the documentation
All segments in the subset used by Delphi are described in the following pages. The
segment description is to be read as follows:
0020
BGM - BEGINNING OF MESSAGE
Segment group:
EDIFACT status:
Maximum use:
None.
Mandatory.
1 per message.
Function:
Delphi
interchange:
Example:
Level:
1.
Delphi status:
Mandatory.
Delphi
1 per message.
occurrences:
Segment for the unique identification of the delivery schedule document, by means of its
name and its number.
See remarks.
BGM+241+12+5
A
EDIFACT STANDARD DEFINITION

REF
NAME
ST
FT
C002
1001
1131
3055
C
C
C
C
an..3
an..3
an..3
:
:
:
C
C
an..35
1004
1056
1060
1225
DOCUMENT/MESSAGE NAME
Document/message name, coded
Code list qualifier
Code list responsible agency,
coded
Document/message name
DOCUMENT/MESSAGE
IDENTIFICATION
Document/message number
Version
Revision number
MESSAGE FUNCTION, CODED
C
C
C
C
an..35
an..9
an..6
an..3
:
:
+
+
4343
RESPONSE TYPE, CODED
an..3
1000
C106
B
Delphi IMPLEMENTATION
TAG
SP
Version: 1.1 - 09/20/01
ST
FT
REMARKS
C
C
an..3
'241 = Delivery Schedule
an..35
Delphi assigned release number
an..3
Function of the message. For code

values see below.
II.M01 - 6
COMMENTS
CODE VALUES
LEGEND
segment position in the message structure, segment tag and segment name.
identification (when applicable) of the segment group in which the segment is situated
and indication at which level the segment is in the message.
status of the segment: as defined by EDIFACT and by Delphi.
number of occurrences of the segment: as defined by EDIFACT and as used by

Delphi.
description of the function of the segment as defined by EDIFACT and as used by

Delphi.
example of the segment as it may appear in an interchange. This example is only

illustrative and does not necessarily represent an actual situation. It should NOT be
used as a basis to implement this message.
definition of the segment content as defined by EDIFACT and as implemented by

Delphi.
identification of the data elements in the segment

reference to the example.
data element tag - data elements with a C denote a composite data element.
data element name - italic CAPITALS denote a composite data element.
ST - the status of the data element.
FT - the format of the data element, i.e. the indication of the number of
characters (numerical or alphabetical) for this data element.
SP - the separator used between the data elements.
remarks on the specific use of the data element in the interchange with Delphi.
Shaded areas in the Delphi description mean that Delphi does not use the data
elements.
the segment description can be followed by:

comments providing more information regarding specific data elements and how
they must be used and/or understood in messages from Delphi.
code values to be used for data elements contained in the message.
3.1.2. General remarks

Following remarks are applicable for the complete documentation:
Dates
Unless otherwise specified in the field explanation in the documentation, dates are
always expressed as CCYYMMDD (qualifier 2379 = 102).
Times
Unless otherwise specified in the field explanation in the documentation, times are
always expressed as HHMM.
Version: 1.1 - 09/20/01
II.M01 - 7
3.2. SEGMENT TABLE

The following table shows the segments defined for the EDIFACT UNSM RECADV D97.A Receiving Advice message.
Shaded areas identify the segments that are not used in the subset of RECADV used by Delphi.
Must Use
Must Use
Must Use
Not Used
Pos
No
Seg
ID
0010
0020
0030
0040
UNH
BGM
DTM
ALI
0050
Name
Req
Desc
Message Header
Beginning of Message
Date/Time/Period
Additional Information
M
M
C
C
Segment Group1: REF-DTM
Max Use
Group
Repeat
1
1
10
5
10
Must Use
Must Use
0060
0070
RFF
DTM
Reference
Date/Time/Period
M
C
1
9
Must Use
Must Use
0080
0090
DOC
Segment Group2: DOC-SG3

Document/Message Details
C
M
Not Used
Not Used
0100
0110
0120
CDI
INP
Segment Group3: CDI-INP

Physical or Logical state
Parties to Instruction
C
M
C
1
5
Must Use
0130
Must Use
Not Used
0140
0150
NAD
LOC
Segment Group4:
NAD-LOC-SG5-SG6
Name and Address
Place/Location Identification
M
C
1
10
Not Used
Not Used
0160
0170
0180
RFF
DTM
Segment Group5: RFF-DTM

Reference
Date/Time/Period
C
M
C
1
1
Not Used
Not Used
0190
0200
0210
CTA
COM
Segment Group6: CTA-COM

Contact Information
Communication Contact
C
M
C
Not Used
0220
0230
TOD
Segment Group7: TOD-SG8-SG9

Terms of Delivery or Transport
C
M
Not Used
Not Used
0240
0250
0260
CDI
INP

Physical or Logical State
C
M
C
10
1
5
Not Used
Not Used
Not Used
0270
0280
0290
Segment Group9: LOC-CDI

Place/Location Identification
C
M
C
10
LOC
CDI
Not Used
Not Used
0300
0310
Segment Group10: TDT-DTM-CDI

Details of Transport
C
M
10
TDT
Version: 1.1 - 09/20/01
Notes and
Comments
10
10
10
10
10
10
1
II.M01 - 8
Not Used
Not Used
0320
0330
DTM
CDI
Not Used
0340
Not used
0350
EQD
Not used
Not used
Not used
0360
0370
0380
Not used
Not used
Not used
Date/Time/Period
C
C
C
9999
Equipment Details
CDI
INP

C
M
C
1
5
0390
0400
0410
SEL
CDI
Segment Group13: SEL-CDI

Seal Number
C
M
M
1
10
Not used
Not used
0420
0430
EQA
Segment Group14: EQA-SG15

Attached Equipment
C
M
Not used
Not used
Not used
0440
0450
0460
CDI
INP

M
C
1
5
Must Use
Must Use
0470
0480
CPS
Segment Group16: CPS-SG17-SG22

Consignment Packing Sequence
C
M
Not used
Not used
Not used
0490
0500
0510
PAC
QVR
Segment Group17: PAC-QVR-SG18

Package
Quantity Variances
C
M
C
1
1
Not used
0520
Not used
Not used
Not used
Not used
Not used
0530
0540
0550
0560
0570
Not used
Not used
0580
0590
Not used
Not used
Not used
0600
0610
0620
0630
CDI
INP
0640
0650
0660
0670
0680
0690
0700
LIN
PIA
IMD
QTY
QVR
DTM
PRI
Must Use
Not Used
Not Used
Must Use
Must Use
Not Used
Not Used
SEGMENT GROUP11: EQD-SG12SG13-SG14
SEGMENT GROUP18: PCI-RFFSG19-SG20
PCI
RFF
10
25
10
10
999
9999
999
CDI
INP
Package Identification
Reference
M
C
C
M
C
1
5
GIN
Segment Group20: GIN-SG21

Goods Identity Number
C
M
0710

Segment Group22: LIN-PIA-IMDQTY-QVR-DTM-PRI-SG23-SG24SG26-SG28-SG29
Line Item
Additional Product Id
Item Description
Quantity
Quantity Variances
Date/Time/Period
Price Details
Version: 1.1 - 09/20/01
10
99
10
M
C
C
1
5
M
C
C
C
C
C
C
1
10
25
10
10
5
1
9999
10
II.M01 - 9
Not Used
Not Used
0720
0730
CDI
INP

M
C
1
5
Not Used
Not Used
0740
0750
DOC
Segment Group24: DOC-SG25

Document/Message Details
C
M
Not Used
Not Used
Not Used
0760
0770
0780
CDI
INP

Physical or Logical state
C
M
C
1
5
Not Used
Not Used
0790
0800
GIN

C
M
Not Used
Not Used
Not Used
0810
0820
0830
CDI
INP

C
M
C
1
5
Must Use
Not Used
0840
0850
0860
RFF
DTM
Segment Group28: RFF-DTM

Reference
Date/Time/Period
C
M
C
1
1
Not Used
0870
Not Used
Not Used
Not Used
0880
0890
0900
PCI
QTY
QVR
Segment Group29: PCI-QTY-QVRSG30-SG31

Package Identification
Quantity
Quantity Variances
Not Used
Not Used
Not Used
0910
0920
0930
CDI
INP

C
M
C
1
5
Not Used
Not Used
0940
0950
GIN

C
M
Not Used
Not Used
Not Used
0960
0970
0980
CDI
INP

C
M
C
1
5
Not Used
Must Use
0990
1000
CTN
UNT
Control Total
Message Trailer
C
M
1
1
Version: 1.1 - 09/20/01
10
10
99
10
10
9999
1
1
1
10
10
10
II.M01 - 10
3.3. MESSAGE STANDARD DESCRIPTION

This section provides the description of the UN Standard Message RECADV as defined in the
97.A Directory. Only the segments printed in bold are used in the subset defined by Delphi
and will be further explained in section 3.6.
3.3.1
Header section
Information to be provided in the Header section:

0010 UNH, Message header
A service segment starting and uniquely identifying a message. The message type code for the Receipt
Advice message is RECADV.
0020 BGM, Beginning of message

A segment for unique identification of the Receipt Advice message by means of its name and its number
and its function (original, replacement, and change).
0030 DTM, Date/time/period

The DTM segment shall be used to specify the receipt advice message date.
0040 ALI, Additional information

A segment indicating that the line item is subject to special conditions due to origin, customs preference,
or commercial factors.
0050 Segment group 1: RFF-DTM

A group of segments giving references relevant to the whole message, e.g. contract number.
0060 RFF, Reference

A segment for referencing documents relating to the whole receipt adive, e.g. advance ship notice
number.

Date or time, or date and time of the reference. This segment will provice the date of the advance ship
notice referenced in the preceding RFF segement.
0080 Segment group 2: DOC SG3

A group of segments identifying the discrepancies with the documentary requirements relating to the
whole cosignment.
0090 DOC, Document/message details

A segment describing the documents required for the specified consignee.
0100 Segment group 3: CDI-INP

A group of segments to report the physical or logical state of the document upon receipt and to give the
appropriate instructions if needed.
0110 CDI, Physical or Logical state

A segment to report the logical state of the document upon receipt
0120 INP, Parties to Instruction

A segment to give instructions to correct the discrepancy reflected by the CDI segment
0130 Segment group 4: NAD-LOC-SG5-SG6

A group of segments to identifying names, addresses, and locations relevant to the whole receiving
advice
0140 NAD, Name and address

A segment for identifying names and addresses and their functions relevant for the whole Receipt
Advice. The principal parties for the Receipt Advice message shall be identified.
0150 LOC, Place/location identification

A segment identifying a specific location at the consignee address (e.g. dock, gate,) to which product, as
specified in the LIN-Segment groups, should be delivered.
Version: 1.1 - 09/20/01
II.M01 - 11

A group of segments giving references relevant to the party.
0170 RFF, Reference

A segment giving references related to the party.

Date/time/period of the reference.
0190 Segment group 6: CTA-COM

A group of segments to identify person, function, or department and appropriate numbers to whom
communication should be directed.
0200 CTA, Contact information

A segment to identify the person, function, or department to whom communication should be directed.
0210 COM, Communication contact

A segment identifying communication types and numbers for the person, function, or department identified
in the CTA segment.
0220 Segment group 7: TOD-SG8-SG9

A group of segments to report on discrepancies on terms of deliveries
0230 TOD, Terms of Delivery or Transport

A segment to indicate the terms of delivery



0270 Segment group 9: LOC-CDI

A group of segments to report discrepancy on locations related to terms of delivery
0280 LOC, Place/location identification

A segment identifying a specific location at the consignee address (e.g. dock, gate,) to which product, as
specified in the LIN-Segment groups, should be delivered.

0300 Segment group 10: TDT-DTM-CDI

A group of segments specifying details of the mode and means of transport, the date or date and time of
arrival, if a discrepancy has occurred or if required by the recipient of the message for further
identification
0310 TDT, Details of transport

A segment specifying the carriage, and the mode and means of transport.

A segment indicating the date/time/period details of departure or arrival relating to the TDT segment.

0340 Segment group 11: EQD-SG12-SG13-SG14

A group of segments identifying equipment with which a problem has occurred or if required by the
recipient of the message for further identification
0350 EQD, Equipment Details

A segment to identify the specific equipment item.

Version: 1.1 - 09/20/01
II.M01 - 12


0390 Segment group 13: SEL-CDI

A group of segments identifying the seal number and reporting anomalies.
0400 SEL, Seal Number

A segment specifying a seal number

0420 Segment group 14: EQA-SG15

A group of segments identifying attached equipment with which a problem has ocurred or if required by
the recipient of the message for further identification
0430 EQA, Attached equipment

A segment identifying equipment attached to the equipment identified in the EQD segment.



3.3.2
Detail section
0470 Segment group 16: CPS-SG17-SG22

A group of segments providing details of all packages and/or individual items as received. This segment
group provides the capability to give the top down hierarchical relationship of the packaging levels.
0480 CPS, Consignment Packing Sequence

A segment identifying the sequence in which packing of the consignment is presented.
0490 Segment group 17: PAC-QVR-SG18

A group of segments identifying packaging, quantities and maks and numbers.
0500 PAC, Package

A segment specifying the number of package units and the type of packaging for the line item, e.g. pallet.
0510 QVR, Quantity Variances

A segment identifying quantity variances between the number the number of units received and the
number of units expected or planned.
0520 Segment group 18: PCI-RFF-SG19-SG20

A group of segments identifying packaging, quantities and maks and numbers.
0530 PCI, Package identification

Version: 1.1 - 09/20/01
II.M01 - 13
A segment specifying markings and labels used on individual physical units (packages) described in the
PAC segment.
0540 RFF, Reference

A segment giving references related to the party.



0580 Segment group 20: GIN-SG21

A group of segments giving package identification numbers and if required the related anomalies
0590 GIN, Goods identity number

A segment providing identity numbers to be applied to the packages to be delivered.



0630 Segment group 22: LIN-PIA-IMD-QTY-QVR-DTM-PRI-SG23-SG24-SG26-SG28-SG29

A group of segments providing details of the product or services received
0640 LIN, Line Item

A segment identifying the product or service received.
0650 PIA, Additional Product ID

A segment providing additional product or service identification
0660 IMD, Item Description

A segment describing the product or service received. This segment should be used for a product or
service that cannot be identified by a product code or article number.
0670 QTY, Quantity

A segment to give quantity information about the product specified in the LIN, PIA, or IMD segment

A segment identifying quantity variances between quantity per item and quantity per item expected or
planned

0700 PRI, Price Details

A segment to provide price information related to the current line item.


Version: 1.1 - 09/20/01
II.M01 - 14

0740 Segment group 24: DOC-SG25

A group of segments identifying the discrepancies with the documentary requirements relating to the line
item
0750 DOC, Document/Message Details

A segment identifying documents where a discrepancy occurs.




A group of segments giving goods identificaiton numbers and if required the related anomolies





A group of segments giving references relevant to the line item.
0850 RFF, Reference

A segment giving references related to the line item. This segment will provide the Delphi schedule
agreement number corresponding to the goods receipt.

0870 Segment group 29: PCI-QTY-QVR-SG30-SG31

A group of segments identifying one specific package or a number of packages, the marks and the
numbers, quantities and receiving conditions.
0880 PCI, Package Identification

A segment specifying markings and labels used on identified packages.
0890 QTY, Quantity

A segment to give quantity information about the product specified in the LIN, PIA, or IMD segment

A segment identifying quantity variances between quantity per item and quantity per item expected or
planned

Version: 1.1 - 09/20/01
II.M01 - 15



A group of segments giving goods identificaiton numbers and if required the related anomolies




0990 CTN, Control Total

A segment by which control total may be provided by sender for checking by the receiver
1000 UNT, Message Trailer

A service segment ending a message, giving the total number of segments in the message and the control
reference number of the message.
3.4 SERVICE SEGMENTS DESCRIPTION

Following service segments are as defined by UN/EDIFACT and presented under ISO 9735.
The UNB, UNH, UNT and UNZ segments are the envelope of any message, enclosing all the
data that is being transmitted.
The UNB (Interchange header) and UNZ (Interchange trailer) segments mark respectively the
beginning and the end of an interchange thereby providing a unique interchange control
reference.
Within the interchange the UNH (message header) and UNT (Message trailer) segments
uniquely begin and end the various messages contained in an interchange.
UNB
UNH
MESSAGE
1
UNT
UNH
EXAMPLE OF AN
INTERCHANGE STRUCTURE
MESSAGE
2
UNT
...
UNH
Version: 1.1 - 09/20/01
II.M01 - 16
MESSAGE
N
UNT
UNZ
Version: 1.1 - 09/20/01
II.M01 - 17
0000
UNB - INTERCHANGE HEADER
Segment Group:
EDIFACT status:
Maximum use:
Function
none
Level:
0
mandatory
Delphi status:
mandatory
1 per interchange
Delphi occurrences: 1 per interchange
service segment providing the unique identification of an interchange. It allows the identification of
the sender and the receiver of the interchange, gives date and time of preparation as well as the
interchange control reference and the application reference.
Delphi interchange: see remarks.
Example:
UNB+UNOA:2+MBXNODelphi+MBXNOSUPPLIER+970611:0735+12++RECADV
A

REF
TAG
NAME
ST
FT
SP
ST
FT
REMARKS
a4
n1
UNOA.
Indication of the syntax version used for this
message.
A
B
S001 SYNTAX IDENTIFIER

0001 Syntax identifier
0002 Syntax version number
M
M
M
a4
n1
:
+
M
M
M
S002 INTERCHANGE SENDER

0004 Sender identification
M
M
an..35
M
M
an..35
Communication code/mailbox number of the

party originating the message.
Identification code qualifier

Address for Reverse Routing
INTERCHANGE RECIPIENT
Recipient identification
C
C
M
M
an..4
an..14
:
+
0007
0008
S003
0010
an..35
M
M
an..35
Communication code/mailbox number of the

party receiving the message.
Identification code qualifier

Routing address
DATE / TIME OF PREPARATION
Date of preparation
Time of preparation
INTERCHANGE CONTROL REFERENCE
C
C
M
M
M
M
an..4
an..14
:
+
E
F
G
0007
0014
S004
0017
0019
0020
n6
n4
an..14
:
+
+
M
M
M
M
n6
n4
an..14
YYMMDD format
HHMM format
The ICR number is UNIQUE within an inventory
year.
M
C
an..14
an2
:
+
C
C
C
C
C
an..14
a1
n1
an..35
n1
+
+
+
+
'
an..14
RECADV
n1
S005 RECIPIENTS REFERENCE

PASSWORD
0022 Recipient's reference / password
0025 Recipient's reference / password
qualifier
0026 APPLICATION REFERENCE
0029 PROCESSING PRIORITY CODE
0031 ACKNOWLEDGEMENT REQUEST
0032 COMMUNICATIONS AGREEMENT ID
0035 TEST INDICATOR
Will be sent during testing
COMMENTS
Version: 1.1 - 09/20/01
II.M01 - 18
0010
UNH - MESSAGE HEADER
Segment group:
EDIFACT status:
Maximum use:
Function:
none
Level:
0
mandatory.
Delphi status:
mandatory.
1 per message.
Delphi occurrences: 1 per message.
service segment starting and uniquely identifying a message. The message type code for the
Receiving Advice is RECADV.
Example:
UNH+1+RECADV:D:97A:UN
A

REF
TAG
0062
S009
0065
0052
0054
0051
0057
0068
S010
0070
0073
B
C
D
E
NAME
ST
FT
SP
ST
FT
REMARKS
MESSAGE REFERENCE NUMBER
an..14
an..14
Message Control number assigned by the

sender to the message. See comments below.
MESSAGE IDENTIFIER
Message type
Message version number
Message release number
Controlling agency
Association assigned code
COMMON ACCESS REFERENCE
STATUS OF TRANSFER
Sequence of transfer
First and last transfer
M
M
M
M
M
C
C
C
M
C
an..6
an..3
an..3
an..2
an..6
an..35
:
:
:
:
+
+
M
M
M
M
M
an..6
an..3
an..3
an..2
RECADV .
D.
97A.
UN.
n..2
a1
COMMENTS
0062 - Message Reference Number
The Message Reference number used by Delphi is structured as follows:
First message:
Second message:
Up to:
1
2
9999
Version: 1.1 - 09/20/01
II.M01 - 19
1000
UNT - MESSAGE TRAILER
Segment group:
EDIFACT status:
Maximum use:
Function: service
none
Level:
0
mandatory
Delphi status:
mandatory
1 per message
Delphi occurrences: 1 per message
segment ending a message, giving the total number of segments in the message and the control
reference number of the message.
Example:
UNT+99+1
A

REF
TAG
0074
0062
NAME
NUMBER OF SEGMENTS IN THE

MESSAGE
MESSAGE REFERENCE NUMBER
ST
FT
SP
ST
FT
n..6
n..6
an..14
an..14
REMARKS
Control count of the number of segments in

the message, including UNH and UNT.
Number must be identical to UNH - tag 0062
1010 UNZ - INTERCHANGE TRAILER

Segment Group:
none
Level:
0
EDIFACT status:
mandatory
Delphi status:
mandatory
Maximum use:
1
Delphi occurrences: 1 per interchange
Function: service segment ending an interchange and giving the number of messages contained in the interchange as
well as the Interchange Control Reference number.
Example:
UNZ+1+12
A

REF
A
B
TAG
NAME
0036 INTERCHANGE CONTROL COUNT

0020 INTERCHANGE CONTROL REFERENCE
ST
FT
SP
ST
FT
REMARKS
M
M
n..6
an..14
M
M
n..6
an..14
Number of messages in an interchange.

Value must be the same as 0020 - Interchange
Control Reference in UNB.
Version: 1.1 - 09/20/01
II.M01 - 20
3.5. DATA SEGMENTS DESCRIPTION

This part includes only the segments defined in the standard and used in the subset
exchanged between Delphi and its Trading Partners. The segments are described in the
same sequence as they appear in the message.
The EDIFACT RECADV segments that are not used in the subset used by Delphi are included
in alphabetical sequence under item 3.9.
0020 BGM - BEGINNING OF MESSAGE

Segment group:
none
Level:
1
EDIFACT status:
mandatory
Delphi status:
mandatory
Maximum use:
1 per message
Function: segment for the unique identification of the delivery schedule document, by means of its name and its
number.
Example:
BGM+632+23445566+9
A

REF
TAG
NAME
ST
C002
1001
Document/message name, coded
C
C
1131
3055
1000
C106
FT
SP
ST
FT
an..3
C
M
an..3
632 = Goods Receipt. Document/message

issued by a port, warehouse/shed, or terminal
operator acknowledging receipt of goods
specified therein on conditions stated or
referred to in the document
C
C
C
C
an..3
an..3
an..35
:
:
+
an..35
an..35
Reference
number
assigned
to
the
document/message by the issuer. Reference
identification number unique for a calendar
year.
an..3
9 = Original Receipt Advice

Code indicating function of the message.
1004
Code list qualifier

Code list responsible agency, coded
Document/message name
DOCUMENT/MESSAGE
IDENTIFICATION
1056
1060
1225
Version
Revision number
MESSAGE FUNCTION, CODED
C
C
C
an..9
an..6
an..3
:
+
+
4343
RESPONSE TYPE, CODED
an..3
REMARKS
CODE VALUES
1001 Document/Message name, coded

632
Goods Receipt
1225 - Message Function, coded

9
Original Receipt Advice
Version: 1.1 - 09/20/01
II.M01 - 21
0030 DTM - DATE/TIME/PERIOD

Segment group:
none
Level:
1
EDIFACT status:
mandatory
Delphi status:
mandatory
Maximum use:
10 per message at level 1
Delphi occurrences: max. 3 per message
Function: segment specifying the date, and when relevant, the time/period of the beginning and ending of the validity
period of the document. The DTM must be specified at least once to identify the Delivery Schedule
document date.
Delphi interchange: there may be up to 3 occurrences of DTM in position 0030: one to specify the message issue date,
one to specify the horizon start date and one for the horizon end date.
Example:
DTM+137:20010616:102
A

REF
TAG
NAME
ST
FT
M
M
C
C
an..3
an..35
an..3
SP
ST
FT
:
:
M
M
M
M
an..3
an..35
an..3
REMARKS
Receipt Advice Document Date

A
B
C
C507
2005
2380
2379
DATE/TIME/PERIOD
Date/time/period qualifier
Date/time/period
Date/time/period format qualifier
137 = Document date.

Receipt Advice Date
102 = CCYYMMDD.
CODE VALUES
2005 Date/Time/Period Qualifier
137
Document Date
Version: 1.1 - 09/20/01
II.M01 - 22
Segment group 1: RFF-DTM

Segment group:
EDIFACT status:
Maximum use:
Function:
Delphi interchange:
1 [RFF-DTM]
Level:
1
Conditional
Delphi status:
Cconditional
10 per message
group of segments giving references related to the line item and where necessary, their dates.
see segment description.
0060
RFF - REFERENCE
Segment group:
EDIFACT status:
Maximum use:
Function:
1 [RFF-DTM]
Level:
1
mandatory if segment group 1 is used
Delphi status:
mandatory
1 per segment group 1
Delphi occurrences: 1 per segment group 1
segment for identifying documents relating to the line item, e.g. a contract and its appropriate line
item.
Example:
RFF+SI:A1A2A3A4A
RFF+BM:456456
RFF+CR:18000999
A

REF
TAG
NAME
ST
C506
1153
REFERENCE
Reference qualifier
M
M
1154
1156
4000
Reference number
Line number
Reference version number
C
C
C
REF
TAG
C506
1153
REFERENCE
Reference qualifier
M
M
1154
1156
4000
Reference number
Line number
C
C
C
REF
TAG
C506
1153
REFERENCE
Reference qualifier
M
M
1154
Reference number
1156
4000
Line number
FT
SP
ST
FT
an..3
M
M
an..3
an..35
an..6
an..35
:
:
an..35
SP
ST
FT
an..3
M
M
an..3
an..35
an..6
an..35
:
:
an..35
SP
ST
FT
an..3
M
M
an..3
an..35
an..35
C
C
an..6
an..35

NAME
ST
ST
SI=Shipper Identification Number.

Code
giving specific meaning to a reference
number.
Reference identification number
FT

NAME
REMARKS
REMARKS
BM=Bill of Lading Number. Code giving

specific meaning to a reference number.
Reference identification number
FT
REMARKS
CR= Delphi Delivery Number. Code giving

specific meaning to a reference number.
Reference identification number.
Delphi
internal reference to the shipment.
CODE VALUES
Version: 1.1 - 09/20/01
II.M01 - 23
1153 - Communication number, qualifier

SI
BM
CR
Shippers Identification Number

Bill of Lading Number
Customer Reference Number
Version: 1.1 - 09/20/01
II.M01 - 24
0700
DTM - DATE/TIME/PERIOD
Segment group:
EDIFACT status:
Maximum use:
Function:
1 [RFF-DTM]
Level:
1
Conditional
Delphi status:
Conditional
segment specifying the date, and when relevant, the time/period of the beginning and ending of the
validity period of the document.
Delphi interchange: there will only be one occurrence of this DTM segment to specify the ship notice date. This segment
will follow the RFF segment with reference to the ship notice reference number.
Example:
DTM+111:20010611:102
A

REF
TAG
NAME
ST
FT
M
M
C
C
an..3
an..35
an..3
SP
ST
FT
:
:
M
M
M
M
an..3
an..35
an..3
REMARKS
Document generation date.

A
B
C
C507
2005
2380
2379
DATE/TIME/PERIOD
Date/time/period qualifier
Date/time/period
Date/time/period format qualifier
111 = Manifest / Ship Notice Date

Actual Ship Notice Date
102 = CCYYMMDD.
CODE VALUES
2005 Date/Time/Period Qualifier
111
Manifest / Ship Notice Date
Version: 1.1 - 09/20/01
II.M01 - 25
Segment group 2: DOC-SG3

Segment group:
EDIFACT status:
Maximum use:
Function:
2 [DOC-SG3]
Conditional
10 per message
Level:
1
Delphi status:
Conditional
group of segments identifying the discrepancies with the documentary requirements relating to the whole cosighnment.
Delphi interchange: See segment description.
0080 DOC DOCUMENT/MESSAGE DETAILS

Segment group:
2 [DOC-SG3]
Level:
1
EDIFACT status:
mandatory if segment group 2 is used
Delphi sta tus:
mandatory
Maximum use:
Function: segment describing the documents required for the specified consignee
Example:
DOC+632
A
REF
TAG
C002
1001
1131
3055
1000
C503
1004
1373
1366
3453
3153
1220
1218
NAME
ST
FT
SP
ST
FT
Document/Message name, coded
M
C
an..3
an..3
Code list qualifier

Code list responsible agency coded
Document/Message name
DOCUMENT/MESSAGE DETAILS
Document/message status, coded
Document/message source
Language, coded
Communication channel identifier
Number of copies of document
required
Number of originals of document
required
C
C
C
an..3
an..3
an..35
:
:
+
an..35
an..3
an..35
an..3
an..3
n..2
:
:
:
+
+
+
n..2
REMARKS
632 = Goods Receipt

Identification of the type of document/message
by code or name.
CODE VALUES
1001 Document/Message Name, coded
632
Goods Receipt
Version: 1.1 - 09/20/01
II.M01 - 26
Segment group 4: NAD-LOC-SG5-SG6

Segment group:
4 [NAD-LOC-SG5-SG6]
Level:
1
EDIFACT status:
mandatory
Delphi status:
mandatory
Maximum use:
10
Delphi occurrences: 3
Function: group of segments identifying names, addresses, and locations relevant to the whole receiving advice
Delphi interchange: see segment description.
0130 NAD - NAME AND ADDRESS

Segment group:
4 [NAD-LOC-SG5-SG6]
Level:
1
EDIFACT status:
mandatory
Delphi status:
mandatory
Maximum use:
Function: segment for identifying names and addresses and their functions relevant to the receipt advice
Example:
NAD+SU+2223412::16
NAD+MI+102356::92
NAD+ST+1998877::92
A
REF
TAG
NAME
ST
FT
3035
C082
3039
1131
3055
C058
3124
3124
C080
3036
3036
3036
3045
C059
3042
3042
3164
3229
PARTY QUALIFIER
PARTY IDENTIFICATION DETAILS
Party id. Identification
Code list qualifier
NAME AND ADDRESS
Name and address line
Name and address line
PARTY NAME
Party name
Party name
Party name
Party name format, coded
STREET
Street and number/P.O.. box
Street and number/P.O.. box
CITY NAME
COUNTRY SUB-ENTITY
IDENTIFICATION
POSTCODE IDENTIFICATION
COUNTRY, CODED
M
C
M
C
C
C
M
C
C
M
C
C
C
C
M
C
C
C
C
C
B
C
3251
3207
SP
ST
FT
an..3
an..3
SU = Supplier
an..35
an..3
an..3
:
:
+
M
M
M
REMARKS
an..35
Code identifying the supplier
an..3
For code value see below.
an..35
an..35
:
+
an..35
an..35
an..35
an..3
:
:
:
+
an..35
an..35
an..35
an..9
:
+
+
+
an..9
an..3
CODE VALUES
3035 Party Qualifier
SU
Supplier
3055 - Code List Responsible Agency, coded
Version: 1.1 - 09/20/01
II.M01 - 27

16
92
DUN & Bradstreet (DUNS)

Assigned by buyer
0130 NAD - CONTINUED

Material Release Issuer
A
B
C
3035
PARTY QUALIFIER
C082
3039
1131
3055
C058
C080
3036

Code list qualifier
NAME AND ADDRESS
PARTY NAME
Party name
REST OF SEGMENT NOT USED.
C
M
C
C
C
C
M
PARTY QUALIFIER
Code list qualifier
NAME AND ADDRESS
PARTY NAME
Party name
REST OF SEGMENT NOT USED.
M
C
M
C
C
C
C
M
an..3
an..35
an..3
an..3
:
:
+
an..35
an..3
an..35
an..3
an..3
:
:
+
an..35
An..3
MI = Planning schedule/material release

issuer.
M
M
an..35
Code identifying the issuer.
an..3
M
M
M
an..3
ST = Ship To
an..35
Code identifying the ship from location.
an..3
Ship To
A
B
C
3035
C082
3039
1131
3055
C058
C080
3036
CODE VALUES
3035 Party Qualifier
MI
ST
Planning Schedule/Material Release Issuer

Ship To
3055 - Code List Responsible Agency, coded

16
92
DUN & Bradstreet (DUNS) - (currently used by Delphi with 9 digits)

Assigned by buyer
Version: 1.1 - 09/20/01
II.M01 - 28
Segment group 16: CPS-SG17-SG22

Segment group:
EDIFACT status:
Maximum use:
Function:
16 [CPS-SG17-SG22]
Level:
1
mandatory
Delphi status :
mandatory
9999
Delphi occurrences: 9999
group of segments providing details of all packages and/or individual items as received. This
segment group provides the capability to give the top-down hierarchical relationship of the package
levels.
Delphi interchange: see segment description.
0480
CPS CONSIGNMENT PACKING SEQUENCE
Segment group:
EDIFACT status:
Maximum use:
Function:
Delphi interchange:
16 [CPS-SG17-SG22]
Level:
1
mandatory
Delphi status:
mandatory
segment identifying the sequence in which packing of the consignment is presented
see remarks
Example:
CPS+1++4
A

REF
TAG
7164
7166
7075
NAME
ST
FT
SP
ST
FT
Hierarchical id number
REMARKS
an..12
an..12
A unique number assigned by the sender to

identify within a hierarchical structure. Begins
with the number 1 and increments by one for
each occurrence within the message.
Hierarchical id numbers are not to be repeated
within the same message.
Hierarchical parent id
Packaging level
C
C
an..12
an..3
an..3
4= No packaging hierarchy. There is no

specfiable leel of packaging: packaging is
inner and outer level as well.
CODE VALUES
7075 Packaging Level
4
No Packaging Hierarchy
Version: 1.1 - 09/20/01
II.M01 - 29
Segment group 22: LIN-PIA-IMD-QTY-QVR-DTM-PRI-SG23-SG24SG25-SG26-SG28-SG29

Segment group:
EDIFACT status:
Maximum use:
Function:
Delphi interchange:
22 [LIN-PIA-IMD-QTY-QVR-DTM-PRI-SG23-SG29] Level:
2
conditional
Delphi status:
conditional
9999
Delphi occurrences: max. 9999
group of segments providing details of the individual line items received.
0640 LIN - LINE ITEM

Segment group:
EDIFACT status:
Maximum use:
Function:
22 [LIN-PIA-IMD-QTY-QVR-DTM-PRI]
Level:
2
mandatory
Delphi status:
mandatory
segment identifying the details of the product or service that has been delivered, e.g. product
identification. All other segments in the detail section following the LIN segment refer to the line item.
Example:
LIN+++12345678:IN
A

REF
A
B
TAG
NAME
ST
FT
1082
1229
LINE ITEM NUMBER

ACTION REQUEST/ NOTIFICATION,
CODED
ITEM NUMBER IDENTIFICATION
Item number
Item number type, coded
Code list qualifier
SUB-LINE INFORMATION
Sub-line indicator, coded
Line item number
CONFIGURATION LEVEL
CONFIGURATION, CODED
C
C
n..6
an..3
+
+
an..35
an..3
an..3
an..3
:
:
:
+
an..3
an..6
n..2
an..3
:
+
+
C212
7140
7143
1131
3055
C829
5495
1082
1222
7083
C
C
C
C
C
C
C
C
C
C
SP
ST
FT
M
M
M
an..35
an..3
REMARKS
Delphi assigned part number.

IN = Buyers item number.
CODE VALUES
7143 Item number type, coded
IN
Buyers Item Number
Version: 1.1 - 09/20/01
II.M01 - 30
0670
QTY - QUANTITY
Segment group:
EDIFACT status:
Maximum use:
Function:
Delphi interchange:
Level:
3
Conditional
Delphi status:
mandatory
segment to give quantity information about the product specified in the LIN, PIA, or IMD segment.
see remarks.
Example:
QTY+12:9999
QTY+48:9999
A

REF
TAG
A
B
C186
6063
6060
6411
REF
TAG
A
B
C
C186
6063
6060
6411
NAME
ST
QUANTITY DETAILS
Quantity qualifier
Quantity
Measure unit qualifier
M
M
M
C
FT
an..3
n..15
an..3
SP
:
:
ST
FT
M
M
M
an..3
n..15
ST
FT
M
M
M
an..3
n..15
REMARKS
12 = Dispatch Quantity.
Advance Ship Notice Quantity
NAME
ST
FT
QUANTITY DETAILS
Quantity qualifier
Quantity
Measure unit qualifier
M
M
M
C
an..3
n..15
an..3
SP
:
:
REMARKS
48 = Received Quantity
Quantity which has been received
CODE VALUES
6063 Quantity Qualifier
12
48
Dispatch Quantity
Received Quantity
Version: 1.1 - 09/20/01
II.M01 - 31
0680
QVR QUANTITY VARIANCES
Segment group:
EDIFACT status:
Maximum use:
Function:
Level:
3
Conditional
Delphi status:
mandatory
segment identifying quantity variances between quantity per item and quantity per expected or
planned.
Delphi interchange: one QVR segment will be transmitted to notify supplier of either a short shipped descrepancy or an
over shipped descrepancy. see remarks.
Example:
QVR+100:119
QVR+50:121
A

REF
TAG
C279
A
NAME
ST
FT
SP
6064
6063
QUANTITY DIFFERENT
INFORMATION
Quantity difference
Quantity qualifier
C
M
C
n..15
an..3
:
+
4221
C960
4295
1131
3055
4294
Descrepancy, coded
REASON FOR CHANGE
Change reason
Code list qualifier
Code list responsible agency
Change reason
C
C
C
C
C
C
an..3
an..3
an..3
an..3
an..35
:
:
:
ST
FT
M
M
C
n..15
an..3
ST
FT

REF
TAG
C279
A
6064
6063
NAME
QUANTITY DIFFERENT
INFORMATION
Quantity difference
Quantity qualifier
ST
Short shipped descrepancy quantiy

119 = Short Shipped. The descrepancy
quantity received is below the ship notification
quantity.
FT
SP
C
M
C
REMARKS
REMARKS
M
n..15
an..3
:
+
M
C
n..15
an..3
Version: 1.1 - 09/20/01
Over shipped descrepancy quantiy

121 = Over Shipped. The descrepancy
quantity received is over the ship notification
quantity.
II.M01 - 32

4221
C960
4295
1131
3055
4294
Descrepancy, coded
REASON FOR CHANGE
Change reason
Code list qualifier
Code list responsible agency
Change reason

C
C
C
C
C
C
an..3
an..3
an..3
an..3
an..35
:
:
:
CODE VALUES
6063 Quantity Qualifier
119 Short Shipped
121 Over Shipped
Segment group 28: RFF-DTM

Segment group:
EDIFACT status:
Maximum use:
Function:
Delphi interchange:
28 [RFF-DTM]
Level:
3
conditional
Delphi status:
mandatory
group of segments giving references related to the line item and where necessary, their dates.
0850
RFF - REFERENCE
Segment group:
EDIFACT status:
Maximum use:
Function:
Delphi interchange:
Example:
28 [RFF-DTM]
Level:
1
mandatory
Delphi status:
mandatory
segment for identifying documents relating to the line item, e.g. schedule agreement number
see remarks.
RFF+ON:55000099
A

REF
A
B
TAG
C506
1153
1154
1156
4000
NAME
REFERENCE
Reference qualifier
Reference number
Line number
ST
M
M
C
C
C
FT
an..3
an..35
an..6
an..35
SP
:
:
:
ST
FT
M
M
C
an..3
an..35
REMARKS
ON=Order number.
Delphi Schedule Agreement Number
CODE VALUES
Version: 1.1 - 09/20/01
II.M01 - 33
1153 - Communication number, qualifier

ON
Order Number
Version: 1.1 - 09/20/01
II.M01 - 34
3.6. EXAMPLE OF MESSAGE

Following example is only illustrative and does not necessarily reflect an existing situation. It
MAY NEVER be used as a basis for programming or implementing this message.
UNB+UNOA:2+VG4:ZZ+ MBXNOSUPPLIER:ZZ+000615:1733+16++RECADV'
or
Chassis Mailbox ID
UNB+UNOA:2+VG5:ZZ+ MBXNOSUPPLIER:ZZ+000615:1733+16++RECADV'
Singapore Mailbox ID
UNH+1+RECADV :D:97A:UN'
BGM+632+87876788+9'
DTM+137:20001231:102'
RFF+SI:555666444'
DTM+111+20000605:102
RFF+BM:454545456'
RFF+CR:87876788'
DOC+623
NAD+MI+595172891::16'
NAD+SU+1000092::92 '
NAD+ST+ H402::92 '
CPS+1++4
LIN+++16016704:IN'
QTY+12:80000'
QTY+48:79500'
QVR+500:119'
RFF+ON:5500009999'
UNT+38+1'
UNZ+1+16'
Receipt Advice date

Supplier Advance Ship Notice Number
Supplier Advance Ship Notice Date
Bill of Lading Number
Customer Shipment Reference
Receipt Advice Document Identifier
Material issuer
Supplier Reference Number
Delphi Ship To Location
Heirarchical Shipment Package Indicator
Delphi Part Number
Advance Ship Notice Quantity
Acutal Received Quantity
Short Shipped Quantiy
Delphi Schedule Agreement Number
For ease of reading the message has been shown with each segment type on a separate line, which will not be the case
when the message is normally transmitted.
Version: 1.1 - 09/20/01
II.M01 - 35

Recadv Edi

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Recadv Edi

Загружено:

Авторское право:

Доступные форматы

EDI IMPLEMENTATION GUIDELINES FOR Delphi

EDIFACT RECADV / Receiving Advice

Delphi Version 1.1

Version: 1.1 - 09/20/01

EDI IMPLEMENTATION GUIDELINES FOR Delphi

EDIFACT RECADV / Receiving Advice

Implementation Guideline RECADV

Version: 1.1 - 09/20/01

EDI IMPLEMENTATION GUIDELINES FOR Delphi

EDIFACT RECADV / Receiving Advice

FUNCTIONAL DEFINITION ................................................................................................................ 4

Implementation Guideline RECADV

Version: 1.1 - 09/20/01

EDI IMPLEMENTATION GUIDELINES FOR Delphi

EDIFACT RECADV / Receiving Advice

2.1. FUNCTIONAL DEFINITION

Notify supplier of receipt quantity descrepancies

Implementation Guideline RECADV

Version: 1.1 - 09/20/01

EDI IMPLEMENTATION GUIDELINES FOR Delphi

EDIFACT RECADV / Receiving Advice

Implementation Guideline RECADV

Version: 1.1 - 09/20/01

EDI IMPLEMENTATION GUIDELINES FOR Delphi

EDIFACT RECADV / Receiving Advice

2.4. FIELD OF APPLICATION

BGM - BEGINNING OF MESSAGE

EDIFACT STANDARD DEFINITION

RESPONSE TYPE, CODED

Implementation Guideline RECADV

Version: 1.1 - 09/20/01

'241 = Delivery Schedule

Delphi assigned release number

Function of the message. For code

EDI IMPLEMENTATION GUIDELINES FOR Delphi

EDIFACT RECADV / Receiving Advice

status of the segment: as defined by EDIFACT and by Delphi.

number of occurrences of the segment: as defined by EDIFACT and as used by

description of the function of the segment as defined by EDIFACT and as used by

example of the segment as it may appear in an interchange. This example is only

definition of the segment content as defined by EDIFACT and as implemented by

identification of the data elements in the segment

the segment description can be followed by:

3.1.2. General remarks

Implementation Guideline RECADV

Version: 1.1 - 09/20/01

EDI IMPLEMENTATION GUIDELINES FOR Delphi

EDIFACT RECADV / Receiving Advice

3.2. SEGMENT TABLE

Segment Group1: REF-DTM

Segment Group2: DOC-SG3

Segment Group3: CDI-INP

Segment Group5: RFF-DTM

Segment Group6: CTA-COM

Segment Group7: TOD-SG8-SG9

Segment Group8: CDI-INP

Segment Group9: LOC-CDI

Segment Group10: TDT-DTM-CDI

Implementation Guideline RECADV

Version: 1.1 - 09/20/01

EDI IMPLEMENTATION GUIDELINES FOR Delphi

EDIFACT RECADV / Receiving Advice

Segment Group12: CDI-INP