MYER€¦ · structure and use is in alignment with the GS1 Australia (GS1AU) General Merchandise Harmonised Guide. For any information regarding EANCOM® or this MIG, please contact:

Myer Message Implementation Guideline

Myer Despatch Advice V1.5.1 November 2016 i Prepared by GS1 Australia

MYER

Message Implementation Guideline

- DESADV

GS1AU General Merchandise Harmonised Guideline

(Based on the EANCOM 2002 Guideline using

UN/EDIFACT Directory D01B- 2012 Edition)

November 2016


Myer Despatch Advice V1.5.1 November 2016 2 Prepared by GS1 Australia

1. Introduction ................................................................................................................................... 3

2. Disclaimer ...................................................................................................................................... 4

3. Change Control ............................................................................................................................. 4

4. Reading this Document ................................................................................................................ 5

5. Application of DESADV within Myer ........................................................................................... 7

6. Summary: Data Content ............................................................................................................... 8

7. Message Sample ......................................................................................................................... 12

8. DESADV: Despatch Advice Message ........................................................................................ 15



1. Introduction This document contains the Message Implementation Guidelines (MIG) for the Myer Despatch Advice message, it should be read in conjunction with any appropriate terms and conditions of trade between the trading partners. This Electronic Data Interchange (EDI) MIG is based on GS1 International’s EANCOM® 2002 Guideline (2012 Edition) using UN/EDIFACT Directory D.01B. The structure and use is in alignment with the GS1 Australia (GS1AU) General Merchandise Harmonised Guide. For any information regarding EANCOM® or this MIG, please contact: Brendon Johnson Senior Advisor, Consulting

GS1 Australia

Access Corporate Park Unit 100, 45 Gilby Road Mt Waverley, VIC 3149 Locked Bag 10 Oakleigh VIC 3166

E-mail address: [email protected] Internet Web Site: www.gs1au.org For Myer related questions please contact: Myer EDI and Supply Chain Team 1300 667 007 – Option 6, then option 2 [email protected] http://myersupplier.myer.com.au In addition, Myer use the following EDI addresses for sending/receiving EDIFACT documents Production: 9313938000525 (default) 9313938000679 (used by some trading partners) A typical “production” interchange will therefore look like so:

UNB+UNOA:3+9312345000001:ZZ+9313938000525:ZZ+060701:0811+100++++1 Testing / Accreditation: 9313938000877

mailto:[email protected]



Please note that in addition to the test EDI address, test messages sent and received by Myer will make use of the Test Indicator. This appears in the last position of the UNB segment as below:

UNB+UNOA:3+9312345000001:ZZ+9313938000877:ZZ+160728:0811+100++++1++1' Please note that Myer B2B systems will automatically respond to all inbound EDI documents with a Functional Acknowledgment (CONTRL) message.

2. Disclaimer Every possible effort has been made to ensure that the information and specifications in this document are correct; however GS1 Australia expressly disclaims liability for any errors. In addition, no warranty or representation is made that this document will not require modification due to developments in new business practice, technology, changes, omissions or additions.

3. Change Control

Date Version Comments

15/07/2014 1.00 Initial Draft - complete document

21/07/2014 1.1 Release version

30/07/2014 1.2 Merged document, with Preamble

25/11/2014 1.3 Added clause for Final Flag

26/03/2015 1.4 Final changes for release

26/07/2016 1.5 Added changes for Shipping Reference Number

18/11/2016 1.5.1 Minor revisions



4. Reading this Document A UN/EDIFACT (ISO 9735) file is called an “interchange”. This is the EDI terminology. The interchange is made up of segments, which is also an EDI term equivalent to the term “record”. An interchange starts with the interchange header segment “UNB” and terminates with the interchange trailer segment “UNZ”. Within the UNB – UNZ envelope are the segments that comprise the electronic EDI business messages themselves. Each business message begins with the header “UNH” segment and terminates with the trailer “UNT” segment. In between the message header and trailer are the user segments containing the business data.

Sample below1:

UNB (start of interchange)

UNH (start of first business message) ……..user segments UNT (end of first business message) UNH (start of second business message) ……..user segments UNT (end of second business message)

UNZ (end of interchange) Segments are made up of one or more data elements. Each data element in a segment is separated by a plus (+) symbol. A data element can be made up of components, which are separated from each other by a colon (:). If a data element has multiple components, it becomes a composite element. Segments are terminated by the apostrophe ('). See data stream examples in the sample message below, and the segment definitions detailed further in the MIG. UN/EDIFACT segments are given a Base Status, whilst the elements belonging to the segment are given Base Attributes. Base Status/Attributes:

M - Mandatory: this segment/element must always be sent2

C - Conditional: this segment/element may be sent, see User Status/User Attributes (below)

1 This Message Implementation Guideline (MIG) does not include the specifications for the interchange segments (UNB & UNZ) as typically they are generated automatically and contain the

addressing data required to deliver the interchange across the communications medium being used to exchange messages between trading partners. Many users use their GS1 company Global

Location Number (GLN) for addressing purposes.

2 Note that a segment with status “M” may occur in a group with status “C”. If the group is not used, the segment is not required, however if the group is used the segment must be provided.

Similarly with data elements, if a composite element is not required, then the components inside the composite element are not required, however if the composite element is provided, the base

attributes for the components takes effect.



This Message Implementation Guideline (MIG):

Only those segments in the standard message to be used in this MIG are specified, any segments not used have been omitted for readability. Within the detailed specification of each segment, all data elements are identified, even if they are not used, as placement of data elements within a segment is critical. The User Status/Attribute (see below) will indicate whether a particular segment or element is sent or not. User Status/Attributes: M - Mandatory: Base Status/Attribute is mandatory so user status must also be mandatory R - Required: Base Status/Attribute is Conditional, but for this MIG and its use within Myer EDI implementations it must always be sent D - Dependent: must or may be sent where stated conditions apply

Note: For the following Segments/Elements, the condition applicable to the "Dependent" status is: ' Not yet ratified for inclusion in the GS1 Australia General Merchandise MIG, use currently to restricted to as required'. It is anticipated the segments and elements will be included in the next update to the Harmonised MIG. - ALI Segment - TDT/LOC segment - LIN/ Sub line composite element - MEA segment at LIN level It may be advisable to seek advice and clarification before using these segments/elements. Segments, Elements and Codes noted as "Subject to Work Request Approval" are available for use but as yet have not been formally included into the harmonised Message Guide.

O - Optional: may be sent. If sent and not used by Myer, it will be ignored and not generate processing errors. X - Not Used: never sent

Notation:

Wherever possible notes have been inserted into the MIG content (shown as shaded) to clarify how the data is to be used, as well as any business rules to follow. Where applicable, reference to Work Request submission (for inclusion in the Harmonised guide) is attached to specific segments, elements and/or code values. Most segments have a shaded block of notes at the beginning of the segment. Much of this is automatically generated text from the EANCOM superset on which this MIG is based. In some cases there may be descriptions of data elements or code usage that are not available for use in this MIG.



5. Application of DESADV within Myer Myer will receive a number of Despatch Advice (DESADV) types based on the Implementation Guide, with the key variations in message content Identified below for each message type (for details, refer to the segment details in DESADV guide):

For all Despatch Advice messages in:

A DESADV is required in response to all Myer Orders

A DESADV is required per Order; a single DESADV cannot reference more than one Order

The Myer Order number is required at the header level together with its creation date/time

The Despatch Advice number and date/time sent are required

Estimated delivery date is required

At the shipment level (level 1): o Number of cartons or pallets is required

At the Store Level (level 3): o The Myer internal store number is required o Pallets details are optional, however if details are provided, SSCC label details must also be provided

At the Carton Level (level 5): o SSCC label details are required

At the Item Level: o GTIN details are required o Quantity shipped is required

Additional fields for Despatch Advice messages in response to Customer Orders (Delivered to Myer):

Despatch or Delivery date is required

The Customer Order number is required

Customer name details are required Additional fields for Despatch Advice messages in response to Customer Orders (Direct)

The Despatch or Delivery date is required

The Carrier’s consignment note is required

The shipment reference number is required

The Customer Order number is required

Carrier name is required

Customer name details are required

If using BYO Carrier (i.e. not using Myer’s Carrier), the full tracking URL is required



6. Summary: Data Content This section contains an overview of the content and structure of the DESADV message as an aid to understanding. It should be noted that while this is indicative of the content and structure of a DESADV message, the detailed implementation guideline that forms the majority of the document is the only authoritative source of content and structure. In the event of a discrepancy between the information in this section and the information in the detailed implementation guideline, the detailed implementation guideline should prevail.

Harmonised

Segment Element Function GM Definition Usage

Industry

MIG

EANCOM

D.01B

UNH 0062 Message reference no. U

0065 Message type ID DESADV

0052 Message type version No D

0054 Message type release No 01B

0051 Controlling agency UN

0057 Association assigned code EAN007

BGM 1001 Document name 351 Despatch Advice

YA5 Cross-docking despatch Indicates goods will be delivered store-ready to the DC

3055 Code list agency 9 GS1 codes Indicates the above codes are from a GS1 list

1004 Message number U Document numbers Despatch Advice number

1225 Function 7 Duplicate Only used if Myer request a retransmit

9 Original All new Despatch Advice messages will provide “Original”

DTM 2005 Date/Time qualifier 11 Despatch date/time For DSV only, when Order has DTM+38 (send by date)

17 Estimated delivery date/time For DSV only, when Order has DTM+2 (deliver on date)

137 Document date/time Required for all DESADV

191 Expected delivery date/time Required for all DESADV except DSV

2380 Date/Time period U Date value

2379 Date/Time qualifier 102 CCYYMMDD Indicates date value is provided in the format CCYYMMDD



203 CCYYMMDDHHMM Indicates date value is provided in the format CCYYMMDDHHMM

ALI 4183 Special conditions coded 164 Shipment completes Order Indicates no further DESADV messages are expected

165 Split shipment Indicates the Order will be fulfilled across multiple DESADV messages and shipments

RFF 1153 Reference qualifier CN Carriers Reference Number The carrier consignment note number

ON Order number The Myer Purchase Order number

SRN Shipment reference number Number assigned to track the shipment, e.g. Temando reference number

UO Ultimate customer's Order number

The Myer-generated Customer Order number

1154 Reference number U

DTM 2005 Date/Time qualifier 171 Reference date/time Myer Order number; only used where RFF.1153 = “ON”

2380 Date/Time period U

2379 Date/Time period format 203 CCYYMMDDHHMM Indicates the date-time value provided contains date and time value of the original Order, in the format CCYYMMDDHHMM

NAD 3035 Party qualifier BY Buyer Required for all DESADV messages

CA Carrier Required for all DSV DESADV messages

ST Ship to Required for all Non-DSV DESADV messages

SU Supplier Required for all DESADV; value provided is the internal vendor number

assigned by Myer in the original Order

UD Ultimate customer Required for all DSV DESADV messages

TF Source of information Only provided for DSV Orders where Supplier uses own carrier for shipping, and tracking URL does not pertain to the carrier

3039 Party ID identification U

3055 Code list agency 9 GS1 codes Indicates the provided identification value (NAD.3039) is from a GS1 list

92 Assigned by buyer Required by Myer when NAD.3035 = “SU”

3036 Party name U Name Address details, required for DSV Orders only

3036 Party name U Name Additional address details for DSV Orders

CTA 3139 Contact function code IC Information contact Indicates following COM segment contains URL used to track delivery of order

COM 3148 Communication address identifier U

3155 Communication address code qualifier

AO Track delivery URL Optional for DSV Orders; contains full URL to track the delivery



CPS 7164 Hierarchical ID number U Unique number to identify consignment segment

7166 Parent ID U Reference to higher level segment identified (CPS.7164) for Outer and Inner consignments

7075 Packaging level 1 Inner Indicates carton level

3 Outer Indicates store or warehouse level

5 Shipment Indicates the full shipment; highest level of order

PAC 7224 Number of packages U

7065 Type of packaging U

3055 Responsible agency 9 GS1 codes Indicates the above codes are from a GS1 list

MEA 6311 Measurement application identifier

PD Physical dimensions If used, the measurements provided in the segment apply to the CPS loop unit

6313 Dimension coded AAB Unit gross weight Gross weight in kilograms for the unit

ABJ Volume Volume of the unit in litres

6411 Measure unit qualifier KGM Kilogram Paired with MEA.6313 = “AAB”

LTR Litre Paired with MEA.6313= ”ABJ”

6314 Value U

PCI 4233 Marking instructions 33E Marked with SSCC The SSCC number applied to the package

IEN Package identity number If provided details the Temando article number

GIN 7405 Identity number qualifier AW Serial shipping container code Identifies the SSCC number; provided when PCI.4233= “33E”

ML Marking label Associated with PCI.4233 = ”IEN”, to carry the Article number

7402 Identity number U

LIN 1082 Line item number U Unique value to identify each line item

7140 Item number U 13-digit GTIN of item being shipped

7143 Item number type, coded SRV Value is GTIN

QTY 6063 Quantity qualifier 12 Despatch quantity Total quantity of the item shipped

6060 Quantity U

LOC 3227 Place location qualifier 8 Place of destination Provided in XDOCK DESADV to identify the store or warehouse receiving the shipment

3225 Place location identification U

3055 Code list responsible agency 92 Assigned by buyer Indicates place location identification (LOC.3225) is a Myer-allocated store or DC number



CNT 6069 Control qualifier 1 Total of all QTY segments Total item count for the whole Despatch Advice

2 Number of line items Number of LIN segments in Despatch Advice

6066 Control value U

UNT 0074 Number of message segments U Count of segments Total count of segments in Despatch Advice

0062 Message reference number U Message number Message reference, matching UNH.0072



7. Message Sample

Merchandise Order – XDock to Multiple Stores

Merchandise Order – Direct to Store

DSV – Using Myer Carrier UNA:+.? ' UNB+UNOA:3+9312345000001:ZZ+9313938000525:ZZ+160726:1535+12++++1' UNH+100+DESADV:D:01B:UN:EAN007' BGM+351::9+0036074887+9' DTM+137:201607261535:203' DTM+11:20160728:102' DTM+17:20160729:102' ALI+++164' RFF+ON:CC4500000001D000' DTM+171:201607261130:203' RFF+UO:1580008986' RFF+SRN:XYZ123' RFF+CN:0011223344' NAD+SU+6779999::92' NAD+CA+AUSTRALIA_POST::92++AUSTRALIA_POST' NAD+BY+9313938000525::9' NAD+UD+++John Doe' CPS+1++5' PAC+1++9' CPS+2+1+3' CPS+3+2+1' PCI+33E' GIN+AW+00300370007400036964' LIN+1++9876543210123:SRV' QTY+12:7' LIN+2++9876543210124:SRV' QTY+12:5' LIN+3++9876543210125:SRV' QTY+12:3' LIN+4++9876543210126:SRV' QTY+12:10' LIN+5++9876543210127:SRV' QTY+12:6' LIN+6++9876543210128:SRV' QTY+12:2' CNT+2:6' UNT+35+100' UNZ+1+12'

DSV – Using supplier’s own carrier (BYO Carrier) UNA:+.? ' UNB+UNOA:3+9312345000001:ZZ+9313938000525:ZZ+160726:1535+12++++1' UNH+100+DESADV:D:01B:UN:EAN007' BGM+351::9+0036074887+9'



DTM+137:201607261535:203' DTM+11:20160728:102' DTM+17:20160729:102' ALI+++164' RFF+ON:CC4500000001D000' DTM+171:201607261130:203' RFF+UO:1580008986' RFF+SRN:XYZ123' RFF+CN:0011223344' NAD+SU+6779999::92' NAD+CA+UPS::92++UPS' CTA+IC' COM+https?://www.ups.com/WebTracking/??tracknum=XYZ123:AO' NAD+BY+9313938000525::9' NAD+UD+++John Doe' CPS+1++5' PAC+1++9' CPS+2+1+3' CPS+3+2+1' PCI+33E' GIN+AW+00300370007400036964' LIN+1++9876543210123:SRV' QTY+12:7' LIN+2++9876543210124:SRV' QTY+12:5' LIN+3++9876543210125:SRV' QTY+12:3' LIN+4++9876543210126:SRV' QTY+12:10' LIN+5++9876543210127:SRV' QTY+12:6' LIN+6++9876543210128:SRV' QTY+12:2' CNT+2:6' UNT+37+100' UNZ+1+12'

DSV – Using supplier’s own carrier (BYO Carrier) where the tracking URL does not pertain to the carrier UNA:+.? ' UNB+UNOA:3+9312345000001:ZZ+9313938000525:ZZ+160726:1535+12++++1' UNH+100+DESADV:D:01B:UN:EAN007' BGM+351::9+0036074887+9' DTM+137:201607261535:203' DTM+11:20160728:102' DTM+17:20160729:102' ALI+++164' RFF+ON:CC4500000001D000' DTM+171:201607261130:203' RFF+UO:1580008986' RFF+SRN:XYZ123' RFF+CN:0011223344' NAD+SU+6779999::92' NAD+CA+AUSTRALIA_POST::92++AUSTRALIA_POST' NAD+TF+TrackingService::92' CTA+IC' COM+https?://www.ups.com/WebTracking/??tracknum=XYZ123:AO'



NAD+BY+9313938000525::9' NAD+UD+++John Doe' CPS+1++5' PAC+1++9' CPS+2+1+3' CPS+3+2+1' PCI+33E' GIN+AW+00300370007400036964' LIN+1++9876543210123:SRV' QTY+12:7' LIN+2++9876543210124:SRV' QTY+12:5' LIN+3++9876543210125:SRV' QTY+12:3' LIN+4++9876543210126:SRV' QTY+12:10' LIN+5++9876543210127:SRV' QTY+12:6' LIN+6++9876543210128:SRV' QTY+12:2' CNT+2:6' UNT+38+100' UNZ+1+12'



8. DESADV: Despatch Advice Message

Introduction:

This specification provides the definition of the GS1AU Harmonised DESADV message to be used in EDI

between trading partners involved in the Australian General Merchandise Sector.

The Harmonised MIG will be the basis for all trading partners in the sector, while individual trading hubs may

define their own implementation requirements, such implements will be a subset of the harmonised guide, with all

segment, element and code values having identical definitions and interpretations. In general, it is anticipated each

trading hub will support the full implementation guide by simply ignoring any segments, elements or code values

(other than Mandatory and Required items) which are not required for their business needs.

Segments flagged as Not Recommended are in use by Sector participants but have not yet been ratified by the

GS1AU working group for inclusion in the Harmonised MIG definitions. Elements and code values will similarly

be flagged as Not Recommended with some elements and code values submitted to global process for inclusion in

EANCOM specifications.

Pos. Seg. Req. Group Notes and

No. ID Name Des. Max.Use Repeat Comments

M 0010 UNH Message header M 1 M 0020 BGM Beginning of message M 1 M 0030 DTM Date/time/period M 10 O 0040 ALI Additional information C 5 O 0080 Segment Group 1: RFF-DTM C 10 M 0090 RFF Reference M 1 O 0100 DTM Date/time/period C 1

O 0110 Segment Group 2: NAD C 99 M 0120 NAD Name and address M 1 O 0170 Segment Group 4: CTA-COM C 10 M 0180 CTA Contact information M 1 M 0190 COM Communication contact M 5

O 0390 Segment Group 10: CPS-SG11-SG17 C 9999 M 0400 CPS Consignment packing sequence M 1 O 0430 Segment Group 11: PAC-MEA-SG13 C 9999 M 0440 PAC Package M 1 O 0450 MEA Measurements C 10 O 0500 Segment Group 13: PCI-SG15 C 1000 M 0510 PCI Package identification M 1 O 0570 Segment Group 15: GIN C 99 M 0580 GIN Goods identity number M 1

O 0650 Segment Group 17: LIN-QTY-SG20 C 9999 M 0660 LIN Line item M 1 O 0700 QTY Quantity C 10 O 0910 Segment Group 20: LOC-QTY C 100 M 0920 LOC Place/location identification M 1 O 0950 QTY Quantity C 10

O 1140 CNT Control total C 5 M 1150 UNT Message trailer M 1



Segment: UNH Message header

Position: 0010

Group: Level: 0

Usage: Mandatory

Max Use: 1

Purpose: A service segment starting and uniquely identifying a message. The message type code

for the Despatch Advice message is DESADV.

Note: Despatch Advice messages conforming to this document must contain the

following data in segment UNH, composite S009:

Data element Value 0065 DESADV

0052 D

0054 01B

0051 UN

Dependency Notes:

Semantic Notes:

Comments:

Notes: Despatch Advice Heading Section

This segment is used to head, identify and specify a message.

Elements 0065, 0052, 0054 and 0051: Indicate that the message is a UNSM Despatch

Advice message based on the D.01B directory, under the control of the United Nations.

Example:

UNH+100+DESADV:D:01B:UN:EAN007'

Data Element Summary

Data Component

Element Element Name Attributes

M 0062 MESSAGE REFERENCE NUMBER M an..14

Unique message reference assigned by the sender.

Sender’s unique message reference. Sequence number of the messages in the

interchange. DE 0062 in the UNT will be identical. Sender generated. M S009 MESSAGE IDENTIFIER M

Identification of the type, version etc. of the message being interchanged.

M 0065 Message type M an..6

Code identifying a type of message and assigned by its controlling agency.

DESADV Despatch advice message.

A code to identify the despatch advice message.

GS1 Description:

A message specifying details for goods despatched or

ready for despatch under agreed conditions. The United

Nations Despatch Advice Message serves both as a

specification for Delivery Despatch Advice and also as

a Returns Despatch Advice message. M 0052 Message version number M an..3

Version number of a message type.

D Draft version/UN/EDIFACT Directory.

Message approved and issued as a draft message (valid

for directories published after March 1993 and prior to

March 1997). Message approved as a standard message

(valid for directories published after March 1997). M 0054 Message release number M an..3

Release number within the current message type version number (0052).

01B Release 2001 – B.



Message approved and issued in the second 2001 release

of the UNTDID (United Nations Trade Data Interchange

Directory). M 0051 Controlling agency M an..2

Code to identify the agency controlling the specification, maintenance and

publication of the message type. UN UN/CEFACT

United Nations Centre for Trade Facilitation and

Electronic Business (UN/CEFACT). GS1 Description:

UN Economic Commission for Europe (UN/ECE),

Committee on the Development of Trade (TRADE),

Working Party on Facilitation of International Trade

Procedures (WP.4). R 0057 Association assigned code C an..6

A code assigned by the association responsible for the design and maintenance

of the message type concerned, which further identifies the message. Indicates that the message is the EANCOM version 007 of the UNSM

Despatch Advice. EAN007 GS1 version control number (GS1 Code)

X 0068 COMMON ACCESS REFERENCE C an..35

Reference serving as a key to relate all subsequent transfers of data to the same

business case or file. X S010 STATUS OF THE TRANSFER C

Statement that the message is one in a sequence of transfers relating to the

same topic. X 0070 Sequence of transfers M n..2

Number assigned by the sender indicating the numerical sequence of one or

more transfers. X 0073 First and last transfer C a1

Indication used for the first and last message in a sequence of the same type of

message relating to the same topic.



Segment: BGM Beginning of message

Position: 0020

Group: Level: 0

Usage: Mandatory

Max Use: 1

Purpose: A segment for unique identification of the Despatch Advice document, by means of its

name and number.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is used to indicate the type and function of the message and to transmit the

identifying number.

All references other than the document number DE 1004 are to be put in the RFF

segment.

Example:

BGM+351::9+0036074887+9'


Data Component


R C002 DOCUMENT/MESSAGE NAME C

Identification of a type of document/message by code or name. Code preferred.

R 1001 Document name code C an..3

Code specifying the document name.

351 Despatch advice.

Document/message by means of which the seller or

consignor informs the consignee about the despatch of

goods. YA5 Intermediate handling cross docking despatch advice

(EAN Code). Document by means of which the supplier or consignor

informs the buyer, consignee or the distribution centre

about the despatch of goods needing intermediate

handling. X 1131 Code list identification code C an..17

Code identifying a user or association maintained code list.

D 3055 Code list responsible agency code C an..3

Code specifying the agency responsible for a code list.

Only used if EAN code values are used in element 1001.

9 GS1 (Formally EAN International), an organisation of

GS1 Member Organisations, which manages the GS1

System. GS1 International, based in Belgium, is an organization of

GS1 Member Organizations that jointly manages the

EAN.UCC System with the Uniform Code Council. X 1000 Document name C an..35

Name of a document.

R C106 DOCUMENT/MESSAGE IDENTIFICATION C

Identification of a document/message by its number and eventually its version

or revision. R 1004 Document identifier C an..35

To identify a document.

Despatch Advice number assigned by the document sender.

It is recommended that the length of the document number be restricted to a

maximum of 17 characters.



X 1056 Version identifier C an..9

To identify a version.

X 1060 Revision identifier C an..6

To identify a revision.

R 1225 MESSAGE FUNCTION CODE C an..3

Code indicating the function of the message.

The message function code is a critical data element in this segment. It applies

to all data indicated in the message. Consequently, one separate message has to

be provided per type of function required. The following definitions apply for

the restricted codes:

7 = Duplicate - A retransmission involving the same parties, on the specific

request of the receiver.

9 = Original - An original transmission of a Despatch Advice.

7 Duplicate

The message is a duplicate of a previously generated

message. 9 Original

Initial transmission related to a given transaction.

X 4343 RESPONSE TYPE CODE C an..3

Code specifying the type of acknowledgment required or transmitted.



Segment: DTM Date/time/period

Position: 0030

Group: Level: 1

Usage: Mandatory

Max Use: 10

Purpose: Date/time/period related to the whole message. The DTM segment must be specified at

least once to identify the Despatch Advice date.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is used to specify the date of the Despatch Advice or any dates related to

the delivery of goods.

DE 2005: Identification of the 'Document/message date/time' (code value 137) is

mandatory in an EANCOM message.

Example:

DTM+137:201607261535:203'


Data Component


M C507 DATE/TIME/PERIOD M

Date and/or time, or period relevant to the specified date/time/period type.

M 2005 Date or time or period function code qualifier M an..3

Code qualifying the function of a date, time or period.

11 Despatch date and/or time.

(2170) Date/time on which the goods are or are expected

to be despatched or shipped. Implemented by Myer for Drop Ship Vendors , will

only be used when Order has DTM+38 (send by date) 17 Delivery date/time, estimated.

Date and/or time when the shipper of the goods expects

delivery will take place. Implemented by Myer for Drop Ship Vendors , will

only be used when Order has DTM+2 (deliver on date) 137 Document/message date/time.

(2006) Date/time when a document/message is issued.

This may include authentication. Required for all Myer Despatch Advice messages, with

format as DE2379=203 191 Delivery date/time, expected.

Date/time on which goods are expected to be delivered.

To be used for all Despatch Advice messages, except

DSV Orders R 2380 Date or time or period value C an..35

The value of a date, a date and time, a time or of a period in a specified

representation. R 2379 Date or time or period format code C an..3

Code specifying the representation of a date, time or period.

102 CCYYMMDD

Calendar date including time with minutes: C=Century;

Y=Year; M=Month; D=Day. 203 CCYYMMDDHHMM


Y=Year; M=Month; D=Day; H=Hour; M=Minutes.



Segment: ALI Additional information

Position: 0040

Group: Level: 1

Usage: Conditional (Optional)

Max Use: 5

Purpose: A segment indicating that the message is subject to special conditions due to origin,

customs preference or commercial factors.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is used to indicate special conditions with regard to the shipment.

As the codes supported by Myer are mutually exclusive, there will only ever be 1

occurrence of the ALI segment per message. GS1 AU Usage: It is recommended that the ALI segment be implemented with a single

occurrence of ALI.4183 in all cases. The ALI segments is thus repeated if multiple values

are required to be sent.

While the implementation guide may show 2 occurrences, this has been included for

migration purposes only and not the recommended implementation option.

Example:

ALI+++164'


Data Component


X 3239 COUNTRY OF ORIGIN NAME CODE C an..3

Code specifying the name of the country of origin.

X 9213 DUTY REGIME TYPE CODE C an..3

Code specifying a type of duty regime.

O 4183 SPECIAL CONDITION CODE C an..3

Code specifying a special condition.

NOTE:

Only to be used under circumstances where agreement with Myer has been

arranged. All other orders should not populate this DE.

164 Shipment completes order.

There will be no further shipments for this order as it is

considered complete. 165 Split shipment.

Subsequent shipment(s) will arrive for this order as it has

been split over more than one shipment. X 4183 SPECIAL CONDITION CODE C an..3


X 4183 SPECIAL CONDITION CODE C an..3








Group: RFF Segment Group 1: Reference

Position: 0080

Group: Level: 1


Max Use: 10

Purpose: A group of segments giving references where necessary, their dates relating to the

whole message, e.g. contact number.

Notes: Used by Myer to specify the Order number and other references related to the whole

Despatch Advice.

Segment Summary

Pos. Seg. Req. Max. Group:

No. ID Name Des. Use Repeat M 0090 RFF Reference M 1 O 0100 DTM Date/time/period C 1



Segment: RFF Reference

Position: 0090 (Trigger Segment)

Group: Segment Group 1 (Reference) Conditional (Optional)

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: A segment for referencing documents relating to the whole despatch advice message,

e.g. Purchase Orders, delivery instructions, import/export license.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is used to provide references that apply to the whole transaction.

Example:

RFF+ON:CC4500000001D000'


Data Component


M C506 REFERENCE M

Identification of a reference.

M 1153 Reference code qualifier M an..3

Code qualifying a reference.

CN Carrier's reference number.

Reference number assigned by carrier to a consignment.

Implemented by Myer; contains the Carrier’s

consignment note number. ON Order number (buyer).

Reference number assigned by the buyer to an order.

Required by Myer for all Despatch Advice messages

SRN Shipment reference number

Reference number assigned to a shipment.

GS1 Description:

Reference number assigned by a consignor to a

particular shipment for his own purposes or for those of

the consignee. Implemented by Myer in Customer Orders (Direct)

Despatch Advices where the Myer carrier is used, this

will be the Temando reference number, used by the

customer for tracking delivery. UO Ultimate customer's order number

The originator's order number as forwarded in a sequence

of parties involved. Required by Myer in all Customer Order (Direct)

Despatch Advices. R 1154 Reference identifier C an..70

Identifies a reference.

X 1156 Document line identifier C an..6

To identify a line of a document.

X 4000 Reference version identifier C an..35

To identify the version of a reference.

X 1060 Revision identifier C an..6

To identify a revision.



Segment: DTM Date/time/period

Position: 0100

Group: Segment Group 1 (Reference) Conditional (Optional)

Level: 2


Max Use: 1

Purpose: Date/time/period from the referred document.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is used to specify dates relating to the references given in the previous RFF

segment.

Example:

DTM+171:201607261130:203' Myer only require this DTM segment with the RFF segment where DE1153=ON


Data Component


M C507 DATE/TIME/PERIOD M

Date and/or time, or period relevant to the specified date/time/period type.

M 2005 Date or time or period function code qualifier M an..3

Code qualifying the function of a date, time or period.

171 Reference date/time

Date/time on which the reference was issued.

Required by Myer for all Despatch Advice messages, to

carry the Purchase Order date. R 2380 Date or time or period value C an..35

The value of a date, a date and time, a time or of a period in a specified

representation. R 2379 Date or time or period format code C an..3

Code specifying the representation of a date, time or period.

203 CCYYMMDDHHMM


Y=Year; M=Month; D=Day; H=Hour; M=Minutes.



Group: NAD Segment Group 2: Name and address

Position: 0110

Group: Level: 1


Max Use: 99

Purpose: A group of segments identifying names, addresses, locations, and required supporting

documents relevant to the whole Despatch Advice.

Notes:

Segment Summary


No. ID Name Des. Use Repeat M 0120 NAD Name and address M 1



Segment: NAD Name and address


Group: Segment Group 2 (Name and address) Conditional (Optional)

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: A segment for identifying names, addresses, and their functions relevant to the whole

Despatch Advice. Identification of the parties involved is recommended for the

Despatch Advice message, and is to be given in the NAD segment.

It is recommended that where possible, only the coded form of the party ID should be

specified, e.g. the buyer and seller are known to each other, thus only the coded ID is

required. The consignee or delivery address may vary and would have to be clearly

specified, preferably in structured format.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is used to identify the trading partners involved in the Despatch Advice

message. Identification of the supplier and buyer is recommended in the Despatch

Advice. Additionally, the shipper and delivery party may be identified when different

from the supplier or buyer.

The delivery address in NAD is the main delivery address valid for all line items. It can

be overridden at line level by the use of the Segment Group 20 (LOC-NAD-DTM-QTY)

in which multiple delivery addresses can be specified for split deliveries.

Example:

NAD+SU+6779999::92'

NAD+CA+AUSTRALIA_POST::92++AUSTRALIA_POST'

NAD+BY+9313938000877::9'


Data Component


M 3035 PARTY FUNCTION CODE QUALIFIER M an..3

Code giving specific meaning to a party.

BY Buyer

Party to whom merchandise and/or service is sold.

Required by Myer for all Despatch Advice messages.

CA Carrier

(3126) Party undertaking or arranging transport of goods

between named points. Required by Myer for all DSV Despatch Advices.

ST Ship to

Identification of the party to where goods will be or have

been shipped. Required by Myer for all Despatch Advice messages

except for DSV. SU Supplier

Party who supplies goods and/or services.

GS1 Description:

Party which provides service(s), manufactures or

otherwise has possession of goods, and consigns or

makes them available in trade. Required by Myer for all Despatch Advice messages.

Value provided in NAD.3039 will be the Myer-assigned

vendor number as sent in the Purchase Order. TF Source of Information

To specify that the party is the source of information.



Used by Myer for Suppliers utilising BYO Carrier.

Indicates that following CTA/COM segments (Segment

Group 4) will hold the Tracking URL, however this

URL does not relate to a specific Carrier.

UD Ultimate customer

The final recipient of goods.

Required by Myer for all DSV Despatch Advice

messages. R C082 PARTY IDENTIFICATION DETAILS C

Identification of a transaction party by code.

This composite element is required by Myer where NAD.3035 = “ST”, “BY”

& “SU”. M 3039 Party identifier M an..13

Code specifying the identity of a party.

For identification of parties it is recommended to use the GLN, in the format of

13-digits, all numerical. X 1131 Code list identification code C an..17


R 3055 Code list responsible agency code C an..3




System GS1 International, based in Belgium, is an organization of


EAN.UCC System with the Uniform Code Council. 92 Assigned by buyer or buyer's agent

Codes assigned by a buyer or buyer's agent.

Required by Myer when NAD.3035 = “SU”.

X C058 NAME AND ADDRESS C

Unstructured name and address: one to five lines.

X 3124 Name and address description M an..35

Free form description of a name and address line.

X 3124 Name and address description C an..35








D C080 PARTY NAME C

Identification of a transaction party by name, one to five lines. Party name may

be formatted. Required by Myer where NAD.3035 = “CA” & “UD”. Not expected where

NAD.3035 = “SU”, “ST” & “BY”/ M 3036 Party name M an..35

Name of a party.

Party name in clear text

O 3036 Party name C an..35

Name of a party.

X 3036 Party name C an..35

Name of a party.




Name of a party.


Name of a party.

X 3045 Party name format code C an..3

Code specifying the representation of a party name.

X C059 STREET C

Street address and/or PO Box number in a structured address: one to four lines.

X 3042 Street and number or post office box identifier M an..35

To identify a street and number and/or Post Office box number.

X 3042 Street and number or post office box identifier C an..35






X 3164 CITY NAME C an..35

Name of a city.

X C819 COUNTRY SUB-ENTITY DETAILS C

To specify a part of a country (e.g. county or part of a city).

X 3229 Country sub-entity name code C an..9

Code specifying the name of a country sub-entity.

X 1131 Code list identification code C an..17


X 3055 Code list responsible agency code C an..3


X 3228 Country sub-entity name C an..70

Name of a country sub-entity.

X 3251 POSTAL IDENTIFICATION CODE C an..17

Code specifying the postal zone or address.

X 3207 COUNTRY NAME CODE C an..3

Identification of the name of the country or other geographical entity as defined

in ISO 3166-1.



Group: CTA Segment Group 4: Contact information

Position: 0170

Group: Level: 1


Max Use: 10

Purpose: A group of segments to identify the people, functions, departments and appropriate

numbers to whom communication should be directed.

Notes: Segment group is to be provided when using BYO Carrier, rather than using a Myer

Carrier. The full tracking URL is contained in this group, and must be provided.

Segment Summary


No. ID Name Des. Use Repeat D 0180 CTA Contact information M 1 D 0190 COM Communication contact M 5



Segment: CTA Contact information


Group: Segment Group 4 (Contact information) Conditional (Dependent)

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: A segment to identify the person, function or department to whom communication

should be directed.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is used to identify contact names within the company specified in the NAD

segment.

Myer use: Used for the URL to track the delivery of the order. Provided when NAD.3035

= “TF” or “CA”

Example:

CTA+IC'


Data Component


M 3139 CONTACT FUNCTION CODE C an..3

Code specifying the function of a contact (e.g. department or

person).

For Tracking URL, Myer expects the value of “IC” to be

provided.

X C056 DEPARTMENT OR EMPLOYEE DETAILS C

Code and/or name of a department or employee. Code preferred.

X 3413 Department or employee name code C an..17

Code specifying the name of a department or employee.

X 3412 Department or employee name C an..35

Name of a department or employee.



Segment: COM Communication contact


Group: Segment Group 4 (Contact information) Conditional (Optional)

Level: 1

Usage: Mandatory

Max Use: 5

Purpose: A segment to identify communication types and numbers for the person, function or

department identified in the CTA.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment identifies the communications number and type of communications, for the

person or department identified in the preceding CTA segment.

Myer use: Used for the URL to track the delivery of the order. Provided when NAD.3035

= “TF” or “CA”

Note: EDI syntax tokens, such as “:” and “?” should be correctly escaped using the

escape character defined in the UNA segment, or “?” as a default. Refer to the example

below for details.

Example:

COM+https?://trackingurl.com/track??trackid=12345:AO'


Data Component


D C076 COMMUNICATION CONTACT C

Communication number of a department or employee in a specified channel.

M 3148 Communication address identifier C an..512

To identify a communication address.

Contains the full URL with syntax tokens escaped

M 3155 Communication address code qualifier C an..3

Code qualifying the communication address.

“AO” (Track Delivery URL) qualifier should be used.



Group: CPS Segment Group 10: Consignment packing sequence

Position: 0390

Group: Level: 1


Max Use: 9999

Purpose: A group of segments providing details of all package levels and of the individual

despatched items contained in the consignment. This segment group provides the

capability to give the hierarchical packing relationships. The group defines a logical

top-down order structure. The lowest level package information of the hierarchy is

followed by the detail product information.

Notes: Despatch Advice Detail Section

Segment Summary


No. ID Name Des. Use Repeat M 0400 CPS Consignment packing sequence M 1

0430 Segment Group 11: Package C 9999

0650 Segment Group 17: Line item C 9999



Segment: CPS Consignment packing sequence


Group: Segment Group 10 (Consignment packing sequence) Conditional (Optional)

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying the sequence in which packing of the consignment occurs, e.g.

boxes loaded onto a pallet

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is used to identify the sequence in which packing of the consignment

occurs.

Please refer to the Summary: Data Content section in this document for details on the use

of the CPS segment.

Example:

CPS+1'


Data Component


M 7164 HIERARCHICAL STRUCTURE LEVEL

IDENTIFIER M an..35

To identify a level within a hierarchical structure.

Sequential numbering recommended. Must be unique within the message for

messages sent to Myer

D 7166 HIERARCHICAL STRUCTURE PARENT

IDENTIFIER C an..35

To identify the next higher level in a hierarchical structure.

Required when the packaging level is “Inner” (CPS.7075 = “1”) or Outer

(CPS.7075 = “3”) O 7075 PACKAGING LEVEL CODE C an..3

Code specifying a level of packaging.

1 Inner

Level of packing, if it exists, that is immediately

subordinate to the intermediate packaging level. Used by Myer, typically the carton level

3 Outer

For packed merchandise, outermost level of packaging for

a shipment. Used by Myer, typically the Store or warehouse level

5 Shipment Level

The packaging level being described is the shipment level.

Subject to Work Request approval

Used by Myer as the highest level of packaging



Group: PAC Segment Group 11: Package

Position: 0430


Level: 2


Max Use: 9999

Purpose: A group of segments identifying packaging, physical dimensions, marks and numbers,

quantities, date and time information, handling information and information about

packing at this level.

Notes:

Segment Summary


No. ID Name Des. Use Repeat M 0440 PAC Package M 1 O 0450 MEA Measurements C 10

0500 Segment Group 13: Package identification C 1000



Segment: PAC Package


Group: Segment Group 11 (Package) Conditional (Optional)

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment specifying the number and type of the packages/physical units and the

physical type of packaging for the despatched goods.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment can be used to identify the total number of packages per hierarchical level

identified in the CPS segment, in a shipment. The contents of each package are

subsequently described in the following LIN segment.

Please refer to the 'Structure of the Despatch Advice Message' section in the introduction

for details on the use of the PAC segment.

Example:

PAC+1++CT::9'


Data Component


O 7224 PACKAGE QUANTITY C n..8

To specify the number of packages.

Not used at the Myer Store level (CPS.7075 = “3”)

X C531 PACKAGING DETAILS C

Packaging level and details, terms and conditions.

X 7075 Packaging level code C an..3

Code specifying a level of packaging.

X 7233 Packaging related description code C an..3

Code specifying information related to packaging.

X 7073 Packaging terms and conditions code C an..3

Code specifying the packaging terms and conditions.

O C202 PACKAGE TYPE C

Type of package by name or by code from a specified source.

R 7065 Package type description code C an..17

Code specifying the type of package.

Refer to D.01B Data Element Dictionary for acceptable code values.







System GS1 International, based in Belgium, is an organization of


EAN.UCC System with the Uniform Code Council. X 7064 Type of packages C an..35

Description of the form in which goods are presented.

X C402 PACKAGE TYPE IDENTIFICATION C

Identification of the form in which goods are described.

X 7077 Description format code M an..3

Code specifying the format of a description.



X 7064 Type of packages M an..35


X 7143 Item type identification code C an..3

Coded identification of an item type.

X 7064 Type of packages C an..35


X 7143 Item type identification code C an..3


X C532 RETURNABLE PACKAGE DETAILS C

Indication of responsibility for payment and load contents of returnable

packages. X 8395 Returnable package freight payment responsibility code C an..3

Code specifying the responsibility for the freight payment for a returnable

package. X 8393 Returnable package load contents code C an..3

Code specifying the load contents for a returnable package.



Segment: MEA Measurements

Position: 0450


Level: 3


Max Use: 10

Purpose: A segment specifying physical measurements of the packages/physical units described

in the PAC segment.

Dependency Notes:

Semantic Notes:

Comments:

Notes: Not implemented by Myer

This segment is used to provide measurements relevant to the packaging unit and level

described in the PAC segment.

Example:

MEA+PD+AAB+KGM:12'


Data Component


M 6311 MEASUREMENT PURPOSE CODE QUALIFIER M an..3

Code qualifying the purpose of the measurement.

PD Physical dimensions (product ordered)

Specified measurement dimensions refer to physical

dimensions of a product, material or package. GS1 Description:

The restriction 'product ordered' can be ignored. R C502 MEASUREMENT DETAILS C

Identification of measurement type.

R 6313 Measured attribute code C an..3

Code specifying the attribute measured.

AAB Unit gross weight

[6292] Weight (mass) of goods including packing but

excluding the carrier's equipment. ABJ Volume

The amount of air space taken up by the entity identified

in the 6311 qualifier. GS1 Description:

The usage of this code relates to the cube of air that the

package takes up. X 6321 Measurement significance code C an..3

Code specifying the significance of a measurement.

X 6155 Non-discrete measurement name code C an..17

Code specifying the name of a non-discrete measurement.

X 6154 Non-discrete measurement name C an..70

Name of a non-discrete measurement.

R C174 VALUE/RANGE C

Measurement value and relevant minimum and maximum values of the

measurement range. M 6411 Measurement unit code M an..3

Code specifying the unit of measurement.

KGM kilogram

LTR litre



GS1 Description:

Litre (1 dm3) O 6314 Measurement value C an..18

To specify the value of a measurement.

X 6162 Range minimum value C n..18

To specify the minimum value of a range.

X 6152 Range maximum value C n..18

To specify the maximum value of a range.

X 6432 Significant digits quantity C n..2

Count of the number of significant digits.

X 7383 SURFACE OR LAYER CODE C an..3

Code specifying the surface or layer of an object.



Group: PCI Segment Group 13: Package identification

Position: 0500


Level: 3


Max Use: 1000

Purpose: A group of segments specifying markings, labels, and packing numbers.

Notes:

Segment Summary


No. ID Name Des. Use Repeat M 0510 PCI Package identification M 1

0570 Segment Group 15: Goods identity number C 99



Segment: PCI Package identification


Group: Segment Group 13 (Package identification) Conditional (Optional)

Level: 3

Usage: Mandatory

Max Use: 1

Purpose: A segment specifying markings and/or labels used on individual physical units

(packages) described in the PAC segment.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is used to provide markings and labels information relevant to the

packaging unit and level identified in the PAC segment.

Example:

PCI+33E' Only used by Myer at the carton level (CPS / DE7075 = 1)


Data Component


R 4233 MARKING INSTRUCTIONS CODE C an..3

Code specifying instructions for marking.

33E Marked with serial shipping container code (EAN Code)

Indication that the serial shipping container code has been

marked on a package. IEN Package Identity Number (EAN Code)

Number uniquely identifying a package.

Implemented by Myer for DSV Orders, it will be the

article number assigned to the package. X C210 MARKS & LABELS C

Shipping marks on packages in free text; one to ten lines.

X 7102 Shipping marks description M an..35

Free form description of the shipping marks.

X 7102 Shipping marks description C an..35


















X 8275 CONTAINER OR PACKAGE CONTENTS

INDICATOR CODE C an..3



Code indicating the contents of container or package.

X C827 TYPE OF MARKING C

Specification of the type of marking that reflects the method that was used and

the conventions adhered to for marking (e.g. of packages). X 7511 Marking type code M an..3

Code specifying the type of marking.







Group: GIN Segment Group 15: Goods identity number

Position: 0570

Group: Segment Group 13 (Package identification) Conditional (Optional)

Level: 4


Max Use: 99

Purpose: A group of segments giving package identification numbers and, where relevant,

delivery limitation information.

Notes:

Segment Summary


No. ID Name Des. Use Repeat M 0580 GIN Goods identity number M 1



Segment: GIN Goods identity number


Group: Segment Group 15 (Goods identity number) Conditional (Optional)

Level: 4

Usage: Mandatory

Max Use: 1

Purpose: A segment providing the identity numbers of packages being despatched.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is used to provide identification numbers relevant to the packaging unit and

level identified in the PAC segment.

Example:

GIN+AW+00300370007400036964’


Data Component


M 7405 OBJECT IDENTIFICATION CODE QUALIFIER M an..3

Code qualifying the identification of an object.

In EANCOM it is recommended to use the Serial Shipping Container Code

(SSCC) for unique identification of individual transport packages. AW Serial shipping container code

A single unique serial number which identifies shipping

containers or shipping packages. ML Marking/label number

The number on the marking or label.

Used by Myer at this level to identify the article number

marked on the packaging. This is the article number on

the Temando label for Customer Order (Direct)

deliveries using a Myer Carrier. M C208 IDENTITY NUMBER RANGE M

Goods item identification numbers, start and end of consecutively numbered

range. M 7402 Object identifier M an..35

Code specifying the unique identity of an object.

X 7402 Object identifier C an..35


X C208 IDENTITY NUMBER RANGE C


range. X 7402 Object identifier M an..35












range.



X 7402 Object identifier M an..35












Group: LIN Segment Group 17: Line item

Position: 0650


Level: 2


Max Use: 9999

Purpose: A group of segments providing details of the individual despatched items.

Segment Summary


No. ID Name Des. Use Repeat M 0660 LIN Line item M 1 O 0700 QTY Quantity C 10

0910 Segment Group 20: Place/location identification C 100



Segment: LIN Line item


Group: Segment Group 17 (Line item) Conditional (Optional)

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying the product being despatched.

All other segments in the detail section following the LIN segment refer to that line

item.

Dependency Notes:

Semantic Notes:

Comments:

Notes: Used at the store and carton level (where CPS.7075 = “3” and “1”). When used at the

carton level, the GTIN must be specified

Example:

LIN+1++ 9876543210123:SRV'


Data Component


R 1082 LINE ITEM IDENTIFIER C an..6

To identify a line item.

Application generated number of the item line within the Despatch Advice.

At the store level the value will be 0

X 1229 ACTION REQUEST/NOTIFICATION DESCRIPTION

CODE C an..3

Code specifying the action to be taken or already taken.

D C212 ITEM NUMBER IDENTIFICATION C

Goods identification for a specified source.

R 7140 Item identifier C an..14

To identify an item.

Format n.14

GTIN - this is the number of the article being despatched. R 7143 Item type identification code C an..3


SRV EAN.UCC Global Trade Item Number

A unique number, up to 14-digits, assigned according to

the numbering structure of the EAN.UCC system. 'EAN'

stands for the 'International Article Numbering

Association', and 'UCC' for the 'Uniform Code Council'. X 1131 Code list identification code C an..17




X C829 SUB-LINE INFORMATION C

To provide an indication that a segment or segment group is used to contain

sub-line or sub-line item information and to optionally enable the sub-line to be

identified. X 5495 Sub-line indicator code C an..3

Code indicating a sub-line item.

X 1082 Line item identifier C an..6

To identify a line item.

X 1222 CONFIGURATION LEVEL NUMBER C n..2



To specify a level within a configuration.

X 7083 CONFIGURATION OPERATION CODE C an..3

Code specifying the configuration operation.



Segment: QTY Quantity

Position: 0700


Level: 3


Max Use: 10

Purpose: A segment to give quantity information concerning the product.

Dependency Notes:

Semantic Notes:

Comments:

Notes: Used at the carton level (CPS.7075 = “1”) to specify the quantity of the item being

despatched

Example:

QTY+12:10'


Data Component


M C186 QUANTITY DETAILS M

Quantity information in a transaction, qualified when relevant.

M 6063 Quantity type code qualifier M an..3

Code qualifying the type of quantity.

12 Despatch quantity

Quantity despatched by the seller.

M 6060 Quantity M an..35

Alphanumeric representation of a quantity.

D 6411 Measurement unit code C an..3


Refer to D.01B Data Element Dictionary for acceptable code values. This DE is only used if the unit of measure on the order was not EA



Group: LOC Segment Group 20: Place/location identification

Position: 0910


Level: 3


Max Use: 100

Purpose: A group of segments giving location information and where relevant, additional

addresses, date and time, and quantities.

Notes: Used by Myer at the Store Level (CPS.7075 = 3) to specify the store

Segment Summary


No. ID Name Des. Use Repeat M 0920 LOC Place/location identification M 1 O 0950 QTY Quantity C 10



Segment: LOC Place/location identification


Group: Segment Group 20 (Place/location identification) Conditional (Optional)

Level: 3

Usage: Mandatory

Max Use: 1

Purpose: A segment identifying a specific location to which products will be delivered.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is used to identify the location of delivery for a split delivery despatch

advice. This segment can also be used to identify a delivery location for a specific line

item which might be different to the delivery location specified in the NAD or LOC

segment in the heading section.

Example:

LOC+8+4052::92’


Data Component


M 3227 LOCATION FUNCTION CODE QUALIFIER M an..3

Code identifying the function of a location.

8 Place of destination

Port, airport or other location to which a means of

transport or transport equipment is destined. Currently Implemented by Myer for Cross-Dock

deliveries, specifies the store R C517 LOCATION IDENTIFICATION C

Identification of a location by code or name.

R 3225 Location name code C an..13

Code specifying the name of the location.





92 Assigned by buyer or buyer's agent

Codes assigned by a buyer or buyer's agent.

X 3224 Location name C an..256

Name of the location.

X C519 RELATED LOCATION ONE IDENTIFICATION C

Identification the first related location by code or name.

X 3223 First related location name code C an..25

Code specifying first related location.





X 3222 First related location name C an..70

Name of first related location.

X C553 RELATED LOCATION TWO IDENTIFICATION C

Identification of second related location by code or name.

X 3233 Second related location name code C an..25



Code specifying the second related location.





X 3232 Second related location name C an..70

Name of the second related location.

X 5479 RELATION CODE C an..3

Code specifying a relation.



Segment: QTY Quantity

Position: 0950

Group: Segment Group 20 (Place/location identification) Conditional (Optional)

Level: 4


Max Use: 10

Purpose: A segment to specify quantity for the given location.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is used to indicate the delivery quantity for the delivery location specified

in the previous LOC segment. The total of all quantities specified in the current segment

group for the line must equal the value for the total quantity detailed in the QTY segment

at line level.

Example:

QTY+12:14'


Data Component


M C186 QUANTITY DETAILS M

Quantity information in a transaction, qualified when relevant.

M 6063 Quantity type code qualifier M an..3

Code qualifying the type of quantity.

12 Despatch quantity

Quantity despatched by the seller.

M 6060 Quantity M an..35

Alphanumeric representation of a quantity.

X 6411 Measurement unit code C an..3




Segment: CNT Control total

Position: 1140

Group: Level: 1


Max Use: 5

Purpose: A segment by which control totals may be provided by sender for checking by the

receiver.

Dependency Notes:

Semantic Notes:

Comments:

Notes: Despatch Advice Summary Section

This segment is used to provide message control information for checking on the

message receiver's in-house system.

Example:

CNT+2:12'


Data Component


M C270 CONTROL M

Control total for checking integrity of a message or part of a message.

M 6069 Control total type code qualifier M an..3

Code qualifying the type of control of hash total.

When using code value '11= Total number of packages’ in this data element,

the total specified in CNT.6066 is calculated by adding the values of

PAC.7224 in the message. 2 Number of line items in message

Self-explanatory.

GS1 Description:

The total number of LIN segments in a message. 11 Total number of packages

Total number of packages of the entire consignment.

M 6066 Control total value M n..18

To specify the value of a control quantity.

X 6411 Measurement unit code C an..3




Segment: UNT Message trailer

Position: 1150

Group: Level: 0

Usage: Mandatory

Max Use: 1

Purpose: A service segment ending a message, giving the total number of segments in the

message (including the UNH & UNT) and the control reference number of the

message.

Dependency Notes:

Semantic Notes:

Comments:

Notes: This segment is a mandatory UN/EDIFACT segment. It must always be the last segment

in the message.

Example:

UNT+35+100'


Data Component


M 0074 NUMBER OF SEGMENTS IN THE MESSAGE M n..6

Control count of number of segments in a message.

The total number of segments in the message is detailed here.

M 0062 MESSAGE REFERENCE NUMBER M an..14

Unique message reference assigned by the sender.

The message reference detailed here should match the value specified in the

UNH segment (UNH.0062).

Documents

MYER€¦ · structure and use is in alignment with the GS1 Australia (GS1AU) General Merchandise Harmonised Guide. For any information regarding EANCOM® or this MIG, please contact: