DEFENSE LOGISTICS AGENCY

HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

FORT BELVOIR, VIRGINIA 22060-6221

April 23, 2018 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

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

1290, DLMS Enhancement to Revise Mapping for Exception Addressing in the 

Release Confirmation (DLMS/Supply) 

 The attached change to DLM 4000.25, Defense Logistics Management Standards 

(DLMS), is approved. This change will be effective 30 days from the above approval date and 

will authorize staggered implementation. The Enterprise Business Standards Office will post the 

updated DLMS Implementation Convention (IC) to the Web at 

http://www.dla.mil/HQ/InformationOperations/DLMS/elibrary/Transformats/140_997/, within 

10 days from the above date. 

Addressees may direct questions to Mr. Eric Flanagan at 

email:DLMS_MILSTRIP@dla.mil. All others must contact their Component designated Supply 

PRC representative available at www.dla.mil/HQ/InformationOperations/DLMS/allpoc . 

HEIDI M. DAVEREDE

Director 

Enterprise Business Standards Office

Attachment

As stated

cc:

ODASD (SCI)
Attachment, ADC 1290 

Page 1 

Attachment to ADC 1290

DLMS Enhancement to Revise Mapping for Exception Addressing 

in the Release Confirmation

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Eric Flanagan,

DOD MILSTRIP Administrator, Enterprise Business Standards Office (EBSO), email:

DLMS_MILSTRIP@dla.mil

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply

b. Primary/Secondary Functional Process: Distribution

3. REFERENCE: Defense Logistics Manual (DLM) 4000.25, Defense Logistics Management

Standards (DLMS), Volume 2, Chapter 4, Requisitioning

4. APPROVED CHANGE(S):

a. Brief Overview of Change: This change allows shippers to include the full

exception address in the DLMS 945A Materiel Release Confirmation. This change requires Air

Force Contractor Inventory Control Points (CICPs) to provide the full exception address to the 

Air Force Accountable Property System of Record (APSR). This change is optional for systems 

that do not have this current requirement. 

b. Background:

(1) Materiel owners can pass an exception (clear text) ship-to address to storage

activities in the DLMS 940R Materiel Release Order (MRO). However, the DLMS 945A does 

not include the clear text address even though most information from the materiel release order is 

perpetuated to the materiel release confirmation. The DLMS 945A only includes the N101 

qualifier DA, which is used for the clear text name of the ship-to. The DLMS format does not 

include the remaining address lines normally mapped to the N2, N3, and N4 address segments. 

These address segments are not currently used in the detail portion of the DLMS 945A. This

limitation is generally acceptable since the originator of the materiel release order usually has 

visibility of the clear text address information. 

(2) The Air Force identified a requirement for enhanced shipping address

visibility in support Air Force Government-furnished property (GFP) accountability. Air Force 

CICPs are required to share inventory accounting transactions with the Air Force APSR. The 

CICP uses the DLMS 945A transaction to notify the program manager’s APSR of a status of a 

shipment. The CICP may ship property to a mailing address that is not supported by a routing 

identifier code (RIC) or DOD activity address code (DoDAAC). Because the CICP is

performing materiel management outside of the APSR, the program manager may not have prior 

visibility of exception address details, which normally appears in the materiel release order. 
Attachment, ADC 1290 

Page 2

Updating the DLMS 945A to carry the clear text exception address will provide the program 

manager/APSR full visibility of the ship-to location.

c. Approved Change in Detail: This change updates the DLMS 945A implementation 

convention (IC) to identify clear text shipping addresses. This information is required when the 

full address details would not otherwise be available to the owner/program manager 

transactionally. The DLMS 945A does not need to perpetuate the clear text address if the ownergenerated MRO identifies a clear-text ship-to address.

d. Revisions to DLM 4000.25 Manuals: Revise DLM 4000.25 as shown in the 

enclosure.

e. Proposed Transaction Flow: No changes to existing flow.

f. Alternatives: None identified.

5. REASON FOR CHANGE: This change provides capability to include the full exception 

ship-to address if the materiel owner does not have visibility of the clear text ship-to address. 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: This change corrects gaps affecting completeness of information 

communicated to trading partners via materiel release confirmation.

b. Disadvantages: None identified.

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: This change will be 

effective 30 days from approval and will authorize staggered implementation.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None identified.

9. IMPACT:

a. New DLMS Data Elements: None.

b. Changes to DLMS Data Elements: None.

c. Automated Information Systems (AIS): The Defense Property Accountability 

System (DPAS) and CICP systems supporting Air Force GFP-A must be updated to support full 

exception ship-to address details in the materiel release confirmation. Components must identify 

other systems requiring ship-to address details in the materiel release confirmation.

d. Defense Automatic Addressing System (DAAS): Update DAAS map for the 

exception address in the DLMS 945A. There is no legacy format requirement for this change.

e. Non-DLM 4000.25 Series Publications: DOD Components may need to update 

internal operating procedures and other published guidance.
Attachment, ADC 1290 

Page 3

10. PROPOSED DLMS CHANGE (PDC) 1290 RESPONSE/COMMENT RESOLUTION:

Originator Response/Comment Disposition

1. DLA No Response. Noted.

2. Navy Concur without Comment Noted.

3. Air Force Concur without Comment Noted.

4. US Army No Response. Noted.

5. USMC Concur without Comment Noted.

6. DAAS Concur without Comment Noted.

7. USTRANSCOM Concur without Comment Noted.
Enclosure 1, ADC 1290 

Page 1

Enclosure 1 to ADC 1290 

Revise the DLMS implementation convention (IC) as shown:

# Location Revisions to DLMS 945A

Materiel Release Advice (Version 4030 only)

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1290 to the list of applicable DLMS changes included in the 

DLMS IC introductory notes:

- ADC 1290 , DLMS Enhancement to Revise Mapping for Exception 

Addressing in the Release Confirmation

Identifies DLMS 

changes included 

in the IC.

2. DLMS 

Introductory 

Notes

Insert new DLMS Note 7 and renumber existing DLMS Note 8.

7. Effective April 1, 2014, Refer to ADC 1075. Users must reference 

the GENC Standard for country codes

(https://geo.aitcnet.org/NSGREG/genc/discovery) for a listing of 

authorized values. Under DLMS, use the GENC Digraph (twocharacter) code values.

8. This DLMS IC incorporates the following Proposed DLMS Change 

(PDC) and Approved DLMS Changes (ADC) listed. PDC/ADCs are 

available from the DLMS Program Office Web site: 

http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes

/processchanges/

To insert a new 

DLMS Note 7 

and move the 

existing one to a 

DLMS Note 8.

3. 1/N1/0400 Add new DLMS note 2 at the segment level as follows:

1. Must use this 1/N1/040 loop to identify the organization originating 

the transaction set.

2. Use a second iteration of the N1 loop to provide in-the-clear 

exception ship-to address details for the identified (single) document 

number under authorized conditions. 

New 

functionality for 

exception 

addressing.

4. 1/N101/0400 Add new Code DA with associated DLMS notes:

DA Delivery Address

DLMS Note:

1. Use N101 DA to identify the in-the-clear exception ship-to address 

organization name when providing detailed address lines. Use with 

1/N2/0500, 1/N3/0600, and 1/N4/0700. 

2. When detailed address lines are provided, do not repeat this entry at 

2/N101/0800 Code DA. 

3. DLMS enhancement (requires prior coordination with the 

recipient); refer to ADC 1290.

Staffing Note:

The X12 standard only supports full address details in the N1 loop at the 

header level. Since the N1 loop is the most appropriate approach for 

mapping address information, this change inserts address details at the 

header level. Because the address details are at the header level, the 

segment note specifies that this address is applicable to the single 

New 

functionality for 

exception 

addressing.
Enclosure 1, ADC 1290 

Page 2

# Location Revisions to DLMS 945A

Materiel Release Advice (Version 4030 only)

Reason

document number provided in the transaction. However, there is no 

expectation that the sender will consolidate multiple transactions 

(multiple document numbers) in a single transaction set transmission (as 

is authorized in some DLMS transactions).

5. 1/N2/0500 Open N2 with new segment level note:

DLMS Note: Use only with 1/N101/0400 Code DA to identify 

additional address information.

New 

functionality for 

exception 

addressing.

6. 1/N201/0500 Open N201 with new DLMS note:

N201 Name

DLMS Note: Use to identify in-the-clear exception organization name 

when an additional address line is needed for this information (this 

equates to address line 2 when used).

New 

functionality for 

exception 

addressing.

7. 1/N3/0600 Open N3 with new segment level notes:

DLMS Note: Use only with 1/N101/0400 Code DA to identify 

additional address information.

New 

functionality for 

exception 

addressing.

8. 1/N301/0600 Open N301 with new DLMS note:

Address Information

DLMS Note: Use to identify exception address information (this 

equates to address line 3 when all address lines are used).

New 

functionality for 

exception 

addressing.

9. 1/N302/0600 Open N302 with new DLMS note:

Address Information

DLMS Note: Use to identify exception address information (this 

equates to address line 4 when all address lines are used).

New 

functionality for 

exception 

addressing.

10. 1/N4/0700 Open N4 with new segment level note:

DLMS note: Use only with 1/N101/0400 Code DA to identify 

additional information.

New 

functionality for 

exception 

addressing.

11. 1/N401/0700 Open N401:

City Name

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

Component-unique MRC exception data.

New 

functionality for 

exception 

addressing.

12. 1/N402/0700 Open N402 with new DLMS note:

State or Province Code

DLMS Note: Use when applicable to identify the state when 

transaction includes Component-unique MRC exception data.

New 

functionality for 

exception 

addressing.

13. 1/N403/0700 Open N403:

Postal Code

DLMS Note: Use when the transaction includes Component-unique 

MRC exception data for initial postal code associated with the ship-to 

address.

New 

functionality for 

exception 

addressing.
Enclosure 1, ADC 1290 

Page 3

# Location Revisions to DLMS 945A

Materiel Release Advice (Version 4030 only)

Reason

14. 1/N404/0700 Open N404 with new DLMS note:

Country Code

DLMS Note:

1. Use to identify the country. See DLMS introductory note 7 (Refer to 

ADC 1075 for implementation).

2. Use when transaction includes Component-unique MRC exception 

data (when other than U.S.) to reflect the country code.

New 

functionality for 

exception 

addressing.

15. 2/N101/0800 Add new DLMS Note 2 for existing Code DA:

DA Delivery Address

DLMS Note:

1. Use with N102 to identify the in-the-clear exception ship-to address 

organization name.

2. Use with 2/N2/1101, 2/N3/1102, and 2/N4/1103 to identify the full 

in-the-clear exception ship-to address information under authorized 

conditions. Refer to ADC 1290.

New 

functionality for 

exception 

addressing.
Enclosure 2, ADC 1290 

Page 1

Enclosure 2, DLMS Manual Revisions

A. Revise DLM 4000.25, Volume 2, Chapter 4, Requisitioning, as indicated in red bold, italics. 

Changes shown are based upon Formal Change 9.

C4.2.6. Exception Data. 

(Intervening text not shown)

C4.2.7.5. Exception Address Information in the Materiel Release Confirmation. 

The shipping activity must include address line details in the MRC when the full address 

details would not otherwise be available to the owner/program manager transactionally. 

When the owner-generated MRO identifies a clear-text ship-to address there is no 

requirement to perpetuate this address in the confirmation beyond the first address line 

containing the organization name.