Message Implementation Guideline. SLSRPT Sales data report message

Transcription

1 Message Implementation Guideline EANCOM - SLSRPT:D:01B SLSRPT Sales data report message Implementation v1.1 APRIL

2 Introduction This document contains the Message Implementation Guidelines (MIG) for the Myer EANCOM SLSRPT:D01B Sales Data report 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 is expected that Trading Partners will return a valid Functional Acknowledgment for all Production and Test/Accreditation interchanges sent by Myer. Myer requires that a valid CONTRL message is sent within 48 hours of receiving an EDI Document. 2

3 Table of Contents Overview UNA UNB UNH BGM DTM RFF NAD LOC DTM RFF LIN PIA MOA QTY UNT UNZ Message Example

4 SLSRPT Sales data report message Overview: This specification provides the definition of the Sales data report message (SLSRPT) to be used in Electronic Data Interchange (EDI) between trading partners involved in administration, commerce and transport. A message to enable the conveyance of product activity related to the sale of products or services, such as the activity location, date, time or period, quantity, pricing, monetary amount, market sector, involved parties and other data enabling various sales analysis processes. Such activity information allows the recipient to perform statistical and quantitative analysis in support of production, planning, marketing, replenishment, and other processes. The Sales data report message may be used for both national and international applications. It is based on universal practice related to administration, commerce and transport, and is not dependent on the type of business or industry. Pos. Seg. Req. Group Notes and R No. ID Name Des. Max.Use Repeat Comments 0003 UNA UNA Service String Advice C 1 R 0005 UNB Interchange header C 1 M 0010 UNH Message header M 1 M 0020 BGM Beginning of message M 1 M 0030 DTM Date/time/period M Segment Group 1: RFF C 9 M 0060 RFF Reference M 1 M 0080 Segment Group 2: NAD M 5 M 0090 NAD Name and address M Segment Group 6: LOC-DTM-SG7-SG8 C M 0210 LOC Place/location identification M DTM Date/time/period C 5 R 0240 Segment Group 7: RFF C 8 M 0250 RFF Reference M Segment Group 8: LIN-PIA-MOA-SG10 C M 0280 LIN Line item M PIA Additional product id C MOA Monetary amount C 4 D 0420 Segment Group 10: QTY C 2 M 0430 QTY Quantity M 1 M 0710 UNT Message trailer M UNZ Interchange trailer C 1 4

5 Segment: UNA UNA Service String Advice Position: 0003 Group: Level: 0 Usage: Conditional (Required) Max Use: 1 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: The service string advice shall begin with the upper case characters UNA immediately followed by six characters in the order shown below. The same character shall not be used in more than one position of the UNA. This UNA segment specifies that the standard UNOA service characters will be used for all Myer MIG's. Example: UNA:+.? ' Data Element Summary Data Component Element Element Name Attributes UNA1 COMPONENT DATA ELEMENT SEPARATOR C an1 Used as a separator between component data elements contained within a composite data element (default value: ":") UNA2 DATA ELEMENT SEPARATOR C an1 Used to separate two simple or composite data elements (default value: "+") UNA3 DECIMAL NOTATION C an1 Used to indicate the character used for decimal notation (default value: ".") UNA4 RELEASE CHARACTER C an1 Used to restore any service character to its original specification (value: "?"). UNA5 RESERVED FOR FUTURE USE C an1 (default value: space ) UNA6 SEGMENT TERMINATOR C an1 Used to indicate the end of segment data (default value: " ' ") 5

6 Segment: UNB Interchange header Position: 0005 Group: Level: 0 Usage: Conditional (Required) Max Use: 1 Purpose: To start, identify and specify an interchange. Dependency Notes: Semantic Notes: Comments: Notes: Examples: UNB+UNOC: :ZZ :ZZ : ' (live) UNB+UNOC: :ZZ :ZZ : ' (test) Data Element Summary Data Component Element Element Name Attributes M S001 SYNTAX IDENTIFIER M Identification of the agency controlling the syntax and indication of syntax level, plus the syntax version number. M 0001 Syntax identifier M a4 Coded identification of the agency controlling a syntax and syntax level used in an interchange. UNOC UN/ECE level C As defined in ISO : Information processing - Part 1: Latin alphabet No. 1. M 0002 Syntax version number M n1 Version number of the syntax identified in the syntax identifier (0001). Refer to D.01B Data Element Dictionary for acceptable code values. M S002 INTERCHANGE SENDER M Identification of the sender of the interchange. M 0004 Sender identification M an..35 Name or coded representation of the sender of a data interchange Partner identification code qualifier C an..4 Qualifier referring to the source of codes for the identifiers of interchanging partners. ZZ Mutually Defined Mutually defined between trading partners. Myer Usage: The Myer EDI identifier will always be qualified with ZZ, as mutually agreed between all parties in the transaction. M S003 INTERCHANGE RECIPIENT M Identification of the recipient of the interchange. M 0010 Recipient identification M an..35 Name or coded representation of the recipient of a data interchange Partner identification code qualifier C an..4 Qualifier referring to the source of codes for the identifiers of interchanging partners. 14 GS1 International GS1 International, based in Belgium, is an organization of GS1 Member Organizations that jointly manages the EAN.UCC System with the Uniform Code Council. 6

7 ZZ Myer Usage: While the typical qualifier used by Myer is ZZ, at the request of a trading partner 14 will also be supported by Myer. Mutually Defined Mutually defined between trading partners. Myer Usage: The Recipients EDI identifier will typically be qualified with ZZ, as mutually agreed between the parties in the transaction. M S004 DATE/TIME OF PREPARATION M Date/time of preparation of the interchange. M 0017 Date of preparation M n6 Local date when an interchange or a functional group was prepared Format: YYMMDD = th January 2017 M 0019 Time of preparation M n4 Local time of day when an interchange or a functional group was prepared. M 0020 INTERCHANGE CONTROL REFERENCE M an..14 Unique reference assigned by the sender to an interchange. X S005 RECIPIENT'S REFERENCE, PASSWORD C X 0026 APPLICATION REFERENCE C an..14 X 0029 PROCESSING PRIORITY CODE C a1 Refer to D.01B Data Element Dictionary for acceptable code values ACKNOWLEDGEMENT REQUEST C n1 Code determined by the sender for acknowledgement of the interchange. Refer to D.01B Data Element Dictionary for acceptable code values. X 0032 COMMUNICATIONS AGREEMENT ID C an TEST INDICATOR C n1 Indication that the interchange is a test. Refer to D.01B Data Element Dictionary for acceptable code values. 7

8 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 Sales data report message is SLSRPT. Dependency Notes: Semantic Notes: Comments: Notes: Sales Data Report Heading Section This segment is used to head, identify and specify a message. DE's 0065, 0052, 0054, and 0051: Indicate that the message is a Sales Data Report based on the EDIFACT D.01B directory under the control of the United Nations. Example: UNH+1044+SLSRPT:D:01B:UN:EAN006' 1. The combination of the values carried in data elements 0062 and S009 shall be used to identify uniquely the message within its group (if used), or if not used, within its interchange, for the purpose of acknowledgement. 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 numbers of messages in the interchange, DE 0062 in the UNT will have the same value. Generated by the sender. M S009 MESSAGE IDENTIFIER M Identification of the type, version etc. of the message being interchanged. M 0065 Message type identifier M an..6 Code identifying a type of message and assigned by its controlling agency. SLSRPT Sales data report message A code to identify the sales data report message. GS1 Description: Message to enable the transmission of sales data related to products or services, such as corresponding location, period, product identification, pricing, monetary amount, quantity, market sector information, sales parties. It enables the recipient to process the information automatically and use it for production, planning, marketing, statistical purposes, etc. M 0052 Message type 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 type release number M an..3 Release number within the current message type version number (0052). 01B Release B 8

9 Message approved and issued in the second 2001 release of the UNTDID (United Nations Trade Data Interchange Directory). M 0051 Controlling agency M an..2 Code identifying 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) Association assigned code C an..6 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 an EANCOM version 006 of the Sales Data Report. EAN006 EAN version control number (EAN Code) 9

10 Segment: BGM Beginning of message Position: 0020 Group: Level: 0 Usage: Mandatory Max Use: 1 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A segment by which the sender must uniquely identify the sales data report by means of its type and number. This segment is used to indicate the type and function of a message and to transmit the identifying number. All references other than the document number DE 1004 are in the RFF segment (segment group 1). Example: BGM+73E::9:Detailed Sales Data ' 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. 73E Sales data report (EAN Code) A message enabling companies to exchange or report electronically, basic sales data related to products or services, including the corresponding location, time period, product identification, pricing and quantity information. It enables the recipient to process the information automatically and use it for production, marketing or statistical purposes. X 1131 Code list identification code C an..17 Refer to D.01B Data Element Dictionary for acceptable code values. R 3055 Code list responsible agency code C an..3 Code specifying the agency responsible for a code list. 9 GS1, 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 Document name C an..35 Name of a document. Required: Myer will use document name in this version to identify the Report type: - Detailed Sales Data, this will identify the transaction level sales report format - Summary Sales Data, this will be used to identify the summary level format if continued into new mapping. 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. Sales Data Report number assigned by the document sender. 10

11 Myer Note: The Report # will be the report date. R 1225 MESSAGE FUNCTION CODE C an..3 Code indicating the function of the message. The message function, coded is a critical data element in this segment. It applies to all data indicated in the message. The following definitions apply for the restricted codes: 9 = Original - An original transmission of a sales data report. 9 Original Initial transmission related to a given transaction. Required: All Myer Sales reports will be original documents. 11

12 Segment: DTM Date/time/period Position: 0030 Group: Level: 1 Usage: Mandatory Max Use: 5 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A segment specifying general dates and, when relevant, times related to the whole message. The sales report preparation date and the sales period covered by the report must be specified using this segment. Required: Identification of the 'Document/message date/time' (code value 137) is mandatory in all Myer EANCOM messages. Example: DTM+137: :102' The sales data report message is dated the 15th February DTM+356: :718' The sales data report covers the period from 15th February 2017 to 20th February Data Element Summary Data Component Element Element Name Attributes M C507 DATE/TIME/PERIOD M Date and/or time, or period relevant to the specified date/time/period type. Myer: Code 137 is required for all reports, together with either code 90 or code 356. M 2005 Date or time or period function code qualifier M an..3 Code qualifying the function of a date, time or period. 90 Report start date The date on which a report is to begin. Myer Usage: Used to indicate the report is for a single 24 hour period, the report will start and finish on the same date. 137 Document/message date/time (2006) Date/time when a document/message is issued. This may include authentication. Required: Message date, if report if for a single day this will also be the same as the report date. 356 Sales date, and or time, and or period The date, and or time, and or period on which a sale took place. Dependent: Will identify the period, the start and finish date of the report. Myer Usage: For existing report structure the Start and End dates will be a weekly window. For new Detailed reports the structure of the Start and End dates will be same day. (alternatively, for the Detailed report a single date can be provided using code 90) 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. 12

13 102 CCYYMMDD Calendar date: C = Century ; Y = Year ; M = Month ; D = Day. 718 CCYYMMDD-CCYYMMDD Format of period to be given without hyphen. Note: Only used when DE 2005 =

14 Group: RFF Segment Group 1: Reference Position: 0050 Group: Level: 1 Usage: Conditional (Optional) Max Use: 9 Purpose: A group of segments for giving references and where necessary, their dates, relating to the whole message e.g. contract number. Notes: A group of segments for giving references and where necessary, their dates, relating to the whole message e.g. contract number. Segment Summary Pos. Seg. Req. Max. Group: No. ID Name Des. Use Repeat M 0060 RFF Reference M 1 14

15 Segment: RFF Reference Position: 0060 (Trigger Segment) Group: Segment Group 1 (Reference) Conditional (Optional) Level: 1 Usage: Mandatory Max Use: 1 Purpose: A segment identifying the reference by its number and where appropriate a line number within the document. Dependency Notes: Semantic Notes: Comments: Notes: This segment is used to specify references relating to the sales data report. References should normally be given at this point if they apply to all or a majority of the line items. Example: RFF+SD:4477' 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. SD Sales department number A number that identifies a sales department. Myer: In the case of Myer, at the header level, this is also referred to as 'Class Group' R 1154 Reference identifier C an..70 Identifies a reference. 15

16 Group: NAD Segment Group 2: Name and address Position: 0080 Group: Level: 1 Usage: Mandatory Max Use: 5 Purpose: A group of segments identifying the parties with associated information. Notes: A group of segments identifying the parties with associated information. Segment Summary Pos. Seg. Req. Max. Group: No. ID Name Des. Use Repeat M 0090 NAD Name and address M 1 16

17 Segment: NAD Name and address Position: 0090 (Trigger Segment) Group: Segment Group 2 (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 sales data report. Identification of the sender of the report and the recipient is mandatory for the sales data report message. It is recommended that where possible only the coded form of the party ID should be specified e.g. the sender and receiver of the report are known to each other, thus only the coded ID is required, but when a new address might have to be clearly specified, this should be done preferably in structured format. This segment is used to identify the trading parties involved in the Sales Data Reporting process. Identification of the sender and receiver of the report is mandatory. These parties may be different than those specified in UNB. Example: NAD+BY ::9' NAD+SU ::91' Data Element Summary Data Component M Element Element Name Attributes 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. 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. Myer Usage: Will be the Myer's SAP account number for the Supplier. 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. For the identification of parties, it is recommended to use GLN - Format n13. X 1131 Code list identification code C an..17 Refer to D.01B Data Element Dictionary for acceptable code values. R 3055 Code list responsible agency code C an..3 Code specifying the agency responsible for a code list. 9 GS1, 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. 91 Assigned by supplier or supplier's agent 17

18 Codes assigned by a seller or seller's agent. GS1 Description: Code assigned by the supplier or supplier's agent. 18

19 Group: LOC Segment Group 6: Place/location identification Position: 0200 Group: Level: 1 Usage: Conditional (Optional) Max Use: Purpose: A group of segments providing activity, e.g. sales, data by line item within a specific location. Notes: Myer use: A group of segments providing details of the location for which sales are being reported and the period or sub-period during which the sales took place. There must be at least one occurrence of Segment group 6 within a sales data report. Sales Data Report Detail Section. Segment Summary Pos. Seg. Req. Max. Group: M No. ID Name Des. Use Repeat 0210 LOC Place/location identification M DTM Date/time/period C Segment Group 7: Reference C Segment Group 8: Line item C

20 Segment: LOC Place/location identification Position: 0210 (Trigger Segment) Group: Segment Group 6 (Place/location identification) Conditional (Optional) Level: 1 Usage: Mandatory Max Use: 1 Purpose: A segment to identify the activity, e.g. sales, the quantity of the activity, and other data related to the specific activity such as buying party, selling price, date sold, etc. Dependency Notes: Semantic Notes: Comments: Notes: This segment is used to identify the location where the sales took place. The LOC segment is the trigger segment for the Sales Data Report detail section. Example: LOC ::92' Data Element Summary Data Component M Element Element Name Attributes 3227 LOCATION FUNCTION CODE QUALIFIER M an..3 Code identifying the function of a location. 162 Place or location of sale Place or location at which the sale takes place. R C517 LOCATION IDENTIFICATION C Identification of a location by code or name. R 3225 Location name code C an..25 Code specifying the name of the location. Myer Usage: 3-digit Myer Store Number for Transaction set location. For identification of locations it is recommended to use GLN - Format n13. X 1131 Code list identification code C an..17 Refer to D.01B Data Element Dictionary for acceptable code values. D 3055 Code list responsible agency code C an..3 Code specifying the agency responsible for a code list. DE 3055 must be used if DE 3225 is used and does not contain an UN/LOCODE. 92 Assigned by buyer or buyer's agent Codes assigned by a buyer or buyer's agent. Used to identify that the value carried in DE 3225 is the location assigned by Myer to the location within the store that the sale took place. 20

21 Segment: DTM Date/time/period Position: 0220 Group: Segment Group 6 (Place/location identification) Conditional (Optional) Level: 2 Usage: Conditional (Optional) Max Use: 5 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A segment identifying the sub-period during which the sales being reported occurred if different than the period specified in the heading section e.g. within a biweekly sales data report as specified in the heading section, sales are reported in sub-periods of one week. Example: DTM+356: :102' 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. 356 Sales date, and or time, and or period The date, and or time, and or period on which a sale took place. 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. 203 CCYYMMDDHHMM Calendar date including time with minutes: C=Century; Y=Year; M=Month; D=Day; H=Hour; M=Minutes. 21

22 Group: RFF Segment Group 7: Reference Position: 0240 Group: Segment Group 6 (Place/location identification) Conditional (Optional) Level: 2 Usage: Conditional (Required) Max Use: 8 Purpose: A group of segments giving references at an intermediate level relating to several lines items, e.g. an invoice, shipment, notification, etc. Segment Summary Pos. Seg. Req. Max. Group: No. ID Name Des. Use Repeat M 0250 RFF Reference M 1 22

23 Segment: RFF Reference Position: 0250 (Trigger Segment) Group: Segment Group 7 (Reference) Conditional (Required) Level: 2 Usage: Mandatory Max Use: 1 Purpose: To specify a reference. Dependency Notes: Semantic Notes: Comments: 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. ACD Additional reference number Reference number provided in addition to another given reference. Myer Usage: Will be used to provide the Team Member Identifier of the person who entered the sales transaction. ACE Related document number Reference number identifying a related document. Myer Usage: Where appropriate, will contain the Team member name related to the Team member ID provide with RFF+ACD. AGT Service group identification number Identification used for a group of services. Myer Usage: Where appropriate, this will be populated with the POS register ID. AIJ Customer's individual transaction reference number Customer's reference number allocated by the customer to one specific transaction. Myer Usage: This will be the Myer POS transaction number. XFL XFM XSC Fulfilment Location (local use) Myer Usage: Will be the Fulfilment Location to be paired with the Fulfilment method. Will be Blank for BNM, for all others it will be either, Myer Store Number, Warehouse Number or Supplier Node number. Fulfilment Method (local use) Myer Usage: Will be used to carry the Fulfilment method identifier, will be one of the following values: - BNM Bricks & Mortar - DEL For delivery direct to customer - CNC Click and Collect Sales Channel (local use) Myer Usage: Will be used to carry the Sales channel 23

24 XVV identifier, will be one of the following values: - BNM Bricks & Mortar - ONL Online - MOB Mobility Tablet - COM Customer Service Centre Loyalty scheme identifier (local use) Myer Usage: Will be used to pass the Loyalty card number. Conditional Rule: Where applicable - The loyalty card number or other identifier (e.g. customer address) associated with this transaction Reference identifier C an..70 Identifies a reference. 24

25 Group: LIN Segment Group 8: Line item Position: 0270 Group: Segment Group 6 (Place/location identification) Conditional (Optional) Level: 2 Usage: Conditional (Optional) Max Use: Purpose: Notes: A group of segments to identify the product or service and the activity, e.g. sales, which applies to the product or service. In addition, other data related to the activity may be specified. A group of segments providing details per location and period of the individual products sold in terms of product family or group, promotional flags, total sale monetary amount and sale price. Segment Summary Pos. Seg. Req. Max. Group: M No. ID Name Des. Use Repeat 0280 LIN Line item M PIA Additional product id C MOA Monetary amount C Segment Group 10: Quantity C 2 25

26 Segment: LIN Line item Position: 0280 (Trigger Segment) Group: Segment Group 8 (Line item) Conditional (Optional) Level: 2 Usage: Mandatory Max Use: 1 Purpose: A segment identifying the line item by the line number and configuration level. In addition, it may identify the product or service to which the activity, e.g. sales is applicable. Dependency Notes: Semantic Notes: Comments: Notes: Example: LIN :SRV' If Global Trade Item Numbers are available, it is mandatory to use GTIN within the LIN segment. Data Element Summary Data Component R Element Element Name Attributes 1082 LINE ITEM IDENTIFIER C an..6 To identify a line item. Application generated number of the item lines within the Sales Data Report. X 1229 ACTION REQUEST/NOTIFICATION DESCRIPTION C an..3 CODE Refer to D.01B Data Element Dictionary for acceptable code values. D C212 ITEM NUMBER IDENTIFICATION C Goods identification for a specified source. This composite is only used for the identification of GTIN's. If another coding structure is required, e.g. HIBC, then this composite will not be used and the code will be detailed in the PIA segment. R 7140 Item identifier C an..35 To identify an item. Format n..14 GTIN This is the number of the article whose sales are being reported. 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'. 26

27 Segment: PIA Additional product id Position: 0290 Group: Segment Group 8 (Line item) Conditional (Optional) Level: 3 Usage: Conditional (Optional) Max Use: 5 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A segment providing either additional identification to the product specified in the LIN segment or providing any substitute product identification. In the Sales Data Report the PIA segment can be used when a product specified in LIN has to be associated with a group or family of products whose identity could be specified in PIA. Example: PIA :IN' PIA :SA' Data Element Summary Data Component Element Element Name Attributes M 4347 PRODUCT IDENTIFIER CODE QUALIFIER M an..3 Code qualifying the product identifier. Product Id function has the following restricted coded function: 5 - Product Identification - To provide the primary product identification code when no GTIN has been provided in the LIN segment. 5 Product identification The item number is for product identification. M C212 ITEM NUMBER IDENTIFICATION M Goods identification for a specified source. R 7140 Item identifier C an..35 To identify an item. R 7143 Item type identification code C an..3 Coded identification of an item type. IN Buyer's item number The item number has been allocated by the buyer. Myer Usage: The Myer internal item number (Key Code) for the scanned item. SA Supplier's article number Number assigned to an article by the supplier of that article. 27

28 Segment: MOA Monetary amount Position: 0360 Group: Segment Group 8 (Line item) Conditional (Optional) Level: 3 Usage: Conditional (Optional) Max Use: 4 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A segment specifying any monetary amounts relating to the product. For the sales data report the MOA segment can be used to express the total monetary amount of the product sold in one location for one period. This segment is used to indicate the value of the sales for the current line item for the period being reported. Example: MOA+203:178.65' Sales amounts is $ MOA+508:76.45' Value of returned product is $76.45 MOA+5:78.65' Markdown Sales MOA+43E:58.65' Return Markdown Data Element Summary Data Component M Element Element Name Attributes C516 MONETARY AMOUNT M Amount of goods or services stated as a monetary amount in a specified currency. M 5025 Monetary amount type code qualifier M an..3 Code qualifying the type of monetary amount. 5 Adjusted amount The amount specified is the adjusted amount. Myer Usage: Sold at discount, Markdowns 203 Line item amount Goods item total minus allowances plus charges for line item. See also Code 66. Myer usage: Will be the line item sales amount. 43E Customer returns value (EAN Code) Value of product returned by the customer to the place/party of sale. Myer Usage: Returns at markdown value 508 Value of returned product Myer Usage: The full price of the sales return, before discounts or markdowns. R 5004 Monetary amount C n..35 To specify a monetary amount. 28

29 Group: QTY Segment Group 10: Quantity Position: 0420 Group: Segment Group 8 (Line item) Conditional (Optional) Level: 3 Usage: Conditional (Dependent) Max Use: 2 Purpose: Notes: A group of segments to identify the activity, e.g. sales, the quantity of the activity, and other data related to the specific activity such as buying party, selling price, date sold, status for the quantity, etc. A group of segments providing split delivery sales parties and relevant quantities information. Myer Usage: Required for all LIN loops other than LIN+0 Segment Summary Pos. Seg. Req. Max. Group: No. ID Name Des. Use Repeat M 0430 QTY Quantity M 1 29

30 Segment: QTY Quantity Position: 0430 (Trigger Segment) Group: Segment Group 10 (Quantity) Conditional (Dependent) Level: 3 Usage: Mandatory Max Use: 1 Purpose: A segment identifying the quantity and activity, e.g. quantity sold. Dependency Notes: Semantic Notes: Comments: Notes: Example: QTY+153:48' QTY+210:3' 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. 153 Statistical sales quantity Quantity of goods sold in a specified period. Myer Usage: Quantity Sold 210 Returned by consumer quantity Quantity returned by a consumer. Myer Usage: Quantity of the product returned by customer to place of sale. M 6060 Quantity M an..35 Alphanumeric representation of a quantity. 30

31 Segment: UNT Message trailer Position: 0710 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. Sales Data Report Summary Section This segment is a mandatory UN/EDIFACT segment. It must always be the last segment in the message. Before the interchange Trailer. Example: UNT ' Data Element Summary Data Component M Element Element Name Attributes 0074 NUMBER OF SEGMENTS IN A 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 equal the one specified in the UNH segment. 31

32 Segment: UNZ Interchange trailer Position: 0720 Group: Level: 0 Usage: Conditional (Optional) Max Use: 1 Purpose: Dependency Notes: Semantic Notes: Comments: Notes: To end and check the completeness of an interchange. Example: UNZ+1+123' Data Element Summary Data Component M Element Element Name Attributes 0036 INTERCHANGE CONTROL COUNT M n..6 Count either of the number of messages or, if used, of the number of functional groups in an interchange. M 0020 INTERCHANGE CONTROL REFERENCE M an..14 Unique reference assigned by the sender to an interchange. 32

33 SLSRPT Sales data report message Example UNA:+.? ' UNB+UNOC: :ZZ :ZZ : ' UNH+2+SLSRPT:D:01B:UN:EAN006' BGM+73E::9:Detailed Sales Data ' DTM+137: :102' DTM+356: :718' RFF+SD:1499' NAD+BY ::9' NAD+SU ::91' LOC+162+1::92' DTM+137: :102' DTM+356: :203' RFF+AIJ:5555' RFF+AGT:227' RFF+ACD: ' RFF+ACE:John Smith' RFF+XSC:BNM' LIN :SRV' PIA :IN' MOA+203:49.50' MOA+5:49.50' MOA+43E:0.00' MOA+508:0.00' QTY+153:1' QTY+210:0' LOC+162+1::92' DTM+137: :102' DTM+356: :203' RFF+AIJ:5567' RFF+AGT: ' RFF+ACD:John Smith' RFF+XSC:BNM' LIN :SRV' PIA :IN' MOA+203:0.00' MOA+5:0.00' MOA+43E:0.00' MOA+508:0.00' QTY+153:1' QTY+210:0' LIN :SRV' PIA :IN' MOA+203:110.00' MOA+5:110.00' MOA+43E:0.00' MOA+508:0.00' 33

34 QTY+153:1' QTY+210:0' LOC+162+4::92' DTM+137: :102' DTM+356: :203' RFF+AIJ:1591' RFF+AGT:233' RFF+ACD: ' RFF+XVV: ' RFF+XSC:BNM' LIN :SRV' PIA :IN' MOA+203:24.50' MOA+5:24.50' MOA+43E:0.00' MOA+508:0.00' QTY+153:1' QTY+210:0' LOC+162+7::92' DTM+137: :102' DTM+356: :203' RFF+AIJ:3084' RFF+AGT:118' RFF+ACD:930711' RFF+XSC:BNM' LIN :SRV' PIA :IN' MOA+203:0.00' MOA+5:0.00' MOA+43E:29.00' MOA+508:29.00' QTY+153:0' QTY+210:1' UNT+80+2 UNZ