DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 1 July 17, 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 to the wholesale distribution system for authorized materiel returns,

including automatic returns. Use a single occurrence of this transaction set to transmit single or multiple shipment status transactions to one

inventory control point (ICP)/ integrated material manager (IMM).

2. 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.

3. This DLMS Implementation Convention contains:

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 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 legacy

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. 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 legacy 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.

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

(including expanded field sizes) 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.

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 transaction may be used to provide passive Radio Frequency Identification (RFID) tag identification as applicable to interior and

exterior packaging.

6. All new development and significant enhancements to the DLMS 856R must use the 4030 version of the DLMS Implementation

Convention. The 4010 version of the DLMS 856R IC will be phased out in 2019, to correspond with the deadline for full DLMS compliance

per the OSD AT&L Strategy.

7. 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.

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

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

- ADC 62, Revision to DS 856R, Shipment Status Material Returns

- ADC 62A, Addendum for Revision to DS 856R, Shipment Status Material Returns

- ADC 241, UID of Items and RFID in DLMS Supplement 856R, Shipment Status Material Returns

- ADC 353A, Revised Procedures for Pre-positioned Materiel Receipt (PMR) and Shipment Status for Retrograde and Directed

Discrepant/Deficient Materiel Returns Including Corrected Time Standard for Security Assistance/Foreign Military Sales (SA/FMS)

(Supply/SDR/PQDR/TDR/Retrograde)

1. Organizations use this transaction set to provide shipment status to the wholesale distribution system for authorized materiel returns,

including automatic returns. Use a single occurrence of this transaction set to transmit single or multiple shipment status transactions to one

inventory control point (ICP)/ integrated material manager (IMM).

2. 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.

3. This DLMS Implementation Convention contains:

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 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 legacy

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. 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 legacy 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.

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

(including expanded field sizes) 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.

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 transaction may be used to provide passive Radio Frequency Identification (RFID) tag identification as applicable to interior and

exterior packaging.

6. All new development and significant enhancements to the DLMS 856R must use the 4030 version of the DLMS Implementation

Convention. The 4010 version of the DLMS 856R IC will be phased out in 2019, to correspond with the deadline for full DLMS compliance

per the OSD AT&L Strategy.

7. 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.

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

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

- ADC 62, Revision to DS 856R, Shipment Status Material Returns

- ADC 62A, Addendum for Revision to DS 856R, Shipment Status Material Returns

- ADC 241, UID of Items and RFID in DLMS Supplement 856R, Shipment Status Material Returns

- ADC 353A, Revised Procedures for Pre-positioned Materiel Receipt (PMR) and Shipment Status for Retrograde and Directed

Discrepant/Deficient Materiel Returns Including Corrected Time Standard for Security Assistance/Foreign Military Sales (SA/FMS)

(Supply/SDR/PQDR/TDR/Retrograde)
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 2 July 17, 2023

- 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 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 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 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- ADC 1071, Implementation of Item Unique Identification (IUID) Supply Policy in Version 4030 DLMS 856R Shipment Status Materiel

Returns

- 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 February 21, 2014.

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

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

and DLMS Manuals (Supply/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

- ADC 1249, Revised Procedures for Directed Return of Discrepant/ Deficient Materiel including New Document Number Assignment for

Return Shipment

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

February 21, 2019

- 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

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

Office (DEDSO) - Completed on March 8, 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 1429, Update DLMS 856R 4030 Shipment Status Materiel Returns – Update Code Associations for Transaction Type Qualifier

- 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 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 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 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- ADC 1071, Implementation of Item Unique Identification (IUID) Supply Policy in Version 4030 DLMS 856R Shipment Status Materiel

Returns

- 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 February 21, 2014.

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

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

and DLMS Manuals (Supply/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

- ADC 1249, Revised Procedures for Directed Return of Discrepant/ Deficient Materiel including New Document Number Assignment for

Return Shipment

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

February 21, 2019

- 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

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

Office (DEDSO) - Completed on March 8, 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 1429, Update DLMS 856R 4030 Shipment Status Materiel Returns – Update Code Associations for Transaction Type Qualifier

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 Not Used

* 0800 MEA Measurements O 40 Not Used

* 0900 PWK Paperwork O 25 Not Used

* 1000 PKG Marking, Packaging, Loading O 25 Not Used

* 1100 TD1 Carrier Details (Quantity and

Weight)

O 20 Not Used

1200 TD5 Carrier Details (Routing

Sequence/Transit Time)

O 12 Used

* LOOP ID - TD3 * LOOP ID - TD3 12
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004030F856R2RA19 3 July 17, 2023

1300 TD3 Carrier Details (Equipment) O 1 Used

1350 AT9 Trailer or Container Dimension and

Weight

O 1 Used

* 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 Not Used

* LOOP ID - LH1 * LOOP ID - LH1 100

1520 LH1 Hazardous Identification

Information

O 1 Used

1530 LH2 Hazardous Classification

Information

O 4 Used

1540 LH3 Hazardous Material Shipping

Name

O 12 Used

1550 LFH Freeform Hazardous Material

Information

O 20 Used

1560 LEP EPA Required Data O >1 Used

1570 LH4 Canadian Dangerous

Requirements

O 1 Used

1580 LHT Transborder Hazardous

Requirements

O 3 Used

1590 LHR Hazardous Material Identifying

Reference Numbers

O 10 Used

1600 PER Administrative Communications

Contact

O 5 Used

1610 LHE Empty Equipment Hazardous

Material Information

O 1 Used

* LOOP ID - CLD * LOOP ID - CLD 200

1700 CLD Load Detail O 1 Used

1800 REF Reference Identification O 200 Used

1850 DTP Date or Time or Period O 1 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 Not 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
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004030F856R2RA19 4 July 17, 2023

3400 LM Code Source Information O 1 Used

3500 LQ Industry Code M 100 Must use

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

3600 V1 Vessel Identification O 1 Used

3700 R4 Port or Terminal O >1 Used

3800 DTM Date/Time Reference O >1 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) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 5 July 17, 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) is used by the translation routines of the interchange partners to select the appropriate transaction

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

2. The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate

implementation convention to match the transaction set definition.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use 1

CodeList Summary (Total Codes: 314, Included: 1)

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 1

ST03 1705 Implementation Convention Reference

Description: Reference assigned to

identify Implementation Convention

DLMS Note: Use to indicate this

transmission uses the 856R DLMS

Implementation Convention (IC). Enter the

DLMS IC: 004030F856R0RA00.

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

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 6 July 17, 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 Rep

BSN01 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 65, Included: 4)

Code Name

00 Original

01 Cancellation

DLMS Note:

1. Use when a shipment status must be reversed. Cancellations shall not be used unless the materiel

is still on hand.

2. Applicable when used for retrograde returns and directed returns of discrepant/deficient materiel

(BSN06/640/Code RD). Not applicable to MILSTRIP Materiel Returns Program except as authorized

for intra-Component use. 

3. DLMS enhancement. Refer to ADC 353A.

1. Use when a shipment status must be reversed. Cancellations shall not be used unless the materiel

is still on hand.

2. Applicable when used for retrograde returns and directed returns of discrepant/deficient materiel

(BSN06/640/Code RD). Not applicable to MILSTRIP Materiel Returns Program except as authorized

for intra-Component use. 

3. DLMS enhancement. Refer to ADC 353A.

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.

CO Corrected

DLMS Note:

1. Use to correct shipment information (e.g., TCN or RFID tag number).

2. Applicable when used for retrograde returns and directed returns of discrepant/deficient materiel. 

Not applicable to MILSTRIP Materiel Returns Program except as authorized for intra-Component use.

3. DLMS enhancement. Refer to ADC 353A.

BSN02 396 Shipment Identification

Description: A unique control number

assigned by the original shipper to identify

a specific shipment

DLMS Note: Use Code "ZZ" for this data

element to satisfy mandatory X12 syntax

requirements.

M AN 2/30 Must use 1
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004030F856R2RA19 7 July 17, 2023

BSN03 373 Date

Description: Date expressed as

CCYYMMDD where CC represents the first

two digits of the calendar year

DLMS Note: This date corresponds to the

Universal Time Coordinate (UTC).

M DT 8/8 Must use 1

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 1

BSN06 640 Transaction Type Code

Description: Code specifying the type of

transaction

X ID 2/2 Must use 1

CodeList Summary (Total Codes: 500, Included: 2)

Code Name

FT Material Returns

DLMS Note:

Use to indicate this transaction provides shipment status information related to materiel returns program

transactions (MILSTRIP FTM, Shipment Status (Customer Status to ICP/IMM). For all other types of

returns, use Code RD.

RD Returns Detail

DLMS Note:

1. Use for retrograde shipment for return or repair which fall outside the scope of the MILSTRIP Materiel

Returns Program asset reporting.

2. Use when seeking intra-Service DLR Exchange Pricing credit for materiel turn-in.

3. Use when shipping directed return of discrepant/deficient materiel associated with a Supply

Discrepancy Report (SDR), Product Quality Deficiency Report (PQDR), or Transportation Discrepancy

Report (TDR). 

4. Use in conjunction with a Return Type Code to identify the reason for the return (LQ01= KYL).

5. DLMS enhancement. Refer to ADC 353A.

1. Use for retrograde shipment for return or repair which fall outside the scope of the MILSTRIP Materiel

Returns Program asset reporting.

2. Use when seeking intra-Service DLR Exchange Pricing credit for materiel turn-in.

3. Use when shipping directed return of discrepant/deficient materiel associated with a Supply

Discrepancy Report (SDR), Product Quality Deficiency Report (PQDR), or Transportation Discrepancy

Report (TDR). 

4. Use in conjunction with a Return Type Code to identify the reason for the return (LQ01= KYL).

5. DLMS enhancement. Refer to ADC 353A.

BSN07 641 Status Reason Code

Description: Code indicating the status

reason

O ID 3/3 Used 1

CodeList Summary (Total Codes: 419, Included: 1)

Code Name

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) 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 
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Code Name

004030F856R2RA19 8 July 17, 2023

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.
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 9 July 17, 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 RFID and/or by IUID as applicable.

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

3. Use the second and subsequent 2/HL/0100 loop iterations to identify individual transaction shipment status information.

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.

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

packaging RFID and/or by IUID as applicable.

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

3. Use the second and subsequent 2/HL/0100 loop iterations to identify individual transaction shipment status information.

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.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

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 1. In each subsequent loop

iteration, increase incrementally by 1.

M AN 1/12 Must use 1

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 (child) loop to identify the

HL01 ID Number of the next higher parent

loop.

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 (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.

O AN 1/12 Used 1

HL03 735 Hierarchical Level Code M ID 1/2 Must use 1
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004030F856R2RA19 10 July 17, 2023

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 (materiel returns

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 (materiel returns

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

RFID and IUID loops are optional. Use

multiple P loops to depict a nested RFID

relationship.

CodeList Summary (Total Codes: 218, Included: 4)

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 transaction set originating activity address loop.

W Transaction Reference Number

DLMS Note:

Use to identify the individual transaction materiel returns shipment status loops.
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 11 July 17, 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 in 2/HL/0100 transaction reference number loops to identify the materiel shipped. Do not use in the 2/HL/0100 address loop.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

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 only one of codes A2,

A4, FB, FS, FT, MG, or YP to identify the

materiel shipped. Must use the National

Stock Number (NSN) when known, except

when appropriate brand name subsistence

items are identified by the Subsistence

Identification Number.

DLMS Note: 1. Use only one of codes A2,

A4, FB, FS, FT, MG, or YP to identify the

materiel shipped. Must use the National

Stock Number (NSN) when known, except

when appropriate brand name subsistence

items are identified by the Subsistence

Identification Number.

2. The following codes are authorized.

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 505, Included: 10)

Code Name

A2 Department of Defense Identification Code (DoDIC)

DLMS Note:

1. Use to identify ammunition items.

2. DLMS enhancement; see introductory DLMS note 3a.
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Code Name

004030F856R2RA19 12 July 17, 2023

A4 Subsistence Identification Number

DLMS Note:

Use to identify subsistence items.

F4 Series Identifier

DLMS Note:

1. Use to identify the manufacturer's series number of the end item.

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

FB Form Number

DLMS Note:

1. Use to identify the form stock number.

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

FS National Stock Number

FT Federal Supply Classification

DLMS Note:

1. Use to identify nonstandard materiel when a part number is not available, and materiel reported was

identified by description (e.g., non NSN lumber products).

2. Use only with BSN06 code RD.

MG Manufacturer's Part Number

DLMS Note:

Use to identify nonstandard materiel.

MN Model Number

DLMS Note:

1. Use to identify the manufacturer's model number of the end item.

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

YP Publication Number

DLMS Note:

1. Use to identify the publication stock number.

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

ZZ Mutually Defined

DLMS Note:

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

determined. May be used for legacy MILSTRIP-to-DLMS conversion when the translator cannot

determine a more appropriate code.

LIN03 234 Product/Service ID

Description: Identifying number for a

product or service

M AN 1/48 Must use 1

LIN04 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

DLMS Note: Use only one of codes CN or

ZB to fully identify the materiel.

X ID 2/2 Used 1

CodeList Summary (Total Codes: 505, Included: 2)

Code Name

CN Commodity Name

DLMS Note:

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

ZB Commercial and Government Entity (CAGE) Code
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Code Name

004030F856R2RA19 13 July 17, 2023

DLMS Note:

Use with LIN02 code MG to uniquely identify a manufacturer's part number.

LIN05 234 Product/Service ID

Description: Identifying number for a

product or service

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

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 14 July 17, 2023

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

Detail - Optional

Loop: HL Elements: 2

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:

Use only in 2/HL/0100 transaction reference number loops to identify the number of items shipped.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

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. Use to identify the shipped

quantity.

2. Express as a whole number with no

decimals.

3. A field size exceeding 5 positions may

not be received or understood by the

recipient’s automated processing system. 

See introductory DLMS note 3d. 

M R 1/10 Must use 1

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 and

Purchase Unit Conversion Table for

available codes.

M ID 2/2 Must use 1
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 15 July 17, 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 transaction reference number loops to identify the mode of shipment.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

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 mode of

shipment.

2. DLMS users see the Transportation

Method/Type Code Conversion Guide for

available codes.

X ID 1/2 Must use 1
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 16 July 17, 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. Use in 2/HL/0100 shipment status loop to identify the 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. Must use in 2/HL/0100 transaction reference number loops to identify the document number, fund code and the transportation control

number with the shipment status transaction.

5. Financial accounting data is provided as a DLMS enhancement. When implemented, refer to the Accounting Classification Appendix for

specific entries for the basic appropriation number and supplemental accounting classification data.

6. This transaction supports unique item identification based upon the UII. Shipment status for materiel returns will be prepared using both

the serial number and UII (when available) and required by DoD IUID Supply Policy. (see ADC 1071).

7. 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. 

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

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

9. Under DOD IUID policy, UIT programs require serialization data visibility. Prepare shipment status materiel return with the serial number

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

1. Use in 2/HL/0100 shipment status loop to identify the 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. Must use in 2/HL/0100 transaction reference number loops to identify the document number, fund code and the transportation control

number with the shipment status transaction.

5. Financial accounting data is provided as a DLMS enhancement. When implemented, refer to the Accounting Classification Appendix for

specific entries for the basic appropriation number and supplemental accounting classification data.

6. This transaction supports unique item identification based upon the UII. Shipment status for materiel returns will be prepared using both

the serial number and UII (when available) and required by DoD IUID Supply Policy. (see ADC 1071).

7. 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. 

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

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

9. Under DOD IUID policy, UIT programs require serialization data visibility. Prepare shipment status materiel return 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 Rep

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 1071.

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 1071.

2. The following codes are authorized.

M ID 2/3 Must use 1

CodeList Summary (Total Codes: 1631, Included: 11)

Code Name

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. The batch/lot number may not exceed 20 characters in accordance with IUID policy.

2. DLMS enhancement; see introductory DLMS note 3a.
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Code Name

004030F856R2RA19 17 July 17, 2023

CR Customer Reference Number

DLMS Note:

1. Use the Customer Reference Number to cross-reference to the requisition number under which the

materiel was ordered, when it differs from the turn-in/return document number used with Code TN. This

is applicable to directed return of discrepant/deficient materiel and other types of retrograde shipments.

2. Authorized DLMS enhancement. Refer to ADC 353A and ADC 1249.

D9 Claim Number

DLMS Note:

1. Use to identify the TDR control number directing the return. Recommended for inclusion in the PMR

where an automated interface with the discrepancy reporting application is available.

2. DLMS enhancement. Refer to ADC 353A.

FG Fund Identification Number

DLMS Note:

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

2. Use to identify accounting classification data against which a credit for the returned materiel will be

provided.

3. This is a DLMS enhancement, but it is a required entry for identification of the Fund Code below.

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. May be used in the IUID loop when an RFID tag is applied to the individual item.

3. Authorized DLMS migration enhancement. See introductory DLMS note 3f.

NN Nonconformance Report Number

DLMS Note:

1. Use to identify the DoD WebSDR control number applicable to the SDR Reply directing the return. 

Recommended for inclusion in the PMR where an automated interface with the discrepancy reporting

application is available.

2. DLMS enhancement. Refer to ADC 353A.

QR Quality Report Number

DLMS Note:

1. Use to cite the PQDR report control number (RCN) directing the return. Recommended for inclusion

in the PMR where an automated interface with the discrepancy reporting application is available.

2. DLMS enhancement. Refer to ADC 353A.

SE Serial Number

DLMS Note:

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

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

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

dashes and forward slashes. Spaces are not allowed. 

TG Transportation Control Number (TCN)

DLMS Note:

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

2. Reuse/duplication of a previously used TCN is not permitted. If the controlling document number for

the retrograde or directed return is the same as the original shipment, a unique TCN (not derived from

the original document number) must be identified. 

TN Transaction Reference Number

DLMS Note:

Must use in every 2/HL/0100 transaction reference number loop to identify the document number 
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Code Name

004030F856R2RA19 18 July 17, 2023

associated with the materiel return.

U3 Unique Supplier Identification Number (USIN)

DLMS Note:

1. Use in IUID loop to identify the UII value in REF03. See ADC 1071. The UII may not exceed 50

characters in accordance with IUID Policy. An ANSI data maintenance action was approved in version

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

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

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 1

REF03 352 Description

Description: A free-form description to

clarify the related data elements and their

content

DLMS Note: 1. Use to indicate UII value

when REF01=U3. Refer to ADC 1071. 

2. Use with REF01 code FG and REF04-01

code AT to cite the supplemental

accounting classification data. This is a

DLMS enhancement; see introductory

DLMS note 3a. 

X AN 1/80 Used 1

REF04 C040 Reference Identifier

Description: To identify one or more

reference numbers or identification

numbers as specified by the Reference

Qualifier

DLMS Note: 1. When providing financial

data (REF01 is FG): 

If providing only the fund code use

REF04-01 code FU and cite the fund code

in REF04-02. 

2. The following options are identified as a

DLMS enhancement; see introductory

DLMS note 3a. 

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 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 following data

element of the pair.

When needed, use codes from REF01-01

and the next available combination of data

element 128/127 pairs to provide the

necessary data. 

Syntax: 

1. P0304 - If either C04003 or C04004 is

present, then the other is required.

2. P0506 - If either C04005 or C04006 is

present, then the other is required.

O Comp Used 1

REF04-01 128 Reference Identification Qualifier M ID 2/3 Must use 1
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004030F856R2RA19 19 July 17, 2023

Description: Code qualifying the

Reference Identification

DLMS Note: 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.

CodeList Summary (Total Codes: 1631, Included: 13)

Code Name

08 Carrier Assigned Package Identification Number

DLMS Note:

1. Use to identify carrier package identification 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 note 3f.

10 Account Managers Code

DLMS Note:

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).

AT Appropriation Number

DLMS Note:

Use in one of REF04-01 or REF04-03 to identify the basic appropriation data.

AW Air Waybill Number

DLMS Note:

1. Use to identify the shipment unit air waybill number.

2. Authorized DLMS migration enhancement. See introductory DLMS note 3f.

BL Government Bill of Lading

DLMS Note:

1. Use to identify the government bill of lading.

2. Authorized DLMS migration enhancement. See introductory DLMS note 3f.

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 note 3f.

FU Fund Code

DLMS Note:

Use with REF01 code FG to identify the fund code.

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 note 3f.

K2 Certified Mail Number

DLMS Note:

1. Use to identify the shipment unit certified mail number.

2. Authorized DLMS migration enhancement. See introductory DLMS note 3f.

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 note 3f.
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Code Name

004030F856R2RA19 20 July 17, 2023

W8 Suffix

DLMS Note:

Use with REF01 code TN to identify the transaction number suffix.

WY Waybill Number

DLMS Note:

1. Use to identify the shipment unit surface waybill number.

2. Authorized DLMS migration enhancement. See introductory DLMS note 3f.

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 note 3f.

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 1

REF04-03 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: For valid codes, see REF04,

C04001.

All valid standard codes are used. (Total

Codes: 1631)

X ID 2/3 Used 1

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 1

REF04-05 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: For valid codes, see REF04,

C04001.

All valid standard codes are used. (Total

Codes: 1631)

X ID 2/3 Used 1

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 1
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 21 July 17, 2023

DTM Date/Time Reference Pos: 2000 Max: 10

Detail - Optional

Loop: HL Elements: 2

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:

Use only in 2/HL/0100 transaction reference number loops to identify dates associated with the shipment status.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DTM01 374 Date/Time Qualifier

Description: Code specifying type of date

or time, or both date and time

DLMS Note: Use only one of codes 011 or

514 to identify the available shipment

information.

M ID 3/3 Must use 1

CodeList Summary (Total Codes: 1226, Included: 1)

Code Name

011 Shipped

DLMS Note:

Use to identify the date released to carrier/shipment date, regardless of shipment method.

DTM02 373 Date

Description: Date expressed as

CCYYMMDD where CC represents the first

two digits of the calendar year

X DT 8/8 Must use 1
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 22 July 17, 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.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

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 1

CodeList Summary (Total Codes: 1446, Included: 10)

Code Name

41 Submitter

DLMS Note:

Use to identify the organization transmitting the transaction set.

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 3f.

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 3a.

MF Manufacturer of Goods

DLMS Note:

1. Use in IUID loop to identify the manufacturer of the identified item.

2. DLMS enhancement: See introductory DLMS note 3a.

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.

RT Returned to
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Code Name

004030F856R2RA19 23 July 17, 2023

DLMS Note:

1. Cite the applicable routing identifier code (RIC) for the receiving depot for materiel returns program

shipment status (BSN06=FT).

2. For other types of returns, cite the applicable DoDAAC or CAGE. 

3. Inclusion of the associated text address is optional.

4. Use of DoDAAC and CAGE is a DLMS enhancement. Refer to ADC 353A.

SF Ship From

DLMS Note:

1. Use to identify the shipping activity (ship from) when other than the submitter.

2. DLMS enhancement: See introductory DLMS note 3a.

Z1 Party to Receive Status

DLMS Note:

1. Use to indicate the organization to receive shipment status.

2. Use to identify the PICA RIC when reporting materiel returns shipment status to the SICA under

MILSTRIP MRP supporting DOD IUID Supply Policy; authorized for optional use for non-UII materiel

returns. Authorized DLMS enhancement; see introductory DLMS Note 3f. Refer to ADC 1071.

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 status recipients, as needed. See introductory DLMS 3a.

1. Use to indicate the organization to receive shipment status.

2. Use to identify the PICA RIC when reporting materiel returns shipment status to the SICA under

MILSTRIP MRP supporting DOD IUID Supply Policy; authorized for optional use for non-UII materiel

returns. Authorized DLMS enhancement; see introductory DLMS Note 3f. Refer to ADC 1071.

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 status recipients, as needed. See introductory DLMS 3a.

Z4 Owning Inventory Control Point

ZB Party to Receive Credit

DLMS Note:

Use to identify the organization to receive credit for the materiel when different from the organization

originating the transaction set.

N102 93 Name

Description: Free-form name

DLMS Note: 1. Use with N101 code CA to

identify the carrier by name. (Field length

restricted to 20 positions.)

2. Use with N101 Code RT to identify the

returned-to location activity name (address

line 1). (Field length restricted to 35

positions.)

X AN 1/60 Used 1

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

X ID 1/2 Must use 1

CodeList Summary (Total Codes: 223, Included: 6)

Code Name

2 Standard Carrier Alpha Code (SCAC)

DLMS Note:

Use to identify the commercial carrier.

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement; See introductory DLMS note 3a.

33 Commercial and Government Entity (CAGE)

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

Use to indicate the Security Assistance (SA) structured address data. Interpretation may require

additional codes cited elsewhere in the transaction.
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Code Name

004030F856R2RA19 24 July 17, 2023

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 3a.

N104 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Must use 1

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

DLMS Note: Use only in 2/HL/0100

address loops.

O ID 2/3 Used 1

CodeList Summary (Total Codes: 1446, Included: 3)

Code Name

FR Message From

DLMS Note:

Must use with the appropriate 2/N101/2200 code to indicate the organization cited in N104 is sending

the transaction set.

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 3a.

TO Message To

DLMS Note:

1. Must use with the appropriate 2/N101/2200 code to indicate the organization cited in N101 is

receiving the transaction set.

2. Use to identify the party directing the return (N101=Z4). Required for MILSTRIP Materiel Returns

Program Shipment Status (BSN06=FT).

3. Use a separate N1 loop to identify the returned-to activity (N101=RT) if identified by DoDAAC or RIC.

 DLMS enhancement. Refer to ADC 353A.

1. Must use with the appropriate 2/N101/2200 code to indicate the organization cited in N101 is

receiving the transaction set.

2. Use to identify the party directing the return (N101=Z4). Required for MILSTRIP Materiel Returns

Program Shipment Status (BSN06=FT).

3. Use a separate N1 loop to identify the returned-to activity (N101=RT) if identified by DoDAAC or RIC.

 DLMS enhancement. Refer to ADC 353A.
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 25 July 17, 2023

N2 Additional Name Information Pos: 2300 Max: 2

Detail - Optional

Loop: N1 Elements: 1

User Option (Usage): Used

Purpose: To specify additional names

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N201 93 Name

Description: Free-form name

DLMS Note: Use when a clear text address

must be specified (address line 2, if

needed). (Field length restricted to 35

positions.)

M AN 1/60 Must use 1
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 26 July 17, 2023

N3 Address Information Pos: 2400 Max: 2

Detail - Optional

Loop: N1 Elements: 1

User Option (Usage): Used

Purpose: To specify the location of the named party

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N301 166 Address Information

Description: Address information

DLMS Note: Use when a clear text address

must be specified. This equates to the

street address. (Field length restricted to

35 positions.)

M AN 1/55 Must use 1
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 27 July 17, 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. E0207 - Only one of N402 or N407 may be present.

2. C0605 - If N406 is present, then N405 is required.

3. C0704 - If N407 is present, then N404 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.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used 1

N402 156 State or Province Code

Description: Code (Standard

State/Province) as defined by appropriate

government agency

X ID 2/2 Used 1

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 1

N404 26 Country Code

Description: Code identifying the country

DLMS Note: Use to identify the country.

See introductory DLMS note 6 (Refer to

ADC 1075 for implementation).

X ID 2/3 Used 1
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 28 July 17, 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 as directed by the authorizing Service/Agency to provide contract information for shipments of GFP directed returns/retrograde. 

3. Authorized DLMS enhancement. Refer to ADC 1014.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

GF01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

X ID 2/3 Used 1

CodeList Summary (Total Codes: 1631, Included: 1)

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

X AN 1/50 Used 1

GF03 367 Contract Number

Description: Contract number

DLMS Note: Must use to identify the

applicable procurement instrument

identifier (PIID). Use the legacy

procurement instrument identification

number (PIIN) pending transition to the

PIID. When GFM 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 legacy

procurement instrument identification

number (PIIN) pending transition to the

PIID. When GFM 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 1

GF07 328 Release Number

Description: Number identifying a release

against a Purchase Order previously placed

O AN 1/30 Used 1
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004030F856R2RA19 29 July 17, 2023

by the parties involved in the transaction

DLMS Note: 1. Use to identify the legacy

four-position call/order associated with the

PIIN number.

2. Do not use for the PIID call/order

number. The PIID call/order number is

mapped to GF03. Refer to ADC 1161.
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 30 July 17, 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:

Use only in 2/HL/0100 transaction reference number loops to identify coded information maintained in department or agency documentation.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

Description: Code identifying the agency

assigning the code values

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 187, Included: 1)

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 31 July 17, 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 Rep

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 Must use 1

CodeList Summary (Total Codes: 768, Included: 14)

Code Name

0 Document Identification Code

DLMS Note:

1. The 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. Future streamlined data; See introductory DLMS note 3c.

79 Priority Designator Code

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

83 Supply Condition Code

DLMS Note:

1. Use only with return of discrepant materiel (BSN06 code RD).

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

87 Subsistence Type of Pack Code

DLMS Note:

Use only for subsistence items to identify the subsistence type of pack item identification.

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data.

2. During legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the

MILSTRIP Supplemental Address (SUPAAD) field. During this time the field size is restricted to 6

positions.

3. Expanded use of this field for supplemental data without size restriction is a DLMS enhancement;

see introductory DLMS note 3a.

1. Use to identify supplemental address/data.

2. During legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the

MILSTRIP Supplemental Address (SUPAAD) field. During this time the field size is restricted to 6

positions.

3. Expanded use of this field for supplemental data without size restriction is a DLMS enhancement;

see introductory DLMS note 3a.

AJ Utilization Code

DLMS Note:

1. Under legacy MILSTRIP, this is the first position of the document serial number.

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

AL Special Requirements Code
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

Code Name

004030F856R2RA19 32 July 17, 2023

DLMS Note:

1. Use to identify the precedence, special handling, and processing requirements.

2. Under legacy MILSTRIP, this is carried in the required delivery date field.

3. DLMS enhancement; see introductory DLMS note 3a.

DE Signal Code

DF Media and Status Code

COG Cognizance Symbol

DLMS Note:

Use to identify the material 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.

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.

KYL Key Event Lookup

DLMS Note:

1. Use to identify the Return Type Code. 

2. Enter the applicable value in LQ02:

 S = Directed return of discrepant materiel associated with a SDR

 Q = Directed return of quality deficient materiel associated with a PQDR or Security Assistance

quality SDR

 T = Directed return associated with a TDR

 R = Retrograde (general retrograde movement of unit materiel)

 X = Carcass return under Component exchange pricing rules

 M = Directed return under Materiel Returns Program (may be assigned by DAAS for returns status

originated in MILS format) 

 O = Other

3. DLMS enhancement. Refer to ADC 353A.

1. Use to identify the Return Type Code. 

2. Enter the applicable value in LQ02:

 S = Directed return of discrepant materiel associated with a SDR

 Q = Directed return of quality deficient materiel associated with a PQDR or Security Assistance

quality SDR

 T = Directed return associated with a TDR

 R = Retrograde (general retrograde movement of unit materiel)

 X = Carcass return under Component exchange pricing rules

 M = Directed return under Materiel Returns Program (may be assigned by DAAS for returns status

originated in MILS format) 

 O = Other

3. DLMS enhancement. Refer to ADC 353A.

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:

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.

LQ02 1271 Industry Code

Description: Code indicating a code from a

specific industry code list

X AN 1/30 Must use 1
DLMS Implementation Convention (IC) 856R,

Shipment Status Materiel Returns

ADC 62, 62A, 241, 353A, 417, 448, 448B, 1014, 1043C, 1071, 1075, 1136, 1161, 1198, 1244, 1244B,

1249, 1287, 1353, 1367, 1412, 1420 and 1429 DLM 4000.25

004030F856R2RA19 33 July 17, 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 Rep

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 1

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 1