DESADV spec 1.4 - iconnect-corp.com... desadv spec 1.4.doc Date created : 12-09-02 14:10 Status :...

DESADVEDIFACT MESSAGE.

This document contains the use of the Edifact message“DESADV”. This message sent by seller will inform receiver aboutgoods despatched.

Document : desadv spec 1.4.doc

Date created : 12-09-02 14:10

Status : Definitive

Date printed : 13 September, 2002

EDIFACT July 1999Definition of DESADV-message Version 1.4

DESADV of 46

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

1.1 PREFACE ..................................................................................................................................... 4

1.2 EXPLANATION OF MESSAGE-DEFINITION .................................................................................... 5

2. DESADV MESSAGE-DEFINITION .......................................................................................... 7

2.1 GENERAL COMMENTS ................................................................................................................. 7

2.2 INTERPRETATION ISSUES DESADV-MESSAGE ............................................................................ 7

2.3 EXAMPLE OF HOW TO USE PACKAGING INFORMATION................................................................. 8

2.4 MAIN DIFFERENCES DESADV VERSUS AVIEXP-MESSAGE ..................................................... 10

2.5 UNH “OF MESSAGE” POSITION: 0/-/1 ...................................................................................... 12

2.6 BGM “OF MESSAGE” POSITION: 1/-/2 ...................................................................................... 13

2.7 DTM “OF MESSAGE CREATED” POSITION: 1/-/3....................................................................... 14

2.8 MEA "OF SHIPMENT" (GROSS WEIGHT) POSITION: 1/-/5 .......................................................... 15

2.9 MEA "OF SHIPMENT" (VOLUME) POSITION: 1/-/5.................................................................... 16

2.10 NAD “OF CARRIER” POSITION: 1/2/9 .................................................................................. 17

2.11 NAD “OF CONSIGNEE” POSITION: 1/2/9.............................................................................. 18

2.11.1 LOC “of destination of consignee” Position: 2/2/10 ..................................................... 19

2.12 NAD “OF CONSIGNOR” POSITION: 1/2/9 ............................................................................. 20

2.13 NAD “OF SELLER” POSITION: 1/2/9 .................................................................................... 21

2.14 TDT "OF DESPATCH" POSITION: 1/6/18 ............................................................................. 22

2.15 CPS "OF DESPATCH OF INNER PACK." POSITION: 1/10/28..................................................... 23

2.15.1 PAC "of consignment" Position: 2/11/30 ................................................................... 24

2.15.1.1 MEA "of package of consignment" Position: 3/11/31 ........................................................ 25

2.15.1.2 QTY "of package of consignment" Position: 3/11/32 ..................................................... 26

2.15.1.3 PCI "of package of consignment " Position: 3/13/35 .......................................................... 27

2.15.1.3.1 RFF "of Package id. of pack. of cons." Position: 4/13/36 .............................................. 28

2.15.1.3.2 GIR "of Package id. of package of consignment" Position: 4/13/38 ................................ 29

2.15.1.3.3 GIN "of package id. of package of consignment " Position: 4/13/39 ............................... 30

2.15.2 LIN "of consignment" Position: 2/15/41 ....................................................................... 31

2.15.2.1 MEA "of shipment" (net weight) Position: 3/15/44 ........................................................... 32

2.15.2.2 QTY "of article of consignment" Position: 3/15/45 ........................................................ 33

2.15.2.3 RFF "of article of cons." (order) Position: 3/16/53 ............................................................. 34

2.15.2.4 RFF "of article of. cons." (Del. schedule Nr.) Position: 3/16/53......................................... 35

2.15.2.5 RFF "of article of. cons." (Part con. NR.) Position: 3/16/53 ............................................... 36

2.15.2.6 LOC "of article of consignment" Position: 3/18/58 ........................................................... 37

2.16 CPS "OF DESPATCH OF HANDLING UNITS" POSITION: 1/10/28.............................................. 38


DESADV of 46

2.16.1 PAC "of despatch of handling units" Position: 2/11/30 ................................................ 39

2.17 UNT “OF MESSAGE” POSITION: 0/-/76 .......................................................................... 40

3. PROCEDURE OF IMPLEMENTATION................................................................................ 41

4. EXAMPLE OF DESADV-MESSAGE...................................................................................... 43

5. OVERVIEW OF ATTACHMENTS ......................................................................................... 46

5.1 MESSAGE BRANCHING DIAGRAM AS USED BY DAF.................................................................. 46


DESADV of 46

1. Introduction

1.1 PrefaceAll electronic communication between DAF and suppliers is based on thestandards of Odette. Begin 1997 the decision was taken to change to theEdifact standards. This decision was taken because:

• Odette will no longer be supported in the new century,

• Problems might occur because Odette doesn’t support century 2000.

All current suppliers of DAF using Odette, will be contacted to migrate toEdifact. By the end of 1998, DAF will no longer support Odette-messages.

This document informs you how the migration to Edifact will take place. Weadvise you to read this document carefully. In this document DAF will explainhow the DESADV-message will be processed and how the migration will takeplace.

In case you have a problem or question, please contact:

DAF TRUCKS N.V.

ATT. Paul Jacobs or John de KleijnPostbox 900655600 PT EindhovenHollandTel. 040-2143816 / 2142618

We hope that the migration to Edifact will be well prepared by your people inorder not to disturb the production process. In advance, we thank you for yourco-operation.

P. JacobsEDI-managerDAF-Trucks n.v.


DESADV of 46

1.2 Explanation of Message-definitionIn this paragraph some information can be found how the segments aredescribed. In the contents you can find all segments and their sequence inwhich they will appear in the DESADV-message. In attachment 5.1 you canfind a branching diagram of all segments used by DAF. Every segment will bedescribed in detail in the according paragraph. The codes used have thefollowing meaning:

Explanation of the paragraph:

X.X YYY “description of segment” Position: A/B/C

X.XParagraph number indicating the sequence position and level of the segmentin the message.

YYYSegment identification.

“description of segment”Description what information can be found in the segment at that specificposition within the message.

Position: A/B/CA: Indicates the level of the segment at that specific position within message.

B: Indicates the group where segment is part of that position withinmessage.

C: Indicates the sequence position of the segment within the message.

Explanation of the first part of the table:

YYY M 1/3 Description

Explanation what global information can be found within this segment (Edifactdefinition).

Explanation how DAF will process this segment at this position.


DESADV of 46

YYYSegment identification.

MDefines if DAF always M(andatory) or only if available O(ptional) expects thissegment. Value R(equired) is used in case of an optional segment that willalways be expected.

1/3Indicates the occurrences that might occur of this segment at this position.Example; this segment can occur 1, 2 or 3 times.

DescriptionDescription of the segment.

Explanation of the second part of the table:

For every data element DAF might use, besides the official description, anextra line is added how DAF will use the specific data element to receive datafrom suppliers:

Elm. DESCRIPTION EXPLANATION

C002 Edifact definition ofcomposite dataelement.

M Edifact description of composite dataelement.

2005 Edifact definition ofdata element

An..3 M Edifact description of use of dataelement

DAF Internal (DAF)explanation of dataelements used. Usedfor programmingpurposes.

M Explanation for suppliers how DAF willuse the specific data element an whatvalues can be expected.

Explanationimportant forSupplier.


DESADV of 46

2. DESADV Message-definition

2.1 General commentsThis specification is based on Odette release V5R1 (D96A) and provides thedefinition of the despatch advise message “DESADV” to be used in ElectronicData Interchange (EDI) between trading partners involved in administration,commerce and transport. Within this chapter DAF will define in detail how themessage needs to be filled.

All segments at this moment used by DAF are described according thephysical sequence in which they are processed by DAF. The EDIFACT rulesare applicable to the complete DESADV-message.

DAF will reserve the right to add segments or to fill additional fields in existingsegments in case this might improve the data exchange with suppliers.EDIFACT/ODETTE rules will also be applicable to these modifications.Suppliers will be informed in advance of all future modifications.

2.2 Interpretation issues DESADV-messageIn order to interpret the DESADV-message as used by DAF correctly, pleasetake notice of the following remarks:

• Essential for DAF is to receive a NEW DESADV-message for every otherlocation as mentioned in the LOC-segment with qualifier ‘11’ (Place/portof destination). Every message must contain a unique identification of thedespatch document (Tag 1004 in the BGM-segment). In case of despatchnumbers per article, the ‘Ladebezugsnummer’ must be filled here.

• In case sender uses ONE despatch document per article, Despatchnumber (Lieferscheinnummer) must be filled in RFF-segment for everyarticle with qualifier ‘AAN’ (position 3/15/53).

• If DAF receives more information as defined here, (more segments, moretags or longer tags as DAF-format) this data will NOT be processed.

• DAF expects for EVERY article a new group 10 (starting with the CPS-segment). Within this group different groups of packaging info can beprocessed (Group 11). Only one group 15, starting with the LIN-segmentcan be processed.


DESADV of 46

2.3 Example of how to use packaging informationBelow an example can be found concerning the information about packagingand what segments DAF expects.

General remarks

1. a handling unit type has one code for the complete unit (i.e. H3 = 1 pallet60*80 +3 collars +1 lid)

2. unique identification (licence plate) per handling unit (outer unit)

3. in case of a mixed pallet DAF requires an identification of the handling unitfor every other article on a handling unit (A RFF-segment containing theidentification of the handling unit).

4. GIN-segment alsways contains detailed package id’s.In case of ‘S’ labels: Id. of handling unit;In case of ‘M’ or ‘G’ labels: Optional.

Reference to Odette-Edifact documentation:

AVIEXP/DESADV V5R1 (based on D96A) october 1996 - part 3 examples :

• Packaging of the article: case 3

• Handling unit description: case 3

• Package content: case 1

Example:

Despatch contains: (see also picture)

• Article 1234567 : 2 handling units type H3 with 100 pcs per unit (transport labelnumbers: T111 and T112) , 1 handling unit type H2 with 60 pcs (transport label numberT113)

• Article 1231234: 1 handling unit type HP (transport label number T114) with 2 partpackages: 1 package K4 with 100 pcs and 1 package K3 with 60 pcs

• Article 9999999 : 1 handling unit type R1 (transport label number T115) with partpackages: 30 boxes D1 à 100 pcs ; 5 boxes D1 à 100 pcs on a ‘mixed pallet’ type H1(transport label number T116)

• Article 9876543: 10 boxes D2 à 50 pcs on ‘mixed pallet’ type H1 (transport label numberT116)


DESADV of 46

1234567

H3

100 pcs 123456760 pcs

H2H3

1234567

100 pcs

K3

R1 H1

30 boxes D1 a 100 pcs 99999995 boxes D1 a 100 pcs 9999999

10 boxes D2 a 50 pcs 9876543

T115 T116

T111 T112 T113

HP

K41231234 100 pcs 1231234

60 pcs

T114

‘mixed pallet’

Corresponding message structure:

CPS(1) “1” (Package of first article)PAC ‘H3’, 2

QTY 100PCI ‘S’ (Handling unit without part package)

GIN “T111” Identification of handling unit.GIN “T112” Identification of handling unit.

PAC ‘H2’, 1QTY 60PCI ‘S’ (Handling unit without part package)

GIN “T113” Identification of handling unit.LIN “1234567” (article number)

QTY 260 (2*100 + 1*60)CPS(2) “1” (Package of second article)

PAC ‘K4’, 1QTY “100”PCI “M” (Handl. unit with part pack. of same article)

RFF “T114” Identification of handling unit.GIN (Optional detailed package info).

PAC ‘K3’, 1QTY “60”PCI ‘M’ (Handl. unit with part pack. of same article)

RFF “T114” Identification of handling unit. GIN (Optional detailed package info).

LIN “1231234” (article number)


DESADV of 46

QTY 160 (1*100 + 1*60)CPS(3) “1” (Package of third article)

PAC ‘D1’, “30”QTY “100”PCI “M” (Handl. unit with part pack. of same article)


PAC ‘D1’, ‘5’QTY “100”PCI ‘G’ (Handl. unit with part pack. of different articles)


LIN “9999999” (article number)QTY 3500 (30*100 + 5*100)

CPS(4) “1” (Package of fourth article)PAC ‘D2’, “10”

QTY “50”PCI “G” (part package on different handling units)


LIN “9876543” (article number)QTY 500 (10*50)

CPS(5) “3” (Handling unit info)PAC ‘H3’, “2”PAC ‘H2’, “1”PAC ‘HP’, “1”PAC ‘R1’, “1”PAC ‘H1’, “1”

2.4 Main differences DESADV versus AVIEXP-messageSome differences between the DESADV-message and the AVIEXP-messagemight result in a different interpretation of the message. Please take notice ofthese main differences;

1. Values in the two LOC-segments of the related DELFOR-message,(destination and additional destination) are exchanged. In the first LOC-segment DAF fills an identification of the warehouse (e.g. 2MC, ODC etc.).For every other warehouse, DAF requires a new DESADV-message. In


DESADV of 46

the second LOC-segment additional info like building and gate will befilled.


DESADV of 46

2.5 UNH “of message” Position: 0/-/1UNH M 1/1 Message Header

Service segment starting and uniquely identifying a message.

Requires ONE UNH-segment.Additionally, a SEPARATE message must be created for every destination as definedin the LOC-segment with qualifier ‘11’ (Place/port of discharge).Conclusion: Another place/port of discharge results in a new DESADV-message witha unique despatch number in the BGM-segment.


0062 MESSAGE REF.NUMBER

An..14 M Message reference number

DAF EDIMRE An..14-

M A unique session number for message.

S009 MESSAGEIDENTIFIER

M Identifier of message

0065 Message Type An..6 M Type of message

DAF EDIMTYODTMESNAM

An..6 M Value ‘DESADV’

0052 Message versionnumber

An..3 M Version number

DAF EDIMVN An..3 M Value “D”

0054 Message releasenumber

An..3 M Release number

DAF EDIMRN An..3 M Value “96A”

0051 Controlling agency An..2 M Controlling agency

DAF EDICOA An..2 M Value “UN”

0057 Associated assignedcode

An..6 C

DAF EDIAAC An..6 C Value “A01051”


DESADV of 46

2.6 BGM “of message” Position: 1/-/2BGM M 1/1 Beginning of message

A segment for the unique identification of the delivery schedule document by meansof its name and its number. To indicate the type and function of a message and totransmit the identifying number.

Requires ONE BGM-segment.Processes 1/1 BGM-segment.


C002 DOC. MESS. NAME C Id. of a type of doc. by code or name.

1001 Doc./mess.name,coded An..3 C Type of message

DAF EDIDMC R Value ‘351’ (Despatch advice)

1004

DAF

DOCUMENT NUMBER

EDIDNU

MESNUM

TPTDOKIDE

An..35

An..17

An..17

CR

Reference number document.The unique identification of the despatchdocument. This identification must beunique within one year.

This is an essential identification forDAF. For every other destination, DAFrequires a separate despatch document.

This number will be used by DAF toinform the seller about the last twodespatches received (Identification ofdespatch document).

>>>In case seller sends a unique"despatch number on article level"("Lieferscheinnummer"), this number willbe used instead of this DocumentMessage number. This "despatchnumberon article level" must be send in the RFF-segment with qualifier 'AAN' in group 16,below the LIN-segment. In this case aunique "Ladungsbezugnummer" must befilled here.


DESADV of 46

2.7 DTM “of message created” Position: 1/-/3DTM R 1/1 Date/time/period

A segment specifying the date, and when relevant, the time/period of the beginningand ending of the validity period of the document. The DTM must be specified at leastonce to identify the delivery schedule document date.

Requires ONE DTM-segment with the Despatch Advice Date.

Processes 1/1 DTM-segment.


C507 DATE/TIME/PERIOD M Date and/or time or period relevant tothe specified date/time/period

2005 Date/time/periodqualifier

An..3 M Code giving specific meaning to a date,time or period.

DAF EDIDTQ M Value 137’ (Document/messagedate/time)

2380 Date/time/period An..35 C The value of a date, a date and time atime or of a period in a specifiedrepresentation.

DAF EDIDTPMESJMD+MESONTUMT

R Despatch Advice date and timeDESADV-message is created.

Date will be used to inform supplier inDELFOR-message about previousdespatches.

2379 Date/time/period formatqualifier

An..3 C Specification of the representation of adate, a date and time or of a period.

DAF EDIDFQ R Value “203” (represents:CCYYMMDDHHMM)


DESADV of 46

2.8 MEA "of shipment" (gross weight) Position: 1/-/5MEA C 0/2 Measurements (of shipment)

A segment specifying physical measurements of the packages/physical unitsdescribed in the PAC segment.

Expects gross weight (AAD) and Volume (ABJ) of despatch.

Processes 0/2 MEA-segments.


6311 MEASUREMENTAPPLICATIONQUALIFIER

An..3 M Specification of the application of thephysical measurement used.

DAF EDIMAQ M AAX (Consignment measurement)

C502 MEASUREMENTDETAILS

C Identification of measurement type

6313 Measurementdimensions coded.

An..3 M Specification of the type of dimension tobe measured

DAF EDIMDC M AAD (Total gross weight)

C174 VALUE/RANGE C Measurement value and relevantminimum and maximum tolerances inthat order

6411 Measure unit qualifier An..3 M If not filled DAF will use followingdefaults:

DAF EDIMUQ

ZNDGEWBRTENH

C KGM (qualifier in case of weight)

6314 Measurement value N..18 C Gross weight and/or volume of shipmentmust be entered here.

DAF EDIMEV

ZNDGEWBRT N..7

R Gross weight of shipment


DESADV of 46

2.9 MEA "of shipment" (Volume) Position: 1/-/5MEA C 0/2 Measurements (of shipment)


Requires gross weight (AAD) and Volume (ABJ) of despatch.

Processes 0/2 MEA-segments.




DAF EDIMAQ M AAX (Consignment measurement)





DAF EDIMDC M ABJ (Volume)



DAF EDIMUQ

ZNDVOLENH

C MTQ (qualifier in case of volume)


DAF EDIMEV

ZNDVOL N..9

R volume of shipment


DESADV of 46

2.10 NAD “of carrier” Position: 1/2/9NAD R 2/4 Name and address (of carrier)

A segment for identifying names, addresses, and their functions relevant to the wholeDespatch Advice. Identification of the parties involved is recommended for theDespatch Advice message, and is to be given in the NAD segment. It isrecommended that where possible, only the coded form of the party-ID should bespecified, e.g. the buyer and seller are known to each other, thus only the coded ID isrequired.

Requires Group of NAD of Seller (SE) and NAD of Consignee (CN).Group of NAD of Carrier (CA) and Consignor (CZ) are optional.Processes 2/4 Groups of NAD-segments.


3035 PARTY QUALIFIER An..3 M Code giving specific meaning to a party.

DAF EDIPAQ M Default value “CA” (carrier)

C082 PARTY ID. DETAILS C Id. of a transaction party by code

3039 Party id. identification An..35 M Code identifying a party involved in atransaction. User or association definedcode. May be used in combination with1131/3055.

DAF EDIPAI

LVCNUMTPT An..5

M Fill identification of Carrier.

3055 Code list responsibleagency, coded

An..3 C Code identifying the agency responsiblefor a code list.

DAF EDICAC R Value “92” (Assigned by buyer or buyer’sagent)

C058 NAME AND ADDRESS C Unstructured name and address: oneto five line.

3124 Name and address line An..35 M Free form name and address description

DAF EDINAL

TPTBDF An..13

M Name of Carrier


DESADV of 46

2.11 NAD “of consignee” Position: 1/2/9NAD R 2/4 Name and address (of consignee)





DAF EDIPAQ M Default value “CN” (consignee)

C082 PARTYIDENTIFICATIONDETAILS

C Identification of a transaction party bycode


DAF EDIPAI

VTGKOD An..1

M Fill DAF-identification of Consignee. Forexample: ‘E’ = Eindhoven, ‘W’ =Westerlo, ‘P’ = Parts.





DESADV of 46

2.11.1 LOC “of destination of consignee” Position: 2/2/10LOC R 1/1 Place/location identification

A segment indicating more details regarding specific places/locations related to theparty specified in the NAD segment, e.g. internal site/building number.

Required only in combination with NAD-segment of consignee (CN).

For every OTHER destination, DAF REQUIRES another message!

Processes 1/1 LOC-segments.


3227 PLACE/LOCATIONQUALIFIER

An..3 M Code identifying the function of alocation.

DAF EDIPDQ M Value “11” (Place/port of discharge)

C517 LOCATIONIDENTIFICATION

C Identification of a location

3225 Place/locationidentification

An..25 C

DAF EDIPDI

LOKIDE An..9

R Place of destination. Example "2MC"


DESADV of 46

2.12 NAD “of consignor” Position: 1/2/9NAD R 2/4 Name and address (of consignor)





DAF EDIPAQ M Default value “CZ” (consignor)

C082 PARTYIDENTIFICATIONDETAILS

C Identification of a transaction party bycode


DAF EDIPAI

LVCNUMLVR An..5

M Fill DAF-identification of Consignor.





DESADV of 46

2.13 NAD “of seller” Position: 1/2/9NAD R 2/4 Name and address (of seller)


Requires Group of NAD of Seller (SE) and NAD of Consignee (CN).

Group of NAD of Carrier (CA) and Consignor (CZ) are optional.

Processes 2/4 Groups of NAD-segments.



DAF EDIPAQ M Default value “SE” (seller)

C082 PARTY ID. DETAILS C Id. of a transaction party by code


DAF EDIPAI

LVCNUM An..5

M Fill DAF-identification of Seller.





DESADV of 46

2.14 TDT "of despatch" Position: 1/6/18TDT R 1 Details of transport

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

Expects ONE TDT-segmentProcesses 0/1 TDT-segments.


8051 TRANSPORT STAGEQUALIFIER

An..3 M Qualifier giving a special meaning to thetransport details

DAF EDITSQ M Value "12" (At departure)

C220 MODE OF TRANSP. C Method of transport code name

8067 Mode of transp. coded An..3 C

DAF EDIMTC

TPTMET N..2

C Code according ODDC003. In case notfilled, default value "30" (Road transport)

C222 TRANSPORTIDENTIFICATION

C Code identifying means of transport

8212 Id. of means oftransport

An..35 C

DAF EDIIMT

KENTPTMID An..10

C Identification of the vehicle (Licenseplate). Example: HH-DM-232.


DESADV of 46

2.15 CPS "of despatch of inner pack." Position: 1/10/28CPS R 1/N Consignment packing sequence

A segment identifying the sequence in which packing of the consignment occurs, e.g.boxes loaded onto a pallet.

Requires at least ONE group that starts with the CPS-segment. For every article, aCPS-group must be defined. First all articles with the specifications of the INNER-package will be defined. After all articles have been described, a second group opCPS-segments will start to define the handling units (OUTER package, thetransportpackage). IN this group, that starts with the CPS-segment, NO articlenumbers/quantities (starting with the LIN-segment) will be described.


7164 HIERARCHICAL ID.NUMBER

An..12 M Number assigned by sender to identify alevel o hierarchical structure.

DAF EDIHIN M Sequential number

7075 PACKAGINGLEVEL,CODED

An..3 C Identification of level of packagingspecified.

DAF EDIPLC R Value "1" (Inner)


DESADV of 46

2.15.1 PAC "of consignment" Position: 2/11/30PAC O 0/N Package (of consignment)

A segment to specify the number of package units and the physical type.

Expects at least one PAC-segment. A new group starting with the PAC-segment mustbe created in case of: another article, another quantity per package or anotherpackage type.

Processes 0/n groups of package information.


7224 NUMBER OFPACKAGES

N..8 C Quantity of packages.

DAF EDINUP

EMBQTYLVR N..9

R Quantity of packages for ONE article withSAME quantity per package.

C531 PACKAGE DETAILS C Details of package

C202 PACKAGE TYPE C Type of package by name or by codefrom a specified source.

7065 Type of packagesidentification

An..17 C Code description of the form in whichgoods are presented.

DAF EDITPI

EMBMIDLVR An..2

R DAF code to identify the package. Forexample : ‘MB’





DESADV of 46

2.15.1.1 MEA "of package of consignment" Position: 3/11/31

MEA C 0/1 Measurements (of package)


Expects ONE MEA-segmentProcesses 0/1 MEA-segments.




DAF EDIMAQ M AAY (Package measurement)





DAF EDIMDC M G (Gross weight)



DAF EDIMUQ

GEWENHEEN An..3

C Code according ODDC025 defining themeasure of weight.

If not filled DAF will use "KGM" asdefault.


DAF EDIMEV

EMBGEWBRT N..11

R Gross weight of package.


DESADV of 46

2.15.1.2 QTY "of package of consignment" Position: 3/11/32

QTY C 0/1 Quantity (of package)

A segment to specify pertinent quantities.

Expects ONE QTY-segment.Processes 0/1 QTY-segments.


C186 QUANTITY DETAILS M Quantity information in a transaction,qualified when relevant.

6063 Quantity qualifier An..3 M Code giving specific meaning to aquantity

DAF EDIQUQ M Value “52” (Quantity per pack)

6060 Quantity N..15 M Numeric value of a quantity.

DAF EDIQUA

EMBENHQTY N..5

M Quantity of articles in ONE package.

6411 Measure unit qualifier An..3 C Indication of the unit of measurement inwhich weight (mass) capacity, length,area, volume or other quantity isexpressed.

DAF EDIMUQ

ARTENHODT An..3

C Measure of quantity accordingODDC025. If space, DAF will use "PCE"(pieces).


DESADV of 46

2.15.1.3 PCI "of package of consignment " Position: 3/13/35

PCI R 1/1 Package identification (of package)

A segment specifying markings and/or labels used on individual physical units(packages) described in the PAC-segment.

Requires ONE PCI-segment in every PAC-group..Processes 1/1 PCI-segments.


4233 MARKINGINSTRUCTIONS,CODED

An..3 M Code indicating instructions on howspecified packages or physical unitsshould be marked.

DAF EDIMIC M Value "17" (Seller's instructions)

C827 TYPE OF MARKING C Specification of the type of marking

7511 Type of marking, coded An..3 M Specify type of marking.

DAF EDITMA M G - Mixed handling unit

M - Homogeneous handling unit(contains multiple part packages).

S - Simplified handling unit (no part packages)

3055 Code list responsibleagency

An..3 C

DAF EDICAC R Value "10" (ODETTE)


DESADV of 46

2.15.1.3.1 RFF "of Package id. of pack. of cons." Position: 4/13/36

RFF C 0/1 Reference

A segment for identifying documents relating to the line item, e.g. a contract and itsappropriate line item.

Expects ONE RFF-segment.Processes 0/1 RFF-segments


C506 REFERENCE M Identification of a reference

1153 Reference qualifier An..3 M Code giving specific meaning toreference segment or a referencenumber.

DAF EDIRQU M Value “AAT” (Master label number)

1154 Reference number An..35 C Identification number of a handling unit

DAF EDIRNU

TPTLBEIDE An..17

R Transport label number is required incase of handling unit category ‘M’ or ‘G’.


DESADV of 46

2.15.1.3.2 GIR "of Package id. of package of consignment" Position: 4/13/38

GIR O Related identification numbers

A segment specifying the type/source of identity number.

Only used for BATCH number informationProcesses 0/1 GIR-segments.


7297 SET IDENTIFICATIONQUALIFIER

An..3 M Identification of the type of set

DAF EDISIQ M Value "3" (Package)

C206 IDENTIFICATIONNUMBER

C Identification of an object

7402 Identity number An..35 M Identity number

DAF EDIINU M Number identifying the manufacturingbatch number

7405 Identity numberqualifier

An..3 C Code specifying the type/source ofidentity number

DAF EDIINQ R BX - Batch number


DESADV of 46

2.15.1.3.3 GIN "of package id. of package of consignment " Position: 4/13/39

GIN C 0/99 Goods identity number

A segment providing the identity numbers of packages being despatched.Attention: Only first occurrence of composite date element C208 is used by Odette.Maximum of five numbers can be filled in ONE GIN-segment..


7405 IDENTITY NUMBERQUALIFIER

An..3 M Code specifying the type/source ofidentity number

DAF EDIINQ M BN - Serial number

C208 ID. NUMBER RANGE M Item id.numbers, start/ end of range.

7402 Identity number An..35 M Identity of package. Mandatory in case oftag 7511 in PCI-segment has value ‘S’(simplified handling unit).

DAF EDIMNUTPTSERNUM An..17

M Serial number

C208 ID. NUMBER RANGE C

7402 Identity number An..35 M

DAF EDIMNU M Serial number











DESADV of 46

2.15.2 LIN "of consignment" Position: 2/15/41LIN R 1/N Line item

A segment identifying the details of the product or service to be delivered e.g. productidentification. All other segments in the detail section following the LIN segment, referto the line item.

Requires ONE group that starts with the LIN-segmentProcesses 1/N LIN-segments.


C212 ITEM NUMBERIDENTIFICATION

C Goods identification for a specifiedsource.

7140 Item number An..35 C A number allocated to a group or item.

DAF EDIITN

ITENUM An..7

C DAF code of article. Do NOT fill in casetag 1222 = ‘1’

7143 Item numbertype,coded

An..3 C Identification of the type of the itemnumber. User or association definedcode. May be used in combination with1131/3055.

DAF EDIITC C Value ‘IN’ (Buyer’s item number). DoNOT fill in case tag 1222 = ‘1’

1222 CONFIGURATIONLEVEL

N..2 C Level of article.

DAF EDICLEARTSRTMELSRT (If ARTSRT‘1’ occurs, fill MELSRTwith value ‘1’

C Level indicating set of articles(component/kit) or separate articles. Ifnot filled, no level assumed.Possible values:

‘0’ = no level (single articles)‘1’ = set level (set of articles)‘2’ = article level (in set of articles)


DESADV of 46

2.15.2.1 MEA "of shipment" (net weight) Position: 3/15/44

MEA C 0/1 Measurements (of article)


Requires net weight (AAL) of despatched article.Processes 0/1 MEA-segments.




DAF EDIMAQ M PD (Physical dimensions of productordered)





DAF EDIMDC M AAL (Net weight)



DAF EDIMUQ

GEWENH

C KGM (qualifier in case of weight)


DAF EDIMEV

GEWNET N..9

R net weight of despatched articles


DESADV of 46

2.15.2.2 QTY "of article of consignment" Position: 3/15/45

QTY R 1/1 Quantity (of articles)

A segment to specify pertinent quantities.

Requires ONE QTY-segmentProcesses 1/1 QTY-segment


C186 QUANTITY DETAILS M Quantity information in a transaction,qualified when relevant.

6063 Quantity qualifier An..3 M Code giving specific meaning to aquantity

DAF EDIQUQ M Value “12” (Despatch quantity)

6060 Quantity N..15 M Despatched quantity of articles.

DAF EDIQUA

ONTQTY N..7

M Total must be equal to sum of allpackage quantities as described inprevious segments under the CPS-segment.

6411 Measure unit qualifier An..3 C Indication of the unit of measurement inwhich weight (mass) capacity, length,area, volume or other quantity isexpressed.

DAF EDIMUQ

ARTENHLVR An..3

C Measurement of articles. In case notfilled DAF will use "PCE" as default..


DESADV of 46

2.15.2.3 RFF "of article of cons." (order) Position: 3/16/53

RFF O 0/1 Reference


Processes 0/3 RFF-segmentsOrdernumber NOT available for components (in case LIN-segment in tag 1222 = ‘1’)




DAF EDIRQU M Value “ON” (Order number purchase)

1154 Reference number An..35 C Order number

DAF EDIRNU

ORDNUM An..6

R Order number as used by DAF of article.Not filled in case of component.


DESADV of 46

2.15.2.4 RFF "of article of. cons." (Del. schedule Nr.) Position: 3/16/53

RFF O 0/1 Reference


Requires ONE RFF-segment.Processes 1 /3 RFF-segments




DAF EDIRQU M Value “AAN” (Delivery schedule nr.)

1154 Reference number An..35 C Reference number.

DAF EDIRNU

ZNDVLGNUM An..17

R Part consignment number of article.Example: the "Lieferscheinnummer".>>> In case this number is filled, thisnumber will be used by DAF to informseller about previous despatches of thisarticle in the DELFOR-message.


DESADV of 46

2.15.2.5 RFF "of article of. cons." (Part con. NR.) Position: 3/16/53

RFF O 0/1 Reference


This segment is only mandatory in case the delivery is triggered with the DELJIT-message. In case of the SYNCRO-DELJIT or the CALDEL-DELJIT the‘Manufacturing Reference Number’ sent by DAF in the GIR-segment (position 2/4/13)with qualifier ‘AN’ must be filled in this RFF-segment.

Requires ONE RFF-segment.Processes 1 /3 RFF-segments




DAF EDIRQU M Value “AAP” (Part consignment number)

1154 Reference number An..35 C Reference number.

DAF EDIRNU

VRZMASKEY An..6

R Fill Manufacturing reference number.Important data for DAF!!


DESADV of 46

2.15.2.6 LOC "of article of consignment" Position: 3/18/58

LOC O 0/1 Place/location identification

A segment indicating more details regarding specific places/locations related to theparty specified in the NAD segment, e.g. internal site/building number.

Requires ONE LOC-segment.Processes 0/1 LOC-segments.


3227 PLACE/LOCATIONQUALIFIER

An..3 M Code identifying the function of alocation.

DAF EDIPDQ M Value “159” (Additional internaldestination)

C517 LOCATIONIDENTIFICATION

C Identification of a location

3225 Place/locationidentification

An..25 C

DAF EDIPDI

ADMIDE An..5

R Additional destination info ofbuilding/gate.Example: "C3600" = Building "C36" andgate "00".


DESADV of 46

2.16 CPS "of despatch of handling units" Position: 1/10/28CPS O 0/N Consignment packing sequence

A segment identifying the sequence in which packing of the consignment occurs, e.g.boxes loaded onto a pallet.

After all articles have been described, a second group of CPS-segments will start todefine the handling units (OUTER package, the transportpackage). In this group, thatstarts with the CPS-segment, NO article numbers/quantities (starting with the LIN-segment) will be described.


7164 HIERARCHICAL ID.NUMBER

An..12 M Number assigned by sender to identify alevel o hierarchical structure.

DAF EDIHIN M Sequential number

7075 PACKAGINGLEVEL,CODED

An..3 C Identification of level of packagingspecified.

DAF EDIPLC R Value "3" (Outer)


DESADV of 46

2.16.1 PAC "of despatch of handling units" Position: 2/11/30PAC R 1/N Package (of handling units)

A segment to specify the number of package units and the physical type.

Requires at least one Group that starts with the PAC-segment. All handling units mustbe described in this segment.

Processes 1/n groups of package information.


7224 NUMBER OFPACKAGES

N..8 C Quantity of same handling units.

DAF EDINUP R Quantity of handling units

C202 PACKAGE TYPE C Type of package by name or by codefrom a specified source.

7065 Type of packagesidentification

An..17 C Code description of the form in whichgoods are presented.

DAF EDITPI R DAF code to identify the handling units(transport package).





DESADV of 46

2.17 UNT “of Message” Position: 0/-/76UNT M 1 Message trailer

A service segment ending a message, giving the total number of segments in themessage and the control reference number of the message.


0074 NUMBER OFSEGMENTS IN THEMESSAGE

N..6 M Number of segments in the message

DAF EDINSM M Total of transmitted segments inmessage.

0062 MESSAGEREFERENCENUMBER

An..14 M Message reference number

DAF EDIMRE M Unique session number.


DESADV of 46

3. Procedure of implementationIn this chapter we describe the steps to be taken to convert from the currentOdette message to the standard Edifact message. We also defined atimeframe in which we want to complete the migration of the DESADV-message with your organisation.

1. Introduction (max. 1 week).Investigate EDI-interaction between DAF and supplier. Some questionsthat needs to be answered:

• What messages (IN/OUT) are used?

• DAF will check if EDI-contract between DAF and supplier isavailable. If not, DAF will send one that needs to be signed by thesupplier.

• ogether with the supplier, a global timeframe will be made for theremaining steps to be taken.

2. Check DESADV-definition used by DAF (Max. 2 weeks).Supplier will check how DAF will process the DESADV-message andconfirm on paper that the message can be created according thesespecifications. If necessary, supplier will take action to initiate systemadjustments.

3. Plan migration activities (Max. 1 week).Based on the results of the previous action, the migration of the DESADV-message will be planned together with the supplier.

4. Prepare system supplier. (1 to 4 weeks).Supplier will develop the DESADV-message according the DAF-specifications. System will be prepared to send the first test DESADV-meassage.

5. Test DESADV (Max. 4 weeks).Supplier will inform when first DESADV-message can be transmitted fortest purposes. This will be a copy of an operational AVIEXP-message.These test DESADV-messages will be transmitted separately to avoidproblems in the operational environment. If necessary more test messages


DESADV of 46

will be send. DAF will confirm op paper that the message can beprocessed correctly.

6. Operational DESADV (milestone X).Together a date will be determined to replace the operational AVIEXP-message by the DESADV-message. From that date, the DESADV-message will become an operational status. The AVIEXP-message will nolonger be supported.

7. Evaluate DESADV (max. 4 weeks).During the first 4 weeks of being operational, the message exchange willbe checked carefully in order to avoid problems. After this period anevaluation will take place together with the supplier, to discuss thecomplete process.

Based on these steps, DAF will try to complete the implementation within atimeframe of 16 weeks. This timeframe will be discussed with your people.


DESADV of 46

4. Example of DESADV-messageUNB+UNOA:3+O0013000023HELLA-KG+003117000000032876000001+

980504:1508+00104055++++++1'

UNH+00228160-001+DESADV:D:96A:UN:A01051'

BGM+351+00228160-001'

DTM+137:199805041508:203'

MEA+AAX+AAD+KGM:369'

NAD+CA++D & L'

NAD+CN+W::92'

LOC+11+4MK'

NAD+SE+88080::92'

TDT+12++30+++++:::SO - CC 560'

CPS+001++1'

PAC+1++::92'

MEA+AAY+G+GRM:162000'

QTY+52:408:PCE'

PCI+17+++S::10'

GIN+BN+S000486631'

LIN+++1272269:IN'

QTY+12:408:PCE'

RFF+ON:BF2751'

RFF+AAN:00295102'

CPS+002++1'

PAC+1++::92'

MEA+AAY+G+GRM'


DESADV of 46

QTY+52:36:PCE'

PCI+17+++G::10'

RFF+AAT:G000488317'

GIN+BN+S000488108'

LIN+++1268427:IN'

QTY+12:36:PCE'

RFF+ON:BE6335'

RFF+AAN:00295484'

CPS+003++1'

PAC+1++::92'

MEA+AAY+G+GRM'

QTY+52:348:PCE'

PCI+17+++G::10'

RFF+AAT:G000488317'

GIN+BN+S000488316'

LIN+++1281147:IN'

QTY+12:348:PCE'

RFF+ON:BF4412'

RFF+AAN:00295484'

CPS+004++1'

PAC+7++::92'

MEA+AAY+G+GRM:5000'

QTY+52:36:PCE'

PCI+17+++S::10'

GIN+BN+S000484144+S000484145+S000484146+S000484147+S000484148'


DESADV of 46

GIN+BN+S000484149+S000484433'

LIN+++1268427:IN'

QTY+12:252:PCE'

RFF+ON:BE6335'

RFF+AAN:00297436'

CPS+005++3'

PAC+2++::92'

PAC+7++::92'

UNT+56+00228160-001'

UNZ+1+00104055'

_


DESADV of 46

5. Overview of attachments

5.1 Message branching diagram as used by DAF

UNH

1M

0

1

2

3

Bgm

1M

DTM

1R

TDT

1M

Grp 6

1C

NAD

1M

Grp 2

4C

PAC

1M

UNT

1M

Grp 11

999C

4

MEA

1C

PCI

1M

Grp 13

1000C

GIN

1M

Grp 14

99C

LOC

1M

Grp 18

10C

LOC

1R

CPS

1M

Grp 10

999C

MEA

2C

LIN

1M

Grp 15

999C

QTY

1C

RFF

1C

GIR

1C

MEA

1C

RFF

1M

Grp 16

10C

QTY

1C

DESADV spec 1.4 - iconnect-corp.com... desadv spec 1.4.doc Date created : 12-09-02 14:10 Status :...

Documents

Transcript of DESADV spec 1.4 - iconnect-corp.com... desadv spec 1.4.doc Date created : 12-09-02 14:10 Status :...