despatch advice message desadv (outbound from ti) · 2005. 2. 4. · the despatch advice is defined...

Texas Instruments Incorporated 1 of 44 Despatch Advice Message v. 1.0

TEXASINSTRUMENTS

Despatch Advice Message

DESADV

(Outbound from TI)

Based on EDIFICE Issue 3(Based on EDIFACT Version 92.1)

Date : July 1996TI Version 1.0

This document can be found on the World Wide Web from http://www.ti.com/sc/docs/scedi/sctecpak.htm


Copyright 1996Texas Instruments IncorporatedAll Rights Reserved

The information and/or drawings set forth in this document and all rights in and to inventionsdisclosed herein and patents which might be granted there on disclosing and employing thematerials, methods, techniques, or apparatus described herein are exclusive property of TexasInstruments Incorporated.


Table of Contents

TITLE __________________________________________________________________PAGE

TABLE OF CONTENTS________________________________________________________ 3INTRODUCTION _____________________________________________________________ 4HOW TO USE THIS DOCUMENTATION_________________________________________ 5PURPOSE OF THIS MESSAGE _________________________________________________ 6REFERENCES _______________________________________________________________ 8EDIFICE MESSAGE DIAGRAM_________________________________________________ 9UNH MESSAGE HEADER_______________________________________________________ 10BGM BEGINNING OF MESSAGE__________________________________________________ 11DTM DATE / TIME / PERIOD ____________________________________________________ 12MEA Measurements 13SEGMENT GROUP 1 ___________________________________________________________ 14

RFF REFERENCE_________________________________________________________ 15SEGMENT GROUP 2 ____________________________________________________________ 16

NAD NAME AND ADDRESS_________________________________________________ 17SEGMENT GROUP 6 ____________________________________________________________ 19

TDT DETAILS OF TRANSPORT________________________________________________ 20SEGMENT GROUP 7 ____________________________________________________________ 22

LOC LOCATION __________________________________________________________ 23DTM DATE / TIME / PERIOD ________________________________________________ 24

SEGMENT GROUP 10 ___________________________________________________________ 25CPS CONSIGNMENT PACKING SEQUENCE______________________________________ 27

SEGMENT GROUP 11 ___________________________________________________________ 28PAC PACKAGE___________________________________________________________ 29

SEGMENT GROUP 13 ___________________________________________________________ 30PCI PACKAGE IDENTIFICATION ______________________________________________ 31

SEGMENT GROUP 14 ___________________________________________________________ 32GIN GOODS IDENTITY NUMBER _____________________________________________ 33

SEGMENT GROUP 15 ___________________________________________________________ 34LIN L INE ITEM___________________________________________________________ 36PIA ADDITIONAL PRODUCT ID ______________________________________________ 37QTY QUANTITY __________________________________________________________ 39

SEGMENT GROUP 16 __________________________________________________________ 40RFF REFERENCE_________________________________________________________ 41

UNT MESSAGE TRAILER_______________________________________________________ 42EXAMPLES ________________________________________________________________ 43

Texas Instruments Incorporated 4 of 44 Despatch Advice (DESADV) v. 1.0

Introduction

This guide was developed by members of the Texas Instruments EDI message developement Group. It isbased on the guide developed by members of the Electronics Industry through the associationsrepresenting Europe (EDIFICE), Japan (EIAJ) and the USA (EIDX). It represents the joint requirementsof these associations and is specific to the useage as specified by Texas Instruments.


How To Use This Documentation

This document was created to aid in your implementation of UN/EDIFACT standards. Thisdocumentation contains those segments and elements that will be used by Texas InstrumentsIncorporated.

A complete description of the segments are outlined in the UN/EDIFACT Standards Manual. If yourequire/need to be sent additional segments not listed in this documentation, an agreement must bereached with Texas Instruments Incorporated.

This document defines the TI preferred structure and content of the EDIFICE endorsed DESADVmessage.

Segment/Data Element Usage(M) Mandatory = EDIFACT dictates that the Data Element or Segment must be present.(R) Required = EDIFICE members agree that the data concerned must be sent.(D) Depending = The data concerned must be sent if a particular defined condition or set of conditions

exists. The associated conditions must be explained at the appropriate level of detail.(A) Advised = Indicates that the RECEIVER of the message would prefer the data concerned to be

sent, but does not require its transmission.(O) Optional = Indicates that the transmission of the data concerned is at the need or discretion of the

SENDER, i.e. it is not required by the receiver in order to perform its businessfunction. EDIFICE requires that the use of ‘O’ must be agreed between tradingpartners.

(X) Not Used = The Data Element or Segment will not be used by EDIFICE members.

The EDIFICE usage status and number of occurrences for segments or segment groups will berepresented analogous to the representation of data elements.

e.g.: R3 The segment or group is required 3 times (fixed number)R..3 The segment or group is required up to 3 times (maximum number)

Data Element Representation(a) Alpha(an) Alpha Numeric(n) Numeric

EnvelopingThe UNB/UNZ interchange envelope and the UNH/UNT message envelope are shown in this documentin the message diagram. Details on these segments are found separately in the SERSEG document.


Purpose of this Message

The Despatch Advice is defined as a logistics transaction message sent by the consignor and is intended toadvise the consignee of the despatch of goods and the detailed contents of the consignment, to enable thereceiving location to control the incoming material flow.

The message relates to a single despatch point and a single destination point, with one set of deliveryterms. It may cover a number of different items or packages.

The Despatch Advice message relates to one buyer and one seller. It should always be sent by the seller tothe buyer before the goods are physically delivered. This makes it possible for the buyer to know when thegoods have been despatched, or will be despatched, and use the data to prepare efficiently for thereception of the goods. The message can also be used by the Seller to indicate to the Buyer that the goodsare ready to be collected (an EXWORKS trade scenario), or if the goods are Returns. Texas Instrumentshas no plans to include either of these message functions at this time.

The Despatch Advice message holds precise details of the shipment.

Each unit delivered e.g. pallet, carton, should be uniquely identified. In the Despatch Advice message, theproducts contained in each uniquely identified unit are described. When the goods are received, thephysicalshipment and the electronic message can be cross-checked e.g. by barcode scanning. Discrepancies can beimmediately identified, and these may be transmitted back to the seller by use of the Receiving Advice(RECADV) message.

The message enables a hierarchical description of the shipment, starting with the highest level (shipment)and ending with the lowest level (items). One can for example describe a container comprising 5 pallets, apallet being composed of several large despatch units which themselves contain smaller despatch units.The traded units (any level of packaging agreed by the trading partners) are then specified. It is howevernot mandatory to describe the hierarchical structure of the shipment. As such, the simplest use of themessage consists of specifying the items to be despatched, or collected, and the relevant information peritem such as quantity and description. Please refer to the example at the back of this document.

Additional principles that apply to the Despatch Advice message are:-

* Buyer Part numbers are used in the LIN segment to identify the product that is being despatched. Wherethis is not available , the Texas Instruments Part Number will be identified in the PIA segment followingtheLIN segment.


* References pertaining to the goods are specified only at one level, normally within the detail section.Where the information is applicable to the whole despatch advice, it will be sent in the Header section, inwhich case it will not be sent at the Detail level.

* Total shipment weights, volume and number of unit loads will be specified in the Header section of themessage i.e. in the MEA segment below the BGM.

* Business practices reflect two possible ways of describing the contents of the shipment; by the physicalpackaging, or by the products (with package information related to each product). The physical packaginglogic describes package per package starting from the outer packages and ending with the inner packages.The product(s) are identified at the lowest level of the packaging. The product logic describes per product.Texas Instruments will utilize the former method, i.e Package level logic.

* The segment groups, segments and data elements which are labeled with 'O' (optional) should be usedonly if the information they contain cannot be incorporated in the business or commercial agreements. Theuse of 'O' (optional) will be agreed between Trading Partners.

It is recognised that information pertaining to the goods and or the transport of the goods, may changeafter the initial message has been sent. Under the International Custom's Regulations - and subsequentlythe International Law's of Trade and Commerce - CHANGES (of the contents) of "Accountable Dataand/or Documents" are prohibited. Instead, CANCELLATION (of the entire document) andREPLACEMENT (by a new document) are imperative. All Accountable Documents - including thecanceled ones - haveto be safeguarded for a period of at least 5 years or longer, depending on national prescriptions.

To accommodate these scenarios, both 'replace' and 'cancellation' message types are catered for in theEDIFICE endorsed DESADV message. However, Texas Instruments will does not plan to adopt either ofthese message functions at this time.


References

UNSM Despatch Advice message (DESADV) Version 1, Release 921, Status 1, Date 92-09EDIFACT STANDARD DATA SEGMENT DIRECTORY 92.1EDIFACT CODE LIST 92.1EDIFACT Service Segments, ISSUE 2ISO 9735 : 1988 (E) EDIFACT - APPLICATION LEVEL SYNTAX RULES, FIRST EDITION : 1988-07-15 AMENDED AND REPRINTED : 1990-11-15ISO 3166 Codes for the representation of names of countries.UN/ECE RECOMMENDATION No.5 : Incoterms 1990.UN/ECE RECOMMENDATION No.16: UNLOCODE.UN/ECE RECOMMENDATION No.20: Codes for Units of Measurement.UN/ECE RECOMMENDATION No.21: Codes for Types of Cargo, Packages and Packaging Materials.UNTDED 5.9 p2 CIMP


Despatch Advice (DESADV)

SEG NAME REQDES

MAXUSE

LOOP REPEAT

UNB Interchange header M 1UNH Message header M 1BGM Beginning of message M 1DTM Date/time/period R ..3MEA Measurements A ..4

SEGMENT GROUP 1 D..10RFF Reference M 1

SEGMENT GROUP 2 R..10NAD Name and Address M 1

SEGMENT GROUP 6 D..5TDT Details of transport M 1

SEGMENT GROUP 7 O..6LOC Place/location identification M 1DTM Date/time/period A..2

SEGMENT GROUP 10 R..9999CPS Consignment packing sequence M 1

SEGMENT GROUP 11 A..10PAC Package M 1

SEGMENT GROUP 13 A1PCI Package identification M 1

SEGMENT GROUP 14 D 1GIN Goods identity number M 1

SEGMENT GROUP 15 D..9999LIN Line Item M 1PIA Additional product id D ..2QTY Quantity R 1

SEGMENT GROUP 16 A..5RFF Reference M 1

UNT Message trailer M 1UNZ Interchange trailer M 1


UNH - Message Header

Function: To head, identify and specify a message.

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationUNH01 0062 an..14 MESSAGE REFERENCE NUMBER M See Note 1UNH02 S009 MESSAGE IDENTIFIER M

0065 an..6 Message type identifier M ‘DESADV’0052 an..3 Message type version number M ‘1’0054 an..3 Message type release number M ‘921’0051 an..2 Controlling agency M ‘UN’0057 an..6 Association assigned code R ‘ED3’

UNH03 0068 an..35 COMMON ACCESS REFERENCE XUNH04 S010 STATUS OF THE TRANSFER X

0070 n..2 Sequence message transfer number0073 a1 First/last sequence message transfer

indication

UNH Notes

1. DE 0062 MESSAGE REFERENCE NUMBERThis reference number must also be in the UNT segment of this message.


BGM - Beginning of Message

Function: To indicate the beginning of the Despatch Advice message; the type of transaction beingperformed, and the function of the message. It is also used to transmit the shipment number.

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationBGM01 C002 DOCUMENT/MESSAGE NAME R

1001 an..3 Document/message name, coded R‘351’ Despatch advice1131 an..3 Code list qualifier X3055 an..3 Code list responsible agency, coded X1000 an..35 Document/message name X

BGM02 1004 an..35 DOCUMENT/MESSAGE NUMBER R See Note 1BGM03 1225 an..3 MESSAGE FUNCTION, CODED R ‘9’ OriginalBGM04 4343 an..3 RESPONSE TYPE, CODED X

BGM Notes

1. DE 1004 DOCUMENT/MESSAGE NUMBERThe recommendation is that the Shipment Number be used to uniquely identify the Despatch Advice. The shipmentnumber is a unique number, created by the supplying company, which will be used to identify the shipment from thesupplier through to the receiving location’s receipt validation step. (Waybill number)


DTM - Date/Time/Period

Function: To provide a date (or dates and times) relevant to the whole despatch advice.

Usage: R..3

Remarks: All dates and times are local dates and times to the place of activity being described. It isrequired to specify the date of issue of the message.This segment is not required when a Cancellation is sent.

Field # Ref. Rep. Field Usage TI UtilisationDTM01 C507 DATE/TIME PERIOD M

2005 an..3 Date/time/period qualifier M ‘137’ Document/message date/time2380 an..35 Date/time/period R See Note 12379 an..3 Date/time/period format qualifier R See Note 2

DTM Notes

1. DE 2380 Date/time/periodUsed to specify the date, preferably in the recommended format (CCYYMMDD)

2. DE 2379 Date/time/period format qualifier‘101’ YYMMDD‘102’ CCYYMMDD


MEA - Measurements

Function: To specify weights, volume and quantity of shipment unit loads of the entire shipment.

Usage: A..4

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationMEA01 6311 an..3 MEASUREMENT APPLICATION

QUALIFIERM See Note 1

MEA02 C502 MEASUREMENT DETAILS R6313 an..3 Measurement dimension, coded R See Note 26321 an..3 Measurement significance, coded X6155 an..3 Measurement attribute, coded X

MEA03 C174 VALUE/RANGE R6411 an..3 Measure unit qualifier M See Note 36314 n..18 Measurement value R6162 n..18 Range minimum X6152 n..18 Range maximum X

MEA04 7383 an..3 SURFACE/LAYER INDICATOR,CODED

X

MEA Notes

1. DE 6311 MEASUREMENT APPLICATION QUALIFIER‘CT’ Counts‘WT’ Weights

2. DE 6313 MEASUREMENT DIMENSION, CODED‘AAD’ Total gross weight‘SQ’ Shipped quantity

3. DE 6411 MEASURE UNIT QUALIFIER‘KGM’ Kilogram‘MTQ’ Cubic Metres‘NMP’ Number of packs‘LBS’ Pounds


Segment Group 1

Function: A segment group for referencing documents and their dates relating to the whole DespatchAdvice.

Usage: D..10

Remarks: Normally references are specified at the line item level. Where the information refers to thewhole Despatch Advice it must be in Segment Group 1. Where the information is not thesame in every line item (LIN) it must appear in every SG 16, and not here.

SEG NAME REQDES

MAXUSE

LOOP REPEAT

SEGMENT GROUP 1 D..10RFF Reference M 1


Segment Group 1RFF - Reference

Function: Used for referencing a document related to the whole of the Despatch Advice.

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationRFF01 C506 REFERENCE M

1153 an..3 Reference qualifier M ‘AWB’ Air waybill number1154 an..35 Reference number R1156 an..6 Line number X4000 an..35 Reference version number X


Segment Group 2

Function: A group of segments identifying Names, Addresses and Contacts relevant to the wholeDespatch Advice.

Usage: R..10

Remarks: The address of the seller (SE) must be present.

It is also possible that the address from which the shipment is actually made, or delivered to, isdifferent to the address of the SE. In this case NADs must be present for the ‘ship to’ (DP)codes.

Where possible, only the coded form of the party ID should be specified, e.g. the buyer andseller are known to each other, thus only the coded ID is required. The consignee or deliveryaddress may vary and would have to be clearly specified, preferably in structured format.

This segment group is not required when a cancellation is sent.

When the customer request it, TI returns the NAD code as sent within the ORDERS message.

SEG NAME REQDES

MAXUSE

LOOP REPEAT

SEGMENT GROUP 2 R..10NAD Name and Address M 1


Segment Group 2NAD - Name and AddressFunction: To specify the identification/name/address of the parties involved in the Despatch Advice.

Usage: M1

Remarks: The recommended method of identifying a party is through the use of codes in C082. If C082cannot be used, (through lack of codes or codes not sufficiently precise), it is recommended touse a structured address (C080 through 3207) rather than an unstructured one (C058)

Field # Ref. Rep. Field Usage TI UtilisationNAD01 3035 an..3 PARTY QUALIFIER M See Note 1NAD02 C082 PARTY IDENTIFICATION DETAILS A

3039 an..17 Party id identification M Code identifying the party1131 an..3 Code list qualifier O3055 an..3 Code list responsible agency, coded R See Note 2

NAD03 C058 NAME AND ADDRESS D3124 an..35 Name and address line M3124 an..35 Name and address line O3124 an..35 Name and address line O3124 an..35 Name and address line O3124 an..35 Name and address line O

NAD04 C080 PARTY NAME D3036 an..35 Party name M3036 an..35 Party name O3036 an..35 Party name O3036 an..35 Party name O3036 an..35 Party name O3045 an..3 Party name format, coded O

NAD05 C059 STREET D3042 an..35 Street and number/P.O. Box M3042 an..35 Street and number/P.O. Box O3042 an..35 Street and number/P.O. Box O

NAD06 3164 an..35 CITY NAME DNAD07 3229 an..9 COUNTRY SUB-ENTITY

IDENTIFICATIOND

NAD08 3251 an..9 POSTCODE IDENTIFICATION DNAD09 3207 an..3 COUNTRY, CODED D See ISO 3166 2 alpha country

code e.g. BE Belgium.


Segment Group 2NAD - Name and Address

NAD Notes

1. DE 3035 PARTY QUALIFIER‘DP’ Delivery party

This is the ‘ship to’ address.‘SE’ Seller

2. DE 3055 CODE LIST RESPONSIBLE AGENCY, CODED‘91’ Assigned by seller or seller’s agent‘92’ Assigned by buyer or buyer’s agent


Segment Group 6

Function: A segment group to specify the stage of the transport, details of the Carrier, the mode oftransport, and identification of the transport.

Usage: D..5

Remarks: The segment group must be used if the shipment has occurred i.e. if the code used in theBGM is ‘351’. If the code used is ‘345’ (ready for despatch) then this is an optional segmentgroup. The segment group will be repeated for specifying the mode of transportation forsuccessive stages e.g. road, air. When required, carrier identification and name may be givenin TDT C040.

SEG NAME REQDES

MAXUSE

LOOP REPEAT

SEGMENT GROUP 6 D..5TDT Details of transport M 1

SEGMENT GROUP 7 O..5LOC Place/location identification M 1DTM Date/time/period A ..2


Segment Group 6TDT - Details Of Transport

Function: To specify the mode of transport, the identification of the means of transport, and if necessarythe Carrier information.

Usage: M1

Remarks: DE 8028 may be used to reference a current transport stage as identified in DE 8051, if thisinformation is already known e.g. flight number.Identification such as vehicle license plate number may be provided in C222 DE 8212.

Field # Ref. Rep. Field Usage TI UtilisationTDT01 8051 an..3 TRANSPORT STAGE QUALIFIER M ‘20’ Main-carriage transportTDT02 8028 an..17 CONVEYANCE REFERENCE

NUMBERA Used for Flight or Voyage no.

TDT03 C220 MODE OF TRANSPORT R8067 an..3 Mode of transport, coded R See Note 18066 an..17 Mode of transport X

TDT04 C228 TRANSPORT MEANS X8179 an..88178 an..17

TDT05 C040 CARRIER A3127 an..17 Carrier identification A Mutually defined code1131 an..3 Code list qualifier O3055 an..3 Code list responsible agency, coded A See Note 23128 an..35 Carrier name D Used if no coded name

exchangedTDT06 8101 an..3 TRANSIT DIRECTION, CODED XTDT07 C401 EXCESS TRANSPORTATION

INFORMATIONX

8457 an..3 Excess transportation reason, coded8459 an..3 Excess transportation responsibility,

coded7130 an..17 Customer authorization number

TDT08 C222 TRANSPORT IDENTIFICATION A8213 an..9 Id of means of transport identification X1131 an..3 Code list qualifier X3055 an..3 Code list responsible agency, coded X8212 an..17 Id of the means of transport A Vessel name or vehicle license

number.8453 an..3 Nationality of means of transport, coded O Use ISO 3166 2 alpha country

code e.g. BE Belgium.


Segment Group 6TDT - Details Of Transport (Continued)

TDT Notes

1. DE 8067 Mode of transport, coded‘30’ Road‘40’ Air‘50’ Mail

2. DE 3055 Code list responsible agency, coded‘91’ Assigned by seller or seller’s agent‘92’ Assigned by buyer or buyer’s agent


Segment Group 7

Function: A segment group to specify the location information applying to the transportation.

Usage: O..6

Remarks:

SEG NAME REQDES

MAXUSE

LOOP REPEAT

SEGMENT GROUP 7 O..6LOC Place/location identification M 1DTM Date/time/period A ..2


Segment Group 7LOC - Place/Location Identification

Function: To identify the location.

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationLOC01 3227 an..3 PLACE/LOCATION QUALIFIER M See Note 1LOC02 C517 LOCATION IDENTIFICATION X

3225 an..25 Place/location identification1131 an..3 Code list qualifier3055 an..3 Code list responsible agency, coded3224 an..17 Place/location

LOC03 C519 RELATED LOCATION ONEIDENTIFICATION

X

3223 an..25 Related place/location oneidentification

1131 an..3 Code list qualifier3055 an..3 Code list responsible agency, coded3222 an..70 Related place/location one

LOC04 C553 RELATED LOCATION TWOIDENTIFICATION

X

3233 an..25 Related place/location twoidentification

1131 an..3 Code list qualifier3055 an..3 Code list responsible agency, coded3232 an..70 Related place/location two

LOC05 5479 an..3 RELATION, CODED X

LOC Notes

1. DE 3227 PLACE / LOCATION QUALIFIER‘5’ Place of departure‘7’ Place of delivery


Segment Group 7DTM - Date/Time/Period

Function: To specify a date/time of departure and/or arrival of the transported goods for the specificlocation.

Usage: A..2

Remarks: All dates and times are local to the place of the activity being described.

Field # Ref. Rep. Field Usage TI Utilisation

DTM01 C507 DATE/TIME PERIOD M2005 an..3 Date/time/period qualifier M See Note 12380 an..35 Date/time/period R See Note 22379 an..3 Date/time/period format qualifier R See Note 3

DTM Notes

1. DE 2005 Date/time/period qualifier‘11’ Despatch date/time‘17’ Delivery date/time, estimated

2. DE 2380 Date/time/periodUsed to specify the date, preferably in the recommended format (CCYYMMDD)

3. DE 2379 Date/time/period format qualifier‘101’ YYMMDD‘102’ CCYYMMDD


Segment Group 10

Function: A group of segments providing details of all package levels and of the individual despatcheditems contained in the shipment. This group provides the capability to give the hierarchicalpacking relationship. The group defines a logical top-down order structure. The lowest levelpackage information of the hierarchy is followed by the detail part information.

Usage: R..9999

Remarks: Business practices can describe the contents of a despatch advice according to two mainlogics:

The PACKAGE driven logic: the despatch advice is described package per package,according to the physical structure of the packaging hierarchy, starting from the outerpackages ending with the inner packages. The contended items are identified at thelowest level of the packaging structure. There is a one to one relationship between theCPS and PAC segments.

It is recommended that users of this guide adopt the PACKAGE driven logic. See theEXAMPLE section of the guide on how to use this segment group.

Package identification numbers will be placed in the GIN segment in segment group 14.

This segment loop is required at least once.


Segment 10 (Continued)Despatch Advice (DESADV)

SEG NAME REQDES

MAXUSE

LOOP REPEAT

SEGMENT GROUP 10 R..9999CPS Consignment packing sequence M 1



SEGMENT GROUP 14 D1GIN Goods identity number M 1




Segment Group 10CPS - Consignment Packing Sequence

Function: To identify the sequence in which physical packing is presented in the consignment, e.g. boxesloaded onto a pallet..

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationCPS01 7164 an..12 HIERARCHICAL ID NUMBER M See Note 1CPS02 7166 an..12 HIERARCHICAL PARENT ID XCPS03 7075 an..3 PACKAGING LEVEL, CODED X

CPS Notes

1. DE 7164 HIERARCHICAL ID NUMBERSequential numbering is recommended. The number remains unique within the message.


Segment Group 11

Function: A segment identifying packaging, physical dimensions, label numbers, and quantities.

Usage: A..10

Remarks: Use of this segment group is dependent on the trading partners agreement to describe theconsignment by the packaging levels. While it is not mandatory to describe the hierarchicalstructure of the shipment, for a number of reasons (customs, insurance, etc.), it is advised tospecify at least each unit delivered.

SEG NAME REQDES

MAXUSE

LOOP REPEAT





Segment Group 11PAC - Package

Function: For specifying the number and type of identical packages for given items, or of identicalhandling units of the despatch.

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationPAC01 7224 n..8 NUMBER OF PACKAGES RPAC02 C531 PACKAGING DETAILS X

7075 an..3 Packaging level, coded7233 an..3 Packaging related information, coded7073 an..3 Packaging terms and conditions,

codedPAC03 C202 PACKAGE TYPE R

7065 an..7 Type of packages identification A 'BX' Box1131 an..3 Code of list qualifier O3055 an..3 Code list responsible agency, coded D See Note 17064 an..35 Type of packages O

PAC04 C402 PACKAGE TYPE IDENTIFICATION X7077 an..3 Item description type, coded7064 an..35 Type of packages7143 an..3 Item number type, coded7064 an..35 Type of packages7143 an..3 Item number type, coded

PAC05 C532 RETURNABLE PACKAGE DETAILS X8395 an..3 Returnable package freight payment

responsibility, coded8393 an..3 Returnable package load contents,

coded

PAC Notes

1. DE 3055 Code list responsible agency, codedOnly used if the UN/ECE Recommendation No.21 (TDED 5.8) is not used.


Segment Group 13

Function: A group of segments specifying packaging identification numbers and associated referencedocument numbers.

Usage: A1

Remarks: If barcode labeling is used on the packaging it is recommended that the Packagingidentification be one of the items barcoded.

SEG NAME REQDES

MAXUSE

LOOP REPEAT




Segment Group 13PCI - Package Identification

Function: This segment carries no business information and is only used to access reference and packageId information.

Usage: M1

Remarks: The value entered in this segment is only used to enable access to the following segmentswithin this segment group.

Field # Ref. Rep. Field Usage TI UtilisationPCI01 4233 an..3 MARKING INSTRUCTIONS,

CODEDR '17' Seller's instructions

PCI02 C210 MARKS & LABELS X7102 an..35 Shipping marks7102 an..35 Shipping marks7102 an..35 Shipping marks7102 an..35 Shipping marks7102 an..35 Shipping marks7102 an..35 Shipping marks7102 an..35 Shipping marks7102 an..35 Shipping marks7102 an..35 Shipping marks7102 an..35 Shipping marks

PCI03 8275 an..3 CONTAINER/PACKAGESTATUS, CODED

X


Segment Group 14

Function: A segment group providing the identity number of a package being despatched.

Usage: D1

Remarks: The usage of this segment group is dependent on the existence of a package identification(license plate) on the package.

SEG NAME REQDES

MAXUSE

LOOP REPEAT



Segment Group 14GIN - Goods Identity Number

Function: To give the unique identification number of the package

Usage: M1

Remarks: When using barcoding this information relates to the appropriate data identifiers that indicateLicense Plate.

Field # Ref. Rep. Field Usage TI UtilisationGIN01 7405 an..3 IDENTITY NUMBER

QUALIFIERM ‘ML’ Marking/label number

GIN02 C208 IDENTITY NUMBER RANGE M TI Box Number7402 an..35 Identity number M7402 an..35 Identity number D

GIN03 C208 IDENTITY NUMBER RANGE X7402 an..35 Identity number7402 an..35 Identity number





Segment Group 15

Function: A segment providing details of the individual despatched items within the packages described.

Usage: D..9999

Remarks: The usage of this group within the CPS group is dependent on the level of packaging beingdescribed. If describing packages that contain lower level packages, then this group ofsegments would be omitted until the lowest level package was being described.

This segment loop is required at least once for the lowest level of packaging.

The Seller/Shipper should only need to indicate in the Despatch Advice the same itemidentification as was given in the Purchase Order. This item identification should be placed inthe LIN segment.

In the event that additional information needs to be given to that primary item identificationreference then it should be placed in the PIA segment.

Information on other associated item ids should also be placed in the PIA segment.

Item identification should be used where ever possible. In a situation where no itemidentification can be given then a coded, or free text description may be given in the IMDsegment.

Physical representation of the data in the LIN segment can be handled by barcoded productand package labels.

Example of use are:

1. Item as identified by the Buyer’s product id number.

LIN+1++12345-12:IN::92’

2. Item as identified by the Seller’s product id number with an additional drawing revisionnumber as assigned by the Seller.

LIN+1++ABCDE-AA:SA::91’PIA+1+ABCDE-AA-1:DR::91’

3. Item as identified by the Seller’s product id number with the addition of the Buyer’sreference number for this product.

LIN+1++ABCDE-AA:SA::91’PIA+1+12345-12:IN::92’


Segment Group 15 (Continued)

4. Item as identified by the Seller’s product number with the addition of the Seller’ssubstitute number for this product, and also the Buyer’s own product and substitutenumber for this product.

LIN+1++ABCDE-AA:SA::91’PIA+4+ABCDE-AB:SA::91+12345-15:IN::92’PIA+1+12345-12:IN::92’

SEG NAME REQDES

MAXUSE

LOOP REPEAT




Segment Group 15LIN - Line Item

Function: To specify the line item being described, and the part number agreed to be the primaryreference number between the Buyer and Seller.

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationLIN01 1082 n..6 LINE ITEM NUMBER A See Note 1

LIN02 1229 an..3 ACTION REQUEST/NOTIFICATION, CODED

X

LIN03 C212 ITEM NUMBER IDENTIFICATION R7140 an..35 Item number R See Note 27143 an..3 Item number type, coded R 'BP' Buyer's part number1131 an..3 Code list qualifier O3055 an..3 Code list responsible agency, coded O '92' Assigned by buyer or buyer's

agentLIN04 5495 an..3 SUB-LINE INDICATOR, CODED XLIN05 1222 n..2 CONFIGURATION LEVEL XLIN06 7083 an..3 CONFIGURATION, CODED X

1. DE 1082 LINE ITEM NUMBERThis number is assigned by the sender of the message. The first line item within a message will be numbered '1' and further line items will be incremented by '1' for each new line.

2. DE 7140 ITEM NUMBERUse the primary part number. Other related numbers should be in the PIA segment.


Segment Group 15PIA - Additional Product ID

Function: To specify additional item identification.

Usage: D..2

Remarks: This segment is dependent on whether the primary reference to the item being ordered isinsufficient to identify the item. Information such as engineering change level, drawingrevision number etc. can also be included in this segment.

Field # Ref. Rep. Field Usage TI UtilisationPIA01 4347 an..3 PRODUCT ID FUNCTION

QUALIFIERM '1' Additional identification

PIA02 C212 ITEM NUMBER IDENTIFICATION M7140 an..35 Item number R7143 an..3 Item number type, coded R See Note 11131 an..3 Code list qualifier O3055 an..3 Code list responsible agency, coded O '91’ Assigned by seller or seller's

agentPIA03 C212 ITEM NUMBER IDENTIFICATION X

7140 an..35 Item number7143 an..3 Item number type, coded1131 an..3 Code list qualifier3055 an..3 Code list responsible agency, coded

PIA04 C212 ITEM NUMBER IDENTIFICATION X7140 an..35 Item number7143 an..3 Item number type, coded1131 an..3 Code list qualifier3055 an..3 Code list responsible agency, coded




Segment Group 15PIA - Additional Product ID

PIA Notes

1. DE 7143 ITEM NUMBER TYPE, CODED'VP' Vendor's (seller's) part number‘EC’ Engineering change


Segment Group 15QTY - Quantity

Function: To give the despatch quantity.

Usage: R1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationQTY01 C186 QUANTITY DETAILS M

6063 an..3 Quantity qualifier M ‘12’ Despatch quantity6060 n..15 Quantity M6411 an..3 Measure unit qualifier O ‘PCE’ Piece


Segment Group 16

Function: A segment group to specify identifying numbers and dates of previous documents associatedwith the item being described.

Usage: A..5

Remarks: References are normally used at this level

SEG NAME REQDES

MAXUSE

LOOP REPEAT



Segment Group 16RFF - Reference

Function: To specify identifying numbers associated with the item.

Usage: M1

Remarks: Where references do not apply to the whole message they must appear here.

Field # Ref. Rep. Field Usage TI UtilisationRFF01 C506 REFERENCE M

1153 an..3 Reference qualifier M See Note 11154 an..35 Reference number R1156 an..6 Line number O4000 an..35 Reference version number X

RFF Notes

1. DE 1153 REFERENCE QUALIFIER'ON' Order number (purchase)'PK' Packing list number'VN' Order number (vendor)


Segment Group 16UNT - Message Trailer

Function: To end and check the completeness of a message.

Usage: M1

Remarks:

Field # Ref. Rep. Field Usage TI UtilisationUNT01 0074 n..6 NUMBER OF SEGMENTS IN

A MESSAGEM See Note 1

UNT02 0062 an..14 MESSAGE REFERENCENUMBER

M See Note 2

UNT Notes

1. DE 0074 NUMBER OF SEGMENTS IN A MESSAGECount of all segments in the message, UNH and UNT included.

2. DE 0062 MESSAGE REFERENCE NUMBERMust be the same reference number as in DE0062 of the UNH segment of this message.


Example

UNH+1+DESADV:1:921:UN:ED3'

BGM+351+1205393+9' Despatch Advice - OriginalDTM+137:960718:101' Document DateMEA+WT+AAD+KGM:15' Total WeightMEA+CT+SQ+NMP:1' Number of Cartons to be deliveredRFF+AWB:1205393' Waybill Number

NAD+DP+GA/ERA/DEL::92++COMPANY ABC Customer - Delivery Party IDNAD+SE+GBTXI.TXI002::92++TEXAS INSTRUMENTS' Seller Id

TDT+20++SUR++CARRIER XYZ' Carrier mode, and ID

LOC+5'DTM+11:960716:101' Despatch DateLOC+7'DTM+17:960719:101' Expected Delivery date (Dock Date)

CPS+1' First Package (Item)PAC+1++BX'PCI+17'GIN+ML+EC412219' TI Box NumberLIN+1++RYT3252001/2C:BP::92' Buyer s Part NumberPIA+1+SN74ABTH18502APMR:VP::91' TI Part NumberQTY+12:2000:PCE' Quantity DespatchedRFF+PK:003943018' TI Packlist NumberRFF+ON:IPG046042102:11' Customer PO Number & ItemRFF+VN:001335829:00001' TI Sales Order Number & Item

CPS+2' Second Package (Item)PAC+1++BX'PCI+17'GIN+ML+EC412219' TI Box NumberLIN+2++RYT3066011/C:BP::92' Buyer s Part NumberPIA+1+SN74HC573ADWR:VP::91' TI Part NumberQTY+12:6000:PCE' Quantity DespatchedRFF+PK:003943241' TI Packlist NumberRFF+ON:IPG045931801:9' Customer PO Number & ItemRFF+VN:001335828:00001' TI Sales Order Number & Item


Example (continued)

CPS+3' Third Package (Item)PAC+1++BX'PCI+17'GIN+ML+EC412219' TI Box NumberLIN+3++RYT3062007/C:BP::92' Buyer s Part NumberPIA+1+SN74HC04DR:VP::91' TI Part NumberQTY+12:7500:PCE' Quantity DespatchedRFF+PK:003944985' TI Packlist NumberRFF+ON:IPG045066204:7' Customer PO Number & ItemRFF+VN:001338562:00001' TI Sales Order Number & Item

CPS+4' Fourth Package (Item)PAC+1++BX'PCI+17'GIN+ML+EC412219' TI Box NumberLIN+4++RYT1096042/1C:BP::92' Buyer s Part NumberPIA+1+SN75175DR:VP::91' TI Part NumberQTY+12:2500:PCE' Quantity DespatchedRFF+PK:003945209' TI Packlist NumberRFF+ON:IPG036644023:3' Customer PO Number & ItemRFF+VN:001338561:00001' TI Sales Order Number & Item

UNT+54+1' Number of segments - UNH to UNT