1

ADC 242 

Shipment Status (DS 856S): 

PD, TP, Project Code, Special Requirements Code 

1. ORIGINATOR: 

a. Service/Agency: Defense Distribution Center (DDC), Defense Logistics Agency 

(DLA), and the Defense Logistics Management Standards Office (DLMSO) 

 

 b. Originator: DDC: DSN 771-5186 / COMM 717-770-5186 

c. Sponsor: Supply PRC, Chair: Ellen Hilert, DLMSO/DLA J-6251, 703-767-0676 (DSN 

427), ellen.hilert@dla.mil 

2. FUNCTIONAL AREA: Primary: Supply 

3. REFERENCES: 

 a. DoD 4140.1-R, "DoD Supply Chain Materiel Management Regulation" (available at: 

http://www.dtic.mil/whs/directives/corres/html/41401r.htm). 

b. DLMSO memorandum dated May 30, 1996, subject: Revised Addendum to Approved 

MILSTRIP Change Letter (AMCL) 138, Revision of the Transportation Control Number (TCN) 

Field in MILSTRIP Transactions. This document provided the business rule update for inclusion of 

the TCN under MILSTAMP (later DTR) structure/rules in the material release confirmation and the 

shipment status transaction formats. 

c. DLMSO memorandum dated March 19, 2007, subject: ADC 223, DLMS Shipment 

Status Enhancements: Secondary Transportation Number, Initial Shipping Activity, Carrier 

Identification, and Port of Embarkation (POE) 

d. DLMSO memorandum dated April 30, 2007, subject: Proposed DLMS PDC 265, 

DLMS Material Release Confirmation: Secondary Transportation Number, Carrier Identification, 

and POE 

4. REQUESTED CHANGE: 

 a. Title: Shipment Status (DS 856S): PD, TP, Project Code, Special Requirements Code 

 b. Description of Change: 

 (1) This change establishes a requirement to provide additional data elements in the 

DLMS 856S. All shipment status under DLMS shall include the following data elements when 

applicable and available. These data elements shall be perpetuated from the requisition to the 

shipment status by all Sources of Supply (SoS)/Inventory Control Points (ICPs)/Integrated Material 

Managers (IMMs). The Distribution Standard System will perpetuate these data elements from the 

material release order. 
2

• Project Code 

• Special Requirements Code (MILS RDD coded entries, e.g. 999, N for Not Mission 

Capable, etc.) 

• Priority Designator 

 (2) In addition, all shipment status under DLMS shall include the transportation 

priority as determined under reference 3.a. in support of time definite delivery procedures or as 

derived from other criteria. 

 c. Background for MPC Requirement. Although expanded to all DLMS shipment status 

transactions, this change originated with a requirement to support the Material Processing Center 

(MPC): 

 (1) Today, the DDC-operated MPCs support the Navy by working with the ships to 

identify material sortation requirements so that when material is received, it is pre-sorted to the 

ships request so once on board, the material can be delivered to the various storerooms or other 

areas to be placed on the shelf. This takes the time-consuming sortation burden of the work off the 

sailor and places it on the worker within the MPC. 

 (2) Material sortation today within the MPC to make delivery to the ship is a labor 

intensive manual effort. This is accomplished by reviewing each 1348-1 for the Supplementary 

Address, Transportation Priority code, Project Code, Document Number Series, and RDD/Special 

Requirements Code, to the ships individual sortation sheet identifying all storeroom/sortations. 

After the manual effort has been performed, the item is then taken to the appropriate tri-wall for 

consolidation. Once the material sortation and consolidation has been completed, the material will 

be manifest and delivered to the ship/customer based on pre-determined delivery schedules or based 

on the ship/customer calling for a delivery of his material. 

 

 d. Detailed Procedure Revisions: 

 (1) Revise DLMS/MILSTRIP. 

(a) SoS/ICPs, DSS, and DAAS will include the additional data fields in the DLMS 

856S. 

(c) DLMS Supplement revisions are identified at Enclosure 1. 

(d) DLMS manual, Vol 2, Chapter 5, revisions are identified at Enclosure 2. 

 
3

5. REASON FOR CHANGE: 

a. MPC Requirement. System changes to DSS were made to include MPC functionality 

and to improve systems processing and operational efficiencies. One of the processing changes 

made to DSS was the inclusion of sortation logic that uses key data elements from the 856S, 

allowing DSS to systematically identify material sortation vice the manual process performed 

today. DAASC will make distribution of the 856S to the appropriate MPC operated by the Defense 

Distribution Center (DDC) receiving site which will hold the material for later delivery to the Navy 

ship. The MPC will incorporate the additional data in the due-in record and use for management 

information in their sortation process. Key data elements include the Supplementary Address, 

Transportation Priority (or Priority Designator), Project Code, Document Number series, and coded 

RDD/Special Requirements Code, allowing DSS to systematically perform the sortation 

identification requirements based on the customer’s request. This process will significantly reduce 

the manual effort performed today and significantly improve material sortation so when the material 

is delivered to the ship, the ship can more easily receipt and take custody of the material to delivery 

to the appropriate storeroom for put away. 

 b. Standard DLMS Requirement. 

 (1) The transportation priority will be provided, not just for MPC requirements, but 

for all shipments. In this regard, the TP can more accurately communicate to the customer when he 

will receive his shipment because there is a Time Definite Delivery (TDD) standard for each TP. 

Using the date shipped and the TDD days to deliver, the customer could more accurately forecast 

the arrival date of materiel. Other uses of this information for metrics and other processes might 

also be considered. 

 (2) Until the 1996 MILSTRIP revision to adopt the 17-position Transportation 

Control Number, the priority designator was carried in the Shipment Status as perpetuated from the 

material release order (reference 3.b.). Due to space constraints the PD had to be dropped. This 

change allows it to be reinstated. 

 (3) Inclusion of the Project Code and Special Requirements Code provides full 

visibility to all status recipients. The inclusion of these codes in conjunction with the PD allows all 

precedence indicators and project identification information to be available to the receiving activity. 

This information may be used for receipt scheduling and prioritization. Additionally, until all 

supply sources include the TP as a data element in shipment status, the standard TDD for the 

shipment can be determined based on the combination of these codes. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: 

 (1) The 856S will provide key data elements that are used by the DDC in DSS for 

the MPC material receipt/sortation process. This change will permit the DDC to further support our 

DSS operated MPCs under DLMS. 
4

 (2) In making this change for the MPC, additional standard data content is being 

adopted for its value-added content to the shipment status under DLMS. 

 b. Disadvantages: Negative aspects of this change identified during coordination by 

DLA: Inclusion of the TP will require significant development hours for the ICP system. Specific 

identification of the TP is not needed because the military understand what the typical time frames 

it takes to receive a part once shipped. The priority designator, project code and RDD have already 

been provided via the requisition by the customer and are normally the retained as submitting so 

repeating on all shipment status causes perpetuation of unneeded data content. 

7. IMPACT: 

 a. Data Content/Procedures: This change will require changes to the following:

 (1) Distribution Standard System (DSS). Implementation May 2007. 

 (2) SoS/ICP/IMM systems which generate shipment status. A phased and 

staggered implementation is authorized. Components may adopt this change under modernization 

or update modernized systems when most practical. It is recommended that this change be 

implemented in coordination with ADC 223, DLMS Shipment Status Enhancements: Secondary 

Transportation Number, Initial Shipping Activity, Carrier Identification, and POE, (reference 3.c.) 

and PDC 265, DLMS Material Release Confirmation: Secondary Transportation Number, Carrier 

Identification, and POE, (currently pending approval) (reference 3. d.). 

 (2) DS 856S to accommodate the new data fields. DLMS-capable receiving 

applications which have not yet adopted these DLMS enhancements must verify that inclusion of 

the new data will not cause transactions to reject. 

 (3) DAAS processing. Perpetuate data content upon approval. Update to 

WebVLIPS to show TP will occur as soon as feasible.

 b. Publications: This change will impact DOD 4000.25-M and implementing instructions.
5

Enclosure 1: DLMS Supplement Revisions 

Item # Location Revision to 

4030 856S 

Reason Federal IC 

Impact 

1. DLMS 

Introductory 

Note: 

Added ADC 242 to DLMS Introductory note 3: 

- ADC 242, Shipment Status (DS 856S) in Support 

of MPCs: PD, TP, Project Code, Special 

Requirements Code 

To identify DLMS 

changes included in the 

DS 

No update 

needed 

2. 2/LQ01/3500 Revise DLMS note for existing code 79:

79 Priority Designator Code 

DLMS Note: 

Use to accommodate legacy system requirements. 

1. Must use to identify the applicable priority 

designator.

2. Authorized DLMS migration enhancement; see 

introductory DLMS 2f.

Provides PD as needed for 

MPC requirement and 

makes it a required 

element under DLMS 

Identifies this data 

element as an authorized 

DLMS enhancement. 

No update 

needed 

3. 2/LQ01/3500 Add new code BD and DLMS Notes

BD Transportation Priority Code 

DLMS Note: 

1. Use to identify the applicable transportation 

priority when available. 

2. Authorized DLMS migration enhancement; see 

introductory DLMS 2f.

Provides TP as needed for 

MPC requirement and 

makes it a required 

element under DLMS 

Identifies this data 

element as an authorized 

DLMS enhancement 

No update 

needed 

4. 2/LQ01/3500 Add new DLMS note 2 to existing code 78:

78 Project Code 

DLMS Notes: 

1. Must use to provide the project code when 

applicable. 

2. Required when applicable to communicate the 

project code associated with the Army Total 

Package Fielding Unit Materiel Fielding Point or 

staging site shipment document. 

3. Authorized DLMS migration enhancement; see 

introductory DLMS 2f. 

. DLMS enhancement; see introductory DLMS note 

2a.

Provides project code 

when applicable as 

necessary for MPC 

sortation 

Identifies this data 

element as an authorized 

DLMS enhancement 

No update 

needed 

5. 2/LQ01/3500 Add new DLMS note 2 to existing code AL:

AL Special Requirements Code 

Provides special 

requirements codes 

(coded values in the RDD 

field) as necessary for 

No update 

needed 
6

1. Must use to identify special handling and 

priority codes when applicable. Under DLSS, this 

is carried in the required delivery date field. 

2. Authorized DLMS migration enhancement for 

optional use; see introductory DLMS 2f. 

. DLMS enhancement; see introductory DLMS note 

2a.

MPC sortation 

Identifies this data 

element as an authorized 

DLMS enhancement 
Enclosure 2 – DLMS Manual Procedures. 

ADC 223 revisions are included in the text below. PDC Changes identified in bold italics.

C5.2.1.2. Shipment Status. Shipment status informs organizations of the actual shipping dates (such 

as the date released to the carrier), the release criteria for shipments, or shipment delay notifications. It 

also provides for an interface with transportation and for shipment tracing by organizations under DoD 

4500.9-M. The shipment status may be provided by the shipping activity or by the supply source 

using the DLMS Supplement 856S. Shipment status provided by shipping activities will reflect 

enhanced data content under DLMS and support item unique identification (IUID) and intransit 

visibility requirements as directed under DoD policy/procedures (DoD 4140.1-R)1. Shipment status 

provided by the supply source for direct vendor deliver (contractor direct) or in response to a 

requisition follow-up will include enhanced data content when available. DLMS enhancements for 

expanded data content, including Passive Radio Frequency Identification (RFID) and IUID include, 

but are not limited to the following:2

 

 

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

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 Item Unique Identification (IUID) 

and/or serial number. Serial number without applicable IUID may only be used during MILS/DLMS 

transition and pending implementation of IUID capability. Additional UID information as identified in 

the DS 856S is optional. 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 name and Standard Carrier Alpha Code (SCAC). 

 C5.2.1.2.3 Identification of the initial DoD shipping activity (origin) by DODAAC. 

 C5.2.1.2.4 For Outside Continental United States (OCONUS) shipments made via Defense 

Transportation System (DTS), GBL/CBL, parcel post, and small package carrier shipments, specific 

identification of the Port of Embarkation (POE) or Consolidation and Containerization Point (CCP). 

The shipment status will specify air terminal, water terminal, or CCP by applicable qualifier code in 

the DS. (During MILS/DLMS transition, DAAS may substitute a generic terminal qualifier for 

shipment status transactions converted from MILS where the type of facility is unknown.) 

C5.2.1.2.5 Under DLMS, the shipment status shall perpetuate data content as applicable: 

Project Code, the Special Requirements Code (MILS RDD coded entries, e.g. 999), and Priority 

Designator . 3

 

1

 DoD 4140.1-R guidance for passive RFID and IUID requirements is pending publication as of the date of this change. 

Interim guidance is available at http://www.acq.osd.mil/log/rfid/index.htm (RFID) and http://www.acq.osd.mil/dpap/UID

(IUID). 

2

 Refer to ADC 223 approved for phased and staggered implementation. 

3

 Refer to ADC 242 approved for phased and staggered implementation. 
ii

 C5.2.1.2.6 The Transportation Priority shall be included in all shipment status transactions 

as derived under DoD 4140.1-R guidance or other pertinent criteria. 4

4

 Refer to Footnote 3. 

Intervening text not shown 

Renumber existing Table C5.T1

C5.2.6.5.1. Shipment Status to DAAS. Supply sources shall transmit shipment status to DAAS for all 

supply source requisitions to include DS 856S for all DVDs, as required. Upon receipt of shipment 

status, DAAS shall convert the shipment status to the appropriate response type of status and make 

distribution per paragraph C5.2.7, below. Except for cancellation and rejections, DAAS shall send 

status to designated status recipients as identified by the activity designated by a significant media 

and status code (DoD or Component level), and to the activity designated by a significant alphabetic

distribution code, or significant numeric code (http://www.dla/j-6/dlmso/qualifiers/qualifiers.htm) and 

to any activity identified by DoDAAC as a party to receive status. Supply sources shall give shipment 

status for exception ship-to addresses. 

 C5.2.6.5.1.1 DAAS will also provide a copy of shipment status for material to be delivered to 

Navy ships to the applicable Material Processing Center (MPC) operated by the Defense 

Distribution Center (DDC) at the co-located Distribution Depot (DD) receiving site. In order to 

accomplish, this DAASC will maintain a table of Navy ships DoDAACs associated with a DD which 

provides MPC support to the specified Navy ship. The DDC, in coordination with the Navy, will 

provide Navy ship updates to DAASC as needed. When DAAS processes the 856S/AS8 and the shipto DoDAAC begins with N, R, or V, DAAS will match the ship-to DoDAAC to the Navy ships/MPC 

table. When an appropriate DD/MPC is identified, an 856S will be forwarded to the Distribution 

Standard System for establishment of a due-in record at the applicable MPC. 

 C5.2.6.5.1.1.1 MPCs which will receive shipment status are located at the DD locations 

identified in Table C5.T1. 

Table C5.T1. Distribution Depots and Co-located Material Processing Centers

DD with co-located MPC DD DoDAAC MPC Routing Identifier 

DD Norfolk SW3117 PSJ 

DD Jacksonville SW3122 PSU 

DD San Diego SW3218 PSK 

DD Puget SW3216 PSN 

DD Yokosuka SW3142 PSL 

DD Sasebo SW3143 PSM 

 

4

 Refer to PDC 263. 
iii

DD Guam SW3147 SCN 

DD Pearl Harbor SW3144 PSY 

C5.2.6.5.1.1.2. The MPC will use the Supplemental Address, Project Code, Special Requirements 

Code, and Transportation Priority or Priority Designator from the due-in record or the shipment 

documentation to sort material for delivery per the Navy customer direction.