Message Implementation Guideline (MIG) The Good Guys. Message Envelope Implementation Guide. The Good Guys Suppliers. Audience: Version: 1.

Transcription

1 Message Implementation Guideline (MIG) The Good Guys Message Envelope Implementation Guide Audience: The Good Guys Suppliers Version: 1.0 Status: Issue Date: Written by: Final 29-Sep-2011 Sudhir Rajai Solution Architect evision Pty Ltd

2 CONTENTS DOCUMENT PROPERTIES... 3 Copyright... 3 Change History... 3 UN/EDIFACT SPECIFICATIONS... 4 Definition of UN/EDIFACT... 4 UN/EDIFACT Syntax... 4 Structure of an Interchange... 4 ENVELOPE SEGMENT DEFINITIONS... 7 CONTACT DETAILS evision - MessageXchange The Good Guys evision Pty Ltd Commercial In Confidence 2

3 DOCUMENT PROPERTIES Copyright This document is the property of: Evision Pty Ltd. Level 3, 488 Bourke Street, Melbourne Vic This Message Implementation Guide has been created for The Good Guys. Unauthorized access, copying, replication and usage for a purpose other than for which this is intended is prohibited by Copyright Laws. The holder is responsible for incorporating revisions into his copy of the document and keeping the contents up-to-date. Change History Version Date Updated by Nature of Amendment Sep-2011 Sudhir Rajai Initial Version evision Pty Ltd Commercial In Confidence 3

4 UN/EDIFACT SPECIFICATIONS Definition of UN/EDIFACT United Nations rules for Electronic Data Interchange for Administration, Commerce and Transport. They comprise a set of internationally agreed standards, directories and guidelines for the electronic interchange of structured data, and in particular that related to trade in goods and services, between independent computerized information systems - EDI systems. UN/EDIFACT Syntax The UN / EDIFACT syntax rules set the standards for structuring data into segments, segments into messages, and messages into an interchange. Structure of an Interchange Below is a diagram of the control segments of UN/EDIFACT format. Segments starting with UN are called service segments. They constitute the envelope or the packing of the EDIFACT messages. User data segments contain the information itself, in a format specific to each message type. An Interchange may consist of the following segments: Segment ID Segment Name Usage UNA Service String Advice Optional UNB Interchange Header Mandatory UNG Functional Group Header Conditional UNH Message Header Mandatory User Data Segments UNT Message Trailer Mandatory UNE Functional Group Trailer Conditional UNZ Interchange Trailer Mandatory evision Pty Ltd Commercial In Confidence 4

5 STRUCTURE OF A MESSAGE Each data segment has a specific place within the sequence of segments in the message. They may occur in any of the following three sections of the message: Heading section - A segment occurring in this section relates to the entire message. Detail section - A segment occurring in this section relates to the detail information only. Summary section - Only segments containing totals or control information may occur in the summary section. The same segment type may occur in more than one of the message sections, e.g. in the header and in the detail section, and/or more than once in the same section. Some segments may be repeated a certain number of times at their specific location in the message. The status, Mandatory or Conditional, and the maximum number of repetitions of segment types are indicated in the message structure. Within a message, specific groups of functionally related segments may be repeated; these groups are referred to as "segment groups". The maximum number of repetitions of a particular segment group at a specific location is included in the message definition. A segment group may be nested within other segment groups, provided that the inner segment group terminates before any outer segment group terminates. SEGMENT STRUCTURE A segment consists of: A segment tag: identifies the segment type Data element separators Simple, composite, or component data elements A segment terminator Data elements can be defined as having a fixed or variable length. A composite data element contains two or more component data elements. A component data element is a simple data element used in a composite data element. A data element can be qualified by another data element, the value of which is expressed as a code that gives specific meaning to the data. The data value of a qualifier is a code taken from an agreed set of code values. evision Pty Ltd Commercial In Confidence 5

6 SEPARATORS In EANCOM four service characters (extracted from UNOA) have a special meaning and act as the default separators for EANCOM. ASCII HEX Apostrophe ' 27 Segment terminator Decimal. 2E Decimal Point Point Plus sign + 2B Segment tag and data element separator Colon : 3A Component data element separator Question mark? 3F Release character; immediately preceding one of the service characters; it stores their normal meaning. E.g. 10?+10=20 means 10+10=20. Question mark is represented by?? UN / EDIFACT DOCUMENTATION CONVENTIONS Format and Picture of Data Elements The following conventions apply in the present documentation: a n an a3 n3 an3 a..3 n..3 an..3 alphabetic characters numeric characters alpha-numeric characters 3alphabetic characters, fixed length 3 numeric characters, fixed length 3 alpha-numeric characters, fixed length up to 3 alphabetic characters up to 3 numeric characters up to 3 alpha-numeric characters The format and picture of the data elements that will be used by The Good Guys in the following EDI documents comply with the UN/EDIFACT Standards. USAGE INDICATORS There are five types of status used in the following pages, whether for simple, component or composite data elements. They are listed below and can be identified when relevant by the abbreviations. MANDATORY M Indicates that the entity is required and must be sent. RECOMMENDED R Indicates that the entity is advised or recommended. CONDITIONAL C Indicates that the entity must be sent in certain conditions, as defined by the relevant explanatory note. OPTIONAL O Indicates that the entity is optional and may be sent at the discretion of the user. NOT USED N Indicates that the entity is not used and should be omitted. evision Pty Ltd Commercial In Confidence 6

7 ENVELOPE SEGMENT DEFINITIONS Segment: UNA - Service String Advice Position: Usage: O Max. Use: 1 Purpose: To define default separators used in message. Example: UNA:+.? ' Position Segment Usage Representation 010 UNA1 COMPONENT DATA ELEMENT SEPARATOR M an..1 UNA2 DATA ELEMENT SEPARATOR M an..1 UNA3 DECIMAL MARK M an..1 UNA4 RELEASE INDICATOR M an..1 UNA5 RESERVED FOR FUTURE USE M an..1 UNA6 SEGMENT TERMINATOR M an..1 evision Pty Ltd Commercial In Confidence 7

8 Segment: UNB - Interchange header Position: Usage: M Max. Use: 1 Purpose: To start, identify and specify an interchange. Example: UNB+UNOA: :ZZ :ZZ : ' Position Segment Usage Representation 010 S001 SYNTAX IDENTIFIER M 0001 Syntax identifier UNOA - UN/ECE level A M a Syntax version number 3 - Version 3 M n1 020 S002 INTERCHANGE SENDER M 0004 Sender identification M an Partner identification code qualifier ZZ - Mutually defined C an S003 INTERCHANGE RECIPIENT M 0010 Recipient identification M an Partner identification code qualifier ZZ - Mutually defined C an S004 DATE/TIME OF PREPARATION M 0017 Date of preparation M n Time of preparation M n Interchange control reference M an..14 evision Pty Ltd Commercial In Confidence 8

9 Notes: EDI identification codes: The Good Guys Australia Test The Good Guys New Zealand Test The Good Guys Australia Production The Good Guys New Zealand Production The combination of the values carried in data elements S002, S003 and 0020 shall be used to identify uniquely the interchange, for the purpose of acknowledgement. evision Pty Ltd Commercial In Confidence 9

10 Segment: UNH - Message header Position: Usage: M Max. Use: 1 Purpose: To head, identify and specify a message. Example: UNH ORDERS:D:96A:UN:EAN008' Position Segment Usage Representation Message reference number M an S009 MESSAGE IDENTIFIER M Message type ORDERS - Purchase order message CONTRL - Syntax and service report message 0065 ORDRSP - Purchase order response message ORDCHG - Purchase order change request message M an..6 DESADV - Despatch advice message INVOIC - Invoice message PRICAT - Price/sales catalogue message 0052 Message version number D - Draft version/un/edifact Directory M an Message release number 96A - Release A M an Controlling agency UN - UN/CEFACT M an Association assigned code EAN008 C an..6 evision Pty Ltd Commercial In Confidence 10

11 Segment: UNT - Message trailer Position: Usage: M Max. Use: 1 Purpose: To end and check the completeness of a message. Example: UNT ' Position Segment Usage Representation Number of segments in the message M n Message reference number M an..14 evision Pty Ltd Commercial In Confidence 11

12 Segment: UNZ - Interchange trailer Position: Usage: M Max. Use: 1 Purpose: To end and check the completeness of an interchange. Example: UNZ ' Position Segment Usage Representation Interchange control count M n Interchange control reference M an..14 evision Pty Ltd Commercial In Confidence 12

13 CONTACT DETAILS evision - MessageXchange 3/488 Bourke Street Melbourne, VIC Australia, 3000 P: E: info@messagexchange.com Technical support P: E: support@messagexchange.com The Good Guys Toni Green B2B Project Leader The Good Guys Phone: tonigreen@thegoodguys.com.au evision Pty Ltd Commercial In Confidence 13