DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

May 03, 2016

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

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

Intra-Air Force Use of Ship-From DoD Activity Address Code (DoDAAC) in DLMS 

527R Receipt Transactions for Intra-Air Force Shipments (Supply/MILSTRAP)

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

DLM 40000.25-2, Military Standard Transaction Reporting and Accountability Procedures 

(MILSTRAP), is approved. The intra-Air Force target implementation date is June 2016.

Addressees may direct questions to Ms. Mary Jane Johnson, email: 

Mary.Jane.Johnson@dla.mil; or Mr. Rafael Gonzalez, email: Rafael.Gonzalez@dla.mil.

Others may direct questions to their Service or Agency designated Supply PRC representative 

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

 

 

DONALD C. PIPP

Director

Defense Logistics Management 

Standards Office

Attachment

As stated 

cc: 

ODASD (SCI)
Attachment, ADC 1185

Page 1

ADC 1185

Intra-Air Force Use of Ship-From DoDAAC in DLMS 527R Receipt 

Transactions for Intra-Air Force Shipments 

 1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Primary POC: Peter Talamonti, AFMC AFLCMC/HIAR DSN 596-2012 / 

(334) 416-2012, email: peter.talamonti.ctr@us.af.mil

b. Alternate POC: Todd Landuyt, AFMC AFLCMC/HIAR DSN 596-5023/

(334) 416-5023. Email: todd.landuyt.1.ctr@us.af.milailto:

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Intra-Air Force Supply (Retail/Wholesale)

b. Primary/Secondary Functional Process: Supply Chain Visibility and 

Accountability

3. REFERENCES:

a. DLM 4000.25-2, Military Standard Transaction Reporting and Accountability 

Procedures (MILSTRAP), Appendix 3.2 Materiel Receipt – Other than Procurement 

Instrument Source 

b. DLM 4000.25, Defense Logistics Management Standards (DLMS), DLMS 527R

Receipt

4. APPROVED CHANGE(S):

a. Brief Overview of Change: This change documents intra-Air Force use of the 

Ship-From DoDAAC in MILSTRAP (Reference 3.a.) legacy Document Identifier Code 

(DIC) D6_ Receipt and the DLMS (Reference 3.b.) 527R Receipt transactions.

b. Background:

(1) Air Force Supply Chain Management is in the process of overhauling intransit requirements. To accomplish this, the Air Force is enhancing its ability to track the 

intra-Air Force movement of serviceable and unserviceable materiel. The Air Force retail 

supply system, Integrated Logistics Solution-Supply (ILS-S), creates the MILSTRAP legacy 

DIC D6_ and transforms those into DLMS 527R Receipt transactions for consumption by 

D035 AF wholesale supply system. As part of the wholesale and retail supply in-transit 

visibility requirement, ILS-S will send real-time transactions through Transaction Services to 

Air Force wholesale systems. The MILSTRAP legacy transactions are as follows: DICs D4_, 

D6_, D7_, D8_, D9_ and DAC. The Air Force wholesale system is currently making changes 

to its in-transit tracking software. To fully support the Air Force in-transit visibility initiative, 

the Air Force wholesale system requires the additional information of the shipping activity to 
Attachment, ADC 1185

Page 2

close the loop of the shipments being sent and received. The shipping activity DoDAAC 

provides the wholesale system an increased capability to track receipt of shipments to Air 

Force bases.

(2) Most MILSTRAP transactions contain multi-use data fields for use on an 

intra-Component basis for data prescribed by the Component. DLMSO has no visibility of 

how these fields are used until such time as a DOD Component documents its intra-Component 

use in a DLMS Change, for use of the data in the corresponding DLMS transaction. This 

change addresses one of these MILSTRAP legacy multi-use fields.

c. Approved Change in Detail:

(1) This change documents intra-Air Force use of the Ship-From DoDAAC in 

MILSTRAP legacy DIC D6_ Receipt transaction multi-use field provided for intraComponent data (record position (rp) 60-65), for transactions originating from Air Force 

ILS-S. Per MILSTRAP, Appendix 3.2 Materiel Receipt, rp 60-66 is available on an intraComponent basis, for data prescribed by the Component.

(2) This change also modifies the corresponding DLMS 527R Receipt 

transaction to document Air Force use of the existing 527R qualifier (2/N101/210/[Code CIConsignor] with 2/N103/210/[Code 10-DoDAAC]). The 2/N101/210 qualifier CI is used 

for the Ship-From in the 527R Receipt transaction.

d. Revisions to DLM 4000.25 Manuals:

(1) Revise DLMS 527R Receipt, as shown in Enclosure 1. 

(2) Revise DLM 4000.25-2, MILSTRAP, Appendix 3.2, DIC D6_, as 

shown in Enclosure 2.

5. REASON FOR CHANGE: To support Air Force in-transit visibility initiative. Using 

the Ship-From DoDAAC provides the Air Force wholesale system an increased capability 

to track receipt of shipments to Air Force bases. 

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Intra-Air Force use of the Ship-From DoDAAC in the Receipt 

transaction provides the Air Force wholesale system an increased capability to track Air 

Force receipt of shipments to Air Force bases. 

b. Disadvantages: None.

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Intra- Air Force

target implementation date is June 2016. 
Attachment, ADC 1185

Page 3

8. IMPACT: 

a. New DLMS Data Elements: There are no new DLMS data elements.

b. Changes to DLMS Data Elements: Modifies DLMS 527R Receipt 

transactions to document intra-Air Force use of existing qualifier for Ship-From data in 

527R Receipt, used with existing DoDAAC qualifier. The Ship-From is identified in 

527R Receipt using 2/N101/210/Code CI. Modifies MILSTRAP legacy D6_ Receipt to 

document intra-Air Force use of Ship-From DODAAC in a DIC D6_ multi-use field.

c. Automated Information Systems (AIS): This ADC applies to the Air Force 

only. Other DOD Components who may want to take advantage of this capability in 

DLMS transactions should provide feedback to DLMSO in response to this ADC.

d. Transaction Services: Update mapping to recognize Air Force use of Ship-From 

DoDAAC in DLMS 527R and MILSTRAP legacy DIC D6_ as documented in this change.

e. Non-DLM 4000.25 Series Publications: The Air Force must update their 

Component-level publications as needed.

9. PDC 1185 Response Table:

Enclosures

Component Component Responses Received DLMSO Response

Air Force Concurs without comment. Noted.

Navy Concur without comment. Noted.

DLA Concur without comment. No intent to use this at DLA. Noted.

USTRANSCOM Abstains Noted.
Enclosure 1, ADC 1185

Page 1

ENCLOSURE 1 to ADC 1185

Intra-Air Force Use of Ship-From DoDAAC in DLMS 527R Receipt Transactions for Intra-Air 

Force Shipments (Supply/MILSTRAP)

# Location Revisions to DLMS 527R Receipt Reason

1. DLMS 

Introductory 

Note

Add ADC 1185 to DLMS Introductory Note X:

ADC 1185, Intra-Air Force Use of Ship-From DoD Activity 

Address Code (DoDAAC) in DLMS 527R Receipt 

Transactions for Intra-Air Force Shipments 

(Supply/MILSTRAP)

Identifies DLMS 

Changes included in 

the DS

2. 2/N101/210 Add new DLMS Note 3 to existing code CI Consignor:

CI Consignor

DLMS Note:

1. Use in Navy Commercial Asset Visibility (CAV) receipts 

to identify the organization shipping the materiel. 

Authorized DLMS migration enhancement. See introductory 

DLMS note 5g.

2. Use in “not from due” receipts to identify the organization 

shipping the materiel. DLMS enhancement. See introductory 

DLMS note 5a.

3. For intra-Air Force use in Air Force retail receipts of 

shipments from Air Force retail activities to identify the 

DoDAAC of the shipping activity (the Ship-From 

DoDAAC). Authorized DLMS migration enhancement for 

intra-Air Force use. See introductory DLMS note 5.g. 

Refer to ADC 1185. 

Identifies intra-Air 

Force requirement.

3. 2/N103/210 Add new DLMS Note 5 to existing Code 10 DoDAAC:

10 Department of Defense Activity Address Code 

(DODAAC)

DLMS Note:

1. DLMS enhancement; see introductory DLMS note 5a.

2. CAV uses for receipts in conjunction with N101 codes Z4 and 

ZD.

3. Authorized DLMS enhancement for Inter-Service Ammunition 

use with N101 code RC to identify consignee DODAAC (DIC 

BG1/BG2 rp 66-71). (Refer to ADC 261 and ADC 445.

4. DLA Disposition Services Field Office uses in the TRA 

transaction with N101 code ZD.

5. Authorized for intra-Air Force use with N101 Code CI to 

identify the Ship-From DoDAAC. See introductory DLMS 

note 5g. Refer to ADC 1185.

Documents intra-Air 

Force requirement.
DLM 4000.25-2

Change xx

Enclosure 2, ADC 1185

Page 1

ENCLOSURE 2 TO ADC 1185

Intra-Air Force Use of Ship From DoDAAC in DLMS 527R Receipt for Intra-Air Force Shipments 

DLMS 527R Receipt Change table, Changes identified by bold red italics or double strikethrough.

AP3.2. APPENDIX 3.2

MATERIEL RECEIPT – OTHER THAN

PROCUREMENT INSTRUMENT SOURCE

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier 

Code

1-3 Enter appropriate DIC from the D6 series.

Routing Identifier 

Code (TO)

4-6 Enter (or perpetuate) the RIC of the Inventory 

Control Point to which this transaction is 

being forwarded.

Blank 7 Leave blank.1

Stock or Part Number 8-22 Enter stock or part number of item received.

Unit of Issue 23-24 Enter UI of item.

Quantity (Received) 25-29 Enter quantity received, preceding significant 

digits with zeros. 2, 3

Document Number 30-43 Enter controlling document number.

Suffix 44 Enter consecutive alpha codes A through Z 

when assignments of suffix codes are 

necessary.4

Supplementary 

Address

45-50 Enter (or perpetuate) SUPADD; otherwise, 

leave blank.

Signal 51 Enter (or perpetuate) the signal code; 

otherwise, leave blank.

 1 Navy uses rp 7 for Navy Materiel Turned Into Store (MTIS) indicator ‘S’. The MTIS indicator identifies and 

allows completion of a receipt that was initiated through a unique MTIS Interface between DSS and Navy 

Uniform Automated Data Processing System (UADPS) II (U2). Navy use is documented in MILSTRAP for 

mapping purposes for conversion to DLMS in a mixed DLSS/DLMS environment. (Refer to ADC 246.See PDC 

249). 2 See Appendix AP3 - Formats Introduction, AP3.3.1. 3 See Appendix AP3 - Formats Introduction, AP3.3.2. 4 See Appendix AP3 - Formats Introduction, AP3.3.3.
DLM 4000.25-2

Change xx

Enclosure 2, ADC 1185

Page 2

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Fund 52-53 Enter (or perpetuate) fund code; otherwise, 

leave blank.

Distribution 54-56 Enter (or perpetuate) distribution code; 

otherwise, leave blank.

Project 57-59 Enter (or perpetuate) project code; otherwise, 

leave blank.

Dual-Use

Multi-Use

or

DSS Operations 

Control Number 

(OCN)

60-66

(60-66)

(60-66)

For intra-DoD ComponentService use, enter 

data prescribed by DoD Component.

5, 6, 7, 7

For inter-DoD Component use, and intra-DLA 

use, DLA storage activities will enter the DSS 

OCN; otherwise, leave blank8.

Routing Identifier 

Code (Receiving 

Location)

67-69 Enter (or perpetuate) the RIC identifying 

activity at which item is received, if available; 

otherwise, leave blank.

Ownership/Purpose 70 Enter ownership/purpose code.

Supply Condition 71 Enter supply condition code of item received.

Management 72 Enter management code; otherwise leave 

blank.

Day of Year

(Released by Carrier)

73-75 Enter ordinal day of the calendar year that 

materiel was released by carrier.9

Multiuse 76-80 For intra-Component use, enter data 

prescribed by Component. For interComponent use, leave blank.

10, 11

 5 For intra-Army use, rp 60-61 identifies the priority designator. (SeeRefer to ADC 234.) 6 For intra-Army use, rp 65-66 identifies the advice code. (SeeRefer to ADC 234.) 7 Priority designator is identified in Army Regulation (AR) for intra-Army use in rp 60-61. Staffing Note: Administrative 

deletion of footnote 7 as duplicate of footnote 5. 7 For intra-Air Force use, rp 60-65 identifies the Ship-From DoDAAC for use in Air Force retail receipts of shipments 

from Air Force retail activities . (Refer to ADC 1185.) 8 SeeRefer to ADC 218. 9 On an intra-Army basis, Army sometimes uses D6X for their Direct Support/Reparable Exchange process by citing 

X in rp 73 with rp 74-75 blank. This is a temporary deviation from standard processing in place until 

implementation of Army Exchange Pricing (estimated to be April 2009). (SeeRefer to ADC 267.) 10 For Navy CAV-ORM DIC D6K, rp 76-78 identifies the Shipper RIC. 11 For intra-Army use only, rp 80 identifies the discrepancy indicator code (see appendix AP2.17). (SeeRefer to ADC 

272.)