Recadv Edi Doc

EDI IMPLEMENTATION GUIDELINES FOR Delphi EDIFACT RECADV / Receiving Advice

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

Delphi VegaSupplier EDI Specification

Receipt AdviceEDIFACT RECADV D97.A

Delphi Version 1.1Final



DOCUMENT CHANGE LOG

Version Date Description1.0 2001.02.08 Document issued.1.1 2001.09.20 UNB example corrected1.1 2001.09.20 RFF+VN example corrected - RFF+CR1.1 2001.09.20 QVR – Overshipped qty qualifier changed from 120 to 121



0. TABLE OF CONTENT

0. TABLE OF CONTENT............................................................................................................................. 3

1. INTRODUCTION .................................................................................................................................... 4

2. MESSAGE DEFINITION.......................................................................................................................... 4

2.1. FUNCTIONAL DEFINITION ................................................................................................................ 42.2. PRINCIPLES.................................................................................................................................... 42.3. REFERENCES................................................................................................................................. 42.4. FIELD OF APPLICATION .................................................................................................................. 6

3. MESSAGE DESCRIPTION...................................................................................................................... 6

3.1. INTRODUCTION .................................................................................................................................... 63.1.1. How to read the documentation.................................................................................................... 63.1.2. General remarks ........................................................................................................................ 7

3.2. SEGMENT TABLE............................................................................................................................ 83.3. MESSAGE STANDARD DESCRIPTION................................................................................................ 113.4. SERVICE SEGMENTS DESCRIPTION............................................................................................. 163.5. DATA SEGMENTS DESCRIPTION................................................................................................... 213.6. EXAMPLE OF MESSAGE............................................................................................................... 35



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 EDIFACTRECADV D97.A, to be used in Electronic Data Interchange (EDI) between Delphi and itsTrading Partners.

This documentation is fully comprehensive and allows the implementation of the EDIFACTRECADV 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 thebusiness needs related to the goods receipt. This message is used to report the physicalreceipt of goods. The message allows the reporting of discrepancies in products, quantities,terms, packages, etc. The message may inform about the discrepancies: - between thereceived consignment and the consignment information given in the Shipping Notificationmessage –between the received goods and the ordered goods in the ORDERS, DELFOR, orDELJIT 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 MessageRECADV as published in the UN/EDIFACT D97.A Directory.



� The agreement between the Trading Partners on the data elements to be used, theirunique definition, their representation and their values (coded or clear form) asidentified in this document.



2.4. FIELD OF APPLICATION

The following definition of a Receipt Advice Message in EDIFACT format is applicable for theinterchange of receipt advice information issued by Delphi for material deliveries to one ormore Delphi operations.

3. MESSAGE DESCRIPTION

Following pages contain a full description of the EDIFACT RECADV D97. A message asimplemented by Delphi. All segments are included regardless whether used or not used inthe interchange with Delphi. The official EDIFACT segment description is complemented withremarks pertaining to the specific requirements for an interchange with Delphi. Thoseremarks contain specific code values used, additional information on the values shown in aspecific 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. Thesegment description is to be read as follows:

� 0020 BGM - BEGINNING OF MESSAGE� Segment group: None. Level: 1.� EDIFACT status: Mandatory. Delphi status: Mandatory.� Maximum use: 1 per message. Delphi

occurrences:1 per message.

� Function: Segment for the unique identification of the delivery schedule document, by means of itsname and its number.

� Delphiinterchange:

See remarks.

� Example: BGM+241+12+5’ A B C

� EDIFACT STANDARD DEFINITION Delphi IMPLEMENTATION� REF TAG NAME ST FT SP ST FT REMARKS

C002 DOCUMENT/MESSAGE NAME C CA 1001 Document/message name, coded C an..3 : C an..3 '241’ = Delivery Schedule

� 1131 Code list qualifier C an..3 :3055 Code list responsible agency,

codedC an..3 :

1000 Document/message name C an..35 +C106 DOCUMENT/MESSAGE

IDENTIFICATIONC

B 1004 Document/message number C an..35 : C an..35 Delphi assigned release number1056 Version C an..9 :1060 Revision number C an..6 +

C 1225 MESSAGE FUNCTION, CODED C an..3 + C an..3 Function of the message. For codevalues see below.

4343 RESPONSE TYPE, CODED C an..3 ‘



� 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 situatedand 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 byDelphi.

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

� example of the segment as it may appear in an interchange. This example is onlyillustrative and does not necessarily represent an actual situation. It should NOT beused as a basis to implement this message.

� definition of the segment content as defined by EDIFACT and as implemented byDelphi.

� 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 dataelements.

� 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:

� DatesUnless otherwise specified in the field explanation in the documentation, dates arealways expressed as CCYYMMDD (qualifier 2379 = 102).

� Times

Unless otherwise specified in the field explanation in the documentation, times arealways expressed as HHMM.



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.

PosNo

SegID

NameReqDesc

Max Use GroupRepeat

Notes andComments

Must Use 0010 UNH Message Header M 1Must Use 0020 BGM Beginning of Message M 1Must Use 0030 DTM Date/Time/Period C 10

Not Used 0040 ALI Additional Information C 5

0050 Segment Group1: REF-DTM C 10

Must Use 0060 RFF Reference M 1Must Use 0070 DTM Date/Time/Period C 9

Must Use 0080 Segment Group2: DOC-SG3 C 10Must Use 0090 DOC Document/Message Details M 1

0100 Segment Group3: CDI-INP C 10Not Used 0110 CDI Physical or Logical state M 1Not Used 0120 INP Parties to Instruction C 5

Must Use 0130 Segment Group4:NAD-LOC-SG5-SG6

M 10

Must Use 0140 NAD Name and Address M 1Not Used 0150 LOC Place/Location Identification C 10

0160 Segment Group5: RFF-DTM C 10Not Used 0170 RFF Reference M 1Not Used 0180 DTM Date/Time/Period C 1

0190 Segment Group6: CTA-COM C 10Not Used 0200 CTA Contact Information MNot Used 0210 COM Communication Contact C

0220 Segment Group7: TOD-SG8-SG9 C 10Not Used 0230 TOD Terms of Delivery or Transport M 1

0240 Segment Group8: CDI-INP C 10Not Used 0250 CDI Physical or Logical State M 1Not Used 0260 INP Parties to Instruction C 5

Not Used 0270 Segment Group9: LOC-CDI C 10Not Used 0280 LOC Place/Location Identification MNot Used 0290 CDI Physical or Logical State C

Not Used 0300 Segment Group10: TDT-DTM-CDI C 10Not Used 0310 TDT Details of Transport M



Not Used 0320 DTM Date/Time/Period CNot Used 0330 CDI Physical or Logical State C

Not Used 0340SEGMENT GROUP11: EQD-SG12-SG13-SG14

C 9999

Not used 0350 EQD Equipment Details M 1

Not used 0360 Segment Group12: CDI-INP C 10Not used 0370 CDI Physical or Logical State M 1Not used 0380 INP Parties to Instruction C 5

Not used 0390 Segment Group13: SEL-CDI C 25Not used 0400 SEL Seal Number M 1Not used 0410 CDI Physical or Logical State M 10

Not used 0420 Segment Group14: EQA-SG15 C 10Not used 0430 EQA Attached Equipment M 1

Not used 0440 Segment Group15: CDI-INP 10Not used 0450 CDI Physical or Logical State M 1Not used 0460 INP Parties to Instruction C 5

Must Use 0470 Segment Group16: CPS-SG17-SG22 C 999Must Use 0480 CPS Consignment Packing Sequence M 1

Not used 0490 Segment Group17: PAC-QVR-SG18 C 9999Not used 0500 PAC Package M 1Not used 0510 QVR Quantity Variances C 1

Not used 0520SEGMENT GROUP18: PCI-RFF-SG19-SG20

C 999

Not used 0530 PCI Package Identification MNot used 0540 RFF Reference CNot used 0550 Segment Group19: CDI-INP C 10Not used 0560 CDI Physical or Logical State M 1Not used 0570 INP Parties to Instruction C 5

Not used 0580 Segment Group20: GIN-SG21 C 99Not used 0590 GIN Goods Identity Number M 1

Not used 0600 Segment Group21: CDI-INP 10Not used 0610 CDI Physical or Logical State M 1Not used 0620 INP Parties to Instruction C 5

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

C 9999

Must Use 0640 LIN Line Item M 1Not Used 0650 PIA Additional Product Id C 10Not Used 0660 IMD Item Description C 25Must Use 0670 QTY Quantity C 10Must Use 0680 QVR Quantity Variances C 10Not Used 0690 DTM Date/Time/Period C 5Not Used 0700 PRI Price Details C 1

0710 Segment Group23: CDI-INP C 10



Not Used 0720 CDI Physical or Logical State M 1Not Used 0730 INP Parties to Instruction C 5

Not Used 0740 Segment Group24: DOC-SG25 C 10Not Used 0750 DOC Document/Message Details M 1

Not Used 0760 Segment Group25: CDI-INP C 10Not Used 0770 CDI Physical or Logical state M 1Not Used 0780 INP Parties to Instruction C 5

Not Used 0790 Segment Group26: GIN-SG27 C 99Not Used 0800 GIN Goods Identity Number M 1

Not Used 0810 Segment Group27: CDI-INP C 10Not Used 0820 CDI Physical or Logical State M 1Not Used 0830 INP Parties to Instruction C 5

0840 Segment Group28: RFF-DTM C 10Must Use 0850 RFF Reference M 1Not Used 0860 DTM Date/Time/Period C 1

Not Used 0870 Segment Group29: PCI-QTY-QVR-SG30-SG31

C 9999

Not Used 0880 PCI Package Identification 1Not Used 0890 QTY Quantity 1Not Used 0900 QVR Quantity Variances 1


Not Used 0940 Segment Group31: GIN-SG32 C 10Not Used 0950 GIN Goods Identity Number M 1


Not Used 0990 CTN Control Total C 1Must Use 1000 UNT Message Trailer M 1



3.3. MESSAGE STANDARD DESCRIPTION

This section provides the description of the UN Standard Message RECADV as defined in the97.A Directory. Only the segments printed in bold are used in the subset defined by Delphiand will be further explained in section 3.6.

3.3.1 Header section

Information to be provided in the Header section:

0010 UNH, Message headerA service segment starting and uniquely identifying a message. The message type code for the ReceiptAdvice message is RECADV.

0020 BGM, Beginning of messageA segment for unique identification of the Receipt Advice message by means of its name and its numberand its function (original, replacement, and change).

0030 DTM, Date/time/periodThe DTM segment shall be used to specify the receipt advice message date.

0040 ALI, Additional informationA segment indicating that the line item is subject to special conditions due to origin, customs preference,or commercial factors.

0050 Segment group 1: RFF-DTMA group of segments giving references relevant to the whole message, e.g. contract number.

0060 RFF, ReferenceA segment for referencing documents relating to the whole receipt adive, e.g. advance ship noticenumber.

0070 DTM, Date/time/periodDate or time, or date and time of the reference. This segment will provice the date of the advance shipnotice referenced in the preceding RFF segement.

0080 Segment group 2: DOC– SG3A group of segments identifying the discrepancies with the documentary requirements relating to thewhole cosignment.

0090 DOC, Document/message detailsA segment describing the documents required for the specified consignee.

0100 Segment group 3: CDI-INPA group of segments to report the physical or logical state of the document upon receipt and to give theappropriate instructions if needed.

0110 CDI, Physical or Logical stateA segment to report the logical state of the document upon receipt

0120 INP, Parties to InstructionA segment to give instructions to correct the discrepancy reflected by the CDI segment

0130 Segment group 4: NAD-LOC-SG5-SG6A group of segments to identifying names, addresses, and locations relevant to the whole receivingadvice

0140 NAD, Name and addressA segment for identifying names and addresses and their functions relevant for the whole ReceiptAdvice. The principal parties for the Receipt Advice message shall be identified.

0150 LOC, Place/location identificationA segment identifying a specific location at the consignee address (e.g. dock, gate,) to which product, asspecified in the LIN-Segment groups, should be delivered.



0160 Segment group 5: RFF-DTMA group of segments giving references relevant to the party.

0170 RFF, ReferenceA segment giving references related to the party.

0180 DTM, Date/time/periodDate/time/period of the reference.

0190 Segment group 6: CTA-COMA group of segments to identify person, function, or department and appropriate numbers to whomcommunication should be directed.

0200 CTA, Contact informationA segment to identify the person, function, or department to whom communication should be directed.

0210 COM, Communication contactA segment identifying communication types and numbers for the person, function, or department identifiedin the CTA segment.

0220 Segment group 7: TOD-SG8-SG9A group of segments to report on discrepancies on terms of deliveries

0230 TOD, Terms of Delivery or TransportA segment to indicate the terms of delivery




0270 Segment group 9: LOC-CDIA group of segments to report discrepancy on locations related to terms of delivery

0280 LOC, Place/location identificationA segment identifying a specific location at the consignee address (e.g. dock, gate,) to which product, asspecified in the LIN-Segment groups, should be delivered.


0300 Segment group 10: TDT-DTM-CDIA group of segments specifying details of the mode and means of transport, the date or date and time ofarrival, if a discrepancy has occurred or if required by the recipient of the message for furtheridentification

0310 TDT, Details of transportA segment specifying the carriage, and the mode and means of transport.

0320 DTM, Date/time/periodA segment indicating the date/time/period details of departure or arrival relating to the TDT segment.


0340 Segment group 11: EQD-SG12-SG13-SG14A group of segments identifying equipment with which a problem has occurred or if required by therecipient of the message for further identification

0350 EQD, Equipment DetailsA segment to identify the specific equipment item.

0360 Segment group 12: CDI-INP



A group of segments to report the physical or logical state of the document upon receipt and to give theappropriate instructions if needed.



0390 Segment group 13: SEL-CDIA group of segments identifying the seal number and reporting anomalies.

0400 SEL, Seal NumberA segment specifying a seal number


0420 Segment group 14: EQA-SG15A group of segments identifying attached equipment with which a problem has ocurred or if required bythe recipient of the message for further identification

0430 EQA, Attached equipmentA segment identifying equipment attached to the equipment identified in the EQD segment.




3.3.2 Detail section

0470 Segment group 16: CPS-SG17-SG22A group of segments providing details of all packages and/or individual items as received. This segmentgroup provides the capability to give the top down hierarchical relationship of the packaging levels.

0480 CPS, Consignment Packing SequenceA segment identifying the sequence in which packing of the consignment is presented.

0490 Segment group 17: PAC-QVR-SG18A group of segments identifying packaging, quantities and maks and numbers.

0500 PAC, PackageA segment specifying the number of package units and the type of packaging for the line item, e.g. pallet.

0510 QVR, Quantity VariancesA segment identifying quantity variances between the number the number of units received and thenumber of units expected or planned.

0520 Segment group 18: PCI-RFF-SG19-SG20A group of segments identifying packaging, quantities and maks and numbers.

0530 PCI, Package identification



A segment specifying markings and labels used on individual physical units (packages) described in thePAC segment.

0540 RFF, ReferenceA segment giving references related to the party.




0580 Segment group 20: GIN-SG21A group of segments giving package identification numbers and if required the related anomalies

0590 GIN, Goods identity numberA 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-SG29A group of segments providing details of the product or services received

0640 LIN, Line ItemA segment identifying the product or service received.

0650 PIA, Additional Product IDA segment providing additional product or service identification

0660 IMD, Item DescriptionA segment describing the product or service received. This segment should be used for a product orservice that cannot be identified by a product code or article number.

0670 QTY, QuantityA segment to give quantity information about the product specified in the LIN, PIA, or IMD segment

0680 QVR, Quantity VariancesA segment identifying quantity variances between quantity per item and quantity per item expected orplanned


0700 PRI, Price DetailsA segment to provide price information related to the current line item.






0740 Segment group 24: DOC-SG25A group of segments identifying the discrepancies with the documentary requirements relating to the lineitem

0750 DOC, Document/Message DetailsA segment identifying documents where a discrepancy occurs.




0790 Segment group 26: GIN-SG27A group of segments giving goods identificaiton numbers and if required the related anomolies





0840 Segment group 28: RFF-DTMA group of segments giving references relevant to the line item.

0850 RFF, ReferenceA segment giving references related to the line item. This segment will provide the Delphi scheduleagreement number corresponding to the goods receipt.


0870 Segment group 29: PCI-QTY-QVR-SG30-SG31A group of segments identifying one specific package or a number of packages, the marks and thenumbers, quantities and receiving conditions.

0880 PCI, Package IdentificationA segment specifying markings and labels used on identified packages.

0890 QTY, QuantityA segment to give quantity information about the product specified in the LIN, PIA, or IMD segment

0900 QVR, Quantity VariancesA segment identifying quantity variances between quantity per item and quantity per item expected orplanned

0910 Segment group 30: CDI-INP



A group of segments to report the physical or logical state of the document upon receipt and to give theappropriate instructions if needed.



0940 Segment group 31: GIN-SG32A group of segments giving goods identificaiton numbers and if required the related anomolies





0990 CTN, Control TotalA segment by which control total may be provided by sender for checking by the receiver

1000 UNT, Message TrailerA service segment ending a message, giving the total number of segments in the message and the controlreference 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 thedata that is being transmitted.

The UNB (Interchange header) and UNZ (Interchange trailer) segments mark respectively thebeginning and the end of an interchange thereby providing a unique interchange controlreference.

Within the interchange the UNH (message header) and UNT (Message trailer) segmentsuniquely begin and end the various messages contained in an interchange.

UNBUNH

MESSAGE 1

UNT

UNHEXAMPLE OF ANINTERCHANGE STRUCTURE

MESSAGE 2

UNT

...

UNH



MESSAGEN

UNTUNZ



0000 UNB - INTERCHANGE HEADERSegment Group: none Level: 0EDIFACT status: mandatory Delphi status: mandatoryMaximum use: 1 per interchange Delphi occurrences: 1 per interchangeFunction 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 theinterchange control reference and the application reference.

Delphi interchange: see remarks.

Example: UNB+UNOA:2+MBXNODelphi+MBXNOSUPPLIER+970611:0735+12++RECADV’ A B C D E F G H

EDIFACT STANDARD DEFINITION Delphi IMPLEMENTATIONREF TAG NAME ST FT SP ST FT REMARKS

S001 SYNTAX IDENTIFIER M MA 0001 Syntax identifier M a4 : M a4 “UNOA”.B 0002 Syntax version number M n1 + M n1 Indication of the syntax version used for this

message.S002 INTERCHANGE SENDER M M

C 0004 Sender identification M an..35 : M an..35 Communication code/mailbox number of theparty originating the message.

0007 Identification code qualifier C an..4 :0008 Address for Reverse Routing C an..14 +S003 INTERCHANGE RECIPIENT M M

D 0010 Recipient identification M an..35 : M an..35 Communication code/mailbox number of theparty receiving the message.

0007 Identification code qualifier C an..4 :0014 Routing address C an..14 +S004 DATE / TIME OF PREPARATION M M

E 0017 Date of preparation M n6 : M n6 YYMMDD formatF 0019 Time of preparation M n4 + M n4 HHMM formatG 0020 INTERCHANGE CONTROL REFERENCE M an..14 + M an..14 The ICR number is UNIQUE within an inventory

year.S005 RECIPIENTS REFERENCE

PASSWORDC

0022 Recipient's reference / password M an..14 :0025 Recipient's reference / password

qualifierC an2 +

H 0026 APPLICATION REFERENCE C an..14 + C an..14 “RECADV ”0029 PROCESSING PRIORITY CODE C a1 +0031 ACKNOWLEDGEMENT REQUEST C n1 +0032 COMMUNICATIONS AGREEMENT ID C an..35 +0035 TEST INDICATOR C n1 ' C n1 Will be sent during testing

COMMENTS



0010 UNH - MESSAGE HEADER

Segment group: none Level: 0EDIFACT status: mandatory. Delphi status: mandatory.Maximum use: 1 per message. Delphi occurrences: 1 per message.Function: service segment starting and uniquely identifying a message. The message type code for the

Receiving Advice is RECADV.Delphi interchange: see remarks.

Example: UNH+1+RECADV:D:97A:UN’ A B C D E


A 0062 MESSAGE REFERENCE NUMBER M an..14 + M an..14 Message Control number assigned by thesender to the message. See comments below.

S009 MESSAGE IDENTIFIER M MB 0065 Message type M an..6 : M an..6 “RECADV ”.C 0052 Message version number M an..3 : M an..3 “D”.D 0054 Message release number M an..3 : M an..3 “97A”.E 0051 Controlling agency M an..2 : M an..2 “UN”.

0057 Association assigned code C an..6 +0068 COMMON ACCESS REFERENCE C an..35 +S010 STATUS OF TRANSFER C0070 Sequence of transfer M n..2 :0073 First and last transfer C a1 ‘

COMMENTS

0062 - Message Reference Number

The Message Reference number used by Delphi is structured as follows:

First message: 1Second message: 2Up to: 9999



1000 UNT - MESSAGE TRAILER

Segment group: none Level: 0EDIFACT status: mandatory Delphi status: mandatoryMaximum use: 1 per message Delphi occurrences: 1 per messageFunction: service segment ending a message, giving the total number of segments in the message and the control

reference number of the message.Delphi interchange: see remarks.

Example: UNT+99+1’ A B


A 0074 NUMBER OF SEGMENTS IN THEMESSAGE

M n..6 M n..6 Control count of the number of segments inthe message, including UNH and UNT.

B 0062 MESSAGE REFERENCE NUMBER M an..14 M an..14 Number must be identical to UNH - tag 0062

1010 UNZ - INTERCHANGE TRAILERSegment Group: none Level: 0EDIFACT status: mandatory Delphi status: mandatoryMaximum use: 1 Delphi occurrences: 1 per interchangeFunction: service segment ending an interchange and giving the number of messages contained in the interchange as

well as the Interchange Control Reference number.Delphi interchange: see remarks.

Example: UNZ+1+12’ A B


A 0036 INTERCHANGE CONTROL COUNT M n..6 + M n..6 Number of messages in an interchange.B 0020 INTERCHANGE CONTROL REFERENCE M an..14 ‘ M an..14 Value must be the same as 0020 - Interchange

Control Reference in UNB.



3.5. DATA SEGMENTS DESCRIPTION

This part includes only the segments defined in the standard and used in the subsetexchanged between Delphi and its Trading Partners. The segments are described in thesame sequence as they appear in the message.

The EDIFACT RECADV segments that are not used in the subset used by Delphi are includedin alphabetical sequence under item 3.9.

0020 BGM - BEGINNING OF MESSAGE

Segment group: none Level: 1EDIFACT status: mandatory Delphi status: mandatoryMaximum use: 1 per message Delphi occurrences: 1 per messageFunction: segment for the unique identification of the delivery schedule document, by means of its name and its

number.Delphi interchange: see remarks.

Example: BGM+632+23445566+9’ A B C


C002 DOCUMENT/MESSAGE NAME C CA 1001 Document/message name, coded C an..3 : M an..3 “632” = Goods Receipt. Document/message

issued by a port, warehouse/shed, or terminaloperator acknowledging receipt of goodsspecified therein on conditions stated orreferred to in the document

1131 Code list qualifier C an..3 :3055 Code list responsible agency, coded C an..3 :1000 Document/message name C an..35 +C106 DOCUMENT/MESSAGE

IDENTIFICATIONC

B 1004 Document/message number C an..35 : M an..35 Reference number assigned to thedocument/message by the issuer. Referenceidentification number unique for a calendaryear.

1056 Version C an..9 :1060 Revision number C an..6 +

C 1225 MESSAGE FUNCTION, CODED C an..3 + M an..3 “9” = Original Receipt AdviceCode indicating function of the message.

4343 RESPONSE TYPE, CODED C an..3 ‘

CODE VALUES

1001 – Document/Message name, coded

632 Goods Receipt

1225 - Message Function, coded

9 Original Receipt Advice



0030 DTM - DATE/TIME/PERIOD

Segment group: none Level: 1EDIFACT status: mandatory Delphi status: mandatoryMaximum use: 10 per message at level 1 Delphi occurrences: max. 3 per messageFunction: 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 Scheduledocument 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 B C


Receipt Advice Document Date

C507 DATE/TIME/PERIOD M MA 2005 Date/time/period qualifier M an..3 : M an..3 “137” = Document date.B 2380 Date/time/period C an..35 : M an..35 Receipt Advice DateC 2379 Date/time/period format qualifier C an..3 ‘ M an..3 “102” = CCYYMMDD.

CODE VALUES

2005 – Date/Time/Period Qualifier

137 Document Date



Segment group 1: RFF-DTM

Segment group: 1 [RFF-DTM] Level: 1EDIFACT status: Conditional Delphi status: CconditionalMaximum use: 10 per message Delphi occurrences: 3 per messageFunction: group of segments giving references related to the line item and where necessary, their dates.Delphi interchange: see segment description.

0060 RFF - REFERENCE

Segment group: 1 [RFF-DTM] Level: 1EDIFACT status: mandatory if segment group 1 is used Delphi status: mandatoryMaximum use: 1 per segment group 1 Delphi occurrences: 1 per segment group 1Function: segment for identifying documents relating to the line item, e.g. a contract and its appropriate line

item.Delphi interchange: see remarks.Example: RFF+SI:A1A2A3A4A’

RFF+BM:456456’RFF+CR:18000999’ A B


C506 REFERENCE M MA 1153 Reference qualifier M an..3 : M an..3 “SI”=Shipper Identification Number. Code

giving specific meaning to a referencenumber.

B 1154 Reference number C an..35 : C an..35 Reference identification number1156 Line number C an..6 :4000 Reference version number C an..35 ‘


C506 REFERENCE M MA 1153 Reference qualifier M an..3 : M an..3 “BM”=Bill of Lading Number. Code giving

specific meaning to a reference number.B 1154 Reference number C an..35 : C an..35 Reference identification number

1156 Line number C an..6 :4000 Reference version number C an..35 ‘


C506 REFERENCE M MA 1153 Reference qualifier M an..3 : M an..3 “CR”= Delphi Delivery Number. Code giving

specific meaning to a reference number.B 1154 Reference number C an..35 : C an..35 Reference identification number. Delphi

internal reference to the shipment.1156 Line number C an..6 :4000 Reference version number C an..35 ‘

CODE VALUES



1153 - Communication number, qualifier

SI Shipper’s Identification NumberBM Bill of Lading NumberCR Customer Reference Number



0700 DTM - DATE/TIME/PERIOD

Segment group: 1 [RFF-DTM] Level: 1EDIFACT status: Conditional Delphi status: ConditionalMaximum use: 1 per segment group 1 Delphi occurrences: 1 per segment group 1Function: 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 B C


Document generation date.

C507 DATE/TIME/PERIOD M MA 2005 Date/time/period qualifier M an..3 : M an..3 “111” = Manifest / Ship Notice DateB 2380 Date/time/period C an..35 : M an..35 Actual Ship Notice DateC 2379 Date/time/period format qualifier C an..3 “ M an..3 “102” = CCYYMMDD.

CODE VALUES

2005 – Date/Time/Period Qualifier

111 Manifest / Ship Notice Date



Segment group 2: DOC-SG3

Segment group: 2 [DOC-SG3] Level: 1EDIFACT status: Conditional Delphi status: ConditionalMaximum use: 10 per message Delphi occurrences: 1 per messageFunction: 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: 1EDIFACT status: mandatory if segment group 2 is used Delphi status: mandatoryMaximum use: 1 per segment group 2 Delphi occurrences: 1 per segment group 2Function: segment describing the documents required for the specified consigneeDelphi interchange: see remarks.

Example: DOC+632’ A


A C002 DOCUMENT/MESSAGE NAME M1001 Document/Message name, coded C an..3 : C an..3 “632” = Goods Receipt

Identification of the type of document/messageby code or name.

1131 Code list qualifier C an..3 :3055 Code list responsible agency coded C an..3 :1000 Document/Message name C an..35 +C503 DOCUMENT/MESSAGE DETAILS1004 Document/message number an..35 :1373 Document/message status, coded an..3 :1366 Document/message source an..35 :3453 Language, coded an..3 +3153 Communication channel identifier an..3 +1220 Number of copies of document

requiredn..2 +

1218 Number of originals of documentrequired

n..2 ‘

CODE VALUES

1001 – Document/Message Name, coded

632 Goods Receipt



Segment group 4: NAD-LOC-SG5-SG6

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

0130 NAD - NAME AND ADDRESSSegment group: 4 [NAD-LOC-SG5-SG6] Level: 1EDIFACT status: mandatory Delphi status: mandatoryMaximum use: 1 per segment group 4 Delphi occurrences: 1 per segment group 4Function: segment for identifying names and addresses and their functions relevant to the receipt adviceDelphi interchange: see remarks.

Example: NAD+SU+2223412::16’

NAD+MI+102356::92’

NAD+ST+1998877::92’ A B C


A 3035 PARTY QUALIFIER M an..3 + M an..3 “SU” = SupplierC082 PARTY IDENTIFICATION DETAILS C M

B 3039 Party id. Identification M an..35 : M an..35 Code identifying the supplier1131 Code list qualifier C an..3 :

C 3055 Code list responsible agency, coded C an..3 + M an..3 For code value see below.C058 NAME AND ADDRESS C3124 Name and address line M an..35 :3124 Name and address line C an..35 +C080 PARTY NAME C3036 Party name M an..35 :3036 Party name C an..35 :3036 Party name C an..35 :3045 Party name format, coded C an..3 +C059 STREET C3042 Street and number/P.O.. box M an..35 :3042 Street and number/P.O.. box C an..35 +3164 CITY NAME C an..35 +3229 COUNTRY SUB-ENTITY

IDENTIFICATIONC an..9 +

3251 POSTCODE IDENTIFICATION C an..9 +3207 COUNTRY, CODED C an..3 “

CODE VALUES

3035 – Party Qualifier

SU Supplier

3055 - Code List Responsible Agency, coded



16 DUN & Bradstreet (DUNS)92 Assigned by buyer

0130 NAD - CONTINUED

Material Release Issuer

A 3035 PARTY QUALIFIER M an..3 + M An..3 “MI” = Planning schedule/material releaseissuer.

C082 PARTY IDENTIFICATION DETAILS C MB 3039 Party id. Identification M an..35 : M an..35 Code identifying the issuer.

1131 Code list qualifier C an..3 :C 3055 Code list responsible agency, coded C an..3 + M an..3 For code value see below.

C058 NAME AND ADDRESS CC080 PARTY NAME C3036 Party name M an..35 :

REST OF SEGMENT NOT USED.

Ship To

A 3035 PARTY QUALIFIER M an..3 + M an..3 “ST” = Ship ToC082 PARTY IDENTIFICATION DETAILS C M

B 3039 Party id. Identification M an..35 : M an..35 Code identifying the ship from location.1131 Code list qualifier C an..3 :

C 3055 Code list responsible agency, coded C an..3 + M an..3 For code value see below.C058 NAME AND ADDRESS CC080 PARTY NAME C3036 Party name M an..35 :

REST OF SEGMENT NOT USED.

CODE VALUES

3035 – Party Qualifier

MI Planning Schedule/Material Release IssuerST Ship To

3055 - Code List Responsible Agency, coded

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



Segment group 16: CPS-SG17-SG22

Segment group: 16 [CPS-SG17-SG22] Level: 1EDIFACT status: mandatory Delphi status: mandatoryMaximum use: 9999 Delphi occurrences: 9999Function: 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 packagelevels.

Delphi interchange: see segment description.

0480 CPS – CONSIGNMENT PACKING SEQUENCE

Segment group: 16 [CPS-SG17-SG22] Level: 1EDIFACT status: mandatory Delphi status: mandatoryMaximum use: 1 per segment group 16 Delphi occurrences: 1 per segment group 16Function: segment identifying the sequence in which packing of the consignment is presentedDelphi interchange: see remarks

Example: CPS+1++4’ A B


A 7164 Hierarchical id number M an..12 : M an..12 A unique number assigned by the sender toidentify within a hierarchical structure. Beginswith the number 1 and increments by one foreach occurrence within the message.Hierarchical id numbers are not to be repeatedwithin the same message.

7166 Hierarchical parent id C an..12 :B 7075 Packaging level C an..3 “ C an..3 “4”= No packaging hierarchy. There is no

specfiable leel of packaging: packaging isinner and outer level as well.

CODE VALUES

7075 – Packaging Level

4 No Packaging Hierarchy



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

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

0640 LIN - LINE ITEM

Segment group: 22 [LIN-PIA-IMD-QTY-QVR-DTM-PRI] Level: 2EDIFACT status: mandatory Delphi status: mandatoryMaximum use: 1 per segment group 22 Delphi occurrences: 1 per segment group 22Function: 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.Delphi interchange: see remarks.

Example: LIN+++12345678:IN’ A B


1082 LINE ITEM NUMBER C n..6 +1229 ACTION REQUEST/ NOTIFICATION,

CODEDC an..3 +

C212 ITEM NUMBER IDENTIFICATION C MA 7140 Item number C an..35 : M an..35 Delphi assigned part number.B 7143 Item number type, coded C an..3 : M an..3 “IN” = Buyer’s item number.

1131 Code list qualifier C an..3 :3055 Code list responsible agency, coded C an..3 +C829 SUB-LINE INFORMATION C5495 Sub-line indicator, coded C an..3 :1082 Line item number C an..6 +1222 CONFIGURATION LEVEL C n..2 +7083 CONFIGURATION, CODED C an..3 ‘

CODE VALUES

7143 – Item number type, coded

IN Buyer’s Item Number



0670 QTY - QUANTITY

Segment group: 22 [LIN-PIA-IMD-QTY-QVR-DTM-PRI] Level: 3EDIFACT status: Conditional Delphi status: mandatoryMaximum use: 10 per segment group 22 Delphi occurrences: 3 per segment group 22Function: segment to give quantity information about the product specified in the LIN, PIA, or IMD segment.Delphi interchange: see remarks.

Example: QTY+12:9999’

QTY+48:9999’ A B


C186 QUANTITY DETAILS M MA 6063 Quantity qualifier M an..3 : M an..3 “12” = Dispatch Quantity.B 6060 Quantity M n..15 : M n..15 Advance Ship Notice Quantity

6411 Measure unit qualifier C an..3 ‘


C186 QUANTITY DETAILS M MA 6063 Quantity qualifier M an..3 : M an..3 “48” = Received QuantityB 6060 Quantity M n..15 : M n..15 Quantity which has been receivedC 6411 Measure unit qualifier C an..3 ‘

CODE VALUES

6063 – Quantity Qualifier

12 Dispatch Quantity48 Received Quantity



0680 QVR – QUANTITY VARIANCES

Segment group: 22 [LIN-PIA-IMD-QTY-QVR-DTM-PRI] Level: 3EDIFACT status: Conditional Delphi status: mandatoryMaximum use: 10 per segment group 22 Delphi occurrences: 1 per segment group 22Function: 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 B


C279 QUANTITY DIFFERENTINFORMATION

C M

A 6064 Quantity difference M n..15 : M n..15 Short shipped descrepancy quantiy6063 Quantity qualifier C an..3 + C an..3 “119” = Short Shipped. The descrepancy

quantity received is below the ship notificationquantity.

4221 Descrepancy, coded C an..3 +C960 REASON FOR CHANGE C4295 Change reason C an..3 :1131 Code list qualifier C an..3 :3055 Code list responsible agency C an..3 :4294 Change reason C an..35 ‘


C279 QUANTITY DIFFERENTINFORMATION

C M

A 6064 Quantity difference M n..15 : M n..15 Over shipped descrepancy quantiy6063 Quantity qualifier C an..3 + C an..3 “121” = Over Shipped. The descrepancy

quantity received is over the ship notificationquantity.



4221 Descrepancy, coded C an..3 +C960 REASON FOR CHANGE C4295 Change reason C an..3 :1131 Code list qualifier C an..3 :3055 Code list responsible agency C an..3 :4294 Change reason C an..35 ‘

CODE VALUES

6063 – Quantity Qualifier

119 Short Shipped121 Over Shipped

Segment group 28: RFF-DTM

Segment group: 28 [RFF-DTM] Level: 3EDIFACT status: conditional Delphi status: mandatoryMaximum use: 10 per segment group 22 Delphi occurrences: 1 per segment group 22Function: group of segments giving references related to the line item and where necessary, their dates.Delphi interchange: see segment description.

0850 RFF - REFERENCE

Segment group: 28 [RFF-DTM] Level: 1EDIFACT status: mandatory Delphi status: mandatoryMaximum use: 1 per segment group 28 Delphi occurrences: 1 per segment group 28Function: segment for identifying documents relating to the line item, e.g. schedule agreement numberDelphi interchange: see remarks.Example: RFF+ON:55000099’

A B


C506 REFERENCE M MA 1153 Reference qualifier M an..3 : M an..3 “ON”=Order number.B 1154 Reference number C an..35 : C an..35 Delphi Schedule Agreement Number

1156 Line number C an..6 :4000 Reference version number C an..35 ‘

CODE VALUES



1153 - Communication number, qualifier

ON Order Number



3.6. EXAMPLE OF MESSAGE

Following example is only illustrative and does not necessarily reflect an existing situation. ItMAY NEVER be used as a basis for programming or implementing this message.

UNB+UNOA:2+VG4:ZZ+ MBXNOSUPPLIER:ZZ+000615:1733+16++RECADV' Chassis Mailbox IDor

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' Receipt Advice dateRFF+SI:555666444' Supplier Advance Ship Notice NumberDTM+111+20000605:102’ Supplier Advance Ship Notice DateRFF+BM:454545456' Bill of Lading NumberRFF+CR:87876788' Customer Shipment ReferenceDOC+623’ Receipt Advice Document IdentifierNAD+MI+595172891::16' Material issuerNAD+SU+1000092::92 ' Supplier Reference NumberNAD+ST+ H402::92 ' Delphi Ship To LocationCPS+1++4’ Heirarchical Shipment Package IndicatorLIN+++16016704:IN' Delphi Part NumberQTY+12:80000' Advance Ship Notice QuantityQTY+48:79500' Acutal Received QuantityQVR+500:119' Short Shipped QuantiyRFF+ON:5500009999' Delphi Schedule Agreement NumberUNT+38+1'UNZ+1+16'

For ease of reading the message has been shown with each segment type on a separate line, which will not be the casewhen the message is normally transmitted.

Recadv Edi Doc

Documents

delphi edifact recadv

message description

example of message

adelphi version

message standard description

message definition

service segments description

data segments description