ADC 241 

IUID and RFID in 

DS 856R, Shipment Status Material Returns 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Management Standards Office (DLMSO)

b. Sponsors:

(1) Supply Process Review Committee, Chair, Ellen Hilert, DLA DLMSO (J-6251), 

703-767-0676 (DSN 427), ellen.hilert@dla.mil 

(2) Unique Item Tracking Committee (UITC)/MILSTRAP Chair, Mary Jane Johnson, DLA 

DLMSO (J-6251), 703-767-0677 (DSN 427), mary.jane.johnson@dla.mil

2. REFERENCES: 

a. DOD Item Unique Identification (IUID) policy and associated documentation are available at:

http://www.acq.osd.mil/UID/index.html 

b. DOD Passive RFID policy and associated documentation are available at: DOD 

http://www.acq.osd.mil/log/rfid/index.htm

3. FUNCTIONAL AREA: Primary: Supply

4. COMMENTS RESULTING FROM PROPOSAL COORDINATION: 

HQ DLA comments applicable to IUID: “The allocation of data elements in EDI transactions is 

innocuous. However, since the implementation of this concept comes with the expectation of standing 

up a new process to perpetuate UID data, we have some concerns. If new data is introduced to an 

interface, we would require a significant period of time to sufficiently design, build, and test the 

changes. Formal process documentation for IUID is still lacking. Without a clearly stated process for 

the flow of data and expectations by all interface partners, there are obvious concerns within DLA for 

how this will work. Some of the challenges would include: 

 a. OSD developing an IUID to RFID item unit pack relationship that has not been established 

by OSD policy. 

 b. OSD policy is evolving, and additional changes may be required to modify, or enhance, the 

transactional exchange as outlined in this proposal. 
2

 c. With limited policy or business rules to define this relationship, it may be premature to do 

this in a DLMS transaction. Also, there may be more DLMS changes necessary as indicated in the 

PDC, i.e., “as policy and desired functionality are more fully developed." 

..... “this is an extremely complex process. We think it is very important to insure Service 

concurrence/buy in on this proposal.” 

5. REQUESTED CHANGE: 

a. Description of Change: This change updates DLMS Supplement 856R, Shipment Status 

Material Returns, to carry IUID information and passive RFID tag information. This ADC is a 

planning tool for establishing techniques for accommodating IUID and RFID tag data within 

transactional exchanges under the DLMS to support business process improvements. As policy and 

desired functionality are more fully developed, additional DLMS changes may be necessary. 

Component system changes, which are required to support the integration of the IUID or RFID tag 

data requirements, are not identified in this change. This change also harmonizes the 856R for 

Shipment Status Material Returns, with the 856S, DLMS Shipment Status, using the same 

version/release (ASC X12 4030). It adds administrative notes to clarify usage and further identify 

specific DLMS enhancements. 

b. Procedures: 

(1) General Information. 

[a] Capability to identify the transportation control number (TCN) and a secondary 

transportation number (e.g. carrier assigned shipping number) is to be implemented during 

modernization. The Standard Carrier Alpha Code for carrier identification should also be included for 

tracking purposes. 

[b] The shipment status for material returns includes specific identification of the 

party to receive credit and the ship-from activity. These two data fields equate to the dual use of the 

MILS Supplemental Address field. During MILS/DLMS transition, one activity may be identified so 

that it may be mapped to the MILS for conversion without loss of content. However, full DLMS 

implementation is intended to enable identification of different activities using these separate 

qualifiers. Components implementing this transaction should plan for this future capability. However, 

implementation may not occur without prior coordination, 

[c] to ensure the receiving activity can accommodate this process. Components 

should report a planned implementation date for this procedure to DLMSO. 

[d] The revised shipment status for material returns structure provides the flexibility 

to identify the non-parsable UII value and related elements. There will be a separate Hierarchical 

Level (HL) loop for each item identified. The available data fields are: UII, serial number, 

manufacturer, part number, and batch/lot number. 

[e] The revised shipment status for material returns also provides the flexibility to 

identify multiple levels of packing to which an RF tag may be identified. There will be a separate HL 

loop for each level, or RFID may be identified at the IUID item level. A parent/child relationship may 
3

be established between the IUID and the packaging level (to associate the IUID item with the RF tag 

on its packaging). In addition, a parent/child relationship may be established between each of the 

packing levels (e.g., to associate which case is in which pallet). 

[f] The transaction structure will accommodate DLMS unique item tracking by serial 

number. This is a transitional requirement which may be employed until tracking by UII is 

implemented across DOD. 

[g] This transaction is provided using ANSI Version 4030. The existing 

implemented 4010 version will continue to be supported until Components migrate to the higher level. 

The transaction is migrated to the higher version to remain consistent with the DLMS Shipment Status, 

856S, which carries RFID and IUID. 

[h] The original 4010 structure was designed to permit multiple shipment status 

transactions (different requisition document numbers) to be included in a single 856R transaction 

exchange using multiple HL loops (for economy of transmission; not for any functional purpose such 

as describing an entire shipment unit and its contents). The 4030 version is restricted to a single 

material returns shipment status transaction, since the structure is more complex with the added RFID 

and UID loops. 

(2) Modify DOD 4000.25-M, Defense Logistics Management System Manual as shown in 

Enclosure 1. 

(3) Modify the DLMS Supplement 856R as shown in Enclosure 2. A sample transaction is 

shown at Enclosure 3. 

6. REASON FOR CHANGE: 

a. OSD policy for the IUID states that the Unique Item Identifier shall be the primary pointer or 

key data element for the AIS in all computational functions including inventory acceptance, item 

accountability, storage, issue, receipt, valuation, maintenance, and disposal. In support of this 

requirement, logistics transactions must identify the UII. This change is required to incorporate the 

placeholder for UII as currently defined within DLMS logistics exchange transactions and provide 

maximum flexibility. 

b. OSD policy for passive RFID directs the use of RFID by DOD shippers. Passive tagging 

specifically applies to DOD shipments at the case (i.e., shipping container or exterior container) and 

pallet (i.e., palletized unit load) levels. Passive RFID at the packaging level for items requiring IUID 

is not required for initial implementation. Passive tags should be applied at the case and pallet levels 

to all sustainment or retrograde shipments to support asset visibility within the DOD supply chain and 

improved logistics business processes. 

c. Selected DLMS enhancements have been identified for migration without prior notification. 

These require identification in the DS and appropriate procedures in the manual. 

7. ADVANTAGES AND DISADVANTAGES: 
4

a. Advantages: Supports implementation of UID/RFID policy within the supply functional area. 

b. Disadvantages: None specifically identified; however, policy is evolving and additional 

changes may be required to modify or enhance the transactional exchange as outlined in this proposal. 

8. IMPACT: 

 a. This change impacts DLMS-capable application and those in the process of planning for 

migration. This change may be implemented on a phased and staggered basis without prior 

coordination with trading partners (with exception as noted above for parties to receive credit). 

DLMS-capable receiving applications which have not yet adopted these DLMS enhancements should 

verify that inclusion of the new data will not cause transactions to reject. 

 b. DAASC will need to maintain both 4010 and 4030 version of this transaction until those using 

the 4010 version have migrated. 

 c. DOD 4000.25-M, DLMS, and 856R Federal IC and corresponding DLMS Supplement. 

Revisions to Federal ICs will be submitted to the EDISMC. 

 d. This change impacts the Defense Automatic Addressing System (DAAS), Global Transportation 

Network (GTN), and other applications maintaining a historical database and query capability, so that 

additional data content may be saved and displayed appropriately. 

Enclosures
Enclosure 1 

DLMS Manual Revision 

C5.2.3.3. Shipment Status Material Returns. Use the DS to the Federal IC 856R, Shipment Status 

Material Returns, to prepare a shipment status and promptly submit to the ICP/IMM after materiel 

directed for return is released to the carrier. Refer to chapter 11 for material returns program 

procedures. The shipment status for material returns shall include the transportation control 

number, shipment date, mode of shipment, and quantity shipped. It shall perpetuate data content 

from the automatic return notification (DS 180M) or the ICP/IMM reply to the customer’s asset 

report and shipping information (870M), as applicable, per guidance in the DS. The DLMS 

Shipment Status shall include asset visibility content, such as IUID, and intransit visibility 

requirements, such as passive RFID and the transportation control number as directed under DoD 

policy/procedures (DoD 4140.1-R). DLMS enhancements include, but are not limited to, the 

following: 

 

 C5.2.1.2.1 Passive RFID for the shipment unit/case/pallet associated at the document 

number level. The shipment status transaction may identify a hierarchy to clarify the relationship 

of passive tags within different shipment levels. 

 C5.2.1.2.2 For Unique Item Tracking (UIT) purposes, the IUID and/or serial number. 

Serial number without applicable IUID may be used during MILS/DLMS transition and pending 

implementation of IUID capability. Refer to chapter 19 for UIT guidance. 

 C5.2.1.2.3 Both the TCN and a secondary transportation number, such as the small package 

carrier number, when this is applicable. 

 C5.2.1.2.4 Identification of the carrier, when other than United States Postal Service 

(USPS), by Standard Carrier Alpha Code (SCAC). 

C5.2.1.2.5 Specific identification of all parties associated with the material return. This 

includes the party to receive credit when different from the document number DoDAAC (previously 

carried in the MILS Supplemental Address field) and all parties to receive status. Transition to use 

of specifically identified parties will facilitate full DLMS implementation which will enable 

identification of multiple different activities (e.g. submitter, ship-from, credit-to, status-to). Prior 

coordination for this DLMS enhanced capability is required.

Enclosure 2 

DLMS Supplement Revision 

Item 

# 

Location 856R Revision Reason

1. DLMS 

Introducto

ry Notes 

Add new DLMS notes e and f to read:

e. Repetition of data (using multiple iterations or loops) which 

is not compatible with existing DLSS capability. Although 

supported by the use of the ANSI X12 standard, such data is 

not compatible with DLSS/DLMS conversion and may not be 

supported by the recipient's automated processing system. 

Components must coordinate implementation of enhanced 

capability with DLMSO 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.

New note added to clarify 

intent for implementation 

of specific enhancements. 

These data elements 

should be adopted by 

DLMS-capable systems 

without prior 

coordination and trading 

partner agreement.

2. DLMS 

Introducto

ry Notes 

Add new DLMS notes 4, 5 and 6 to read: 

4. This transaction may be used to provide Unique Item 

Identifier (UII) information. Refer to the UID web at URL: 

http://www.acq.osd.mil/dpap/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. This revision to the DLMS Supplement incorporates 

Proposed DLMS Change (PDC) and Approved DLMS 

Changes (ADC) listed. PDCs and ADCs are available from the 

DLMSO website: http://www.dla.mil/j-6/dlmso/Changes. 

- 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 

To identify UID web 

URL, to identify RFID 

information along with 

identifying DLMS 

Changes included in 

this DLMS Supplement 

3. 1/BSN07/

0200 

Add the following DLMS note 2 to qualifier “W05”:

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

Clarification 

4. 2/HL/0100 Revise first 3 Federal notes as follows and added notes 4 and 

5:

1. The transaction set hierarchical data structure is 

Supports IUID and 

RFID 

(IUID is primarily a 
2

Item 

# 

Location 856R Revision Reason

address information, followed by transaction shipment 

status, followed interior/exterior packaging RFID and/or 

by UID as applicable.

2. Use the first 2/HL/0100 loop iteration to provide transaction 

set originating activity address information. 

3. Use the second and all 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.

placeholder in the 

DLMS format since 

explicit policy directing 

its use within this 

process is not currently 

available.) 

5. 2/HL02/01

00 

Open Data Element HL02 and added the following DLMS 

notes:

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. UID loops may be associated with a parent RFID loop (e.g. 

item pack). Not applicable to the UID loop if no specific parent 

RFID loop is identified.

Supports IUID and 

RFID 

6. 2/HL03/01

00 

Add the following DE DLMS note, added qualifiers “I” and “P” 

both w/ DLMS notes and revised DLMS note for qualifier “V”:

DE DLMS Note: 

The following informational loops are applicable to this 

transaction. When all loops are used, the HL sequence is V 

(address), W (material returns shipment status), P (RFID), and 

I (UID). RFID and UID loops are optional. Use multiple P 

loops to depict a nested RFID relationship. 

I Item 

DLMS Note: Use to identify IUID data consistent with UID 

data requirements. The IUID data is carried in the REF and 

N1 segments; no other segments are used in the UID loop. 

Use a separate UID loop for each item. If an RFID is provided 

at the item level it may 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 

Supports IUID and 

RFID 
3

Item 

# 

Location 856R Revision Reason

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.

7. 2/LIN02/0

200 

Add the following DLMS note 2 to the following qualifiers A1, 

A2, F4, FB, MN, YP: 

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

Deleted qualifier: SE Serial Number 

Added second sentence to DLMS note for qualifier ZZ: 

ZZ Mutually Defined: 

DLMS Note: Use to identify nonstandard material when all 

other authorized codes do not apply or cannot be determined. 

May be used for DLSS-to-DLMS conversion when the 

translator cannot determine a more appropriate code. 

Clarification 

8. 2/SN1/030

0 

Revise Federal segment level DLMS note to read: 

Use only in 2/HL/0100 transaction reference number loops to 

identify the number of items shipped. 

Supports IUID and 

RFID 

9. 2/SN102/0

300 

Add DE Level DLMS note to read:

A field size exceeding 5 positions may not be received or 

understood by the recipient’s automated processing system. 

See introductory DLMS note 3d.

Clarification 

10. 2/REF/15

00 

Delete Federal note 1 and added the following new segment 

level Federal notes: 

1. Use in 2/HL/0100 transaction reference number loops to 

provide financial data citing the fund purpose code and either 

or both of the fund code and the long-line accounting data.

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 UID loop to provide IUID information. 

Repeat the REF segment within each UID 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 

Supports IUID and 

RFID 
4

Item 

# 

Location 856R Revision Reason

relationship between tags at different layers of packaging.

11. 2/REF/15

00 

Revise segment level DLMS notes 1 and 2 and added the 

following DLMS notes 3 and 4:

1. Must use in 2/HL/0100 transaction reference number loops 

to identify the customer assigned transaction document 

number, fund code financial accounting data, L and the 

shipment unit transportation control number, and unique item 

tracking (UIT) associated with the shipment status transaction. 

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

3. This transaction will support item identification based 

upon the UII or the serial number. Data elements 

associated with the UII may be identified separately. Use 

the appropriate data elements to satisfy the desired 

functionality. 

4. This transaction will support association of the UID 

information with the RFID tag at the UID packaging level 

and/or at each higher level of packing which has been 

tagged. 

Supports IUID and 

RFID 

12. 2/REF01/

1500 

Add new Federal note and revised DLMS note 1 to read:

Federal Note: Use any code. 

DLMS Note: 1. Use codes separately or in combination, to 

identify appropriate information for unique item tracking (UIT).

Supports IUID 

13. 2/REF01/

1500 

Revise the following DLMS notes for the following qualifiers:

BT Batch Number 

DLMS Note: 1. Use in UID 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 UID policy. 

2. DLMS enhancement; see introductory DLMS 3a. 

SE Serial Number 

DLMS Note: 1. Use in UID loop to identify the serial number. 

2. DLMS enhancement; see introductory DLMS 3a.

Supports IUID 
5

Item 

# 

Location 856R Revision Reason

Delete qualifier: LT Lot Number 

Add DLMS note 3 for qualifier FG:

FG Fund Identification Number: 

3. This is a DLMS enhancement, but it is a required entry for 

identification of the Fund Code below. 

14. 2/REF01/

1500 

Add the following qualifiers w/ DLMS notes and revised DLMS 

note for qualifier “TN”:

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 UID loop when an RFID tag is applied 

to the individual item. 

3. Authorized DLMS migration enhancement. See DLMS 

introductory note 3f. 

PM Part Number 

DLMS Note: 1. Use in UID loop to identify the applicable part 

number. 

2. May be used when primary item identification is the NSN. 

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

U3 Unique Supplier Identification Number (USIN) 

DLMS Note: 1. Use in UID loop to identify the UII value in 

REF03. The UII may not exceed 50 characters in accordance 

with UID Policy. An ANSI data maintenance was approved in 

version 5020. The approved code/name is “UII-Department of 

Defense Unique Item Identifier”. 

2. Authorized DLMS migration enhancement. See DLMS 

introductory note 3f. 

TN Transaction Reference Number 

DLMS Note: Must use in every 2/HL/0100 transaction 

reference number loop to identify the original customerassigned document number associated with the material 

return.

Supports IUID and 

RFID 

15. 2/REF03/

1500 

Move the following Federal Notes to the DLMS level note:

DLMS Note: 1. Use to indicate UII value when REF01=U3. 

2. Use with REF01 code FG and REF04-01 code AT to cite 

Maintaining notes at 

the DLMS level 

facilitate future update. 
6

Item 

# 

Location 856R Revision Reason

the supplemental accounting classification data. This is a 

DLMS enhancement; see introductory DLMS note 3a.

16. 2/REF04/

1500 

Move the following Federal Notes to the DLMS level note:

DLMS Note: 

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. 

Delete qualifier K1: 

K1 Foreign Military Sales Notice Number 

Revise DLMS notes as follows: 

128 Reference Identification Qualifier 

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. 

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.

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.

Maintaining notes at 

the DLMS level 

facilitate future update. 

FMS Notice Number is 

not applicable to the 

material returns 

process. 

Clarification of usage 

and identification of 

authorized 

DLMS enhancements. 

 BL Government Bill of Lading 
7

Item 

# 

Location 856R Revision Reason

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.

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.

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.

17. 2/DTM01/

2000 

Delete qualifier “514”:

514 Transferred (date transferred to the carrier, if a delay 

occurs prior to actual shipment.)

This date field is not 

used in the material 

returns process. 

 2/N101/22 CA Carrier Includes authorized 
8

Item 

# 

Location 856R Revision Reason

00 

N102 

N103 

DLMS Note: 

1. Use as needed to identify the shipment unit carrier when other 

than the United States Postal Service. 

2. The carrier is identified by Standard Carrier Alpha Code 

(SCAC). Carrier may be identified by name (N102). 

3. Authorized DLMS migration enhancement; see introductory 

DLMS note 3f. 

Name 

Use with N101 code CA to identify the carrier by name. (Field 

length restricted to 20 positions.) 

2. Standard Carrier Alpha Code (SCAC) 

DLMS Note: Use as needed to identify the commercial carrier.

DLMS enhancement note 

and improves flexibility 

by allowing identification 

by name or SCAC.

18. 2/N101/22

00 

Revise DLMS note for qualifier CN:

CN Consignee 

DLMS Note: 1. Use to identify the material consignee when 

different from the Ship To. 

Delete qualifier “ST” and associated note:

ST Ship To 

DLMS Note: 1. Use to identify the organization to receive 

the material. 

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

There is a requirement 

for only one data 

element to identify the 

consignee/ ship-to. 

The DLMS 

enhancement for the 

ST Ship To is 

unnecessary and the 

note for the CN 

Consignee must be 

updated to remove the 

reference to a different 

ship to 

19. 2/N101/22

00 

Delete DLMS note 1 and add new DLMS 1 and 2 for qualifier 

“MF”:

MF Manufacturer of Goods 

DLMS Note: 

1. Use in UID loop to identify the manufacturer of the 

identified item. 

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

Clarification of usage. 

20. 2/N101/22

00 

Add qualifier “KK” with DLMS note:

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. 

Added for consistency 

with ADC 165, Optional 

Capability for Sending 

Information Copy of 

DLMS Supplements 

856, 856S, 861, 867I, 

870M, 945A, and 947I 

to a Component UIT 

Registry 
9

Item 

# 

Location 856R Revision Reason

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

21. 2/N103/22

00 

Delete DLMS note for qualifier “M4” and added qualifier “UR” 

with DLMS note:

M4 Department of Defense Routing Identifier Code (RIC) 

DLMS Note: 1. The RIC is retained in the DLMS to facilitate 

transaction conversion in a mixed DLSS/DLMS environment. 

Continued support of the RIC in a full DLMS environment will 

be assessed at a future date. Typically under the DLMS, the 

RIC will be replaced with a DoDAAC or a commercial 

identifier.

2. Future streamlined data; See introductory DLMS note 3c.

UR Uniform Resource Locator 

DLMS Note: 1. Use when appropriate to identify the 

Component UIT registry. 

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

This note is removed 

as there are no plans 

at this time to 

discontinue use of the 

routing identifier. 

Consistent with ADC 

165 

22. 2/N106/22

00 

Add the following qualifier with DLMS note:

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.

Consistent with ADC 

165 

23. 2/LQ01/35

00 

Revise DLMS note to qualifier “79” to read:

79 Priority Designator Code 

DLMS Note: DLMS enhancement; see introductory DLMS 

note 3a. 

Added DLMS note 2 to qualifier 83:

83 Supply Condition Code 

DLMS Note: 1. Use only with return of discrepant material 

(BSN07 code W05). 

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

Revise DLMS notes for qualifier “A9” as follows:

A9 Supplemental Data 

DLMS Note: 1. Use to identify supplemental address/data. 

2. During DLSS/DLMS transition, this field will be used to 

Added standard DLMS 

notes for enhancement 

and usage. 
10

Item 

# 

Location 856R Revision Reason

perpetuate/populate the DLSS 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 3.a. 

2. Future streamlined data; see introductory DLMS note 3c.
Enclosure 

DS 856R Example 

ST~85R~(transaction control number) Header

BSN~00~ZZ~(date-ccyymmdd)~(time-hhmm)~~AS Beginning Segment – Shipment Advice

HL~1~~V Address information loop

 N1~41~~10~(DoDAAC)~~FR Originating transaction organization 

 N1~Z4~~M4~(RI code)~~TO ICP/IMM receiving the transaction 

HL~2~~W Shipment status loop

 LIN~~FS~(NSN) NSN 

 SN1~~7~EA Quantity and Unit of Issue of shipped items 

 TD5~~~~(mode code) Mode of Shipment 

 REF~TG~(TCN) ~~08~(carrier no.) TCN and Carrier assigned shipping no. 

 REF~TN~(document number)~~W8~(suffix number) Document Number and Suffix 

 REF~FG~(fund purpose code)~~ FU^(fund code) Fund Purpose Code and Fund Code 

 DTM~011~(date-ccyymmdd) Date shipped 

 N1~CN~~M4~(RI code) Receiving Depot (ship-to location) 

 N1~ZB~~10~(DoDAAC) Party to Receive Credit (from MILS SUPADD) 

 N1~Z1~~10~(DoDAAC) Party to Receive Status 

 LM~DF Identifies DOD as agency assigning code values 

 LQ~0~FTM MILS Document ID Code 

 LQ~DE~(signal code) Signal code 

 LQ~DF~(media and status code) Media and Status Code 

 LQ~A9~(supplementary address) Supplementary Address 

HL~3~~P RFID Loop 

 REF~JH~(tag number) RFID tag number 

SE~77~(transaction control number) Transaction Set Trailer