DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J . KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

November 18, 2014 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

SUBJECT: Approved Defense Logistics Management Standards (DLMS) Change (ADC) 1150, 

Update Mapping for DLMS 940R, Materiel Release Order/Disposal Release Order 

Exception Data, to Expand Field Size of Pick/Pack/Delivery Instructions Field for 

Army Orders (Supply) 

The attached change to Defense Logistics Manual (DLM) 4000.25, Defense Logistics 

Management System, is approved for joint implementation on December 1, 2014. 

Addressees may direct questions to Ms. Ellen Hilert, DoD MILSTRIP Administrator, (703) 

767-0676; DSN 427-0676, email: Ellen.Hilert@dla.mil; or Ms. Heidi Daverede, DoD 

MILSTRIP Alternate, (703) 767-5111, DSN 427-5111, email: Heidi.Daverede@dla.mil. Others 

must contact their Component designated Supply PRC representative available at 

https://www2.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp. 

Attachment 

cc: 

ODASD (SCI) 

efense Logistics Management 

Standards Office 
Attachment, ADC 1150

Page 1

ADC 1150

Update Mapping for DLMS 940R, Materiel Release Order/Disposal 

Release Order Exception Data, to Expand Field Size of 

Pick/Pack/Delivery Instructions Field for Army Orders

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Technical POC: Army Logistics Modernization Program, (856) 988-4802 

b. Functional POC: Army Logistics Modernization Program, (314) 625-2846

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply

b. Primary/Secondary Functional Process: Materiel Release Order/Disposal Release 

Order Processing

3. REFERENCES:

a. Approved DLMS Change (ADC) 71, DLMS Mapping for DLA Materiel Release Order 

(MRO) Exception Data Transaction, Document Identifier Code CGU, dated August 7, 2002

b. ADC 71A, DLMS Mapping for Materiel Release Order (MRO)/Disposal Release 

Order (DRO) Exception Data Transaction, dated September 21, 2004

4. REQUESTED CHANGE(S):

a. Brief Overview of Change: This change modifies the mapping of the DLMS 940R

Materiel Release Order/Disposal Release Order Exception Data to allow 12 iterations of the NTE 

segment for pick/pack data in support of Army Logistics Modernization Program (LMP) and 

DLA Distribution Standard System (DSS) processing.

b. Background:

(1) ADC 71 (see reference 3.a.) modified the DLMS 940R MRO Exception Data 

mapping to transmit the data content of the DLA legacy document identifier code (DIC) CGU 

that contained clear-text exception ship-to or pick/pack/delivery instructions to be transmitted 

between the DLA Inventory Control Point (ICP) and the DLA storage activity.

(2) ADC 71A (see reference 3.b.) modified the DLMS 940R MRO/DRO 

Exception Data mapping to transmit the data content of the Service-unique variations of the 

legacy DIC ZGU data content for pick/pack/delivery instructions, which pass from the Service 

ICP to the DLA storage activity. For Army legacy DIC ZGU exception data, the pick/pack data 

field was limited to 55 characters; thereby limiting the 2/NTE01-02/0450 Code ORI to one 
Attachment, ADC 1150

Page 2

iteration in the DLMS 940R, despite the DLMS Implementation Convention (IC) capability to 

support 12 iterations.

(3) When Army LMP implemented the DLMS 940R MRO Exception Data to 

replace the legacy DIC ZGU transactions, they implemented the 12 iterations of pick/pack data

despite the ADC 71A limitation requested by the Army in 2004. With implementation of the 

DLMS, Army now requires the capability to exceed the previous 55 character limit currently in 

force. This change was identified during testing of Exception Data transactions going from 

Army LMP to DLA’s Distribution Standard System (DSS) via DLA Transaction Services. 

c. Describe Approved Change in Detail: Modify the DLA Transaction Services DLMS 

940R MRO/DRO mapping for Army LMP transactions to allow 12 iterations of 2/NTE01-

02/0450 Code ORI for a maximum of 360 characters. This data is to be passed to DSS for use in 

the Pick, Pack and/or Shipment processes.

d. Revisions to DLM 4000.25 Manuals: There is no impact to the DLMS 940R IC, as it 

already supports 12 iterations of the NTE segment for pick/pack/delivery instructions.

e. Approved Transaction Flow: There are no changes to current flows.

f. Alternatives: None.

g. Proposed DLMS Change (PDC) 1150 Staffing Response/Comment Resolution:

Originator Response/Comment Disposition

USTRANSCOM (9/25/2014) Concur without comment. Noted.

Marine Corps (10/7/2014) Concur without comment. Noted.

Air Force (10/17/2014) Concur without comment. Noted.

DLA (10/21/2014) Concur without comment. Noted.

Navy (10/27/2014) Concur without comment. Noted.

Army (11/5/2014) Concur without comment. Noted.

5. REASON FOR CHANGE: Army is not currently able to make full use of the capability that 

was to be provided by this process. Transactions sent from LMP do not process correctly, 

thereby preventing special instructions from being conveyed to the shipping activity. 

Implementation of this change will enable complete exception data to be passed to DSS, so 

supply actions can be carried out to the full extent requested by the customer and/or releasing 

Inventory Control Point (ICP).
Attachment, ADC 1150

Page 3

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: This change will enable Army to convey to DSS complete special 

instructions for picking, packing, and or shipping of materiel to customers. 

b. Disadvantages: None noted.

7. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW 

DEVELOPMENT: As this capability is already in use by one or more other DoD Components, 

DSS should have no difficulty implementing this for Army processed documents, and it is 

anticipated that no DSS changes are required.

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: December 1, 2014

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not identified.

10. IMPACT:

a. New DLMS Data Elements: None.

b. Changes to DLMS Data Elements: None.

c. Automated Information Systems (AIS):

(1) Army LMP has already begun generating transactions, under the assumption 

that a field length of 360 characters was authorized. 

(2) DLA’s DSS needs to ensure that they can receive and process this additional 

data content.

d. DLA Transaction Services: DLA Transaction Services will need to implement 

changes to the mapping of these transactions for Army to allow up to 12 iterations of 2/NTE01-

02/0450 Code ORI. DLA Transaction Services has confirmed that they can do the map update to 

allow 12 iterations of the NTE segment.

e. Non-DLM 4000.25 Series Publications: None.