. ...
`
`.,.
`
`.••
`
`• . ;---~ . -
`
`• c.;;l.,
`
`i ANSI MH10.8.2-1995
`'
`
`Data Avolication
`..
`Identifier Standard
`
`.._
`
`__ ,,_ ...... ~--------------~~~~~
`
`~IV..,I American National Standards Institute
`11 West 42nd Street
`New York, New York
`
` 1
`
` of 94
`
`FedEx Exhibit 1007
`
`

`

`r·
`
` 2
`
` of 94
`
`

`

`ANSI ®
`MH1 0.8.2-1995
`Revision and redesignation of
`ANSI/FACT 1-1991
`
`Data Application .Identifier Standard
`
`)
`
`Secretariat
`Material Handling Institute
`_/
`
`Approved November 15, 1995
`American National Standards Institute, Inc.
`
` 3
`
` of 94
`
`

`

`American
`1\k:dil"''n ~I
`Standard
`
`1 ... 1...4.'-IVIII..A.I
`
`Approval of an American National Standard requires verification by ANSI that the
`requirements for due process, consensus, and other criteria for approval have
`be0n met by the standards deve!oper.
`
`f
`\
`
`Consensus is established when, in the judgment of the ANSI Board of Standards
`Review, substantial agreement has been reached by directly and materially
`affected interests. Substantial agreement means much more than a simple
`majority, but not necessarily unanimity. Consensus requires that all views and
`objections be considered, and that a concerted effort be made toward their
`____ ,,, ... : __
`I t::::>UIUliUI I.
`
`The use of American National Standards is completely voluntary; their existence
`does not in any respect preclude anyone, whether he has approved the
`standards or not, from manufacturing, marketing, purchasing, or using products,
`processes, or procedures not conforming to the standards.
`
`The American National Standards Institute does not develop standards and will in
`no circumstances give an interpretation of any American National Standard.
`Moreover, no person shall have the right or authority to issue an interpretation of
`an American r'"Jational Standard in the name of the American f'Jational Standards
`Institute. Requests for interpretations should be addressed to the secretariat or
`sponsor whose name appears on the title page of this standard.
`
`CAUTION NOTICE: This American National Standard may be revised or
`withdrawn at any time. The procedures of the American National Standards
`Institute require that action be taken periodically to reaffirm, revise, or withdraw
`this standard. Purchasers of American National Standards may receive current
`information on all standards by calling or writing the American National Standards
`Institute.
`
`(
`
`Published by
`
`American National Standards Institute
`11 West 42nd Street, New York, New York 10036
`
`Copyright ©1996 by American National Standards Institute
`All rights reserved.
`
`No part of this publication may be reproduced in any
`form, in an electronic retrieval system or otherwise,
`without prior written permission of the publisher.
`
`Printed in the United States of America
`
`APS2C496/65
`
` 4
`
` of 94
`
`

`

`Document Number: ANSI MH 10.8.2-1995
`
`Title: Data Application Identifier Standard
`(revision and redesignation of ANSIIF ACT 1-1991)
`
`Scope: Covers-a comprehensive dictionary of data and application identifiers, assign new data identifiers, as required,
`and to provide a document detailing the correlation, or mapping, of data identifiers to application identifiers, where a
`correlation exists.
`
`,--
`\ )
`
`C.~
`
` 5
`
` of 94
`
`

`

`.•
`
`(1
`
`n
`
`l
`I ,
`
` 6
`
` of 94
`
`

`

`r-
`
`Contents
`
`Section
`
`Page
`
`Foreword ...................................................... .......... .................. ......... .. .... . ii
`
`Definitions ........................................................ ...... ........... ...... ..... ... ....... .. 1
`
`FACT Data Identifiers (Dis) .................. ..... ..... ......... ..... ...................... 7
`
`II
`
`UCC/EAN Application Identifiers (Ais) ... ..................... .. .. ... ... .. ........... 23
`
`Ill Mapping FACT Dis and UCC/EAN Als .................... .. ......................... 27
`
`IV Mapping UCC/EAN Als to FACT Dis ..... ............. .. ... .. ... ...... .. ............. 41
`
`V Short titles ........... ............ .. ................. ........................................... .. 45
`
`VA FACT Dl short titles .......... ......................................................... .. 46
`
`VB UCC/EAN AI short titles .... ......................... ............ .. .......... .. ....... 49
`
`Annexes
`
`A Quick reference to Data ldentifer (DI) categories ............................... 51
`
`8 Annotated listing of assigned Data Identifier (DI) catagories .............. 53
`
`C Data Identifier (DI) application notes ...................................... .. .. .. ..... 56
`
`D Data element number 355
`Unit of measure code (ANSI X12.3) ................................................... 67
`
`E Data element number 374 date/time codes (ANSI X12.3) ................... 72
`F Data element numbers 208 & 209
`Hazardous material codes (ANSI X12.3) .............................. ... .......... 74
`
`G Unit of value
`Currencies and funds (ISO 4217) ... ................................................... 75
`
`H
`
`ISO 3166: 1988 (E/F) country code ............ .. ...... .... .......... .. ............... 76
`
`Data identifier and application identifier request forms ...... ................ 77
`
`J
`
`User guidance ............... ........ ... ........... ............................................. 84
`
` 7
`
` of 94
`
`

`

`Foreword (This foreword is not part of American National Standard MH10.8.2-1995.)
`
`The Federation of Automatic Coding Technologies (FACT) developed a
`standard for Data Identifiers (Dis) in 1989. In early 1990 FACT submitted
`the FACT Data Identifier Standard dated October 2, 1989 to the American
`National Standards Institute (ANSI). This standard was approved in 1991
`and has been published as ANSI/FACT 1-1991.
`
`In 1991 the Uniform Code Council (UCC) and the EAN International (EAN)
`adopted an expanded list of application identifiers which served many of
`the same purposes as had been accomplished with FACT Dis. These
`UCC/EAN identifiers are known as Application Identifiers (Ais).
`
`The existence of two approaches to accomplish the same level of identifi(cid:173)
`cation became a burden to those companies supplying general trade prod(cid:173)
`uct to many customers. FACT was asked to develop a standard that would
`harmonize these two approaches.
`
`The stated mission of the UCC is to enable " ... related distribution channels
`to operate more efficiently and effectively while contributing added
`value ... " to the end user. FACT's mission statement included a charge to
`" ... reduce the proliferation of conflicting bar code standards ... " to achieve
`similar efficiencies.
`
`Recognizing their common missions, F.t.,CT and UCC committed to the
`development of a committee that would issue a comprehensive dictionary
`of data and application identifiers. The dictionary would be to ANSI a revi(cid:173)
`sion for ANSI/FACT 1-1991.
`
`On December 31, 1992 the FACT organization was dissolved. Prior to its
`dissolution, the SBC-8 Subcommittee of ANSI MH1 0 agreed to continue its
`maintenance and assume responsibility for the document.
`
`It is the mission of this committee to develop a comprehensive dictionary
`of data and application identifiers, assign new data identifiers, as required,
`and to provide a document detailing the correlation, or mapping, of data
`identifiers to application identifiers, where a correlation exists.
`
`As with any standard, new requirements are identified and interested par(cid:173)
`ties request the assignment of new Data Application Identifiers to meet the
`needs of a particular industry or activity. Under ANSI rules, ANSI stan(cid:173)
`dards are valid for five (5) years from the date of publication, after which
`time these standards are either reaffirmed, modified, or withdrawn. During
`the intervening five-year period between publication and re-review a
`Working Document is maintained by a maintenance committee.
`
`This standard contains 10 annexes that are for information only and are
`not part of this standard .
`
`Users desiring assignment of new Data Identifiers may submit their
`request to the ANSI MH1 0.8.2-1995 Chairman, Craig K. Harmon
`(Telephone: +1 319/364-0212; Fax: +1 319/365-8814).
`
`North American users desiring assignment of new Application Identifiers
`may submit their request to the Uniform Code Council, Inc., Attn:
`Technical Director, (Telephone: +1 513.435.3870; Fax: +1 513.435.4749).
`Users in other countries desiring assignment of new Application Identifiers
`may submit their request to EAN International , Attn: Technical Director,
`(Telephone: +32 2.218 .76.74; Fax : +32 2.218.75 .85).
`
`ii
`
` 8
`
` of 94
`
`

`

`)
`
`These Data Application Id e ntifi e r Guidelines were prepared by the
`ANSI/FACT-1 Work Group (WG2) of ANSI MH10 SBC-8 who maintained
`contact with the following individuals involved with the associated stan(cid:173)
`dards-making activities:
`
`Gary Ahlqui st, ANSI MH1 0 SBC-8 Chairman
`Allan Gilligan, ANSI MH1 0 Chairman
`Craig K. Harmon, ANSI/FACT 1-1991 & ANSI MH1 0.8.2M-1995 Chairman
`Robert F. McQuade, FACT Chairman 1988, Secretary/Treasurer 1992
`Roger Morrison, ANSI MH1 0 Chairman
`Marilyn Sherry, FACT Chairman 1990
`
`Name of Representative
`Organization Represented
`A.B. Chance Company ................ .. .... ....... ... .................. .... Richard Milhollin
`American Furniture Manufacturers Association (AFMA) ...... Larry Runyan
`American Trucking Associations {ATA) ....... ................. .. .... Doug Anderson
`AMP, Inc . ... .. ... ............................. .. .... .. ... ........................ .. Richard M. Farrell
`Robert Osif
`Article Numbering Association (UK), Ltd. (ANA) ................ . Andrew Osborne
`Association Franyaise de Normalisation (AFNOR) ........ .... .. Phillip Camuset
`Michel Grolee
`
`Asociacion Mexicana del Codigo
`de Producto AC (AMECOP) ...... ...... .... .. .... ................ ...... . Lourdes Sanchez de Ia Vega
`Australian Product Numbering Association (APNA) ...... .. .... Brian Smith
`Automatic Identification Manufacturers (AIMusA) .......... .. .... Dan Mullen
`Boeing Company .................... ......... ...... .... ........................ Ron Pemberton
`Caterpillar, lnc ............................... .. .. .. ....................... .. ..... Joe Burgess
`Comite Europeen de Normalisation (CEN) .................. .. ..... Michael Laplane
`Jelte A. Dijkstra
`David Mendus
`.
`Computing Technology Industry Association (CTIA) .. .... ..... Martha Wahsoki
`Department of Defense (DoD) .............. ............ ...... ........ .... Stuart Crouse
`Distribution Code Center (DCC) ...... ...... ............ .. .... ........... Asano Kyosuke
`Dow Chemical USA ..... ... ... ..... ........ .... .. ... ............ .. ........ .... Steve Puett
`DuPont Engineering ...... .... .... ... ............ .. ........ .. ..... ... .. .. .. ... Richard Ungerbuehler
`Eastman Kodak Company ...... .. .. .. ... .... .. .. .......... ..... .... ..... .. . John Brasser
`EDI Center (EIAJ) ... ....... .. ......... .. .. ...... ... .. .. ....... ... ....... ....... Yasuyuki Sakakibara
`Ericisson Telecom AB ............ ... ..... ..... .. ....... ... .. ..... .. ...... .... Lars Magnusson
`IBM D.E.S .C ...... .................................. .. .... .... ... ...... ....... .... Karsten Staiger
`EHIBCC ......... ............................. ... .. ........ .............. .. .. .. ..... Philip L. Martin
`GE ED&C .. .... .................................. ...... .. .. ............. .... ... .... AI Collver
`Graphic Communications Association (GCA) .......... ............ Alan Kotok
`Intelligent Data Acquisition Technologies (IDAT) ..... ...... ..... Bert Moore
`Levi Strauss & Company ............ ... ............ ................ .. .. .... James D. Sykes II
`LTV Steel .. ....... .. ................................. .... ................ ..... ..... Leo Roach
`Matsushita Electric Corporation (Panasonic) ................ ...... Betsy Schneider
`McDonn ell Douglas Corporation .. .. ...... .. .. .. .. .. .. .. .. ....... ...... .. Gerry Mueller
`Rick Lafferty
`MEMC ..... .. .. ... .... ....... ....... ....... ... .. ........ ... ...... .. .. .. ...... .. ...... Gerald Gayer
`Monarch Marking ..... ....... .... .. ....... ... .. .. .. ....... ........ .. ....... ..... Larry Graham
`Moore Rese arch ............... ...... .. ... .. ........ ...... ...................... Delmer H. Oddy
`National Housewares Manufacturers Association (NHMA) .. Dianne L. Sawaya
`New Zealand Product Number Association (NZPNA) .......... Barry Houston
`Praxis Consultants ........................ .. ....... ... ........................ Paul Chartier
`Product Code Council of Canada (PCCC) .... ...................... David Armstrong
`PSC ... ... .. .. .... .... .......................... .............. ........................ Chuck Biss
`Roadway Package Systems (RPS) .... .... ....... ......... .. .......... Amy Santucci
`Semco, Sweet & Mayer .................... ........ ........... .. ............ Andrew Chesley
`Semiconductor Equipment & Materials
`International (SEMI) .. .. ...... ... .. ... ....... ..... ... ... ..... .... .... .. ..... Xavier Pucel
`Siemens AG ..... ..................... ............ .... .... ... .... .......... .. ..... Hartmut Hermes
`Spectra-Physics ...................... .... .. .......... ......... .. ... ..... .. ..... Phillip Shepard
`Standard Register .. .. .... .. .. ....... .. ..... .. .. ... .. ............ ....... .... ... Marty Hileman
`Stone Container ....... ........... ....... ........... .. ............... ........ ... Doug Reinke
`
`iii
`
` 9
`
` of 94
`
`

`

`Name of Representative
`Organization Represented
`Symbol Technologies ................... ................. ........ .... ..... ... Rob Durst
`Tina Barkan
`Uniform Code Council (UCC) ....... .... ... ........ .... .. ............... .. Bruce Philpot
`Tom Brady
`Union Carbide Chemical & P!astic ................................... ... Dave Hill
`United Parcel Service .................. ..... .. ............................... Mark Lewis
`Upjohn Company .......................... ............. .... .......... ....... ... Jerome Johnson
`Zebra Technologies ...................... ........... .......................... Karen Longe
`
`(
`
`iv
`
`
`
`10 of 94
`
`

`

`AMERICAN NATIONAL STANDARD
`
`ANSI MH10.8.2-1995
`
`Data Application Identifier Standard
`
`' -
`
`Referenced standards
`
`The cmrent standard or "draft standard approved for trial use" of all referenced ANSI, ISO and UCC/EAN
`standards shall apply where referenced within this document.
`
`Definitions
`
`For the purposes of these Guidelines, the following definitions shall apply:
`"+" (PLUS SIGN)
`The "+" is used with specific data identifiers defined within this document (e.g., 14K and 3W) to
`separate different types of data that are encoded within a single field (e.g., a single bar code
`symbol). The"+" is also referenced as a flag character used by the HIBCC.
`<SPACE>
`See DI Indicator.
`ACTUAL WEIGHT
`The weight as measured. Also see "Theoretical Weight".
`ALLOCATED
`Set aside for a specific purpose, such as a set of Data Identifiers allocated for a specific Category.
`ALPHANUMERIC CODE
`A code containing both numbers (0-9) and alphabetic characters (A-Z).
`APPLICATION IDENTIFIER
`A UCC/EAN specified character (or string of characters) that defines the general category or
`intended use of the data that follows.
`ASSIGNED
`Designated for a specific purpose, such as a given Data Identifier assigned for a specific purpose
`(e.g., "Container Type" has been assigned the Data Identifier "B".)
`AUTHORIZED RETAIL INDUSTRY FORMAT
`A coding structure assigned by the Uniform Code Council (UCC) or EAN International.
`BILL OF LADING
`An itemized list of goods contained in a shipment.
`BUDGET RESPONSIBILITY
`Accountability for the planning and reporting of resource expenditures.
`CARRIER
`In a transaction, the party that provides transportation services (e.g., air, boat, rail, truck, etc.).
`CATEGORY
`A class or division in a scheme of classification (e.g., the Category for dating formats is
`Category 4: Date.).
`
`A discrete system which performs a predetermined series of operations in the manufacture or
`assembly of an item.
`
`
`
`11 of 94
`
`

`

`ANSI MH10.8.2-1995
`
`CHARACTER
`A letter, digit or special character (e.g.,-,+,/,$) that is used to represent data.
`
`CLOSED SYSTEM
`-
`A system in which a single authority has control over all elements (e.g., data content, bar code
`printing, bar code scanners). Opposite of II Open System. II
`
`CODE
`
`A structured set of characters used to represent an entity, event, person, or organization. For
`example: 01, 02, ... ,12 may be used to represent the months January, February, ... , December.
`
`COMMON CARRIER
`A transportation business that offers service to the general public. Also see "Carrier."
`
`CONCATENATE
`The combination of specific pieces of data into a single field. In this document variable length data
`is separated by a plus "+" symbol (e.g., 3W and 14K). Application standards may define
`additional uses for a concatenation character.
`
`CONTAINER
`Something that encloses or can enclose one or more items (e.g., box, crate, can, jar, etc.).
`
`CONT.A ThJER SPCUP~TTY SEAL
`A pre-numbered device designed to secure a container to preclude its being opened without
`detection (e.g., doors of a truck trailer).
`
`CUSTOMER
`In a transaction, the party that receives, buys, or consumes an item or service.
`
`DATA IDENTIFIER
`A specified character (or string of characters) that defines the general category or intended use of
`the data that follows.
`
`DI INDICATOR
`An encoded <space> character which may, in specific instances, be encoded after a FACT DI.
`This character is used to indicate to the host computer system the presence (or end point) of a data
`identifier string. See C. I for further information.
`
`DIGIT
`
`Any of the numeric characters 0 (zero) through 9 (nine), inclusive.
`
`DUNS Number
`A nine-digit site specific trading partner identification code assigned by Dun & Bradstreet.
`
`(L. exempli gratia) for example.
`
`ELECTRONIC DATA INTERCHANGE CEDI)
`The electronic exchange of structured information between locations over a telecommunications
`network. Usually refers to business transactions transmitted from one computer application to
`another computer application.
`
`(
`
`( .
`
`2
`
`
`
`12 of 94
`
`

`

`ANSI MH10.8.2-1995
`
`EMPLOYEE
`One whose labor or services are engaged by another, either for pay or on a volunteer basis.
`
`ENTITY
`In this document, any person, place or thing that can be distinctly identified from other identical or
`like persons, places, or things. A subset of "Item".
`
`EXCLUSIVE ASSIGNMENT
`A data identifier whose prior use by a single specific agency, under a previously existing standard,
`is recognized by ANSIIF ACT 1 and whose use is d~fined within these Guidelines as the sole
`province of that agency. Also see "Prior Assignment".
`
`FIRST LEVEL. .. FIFTH LEVEL
`Used to provide additional or different levels of information about a class of items or entities within
`a category (such as "L," "P," or "T") about the same entity. See C.5.2, C.6, and C.9, respectively,
`for examples.
`
`FIXED ASSET
`A durable or non-consumable item owned by a company or agency.
`
`FLAG CHARACTER
`A character that is used to signify that the data that follows conforms to a specific industry
`standard. Note that these standards do not conform with the overall FACT DAI Standard. See
`Category 0.
`
`(L. id est) that is (to say).
`
`Il'RM
`
`A member of a class of entities or services that may be grouped together because of certain likeness
`or common traits (e.g., a part or a service). Also see "Entity".
`
`ITEM CODE
`A code identifying an item.
`
`MANUFACTURER
`Actual producer/fabricator of an entity not necessarily the supplier in a transaction. Manufacturer's
`ID code is a property of an entity, not of a transaction. See "Supplier" for transaction.
`
`MUTUALLY DEFINED CODE
`A code whose meaning has been agreed upon by all appropriate parties to the transaction.
`
`No equivalent data identifier for application identifier or no equivalent application identifier for data
`identifier.
`
`NUMBER
`A set of characters which refer to a code structure, not restricted to numeric digits.
`In this
`document the term "number" is used synonymously with the term "code". Also see "numeric
`code".
`
`3
`
`
`
`13 of 94
`
`

`

`ANSI MH10.8.2-1995
`NUMERIC CODE
`A code that contains only the digits 0 (zero) through 9 (nine).
`
`OPEN SYSTEM
`A system that conforms to established standards and therefore can be readily connected to other
`systems that comply with the same standard. Opposite of "Closed System".
`
`(
`
`OPERATION
`A process or action that is part of a series in some work. The process whereby a work piece is
`changed from one state to some other state.
`
`OPER-A. TION CODE
`A code used to identify the type of work performed.
`
`OPERATION SEQUENCE NUMBER
`A number that defines the order of a particular operation in a series of operations, generally in a
`manufacturing or assembly process.
`
`ORDER
`A request or commission to make or provide an item or service (e.g., purchase order, shop order,
`customer order, work order).
`
`PACKAGEID
`A code that provides the ability to differentiate one package from any other package (e.g., carton or
`label serial number). Also see "Serial Number".
`
`PACKAGING
`The container, wrapping, etc. (generally considered to be disposable), in which a commodity is
`packed for sale or transport. That which provides protection and containment of items plus ease of
`handling by manual or mechanical means.
`
`PRIOR ASSIGNMENT
`Data identifiers with which there were significant conflicts among industry standards at the time
`this document was created. These data identifiers will not be assigned until all conflicts are
`resolved. Data identifier definitions which are indicated as "Prior Assignment" have been recreated
`elsewhere in this document in non-conflicting configurations. A Prior Assignment is a data
`identifier that was previously assigned by more than one other standards' body for different
`categories. Instead of arbitrarily choosing one standard's category over the other, ANSIIF ACT -1
`declared the conflicting data identifier as a Prior Assignment and then recreated the definition
`elsewhere in the document in a non-conflicting configuration.
`
`PRO NUMBER CPRO #)
`The unique number assigned by a motor freight carrier and placed on a freight bill for internal
`billing purposes. The PRO (PROgressive) number is usually the freight bill (invoice) number.
`May also be affixed to a container (or containers) in a shipment for tracking purposes.
`
`RESERVED
`A category or data identifier that is being held for future use by the committee controlling this
`document.
`
`4
`
`( .
`
`
`
`14 of 94
`
`

`

`ANSI MH10.8.2-1995
`
`RETURNABLE CONTAINER
`A container which, after having been used to enclose or transport items, is returned to the supplier
`or owner.
`
`ROUTE CODE
`As employed in DI "6L"- Data element #1 of the TDCC/ANSI Trade Elements Data Dictionary.
`Route Code may have up to 13 characters.
`
`SERIAL NUMBER
`A unique code assigned to an item that provides for the differentiation of that item from any other
`like item. Within these guidelines serial number takes on two meanings. The first meaning is a
`code assigned to an individual entity for the life of the product such as a computer serial number.
`The second meaning is a code assigned to a package, usually contained on the package label, that
`uniquely identifies that package from any other package.
`
`STATUS CODE
`A code that represents a condition or situation.
`
`SUPPLIER
`In a transaction, the party that produces, provides, or furnishes an item or service, other than
`transportation services. Also see "Carrier" and "Manufacturer".
`
`THEORETICAL WEIGHT
`Weight as calculated. Also see ''Actual Weight".
`
`TOOLIDCODE
`A code that uniquely identifies a particular implement required by a person or machine to perform a
`task.
`
`_)
`
`TRACEABILITY NUMBER
`A number assigned by a controlling authority to provide unique identification to an entity or group
`of entities for subsequent tracking and/or identification.
`
`TRANSACTION
`An exchange conducted, performed or carried out between two (or more) parties that accomplishes
`a particular action or result.
`
`VMRS
`
`Vehicle Maintenance Reporting Standard is an established standard used to identify and track
`vehicle repair parts, primarily in the transportation industry, having cross-industry (and
`international) application for any company which maintains a fleet of vehicles.
`
`WAYBILL
`A document prepared by the carrier of a shipment of goods that contains details of the shipment,
`route, and charges.
`
`WORK ORDER NUMBER
`An identifying number associated with the process, or authorization of, the manufacture or
`assembly of an item.
`
`5
`
`
`
`15 of 94
`
`

`

`(
`
`(
`
`
`
`16 of 94
`
`

`

`SECTION I
`FACT
`DATA IDENTIFIERS
`(Dis)
`
`
`
`17 of 94
`
`

`

`ANSI MH10.8.2-1995
`Defined categories
`
`NOTE- The usage of the te1m "number" below is not intended to be restricted to numeric characters only,
`but to generically refer to a code structure that may contain numeric and/or alphabetic data. The following
`Data Identifiers are assigned to the usages described. The usage of any alphabetic, numeric, or special
`character in a leading position (as a "data Application Identifier") not defined herein is reserved for future
`assignment by the body controlling these guidelines. Unless otherwise specified leading zeroes (O's) are
`non-significant and not to be employed (e.g., OA, OOA, OOOA, OlA, OllA). References to other ANSI
`Standards are to the most current version of that standard.
`
`(
`
`CATEGORY 0:
`Allocation:
`Assigned:
`
`CATEGORY 1:
`Allocation:
`Assigned:
`
`CATEGORY 2:
`Allocation:
`Assigned:
`
`Special Characters Not Assigned or Controlled by ANSI MH10.8.2 1l
`All Non-Alphanumeric Characters
`+
`Health Industry Business Communications Council
`(HIBCC)
`Prior Assignment
`American Association of Blood Banks (AABB)
`International Society for Blood Transfusion (ISBT)
`Graphic Communications Industry Bar Code Council
`(GIBC)
`Appears in the first position following the symbology start
`character of a Code 128, Code 49, or Code 16K
`Symbol to signify a UCC- or EA1'~-controlled symbol
`
`&
`=
`I
`
`FNCl
`
`Reserved
`A- 999A
`A -SA
`6A- 999A
`
`Prior Assignment
`Reserved
`
`Container Information
`B- 999B
`B
`lB
`
`Container Type (internally assigned or mutually defined)
`Returnable container identification code assigned by the
`container owner or the appropriate regulatory agency (e.g., a
`metal tub, basket, reel, unit load device (ULD), trailer, tank,
`or intermodal container) (excludes gas cylinders See "2B'')
`Gas Cylinder Container Identification Code assigned by the
`manufacturer in conformance with U.S. Department of
`Transportation (D.O.T.) standards
`Motor Freight Transport Equipment Identification Code
`assigned by the manufacturer in conformance with
`International Standards Organization (ISO) standards
`Reserved
`
`2B
`
`3B
`
`4B- 999B
`
`1 l This is not an exhaustive list. It is not advisable to assign special characters in a "closed" system unless an exhaustive search has
`been accomplished that ensures that the special characters in question will never be confronted on items supplied from outside the
`closed system.
`
`8
`
`(
`
`
`
`18 of 94
`
`

`

`CATEGORY 3:
`Allocation
`Assigned:
`
`FieJd Continuation
`C- 999C
`c
`
`CATEGORY 4:
`Allocation:
`Assigned:
`
`lC
`
`2C
`
`3C
`
`4C
`sc
`
`6C- 999C
`
`Date
`D- 999D
`D
`lD
`2D
`3D
`4D
`SD
`
`6D
`
`7D
`8D
`9D
`lOD
`llD
`12D
`13D
`
`2) Mutually Defined Significance
`
`14D- 999D
`
`ANSI MH10.8.2-1995
`
`Continuation of an Item Code (Categ01y 16) assigned by
`Customer that is too long for a required field size
`Continuation of Traceability Code (Category 20) assigned
`by Supplier
`Continuation of Serial Number (Category 19) assigned by
`Supplier
`Continuation of Free Text (Category 26) mutually defined
`between Supplier/Carrier/Customer
`Continuation of Transaction Reference (Category 11)
`mutually defined between Supplier/Carrier/Customer
`Continuation of Item Code (Category 16) Assigned by
`Supplier
`Reserved
`
`Format YYMMDD2>
`Format DD:MM_Y"Y2>
`F01mat :MMDDW>
`Format YDDD (Julian ?
`Format YYDDD (Julian )2>
`ISO format YYMMDD immediately followed by an ANSI
`X12.3 Data Element Number 374 Qualifier providing a code
`....,_,...."':C",..r;_,_ 4-.... r_,.... ,..,C ,.1'""'4-~ f"' r-
`roh~"r'- ..-lnf-.o
`.......,n....,11f"nrof-11rn.. rlr,t-a\
`L>J:lCvU.J .lUO LJ J:'C V.l UUlv \ '-'·o•> i)lHl' UULv, UlUllULU.vLUliJ UU.Lv)
`ISO format YYYYMMDD immediately followed by an
`ANSI Xl2.3 Data Element Number 374 Qualifier providing
`a code specifying type of date (e.g., ship date, manufacture
`date)
`Format MM_YY2>
`Reserved
`Date (structure and significance mutually defined)
`Format yYWV(2>
`Format -yyyyww>
`Format YYYYMMDD2>
`Oldest and Newest Manufacturing Date in the format
`YYWWYYWW
`Reserved
`
`9
`
`
`
`19 of 94
`
`

`

`ANSI MH10.8.2-1995
`
`CATEGORY 5:
`Allocation:
`Assigned:
`
`CATEGORY 6:
`Allocation:
`Assigned:
`
`CATEGORY 7:
`Allocation:
`Assigned:
`
`CATEGORY 8:
`Allocation:
`Assigned:
`
`Reserved
`E- 999E
`E
`lE- 999E
`
`Reserved
`F- 999F
`F
`lF- 999F
`Reserved
`G- 999G
`G
`lG- 999G
`
`Human Resources
`H- 999H
`H
`lH
`2H
`3H
`
`4H
`SH- 999H
`
`CATEGORY 9:
`Allocation:
`Assigned
`
`Reserved
`I- 9991
`I
`
`(
`
`Prior Assignment
`Reserved
`
`Prior Assignment
`Reserved
`
`Prior Assignment
`Reserved
`
`Reserved
`Employee Identification Code assigned by employer
`U.S. Social Security Number
`ID Number for non-employee (internally assigned or
`mutually defined) (e.g., contract workers, vendors, service,
`and delivery personnel)
`National Social Security Number
`Reserved
`
`Exclusive Assignment (U.S. Vehicle
`Identification Number- VIN)
`Reserved
`Abbreviated VIN Code
`Not recommended for use due to similarity of "1" to "I"
`
`Unique license plate number*
`Unique license plate number* assigned to a transport unit
`that is the lowest level of packaging, the unbreakable unit
`Unique license plate number* assigned to a transport unit
`that contains multiple packages
`Unique license plate number* assigned to a transport unit
`that is the lowest level of packaging, the unbreakable unit
`and which has EDI data associated with the unit
`Unique license plate number* assigned to a transport unit
`that contains multiple packages and which is associated
`with EDI data
`*Note: For a license plate number to be unique world wide requires: 1) A unique number assigned
`by the trading partner, 2) A unique code assigned to the trading partner by an organization, and
`3) A unique code providing global identification of the assigning organization.
`
`CATEGORY 10:
`Allocation:
`Assigned:
`
`11
`2I
`31- 9991
`Reserved
`J- 999J
`J
`lJ
`
`2J
`3J
`
`4J
`
`10
`
`
`
`20 of 94
`
`

`

`CATEGORY 11:
`Allocation:
`Assigned:
`
`- -.
`
`ANSI MH10.8.2-1995
`
`Transaction Reference Used In Trading Relationships
`K - 999K
`K
`
`Order number assigned by Customer to identify a
`Purchasing Transaction (e.g., purchase order number)
`Order number assigned by Supplier to identify a Purchasing
`Transaction
`Bill of Lading/Waybill/Shipment Identification Code
`assigned by Supplier/Shipper
`Bill of Lading/Waybill/Shipment Identification Code
`assigned by Carrier
`Line number of the order assigned by Customer to identify a
`Purchasing Transaction (See Annex C.l 0)
`Reference number assigned by the Customer to identify a
`Shipment Authorization (Release) against an established
`Purchase Order
`PRO# Assigned by Carrier
`Carrier Mode in Free Text format mutually defined between
`Customer and Supplier (e.g., Air, Truck, Boat, Rail)
`Contract Number
`Generic Transaction Reference Code (internally assigned or
`mutually defined)
`Invoice Number
`Packing List Number
`SCAC (Standard Carrier Alpha Code) (an4- dash"-" filled
`left) and carrier assigned PROgressive number
`Reserved
`Combined Order Number and Line Number in the format
`nn ... nn+nn ... n where a plus symbol ( +) is used as a
`delimiter between the Order Number and Line Number
`KANBAN Number
`DELINS Number: code assigned to identify a document
`that contains delivery information
`Check Number
`Reserved
`
`lK
`
`2K
`
`3K
`
`4K
`
`SK
`
`6K
`7K
`
`8K
`9K
`
`lOK
`llK
`12K
`
`13K
`14K
`
`lSK
`16K
`
`17K
`18K- 999K
`
`11
`
`
`
`21 of 94
`
`

`

`ANSI MH10.8.2-1995
`
`CATEGORY 12:
`Allocation:
`Assigned:
`
`Location Reference
`L- 999L
`L
`lL
`2L
`
`3L
`
`4L
`SL
`
`6L
`
`7L -19L
`
`Storage Location
`Location
`"Ship To:" Location code defined by an industry standard or
`mutually defined
`"Ship From:" Location code defined by an industry standard
`or mutually defined
`Country of