2

Approved DLMS Change 71B 

Administrative Correction for DLMS Mapping for MRO Exception Data Transaction 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Agency/DLMSO

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

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

2. FUNCTIONAL AREA: 

 Primary: Supply

3. REFERENCE: 

a. 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)

b. DLMSO Memorandum, September 21, 2004, subject: Approved DLMS Change 71A, DLMS 

Mapping for MRO Exception Data Transaction (Supply)

4. REQUESTED CHANGE: 

a. Title: Administrative Correction for DLMS Mapping for MRO Exception Data Transaction

b. Description of Change: This is an administrative change to adjust the mapping of clear text 

addressing in the DS 940R, MRO. This change corrects the placement of address lines 3 and 4 when 

DAAC conversion is required from Component unique DI Code CGU/ZGU. It also corrects the DS to 

correctly show placement of address line 3 when the clear text address is created in DLMS (i.e., the 

originating system produces a 940R with the clear text addressing already incorporated as distinct data 

elements). This change also requires that the country code be used to identify addresses outside the US 

using the appropriate X12 data element.

c. Procedures: 

(1) This transaction will be employed whenever an MRO includes clear-text exception ship-to or 

pick/pack/delivery instructions or specialized information that must be transmitted from the ICP to a DSS 

storage activity. Three types of clear text address are addressed in this administrative change as identified 

by the 2/N101/1100 qualifiers DA, IF and IAD (yellow highlighting indicate changes from previous 

version): 
3

Rules for ZGU/CGU Address Mapping for DAAS Conversion:

DA (TAC 2) Ship-to IF (TAC 3) NOA IAD (TAC M) FMS In country 

N102 address line 1 N102 address line 1 N102 address line 1 

N201 address line 2 N201 address line 2 N201 address line 2 

N202 not used N202 not used N202 not used 

N301 address line 3 N301 address line 3 N301 address line 3 

N302 address line 4 N302 address line 4 N302 address line 4 

N4 multiple postal (zip) codes N4 not used N4 not used 

 

Mapping when 940 originated in DLMS with address already integrated:

DA IF TAC 3 IAD TAC M BSM example 

N102 address line 1 N102 address line 1 N102 address line 1 N1*DA*ATTN: DANIEL MENDIOLA 

N201 address line 2 N201 address line 2 N201 address line 2 N2*MULTIPLE SCHOOL UNIT, GUAM 

N202 not used N202 not used N202 not used 

N301 address line 3 N301 address line 3 N301 address line 3 N3*PSC 455 BOX 194 

N302 not used N302 not used N302 not used 

N401 city 

N402 state (when 

applicable) 

N403 postal code 

N404 country (when 

not US) 

N405 Code IP 

N406 second Postal 

Code 

N4 city, state, 

country, postal code 

N4 city, state, 

country, postal code

N4*U.S.NAVAL STATION*GU*96913 

Note: GU in this example is the USPS State 

Abbreviation for Guam, and, therefore, 

appears in the N402. Country codes must 

appear in the N404. 

 

(2) Revise the following notes in the 940R, Material Release Order (original unchanged clear text 

address notes also included to facilitate reading): 
4

 

Location Revision Reason Federal 

IC 

2/N1/1100 Revise DLMS notes at N101: 

DA Delivery Address

DLMS Note: Use for MRO Exception Data Transaction to indicate the ship-to clear-text 

exception address is a MRO Type Address Code (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 Component-unique MRO exception data; 

may be referred to as MAPAC “TAC M” address. See introductory DLMS note 4e.

IF International Freight Forwarder 

Federal Note: Use for MRO clear-text exception data FMS Notice of Availability (NOA) 

address. 

DLMS Note: Use when transaction includes Component-unique MRO exception data; 

may be referred to as 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. 

DLMS note at N102:

Use when transaction includes Component-unique MRO exception data with N101 code 

DA, IAD, and IF to identify the exception activity name (this equates to address line 1). 

See introductory DLMS notes 4a and 4e. 

Clarification 

of acronym 

No 

update 

required 

2/N2/1101 Note at N201. 

Use when transaction includes Component-unique MRO exception data with N101 code 

DA, IAD, and IF to identify the exception address information (this equates to address 

line 2). Includes Mark For/Attention when applicable. See introductory DLMS note 4e. 

Revise N202 note. 

Delete note and close

Correction No 

updated 

required 

2/N3/1102 Revise note at N301:

DLMS Note: 1. Use when transaction includes Component-unique MRO exception data 

with N101 code DA,IAD, and IF to identify the exception address information (this 

equates to address line 3). 

3. See introductory DLMS note 4e. 

Correction 

and 

clarification 

No 

updated 

required 
5

Revise note at N302:

DLMS Note: 1. 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 only. For conversion mapping, this equates to address line 4). 

2. Do not use N302 for addresses created using the DLMS. Address line 4 with city, 

state, country information is reflected in the N4 segment using the appropriate data 

elements.

2/N4/1103 Note at N401:

DLMS Note: Use to identify the city name when transaction includes Component-unique 

MRO exception data. 

Note at N402:

DLMS Note: Use when applicable to identify the state when transaction includes 

Component-unique MRO exception data. 

Note at N403:

DLMS Note: Use when transaction includes Component-unique MRO exception data for 

initial postal code associated with the ship-to address. 

Note at 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 Componentunique MRO exception data (when other than U.S.) to reflect the country code. Deleted 

text: For DLA unique data (formerly associated with DI Code CGU), may reflect DLA 

3-position country code. See introductory DLMS note 4e. 

Note at N405:

DLMS Note: Use when transaction includes Component-unique MRO exception data to 

identify the secondary (parcel post) nine-position postal code associated with the ship-to 

address (N101 Code DA). 

 

d. Alternatives: None identified.

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

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

original CGU format. The ADC 71A addendum was required by DSS to receive exception data as initiated 

by Service ICPs using the ZGU format and DLA ICPs using CGU formats. This ADC 71B is an 

administrative correction to adjust the mapping of clear text addressing to support both conversion and 

addressing created under the DLMS. This revision will ensure that the address information is properly 

communicated.

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Supports Component-level DLMS implementation.

b. Disadvantages: None identified.
6

7. IMPACT: 

a. Data Content/Procedures: Requires update to DSS.

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 if needed.