DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 2206<>-6221 

July 10, 2015 

MEMORANDUM FOR SUPPLY AND SUPPLY DISCREPANCY REPORT PROCESS 

REVIEW COMMITTEE (PRC) MEMBERS 

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

Revise DLMS 940R Materiel Release and DLMS 945A Materiel Release 

Confirmation for Carrier Account Data Associated with Directed Return of 

Discrepant/Deficient Materiel and Procedures for use of the DLMS 940R when 

Directing Shipment of Discrepant/Deficient Materiel via Supply Discrepancy 

Report (SDR) Reply (Supply/SDR) 

The attached change to DLM 4000.25, Defense Logistics Management Standards, is 

approved for implementation. The updated DLMS Implementation Conventions (IC) will be 

posted to the Defense Logistics Management Standards Office Web at www.dla.mil/j6/dlmso/elibrary/TransFormats/ 140 997.asp within 10 days from the above date. 

Addressees may direct questions to Ms. Ellen Hilert, DOD MILSTRIP Administrator, 703-

767-0676 or DSN 427-0676, e-mail: ellen.hilert@dla.mil, or Ms. Heidi Daverede, DOD 

MILS TRIP Alternate, 703-767-5111; DSN 427-5111, e-mail: heidi.daverede@dla.mil. Others 

may contact their Component designated Supply PRC representative available at: 

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

Attachment 

As stated 

cc: 

ODASD (SCI) 

Director 

Defense Logistics Management 

Standards Office 
Attachment, ADC 1164

Page 1

ADC 1164

Revise DLMS 940R Materiel Release and 

DLMS 945A Materiel Release Confirmation for Carrier Account Data

Associated with Directed Return of Discrepant/Deficient Materiel and

Procedures for Use of the DLMS 940R When Directing Shipment of 

Discrepant/Deficient Materiel via Supply Discrepancy Report (SDR) Reply

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Technical POC: DLA Distribution, J4-BC, 717-770-5006 

b. Functional POC: DLA Distribution, J4-BC, 717-770-5006

2. FUNCTIONAL AREA:

a. Primary Functional Area: Materiel Release and SDR/PQDR

b. Secondary Functional Area: Transportation 

3. REFERENCES:

a. DLM 4000.25-M, Defense Logistics Management Standards, Volume 2, Supply

b. DLA Audit Report OIG-FY-14-05, Supply Discrepancy Reports – Vendor Follow-up 

and Resolution, dated February 7, 2014

4. REQUESTED CHANGE(S):

a. Brief Overview of Change: Substantive updates subsequent to staffing are 

highlighted.

(1) This change approves incorporation of carrier and associated account data in 

the DLMS 940R Materiel Release Order (MRO) for the purpose of communicating return 

shipping instructions to the storage activity. Identification of the carrier and applicable account 

number will permit systemic logic within the storage activity to read and apply the data thereby 

enabling the transportation costs to be assumed by the vendor to which discrepant materiel is 

being returned. Use of the directed carrier will be confirmed by repeating the carrier and account 

information in the DLMS 945A. Although the original proposed use of this change targeted 

DLA distribution center receipt of discrepant/deficient materiel, this change is authorized for 

internal Component use and for the supply-transportation interchange.

(2) This change also updates SDR Reply procedures to clarify that disposition 

instructions for discrepant/deficient materiel provided to DLA distribution centers for the 

purpose of directing shipment of the discrepant materiel to another location, (e.g., return to the 

vendor) requires concurrent transmission of a DLMS 940R Materiel Release. The DLMS 940R 

is required to ensure the audit history for this materiel is properly recorded.
Attachment, ADC 1164

Page 2

b. Background:

(1) DLA Audit Report OIG-FY-14-05, 7 February 2014, provided a finding 

“DLA Incurred Shipping Costs.” Among audited SDR transactions, DLA incurred about $2,000 

as a result of the distribution center’s failure to properly follow instructions provided on 46 

audited SDRs. Recommendation 8 was presented to “Identify and evaluate the gaps in the 

process that are preventing the depots from returning discrepant material to the vendor at vendor 

expense. Make systemic changes to [DLA Distribution Standard System] DSS that will allow 

warehouse employees to consistently return material at vendor expense for both small parcel and 

freight.”

(2) It is current practice for owners of discrepant/deficient materiel to provide a 

release order to the distribution center to ship this materiel to another location. However, there is 

no explicit guidance stating this is a requirement. DLA Distribution has reported that there are 

some occasions when no release order is provided and center personnel must generate the 

applicable release transaction on behalf of the owner. 

c. Approved Change in Detail:

(1) DLMS transactions must be updated to support standard formatting to 

systemically provide/read/confirm the carrier name, Standard Carrier Alpha Code (SCAC), and 

carrier account number for accomplishing directed return of discrepant/deficient materiel to the 

vendor. This is data specifically applicable when the materiel owner has coordinated with the 

vendor for disposition of the nonconforming materiel and the vendor has agreed to assume the 

transportation cost for the return movement. However, it could be used for other scenarios 

where the owner wants to ensure that a specific carrier and carrier account number are used. 

Revise DLMS 940R Materiel Release to provide Carrier Name, with its associated SCAC, and

the applicable Carrier Account Number. The storage activity is required to ship using the 

designated carrier and account number provided in the MRO; no other routing logic or

transportation contracts can be used. Inclusion of carrier data on the DLMS 940R is optional 

based upon Component need and implementation status. The Carrier Name, SCAC, and Carrier 

Account Number will be perpetuated to the DLMS 945A Materiel Release Confirmation. 

(2) Components must submit a materiel release transaction to DLA distribution 

centers when directing shipment of discrepant materiel located at a DLA distribution center. 

Components must ensure the release order is provided and not rely on the distribution center to 

generate the necessary transaction to drop the inventory and issue the materiel. This requirement 

is also applicable to disposal release orders (DRO) when the SDR directs disposal of the 

discrepant materiel. 

(3) Components using the DLMS materiel release internally may also employ 

these procedures to provide carrier information. Where applicable, carrier account information 

may be communicated through the supply-transportation interchange using the DLMS 940R and 

945A.

d. Revisions to DLM 4000.25 Manual:

(1) DLM 4000.25, Volume 2 revisions are shown at Enclosure 1. 

(2) DLM 4000.25, Volume 3 revisions are shown at Enclosure 2. 
Attachment, ADC 1164

Page 3

(3) DLMS Implementation Convention (IC) revisions are shown at Enclosure 2. 

This change is applicable to the DLMS 940R and the DLMS 945A (Version 4010 and Version 

4030).

e. Transaction Flow: No change to existing transaction flow. 

f. Alternatives: Provide carrier information offline or by using a remarks data field in 

the MRO (e.g., the narrative field used for delivery instructions (2/NTE01/0450 Code ORI).

5. REASON FOR CHANGE: This change accommodates communication of carrier 

information using enhanced DLMS transactions to facilitate payment of transportation charges 

by a third party. This will reduce the cost to Government for discrepancies/deficiencies 

attributed to the vendor.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: This change will facilitate standardized transmission of carrier and 

account information to storage activities or customers when directing shipment of 

discrepant/deficient materiel. Standardizing this information will improve recognition and 

processing of transportation charges to the correct party.

b. Disadvantages: None noted.

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: 

a. A target date for DLA Enterprise Business System (EBS) and DLA Distribution 

Standard System (DSS) implementation of updates to the release order are not available at this 

time.

b. DLA Transaction Services will complete updates approximately six weeks from 

release of the ADC.

c. Components are requested to identify target implementation date for Component use 

of these procedures. 

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: DLA estimated transportation savings at $85,000 

based on total SDR population of DLA audit (Reference 3.b.). 

9. IMPACT:

a. New DLMS Data Elements: This change adds one new data element:

Carrier Account Number. Identifies the account established with a commercial transportation

company (e.g., FedEX, UPS, etc.) by the party responsible for payment of transportation costs.

DLA recommends this data element be established as a maximum of ten alphanumeric 

characters.

b. Changes to DLMS Data Elements: None identified.
Attachment, ADC 1164

Page 4

c. Automated Information Systems (AIS):

(1) DSS: System changes will be required to accept carrier information from the 

MRO and perpetuate to the materiel release confirmation. System changes may be required to 

ensure that the carrier information provided in the MRO is applied rather than an alternative 

routing logic/transportation contract. 

(2) EBS: System changes will be needed to input carrier information account 

number on the MRO and accept the perpetuation of this information on the materiel release 

confirmation. 

(3) DLMS-capable Component ICP systems: Component systems should be 

updated to support inclusion of carrier account information in MROs and resulting confirmation

for the DLA DSS interface and for internal use as appropriate.

(4) Cargo Movement Operations System (CMOS): System changes will be 

needed to accommodate carrier information account number on the DLMS 940R and 945A used 

for the supply-transportation interchange.

d. DLA Transaction Services:

(1) DAAS maps must be updated for the DLMS 940R and 945A.

(2) The carrier account number must be protected so it is not visible to outside 

parties. It should not be displayed in Web Visual Logistics Information Processing System 

(WebVLIPS).

(3) Request the carrier account number data field be suppressed when providing 

copies of the MRO or associated confirmation to Enterprise visibility systems, such as Integrated 

Data Environment (IDE)/Global. Transportation Network (GTN) Convergence (IGC).

e. Non-DLA Logistics Management Standards Publications: The following internal 

DLA guidance may be impacted.

(1) Transportation Training Manual

(2) Stock Readiness Training Manual

(3) Inventory Training Manual 

10. PROPOSED DLMS CHANGE 1164 STAFFING RESPONSE/COMMENT 

RESOLUTION:

Originator Response/Comment Disposition

1. Army Concur Noted.
Attachment, ADC 1164

Page 5

Originator Response/Comment Disposition

2. Marine Corps Concur Noted.

3. DLA DLA concurs with PDC 1164 and submits the 

following comment on Staffing Note #2:

Currently, material is identified in SDR. SDR 

disposition is a direct response to material stock 

number and condition code. In future state, 

requisitions dropped by the Supply Center /ICP 

continue to identify material stock number and 

condition code with no change from current process. 

The process change directed by this PDC merely 

provides a format by which Supply Center/ICP may 

identify small parcel or freight Carrier and vendor 

account number to be used when it is determined that 

material should be returned at vendor expense rather 

than DOD funding the transportation for SDR 

disposition of material back to vendor. 

Today, and future state, neither process systemically 

links the MRO/DRO to a specific SDR/SQCR. The 

supply center drops the MRO. However, the MRO 

should be dropping to support specific SDR 

disposition. It's part of the same process, but never 

linked systemically. 

Noted.

PDC 1164 included the following 

staffing notes: 

1. Components must ensure the MRO is 

provided and not rely on the distribution 

center to generate the necessary 

transaction to drop the inventory and 

issue the materiel. (This requirement is 

also applicable to disposal release orders 

(DRO) when the SDR directs disposal of 

the discrepant materiel.)

2. The distribution center must be able 

to link the materiel associated with the 

MRO (or DRO) with the specific 

materiel identified in the SDR. It is not 

clear if there is a potential for 

misaligning the intended MRO (or 

DRO) materiel with the applicable SDR 

since the materiel is generically 

identified by stock number and condition 

in both. Request feedback on this 

concern from DLA Distribution.

4. Navy Navy concurs with PDC 1164, with the following 

comments:

1. Navy ERP--Navy and DLA will have to examine 

whether this functionality should be used for the 

shipment of NWCF stock using the electronic 

Retrograde Management System (eRMS)/Navy InTransit Accountability (NITA) carrier. Currently this 

is a manual process to pull the material off of the 

shipping floor at the distribution center and contact the 

carrier. This may allow automation of this process at 

the distribution center. Recommend a meeting be set 

up between WSS eRMS/NITA office, Navy ERP and 

DLA DSS. The PDC does suggest that this could be 

used for processes outside of the sphere of SDR. If it 

is decided to use the process to support the 

eRMS/NITA carrier then it would be a small change to 

Navy ERP. The SDR process is not within Navy ERP 

at this time - so that part of the change will not impact 

Navy ERP.

2. Question for DLMSO--as Navy ERP mentioned, is it 

appropriate to use this transaction outside the SDR 

process?

Noted.

1. Meeting to be scheduled.

2. Once programmed for DSS, the 

carrier information will be available for 

use in support of other types of directed 

shipments using the DLMS 940R. 

DLMS capable non-DSS storage 

activities may also implement this 

process.
Attachment, ADC 1164

Page 6

Originator Response/Comment Disposition

5. Air Force Concur.

Below is ILS-S response to subject PDC:

ILS-S has several questions/concerns concerning this 

PDC: 

1. How does this MRO tie into the SDR process? Will 

we receive an 842A/R with information that 

corresponds to the MRO directing the return shipment?

2. Currently, ILS-S takes the 940R MRO and 

transforms it into the MILS A2*. ILS-S will currently 

NOT be able to make use of the additional info on the

940R, i.e. carrier and shipping 

information/instructions. We will update our DLMS 

compliancy action plan and our DLMS requirements 

documentation to include this new process once the 

PDC is approved.

3. Additionally - we should add to this PDC - to 

perpetuate the MRO (940R) shipping information to 

the CMOS 940R and 945A as applicable.

Noted.

1. At this time, there is no change to the 

formatted content of the SDR. A 

separate change may be considered in 

the future. SDR replies for discrepant 

receipts at retail locations normally 

provide contact information to obtain 

carrier account information for the return 

shipment. The ADC clarifies that the 

SDR reply to distribution centers 

requesting shipment of 

discrepant/deficient materiel must be 

provided concurrent with a materiel 

release order.

2. Noted.

3. Added. The ADC now states: 

"Components using the DLMS materiel 

release internally may also employ these 

procedures to provide carrier 

information. Where applicable carrier 

information must be passed through the 

supply-transportation interchange" and 

impact is updated to specify CMOS.

6. USASAC How will the action activity provide the carrier's 

info/account to the ILCO for directed returns? Each 

time the action activity (SMS) directs returns they DO 

NOT provide TAC/Comm Carrier or other methods of 

reimbursement, only the return destination is provided. 

Will this information be part of the WEBSDR response 

reply? The USASAC has been assigning the DLA 

TAC when arranging transportation for DLA directed 

returns. 

"As an alternative to providing transportation 

reimbursement, the responsible action activity may 

provide the transportation account code (TAC) 

chargeable for the transportation services or direct use 

of a commercial carrier by providing the paying 

activity's carriers account number or a pre-paid return 

shipping label." 

DLA has been notified of this issue. 

At this time, there is no change to the 

formatted content of the SDR. A 

separate change may be considered in 

the future. 

7. GSA Under this PDC would customers be expecting GSA to 

provide carrier information and carrier account 

number?

Normal procedure for us under these circumstances 

This is only for materiel in a DLA 

Distribution Center; not for materiel 

shipped directly to a customer.

The new procedure will not be 
Attachment, ADC 1164

Page 7

Originator Response/Comment Disposition

would be a call tag from UPS or FedEx provided by 

the vendor. In some cases for larger shipments a bill of 

lading to a carrier may be issued by the vendor. 

Not sure that our vendors would be comfortable with 

releasing their UPS/FedEx account numbers. 

mandatory; it is optional if the vendor 

agrees to pay for transportation of the 

return shipment and provides the 

account number.

8. US 

TRANSCOM

After review and coordination, USTRANSCOM 

provides the following comments to the subject PDC:

REF: Enclosure 2, DLMS Implementation 

Conventions (ICs) Revision, Change Table for 940R 

Materiel Release, Line Item #3.

The proposed DLMS Note #2 reads: "The carrier is 

identified by name (N102) and Standard Carrier Alpha 

Code (SCAC) (N103), when available." This is 

incorrect, the carrier SCAC is passed in the N104 and 

qualified with the code value '2' in the N103 (see line 

item #5). Additionally, recommend requirement for 

DLMS usage note at 2/N104/1100 indicating that this 

is the actual SCAC.

RER: Enclosure 2, DLMS Implementation 

Conventions (ICs) Revision, Change Table for 945A 

Materiel Release Advice, Line Item #3

The proposed DLMS Note #2 reads: "The carrier is 

identified by Standard Carrier Alpha Code (SCAC) in 

N103. The carrier name is identified in N102". This is 

incorrect, the carrier SCAC is passed in the N104 and 

qualified with the code value '2' in the N103

Assuming that the following corrections are made, 

USTRANSCOM will vote 'approved' on the subject 

PDC.

Noted.

IC notes have been updated.

9. DLA 

Transaction 

Services

Have a question for PDC 1164, 10. Impact; c. 

Automated Information System

(AIS); d. DLA Transaction Services; (2) The carrier 

account number must be protected so it is not visible to 

outside parties. It should not be displayed in Web 

Visual Logistics Information Processing System 

(WebVLIPS).

Does this include LDG? Will the data need to be 

suppressed in LDG.? If so this will take some time to 

program, WEBVLIPS will not make any changes to 

display the data, so no issue there; LDG will need to 

set up some rules when dealing with the data.

No external copies should include the 

account number; it should only go to the 

storage activity to which the release 

order is directed (or to the ICP to which 

the release confirmation is directed).

It is acceptable for the carrier 

information to be retained for the 

historical transaction retained in 

Logistics Data Gateway (LDG).
Enclosure 1, ADC 1164

Page 1

Enclosure 1, DLM Volume 2 Revisions

Changes are identified by bold red italics and strike-through text.

A. Revise Chapter 4, Requisitioning, as follows:

C4.7.14. Preparing MROs

C4.7.14.1. Originator. MROs, DLMS 940R, Materiel Release, are prepared by the source of 

supply as a result of processing requisitions against inventory records and determining that materiel is 

available. MROs are used as a directive for release and shipment of materiel from stock. 

C4.7.14.1.1 MROs directing shipment of requisitioned GFM will perpetuate contract 

data to include the contract number authorizing GFP, and the call/order and CLIN when available. 

Contract data will be provided by the source of supply for pushed GFM not initiated by a requisition.

C4.7.14.1.2. MROs directing shipment of reparables for induction for commercial 

maintenance will include the contract number authorizing GFP, and the call/order and CLIN when 

available.

C4.7.14.1.3. MROs directing shipment of GFP in contractor custody will include the 

contract number authorizing GFP, and the call/order and CLIN when available.

C4.7.14.1.4. MROs directing return of discrepant/deficient materiel to vendors at 

vendor expense will include identification of the carrier and the carrier account number.

B. Revise Chapter 17, Supply Discrepancy Reporting, as follows:

C17.3.12.4. Disposition of Materiel. Use the SDR response as an action reply for those 

discrepant conditions requiring disposition instructions to the reporting activity, e.g., overages, 

damages (USPS), deficient materiel (Security Assistance), or erroneous or misdirected materiel.

C17.3.12.4.1. Returning Discrepant Materiel Customer Returns. When discrepant 

materiel is directed to be returned, the responsible activity will direct the customer to reship the 

materiel using the same document number under which the materiel was originally shipped. The SDR 

reply will include the date by which the customer is requested to return the materiel to the designated 

location. The ICP will require expedited return where appropriate, such as FMS classified/sensitive 

item returns, and overage returns for back-ordered materiel not available within another customer’s 

required delivery date. The return-to location will be identified by DoDAAC or CAGE (contractors 

where no DoDAAC is assigned). Clear text addresses may be included in addition to the coded 

address since all customers may not have access to the authoritative address source. The SoS will 

provide reimbursement for packing, crating, handling, and transportation for directed returns under 

MILSBILLS procedures in DLM 4000.25, Volume 4, Finance, procedures and use of the Defense 

Transportation System (DTS) for the return movement is encouraged except where use of a designated 

commercial carrier is more cost effective/efficient or transportation cost will be borne by another

party (e.g., a vendor for return of nonconforming materiel). As an alternative to providing 

transportation reimbursement, the responsible action activity may provide the transportation account 

code (TAC) chargeable for the transportation services or direct use of a commercial carrier by 

providing the paying activity’s carriers account number or a pre-paid return shipping label. and 

supporting information, e.g., the bill of lading number, or small package carrier account information. 
Enclosure 1, ADC 1164

Page 2

In those cases were an exhibit of the discrepant materiel is directed for return, the activity requesting 

this action will pay for exhibit shipment costs. Action activities will either furnish DD Form 1348-1A 

for materiel to be returned or provide comparable information to accomplish the return. A copy of the 

SDR and the shipment document will be included with returned materiel and annotated as an “SDR 

RETURN.” When discrepant materiel is directed for return to a contractor, a hard-copy SDR 

including disposition instructions will be included with the shipment. No statement adversely affecting 

the Government's claim will be shown on any documentation returned to the contractor. For nonSecurity Assistance customers, materiel not returned as directed within 90 calendar days (if CONUS)

or 120 days (if OCONUS) of the SDR reply will be billed.

C17.3.12.4.2. DLA Distribution Center Returns and Transfers to DLA Disposition 

Services. SDR disposition instructions to DLA disposition centers may direct disposal or shipment 

of discrepant/deficient materiel to another location (e.g., return to a vendor) using the appropriate 

SDR reply code. This type of SDR disposition must be provided concurrent to transmission of the

DLMS 940R Materiel Release Order in accordance with MILSTRIP procedures in DLM Volume 2

for clear audit history for inventory reporting. The DLMS MRO supports discrete identification of 

the carrier and the carrier account number to allow systemic recognition of this information and 

ensure the appropriate party is charged for the transportation of the nonconforming materiel.

1

 1 Refer to ADC 1164
Enclosure 2, ADC 1164

Page 1

Enclosure 2, DLM Volume 3 Revisions

Revise Chapter 2, Retail Supply and Transportation Interchange – Stock Shipments to insert new 

subparagraph C2.3.2.1.5. and renumber the existing paragraph. Changes are identified by bold red 

italics.

C2.3.2.1. Pre-Positioned Release Order. For designated supply trading partners, the 

Defense Automatic Addressing System (DAAS) will transmit copies of the DLMS 940R, Materiel 

Release Order/Disposal Release Order/Redistribution Order (Document Identifier Codes (DIC) 

A2_/A5_/A4_) transactions to the designated transportation system to be pre-positioned awaiting 

actual arrival of cargo from the supply warehouse.

(Intervening text not shown)

C2.3.2.1.5. When authorized by the trading partners, the materiel release may 

include identification of a pre-designated carrier and the carrier account number for the applicable 

shipment. When provided, this information will be perpetuated to the materiel release 

confirmation.2

 2 Refer to ADC 1164
Enclosure 3, ADC 1164

Page 1

Enclosure 3, DLMS Implementation Conventions (ICs) Revisions

# Location Change Table for 

940R Materiel Release

Reason

1. DLMS 

Introductory 

Note

Add ADC 1164 to DLMS Introductory note: 

- ADC 1164, Revise DLMS 940R Materiel Release Order 

(MRO) and DLMS 945A Materiel Release Confirmation 

for Carrier Account Data Associated with Directed Return 

of Discrepant/Deficient Materiel and Procedures for use of 

the DLMS 940R when Directing Shipment of 

Discrepant/Deficient Materiel via Supply Discrepancy 

Report (SDR) Reply

To identify DLMS 

changes included in the 

DLMS.

2. 2/N901/0400 Add Code QJ and associated DLMS notes:

QJ Return Material Authorization Number

DLMS Note:

1. Used to identify the paying activity’s carrier account 

number applicable to the identified carrier (2/N101/1100 

Code CA) for the directed materiel release. (Field length = 

10 positions). Refer to ADC 1164.

2. Authorized DLMS enhancement; see DLMS introductory 

note 4f.

Supports new 

requirement for carrier 

account number 

3. 2/N101/1100 Add Code CA and associated DLMS notes:

CA Carrier

DLMS Note:

1. Use as needed for directed returns to identify the carrier 

to be used for the return shipment. Refer to ADC 1164.

2. The carrier is identified by name (N102) and Standard 

Carrier Alpha Code (SCAC) using Code 2 (N103), when 

available.

3. Authorized DLMS enhancement; see DLMS 

introductory note 4f.

Supports new 

requirement for carrier 

identification.

4. 2/N102/1100 Add new DLMS Note5 (existing notes not shown):

Name

DLMS Note: 

Use with N101 Code CA to identify the carrier by name. 

(Field length for DLMS is 60 positions.)

Supports new 

requirement for carrier 

identification.

5. 2/N103/1100 Add Code 2 and associated DLMS Note:

2 Standard Carrier Alpha Code (SCAC)

DLMS Note: Use with N101 Code CA to identify the 

commercial carrier by code. Identify the value of the SCAC 

in N104.

Supports new 

requirement for carrier 

identification.
Enclosure 3, ADC 1164

Page 2

# Location Change Table for 

945A Materiel Release Advice

(Version 4010 with comparable changes to Version 4030;

location in table below correlates to Version 4010)

Reason

1. DLMS 

Introductory 

Note

Add ADC 1164 to DLMS Introductory note: 

- ADC 1164, Revise DLMS 940R Materiel Release Order 

(MRO) and DLMS 945A Materiel Release Confirmation 

for Carrier Account Data Associated with Directed Return 

of Discrepant/Deficient Materiel and Procedures for use of 

the DLMS 940R when Directing Shipment of 

Discrepant/Deficient Materiel via Supply Discrepancy 

Report (SDR) Reply

To identify DLMS 

changes included in the 

DLMS.

2. 2/N901/40 Add Code QJ and associated DLMS Notes:

QJ Return Material Authorization Number

DLMS Note:

1. Used to identify the carrier account number applicable to 

the identified carrier (2/N101/80 Code CA) for the directed 

materiel release. (Field length = 10 positions). Refer to 

ADC 1164.

2. Authorized DLMS enhancement; see DLMS 

introductory note 4e. 

Supports new 

requirement for carrier 

account number.

3. 2/N101/80 Revise DLMS Notes for existing Code CA:

CA Carrier

DLMS Note:

1. Use for materiel release confirmations, historical materiel 

release confirmations, disposal release confirmations, and 

historical disposal release confirmations to identify the 

shipment unit carrier when other than the United States 

Postal Service.

2. The carrier shall be is identified by Standard Carrier Alpha 

Code (SCAC) using Code CA in N103. The carrier name is 

optional and may be identified in N102.

3. Perpetuate from the materiel release order to confirm 

use of the carrier designated for directed return to a 

vendor. Refer to ADC 1164.

4. Authorized DLMS migration enhancement; see 

introductory DLMS 4ef.

Clarification.
Enclosure 3, ADC 1164

Page 3

4. 2/N102/80 Revise DLMS Note 1 for existing data field:

Name

DLMS Note: 

1. May be used Use to identify the carrier name (used with 

Qualifier CA, above). Field length for DLMS is 60 

positions. 

Clarification.

5. 2/N103/80 Move Federal Note to DLMS Note level for existing Code 2:

2 Standard Carrier Alpha Code (SCAC)

Federal Note:

DLMS Note:

1. Use as needed with N101 Code CA to identify the 

commercial carrier by code. Identify the value of the SCAC 

in N104.

2. Authorized DLMS migration enhancement; see 

introductory DLMS 4e.

Removes Federal note 

from DLMS IC.