ADC 401, Attachment Page 1

ADC 401

Procedures and Data Content for DLMS Warehouse Service Request (940S), and 

Warehouse Service Advice (943A), under Navy and Marine Corps BRAC

 

1. ORIGINATOR: Defense Logistics Agency, DLA J331, 703-325-1924 (DSN 427)

2. FUNCTIONAL AREA: Primary: Supply/ Logistics.

3. REFERENCES: 

a. Functional Requirements for DLA’s implementation of Base Realignment and 

Closure(BRAC) Retail Supply, Storage And Distribution (SS&D)/Inventory Management and Stock

Positioning (IMSP) Spiral 2.

b. Functional Requirements Pre-Design for DLA’s implementation of Marine Corps Base 

Realignment and Closure (BRAC) Storage and Distribution Interface (SDI). 

c. DLMS Supplement 940S and DLMS Supplement 943A on the DLA Logistics 

Management Standards Web site at: www.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp.

d. Proposed DLMS Change (PDC) 384, New DLMS Supplement (DS) 940S, Warehouse 

Service Request (for Materiel Protection/Re-Warehousing, Staging, and Picklist/Callout), New DS 

943A, Warehouse Service Advice, and Associated Procedures under Navy BRAC SS&D/IMSP, dated 

April 20, 2010. This change addressed the Navy requirements associated with the Warehouse Service 

request.

e. PDC 384A, Procedures and Data Content for DLMS Warehouse Service Request (940S) 

and Warehouse Service Advice (943A) under Navy and Marine Corps BRAC, dated September 2, 

2010. This change focused on the Marine Corps BRAC usage, but provided several updates to the 

core content of the transaction exchange applicable to the Navy or joint Navy/Marine Corps usage.

4. REQUESTED CHANGE: Green highlighting identifies substantive changes subsequent to 

staffing.

a. This change approves procedures and a new DLMS transaction to communicate a 

Warehousing Service Request (DLMS 940S) including requests for re-warehousing and/or protection, 

staging, or picklist/callout actions, to the Distribution Depot. A new DLMS transaction 

communicating Warehouse Service Advice (DLMS 943A) allows the Distribution Depot to provide 

positive or negative status on the requested action. The DLMS 940S and 943A transactions will serve 

both the Navy and Marine Corps BRAC initiatives, but procedures and data content will differ. 

Following is an overview of some of the applicable business processes:

(1) When used in support of Navy Shipyards (NSY) and Fleet Readiness Centers (FRCs) 

operating under the Navy-DLA BRAC 2005 SS&D concept of operations (CONOPS): 

(a) Materiel purchased by DLA in support of a specific maintenance mission at an 

NSY or FRC site will be protected within DLA Enterprise Business System (EBS) by using Purpose 
ADC 401, Attachment Page 2

Code E. NSY sites will have an additional protection by Requisition Alert Document Number and Job 

Order combination for DLA-owned materiel within EBS and Distribution Standard System (DSS).

During receipt processing of materiel purchased in support of the Navy IA, EBS will recognize the 

open requisition alert1 and generate a request for re-warehousing to the Industrial Activity worksite 

within DSS and inclusion of protection information. DSS will react to this request by moving the 

materiel from the Distribution Depot side of the co-located depot to the IA worksite within the same 

co-located depot (if the materiel is already located within the IA worksite, DSS will apply protection,

and re-warehousing will not pertain). This Warehouse Service Request will reflect applicable 

document number(s) and, for NSY, the JO and KO, which DSS will reference when stowing the 

materiel. 

(b) The NSY (using the Materiel Access Technology (MAT) application) will have 

visibility of available assets by document number and location.2 Based on this information, the NSY 

will request DLA assets be staged and assembled in preparation of the scheduled maintenance. There 

may be instances when NSY sites have Navy-owned assets which will need to be staged to unique 

warehouse locations at the waterfront prior to a maintenance job commencing, this same process 

would be used between NSY (MAT) and DSS. In preparation for maintenance jobs to commence 

when the funded requisition is generated, the picklist is simultaneously generated by the NSY site. 

NSY may generate a picklist by document number at the time of initial submission of a requisition 

alert or at any other time, up to and including the callout of materiel by the submission of funded 

requisitions to DLA or the issuing of Navy owned assets via an MRO. Once the picklist has been 

established by individual document number, then the subsequent staging or issue callout picklist 

actions may be executed by a single WSR (DLMS 940S) citing the picklist control number. During 

the pick of materiel based on a Materiel Release Order (MRO) from DLA and Navy, DSS will be 

required to access additional delivery information.

(c) FRC sites (using the Materiel Resource Planning (MRP) II application) will have 

visibility of DLA and Navy-owned assets, but will not have staging requirements. The FRCs will 

generate picklist/callout request to DSS when a funded requisition is generated from the MRP II

system to EBS regardless if assets are available or not and when an MRO is generated for callout of 

Navy owned assets.

(d) Subsequent to staffing of the original Navy concept for tracking by Materiel Control 

Tracking (MCT) Tag Suffix the concept was revised so that the MCT Suffix would no longer be 

handled as a separate data element for system accountability for this materiel. Under the new concept, 

items broken down into component parts for maintenance actions will no longer be identified on the 

DSS records by their unique suffixes. When individual component parts are moved into maintenance 

shops, they will be tracked by the Navy system. Staffing Note: Additional documentation of this 

process was requested for the approved change. It currently appears that the MCT Tag value will 

remain on the DSS accountable record although not considered in DSS custody while the 

component parts are separately undergoing maintenance action. The DLA Logistics Management 

Standards believes this new procedure may require that HQ DLA address an overarching DOD 

policy change. DOD 4140.1-R, DOD Supply Chain Materiel Management Regulation, directs: 

 1 Refer to ADC 381 (381A and 381B), DLMS Revisions Supporting the Requisition Alert Transaction and Materiel 

Identification associated with DLA Support to Navy NSYs and FRCs under BRAC SS&D/IMSP: The requisition alert 

transaction allows Navy IA sites to notify DLA of their requirements in advance of the funded requisition, thereby allowing 

DLA to procure and position materiel appropriately to support prompt order fulfillment. 

2 Refer to ADC 374, Modification of the Request for Asset Status Inquiry/Report (D S 846I) under BRAC SS&D/IMSP. 
ADC 401, Attachment Page 3

“C5.7.1.1.4. Storage activities shall be accountable for the accuracy of that portion of the total item 

property record showing the quantitative balance in their custody.”

(2) When used in support of Marine Corps Maintenance Center (MCMC) sites under the 

Marine Corps-DLA BRAC 2005 SS&D CONOPS: 

(a) Materials stored by DLA in support of a specific maintenance mission at an MCMC 

site is 100% owned by the Marine Corps and will be protected to specific maintenance projects. 

MCMC systems segregate materiel by Industrial Logistics Support Management Information System. 

(ILSMIS) file designator or Manufacturing Resource Planning (MRP II) stock room designators. 

These designators are replaced within DLA Distribution Standard System (DSS) by using owner 

Routing Identifier Codes (RICs) for each designated maintenance project. Marine Corps may generate 

a request for change of “ownership” within the industrial activity worksite within DSS. DSS will react 

to this request by changing ownership of the designated materiel and physically moving the materiel if 

necessary. The DLMS Warehouse Service Advice (DLMS 943A) allows the depot to provide positive 

or negative status on the requested action. It will be provided only when requested. Additionally, the 

Warehouse Service Advice may be provided without a prior Warehouse Service Request based upon 

Marine Corps business rules for depot operations. Following is an overview of some of the applicable 

business processes. 

(b) The Marine Corps will request an ownership RIC change and DSS will internally 

decide if that request requires a re-warehousing action. For example, if the Marine Corps requests an 

ownership RIC change for the entire quantity in location, DSS may or may not physically move the 

materiel, depending upon how DSS is configured for ownership RIC segregation.

(c) The Warehouse Service Request will reflect applicable document number(s), which 

DSS will reference when stowing the materiel. In addition to standard materiel identification by 

National Stock Number (NSN), this process will apply to:

1. Identification of non-NSN materiel by a Local Stock Number (LSN), and

2. Identification of NSN materiel issued at the unit of use (in lieu of unit of issue) 

identified by a Local Stock Number (LSN).

(d) The Marine Corps requires inclusion of the original and new DSS storage locations 

(“pick location” and “stow location”) to Warehouse Service Advice (DLMS 943A). The MCMC will 

utilize the DSS storage location to link SDR/PQDR materiel stored in the SDR/PQDR storage 

location/“cage” (hereafter referred to as the SDR/PQDR cage) with Marine Corps owned inventory in 

ILSMIS and MRP II. 

(e) MCMC Warehouse Service Request will be identified by Service Requested Code 

M and Event Code M to request ownership transfer/re-warehousing action. There is no requirement 

for change or delete functionality. DSS will react to the ownership RIC change immediately.

(f) Warehouse Service Advice will be provided to the MCMC without a prior 

Warehouse Service Request under Marine Corps business rules as follows:
ADC 401, Attachment Page 4

1. Receipt. The Warehouse Service Advice (943A) will be provided to the 

MCMC subsequent to the reported receipt in order to communicate the storage location which is not 

known until the materiel is physically stowed. (DSS receiving provides the warehouse personnel with 

a recommended stow location, but the user can override that recommendation and stow in a different 

location.) 

2. Discrepant/Deficient Materiel Receipt. If the entire quantity received is 

considered discrepant/deficient, the materiel may need to be segregated and the Warehouse Service 

Advice owner/location will reflect the designated values applicable to discrepant/deficient materiel. 

3. Partial Quantity Discrepant/Deficient Materiel Receipt. If a portion of the 

quantity received is considered discrepant/deficient and is segregated, a second Warehouse Service 

Advice will be prepared for the discrepant deficient quantity.

4. Discrepant/Deficient Materiel in Storage. The Warehouse Service Advice 

(943A) may also be provided without a preceding Warehouse Service Request when 

discrepant/deficient materiel is discovered in storage and is subsequently relocated and transferred to 

the designated owner for discrepant/deficient materiel.

5. Expired Shelf Life Materiel. Shelf life managed materiel stored by DLA in 

support of a specific maintenance mission at an MCMC will be stored and tracked within DLA DSS. 

Upon expiration of shelf life, DSS will prepare a dual inventory adjustment/condition change DLMS 

947I (DAC) to notify the MCMC. The MCMC system will respond with a Warehouse Service 

Request (940S) to relocate the materiel to the appropriate owner RIC (representing the ILSMIS file 

designator or MRP II stock room) or the MCMC will provide disposal guidance, as appropriate.

b. Background: BRAC Concept 

(1) Navy. As a result of the 2005 BRAC decision, retail supply, storage and distribution 

functions and associated infrastructure supporting the Navy industrial/maintenance sites will transfer 

to DLA. The Navy sites consist of NSYs and FRCs. The intent of the directive is to significantly 

improve combat effectiveness while reducing costs by developing a world-class, cost-effective supply 

chain focused on readiness; taking every opportunity to eliminate waste, reduce touches, reduce cost, 

and improve readiness. DLA will be the materiel provider for all standard and non-standard, DLA 

managed and non-DLA managed, consumable materiel required for fulfillment of IA unfunded 

requisition alerts and funded requisitions. DLA will be required to support FRC and NSY sites by 

obtaining assets prior to the start of any maintenance job, protecting and re-locating the assets as 

appropriate. The Distribution Depot will be required to support NSY and FRC by recognizing staging 

and picklist/callout requests and providing the requested service.

(2) Marine Corps. As a result of the 2005 BRAC decision, storage and distribution 

functions for Operating Materiel and Supplies associated infrastructure supporting the MCMC sites 

will transfer to DLA. The Marine Corps sites are Maintenance Center Albany (MCA) and 

Maintenance Center Barstow (MCB). The intent of the directive is to significantly improve combat 

effectiveness while reducing costs by developing a world-class, cost-effective supply chain focused on 

readiness; taking every opportunity to eliminate waste, reduce touches, reduce cost, and improve 

readiness. In accordance with the signed CONOPS, DLA has agreed to provide storage and 

distribution support to the Marine Corps sites. 
ADC 401, Attachment Page 5

(3) Policy: On March 11, 2010, the Deputy Assistant Secretary of Defense for Supply 

Chain Integration, DASD (SCI), authorized DLA to proceed with development of procedures

supporting BRAC including materiel storage at less than the unit of issue and for issuance of non-NSN 

items using a local stock number for identification. Policy decisions originally applicable to the Navy 

BRAC implementation are extended to the Marine Corps implementation where applicable. 

c. Detailed Procedure associated with Navy BRAC:

(1) EBS Re-Warehousing and/or Protection Request:

(a) NSY and FRC sites will communicate the need for materiel in support of specific 

maintenance jobs with a Requisition Alert to DLA. The request will require DLA to position and 

protect materiel at the IA worksite. 

(b) There will be instances when the materiel is physically located at the co-located 

depot and is available immediately to fill the request. EBS will communicate the requirement to rewarehouse and protect the materiel to the IA worksite. A DLA request for re-warehousing and/or 

protection will reflect Service Performed Code 7, EBS Protection/Re-Warehousing Request. When the 

action is completed (materiel re-warehoused and protect the materiel to the IA worksite), DSS will 

notify EBS by providing Warehouse Service Advice, DLMS 943A. Upon receipt of the 943A, EBS 

will update the protection table and generate a Supply Status, 870S, with PQ status indicating the 

requisition alert document number referenced in the supply status has been protected. The requisition 

alert sales order in EBS will be updated with the same status and considered filled.

(c) When an availability at an NSY site is completed the NSY MAT system will notify 

EBS to remove protection against specific document number and Job Order via DLMS 846A. At this 

time EBS will communicate the requirement to unprotect materiel associated with the specific 

document number and JO/KO, via DLMS 846A. When the action is completed DSS will notify EBS 

with a DLMS 846A. Upon receipt of the 846A, EBS will remove entry from the protection table and 

reply to NSY MAT system with 846A. Assets will then be available for global distribution. 

(d) At a later period in time, unprotected stock will be reviewed and if re-warehousing 

is required a 940S will be generated requesting materiel be re-warehoused from the IA worksite to the 

Distribution Depot worksite via A DLA request to re-warehouse will reflect Service Performed Code 

7, EBS Protection/Re-Warehousing Request, with Event Identification code ‘S’. When the action is 

completed (materiel re-warehoused to the Distribution Depot worksite), DSS will notify EBS by 

providing Warehouse Service Advice, DLMS 943A. Upon receipt of the 943A, EBS will move the 

materiel from storage location ‘EA’ to ‘AA’. Assets will then be available for global distribution.

(e) Materiel protected within EBS will be reflected in Ownership Code ‘E’. Unique 

logic has been added to EBS to remove assets with no movement or activity in a specified period of 

time from protection and make them available for global distribution. When this occurs, EBS will 

communicate the requirement to unprotect and re-warehouse materiel from the IA worksite to the 

Distribution Depot worksite. A DLA request to re-warehouse will reflect Service Performed Code 7, 

EBS Protection/Re-Warehousing Request, with Event Identification code ‘S’. When the action is 

completed (materiel re-warehoused to the Distribution Depot worksite), DSS will notify EBS by 

providing Warehouse Service Advice, DLMS 943A. Upon receipt of the 943A, EBS will move the 

materiel from storage location ‘EA’ to ‘AA’. Assets will then be available for global distribution
ADC 401, Attachment Page 6

(f) If materiel is physically located at the co-located depot of IA ‘home site’ to support 

an off-station forward site support requirements, when the maintenance is being done at a facility other 

than the ‘home site’, the request to re-warehouse and protect will include the DoDAAC of the forward 

site. 

1. DSS will react to this re-warehousing request using the current transshipment 

process. This will allow for the pick, pack, and shipment of the materiel to the forward site. The fact 

that this is an off-base shipment will be denoted on the Re-Warehousing Ticket. The re-warehousing 

pick will be performed by the IA site and completed in DSS. The Re-Warehousing Ticket will be 

attached to the materiel and the materiel will be taken to the DLA Transportation Office for 

transshipment. The DSS transshipment process will generate all the necessary shipping and 

transportation documentation such as Commercial Bills of Lading, Government Bills of Lading, 

Hazardous Manifests, MIL-STD-129 Labels, Small Parcel Carrier Labels, and Transportation Control 

and Movement Documents (TCMD) (for over-ocean shipments) utilizing Defense Transportation 

Coordinator Initiative (DTCI) and Surface Deployment and Distribution Command (SDDC) rates. 

Passive and Active Radio Frequency tags may also be generated and affixed to the materiel. The DSS 

transshipment process automatically interfaces with all port and carrier systems as necessary. The 

transshipment process will tie the shipment to the open DSS Re-warehousing “Put-Away.” [Staffing 

Note: The transshipment process will implement generation of a DLMS 856S, Shipment Status, upon 

implementation of 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 Radio Frequency Identification (RFID) 

(Staffed as PDC 424)]. The materiel will be physically shipped to the off-station site. 

2. When the materiel arrives at the off-station site the DSS Re-warehousing 

Ticket will be scanned and the location where the materiel is put-away will be recorded in DSS. The 

site has the ability to query open re-warehousing to ascertain the transshipment information such as 

carrier tracking numbers so the materiel location and status can be determined while the materiel is intransit. When the action is completed (materiel re-warehoused at the forward site) DSS will notify 

EBS by providing Warehouse Service Advice, DLMS 943A. 

3. EBS will update the protection table and generate a Supply Status, 870S, with 

PQ status indicating the requisition alert document number referenced in the supply status has been 

protected. The requisition alert sales order in EBS will be updated with the same status and considered 

filled. 

(g) If the materiel is not physically available at the co-located depot when EBS 

processes the requisition alert, but is available within the DSS network, the request will be placed in 

backorder status3 and EBS will obtain the materiel based upon current redistribution order sourcing 

rules. When the materiel is receipted at the DSS IA collocated depot, EBS will communicate the 

requirement to re-warehouse and protect the materiel to the IA worksite. EBS request for rewarehousing and/or protection will reflect Service Performed Code 7.

 3 Refer to ADC 379, Supply Status Usage to Support Virtual Receipt Processing, Non-Production Materiel Requisitions,

and Requisition Alerts under Navy BRAC SS&D/IMSP, for procedures and new/revised definitions for supply status 

codes.
ADC 401, Attachment Page 7

(h) When re-warehousing and/or protection action is completed DSS will communicate 

the action to EBS with a Warehouse Service Advice, 943A reflecting Action Certification Code A1 

indicating the full quantity has been re-warehoused and protected. 

(i) EBS will protect the quantity and update associated protection table upon receipt of 

the Service Request Advice, 943A. EBS will update the requisition alert and notify the FRC or NSY 

site that materiel has been protected using 870S Supply Status with status PQ.4

(j) When assets on the re-warehousing and/or protection request are not available, the 

Warehouse Service Advice will reflect either Action Certification Code A2, indicating a partial 

quantity was not available for re-warehousing and/or protection or Action Certification Code A3, 

indicating none of the quantity was available for re-warehousing and/or protection. 

(k) EBS will take action to fulfill the open requirement through normal order 

fulfillment. The requisition alert will remain in the initial BB status. If a new procurement action is 

generated as the result of this request the status code will be updated to BZ and a supply status will be 

sent to requesting site. 

(l) DSS logic will produce a physical inventory request for all negative responses

(Action Certification Code A2 or A3) on re-warehousing and/or protection actions if a quantity was 

resident in DSS when the rewarehousing/protection request was received. The materiel owner will 

receive an inventory adjustment as applicable based on the physical inventory count.

(2) NSY Staging and Picklist/Callout Request: 

(a) DLA will be the materiel provider for BRAC NSY sites and will be responsible for 

purchasing, receipting, storing, and issuing of all consumable materiels in support of the maintenance 

operations at these sites. Materials requested by NSY from DLA on a Requisition Alert will be 

receipted under the DLA document number, and stowed and protected by Requisition Alert Document 

Number and Job Order (JO) combination. These items are referred to as Direct Materiel Inventory 

(DMI). 

(b) In addition to the above, DMI could include any or all of the following types of

materiels: mission support materiel (MSM)5, materiel identified under a Materiel Control Tracking 

(MCT) Tag (e.g. rip-out)6, future use materiel (FUM), or Navy program managed materiel. 

(c) Navy-owned assets will be stored and protected by the funded document number 

and JO combination as the result of an issue without Use Code E. Navy-owned assets may also be 

identified by MCT Tag Number. 

(d) Maintenance phases will require specific DMI to be staged at various locations and 

times to effectively support maintenance cycles at the NSY site. In preparation of maintenance cycle, 

NSY engineers will request specific DMI or MSM materiels to be staged either within a warehouse or 

 4 Refer to ADC 379. 5 Refer to ADC 338, New Advice Code for Surge Requirements of Mission Support Materiel (MSM) under Navy BRAC 

IMSP, for additional clarification of MSM.

6 Refer to ADC 373, Document Process for Materiel Control Tracking (MCT) Tag Number and Revise DLMS 527D, 

527R, 867I, 940R, and 945A in Support of BRAC SS&D/IMSP, for additional clarification on use of the MCT Tag 

Number.
ADC 401, Attachment Page 8

at the waterfront prior to the artisan beginning work. 

(e) Navy engineers will submit a request through MAT to stage specific items 

associated with a JO in a staging or assembly area within the warehouse or at the waterfront. MAT 

will generate the Warehouse Service Request (940S) to the Distribution Depot with the applicable 

service performed code. DSS will move the materiel from the current storage location to the staging or 

assembly area at the NSY site as indicated by the following service performed codes. The event 

identification code for the first submission for the staging request will be N (New). 

1. Service Performed Code 1 - Stage and Hold (for future delivery by pick list 

control number) 

2. Service Performed Code 2 - Stage and Deliver (to designated point by pick list 

control number) 

3. Service Performed Code 3 - Deliver (from staging if previously staged, or pick 

and deliver to designated point. 

(f) When requested service is completed, DSS will reply with a Warehouse Service 

Advice, DLMS 943A, to the NSY site. There may be multiple responses when materiel is moved from 

multiple locations. The final action completing the request will contain an Action Certification Code 

A1 indicating the full quantity has been staged. This functionality is being provided because MAT 

cannot track partial quantity confirmations associated with one request. 

(g) Subsequent staging or picklist request from MAT will stage/move a group of 

documents to a designated area with a single 940S containing the picklist control number (PLCN) 

documents. DSS will in turn pick all documents for that PLCN from a single 940S and move/ stage 

materiel accordingly. There will never be partial movements of documents for a PLCN, e.g. if there 

were 100 documents initially assigned to a PLCN and now only 50 were needed a new 940S (change 

or delete) would be sent to DSS to update the pick list table. DSS will reply with a 943A to MAT to 

show documents have been moved/staged.

(h) When DSS attempts to move materiel on the staging request, the Warehouse 

Service Advice will indicate certified partial, certified in total, or not certified for the entire staging or 

picklist request. If the entire picklist has been certified partial or not certified, then each document 

number in the picklist will be reflected in the detail section and will carry a yes/no indicator to provide 

status on whether that document number has been completed or not completed. When the action is 

partially completed, the quantity field will reflect the quantity picked or staged. When the document 

number has not been completed, the quantity will be zero.

1. MAT will produce a report for manual review of all service requests resulting 

in an incomplete status. 

2. DSS logic will produce a physical inventory request for all service requests 

which could not be completed. The materiel owner will receive an inventory adjustment based 

incomplete action and any subsequent adjustment based on the physical inventory count. [Staffing 

Note: This may require additional business rules for the different scenarios involved (e.g. service 

requests may precede actual release of materiel to the Navy.]

(i) Picklist/Callout for previously staged materiel submitted concurrent with the funded 

requisition will reflect Service Performed Code 4. These picklists from MAT will group multiple 
ADC 401, Attachment Page 9

funded documents for delivery of materiel by DSS to a designated area using a single 940S containing 

the PLCN. Multiple funded requisitions will be sent to EBS for DLA-owned assets or multiple MROs 

will be sent to DSS for Navy-owned assets. When DSS receives the EBS or Navy MROs, all 

documents for that PLCN from a single 940S will be picked and delivered to the artisan. The 

Warehouse Service Request will indicate if a response (Warehouse Service Advice, 943A) is required.

(j) A picklist for materiel not previously staged will be submitted concurrently with the 

funded requisition and will reflect Service Performed Code 5 (applicable to Reason for Requisitioning 

Code E, End Use Delivery, and Reason for Requisitioning Code D (DMI). This action code will be 

used for DMI items to be issued for immediate use (E Use Code), or stored under the Navy’s account 

for future use (D Use Code). The PLCN will be on the funded requisition to DLA and the subsequent 

MRO to DSS. DSS will pull the picklist information by Document Number on the MRO from EBS. 

If the materiel is Navy owned the PLCN will be reflected on the MRO to DSS from MAT. The 

Warehouse Service Request will indicate if a response (Warehouse Service Advice, 943A) is required.

(k) A picklist for materiel not previously staged, stored at the IA worksite will reflect 

Service Performed Code 6. This will be concurrent with the submission of a funded requisition for 

DLA-owned materiel and MRO for Navy-owned materiel. When DSS receives the EBS or Navy 

MRO, the picklist information will be retrieved by the Document Number on the MRO. The use of 

Service Performed Code 6 may include the condition when no requisition alert preceded the Navy 

funded requisition. The Warehouse Service Request will indicate if a response (Warehouse Service 

Advice, 943A) is required.

(l) The picklist information will be maintained in DSS. The funded requisition from 

MAT will reflect the PLCN. The PLCN will also be reflected on the MRO sent to DSS from either 

EBS or MAT. When the PLCN is not found on the picklist table, DSS will use the document number 

to locate picklist information.

(m) The picklist may reflect a National Stock Number (NSN), unit of use and a quantity 

associated with the unit of use. The MRO generated from EBS will reflect both the NSN and 

associated Local Stock Number (LSN) for materiel that has been requested in a unit of use. Any MRO 

generated from MAT to DSS will reflect only the NSN, quantity associated with the unit of use and a 

unique qualifier indicating the quantity is associated with unit of use. DSS will cross reference the 

NSN to LSN for the Distribution Depot 1348-1A, Issue, Release/Receipt Document (IRRD) in order to 

print both the LSN and NSN and to bar code these on the document. 

(n) The pick list maintenance will be based on updates from the NSY MAT system. 

MAT will generate picklist data to DSS on a daily basis to provide additional delivery information 

associated with funded requisitions submitted. Based on the Event Identification, DSS will take action 

to update the picklist table. 

• A = Add a record to picklist or staging request 

• C = Change a record’s data element(s) from a previous picklist or staging request

• D = Delete a record from a previous picklist or staging request

• N = New picklist or staging request for DSS to create initial table entry

• U = Staging or picklist unchanged; perform as requested by Service Performed Code

• X = Delete all records for the PLCN

• Y = Delete all records for a JO/KO on previous picklist or staging requests
ADC 401, Attachment Page 10

(3) FRC Picklist/Callout: 

(a) The FRC pick list will contain Service Performed Code 8 indicating to DSS an 

MRO is associated with the materiel. FRC sites will generate a picklist service request for any funded 

requisitions sent to EBS requesting DLA-owned assets or for any MROs sent to DSS for Navy-owned 

assets stored within DSS under local Navy ownership. 

(b) When DSS receives the EBS or Navy MROs, all documents for that PLCN from a 

single Warehouse Service Request will be picked and delivered to the artisan. 

(c) FRCs do not expect DSS to hold any MRO on the picklist to complete all document 

numbers on a single picklist, but to process the MROs as received to issue materiel to the artisan. 

When the PLCN is not found on the picklist table, DSS will use the document number to locate 

picklist information. The Warehouse Service Request will indicate if a response (Warehouse Service 

Advice, 943A) is required.

(d) FRC will provide an overlay of the associated picklist to DSS on a daily basis. This 

will ensure the correct data is being used for delivery. 

(e) MRP II will generate picklist data to DSS on a daily basis to provide additional 

delivery information associated with funded requisitions submitted. Based on the Event Identification, 

DSS will take action to update the picklist table. The Warehouse Service Request will indicate if a 

response (Warehouse Service Advice, 943A) is required. 

• A = Add a record to picklist or staging request 

• C = Change a record’s data element(s) from a previous picklist or staging request

• D = Delete a record from a previous picklist or staging request

• N = New picklist or staging request for DSS to create initial table entry

• O(alpha) = Overlay entire picklist file (FRC)

(4) The picklist may reflect an NSN, unit of use and a quantity associated with the unit of 

use. The MRO generated from EBS will reflect both the NSN and associated LSN for materiel that 

has been requested in a unit of use. Any MRO generated from MRP II to DSS will reflect only the 

NSN, quantity associated with the unit of use and a unique qualifier indicting the quantity is associated 

with unit of use. DSS will cross reference the NSN to LSN for the IRRD in order to print both the 

LSN and NSN and to bar code these on the document. 

(5) The data content to be captured in the Warehouse Service Request, 940S is shown at 

Enclosure 1. Lines identified as H (header) will be applicable to the entire request, those identified as 

D (detail) will be at the document number level. 

(6) The data content to be captured in the Warehouse Service Advice, 943A is shown at 

Enclosure 2. All lines at the header level of the 943A will need to be grouped together as there may be 

multiple responses for each pick list control number.
ADC 401, Attachment Page 11

(7) Additional data elements required at the NSY and FRC sites will be printed on a 

separately generated materiel movement document. A second requirement is to print both the NSN 

and unit of use LSN on any IRRD generated at the IA worksite to issue materiel to an artisan. 

Examples are provided at Enclosure 6.

d. Detailed Procedure associated with MCMC BRAC:

(1) Use of Service Performed Codes and Event Identification: For the Marine Corps 

SDI implementation, the Warehouse Service Advice may be used in response to a requested action 

communicated by a Warehouse Service Request, or it may be provided by the storage activity based 

upon pre-determined business rules. For those requests initiated by the MCMC, both transactions will 

carry the Service Performed Code M and the Event Identification M. When the storage activity 

provides the Warehouse Service Advice without a prior Warehouse Service Request, the Service 

Performed Code M will be used with either Event Identification R, indicating a transaction triggered 

by standard receiving, or Event Identification D, indicating a transaction triggered by the presence of 

suspected discrepant or deficient materiel either in storage or at time of receipt. The Event 

Identification data element was added to the Warehouse Service Advice as a means of recognizing 

these differences in business process without impacting the planned use of the generic Service 

Performed Code M by the MCMC applications.

(2) Receipt of Materiel and Communication of Storage Location

(a) MCMC systems will prepare and transmit the Pre-positioned Materiel Receipt 

(PMR)/Advanced Receipt Information (527D) to the DLA DSS operating the collocated DLA 

warehouse. The PMR will identify materiel to be received.

(b) Materiel is received at the depot and receipted into DSS. DSS will create and send 

a Receipt (527R) through DAAS to the Marine Corps Bridge. Materiel will be stowed in the depot and

DSS will create and send the Warehouse Service Advice (943A) citing Service Performed Code M and 

Event Code R through DAAS to Marine Corps Bridge identifying the stow location.

1. Discrepant/Deficient Materiel Receipt. If the entire quantity received is 

considered discrepant/deficient, the materiel may need to be segregated. If so, the Warehouse Service 

Advice owner/location will reflect the designated values applicable to the discrepant/deficient materiel 

location and owner RIC, and the condition code of the materiel L, K, or Q, as applicable. When used 

to report discrepant/deficient materiel, the Warehouse Service Advice will cite Event Code D.

2. Partial Quantity Discrepant/Deficient Materiel Receipt. If a portion of the 

quantity received is considered discrepant/deficient and is segregated, a Warehouse Service Advice 

will be prepared for the discrepant deficient quantity citing Event Code D in addition to the Warehouse 

Service Advice citing Event Code R. (The transaction structure will also support sending one 

transaction with two detail loops identifying different Event Codes.)

(c) The Marine Corps Bridge will transmit Warehouse Service Advice information to 

ILSMIS and MRP as necessary. 

1. Marine Corps Bridge will send a ZRT to ILSMIS for MILSTRIP. Local 

Purchase and Contract buys will not be sent systematically, the receipts will be processed by Marine 

Corps manually in ILSMIS.
ADC 401, Attachment Page 12

2. Marine Corps Bridge sends INV-6 to MRP II.

(d) Re-warehousing with owner RIC change.

1. To communicate an ownership transfer, the MCMC systems will prepare and 

transmit the Warehousing Service Request (940S), citing Service Performed Code M and Event Code 

M, to the DLA DSS operating the collocated DLA warehouse. The request will identify the current

owner RIC (ILSMIS file designator or MRP II stock room) and the new requested owner RIC 

(ILSMIS file designator or MRP II stock room). 

2. DSS logic will change the owner RIC associated with the materiel and will relocate the materiel as necessary within the collocated DLA warehouse. 

3. When re-warehousing action is completed DSS will communicate the action to 

the MCMC with a Warehouse Service Advice (DLMS 943A) citing Event Code M and reflecting 

Action Certification Code 1 indicating the full quantity has been re-warehoused. 

4. In addition to providing the Warehouse Service Advice, DSS will create the 

inventory adjustment (DLMS 947I) indicating an ownership change to reflect the inventory gain and

loss (Document Identifier Codes D8_ and D9__, respectively)7

.

5. DSS logic will produce a physical inventory request for all negative responses 

(Action Certification Code 2 or 3) on re-warehousing/ownership transfers. The materiel owner will 

receive an inventory adjustment as applicable based on the physical inventory count.

(3) Shelf Life Owner RIC Change.

(a) DSS will identify expired materiel in storage and send DLMS 947I (Document 

Identifier Code DAC) transaction to Marine Corps Bridge to change Condition Code to H. 

(b) The Marine Corps Bridge will pass single line transfer transaction to ILSMIS (D9Z 

CC A/D8Z CC H). Staffing Note: The communication between the Marine Corps Bridge and 

ILSMIS is not consistent with MILSTRAP/DLMS standard procedures and should be addressed in any 

future modernization. 

(c) If required, MCMC systems will prepare and transmit the Warehouse Service 

Request (DLMS 940S), to the DLA DSS operating the collocated DLA warehouse. The request will 

identify previous owner RIC (ILSMIS file designator or MRP II stock room) and the new requested 

owner RIC (ILSMIS file designator or MRP II stock room). 

1. DSS logic will change the owner RIC associated with the materiel and will relocate the materiel as necessary within the collocated DLA warehouse. 

2. In the above scenario for expired shelf life, the MCMC Warehouse Service 

Request will indicate that a DSS response is not requested, and no corresponding Warehouse Service 

Advice will be provided.

 7 ADC 402 addresses procedures including establishment of a new Quantity or Status Adjustment Reason Code to identify 

the gain/loss due to ownership transfer on the Inventory Adjustment.
ADC 401, Attachment Page 13

(d) Alternatively, the Marine Corps may provide disposition instructions to DLA (email 

or hard copy) for appropriate disposal action.

1. Per instructions, the depot will generate a disposal release order (DLMS 940R

(A5J) to dispose of expired shelf life materiel.

2. DSS will communicate the release to the MCMC with a Materiel Release 

Advice 945A (ARJ). 

(4) Relocation of discrepant/deficient materiel

(a) Materiel is identified as defective or discrepant in the warehouse, requiring 

relocation of materiel to the appropriate location (may be referred to as SDR/PQDR cage) and the 

associated discrepant/deficient owner RIC. Materiel considered discrepant/deficient at time of receipt 

will be moved to the appropriate location as noted in paragraph 4.d.(2)(b)1. above.

(b) DSS will provide physical storage location to the Marine Corps as part of 

Warehouse Service Advice (DLMS 943A) and will cite Event Code D.

(c) Normally, a Storage Quality Control Report or Product Quality Deficiency Report 

will also be prepared.

(5) The data content to be captured in the Warehouse Service Request (940S) is shown at 

Enclosure 1. 

(6) The data content to be captured in the Warehouse Service Advice (943A) is shown at 

Enclosure 2. 

(7) Refer to the DLMS Supplement web page for transaction formats at:

www2.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp#870.

(8) The Matrix for Service Performed Code to Event Identification Codes is shown at

Enclosure 3.

(9) Navy BRAC transaction flow diagrams are shown at Enclosure 4.

(10) Marine Corps transaction flow diagrams are shown at Enclosure 5.

(11) Distribution Depot 1348-1A sample documents are shown at Enclosure 6.

(12) Component staffing responses and comment resolution are shown at Enclosure 7.

5. REASON FOR CHANGE: As a result of BRAC 2005 SS&D DSS will be storing and issuing all 

consumable items in support of the Marine Corps Maintenance Centers. Changes will ensure the same 

or better functionality exists after the implementation of BRAC 2005 as before. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: MRP II, ILSMIS, and DSS will be able to comply with DLMS standards for the 

BRAC IMSP Spiral 2 process.
ADC 401, Attachment Page 14

b. Disadvantages: None

7. IMPACT:

a. DLMS Data Content: Many of the data elements included on the Warehouse Service Request

are defined under other approved changes associated with Navy and Marine Corps BRAC IMSP. Data 

elements unique to the DLMS in support of the Warehouse Service Request and Warehouse Service 

Advice are as follows:

DLMS Data Element X12 Name 

(if significantly different) Transaction(s)

Warehouse Storage Location for Pick Distributor Company Number 943A

Service Performed Code 940S & 943A

Event Identification 940S & 943A

Response Required Indicator 940S

Warehouse Action Certification/Status 

Code

943A

b. DLA Transaction Services Mapping/Procedures: The DLMS 940S and 943A are new 

transactions. These two transactions will be processed and passed without special edit or routing rules. 

Staffing Note: The current FRC design does not accommodate DOD to ANSI unit of measure (UoM)

conversion as required for compliance with DLMS and the underlying American National Standards 

Institute (ANSI) American Standards Committee (ASC) X12 transactions. DLA Transaction Services 

will provide temporary conversion logic until the FRCs can develop and implement the long-term 

solution. The DLA Transaction Services will ensure that all parties receiving DLMS transactions

originated by the FRC (including any image transactions provided to other parties) carry the correct 

X12 data value for the DOD unit of issue (conversely, the FRC will receive the DOD unit of issue). 

This approach was authorized by DLA senior management.

c. Publications: Procedures must be documented for the DLMS manual subsequent to ADC 

publication. Staffing Notes: The DLA J33 Supply PRC representatives are responsible for 

coordination with the appropriate DLA, Navy, and Marine Corps offices for development and 

submission of documentation of the DLMS procedures associated with BRAC for the DLMS manual. 

With the recent implementation of the BRAC associated changes, it is required that the DLMS 

procedural guidance be provided as soon as possible, but no later than 90 days from the date of this 

memorandum. Request DLA J33 provide the BRAC IMSP SS&D and SDI procedures as a separate 

chapter for the DLMS manual, Volume 2, Supply, with cross-references identified for placement 

within the related functional area guidance. Additionally, the documentation provided must 

specifically define the DD 1348-1A supplemental data provided by the Distribution Depot per 

Enclosure 6.

d. FRC. Post-go live implementation change required to apply UoM codes per the DLMS UoM 

conversion guide (see DLA Transaction Services Mapping/Procedures staffing note above). 
ADC 401, Enclosure 1, Page 1

Enclosure 1, Warehouse Service Request Data Content

Lines identified as H (header) will be applicable to the entire request, those identified as D (detail) 

will be at the document number level.

# 

& H/D DS 940S Data Content Description 

Length

&

Type

Applicability:

Navy (N) or

Marine 

Corps (M)

1

H

Transaction Purpose 

Code

WA = Warehouse Service Request 1 N/M

2

H/D

Service Performed Code

Staffing Note: 

New Code 9 applicable 

to Navy.

New Code M is

included to support 

Marine Corps.

This code designates the type of warehouse service 

requested.

 Code 1 - NSY Request to Stage and Hold Materiel 

for Future Delivery by PLCN (Document Numbers may 

identify Service-Owned Materiel or DLA-owned 

materiel under the Requisition Alert Document Number)

 Code 2 – NSY Request to Stage and Deliver 

Materiel to Designated Delivery Point by PLCN 

 Code 3 –NSY Request to Move Materiel from 

Staging or Pick from Current Location To Designated 

Delivery Point By PLCN

 Code 4 – NSY Callout of Previously Staged 

Materiel by PLCN and JO (Provided Concurrent with 

Submission of Funded Requisitions or Materiel Release 

Order for Service-Owned Materiel)

 Code 5 – NSY Callout of Materiel by Funded 

Requisition Document Number and JO/KO or by 

Materiel Release Order for Service-Owned Materiel 

(Not Previously Staged). 

 Code 6 – NSY Callout of Materiel by PLCN with 

Funded Requisition Document Number or by Materiel 

Release Order for Service-Owned Materiel. (May be 

for MSM, DMI, Ripout or Program materiel which has 

not been previously staged) 

 Code 7 – DLA Re-Warehousing, or ReWarehousing with Protection Request, by Requisition 

Alert Document Number (Document Number and JO if 

applicable to NSY)

 Code 8 – FRC Picklist (Provided Concurrent with 

Submission of Funded Requisitions or Materiel Release 

Order for Service-Owned Materiel)

 Code 9 – NSY Re-Warehousing Request to Move 

Materiel Identified by MCT Tag to a Specific 

Maintenance Shop. (Materiel Leaves DLA Custody, but 

Remains on DSS records and MAT records under NSY 

1 N/M
ADC 401, Enclosure 1, Page 2

# 

& H/D DS 940S Data Content Description 

Length

&

Type

Applicability:

Navy (N) or

Marine 

Corps (M)

Ownership. Materiel may be Tracked within DSS to the

Maintenance Shop and Responsible Individual based 

Name and Badge Number) 

 Code B – NSY Update to Individual Line Items 

used with Update Action Code A, C, D, X, or Y. 

 Code M – MCMC Warehouse Service Request

3

H/D

Picklist Control Number 

(PLCN)

The control number assigned to identify a specific job 

for which materiels are being assembled together, e.g. 

in support of an FRC or NSY site. The PLCN will be 

the same for each record associated with a particular 

pick list/kit.

A PLCN is mandatory for Service Performed Codes 1-6, 

8 and 9.

PLCN is not used for Service Performed Code 7 or M. 

32

a/n

N

4

H/D

Event Identification Identifies action DSS needs to take on the warehouse 

service request.

A=Add a record to pick list or staging request (NSY) 

C=Change a record’s data element(s) from a previous 

pick list or staging request (NSY)

D=Delete a record from a previous picklist or staging 

request (NSY)

M= Ownership transfer/warehousing action (MCMC)

N= New pick list or staging request for DSS to create 

initial table entry (NSY)

O (alpha)= Overlay entire pick list file (FRC)

This field is alphanumeric and will be mandatory to be 

used on all staging or pick list request from MAT or

MRP II or EBS.

P=Re-warehouse to IA worksite and protect stock, if

applicable (EBS) 

S= Unprotect and re-warehouse from IA worksite to 

Distribution Depot (EBS)

U = Staging or picklist unchanged; perform action 

requested by Service Request code

X= Delete all records for the Pick list Control Number 

(NSY)

Y= Delete all records for a JO/KO on previous picklists 

or staging requests (NSY)

1 N/M
ADC 401, Enclosure 1, Page 3

# 

& H/D DS 940S Data Content Description 

Length

&

Type

Applicability:

Navy (N) or

Marine 

Corps (M)

5

D

Requisition Alert 

Document Number

Document number reflected on the unfunded Navy 

requirement for pre-positioning prior to submission of a 

funded requisition. 

The Requisition Alert Document number, suffix code, 

and JO will be key data elements to releasing issues at 

Naval Shipyards.

All Navy-prepared staging requests (Service Performed 

Codes 1-3) will reflect a document number; however, 

the document number may identify Service-owned 

materiel or DLA-owned materiel under the requisition 

alert document number. 

Service Performed Code 7 will be used when the request 

is not associated with a unit of use re-warehousing 

request. 

14 N

6

D

Requisition Alert Suffix 

Code

Suffix code reflected on the original pre-requisitioning 

requirements signal. Original Requisition Alert 

Document number, suffix code, and JO/KO will be key 

data elements to releasing issues at Naval Shipyards. 

This is an alpha field and will be optional.

1 N

7

H

Job Order (JO) Number 

(JON)

Used by NSY maintenance activity to identify a 

particular package of work. The first two positions are 

the Work Category Number, the next three positions are 

the Availability Number, and the remaining five digits 

make up the Work Breakdown Structure.

Original Requisition alert Document number, suffix 

code and JO and Key Operation Numbers will be key 

data elements to releasing issues at Naval Shipyards. 

Alphanumeric Field, Mandatory, applicable to both 

funded and unfunded requisitions at NSY sites. 

10 N

8

H/D

Key Operation (KO) 

Number 

The logical division of a Job Order which may be 

scheduled to be performed without significant 

interruption, and which can be closed out to further 

charges upon completion. This value will be a reference 

field on all transactions. 

Alpha/Numeric Field

Mandatory, applicable to both funded and unfunded 

requisitions at NSY sites. 

3 N
ADC 401, Enclosure 1, Page 4

# 

& H/D DS 940S Data Content Description 

Length

&

Type

Applicability:

Navy (N) or

Marine 

Corps (M)

9

D

Document Number Document Number generated by MRP II or MAT of the 

issue request of materiel. When the request is for DLA 

owned assets the request will be a funded requisition. 

When the request is for Navy owned assets the request 

will be a Materiel Release Order to DSS from MAT or 

MRP II. 

Required for Service Performed Code 4, 5, 6, 7, 8 and 9. 

All Navy-prepared staging requests (Service Performed 

Codes 1-3) will reflect a document number; however, 

the document number may identify Service-owned 

materiel or DLA-owned materiel under the requisition 

alert document number.

14 N/M

10

D

Suffix Code Suffix code associated with the funded requisition or 

MRO for Service-owned assets. 

Optional

1 N/M

11

D

Primary Materiel 

Identification:

National Stock Number 

(NSN)

or

Local Stock Number 

(LSN)

The primary materiel identification is the identification 

by which the materiel is receipted, stored, inventoried 

and sold:

 

National Stock Number (NSN)

or

Local Stock Number (LSN) 

NSN/LSN is not applicable when materiel is identified 

by a Materiel Control Tracking (MCT Tag). See MCT 

Tag below.

13 N/M

Cross-Reference NSN Represents FLIS NSN if primary materiel identification 

is a unit of use LSN.

13 N/M

12

D

Materiel Control 

Tracking (MCT) Tag 

Number

Materiel identification number applicable to items in 

courtesy storage (e.g. ripout, prefab) on behalf of the 

Navy while specific maintenance is being performed. 

If component parts are separately identified, a suffix 

will be assigned and retained within the MCT tag 

number field. The MCT tag number suffix will be 

appended to the value of the MCT tag number in lieu of 

using a separate data field.

This field will not be used when the LSN or NSN is the 

primary materiel identification. 

32 N
ADC 401, Enclosure 1, Page 5

# 

& H/D DS 940S Data Content Description 

Length

&

Type

Applicability:

Navy (N) or

Marine 

Corps (M)

13

D

Unit of Issue Unit of issue recorded for the stock number to be staged 

or protected. This may be at unit of use level based on 

the presence of the unit of use qualifier. 

Mandatory

There will be instances when the requesting activity 

requires a quantity in less than the standard unit of issue 

established on the FLIS record for a specific NSN. 

When this occurs the requesting site will include a 

unique qualifier indicating the quantity and unit of issue 

are for less than the standard unit of issue.

2 N/M

14

D

Unit of Use Indicator Qualifier used to indicate to receiving system the 

quantity and unit of issue are associated with a unit of 

use (not equal to FLIS unit of issue applicable to 

requested NSN but will be within the common set of 

values for DOD units of issue). 

1 N/M

15

D

Quantity Quantity requested to be staged/picked or protected/rewarehoused. 

Mandatory

7 N/M

16

D

Special Materials 

Content Code (SMIC) 

Optional 2 N

17

H

Work Order Number Work order number associated with the funded 

requisition. Work order number is assigned internally 

within FRC system, MRP II. 

Alpha/numeric, optional. FRC use only. 

10 N

18

D

Quality Inspection Code Code indicating the quality level of inspection to which 

the item must be procured and inspected. 

Mandatory for FRC and NSY request

1 N

19

D

Requirement Churn 

Reason

Code used as a basis for metrics, tracking request for 

materiel after the start of availability at a shipyard. The 

churn code will be used to track an agreed to strategic 

metric between Navy and DLA. 

Optional entry, to be printed on Materiel Movement 

Document 

1 N
ADC 401, Enclosure 1, Page 6

# 

& H/D DS 940S Data Content Description 

Length

&

Type

Applicability:

Navy (N) or

Marine 

Corps (M)

20

H

Delivery Priority Code Code used by NSY sites to reflect materiel has an 

urgency of need within the maintenance shop and must 

be delivered within one hour of receipt of the issue 

request. Value will be X (1 hour issue) when 

applicable. (Previously referred to as Criticality Code) 

DSS has unique indicator which can be set to exclude 

additional cost for delivery priority at the BRAC SS&D 

sites.

Applicable to funded requisitions at NSY sites. 

Staffing Note: Requires update to existing DLMS 

definition to include Navy use under PDC 366,

1 N

21

H

Technical Work 

Document Number

Technical Work Document Number identifies the work 

and job for which the materiel is being requested. This 

is assigned by Planning system for 

Engineering/Planning and production area at the NSY 

sites. 

Optional Entry, to be printed on Materiel Movement 

Document

20 N

22

D

Reason for 

Requisitioning Code

Code used at NSY site referring to the use of the 

materiel. FRC sites will default to ‘E’. 

D- Direct Materiel Inventory (DMI)

E – End Use Inventory

M – Mission Support Materiel (MSM)

U – Ripout/courtesy storage

S – Nuclear Shop delivery

Mandatory entry on staging and pick list, action code 1-

6 and 9. Not applicable to action code 7.

1 N

23

H

Response Required 

Indicator

Indicates to DSS when to reply to a re-warehousing 

and/or staging, or picklist request with 943A, stow 

confirmation. 

Mandatory.

Y (Response Required) (NSY, Marine Corps and EBS)

N (No Response Required if Performed as Requested) 

(FRC, Marine Corps)

1 N/M

24

H

Ship-To DoDAAC DoDAAC of a forward site where materiel will be 

transshipped in support of off station support 

maintenance. 

6 N

25

D

Special Material Content 

Code

A code that indicates an item represents or contains 

peculiar material requiring special treatment, 

precautions, or management control of the item. 

Applies to Navy Managed items only and is referred to 

as Haz Mat Indicator code within Navy system (MAT). 

1 N
ADC 401, Enclosure 1, Page 7

# 

& H/D DS 940S Data Content Description 

Length

&

Type

Applicability:

Navy (N) or

Marine 

Corps (M)

26

H

Required Delivery Date Date when materiel is to be delivered to Artisan. 

Format YYYYMMDD

Optional entry, NSY use only 

8 N

27

H

Required Delivery Time Time when materiel is to be delivered to Artisan. 

HHMM

Optional entry, NSY use only

4 N

28

H

Requester Point of 

Contact (POC) Name

Person who is requesting the materiel (Production 

Controller, Artisan)

Mandatory entry on staging and pick list, action code 1-

6 and 9. Not applicable to action code 7.

30 N

29

H

Requester Phone 

Number

Phone number for person requesting materiel. 

Optional, NSY use only

The transaction allows for both commercial and DSN 

numbers. 

Staffing Note: Since the preference is for commercial 

numbers to be used, the order of the qualifiers has been 

switched to make commercial precede the DSN. Since 

there is no desire to include e-mail, the optional qualifier 

for e-mail has been dropped from the format.

10 N

30

H

Requester Badge 

Number

Badge number of person requesting materiel 

Mandatory for action codes 1-6 and 9 NSY use only. 

6 N

31

H/D

Delivery Location Location to which materiel is to be delivered.

Mandatory entry on staging and pick list, action code 1-

6 and 9. Not applicable to action code 7.

30 N

32

H

Document Number 

Count

A count of the total number of documents required for 

the pick

Optional, NSY use only

4 N

33

H/D

Staging/Picklist General 

Remarks

Free form information related to the materiel itself (use, 

install instructions, drawings, etc

Optional, NSY use only

40 N

34

H/D

Special Delivery 

Instructions

Free form instructions related to the delivery of the 

materiel.

Optional, NSY use only

180 N

35

D

New Owner This will identify the owner RIC subsequent to rewarehousing action. 

The owner RIC within the industrial activity at the 

MCMC identifies the specific maintenance mission for 

which the materiel is designated. Marine Corps may 

generate a request for re-warehousing and change of 

ownership to within the IA worksite. 

Note: When used for ownership transfer, the transaction 

originator will be the current owner RIC.

3 M
ADC 401, Enclosure 1, Page 8

# 

& H/D DS 940S Data Content Description 

Length

&

Type

Applicability:

Navy (N) or

Marine 

Corps (M)

36

D

Supply Condition Code Condition Code is included on the warehouse service 

request because multiple condition codes may be stored 

under the same owner RIC in DSS. Inclusion of the 

condition code will allow the MCMC to specifically 

identify which materiel is to be transferred.

1 M
ADC 401, Enclosure 2, Page 1

Enclosure 2, Warehouse Service Advice Data Content

Lines identified as H (header) will be applicable to the entire response, those identified as D 

(detail) will be at the document number level.

#

&H/D DS 943A Data Content Description Field 

Length

Applicabili

ty:

Navy (N) 

or

Marine 

Corps (M)

1

H

Transaction Purpose 

Code

ZS = Warehouse Service Advice 2 N/M

2

H

Service Performed Code

Staffing Note: 

New Code 9 applicable 

to Navy.

New Code M is

included to support 

Marine Corps.

This code designates the type of warehouse service that has 

been performed.

 Code 1 - NSY Request to Stage and Hold Materiel for 

Future Delivery by PLCN (Document Numbers may 

identify Service-Owned Materiel or DLA-owned materiel 

under the Requisition Alert Document Number) 

 Code 2 – NSY Request to Stage and Deliver Materiel 

to Designated Delivery Point by PLCN 

 Code 3 –NSY Request to Move Materiel from Staging 

or Pick from Current Location To Designated Delivery 

Point By PLCN

 Code 4 – NSY Callout of Previously Staged Materiel 

by PLCN and JO (Provided Concurrent with Submission of 

Funded Requisitions or Materiel Release Order for 

Service-Owned Materiel)

 Code 5 – NSY Callout of Materiel by Funded 

Requisition Document Number and JO/KO or by Materiel 

Release Order for Service-Owned Materiel (Not Previously 

Staged). 

 Code 6 – NSY Callout of Materiel by PLCN with 

Funded Requisition Document Number or by Materiel 

Release Order for Service-Owned Materiel. (May be for 

MSM, DMI, Ripout or Program materiel which has not 

been previously staged) 

 Code 7 – DLA Re-Warehousing, or Re-Warehousing 

with Protection Request, by Requisition Alert Document 

Number (Document Number and JO if applicable to NSY)

 Code 8 – FRC Picklist (Provided Concurrent with 

1 N/M
ADC 401, Enclosure 2, Page 2

#

&H/D DS 943A Data Content Description Field 

Length

Applicabili

ty:

Navy (N) 

or

Marine 

Corps (M)

Submission of Funded Requisitions or Materiel Release 

Order for Service-Owned Materiel)

 Code 9 – NSY Re-Warehousing Request to Move 

Materiel Identified by MCT Tag to a Specific Maintenance 

Shop. (Materiel Leaves DLA Custody, but Remains on 

DSS records and MAT records under NSY Ownership. 

Materiel may be Tracked within DSS to the Maintenance 

Shop and Responsible Individual based Name and Badge 

Number) 

 Code B – NSY Update to Individual Line Items used 

with Update Action Code A, C, D, X, or Y. 

 Code M – MCMC Warehouse Service Request

3

H

Picklist Control Number Control Number assigned to identify a specific job for 

which materiels are being assembled together in support of 

FRC or NSY site. 

It will be the same for each record associated with a 

particular pick list/kit.

This is a alpha/numeric field and will be optional

32 N

4

H/D

Warehouse Action 

Certification/ Status 

Code

Indicates DSS certification of completion/status on a 

service request.

Header:

1=Certified in total. Used at header level when positive 

status is applicable to the entire requested service. (X12 

Qualifier=A1)

2=Certified-partial. Used at header level when partial 

completion is reported, use the detail level of this 

transaction to identify each individual document number 

and the associated status. (X12 Qualifier=A2)

3=Not certified. Used at header level when negative status 

is reported, use the detail level of this transaction to 

identify each individual document number and the 

associated status. (X12 Qualifier=A3)

C = All actions applicable to staging/picklist are complete. 

Code C is used at header level indicating this is final 

transaction accomplishing completion of the service 

request.

Detail:

Y = Document number complete. Used at detail level 

when partial completion applies. 

N = Document number not complete. Used at detail level 

when partial completion or total incomplete status applies.

1 N/M
ADC 401, Enclosure 2, Page 3

#

&H/D DS 943A Data Content Description Field 

Length

Applicabili

ty:

Navy (N) 

or

Marine 

Corps (M)

Note: The DOD codes values 1, 2, and 3 are associated 

with the X12 qualifiers A1, A2, and A3 respectively, due 

to the X12 configuration.

5

D

Requisition Alert 

Document Number

Document number reflected on the original prerequisitioning requirements signal. Original Requisition 

Alert Document number, suffix code, and JO/KO will be 

key data elements to releasing issues at Naval Shipyards.

14 N

6

D

Requisition Alert Suffix 

Code

Suffix code reflected on the original pre-requisitioning 

requirements signal. Original Requisition Alert Document 

number, suffix code, and JO/KO will be key data elements 

to releasing issues at Naval Shipyards.

1 N

7

H

Job Order (JO) Number 

(JON)

Used at by NSY maintenance activity identifying a 

particular package of work. The first two positions are the 

Work Category Number, the next three positions are the 

Availability Number, and the remaining five digits make 

up the Work Breakdown Structure.

Original Requisition alert Document number, suffix code,

and JO/KO will be key data elements to releasing issues at 

Naval Shipyards. 

Alphanumeric Field, Mandatory, applicable to both funded 

and unfunded requisitions at NSY sites. 

10 N

8

D

Key Operation (KO) 

Number 

The logical division of a Job Order which may be 

scheduled to be performed without significant interruption, 

and which can be closed out to further charges upon 

completion. The KO value will be a reference field on all 

transactions. 

Mandatory, applicable to both funded and unfunded 

requisitions at NSY sites. 

3 N

9

D

Warehouse Storage 

Location

DSS will use this field to pass the physical location of 

materiel at a BRAC SS&D sites as indicated on the DSS 

record subsequent to the requested action, i.e. stow 

location. (X12 name = Bin Location Number)

If stowed materiel must be split between locations (e.g. due 

to size, weight, or other factors), this data field may be 

repeated up to six times to provide location identification.

30 N/M

10

H/D

Delivery Location Location to which materiel is delivered

Mandatory entry on staging and picklist (Service 

Performed Code 1-6, 8, 9 and B; not applicable to Code 7).

30 N

11

D

Primary Materiel 

Identification:

The primary materiel identification is the identification by 

which the materiel is receipted, stored, inventoried, and 

sold. There will be two materiel identifiers in this 

category:

13 N/M
ADC 401, Enclosure 2, Page 4

#

&H/D DS 943A Data Content Description Field 

Length

Applicabili

ty:

Navy (N) 

or

Marine 

Corps (M)

National Stock Number 

(NSN)

or

Local Stock Number 

(LSN)

 

National Stock Number (NSN)

or

Local Stock Number (LSN) 

This data is not applicable when materiel is identified by 

an MCT Tag. 

12

D

Unit of Use Indicator Qualifier used to indicate to receiving system the quantity 

and unit of issue are associated with a unit of use request 

(not equal to FLIS unit of issue applicable to requested 

NSN but will be within the common set of values for DOD

units of issue). Requisition Alerts and Funded 

Requisitions will reflect this qualifier when request is for 

other than the FLIS standard unit of issue, but will not 

reflect the LSN associated with the NSN. 

All other DLMS transactions in response to the 511R will 

reflect this qualifier and both the NSN and LSN when 

applicable for unit of use. 

 

2 N/M

13

D

Quantity Actual quantity applicable to the advice. May be different 

than original request if done in partial staging actions 

based on physical location of materiel.

7 N/M

14

D

Document Number A document number will be cited for each detail line 

corresponding to the original request. May be a requisition 

alert, funded requisition, or MRO document number.

14 N/M

15

D

Suffix Code Suffix code associated with the funded requisition or MRO 

for Service-owned assets. 

Optional

1 N/M

16

D

Materiel Control 

Tracking (MCT) Tag 

Number

Materiel identification number applicable to items in 

courtesy storage (e.g. ripout, prefab) on behalf of the Navy 

while specific maintenance is being performed. 

If component parts are separately identified, a suffix will 

be assigned and retained within the MCT tag number field. 

The MCT tag number suffix will be appended to the value 

of the MCT tag number in lieu of using a separate data 

field.

This field will not be used when the LSN or NSN is the 

primary materiel identification. 

32 N

17

D

Warehouse Storage

Location for Pick

DSS will use this field to pass the physical location of 

materiel at a BRAC SS&D site as indicated on the DSS 

record prior to the requested action, i.e. pick location.

16 M
ADC 401, Enclosure 2, Page 5

#

&H/D DS 943A Data Content Description Field 

Length

Applicabili

ty:

Navy (N) 

or

Marine 

Corps (M)

18

D

Supply Condition Code Condition Code is included to specifically identify the 

condition of the materiel applicable to the warehouse 

action. 

1 M

19

D

Event Identification Identifies depot action warehouse service request.

Use only with Service Requested Code M.

M – Ownership transfer/warehousing action in response to 

MCMC request

D – Depot-initiated ownership transfer/warehousing action 

associated with discrepant/deficient MCMC materiel

R – Depot-initiated warehousing action associated with 

receipt of MCMC materiel

1 M
ADC 401, Enclosure 3, Page 1

Enclosure 3, Matrix for Service Performed Code to Event Identification Codes

The following matrix shows which event identification code may be used with each service performed 

code. Applicability identified is provided for information; it is associated with preliminary design and 

is not intended to be restrictive.

Service Performed Code Applicability Event Identification 

1 - NSY Request to Stage and Hold Materiel 

for Future Delivery by PLCN (Document 

Numbers may identify Service-Owned 

Materiel or DLA-owned materiel under the 

Requisition Alert Document Number) 

NSY N – New staging or picklist request

2 – NSY Request to Stage and Deliver 

Materiel to Designated Delivery Point by 

PLCN 

NSY N – New picklist or staging request

U – Staging or picklist unchanged, perform 

action requested by staging action code

3 – NSY Request to Move Materiel from 

Staging or Pick from Current Location To 

Designated Delivery Point By PLCN

 

NSY N- New picklist or staging request for DSS to 

create initial table entry

U - Staging or picklist unchanged, perform 

action requested by staging action code

4 – NSY Callout of Previously Staged 

Materiel by PLCN and JO (Provided 

Concurrent with Submission of Funded 

Requisitions or Materiel Release Order for 

Service-Owned Materiel)

NSY U - Staging or picklist unchanged, perform 

action requested by staging action code

5 – NSY Callout of Materiel by Funded 

Requisition Document Number and JO/KO or 

by Materiel Release Order for Service-Owned 

Materiel (Not Previously Staged). 

NSY N - New picklist or staging request for DSS to 

create initial table entry

U – Staging or picklist unchanged, perform 

action requested by staging action code

6 – NSY Callout of Materiel by PLCN with 

Funded Requisition Document Number or by 

Materiel Release Order for Service-Owned 

Materiel. (May be for MSM, DMI, Ripout or 

Program materiel which has not been 

previously staged) 

NSY N - New picklist or staging request for DSS to 

create initial table entry

U – Staging or picklist unchanged, perform 

action requested by staging action code

7 – DLA Re-Warehousing, or ReWarehousing with Protection Request, by

Requisition Alert Document Number 

(Document Number and JO if applicable to 

NSY)

DLA P – Re-warehouse to IA worksite, and protect 

stock (by document number and JO), when 

applicable

S – Unprotect and re-warehouse from IA 

worksite to Distribution Depot worksite.

8 – FRC Picklist (Provided Concurrent with 

Submission of Funded Requisitions or 

Materiel Release Order for Service-Owned 

Materiel)

FRC A – Add a record to picklist or staging request

C – change a record’s data elements on a 

previous pick list or staging request

D – delete a record from a previous picklist or 

staging request

N - New picklist or staging request for DSS to 

create initial table entry

O – Overlay entire picklist 
ADC 401, Enclosure 3, Page 2

9 – NSY Re-Warehousing Request to Move 

Materiel Identified by MCT Tag to a Specific 

Maintenance Shop. (Materiel Leaves DLA 

Custody, but Remains on DSS records and 

MAT records under NSY Ownership. 

Materiel may be Tracked within DSS to the 

Maintenance Shop and Responsible Individual 

based Name and Badge Number) 

NSY N – New picklist or staging request for DSS to 

create initial table entry

B – Update to line item data on a picklist NSY A – Add a record to picklist or stating request

C – change a record’s data elements on a 

previous pick list or staging request

D – delete a record on from a previous picklist 

or stating request

X – Delete all records for the PLCN

Y– Delete all records for JO/KO on a previous 

picklist or stating request

M – MCMC Warehouse Service Request MCMC M – Ownership transfer/warehousing action in 

response to MCMC request

D – Depot-initiated ownership 

transfer/warehousing action associated with 

discrepant/deficient MCMC materiel

R – Depot-initiated warehousing action 

associated with receipt of MCMC materiel
ADC 401, Enclosure 4, Page 1

Enclosure 4, Navy BRAC Transaction Flow Diagrams (as staffed with PDC384)

1a. User inputs pick list requirements into MAT to create staging & hold for future delivery request, 940S (Action Code 

#1{AC#1}). A log number (pick list control number) is generated in MAT for the pick list. ->2

1b. User inputs pick list requirements into MAT to create staging & delivery to a designated point request, 940S (Action 

Code #2{AC#2}). A log number (pick list control number) is generated in MAT for the pick list. ->2

1c. User inputs pick list requirements into MAT to move from staging & hold area and for delivery to a designated point 

request, 940S (Action Code #3{AC#3}). A log number is generated in MAT for the pick list. ->2

2. MAT passes 940S to PS I/O F, which receives and passes 940S to DLA Transaction Services. ->3 (From 1a, 1b, 1c)

3. DLA Transaction Services receives and routes the staging/delivery request (940S with either AC#1, 2, 3) to DSS IA 

Worksite ->4

4. DSS IA Worksite assigns control number to pick list (links to MAT log number). -> 4b1, 4b2, 4b3

4a. Not used 

4b1. DSS IA Worksite builds the kit from materiel stowed at warehouses based on the pick list 940S (AC#1) 

->4c (denial) or 4d1 (stow)

4b2. DSS IA Worksite builds the kit from materiel stowed at the warehouses based on the pick list 940S (AC#2) ->4c 

(denial) or 4d2 (stow)

4b3. DSS IA Worksite processes 940S (re-warehouse) for materiel at Stage & Hold area (AC#3) ->4c (denial) or 4d3 

(stow)
ADC 401, Enclosure 4, Page 2

4c. DSS IA Worksite passes a 943A indicating pick denial or shortage, for each 940S to DLA Transaction Services for 

AC#1, AC#2 and AC#3 ->4c1

4c1. DLA Transaction Services puts the 943A Stow confirmation for each 940S to the NSY hold queue for retrieval by PS 

I/O F. ->5

4d1. DSS IA Worksite moves the staged kit (AC#1) to the staging hold location ->4e

4d2. DSS IA Worksite moves the staged kit (AC#2) to the designated delivery point (Pier/Materiel Envelope). ->4e

4d3. DSS IA Worksite moves the staged request (re-warehouse) kit (AC#3) from staging hold location to designated 

delivery point (Pier/Materiel Envelope). ->4e

4e. DSS IA Worksite processes the 943A stow confirmation, for each 940S ->4e1, Funded Requisition may occur after 

materiel is stowed in staging location or later Pier/Materiel Envelope location 

4e1. DSS IA Worksite passes the 943A stow confirmation, for each 940S to DLA Transaction Services ->4e2

4e2. DLA Transaction Services puts the 943A stow confirmation, for 940S in the NSY hold queue for retrieval by PS I/O 

F. ->5

5. PS I/O F retrieves the request acknowledgement and 943A stow/pick confirmations from the DLA Transaction Services

NSY hold queue and passes to MAT ->6

6. MAT updates status of kit build; recording status and location for each document number, log number. (Note: 

Document number could include a suffix or could be a MCT tag number for Ripout or Courtesy Storage Item). ->END
ADC 401, Enclosure 4, Page 3

1) FRC sites will use IF5 to create and send 940S with action code 6, Materiel Protection, Staging, Rewarehousing and Pick-list Request (add, change, delete or overlay) to DSS IA Worksite when the funded 

requisition occurs. -> 1a

1a) DLA Transaction Services receives and passes the 940S to DSS IA Worksite. -> 1b

1b) DSS IA Worksite updates (add, change, delete, or overlay) Picklist -> END

NOTE: no response is required when 940S is from an FRC site. 

2) MAT generates 940S and sends it to PS I/O F for delivery to NSY pull queue. 

 PS I/O F pushes the 940S to DLA Transaction Services -> 2a

2a) DLA Transaction Services routes the 940S to DSS -> 2b

2b) DSS receives and processes the 940S request -> 2c

2c) DSS will respond with a 943A when the 940S request is completed -> 2d

2d) DLA Transaction Services routes the 943A to the NSY PS I/O F queue -> 2e

2e) Navy PS I/O F queue retrieves 943A stow/pick confirmation from the DLA Transaction Services NSY hold 

queue and passes to MAT ->END

From the Funded Requisition or Requisition Alert Process EBS may generate a 940S requesting re-warehouse and 

protection of assets 

3) EBS will generate a 940S with action code 7 to protect assets to DLA Transaction Services -> 3a

3a) DLA Transaction Services will receive and pass 940s to DSS-> 3b

3b) DSS will received 940s, re-warehouse and protection materiel. -> 3c
ADC 401, Enclosure 4, Page 4

3c) When action is completed DSS will generate a STOW confirmation, 943A to DLA Transaction Services -> 3d

3d) DLA Transaction Services will pass 943A to EBS -> 3e

3e) EBS will process 943A to completed update of protection and generate applicable status to NSY or FRC -> 

END, Status Process. 
ADC 401, Enclosure 5, Page 1

Enclosure 5, Marine Corps BRAC Transaction Flow Diagrams (as staffed with PDC 384A)

Receipt

Receipt Condition Code “A” to Stock: 

MRPII

DAAS

ILSMIS Marine Corps 

Bridge

4. ZRT

DSS

2.2.

(527R) 

MILSTRIP

Req 

Receipt

2.1. 

(527R)

Offline

Order

Receipt

2.3. 

(527R)

Local

Purch

Receipt

2.4. (527R) 

Contract

Receipt

2.2. 

(527R) 

MILSTRIP

Req 

Receipt

2.1. 

(527R)

Offline

Order

Receipt

2.3. 

(527R)

Local

Purch

Receipt

2.4. (527R) 

Contract

Receipt

5. INV-6

1.1

(527D)

PMRD

1.1

(527D)

PMRD

3.

(943A)

3.

(943A)

1. 527D

1. Advanced Receipt Information (527D) passed from ILSMIS to Marine Corps Bridge

1.1. Advanced Receipt Information (527D) passed from Marine Corps Bridge through 

DAAS to DSS

2. Materiel receipted into DSS 

2.1. DSS will send (527R)(D6) receipt transaction through DAAS to Marine Corps 

Bridge for A0_ offline order receipts
ADC 401, Enclosure 5, Page 2

2.2. DSS will send (527R) (D6) receipt transaction through DAAS to Marine Corps 

Bridge for A0A MILSTRIP requisition receipts

2.3. DSS will send (527R) (D4) receipt transaction through DAAS to Marine Corps 

Bridge for local purchase receipts (To include CLIN number) 

2.4. DSS will send (527R) (D4) receipt transaction through DAAS to Marine Corps 

Bridge for contract receipts (To include CLIN number)

3. Materiel stowed in DSS, (943A) passed from DSS through DAAS to Marine Corps 

Bridge

4. Marine Corps Bridge sends ZRT to ILSMIS for MILSTRIP and offline order (Local 

Purchase and Contract buys will not be sent systematically, the receipts will be 

processed by Marine Corps manually in ILSMIS)

5. Marine Corps Bridge sends INV-6 to MRP II
ADC 401, Enclosure 5, Page 3

Owner Change

Re-warehousing -ILSMIS file designator change & MRP II stockroom change – Owner 

Change:

2.1 MRPII

DSS

Black Box 1.1 ILSMIS

1.2 Single 

line transfer

2.2 Stock Room 

Change (INV-8)

1.4, 2.4 Re-warehousing

Black Box

1.3 File 

designator 

change 

(940S)

2.3 Stock 

Room 

change 

(940S)

1.3 File 

designator 

change 

(940S)

2.3 Stock 

Room 

change 

(940S)

3. 943A?

3. 943A

1. ILSMIS file designator change:

1.1. Marine Corps will perform “Single line transfer”.

1.2. ILSMIS will send “Single line transfer” transaction to Marine Corps Bridge to 

identify file designator change

1.3. Marine Corps Bridge will send 940S transaction to DSS to identify owner RIC 

(file designator) change

1.4. DSS will re-warehouse the materiel if required based on physical location 

constraints

2. MRP II stockroom change:

2.1. Marine Corps will perform INV-8 transfer.
ADC 401, Enclosure 5, Page 4

2.2. MRP II will send INV-8 transaction to Marine Corps Bridge to identify stock room 

change

2.3. Marine Corps Bridge will send 940S transaction to DSS to identify stock room 

change

2.4. DSS will re-warehouse the materiel if required based on physical location 

constraints

3. DSS sends 947I (D8Z/D9Z) to Marine Corps Bridge via DAAS.

4. DSS sends 943A transaction through DAAS to Marine Corps Bridge
ADC 401, Enclosure 5, Page 5

Expired Shelf Life

Expired Shelf Life > $100: 

MRPII

DSS

Black Box ILSMIS

1. DAC

(947I)

1.1 Single Line Transfer 

(947I) 

1.2. INV-8

DAAS

1. DAC

(947I)

Expired Shelf Life

1.3

940S

1.3

940S

1. DSS will send DAC (947I) transaction to Black Box. 

 1.1. Black Box will pass Single Line Transfer transaction to ILSMIS (D9Z 

CC A / D8Z CC H) 

 1.2. Black Box will pass INV-8 transaction to MRP II

 1.3. If required Black Box will send DSS an (940S) transaction to change the 

owner RIC and relocate the materiel

 1.4. Marine Corps will provide disposition instructions to DLA (email or 

hard copy)

 1.5. DSS will send 945A (ARJ) through DAAS to black box
ADC 401, Enclosure 5, Page 6

Defective or Discrepant Materiel

(1) Defective Materiel Received

MRPII

DSS

Black Box ILSMIS

5.1.1. 527R receipt 

1. Receiver Identifies Defective 

Material upon receipt

DAAS

5.1. 

(527R) 

5.2

(527R)

Code L

or K

5.2.1. (527R) 

Code L or K

5.1.2.

INV-6

6. 527D

5.3.2 

(943A)

5.1. 

(527R) 

5.2

(527R)

Code L 

Or K 5.3.2 

(943A)

5.3.3

INV-6

Code L 

or K

6. 527D

6. 527D

1. Defective Materiel received (total receipt should match the actual quantity received):

1.1. Non-defective Quantity received under condition code A(527R) passed from DSS 

through DAAS to Marine Corps Bridge

1.1.1. 527R for non-defective quantity passed from Marine Corps Bridge to 

ILSMIS

1.1.2. INV-6 passed from Marine Corps Bridge to MRP II for non defective 

quantity received

1.2. Defective quantity received in SDR Owner RIC condition code L for contract 

receipts or condition code K for document number receipt, 527R passed from DSS 

through DAAS to Marine Corps Bridge (If inspection required flag is set on 

PMRD, DSS will set inspection flag at location, inspection required if materiel

disposition is going to condition code A)

1.2.1. 527R for condition code L or K passed from Marine Corps Bridge to ILSMIS 

using generic DSS location
ADC 401, Enclosure 5, Page 7

1.3. SDR created

1.3.1. 842A created and passed from DSS through DAAS (DOD WebSDR) to 

Marine Corps Bridge

1.3.2. 943A created and passed from DSS through DAAS to Marine Corps Bridge

for stow of defective materiel to SDR owner RIC (including actual DSS 

location

1.3.3. INV-6 for condition code L or K passed from Marine Corps Bridge to MRP 

II

1.3.4. Defective materiel moved into discrepant cage

2. Quality informs maintenance center supply tech to set freeze code for materiel in 

ILSMIS (as necessary). ILSMIS should update inspection required flag for all open 

PMRD records. Updated PMRD (527D) sent from ILSMIS to Marine Corps Bridge

2.1. Updated PMRD (527D) for any open Dues with defective NIIN sent from Marine 

Corps Bridge through DAAS to DSS

 
ADC 401, Enclosure 5, Page 8

 (2) Incorrect Materiel Received

MRPII

DSS

Black Box ILSMIS

1. Receiver Identifies incorrect 

Material upon receipt

DAAS

5.1

(527R)

Code L

or K

5.2. (527R) 

Code L or K

6. 527D

5.3.2 

(943A)

5.3.1

(842A)

5.1

(527R)

Code L 

Or K 5.3.2 

(943A)

5.3.1

(842A)

5.3.3

INV-6

Code L 

or K

6.1. 

527D

6.1. 

527D

5. Incorrect Materiel received (total receipt should match the actual quantity received):

NOTE: If shipment contains correct as well as incorrect materiel, a split receipt will be 

required similar to partial discrepant receipt. Correct NIIN will follow normal 

receipting logic.

5.1. Quantity received for actual NSN received under condition code L for contract buy 

or condition code K for document number to SDR owner RIC (527R) passed from 

DSS through DAAS to Marine Corps Bridge (If inspection required flag is set on 

PMRD, DSS will set inspection flag at location, inspection required if materiel

disposition is going to condition code A)

5.2. 527R containing actual NSN received passed from Marine Corps Bridge to 

ILSMIS

5.3. SDR created

5.3.1. 842A created and passed from DSS through DAAS (DOD WebSDR) to 

Marine Corps Bridge
ADC 401, Enclosure 5, Page 9

5.3.2. 943A created and passed from DSS through DAAS to Marine Corps Bridge

for stow of defective materiel to SDR owner RIC (including actual DSS 

location

5.3.3. INV-6 for condition code L passed from Marine Corps Bridge to MRP II

5.3.4. Incorrect materiel moved into discrepant cage

6. Quality informs maintenance center supply tech to set freeze code for materiel in 

ILSMIS (as necessary). ILSMIS should update inspection required flag for all open 

PMRD records. (see section 6.3.5.4 for receipt override logic) Updated PMRD (527D) 

sent from ILSMIS to Marine Corps Bridge

6.1. Updated PMRD (527D) for any open Dues with incorrect NIIN sent from Marine 

Corps Bridge through DAAS to DSS
ADC 401, Enclosure 5, Page 10

 (3) Materiel Identified as Defective After Issue

MRPII

DSS

Black Box ILSMIS

2. (527R) 

Condition

Code Q

3. (867I) (D7A)

Issue Reversal

2.1.4. 

INV-6

4. (947I DAC) 

Condition Code Q 

1. Material Identified as discrepant

Turned in to DSS With 

Appropriate documentation

DAAS

2. (527R) 

Condition

Code Q

5. (527D)

6. 527D

Inspection 

Req.

6. 527D

Inspection 

Req.

2.1.3

(943A)

2.1.3

(943A)

1. Shop planner turns materiel into DSS with appropriate documentation (DDMR and 

MCB006 (MCB uses MCB006 for PQDR) or QIR (MCA uses QIR for PQDRs and 

SDRs). 

2. DSS sends 527R from DSS through DAAS to Marine Corps Bridge (including original 

Issue Document Number) moving materiel to SDR/PQDR owner RIC in Condition 

Code Q

2.1. Email sent from Warehouse to QA to identify materiel requiring inspection

2.1.1. Email contains NIIN and all locations containing A condition materiel and 

the location for the PQDR materiel

2.1.2. QA will create PQDR from documentation if materiel is discrepant

2.1.3. (943A) created and passed from DSS through DAAS to Marine Corps Bridge

for stow of defective materiel to SDR/PQDR owner RIC (including actual 

DSS location

2.1.4. INV-6 for Condition Code Q passed from Marine Corps Bridge to MRP II

2.2. DSS locates the materiel into SDR/PQDR Owner RIC

3. Marine Corps Bridge sends (867I) to ILSMIS for issue reversal (ILSMIS: On any 

reversal that increases inventory, ILSMIS should not automatically release back orders.) 
ADC 401, Enclosure 5, Page 11

4. Marine Corps Bridge sends Condition Code Q (947I DAC) transaction to ILSMIS 

5. Quality informs maintenance center supply tech to set freeze code for materiel in 

ILSMIS (as necessary). ILSMIS should update inspection required flag for all open 

PMRD records. (see section 6.3.5.4 for receipt override logic) Updated PMRD (527D) 

sent from ILSMIS to Marine Corps Bridge

6. Updated PMRD (527D) for any open Dues with defective NIIN sent from Marine 

Corps Bridge through DAAS to DSS
ADC 401, Enclosure 5, Page 12

(4) Materiel Identified as Discrepant After Issue:

MRPII

DSS

Black Box ILSMIS

2. (527R) 

Condition

Code K

3. (867I) (D7A)

Issue Reversal

2.1.3. 

INV-6

4. (947I DAC) 

Condition Code K 

1. Material Identified as discrepant

Turned in to DSS With 

Appropriate documentation

DAAS

2. (527R) 

Condition

Code K

5. (527D)

6. 527D

Inspection 

Req.

6. 527D

Inspection 

Req.

2.1.2

(943A)

2.1.2

(943A)

1. Shop planner turns materiel into DSS with appropriate documentation (DDMR and 

MCB006 (MCB uses MCB006 for PQDR and SDRs) or QIR (MCA uses QIR for 

PQDRs and SDRs)

2. DSS sends 527R from DSS through DAAS to Marine Corps Bridge (including original 

Issue Document Number) moving materiel to SDR/PQDR owner RIC in condition code 

L or K 

2.1. SDR created

2.1.1. 842A created and passed from DSS through DAAS (DOD WebSDR) to 

Marine Corps Bridge

2.1.2. 943A created and passed from DSS through DAAS to Marine Corps Bridge

for stow of discrepant materiel to SDR/PQDR owner RIC (including actual 

DSS location

2.1.3. INV-6 for condition code K passed from Marine Corps Bridge to MRP II

NOTE: Location in MRP II should be ILSMIS File Designator from issue 

document history table + a space “ “ + true DSS storage location, 
ADC 401, Enclosure 5, Page 13

NOTE: Marine Corps to create new table to store issue document history 

within Marine Corps Bridge

2.2. DSS locates the materiel into SDR/PQDR Owner RIC

3. Marine Corps Bridge sends (867I) to ILSMIS for issue reversal (ILSMIS: On any 

reversal that increases inventory, ILSMIS should not automatically release back orders.)

4. Marine Corps Bridge sends condition code K (947I DAC) transaction to ILSMIS 

5. Quality informs maintenance center supply tech to set freeze code for materiel in 

ILSMIS (as necessary). ILSMIS should update inspection required flag for all open 

PMRD records. (see section 6.3.5.4 for receipt override logic) Updated PMRD (527D) 

sent from ILSMIS to Marine Corps Bridge

6. Updated PMRD (527D) for any open Dues with defective NIIN sent from Marine 

Corps Bridge through DAAS to DSS
ADC 401, Enclosure 6, Page 1

Enclosure 6: Distribution Depot 1348-1A Sample Documents

Navy Shipyard:
ADC 401, Enclosure 6, Page 2

Navy FRC:
ADC 401, Enclosure 6, Page 3

Marine Corps
ADC 401, Enclosure 7, Page 1

Enclosure 7, Comment Resolution for PDC 384A

Originator Response/Comment Disposition

1. Army Concur Noted.

2. Navy Concur Noted.

3. Air Force None No impact.

4. Marine 

Corps

Marine Corps RIC Monitor:

The requirement in this PDC infers that every maintenance 

project will require a RIC (or series of RICs), in which 

case, it wouldn't take but a matter of a few years or shorter 

for the Marine Corps to zip through its current 871 unused 

RIC combinations. ... What concerns me is whether or not 

a RIC would be deleted upon completion of a maintenance 

project, or rolled over to a new project, or some other 

concept. 

Mr DeLaney is in the process of re-writing the Marine 

Corps' policy for management of the DODAAD, however, 

the Marine Corps does not currently have visibility of a 

POC or notification when there is no longer an ongoing 

requirement for an assigned RIC.

DLA Response: Under the current 

design not every maintenance 

project requires a separate RIC, 

only maintenance projects where 

the Marine Corps Maintenance 

Centers need to track materiel

separately for financial reasons. 

Also once a RIC is no longer used 

(or it is no longer necessary to track 

that materiel separately) that RIC 

can be re-used by the Maintenance 

Centers. 

 The decision to use RICs was 

that the Marine Corps Maintenance 

Centers customers/program 

managers provide materiel to be 

used only on their repair mission. 

The Maintenance Centers must bill 

their customers/program managers 

appropriately for materiel based on 

whether the customer/program 

manager owns the materiel or 

whether the Maintenance Center 

must purchase the materiel for 

them. 

 At this point Marine Corps 

LOGCOM (Mr. Madden) has 

already approved this design and 

any changes will impact the Marine 

Corps-DLA completion of BRAC

2005 which must done by 

September 15, 2011.

DLA Logistics Management 

Standards Response: This office 

did not advocate the use of owner 

RICs for maintenance center 

projects and concur that this 
ADC 401, Enclosure 7, Page 2

Originator Response/Comment Disposition

process impacts the already limited 

availability of RICs for standard 

logistics support.

5. Marine 

Corps 

Request following changes to indicated PDC 384A 

enclosures:

1. Enclosure 1

 a. #3&H/D Picklist Ctrl Number (PLCN)

 i. Change comment from “It is not used

for Service Performed Code 7” to “Picklist Control 

Number (PLCN) not used for Service Performed Code 7 or

M

 b. Cross-Reference NSN on page 5 of

Enclosure 1 (not assigned #& H/ID)

 i. Missing data elements Length & Type

and Applicability

 1. Length = 30

 2. Applicability = M

 c. #3&H/D Delivery Location

 i. Remove Applicability code M. The Marine Corps will 

not use delivery HQMC location in the 940S.

2. Enclosure 2

 a. #17& H/ID New Owner

 i. Remove entry. This appears to be a carry-over from 

the 940S; not required for the 943A.

 b. #20& H/ID Supply Condition Code

 i. Remove entry. This appears to be a

carryover from the 940S; not required for the 943A

 c. #21& H/ID Event Identification

 i. Remove entry. This appears to be a

carryover from the 940S; not required for the 943A

1.Enclosure 1:

a. Done

b. Updated. Max length for the 

cross-reference NSN is 13.

c. Delivery Location applicability 

to the Marine Corps has been 

removed.

2. Enclosure 2:

a. New Owner removed from 943A

b. 943A Supply Condition Code 

was added by intent. It has been 

retained by DLA DSS.

c. 943A Event Identification was 

added by intent. It has been 

retained by DLA DSS.

6. DLA Concur.

During design and conversations with DSS a need for a 

new Event code has been identified for the 940S to support 

Navy BRAC. This would be to indicate to DSS that 

materiel has been unprotected and should be rewarehoused from the IA to the Distribution Depot site. 

Noted.

ADC updated to reflect the 

addition.

7. DLA 

Distribution

The Navy usage requires inclusion of the storage (bin) 

location. When DLA attempts to stow the materiel, the 

may find that it does not all fit in one location (e.g., due to 

size, weight, other factor) and must be split. Can multiple 

locations be provided?

After first verifying that only two 

locations would be needed and that 

the Navy does not need to know the 

exact quantity in each location, it 

was agreed that the segment 

identifying the storage location 

would be repeated to provide the 
ADC 401, Enclosure 7, Page 3

Originator Response/Comment Disposition

second location. ADC reflects this 

change.

Subsequently, it was determined 

that up to six warehouse storage 

locations may be needed to 

accommodate the Marine Corps 

requirement. The ADC has been 

updated to allow up to 6 locations.

8. DLA 

Distribution

The DSS test question on the W27 segment in the 943A 

dealt with a syntax compliance issue. W27 (carrier details) 

is a mandatory segment in the 943. In the PDCs, there was 

no requirement to pass the mode code or carrier SCAC as a 

part of this functional requirement. The PDC DLMS 

Supplement made the W2701 (mode code) a default "ZZ" 

for X12 syntax compliance. What we forgot to do was 

satisfy the relational syntax requirement, which was to put 

a default value in either the W2702 or W2703. 

Since we already had the W2703 in 

the draft supplement without a 

DLMS note, we recommended 

inclusion of the "ZZ" (default 

value) there too, to align with what 

we did in the W2701. The DLMS 

note for the W2703 has been 

updated to use code "ZZ" to meet 

X12 syntax requirements. 

9. DLA (EBS

contractor 

support)

We will ensure that we always use TN in every 940S and 

will communicate this to DSS as well. I have provided a 

proposed change to the TN DLMS notes below in line with 

this direction (I only updated #1 to include RAs):

DLMS Note:

1. Must use to identify the transaction document number of 

the funded Requisition, materiel release order (MRO), or 

Requisition Alert.

2. Use for staging requests where a requisition alert, 

funded requisition, or MRO document number does not 

apply.

(initial email with options below)

... suggested that the event identification P description 

should be updated so that it is not necessarily for protection 

to accommodate its use at FRCs as well as NSYs when we 

are not protecting (i.e. unit of use). This was also touched 

on in the attached email where we suggested the

following: "DLA Re-Warehousing Request (and protection 

if applicable)"

EBS will only be sending 940S transactions in relation to 

Requisition Alerts to move stock to the IA or for internally 

generated re-warehousing requests back to the Distribution 

Depot. EBS needs to be able to communicate to DSS 

when the associated quantity should be protected or not.

I think there are 3 ways we can do this:

The basic rule is that the PWC is 

only used when a second document 

number applies to a transaction. If 

only one document number is used 

in a transaction, then the TN is the 

applicable qualifier, regardless of 

what type of document number it is. 

The ADC is updated to reflect the 

following DLMS Note for TN: 

Must use to identify the transaction 

document number of the funded 

requisition, materiel release order 

(MRO) or requisition alert (when 

used to identify the requisition alert

document number this will be prior 

to submission of the funded 

requisition).

Service Performed Code 7 is 

updated as follows: DLA ReWarehousing, or Re-Warehousing 

with Protection Request, by 

Requisition Alert Document 

Number (Document Number and 

JO if applicable to NSY)

Event Identification P is updated as 

follows: Re-warehouse to IA 

worksite, and protect stock, if
ADC 401, Enclosure 7, Page 4

Originator Response/Comment Disposition

 1) EBS always uses TN in the 940S and would use PWC 

in addition when protection is also being requested (PWC 

means protection document number rather than RA 

document number)

 2) DSS keys off of presence of JO/KO to determine if 

protection is required (PWC means RA document numbers 

as stated in IC)

 3) New event code for just re-warehousing and NO 

protection (PWC means RA document numbers as stated in 

IC)

PDC 384 says the following for the document number 

which could be read to mean that we always have to 

populate something in this field since code 7 is EBS only 

so is the presence of 7 here a typo or does this contradict 

the TN notes?

Required for Service Performed Code 4, 5, 6, 7, 8 and 9.

All Navy-prepared staging requests (Service Performed 

Codes 1-3) will reflect a document number; however, the 

document number may identify Service-owned materiel or 

DLA-owned materiel under the requisition alert document 

number.

Let's assume for now PDC 376 is the way to interpret and 

that TN can be used for RAs and PWC is not so much the 

RA document number but the "protection" document 

number being referenced. In that case, the following may 

make sense and is the way we thought it was:

1) We always should use TN to pass a document number in 

all 940S transactions (which will usually also be an RA 

doc number).

2) If we are processing an RA and protecting the inventory 

to an ODN and JO/KO, we also use PWC.

3) If we are processing an RA and not protecting the 

inventory to an ODN and JO/KO, we do not use PWC (unit 

of use where the full unit pack is not being protected to a 

job, FRC).

4) If we are requesting re-warehousing back to the 

Distribution Depot, we only use TN with our internally 

generated ODN.

That said, if our interpretation is closer to the IC and PDC 

384 then we have an issue in that we don't know how to 

tell DSS whether to protect or not when the 940S is 

generated from an RA. The RA document number would 

be qualified with PWC regardless. The Service Performed 

Code does not help because we only have one to use:

applicable.

DLA provided the following 

response: DLA EBS will always 

populate the TN, however, the 

PWC could be blank or (if 

protection is needed) EBS will 

repeat the TN value using the PWC. 

There are scenarios where EBS 

would be sending a 940S to DSS 

for re-warehousing purposes 

without protecting to the 

Requisition Alert Document 

number. EBS is only mapping the 

document number with PWC when 

re-warehousing AND protecting. 

In this case the same document 

number is mapped with TN and 

PWC.
ADC 401, Enclosure 7, Page 5

Originator Response/Comment Disposition

Code 7 - DLA Re-Warehousing/Protection Request by 

Requisition Alert Document Number (Document Number 

and JO if applicable to NSY).

The Event Code does not help because we only have one to

use for moving to the IA site:

P=Re-warehouse to IA worksite and protect stock (EBS)

So what is the key from EBS to DSS so they know what to 

do? Here are some thoughts:

1) JO/KO - If we send a PWC document number with 

JO/KO we are asking to protect. If we do not want to 

protect we leave JO/KO blank. This seems to make sense 

from an FRC perspective too where we would never have a 

JO/KO so would not be asking for protection by document 

number on the 940S.

2) New Event code - The current code definition is to rewarehouse AND protect. A new code could be added that 

is just to re-warehouse (and NOT protect). This new event 

code would be used for unit of use where we are not 

protecting the full unit pack and FRCs re-warehousing for 

example.

10. DFAS No comment. Noted

11. DPAP We have reviewed and do not believe the changes impact 

WAWF or the Registry, to include the Hub. 

Concur.

12. DLA 

Logistics 

Mgt

Standards 

Questions posed to DLA Team:

Can you confirm that the Marine Corps will code the 940S 

under the disposal scenario to indicate they do not want a 

943A response? 

Also, to complete the detail can you clarify why the 

disposal direction is by email versus a 940R disposal 

release order? Are there other explicit written disposal 

directions that require an email versus a transaction? 

Assume a disposal release order is entered into DSS based 

on the email to complete the process and generate the 

945A? 

The Marine Corps will code the 

940S to indicate that they do not 

want a 943A response. 

Also, having the Marine Corps

generate an A5J would have been 

the best solution. But the Marine 

Corps said their people that would 

have entered the A5J (they can't 

systemically generate it) were 

transferred to DLA as a result of 

BRAC so DLA has to enter the 

A5J. 

13. USTRANS

COM

USTRANSCOM abstains Noted.