E-Commerce Purchase Orders - Myer Supplier Information Website

Supply Chain – Merchandise LogisticsE-Commerce Purchase OrderE-Commerce Purchase Order Page 1 of 53October 2008© Myer Pty Ltd

ContentsIntroduction___________________________________________ 3E-Commerce orderingHow Myer Orders merchandise _____________________________________ 4Purchase order format _____________________________________________ 4Basic purchase order _______________________________________________ 5Spreadsheet purchase order_________________________________________ 9Combination basic & spreadsheet purchase order _____________________ 13Confirmation of EDI document retrieval _____________________________ 16Myer document formats ___________________________________________ 17SegmentsANSI X12 envelope structure ___________________________________________ 18Segment ISA Interchange control header __________________________ 19Segment GS Functional group header ____________________________ 23Segment ST Transaction set header ______________________________ 25Segment SE Transaction set trailer _______________________________ 26Segment GE Group control trailer ________________________________ 27Segment IEA Interchange control trailer ___________________________ 28VICS 850 purchase order _______________________________________________ 29Segment ST Transaction set header ______________________________ 30Segment BEG Beginning segment for purchase order ________________ 31Segment REF Reference numbers _________________________________ 32Segment SSS Special services ____________________________________ 33Segment DTM Date/time reference ________________________________ 35Segment SHH General schedule ___________________________________ 36Segment N1 Name _____________________________________________ 37Segment PO1 Purchase order baseline item data ____________________ 38Segment CTP Pricing information _________________________________ 39Segment SDQ Destination quantity ________________________________ 40Segment CTT Transaction totals __________________________________ 42Segment SE Transaction totals __________________________________ 43VICS 997 functional acknowledgment ___________________________________ 44Segment GS Functional Group Header ___________________________ 45Segment ST Transaction set header ______________________________ 47Segment AK1 Functional group response___________________________ 48Segment AK9 Functional group response___________________________ 49Segment SE Transaction set trailer _______________________________ 51Appendix Functional acknowledgment__________________ 52E-Commerce Purchase Order Page 2 of 53October 2008© Myer Pty Ltd

IntroductionPurpose of this implementation guideThe purpose of this guide is to provide suppliers with the necessary information to enable theimplementation of receiving electronic purchase orders from Myer Pty LtdWho should use this guideThis guide is intended for use by Myer suppliers to prepare for the implementation of Electronic DataInterchange (EDI) and to assist with applications integration, thereby ensuring successful electronic trading.E-Commerce Purchase Order Page 3 of 53October 2008© Myer Pty Ltd

E-Commerce orderingHow Myer orders merchandiseWithin the VICS standards, there are four purchase order types ...(RE)(SA)(BK)(RL)Re orderIndent orderUnallocated/unapportioned orderRelease orderThese methods of ordering are denoted within the BEG segment and are defined as follows ...RESABKRLMyer uses RE where basic merchandise is being ordered via the Automated StockReplenishment (ARS) or the (KAB) replenishment systemA stand alone order will be used for indent ordersA blanket order will be used when the supplier is to reserve merchandise, but not deliver untilallocation is forwarded in the form of a release orderA release order will be used when merchandise has been allocated from the respective blanketorderPurchase order formatMyer uses either a basic or a spreadsheet purchase order format dependant upon the delivery point.The following section provides you with samples of the Myer EDI purchase order and an explanation of thesegments and associated codes.These sample purchase orders are taken from the GE EDI*PC software and are displayed in an unformattedflat file print.E-Commerce Purchase Order Page 4 of 53October 2008© Myer Pty Ltd

E-Commerce ordering cont’dBasic purchase orderA basic purchase order is one in which the merchandise is delivered directly to one central location - aregional distribution centre.*GE850 031SAU 00200*>. 1 9313164000009 2 ZZ 9311153000009 3 4 920508 ZZ9311153000009 X 002040VICS 5BEG00RE 6 000000340115X020 920508 8REFDP4262 9SSSNVITC 99 10DTM037920515 11DTM001920529 12SHHSC 13N1 BS 92020 14PO1 15 17 (i) EA (ii) 29 (iii) TEEN (iv) 9311153202007CTPRSRES 16 42PO1 10EA 35TEEN9311153203004CTPRSRES 42PO1 12EA 49.09TEEN9311153204001CTPRSRES 42PO1 10EA 63.53TEEN9311153207002CTPRSRES 42PO1 7EA 65.84TEEN9311153408003CTPRSRES 42PO1 20EA 57.75TEEN9311153052008CTPRSRES 42PO1 14EA 70.46TEEN9311153053005CTPRSRES 42PO1 15EA 49.09TEEN9311153512007CTPRSRES 42CTT 8 17E-Commerce Purchase Order Page 5 of 53October 2008© Myer Pty Ltd

E-Commerce ordering cont’dBasic purchase order cont’d16 CTPThe retail price of each line item ...17 CTT♦ RS Resale♦ RES Retail price $42Control total describing the number of individual line items contained within the transaction set.Used to check that the complete transmission has been received.E-Commerce Purchase Order Page 8 of 53October 2008© Myer Pty Ltd

E-Commerce ordering cont’dSpreadsheet purchase orderThe spreadsheet purchase order is used when merchandise is delivered to multiple store locations, asidentified in the PO1 and SDQ segments. With this information the supplier is required to pack the correctstore/merchandise combinations and deliver directly to stores. This is not intended for use in The Myer.*GE850 031SAU 00200*>. 1 9313164000009 2 ZZ 9314442000001 3 920508 4 ZZ9314442000001 X 002040VICS 5BEG00RE 6 0000592867X020 7 920508 8REFDP4262 9SSSNVITC 99 10DTM037920515 11DTM001920529 12SHHSC 13PO1 14 17 (i) EA (ii) 29 (iii) TEEN (iv) 9314442092495CTP 15 42SDQ 16 EA92201 7 17 219 10 18PO1 20EA 29TEEN9314442092570CTPRSRES 42SDQEA92204 5215 5220 5222 5PO1 7EA 29TEEN9134442092655CTPRSRES 42SDQEA92203 3204 3214 1PO1 5EA 29TEEN9314442092730CTPRSRES 42SDQEA92215 3219 2PO1 14EA 29TEEN9314442092815CTPRSRES 42SDQEA92201 5203 3204 4209 2PO1 20EA 29TEEN9314442092501CTPRSRES 42SDQEA92211 7215 10220 3CTT6 19E-Commerce Purchase Order Page 9 of 53October 2008© Myer Pty Ltd

E-Commerce ordering cont’dSpreadsheet purchase order cont’d1 *GE850 031SAU 00200*>GE envelope structure which is inserted by the EDI*PC software for inbound documents. Thisenvelope structure is also required for all outbound documents. (Refer to EDI*PC System Version 7,User Guide, Appendix E)2 Sender identifierMyer EDI address, utilises the 13 digit EDI address as per EDICA guidelines. This will include a validcheck digit.3 Receiver identifierSupplier’s EDI address, as per EDICA guidelines.4 Date and time of transmissionDate and time when the purchase order was sent.5 X002040VICSThe current document standard and version release number.6 BEG00REThe beginning segment, where 00 is the original order, seen for the first time, and RE is the re order ofbasic merchandise.7 000000340115X020A buying office raised purchase order number and region DC suffix.8 YY/MM/DDThe date when the purchase order was created.9 REFDPThe reference number of the department. This refers exclusively to Myer internal class group. Thisnumber is beneficial to suppliers who supply across the business.E-Commerce Purchase Order Page 10 of 53October 2008© Myer Pty Ltd

E-Commerce ordering cont’dCombination basic & spreadsheet purchase orderIt is also possible to transmit a purchase order that is a combination of the basic purchase order and thespreadsheet purchase order.This document includes both N1 and SDQ segments and consequently the N1 segment overrides the SDQsegment for destination/delivery points, as SDQ pertains to the individual store packing information.This type of order may also be used where a supplier is not ticketing, but is packing by store.Where a supplier undertakes to produce tickets conforming to Myer specifications and to pre mark and packmerchandise by store for delivery to a central location, this type of purchase order will be used.NoteSuppliers wishing to produce tickets must have the format approved by Myer before proceeding.E-Commerce Purchase Order Page 13 of 53October 2008© Myer Pty Ltd

E-Commerce ordering cont’dCombination basic & spreadsheet purchase order cont’d*GE850 031SAU 00200*>. 9313164000009 ZZ 9414613000004 ZZ9414613000004 X 00204VICSBEG00RE000000340115X020 920508REFDP4262SSS 1 NVI 2 TC 99 3DTM037920515DTM001920529SHHSCN1 BS 92020 4PO1 5 16EA 16.20TEEN9414613000971 SK65882092 6CTPRSRES 7 42SDQ 8 EA92201 7006 3008 6PO1 13EA 16.20TEEN9414613100980 SK65882115CTPRSRES 42SDQEA92001 6004 4014 3PO1 6EA 16.20TEEN9414613100995 SK65882139CTPRSRES 42SDQEA92005 2007 2009 2PO1 2EA 16.20TEEN9414613101046 SK65882153CTPRSRES 42SDQEA92004 2PO1 13EA 16.20TEEN9414613101060 SK65882160CTPRSRES 42SDQEA92004 5005 5009 3PO1 9EA 16.20TEEN9414613101077 SK65882856CTPRSRES 42SDQEA92001 6004 3PO1 11EA 18TEEN9414613101107 SK65882924CTPRSRES 42SDQEA92007 7011 2012 2PO1 6EA 18TEEN9414613101176 SK65882956CTPRSRES 42SDQEA92004 1007 3010 2CTT8E-Commerce Purchase Order Page 14 of 53October 2008© Myer Pty Ltd

E-Commerce ordering cont’dCombination basic & spreadsheet purchase order cont’dThe header details for this type of purchase order are the same for those outlined in the previous sectionsdescribing basic and spreadsheet purchase orders. For example, BEG, REF, DTM, SHH, N1 and SDQsegments. Therefore, only the SSS, N1 and SDQ segments and codes are explained below.1 SSS2 NVISpecial services segment, used to describe an order as pre ticketed, or promotional.Mandatory codes describing if the order is promotional, or pre ticketed.NVINo charge allowanceVICS document version is being used3 TC 99The ticket type information that must be decided upon, prior to receiving the order.For example, 99 is the pre ticketed order.NoteIn the event of promotion type orders, TC will be replaced by PR.4 N1 BS 920205 PO1Describes where the supplier’s terms and conditions specify delivery to distribution centres.For example, 020 requires delivery to Altona distribution centre.The purchase order baseline item date. This remains unaltered, pending the EANs being used.6 SK658820927 CTP8 SDQThe SKU supplied Myer keycode (65882092). This keycode is an additional check for merchandise tobe ticketed.The retail price of each line item ...♦ RS Resale♦ RES Retail price $42Included when the supplier pre packs merchandise by store allocations.E-Commerce Purchase Order Page 15 of 53October 2008© Myer Pty Ltd

E-Commerce ordering cont’dConfirmation of EDI document retrievalMyer requires the VICS 997 functional acknowledgment (FA) document to be generated by EDI tradingpartners, each time a purchase order is retrieved from their mailbox.The purpose of the FA document is to provide confirmation that a supplier has retrieved a purchase orderfrom their mailbox. The document does not serve any other purpose than to confirm whether the content ofa purchase order has been received intact. However, if the content is unclear, it is the responsibility of thesupplier to promptly contact the Supplier Liaison Team, who will arrange for another transmission.When establishing trading partnerships, Myer will ensure a separate trading partnership is initiated forfunctional acknowledgments.In the event of a supplier using the GE EDI*PC software package a further activity needs to be includedbefore the FA document process is complete. This task exists within the EDI Express, whereby the FAselection option must be accessed.Upon entering this option, the FA selection table must be completed in order to flat an FA (as shown in theAppendix). It is the responsibility of the supplier to ensure that the table is completed, before electronictrading is to commence.E-Commerce Purchase Order Page 16 of 53October 2008© Myer Pty Ltd

E-Commerce ordering cont’dMyer EDI document formatsThe following sections outline the formats for the ...ANSI X12 Version 00200Envelope structure850 VICS 2040 Purchase order997 VICS 2040 Functional acknowledgmentAll describe the relevant segments and codes pertinent for Myer EDI transactions.E-Commerce Purchase Order Page 17 of 53October 2008© Myer Pty Ltd

ANSI X12 envelope structureTransaction SetInterchange Control StructureVersion 00200This 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 functionalgroups within each transmission. The ST segment marks the beginning of each transaction set (electronicdocument). 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 MANDATORYGS FUNCTIONAL GROUP HEADER MANDATORYST TRANSACTION SET HEADER (FOLLOWED BY TRANSACTION SET SEGMENTS) MANDATORYSE TRANSACTION SET TRAILER MANDATORYGE FUNCTIONAL GROUP TRAILER MANDATORYIEA INTERCHANGE CONTROL TRAILER MANDATORYE-Commerce Purchase Order Page 18 of 53October 2008© Myer Pty Ltd

Segment ISAInterchange control headerLevelReq DesEnvelopeMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTSO1AUTHORISATIONINFORMATIONQUALIFIER02 AUTHORISATIONINFORMATION03 SECURITYINFORMATIONQUALIFIER101 ID 2 2 M Code to identify the type of information in theauthorisation information.Authorisation information is used to accommodate aUCS communications ID. It is only used when usingANSI standard and UCS communications. Normallythe value is 00.00=No authorisation information is present (nomeaningful information in I02).The interchange control number value in this headermust match the value in the same data element inthe corresponding interchange control trailer.102 AN 10 10 M Information used for additional identification orauthorisation of the sender or the data in theinterchange. The type of information is set by theauthorisation information qualifier.Normally this field is blank. If ISA01 is 01 this fieldwill contain the UCS communications IS.The first occurrence of the (byte 4) defines theactual value of the data element separator and isgraphically displayed as an asterisk “ “ “ in otherANSIX12 data segment documentation (eg the PO1segment). The first occurrence of the , 1 byteafter the data element ISA16, defines the actualvalue of the segment terminator and is graphicallydisplayed as NL in other ANSI ASCX12 datasegment documentation (eg the BFR segment inANSIX12.22).103 ID 2 2 M Code to identify the type of information in theSecurity Information.Security Information is only used when using theUCS Communication standard. Normally the valueis 00.00=No security information present (no meaningfulinformation in 104).E-Commerce Purchase Order Page 19 of 53October 2008© Myer Pty Ltd

Segment ISAInterchange control header cont’d04 SECURITYINFORMATION05 INTERCHANGEID QUALIFIER06 INTERCHANGESENDER07 INTERCHANGEID QUALIFIER104 AN 10 10 M This is used for identifying the security informationabout the sender on the data in the interchange.The type of information is set by the securityinformation qualifier.Normally this field is blank. If ISA03 is 01 this fieldwill contain a password that has been agreed to bythe sender and receiver.105 ID 2 2 M Qualifier to designate the system/method of codestructure used to designate the sender or receiver idelement being qualified.The interchange ID qualifier is used to define thecode used in ISA06 to identify sender of theinterchange.ZZ=mutually defined.106 ID 15 15 M 9313164000009=Myer ID.Identification code published by the sender for otherparties to use as the receiver ID to route data tothem. The sender always codes this number in thesender ID element.The identification code described by ISA05. Leftjustified, blank fill.105 ID 2 2 M Qualifier to designate the system/method of codestructure used to designate the sender or receiverID element being qualified.The interchange ID qualifier is used to define thecode used, in ISA08, to identify receiver of theinterchange.ZZ=mutually defined.08 INTERCHANGERECEIVER107 ID 15 15 M Supplier ID.Identification code published by the receiver of thedata. When sending, it is used by the sender astheir ID, thus other parties sending to them will usethis as receiving ID to route data to them.The identification code described by ISA07. Leftjustified, blank fill.09 DATE 108 DT 6 6 M Date of the interchange ISA generated (YYMMDD).The date the interchange was created in thesender’s system; submit date.10 TIME 109 TM 4 4 M Time of the interchange created (HHMM) in thesender’s system; submit time. 24 hour clock.11 INTERCHANGESTANDARDSIDENTIFIER110 ID 1 1 M Code to identify the agency responsible for thecontrol standard used by the message that isenclosed by the interchange header and trailer.U US EDI Community of X12, TDCC and UCS.E-Commerce Purchase Order Page 20 of 53October 2008© Myer Pty Ltd

Segment ISAInterchange control header cont’d12 INTERCHANGEVERSION ID13 INTERCHANGECONTROLNUMBER14 ACKNOWLEDGMENTREQUESTED15 TESTINDICATOR16 SUBELEMENTSEPARATOR111 ID 5 5 M This version number covers the interchange controlsegment only. Positions 1-3 of the field = majorversion, 4-5 of the field = release level of theversion.This version number is for the envelope only. It isnot the same as the version number is the GSsegments.00200=The current value, Version 2, Release 0.112 N 9 9 M Generated by Myer .This number uniquely identifies the interchangedata to the sender. It is assigned by the sender.Together with sender ID, it uniquely identifies theinterchange data to the receiver. It is suggestedthat the sender, receiver and all third parties be ableto maintain an audit trail of interchanges using thisnumber.The number is sequentially assigned, by the sender,starting with one within each trading partner. Thetrading partner at the interchange level is defined bythe interchange receiver ID (ISA08). The controlnumber is incremented by one for each interchangeenvelope sent to the trading partner. When thecontrol numbers reaches 999999999 (maximumsize) the next interchange envelope will have thecontrol number of 000000001.113 ID 1 1 M Code set by the sender to request an interchangeacknowledgment.The retail industry is not using transmissionacknowledgments. The transmission is not thesame as the functional group acknowledgment.O=No acknowledgment requested.114 ID 1 1 M Code to indicate whether data enclosed by thisinterchange envelope is test or production.The test indicator is valuable for startup systemtests. The indicator applies to the entiretransmission.P=Production data.T=Test data.115 AN 1 1 M This is a field reserved for future expansion inseparating data element subgroups.>=The value identified for retail use.E-Commerce Purchase Order Page 21 of 53October 2008© Myer Pty Ltd

Segment ISAInterchange control header cont’dNOTESThe purpose of this segment is to start and identify and interchange of one or more functionalgroups and interchange related control segments.The interchange control number value in this header must match the value in the same dataelement in the corresponding interchange control trailer.The first occurrence of the (byte 4) defines the actual value of the data element separatorand is graphically displayed as an asterisk *** in other ANSIX12 data segment documentation(for example, the PO1 segment). The first occurrence of the , 1 byte after the data elementISA16, defines the actual value of the segment terminator and is graphically displayed as NL inother ANSI ASCX12 data segment documentation (for example, the BFR segment inANSIX12.22).The ISA segment is fixed length (min/max are equal for each element), however, data elementseparators are used between data elements to be consistent with the basic syntax of segmentstructure.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 firstoccurrence of the segment terminator in the ISA segment, for example, ISA*00...N/LWhichever character is used for the segment terminator must be used throughout thetransmissionElement 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 firstoccurrence 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, thatcontrol character cannot be used as data within the transmission. Some systems/networkprotocols 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 conventionfor identification of the receiver and the sender.ISA01 through ISA04 are only used if the trading partners are using the UCS communicationstandard. 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 containthe UCS communication ID, password and the telephone number for the receiver’s modem.SEGMENT EXAMPLEI S A *0 0 * * 0 0 * *Z Z * 9 3 1 3 1 6 4 0 0 0 0 0 9 * Z Z * 9 3 0 0 1 0 0 1 2 3 4 5 8*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 *>E-Commerce Purchase Order Page 22 of 53October 2008© Myer Pty Ltd

Segment GSFunctional group headerLevelReq DesGroupMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 FUNCTIONAL ID 479 ID 2 2 M Code identifying a group of application relatedtransaction sets.P O (850)=Purchase order.02 APPLICATIONSENDER’SCODE03 APPLICATIONSRECEIVER’SCODE04 DATAINTERCHANGEDATE05 DATAINTERCHANGETIME06 DATAINTERCHANGECONTROL142 ID 2 12 M EQ850=Myer.Code Identifying party sending transmission.A unique code to identify the sender. This is usuallythe same as the code used in ISA06. It could beused to define sub organisations, ie companies of acorporation, departments etc. The trading partnersmust agree on the codes.124 ID 2 12 M Supplier ID.Code identifying party receiving transmission.This is usually the same as the code used in ISA08.It could be used to define sub organisations, iecompanies or a corporation, departments etc. Thetrading partners must agree on the codes.29 DT 6 6 M Date GE segment generated (YYMMDD).Date sender generated a functional group oftransaction sets.The date the group was created in the sender’ssystem; submit date.30 TM 4 4 M (HHMM) expressed in 24 hour clock time when thesender generated.The time the group was created in the sender’ssystem; submit time.28 N 1 9 M Assigned number originated and maintained by thesender.The number assigned by the sender must beunique within each trading partner. The tradingpartner at the group level is defined by theapplication receiver code (GS03). The uniquenessmust be maintained until such time that a functionalacknowledgment is received for that group.E-Commerce Purchase Order Page 23 of 53October 2008© Myer Pty Ltd

Segment GSFunctional group header cont’d07 RESPONSIBLEAGENCY CODE455 ID 1 2 M Code used in conjunction with the version dataelement 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 theFunctional Identifier to specify an exact version ofand EDI standard. Format of the version is ...Position Content1-3 Major version number4-6 Release level of version7-12 Industry or trade assoc ID(optionally assigned by user)Version/release number is the Version and releaseof the transaction sets within the group. This is notthe same as the version number in the ISAsegment.002040VICS-ANSI X12 version 2, release 4, theVICS subset.NOTEThe purpose of this segment is to indicate the beginning of a functional group and to providecontrol information.SEGMENT EXAMPLEGS*PO*EQ850*930010012345*901016*1012*952*X*002040VICSE-Commerce Purchase Order Page 24 of 53October 2008© Myer Pty Ltd

Segment STTransaction set headerLevelReq DesHeaderMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 TRANSACTIONSET IDENTIFIERCODE02 TRANSACTIONSET CONTROLNUMBER143 ID 3 3 M Code uniquely identifying a transaction set.850X12.1 Purchase order.The transaction set identifier (ST01) is intended foruse by the translation routines of the interchangepartners to select the appropriate transaction setdefinition, for example, 810 selects the invoicetransaction set.329 AN 4 9 M Generated by Myer.Identifying control number assigned by theoriginator for a transaction set.The number is sequentially assigned, by thesender, starting with one within each functionalgroup. For each functional group the firsttransaction set control number will be 0001 andincremented by one for each additional transactionset within the group.NOTEThe purpose of this segment is to indicate the start of a transaction set and to assign a controlnumber.SEGMENT EXAMPLEST*850*0001E-Commerce Purchase Order Page 25 of 53October 2008© Myer Pty Ltd

Segment SETransaction set trailerLevelReq DesSummaryMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 NUMBER OFINCLUDEDSEGMENTS02 TRANSACTIONSET CONTROLNUMBER96 N 1 6 M Generated by Myer.Total number of segments included in a transactionset including ST and SE segments.329 AN 4 9 M Identifying control number assigned by theoriginator for a transaction set.This must be the same number as in the STsegment (ST02) for the transaction set.NOTESThe purpose of this segment is to indicate the end of the transaction set and provide the countof the transmitted segments (including the beginning (ST) and ending (SE) segments).SE is the last segment of each transaction set.SEGMENT EXAMPLESE*3*0001E-Commerce Purchase Order Page 26 of 53October 2008© Myer Pty Ltd

Segment GEGroup control trailerLevelReq DesGroupMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 NUMBER OFTRANSACTIONSETS02 GROUPCONTROLNUMBER97 N 1 6 M Generated by Myer.Total number of transaction sets included in thefunctional group or interchange (transmission)group terminated by the trailer containing this dataelement.The count of ST segments within the group.28 N 1 9 M Generated by Myer.Assigned numbers originated and maintained by thesender.Must be the same number as in the GS segment(GS06) for the group.NOTESThe purpose of this segment is to indicate the end of a functional group and to provide controlinformation.The use of identical data interchange control numbers in the associated functional group headerand trailer is designed to maximise functional group integrity. The control number is the sameas that used in the corresponding header.SEGMENT EXAMPLEGE*5*952E-Commerce Purchase Order Page 27 of 53October 2008© Myer Pty Ltd

Segment IEAInterchange control trailerLevelReq DesEnvelopeMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 NUMBER OFINCLUDEDGROUPS02 INTERCHANGECONTROLNUMBER116 N 1 5 M Generated by Myer.A count of the number of functional groups includedin a transmission.The count of GS segments within the transmission.112 N 9 9 M Generated by Myer.This number uniquely identifies the interchangedata to the sender. It is assigned by the sender.Together with the sender, receiver and all thirdparties be able to maintain an audit trail ofinterchange using this number.Must be the same number as in the ISA segment(ISA13) for the transmission.NOTESThe purpose of this segment is to define the end of an interchange of one or more functionalgroups and interchange related control segments.The interchange control number in this trailer must match the value in the same data element inthe corresponding interchange control header.The value of the data element separator represented by and the data segment terminatorrepresented by are set by the interchange control header ISA for this interchange.SEGMENT EXAMPLEIEA*1*000000789E-Commerce Purchase Order Page 28 of 53October 2008© Myer Pty Ltd

VICS 850 purchase orderFunctional Group ID = POThis standard provides the format and establishes the data contents of a purchase order transaction set. Thepurchase order transaction set provides for customary and established business and industry practicerelative to the placement of purchase orders for goods and services. This transaction set should not be usedto convey purchase order changes or purchase order acknowledgment informationHeaderSEG ID NAME REQDESMAXUSELOOPREPEATST TRANSACTION SET HEADER M 1 USEBEG BEGINNING SEGMENT FOR PURCHASE ORDER M 1 USENTE NOTE/SPECIAL INSTRUCTION F 100 NOT USEDCUR CURRENCY 0 1 NOT USEDREF REFERENCE NUMBERS 0 12 USEPER ADMINISTRATIVE COMMUNICATIONS CONTACT 0 3 NOT USEDFOB F.O.B. RELATED INSTRUCTIONS 0 1 NOT USEDSSS SPECIAL SERVICES 0 25 USECSH HEADER SALE CONDITION 0 1 NOT USEDITA ALLOWANCE, CHANGE OR SERVICE 0 10 NOT USEDITD TERMS OF SALE/DEFERRED TERMS OF SALE 0 5 NOT USEDDTM DATE/TIME REFERENCE 0 10 USESHH GENERAL SCHEDULE 0 5 USETD5 CARRIER DETAILS (ROUTING SEQUENCE/TRANSIT 0 12 NOT USEDTIME)N1 NAME 0 1 N1/200 USEN2 ADDITIONAL NAME INFORMATION 0 2 NOT USEDN3 ADDRESS INFORMATION 0 2 NOT USEDN4 GEOGRAPHIC LOCATION 0 1 NOT USEDDetailPO1 PURCHASE ORDER BASELINE ITEM DATA M 1 PO1/100000 USECTP PRICING INFORMATION O 25 USEPID PRODUCT/ITEM DESCRIPTION O 1000 NOT USEDMEA MEASUREMENTS O 40 NOT USEDPO4 ITEM PHYSICAL DETAILS O 1 NOT USEDSSS SPECIAL SERVICES O 25 NOT USEDITA ALLOWANCE, CHANGE OR SERVICE O 10 NOT USEDITD TERMS OF SALE/DEFERRED TERMS OF SALE O 5 NOT USEDSDQ DESTINATION QUANTITY O 500 USESLN SUBLINE ITEM DETAIL O 1 SLN/1000 NOT USEDSummaryCTT TRANSACTION TOTALS M 1 USESE TRANSACTION SET TRAILER M 1 USEE-Commerce Purchase Order Page 29 of 53October 2008© Myer Pty Ltd

Segment STTransaction set headerLevelReq DesHeaderMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 TRANSACTIONSET IDENTIFIERCODE02 TRANSACTIONSET CONTROLNUMBER143 ID 3 3 M Code uniquely identifying a transaction set.850X12.1 purchase order.The transaction set identifier (ST)1) is intended foruse by the translation routines of the interchangepartners to select the appropriate transaction setdefinition.329 AN 4 9 M Identifying control number assigned by theoriginator for a transaction set.The number is sequentially assigned, by thesender, starting with one within each functionalgroup. For each functional group the firsttransaction set control number will be 0001 andincremented by one for each additional transactionset within the group.Inserted by Myer computer system.NOTEThe purpose of this segment is to indicate the start of a transaction set and to assign a controlnumber.SEGMENT EXAMPLEST*850*001E-Commerce Purchase Order Page 30 of 53October 2008© Myer Pty Ltd

Segment BEGBeginning segment for purchase orderLevelReq DesHeaderMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 TRANSACTIONSET PURPOSECODE02 PURCHASEORDER TYPECODE03 PURCHASEORDERNUMBER05 PURCHASEORDER DATE353 ID 2 2 M Code identifying purpose of transaction set.00=Original.01=Cancelled.07=Duplicate.92 ID 2 2 M Code specifying the type of purchase order.RE=Reorder.SA=Stand alone.BK=Blanket order.RL=Release order.324 AN 1 22 M Identifying number for purchase order assigned bythe orderer/purchaser.Myer original PO number.323 DT 6 6 M Date assigned by the purchaser to purchase order.Myer original PO date.NOTEThe purpose of this segment is to indicate the beginning of the purchase order transaction setand transmit identifying numbers and dates.SEGMENT EXAMPLEBEG*00*RE*000000340115**920302E-Commerce Purchase Order Page 31 of 53October 2008© Myer Pty Ltd

Segment REFReference numbersLevelReq DesHeaderOptionalMax Use 12Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 REFERENCENUMBERQUALIFIER02 REFERENCENUMBER128 ID 2 2 M Code qualifying the reference number.DP=Department number.127 AN 1 30 M Reference number or identification number asdefined for a particular Transaction set, or asspecified by the reference number qualifier.This is the Myer internal class group number whichis always a four digit code.NOTESThe purpose of this segment is to specify identifying numbers.There must be one occurrence of this segment to specify the retailer’s department, if the retailerhas departments. Additional segments may be used to specify other reference numbers.E-Commerce Purchase Order Page 32 of 53October 2008© Myer Pty Ltd

Segment SSSSpecial servicesLevelReq DesHeaderOptionalMax Use 25Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 ALLOWANCEOR CHARGEINDICATOR02 ASSOCIATIONQUALIFIERCODE03 SPECIALSERVICESCODE248 ID 1 1 M Code which indicates an allowance or charge forthe service specified.N=No allowance or charge.559 ID 2 2 M Code identifying the association assigning the codevalues.V1=Voluntary Inter-industry CommunicationStandards (VICS)This signifies the code list is maintained by theVICS EDI Committee. The only place these codesare printed is in this publication.560 ID 2 10 M Code identifying the special service.There are four services identified by VICS: ticketing,order handling, inscription and monogramming.The first two characters identify the service.Ticketing and order handling use additionalcharacters for further define the service.Service type (positions 1 & 2).TC=Ticketing serviceOH=Order handlingOrder processing type (positions 3 & 4)99=Non standard ticketPR=Promotional orderE-Commerce Purchase Order Page 33 of 53October 2008© Myer Pty Ltd

Segment SSSSpecial services cont’dNOTESThe purpose of this segment is to specify special conditions or services associated with thepurchased product.This segment can be used to convey the necessary information for marking merchandise to thecustomised requirements of the retailer. It can be used to identify special types of purchaseorders so they may be processed differently in the vendor’s system, for example, new store,rust, etc. This segment can be used to specify inscription and monogram data.There are four distinct special services codified in SSS03: ticketing, order handling, inscription,and monogramming. Each type has a different multipart code structure.Used by Myer to specify ticketing requirements where applicable.If this segment is present for ticketing then SKU details will be provided in the PO1 segment.This is the two part code to describe the order handling ...♦ Part 1 Service type (positions 1 & 2) TC Ticketing serviceOH Order handling♦ Part 2 Order Processing type (positions 3 & 4) 99 Non standard ticketPR Promotional orderAll standard orders will be sent with TC99 in this segment.Orders for advertised merchandise will be sent with OHPR in this segmentSEGMENT EXAMPLESSSS*N*VI*TC99SSS*N*VI*OHPRE-Commerce Purchase Order Page 34 of 53October 2008© Myer Pty Ltd

Segment DTMDate/time referenceLevelReq DesHeaderOptionalMax Use 10Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 DATE/TIMEQUALIFIER374 ID 3 3 M Code specifying type of date or time, or both dateand time.037= Ship Not Before.If the retailer allows shipment before therequested ship date then this is the earliestdate shipping can occur.001= Cancel After.If the order has not been shipped by this datethe order is considered cancelled.015= Advertised dateIf this qualifier is present in the purchaseorder, it will need to trigger printing of theletters AD in the specified location on eachSCM label02 DATE 373 DT 6 6 C Date (YYMMDD).NOTESThe purpose of this segment is to specify pertinent dates and times.At least one of DTM02 or DTM03 must be present.This segment is used to specify order processing dates.SEGMENT EXAMPLESDTM*037*920313DTM*001*920415DTM*015*920430E-Commerce Purchase Order Page 35 of 53October 2008© Myer Pty Ltd

Segment SHHGeneral scheduleLevelReq DesHeaderOptionalMax Use 5Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 SCHEDULING /SHIPPINGCODE562 ID 2 2 M Code indicating general scheduling/shippingarrangements.SC=Ship complete.NOTESThe purpose of this segment is to specify general scheduling conditions.At least one of DTM02 or DTM03 must be present.This segment is used to specify order processing priority codes, only SHH01 is used.SEGMENT EXAMPLESHH*SCE-Commerce Purchase Order Page 36 of 53October 2008© Myer Pty Ltd

Segment N1NameLevelReq DesHeaderOptionalMax Use 01Loop N1 Repeat: 200FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 ENTITYIDENTIFIERCODE03 IDENTIFICATIONCODEQUALIFIER04 IDENTIFICATIONCODE98 ID 2 2 M Code identifying an organisational entity or aphysical location.BS=Bill and ship to delivery location specifiedbelow.66 ID 1 2 C 92=Assigned by buyer.67 ID 2 17 C Code identifying a distribution centre.If this segment is present in a document then allproducts ordered must be delivered to thedistribution centre identified by the 3 digit code.NOTESThe purpose of this segment is to identify a party by type of organisation, name and code.The N1 segment overrides the SDQ segment.If there is no N1 segment on a spreadsheet order (direct to store) pick up the SDQ segment todetermine the delivery destination.SEGMENT EXAMPLEN1*BS**92*265E-Commerce Purchase Order Page 37 of 53October 2008© Myer Pty Ltd

Segment PO1Purchase order baseline item dataLevelReq DesDetailMandatoryMax Use 01Loop PO1 Repeat: 100000FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 ASSIGNEDIDENTIFICATION350 AN 1 6 O Alphanumeric characters assigned for differentiationwithin a transaction set, however, we use item todifferentiate various lines, ie EANs.02 QUANTITY 330 R 1 9 M Quantity ordered.ORDERED03 UNIT OFMEASUREMENTCODE355 ID 2 2 M Code identifying the basic unit of measurement.Myer uses EA only.04 UNIT PRICE 212 R 1 14 C Price per unit of product, service, commodity etc.The price will be sent with a decimal point onlywhen needed. For example, $15.95 would be sentas ‘15.95’, and $29.00 would be sent as ‘29’.05 BASIS OF UNITPRICE CODE639 ID 2 2 O Code identifying the type of unit price for an item.TE=Contract price per each.06 PRODUCT /SERVICE IDQUALIFIER07 PRODUCT /SERVICE ID ->08 PRODUCT /SERVICE IDQUALIFIER09 PRODUCT /SERVICE ID235 ID 2 2 O Code identifying the type/source of the descriptivenumber used in product/service ID (234).EN=Australian Product Number (2-5-5-1).234 AN 1 30 C 13 Digit Global Trade Identification Number.Identifying number for a product or service.235 ID 2 2 O Code identifying the type/source of the descriptivenumber used in product/service ID (234).SK=Stock keeping unit (SKU) which refers to theMyer keycode.234 AN 1 30 C Identifying number for a product or service Myerkeycode.NOTESThe purpose of this segment is to specify basic and most frequently used purchase order lineitem data.SEGMENT EXAMPLEThe ‘SK’ qualifier and following product ID will only be sent if the ‘SSS’ segment is present inthe document specifically for ticketing information.PO1**50*EA*1.75*TE*EN*9312345543210*SK*67890123E-Commerce Purchase Order Page 38 of 53October 2008© Myer Pty Ltd

Segment CTPPricing informationLevelReq DesDetailOptionalMax Use 25Loop PO1 Repeat 100000FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 CLASS OFTRADE CODE02 PRICEIDENTIFIERCODE687 ID 2 2 O Always set toRS = Resale236 ID 3 3 O Always set toRES = Retail price03 UNIT PRICE 212 R 1 14 O Price per unit of product, service, commodity, etc.Expressed in dollars. The decimal point is requiredif the price is not in whole dollars.The price is sent with a decimal point only whenneeded, for example $15.95 would be sent as“15.95” and $29.00 would be sent as “29”.04 to 07 Not used.NOTESThe purpose of the segment is to specify pricing information.SEGMENT EXAMPLECTP*RS*RES*42E-Commerce Purchase Order Page 39 of 53October 2008© Myer Pty Ltd

Segment SDQDestination quantityLevelReq DesDetailOptionalMax Use 500LoopPO1FLD#ELEMENT NAME01 UNIT OFMEASUREMENTCODE02 IDENTIFICATIONCODEQUALIFIER03 IDENTIFICATIONCODEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS355 ID 2 2 M Code Identifying the basic unit of measurement.Myer use ‘EA’ only65 ID 1 2 O Code designating the system/method of codestructure used for Identification Code (67)67 ID 2 17 M A 3-digit Code identifying a Myer store is provided04 QUANTITY 380 R 1 10 M Numeric value of quantity05 IDENTIFICATION 67 ID 2 17 O Code identifying a storeCODE06 QUANTITY 380 R 1 10 C Numeric value of quantity07 IDENTIFICATION 67 ID 2 17 O Code identifying a storeCODE08 QUANTITY 380 R 1 10 C Numeric value of quantity09 IDENTIFICATION 67 ID 2 17 O Code identifying a storeCODE10 QUANTITY 380 R 1 10 C Numeric value of quantity11 IDENTIFICATION 67 ID 2 17 O Code identifying a storeCODE12 QUANTITY 380 R 1 10 C Numeric value of quantity13 IDENTIFICATION 67 ID 2 17 O Code identifying a storeCODE14 QUANTITY 380 R 1 10 C Numeric value of quantity15 IDENTIFICATION 67 ID 2 17 O Code identifying a storeCODE16 QUANTITY 380 R 1 10 C Numeric value of quantity17 IDENTIFICATION 67 ID 2 17 O Code identifying a storeCODE18 QUANTITY 380 R 1 10 C Numeric value of quantity19 IDENTIFICATION 67 ID 2 17 O Code identifying a storeCODE20 QUANTITY 380 R 1 10 C Numeric value of quantity21 IDENTIFICATION 67 ID 2 17 O Code identifying a storeCODE22 QUANTITY 380 R 1 10 C Numeric value of quantityE-Commerce Purchase Order Page 40 of 53October 2008© Myer Pty Ltd

Segment SDQDestination quantity cont’dNOTESThis segment is used to distribute the line item quantity to various locations. In the case ofMyer we use this when delivery locations are individual stores rather than D.C.B. SDQ02serves the same purpose as N103, and all occurrences of data element number 67, in thissegment, function as N104. The N1, in the basic order specifies only one location. The sum ofall quantities in all SDQs, for a line item, must equal the quantity in the line item, (PO1).SEGMENT EXAMPLESSDQ*EA*92*001*12*004*10I.E. Deliver 12 items to store 001 and 10 items to store 004E-Commerce Purchase Order Page 41 of 53October 2008© Myer Pty Ltd

Segment CTTTransaction totalsLevelReq DesSummaryMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 NUMBER OFLINE ITEMS354 NO 1 6 M Total number of line items in the transaction set.The number of PO1 segments present in thetransaction.NOTESThis segment is intended to provide hash totals to validate transaction completeness andcorrectness.SEGMENT EXAMPLECCT*2ie 2 PO1 segmentsE-Commerce Purchase Order Page 42 of 53October 2008© Myer Pty Ltd

Segment SETransaction totalsLevelReq DesSummaryMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 NUMBER OFINCLUDEDSEGMENTS02 TRANSACTIONSET CONTROLNUMBER96 NO 1 6 M Total number of segments included in a transactionset including ST and SE segments.329 AN 4 9 M Identifying control number assigned by theoriginator for a transaction set.This must be the same number as in the STsegment (ST02) for the transaction set.NOTESThe purpose of this segment is to indicate the end of the transaction set and provide the countof the transmitted segments (including the beginning (ST) and ending (SE) segments).SE is the last segment of each transaction set.SEGMENT EXAMPLESE*16*0001E-Commerce Purchase Order Page 43 of 53October 2008© Myer Pty Ltd

VICS 997 functional acknowledgmentFunctional group ID = FAThis standard provides the format and establishes the date contents of a functional transaction set. Thepurpose of this standard is to define the control structures for a set of acknowledgments to indicate theresults of the syntactical analysis of the electronically encoded documents. The encoded documents are thetransaction sets, which are grouped in functional groups, used in defining transactions for business datainterchange. This standard does not cover the semantic meaning of the information encoded in thetransaction sets.SEG ID NAME REQDESMAXUSELOOPREPEATGS FUNCTIONAL GROUP HEADER M 1 USEST TRANSACTION SET HEADER M 1 USEAK1 FUNCTIONAL GROUP RESPONSE HEADER M 1 USEAK2 TRANSACTION SET RESPONSE HEADER O 1 AK2/999999 NOT USEDAK3 DATA SEGMENT NOTE O 1 AK3/999999 NOT USEDAK4 DATA SEGMENT NOTE O 99 NOT USEDAK5 TRANSACTION SET RESPONSE TRAILER M 1 NOT USEDAK9 FUNCTIONAL GROUP RESPONSE TRAILER M 1 USESE TRANSACTION SET TRAILER M 1 USEE-Commerce Purchase Order Page 44 of 53October 2008© Myer Pty Ltd

Segment GSFunctional group headerLevelReq DesGroupMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 FUNCTIONAL ID 479 ID 2 2 M Code identifying a group of application relatedtransaction sets.FA (997)=Functional Acknowledgment.02 APPLICATIONSENDER’SCODE03 APPLICATIONSRECEIVER’SCODE04 DATAINTERCHANGEDATE05 DATAINTERCHANGETIME06 DATAINTERCHANGECONTROL142 ID 2 12 M Supplier ID.Code Identifying party sending transmission.A unique code to identify the sender. This is usuallythe same as the code used in ISA06. It could beused to define sub organisations, ie companies of acorporation, departments etc. The trading partnersmust agree on the codes.124 ID 2 12 M EQ850=Myer.Code identifying party receiving transmission.This is usually the same as the code used in ISA08.It could be used to define sub organisations, iecompanies or a corporation, departments etc. Thetrading partners must agree on the codes.29 DT 6 6 M Date GE segment generated (YYMMDD).Date sender generated a functional group oftransaction sets.The date the group was created in the sender’ssystem; submit date.30 TM 4 4 M (HHMM) expressed in 24 hour clock time when thesender generated.The time the group was created in the sender’ssystem; submit time.28 N 1 9 M Assigned number originated and maintained by thesender.The number assigned by the sender must beunique within each trading partner. The tradingpartner at the group level is defined by theapplication receiver code (GS03). The uniquenessmust be maintained until such time that a functionalacknowledgment is received for that group.E-Commerce Purchase Order Page 45 of 53October 2008© Myer Pty Ltd

Segment GSFunctional group header cont’d07 RESPONSIBLEAGENCY CODE455 ID 1 2 M Code used in conjunction with the version dataelement 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 theFunctional Identifier to specify an exact version ofand EDI standard. Format of the version is ...Position Content1-3 Major version number4-6 Release level of version7-12 Industry or trade assoc ID(optionally assigned by user)Version/release number is the Version and releaseof the transaction sets within the group. This is notthe same as the version number in the ISAsegment.002040VICS-ANSI X12 version 2, release 4, theVICS subset.NOTEThe purpose of this segment is to indicate the beginning of a functional group and to providecontrol information.SEGMENT EXAMPLEGS*FA*930010012345*EQ850*901016*1012*952*X*002040VICSE-Commerce Purchase Order Page 46 of 53October 2008© Myer Pty Ltd

Segment STTransaction set headerLevelReq DesHeaderMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 TRANSACTIONSET IDENTIFIERCODE02 TRANSACTIONSET CONTROLNUMBER143 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 theoriginator for a transaction set.The number is sequentially assigned, by thesender, starting with one within each functionalgroup. For each functional group the firsttransaction set control number will be 0001 andincremented by one for each additional transactionset within the group.NOTESThe purpose of this segment is to indicate the start of a transaction set and to assign a controlnumber.The transaction set identifier (ST01 is intended for use by the translation routine of theinterchange partners to select the appropriate transaction set definition, for example, 810 selectsthe invoice transaction set.E-Commerce Purchase Order Page 47 of 53October 2008© Myer Pty Ltd

Segment AK1Functional group responseLevelReq DesHeaderMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 FUNCTIONALIDENTIFIERCODE02 GROUPCONTROLNUMBER479 ID 2 2 M Code identifying a group of application relatedtransaction sets.This is the functional group ID of the group that isbeing acknowledged, for example, if a purchaseorder group is being acknowledged the value wouldbe PO; it is the value sent in GS01 for the originaltransmission.28 N 1 9 M Assigned number originated and maintained by thesender.This is the control number assigned to the groupbeing acknowledged, for example, this is the controlnumber assigned by the sender of the originaltransmission. Its value is the value sent in GS06 forthe original transmission.The data interchange control number found in theGS segment in the functional group beingacknowledged.NOTESThe purpose of this segment is to start acknowledgment of a functional group.E-Commerce Purchase Order Page 48 of 53October 2008© Myer Pty Ltd

Segment AK9Functional group responseLevelReq DesHeaderMandatoryMax Use 01Loop_____________________FLD#ELEMENTNAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 FUNCTIONALGROUPACKNOWLEDGECODE02 NUMBER OFTRANSACTIONSETSINCLUDED03 NUMBER OFRECEIVEDTRANSACTIONSETS04 NUMBER OFACCEPTEDTRANSACTIONSETS05 FUNCTIONALGROUPSYNTAX ERRORCODE06 FUNCTIONALGROUPSYNTAX ERRORCODE07 FUNCTIONALGROUPSYNTAX ERRORCODE715 ID 1 1 M Code indicating accept or reject condition based onthe syntax editing of the functional group.A=Accepted.E=Accepted, but errors were noted.P=Partially accepted, at least one transaction setwas rejected.R=Rejected.97 N 1 6 M Total number of transaction sets included in thefunctional group or interchange (transmission)group terminated by the trailer containing this dataelement.123 N 1 6 M Number of transaction sets received.2 N 1 6 M Number of accepted transaction sets in a functionalgroup.716 ID 1 3 O Code indicating error found based on the syntaxediting 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 functionalgroup header and trailer do not agree.5=Number of included transaction sets does notmatch actual count.716 ID 1 3 O716 ID 1 3 OE-Commerce Purchase Order Page 49 of 53October 2008© Myer Pty Ltd

Segment AK9Functional group response cont’d08 FUNCTIONALGROUPSYNTAX ERRORCODE09 FUNCTIONALGROUPSYNTAX ERRORCODE716 ID 1 3 O716 ID 1 3 ONOTESThe purpose of this segment is to acknowledge acceptance or rejection of a functional groupand 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 thetransmitted group is rejected.The code values listed for AK905 will be the same for all occurrences of data element 716.E-Commerce Purchase Order Page 50 of 53October 2008© Myer Pty Ltd

Segment SETransaction set trailerLevelReq DesSummaryMandatoryMax Use 01Loop_____________________FLD#ELEMENT NAMEDICTNUMTYPEMINLENMAXLENREQCODES & COMMENTS01 NUMBER OFINCLUDEDSEGMENTS02 TRANSACTIONSET CONTROLNUMBER96 N 1 6 M Total number of segments included in a transactionset including ST and SE segments.329 AN 4 9 M Identifying control number assigned by theoriginator for a transaction set.This must be the same number as in the STSegment (ST02) for the transaction set.NOTESThe purpose of this segment is to indicate the end of the transaction set and provide the countof the transmitted segments (including the beginning (ST) and ending (SE) segments).E is the last segment of each transaction set.E-Commerce Purchase Order Page 51 of 53October 2008© Myer Pty Ltd

AppendixFunctional acknowledgmentFunctional acknowledgment selection tableMyer requires the VICS 997 functional acknowledgment (FA) document to be generated by EDI tradingpartners, each time a purchase order is retrieved from their mailbox.The purpose of the FA document is to provide confirmation that a supplier has retrieved a purchase anddoes not confirm whether the content of a purchase order has been received intact. For example, if thecontent is unclear, then it is the responsibility of the supplier to promptly contact the Supplier Liaison Team.Functional acknowledgmentsFunctional acknowledgments are an optional feature of EDI*PC and are used in many EDI implementations.The purpose of a functional acknowledgment is to ...♦♦Provide confirmation to the document sender that the receiver’s translation software(such as EDI*PC) has successfully received the EDI documentsProvide confirmation to the sender that the received documents comply to the EDIstandard being usedMyer EDI implementation will use functional acknowledgments. You should set your EDI*PC software toautomatically generate functional acknowledgments for documents received.To set up automatic functional acknowledgments on EDI*PC ...Sender’s EDIAddress1 Access EDI*PC main menu2 Select “Rules” icon and press “Enter” key3 Select “Functional Acknowledgment Selection”4 At functional acknowledgment selection menu, choose “F2” to add ...GE Information ServicesEDI*PC WorkstationSend IncludeFmt FA FA AK2/AK5Name Version Type Y/N Y/N--------------------------- ----------- ----------- ---------- ---------- ----------9313164000009 X 002040V FA Y NPgUp PgDn)F1Help F2Create F3Modify F4Undo F4Copy/Modify F9Del EscRtrnE-Commerce Purchase Order Page 52 of 53October 2008© Myer Pty Ltd

AppendixFunctional acknowledgment cont’dDocument acknowledgment status reportAs a sender of documents, you can use the EDI*PC Document Acknowledgment Status Report to check thefunctional acknowledgment status for all documents sent (ie. invoices). To access the documentacknowledgment status report ...1 Access EDI*PC “Desktop”2 Select “Reports” icon and press “Enter” key3 Make sure your printer is attached on line4 Select “Document Acknowledgment Status Report”. The report will print out on yourprinter.For more information on the Document Acknowledgment Status Report, see Section 4 of the EDI*PC 7.0manual.E-Commerce Purchase Order Page 53 of 53October 2008© Myer Pty Ltd