ADC 229

Material Processing Center (MPC) 

Material Receipt and Delivery Supply Status 

1. ORIGINATOR: 

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

 

 b. Originator: Mr. David M. Olenick, DSN 771-5186 / COMM 717-770-5186: or e-mail: 

Dave.Olenick@dla.mil 

2. FUNCTIONAL AREA: Primary: Supply 

3. REQUESTED CHANGE: 

 a. Title: MPC Material Receipt and Delivery Supply Status 

 b. Description of Change: This change establishes procedures for preparation of supply status 

transactions (DLMS 870S, equivalent of MILSTRIP Document Identifier AE8) by the Distribution 

Standard System (DSS) upon MPC receipt or delivery of material. This supply status provides 

notification to the Navy ship/customer and other status recipients for tracking material and for 

performance metrics. This change adapts a currently-used Navy-unique process for inter-NavyDefense Distribution Center (DDC) use under DLMS. Revisions identified after staffing are identified 

by yellow highlight. 

 c. General Procedures: 

 (1) An 870S transaction from DSS with status code of “NL” will be created at the time of 

material receipt in the MPC, to include receipt date/time, and sent to DAAS. DAAS will re-format to 

AE_ transactions that the Navy/ships receive today from the Navy Logistics Customer Asset Visibility 

(LCAV). 

 (2) An 870S transaction from DSS with “NW” status will be created when signature 

delivery has been posted in DSS, to include date/time, and sent to DAAS. DAAS will re-format to 

AE_ transactions that the Navy/ships receive today from LCAV. (DAAS will convert the NW to BA 

status pending Navy program changes to accept the new status code.)

 d. Background: 

 (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 store rooms or other areas to be 

placed on the shelf. This takes the time-consuming sortation burden of the work off the sailor. 

 (2) In this process, the DDC uses the Navy LCAV web-based system for this process. 

LCAV is used to scan in a document or manually enter in a document to show material has arrived in 

the MPC. LCAV creates an AE1 transaction with NL status code, sent out every 15 minutes to 

DAAS, to pass to the ship/customer. This AE1 provides system notification the material has arrived at 

the MPC. 
2

 (3) After material has been sorted and consolidated, the sorted 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. Material is manifested in LCAV with a date and 

time, the manifest produced, and then taken to the ship/customer. After the manifest has been signed, 

the MPC person comes back and places in LCAV the actual date and time and POD name, thus closing 

out the manifest. When this is done, every 15 minutes, LCAV sends out another AE1 on each 

document number that was on the manifest(s) with BA status code for DAASC to pass to the 

ship/customer. This AE1 provides system notification the material was delivered to the ship. 

 (4) The Navy uses AE1 with NL and BA status for performance measurement and 

material visibility. 

 e. Detailed Procedure Revisions: 

 (1) Status Codes. Revise DLMS/MILSTRIP Appendix 2.16, Supply Status, to include the 

following codes. Supply Status NL is currently used by the Navy and will be adopted for interNavy/DDC use. Supply Status NW is a new code replacing the BA status currently used by the Navy 

for MPC delivery. 

Code Explanation1

NL Item received by the Logistics Support Center (LSC)/ Material Processing Center 

 (MPC) (MILSTRIP rp 4-6). Contact local LSC/MPC for delivery. 

 

NW Item delivered by the MPC (MILSTRIP rp 4-6). 

 (2) Transaction Formats/DAAS Conversion Mapping: 

(a) There is a DLMS requirement to identify the organization sending the transaction. 

For this exchange, the originating organization will be identified by the routing identifier (RI) of the 

Distribution Depot (DD). An additional DLMS qualifier SB, Storage Area, will be established in the 

870S header for this purpose. The DD is not shown in the AE_ format, so DAAS maps will only use 

the MPC RIC for conversion purposes. A new DLMS qualifier WD, Storage Facility at Destination, 

will be established in the 870S detail for this purpose. This RI will be mapped by DAAS into the AE_ 

RI-From (rp 4-6) and RI at 67-69. The MPC RI will not be carried twice in the DLMS format as it is 

in the LCAV AE1 format. 

(b) DAAS will use standard MILS/DLMS distribution rules for distribution of the 

supply status to eligible status recipients. 

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

(d) DAAS mapping revisions are identified at Enclosure 2. 

(e) Examples of current AE1 and approved 870S formats are provided at Enclosure 4. 

 (f) DLMS Vol 2, Chapter 5, revisions are provided at Enclosure 5. 

 

1

 Record positions will not be included in the DLMS dictionary definition. 
3

(g) MILSTRIP Appendix 3.10 revisions are provided at Enclosure 6. 

 (3) Routing Identifier Code/DODAAC Files. The Navy will update the clear text 

address associated with the MPC in the DAASC Routing Identifier Table/DODAAC Table to identify 

the location to the DDC. 

 (a) MPCs applicable to this process are identified at Enclosure 3. 

 (b) Enclosure 3 also shows an example of an MPC clear text name which should be 

identified the DDC/DD (currently shows only Navy FISC). 

4. REASON FOR CHANGE: DDC is replacing Navy Logistics Customer Asset Visibility 

(LCAV) web-based system that supports the MPCs with DSS MPC functionality to improve systems 

processing and operational efficiencies. DSS today does not provide supply status transactions. This 

change authorized the MPC using DSS to create DLMS compliant supply status using the 870S and 

Supply Status NL or NW. 

5. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: 

 (1) The 870S transactions will provide the ability to track MPC material receipt and 

delivery and Logistics Response Time (LRT) performance. The addition of date/time will provide a 

DLMS enhancement for future use. Also, as this and additional MPC functionality is incorporated in 

DSS, DSS will replace in total the Navy LCAV system, thereby allowing the Navy to discontinue 

LCAV systems and operational support costs. The use of NW vice BA allows for systematic 

association with the MPC function vice the standard supply status usage. However, since the Navy 

cannot accept the NW until RSupply Viking Release due in late 2007, DAAS will convert to the 

current BA status during the interim.

 (2) This change will permit the DDC to support the MPC migration to DSS under DLMS 

as a near-term implementation requirement. It is understood that the process may evolve as 

unresolved issues identified in paragraph 6.b. below are explored.

 b. Disadvantages: None identified. 

6. IMPACT: 

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

 (1) Distribution Standard System (DSS) 

 (2) DLMS/MILSTRIP to accommodate the new Status Codes and to the 870S format; and 

MPC procedures 

 (3) Navy applications to process the new Supply Status NW 

 (4) DAAS should update WebVLIPS to include identification of the MPC Routing 

Identifier (not required for initial implementation). 
4

 (5) Logistics Response Time (LRT)/Customer Wait Time (CWT) 

 (6) Asset Visibility applications, e.g. GTN and TAV/IDE 

b. Unresolved Issues: The issues below are identified for continued discussion and exploration. 

By agreement, the above changes will be pursued for late-March 2007 implementation rather than 

delay until all issues can be resolved. Full resolution may ultimately require significant reengineering of some aspects of the process. 

 (1) Material Accountability: With DLA/DDC performing the MPC function for the 

Navy and temporarily holding the material before delivery, there are concerns regarding material 

accountability which must be explored. The MPC function is currently considered to be outside DOD 

4140.1-R, DOD Materiel Management Regulation, business rules which require that the storage 

activity maintain materiel accountability for assets in their custody. MILSTRAP/DLMS procedures 

which ensure that the storage activity maintains the property accountability record for all materiel in 

storage and is responsible, as a minimum, for materiel custody, care, receipt, storage, and issue, are bypassed under the current MPC function. 

 (2) Material Receipt Acknowledgement (MRA). DLMSO is concerned that the delay 

for posting of the accountable receipt for material held by the MPC, is perpetuated to delays in 

preparation of the MRA which is a DOD requirement for material shipped from wholesale supply 

sources. The MRA may become an important requirement for timely payment of vendors. 

 (3) Acceptance Report under Wide Area Work Flow-Receipt and Acceptance 

(WAWF-RA). DLMSO is also concerned that the delay for true receipt processing of the material 

held by the MPC is also perpetuated to the preparation of the Acceptance Report. The Acceptance 

Report is required for FOB destination shipments from vendors in order to properly process the 

vendor’s invoice. 

 c. Publication: 

 (1) This change will impact DOD 4000.25-M and implementing instructions. 

 (2) NAVSUP P-409, MILSTRIP/MILSTRAP Desk Guide, should be updated to include 

Supply Status NW. 

 

Enclosures 
5

Enclosure 1, DLMS Supplement (DS) 870S, Supply Status, Revisions 

# Location Revision Reason 

1. 1/ BSR01 at 

position 20 

Code 4 

Revise note: 

Response to Requisition 

DLMS Note: 

Use to indicate normal requisition supply status. 

Administrative correction 

2. 1/N101 at 

position 50 

Add the following qualifier and DLMS note: 

SB Storage Area 

1. Use to identify the distribution depot 

generating the supply status. 

2 Used when providing Material Processing 

Center (MPC) status.

Allows for required 

identification of the 

organization generating 

the status transaction. 

3. 2/N101 at 

position 90 

Add the following qualifier and DLMS note: 

WD Storage Facility at Destination 

DLMS Note: Use to identify the Material 

Processing Center (MPC).

Allows for identification 

of the MPC. The presence 

of this unique qualifier 

will allow for proper 

interpretation of the 

transaction as MPC status. 

4. 2/DTM01 at 

position 240 

Add the following qualifiers and DLMS notes: 

050 Received 

DLMS Note: Use with Status Code NL to 

identify the date material is received at the 

Material Processing Center (MPC) for temporary 

storage pending delivery to the Navy vessel. 

035 Delivered 

DLMS Note: Use with Status Code NW to 

identify the date material is delivered from the 

Material Processing Center (MPC) to the Navy 

vessel (signature date). 

Allows for identification 

of the dates provided on 

the MPC status 

transactions. 

5. 2/DTM03 at 

position 240 

Open the time date element and add the DLMS 

notes: 

DLMS Note: 

1. Use when providing MPC receipt or delivery 

status to provide the associated time. 

2. Express the originating activity's time in UTC. 

3. Express time in a four-position (HHMM) 

format.

Allows for identification 

of the time associated with 

the MPC receipt or 

delivery of material using 

universal time coordinate 

(zulu time). This time 

may differ from the time 

transaction is generated. 
6

Enclosure 2, DAAS Map Revisions 

Field Name Record 

Position 

(DLSS) 

Conditions DLMS Data Element Table 

Gateway 

Provider 

4-6 If RP 4-6 = SGA or SHA N101=GP 

N103=M4 

N104=SGA 

N106=FR 

1 

Management 

Control 

Activity 

4-6 If RP1-2=AB or AE 

If RP 4-6=A81, A82, A83, A84, A85, A86, A87, 

A88, F2M, F4M, F6M, F7M, F8M, FFF, FG6, FH6, 

FL6, S5C, S5E, S5F, S5G, S5I, S5M, S5T, S5V, 

MPM, HG2, HG3, HG4, or HDN 

N101=Z5 

N103=M4 

N104=RP4-6 

N106=FR 

1 

Monitoring 

Party 

4-6 If RP1-2=AB or AE 

If RP 4-6 = FNH, BY7, or N65 

N101=ZS 

N103=M4 

N104=RP4-6 

N106=FR 

1 

Owning 

Inventory 

Control Point 

4-6 If RP1-2=AB or AE N101=Z4 

N103=M4 

N104=RP 4-6 

N106=FR 

1 

Distribution 

Depot 

DLMS only if MPC Supply Status (870S and MPC 

identified at 2/N101=WD) 

Note: The DLMS format will show the standard 

DSS depot routing identifier as originating the 

transaction in the 1/N101, qualifier SB. For 

conversion, the AE_ format will show the MPC 

routing identifier in both 4-6 and 67-69. 

N101=SB 

N103=M4 

N106=FR 

12

Last Known 

Source of 

Supply 

67-69 If RP1-2=AE and RP67-69≠Blanks N101=Z8 

N103=M4 

N104=RP 67-69 

2 

Material 

Processing 

Center 

4-6 

67-69 

If MPC Supply Status (870S and MPC identified at 

2/N101=WD) 

Note: The DLMS format will show the standard 

DSS depot routing identifier as originating the 

transaction in the 1/N101, qualifier SB. For 

conversion, the AE_ format will show the MPC 

routing identifier in both 4-6 and 67-69. 

N101= WD

N103=M4 

N104=RP 4-6 and 67-69 

2 

Status Code 65-66 If RP1-2=AE 

If MPC Supply Status and LQ02=BW convert to 

RP 65-66=BA (temporary requirement pending 

Navy implementation of BW)

LQ01=81 

LQ02=RP 65-66 

2 

Estimated 

Shipment Date 

70-73 If RP1-2=AE 

RP70-73 (Function YDDD2CCDAT) 

DTM01=369 

DTM02=()CCYYMMD

D 

2 

Received at 

MPC Date 

70-73 If MPC Supply Status (870S and MPC identified at 

2/N101=WD) 

RP70-73 (Function YDDD2CCDAT) 

DTM01=50 

DTM02=()CCYYMMDD 

2 

Delivered by 

MPC Date 

70-73 If MPC Supply Status (870S and MPC identified at 

2/N101=WD) 

RP70-73 (Function YDDD2CCDAT) 

DTM01=035 

DTM02=()CCYYMMDD 

2 

Received at N/A DLMS only DTM01=50 2 

 

2

 Table 1 (vice Table 2) corrected subsequent to publication of the ADC. 
7

MPC Time DTM03=()HHMM 

Delivered by 

MPC Time 

N/A DLMS only DTM01=035 

DTM03=()HHMM 

2 

Enclosure 3, DDC MPC List 

MPC NAME MPC CODE MPC RIC MPC UIC

DLA Jacksonville (Mayport) - DDJF 04A PSU 69267

DLA Norfolk-DDNV 01E PSJ 69262

DLA Pearl Harbor-DDPH 05A PSY 69270

DLA Puget Sound-DDPW 03A PSN 69264

DLA San Diego-DDDC 02A PSK 69263

DLA Yokosuka-DDYJ 06A PSL 4357A

DLA Yokosuka-Sasebo - DDYJ 06C PSM 4358A

DLA Yokosuka-Guam 06F SCN B3105

Example of clear text name: 

PSU is currently identified as the FISC on the DAAS Routing Identifier Query. The Navy should 

update MPC address information to associate the MPC with the DDC. 

FLEET AND INDUSTRIAL SUPPLY CENTER 

DET MATERIAL PROCESSING CTR MAYPORT 

BUILDING 191 NAVAL STATION MAYPORT 

MAYPORT FL 32218-5000 
8

Enclosure 4, Sample Navy-originated AE1 Transactions 

AE1PSK 5962010752660 EA00002R205506276Y201 A 03284NLPSK62840000000 

AE1PSK 5962010752660 EA00002R205506276Y201 A 03284BAPSK62840000000 

Sample DSS-originated 870S Transactions: 

ISA*00* *00* *10*W25G1U *10*S36121 

*070306*1712*U*00401*000000001*0*P*.~ 

GS*RS*W31G1Z*S36121*20070306*1712*000000001*X*004010~ 

ST*870*0001~ 

BSR*4*CO*Z*20070306***1712****00~ 

N1*SB**M4*SDF**FR~ 

HL*1**W~ 

DTM*097*20070306~ 

REF*TN*W31G3H6103H047~ 

N1*WD**M4*PSJ~ 

LM*DF~ 

LQ*0*AE8~ 

LQ*COG*9L 

LQ*A9*N69262~ 

LQ*SMI*BL~ 

LQ*DF*S~ 

PO1**3*EA***FS*6920002234919~ 

ISR*UR~ 

DTM*050*20070306*1615~ 

LM*DF~ 

LQ*83*A~ 

LQ*81*NL~ 

SE*19*0001~ 

GE*1*000000001~ 

IEA*1*000000001~ 

ISA*00* *00* *10*W25G1U *10*S36121 

*070306*1712*U*00401*000000002*0*P*.~ 

GS*RS*W31G1Z*S36121*20070306*1712*000000002*X*004010~ 

ST*870*0001~ 

BSR*4*CO*Z*20070306***1712****00~ 

N1*SB**M4*SDF**FR~ 

HL*1**W~ 

DTM*097*20070306~ 

REF*TN*W31G3H6103H047~ 

N1*WD**M4*PSJ~ 

LM*DF~ 

LQ*0*AE8~ 

LQ*COG*9L 

LQ*A9*N69262~ 

LQ*SMI*BL~ 

LQ*DF*S~ 

PO1**3*EA***FS*6920002234919~

ISR*UR~ 

DTM*035*20070306*1616~ 

LM*DF~ 

LQ*83*A~ 

LQ*81*NW~ 

SE*19*0001~ 

GE*1*000000002~ 

IEA*1*000000002~ 
9

Enclosure 5, DLMS Manual Revision 

DoD 4000.25-M Volume 2, June 2005 

Change 2 

C5.2.2.1. Supply Status. Use DS to Federal IC 870S, Supply Status. 

 C5.2.2.1.1. Response to Requisition

 C5.2.2.1.1.1. Processing GFM. Supply sources (or MCAs, processing GFM 

transactions), use the DS 870S with appropriate status codes to convey advice to organizations. It is 

used to convey notice of action taken or being taken on requisitions and requisition-related 

transactions; such as, retransmitted requisitions, cancellations, modifications, and requisition inquiries 

(follow-ups and/or requests for supply assistance). Organizations must identify additional status 

addressees in the original requisition and/or requisition-related transactions, as applicable. DAASC 

generates supply status in selected situations resulting from item identification edits but will indicate 

their DoDAAC as the MESSAGE FROM address in the supply status. 

 C5.2.2.1.1.2. Reporting Status Decisions. Supply sources or MCAs shall 

respond to requisition(s) to advise activities of action taken (as indicated), alone or in combination, to 

any of the requests listed below. This includes status upon processing a requisition inquiry (follow-up 

and request for supply assistance) or a cancellation request, and rejection status when rejecting 

transactions. 

 C5.2.2.1.2.1. Backorder. 

 C5.2.2.1.2.2. Partial issue or partial other action. 

 C5.2.2.1.2.3. Material substitution. 

 C5.2.2.1.2.4. Unit of issue changes. 

 C5.2.2.1.2.5. Retransmitted (rerouted) requisitions. 

 C5.2.2.1.2.6. Cancellation, modification, or inquiry. 

 C5.2.2.1.2.7. Any circumstance that predicts that issue may not be made 

within the timeframes established for the assigned priority designator (PD). 

 C5.2.2.1.2. Material Processing Center (MPC) Status

 C5.2.2.1.2.1. The MPC will provide NL Status to notify the Navy 

ship/customer that material has arrived at the MPC for sortation and temporary storage pending 

delivery to the customer. 

 C5.2.2.1.2.2. The MPC will provide NW Status to provides systematic 

notification material has been delivered from the MPC to the Navy ship/customer. 

 
DoD 4000.25-1-M, January, 2006 

Change 1 

Enclosure 6, MILSTRIP Revision 

AP3.10. APPENDIX 3.10

SUPPLY STATUS

(ISSUES FROM STOCK)

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier 1-3 Enter DI AE_. 

Routing Identifier 4-6 Enter RI of the supply source furnishing the supply status 

(RI From). If used as a DI AE6 transaction, enter the RI of 

the supply source to which the transaction will be sent (RI 

To).1

Media and Status 7 Enter M&S as shown in the original requisition. 

Stock or Part Number 8-22 Enter NSN or part number. 

Unit of Issue 23-24 Enter U/I. 

Quantity 25-29 a. Enter quantity for which status is provided. 

b. For ammunition items only (FSG 13), enter an “M” in 

rp 29 to express in thousands any quantity exceeding 

99,999. Example: A quantity of 1,950,000 will be 

expressed as 1950M (1950 in rp 25-28 and an “M” in rp 

29). 

Document Number 30-43 Enter document number as shown in the requisition. 

Suffix 44 a. Enter suffix applicable to quantity in rp 25-29 when the 

requisitioned quantity is divided into separate supply 

actions. 

b. When the requisition quantity is not divided, leave this 

field blank. 

Supplementary Address 45-50 Enter data from original requisition. 

Signal 51 Enter data from original requisition. 

Fund 52-53 Enter date from original requisition. 

Distribution 54-56 When used as an AE6 to provide status on the processing 

on an LRO, enter 2 for consumables or 3 for reparables in 

rp 54. Otherwise, enter data as shown in the requisition. 

Project 57-59 Enter data from original requisition. 

 

1

 When used by the Material Processing Center (MPC) to notify the Navy customer that material has arrived (NL 

Status) or been delivered (NW or Navy-unique BA Status), rp 4-6 will identify the MPC.
2

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Priority 60-61 Enter data from original requisition. 

Transaction Date 62-64 Enter the day that corresponds with the date of this reply. 

Status 65-66 Enter status code to convey the information regarding the 

status of this transaction. 

Routing Identifier 67-69 Enter the “last known source” to which authorized 

followup action will be directed. If used as a DI AE6 

transaction, the RI will be the activity preparing the 

document.2

Estimated Shipping Date 70-73 When designated by the status code, enter the four-position 

ordinal day by which it is estimated the materiel will be 

shipped.3

Multiple Use4

&5 74-80 

Unit Price 74-80 Enter unit price of the stock or part number shown in rp 8-

22. When the status code in rp 65-66 relates to an 

erroneously routed requisition, this field will be left blank. 

OR 

Blank (74-75) Leave blank. 

Minimum Order Quantity (76-80) For C8 Status, enter the minimum order quantity. 

OR 

Blank (74-75) Leave blank. 

Federal Supply 

Schedule Number6

(76-80) For DA Status, enter Federal Supply Schedule Number 

constructed as follows: 

rp 76-77 Group (numeric) rp 78-79 Part (numeric) rp 80 

Section (alphabetic). 

For DI AE6 Transactions with Status Code BY

 70-71 Leave blank. 

 72 If status code (rp 65-66) is BY (previously denied MRO), 

enter appropriate denial management code. 

 73 Leave blank. 

Unit Price7

 74-80 Enter unit price of the stock or part number shown in rp 8-

22. 

 

2

 When used by the Material Processing Center (MPC) to notify the Navy customer that material has arrived (NL 

Status) or been delivered (NW or Navy-unique BA Status), rp 67-69 will repeat the identification of the MPC. 

3

 When used by the MPC, this will be the date associated with the material arrival (NL Status) or delivery (NW or Navyunique BA Status). 

4

When used by storage in response to a query by the ICP (DI AE6), this data may be omitted at Component option. 

5

DI AE9 transactions generated by DAAS will always be blank in rp 74-80. 

6

Requirement to use DA requisition rejection status to indicate the supply source is direct ordering from the Federal Supply 

Schedule last reported as not implemented by USAF. Refer to AMCL 132B. 

7

When used by storage in response to a query by the ICP (DI AE6), this data may be omitted at Component option. 
3

For DI Code AE_ Transactions with Status Code CE

 79-80 

For transactions containing rejection Status Code CE in rp 

65-66, supply source will enter the correct unit of issue in 

rp 79-808

. 

 

8

Requirement to provide correct unit of issue when original unit of issue on the requisition could not be converted last 

reported as not implemented by USN and DLA (Subsistence). Refer to AMCL 162.