Transcription
EDIFACT StandardsOverview TutorialLearn About Key e-Commerce Trends andTechnologies at Your Own PaceA GXS Tutorial for the Active Business
Welcome!. 3How To Use This Tutorial. 3Tutorial Objectives. 3Part 1: Why use EDI Standards?. 4Part 2: What is EDIFACT?. 4Part 3: Message Definition. 6Part 4: Message Structure: Segment Tables. 6Part 5: Message Structure: Segment Groups. 8Part 6: Segments. 9Part 7: Segment Terminators and Delimiters.10Part 8: What is Mapping?.10Part 9: Data Elements: Simple and Composite. 11Part 10: Composite Data Elements: Qualifier and Value.13Part 11: Message Structure and Electronic Enveloping.14Part 12: Envelope Architecture.14Part 13: Electronic Enveloping.15Part 14: The Message Envelope.15Part 15: The Functional Group Envelope.17Part 16: The Interchange Envelope.17Part 17: The CONTRL Message.18EDIFACT Wrap-up.19EDIFACT Glossary.19EDIFACT Self-Test I: After Completion of Part 5.21EDIFACT Self-Test II: After Completion of Part 10. 22EDIFACT Self-Test III: After Completion of Part 17. 23EDIFACT Standards Overview Tutorial 2GXS Proprietary and Confidential Information
Welcome!This tutorial is an overview of the EDIFACT Standard format.The topics covered in this tutorial are: Objectives of this tutorial and how to use it EDIFACT 101—some basic information about EDIFACT Standards development Messages—structure, segments, types, loops, etc. Segments—structure, interpretations, conditions, etc. Data Elements—what they are and how to use them Message Structure and Enveloping—packaging it all Functional Acknowledgements—who needs them?Terms marked in red are defined in the EDIFACT Glossary.How To Use This TutorialThis tutorial provides information about the development of EDIFACT and basic EDIFACTconcepts. It should be used as a prerequisite to understanding what EDIFACT is, and how EDIFACT is developing to meet the needs of electronic commerce solutions.It is only the beginning. This tutorial will introduce terms and concepts that you will find necessary to form an awareness of EDIFACT.The best way to use this tutorial is to read through a module and its sub-topics, though notnecessarily at one sitting. Each module in this tutorial builds on information presented in earliermodules, but individual sub-topics can be used as reference outside of the linear progression ofthe course. You will find summaries at the end of each module and self tests at the end of thedocument so you can evaluate your understanding of the material.Please send all feedback to [email protected] ObjectivesAfter completing this tutorial, you should be able to discuss: What are EDIFACT and EDIFACT Standards How and why the EDIFACT Standard was developed What is the basic structure of the EDIFACT format How the EDIFACT documents are read What are Functional Acknowledgements and why are they used How the EDIFACT Standard may be used in providing electronic commerce solutionsEDIFACT Standards Overview Tutorial 3GXS Proprietary and Confidential Information
Part 1: Why use EDI Standards?EDI standards facilitate electronic data interchange (EDI) by providing: Rules of syntax Definition of the data organization Editing rules and conventions Published public documentationEDI standards: Allow an ‘open’ system Reduce implementation effort Provide ‘third-party interfaces’Part 2: What is EDIFACT?EDIFACT is an acronym for EDI For Administration, Commerce and Transport. It coordinatesinternational standardization by working through the UN/ECE (United Nations/EconomicCommission for Europe). It provides: an international EDI standard a set of syntax rules data elements, segments and codes messagesAs shown in the following diagram, EDIFACT is the product of the evolution in bringingthe Proprietary Standards of the US and Europe together to form a single internationalEDI standard.Proprietary (U.S.)TDCCANSI X.12EDIFACTGTDIProprietary (Europe)EDIFACT Standards Overview Tutorial 4GXS Proprietary and Confidential InformationIndustry Specificand National VersionsUN/EDIFACTInternationalStandards
In order to bring about the evolution of the EDIFACT standard, the UN has created UN/ECEto coordinate this effort. The organizational structure of the UN/ECE is made up of the following board members:United NationsAfrica EDIFACT BoardGeneral AssemblyAsia EDIFACT BoardRAPPORTEURSEconomic andSocial CouncilRegioanl EconomicCommissionUN/ECECommittee on TradeWP.4Australia/New ZealandEDIFACT BoardEastern EuropeEDIFACT BoardPan AmericanEDIFACT BoardWestern EuropeEDIFACT BoardGE.1Standards Approved HereStandards Developed HereThe organizational structure of the regional boards are all structured in a similar fashion. Here isthe organizational structure of the Pan American Board:United Nations ECE/WP.4Pan AmericanEDIFACT BoardRapporteur/Vice RapporteurChair/Vice ChairSteering CommitteeSecretariat (D.I.S.A.)Delegate Liason Task GroupManagement Work GroupBusiness ModelingAd-Hoc Work GroupTechnical AdvisoryWork Group (ETAG)EDIFACT Standards Overview Tutorial 5GXS Proprietary and Confidential Information
Part 3: Message DefinitionA message is a single business document. Each message is identified by a six character name.From the buyer-side these include: ORDERS—Purchase Orders CUSDEC—Customs Declaration IFTMIN—Instruction Message REMADV—Remittance Advice PAYORD—Payment OrderSeller-side messages include: IFTMAN—Arrival Notice CUSRES—Custom Response INVOIC—InvoicesMessages are made up of a collection of sequenced segments within defined areas. Some segments may be used in more than one area. The segments that can be used in each area are definedby the EDIFACT documentation. EDIFACT provides a hierarchical structure for messages.Messages begin with the Message Header (UNH) Segment and end with the Message Trailer(UNT) Segment. These two segments are the first, and innermost, level of the three levels of“electronic envelopes” within EDIFACT. Here is an example of an Extended Payment Order(PAYEXT) message that illustrates this structure:Part 4: Message Structure: Segment TablesThe message structure is defined in segment tables. These give the ‘rules’ of the message. Theyalso show which segments are used in a particular message and the order in which the segmentsmust appear.EDIFACT Standards Overview Tutorial 6GXS Proprietary and Confidential Information
Here is an example of a segment table for the Extended Payment Order (PAYEXT):Segment tables specify if a segment must appear in a message. This is done using the ‘Requirements Designator’ field. Each segment in the table is designated as either Mandatory (M) orConditional (C). Mandatory means that at least one occurrence of the segment must appear in themessage. Conditional means a segment may be used, if needed, but it is not required.Segment tables also specify how many times a particular segment may repeat. This is called the‘Repetition’ field. Here are the requirements designators and repetition as displayed in the tablefor the Extended Payment Order (PAYEXT) message:EDIFACT Standards Overview Tutorial 7GXS Proprietary and Confidential Information
Part 5: Message Structure: Segment GroupsWhen collections of segments repeat as a group, they are called segment groups. If you are familiar with ANSI X.12, these are the equivalents of loops.Here is an example of segment groups for the Extended Payment Order (PAYEXT):Segment groups may be ‘nested’. This means that a segment group is fully contained withinanother segment group.Here is an example of a Nested Segment Group:EDIFACT Standards Overview Tutorial 8GXS Proprietary and Confidential Information
Both Segment Group 7 segments (CUX, DTM) and Segment Group 8 segments (AJT, MOA,RFF) are within Segment Group 6 (Document Details). Take Self Test I to check your understanding at this point. Self Test I can be found at the endof this tutorial.Part 6: SegmentsA segment is a collection of logically-related data elements in a fixed, defined sequence. Segments contain: A three-character alphanumeric code that identifies the segment. This is called the segment tag. Variable length data elements. These can be either simple or composite.Segments must be separated by a data element separator (data element delimeter), which is normally and :, and terminated by a segment terminator, normally ‘.All segments are fully documented in the United Nations Trade Data Interchange Directory(UNTDID). These tables list the segment position, segment tag and segment name. Segmenttables also specify if a segment must appear in a message using the requirements designator M(Mandatory) or C (Conditional), and how many times a particular segment may repeat (repetition field).In EDIFACT, there are two kinds of segments: Service Segments Generic SegmentsService Segments are: Envelopes (UNB-UNZ, UNG-UNE, UNH-UNT) Delimiter String Advice (UNA) Section Separator (UNS)Generic Segments are: DOC to identify and specify documents MOA for monetary amounts DTM for dates and times NAD for name and address dataHere is a sample segment:EDIFACT Standards Overview Tutorial 9GXS Proprietary and Confidential Information
Part 7: Segment Terminators and DelimitersThe end of each segment is determined by the Data Segment Terminator. In EDIFACT the standard data segment terminator is ‘.Optional or conditional data elements that are not used must be accounted for by their positionwithin the segment. Here is an example:However, optional or conditional data elements without data that appear at the end of a datasegment do not need additional data element separators to correctly position the data. Here is anexample:Part 8: What is Mapping?There are almost as many business applications as there are businesses. In the early days, eachbusiness had its own applications for tracking merchandise, ordering, invoicing, accounts payable, receivable, and other business needs. We soon realized that:1. The computer applications of one business couldn’t talk to those of another. This meantre-entering all data that was received.2. The applications in one department of a business couldn’t talk to those of another in thesame business—order entry couldn’t talk to invoicing which couldn’t talk to accountsreceivable.This meant re-entering required data multiple times.The solution was to standardize the data that was read by a computer program so that the datacould be read by all programs with that standard. Can you read the purchase order below?EDIFACT Standards Overview Tutorial 10GXS Proprietary and Confidential Information
Human readable purchase order:Standards translate the ‘human readable’ invoice to a ‘machine readable’ format:Part 9: Data Elements: Simple and CompositeA simple data element contains one piece of information. The composite data element containsmore than one piece of information, usually containing qualifiers.In EDIFACT, all mandatory data elements must contain data. Conditional data elements may ormay not contain data, depending on the requirements of the particular transmission.Since data elements must be accounted for by their position in the segment, if an optional orconditional data element does not have data, that data element must still be accounted for in itsposition within the segment by using the appropriate number of data element separators to ‘skipover’ the empty field. For example:EDIFACT Standards Overview Tutorial 11GXS Proprietary and Confidential Information
Here is a list of data element types and the rules that apply to them:NumericA numeric segment may contain only digits, a decimal point and, if negative, a minus sign.If the numeric is a given as a decimal, the number must have a digit before and after the decimalpoint. For example: 2.0 is correct (as is 2), however, 2. is wrong. 0.50 is correct (as is 0.5), .50 iswrong.AlphabeticAn alphabetic segment contains the specified number of alpha characters, including embeddedblanks. Leading spaces must be preserved.AlphanumericAlphanumeric segments contain the specified number of alphanumeric characters (includingembedded blanks). Leading spaces must be preserved.Different types of data elements also have specific rules they must follow. The data elementdictionary usually specifies the codes (identifiers) by using the words ‘coded’ or ‘qualifier’ inthe data element name:EDIFACT Standards Overview Tutorial 12GXS Proprietary and Confidential Information
Part 10: Composite Data Elements: Qualifier and ValueIn EDIFACT, the composite data element is made up of two or more pieces of data (known ascomponents) which form a single data unit. Typically the first data element is the value, which isbeing qualified. The second data element is typically the qualifier. These are typically ID (codevalues) fields. The qualifier gives additional definition to the value.Here is an example of a composite data element. This data element is in regard to financial institution information. This is the information provided in the segment detail:This is how the Party Qualifier data element (3035) is displayed in the message:The composite data elements (C078 and C088) are made up of various conditional componentsfrom the segment table. Because they are conditional, not all of the data elements are used. Allcomponents are separated by a sub-element qualifier (:). Take Self Test II to check your understanding at this point. Self Test II can be found at theend of this tutorial.EDIFACT Standards Overview Tutorial 13GXS Proprietary and Confidential Information
Part 11: Message Structure and Electronic EnvelopingThere are three significant steps for creating and sending data using nic.file.Part 12: Envelope ArchitectureLevels and Character SetsIn EDIFACT there are two levels in which messages may be transmitted. The use of a particularlevel designates which character set will be used: LEVEL A (UNA): only upper case; only printable characters LEVEL B (UNB): upper and lower case; includes non-printing characters for delimitersThe UNA Interchange is transmitted as a single string of 9 characters prior to the UNB Interchange segment. UNA is optional, and if not used, the defaults shown below apply:A release character is used when there is a need to transmit a message in which a character isdesignated as a delimiter, indicator or terminator, but it also represented in the message data. Forexample:The name of a company is DON’S DISTRIBUTION COMPANY. The apostrophe is designated as thesegment terminator. Question: How do you transmit the apostrophe in DON’S in your message?EDIFACT Standards Overview Tutorial 14GXS Proprietary and Confidential Information
Solution: Use a release character (normally ?). So the data would look as follows:DON’S DISTRIBUTION COMPANYIt is also possible to release the release character. The question: WHEN WILL YOU SEND THE SHIPMENT? would be transmitted: WHEN WILL YOU SEND THE SHIPMENT?Part 13: Electronic EnvelopingEDIFACT has two required levels of envelopes: Interchange (UNB/UNZ): a set from one sender’s mailbox address to another sender’s mailbox address Message (UNH/UNT): the envelope around one particular messageIn addition, there is one optional envelope level: Functional Group (UNG/UNE). It is used to grouplike messages together and for sub-addressing within an organization. In the US ANSI X.12 standards, this group level is where the message format and version are specified. Use of the UNG/UNE is mandatory to/from North America.The following diagram illustrates Electronic Enveloping:Part 14: The Message EnvelopeThe innermost envelope level is around each message. It is defined by the UNH/UNT segments.The UNH segment has four data elements: Message Reference Number (M): assigned by the sender’s computer and is part of theCONTROL mechanism.EDIFACT Standards Overview Tutorial 15GXS Proprietary and Confidential Information
Message Identifier (M): Composite which identifies the message being enveloped using thesix character message code (e.g., PAYEXT, REMADV) and the Version/Release data. Common Access Reference Number (C): Relates multiple transactions together. Status of the Transfer (C): Sequences a series of related messages.The UNT segment has two data elements: Number of Segments in a Message (M): count of segments in the message (includingUNH and UNT). Message Reference Number (M): same one that was used in the UNH for that particularmessage.Here is an example of how the CONTROL mechanism in the UNH element is used to validatemessage data:The Common Access Reference Number is used to identify a series of related EDIFACTmessages. For example, one purchase may involve a message exchange that requires four messagesto accomplish the complete business transaction as given here:1st Message: ORDERS (Purchase Order)2nd Message: DESADV (Dispatch Advice)3rd Message: INVOIC (Invoice)Buyer4th Message: REMADV (Remittance Advice)For Message #1: UNH 2348 ORDERS:D:94B:UN 10381 1:C’For Message #2: UNH 156009 DESADV:D:94B:UN 10381 2’For Message #3: UNH 156078 INVOIC:D:94B:UN 10381 3’For Message #4: UNH 2451 REMADV:D:94B:UN 10381 4:F’EDIFACT Standards Overview Tutorial 16GXS Proprietary and Confidential InformationSeller
Part 15: The Functional Group EnvelopeFunctional Group EnvelopeThe second (middle) envelope level is around each functional group. It is defined by the UNG/UNEsegments. The use of the UNG and UNE envelopes is mandatory for EDI to/from North America.This envelope groups like types of messages within a transmission. Here are a few examples of thedata elements in the functional group envelope: Functional Group (M) Message Identifier (M) Date/Time Stamp (M): Relates multiple transactions together. Status of the Transfer (C): Sequences a series of related messages. Group Reference Number (M) Controlling Agency (M) Message Version (M) Application Password (C)The UNE segment includes: Number of Segments in a Message (M) Message Reference Number (M)Functional Group Sub-AddressingFunctional Group envelopes contain a sub-addressing capability. The data that is sent to a particular receiver is addressed to the mailbox address on the UNB.Many companies want to route a group of data internally, so the UNG segment has a provisionfor user-defined addresses in the S006 and S007 elements.Here is a diagram that illustrates the sub-addressing function:EDI data fromthird-party networkExternalCommunicationsGeneral Electric Company CorporateEDI Clearing House, Schenectady, NYUNB:UNOA:1 123456789:1 987654321:1 Internal CommunicationsGE Aircraft EnginesCincinnati, OHGE AppliancesLouisville, KYGE LightingClevelend, OHUNG ORDERS 123456789:1 GEAE:92 .UNG ORDERS 123456789:1 GEAP:92 .UNG ORDERS 123456789:1 GEL:92 .Part 16: The Interchange EnvelopeThe outermost level of the message envelope structure is the interchange envelope. It is definedby the UNA, UNB and UNZ segements.EDIFACT Standards Overview Tutorial 17GXS Proprietary and Confidential Information
This envelope is used to identify data sent from one sender to one receiver:The UNA segment contains: Delimiter String Advice Examples of included data elementsThe UNB segment contains: Date/Time Stamp (M)Interchange Control Numbers (M)Password and Application Reference (C)Processing Priority Reference (C)Acknowledgment Request Indicators (C)Communications Agreement ID (C)Test Indicators (C)The UNZ segment includes: Interchange Control Numbers (M) Counts of Messages or Groups in the Interchange (M)Part 17: The CONTRL MessageIt is the responsibility of the receiver’s computer to check the syntax and control numbers of thetransmission and to build and transmit back to the sender this Functional Acknowledgment.The EDIFACT CONTRL message will provide this ation.and.generates.a.Functional.Acknowledgement. Take Self Test III to check your understanding at this point. Self Test III can be found at theend of this tutorial.EDIFACT Standards Overview Tutorial 18GXS Proprietary and Confidential Information
EDIFACT Wrap-upSome things to keep in mind: EDIFACT was orginally developed from a base of US ANSI standards and UN GTDIstandards. The syntax of both standards are remarkably similar. Many segments are similar in the two standards. Translation software can readily generate/accept either EDIFACT or ANSI ASC X.12 data. A key issue will be the organizational improvements needed to develop/maintain EDIFACT standards within the US and Canada.Thank you for using the GXS EDIFACT Tutorial. Please send all feedback to [email protected] GlossaryArea—Areas contain groups of segments that perform specific functions. The areas, in turn, makeup a message. To be complete, a message must contain a header area, detail area and summaryarea.Component—A composite data element made up of two or more pieces of data.Composite Data Element—Two or more related data items separated by a delimiter character,grouped together to form a unit or piece of information as defined in the data dictionary of asystem of EDI Standards, and contained in an EDI message.Conditional—Attribute that indicates that the data element may or may not contain data, de-pending on the message.Data Element—One or more data items, forming a unit or piece of information as defined in thedata dictionary of a system of EDI Standards, and contained in an EDI message or transactionset. The term “data element” is often abbreviated as “DE” followed immediately by the data element number (i.e., data element 128 would be abbreviated as DE128) in some texts.Data Element Separator (Delimiter)—Character that separates the individual data elements in asegment.EDIFACT—Also known as UN/EDIFACT, is the acronym for EDI for Administration, Commerceand Transport. It is the international message standard for EDI being developed through thecooperation of the United Nations and the Economic Commission for Europe (UN/ECE).Mandatory—Attribute that indicates that the data element must contain data.Nested Segment Group—Segment groups that reside within other segment groups.Qualifier—Typically an ID (code value) field, it is used to qualify a particular value in a segment.EDIFACT Standards Overview Tutorial 19GXS Proprietary and Confidential Information
Repetition Field—Entry in a segment table which states how many times a particular segmentmay repeat.Requirements Designator—Usage indicator of segment detail: Mandatory, Optional or Floating.Segment—A part of an EDI message or transaction set, made up of a number of logically-relateddata elements in a fixed, defined, sequence, separated by a delimiter, conveying a part of thebusiness transaction being made.Segment Tables—The message structure is defined in a listing known as a ‘segment table’. Thesegive the ‘rules’ of the message.Segment Tag—A three character alphanumeric code that identifies the segment.Segment Terminator—Character at the end of a segment that indicates no more data follows.Simple Data Element—A data element that contains one piece of information.Service Segment—Service Segments are Envelopes (UNB-UNZ, UNG-UNE, UNH-UNT),Delimiter String Advice (UNA), and Section Separators (UNS).UN/ECE—The United Nations/Economic Commission for Europe that oversees the developmentof the EDIFACT standard.Value—Typically, the first data element which is being qualified.Variable Length Data Element—Data element whose length changes depending on the number ofcharacters in the actual data. Minimum and maximum size of the element is given in the elementtable.EDIFACT Standards Overview Tutorial 20GXS Proprietary and Confidential Information
EDIFACT Self-Test I: After Completion of Part 5Select the most appropriate answer to the following questions:1. A primary benefit of EDIFACT is that.it is an industry-to-industry only standard.it is from the UN.it is both industry-to-industry and country-to-country.it is a form of data encryption.2. Messages:have all the of the next three features.collections of sequenced segments within defined areas.being with the UNH segment and end with the UNT segment.identified by a six character name.3. Message structure is defined in the:segment group.segment table.segment rules.segment tag.4. Segments contain.a segment tag.simple or composite variable length data elements.the data element separators or :.all of the above.EDIFACT Standards Overview Tutorial 21GXS Proprietary and Confidential Information
EDIFACT Self-Test II: After Completion of Part 10Select the most appropriate answer to the following questions:1. Which is true of data elements:All optional or conditional elements must be accounted for.All conditional elements are dependent on message requirements.All mandatory data elements must contain data.All of the above.2. EDIFACT uses two separate pieces of data in a single element:Value and QualifierSimple and CompositeNumeric and AlphabeticComposite and Component3. If there is an alphanumeric data element with an attribute of AN5, all of these would be correctexcept:KEN DEND 6448597TOM124. Optional data elements without data at the end of a segment.need additional data element separators to correctly position the data.must be accounted for by their position with the segment.do not need additional data element separators to correctly position the data.all of the above.EDIFACT Standards Overview Tutorial 22GXS Proprietary and Confidential Information
EDIFACT Self-Test III: After Completion of Part 17Select the most appropriate answer to the following questions:1. The characteristics of Level A EDIFACT transmissions are:upper case, includes non-printing characters for delimiters.upper and lower case.upper case with only printable characters.none of the above.2. A release character.allows the use of a delimiter or terminator within data.is normally the ‘?’.can release a release character.all of the above.3. EDIFACT has two required levels of envelopes:Interchange and Functional GroupMessage and InterchangeFunctional Group and MessageSub-Addressing and Message4. For an incoming message, it is the responsibility of the receiver’s computer to.check syntax, then build and transmit a Contrl message.check control numbers, then build and transmit a Contrl message.build and transmit a Contrl message.check syntax and control numbers, then build and transmit a Contrl message.EDIFACT Standards Overview Tutorial 23GXS Proprietary and Confidential Information
an international EDI standard a set of syntax rules data elements, segments and codes messages As shown in the following diagram, EDIFACT is the product of the evolution in bringing the Proprietary Standards of the US and Europe together to form a single internatio
