Supply Chain – Merchandise Logistics E-Commerce Advance ... · Supply Chain – Merchandise...

E-Commerce Advance Ship Note of 71 October 2008 © Myer Pty Ltd

Supply Chain – Merchandise Logistics

E-Commerce Advance Ship Note


Contents

Introduction ________________________________________________________________ 4

Advance Ship Notes _________________________________________________________ 5

Implementation procedures and operational considerations ______________________ 6

Retail industry conventions and implementation guidelines _____________________ 7

Example of preferred Logistics (SSCC) label/marking __________________________ 10

Logistics (SSCC) label specifications__________________________________________ 11

Supplier system requirements _______________________________________________ 13

Segments

ANSI X12 envelope structure _____________________________________________________________14

Segment ISA Interchange control header ______________________________________15

Segment GS Functional group header ________________________________________19

Segment ST Transaction set header __________________________________________21

Segment SE Transaction set trailer ___________________________________________22

Segment GE Group control trailer ____________________________________________23

Segment IEA Interchange control trailer _______________________________________24

ANSI X12 856 Ship Note Manifest ________________________________________________________25

Segments processed by Myer ________________________________________________________26


Segment BSN Beginning segment for ship note (document number and date) _______28

Segment HL Hierarchical level (shipment level data start) _______________________29

Segment NTE Note/special instruction (shipment label)__________________________30

Segment PO4 Physical details (shipment level)__________________________________31

Segment TD1 Details quantity and weight (shipment level) _______________________32

Segment TD5 Carrier details (shipment level)___________________________________33

Segment TD3 Carrier details equipment (shipment level)_________________________34

Segment REF Reference numbers consignment note number (shipment level) _______35

Segment PER Administrative communications contact (shipment level) ____________36

Segment DTM Date/time reference scheduled delivery date (shipment level) ________37

Segment FOB FOB related instructions (shipment level) __________________________38

Segment N1 Name ship to location (shipment level) ____________________________39

Segment HL Hierarchical level (order level data start) __________________________40

Segment PRF Purchase order reference (Myer PO number) (order level)____________41

Segment TD1 Carrier details quantity and weight (order level)____________________42

Segment TD5 Carrier details (order level) ______________________________________43

Segment REF Reference numbers supplier’s invoice number (order level) __________44

Segment N1 Name retail buying location (order level) __________________________45


Contents cont’d

Segments cont’d

ANSI X12 856 Ship Note Manifest cont’d

Segment CUR Currency (order level)___________________________________________46

Segment HL Hierarchical level tare/pallet (level data start) ______________________47

Segment MAN Marks and numbers pallet identification (tare level) _________________48

Segment HL Hierarchical level pack/carton (level data start) ____________________49

Segment PO4 Item physical details (pack level) _________________________________50

Segment PKG Marking packaging, loading (pack level) __________________________51

Segment MAN Marks and numbers carton identification (pack level) _______________52

Segment HL Hierarchical level (sub pack level data start) _______________________53

Segment MAN Marks and numbers (subpack identification) _______________________54

Segment HL Hierarchical level (item level data start) ___________________________55

Segment LIN Item identification ______________________________________________56

Segment SN1 Item detail shipment (item quantities) _____________________________57

Segment PO4 Item physical details (shipment level) _____________________________58

Segment MEA Measurements _________________________________________________59

Segment PKG Marking, packaging, loading_____________________________________60

Segment DTM Date/time reference ____________________________________________61

Segment ITA Allowance, charge or service _____________________________________62

Segment CTT Transaction totals ______________________________________________63


Example ship note transmission, pick and pack structure ________________________________65

VICS 997 functional acknowledgment _____________________________________________________66


Segment AK1 Functional group response_______________________________________68

Segment AK9 Functional group response_______________________________________69



Introduction

Purpose of this implementation guide

The purpose of this guide is to provide suppliers with the necessary information to enable the implementation of electronic Advance Ship Notes to Myer Pty Ltd.

Who should use this guide

This guide is intended for use by Myer suppliers to prepare for the implementation of Electronic Data Interchange (EDI) and to assist with applications integration, thereby ensuring successful electronic trading.


Advance Ship Notes

The Advance Ship Note document lists the items and quantities contained within a shipment of goods, together with additional information for the shipment, such as order information, product description and carrier information.

Myer intend to utilise this document to speed up the flow of goods through the distribution centres and stores.

Myer’s information systems, combined with the receipt of an electronic Advance Ship Note, enable us to concentrate on the faster physical flow of goods, whilst automatically reconciling the paperwork and paying the invoice.

Suppliers who are pre marking their merchandise, packing by store, and are able to transmit accurate Advance Ship Note documents, will be given priority for their deliveries through the distribution centre. The extent of distribution centre checking for these deliveries will depend on the performance record of the supplier for accuracy (shipped quantity compared to invoiced quantity, and shipped quantity compared to order quantity).


Implementation procedures and operational considerations

Trading partners must be able to demonstrate how they intend to build up the electronic Advance Ship Note document. The required method is for merchandise to be scanned as packed thereby building an accurate manifest of carton contents. Distribution centre management will in turn commit to giving these suppliers priority in our distribution centres.

The Myer E-Commerce Team will be responsible for establishing EDI trading partnerships on the appropriate value added network. Each supplier will be contacted to approve and activate the trading partnership.

The document type used for the transmissions of Advance Ship Note information is referred to as the ANSI 856 document. The document standard and version used for the transmissions of this document is 003020 ANSI.

Trading partners will need to ensure that the disk containing 003020 ANSI standard is loaded into their software before transmission can commence.

One electronic Advance Ship Note will be required per order/receiving location.

The Advance Ship Note is to be transmitted and available at the Myer mail box by 6 pm. on the day before delivery to the distribution centre. Once a supplier is EANway Accredited, invoices will no longer be required.

Accuracy of the information sent will be measured against the physical quantity and paperwork provided by suppliers. Results will be passed to the supplier.

A bar coded EAN/UCC Code 128 Shipping Container Mark is required to identify cartons and their contents. Myer distribution centres have developed the ability to scan the Shipping Container Mark to enable automatic carton sortation to be employed at distribution centres.

Myer will transmit functional acknowledgments which will be transmitted at the functional group level.

Trading partners will be required to monitor and ensure that Myer transmits functional acknowledgments for each Advance Ship Note.

The cost of the transmissions will be based on the provision that the sender pays to send the document and the receiver pays to receive and retrieve the document.


Retail industry conventions and implementation guidelines

The retail industry has identified six hierarchical levels for use within the Advance Ship Note transaction set. The following are the definitions of these level ...

NAME CODE DESCRIPTION

SHIPMENT S Data that applies to the whole shipment, such as bill of lading number, lading quantity, supplier code, etc

ORDER O Data related to the sender's order and the associated receiver's original purchase order

TARE T The tare level is used to identify pallets. If there are no identifiable pallets, this level may be omitted

PACK P The pack level is used to identify the cartons, racks, bags, etc in which the item is shipped. In most cases there will be some sort of packs

SUBPACK Q Data related to a grouping of identifiable packages within the pack level. Note this level is only used when the inner pack has identifiable numbers for each inner pack

ITEM I SKU identification data. If identical SKUs are packed using unidentifiable inner packs, such as four six-packs to a case, this can be related at this level

The retail industry implementation of the Advance Ship Note transaction set supports both methods of merchandise shipment packaging with two distinct hierarchical structures. Each structure contains the same levels, that is shipment, order, tare, pack, subpack, and item, and the usage of the segments within each level are the same. The only difference is the order in which the levels may appear within the transaction set and the use of the hierarchical child code within the HL segment. The hierarchical child code, HL04 within the HL segment, is required for the standard carton pack structure. This informs the receiver, after reading the first HL segment, of the structure of the transaction set. Conversely, it is not used for the pick/pack structure. Therefore, the presence or absence of HL04 will indicate the structure represented within the transaction set. The essential difference in the two structures is where the item level appears.


Retail industry conventions and implementation guidelines cont’d

For the pick/pack structure the item is the lowest level, that is the specification of the SKU is always within the shipment container. The order of the hierarchical levels are shipment, order, tare, pack subpack, and item.

Used by Myer

ITEM SUBPACK PACK TARE ORDER SHIPMENT

For the standard carton pack structure the item is between the order level and the tare level, that is the specification of the shipment containers is always within the SKU. The SKU is specified then all the shipping containers for the SKUs are identified. The order of the hierarchical levels are shipment, order, item, tare, pack, and subpack.

Not used by Myer

SUBPACK PACK TARE ITEM ORDER SHIPMENT


Retail industry conventions and implementation guidelines cont’d

Pick and pack lower case structure example

In this pick and pack structure example the shipment is for an order covering two stores. The first store has two cartons. The first carton contains three items (SKUs), the second carton contains one SKU. The second store has one carton with 6 SKUs in the carton. Each box represents one hierarchical level (one HL segment followed by data segments). The number in each box (top left comer) is the hierarchical sequence number, (the number in HL01 ). The number in the top right is the parent ID (HL02).

09 01ORDER

10 09PACK

16 10

15 10

14 10

13 10

12 10

11 10ITEM

02 01ORDER

07 02PACK

03 02PACK

08 07ITEM

06 03

05 03

04 03ITEM

01SHIPMENT


Example of preferred Logistics (SSCC) label/marking

(EAN/UCC 128 label)

QR

PO123456789112

PO123456789112 PO123456789112

PO123456789112PO123456789112

PO123456789112 PO123456789112PO123456789112

PO123456789112

FROM : Hilton HosieryBroadmeadows Vic

AD3011

Con No : 1198765B/L No : 1198765

SSCC3 9312345123456789 1

(00) 393123451234567891

FOR : Myer 0004Myer Chadstone1341 Dandenong Rd Chadstone 3148

CARRIER : Toll

TO :Myer DC 0020Doherty’s Rd Altona 3025

(421) 0363025 (90) 0004

PO123456789112

8184Hilton Sheer to Light Panty hose Size 10

The label is based on a ‘real estate’ principle. Every data element that could be required, has been given its own specific location. The label must not be reformatted because some data elements are absent. The format of the label always remains constant.

There are three types of data elements included in the label ...

Mandatory (M) Must always appear on the label Mandatory Conditional (MC) Must always appear on the label when a certain condition is met Optional (O) Is available for use by the supplier but is not mandatory for any Myer business requirement


Logistics (SSCC) label specifications

Label size

A6 148 mm x 105 mm or nearest equivalent

Specifications

M = Mandatory MC = Mandatory Conditional O = Optional

Need Label Field Description Specifications Technical Specifications

M From Supplier who received the order

Name and address

M To Ship to delivery location as specified on the order

Business name, distribution centre number, distribution centre name, address & post code

Distribution centre number minimum height 5mm, combined height of these 3 lines 16mm minimum

M SSCC The numbers embedded in the SSCC bar code in human readable format

(refer to SSCC bar code)

MC Advertised Conditional based on receipt of data in the order

AD for Advertised Indicator and advertised date in 4 characters (DDMM)

Combined height of these 2 lines 18mm minimum

M Department Mandatory based on receipt of data in the order

Business class group or department number/name

MC Item description

Conditional based on carton/bag containing only 1 SKU

SKU description from supplier’s EANcross reference file

O Carrier Suppliers or their carriers may want to use this field as an option

Carrier name and consignment note number

M For Store that stock was allocated to in the order

Business name, store number, store name, address & postcode

Store number height of 10 mm minimum

M Purchase order number

Number assigned to the purchase order

Exact purchase order number transmitted in the order


Logistics (SSCC) label specifications cont’d

Specifications cont’d Need Label Field Description Specifications Technical

Specifications

M ‘Ship to’ and ‘For’ bar code

Application identifier (Ai) 421 followed by application identifier (Ai) 90. The store number details are for use by MYER to determine the ship to store location.

Code 128 format, 3 digits for the application identifier ie 421, 3 digits for the ISO country code, 4 digits for the ‘ship to’ post code, 2 digits for the application identifier ie 90, 4 digits for the ‘ship for’ store number (zero front fill for store numbers less than 4 digits). A Set C start indicator followed immediately by a function 1 character is to be used preceding the first Ai identifier (421) and as a separator before the second Ai indicator (90). Do not put brackets or spaces into the bar code.

Height of 38 mm, width of 72.5 mm and magnification of 50%.

Light margin of minimum 5 mm in front of and at the end of the bar code, and 10 mm below the bar code.

M ‘Ship to’ and ‘For’ number

The numbers embedded in the bar code in human readable format.

The application identifiers should be contained in opening and closing brackets. It is optional to place spaces between the pieces of data. For example (421) 1231234 (90) 0009

M SSCC bar code

Serial Shipping Container Code. Application identifier (Ai) 00

Code 128 EAN/UCC Serial Shipping Container Code which must be exactly 20 digits. 2 digits for application identifier ie 00, 1 digit for extension digit, 2 digits for EAN country code, 5 digits for EAN company number, 9 digits for serial number assigned by supplier that will be unique within a 12 month period, and 1 digit as a check digit. A Set C start indicator followed immediately by a function 1 character is to be used preceding the Ai identifier (00). Do not put brackets or spaces into the bar code.

Height of 29 mm, width of 78 mm and magnification of 50%.

Light margin of minimum 5 mm in front of and at the end of the bar code, and 10 mm above and below the bar code.

M SSCC number

The numbers embedded in the bar code in human readable format.

The application identifier should be contained in opening and closing brackets. It is optional to place spaces between the pieces of data. For example (00) 0 93 12345 123456789 0


Supplier system requirements

l Collect carton contents

♦ Scan EANs while packing

2 Carton full

♦ Scan break code and produce a unique EAN/UCC CODE 128 shipping container carton label

3 Item scanned not on retailers purchase order

♦ Alert operator

4 End of order

♦ Scanned items to order file

♦ Highlight discrepancies for investigation

5 Compile the 856 Ship Note Manifest from the data collected and stored during the individual packing operation

Following these steps ensures the SSCC detail matches the physical shipment.


ANSI X12 envelope structure

Transaction Set Interchange Control Structure

Version 00200

This ISA segment marks the beginning of the transmission and provides sender/receiver identification.

Each GS segment marks the beginning of a functional group. There may be one or more than one functional groups within each transmission. The ST segment marks the beginning of each transaction set (electronic document). There can be up to 999,999 transactions sets within each functional group.

The interchange control structure is common to all the transaction sets.

ISA INTERCHANGE CONTROL HEADER MANDATORY GS FUNCTIONAL GROUP HEADER MANDATORY

ST TRANSACTION SET HEADER (FOLLOWED BY TRANSACTION SET SEGMENTS) MANDATORY

SE TRANSACTION SET TRAILER MANDATORY

GE FUNCTIONAL GROUP TRAILER MANDATORY

IEA INTERCHANGE CONTROL TRAILER MANDATORY


Segment ISA Interchange control header

Level Envelope

Req Des Mandatory

Max Use 01

Loop _____________________

FLD #

ELEMENT NAME DICT NUM

TYPE MIN LEN

MAX LEN

REQ CODES & COMMENTS

O1 AUTHORISATION INFORMATION QUALIFIER

101 ID 2 2 M Code to identify the type of information in the authorisation information. Authorisation information is used to accommodate a UCS communications ID. It is only used when using ANSI standard and UCS communications. Normally the value is 00. 00=No authorisation information is present (no meaningful information in I02). The interchange control number value in this header must match the value in the same data element in the corresponding interchange control trailer.

02 AUTHORISATION INFORMATION

102 AN 10 10 M Information used for additional identification or authorisation of the sender or the data in the interchange. The type of information is set by the authorisation information qualifier. Normally this field is blank. If ISA01 is 01 this field will contain the UCS communications IS. The first occurrence of the <gs> (byte 4) defines the actual value of the data element separator and is graphically displayed as an asterisk “ “ “ in other ANSIX12 data segment documentation (eg the PO1 segment). The first occurrence of the <tr>, 1 byte after the data element ISA16, defines the actual value of the segment terminator and is graphically displayed as NL in other ANSI ASCX12 data segment documentation (eg the BFR segment in ANSIX12.22).

03 SECURITY INFORMATION QUALIFIER

103 ID 2 2 M Code to identify the type of information in the Security Information. Security Information is only used when using the UCS Communication standard. Normally the value is 00.

00=No security information present (no meaningful information in 104).


Segment ISA Interchange control header cont’d

04 SECURITY INFORMATION

104 AN 10 10 M This is used for identifying the security information about the sender on the data in the interchange. The type of information is set by the security information qualifier. Normally this field is blank. If ISA03 is 01 this field will contain a password that has been agreed to by the sender and receiver.

05 INTERCHANGE ID QUALIFIER

105 ID 2 2 M Qualifier to designate the system/method of code structure used to designate the sender or receiver id element being qualified. The interchange ID qualifier is used to define the code used in ISA06 to identify sender of the interchange. ZZ=mutually defined.

06 INTERCHANGE SENDER

106 ID 15 15 M Supplier ID (EDI address) Identification code published by the sender for other parties to use as the receiver ID to route data to them. The sender always codes this number in the sender ID element. The identification code described by ISA05. Left justified, blank fill.

07 INTERCHANGE ID QUALIFIER

105 ID 2 2 M Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified. The interchange ID qualifier is used to define the code used, in ISA08, to identify receiver of the interchange. ZZ=mutually defined.

08 INTERCHANGE RECEIVER

107 ID 15 15 M 9313164000525=Myer ID (EDI address) Identification code published by the receiver of the data. When sending, it is used by the sender as their ID, thus other parties sending to them will use this as receiving ID to route data to them. The identification code described by ISA07. Left justified, blank fill.

09 DATE 108 DT 6 6 M Date of the interchange ISA generated (YYMMDD). The date the interchange was created in the sender’s system; submit date.

10 TIME 109 TM 4 4 M Time of the interchange created (HHMM) in the sender’s system; submit time. 24 hour clock.

11 INTERCHANGE STANDARDS IDENTIFIER

110 ID 1 1 M Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer. U US EDI Community of X12, TDCC and UCS.



12 INTERCHANGE VERSION ID

111 ID 5 5 M This version number covers the interchange control segment only. Positions 1-3 of the field = major version, 4-5 of the field = release level of the version. This version number is for the envelope only. It is not the same as the version number is the GS segments. 00200=The current value, Version 2, Release 0.

13 INTERCHANGE CONTROL NUMBER

112 N 9 9 M Generated by the Supplier. This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with sender ID, it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver and all third parties be able to maintain an audit trail of interchanges using this number. The number is sequentially assigned, by the sender, starting with one within each trading partner. The trading partner at the interchange level is defined by the interchange receiver ID (ISA08). The control number is incremented by one for each interchange envelope sent to the trading partner. When the control numbers reaches 999999999 (maximum size) the next interchange envelope will have the control number of 000000001.

14 ACKNOWLEDGMENT REQUESTED

113 ID 1 1 M Code set by the sender to request an interchange acknowledgment. The retail industry is not using transmission acknowledgments. The transmission is not the same as the functional group acknowledgment. O=No acknowledgment requested.

15 TEST INDICATOR

114 ID 1 1 M Code to indicate whether data enclosed by this interchange envelope is test or production. The test indicator is valuable for start up system tests. The indicator applies to the entire transmission. P=Production data. T=Test data.

16 SUBELEMENT SEPARATOR

115 AN 1 1 M This is a field reserved for future expansion in separating data element subgroups. >=The value identified for retail use.



NOTES The purpose of this segment is to start and identify and interchange of one or more functional groups and interchange related control segments.

The interchange control number value in this header must match the value in the same data element in the corresponding interchange control trailer.

The first occurrence of the <gs> (byte 4) defines the actual value of the data element separator and is graphically displayed as an asterisk *** in other ANSIX12 data segment documentation (for example, the PO1 segment). The first occurrence of the <tr>, 1 byte after the data element ISA16, defines the actual value of the segment terminator and is graphically displayed as NL in other ANSI ASCX12 data segment documentation (for example, the BFR segment in ANSIX12.22).

The ISA segment is fixed length (min/max are equal for each element), however, data element separators are used between data elements to be consistent with the basic syntax of segment structure.

The following control characters have been identified for use in the retail industry ...

Segment terminator NEW LIN - (HEX “15” in EBCDIC) CR - (HEX”OD” in ASCII)

♦ The segment terminator that is to be used in the transmission is defined by the first occurrence of the segment terminator in the ISA segment, for example, ISA*00...N/L

♦ Whichever character is used for the segment terminator must be used throughout the transmission

Element separator Recommended character BELL - (HEX “2F” in EBCDIC) (HEX “07” in ASC11) Alternate character “”” - (HEX “5C” in EBCDIC) (HEX “2A” in ASCII)

♦ The element separator that is to be used in the transmission is defined by the first occurrence of the element separator in the ISA segment, for example, ISA*00...

Subelement separator “>“ - (HEX “6E” in EBCDIC) (HEX “3E” in ASCII)

Caution any time a printable character is used to control the translation of data, that control character cannot be used as data within the transmission. Some systems/network protocols may translate control characters when going from EBCDIC to ASCII and back.

The ISA supports the UCS communication standard as well as the normal ANSIX12 convention for identification of the receiver and the sender.

ISA01 through ISA04 are only used if the trading partners are using the UCS communication standard. If the UCS communication standard is NOT used ISA01 and ISA03 will contain 00. ISA02 and ISA04 will contain spaces. If the UCS communication standard is being used ISA01, ISA03 and ISA05 will contain 01, 01 and 13 respectively. ISA02, ISA04 and ISA06 will contain the UCS communication ID, password and the telephone number for the receiver’s modem.

SEGMENT EXAMPLE I S A *0 0 * * 0 0 * *Z Z * 9 3 0 0 1 0 0 1 2 3 4 5 8 * Z Z * 9 3 1 3 1 6 4 0 0 0 0 0 9 *9 0 1 0 2 3 *1 0 2 5* U * 0 0 2 0 0 * 0 0 0 0 0 0 0 8 9 * 0 * P *>


Segment GS Functional group header

Level Group

Req Des Mandatory

Max Use 01

Loop _____________________

FLD #


TYPE MIN LEN

MAX LEN


01 FUNCTIONAL ID 479 ID 2 2 M Code identifying a group of application related transaction sets. SH (856) = Shipment header for an ASN

02 APPLICATION SENDER’S CODE

142 ID 2 12 M Code Identifying party sending transmission. This is the supplier’s EDI address (12 characters) A unique code to identify the sender. This is usually the same as the code used in ISA06. It could be used to define sub organisations, ie companies of a corporation, departments etc. The trading partners must agree on the codes.

03 APPLICATIONS RECEIVER’S CODE

124 ID 2 12 M Code identifying party receiving transmission. Myer EDI application code = EQ856 This is usually the same as the code used in ISA08. It could be used to define sub organisations, ie companies or a corporation, departments etc. The trading partners must agree on the codes.

04 DATA INTERCHANGE DATE

29 DT 6 6 M Date GE segment generated (YYMMDD). Date sender generated a functional group of transaction sets. The date the group was created in the sender’s system; submit date.

05 DATA INTERCHANGE TIME

30 TM 4 4 M (HHMM) expressed in 24 hour clock time when the sender generated. The time the group was created in the sender’s system; submit time.

06 DATA INTERCHANGE CONTROL

28 N 1 9 M Assigned number originated and maintained by the sender. The number assigned by the sender must be unique within each trading partner. The trading partner at the group level is defined by the application receiver code (GS03). The uniqueness must be maintained until such time that a functional acknowledgment is received for that group.


Segment GS Functional group header cont’d

07 RESPONSIBLE AGENCY CODE

455 ID 1 2 M Code used in conjunction with the version data element to identify the issuer of the standard. X Accredited Standards Committee X12.

08 VERSION 480 ID 1 12 M The version code is used in conjunction with the Functional Identifier to specify an exact version of and EDI standard. Format of the version is ... Position Content 1-3 Major version number 4-6 Release level of version 7-12 Industry or trade assoc ID (optionally assigned by user) Version/release number is the Version and release of the transaction sets within the group. This is not the same as the version number in the ISA segment. 003020-ANSI X12 version 3, release2.

NOTE The purpose of this segment is to indicate the beginning of a functional group and to provide control information.

SEGMENT EXAMPLE

GS*SH*930010012345*EQ856*970429*1656*304*X*003020


Segment ST Transaction set header

Level Header

Req Des Mandatory

Max Use 01

Loop _____________________

FLD #


TYPE MIN LEN

MAX LEN


01 TRANSACTION SET IDENTIFIER CODE

143 ID 3 3 M Code uniquely identifying a transaction set. 856X12 Advance Ship Note The transaction set identifier (ST01) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition, for example, 810 selects the invoice transaction set.

02 TRANSACTION SET CONTROL NUMBER

329 AN 4 9 M Generated by the Supplier. Identifying control number assigned by the originator for a transaction set. The number is sequentially assigned, by the sender, starting with one within each functional group. For each functional group the first transaction set control number will be 0001 and incremented by one for each additional transaction set within the group.

NOTE The purpose of this segment is to indicate the start of a transaction set and to assign a control number.

SEGMENT EXAMPLE

ST*856*0001


Segment SE Transaction set trailer

Level Summary

Req Des Mandatory

Max Use 01

Loop _____________________

FLD #


TYPE MIN LEN

MAX LEN


01 NUMBER OF INCLUDED SEGMENTS

96 N 1 6 M Generated by the supplier. Total number of segments included in a transaction set including ST and SE segments.


329 AN 4 9 M Identifying control number assigned by the originator for a transaction set. This must be the same number as in the ST segment (ST02) for the transaction set.

NOTES The purpose of this segment is to indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).

SE is the last segment of each transaction set.

SEGMENT EXAMPLE

SE*3*0001


Segment GE Group control trailer

Level Group

Req Des Mandatory

Max Use 01

Loop _____________________

FLD #


TYPE MIN LEN

MAX LEN


01 NUMBER OF TRANSACTION SETS

97 N 1 6 M Generated by the Supplier. Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element. The count of ST segments within the group.

02 GROUP CONTROL NUMBER

28 N 1 9 M Generated by the Supplier. Assigned numbers originated and maintained by the sender. Must be the same number as in the GS segment (GS06) for the group.

NOTES The purpose of this segment is to indicate the end of a functional group and to provide control information.

The use of identical data interchange control numbers in the associated functional group header and trailer is designed to maximise functional group integrity. The control number is the same as that used in the corresponding header.

SEGMENT EXAMPLE

GE*5*952


Segment IEA Interchange control trailer

Level Envelope

Req Des Mandatory

Max Use 01

Loop _____________________

FLD #


TYPE MIN LEN

MAX LEN


01 NUMBER OF INCLUDED GROUPS

116 N 1 5 M Generated by the Supplier. A count of the number of functional groups included in a transmission. The count of GS segments within the transmission.

02 INTERCHANGE CONTROL NUMBER

112 N 9 9 M Generated by the Supplier. This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender, receiver and all third parties be able to maintain an audit trail of interchange using this number. Must be the same number as in the ISA segment (ISA13) for the transmission.

NOTES The purpose of this segment is to define the end of an interchange of one or more functional groups and interchange related control segments.

The interchange control number in this trailer must match the value in the same data element in the corresponding interchange control header.

The value of the data element separator represented by <gs> and the data segment terminator represented by <tr> are set by the interchange control header ISA for this interchange.

SEGMENT EXAMPLE

IEA*1*000000789


ANSI X12 856 version 003020 segment table

This document describes the EDI mapping format for the Ship Note Manifest ( ANSI 856 ). The document is based on the ANSI 3020 standard developed in North America. The document shows the segments (and their expected data content) that will be processed by Myer.


Segments processed by Myer

ST TRANSACTION SET HEADER MANDATORY BSN BEGINNING SEGMENT FOR SHIP NOTE - DOCUMENT NUMBER AND DATE MANDATORY HL HIERARCHICAL LEVEL - SHIPMENT LEVEL DATA START MANDATORY NTE NOTE /SPECIAL INSTRUCTION - DELIVER TO LOCATION REQUIRED PO4 ITEM PHYSICAL DETAILS - SHIPMENT VOLUME OPTIONAL TDl CARRIER DETAILS (QUANTITY AND WEIGHT) REQUIRED TD5 CARRIER DETAILS (ORDER STATUS) OPTIONAL TD3 CARRIER DETAILS (EQUIPMENT) OPTIONAL REF REFERENCE NUMBERS - CONSIGNMENT NOTE NUMBER REQUIRED PER ADMINISTRATIVE COMMUNICATIONS CONTRACT OPTIONAL DTM DATE/TIME REFERENCE - SCHEDULED DELIVERY DATE REQUIRED FOB FOB RELATED INSTRUCTIONS FUTURE USE Nl NAME - SHIP TO LOCATION REQUIRED HL HIERARCHICAL LEVEL - ORDER LEVEL DATA START MANDATORY PRF PURCHASE ORDER REFERENCE - MYER/ PO NUMBER REQUIRED TD1 CARRIER DETAILS (QUANTITY AND WEIGHT) REQUIRED TD5 CARRIER DETAILS (ORDER STATUS) OPTIONAL REF REFERENCE NUMBERS - SUPPLIER'S INVOICE NUMBER OPTIONAL Nl NAME - RETAIL BUYING LOCATION REQUIRED CUR CURRENCY FUTURE USE HL HIERARCHICAL LEVEL - TARE ( PALLET ) LEVEL DATA START OPTIONAL MAN MARKS AND NUMBERS - PALLET IDENTIFICATION OPTIONAL HL HIERARCHICAL LEVEL - PACK ( CARTON ) LEVEL DATA START MANDATORY PO4 ITEM PHYSICAL DETAILS (CARTON WEIGHT) OPTIONAL PKG MARKING, PACKAGING, LOADING OPTIONAL MAN MARKS AND NUMBERS - CARTON IDENTIFICATION REQUIRED HL HIERARCHICAL LEVEL -SUBPACK LEVEL DATA START OPTIONAL MAN MARKS AND NUMBERS - SUBPACK IDENTIFICATION OPTIONAL HL HIERARCHICAL LEVEL - ITEM LEVEL DATA START MANDATORY LIN ITEM IDENTIFICATION REQUIRED SN1 ITEM DETAIL (SHIPMENT) - ITEM QUANTITIES REQUIRED P04 ITEM PHYSICAL DETAILS (PACKING VARIATIONS) OPTIONAL MEA MEASUREMENTS FUTURE USE PKG MARKING, PACKAGING, LOADING OPTIONAL DTM DATE/TIME REFERENCE (USE BY DATE) OPTIONAL ITA ALLOWANCE, CHARGE OR SERVICE FUTURE USE CTT TRANSACTION TOTALS MANDATORY SE TRANSACTION SET TRAILER MANDATORY



FLD ELEMENT NAME DICT MIN MAX CODES & # NUM TYPE LEN LEN REQ COMMENTS

01 TRANSACTION SET IDENTIFIER CODE 0143 ID 3 3 M 856 (X12.1 Ship Note Manifest) 02 TRANSACTION SET CONTROL NUMBER 0329 AN 4 9 M Identifying control number assigned by originator for a transaction set

SEGMENT EXAMPLE

ST * 856 * 0001


Segment BSN Beginning segment for ship note (document number and date)


01 TRANSACTION SET PURPOSE CODE 0353 ID 02 02 M ‘00’ Original ‘07’ Dup 02 SHIPMENT IDENTIFICATION 0396 AN 02 30 M Unique control number 03 DATE 0373 DT 06 06 M YYMMDD Ship Note date 04 TIME 0337 TM 04 06 M HHMMSS Ship Note time 05 HIERARCHICAL STRUCTURE CODE 1005 ID 04 04 O ‘0001’ Pick & Pack ‘0002’ Standard Pack (Not used by Myer)

NOTES The Advance Ship Note supports two distinct hierarchical structures. Use code 0001 in BSN05 for merchandise packed by store (picked and packed). The Advance Ship Note will have the structure ...

Shipment level Order level Pack (carton) level Item level

Use code 0002 in BSN05 for merchandise in standard cartons (standard pack). The Advance Ship Note will have the structure ...

Shipment level Order level Item level Pack (carton) level

Myer mapping allows for the pick and pack structure only (code 0001).

BSN02 is a unique control number assigned by the supplier to identify the shipment.

SEGMENT EXAMPLE

BSN*00*12345*930125*111559*0001


Segment HL Hierarchical level (shipment level data start)


01 HIERARCHICAL ID NUMBER 0628 AN 01 12 M ‘1’ (note 1) 02 HIERARCHICAL PARENT ID NUMBER 0734 AN 0l 12 O Blank 03 HIERARCHICAL LEVEL CODE 0735 ID 0l 02 M 'S (note 2)' 04 HIERARCHICAL CHILD CODE 0736 ID 0l 0l U Blank

NOTES HL segments are used to bound the segments in each level of the document.

HL0l is assigned by the sender to identify a data segment in the hierarchical structure.

HL02 identifies the hierarchical ID of the HL segment to which it is subordinate.

This number should be assigned sequentially, starting from l, for every HL segment within the transaction set.

This code identifies the beginning of the shipment level data. There is only one occurrence of shipment level data.

SEGMENT EXAMPLE

HL*1**S


Segment NTE Note/special instruction (shipment level)


01 NOTE REFERENCE CODE 0363 IID 3 3 O DEL=Delivery 02 TEXT - DELIVER TO LOCATION CODE 0003 AN 1 60 M Receiving DC or store number

NOTE The deliver to location code will be the same as the shipment, name segment N104.

SEGMENT EXAMPLE

NTE* DEL*020


Segment PO4 Physical details (shipment level)


01 PACK 0356 N0 01 06 O Not used 02 SIZE 0357 R 01 08 O Not used 03 UNIT OF MEASURE CODE 0355 ID 02 02 C Not used 04 PACKAGING CODE 0103 ID 05 05 U Not used 05 WEIGHT QUALIFIER 0187 ID 01 02 U Not used 06 GROSS WEIGHT PER PACK 0384 R 01 09 C Not used 07 UNIT OF MEASURE CODE 0355 ID 02 02 C Not used 08 GROSS VOLUME PER PACK 0385 R 01 09 O Numeric (value of gross volume) 09 UNIT OF MEASURE CODE 0355 ID 02 02 C CR=Cubic meter 10 LENGTH 0082 R 01 08 O Not used 11 WIDTH 0189 R 01 08 O Not used 12 HEIGHT 0065 R 01 08 O Not used 13 UNIT OF MEASUREMENT CODE 0355 ID 02 02 C Not used

NOTE This segment, at the shipment level, is only used to specify the volume or cube of the entire shipment.

SEGMENT EXAMPLE

P04 ********10*CR


Segment TD1 Details quantity and weight (shipment level)


01 PACKAGING CODE 0103 ID 05 05 O Refer to Notes for code list 02 LADING QUANTITY 0080 N0 0l 07 C Number of packages in shipment 03 COMMODITY CODE QUALIFIER 0023 ID 0l 0l U Not Used 04 COMMODITY CODE 0022 AN 0l 16 U Not Used 05 LADING DESCRIPTION 0079 AN 01 50 U Not Used 06 WEIGHT QUALIFIER 0187 ID 01 02 O G=Gross 07 WEIGHT 0081 R 01 08 C Numeric value of weight 08 UNIT OF MEASUREMENT CODE 0355 ID 02 02 C KG=Kilogram

NOTES The following packaging code combinations are used by the retail industry ...

BAG76, BAG79, CTN25, CTN31, PLT01, PLT94, SLP25

Part 1

BAG Bag

CTN Carton

PLT Pallet

SLP Slip sheet

Part 2

01 Aluminium

25 Corrugated or solid

31 Fibre

76 Paper

79 Plastic

94 Wood

This segment can be sent more than once for mixed shipment containing bags and cartons.

SEGMENT EXAMPLE

TDl*CTN25*256 ****G*160*KG


Segment TD5 Carrier details (shipment level)


01 ROUTING SEQUENCE CODE 0133 ID 1 2 O Future use 02 IDENTIFICATION CODE QUALIFIER 0066 ID 1 2 C Future use 03 IDENTIFICATION CODE 0067 AN 2 17 C Future use 04 TRANSPORT METHOD CODE 0091 ID 1 2 C Future use 05 ROUTING 0387 AN 1 35 C Future use 06 SHIPMENT/ORDER STATUS 0368 ID 2 2 O Refer to notes 07 LOCATION QUALIFIER 0309 ID 1 2 O Future use 08 LOCATION IDENTIFIER 0310 AN 1 25 C Future use 09 TRANSIT DIRECTION CODE 0731 ID 2 2 O Not used 10 TRANSIT TIME DIRECTION QUALIFIER 0732 ID 2 2 O Not used 11 TRANSIT TIME 0733 R 1 4 C Not used

NOTES The following shipment/order status codes are used in the retail industry ...

BK Back ordered from previous order BP Shipment partial, back order to ship on (date) CC Shipment complete CM Shipment complete with additional quantity CP Partial shipment, no back order CS Shipment complete with substitution DE Deleted order IC Item cancelled IS Item represents substitution from original order PR Partial shipment SS Split shipment It is Myer policy not to allow back orders, substitution or over delivery.

We expect to receive only CC or PR.

SEGMENT EXAMPLE

TD5 ******CC


Segment TD3 Carrier details equipment (shipment level)


01 ELEMENT DESCRIPTION CODE 0040 ID 2 2 M TL=Trailer 02 EQUIPMENT INITIAL 0206 AN 1 4 O Alpha part of number 03 EQUIPMENT NUMBER 0207 ID 1 10 C Numeric part of number 04 WEIGHT QUALIFIER 0187 ID 1 2 O Not used 05 WEIGHT 0081 R 1 8 C Not used 06 UNIT OF MEASUREMENT CODE 0355 ID 2 2 C Not used 07 OWNERSHIP CODE 0102 ID 1 1 O Not used

NOTE This segment is used to specify the trailer number for a truckload shipment.

SEGMENT EXAMPLE

TD3*TL*FAA*055


Segment REF Reference numbers consignment note number (shipment level)


01 REFERENCE NUMBER QUALIFIER 0128 ID 02 02 M CN=Carrier's reference # 02 REFERENCE NUMBER 0127 AN 0l 30 R Consignment note # 03 DESCRIPTION 0352 AN 0l 80 U Not used

NOTE If available the consignment number can be included in this segment.

SEGMENT EXAMPLE

REF*CN*56789


Segment PER Administrative communications contact (shipment level)


01 CONTACT NAME 0366 ID 2 2 M DI=Delivery instruction HM=Hazardous material 02 NAME 0093 AN 1 35 O Free form name 03 COMMUNICATION NUMBER QUALIFIER 0365 ID 2 2 C TC=Telephone 04 COMMUNICATION NUMBER 0364 AN 7 25 C Phone number using the international standard

NOTE This segment may be used to identify a person or office to whom administrative communications should be directed.

SEGMENT EXAMPLE

PER*D1*JOHN SMITH*TE*61396614605


Segment DTM Date/time reference scheduled delivery date (shipment level)


01 DATE/TIME QUALIFIER 0374 ID 03 03 M ‘067’ Current schedule delivery ‘068’ Current schedule ship 02 DATE 0373 DT 06 06 R YYMMDD 03 TIME 0337 TM 04 06 U Not used 04 TIME CODE 0623 ID 02 02 U Not used 05 CENTURY 0624 N0 02 02 U Not used

NOTE Use this segment to specify the date shipped and scheduled delivery date to the Myer distribution centre.

SEGMENT EXAMPLES

DTM*068*070127

DTM*067*070129


Segment FOB FOB related instructions (shipment level)


01 SHIPMENT METHOD OF PAYMENT 0146 ID 2 2 M Future use 02 LOCATION QUALIFIER 0309 ID 1 2 C Future use 03 DESCRIPTION 0352 AN 1 80 C Future use 04 TRANSPORT TERMS QUALIFIER CODE 0334 ID 2 2 O Future use 05 TRANSPORT TERMS CODE 0335 ID 3 3 C Future use 06 LOCATION QUALIFIER 0309 ID 1 2 C Future use 07 DESCRIPTION 0352 AN 1 80 O Future use 08 RISK OF LOSS QUALIFIER 0054 ID 2 2 O Not used 09 DESCRIPTION 0352 AN I 80 C Not used

NOTE Used to specify transport instruction relating to shipment, but not yet in use by Myer.


Segment N1 Name ship to location (shipment level)


0l ENTITY IDENTIFIER CODE 0098 ID 02 02 M ST=Ship to location 02 NAME 0093 AN 0l 35 C Not used 03 IDENTIFICATION CODE QUALIFIER 0066 ID 0l 02 C '92' Assigned by buyer 04 IDENTIFICATION CODE 0067 AN 02 17 C Ship to location ID

NOTE N104 is the Myer Store or distribution centre ID.

Refer to the Myer list of store addresses for the relevant ID number.

SEGMENT EXAMPLE

Nl*ST**92*020


Segment HL Hierarchical level (order level data start)


01 HIERARCHICAL ID NUMBER 0628 AN 0l 12 M 2=next number in the sequence from HL1 at the shipment level 02 HIERARCHICAL PARENT ID NUMBER 0734 AN 0l 12 O 1 03 HIERARCHICAL LEVEL CODE 0735 ID 0l 02 M O=Order level 04 HIERARCHICAL CHILD CODE 0736 ID 0l 0l U Not used

SEGMENT EXAMPLE

HL*2*1*O


Segment PRF Purchase order reference (Myer PO number) (order level)


01 PURCHASE ORDER NUMBER 0324 AN 01 22 M Myer PO number 02 RELEASE NUMBER 0328 AN 01 30 O Not used 03 CHANGE ORDER SEQUENCE NUMBER 0327 AN 01 08 U Not used 04 PURCHASE ORDER DATE 0323 DT 06 06 O YYMMDD PO date 05 ASSIGNED IDENTIFICATION 0350 AN 01 11 O Not used 06 CONTRACT NUMBER 0367 AN 01 30 O Not used

NOTE Use PRF01 to send the Myer purchase order number.

SEGMENT EXAMPLE

PRF*000000321301X020***921207


Segment TD1 Carrier details quantity and weight (order level)


01 PACKAGING CODE 0103 ID 05 05 O Refer to note 1 for code list 02 LADING QUANTITY 0080 N0 0l 07 C Number of packages in the order 03 COMMODITY CODE QUALIFIER 0023 ID 0l 0l U Not used 04 COMMODITY CODE 0022 AN 0l 16 U Not used 05 LADING DESCRIPTION 0079 AN 01 50 U Not used 06 WEIGHT QUALIFIER 0187 ID 01 02 O Not used 07 WEIGHT 0081 R 01 08 C Not used 08 UNIT OF MEASUREMENT CODE 0355 ID 02 02 C Not used

NOTE This segment details the number of packages for the individual store location in a pick pack structure.

The following packaging code combinations are used by the retail industry ...

BAG76, BAG79, CTN25, CTN31, PLT01, PLT94, SLP25

Part 1

BAG Bag CTN Carton PLT Pallet SLP Slip sheet Part 2

01 Aluminium 25 Corrugated or solid 31 Fibre 76 Paper 79 Plastic 94 Wood

SEGMENT EXAMPLE

TDl*CTN25*20


Segment TD5 Carrier details (order level)


01 ROUTING SEQUENCE CODE 0133 ID 1 2 O Future use 02 IDENTIFICATION CODE QUALIFIER 0066 ID 1 2 C Future use 03 IDENTIFICATION CODE 0067 AN 2 17 C Future use 04 TRANSPORT METHOD CODE 0091 ID 1 2 C Future use 05 ROUTING 0387 AN 1 35 C Future use 06 SHIPMENT/ORDER STATUS 0368 ID 2 2 O Refer Note 07 LOCATION QUALIFIER 0309 ID 1 2 O Future use 08 LOCATION IDENTIFIER 0310 AN 1 25 C Future use 09 TRANSIT DIRECTION CODE 0731 ID 2 2 O Not used 10 TRANSIT TIME DIRECTION QUALIFIER 0732 ID 2 2 O Not used 11 TRANSIT TIME 0733 R 1 4 C Not used

NOTES The following shipment/order status codes are used in the retail industry ...

BK Back ordered from previous order BP Shipment partial, back order to ship on (date) CC Shipment complete CM Shipment complete with additional quantity CP Partial shipment, no back order CS Shipment complete with substitution DE Deleted order IC Item cancelled IS Item represents substitution fro original order PR Partial shipment SS Split shipment It is Myer policy not to allow back orders, substitution or over deliveries.

We expect to receive only CC or PR.

SEGMENT EXAMPLE

TD5 ******CC


Segment REF Supplier's reference number (order level)


01 REFERENCE NUMBER QUALIFIER 0128 ID 02 02 M IA=Internal vendor ref # DP=Internal department # eg. class group 4212 02 REFERENCE NUMBER 0127 AN 01 30 R Unique reference # 03 DESCRIPTION 0352 AN 01 80 U Not used

NOTE Use REF01 to send your reference number for this shipment.

The unique reference number is not mapped in Myer systems at this stage. It has been included in this document to allow for the future requirements of DOMEDI initiatives.

SEGMENT EXAMPLES

REF*IA*987456

REP*DP*4212


Segment N1 Name retail buying location (order level)


01 ENTITY IDENTIFIER CODE 0098 ID 02 02 M BY=Buying location 02 NAME 0093 AN 01 35 C Not used 03 IDENTIFICATION CODE QUALIFIER 0066 ID 01 02 C ‘92’ Assigned by buyer 04 IDENTIFICATION CODE 0067 AN 02 17 C Myer store number

NOTE Repeated within the order level loop for each store on this purchase order.

SEGMENT EXAMPLE

Nl*BY**92*001


Segment CUR Currency (order level)


01 ENTITY IDENTIFIER CODE 0098 ID 2 2 M BY=Buying party 02 CURRENCY CODE 0100 ID 3 3 M ISO currency cd 03 EXCHANGE RATE 0280 R 4 6 0 Multiplier conversion factor 04 ENTITY IDENTIFIER CODE 0098 ID 2 2 O SE=Selling party 05 CURRENCY CODE 0100 ID 3 3 O ISO currency cd 06 to 21 Not used

NOTE Used to specify the currency and conversion used in a transaction not yet in use by Myer.


Segment HL Hierarchical level tare/pallet (level data start)


01 HIERARCHICAL ID NUMBER 0628 AN 01 12 M Next number in sequence 02 HIERARCHICAL PARENT ID NUMBER 0734 AN 01 12 O Id number of the order level (HL01) 03 HIERARCHICAL LEVEL CODE 0735 ID 01 02 M T=Tare 04 HIERARCHICAL CHILD CODE 0736 ID 01 01 U Not used

SEGMENT EXAMPLE

HL*3*2*T


Segment MAN Marks and numbers pallet identification (tare level)


01 MARKS AND NUMBERS QUALIFIER 0088 ID 01 02 M GM=UCC 128 Serial shipping container code 02 MARKS AND NUMBERS 0087 AN 01 45 M The twenty digit code

SEGMENT EXAMPLE

MAN*GM*98765432101111133322


Segment HL Hierarchical level pack/carton (level data start)


01 HIERARCHICAL ID NUMBER 0628 AN 01 12 M Next number in sequence 02 HIERARCHICAL PARENT ID NUMBER 0734 AN 01 12 O ID number of the tare level (HL01) 03 HIERARCHICAL LEVEL CODE 0735 ID 01 02 M P=Pack 04 HIERARCHICAL CHILD CODE 0736 ID 01 01 U Not used

SEGMENT EXAMPLE

HL*4*3*P


Segment PO4 Item physical details (pack level)


01 PACK 0356 N0 01 06 O Not used 02 SIZE 0357 R 01 08 O Qty of SKU in a standard pack - Future use 03 UNIT OF MEASUREMENT CODE 0355 ID 02 02 C EA=Each, future use 04 PACKAGING CODE 0103 ID 05 05 U Not used 05 WEIGHT QUALIFIER 0187 ID 01 02 U Not used 06 GROSS WEIGHT PER PACK 0384 R 01 09 C Numeric 07 UNIT OF MEASUREMENT CODE 0355 ID 02 02 C KG=Kilogram 08 GROSS VOLUME PER PACK 0385 R 01 09 O Not used 09 UNIT OF MEASUREMENT CODE 0355 ID 02 02 C Not used 10 LENGTH 0082 R 01 08 O Numeric 11 WIDTH 0189 R 01 08 O Numeric 12 HEIGHT 0065 R 01 08 O Numeric 13 UNIT OF MEASUREMENT CODE 0355 ID 02 02 C MR

NOTE In a pick and pack structure this segment at the pack level, is only used to specify the carton weight and physical dimensions.

SEGMENT EXAMPLE

P04******10*KG


Segment PKG Marking, packaging, loading (pack level)


01 ITEM DESCRIPTION TYPE 0349 ID 01 01 M S=Structured 02 PACKAGING CHARACTERISTIC CODE 0753 ID 01 05 0 ‘36’ Package specifications 03 AGENCY QUALIFIER CODE 0559 ID 02 02 C VI=VICS 04 PACKAGING DESCRIPTION CODE 0754 AN 01 07 C Refer note 05 DESCRIPTION 0352 AN 01 80 U Not used

NOTES This segment, at the pack level, is used to specify the transport package.

PKG03 can contain a code from an industry code list which provides specific data about the marking, packaging or loading and unloading of a product.

The following codes are supported in VICS3020 ...

Part 1 Container type ( position 1) L Logical container P Physical container

Part 2 Container configuration (positions 2&3) 01 Carton 02 Carton, hanging garments 03 Carton, with hangers (not hanging) 04 Carton, with identifiable inner packs 05 Carton, with unidentifiable inner packs 06 Rack, hanging garments (GOH)

SEGMENT EXAMPLE

PKG*S*36*VI*P02


Segment MAN Marks and numbers carton identification (pack level)


01 MARKS AND NUMBERS QUALIFIER 0088 ID 01 02 M GM UCC=128 Serial shipping container code 02 MARKS AND NUMBERS 0087 AN 01 45 M The twenty digit code

NOTES This code is used to identify the carton.

Scanning equipment located in the Myer distribution centres will scan this code to determine the carton contents and store destination.

SEGMENT EXAMPLE

MAN*GM*98765432101111122233


Segment HL Hierarchical level (sub pack level data start)


01 HIERARCHICAL ID NUMBER 0628 AN 1 12 M Next number in sequence 02 HIERARCHICAL PARENT ID NUMBER 0734 AN 1 12 O ID num of the pack level 03 HIERARCHICAL LEVEL CODE 0735 ID 1 2 M Q=Subpack 04 HIERARCHICAL CHILD CODE 0736 ID 1 1 U Not used

NOTE Only used where sub packs exist otherwise this segment is omitted and item level becomes the next sequence.

SEGMENT EXAMPLE

HL*5*4*Q


Segment MAN Marks and numbers (subpack identification)


01 MARKS AND NUMBERS QUALIFIER 0088 ID 01 02 M GM UCC=128 Serial shipping container code 02 MARKS AND NUMBERS 0087 AN 01 45 M The twenty digit code

NOTE This code is used to identify the sub pack, where it exists.

SEGMENT EXAMPLE

MAN*GM*98765432101111122234


Segment HL Hierarchical level (item level data start)


01 HIERARCHICAL ID NUMBER 0628 AN 01 12 M Next number in sequence 02 HIERARCHICAL PARENT ID NUMBER 0734 AN 01 12 O ID number of the subpack level 03 HIERARCHICAL LEVEL CODE 0735 ID 01 02 M I=Item level 04 HIERARCHICAL CHILD CODE 0736 ID 01 01 U Not used

SEGMENT EXAMPLE

HL*6*5*I


Segment LIN Item identification


01 ASSIGNED IDENTIFICATION 0350 AN 01 11 O Not used 02 PRODUCT/SERVICE ID QUALIFIER 0235 ID 02 0 2 M EN=European Article Number 03 PRODUCT/SERVICE ID NUMBER 0234 AN 01 30 M APN 04-31 Not used

NOTE Include the APN number of the product being shipped in this segment.

SEGMENT EXAMPLE

LIN**EN*9398500041021


Segment SN1 Item detail shipment (item quantities)


01 ASSIGNED IDENTIFICATION 0350 AN 01 11 U Not used 02 NUMBER OF UNITS SHIPPED 0382 R 01 10 M Qty shipped for item in LIN 03 UNIT OF MEASUREMENT CODE 0355 ID 02 02 M EA=Each 04 QUANTITY SHIPPED TO DATE 0646 R 01 09 O Future use 05 QUANTITY ORDERED 0330 R 01 09 O Future use 06 UNIT OF MEASUREMENT CODE 0355 ID 02 02 C Future use 07 RETURNABLE CONTAINER LOAD MAKE-U 0728 ID 01 02 U Not used 08 LINE ITEM STATUS CODE 0668 ID 02 02 U Not used

NOTE Use this segment to specify the quantities associated with the item identified in the preceding LIN segment.

SEGMENT EXAMPLE

SN1**10*EA


Segment PO4 Item physical details (shipment level)


01 PACK 0356 NO 1 6 O Number of inner packs per outer pack unit 02 SIZE 0357 R 1 8 O Number of SKUs in the pack if inner packs are not used 03 UNIT OF MEASURE CODE 0355 ID 2 2 C EA=Each 04 PACKAGING CODE 0103 AN 5 5 O Not used 05 WEIGHT QUALIFIER 0187 ID 1 2 O Not used 06 GROSS WEIGHT PER PACK 0384 R 1 9 C Numeric value of gross pack weight per pack 07 UNIT OF MEASURE CODE 0355 ID 2 2 C KG=Kilogram 08 to 13 Not used

NOTES This segment is used to specify the inner pack of identical SKUs.

For example if the total SKUs in the carton were 72, packed in six inner packs with 12 SKUs per inner pack PO401 would be 6, PO402 would be 12.

This is used by the seller to define item packing variations.

If a manufacturer sells the item in a specific pack, for example six to a box, then PO402 would contain 6 and PO403 would contain code EA.

This segment can also be used to specify the weight for the item by using PO406 and PO407.

SEGMENT EXAMPLE

P04 *6*6*EA


Segment MEA Measurements


01 MEASUREMENT REFERENCE ID CODE 0737 ID 2 2 O PD=Physical dimensions 02 MEASUREMENT QUALIFIER 0738 ID 1 3 O DP=Depth HT=Height LN=Length WD=Width 03 MEASUREMENT VALUE 0739 R I 10 C Numeric value 04 UNIT OF MEASUREMENT CODE 0355 ID 2 2 C MR=Metre 05 to 09 Not used

NOTES This segment is used to specify physical measurements and dimensions.

This has been allowed for future document development and is not currently used by Myer.

SEGMENT EXAMPLE

MEA*PD*LN*1.5*MR


Segment PKG Marking, packaging, loading


01 ITEM DESCRIPTION TYPE 0349 ID 01 01 M 'S' Structured 02 PACKAGING CHARACTERISTIC CODE 0753 ID 01 05 O '34' Product marking 03 AGENCY QUALIFIER CODE 0559 ID 02 02 C 'VI' VICS 04 PACKAGING DESCRIPTION CODE 0754 AN 01 07 C See notes for list 05 DESCRIPTION 0352 AN 01 80 U Not used

NOTES This segment is used to notify Myer that ticketing (item marking) was not as originally requested or expected.

Part II of PKG04 describes what, if any, ticket is on the item. This is only for exceptions.

The receiver assumes all items are marked as requested if not otherwise stated.

PKG04 can contain a code from an industry code list which provides specific data about the marking, packaging or loading and unloading of a product.

The following codes are supported in VICS3020 ...

Part l Service type (positions 1&2) TN Ticketing service not as requested

Part 2 Ticket format code (positions 3&4) 01 No ticket 02 Hang tag (swiftach) 03 Gummed label 04 Pin ticket 05 String ticket (string around button) 06 Hang tag (securtach) 07 Dumbbell gum (jewellery) 08 Double gummed label (peel off on gummed label) 99 Non standard ticket

SEGMENT EXAMPLE

PKG*S*34*VI*TN01


Segment DTM Date/time reference


01 DATE/TIME QUALIFIER 0374 ID 3 3 M ‘036’ Expiration 02 DATE 0373 DT 6 6 C YYMMDD 03 to 05 Not used

NOTE This segment is used to advise use by date for perishable products where required.

SEGMENT EXAMPLE

DTM*036*950531


Segment ITA Allowance, charge or service


01 ALLOWANCE OR CHARGE INDICATOR 0248 ID 1 1 M A=Allowance C=Charge N=No allowance or charge 02 AGENCY QUALIFIER CODE 0559 ID 2 2 0 AX=ANSI X 12 03 SPECIAL SERVICES CODE 0560 ID 2 10 C FG=Free goods TC=Ticketing service 04 ALLOWANCE/CHARGE METHOD CODE 0331 ID 2 2 M Refer notes 05 ALLOWANCE/CHARGE NUMBER 0341 AN 1 16 O Number assigned by vendor 06 ALLOWANCE/CHARGE RATE 0359 R 1 9 O Rate per unit 07 ALLOWANCE/CHARGE TOTAL AMOUNT 0360 N2 1 9 O Total dollar amt 08 ALLOWANCE/CHARGE % QUALIFIER 0378 ID 1 1 O Refer notes 09 ALLOWANCE/CHARGE PERCENT 0332 R 1 6 O % 10 ALLOWANCE/CHARGE QUANTITY 0339 R 1 10 O Quantity allowed or different from order or invoice qty 11 UNIT OF MEASUREMENT CODE 0355 ID 2 2 C EA 12 QUANTITY 0234 R 1 15 O Numeric value 13 Not used 14 Not used

NOTES 01 bill back, 02 off invoice, 03 vendor cheque to customer, 04 credit customer account, 05 charge to be paid by vendor, 06 charge to be paid by customer.

1 item list cost, 2 item net cost, 3 discount/gross, 4 discount/net, 5 base price per unit, 6 base price amount, 7 base price amount less previous discount.

Used to specify allowances, charges or services.

Allowed for future use, not used by Myer at this stage.


Segment CTT Transaction totals


01 NUMBER OF LINE ITEMS 0354 N0 01 06 M The number of HL segments 02 HASH TOTAL 0347 R 01 10 U Not used 03 WEIGHT 0081 R 01 08 U Not used 04 UNIT OF MEASUREMENT CODE 0355 ID 02 02 U Not used 05 VOLUME 0183 R 01 08 U Not used 06 UNIT OF MEASUREMENT CODE 0355 ID 02 02 U Not used 07 DESCRIPTION 0352 AN 01 80 U Not used

SEGMENT EXAMPLE

CTT*6




01 NUMBER OF INCLUDED SEGMENTS 0096 NO 1 6 M Total number of segments in transaction 02 TRANSACTION SET CONTROL NUMBER 0329 AN 4 9 M Identifying control number assigned by originator

NOTE The transaction set control number must be the same number as in the ST segment.

SEGMENT EXAMPLE

SE*50*0001


Example ship note transmission Pick and pack structure

ST * 856*0001 Transaction set header BSN*00*12345*921225*111559*0001 Ship note number and date, pick and pack HL*1**S Shipment level start NTE*DEL*020 Deliver to DC 020 TD1*CTN25*256****G*160*KG Shipment quantity & weight TD5******CC Order status REF*CN*56789 Consignment note number DTM*068*070127 Date shipped DTM*067*070129 Scheduled delivery date N1*ST**92*020 Ship to DC 020 HL*2*1*O Order level start PRF*000000321301X020***921207 Myer PO number TD1*CTN25*20 Packages for store location TD5******CC Order status for store location REF*IA*987456 Suppliers reference number N1*BY**92*001 Myer store number 001 HL*3*2*P Pack (carton) level start - pack 1 PKG*S*36*VI*P02 Carton, hanging garments MAN*GM*98765432101111122233 Carton number HL*4*3*I Item level start LIN**EN*9398500041021 Item number SN1**12*EA Item quantities HL*5*3*I Item level start LIN**EN*9398500041221 Item number SN1**2*EA Item quantities HL*6*3*I Item level start LIN**EN*9398500041331 Item number SN1**12*EA Item quantities HL*7*2*P Pack (carton) level start -pack 2 PKG*S*36*VI*P02 Carton, hanging garments MAN*GM*98765432102222211133 Carton number HL*8*7*I Item level start LIN**EN*9398500041441 Item number SN1**10*EA Item quantities HL*9*1*O Order level, start, next store PRF*000000321301X020***921207 Myer PO number TD1*CTN25*5 Packages for store location TD5******CC Order status for store location REF*IA*987456 Suppliers invoice number Nl*BY**92*204 Myer store number 204 HL*10*9*P Pack (carton) level start - pack 1 PKG*S*36*VI*P02 Carton, hanging garments MAN*GM*98765432105555522233 Carton number HL*11*10*I Item level start LIN**EN*9398500041021 Item number SNl**10*EA Item quantities CTT*11 Number of HL segments SE*46*0001 Transaction set trailer


VICS 997 functional acknowledgment

Functional group ID = FA This standard provides the format and establishes the date contents of a functional transaction set. The purpose of this standard is to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets.

SEG ID NAME REQ DES

MAX USE

LOOP REPEAT

ST TRANSACTION SET HEADER M 1 USE AK1 FUNCTIONAL GROUP RESPONSE HEADER M 1 USE AK2 TRANSACTION SET RESPONSE HEADER O 1 AK2/999999 NOT USED AK3 DATA SEGMENT NOTE O 1 AK3/999999 NOT USED AK4 DATA SEGMENT NOTE O 99 NOT USED AK5 TRANSACTION SET RESPONSE TRAILER M 1 NOT USED AK9 FUNCTIONAL GROUP RESPONSE TRAILER M 1 USE SE TRANSACTION SET TRAILER M 1 USE



Level Header

Req Des Mandatory

Max Use 01

Loop _____________________

FLD #


TYPE MIN LEN

MAX LEN


01 TRANSACTION SET IDENTIFIER CODE

143 ID 3 3 M Code uniquely identifying a transaction set. 997 X12.20 functional acknowledgment.


329 AN 4 9 M Identifying control number assigned by the originator for a transaction set. The number is sequentially assigned, by the sender, starting with one within each functional group. For each functional group the first transaction set control number will be 0001 and incremented by one for each additional transaction set within the group.

NOTES The purpose of this segment is to indicate the start of a transaction set and to assign a control number.

The transaction set identifier (ST01 is intended for use by the translation routine of the interchange partners to select the appropriate transaction set definition, for example, 810 selects the invoice transaction set.


Segment AK1 Functional group response

Level Header

Req Des Mandatory

Max Use 01

Loop _____________________

FLD #


TYPE MIN LEN

MAX LEN


01 FUNCTIONAL IDENTIFIER CODE

479 ID 2 2 M Code identifying a group of application related transaction sets. This is the functional group ID of the group that is being acknowledged, for example, if an Advance Ship Note is being acknowledged the value would be SH; it is the value sent in GS01 for the original transmission.

02 GROUP CONTROL NUMBER

28 N 1 9 M Assigned number originated and maintained by the sender. This is the control number assigned to the group being acknowledged, for example, this is the control number assigned by the sender of the original transmission. Its value is the value sent in GS06 for the original transmission. The data interchange control number found in the GS segment in the functional group being acknowledged.

NOTES The purpose of this segment is to start acknowledgment of a functional group.


Segment AK9 Functional group response

Level Header

Req Des Mandatory

Max Use 01

Loop _____________________

FLD #

ELEMENT NAME

DICT NUM

TYPE MIN LEN

MAX LEN


01 FUNCTIONAL GROUP ACKNOWLEDGE CODE

715 ID 1 1 M Code indicating accept or reject condition based on the syntax editing of the functional group. A=Accepted. E=Accepted, but errors were noted. P=Partially accepted, at least one transaction set was rejected. R=Rejected.

02 NUMBER OF TRANSACTION SETS INCLUDED

97 N 1 6 M Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element.

03 NUMBER OF RECEIVED TRANSACTION SETS

123 N 1 6 M Number of transaction sets received.

04 NUMBER OF ACCEPTED TRANSACTION SETS

2 N 1 6 M Number of accepted transaction sets in a functional group.

05 FUNCTIONAL GROUP SYNTAX ERROR CODE

716 ID 1 3 O Code indicating error found based on the syntax editing of the functional group header and/or trailer. 1=Functional group not supported. 2=Functional group version not supported. 3=Functional group trailer missing. 4=Data interchange control number in the functional group header and trailer do not agree. 5=Number of included transaction sets does not match actual count.


716 ID 1 3 O


716 ID 1 3 O


Segment AK9 Functional group response cont’d


716 ID 1 3 O


716 ID 1 3 O

NOTES The purpose of this segment is to acknowledge acceptance or rejection of a functional group and report the number of included transaction sets from the original trailer, the accepted sets, and the received sets in this functional group.

If AK901 is ‘A’ or ‘E’ then the transmitted functional group is accepted. If AK901 is ‘R’, then the transmitted group is rejected.

The code values listed for AK905 will be the same for all occurrences of data element 716.



Level Summary

Req Des Mandatory

Max Use 01

Loop _____________________

FLD #


TYPE MIN LEN

MAX LEN


01 NUMBER OF INCLUDED SEGMENTS

96 N 1 6 M Total number of segments included in a transaction set including ST and SE segments.


329 AN 4 9 M Identifying control number assigned by the originator for a transaction set. This must be the same number as in the ST Segment (ST02) for the transaction set.

NOTES The purpose of this segment is to indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).

E is the last segment of each transaction set.

Supply Chain – Merchandise Logistics E-Commerce Advance ... · Supply Chain – Merchandise...

Documents

Transcript of Supply Chain – Merchandise Logistics E-Commerce Advance ... · Supply Chain – Merchandise...