MYER. Message Implementation Guideline - ORDRSP

Transcription

1 MYER Message Implementation Guideline - ORDRSP GS1AU General Merchandise Harmonised Guideline (Based on the EANCOM 2002 Guideline using UN/EDIFACT Directory D01B Edition) August 2016 Myer Purchase Order Response V1.7 August 2016 i Prepared by GS1 Australia

2 1. Introduction Disclaimer Change Control Reading this Document Application of ORDRSP within Myer Summary: Data Content Message Sample ORDRSP: Purchase Order Response Message Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

3 1. Introduction This document contains the Message Implementation Guidelines (MIG) for Myer s Purchase Order Response (ORDRSP) 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 address: bjohnson@gs1au.org Internet Web Site: For Myer related questions please contact: Myer EDI and Supply Chain Team Option 6, then option 2 Myer.eCommerce@myer.com.au In addition, Myer use the following EDI addresses for sending/receiving EDIFACT documents Production: (default) (used by some trading partners) A typical production interchange will therefore look like so: UNB+UNOA: :ZZ :ZZ : Testing / Accreditation: 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: :ZZ :ZZ : ' 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. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

4 3. Change Control Date Version Comments 21/07/ Initial Draft - complete document 27/07/ Release version 31/07/ Final Release - Notes edits 1/08/ Change RFF DE1060 from O to D, update sample message 25/11/ Added comments for Back Order Quantity 25/03/ Final changes for release 02/08/ Applied additional feedback and corrections Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

5 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 below 1 : 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 segments 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 sent 2 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 so if the group is not used, then the segment is not used either. However if the group is used the segment must be used. Similarly with data elements. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

6 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 O - Optional: may be sent. If sent and not used by Myer it will be ignored and will 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 element or code usage that are not available for use in this MIG. 5. Application of ORDRSP within Myer Myer will generate a number of Order types, however the Purchase Order Response message has only been implemented for the Customer Order types. No Response message is used for Blanket, Release or Allocation Order types. The three Response types implemented based on the MIG, with the key variations in message content, are identified below for each message type (for details refer to the segment details in the Orders MIG): Accepted In Full (Supplier can accept and deliver the Order as requested in the Myer-generated Customer Order): Response message is expected to be generated based on an actual physical stock check, not an inventory check No line detail is accepted for this Response type Only header and summary section of the message to be sent Supplier to proceed with processing and fulfilling the Order as no further detail is expected to be sent by Myer Rejected In Full (Supplier cannot accept and deliver the Order as requested in the Myer-generated Customer Order): Response message is expected to be generated based on an actual physical stock check, not an inventory check No line detail is accepted for this Response type Only header and summary section of the message to be sent Order is placed on hold until further notice by Myer Myer may choose to send a Purchase Order Cancellation, cancelling the Order, or may send a Purchase Order Change to replace the Order detail Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

7 Accepted With Proposed Change (Supplier can accept and deliver the Order with some proposed changes to the Order details as requested in the Myer-generated Customer Order): Response message is expected to be generated based on an actual physical stock check, not an inventory check Line detail for only those lines with a proposed change are expected to be sent back to Myer in the Response Order is placed on hold until further notice by Myer Myer will normally send a Purchase Order Change to replace the order detail Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

8 6. Summary: Data Content This section contains an overview of the content and structure of the Purchase Order Response message as an aid to understanding. It should be noted that while this is indicative of the content and structure of a Purchase Order Response 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 number U 0065 Message type Id ORDRSP 0052 Message type version number D 0054 Message type release number 01B 0051 Controlling agency UN 0057 Association assigned code EAN009 BGM 1001 Order type 231 Purchase Order Response Indicates message type is a Purchase Order Response 1004 Document number U Document number (preferably unique) to identify ORDRSP message 1225 Function code 4 Change Order is accepted with proposed change only detail lines with amendments are expected 27 Not accepted Order is rejected in full no detail lines expected 29 Accepted without amendment Order is accepted in full no detail lines expected DTM 2005 Date/time qualifier 137 Document date Indicates date provided is representative of the date of document creation 2380 Delivery date U 2379 Date/time format 102 CCYYMMDD Indicates input date (DTM.2380) is in the format CCYYMMDD Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

9 RFF 1153 Reference code qualifier ON Order number Reference to original Order number which the ORDRSP is responding to UO Ultimate customer's Order no. Reference to the Customer Order number as provided in the ORDERS message 1154 Reference number U 1060 Revision identifier U Document version, used to identify a document as an update to previous NAD 3035 Party qualifier BY Buyer Indicates party identification refers to buying supplier (i.e. Myer) SU Supplier Indicates party identification refers to supplier 3039 Party identification U Myer s GLN (NAD.3035 = BY ) or Myer s internal vendor code (NAD.3035 = SU ) 3055 Code list agency 9 GS1 code list Used when NAD.3035 = BY 92 Buyer assigned Used when NAD.3035 = SU LIN 1082 Line item sequence number U Sequential line number to uniquely identify an item line 1229 Action request/notification code 23 Proposed amendment Used for all changed line items (BGM.1225 = 4 ) 7140 Item number U Item s GTIN 7143 Item number type SRV GS1 GTIN Indicates item number reflects item s GTIN QTY 6063 Quantity qualifier 21 Ordered quantity Indicates QTY.6060 represents total quantity as ordered by buyer 6060 Quantity numeric value U 83 Back order quantity Indicates QTY.6060 represents quantity of item back ordered (requires Myer approval prior to use) 113 Quantity to be despatched Indicates QTY.6060 represents quantity of item able to be shipped 6411 Measure unit qualifier U Unit of measurement if not each DTM 2005 Date/time qualifier 506 Back order delivery date Indicates delivery date (DTM.2380) represents date of back order delivery (only used when QTY.6063 = 83 ) 2380 Delivery date U 2379 Date/time format 102 CCYYMMDD Indicates delivery date is in the format of CCYYMMDD RFF 1153 Reference code qualifier LI Line item reference Indicates reference number (RFF.1154) is a line number 1154 Reference number U Line number from the Order UNS 0081 Section identification S Indicates start of summary section CNT 6069 Control qualifier 2 Number of line items Control value represents number of LIN segments in Order Response 6066 Control value U UNT 0074 Number of message segments U Count of segments Total count of segments in Order Response 0062 Message reference number U Message number Message reference, matching UNH.0072 Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

10 7. Message Sample Accepted without amendment UNA:+.? ' UNB+UNOC: :ZZ :ZZ : ' UNH+100+ORDRSP:D:01B:UN:EAN009' BGM ' DTM+137: :203' RFF+UO: ' RFF+ON:CD D000:::1' NAD+BY ::9' NAD+SU ::92' UNS+S' UNT+9+100' UNZ+1+10 Change UNA:+.? ' UNB+UNOC: :ZZ :ZZ : ' UNH+101+ORDRSP:D:01B:UN:EAN009' BGM ' DTM+137: :203' RFF+UO: ' RFF+ON:CD D000:::1' NAD+BY ::9' NAD+SU ::92' LIN :SRV' QTY+21:5' QTY+113:4' UNS+S' CNT+2:4' UNT ' UNZ+1+11' Not accepted UNA:+.? ' UNB+UNOC: :ZZ :ZZ : ' UNH+102+ORDRSP:D:01B:UN:EAN009' BGM ' DTM+137: :203' RFF+UO: ' RFF+ON:CD D000:::1' NAD+BY ::9' NAD+SU ::92' UNS+S' UNT+9+102' UNZ+1+10 Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

11 8. ORDRSP: Purchase Order Response Message Introduction: This specification provides the definition of the GS1AU Harmonised ORDRSP 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) 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. Notes: The ORDRSP message is implemented by Myer for Customer Orders only. No ORDRSP messages are expected for all other Order types. Within the ORDRSP, no detail lines are expected for ORDRSP messages indicating the Order is Accepted without amendment / Not accepted. For Accepted with Proposed Changes, details lines are accepted only for those items which cannot be delivered at the quantity ordered. No other detail lines are accepted for items which can be fulfilled as ordered. 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 35 M 0090 Segment Group 1: RFF M 9999 M 0100 RFF Reference M 1 M 0150 Segment Group 3: NAD M 99 M 0160 NAD Name and address M 1 M 0970 Segment Group 26: LIN-QTY-DTM-SG31 M M 0980 LIN Line item M 1 O 1020 QTY Quantity C 99 O 1050 DTM Date/time/period C 35 M 1330 Segment Group 31: RFF M 9999 M 1340 RFF Reference M 1 M 2200 UNS Section control M 1 O 2220 CNT Control total C 10 M 2270 UNT Message trailer M 1 Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

12 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 Purchase Order Response message is ORDRSP. Note: Purchase Order Response messages conforming to this document must contain the following data in segment UNH, composite S009: Data element Value 0065 ORDRSP 0052 D B 0051 UN Dependency Notes: Semantic Notes: Comments: Notes: Purchase Order Response 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 Purchase Order Response based on the D.01B directory under the control of the United Nations. Example: UNH+100+ORDRSP:D:01B:UN:EAN007' The Order Response message is only used by Myer for Customer Orders. 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 exactly the same. 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. ORDRSP Purchase Order Response message A code to identify the Purchase Order Response message. GS1 Description: Message from the seller to the buyer, responding to a Purchase Order or Purchase Order Change 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 B Message approved and issued in the second 2001 release of the UNTDID (United Nations Trade Data Interchange Directory). Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

13 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 Purchase Order Response. EAN009 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. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

14 Segment: BGM Beginning of message Position: 0020 Group: Level: 0 Usage: Mandatory Max Use: 1 Purpose: A segment by which the sender must uniquely identify the order response by means of its unique number and when necessary its function Dependency Notes: Semantic Notes: Comments: Notes: The message function code (BGM.1225) is a critical element in this segment. The codes detailed in DE 1225 will be used in the following way: BGM.1225 = 29 indicates that the referenced Purchase Order is accepted in its entirety. In this case only header and summary details are permitted. BGM.1225 = 27 indicates that all items in the referenced Purchase Order are unable to fulfilled, and the Order is being rejected completely. In this case only header and summary details are permitted. BGM.1225 = 4 indicates that the referenced Purchase Order has been accepted, however there are issues with the Purchase Order. In this case the ORDRSP will include a proposed modification to the Order that the supplier is able to fulfil (i.e. the content from the referenced Order, modified if necessary to reflect the items, quantities, prices, dates and other conditions of supply that the supplier is able to meet, will be returned in the ORDRSP). Only changed line items should be returned. Example: BGM ' The ORDRSP is transmitted by a supplier in response to a previous Order or Order Change message. All references other than the document number DE 1004 are in the RFF segment. Data Element Summary Data Component R Element Element Name Attributes 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. 231 Purchase Order Response Response to a Purchase Order already received. X 1131 Code list identification code C an..17 Code identifying a user or association maintained code list. X 3055 Code list responsible agency code C an..3 Code specifying the agency responsible for a code list. 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. Order Response number assigned by document sender. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

15 It is recommended that the length of 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 element in this segment. The restricted codes detailed in DE 1225 have the following definitions: 4 = Change - The supplier accepts to supply the goods or services requested in the Order or Order Change message, but requires changes to one or more of the items. 27 = Not accepted - The supplier declines to supply the goods detailed in a Purchase Order or Purchase Order Change Request. 29 = Accepted without amendment - The supplier accepts to supply the goods or services requested according to the terms set out in the Purchase Order or Purchase Order Change Request. 4 Change Message containing items to be changed. GS1 Description: Message containing items (e.g. line items, goods items, customs items, equipment items) to be changed in a previously sent message or an existing data base. 27 Not accepted Message to inform that the referenced message is not accepted by the recipient. Myer do not allow line details to be returned with this response type. 29 Accepted without amendment Referenced message is entirely accepted. Myer do not allow line details to be returned with this response type. X 4343 RESPONSE TYPE CODE C an..3 Code specifying the type of acknowledgment required or transmitted. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

16 Segment: DTM Date/time/period Position: 0030 Group: Level: 1 Usage: Mandatory Max Use: 35 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A segment specifying general dates and, when relevant, times related to the whole message. The segment must be specified at least once to identify the order response date. Examples of the use of this DTM segment are: Lead times that apply to the whole of the Order response and, if no schedule is to be specified, the delivery date. The Date/time/period segment within other Segment groups should be used whenever the date/time/period needs to be logically related to another specified data item. e.g. Payment due date is specified within the PAT Segment group. This segment is used to specify dates/times relating to the Order Response, or if required, dates relating to the delivery or collection of the goods. DTM.2005: Identification of the 'Document/message date/time' (code value 137) is mandatory in an EANCOM message. Example: DTM+137: :203' Only used by Myer for the document date, no other dates are applicable at the header level. Any changes to delivery dates must be identified at the LIN level. Data Element Summary Data Component M Element Element Name Attributes 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. 137 Document/message date/time (2006) Date/time when a document/message is issued. This may include authentication. Required by Myer for all Order Response messages. 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 Calendar date including time with minutes: C=Century; Y=Year; M=Month; D=Day; H=Hour; M=Minutes. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

17 Group: RFF Segment Group 1: Reference Position: 0090 Group: Level: 1 Usage: Mandatory Max Use: 9999 Purpose: A group of segments for giving references and where necessary, their dates, relating to the whole message, e.g. contract number, import/export licence number, reservation number. Notes: A group of segments for giving relevant references and where necessary, their dates relating to the whole message. Segment Summary Pos. Seg. Req. Max. Group: No. ID Name Des. Use Repeat M 0100 RFF Reference M 1 Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

18 Segment: RFF Reference Position: 0100 (Trigger Segment) Group: Segment Group 1 (Reference) Mandatory Level: 1 Usage: Mandatory Max Use: 1 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A segment identifying the reference by its number and where appropriate a line number within a document. This segment is used to refer to the Order or Order Change message to which the Order Response is responding. Example: RFF+UO: ' References the OMS Sales Order number RFF+ON:CD D000:::1' References the Order number CD D000 Data Element Summary Data Component M Element Element Name Attributes C506 REFERENCE M Identification of a reference. M 1153 Reference code qualifier M an..3 Code qualifying a reference. ON Order number (buyer) [1022] Reference number assigned by the buyer to an order. Required by Myer for all Order Response messages UO Ultimate customer's order number The originator's order number as forwarded in a sequence of parties involved. Implemented by Myer, will be the OMS Sales Order number as sent in the original Order 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. D 1060 Revision identifier C an..6 To identify a revision. Only used when DE1153 = ON. Required by Myer for all Order Response messages and references the Original PO revision number. This must match the value of the latest Purchase Order/Order Change received (in BGM.1060). Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

19 Group: NAD Segment Group 3: Name and address Position: 0150 Group: Level: 1 Usage: Mandatory Max Use: 99 Purpose: A group of segments identifying the parties with associated information. Segment Summary Pos. Seg. Req. Max. Group: No. ID Name Des. Use Repeat M 0160 NAD Name and address M 1 Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

20 Segment: NAD Name and address Position: 0160 (Trigger Segment) Group: Segment Group 3 (Name and address) Mandatory Level: 1 Usage: Mandatory Max Use: 1 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A segment identifying names and addresses of the parties, in coded or clear form, and their functions relevant to the order response. Identification of the seller and buyer parties is mandatory for the order response message. 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, but the Consignee or Delivery address may vary and would have to be clearly specified, preferably in structured format. This segment is used to identify the trading partners involved in the Order Response. Identification of the buyer and supplier of goods and services is mandatory using DE's 3035 and C082. Example: NAD+BY ::9' Indicates the buyer s GLN is NAD+SU ::92' Indicates the supplier s buyer-assigned identification is Data Element Summary Data Component Element Element Name Attributes 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 Order Response messages SU Supplier Party who supplies goods and/or services. GS1 Description: Party which provides service(s) and/or manufactures or otherwise has possession of goods, and consigns or makes them available in trade. Required by Myer for all Order Response messages, this is the Myer-allocated internal vendor number. R C082 PARTY IDENTIFICATION DETAILS C Identification of a transaction party by code. M 3039 Party identifier M an..35 Code specifying the identity of a party. X 1131 Code list identification code C an..17 Code identifying a user or association maintained code list. R 3055 Code list responsible agency code C an..3 Code specifying the agency responsible for a code list. 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. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

21 92 Assigned by buyer or buyer's agent Codes assigned by a buyer or buyer's agent. Required by Myer where 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 Free form description of a name and address line. X 3124 Name and address description C an..35 Free form description of a name and address line. X 3124 Name and address description C an..35 Free form description of a name and address line. X 3124 Name and address description C an..35 Free form description of a name and address line. X C080 PARTY NAME C Identification of a transaction party by name, one to five lines. Party name may be formatted. X 3036 Party name M an..35 Name of a party. X 3036 Party name C an..35 Name of a party. X 3036 Party name C an..35 Name of a party. X 3036 Party name C an..35 Name of a party. X 3036 Party name C an..35 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 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 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 To identify a street and number and/or Post Office box number. 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 Code identifying a user or association maintained code list. X 3055 Code list responsible agency code C an..3 Code specifying the agency responsible for a code list. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

22 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 Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

23 Group: LIN Segment Group 26: Line item Position: 0970 Group: Level: 1 Usage: Mandatory Max Use: Purpose: A group of segments providing details of the individual ordered items. Notes: Only changed line items (BGM.1225 = 4 ), are allowed to be returned in this Order Response segment. All other response types require header and summary detail only to be returned, and as such should not populate this segment group. Segment Summary Pos. Seg. Req. Max. Group: M No. ID Name Des. Use Repeat 0980 LIN Line item M 1 O 1020 QTY Quantity C 99 O 1050 DTM Date/time/period C Segment Group 31: Reference M 9999 Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

24 Segment: LIN Line item Position: 0980 (Trigger Segment) Group: Segment Group 26 (Line item) Mandatory Level: 1 Usage: Mandatory Max Use: 1 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A segment identifying the line item by the line number and configuration level, and additionally, identifying the product or service ordered. Other product identification numbers, e.g. Buyer product number, etc., can be specified within the following PIA segment. This segment is used to identify the product being responded to by means of a GS1 GTIN. The detail section of the Order Response is formed by a repeating group of segments, always starting with the LIN segment. DE 1229: Action request code is the critical DE in this segment. The following code value definitions apply: 23 = Proposed amendment: the supplier accepts to supply the line item in a Purchase Order, but requires one or more changes to the terms set out in the referenced message, as indicated by the data in, and following, the LIN segment. Example: LIN :SRV' Data Element Summary Data Component R Element Element Name Attributes 1082 LINE ITEM IDENTIFIER C an..6 To identify a line item. Application generated sequence number R 1229 ACTION REQUEST/NOTIFICATION DESCRIPTION C an..3 CODE Code specifying the action to be taken or already taken. 23 Proposed amendment A code used to indicate an amendment suggested by the sender. Implemented by Myer for all Customer Orders. Contains the supplier s proposed change to the ordered item. D C212 ITEM NUMBER IDENTIFICATION C Goods identification for a specified source. R 7140 Item identifier C an..35 To identify an item. Format n..14 GTIN - this is the number of the article being ordered. R 7143 Item type identification code C an..3 Coded identification of an item type. 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 Code identifying a user or association maintained code list. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

25 X 3055 Code list responsible agency code C an..3 Code specifying the agency responsible for a code list. 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. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

26 Segment: QTY Quantity Position: 1020 Group: Segment Group 26 (Line item) Mandatory Level: 2 Usage: Conditional (Optional) Max Use: 99 Purpose: A segment identifying the product quantities e.g. ordered quantity. Dependency Notes: Semantic Notes: Comments: Notes: This segment is used to specify quantity information related to the current line item. Example: QTY+21:48' The ordered quantity is 48 QTY+113:30' The deliverable quantity is 30 QTY+83:18' The back ordered quantity is 18 Data Element Summary Data Component M Element Element Name Attributes 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. 21 Ordered quantity The quantity which has been ordered. 83 Backorder quantity The quantity of goods that is on back-order. NOTE: Only to be used under circumstances where agreement with Myer has been arranged. All other orders should not populate this quantity. GS1 Description: Quantity of a product for back order purposes. 113 Quantity to be delivered The quantity to be delivered. M 6060 Quantity M an..35 Alphanumeric representation of a quantity. D 6411 Measurement unit code C an..3 Code specifying the unit of measurement. This DE is only used if the product being responded to is a variable quantity product. Myer assume unit of measurement is EA (each) unless otherwise stated. Refer to D.01B Data Element Dictionary for acceptable code values. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

27 Segment: DTM Date/time/period Position: 1050 Group: Segment Group 26 (Line item) Mandatory Level: 2 Usage: Conditional (Optional) Max Use: 35 Purpose: A segment specifying date/time/period details relating to the line item only. Dependency Notes: Semantic Notes: Comments: Notes: This segment is used to specify any dates related to the current line item. Example: DTM+506: :102' This example indicates the back order delivery is to be made on the 30th of August Implemented by Myer - Required only when one of the preceding QTY segments is a back order quantity (QTY.6063 = 83 ). This will be the date back ordered item is expected to be delivered. Data Element Summary Data Component M Element Element Name Attributes 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. 506 Back order delivery date/time/period The date/time/period during which the delivery of a back order will take, or has taken, place. Required by Myer if back order quantity is proposed. 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: C = Century; Y = Year; M = Month ; D = Day. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

28 Group: RFF Segment Group 31: Reference Position: 1330 Group: Segment Group 26 (Line item) Optional Level: 2 Usage: Optional Max Use: 9999 Purpose: A group of segments giving references and where necessary, their dates, relating to the line item. Segment Summary Pos. Seg. Req. Max. Group: No. ID Name Des. Use Repeat M 1340 RFF Reference M 1 Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

29 Segment: RFF Reference Position: 1340 (Trigger Segment) Group: Segment Group 31 (Reference) Mandatory Level: 2 Usage: Mandatory Max Use: 1 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A segment identifying the reference by its number and where appropriate a line number within a document. This segment is used to specify any references which are applicable to the current line item only. References stated here will override those specified in the heading section where the same qualifier is used. Example: RFF+LI:6' This example references line (LIN) number 6 of the buyer s Order specified in the header RFF segment (RFF.1154). Data Element Summary Data Component M Element Element Name Attributes C506 REFERENCE M Identification of a reference. M 1153 Reference code qualifier M an..3 Code qualifying a reference. LI Line item reference number (1156) Reference number identifying a particular line in a document. R 1154 Reference identifier C an..70 Identifies a reference. The Myer line item number from the referenced Order. 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. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

30 Segment: UNS Section control Position: 2200 Group: Level: 0 Usage: Mandatory Max Use: 1 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A service segment placed at the start of the summary section to avoid segment collision. Purchase Order Response summary section This segment is used to separate the detail and summary sections of the message. Example: UNS+S' Data Element Summary Data Component Element Element Name Attributes M 0081 SECTION IDENTIFICATION M a1 Separates sections in a message. S Detail/summary section separation To qualify the segment UNS, when separating the detail from the summary section of a message. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

31 Segment: CNT Control total Position: 2220 Group: Level: 1 Usage: Conditional (Optional) Max Use: 10 Purpose: A segment by which control totals may be provided by the sender for checking by the receiver. Dependency Notes: Semantic Notes: Comments: Notes: This segment is used to provide message control totals. Example: CNT+2:15' This indicates the total number of line items in the ORDRSP is 15. Data Element Summary Data Component M Element Element Name Attributes 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. 2 Number of line items in message Self-explanatory. GS1 Description: The total number of LIN segments in the message. Implemented by Myer control totals are matched against calculated totals. M 6066 Control total value M n..18 To specify the value of a control quantity. X 6411 Measurement unit code C an..3 Code specifying the unit of measurement. Myer Purchase Order Response V1.7 August Prepared by GS1 Australia

32 Segment: UNT Message trailer Position: 2270 Group: Level: 0 Usage: Mandatory Max Use: 1 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: 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. This segment is a mandatory UN/EDIFACT segment. It must always be the last segment in the message. Example: UNT+107+ME000001' Data Element Summary Data Component M Element Element Name Attributes 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 numbered detailed here should match the one specified in the UNH segment (UNH.0062). Myer Purchase Order Response V1.7 August Prepared by GS1 Australia