Skip to main content
Home
  • AI Mode
  • Supply Chain Orchestration
    fast
    Supply Chain Orchestration
    • Life Sciences Company
    • Direct Material Supplier
    • Contract Manufacturer
    • Third Party Logistics
    • Wholesale Distributor
    • Healthcare Provider
    • Retail Pharmacy
  • Network
  • Products
    fast
    Products
    • Multienterprise Information Network Tower (MINT)
    • Process Orchestration for Empowered Teams (POET)
    • Track-and-Trace
  • Resources
    fast
    Resources
    • Resource Center
    • TraceLink University
    • Partners
    • Community
    • Events
  • About
    fast
    About
    • Our Story
    • Newsroom
    • Culture and Careers
    • Leadership
    • Our Values
    • Corporate Social Responsibility
    • Contact Sales
  • Log In
    • Tracelink Classic
      TraceLink Classic app.tracelink.com
      Redirect
    • Opus Platform
      Opus Platform opus.tracelink.com
      Redirect
Log In
  • Tracelink Classic
    TraceLink Classic app.tracelink.com
    Redirect
  • Opus Platform
    Opus Platform opus.tracelink.com
    Redirect
Tracelink University

Breadcrumb

  1. Home
  2. Resources
  3. TraceLink University

Advance ship notice (EDIFACT)

  • Download PDF
  • Share
    • LinkedIn
    • Facebook
    • Mail
    • Twitter

Table of contents

Shipment notices allow companies to exchange serialized data for sales shipments with upstream and downstream supply chain trade partners without giving these trade partners access to their serialization system of record. These shipment notices can be used to inform their Partners of the contents of a shipment, and the notices also allow these companies to comply with government regulations or recommendations for sharing serialized data about shipments.

The Advance ship notice (ASN) EDIFACT message sends data about a purchase order the supplier is fulfilling and notifies the buyer of the pending goods delivery.

Contact your TraceLink Services representative for more information about integrating with this message.

  • Message Type: MPC_ADVANCE_SHIP_NOTICE (Advanced Ship Notice)
  • EDIFACT Format: DESADV
  • Transform Names:
    • B2B_EDI_EDIFACT_DESADV_AdvanceShipNotice_IB_V6

    • B2B_EDI_EDIFACT_DESADV_AdvanceShipNotice_OB_V4
ClosedGuidelines
Input Element Occurs Length Description Example
UNB [1…1]
– Required.Interchange header. –
  UNB01 [1…1]
– Required.Syntax identifier. –
    UNB01.1 [1…1]
4/4 Required.Syntax identifier. UN0B
    UNB01.2 [1…1]
1/1 Required.Syntax version number. 1
  UNB02 [1…1]
– Required.Interchange sender. –
    UNB02.1 [1…1]
1/35 Required.Sender identification. SENDER1
    UNB02.2 [1…0]
1/4 Partner identification code qualifier. 14
    UNB02.2 [1…0]
1/14 Address for reverse routing. –
  UNB03 [1…1]
– Required.Interchange recipient. –
    UNB03.1 [1…1]
1/35 Required.Recipient identification. RECEIVER1
    UNB03.2 [1…1]
1/4 Required.Partner identification code qualifier. 14
    UNB03.3 [1…1]
1/14 Required.Interchange recipient internal identification. –
  UNB04 [1…1]
– Required.Date and time of preparation. –
    UNB04.1 [1…1]
6/6 Required.Date of preparation format: YYMMDD. 231020
    UNB04.2 [1…1]
4/4 Required.Time of preparation Format: hhmm. 142000
  UNB05 [1…1]
1/14 Required.Interchange control reference. 131
  UNB06 [0…1]
– Recipients reference password. –
    UNB06.1 [0…1]
1/14 Recipient's reference or password XYZ
    UNB06.2 [0…1]
2/2

Recipient's reference or password qualifier.

Valid values:

  • BB – Password.
  • AA – Reference.
BB
  UNB07 [0…1]
1/14 Application reference. ORDERS
  UNB08 [0…1]
1/1 Processing priority code. –
  UNB09 [0…1]
1/1 Acknowledgment request. 1
  UNB10 [0…1]
1/35 Communication agreement ID. –
  UNB11 [0…1]
1/1 Test indicator. I
  UNH [1…*]
– Message header. –
    UNH01 [1…1]
1/14 Required.Message reference number. 000000101
    UNH02 [1…1]
– Required.Message Identifier. –
      UNH02.1 [1…1]
1/6 Required.Message type. DESADV
      UNH02.2 [1…1]
1/3 Required.Message version number. D
      UNH02.3 [1…1]
1/3 Required.Message release number. 96A
      UNH02.4 [1…1]
1/3

Controlling agency, coded.

The valid value is UN - UN/CEFACT.

UN
      UNH02.5 [0…1]
1/6 Association assigned code. –
      UNH02.6 [0…1]
1/6 Code list directory version number. –
      UNH02.7 [0…1]
1/6 Message type sub-function identification. –
    UNH03 [0…1]
1/35 Common access reference. –
  BGM [1…1]
– Required.Beginning of message. –
    BGM01 [0…1]
– Document or message name –
      BGM01.1 [0…1]
1/3 Document or message name, coded. The valid value is 351 - Dispatch Advice. 351
      BGM01.2 [0…1]
1/3 Code list qualifier. –
      BGM01.3 [0…1]
1/3 Code list responsible agency, coded. –
      BGM01.4 [0…1]
1/35 Document or message name –
    BGM02 [1…1]
1/35 Required.Document or message number –
      BGM02.1 [1…1]
1/70

Required.Document identifier.

Required to be populated with delivery number.

2738662
      BGM02.2 [0…1]
1/9 Version identifier. –
      BGM02.3 [0…1]
1/6 Revision identifier. –
    BGM03 [0…1]
1/3

Message function, coded If not populated.

Valid values:

  • 09 – Original.
  • 01 – Cancellation.
  • 04 – Change.
  • 05 – Replace.
  • 08 – Status.
  • 11 – Response.
  • 16 – Proposal.
9
    BGM04 [0…1]
1/3 Response type, coded.  
  DTM [1…1]
– Required.Date or time or period. DTM1.1 = 137
    DTM01.1 [1…1]
1/3

Required.Date or time or period function code qualifier.

Valid values:

  • 137 - Document issue date time.
  • 11 - Despatch date and or time. Required if DTM for despatch date and/or time populated.
  • 17- Delivery date/time, estimated. Required if DTM for estimated Delivery date/time populated.
  • 67 - Delivery date/time, current schedule Required if DTM for current scheduled delivery date/time populated.
137
    DTM01.2 [1…1]
1/35 Required.Date or time or period text 20220425054813125
    DTM01.3 [1…1]
1/3 Required.Date or time or period format code. the valid value is 304 - CCYYMMDDHHMMSSZZZ 304
  MEA [0…1]
– Measurements. MEA01 = CT
    MEA01 [1…1]
1/3

Required.Measurement purpose code qualifier.

Valid values:

  • CT - Counts. Required if MEA segment is populated.
  • AAX - Consignment measurements. Required if MEA segment populated forTotal Gross Weight, Tare weight or Actual net weight.
CT
    MEA02 [0…1]
– Measurement details. –
      MEA02.1 [0…1]
1/3

Measured attribute code.

Valid values:

  • AAD - Total gross weight
  • T - Tare weight
  • N - Actual net weight

Required if MEA segment populated for Total Gross Weight, Tare weight or Actual net weight.

–
      MEA02.2 [0…1]
1/3 Measurement significance code. –
      MEA02.3 [0…1]
1/17 Non-discrete measurement name code. –
      MEA02.4 [0…1]
1/70 Non-discrete measurement name. –
    MEA03 [1…1]
– Required. Value or range. Required if MEA segment populated for Counts. –
      MEA03.1 [1…1]
1/8

Required.Measurement unit code

Valid values:

  • PF - Pallet
  • PK - Package
  • CT - Carton
  • KGM - Kilogram
  • PN - Pound net
  • GRM - gram
  • MC - microgram
  • ME - milligram

Required if MEA segment populated for Counts, Total Gross Weight, Tare weight or Actual net weight.

PF
      MEA03.2 [1…1]
1/18

Required.Measure.

Required if MEA segment populated for Counts.

2
      MEA03.3 [0…1]
1/18 Range minimum quantityEdifact Decimal [8 or 8.0 or 0.5]. –
      MEA03.4 [0…1]
1/18 Range maximum quantityEdifact Decimal [8 or 8.0 or 0.5]. –
      MEA03.5 [0…1]
1/2 Significant digits quantityEdifact Decimal [8 or 8.0 or 0.5]. –
    MEA04 [0…1]
1/3 Surface or layer code. –
    RFF [0…1]
–

Reference.

Purchase order is required either at the header RFF segment or at the line level RFF segment.

RFF = ON
      RFF01 [1…1]
–

Required.Reference.

Required if RFF segment populated

 
        RFF01.1 [1…1]
1/3

Required.Reference code qualifier.

Valid vales:

  • ON -Order Number (purchase). If RFF segment populated, then RFF01.1 is required.
  • BM - Bill of lading number. Required if RFF segment populated for bill of lading.
  • AAM - Waybill number. Required if RFF segment populated for waybill number.
  • CN - Carrier's reference number. Required if RFF segment populated for carrier reference number.
  • MB - Master bill of lading number. Required if RFF segment populated for master bill of lading number.
  • SN - Transport equipment seal identifier. Required if RFF segment populated for transport equipment seal identifier.
  • VR - Vendor ID number. Required if RFF segment populated for vendor id number.
  • IV - Invoice document Identifier. Required if RFF segment populated for invoice document number.Invoice Number can be sent in Header or Detail RFF segment.
ON
        RFF01.2 [1…1]
1/70

Required. Reference identifier.

If purchase order populated at the header level RFF, then RFF01.2 is required.

Required if RFF segment populated for:

  • Bill of lading.
  • Waybill number.
  • Carrier reference number.
  • Master bill of lading number.
  • Transport equipment seal identifier.
  • Vendor id number.
  • Invoice document number.Invoice Number can be sent in Header or Detail RFF segment.
PO1098L11
        RFF01.3 [0…1]
1/6 Document line identifier. –
        RFF01.4 [0…1]
1/9 Version identifier. –
        RFF01.5 [0…1]
1/6 Revision identifier. –
      DTM [0…1]
– Date or time or period. DTM1.1 = 171
        DTM01.1 [1…1]
1/3

Required.Date or time or period function code qualifier. The valid value is 171 - Reference date.

Required if DTM segment populated for purchase order date.

171
        DTM01.2 [1…1]
1/35 Required.Date or time or period text Required if DTM segment populated for purchase order date. 20240430
        DTM01.3 [1…1]
1/3

Required.Date or time or period format code.

The valid value is 102 - CCYYMMDD.

Required if DTM segment populated for purchase order date.

102
    NAD [0…1]
– Name and address. NAD01 = MF
      NAD01 [1…1]
1/3

Required.Party function code qualifier.

  • MF- Manufacturer of goods
  • BY- Buyer
  • ST- Ship To Party
  • BT - Party to be billed for other than freight (bill to)
  • SU - Supplier
  • SF - Ship from
  • CA - Carrier
MF
      NAD02 [1…1]
– Required.Party identification details. –
        NAD02.1 [1…1]
1/35

Required.Party identifier.

Required. Required if NAD segment for manufacturer party populated.

MF654984
        NAD02.2 [0…1]
1/17 Code list identification code. –
        NAD02.3 [1…1]
1/3

Required.Code list responsible agency code.

Valid values:

  • 9 – GS1 (GLN n13) Required if NAD segment for manufacturer party populated.
  • 16 – US, D&B (Dun & Bradstreet Corporation).
  • 164 – US, DEA (Drug Enforcement Agency).
  • 91 – Assigned by seller or seller's agent.
  • 92 – Assigned by buyer or buyer's agent.
  • 237 – US, United States health industry .
91
      NAD03 [0…1]
– Name and address. –
        NAD03.1 [1…1]
1/35 Required.Name and address description. –
        NAD03.2 [0…1]
1/35 Name and address description. –
        NAD03.3 [0…1]
1/35 Name and address description. –
        NAD03.4 [0…1]
1/35 Name and address description. –
        NAD03.5 [0…1]
1/35 Name and address description –
      NAD04 [1…1]
– Required.Party name. –
        NAD04.1 [1…1]
1/70 Required.Party name Required if buyer party contact name is populated. Wholesale Inc
        NAD04.2 [0…1]
1/70 Party name. –
        NAD04.3 [0…1]
1/70 Party name. –
        NAD04.4 [0…1]
1/70 Party name. –
        NAD04.5 [0…1]
1/70 Party name. –
        NAD04.6 [0…1]
1/3 Party name format code. –
      NAD05 [0…1]
– Street. –
        NAD05.1 [1…1]
1/256 Required.Street and number or post office box identifier. 555 Neelan Road
        NAD05.2 [0…1]
1/256 Street and number or post office box identifier. Suite 123
        NAD05.3 [0…1]
1/256 Street and number or post office box identifier. –
        NAD05.4 [0…1]
1/256 Street and number or post office box identifier. –
      NAD06 [0…1]
1/35 City name. Sacramento
      NAD07 [0…1]
– Country subdivision details. –
        NAD07.1 [0…1]
1/9 Country subdivision identifier. –
        NAD07.2 [0…1]
1/17 Code list identification code. –
        NAD07.3 [0…1]
1/3 Code list responsible agency code. –
        NAD07.4 [0…1]
1/70 Country subdivision name. –
      NAD08 [0…1]
1/17 Postal identification code. 95833
      NAD09 [0…1]
1/3 Country identifier. US
      CTA [0…1]
– Contact information. CO
        CTA01 [1…1]
1/3

Required.Contact function code

  • CO - Consignor. Required if manufacturer party contact telephone and/or email populated.
  • CN - Consignee. Required if buyer party contact telephone and/or email is populated.
  • PE - Payer contact.Required if bill to party contact telephone and/or email populated.
  • CA - Carrier.Required if carrier party contact telephone and/or email populated.
CO
        CTA02 [0…1]
– Contact details. –
          CTA02.1 [0…1]
1/17 Contact identifier. –
          CTA02.2 [0…1]
1/256

Contact name.

Required if manufacturer party contact name is populated.

–
        COM (1) [0…1]
– Communication contact. COM01.2 = TE
          COM01 [1…1]
– Required.Communication contact. –
            COM01.1 [1…1]
1/512

Required. Communication address identifier.

Required if manufacturer party contact telephone number populated.

07911 123456
            COM01.2 [1…1]
1/3

Required.Communication means type code.

Valid values:

  • TE - Telephone
  • EM - Electronic email
TE
  TDT [0…10]
– Transport information. –
    TDT01 [1…1]
1/3

Required.Transport stage code qualifier. The valid value is 12 - At departure.

Required if TDT segment populated for transport information.

12
    TDT02 [0…1]
1/17 Means of transport journey identifier. –
    TDT03 [0…1]
– Mode of transport. –
      TDT03.1 [0…1]
1/3 Transport mode name code. –
      TDT03.2 [0…1]
1/17 Transport mode name. –
    TDT04 [0…1]
– Transport means. –
      TDT04.1 [0…1]
1/8

Transport means description code.

Valid values:

  • 6 - Aircraft
  • 11 - Ship
  • 25 - Rail Express
  • 31 - Truck
–
      TDT04.2 [0…1]
1/17 Code list identification code. –
      TDT04.3 [0…1]
1/3 Code list responsible agency code. –
      TDT04.4 [0…1]
1/17 Transport means description. –
    TDT05 [0…1]
– Carrier. –
      TDT05.1 [0…1]
1/17 Carrier identifier. B752
      TDT05.2 [0…1]
1/17 Code list identification code. –
      TDT05.3 [0…1]
1/3 Code list responsible agency code. The valid value is 182 - US, Standard Carrier Alpha Code (Motor). 182
      TDT05.4 [0…1]
1/35 Carrier name. –
    TDT06 [0…1]
1/3 Transit direction indicator code. Valid Values: SD - Seller to drop ship designated location.ae SD
    TDT07 [0…1]
– Excess transportation information. –
      TDT07.1 [1…1]
1/3 Required.Excess transportation reason code. –
      TDT07.2 [1…1]
1/3 Required.Excess transportation responsibility code. –
      TDT07.3 [0…1]
1/17 Customer shipment authorization identifier. –
    TDT08 [0…1]
– Transport identification. –
      TDT08.1 [0…1]
1/35 Transport means identification name identifier. –
      TDT08.2 [0…1]
1/17 Code list identification code. –
      TDT08.3 [0…1]
1/3 Code list responsible agency code. –
      TDT08.4 [0…1]
1/70 Transport means identification name. –
      TDT08.5 [0…1]
1/3 Transport means nationality code. –
    TDT09 [0…1]
1/3 Transport means ownership indicator code. –
    TDT10 [0…1]
– Power type. –
      TDT10.1 [0…1]
1/3 Power type code. –
      TDT10.2 [0…1]
1/17 Code list identification code. –
      TDT10.3 [0…1]
1/3 Code list responsible agency code. –
      TDT10.4 [0…1]
1/17 Power type description. –
    TDT11 [0…1]
– Transport service. –
      TDT11.1 [0…1]
1/17 Transport service identification code. –
      TDT11.2 [0…1]
1/17 Code list identification code. –
      TDT11.3 [0…1]
1/3 Code list responsible agency code. –
      TDT11.4 [0…1]
1/35 Transport service name. –
      TDT11.5 [0…1]
1/256 Transport service description. –
  EQD [0…10]
– Equipment details. –
    EQD01 [1…1]
1/3

Required.Equipment type code qualifier.

Valid values:

  • CN - Container
  • RR - Rail Car
  • TE - Trailer

Required if EQD segment populated for equipment details.

RR
    EQD02 [0…1]
– Equipment identification. –
      EQD02.1 [0…1]
1/17 Equipment identifier. RR18598
      EQD02.2 [0…1]
1/17 Code list identification code. –
      EQD02.3 [0…1]
1/3 Code list responsible agency code. –
      EQD02.4 [0…1]
1/3 Country identifier. –
    EQD03 [0…1]
  Equipment size and type. –
      EQD03.1 [0…1]
1/10 Equipment size and type description code. –
      EQD03.2 [0…1]
1/17 Code list identification code. –
      EQD03.3 [0…1]
1/3 Code list responsible agency code. –
      EQD03.4 [0…1]
1/35 Equipment size and type description. –
    EQD04 [0…1]
1/3 Equipment supplier code. –
    EQD05 [0…1]
1/3 Equipment status code. –
    EQD06 [0…1]
1/3 Full or empty indicator code. –
    EQD07 [0…1]
1/3 Marking instructions code. –
    CPS [1…9999]
–

Consignment packing sequence.

A segment identifying the sequence in which packaging of the consignment occurs, e.g. boxes loaded onto a pallet.

  • CPS01 = 1 - represents the Shipment Level in the aggregation. Loose Items or no packaging aggregation will contain a single CPS followed by one or more LIN segments. The first CPS if contains a PAC segment would be to represent the total number of logical containers.
  • CPS01 > 1 - represents an aggregated container. Standard packaging Aggregation the first CPS segment will be followed by one or more additional CPS segments that contains a PAC & PCI segment . PAC segment is used to identify the container quantity. PCI segment is used to identify the container identifier.
–
      CPS01 [1…1]
1/35 Required.Hierarchical structure level identifier. 1
      CPS02 [1…1]
1/35

Required.Hierarchical structure parent identifier.

Not populated for first CPS since shipment has no parent.

–
      CPS03 [0…1]
1/3

Packaging level code

Valid values:

  • 1 - Inner
  • 2 - Intermediate
  • 3 - Outer
  • 4 - No packaging hierarchy
  • 5 - Shipment Level
  • 6 - Highest
–
      PAC [0…9999]
–

Package.

PAC segment is required if an aggregated packaging structure populated.

Pallet - case - item is an example of a aggregated packing structure. A shipment that only contains items and no packaging containers (ie pallets case, pack) would be a non-aggregated packing structure.

–
        PAC01 [0…1]
0/8

Package quantity.

Format: EDIFACT Decimal [8 or 8.0 or 0.8]

–
        PAC02 [0…1]
– Packaging details. –
          PAC02.1 [0…1]
1/3

Packaging level code

Valid values:

  • 1 - Inner
  • 2 - Intermediate
  • 3 - Outer
  • 4 - No packaging hierarchy
  • 5 - Shipment Level
  • 6 - Highest
–
          PAC02.2 [0…1]
1/3 Packaging related description code. –
          PAC02.3 [0…1]
1/3 Packaging terms and conditions code. –
        PAC03 [1…1]
– Required.Package type. –
          PAC03.1 [1…1]
1/17

Required.Package type description code.

  • PALLET
  • CARTON
  • INNERPACK

If PAC segment populated for an aggregated packaging structure, then PAC03.1 is required.

PALLET
          PAC03.2 [0…1]
1/17 Code list identification code. –
          PAC03.3 [0…1]
1/3 Code list responsible agency code. –
          PAC03.4 [0…1]
1/35 Type of packages. –
        PAC04 [0…1]
– Package type identification. –
          PAC04.1 [1…1]
1/3 Required.Description format code. –
          PAC04.2 [1…1]
1/35 Required.Type of packages. –
          PAC04.3 [0…1]
1/3 Item type identification code. –
          PAC04.4 [0…1]
1/35 Type of packages. –
          PAC04.5 [0…1]
1/3 Item type identification code. –
        PAC05 [0…1]
– Returnable package details. –
          PAC05.1 [0…1]
1/3 Returnable package freight payment responsibility code. –
          PAC05.2 [0…1]
1/3 Returnable package load contents code. –
        MEA – –

Measurements.

MEA segment required if package length, width, and/or height dimensions are populated.

–
          MEA01 [1…1]
1/3

Required.Measurement purpose code qualifier.

The valid value is AAY - Package measurement.

Required if MEA segment populated for package length, width, and/or height dimensions.

AAY
          MEA02 [1…1]
– Required.Measurement details. –
            MEA02.1 [1…1]
1/3

Required.Measured attribute code.

  • LN - Length
  • WD - Width dimension
  • HT - Height dimension

Required if MEA segment populated for package length, width, and/or height dimensions.

LN
            MEA02.2 [0…1]
1/3 Measurement significance code. –
            MEA02.3 [0…1]
1/17 Non-discrete measurement name code. –
            MEA02.4 [0…1]
1/70 Non-discrete measurement name. –
          MEA03 [1…1]
– Required.Value or range. –
            MEA03.1 [1…1]
1/8

Required.Measurement unit code.

  • FOT - Foot
  • INH - Inch
  • MMT - Millimeter
  • MTR - Meter

Required if MEA segment populated for package length, width, and/or height dimensions.

MMT
            MEA03.2 [1…1]
1/18 Required.Measure Required if MEA segment populated for package length, width, and/or height dimensions. 150
            MEA03.3 [0…1]
1/18

Range minimum quantity.

Edifact Decimal [8 or 8.0 or 0.5]

–
            MEA03.4 [0…1]
1/18

Range maximum quantity.

Edifact Decimal [8 or 8.0 or 0.5]

–
            MEA03.5 [0…1]
1/2

Significant digits quantity.

Edifact Decimal [8 or 8.0 or 0.5]

–
          MEA04 [0…1]
1/3 Surface or layer code. –
        PCI [0…1]
–

Package identification.

Segment is required if an aggregated packaging structure populated.

PCI01 = 24
          PCI01 [1…1]
–

Required.Marking instructions code.

The valid value is 24 - Shipper Assigned.

Required if aggregated packaging structure populated.

24
          PCI02 [0…1]
– Marks and labels. –
            PCI02.1 [1…1]
– Required.Shipping marks description. –
            PCI02.2 [0…1]
– Shipping marks description. –
            PCI02.3 [0…1]
– Shipping marks description. –
            PCI02.4 [0…1]
– Shipping marks description. –
            PCI02.5 [0…1]
– Shipping marks description. –
            PCI02.6 [0…1]
– Shipping marks description. –
            PCI02.7 [0…1]
– Shipping marks description. –
            PCI02.8 [0…1]
– Shipping marks description. –
            PCI02.9 [0…1]
– Shipping marks description. –
            PCI02.10 [0…1]
– Shipping marks description. –
          PCI03 [0…1]
– Full or empty indicator code. –
          PCI04 [0…1]
– Type of marking. –
            PCI04.1 [1…1]
– Required.Marking type code. –
            PCI04.2 [0…1]
– Code list identification code. –
            PCI04.3 [0…1]
– Code list responsible agency code. –
          GIN [0…99]
–

Goods identity number.

Segment is required if an aggregated packaging structure populated.

GIN01 = BJ
            GIN01 [1…1]
–

Required.Object identification code qualifier.

The valid value is BJ - Serial shipping container code.

Required if aggregated packaging structure populated.

BJ
            GIN02 [1…1]
– Required.Identity number range. –
              GIN02.1 [1…1]
–

Required.Object identifier.

Required if aggregated packaging structure populated.

00881787875498
              GIN02.2 [0…1]
– Object identifier. ZZ20015
      LIN [1…9999]
– Line item. –
        LIN01 [1…1]
1/6 Required.Line item identifier. 1
        LIN02 0…1 1/3 Action code. –
        LIN03 [1…1]
– Required.Item number identification. –
          LIN03.1 [1…1]
1/35 Required.Item identifier. 100021
          LIN03.2 [1…1]
1/3

Required.Item type identification code.

ClosedValid values:
  • BP - Buyer number
  • EN - EAN number
  • IN - Buyer item number
  • MF - Manufacturer number
  • BC - NDC442
  • BD - NDC532
  • BE - NDC541
  • BF - NDC542
  • SK - SKU
  • UA - Case UPC
  • AH - Package UPC
  • SRV - GTIN14
  • UP - UPC
  • VN - Vendor Number.
VN
          LIN03.3 [0…1]
1/17 Code list identification code. –
          LIN03.4 [0…1]
1/3 Code list responsible agency code. –
        LIN04 [0…1]
– Sub-line information. –
          LIN04.1 [0…1]
1/3 Sub-line indicator code. –
          LIN04.2 [0…1]
1/6 Line item identifier. –
        LIN05 [0…1]
0/2

Configuration level number.

Format: EDIFACT Decimal [8 or 8.0 or 0.8]

–
        LIN06 [0…1]
1/3 Configuration operation code. –
        PIA [0…10]
–

Additional product ID.

Lot Number mapping to packagingAggregation.

PIA01 = 1
          PIA01 [1…1]
1/3

Required.Product identifier code qualifier.

The valid value is 1 - additional information.

Required to provide additional product identifiers and/or Lot number.

–
          PIA02 [1…1]
– Required.Item number identification. –
            PIA02.1 [1…1]
1/35

Required.Item identifier.

Required if PIA segment populated for additional product information.

LOTABC
            PIA02.2 [1…1]
1/3

Required.Item type identification code.

ClosedValid values:
  • BB - Lot Number
  • BP - Buyer's part number
  • EN - International Article Numbering Association (EAN)
  • IN - Buyer's item number
  • MF - Manufacturer's (producer's) article number
  • BC - National drug code 4-4-2 format
  • BD - National drug code 5-3-2 format
  • BE - National drug code 5-4-1 format
  • BF - National drug code 5-4-2 format
  • SK - Stock keeping unit (SKU)
  • UA - Universal product code (UPC)
  • AH - Universal Product Code (UPC) Consumer package code (1-5-5)
  • SRV - GTIN UP - Universal product code (UPC)
  • VN - Vendor item number

Required if PIA segment populated for additional product information.

BB
            PIA02.3 [0…1]
1/17 Code list identification code. –
            PIA02.4 [0…1]
1/3 Code list responsible agency code. –
        IMD [0…99]
– Item description. IMD01 = F
          IMD01 [1…1]
1/3

Required.Description format code

The valid value is F - Free form.

Required if IMD segment populated for product description.

F
          IMD02 [1…1]
– Required.Item characteristic. –
            IMD02.1 [1…1]
1/3

Required.Item characteristic code

The valid value is 8 - Product.

Required if IMD segment populated for product description.

8
            IMD02.2 [0…1]
1/17 Code list identification code. –
            IMD02.3 [0…1]
1/3 Code list responsible agency code. –
          IMD03 [0…1]
– Item description. –
            IMD03.1 [0…1]
1/17 Item description code. –
            IMD03.2 [0…1]
1/17 Code list identification code. –
            IMD03.3 [0…1]
1/3 Code list responsible agency code. –
            IMD03.4 [1…1]
1/256

Required.Item description.

Required if IMD segment populated for product description.

Product ABC
            IMD03.5 [0…1]
1/256 Item description. –
            IMD03.6 [0…1]
1/3 Language name code. –
          IMD04 [0…1]
1/3 Surface or layer code. –
        MEA [0…5]
– Measurements. MEA01 = AAX
          MEA01 [1…1]
1/3

Required.Measurement purpose code qualifier.

The valid value is AAX - Consignment measurements.

Required if MEA segment populated for item gross weight and/or net weight.

AAX
          MEA02 [1…1]
– Required.Measurement details. –
            MEA02.1 [1…1]
1/3

Required.Measured attribute code.

Valid values:

  • AAD - Total gross weight
  • T - Tare weight
  • N - actual net weight
  • ABJ - Volume

Required if MEA segment populated for item gross weight and/or net weight.

AAD
            MEA02.2 [0…1]
1/3 Measurement significance code. –
            MEA02.3 [0…1]
1/17 Non-discrete measurement name code. –
            MEA02.4 [0…1]
1/70 Non-discrete measurement name. –
          MEA03 [1…1]
– Required.Value or range. –
            MEA03.1 [1…1]
1/8

Required.Measurement unit code

Valid values:

  • KGM - Kilogram
  • PN - Pound net
  • GRM - Gram
  • MC - Microgram
  • ME - Milligram
  • OZ - Ounce
  • GLI - Gallon
  • PTI - Pint
  • QTI - Quart

Required if MEA segment populated for item gross weight and/or net weight or item volume.

KGM
            MEA03.2 [1…1]
1/18

Required.Measure.

Required if MEA segment populated for item gross weight and/or net weight.

150
            MEA03.3 [0…1]
1/18

Range minimum quantity.

Edifact Decimal [8 or 8.0 or 0.5]

–
            MEA03.4 [0…1]
1/18

Range maximum quantity.

Edifact Decimal [8 or 8.0 or 0.5]

–
            MEA03.5 [0…1]
1/2

Significant digits quantity.

Edifact Decimal [8 or 8.0 or 0.5]

–
          MEA04 [0…1]
1/3 Surface or layer code. –
        QTY [1…10]
– Quantity. QTY01.1 = 12
          QTY01 [1…1]
– Required.Quantity details. –
            QTY01.1 [1…1]
–

Required.Quantity type code qualifier.

Valid values:

  • 12 - Dispatch quantity
  • 21- Ordered quantity
  • 131 - Quantity delivered
12
            QTY01.2 [1…1]
– Required.Quantity. 24.000
            QTY01.3 [1…1]
–

Required.Measurement unit code.

Closed.Valid values
  • 02 – Statute Mile
  • 4G – Microliter
  • AM – Ampoule
  • AV – Capsule
  • BD – Bundle
  • BG – Bag
  • BO – Bottle
  • BX – Box
  • C3 – Centiliter
  • CA – Case
  • CC – Cubic Centimeter
  • CF – Cubic Feet
  • CG – Card, Blister
  • CI – Cubic Inches
  • CL – Cylinder
  • CM – Centimeter
  • CN – Can
  • CP – Crate
  • CQ – Cartridge
  • CR – Cubic Meters
  • CT – Carton
  • DA – Day
  • DI – Dispenser
  • DK – Kilometers
  • DL – Deciliter
  • DM – Decimeter
  • DR – Drum
  • DS – Display
  • DZ – Dozen
  • EA – Each
  • FO – Fluid Ounce
  • FT – Foot
  • GA – Gallon
  • GL – Gram/liter
  • GR – Gram
  • GS – Gross
  • H4 – Hectoliter
  • HF – Hundred Feet
  • HR – Hours
  • IN – Inch
  • K6 – Kiloliters
  • KG – Kilogram
  • KT – Kit
  • LB – Pounds
  • LF – Linear Foot
  • LO – Lot (unit of procurement)
  • LT – Liter
  • LY – Linear Yard
  • MC – Microgram
  • ME – Milligram
  • ML – Milliliter
  • MM – Millimeter
  • MO – Months
  • MR – Meter
  • OZ – Ounces
  • PC – Piece
  • PF – Pallet
  • PK – Package
  • PR – Pair
  • PT – Pint
  • QT – Quart
  • RL – Roll
  • SC – Square Centimeter
  • SF – Square Foot
  • SH – Sheet
  • SI – Square Inch
  • SM – Square Meter
  • ST – Set
  • SY – Square Yard
  • T3 – Thousand Pieces
  • TB – Tube
  • TH – Thousand
  • TY – Tray
  • U2 – Tablet
  • UM – Million
  • UN – Unit
  • V2 – Pouch
  • VI – Vial
  • WK – Week
  • YD – Yard
  • YR – Years
EA
        DTM [0…10]
– Date or time or period. DTM1.1 = 36
            DTM01.1 [1…1]
1/3

Required.Date or time or period function code qualifier.

The valid value is 36 - Expiry date.

Required if DTM segment populated for product expiration date.

36
            DTM01.2 [1…1]
1/35

Required.Date or time or period text.

Required if DTM segment populated for product expiration date.

20220425054813125
            DTM01.3 [1…1]
1/3

Required.Date or time or period format code,

The valid value 304 - CCYYMMDDHHMMSSZZZ .

Required if DTM segment populated for product expiration date.

304
        RFF [1…1]
–

Required.Reference.

Required In either Header or Detail RFF segment.

RFF = ON
          RFF01 [1…1]
– Required.Reference. –
            RFF01.1 [1…1]
1/3

Required.Reference code qualifier.

The valid value is ON -Order Number (purchase).

Required if RFF segment populated for purchase order number.

ON
            RFF01.2 [1…1]
1/70

Required.Reference identifier.

Required if RFF segment populated for purchase order number.

PO1098L11
            RFF01.3 [0…1]
1/6 Document line identifier. –
            RFF01.4 [0…1]
1/9 Version identifier. –
            RFF01.5 [0…1]
1/6 Revision identifier. –
          DTM [0…1]
–

Date or time or period.

Recommended for purchase order date.

DTM1.1 = 171
            DTM01.1 [1…1]
1/3

Required.Date or time or period function code qualifier.

The valid value 171 - Reference date.

Required if DTM segment populated for purchase order date.

171
            DTM01.2 [1…1]
1/35

Required.Date or time or period text.

Required if DTM segment populated for purchase order date.

20240430
            DTM01.3 [1…1]
1/3

Required.Date or time or period format code. The valid value is 102 - CCYYMMDD.

Required if DTM segment populated for purchase order date.

102
UNT [1…*]
– UNT Message Trailer(UNH…UNT transaction). –
  UNT01 [1…1]
1/14 Required.Number of segments in a message, starting with UNH and ending with UNT. 45
  UNT02 [1…1]
1/14 Required.Message reference number. 1
UNZ [1…1]
– Required.UNB… UNZ interchange control trailer envelope. Only one interchange expected per transmission. –
  UNZ01 [1…1]
1/5 Required.Interchange control count. 1
  UNZ02 [1…1]
1/14 Required.Interchange control reference. 3
ClosedExample
UNB+UNOA:2+055762322IV:2+8715865000059:14+051217:1649+00000000000058+XYZ:DD+UB99S++1++I'
UNH+00000000000039+DESADV:D:96A:UN'
BGM+351+DES587441+9'
DTM+137:20220425054813125:304'
DTM+11:20020403051132112:304'
DTM+17:200204030917061255349:304'
DTM+67:20240915081534112:304'
MEA+CT++PF:1'
MEA+AAX+AAD+KGM:50'
MEA+AAX+T+PN:55'
MEA+AAX+N+OZ:63'
MEA+AAX+AAD+GRM:60'
RFF+ON:PO108981'
DTM+171:20240915081534112:102'
RFF+BM:BOL1567'
RFF+AAM:WY59783'
RFF+CN:767380001'
RFF+MB:MB5787'
RFF+SN:SEAL0015'
RFF+VR:VEND87981'
RFF+IV:INV78787875'
DTM+171:20240515:102'
NAD+MF+5411234512309::91++MANU+MF--123 Street:Address2+City++Postal+AO'
CTA+CO+:Jane Doe2'
COM+MFBN-07911 123456:TE'
COM+MFBN-JaneDoe@domain.com:EM'
NAD+BY+BY11234512309::92++BUYER+BY-123 Street:Address2+City++Postal+JO'
CTA+CN+:Jane Doe'
COM+BYCN-07911 123456:TE'
COM+BYCN-JaneDoe@domain.com:EM'
NAD+ST+ST11234512309::9++SHIPTO+123 Street:Address2+City++Postal+US'
CTA+CN+:Jane Doe'
COM+STCN-07911 123456:TE'
COM+STCN-JaneDoe@domain.com:EM'
NAD+BT+BT11234512309::237++BILLTO+BT-123 Street:Address2+City++Postal+IQ'
CTA+PE+:Jane Doe'
COM+BTPE-07911 123456:TE'
COM+BTPE-JaneDoe@domain.com:EM'
NAD+SU+SU11234512309::16++SUPP+SU-123 Street:Address2+City++Postal+BZ'
CTA+CO+:Jane Doe'
COM+SUCO-07911 123456:TE'
COM+SUCO-JaneDoe@domain.com:EM'
NAD+SF+SF11234512309::164++SFROM+SF-123 Street:Address2+City++Postal+CL'
CTA+CO+:Jane Doe'
COM+SFCO-07911 123456:TE'
COM+SFCO-JaneDoe@domain.com:EM'
NAD+CA+CA11234512309::9++CARR1+CA1-123 Street:Address2+City++Postal+GH'
CTA+CA+:Jane Doe1'
COM+CACA-07911 123456:TE'
COM+CACA-JaneDoe@domain.com:EM'
TDT+12+++1+B752::182:Acme Trucking+SD'
EQD+RR+RAIL1596878'
CPS+1'
PAC+2++PALLET::9'
CPS+2+1'
PAC+2++PALLET::9'
MEA+AAY+LN+MMT:1254.2'
MEA+AAY+HT+MMT:12504.11'
MEA+AAY+WD+MMT:100'
PCI'
GIN+BJ+00881787875498:ZZ20015'
LIN+1++5410738000166:VN'
PIA+1+LOT-LOOSE1:BB'
PIA+1+IN5410738000166:IN'
PIA+1+EN5410738000166:EN'
PIA+1+MF5410738000166:VN'
IMD+F+8+:::Loose item 1 description'
MEA+AAX+AAD+ME:150'
MEA+AAX+ABJ+QTI:125'
QTY+12:45:BX'
QTY+131:125:MO'
DTM+36:20250401054813125:304'
RFF+ON:PO108981'
DTM+171:20250405:102'
RFF+IV:IV108981'
DTM+171:20250506:102'
CPS+3+2'
PAC+2++CARTON::9'
MEA+AAY+LN+MTR:2254.2'
MEA+AAY+HT+MTR:22504.11'
MEA+AAY+WD+MTR:200'
PCI'
GIN+BJ+00881787875411:ZZ20011'
LIN+4++IN5410738000166:IN'
PIA+1+LOT-LOOSE4:BB'
PIA+1+AH5410738000166:AH'
PIA+1+SRV5410738000166:SRV'
PIA+1+UP5410738000166:UP'
IMD+F+8+:::Loose item 4 description'
MEA+AAX+ABJ+OZ:25'
MEA+AAX+N+GRM:111'
QTY+12:245:BG'
QTY+21:424:BO'
DTM+36:20250901054813125:304'
RFF+ON:PO108984'
DTM+171:20270405:102'
RFF+IV:IV108984'
DTM+171:20241106:102'
CNT+2:4'
UNT+103+00000000000039'
UNZ+1+00000000000058'
Review TraceLink's API: Terms of Use

Table of contents

Related Content
Related content
Advance ship notice (X12)
Shipment notices allow companies to exchange serialized data for sales shipments with upstream and downstream supply chain trade partners without giving these trade partners access to their serialization system of record.
View More
Related content
Advance ship notice (XML)
Shipment notices allow companies to exchange serialized data for sales shipments with upstream and downstream supply chain trade partners without giving these trade partners access to their serialization system of record.
View More
Related content
Advance ship notice (IDoc)
Shipment notices allow companies to exchange serialized data for sales shipments with upstream and downstream supply chain trade partners without giving these trade partners access to their serialization system of record.
View More
Related content
Advance shipment notices
Advance shipment notices can be used to inform their Partners of the contents of a shipment, and the notices also allow these companies to comply with government regulations or recommendations for sharing serialized data about shipments.
View More
Related content
Purchase orders
Owners and their Partners search for and view, and create purchase orders (POs) that are exchanged with Partners asynchronously.
View More

Cookie Settings

When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies or similar tracking technologies. Please see below for an overview of the categories of cookies and similar technologies used on this site. You can allow or deny some of all of them, except Strictly Necessary Cookies which are required to provide the site to you. However, blocking some types of cookies may impact your experience of the site and services we are able to offer.

Please see our Cookie Policy for more details, including a list of the cookies we use. You can change your consent options at any time by following the “Cookie Settings” link in the Cookie Policy.
'Strictly Necessary' cookies let you move around the Site and use essential features like secure areas, shopping baskets and online billing. Without these cookies you would not be able to navigate between pages or use certain vital features of our Site, so we do not require your consent for their use. These cookies don't gather any information about you that could be used for marketing or remembering where you've been on the internet. For example, we use these Strictly Necessary cookies to identify you as being logged in to the Site. You can set your browser to block or alert you about these cookies, but if you do so, some parts of the Site will not work.
'Performance' cookies collect information about how you use the Site, such as which pages you visit, the time spent on the Site and if you experience any errors. We use performance cookies to provide aggregated statistics on how the Site is used and help us improve the Site including by measuring any errors that occur.
'Functional' cookies are used to provide services or to remember settings to improve your visit. We use 'Functionality' cookies to remember your settings and choices and show you when you're logged in to the Site.
‘Targeting' cookies are linked to services provided by third parties, such as 'Like' buttons and 'Share' buttons. The third party provides these services in return for recognizing that you have visited the Site. We also use 'Targeting' cookies to gather information that could be used to display content that we think may interest you.

Footer

  • Quick Links
    Get a Demo
    TraceLink Network Directory
    The Network
    OPUS Platform
    Technical Support
    Open Jobs
    API: Terms of Use
  • Products
    Multienterprise Information Network Tower
    U.S. DSCSA Compliance
    Targeted Recalls
    Process Orchestration for Empowered Teams
    Serialization
    Global Compliance
  • Resources
    Resource Center
    Events
    TraceLink University
    Partners
    Community
  • About TraceLink
    Our Story
    Newsroom
    Culture & Careers
    Leadership
    Our Values
    Corporate Social Responsibility
  • Hot Topics
    Transaction Integration
    Supply Chain Visibility
    DSCSA Compliance
    Process Orchestration
    Kazakhstan Compliance for Pharmaceuticals
    Kyrgyzstan Compliance for Pharmaceuticals
Follow Us on Social
Facebook
Linkedin
X
Legal & Trust.
© TraceLink Inc. 2009-2026 All Rights Reserved
Contact Us Today
Contact us today to begin your journey toward agentic supply chain orchestration — digitalize your end-to-end supply chain with intelligence, flexibility, and collaborative orchestration.
Contact Us
Stay Up-to-Date
Subscribe to receive industry insights and stay at the forefront of evolving trends.
Subscribe