1

Approved DLMS Change 71A 

DLMS Mapping for MRO/DRO Exception Data Transaction 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Agency

b. Originator: Supply PRC, Chair: Ellen Hilert, DLA DLMSO/J-62, Defense Logistics 

Management Standards Office (DLMSO), 703-767-0676 (DSN 427), ellen.hilert@dla.mil

c. DLA Point of Contact: Ms. Mary Day

2. FUNCTIONAL AREA: 

 Primary: Supply

3. REFERENCE: DLMSO memorandum, August 7, 2002, subject: Approved DLMS Change 71, 

DLMS Mapping for DLA Materiel Release Order (MRO) Exception Data Transaction, Document 

Identifier (DI) Code CGU (Supply)

4. REQUESTED CHANGE: 

a. Title: DLMS Mapping for MRO Exception Data Transaction, DI Code ZGU

b. Description of Change: This change accommodates the Distribution Standard System 

(DSS) requirement for receiving MRO/DRO exception data. This change modifies the IC/DS 

940R, MRO/DRO, to transmit the data content of the Service-unique variations of the DI Code 

ZGU. The DI Code ZGU passes from the Service Inventory Control Point (ICP) to the DSS 

storage activity. Inclusion of these data elements supports DAAS conversion from the Service 

unique ZGU transaction originated by ICP to the DLMS transaction required by the receiver. This 

change also includes commodity-unique variations not included in the ADC 71 mapping for the 

DLA DI Code CGU.

c. Procedures: 

(1) This transaction will be employed whenever an MRO/DRO includes clear-text 

exception ship-to or pick/pack/delivery/disposal instructions or specialized information that must be 

transmitted from the ICP to a DSS storage activity. 

(2) Implementation Scheduling/Issues: Full implementation of the conversion map for 

the ZGU is dependant upon successful accommodation of the zero latency requirement for the 

USAF and USA interface. Until resolved, USAF and USA will continue to use the ZGU submitted 

via the Customer Information Control System (CICS) requiring no conversion by DAAS. USN 

does not employ CICS and implementation for DSS is required to support DSS programming under 

Release 5.1 (December 2004). 
2

(3) Add the following codes/notes to the 940R, Material Release Order/Disposal Release 

Order: 

 

# Location Revision Reason Federal IC 

1. 1/W05/0200 Revise W0507 DLMS notes:

EB Establish Additional Address 

Federal Note: Use with W0506 code NA to indicate the 

MRO contains an exception address. 

Revise DLMS Note: Use for Materiel Release Order (MRO) 

Exception Data Transaction (DLA DI Code CGU/ZGU) 

(ICP to DSS Storage Activity). See introductory DLMS 

note 4e. 

PI Provide Additional Information 

Federal Note: Use with W0506 code NA to indicate the 

MRO contains exception pick/pack/delivery/disposal

instructions. 

Revise DLMS Note: Use for Materiel Release Order 

(MRO)/Disposal Release Order (DRO) Exception Data 

Transaction (DLA DI Code CGU/ZGU) (ICP to DSS 

Storage Activity). See introductory DLMS note 4e. 

Clarification. 

Generic transaction 

name used to include 

additional DI Code. 

Staffing Note: 

Under this change, 

Job order number or 

other non-address 

information will all 

be considered 

applicable to code PI. 

The current 80 rp 

format contains a 

record type which is 

also mapped in the 

LQ segment for 

DADMS exception 

data formats, and 

may be used for all 

exception data 

formats as needed. 

Blue highlighting in 

DLMS notes identifies 

revisions identified 

subsequent to the 

original staffing of the 

proposal. 

No update 

required 

2. 2/N901/0400 Authorize use of additional data element 128 (Reference 

Identification Qualifier) code values to identify the following DLA 

DADMS-specific attributes, and add the accompanying DLMS 

notes:

55 Sequence Number 

DLMS Notes: “1. Use to identify the sequence number 

associated with the map manifest.

2. Use when transaction includes Component-unique 

exception data.” 

P7 Product Line Number

DLMS Notes: “1. Use to identify the mapping products 

Line Number. 2. Use when transaction includes 

Component-unique exception data.” 

IX Item Number 

Supports commodity 

unique requirement for 

maps. 

Code values 55, FJ, IX, or 

MK will accommodate other 

DADMS-unique exception 

data fields (i.e., ZGU 

contents). 

No update 

required 
2

DLMS Notes: “1. Use to identify the map National 

Evacuation Order (NEO) Pack Line Number. 

2. Use when transaction includes Component-unique 

exception data. 

3. An ANSI data maintenance request has been prepared to request 

a new code qualifier for NEO Pack Line Number for future use. ” 

MK Manifest Key Number 

DLMS Notes: “1. Use to identify the map Manifest 

Number. 

2. Use when transaction includes Component-unique 

exception data.” 

6E Map Reference

DLMS Notes: “Use in MRO to identify the mapping 

products National Evacuation Order (NEO) NIMA 

Reference Number (NRN). 

2. Use in DRO to identify the NIMA NRN.

3. Use when transaction includes Component-unique 

exception data.” 

6G Map Number 

DLMS Note: 1. Use to identify the map edition number. 

2. Use when transaction includes Component-unique MRO 

exception data; see introductory DLMS note 4e. 

Revise existing qualifier WO note: 

WO Work Order Number 

DLMS Note: 1. Use as needed to identify a maintenance 

work order number or job number.

2. Use when transaction includes Component-unique 

MRO exception data; see introductory DLMS note 4e.

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

Qualifiers were switched to 

match ANSI names more 

closely with the functional 

data element names. 

3. 2/NTE/0450 Revise DLMS Note: Use to indicate special instructions. 

2. Use when transaction includes Component-unique MRO 

exception data; See introductory DLMS note 4e. 

Revise Note for NTE01 code ORI and add new codes DEL 

and PMT and associated notes. 

ORI Order Instructions.

DLMS Note: DLMS Note: Use to indicate 

pick/pack/delivery instructions Exception information is 

required to be sent with accompanying exception MRO. 

Segment may be repeated up to 12 times with same NTE01 

qualifier. Up to 360 bytes of text may be sent. A maximum 

of 30 bytes may be sent for each occurrence of NTE01. See 

introductory DLMS note 4e. 

DEL Delivery 

DLMS Note: 1. Use to indicate delivery instructions. 

2. Use when transaction includes Component unique MRO 

exception data; see introductory DLMS note 4e. 

Supports 

Component unique 

exception data. 

STAFFING NOTE: 

New codes are a 

placeholder for 

future use. 

Currently only AF 

CICS ZGU Type D 

maps to DEL 

Delivery 

Instructions and 

Type B Billing 

Instructions. 

Others use only 

Type P for 

pick/pack/delivery 

instructions which 

maps to code ORI. 

Updated required 
3

PMT Payment 

DLMS Note: 1. Use to indicate billing instructions. 

2. Use when transaction includes Component unique MRO 

exception data; see introductory DLMS note 4e. 

4. 2/QTY01/0700 Add qualifiers and associated notes:

EU Total Consolidated Subsidiaries 

DLMS Note: 1. Use to identify the mapping products 

National Evacuation Order (NEO) PACK Line Total (total 

number of NEO pack items in this requisition). 

2. Use when transaction includes Component-unique 

exception data. 

3. An ANSI data maintenance request has been prepared to 

request a new code qualifier for Total Number of Lines in 

Pack for future use. 

46 Total Transactions 

DLMS Note: Use to indicate the mapping product total 

manifest lines. (total number of lines/MROs within this NEO 

PACK Manifest). 

2. Use when transaction includes Component-unique 

exception data. 

3. An ANSI data maintenance request has been prepared to 

request a new code qualifier for Total Number of Manifest 

Lines for future use. 

Supports 

commodity unique 

requirement for 

maps. 

5. 2/G6201/0900 Add qualifiers 07 and associated notes:

07 Effective Date 

DLMS Note: 1. Use to identify the map effective date. 

2. Use when transaction includes Component-unique MRO 

exception data; see introductory DLMS note 4e. 

BC Publication Date 

DLMS Note: 1. Use to identify the map edition date. 

2. Use when transaction includes Component-unique MRO 

exception data; see introductory DLMS note 4e. 

Supports 

commodity unique 

requirement for 

maps. 

No update 

required 

6. 2/N1/1100 Revise DLMS notes: 

DA Delivery Address

DLMS Note: Use for MRO Exception Data Transaction 

(DLA DI Code CGU) to indicate the ship-to clear-text 

exception address is a TAC 2 (ship-to) freight address. 

IAD Foreign Office 

Federal Note: Use for MRO clear-text exception data FMS 

in-country address. 

DLMS Note: Use when transaction includes Componentunique MRO exception data; MAPAD TAC M address. See 

introductory DLMS note 4e.

IF International Freight Forwarder 

 No update 

required 
4

Federal Note: Use for MRO clear-text exception data FMS 

Notice of Availability (NOA) address. 

DLMS Note: Use when transaction includes Componentunique MRO exception data; MAPAC TAC 3 address. See 

introductory DLMS note 4e. 

ST Ship To 

DLMS Note: 1. Use with code BT for reimbursable material. 

Use in redistribution orders, material release orders, 

historical material release orders, disposal release orders, 

and historical disposal release orders to identify the 

organization to receive the material, when different from the 

activity being billed for the material. Use precludes the use 

of code BS. 

2. May be used with clear text address for excess plant 

property requisitions only. See introductory DLMS note 

4e. 

Modify DLMS note at N102 as follows:

Use when transaction includes Component-unique MRO 

exception data with N101 code DA, IAD, and IF to identify 

the exception activity name (for conversion mapping this 

equates to address line 1). See introductory DLMS notes 4a 

and 4e. 

7. 2/N2/1101 Revise N201 note. 

Use when transaction includes Component-unique MRO 

exception data with N101 code DA, IAD, and IF to identify 

the exception address information (for conversion mapping 

this equates to address line 2). Includes Mark 

For/Attention when applicable. See introductory DLMS 

note 4e. 

Revise N202 note. 

Use when transaction includes Component-unique MRO 

exception data with N101 code IAD, and IF to identify the 

exception address information (for conversion mapping 

this equates to address line 3). See introductory DLMS 

note 4e. 

Clarification No update 

required 

8. 2/N3/1102 Modify segment note:

DLMS Note: 1. Use with 2/N101/1100 code DA, IAD, IF, 

and ST to provide the additional ship-to information. 

Revise element note to N301:

DLMS Note: 1. Use when transaction includes 

Component-unique MRO exception data with N101 code 

DA to identify the exception address information (for 

conversion mapping this equates to address line 3). 

2. Use when transaction includes Component-unique 

MRO exception data with N101 code IAD, and IF to 

Clarification No update 

required 
5

identify the exception address information (for conversion 

mapping this equates to address line 4). 

 4. See introductory DLMS note 4e. 

9. 2/N4/1103 Modify segment note:

DLMS Note: 1. Use with 2/N101/1100 code DA, IAD, IF, 

and ST to provide the additional ship-to information. 

Add note to N401:

DLMS Note: Use to identify the city name when transaction 

includes Component-unique MRO exception data. 

Add note to N402:

DLMS Note: Use when applicable to identify the state when 

transaction includes Component-unique MRO exception 

data. 

Add note to N403:

DLMS Note: Use when transaction includes Componentunique MRO exception data for initial postal code 

associated with the ship-to address. 

Revise note to N404: 

DLMS Note: Use to identify the country. Data element 1270, 

Code 85, Country and Activity Code, lists applicable code 

values. Use when transaction includes Component-unique 

MRO exception data (when other than U.S.) to reflect the 

country code. For DLA unique data (DI Code CGU), may 

reflect DLA 3-position country code. See introductory DLMS 

note 4e. 

N405 Add code IP: Postal

DLMS Note: Use when transaction includes Componentunique MRO exception data to identify the secondary 

(parcel post) nine-position postal code associated with the 

ship-to address (N101 Code DA). Use only when this postal 

code differs from initial postal code identified in N403. 

Clarification and 

improved mapping. 

No update 

required 

10. 2/LQ01/1300 Add new qualifier and notes: 

61 Information Indicator Code 

DLMS Notes: Use when transaction includes Componentunique exception to indicate the specific type of exception 

data as identified by the exception data record type. 

Supports 

commodity unique 

requirement. 

d. Alternatives: None identified.

5. REASON FOR CHANGE: This change supports DLMS implementation. ADC 71 allowed DLA 

BSM to initiate MRO/DRO exception data in a DLMS format and provided mapping for conversion back 

to the original CGU format. This addendum is required by DSS to receive exception data as initiated by 
6

Service ICPs using the ZGU format and DLA ICPs using CGU formats. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Supports Component-level DLMS implementation.

b. Disadvantages: None identified.

7. IMPACT: 

a. Data Content/Procedures: Requires update to DAAS mapping.

b. Publication(s): DOD 4000.25-M, DLMS, Federal IC 940R and corresponding DS. The DS 

revision requires corresponding revision of the Federal IC. All applicable revisions will be submitted to 

the EDISMC/Logistics Functional Work Group for coordination/approval.

MRO Exception Data Formats 

CICS ZGU received (Air Force): 

Field Length Pos Mapping Information 

Doc Id 3 (1-3) 

Docno 15 (4-18) 2/LQ01/1300-0 

Exception Data 3100 record types are delimited by “*” and records by “@” 

Type “J” record: 

Record Type 1 (19-19) 1/W0507/0100-PI 

Job Ord No 6 (20-25) 2/N901/0400-WO 

POE 3 (26-28) Internal DSS/not mapped 

POD 3 (29-31) Internal DSS/not mapped 

APOE 3 (32-34) Internal DSS/not mapped 

APOD 3 (35-37) Internal DSS/not mapped 

SURC 4 (38-41) Internal DSS/not mapped 

AFS Dodaac 6 (42-47) Internal DSS/not mapped 

CRP BBP Dodaac 6 (48-53) Internal DSS/not mapped 

Type “M” record: 

Record Type 1 (19-19) 1/W0507/0100-EB 

Pre Alloc Flag 1 (20-20) Internal DSS/not mapped 

Pi Pk Hd Ex Flag 1 (21-21) Internal DSS/not mapped 

Cbl Excep Flag 1 (22-22) Internal DSS/not mapped 

Cost Code 2 (23-24) Internal DSS/not mapped 

Func Flag 3 (25-27) Internal DSS/not mapped 

Bol Air Rate 1 (28-28) Internal DSS/not mapped 

Mode Desc 6 (29-34) Internal DSS/not mapped 

Port Bypass Ind 1 (35-35) Internal DSS/not mapped 

Ship to zip code 9 (36-44) 

Prcl Post zip code 9 (45-53) 
7

Type “P” record: 

Record Type 1 (19-19) 1/W0507/0100-PI 

Pick pack instr 60 (20-79) 2/NTE01-02/0450-ORI 

Type “D” record: 

Record Type 1 (19-19) 1/W0507/0100-PI 

Dlvry instr 60 (20-79) 2/NTE01-02/0450-DEL 

Type “B” record: 

Record Type 1 (19-19) 1/W0507/0100-PI 

Bl Spec Instr 60 (20-79) 2/NTE01-02/0450-PMT 

Type “A” record: 

Record Type 1 (19-19) 1/W0507/0100-EB 

Type Address Code 1 (20-20) 

Address line 35 (21-55) 

Navy ZGU or CGU: 

Field Length Pos 

Doc Id 3 (1-3) 

Ric To 3 (4-6) 

Docno 14 (7-20) 

Suffix 1 (21-21) 

Record Type 1 (22-22) 

Exception Data 51 (23-73) 

Ric From 3 (74-76) 

Transaction Nbr 2 (77-78) 

Total Transacations 2 (79-80) 

Type “J” record: (22) 1/W0507/0100-PI 

Job Ord No 6 (23-28) 2/N901/0400-WO 

Type “P” 1 (22) 1/W0507/0100-PI 

Pi Pk Instr 30 (23-52) 

Type “A” record: (22) 1/W0507/0100-EB 

Type Address Code 1 (23-23) 2=Ship-to Address 2/N101/1100=DA 

 3=Notice of Availability 2/N101/1100=IF 

 M=FMS In-Country 2/N101/1100=IAD 

Line Number 1 (24-24) If 2/N101/1100=DA 

Address Line 35 (25-59) 2/N102/1100 

Line Number 2 (24-24) -- 

Address Line 35 (25-59) 2/N201/1101 

Line Number 3 (24-24) -- 

Address Line 35 (25-59) 2/N301/1102 

Line Number 4 (24-24) -- 

Address Line 35 (25-59) 2/N401/1103 (city) 

 Or 
8

 2/N401/1103 (city) 

 N402 (state) 

 N403 (zip) 

 N404 (country code) 

 

 STAFFING NOTE: When exception address is generated in DLMS 940R use discrete data 

elements for city, state (if U.S.), zip, country (if outside U.S.). When exception address is generated as 

CGU/ZGU, it must be converted and entire 4th line is compressed from 35 characters to 30 characters to fit 

in city name field at N401. Components must indicate if use of the country code is acceptable. The 

N4 segment does not provide for a clear text country. DAAS and DSS must be able to process either 

construct. In addition, Country code may be 2-character MILSTRIP authorized value (Data element 1270, 

Code 85) or 3-character DLA unique code perpetuated from YRZ. 

Line Number 1 (24-24) If 2/N101/1100=IF 

Address Line 35 (25-59) 2/N102/1100 

Line Number 2 (24-24) -- 

Address Line 35 (25-59) 2/N201/1101 

Line Number 3 (24-24) -- 

Address Line 35 (25-59) 2/N202/1101 

Line Number 4 (24-24) -- 

Address Line 35 (25-59) 2/N301/1102 

 Or 

 2/N401/1103 (city) 

 N402 (state) 

 N403 (zip) 

 N404 (country code) 

Line Number 1 (24-24) If 2/N1/1100=IAD 

Address Line 35 (25-59) 2/N102/1100 

Line Number 2 (24-24) -- 

Address Line 35 (25-59) 2/N201/1101 

Line Number 3 (24-24) -- 

Address Line 35 (25-59) 2/N202/1101 

Line Number 4 (24-24) -- 

Address Line 35 (25-59) 2/N301/1102 

 Or 

 2/N401/1103 (city) 

 N403 (zip) 

 N404 (country code) 

 

 STAFFING NOTE: Address line 4 for NOA and In-Country were previously mapped to N301. 

Under this revision, we are allowing use of city, state, zip, and country code for exception addresses 

created in DLMS 940R. When exception address is generated in CGU/ZGU, it must be converted and the 

entire 35-character 4th line will continue to map to N301 (no compression needed). DAAS/DSS must be 

able to process either construct. In addition, Country code may be 2-character MILSTRIP authorized value 

(Data element 1270, Code 85) or 3-character DLA unique code perpetuated from YRZ. 

Type “M” record: 1/W0507/0100-EB 

Manual Alloc Flag 1 (23-23) Internal DSS/not mapped 
9

PP Held Flag 1 (24-24) Internal DSS/not mapped 

CBL Flag 1 (25-25) Internal DSS/not mapped 

Cost Code 2 (26-27) Internal DSS/not mapped 

Func Flag 3 (28-30) Internal DSS/not mapped 

Bol Air Rate 1 (31-31) Internal DSS/not mapped 

Mode Desc 6 (32-37) Internal DSS/not mapped 

Zone Code 3 (38-40) Internal DSS/not mapped 

Port Bypass Ind 1 (41-41) Internal DSS/not mapped 

Ship to zip code 9 (42-50) 2/N403/1103 

Prcl Post zip code 9 (51-59) 2/N405-06/1103-IP 

ARMY: 

Field Length Pos Mapping Notes 

Doc Id 3 (1-3) 

Docno 14 (4-17) 

Suffix 1 (18-18) 

Job Ord No 6 (19-24) 2/N901/0400-WO 

Pi Pk Data 55 (25-79) 2/NTE01-02/0450-ORI 

Rec Type 1 (80-80) 1= job ord no 1/W0507/0100-PI 

Rec Type 1 (80-80) 2= pi pk instr 1/W0507/0100-PI 

Defense Mapping Agency Automated Distribution Management System (DADMS) 

Exception Data Materiel Release Order/Disposal Release Orders

 

Common ZGU A5J ZGU DLMS Mapping 

RP Data Element Sample Data 

(either) 

RP Data Element Sample Data 

1-3 DI Code “ZGU” 1-3 DI Code 

“ZGU” 

 2/LQ01/1300-0 

4-6 RI Code TO DDMA RI Code, 

i.e., SAH 

4-6 RI Code TO DDMA RI Code, i.e., 

SAH 

7-21 Document 

No/Suffix 

Must match 

corresponding A5_ 

Document 

No/Suffix 

7-21 Document No/ 

Suffix 

Must match 

corresponding A5J 

Document No/Suffix 

Same as 

corresponding 

MRO/DRO 

22 Record Type Blank, D or P 22 Record Type N or P 1/W0507/0100-PI 

2/LQ01/1300-61 

23-

37 

NEO NIMA 

Reference Number 

(NRN) 

e.g., NEO 

CAMEROON 

 2/N901/0400-6E 

 23-25 Edition 

Number 

2/N901/0400-Z1 

 26-31 Effective Date CCYYMM, e.g., 

2004062 

2/G6201/0900-07 

 32-38 Edition Date CCYYDDD, e.g., 

200403 

2/G6201/0900-BC 

38-

45 

Manifest Number 

(of the associated 

manifest) 

e.g., 59211734 2/N901/0400-MK 

 39-53 NIMA 

Reference 

Relates to NSN, e.g., 

FAATP711065NC01 

2/N901/0400-6E 
10

Number (NRN) 

46-

49 

Sequence Number 

(of the manifest) 

e.g., 0001 2/N901/0400-55 

50-

54 

Line Number (of the 

specific MRO 

within the manifest) 

e.g., 00001 2/N901/0400-P7 

55-

59 

Total Manifest Lines 

(total lines/MRO 

within the manifest) 

e.g., 00013 54-73 Blank 2/QTY01/0700-46 

60-

64 

NEO Pack Line 

Number (the 

specific line number 

for the MRO of this 

NEO pack manifest) 

e.g., 00001 2/N901/0400-IX 

65-

69 

NEO Pack Line 

Total (total number 

of lines/MRO within 

this NEOPACK 

manifest) 

e.g., 00013 2/QTY01/0700-EU

70-

73 

Blank 

74-

76 

RIC FROM DSCR DADMS 

RIC, i.e., “HM8” 

74-76 RIC FROM DSCR DADMS RIC, 

i.e., “HM8” 

Same as 

corresponding 

MRO/DRO 

77-

78 

Transaction Number Constant “01” 77-78 Transaction 

Number 

Constant “01” Not mapped 

79-

80 

Total Transactions Constant “01” 79-80 Total 

Transactions 

Constant “01” Not mapped