DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 1 September 12, 2023

856 Ship Notice/Manifest

Functional Group=SH

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set

(856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a

shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical

characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction

set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to

convey information.The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or

shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the

contents of a shipment or information about the contents of a shipment.

DLMS Note:

1. Organizations use this transaction set to provide shipment status information, lateral redistribution shipment status information, or pseudo

shipment status information on all shipped orders. Use a single occurrence of this transaction set to transmit a single requisition-level

shipment status to a single organization.

a. This transaction may be used to provide passive Radio Frequency Identification (RFID) tag identification as applicable to interior and

exterior packaging.

b. Users operating under the Defense Logistics Management Standards (DLMS) must reference DoD/ASC X12 Conversion Guides for Unit

of Materiel Measure, Type of Pack and Transportation Method/Type Code, which can be found on the Defense Enterprise Data Standards

Office (DEDSO) Website at www.dla.mil/does/DLMS. For Army Total Package Fielding (TPF), Unit Materiel Fielding Points and staging sites

use this transaction set to acknowledge, to the Fielding Command, shipment of the packages.

2. The following introductory notes are applicable to the contents of this DLMS Implementation Convention (IC) . Cross-references to these

notes appear throughout this document to clarify relevant data requirements; however, absence of such a note does not explicitly mean that

none are applicable.

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system.

DLMS procedures may not have been developed. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be received or

understood by the recipient's automated processing system. Components must implement in accordance with the approved change

implementation schedule or coordinate implementation with DEDSO prior to use.

c. Legacy MILSTRIP data which must be retained in the DLMS for a transition period to support transaction conversion in a mixed

MILSTRIP/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components may coordinate

with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment.

d. Data elements which have an expanded files size above existing legacy MILSTRIP capability which may not be supported by the

recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

e. Data required to accommodate Component-unique transaction requirements (ex. C or B-series transactions). Data does not apply to

legacy MILSTRIP transactions.

f. Data associated with a DLMS enhancement authorized for implementation by modernized systems under DLMS migration. This data

should be adopted during, or subsequent, to modernization when applicable to the Component’s business process. Prior coordination is not

required. Components should ensure that inclusion of this data in a DLMS transaction does not cause inappropriate rejection of the

transaction.

g. Repetition of data (using multiple iterations or loops) which is not compatible with existing legacy MILSTRIP capability. Although

supported by the use of the ANSI X12 standard, such data is not compatible with MILSTRIP/DLMS conversion and may not be supported by

the recipient's automated processing system. Components must coordinate implementation of enhanced capability with DEDSO prior to use.

3. Effective April 1, 2014, refer to ADC 1075.Users must reference the GENC Standard for country codes

(https://nsgreg.nga.mil/overview.jsp) for a listing of authorized values. Under DLMS, use the GENC Digraph (two-character) code values.

4. This transaction may be used to provide item unique identification (IUID) information in accordance with DLMS procedures and OSD

Supply Policy. Refer to the item unique identification (IUID) web at URL: http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy.

5. This revision to the DLMS IC incorporates Proposed DLMS Changes (PDC) and Approved DLMS Change (ADC) listed. PDCs and ADCs

are available from the DEDSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

- ADC 55, Revision to DLMS Supplement (DS) 856S, Shipment Status

- ADC 127, UID of Items and RFID in DLMS Shipment Status

1. Organizations use this transaction set to provide shipment status information, lateral redistribution shipment status information, or pseudo

shipment status information on all shipped orders. Use a single occurrence of this transaction set to transmit a single requisition-level

shipment status to a single organization.

a. This transaction may be used to provide passive Radio Frequency Identification (RFID) tag identification as applicable to interior and

exterior packaging.

b. Users operating under the Defense Logistics Management Standards (DLMS) must reference DoD/ASC X12 Conversion Guides for Unit

of Materiel Measure, Type of Pack and Transportation Method/Type Code, which can be found on the Defense Enterprise Data Standards

Office (DEDSO) Website at www.dla.mil/does/DLMS. For Army Total Package Fielding (TPF), Unit Materiel Fielding Points and staging sites

use this transaction set to acknowledge, to the Fielding Command, shipment of the packages.

2. The following introductory notes are applicable to the contents of this DLMS Implementation Convention (IC) . Cross-references to these

notes appear throughout this document to clarify relevant data requirements; however, absence of such a note does not explicitly mean that

none are applicable.

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system.

DLMS procedures may not have been developed. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be received or

understood by the recipient's automated processing system. Components must implement in accordance with the approved change

implementation schedule or coordinate implementation with DEDSO prior to use.

c. Legacy MILSTRIP data which must be retained in the DLMS for a transition period to support transaction conversion in a mixed

MILSTRIP/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components may coordinate

with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment.

d. Data elements which have an expanded files size above existing legacy MILSTRIP capability which may not be supported by the

recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

e. Data required to accommodate Component-unique transaction requirements (ex. C or B-series transactions). Data does not apply to

legacy MILSTRIP transactions.

f. Data associated with a DLMS enhancement authorized for implementation by modernized systems under DLMS migration. This data

should be adopted during, or subsequent, to modernization when applicable to the Component’s business process. Prior coordination is not

required. Components should ensure that inclusion of this data in a DLMS transaction does not cause inappropriate rejection of the

transaction.

g. Repetition of data (using multiple iterations or loops) which is not compatible with existing legacy MILSTRIP capability. Although

supported by the use of the ANSI X12 standard, such data is not compatible with MILSTRIP/DLMS conversion and may not be supported by

the recipient's automated processing system. Components must coordinate implementation of enhanced capability with DEDSO prior to use.

3. Effective April 1, 2014, refer to ADC 1075.Users must reference the GENC Standard for country codes

(https://nsgreg.nga.mil/overview.jsp) for a listing of authorized values. Under DLMS, use the GENC Digraph (two-character) code values.

4. This transaction may be used to provide item unique identification (IUID) information in accordance with DLMS procedures and OSD

Supply Policy. Refer to the item unique identification (IUID) web at URL: http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy.

5. This revision to the DLMS IC incorporates Proposed DLMS Changes (PDC) and Approved DLMS Change (ADC) listed. PDCs and ADCs

are available from the DEDSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

- ADC 55, Revision to DLMS Supplement (DS) 856S, Shipment Status

- ADC 127, UID of Items and RFID in DLMS Shipment Status
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 2 September 12, 2023

- ADC 130, Army/DLA Unique Changes to 527R, Material Receipt, and 856S, Shipment Status, to Support Shipment and Receipt of TPF

Assets by UMFP

- ADC 165, Optional Capability for Sending Information Copy of DLMS Supplements 856, 856S, 861, 867I, 870M, 945A, and 947I to a

Component Unique Item Tracking (UIT) Registry (Supply)

- ADC 192, Administrative Revision to DS 4030 856S, Shipment Status

- ADC 193, Administrative Revision to DLMS Supplements 4030 856S and 4010 870S

- ADC 221, Communication of Unit Price and Total Price under DLMS

- ADC 221A, Revised Procedures associated with the DLMS Enhancement for Communication of Unit Price

- ADC 223, DLMS Shipment Status Enhancements: Secondary Transportation Number, Initial Shipping Activity, Carrier Identification, and

Port of Embarkation (POE)

- ADC 242, Shipment Status (DS 856S) in Support of MPCs: PD, TP, Project Code, Special Requirements Code

- ADC 242A, Approved Addendum to DLMS ADC 242A, Inclusion of Unit Price on DLMS Shipment Status (DS 856S)

- ADC 257, DLMS Shipment Status Generated by the CCP

- ADC 284, Revisions to DLMS Supplements to Add Shop Service Center (SSC) for BRAC Inventory Management and Stock Positioning

(IMSP)

- ADC 284A, Revisions to DLMS Supplements to Add Shop Service Center (SSC) for BRAC Inventory Management and Stock Positioning

(IMSP)

- ADC 288, DSS Local Delivery Manifesting Shipment Status

- ADC 299, Clarification of DLMS Shipment Status Supporting MILSTRIP AS6 to Identify Party to Receive Credit

- ADC 344, Revised DLMS Shipment Status (856S) in Support of Navy Enterprise Resource Program (ERP) and Commercial Asset Visibility

(CAV) II. The CAV Shipment Status enables the Navy Proof of Shipment (POS) process by supporting Navy CAV-unique data and process

requirements via the DLMS 856S on an interim basis pending full DLMS compliance. Refer to ADC 344 for details

- ADC 381, Procedures and Additional Data Content supporting Requisitions, Requisition Alerts, and Unit of Use Requirements under Navy

BRAC SS&D/IMSP

- ADC 411, Update Functionality for DS 856S Shipment Status and DS 945A Material Release Advice

- ADC 417, Shipment Status for Local Delivery Manifested, Outbound MILS Shipments on Behalf of On-Base Customers, Re-Warehousing

Actions between Distribution Depots, and non-MILS Shipments to Off-Base Customers, with Passive RFID

- ADC 422, Revises DLMS Supplement 856S, Shipment Status, in Support of Reutilization Business Integration (RBI)

- ADC 433, Requirements for estimated Shipment Date in the DS 856S Supporting Shipments to DLA Disposition Service Field Offices

- ADC 435, DLMS Revisions for SFIS Compliance 

- ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- ADC 441, Exception Rules to Accommodate Communication of Ammunition/Ammunition Related Quantities in Excess of Five Digits

(Supply/MILSTRIP/MILSTRAP)

- ADC 441A (Addendum to ADC 441) Clarification to Exception Rules to Accommodate Communication of Ammunition/Ammunition Related

Quantities in Excess of Five Digits (Supply/MILSTRIP/MILSTRAP)

- ADC 448, Implementation of International Organization for Standardization (ISO) 3166-1 Codes for the Identification of Countries and their

Subdivisions

- ADC 448B, Delayed implementation for International Organization for Standardization (ISO) 3166-1 Codes for the Identification of

Countries and their Subdivisions

- ADC 461, Revision for Commercial Asset Visibility-Organic Repairables Module (CAV-ORM) Estimated Completion Date (ECD) field on the

MILSTRAP DAC and DLMS 947I ECD transaction, and Administrative Update to 527D, 527R, 867I , 856S (Supply/MILSTRAP/MILSTRIP)

- ADC 466, Revised Procedures to Support Requisitioning and Transaction Exchange associated with DLA Disposition Services under

Reutilization Business Integration (RBI)

- ADC 473, DLMS Revisions to Add the Associated Purchase Order Number in Support of the DLA Interface with the Exchange

- ADC 473A, DLMS Revisions to Add the Associated Purchase Order Number (Supports DLA Interface with the Exchange, Navy Exchange

Service Command (NEXCOM), and Marine Corps Exchange (MCX) Non-Appropriated Funds (NAF) Activities and Non-DoD Customers)

- ADC 1007, New DLMS 842P, PQDR Data Exchange and Enhanced Exhibit Tracking via Standard Logistics Transactions

- ADC 1009A, DLMS Enhancements for Requisitioning to Improve Use of Mark-for Addressing, Expand Authorized Priority Designator

Validation, Correct EMALL Purchase/Credit Card Format Rules, and Require Distribution of Status for Requisitions associated with

Purchase/Credit Card Payment

- ADC 1014, Revised Procedures for Inclusion of Contract Data in Transactions Associated with Government Furnished Property (GFP) and

Management Control Activity (MCA) Validation of Contractor Furnished Materiel (CFM) Requisitions

- ADC 1030, Implementation of Item Unique Identification (IUID) in the DLMS Shipment Status DoD IUID Supply Policy Procedures and

Associated Supply Discrepancy Report Procedures

- ADC 1043, DLMS Revisions for Department of Defense (DoD) Standard Line of Accounting (SLOA)/Accounting Classification

- ADC 1043A, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Support Transaction Rejection Requirements

- ADC 1043B, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Modify Business Rules for Beginning Period of Availability

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- ADC 1068, Enhanced Procedures for Requisitioning via DOD EMALL and GSA Internet Ordering: Component Verification of Funds

Availability and Materiel Identification using the Supplier-Assigned Part Number and/or Supplier Commercial and Government Entity (CAGE)

Code

- ADC 1075, Implementation of Geopolitical Entities, Names, and Codes (GENC) Standard by DoD Components for the Identification of

Countries and their Subdivisions

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on May 29, 2014.

- ADC 1110, Administrative Update to Identify Code DPC Delivery Priority Code as an Approved X12 Migration Code and Associated DLMS

Documentation; Identifies Additional Data Elements Authorized for Modification in the Requisition Modification Process

- ADC 130, Army/DLA Unique Changes to 527R, Material Receipt, and 856S, Shipment Status, to Support Shipment and Receipt of TPF

Assets by UMFP

- ADC 165, Optional Capability for Sending Information Copy of DLMS Supplements 856, 856S, 861, 867I, 870M, 945A, and 947I to a

Component Unique Item Tracking (UIT) Registry (Supply)

- ADC 192, Administrative Revision to DS 4030 856S, Shipment Status

- ADC 193, Administrative Revision to DLMS Supplements 4030 856S and 4010 870S

- ADC 221, Communication of Unit Price and Total Price under DLMS

- ADC 221A, Revised Procedures associated with the DLMS Enhancement for Communication of Unit Price

- ADC 223, DLMS Shipment Status Enhancements: Secondary Transportation Number, Initial Shipping Activity, Carrier Identification, and

Port of Embarkation (POE)

- ADC 242, Shipment Status (DS 856S) in Support of MPCs: PD, TP, Project Code, Special Requirements Code

- ADC 242A, Approved Addendum to DLMS ADC 242A, Inclusion of Unit Price on DLMS Shipment Status (DS 856S)

- ADC 257, DLMS Shipment Status Generated by the CCP

- ADC 284, Revisions to DLMS Supplements to Add Shop Service Center (SSC) for BRAC Inventory Management and Stock Positioning

(IMSP)

- ADC 284A, Revisions to DLMS Supplements to Add Shop Service Center (SSC) for BRAC Inventory Management and Stock Positioning

(IMSP)

- ADC 288, DSS Local Delivery Manifesting Shipment Status

- ADC 299, Clarification of DLMS Shipment Status Supporting MILSTRIP AS6 to Identify Party to Receive Credit

- ADC 344, Revised DLMS Shipment Status (856S) in Support of Navy Enterprise Resource Program (ERP) and Commercial Asset Visibility

(CAV) II. The CAV Shipment Status enables the Navy Proof of Shipment (POS) process by supporting Navy CAV-unique data and process

requirements via the DLMS 856S on an interim basis pending full DLMS compliance. Refer to ADC 344 for details

- ADC 381, Procedures and Additional Data Content supporting Requisitions, Requisition Alerts, and Unit of Use Requirements under Navy

BRAC SS&D/IMSP

- ADC 411, Update Functionality for DS 856S Shipment Status and DS 945A Material Release Advice

- ADC 417, Shipment Status for Local Delivery Manifested, Outbound MILS Shipments on Behalf of On-Base Customers, Re-Warehousing

Actions between Distribution Depots, and non-MILS Shipments to Off-Base Customers, with Passive RFID

- ADC 422, Revises DLMS Supplement 856S, Shipment Status, in Support of Reutilization Business Integration (RBI)

- ADC 433, Requirements for estimated Shipment Date in the DS 856S Supporting Shipments to DLA Disposition Service Field Offices

- ADC 435, DLMS Revisions for SFIS Compliance 

- ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- ADC 441, Exception Rules to Accommodate Communication of Ammunition/Ammunition Related Quantities in Excess of Five Digits

(Supply/MILSTRIP/MILSTRAP)

- ADC 441A (Addendum to ADC 441) Clarification to Exception Rules to Accommodate Communication of Ammunition/Ammunition Related

Quantities in Excess of Five Digits (Supply/MILSTRIP/MILSTRAP)

- ADC 448, Implementation of International Organization for Standardization (ISO) 3166-1 Codes for the Identification of Countries and their

Subdivisions

- ADC 448B, Delayed implementation for International Organization for Standardization (ISO) 3166-1 Codes for the Identification of

Countries and their Subdivisions

- ADC 461, Revision for Commercial Asset Visibility-Organic Repairables Module (CAV-ORM) Estimated Completion Date (ECD) field on the

MILSTRAP DAC and DLMS 947I ECD transaction, and Administrative Update to 527D, 527R, 867I , 856S (Supply/MILSTRAP/MILSTRIP)

- ADC 466, Revised Procedures to Support Requisitioning and Transaction Exchange associated with DLA Disposition Services under

Reutilization Business Integration (RBI)

- ADC 473, DLMS Revisions to Add the Associated Purchase Order Number in Support of the DLA Interface with the Exchange

- ADC 473A, DLMS Revisions to Add the Associated Purchase Order Number (Supports DLA Interface with the Exchange, Navy Exchange

Service Command (NEXCOM), and Marine Corps Exchange (MCX) Non-Appropriated Funds (NAF) Activities and Non-DoD Customers)

- ADC 1007, New DLMS 842P, PQDR Data Exchange and Enhanced Exhibit Tracking via Standard Logistics Transactions

- ADC 1009A, DLMS Enhancements for Requisitioning to Improve Use of Mark-for Addressing, Expand Authorized Priority Designator

Validation, Correct EMALL Purchase/Credit Card Format Rules, and Require Distribution of Status for Requisitions associated with

Purchase/Credit Card Payment

- ADC 1014, Revised Procedures for Inclusion of Contract Data in Transactions Associated with Government Furnished Property (GFP) and

Management Control Activity (MCA) Validation of Contractor Furnished Materiel (CFM) Requisitions

- ADC 1030, Implementation of Item Unique Identification (IUID) in the DLMS Shipment Status DoD IUID Supply Policy Procedures and

Associated Supply Discrepancy Report Procedures

- ADC 1043, DLMS Revisions for Department of Defense (DoD) Standard Line of Accounting (SLOA)/Accounting Classification

- ADC 1043A, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Support Transaction Rejection Requirements

- ADC 1043B, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Modify Business Rules for Beginning Period of Availability

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- ADC 1068, Enhanced Procedures for Requisitioning via DOD EMALL and GSA Internet Ordering: Component Verification of Funds

Availability and Materiel Identification using the Supplier-Assigned Part Number and/or Supplier Commercial and Government Entity (CAGE)

Code

- ADC 1075, Implementation of Geopolitical Entities, Names, and Codes (GENC) Standard by DoD Components for the Identification of

Countries and their Subdivisions

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on May 29, 2014.

- ADC 1110, Administrative Update to Identify Code DPC Delivery Priority Code as an Approved X12 Migration Code and Associated DLMS

Documentation; Identifies Additional Data Elements Authorized for Modification in the Requisition Modification Process
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 3 September 12, 2023

- ADC 1132, Implementation of Mass/Universal Cancellation Procedures under the DLMS and Administrative Realignment of Procedures in

DLM 4000.25, Volume 2 and DLM 4000.25-1

- ADC 1136, Revise Unique Item Tracking (UIT) Procedures to support DODM 4140.01 UIT Policy and Clarify Requirements (Supply)

- ADC 1156, DLA Disposition Services Procedures for the Foreign Military Sales (FMS) Case Number and New Indicators for FMS Freeze

Information under Distribution Disposition Process Alignment (DDPA) Initiative

- ADC 1156A Indicators for Foreign Military Sales (FMS) Information (Supply)

- ADC 1161, Update uniform Procurement Instrument Identifier (PIID) numbering system in the Federal/DLMS Implementation Conventions

and DLMS Manuals (Supply/Contract Administration)

- ADC 1161A, Update Uniform Procurement Instrument Identifier (PIID) Numbering System in the Federal/DLMS Implementation

Conventions and DLMS Manuals (Supply/SDR/DoDAAD/Finance/Contract Administration)

- ADC 1198, Establishing Visibility of Capital Equipment for Service Owned Assets Stored at DLA Distribution Centers

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on January 17, 2017

- ADC 1244, Establishing Visibility of Unique Item Tracking (UIT) Program Items for Service-Owned Assets Stored at DLA Distribution

Centers and Corresponding Revisions to Inventory Procedures Related to Capital Equipment

- ADC 1244B Establishing Visibility of Unique Item Tracking (UIT) Program Items for Service-Owned Assets Stored at DoD Storage

Activities and Corresponding Revisions to the Small Arms and Light Weapons Program

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

September 13, 2018

- ADC 1287 DLMS Implementation Convention (IC) Revisions for Data Element Mapping (Form Stock Number and Manufacturer's Part

Number), Removal of Plant Equipment Number, and Administrative Updates

- ADC 1353, Transportation Method and Transportation Mode Codes on all DLMS ICs

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions

- ADC 1399, Inclusion of Mandatory Data Elements for DLA Disposition Services

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on April 13, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

- ADC 1420, Other Transaction (OT) Agreements Instrument Type and Procurement Instrument Identifier (PIID) Construct (Supply/Contract

Administration)

- ADC 1428, Merge the DLMS 856W Hazardous Material/Hazardous Waste Shipment Status in the 856S Shipment Status

- ADC 1433, Data Element Additions to Update DLMS 841W, DLMS 856S, and DLMS 824R

- ADC 1454, Expand Use of Shop Service Center Codes in Defense Logistics Management Standards Transactions

- ADC 1132, Implementation of Mass/Universal Cancellation Procedures under the DLMS and Administrative Realignment of Procedures in

DLM 4000.25, Volume 2 and DLM 4000.25-1

- ADC 1136, Revise Unique Item Tracking (UIT) Procedures to support DODM 4140.01 UIT Policy and Clarify Requirements (Supply)

- ADC 1156, DLA Disposition Services Procedures for the Foreign Military Sales (FMS) Case Number and New Indicators for FMS Freeze

Information under Distribution Disposition Process Alignment (DDPA) Initiative

- ADC 1156A Indicators for Foreign Military Sales (FMS) Information (Supply)

- ADC 1161, Update uniform Procurement Instrument Identifier (PIID) numbering system in the Federal/DLMS Implementation Conventions

and DLMS Manuals (Supply/Contract Administration)

- ADC 1161A, Update Uniform Procurement Instrument Identifier (PIID) Numbering System in the Federal/DLMS Implementation

Conventions and DLMS Manuals (Supply/SDR/DoDAAD/Finance/Contract Administration)

- ADC 1198, Establishing Visibility of Capital Equipment for Service Owned Assets Stored at DLA Distribution Centers

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on January 17, 2017

- ADC 1244, Establishing Visibility of Unique Item Tracking (UIT) Program Items for Service-Owned Assets Stored at DLA Distribution

Centers and Corresponding Revisions to Inventory Procedures Related to Capital Equipment

- ADC 1244B Establishing Visibility of Unique Item Tracking (UIT) Program Items for Service-Owned Assets Stored at DoD Storage

Activities and Corresponding Revisions to the Small Arms and Light Weapons Program

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

September 13, 2018

- ADC 1287 DLMS Implementation Convention (IC) Revisions for Data Element Mapping (Form Stock Number and Manufacturer's Part

Number), Removal of Plant Equipment Number, and Administrative Updates

- ADC 1353, Transportation Method and Transportation Mode Codes on all DLMS ICs

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions

- ADC 1399, Inclusion of Mandatory Data Elements for DLA Disposition Services

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on April 13, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

- ADC 1420, Other Transaction (OT) Agreements Instrument Type and Procurement Instrument Identifier (PIID) Construct (Supply/Contract

Administration)

- ADC 1428, Merge the DLMS 856W Hazardous Material/Hazardous Waste Shipment Status in the 856S Shipment Status

- ADC 1433, Data Element Additions to Update DLMS 841W, DLMS 856S, and DLMS 824R

- ADC 1454, Expand Use of Shop Service Center Codes in Defense Logistics Management Standards Transactions

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

0100 ST Transaction Set Header M 1 Must use

0200 BSN Beginning Segment for Ship Notice M 1 Must use

* 0400 DTM Date/Time Reference O 10 Not Used

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL LOOP ID - HL 200000 C2/0100L C2/0100L

0100 HL Hierarchical Level M 1 C2/0100 Must use

0200 LIN Item Identification O 1 Used

0300 SN1 Item Detail (Shipment) O 1 Used

* 0400 SLN Subline Item Detail O 1000 Not Used

* 0500 PRF Purchase Order Reference O 1 Not Used

* 0600 PO4 Item Physical Details O 1 Not Used

0700 PID Product/Item Description O 200 Used

0800 MEA Measurements O 40 Used

* 0900 PWK Paperwork O 25 Not Used

1000 PKG Marking, Packaging, Loading O 25 Used

* 1100 TD1 Carrier Details (Quantity and

Weight)

O 20 Not Used

1200 TD5 Carrier Details (Routing

Sequence/Transit Time)

O 12 Used

* 130 TD3 Carrier Details (Equipment) O 12 Not Used

* LOOP ID - TD3 * LOOP ID - TD3 12

* 1300 TD3 Carrier Details (Equipment) O 1 Not Used

* 1350 AT9 Trailer or Container Dimension and

Weight

O 1 Not Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004030F856S3SA51 4 September 12, 2023

* 1400 TD4 Carrier Details (Special Handling,

or Hazardous Materials, or Both)

O 5 Not Used

* 1450 TSD Trailer Shipment Details O 1 Not Used

1500 REF Reference Identification O >1 Used

1510 PER Administrative Communications

Contact

O 3 Used

* LOOP ID - LH1 * LOOP ID - LH1 100

* 1520 LH1 Hazardous Identification

Information

O 1 Not Used

* 1530 LH2 Hazardous Classification

Information

O 4 Not Used

* 1540 LH3 Hazardous Material Shipping

Name

O 12 Not Used

* 1550 LFH Freeform Hazardous Material

Information

O 20 Not Used

* 1560 LEP EPA Required Data O >1 Not Used

* 1570 LH4 Canadian Dangerous

Requirements

O 1 Not Used

* 1580 LHT Transborder Hazardous

Requirements

O 3 Not Used

* 1590 LHR Hazardous Material Identifying

Reference Numbers

O 10 Not Used

* 1600 PER Administrative Communications

Contact

O 5 Not Used

* 1610 LHE Empty Equipment Hazardous

Material Information

O 1 Not Used

* LOOP ID - CLD * LOOP ID - CLD 200

* 1700 CLD Load Detail O 1 Not Used

* 1800 REF Reference Identification O 200 Not Used

* 1850 DTP Date or Time or Period O 1 Not Used

* 1900 MAN Marks and Numbers O >1 Not Used

2000 DTM Date/Time Reference O 10 Used

* 2100 FOB F.O.B. Related Instructions O 1 Not Used

* 2150 PAL Pallet Information O 1 Not Used

LOOP ID - N1 LOOP ID - N1 200

2200 N1 Name O 1 Used

2300 N2 Additional Name Information O 2 Used

2400 N3 Address Information O 2 Used

2500 N4 Geographic Location O 1 Used

* 2600 REF Reference Identification O 12 Not Used

* 2700 PER Administrative Communications

Contact

O 3 Not Used

* 2800 FOB F.O.B. Related Instructions O 1 Not Used

* 2900 SDQ Destination Quantity O 50 Not Used

* 3000 ETD Excess Transportation Detail O 1 Not Used

* 3100 CUR Currency O 1 Not Used

LOOP ID - SAC LOOP ID - SAC >1

3200 SAC Service, Promotion, Allowance, or

Charge Information

O 1 Used

* 3250 CUR Currency O 1 Not Used

3300 GF Furnished Goods and Services O 1 Used

* 3350 YNQ Yes/No Question O 10 Not Used

LOOP ID - LM LOOP ID - LM 10

3400 LM Code Source Information O 1 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004030F856S3SA51 5 September 12, 2023

3500 LQ Industry Code M 100 Must use

* LOOP ID - V1 * LOOP ID - V1 >1

* 3600 V1 Vessel Identification O 1 Not Used

* 3700 R4 Port or Terminal O >1 Not Used

* 3800 DTM Date/Time Reference O >1 Not Used

Summary:

Pos Id Segment Name Req Max Use Repeat Notes Usage

* 0100 CTT Transaction Totals O 1 N3/0100 Not Used

0200 SE Transaction Set Trailer M 1 Must use

Notes: 

3/0100 Number of line items (CTT01) is the accumulation of the number of HL segments. If used, hash total (CTT02) is the sum of the

value of units shipped (SN102) for each SN1 segment.

Comments: 

2/0100L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.

2/0100 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 6 September 12, 2023

ST Transaction Set Header Pos: 0100 Max: 1

Heading - Mandatory

Loop: N/A Elements: 3

User Option (Usage): Must use

Purpose: To indicate the start of a transaction set and to assign a control number

Semantics: 

1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set

definition (e.g., 810 selects the Invoice Transaction Set).

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use

Code Name

856 Ship Notice/Manifest

ST02 329 Transaction Set Control Number

Description: Identifying control number that must

be unique within the transaction set functional group

assigned by the originator for a transaction set

DLMS Note: A unique number assigned by the

originator of the transaction set, or the originator's

application program.

M AN 4/9 Must use

ST03 1705 Implementation Convention Reference

Description: Reference assigned to identify

Implementation Convention

DLMS Note: Use to indicate this transmission uses

the 856S DLMS Implementation Convention (IC). 

Enter the DLMS IC: 004030F856S0SA00.

O AN 1/35 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 7 September 12, 2023

BSN Beginning Segment for Ship Notice Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 6

User Option (Usage): Must use

Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set

Syntax Rules: 

1. C0706 - If BSN07 is present, then BSN06 is required.

Semantics: 

1. BSN03 is the date the shipment transaction set is created.

2. BSN04 is the time the shipment transaction set is created.

3. BSN06 is limited to shipment related codes.

Comments: 

1. BSN06 and BSN07 differentiate the functionality of use for the transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

BSN01 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

M ID 2/2 Must use

Code Name

00 Original

77 Simulation Exercise

DLMS Note:

Use to identify a simulated mobilization exercise transaction set. Activities initiating simulated

mobilization exercises must ensure complete coordination with all activities involved. All transaction set

recipients must use extreme caution to ensure that individual transactions do not process as action

documents which affect accountable records.

ZZ Mutually Defined

DLMS Note:

1. Use to identify the Unit of Use Indicator. When included, the quantity and unit of measure values

associated with this transaction are applicable to the unit of use. This applies when the materiel

identification is by Local Stock Number assigned for unit of use.

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

BSN02 396 Shipment Identification

Description: A unique control number assigned by

the original shipper to identify a specific shipment

DLMS Note: 1. Use code "ZZ" or “RR” for this data

element to satisfy X12 syntax requirements.

2. The ZZ filler differentiates this Shipment Status

format from the Advanced Shipment Notice format

associated with Wide Area Workflow, as both use

BSN06 Qualifier AS, Shipment Advice.

3. Use Code “RR” to indicate this is a replacement

transaction to a previously submitted 856S. Refer to

ADC 411.

4. DLMS enhancement; see introductory DLMS Note

2f.

M AN 2/30 Must use

BSN03 373 Date M DT 8/8 Must use
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F856S3SA51 8 September 12, 2023

Description: Date expressed as CCYYMMDD

DLMS Note: This date corresponds to the Universal

Time Coordinate (UTC).

BSN04 337 Time

Description: Time expressed in 24-hour clock time

as follows: HHMM, or HHMMSS, or HHMMSSD, or

HHMMSSDD, where H = hours (00-23), M = minutes

(00-59), S = integer seconds (00-59) and DD =

decimal seconds; decimal seconds are expressed

as follows: D = tenths (0-9) and DD = hundredths

(00-99)

DLMS Note: 1. Express the originating activity's

time in UTC.

2. Express time in a four-position (HHMM) format.

M TM 4/8 Must use

BSN06 640 Transaction Type Code

Description: Code specifying the type of

transaction

X ID 2/2 Used

Code Name

AS Shipment Advice

DLMS Note:

1. Use to indicate this transaction provides shipment status information related to requisitions . Also

use with BSN07 to indicate shipment status to the ICP/IMM from the reporting activity for lateral

redistribution of retail assets.

2. Also applies to Army Total Package Fielding.

3. Use with BSN07=WTP to identify CAV Shipment Status.

4. Use with BSN07=014 for outbound non-MILS shipments (e.g., a DD1149). Refer to ADC 417

1. Use to indicate this transaction provides shipment status information related to requisitions . Also

use with BSN07 to indicate shipment status to the ICP/IMM from the reporting activity for lateral

redistribution of retail assets.

2. Also applies to Army Total Package Fielding.

3. Use with BSN07=WTP to identify CAV Shipment Status.

4. Use with BSN07=014 for outbound non-MILS shipments (e.g., a DD1149). Refer to ADC 417

AZ Disposal Shipment Advice

DLMS Note:

Use to indicate this transaction provides Hazardous Material/Hazardous Waste shipment status

information for turn-in of material to DLA Disposition Services.

NC Material Release Order Forced Closure

DLMS Note:

Use to indicate this transaction set provides pseudo shipment status information.

BSN07 641 Status Reason Code

Description: Code indicating the status reason

O ID 3/3 Used

Code Name

014 Military Service

DLMS Note:

Use to identify that the shipment status is provided in response to a non-MILS shipment (e.g., DD1149)

in support of passive RFID data exchange. The status may reflect multiple levels of pack associated

with the shipment unit Transportation Control Number (TCN) and may provide the secondary

transportation data (e.g., bill of lading, tracking number, carrier identification). Refer to ADC 417.

035 Borrower Action

DLMS Note:

Use to identify shipments of loaned property.

048 Location Changed

DLMS Note:

Industrial Activity Re-Warehousing/Trans-ship Shipment Status. Use to identify that the shipment

status is provided in response to re-warehousing/transshipments between Home and Forward Industrial

Activities in support of IMSP. Since no Material Receipt Acknowledgement (MRA) is required for these 
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 9 September 12, 2023

types of shipments, the shipment status will not trigger the MRA Reports.

061 Consolidation, Extension, Modification (CEM)

DLMS Note:

Use to identify that shipment status is provided by the Consolidation and Containerization Point (CCP)

subsequent to original shipment in support of passive RFID data exchange. The CCP Shipment Status

may reflect multiple levels of pack associated with the lead Transportation Control Number (TCN). It

may update the shipment date or mode of shipment while providing visibility of additional or

replacement passive RFID tag values associated with the original shipment as a result of CCP

processing/ reconfiguration. The CCP Shipment Status should not be used to overlay the original

shipment status in the receiving application, as this may result in some loss of data content.

Use to identify that shipment status is provided by the Consolidation and Containerization Point (CCP)

subsequent to original shipment in support of passive RFID data exchange. The CCP Shipment Status

may reflect multiple levels of pack associated with the lead Transportation Control Number (TCN). It

may update the shipment date or mode of shipment while providing visibility of additional or

replacement passive RFID tag values associated with the original shipment as a result of CCP

processing/ reconfiguration. The CCP Shipment Status should not be used to overlay the original

shipment status in the receiving application, as this may result in some loss of data content.

091 Reprocessed

DLMS Note:

Trans-ship/Cross-dock Shipment Status (non-CCP). Use to identify that shipment status is provided by

a location performing consolidation subsequent to original shipment (e.g., local delivery manifesting,

deliveries to MPC) in support of passive RFID data exchange. The status may reflect multiple levels of

pack associated with the lead Transportation Control Number (TCN). It may update the shipment date

or mode of shipment while providing visibility of additional or replacement passive RFID tag values

associated with the original shipment as a result of processing/ reconfiguration. The Shipment Status

should not be used to overlay the original shipment status in the receiving application, as this may

result in some loss of data content. Refer to ADC 417.

Trans-ship/Cross-dock Shipment Status (non-CCP). Use to identify that shipment status is provided by

a location performing consolidation subsequent to original shipment (e.g., local delivery manifesting,

deliveries to MPC) in support of passive RFID data exchange. The status may reflect multiple levels of

pack associated with the lead Transportation Control Number (TCN). It may update the shipment date

or mode of shipment while providing visibility of additional or replacement passive RFID tag values

associated with the original shipment as a result of processing/ reconfiguration. The Shipment Status

should not be used to overlay the original shipment status in the receiving application, as this may

result in some loss of data content. Refer to ADC 417.

A13 Other

DLMS Note:

Use to identify shipments to entities outside of the DoD. Qualifier A13 does not apply to loans.

A40 Shipper Related

DLMS Note:

1. Required in conjunction with BSN02 = “RR” to indicate the updated shipment status transaction

corrects erroneous content data (e.g., transportation data, pRFID data). Refer to ADC 411.

2. DLMS enhancement; see introductory DLMS Note 2f.

IV2 Material Shipped Between Intermediate Points

DLMS Note:

Use to indicate transaction set contains a shipment status associated with a lateral redistribution order.

SCP DoD Security Cooperation Program (DSCP)

DLMS Note:

Local code SCP is established for use in this transaction. Use to identify a shipment for the purpose of

(DSCP) (i.e., FMS and Grand Aid). Code maintenance has been submitted to X12. Pending approval

at X12 it will be added in a future release.

W10 Diverted Item

DLMS Note:

Use when shipment status indicates that action is being taken to divert the shipment in response to

request for mass or universal requisition cancellation.

WTP Waiting for Proof

DLMS Note:

Use to indicate that Commercial Asset Visibility (CAV) shipment status is provided by a contractor

under Navy CAV requirements. Also known as “Proof of Shipment (POS).”
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 10 September 12, 2023

HL Hierarchical Level Pos: 0100 Max: 1

Detail - Mandatory

Loop: HL Elements: 3

User Option (Usage): Must use

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments

Comments: 

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment

data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure.

3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01

could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL

segment and would be incremented by one in each subsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

5. HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in

the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring

to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

DLMS Note:

1. The transaction set hierarchical data structure is address information, followed by transaction shipment status, followed interior/exterior

packaging passive RFID and/or by IUID and/or financial information as applicable. 

2. Use the first 2/HL/0100 loop iteration to provide transaction set originator address information.

3. Use the second 2/HL/0100 loop iteration to identify shipment information, or for Hazardous Material/Hazardous Waste shipment status

information (BSN06 = AZ). Only one HM/HW shipment status provided per transaction.

4. Use additional 2/HL/0100 loop iterations to identify RFID as applicable.

5. Use additional 2/HL/0100 loop iterations to identify IUID information as applicable.

6. Use additional 2/HL/0100 loop iterations to identify the container record, EPA waste code record, and state waste code record as

applicable.

7. Use an additional 2/HL/0100 loop iteration to identify financial information in support of SLOA/Accounting Classification information

requirements.

8. The HL Address loop provides address information relating to the originator of this transaction. All other relevant address information is

carried in the Shipment Status loop.

1. The transaction set hierarchical data structure is address information, followed by transaction shipment status, followed interior/exterior

packaging passive RFID and/or by IUID and/or financial information as applicable. 

2. Use the first 2/HL/0100 loop iteration to provide transaction set originator address information.

3. Use the second 2/HL/0100 loop iteration to identify shipment information, or for Hazardous Material/Hazardous Waste shipment status

information (BSN06 = AZ). Only one HM/HW shipment status provided per transaction.

4. Use additional 2/HL/0100 loop iterations to identify RFID as applicable.

5. Use additional 2/HL/0100 loop iterations to identify IUID information as applicable.

6. Use additional 2/HL/0100 loop iterations to identify the container record, EPA waste code record, and state waste code record as

applicable.

7. Use an additional 2/HL/0100 loop iteration to identify financial information in support of SLOA/Accounting Classification information

requirements.

8. The HL Address loop provides address information relating to the originator of this transaction. All other relevant address information is

carried in the Shipment Status loop.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

HL01 628 Hierarchical ID Number

Description: A unique number assigned by the

sender to identify a particular data segment in a

hierarchical structure

DLMS Note: In the first 2/HL/0100 loop iteration,

cite numeric 1. In each subsequent loop iteration,

increase incrementally by 1.

M AN 1/12 Must use

HL02 734 Hierarchical Parent ID Number

Description: Identification number of the next

higher hierarchical data segment that the data

segment being described is subordinate to

DLMS Note: 1. Use to provide association

(parent/child relationship) between interior and

exterior packaging when multiple RFID tags are

employed in the shipment. Use in the subordinate

O AN 1/12 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F856S3SA51 11 September 12, 2023

(child) loop to identify the HL01 ID Number of the

next higher parent loop.

2. IUID loops may be associated with a parent RFID

loop (e.g. item pack). Not applicable to the IUID

loop if no specific parent RFID loop is identified.

3. Use to provide association (parent/child

relationship) between a HM/HW shipping status

record and any container, EPA waste code, and

state waste code records, as applicable. Use in the

subordinate (child) loop to identify the HL01 ID

Number of the shipping status record loop (HL01=2).

3. Use to provide association (parent/child

relationship) between a HM/HW shipping status

record and any container, EPA waste code, and

state waste code records, as applicable. Use in the

subordinate (child) loop to identify the HL01 ID

Number of the shipping status record loop (HL01=2).

4. Not applicable to address and shipment status

loops.

HL03 735 Hierarchical Level Code

Description: Code defining the characteristic of a

level in a hierarchical structure

DLMS Note: The following informational loops are

applicable to this transaction. When all loops are

used, the HL sequence is V (address), W (shipment

status), P (RFID), and I (IUID). RFID and IUID loops

are optional. Use multiple P loops to depict a

nested RFID relationship.

DLMS Note: The following informational loops are

applicable to this transaction. When all loops are

used, the HL sequence is V (address), W (shipment

status), P (RFID), and I (IUID). RFID and IUID loops

are optional. Use multiple P loops to depict a

nested RFID relationship.

M ID 1/2 Must use

Code Name

I Item

DLMS Note:

Use to identify item IUID data consistent with IUID data requirements. The IUID data is carried in the

REF and N1 segments; no other segments are used in the IUID loop. Use a separate IUID loop for each

item. If an RFID is provided at the item level it will be reflected in this loop. Skip this level when not

applicable.

P Pack

DLMS Note:

Use to identify the passive RFID tag identification. The tag identification is carried in the REF segment;

no other segments are used in this loop at this time. Use a separate RFID loop for each RFID

associated with the shipment using the HL02 parent ID to create a parent/child (nested) relationship.

Skip this level when not applicable.

V Address Information

DLMS Note:

Use to identify the address loop which specifies the transaction originator. For Hazardous

Material/Hazardous Waste shipment status information (BSN06 = AZ) also identifies the recipient. Use

only one address loop per transaction.

W Transaction Reference Number

DLMS Note:

Use to identify the shipment status loop which identifies the transaction reference number (requisition

document number) and associated shipment information. Use only one shipment status loop per

transaction.

CN Container

DLMS Note:

Use to identify the container record loop which specifies the storage location code, container

weight/volume and the accumulation start date for the HM/HW shipment status record. Repeat this loop

as necessary and identify the parent loop as the HM/HW shipment status record loop.

FI Financial Information

DLMS Note:

Use to identify the Finance loop to provide DoD SLOA/Accounting Classification information. The

Finance loop includes only the REF/1500 and DTM/2000 segments. This loop is applicable for

shipment status to the ICP from the reporting activity for ICP-directed lateral redistribution order

shipments of retail assets (equivalent to MILSTRIP legacy DIC AS6) or items shipped to DLA 
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 12 September 12, 2023

Disposition Services. Refer to ADC 1043.

HE EPA Waste Number Subsection

DLMS Note:

1. Use to identify the EPA waste code record loop which specifies the applicable EPA waste codes

associated with the shipment. Repeat this loop as necessary and identify the parent loop as the

shipment status loop.

2. A data maintenance action was approved in version 8010. The approved code/name is “HE – EPA

Waste Number Subsection”.

ST State

DLMS Note:

1. Use to identify the state waste code record loop which specifies the applicable state waste codes

associated with the shipment. Repeat this loop as necessary and identify the parent loop as the

shipment status loop.

2. A data maintenance action was approved in version 4040. The approved code/name is “ST – State”.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 13 September 12, 2023

LIN Item Identification Pos: 0200 Max: 1

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To specify basic item identification data

Syntax Rules: 

1. P0405 - If either LIN04 or LIN05 is present, then the other is required.

2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

3. P0809 - If either LIN08 or LIN09 is present, then the other is required.

4. P1011 - If either LIN10 or LIN11 is present, then the other is required.

5. P1213 - If either LIN12 or LIN13 is present, then the other is required.

6. P1415 - If either LIN14 or LIN15 is present, then the other is required.

7. P1617 - If either LIN16 or LIN17 is present, then the other is required.

8. P1819 - If either LIN18 or LIN19 is present, then the other is required.

9. P2021 - If either LIN20 or LIN21 is present, then the other is required.

10. P2223 - If either LIN22 or LIN23 is present, then the other is required.

11. P2425 - If either LIN24 or LIN25 is present, then the other is required.

12. P2627 - If either LIN26 or LIN27 is present, then the other is required.

13. P2829 - If either LIN28 or LIN29 is present, then the other is required.

14. P3031 - If either LIN30 or LIN31 is present, then the other is required.

Semantics: 

1. LIN01 is the line item identification

Comments: 

1. See the Data Dictionary for a complete list of IDs.

2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No.,

ISBN No., Model No., or SKU.

DLMS Note:

Must use only in 2/HL/0100 shipment status loop to identify the materiel shipped.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LIN02 235 Product/Service ID Qualifier

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

DLMS Note: 1. Use one of codes A2, A4, FB, FS,

FT, MG, NN, SW, YP, ZR, or ZZ to identify the

materiel shipped. Must use National Stock Number

(NSN) when known, except, when appropriate,

brand name subsistence items are identified by the

subsistence identification number or when

maintenance/industrial activity materiel is identified

by Local Stock Number or Materiel Control Tracking

(MCT) tag number. An exception is also authorized

for CAV Shipment Status where materiel may be

identified by the National Item Identification Number

(NIIN) when the Federal Supply Code (FSC) is not

available.

DLMS Note: 1. Use one of codes A2, A4, FB, FS,

FT, MG, NN, SW, YP, ZR, or ZZ to identify the

materiel shipped. Must use National Stock Number

(NSN) when known, except, when appropriate,

brand name subsistence items are identified by the

subsistence identification number or when

maintenance/industrial activity materiel is identified

by Local Stock Number or Materiel Control Tracking

(MCT) tag number. An exception is also authorized

for CAV Shipment Status where materiel may be

identified by the National Item Identification Number

(NIIN) when the Federal Supply Code (FSC) is not

available.

2. The following codes are authorized.

M ID 2/2 Must use

Code Name

A2 Department of Defense Identification Code (DoDIC)
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 14 September 12, 2023

DLMS Note:

Use to identify ammunition items.

A4 Subsistence Identification Number

DLMS Note:

Use to identify subsistence items.

FB Form Number

DLMS Note:

Use to identify the form stock number.

FS National Stock Number

FT Federal Supply Classification

DLMS Note:

Use to identify the FSC of the nonstandard materiel when a part number is not available and materiel

can only be identified by description (e.g., non-NSN lumber products).

MG Manufacturer's Part Number

DLMS Note:

1. Use to identify nonstandard materiel.

2. May be used to identify the supplier-assigned part number when applicable to a DoD EMALL or GSA

Advantage/Global internet order from a vendor catalog. Refer to ADC 1068.

NN National Item Identification Number

DLMS Note:

1. Use only for CAV Shipment Status when the NSN (FSC plus NIIN) is not available. 

2. Qualifier NN is a migration code approved for use in X12 version 5020. This is an authorized DLMS

enhancement.

SW Stock Number

DLMS Note:

1. Use to identify the local stock number (LSN). 

2. When used for a unit of use LSN (with 1/BSN01/0200=ZZ), the applicable NSN will be included for

cross-reference (at LIN04-05). May also be used for identification of LSNs assigned for part-numbered

item requisitioning.

3. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

YP Publication Number

DLMS Note:

Use to identify the publication stock number.

ZR Service Control Identification

DLMS Note:

Use to identify Materiel Control Tracking (MCT) tag number. The MCT tag number is an authorized

DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

ZZ Mutually Defined

DLMS Note:

1. Use to identify nonstandard materiel when all other authorized codes do not apply or cannot be

determined (includes management control numbers and locally assigned control numbers). May be

used for legacy MILSTRIP-to-DLMS conversion when the translator cannot determine a more

appropriate code. 

2. DLMS enhancement.

LIN03 234 Product/Service ID

Description: Identifying number for a product or

service

M AN 1/48 Must use

LIN04 235 Product/Service ID Qualifier X ID 2/2 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F856S3SA51 15 September 12, 2023

Description: Code identifying the type/source of the

descriptive number used in Product/Service ID (234)

Code Name

CN Commodity Name

DLMS Note:

1. Use with LIN02 code FT to identify the materiel name or description.

2. Do not use for Hazardous Materiel/Hazardous Waste. Provide the Proper Shipping Name in

2/PID/0700.

FS National Stock Number

DLMS Note:

1. Use to identify the NSN. 

2. The NSN is provided as a cross-reference when unit of use indicator is included (1/BSN01/0200=ZZ)

and the Local Stock Number (LSN) is identified as the primary materiel identification. Authorized DLMS

enhancement under DLA industrial activity support agreement.

ZB Commercial and Government Entity (CAGE) Code

DLMS Note:

1. Use with LIN02 code MG to uniquely identify a manufacturer's (or supplier’s) part number.

2. May be used to identify the supplier CAGE when applicable to a DoD EMALL or GSA

Advantage/Global internet order from a vendor catalog. 

LIN05 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 16 September 12, 2023

SN1 Item Detail (Shipment) Pos: 0300 Max: 1

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To specify line-item detail relative to shipment

Syntax Rules: 

1. P0506 - If either SN105 or SN106 is present, then the other is required.

Semantics: 

1. SN101 is the ship notice line-item identification.

Comments: 

1. SN103 defines the unit of measurement for both SN102 and SN104.

DLMS Note:

Must use only in 2/HL/0100 shipment status loop to identify the number of units shipped.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

SN102 382 Number of Units Shipped

Description: Numeric value of units shipped in

manufacturer's shipping units for a line item or

transaction set

DLMS Note: 1. Express as a whole number with no

decimals. 

2. For shipment status and lateral redistribution

shipment status, use to identify the shipped quantity.

3. For pseudo shipment status (BSN06 code NC),

use to identify the Materiel Release Order (MRO)

quantity.

4. A field size exceeding 5 positions may not be

received or understood by the recipient's automated

processing system. See introductory DLMS note 2d.

5. For CAV shipment status (BSN06=WTP), use to

indicate quantity shipped or quantity reversed.

Always enter a quantity of one (1). A separate CAV

shipment status is prepared for each individual item

shipped. To reverse, enter a quantity of minus one

(-1).

5. For CAV shipment status (BSN06=WTP), use to

indicate quantity shipped or quantity reversed.

Always enter a quantity of one (1). A separate CAV

shipment status is prepared for each individual item

shipped. To reverse, enter a quantity of minus one

(-1).

6. For non-MILS shipment (e.g., DD1149) status

(BSN07=014) in support of pRFID exchange, when

2/LIN02/0200=ZZ and 2/LIN03/0200=MIXED, enter

a quantity of one (1) to indicate multi-line items.

Refer to ADC 417.

7. For HM/HW, use only in 2/HL/0100 Code W

shipment status loop to identify the number of units

shipped/turned in. (This is not the HIN quantity.) 

M R 1/10 Must use

SN103 355 Unit or Basis for Measurement Code

Description: Code specifying the units in which a

value is being expressed, or manner in which a

measurement has been taken

DLMS Note: 1. Use to identify the unit of issue for

the materiel shipped. 

2. DLMS users see the Unit of Issue Conversion 

M ID 2/2 Must use
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F856S3SA51 17 September 12, 2023

Table for available codes. 

3. For non-MILS shipment (e.g., DD1149) status,

(BSN07=014) in support of pRFID exchange, when

2/LIN02/0200=ZZ and 2/LIN03/0200=MIXED, enter

a unit of issue of “MX”. Refer to ADC 417

SN105 330 Quantity Ordered

Description: Quantity ordered

DLMS Note: Use in the HL03 code W loop when

providing the HIN quantity.

X R 1/15 Used

SN106 355 Unit or Basis for Measurement Code

Description: Code specifying the units in which a

value is being expressed, or manner in which a

measurement has been taken

DLMS Note: Use to provide the unit of measure for

HIN quantity when applicable.

X ID 2/2 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 18 September 12, 2023

PID Product/Item Description Pos: 0700 Max: 200

Detail - Optional

Loop: HL Elements: 5

User Option (Usage): Used

Purpose: To describe a product or process in coded or free-form format

Syntax Rules: 

1. C0403 - If PID04 is present, then PID03 is required.

2. R0405 - At least one of PID04 or PID05 is required.

3. C0703 - If PID07 is present, then PID03 is required.

4. C0804 - If PID08 is present, then PID04 is required.

5. C0905 - If PID09 is present, then PID05 is required.

Semantics: 

1. Use PID03 to indicate the organization that publishes the code list being referred to.

2. PID04 should be used for industry-specific product description codes.

3. PID08 describes the physical characteristics of the product identified in PID04. A "Y" indicates that the specified attribute applies to this

item; an "N" indicates it does not apply. Any other value is indeterminate.

4. PID09 is used to identify the language being used in PID05.

Comments: 

1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are

used.

2. Use PID06 when necessary to refer to the product surface or layer being described in the segment.

3. PID07 specifies the individual code list of the agency specified in PID03.

DLMS Note:

Must use only in 2/HL/0100 Code W shipping status record loop to provide the waste description information.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

PID01 349 Item Description Type

Description: Code indicating the format of a

description

M ID 1/1 Must use

Code Name

X Semi-structured (Code and Text)

PID03 559 Agency Qualifier Code

Description: Code identifying the agency assigning

the code values

O ID 2/2 Used

Code Name

DL Defense Logistics Agency

PID04 751 Product Description Code

Description: A code from an industry code list

which provides specific data about a product

characteristic

DLMS Note: 1. Use the following codes to identify

the waste description line number: 

WDL1 - Waste Description Line 1

WDL2 - Waste Description Line 2

WDL3 - Waste Description Line 3

O AN 1/12 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F856S3SA51 19 September 12, 2023

WDL4 - Waste Description Line 4

2. Use the following codes to identify the Proper

Shipping Name in 80 character increments up to

600 characters: 

PSN1 – Proper Shipping Name Part 1

PSN2 – Proper Shipping Name Part 2

PSN3 – Proper Shipping Name Part 3

PSN4 – Proper Shipping Name Part 4

PSN5 – Proper Shipping Name Part 5

PSN6 – Proper Shipping Name Part 6

PSN7 – Proper Shipping Name Part 7

PSN8 – Proper Shipping Name Part 8

3. For DoT Hazardous Material use code DHM and

indicate (Y)es or (N)o in PID08.

4. Use OTH to identify additional Other Hazard

Description (Identify in the PID05 any additional

Hazard descriptive information associated with the

proper shipping name).

5. Use TYO to identify the Type of Operation

Generating Waste with the value provided in PID05.

PID05 352 Description

Description: A free-form description to clarify the

related data elements and their content

O AN 1/80 Used

PID08 1073 Yes/No Condition or Response Code

Description: Code indicating a Yes or No condition

or response

O ID 1/1 Used

Code Name

N No

Y Yes
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 20 September 12, 2023

MEA Measurements Pos: 0800 Max: 40

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and weights(See Figures Appendix for

example of use of C001)

Syntax Rules: 

1. R03050608 - At least one of MEA03, MEA05, MEA06 or MEA08 is required.

2. C0504 - If MEA05 is present, then MEA04 is required.

3. C0604 - If MEA06 is present, then MEA04 is required.

4. L07030506 - If MEA07 is present, then at least one of MEA03, MEA05 or MEA06 is required.

5. E0803 - Only one of MEA08 or MEA03 may be present.

Semantics: 

1. MEA04 defines the unit of measure for MEA03, MEA05, and MEA06.

Comments: 

1. When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a positive (+) value cannot

be assumed, use MEA05 as the negative (-) value and MEA06 as the positive (+) value.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

MEA01 737 Measurement Reference ID Code

Description: Code identifying the broad category to

which a measurement applies

O ID 2/2 Used

Code Name

CT Counts

DLMS Note:

Use in the HL03 code W loop to identify the number of containers. Enter the quantity in the MEA03.

WA Waste Amount

DLMS Note:

Use in the HL03 code W loop with MEA02 code VWT to identify the Disposal Total Weight/Volume.

WT Weights

DLMS Note:

Use in the HL03 code CN loop with MEA02 code VWT to identify the Container Weight/Volume.

MEA02 738 Measurement Qualifier

Description: Code identifying a specific product or

process characteristic to which a measurement

applies

O ID 1/3 Used

Code Name

VWT Volume Weight

DLMS Note:

Use with MEA01 code WA or WT. Enter volume weight in the MEA03.

MEA03 739 Measurement Value

Description: The value of the measurement

O R 1/20 Used

MEA04 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for examples of

O Comp Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F856S3SA51 21 September 12, 2023

use)

MEA04-01 355 Unit or Basis for Measurement Code

Description: Code specifying the units in which a

value is being expressed, or manner in which a

measurement has been taken

M ID 2/2 Must use

Code Name

CR Cubic Meter

DLMS Note:

GenComm equivalent code is C.

CY Cubic Yard

DLMS Note:

GenComm equivalent code is Y.

GA Gallon

DLMS Note:

GenComm equivalent code is G.

KG Kilogram

DLMS Note:

GenComm equivalent code is K.

LB Pound

DLMS Note:

GenComm equivalent code is P.

LT Liter

DLMS Note:

GenComm equivalent code is L.

NS Short Ton

DLMS Note:

GenComm equivalent code is T.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 22 September 12, 2023

PKG Marking, Packaging, Loading Pos: 1000 Max: 25

Detail - Optional

Loop: HL Elements: 3

User Option (Usage): Used

Purpose: To describe marking, packaging, loading, and unloading requirements

Syntax Rules: 

1. R040506 - At least one of PKG04, PKG05 or PKG06 is required.

2. C0403 - If PKG04 is present, then PKG03 is required.

3. C0501 - If PKG05 is present, then PKG01 is required.

Semantics: 

1. PKG04 should be used for industry-specific packaging description codes.

Comments: 

1. Use the MEA (Measurements) Segment to define dimensions, tolerances, weights, counts, physical restrictions, etc.

2. If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and

PKG05 are used.

3. Use PKG03 to indicate the organization that publishes the code list being referred to.

4. Special marking or tagging data can be given in PKG05 (description).

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

PKG01 349 Item Description Type

Description: Code indicating the format of a

description

O ID 1/1 Used

Code Name

F Free-form

PKG02 753 Packaging Characteristic Code

Description: Code specifying the marking,

packaging, loading and related characteristics being

described

O ID 1/5 Used

Code Name

CB Container Type

DLMS Note:

Use in the HL03 code W loop to provide a narrative of the container type and its associated container

volume (e.g., 55 gallon drum).

PKG05 352 Description

Description: A free-form description to clarify the

related data elements and their content

O AN 1/80 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 23 September 12, 2023

TD5 Carrier Details (Routing

Sequence/Transit Time)

Pos: 1200 Max: 12

Detail - Optional

Loop: HL Elements: 1

User Option (Usage): Used

Purpose: To specify the carrier and sequence of routing and provide transit time information

Syntax Rules: 

1. R0204050612 - At least one of TD502, TD504, TD505, TD506 or TD512 is required.

2. C0203 - If TD502 is present, then TD503 is required.

3. C0708 - If TD507 is present, then TD508 is required.

4. C1011 - If TD510 is present, then TD511 is required.

5. C1312 - If TD513 is present, then TD512 is required.

6. C1413 - If TD514 is present, then TD513 is required.

7. C1512 - If TD515 is present, then TD512 is required.

Semantics: 

1. TD515 is the country where the service is to be performed.

Comments: 

1. When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use

TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence,

specified by the party identified in TD502.

DLMS Note:

Use only in 2/HL/0100 shipment status loop to identify the mode of shipment.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

TD504 91 Transportation Method/Type Code

Description: Code specifying the method or type of

transportation for the shipment

DLMS Note: 1. Use to identify the method of

shipment.

2. DLMS users see the Transportation Method/Type

Code Conversion Guide for available codes.

X ID 1/2 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 24 September 12, 2023

REF Reference Identification Pos: 1500 Max: >1

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

1. R0203 - At least one of REF02 or REF03 is required.

Semantics: 

1. REF04 contains data relating to the value cited in REF02.

DLMS Note:

1. Must use in 2/HL/0100 shipment status loop to identify the transaction document number and the transportation control number. Repeat

the REF segment within each shipment status loop to identify relevant information.

2. Use in 2/HL/0100 IUID loop to provide IUID information. Repeat the REF segment within each IUID loop to identify relevant IUID

information.

3. Use in applicable 2/HL/0100 RFID loops to provide the tag identification. Begin a new RFID loop to create a nested relationship between

tags at different layers of packaging.

4. This transaction supports unique item identification based upon the UII. Pending full transition to DoD IUID Supply Policy using the UII,

shipment status will be prepared using both the UII and corresponding serial number when available and required by DoD IUID Supply

Policy. See ADC 1030.

5. This transaction will support association of the IUID information with the RFID tag at the IUID packaging level and/or at each higher level

of packing which has been tagged.

6. Use this segment to comply with the DoD SLOA/Accounting Classification. Cost object elements Project Identifier, Funding Center

Identifier, Functional Area, Cost Element Code, Cost Center Identifier, Activity Identifier, and Work Order Number are used as appropriate

for the system. Refer to ADC 1043.

7. In support of Financial Improvement and Audit Readiness (FIAR) compliance, capital equipment candidates require serialization data

visibility. Prepare shipment status using the serial number. Include the UII when available. Refer to ADC 1198.

8. Under DOD IUID policy, UIT programs require serialization data visibility. Prepare shipment status with the serial number as mandatory

and when available, include the UII. Refer to ADC 1244.

1. Must use in 2/HL/0100 shipment status loop to identify the transaction document number and the transportation control number. Repeat

the REF segment within each shipment status loop to identify relevant information.

2. Use in 2/HL/0100 IUID loop to provide IUID information. Repeat the REF segment within each IUID loop to identify relevant IUID

information.

3. Use in applicable 2/HL/0100 RFID loops to provide the tag identification. Begin a new RFID loop to create a nested relationship between

tags at different layers of packaging.

4. This transaction supports unique item identification based upon the UII. Pending full transition to DoD IUID Supply Policy using the UII,

shipment status will be prepared using both the UII and corresponding serial number when available and required by DoD IUID Supply

Policy. See ADC 1030.

5. This transaction will support association of the IUID information with the RFID tag at the IUID packaging level and/or at each higher level

of packing which has been tagged.

6. Use this segment to comply with the DoD SLOA/Accounting Classification. Cost object elements Project Identifier, Funding Center

Identifier, Functional Area, Cost Element Code, Cost Center Identifier, Activity Identifier, and Work Order Number are used as appropriate

for the system. Refer to ADC 1043.

7. In support of Financial Improvement and Audit Readiness (FIAR) compliance, capital equipment candidates require serialization data

visibility. Prepare shipment status using the serial number. Include the UII when available. Refer to ADC 1198.

8. Under DOD IUID policy, UIT programs require serialization data visibility. Prepare shipment status with the serial number as mandatory

and when available, include the UII. Refer to ADC 1244.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

REF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: 1. Use codes separately or in

combination, to identify appropriate information for

DoD IUID Supply Policy, including, but not limited to

unique item tracking (UIT) programs. See ADC

1030.

DLMS Note: 1. Use codes separately or in

combination, to identify appropriate information for

DoD IUID Supply Policy, including, but not limited to

unique item tracking (UIT) programs. See ADC

1030.

2. The following codes are authorized.

M ID 2/3 Must use

Code Name

2E Foreign Military Sales Case Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Case Designator”.

Refer to ADC 1043.

2. For DLA Disposition Services shipment status for field office relocation of FMS requisitioned materiel

with associated freeze action pending approval, use to identify the Security Cooperation Case 
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 25 September 12, 2023

Designator. Refer to ADC 1156A

3. Authorized DLMS enhancement; see introductory DLMS note 2f.

2I Tracking Number

DLMS Note:

1. Use to identify all shipments to a DLA Disposition Services that qualify for in-transit control

procedures (e.g., the shipped materiel line item value is $800 or more or the item is recorded as

pilferable/sensitive). Cite Y in REF02 if shipment meets specified criteria.

2. DLMS enhancement; see introductory DLMS 2a.

60 Account Suffix Code

DLMS Note:

Use in conjunction with the DTID Number (REF04 Code W1) to identify the DTID Suffix Code, when

applicable. DLMS enhancement, see ADC 466.

79 Cost Account

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Cost Center Identifier”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

86 Operation Number

DLMS Note:

1. Use to identify the Key Operation (KO) Number associated with the JO. 

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

91 Cost Element

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Cost Element Code”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

98 Container/Packaging Specification Number

DLMS Note:

For DLA Disposition Service Field Office shipments issued from a Disposition Services Container, use

in the HL03 code CN loop to enter the Container Number associated with the DTID. Separate shipment

status transactions will be provided for each DTID identified to a specific Container. DLMS

enhancement, see ADC 422.

9R Job Order Number

DLMS Note:

1. Use to identify Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

9X Account Category

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Functional Area”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

AN Associated Purchase Orders

DLMS Note:

Use for cross-reference to the customer’s internal Purchase Order (PO) Number (one PO Number per

document number). Authorized for DLA-directed shipments to the Exchange, NEXCOM, MCX, and

non-DoD customers as required. See ADC 473A.

BE Business Activity

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Activity Identifier”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 2f.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 26 September 12, 2023

BT Batch Number

DLMS Note:

1. Use in IUID loop to identify the manufacturer's batch/lot number or other number identifying the

production run.

2. DLMS enhancement; see introductory DLMS 2a.

CO Customer Order Number

DLMS Note:

1. Use to identify the Customer Order Acceptance Record (COAR) applicable to the Job Order Number.

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381

(or as applicable).

CT Contract Number

DLMS Note:

Use in the HL03 code W loop when identifying the contract number. When procurement is authorized

under a contract number. This is not to be confused with a PIID.

DP Department Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Department Regular”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

FG Fund Identification Number

DLMS Note:

1. Use to identify the fund purpose code. Cite any fund purpose code in REF02 except code CR or DR. 

2. When identifying a Fund Code using REF04, identification of the fund purpose code is required to

meet syntax rules and structured format designed to support future enhancement of

appropriation/funding data. 

FU Fund Code

DLMS Note:

Use to accommodate legacy system requirements. Use in Lateral Referral Order (LRO) shipment

status to identify the fund code to be reimbursed for the materiel and reimbursement for the packaging,

crating, handling and transportation (PCH&T) cost is to be provided.

HD Department of Transportation Hazardous Number

DLMS Note:

Use when the HL03 Code is W to identify the Hazard Class.

JB Job (Project) Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Project Identifier”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

JH Tag

DLMS Note:

1. Use in applicable RFID loop to identify the RFID tag. The RFID will be reflected as a hexadecimal

value.

2. Future enhancement: Use in the IUID loop when an RFID tag is applied to the individual item. 

3. DLMS enhancement; see introductory DLMS 2a.

LI Line Item Identifier (Seller's)

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Case Line Item

Identifier”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 2f.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 27 September 12, 2023

M1 Material Storage Location

DLMS Note:

Use when the HL03 code CN loop to identify the Storage Location Code, as a location within a

warehouse.

MS Manufacturer's Material Safety Data Sheet Number

DLMS Note:

Use when the HL03 code W loop to identify the Safety Data Sheet Number.

PA Price Area Number

DLMS Note:

1. Use for shipments to disposal to indicate actual or estimated pricing information.

2. Available for all other shipment status as an optional data field to perpetuate the actual or estimated

unit price from the associated supply status or materiel release order. This is an authorized DLMS

enhancement.

3. A field size exceeding 7 positions (5 digits dollars and 2 digits cents) may not be received or

understood by the recipient’s automated processing system.

4. DLMS transactions authorize an expanded unit price field size of 9 digits for dollars and 2 digits for

cents. The decimal point is passed in the transaction. If conversion to MILS legacy format is required,

unit prices exceeding the legacy field size constraint will not be perpetuated. Authorized DLMS

migration enhancement; see introductory DLMS 2f. Refer to ADC 221A.

5. Use to identify the unit of use price when the unit of use indicator (1/BSN01/0200) is present.

Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

1. Use for shipments to disposal to indicate actual or estimated pricing information.

2. Available for all other shipment status as an optional data field to perpetuate the actual or estimated

unit price from the associated supply status or materiel release order. This is an authorized DLMS

enhancement.

3. A field size exceeding 7 positions (5 digits dollars and 2 digits cents) may not be received or

understood by the recipient’s automated processing system.

4. DLMS transactions authorize an expanded unit price field size of 9 digits for dollars and 2 digits for

cents. The decimal point is passed in the transaction. If conversion to MILS legacy format is required,

unit prices exceeding the legacy field size constraint will not be perpetuated. Authorized DLMS

migration enhancement; see introductory DLMS 2f. Refer to ADC 221A.

5. Use to identify the unit of use price when the unit of use indicator (1/BSN01/0200) is present.

Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

Q9 Repair Order Number

DLMS Note:

Identifies the Associated Commercial Asset Visibility (CAV) Repair Document Number. Use to cite the

appropriate repair document number (i.e., CAV Repair Cycle Document Number or CAV-Organic

Repair Module (CAV-ORM) Repair Component Document Number), depending upon applicability. Must

use for CAV shipment status to indicate the unique CAV Repair Cycle Document Number. A ‘POS’ is

created for each item citing that item's unique CAV Repair Document Number (e.g., N994179077002).

Refer to ADC 344 and ADC 461.

Identifies the Associated Commercial Asset Visibility (CAV) Repair Document Number. Use to cite the

appropriate repair document number (i.e., CAV Repair Cycle Document Number or CAV-Organic

Repair Module (CAV-ORM) Repair Component Document Number), depending upon applicability. Must

use for CAV shipment status to indicate the unique CAV Repair Cycle Document Number. A ‘POS’ is

created for each item citing that item's unique CAV Repair Document Number (e.g., N994179077002).

Refer to ADC 344 and ADC 461.

QR Quality Report Number

DLMS Note:

1. When applicable, use to cite the associated PQDR report control number (RCN) for exhibit tracking.

2. Authorized DLMS enhancement. Refer to ADC 1007.

SE Serial Number

DLMS Note:

1. Use in IUID loop to identify the serial number. See ADC 1030.

2. DLA Distribution must use in shipment of items designated as capital equipment candidates. All

others use in accordance with Component guidance for capital equipment. See ADC 1198.

3. Must use in shipment of UIT program items. Refer to ADC 1244.

4. The serial number may not exceed 30 characters and may only include alpha numeric characters,

dashes and forward slashes. Spaces are not allowed. 

5. DLMS enhancement; see introductory DLMS Note 2f.

1. Use in IUID loop to identify the serial number. See ADC 1030.

2. DLA Distribution must use in shipment of items designated as capital equipment candidates. All

others use in accordance with Component guidance for capital equipment. See ADC 1198.

3. Must use in shipment of UIT program items. Refer to ADC 1244.

4. The serial number may not exceed 30 characters and may only include alpha numeric characters,

dashes and forward slashes. Spaces are not allowed. 

5. DLMS enhancement; see introductory DLMS Note 2f.

SI Shipper's Identifying Number for Shipment (SID)

DLMS Note:

1. Must use in CAV shipment status (BSN06=WTP) to identify the contractor-assigned shipment

number as shown on the shipping documentation. Normally applicable to a Materiel and Inspection

Receiving Report (DD 250), but may apply to a DD 1348-1A employed by CAV contractors.

2. The shipment number may be 7 or 8 positions. If 8, the last position must be Z, indicating final

shipment.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 28 September 12, 2023

3. Authorized DLMS enhancement; see introductory DLMS 2a.

TF Transfer Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Department Transfer”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

TG Transportation Control Number (TCN)

DLMS Note:

1. Use in 2/HL/0100 transaction reference number loop to identify the shipment unit TCN.

2. DLMS enhancement for shipments to disposal and shipments from Army Total Package Fielding Unit

Materiel Fielding Points and staging sites.

TN Transaction Reference Number

DLMS Note:

1. Must use in the 2/HL/0100 shipment status loop to identify the customer assigned document number

associated with the shipment unit. Use REF04 to identify the associated suffix code if applicable.

2. When status is applicable to a requisition alert, this field will perpetuate the alert document number. 

Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

TT Terminal Code

DLMS Note:

Use only during legacy MILSTRIP-to-DLMS conversion processing to identify the point of embarkation

for OCONUS shipments moving through the DTS, GBL/CBL, parcel post (except APO/FPO); and small

package carrier shipments entering DTS and the POE. During the transition period, transactions

originating as MILSTRIP DIC AS_, Shipment Status, will carry the POE in this field due to the

translator's inability to distinguish among code types. Refer to 2/LQ01/3500 qualifiers 36, Air Terminal

Identifier Code, 37, Water Terminal Identifier, and 38, Consolidation and Containerization Point Code,

for DLMS input. 

Use only during legacy MILSTRIP-to-DLMS conversion processing to identify the point of embarkation

for OCONUS shipments moving through the DTS, GBL/CBL, parcel post (except APO/FPO); and small

package carrier shipments entering DTS and the POE. During the transition period, transactions

originating as MILSTRIP DIC AS_, Shipment Status, will carry the POE in this field due to the

translator's inability to distinguish among code types. Refer to 2/LQ01/3500 qualifiers 36, Air Terminal

Identifier Code, 37, Water Terminal Identifier, and 38, Consolidation and Containerization Point Code,

for DLMS input. 

U3 Unique Supplier Identification Number (USIN)

DLMS Note:

1. Use in IUID loop to identify the UII value in REF03. See ADC 1030. A data maintenance action was

approved in version 5020. The approved code/name is "UII - Department of Defense Unique Item

Identifier”.

2. DLA Distribution must use in shipment of items designated as capital equipment candidates when the

item has been marked under IUID policy. All others use in accordance with Component guidance for

capital equipment. See ADC 1198.

3. Must use in shipment of UIT program items when the item has been marked under IUID policy. 

Refer to ADC 1244.

4. DLMS enhancement; see introductory DLMS Note 2f.

1. Use in IUID loop to identify the UII value in REF03. See ADC 1030. A data maintenance action was

approved in version 5020. The approved code/name is "UII - Department of Defense Unique Item

Identifier”.

2. DLA Distribution must use in shipment of items designated as capital equipment candidates when the

item has been marked under IUID policy. All others use in accordance with Component guidance for

capital equipment. See ADC 1198.

3. Must use in shipment of UIT program items when the item has been marked under IUID policy. 

Refer to ADC 1244.

4. DLMS enhancement; see introductory DLMS Note 2f.

UN United Nations Hazardous Classification Number

DLMS Note:

Use when the HL03 Code W loop to identify the UN/NA Number.

WO Work Order Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Work Order Number”.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

X9 Internal Control Number

DLMS Note:

Contractor’s Reference Number is used to indicate the unique number used by the CAV II System to

identify and track EDI transactions. Refer to ADC 344. 

AGY Agency Disbursing Identifier Code

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Agency Disbursing Identifier Code”. Refer

to ADC 1043.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 29 September 12, 2023

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

3. Qualifier AGY is a migration code approved for use in X12 version 7020.

AGZ Agency Accounting Identifier

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Agency Accounting Identifier”. Refer to

ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

3. Qualifier AGZ is a migration code approved for use in X12 version 7020.

AVT Availability Type

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Availability Type”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

3. Qualifier AVT is a migration code approved for use in X12 version 7020.

BET Business Event Type Code

DLMS Note:

1. Reserved for DoD SLOA/Accounting Classification use to identify “Business Event Type Code”. 

Refer to ADC 1043.

2. Business Event Type Code is a potential future DLMS enhancement; see introductory DLMS note 2a.

3. Qualifier BET is a migration code approved for use in X12 version 7020.

BLI Budget Line Item

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Budget Line Item”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

3. Qualifier BLI is a migration code approved for use in X12 version 7020.

CAL U.S. Environmental Protection Agency (EPA) Hazardous Waste Code

DLMS Note:

1. Use when the HL03 code HE loop to identify the EPA Waste Code.

2. A data maintenance action was approved in version 4040. The approved code/name is “CAL – U.S.

Environmental Protection Agency (EPA) Hazardous Waste Code”.

CAN State Hazardous Waste Code

DLMS Note:

1. Use when the HL03 code ST loop to identify the State Waste Code.

2. At this time a local code ‘CAN’ is established for use in the 856S, version 4030. A data maintenance

action will be submitted for establishment of ‘CAN – State Hazardous Waste Code’ in a future version.

ECA Fund Identifier

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Funding Center Identifier”. Refer to ADC

1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

EVI Event Identification

DLMS Note:

Use for DLA Disposition Services PMR for relocation of FMS requisitioned materiel with associated

freeze action pending approval. The only applicable value for this transaction is Code F=Freeze

Indicator. Refer to ADC 1156.

HIN Hazardous Identification Number
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 30 September 12, 2023

DLMS Note:

1. Use in the HL03 code W loop to identify the type of waste or service action. This data element is not

to be used to convey the CLIN, which is a separate data element in this transaction.

2. At this time a local code ‘HIN’ is established for use in the 856S, version 4030. A data maintenance

action will be submitted for establishment of ‘HIN – Hazardous Identification Number’ in a future version.

MAT Main Account

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Main Account”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

3. Qualifier MAT is a migration code approved for use in X12 version 7020.

PGC Packing Group Code

DLMS Note:

Use in the HL03 Code W loop to identify the Packing Group (e.g., I, II, III).

PWC Preliminary Work Candidate Number

DLMS Note:

1. Use to identify a Requisition Alert Document Number when status is provided on the associated

funded requisition. 

2. Used in support of Navy Shipyards to associate the funded requisition with a previously submitted

requisition alert. 

3. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

REB Reimbursable Code

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Reimbursable Flag”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

3. Qualifier REB is a migration code approved for use in X12 version 7020.

SAT Sub Account

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Sub Account”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

3. Qualifier SAT is a migration code approved for use in X12 version 7020.

SBA Sub-Allocation

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Sub-Allocation (formerly known as

Limit/Subhead)”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

3. Qualifier SBA is a migration code approved for use in X12 version 7020.

SCC Security Cooperation Customer Code

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Customer Code”. 

Refer to ADC 1043.

2. Also applicable to DLA Disposition Services shipment status for field office relocation of FMS

requisitioned materiel with associated freeze action pending approval. Refer to ADC 1156.

3. DLMS enhancement; see introductory DLMS note 2d. A field size exceeding 2 positions is not

supportable under current MILSTRIP and MAPAC processes. Three character codes are not authorized

at this time.

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Customer Code”. 

Refer to ADC 1043.

2. Also applicable to DLA Disposition Services shipment status for field office relocation of FMS

requisitioned materiel with associated freeze action pending approval. Refer to ADC 1156.

3. DLMS enhancement; see introductory DLMS note 2d. A field size exceeding 2 positions is not

supportable under current MILSTRIP and MAPAC processes. Three character codes are not authorized

at this time.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 31 September 12, 2023

4. Qualifier SCC is a migration code approved for use in X12 version 7020.

SCI Security Cooperation Implementing Agency

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Implementing

Agency”. Refer to ADC 1043.

2. Also applicable to DLA Disposition Services shipment status for field office relocation of FMS

requisitioned materiel with associated freeze action pending approval. Refer to ADC 1156.

3. Authorized DLMS enhancement; see introductory DLMS note 2f. A field size exceeding 3 positions is

not supportable under current MILSTRIP processes. Four character codes are not authorized at this

time.

4. Qualifier SCI is a migration code approved for use in X12 version 7020.

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Implementing

Agency”. Refer to ADC 1043.

2. Also applicable to DLA Disposition Services shipment status for field office relocation of FMS

requisitioned materiel with associated freeze action pending approval. Refer to ADC 1156.

3. Authorized DLMS enhancement; see introductory DLMS note 2f. A field size exceeding 3 positions is

not supportable under current MILSTRIP processes. Four character codes are not authorized at this

time.

4. Qualifier SCI is a migration code approved for use in X12 version 7020.

SCL Sub Class

DLMS Note:

1. Reserved for DoD SLOA/Accounting Classification use to identify “Sub Class”. Refer to ADC 1043.

2. Sub Class is a potential future DLMS enhancement; see introductory DLMS note 2a.

3. Qualifier SCL is a migration code approved for use in X12 version 7020.

WPN Waste Disposal Number

DLMS Note:

1. Use in the HL03 code W loop to identify the Waste Profile Sheet Number.

2. A data maintenance action was approved in version 8010. The approved code/name is “WPN –

Waste Disposal Number”. This is an authorized DLMS enhancement.

XX4 Object Code

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Object Class”. Refer to ADC 1043.

2. Qualifier XX4 is a migration code approved for use in X12 version 4040.

3. Authorized DLMS enhancement; see introductory DLMS note 2f.

REF02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

X AN 1/50 Used

REF03 352 Description

Description: A free-form description to clarify the

related data elements and their content

DLMS Note: 1. Use with REF01 code FG and

REF04 code AT to cite the supplemental accounting

classification data.

2. Use to indicate UII value when REF01=U3.

3. DLMS enhancement; see introductory DLMS 2a.

X AN 1/80 Used

REF04 C040 Reference Identifier

Description: To identify one or more reference

numbers or identification numbers as specified by

the Reference Qualifier

DLMS Note: 1. Use REF04 to associate data with

the REF01. When needed, use codes from

REF04-01 and the next available combination of

data element 128/127 pairs to provide the

necessary data.

DLMS Note: 1. Use REF04 to associate data with

the REF01. When needed, use codes from

REF04-01 and the next available combination of

data element 128/127 pairs to provide the

necessary data.

O Comp Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F856S3SA51 32 September 12, 2023

2. When providing financial data (REF01 is code

FG):

If providing only the fund code use REF04-01 code

FU and cite the fund code in REF04-02. For

example: REF01=FG; REF02=FC; REFO4-01

(composite)=FU; REF04-02= fund code value.

If providing only the long line accounting data use

REF04-01 code AT and cite the basic appropriation

data in REF04-02. Use REF04-03 code 10 and cite

the accounting station number in REF04-04. 

If providing both, use REF04-01 code FU,

REF04-03 code AT, and REF04-05 code 10 citing

the related data in the second data element of the

pair.

REF04-01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: 1. Use one of codes 08, AW, BL, BM,

IZ, K2, K3, ZH, or WY with REF01 code TG (TCN)

to identify a secondary transportation number. 

Where applicable, two secondary transportation

numbers may be provided, e.g. for CAV shipment

status the carrier tracking number (PRO) may be

identified in REF04-01 and the bill of lading number

(commercial or Government) may be identified in

REF04-02.

DLMS Note: 1. Use one of codes 08, AW, BL, BM,

IZ, K2, K3, ZH, or WY with REF01 code TG (TCN)

to identify a secondary transportation number. 

Where applicable, two secondary transportation

numbers may be provided, e.g. for CAV shipment

status the carrier tracking number (PRO) may be

identified in REF04-01 and the bill of lading number

(commercial or Government) may be identified in

REF04-02.

2. For CAV shipment status, must use to identify the

procurement document which authorized the

commercial contractor to repair and ship GFP into

DoD inventories. Use with contractor-assigned

shipment number (REF01 Code SI).

3. Under ADC 1014, GFP contract data is

transitioned from the REF segment to the GF

Segment. Delayed implementation is authorized.

M ID 2/3 Must use

Code Name

08 Carrier Assigned Package Identification Number

DLMS Note:

1. Use to identify carrier tracking (PRO) number (when carrier is other than the United States Postal

Service). Use recommended in conjunction with identification of the carrier (2/N101/2200 qualifier CA).

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

10 Account Managers Code

DLMS Note:

1. Use in one of REF04-03 or REF04-05 to identify the authorized accounting activity (AAA)/accounting

disbursing station number (ADSN)/fiscal station number (FSN).

2. DLMS enhancement; see introductory DLMS 2a.

AT Appropriation Number

DLMS Note:

1. Use in one of REF04-01 or REF04-03 to identify the basic appropriation data.

2. DLMS enhancement; see introductory DLMS 2a.

AW Air Waybill Number

DLMS Note:

1. Use to identify the shipment unit air waybill number.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 33 September 12, 2023

BL Government Bill of Lading

DLMS Note:

1. Use to identify the government bill of lading.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

BM Bill of Lading Number

DLMS Note:

1. Use to identify the shipment unit commercial bill of lading number.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

C7 Contract Line Item Number

DLMS Note:

Use when the HL03 code W loop to identify the Contract Line Item Number associated with the contract

number.

CT Contract Number

DLMS Note:

1. Must use for CAV shipment status, to identify the procurement instrument identifier (PIID) authorizing

repair/return of GFP. Use the legacy procurement instrument identification number (PIIN) pending

transition to the PIID. When procurement is authorized under a PIID call/order number (F in 9th

position), provide the value in the PIID field. For Other Transaction (OT) agreements, the type of

instrument (9th position of PIID) will be a 3 for Research OTs or 9 for Prototype and Production OTs.

Refer to ADC 1161A or ADC 1420.

2. Under ADC 1014, GFP contract information is transitioned from the REF segment to the GF

Segment. Delayed implementation is authorized. 

3. Authorized DLMS enhancement; see introductory DLMS 2a.

1. Must use for CAV shipment status, to identify the procurement instrument identifier (PIID) authorizing

repair/return of GFP. Use the legacy procurement instrument identification number (PIIN) pending

transition to the PIID. When procurement is authorized under a PIID call/order number (F in 9th

position), provide the value in the PIID field. For Other Transaction (OT) agreements, the type of

instrument (9th position of PIID) will be a 3 for Research OTs or 9 for Prototype and Production OTs.

Refer to ADC 1161A or ADC 1420.

2. Under ADC 1014, GFP contract information is transitioned from the REF segment to the GF

Segment. Delayed implementation is authorized. 

3. Authorized DLMS enhancement; see introductory DLMS 2a.

FU Fund Code

DLMS Note:

Use with REF01 code FG to identify the Fund Code. Use to accommodate legacy system requirements.

 Use in Lateral Referral Order (LRO) shipment status to identify the fund code to which the credit for the

materiel and reimbursement for the packaging, crating, handling and transportation (PCH&T) cost is to

be provided.

IZ Insured Parcel Post Number

DLMS Note:

1. Use to identify the shipment unit insured parcel post number.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

K1 Foreign Military Sales Notice Number

DLMS Note:

1. Use for Foreign Military Sales (FMS) shipments made on commercial bill of lading or commercial

collect bill of lading, to identify the shipment unit FMS notice number.

2. DLMS enhancement; see introductory DLMS 2a.

K2 Certified Mail Number

DLMS Note:

1. Use to identify the shipment unit certified mail number.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

K3 Registered Mail Number

DLMS Note:

1. Use to identify the shipment unit registered parcel post number.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

W1 Disposal Turn-In Document Number

DLMS Note:

1. Use to identify the DTID number when provided as a secondary reference number. The DTID 
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 34 September 12, 2023

number is used by DLA Disposition Services as a unique number to identify property that was turned

into a DLA Disposition Service Field Office. The value of the DTID may be the original turn-in

document number or may be a unique control number (UCN) assigned by the Field Office during receipt

processing when the original DTID number is not adequate to uniquely identify the property. DLMS

Enhancement, see ADC 422

2. For DLA Disposition Service Field Office shipments, when there is no Suffix Code associated with the

customer’s Document Number, enter the correlating DTID in the REF04-02. If there is a Suffix Code,

then enter the DTID in the REF04-04. DLMS enhancement, see ADC 422.

number is used by DLA Disposition Services as a unique number to identify property that was turned

into a DLA Disposition Service Field Office. The value of the DTID may be the original turn-in

document number or may be a unique control number (UCN) assigned by the Field Office during receipt

processing when the original DTID number is not adequate to uniquely identify the property. DLMS

Enhancement, see ADC 422

2. For DLA Disposition Service Field Office shipments, when there is no Suffix Code associated with the

customer’s Document Number, enter the correlating DTID in the REF04-02. If there is a Suffix Code,

then enter the DTID in the REF04-04. DLMS enhancement, see ADC 422.

W8 Suffix

DLMS Note:

1. Use with REF01 code TN to identify the transaction number suffix.

2. When used in association with the Requisition Alert Document Number (Qualifier PWC, above), this

will be the requisition alert document suffix. The Requisition Alert Document Number Suffix is an

authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

WY Waybill Number

DLMS Note:

1. Use to identify the shipment unit surface waybill number.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

ZH Carrier Assigned Reference Number

DLMS Note:

1. Use to identify the shipment unit express mail number.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

REF04-02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

M AN 1/50 Must use

REF04-03 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: For other valid codes, see REF04,

C04001.

X ID 2/3 Used

Code Name

OQ Order Number

DLMS Note:

1. Use for CAV shipment status to identify the legacy four-position call/order number associated with

the PIIN in (REF04-01 Code CT).

2. Do not use for the PIID call/order number. The PIID call/order number is mapped to REF01, Code

CT. Refer to ADC 1161A.

3. Under ADC 1014, GFP contract information is transitioned from the REF segment to the GF

Segment. Delayed implementation is authorized.

4. Authorized DLMS enhancement; see introductory DLMS 2a.

1. Use for CAV shipment status to identify the legacy four-position call/order number associated with

the PIIN in (REF04-01 Code CT).

2. Do not use for the PIID call/order number. The PIID call/order number is mapped to REF01, Code

CT. Refer to ADC 1161A.

3. Under ADC 1014, GFP contract information is transitioned from the REF segment to the GF

Segment. Delayed implementation is authorized.

4. Authorized DLMS enhancement; see introductory DLMS 2a.

W1 Disposal Turn-In Document Number

DLMS Note:

1. Use to identify the DTID number when provided as a secondary reference number. The DTID

number is used by DLA Disposition Services as a unique number to identify property that was turned

into a DLA Disposition Service Field Office. The value of the DTID may be the original turn-in

document number or may be a unique control number (UCN) assigned by the Field Office during receipt

processing when the original DTID number is not adequate to uniquely identify the property. DLMS

Enhancement, see ADC 422.

1. Use to identify the DTID number when provided as a secondary reference number. The DTID

number is used by DLA Disposition Services as a unique number to identify property that was turned

into a DLA Disposition Service Field Office. The value of the DTID may be the original turn-in

document number or may be a unique control number (UCN) assigned by the Field Office during receipt

processing when the original DTID number is not adequate to uniquely identify the property. DLMS

Enhancement, see ADC 422.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 35 September 12, 2023

2. For DLA Disposition Service Field Office shipments, when there is no Suffix Code associated with the

customer’s Document Number, enter the correlating DTID in the REF04-02. If there is a Suffix Code,

then enter the DTID in the REF04-04. DLMS enhancement, see ADC 422.

REF04-04 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

X AN 1/50 Used

REF04-05 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: For valid codes, see REF04, C04001.

X ID 2/3 Used

Code Name

BL Government Bill of Lading

DLMS Note:

1. Use to identify the government bill of lading.

2. Authorized DLMS enhancement.

BM Bill of Lading Number

DLMS Note:

1. Use to identify the shipment unit commercial bill of lading number.

2. Authorized DLMS enhancement.

C7 Contract Line Item Number

DLMS Note:

1. Must use for CAV shipment status with contract number (REF04-01 code CT) to identify the

application CLIN/SubCLIN.

2. Under ADC 1014, GFP contract information is transitioned from the REF segment to the GF

Segment. Delayed implementation is authorized. 

3. Authorized DLMS enhancement.

REF04-06 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

X AN 1/50 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 36 September 12, 2023

PER Administrative Communications

Contact

Pos: 1510 Max: 3

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To identify a person or office to whom administrative communications should be directed

Syntax Rules: 

1. P0304 - If either PER03 or PER04 is present, then the other is required.

2. P0506 - If either PER05 or PER06 is present, then the other is required.

3. P0708 - If either PER07 or PER08 is present, then the other is required.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

PER01 366 Contact Function Code

Description: Code identifying the major duty or

responsibility of the person or group named

M ID 2/2 Must use

Code Name

IC Information Contact

DLMS Note:

Use when the HL03 code W loop to identify the point of contact.

PER02 93 Name

Description: Free-form name

O AN 1/60 Used

PER03 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

O ID 2/2 Used

Code Name

AU Defense Switched Network

DLMS Note:

Use when the HL03 code W loop to identify the DSN phone number

EM Electronic Mail

DLMS Note:

Use when the HL03 code W loop to identify the email address.

TE Telephone

DLMS Note:

Use when the HL03 code W loop to identify the commercial phone number.

PER04 364 Communication Number

Description: Complete communications number

including country or area code when applicable

O AN 1/256 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 37 September 12, 2023

DTM Date/Time Reference Pos: 2000 Max: 10

Detail - Optional

Loop: HL Elements: 3

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

2. C0403 - If DTM04 is present, then DTM03 is required.

3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

DLMS Note:

1. Use in the 2/HL/0100 shipment status loop to identify dates associated with the shipment status.

2. Use in the 2/HL/0100 Finance loop to comply with DoD SLOA/Accounting Classification information requirements.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

DTM01 374 Date/Time Qualifier

Description: Code specifying type of date or time,

or both date and time

M ID 3/3 Must use

Code Name

011 Shipped

DLMS Note:

Use to identify the materiel shipment date, regardless of shipment method.

(Note: For pseudo shipment status transactions, the date generated is assigned as the shipped date.) 

051 Cumulative Quantity Start

DLMS Note:

Use to identify the accumulation start date when reported at the HL03 code W loop (DTID level) and CN

loop (Container level).

283 Funds Appropriation - Start

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Beginning Period of Availability Fiscal Year

Date”. Refer to ADC 1043.

2. Use as appropriate to represent Program Year. Availability Type Code must be “X”. Refer to ADC

1043B.

3. Authorized DLMS enhancement; see introductory DLMS note 2f.

284 Funds Appropriation - End

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Ending Period of Availability Fiscal Year

Date”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

369 Estimated Departure Date

DLMS Note:

Use to identify the Estimated Shipment Date (ESD) for turn-ins to disposal when the actual date is

unknown. See ADC 433

514 Transferred

DLMS Note:

1. Use to identify the materiel transfer date to the carrier if a delay occurs prior to actual shipment.

2. DLMS enhancement; see introductory DLMS note 2a.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 38 September 12, 2023

585 Report

DLMS Note:

Use when the HL03 code W loop to identify the waste profile established date.

999 Document Date

DLMS Note:

1. Must use for CAV shipment Status to identify the ‘Proof of Shipment Date.’ 2. This date identifies the preparation date on the supporting documentation for shipment from the

contractor’s plant. 

DTM02 373 Date

Description: Date expressed as CCYYMMDD

X DT 8/8 Used

DTM03 337 Time

Description: Time expressed in 24-hour clock time

as follows: HHMM, or HHMMSS, or HHMMSSD, or

HHMMSSDD, where H = hours (00-23), M = minutes

(00-59), S = integer seconds (00-59) and DD =

decimal seconds; decimal seconds are expressed

as follows: D = tenths (0-9) and DD = hundredths

(00-99)

DLMS Note: 1. Enter time shipped in “HHMMSS”

format (in conjunction DTM01, Qualifier 999) to

establish a unique date/time stamp. 

2. Must use for CAV shipment status. 

3. This is an authorized DLMS enhancement; see

introductory DLMS 2f.

X TM 4/8 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 39 September 12, 2023

N1 Name Pos: 2200 Max: 1

Detail - Optional

Loop: N1 Elements: 5

User Option (Usage): Used

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

DLMS Note:

1. Use to identify the organization originating and receiving the transaction. 

2. Use additional iterations to identify other organizations associated with the transaction.

3. Must use the 2/N1/2200 loop in the address loop to identify the organization originating the transaction.

4. Must use the 2/N1/2200 loop in the shipment status loop to identify the organization to receive the transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N101 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an individual

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

Code Name

BS Bill and Ship To

DLMS Note:

Use either this code, or both codes BT and ST, for reimbursable materiel. Use to identify the

organization which receives both the materiel and the billing for the materiel.

BT Bill-to-Party

DLMS Note:

Use with code ST for reimbursable materiel. Use to identify the organization to receive the billing for

materiel when different from the organization receiving the materiel. Use precludes the use of Code BS.

CA Carrier

DLMS Note:

1. Use as needed to identify the shipment unit carrier when other than the United States Postal Service.

2. The carrier may be identified by name (N102) and Standard Carrier Alpha Code (SCAC).

3. Authorized DLMS migration enhancement; see introductory DLMS 2f.

CS Consolidator

DLMS Note:

1. Use to identify the consolidation point DoDAAC when shipment status is provided by the CCP

(BSN07=061).

2. For non-MILS shipment (e.g., DD1149) status, (BSN07=014) in support of pRFID exchange, use to

identify the origin activity generating the shipment status. Refer to ADC 417.

DA Delivery Address
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 40 September 12, 2023

DLMS Note:

1. Use with 2/N2/2300, 2/N3/2400, and 2/N4/2500 to fully identify in-the-clear exception ship-to

address information under authorized conditions.

2. DLMS enhancement; see introductory DLMS note 2a.

GP Gateway Provider

DLMS Note:

1. Use for transition period to support transaction conversion in a mixed legacy MILSTRIP/DLMS

environment. Use to identify DAASC as originator during conversion when the legacy MILSTRIP

transaction does not contain a "From" organization (i.e. blank RIC on AS_). Use to identify DAASC as

the "TO" organization for Component-generated shipment status forwarded for DAAS distribution to

status recipients under MILSTRIP/DLMS distribution rules (DLMS equivalent of AS8).

2. DLMS enhancement required for compliance with design/syntax. (DAASC RIC not converted for use

on legacy MILSTRIP transactions). 

1. Use for transition period to support transaction conversion in a mixed legacy MILSTRIP/DLMS

environment. Use to identify DAASC as originator during conversion when the legacy MILSTRIP

transaction does not contain a "From" organization (i.e. blank RIC on AS_). Use to identify DAASC as

the "TO" organization for Component-generated shipment status forwarded for DAAS distribution to

status recipients under MILSTRIP/DLMS distribution rules (DLMS equivalent of AS8).

2. DLMS enhancement required for compliance with design/syntax. (DAASC RIC not converted for use

on legacy MILSTRIP transactions). 

HZ Hazardous Waste Generator

DLMS Note:

Use when the HL03 code V loop to identify the Hazardous Material/Hazardous Waste Generator’s File

Transfer DoDAAC. Use with code FR in the N106.

KK Registering Party

DLMS Note:

1. Use to identify the Component UIT registry. May be used by a Component when their UIT process

requires that a copy of the transaction also be sent to a UIT registry for information purposes. Must be

used with 2/N106/2200 code ‘PK-Party to Receive Copy’ to identify that this is only an information copy

of the transaction, for use with the Component UIT registry. 

2. DLMS enhancement. See introductory DLMS note 2.a. 

MF Manufacturer of Goods

DLMS Note:

1. Use in the shipment status loop to identify the manufacturer's name for nonstandard materiel (i.e.,

where part number and not NSN is used for materiel identification).

2. Use in IUID loop to identify the manufacturer of the identified item.

OB Ordered By

DLMS Note:

1. Use to identify the requisitioner.

2. DLMS enhancement; see introductory DLMS note 2a.

OW Owner of Property or Unit

DLMS Note:

Shipping activities must use to indicate the materiel owner when the recipient will not be the new

materiel owner. Authorized for all commodities and required for active UIT program items. See ADC

1244B

PW Pick Up Address

DLMS Note:

Use when the HL03 code V loop to identify the Pickup DoDAAC.

RN Repair or Refurbish Location

DLMS Note:

1. Must use for CAV shipment status to identify the CAV repair site. 

2. Use two iterations of the N1 Loop to identify the repair site by both RIC and DoDAAC. Associate the

Message From (N106) with the repair site RIC. Refer to ADC 344.

SB Storage Area

DLMS Note:

1. Use to identify the initial shipping activity.

2. For Army Total Package Fielding (TPF), use to identify the Routing Identifier of the Unit Materiel 
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 41 September 12, 2023

Fielding Point (UMFP) or staging site originating the UMFP shipment document.

 3. Use for LRO shipment status to identify the organization responsible for release of the retail assets.

4. For conversion processing this will be understood to be the originating activity as identified by the

Supplemental Address.

5. A DLMS enhancement allows specific separate identification of the party to receive credit and the

party originating the LRO shipment status/shipping the materiel. DoDAACs associated with qualifier SB

and ZB are expected to be the same at this time. However, when using originated in DLMS, the LRO

originator may be a different party and will be identified by a Routing Identifier. Refer to ADC 299.

6. When implemented as a DLMS enhancement in the shipment loop to allow specific separate

identification of owner/manager and storage activity RIC for ammunition and ammunition related

transactions, a second instance of the SB in the shipment loop must be used to identify the storage

activity by DoDAAC (N103 = 10). Refer to Approved Addendum to ADC 441A.

Fielding Point (UMFP) or staging site originating the UMFP shipment document.

 3. Use for LRO shipment status to identify the organization responsible for release of the retail assets.

4. For conversion processing this will be understood to be the originating activity as identified by the

Supplemental Address.

5. A DLMS enhancement allows specific separate identification of the party to receive credit and the

party originating the LRO shipment status/shipping the materiel. DoDAACs associated with qualifier SB

and ZB are expected to be the same at this time. However, when using originated in DLMS, the LRO

originator may be a different party and will be identified by a Routing Identifier. Refer to ADC 299.

6. When implemented as a DLMS enhancement in the shipment loop to allow specific separate

identification of owner/manager and storage activity RIC for ammunition and ammunition related

transactions, a second instance of the SB in the shipment loop must be used to identify the storage

activity by DoDAAC (N103 = 10). Refer to Approved Addendum to ADC 441A.

ST Ship To

DLMS Note:

1. Use to identify the organization to receive the materiel.

2. For shipment status in response to LROs (DIC AS6), use to identify the ship to activity as directed in

the LRO. Authorized DLMS enhancement. See ADC 1030.

3. Use for HL03 code V loop for disposal shipments use to identify the Disposition Services Field Office.

 For HM/HW shipments provide the RIC.

XN Planning/Maintenance Organization

DLMS Note:

1. Used to identify a Shop Service Center/Shop Store.

2. Use in conjunction with N103 Identification Code Qualifier 92.

3. Refer to ADCs 284A, 381, and 1454 for known applications.

Z1 Party to Receive Status

DLMS Note:

1. Use to indicate the organization to receive shipment status.

2. For shipment status forwarded for DAAS distribution to status recipients under MILSTRIP/DLMS

distribution rules (AS8), the recipients will be identified on the DAAS-generated transactions and will not

appear on the original transaction.

3. As a DLMS enhancement, may be used to identify recipients other than the prescribed status

recipients under DLMS/MILSTRIP distribution rules. Use multiple iterations of the 2/N1/2200 loop to

identify shipment recipients, as needed. Use with N106=TO to indicate that the value in N104 is

receiving the transaction. See introductory DLMS note 2a.

4. Use to provide shipment status to Product Data Reporting and Evaluation Program-Automated

Information System (PDREP-AIS) for PQDR exhibit tracking when the PQDR RCN is included. For use

with DoDAAC N45112. Refer to ADC 1007.

1. Use to indicate the organization to receive shipment status.

2. For shipment status forwarded for DAAS distribution to status recipients under MILSTRIP/DLMS

distribution rules (AS8), the recipients will be identified on the DAAS-generated transactions and will not

appear on the original transaction.

3. As a DLMS enhancement, may be used to identify recipients other than the prescribed status

recipients under DLMS/MILSTRIP distribution rules. Use multiple iterations of the 2/N1/2200 loop to

identify shipment recipients, as needed. Use with N106=TO to indicate that the value in N104 is

receiving the transaction. See introductory DLMS note 2a.

4. Use to provide shipment status to Product Data Reporting and Evaluation Program-Automated

Information System (PDREP-AIS) for PQDR exhibit tracking when the PQDR RCN is included. For use

with DoDAAC N45112. Refer to ADC 1007.

Z4 Owning Inventory Control Point

DLMS Note:

1. Use to identify the Routing Identifier of the supply source or applicable owner/manager as the

originator of the shipment status. This includes shipment status prepared by the Distribution Depot on

behalf of the owner/manager, for owner/manager directed shipments, and CCP/Consolidation shipment

status. Additionally, this includes shipment status prepared by Army storage activities on behalf of the

owner/manager for ammunition and ammunition related shipments.

2. Use to identify the recipient for LRO Shipment Status.

3. Use to identify the recipient Fielding Command for Army Total Package Fielding shipments.

1. Use to identify the Routing Identifier of the supply source or applicable owner/manager as the

originator of the shipment status. This includes shipment status prepared by the Distribution Depot on

behalf of the owner/manager, for owner/manager directed shipments, and CCP/Consolidation shipment

status. Additionally, this includes shipment status prepared by Army storage activities on behalf of the

owner/manager for ammunition and ammunition related shipments.

2. Use to identify the recipient for LRO Shipment Status.

3. Use to identify the recipient Fielding Command for Army Total Package Fielding shipments.

Z5 Management Control Activity

DLMS Note:

Use for submission of all GFM requisitions.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 42 September 12, 2023

Z7 Mark-for Party

DLMS Note:

1. Use to identify an entity located within the ship-to address that is to actually receive the materiel.

2. The Mark-for Party may be identified by DoDAAC, RIC, clear text, or a combination of these. Only

one of DoDAAC or RIC may be used.

3. Maximum length of the Mark-for Party is 24 positions: Mark-for clear text (with no DoDAAC or RIC)

displays on DoD shipment documents as two lines of 12 characters each. If text is combined with a

DoDAAC, up to 17 clear text characters will be allowed. If text is combined with a RIC, up to 20 clear

text characters will be allowed. A slash (/) will be inserted during printing of shipment documentation to

separate the DoDAAC or RIC from clear text; do not perpetuate the slash (/) in the DLMS transaction.

4. Authorized DLMS enhancement; see introductory DLMS note 2f. Refer to ADC 1009A.

1. Use to identify an entity located within the ship-to address that is to actually receive the materiel.

2. The Mark-for Party may be identified by DoDAAC, RIC, clear text, or a combination of these. Only

one of DoDAAC or RIC may be used.

3. Maximum length of the Mark-for Party is 24 positions: Mark-for clear text (with no DoDAAC or RIC)

displays on DoD shipment documents as two lines of 12 characters each. If text is combined with a

DoDAAC, up to 17 clear text characters will be allowed. If text is combined with a RIC, up to 20 clear

text characters will be allowed. A slash (/) will be inserted during printing of shipment documentation to

separate the DoDAAC or RIC from clear text; do not perpetuate the slash (/) in the DLMS transaction.

4. Authorized DLMS enhancement; see introductory DLMS note 2f. Refer to ADC 1009A.

ZB Party to Receive Credit

DLMS Note:

1. Use to identify the party to receive credit for materiel, transportation, and PC&H.

2. For conversion processing this will be the activity as identified by the Supplemental Address and the

same activity identified to release the materiel.

3. A DLMS enhancement allows specific separate identification of the party to receive credit and the

party originating the LRO shipment status/shipping the materiel. Refer to ADC 299.

4. Use for SFIS compliant systems to identify the BPN of the party to receive credit. BPN may only be

used when the corresponding DoDAAC is also provided. This will require a second iteration of the N1

loop with the same qualifier.

5. Authorized DLMS enhancement; see introductory DLMS note 2f.

1. Use to identify the party to receive credit for materiel, transportation, and PC&H.

2. For conversion processing this will be the activity as identified by the Supplemental Address and the

same activity identified to release the materiel.

3. A DLMS enhancement allows specific separate identification of the party to receive credit and the

party originating the LRO shipment status/shipping the materiel. Refer to ADC 299.

4. Use for SFIS compliant systems to identify the BPN of the party to receive credit. BPN may only be

used when the corresponding DoDAAC is also provided. This will require a second iteration of the N1

loop with the same qualifier.

5. Authorized DLMS enhancement; see introductory DLMS note 2f.

N102 93 Name

Description: Free-form name

DLMS Note: 1. Use with N101 code MF to identify

the manufacturer's name and address (including ZIP

code) when the CAGE is not available.

2. Use with N101 code DA to identify the exception

ship-to organization. Also use 2/N2/2300 if

additional information is required.

3. Use with N101 Code Z7 to identify the recipient of

materiel. Total field length is restricted to 24 clear

text characters, when not used in combination with a

DoDAAC or RIC. If combined with a Mark-for

DoDAAC, restrict clear text to 17 characters. If

combined with a Mark-for RIC, restrict clear text to

20 characters. Authorized DLMS enhancement; see

introductory DLMS note 2f. Refer to ADC 1009A.

3. Use with N101 Code Z7 to identify the recipient of

materiel. Total field length is restricted to 24 clear

text characters, when not used in combination with a

DoDAAC or RIC. If combined with a Mark-for

DoDAAC, restrict clear text to 17 characters. If

combined with a Mark-for RIC, restrict clear text to

20 characters. Authorized DLMS enhancement; see

introductory DLMS note 2f. Refer to ADC 1009A.

4. Use with N101 code CA to identify the carrier by

name. (Field length for DLMS is 60 positions.)

5. DLMS enhancement; see introductory DLMS note

2a.

X AN 1/60 Used

N103 66 Identification Code Qualifier

Description: Code designating the system/method

of code structure used for Identification Code (67)

DLMS Note: The following code are authorized.

X ID 1/2 Must use

Code Name

2 Standard Carrier Alpha Code (SCAC)

DLMS Note:

Use as needed to identify the commercial carrier.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 43 September 12, 2023

8 UCC/EAN Global Product Identification Prefix

DLMS Note:

Corresponds to IAC '0-9'.

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

1. Use as needed to identify the organizations listed to include: ship-to, bill-to, and shipping activity.

2. DLMS enhancement; see introductory DLMS note 2a.

33 Commercial and Government Entity (CAGE)

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element “Business Partner Number TP3”. Enter the seller’s BPN in

N104.

2. Authorized DLMS enhancement; see introductory DLMS note 2f.

92 Assigned by Buyer or Buyer's Agent

DLMS Note:

Use with N101 Code XN to identify the user assigned Shop Service Center/Shop Store Identifier. Refer

to ADCs 284A, 381, and 1454.

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

1. Use to indicate the SA structured address data. 

2. DLMS enhancement; see introductory DLMS note 2a.

M4 Department of Defense Routing Identifier Code (RIC)

UR Uniform Resource Locator (URL)

DLMS Note:

1. Use when appropriate to identify the Component UIT registry.

2. DLMS enhancement; see introductory DLMS note 2.a.

N104 67 Identification Code

Description: Code identifying a party or other code

X AN 2/80 Used

N106 98 Entity Identifier Code

Description: Code identifying an organizational

entity, a physical location, property or an individual

O ID 2/3 Used

Code Name

FR Message From

DLMS Note:

1. Must use with the appropriate 2/N101/2200 code to indicate the organization cited in N104 is sending

the transaction set.

2. For LRO shipment status, use with 2/N1/2200 code SB, otherwise use with code Z4 (or GP when

originator not known) to indicate the organization cited in N104 is originating the transaction.

PK Party to Receive Copy

DLMS Note:

1. Use when appropriate to send an information copy of the transaction to a Component UIT registry.

For use with N101 code KK.

2. DLMS enhancement. See introductory DLMS note 2.a.

TO Message To

DLMS Note:

1. Use with the appropriate 2/N101/2200 code to indicate the organization cited in N101 is receiving the

transaction set.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 44 September 12, 2023

2. Use with 2/N1/2200 code GP (for DAASC) or Z1 to indicate the organization cited in N104 is

receiving the transaction.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 45 September 12, 2023

N2 Additional Name Information Pos: 2300 Max: 2

Detail - Optional

Loop: N1 Elements: 2

User Option (Usage): Used

Purpose: To specify additional names or those longer than 35 characters in length

DLMS Note:

1. Use to identify additional name information as authorized.

2. Use with 2/N101/2200 code DA to identify additional in-the-clear exception ship-to name information.

3. DLMS enhancement; see introductory DLMS note 2a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N201 93 Name

Description: Free-form name

M AN 1/60 Must use

N202 93 Name

Description: Free-form name

O AN 1/60 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 46 September 12, 2023

N3 Address Information Pos: 2400 Max: 2

Detail - Optional

Loop: N1 Elements: 2

User Option (Usage): Used

Purpose: To specify the location of the named party

DLMS Note:

1. Use to identify additional address information as authorized.

2. Use with 2/N101/2200 code DA to identify additional in-the-clear exception ship-to name information.

3. DLMS enhancement; see introductory DLMS note 2a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N301 166 Address Information

Description: Address information

M AN 1/55 Must use

N302 166 Address Information

Description: Address information

O AN 1/55 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 47 September 12, 2023

N4 Geographic Location Pos: 2500 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Used

Purpose: To specify the geographic place of the named party

Syntax Rules: 

1. C0605 - If N406 is present, then N405 is required.

Comments: 

1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

2. N402 is required only if city name (N401) is in the U.S. or Canada.

DLMS Note:

1. Use to identify additional address information as authorized.

2. Use with 2/N101/2200 code DA to identify additional in-the-clear exception ship-to name information.

3. DLMS enhancement; see introductory DLMS note 2a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

N401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used

N402 156 State or Province Code

Description: Code (Standard State/Province) as

defined by appropriate government agency

X ID 2/2 Used

N403 116 Postal Code

Description: Code defining international postal

zone code excluding punctuation and blanks (zip

code for United States)

O ID 3/15 Used

N404 26 Country Code

Description: Code identifying the country

DLMS Note: Use to identify the country. See DLMS

introductory note 3 (Refer to ADC 1075 for

implementation).

X ID 2/3 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 48 September 12, 2023

SAC Service, Promotion, Allowance, or

Charge Information

Pos: 3200 Max: 1

Detail - Optional

Loop: SAC Elements: 4

User Option (Usage): Used

Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion,

allowance, or charge

Syntax Rules: 

1. R0203 - At least one of SAC02 or SAC03 is required.

2. P0304 - If either SAC03 or SAC04 is present, then the other is required.

3. P0607 - If either SAC06 or SAC07 is present, then the other is required.

4. P0910 - If either SAC09 or SAC10 is present, then the other is required.

5. C1110 - If SAC11 is present, then SAC10 is required.

6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.

7. C1413 - If SAC14 is present, then SAC13 is required.

8. C1615 - If SAC16 is present, then SAC15 is required.

Semantics: 

1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.

2. SAC05 is the total amount for the service, promotion, allowance, or charge.

3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.

4. SAC08 is the allowance or charge rate per unit. 

5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.

6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion,

allowance, or charge.

7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.

8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion.

9. SAC16 is used to identify the language being used in SAC15.

Comments: 

1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction with

SAC03 to further define SAC02.

2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance,

charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is

represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.

DLMS Note:

Use the SAC Loop to allow subsequent identification of the GFP contract information in the GF Segment.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

SAC01 248 Allowance or Charge Indicator

Description: Code which indicates an allowance or

charge for the service specified

M ID 1/1 Must use

Code Name

C Charge

SAC03 559 Agency Qualifier Code

Description: Code identifying the agency assigning

the code values

O ID 2/2 Used

Code Name

DL Defense Logistics Agency
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 49 September 12, 2023

SAC04 1301 Agency Service, Promotion, Allowance, or

Charge Code

Description: Agency maintained code identifying

the service, promotion, allowance, or charge

DLMS Note: 1. The following codes are authorized

for use: TDC - Total Disposal Cost 

2. Use when the HL03 code W loop to identify the

Total Disposal Cost.

O AN 1/10 Used

SAC05 610 Amount

Description: Monetary amount

O N2 1/15 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 50 September 12, 2023

GF Furnished Goods and Services Pos: 3300 Max: 1

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To specify information related to furnished material, equipment, property, information, and services

Syntax Rules: 

1. P0102 - If either GF01 or GF02 is present, then the other is required.

2. P0506 - If either GF05 or GF06 is present, then the other is required.

3. P0809 - If either GF08 or GF09 is present, then the other is required.

Semantics: 

1. GF04 is the value of government-furnished property.

DLMS Note:

1. Must use in GFP-related transactions. 

2. Use to provide contract information for shipments of GFP to the contractor.

3. Use for contractor shipment of GFP into DoD inventory. 

4. Authorized DLMS enhancement. Refer to ADC 1014.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

GF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

O ID 2/3 Used

Code Name

C7 Contract Line Item Number

DLMS Note:

Use as directed to associate a Contract Line Item Number with the Contract Number.

GF02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

O AN 1/50 Used

GF03 367 Contract Number

Description: Contract number

DLMS Note: Must use to identify the applicable

procurement instrument identifier (PIID). Use the

PIIN pending transition to the PIID. When GFP is

authorized under a PIID call/order number (F in 9th

position), provide the value in the PIID field. For

Other Transaction (OT) agreements, the type of

instrument (9th position of PIID) will be a 3 for

Research OTs or 9 for Prototype and Production

OTs. Refer to ADC 1161A or ADC 1420.

DLMS Note: Must use to identify the applicable

procurement instrument identifier (PIID). Use the

PIIN pending transition to the PIID. When GFP is

authorized under a PIID call/order number (F in 9th

position), provide the value in the PIID field. For

Other Transaction (OT) agreements, the type of

instrument (9th position of PIID) will be a 3 for

Research OTs or 9 for Prototype and Production

OTs. Refer to ADC 1161A or ADC 1420.

O AN 1/30 Used

GF07 328 Release Number

Description: Number identifying a release against a

Purchase Order previously placed by the parties

involved in the transaction

DLMS Note: 1. Use to identify the legacy

four-position call/order number associated with the

O AN 1/30 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F856S3SA51 51 September 12, 2023

PIIN. 

2. Do not use for the PIID call/order number. The

PIID call/order number is mapped to GF03. Refer to

ADC 1161A.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 52 September 12, 2023

LM Code Source Information Pos: 3400 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

Must use only in the 2/HL/0100 shipment status loop to identify coded information maintained in department or agency documentation.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LM01 559 Agency Qualifier Code

Description: Code identifying the agency assigning

the code values

M ID 2/2 Must use

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 53 September 12, 2023

LQ Industry Code Pos: 3500 Max: 100

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

DLMS Note:

Use to identify codes, as appropriate, consistent with management information requirements.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

LQ01 1270 Code List Qualifier Code

Description: Code identifying a specific industry

code list

DLMS Note: The following codes are authorized.

O ID 1/3 Used

Code Name

0 Document Identification Code

DLMS Note:

1. The legacy MILSTRIP DIC is retained in the DLMS to facilitate transaction conversion in a mixed

legacy MILSTRIP/DLMS environment. Continued support of the DIC in a full DLMS environment will be

assessed at a future date.

2. Navy unique Document Identifier POS is authorized for CAV shipment status.

3. Future streamlined data; see introductory DLMS note 2c.

36 Air Terminal Identifier Code

DLMS Note:

1. Use to identify port of embarkation (POE) air terminal identifier codes for Outside Continental United

States (OCONUS) shipments made via Defense Transportation System (DTS) air modes.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

3. During the legacy MILSTRIP/DLMS transition period, transactions originating as MILSTRIP DIC AS_, 

Shipment Status, will carry this information in REF01, qualifier TT, Terminal Code, due to the

translator's inability to distinguish among code types.

1. Use to identify port of embarkation (POE) air terminal identifier codes for Outside Continental United

States (OCONUS) shipments made via Defense Transportation System (DTS) air modes.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

3. During the legacy MILSTRIP/DLMS transition period, transactions originating as MILSTRIP DIC AS_, 

Shipment Status, will carry this information in REF01, qualifier TT, Terminal Code, due to the

translator's inability to distinguish among code types.

37 Water Terminal Identifier Code

DLMS Note:

1. Use to identify port of embarkation (POE) water terminal identifier codes for OCONUS shipments

made via DTS water modes.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

3. During the legacy MILSTRIP/DLMS transition period, transactions originating as MILSTRIP DIC AS_, 

Shipment Status, will carry this information in REF01, qualifier TT, Terminal Code, due to the

translator's inability to distinguish among code types.

1. Use to identify port of embarkation (POE) water terminal identifier codes for OCONUS shipments

made via DTS water modes.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

3. During the legacy MILSTRIP/DLMS transition period, transactions originating as MILSTRIP DIC AS_, 

Shipment Status, will carry this information in REF01, qualifier TT, Terminal Code, due to the

translator's inability to distinguish among code types.

38 Consolidation and Containerization Point Code

DLMS Note:

1. Used to identify the SEAVAN CCP code for OCONUS shipments made via DTS. 

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

3. During the legacy MILSTRIP/DLMS transition period, transactions originating as MILSTRIP DIC AS_, 

Shipment Status, will carry this information in REF01, qualifier TT, Terminal Code, due to the 
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 54 September 12, 2023

translator's inability to distinguish among code types.

58 Transportation Bill Code

DLMS Note:

Use for FMS shipments, to identify the applicable shipment Transportation Bill Code (TBC).

67 Type of Assistance Code

DLMS Note:

1. For Security Assistance (SA) transactions, use only when the coded address in the transaction

number does not identify the type of assistance and financing.

2. DLMS enhancement; see introductory DLMS note 2a. 

78 Project Code

DLMS Note:

1. Must use to provide the project code when applicable.

2. Required when applicable to communicate the project code associated with the Army Total Package

Fielding Unit Materiel Fielding Point or staging site shipment document.

3. For DoD SLOA/Accounting Classification compliance (2/HL/0100 Finance loop) the Project Code

may be repeated as a Project Identifier (REF01 Qualifier JB). Refer to ADC 1043.

4. Authorized DLMS migration enhancement; see introductory DLMS 2f.

1. Must use to provide the project code when applicable.

2. Required when applicable to communicate the project code associated with the Army Total Package

Fielding Unit Materiel Fielding Point or staging site shipment document.

3. For DoD SLOA/Accounting Classification compliance (2/HL/0100 Finance loop) the Project Code

may be repeated as a Project Identifier (REF01 Qualifier JB). Refer to ADC 1043.

4. Authorized DLMS migration enhancement; see introductory DLMS 2f.

79 Priority Designator Code

DLMS Note:

1. Must use to identify the applicable priority designator.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

81 Status Code

DLMS Note:

1. Use to identify additional status information related to the shipment unit.

2. For shipment status other than those resulting from conversion from the legacy MILSTRIP ASY this is

a DLMS enhancement; see introductory DLMS note 2a.

83 Supply Condition Code

DLMS Note:

1. For turn-ins to a DLA Disposition Services Field Office, the supply condition code is mandatory. 

DLMS enhancement, see ADC 422 and 1399.

2. For all other shipments, this is an authorized DLMS enhancement; see introductory DLMS note 2f.

84 Management Code

DLMS Note:

1. Use to communicate the management code associated with Army Total Package Fielding Unit

Materiel Fielding Point or staging site shipment document. 

2. DLMS Component-unique enhancement. See introductory DLMS note 5e.

88 Disposal Authority Code

DLMS Note:

For Hazardous Materiel/Hazardous Waste turn-ins to a DLA Disposition Service Field Office, enter the

disposal authority code to indicate that the designated materiel is authorized for shipment to a DLA

Disposition Service Field Office per the Generator Communication (GenComm) Standard. DLMS

enhancement, see ADC 422.

89 Cooperative Logistics Program Support Code

DLMS Note:

1. For FMS transactions, must use to identify programmed, nonprogrammed, and termination/drawdown

requirements.

2. DLMS enhancement; see introductory DLMS note 2a. 

92 Reason for Disposal Code
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 55 September 12, 2023

DLMS Note:

1. Use for materiel transferred to a Defense Reutilization and Marketing Service (DRMS) to identify the

reason for transfer of the shipment unit.

2. DLMS enhancement; see introductory DLMS note 2a. 

93 Type of Storage Code

DLMS Note:

1. Use to identify the minimum level of storage environment required for shipment unit.

2. DLA Disposition Services uses three to five position alphanumeric code to identify building number of

the pickup DODAAC. Use LQ02 to identify the Storage Building Number. Refer to ADC 1428.

3. DLMS enhancement; see introductory DLMS Note 2a. 

94 Identification Code

DLMS Note:

1. Use in FMS transactions to identify the customer country's requisitioning Service Code: B, D, K, P, or

T. This is the SA program Customer Service Designator (codes derived from Qualifier 71, Service and

Agency Code). A DM has been submitted to create a new qualifier for this data element.

2. DLMS enhancement; see introductory DLMS note 2a.

95 Offer and Release Option Code

DLMS Note:

1. For FMS transactions, must use to advise the supply source of the type of notice required prior to

shipping the materiel.

2. DLMS enhancement; see introductory DLMS note 2a. 

98 Reason for Requisitioning Code

DLMS Note:

1. Use to identify Reason for Requisitioning Code identifying the use of the materiel. 

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

A2 Customer Within Country Code

DLMS Note:

1. For SA transactions, use only when the coded address in the transaction number does not identify

the customer-within-country.

2. DLMS enhancement; see introductory DLMS note 2a. 

A3 Delivery Term Code

DLMS Note:

1. For FMS transactions, use only when the coded address in the transaction number does not identify

the delivery term.

2. DLMS enhancement; see introductory DLMS note 2a. 

A5 Subcase Number

DLMS Note:

1. Use in FMS transactions based on Service requirements.

2. DLMS enhancement; see introductory DLMS note 2a.

A6 Freight Forwarder Number

DLMS Note:

1. Must use in FMS transactions to identify the country representative or freight forwarder to receive

shipments and documentation.

2. DLMS enhancement; see introductory DLMS note 2a. 

A7 Record Control Number

DLMS Note:

1. Must use in MAP/GA transactions to identify the program line item number.
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 56 September 12, 2023

2. DLMS enhancement; see introductory DLMS note 2a. 

A8 Program Year Code

DLMS Note:

1. Must use in MAP/GA transactions to indicate the program year in which the requisitioned item was

approved and funded.

2. DLMS enhancement; see introductory DLMS note 2a. 

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data. 

2. Future streamlined data; see introductory DLMS note 2c.

AJ Utilization Code

DLMS Note:

1. Use to identify a specialized purpose for which the requisition is submitted.

2. Under legacy MILSTRIP, this is the first position of the document serial number within the document

number.

3. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

4. DLMS enhancement; see introductory DLMS note 2a.

AK Distribution Code

DLMS Note:

Future streamlined data; see introductory DLMS note 2c.

AL Special Requirements Code

DLMS Note:

1. Must use to identify special handling and priority codes when applicable. Under legacy MILSTRIP,

this is carried in the required delivery date field.

2. Authorized DLMS migration enhancement for optional use; see introductory DLMS 2f.

BC Transportation Holding Delay Code

DLMS Note:

1. This is the Shipment Hold Code.

2. Use to identify the reason a shipment unit is not shipped. This includes delays occurring immediately

after materiel is picked, packed, marked and made ready for shipment. 

BD Transportation Priority Code

DLMS Note:

1. Use to identify the applicable transportation priority when available.

2. Authorized DLMS migration enhancement; see introductory DLMS 2f.

DE Signal Code

DLMS Note:

Use to accommodate legacy system requirements. Use only in LRO shipment status to indicate the

activity to receive credit and pseudo shipment status to perpetuate the signal code from the materiel

release order.

DF Media and Status Code

FD Demilitarization Code

DLMS Note:

For Hazardous Materiel/Hazardous Waste turn-ins to a DLA Disposition Service Field Office, enter

Demilitarization Code per the Generator Communication (GenComm) Standard. DLMS enhancement,

see ADC 422.

GQ Group Qualifier Code

DLMS Note:
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 57 September 12, 2023

1. Use to identify the Materiel Management Aggregation Code (MMAC) for NSNs to be managed by a

specific manager (i.e., system, program, aggregation, selected FSC, technology group). This is an Air

Force-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate

without action.

2. A data maintenance action was approved in version 5010. The approved code/name is "MAC –

Material Management Aggregation Code". The code source is identified as the Air Force Manual

(AFMAN) 23-110, Volumes 1 and 2.

3. For Hazardous Materiel/Hazardous Waste turn-ins to a DLA Disposition Service Field Office, enter

MMAC per the Generator Communication (GenComm) Standard data element “Additional Data” in the

DTID record. DLMS enhancement, see ADC 422.

1. Use to identify the Materiel Management Aggregation Code (MMAC) for NSNs to be managed by a

specific manager (i.e., system, program, aggregation, selected FSC, technology group). This is an Air

Force-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate

without action.

2. A data maintenance action was approved in version 5010. The approved code/name is "MAC –

Material Management Aggregation Code". The code source is identified as the Air Force Manual

(AFMAN) 23-110, Volumes 1 and 2.

3. For Hazardous Materiel/Hazardous Waste turn-ins to a DLA Disposition Service Field Office, enter

MMAC per the Generator Communication (GenComm) Standard data element “Additional Data” in the

DTID record. DLMS enhancement, see ADC 422.

R3 Delivery Rank (Priority)

DLMS Note:

1. Use to identify, or modify, the Delivery Priority/Special Processing Code for materiel that has an

urgency of need within the maintenance shop and must be delivered within one hour of receipt of the

issue request. Value will be X (1 hour issue) when applicable.

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

3. A data maintenance action was approved in version 5030. The approved code/name is DPC –

Delivery Priority Code. DoD systems will continue to use Qualifier R3 to represent the Delivery

Priority/Special Processing Code until such time as a new ADC directs otherwise.

1. Use to identify, or modify, the Delivery Priority/Special Processing Code for materiel that has an

urgency of need within the maintenance shop and must be delivered within one hour of receipt of the

issue request. Value will be X (1 hour issue) when applicable.

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

3. A data maintenance action was approved in version 5030. The approved code/name is DPC –

Delivery Priority Code. DoD systems will continue to use Qualifier R3 to represent the Delivery

Priority/Special Processing Code until such time as a new ADC directs otherwise.

COG Cognizance Symbol

DLMS Note:

Use to identify the materiel cognizance symbol (COG) of the end item. Indicate NSL for non-stock

numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy

Components are to perpetuate without action.

DSI Disposition Services Indicator Code

DLMS Note:

1. For Hazardous Material/Hazardous Waste turn-ins to a DLA Disposition Service Field Office, enter

the applicable indicator in the LQ02 to identify type of material sent to DLA Disposition Services..

2. DLA Disposition Services uses the following Disposition Services Indicators in the shipment status

transaction:

 HM - Hazardous Material 

 SS – Special Services

 HW - Hazardous Waste

3. A data maintenance action was approved in version 6050. The approved code/name is “DSI –

Disposition Services Indicator Code”. 

1. For Hazardous Material/Hazardous Waste turn-ins to a DLA Disposition Service Field Office, enter

the applicable indicator in the LQ02 to identify type of material sent to DLA Disposition Services..

2. DLA Disposition Services uses the following Disposition Services Indicators in the shipment status

transaction:

 HM - Hazardous Material 

 SS – Special Services

 HW - Hazardous Waste

3. A data maintenance action was approved in version 6050. The approved code/name is “DSI –

Disposition Services Indicator Code”. 

IMC Item Management Code

DLMS Note:

Use to identify the Item Management Code (IMC) for integrated material management. This is a

Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without

action.

MCC Material Control Code

DLMS Note:

Use to identify the Material Control Code (MCC) for special inventory reporting. This is a Navy-unique

data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.

SMI Special Material Identification Code

DLMS Note:

1. Use to identify the Special Material Identification Code (SMIC) for an end item. This is a Navy-unique

data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.

2. For Hazardous Materiel/Hazardous Waste turn-ins to a DLA Disposition Service Field Office, enter

SMIC per the Generator Communication (GenComm) Standard data element “Additional Data” in the

DTID record. DLMS enhancement, see ADC 422.

T05 Inspection Parameters

DLMS Note:
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

Code Name

004030F856S3SA51 58 September 12, 2023

1. Use to identify the Quality Inspection Code indicating the level of quality inspection to which the item

must be procured and inspected. 

2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.

LQ02 1271 Industry Code

Description: Code indicating a code from a specific

industry code list

X AN 1/30 Used
DLMS Implementation Convention (IC) 856S

Shipment Status

ADC 55, 127, 130, 165, 192, 193, 221, 221A, 223, 242, 242A, 257, 284, 284A, 288, 299, 344, 381, 411, 417, 422,

433, 435, 436, 441, 441A, 448, 448B, 461, 466, 473, 473A, 1007, 1009A, 1014, 1030, 1043, 1043A, 1043B,

1043C, 1068, 1075, 1110, 1132, 1136 , 1156, 1156A, 1161A, 1198, 1244, 1244B, 1287, 1353, 1367, 1399, 1412,

1420, 1428, 1433 and 1454 DLM 4000.25

004030F856S3SA51 59 September 12, 2023

SE Transaction Set Trailer Pos: 0200 Max: 1

Summary - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending

(SE) segments)

Comments: 

1. SE is the last segment of each transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

SE01 96 Number of Included Segments

Description: Total number of segments included in

a transaction set including ST and SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control number that must

be unique within the transaction set functional group

assigned by the originator for a transaction set

DLMS Note: Cite the same number as the one cited

in ST02. 

M AN 4/9 Must use