DEFENSE LOGISTICS AGENCY

HEADQUARTERS

8725 JOHN J. KINGMAN ROAD, SUITE 2533

FT. BELVOIR, VIRGINIA 22060-622 1

IN REPLY

REFER TO DLMSO

JAN 1 6 20~

MEMORANDUM FOR: SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

SUBJECT: ADC DLMS Change 88, DLMS Mapping for MILSTRIP Document Identifier (DI)

Code AFT, Request for Shipment Tracing on Registered Insured, and Certified

Parcel Post (Supply) (Staffed as PDC 94)

The attached change to DOD 4000.25-M, Defense Logistics Management System (DLMS), is

approved for implementation. This change is required to support continued operations in a

DT.MS/DT,SS/~l,SS-like environment. The updated TIT,MS S1Ipplement will he posted to the

DLMSO web site (http://www.dla.mil/j-6/dlmso/ICs/Default.htm) within 30 days from the above date

for implementation planning. DLMSO will concurrently pursue coordination/approval with the DOD

Logistics Functional Working Group, the DOD Electronic Data Intcrchangc Standards Management

Committee (EDISMC), and the Federal ED1 Standards Management Coordinating Committee

(FESMCC) for Federal implementation conventions (IC) revisions.

The attached change to DLMS will be incorporated into the DLMS manual/supplement, based

upon the effective or availability date to be determined. NOTE: DAAS and DLA have advance

authorization to employ these procedures under Business Systems Modernization (BSM); however,

configuration management/version control procedures must be observed allowing for sequential

implementation to prevent rejection.

Addressees may direct questions to the DLMSO points of contact, Ms. Ellen Hilert, Chair,

Supply Process Review Committee, 703-767-0676, DSN 427-0676, or e-mail:

ellen~hilert@hq.dla.mil or Ms. Vermella SavBge, DOD MILSTRIP System Administrator,

703-767-0674, DSN 427-0674, or e-mail: vermella-savage@hq.dla.mil. Others must contact their

Component designated representative.

lie birector / /

_ ’ Defense Logistics Management

Standards Office

Attachment

cc:

AUUSU(L)YCl

LMI
1

ADUSD(L)SCI

LMI
1

Approved DLMS Change 88

DLMS Mapping for MILSTRIP DI Code AFT, Request for Shipment Tracing 

on Registered, Insured, and Certified Parcel Post

1. ORIGINATOR:

a. Service/Agency: Defense Logistics Agency

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

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

2. FUNCTIONAL AREA: Primary: Supply

3. REFERENCE: MILSTRIP

4. REQUESTED CHANGE:

a. Title: DLMS Mapping for MILSTRIP DI Code AFT, Request for Shipment Tracing on 

Registered, Insured, and Certified Parcel Post

b. Description of Change: This change incorporates the functionality of the MILSTRIP DI Code 

AFT in the DLMS. All data contents and associated procedures are the same as described in MILSTRIP. 

Refer to MILSTRIP paragraph C3.42, Shipment Tracing, and appendix AP3.46.

c. Procedures: 

Add the following codes/notes to the 869A, Requisition Inquiry/Supply Assistance:

# Location Revision Reason Federal IC

1 Introductory 

Notes 

Modify Note 1 to add additional sentence:

Organizations may also use this transaction to request shipment 

tracing on registered, insured, and certified parcel post.

Provides note 

identifying 

additional 

functionality.

Federal IC 

revision 

required.

2 Introductory 

DLMS Notes

Add new DLMS note 2e:

e. Repetition of data (using multiple iterations or loops) which is 

not compatible with existing DLSS capability. Although supported 

by the use of the ANSI X12 standard, such data is not compatible 

with DLSS/DLMS conversion and may not be supported by the 

recipient's automated processing system. Components must 

coordinate implementation of enhanced capability with DLMSO 

prior to use.

Update to stay 

consistent with all 

DLMS 

Supplements.

No Federal 

change 

required
2

3 Introductory 

DLMS Notes

Revise DLMS note 5, along with adding titles, of applicable 

PDC/ADCs :

This revision to DLMS Supplement (DS) incorporates Proposed 

DLMS Change (PDC) and Approved DLMS Changes (ADCs) 

listed. PDCs/ADCs are available from the DLMSO website: 

http://www.dla.mil/j-6/dlmso/Changes.

--PDC 94, DLMS Mapping for MILSTRIP DI Code AFT, 

Request for Shipment Tracing on Registered, Insured, and Certified 

Parcel Post

-ADC 50, Revision to DLMS Supplement (DS) 869A, Requisition 

Inquiry/Supply Assistance Request

-ADC 76, Air Force Unique Management Coding for

NMCS/MICAP

-ADC 77, Air Force Unique Management Coding for Materiel 

Management Aggregation Code (MMAC) 

Delete Introductory DLMS note 4.

Update to stay 

consistent with all 

DLMS 

Supplements.

No Federal 

Change 

Required 

4 1/BSI03/20 Add note and new code:

PI Selected Orders - Shipped Items

DLMS Note: Use to indicate that the transaction set contains 

transactions that apply to requisitions for which shipment status 

has been received.

Distinguishes 

applicable 

transactions

Federal IC 

revision

required

5 1/BSI08/20 Add note and new code:

71 Filing and Search Request

DLMS Note: Use to identify requests for shipment tracing.

Distinguishes 

applicable 

transactions

Federal IC 

revision 

required

6 2/DTM01/30 Open segment.

Add note and new code:

168 Release

DLMS Note: Use for requests for shipment tracing to identify the 

date materiel was released to the carrier.

Required entry on 

MILSTRIP AFT

Federal IC 

revision 

required

7 2/QTY/80 Modify Federal QTY Segment note:

Federal Note:

Must use in 2/HL/010 transaction loops to identify the applicable

quantity of material requisitioned.

Clarification Federal IC 

revision 

required.

8 2/QTY01/80 Modify Federal note:

01 Discrete Quantity

Federal Note: Use to indicate the quantity requisitioned. Use to 

indicate the quantity shipped when requesting shipment tracing.

Clarification Federal IC 

revision 

required.
3

9 2/QTY01/80 Add DLMS note 2:

DLMS Note: 2. Use in requests for shipment tracing to indicate 

the quantity released to carrier.

Clarification No Federal 

change 

required

10 2/QTY03/80 Modify Federal note:

Unit or Basis for Measurement Code

Federal Note: Use to identify the unit of issue for the material 

requisitioned. 

Clarification Federal IC 

revision 

required

11 2/REF01/105 Insert new data element note 2 and renumber accordingly.

2. For requests for shipment tracing, use the material identification 

provided in the shipment status.

Clarification. No Federal IC 

change

12 2/REF01/105 Add note and new code:

TG Transportation Control Number (TCN)

DLMS Note: Use in transaction reference number loop to identify 

the shipment unit TCN.

Required entry on 

MILSTRIP AFT

Federal IC 

revision 

recommended 

for 

consistency.

13 2/N101/110 Modify DLMS note:

Z8 Last Known Source of Supply

DLMS Note: Use to identify the supply source to receive the 

transaction set. 

Add note and new code:

CI Consignor

DLMS Note: Use to identify the party to receive a request for 

shipment tracing.

GP Gateway Provider

DLMS Note: Use to identify the Defense Automatic Addressing 

System Center (DAASC).

New generic 

qualifier for 

consignor added 

because the 

intended recipient 

may include 

various different 

types of activities, 

e.g., the 

ICP/IMM, the 

depot, or DVD 

contractor, etc.

No Federal IC 

change

Federal IC 

revision 

recommended 

for 

consistency
4

14 2/N106/110 Add new DLMS note:

FR Message From

DLMS Note: For DLMS requests for shipment tracing resulting 

from conversion of the original DLSS DI Code AFT, the originating 

activity will be identified as DAASC.

The MILSTRIP 

AFT is generally 

submitted by the 

consignee. For 

Security 

Assistance, the 

ILCO may submit. 

There is no actual 

field to identify 

the submitter on 

the MILSTRIP 

AFT, however, 

the DLMS 

transaction 

equivalent requires 

identification of 

the submitter.

No Federal IC 

change.

15 2/LQ01/180 Add note and new code:

39 Transportation Mode or Method Code

DLMS Note: Use in requests for shipment tracing to identify the 

mode of shipment.

Required entry on 

MILSTRIP AFT

Federal IC 

revision 

recommended 

for 

consistency

16

2/LQ01/180 Revise DLMS notes for qualifier “A9” to read: 

 

1. Use to identify supplemental address/data.

2. During the DLSS/DLMS transition, this field will be used to 

perpetuate/populate the DLSS Supplementary Address (SUPAAD) 

field. During this time, field size is restricted to 6 positions; see 

introductory DLMS note 2d.

3. Expanded use of this field for supplemental data without size 

restriction is a DLMS enhancement; see introductory DLMS note 

2a.

4. Under full DLMS, the requirement to pass activity address 

information within the supplement data field will be streamlined. 

Activity address data previously contained in the SUPAAD will be 

reflected exclusively in the N1 segment. Future streamlined data; see 

introductory DLMS note 2c.

Update to stay 

consistent with all 

DLMS 

Supplements.

No change 

required
5

17

2/LQ01/180 Add qualifier GQ and the following notes:

Federal Note: Use to identify the Materiel Management 

Aggregation Code (MMAC).

DLMS Note: Use to identify the MMAC for NSNs to be managed 

by a specific manager (i.e., system, program, aggregation, selected 

FSC, technology group).This is an Air Force unique data element, 

meaningful to the Air Force only. Non-Air Force Components 

perpetuate without action. An ANSI data maintenance request has 

been prepared to request a new data element 1270 code qualifier 

assignment for the MMAC. The code source is identified as the Air 

Force Manual (AFMAN) 23-110, Volume 1.

This qualifier 

addition is a 

primary data 

element for Air 

Force requisition 

processing. (see 

ADC 77)

Federal 

change 

required

18

2/LQ01/180 Add qualifier RC and the following notes:

Federal Note: Use to identify the Air Force Urgency Justification 

Code indicating the urgency of need and type of requirement 

(justification) related to a Not Mission Capable Supply/Mission 

Impaired Capability Awaiting Parts (NMCS/MICAP) condition.

DLMS Note: Use in conjunction with Special Requirements Code 

N (2/LQ01/Code AL or perpetuated from DLSS Required Delivery 

Date field). This is an Air Force-unique data element, meaningful to 

the Air Force only. Non-Air Force Components perpetuate without 

action. An ANSI data maintenance request has been prepared to 

request a new data element 1270 code qualifier assignment for the 

Urgency Justification Code. The code source is identified as the Air 

Force Manual (AFMAN) 23-110, Volumes 1 and 2.

This qualifier 

addition is a 

primary data 

element for Air 

Force requisition 

processing. (see 

ADC 76)

Federal

change 

required

19

2/LQ01/180 Revise DLMS notes 2 and 3 for qualifier “AL” to read:

2. DLMS enhancement, see introductory DLMS note 2a.

3. Use in conjunction with 2/LQ01/Code RC, Requirement Code, to 

complete the Air Force unique NMCS/MICAP data requirement.

Clarification (see 

ADC 76)

No Federal 

change 

required

d. Alternatives: 

5. REASON FOR CHANGE: This change is provided to support continued operation in a mixed 

DLMS/DLSS environment. The MILSTRIP DI Code AFT was not included during DLMS concept 

development because the DLMS shipment status transaction was intended to provide all relevant

transportation numbers (including identifying numbers for registered, insured, and certified mail/parcel 

post) along with the DOD required TCN. The consignee would then have adequate information to initiate 

shipment tracing. Since DLMS implementation has not yet incorporated the additional transportation

numbers (even under BSM), there is a continued requirement for the AFT transaction asking depot or ICP 

to trace shipments via registered, insured, and certified mail/parcel post.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Supports DLMS implementation
6

b. Disadvantages: None identified

7. IMPACT:

a. Data Content/Procedures: Note that this revision requires opening of the 2/DTM/30 (currently 

not used in the 869A implementation convention or DS). The addition of a new segment may impact 

current users of the 869A (outside DLA) and implementation should be coordinated to preclude rejection.

b. Publication(s): DOD 4000.25-M, DLMS; Federal IC 869A and corresponding DS. All 

applicable revisions will be submitted to the EDISMC/Logistics Functional Work Group for 

coordination/approval. DAAS mapping and Component DLMS implementation are also impacted.

DLSS/DLMS Mapping Information

Request For Shipment Tracing On Registered, Insured, And Certified Parcel Post:

FIELD LEGEND RP(S)

MILSTRIP ENTRY 

AND INSTRUCTIONS

DLMS MAPPING 

INSTRUCTIONS

Document Identifier 1-3 Enter DI AFT. Beginning Segment Identification: 

BSI03, Code PI and BSI08, Code 71 

Filing and Search Request

2/LQ01/180, Code 0, Document 

Identification Code 

Routing Identifier 4-6 Enter RI (To), Consignor. N101, Code Z8, Last Known 

Source of Supply and N106, Code 

TO

Other Entries 7-80 Duplicate of DI AS_ or DI AU_ document 

received

See below.
7

Shipment Status (DI AS_ or DI AU_):

FIELD LEGEND RP (S)

MILSTRIP ENTRY 

AND INSTRUCTIONS

DLMS MAPPING 

INSTRUCTIONS

Media and Status 7 Use the M&S from the MRO/LRO/DRO or 

cancellation request.

2/LQ01/180, Code DF Media and 

Status

Stock or Part Number 8-22 Enter the NSN or part number of the item 

supplied.

2/LIN02/050, Code FS National 

Stock Number and 2/REF01/105, 

Code S6 Stock Number

Unit of Issue 23-24 Enter the U/I. 2/QTY03-C00101/080

Quantity 25-29 a. Enter the quantity shipped.

b. For ammunition FSG 13 items only, enter 

an “M” in rp 29 to express in thousands 

any quantity exceeding 99,999. Example:

Express a quantity of 1,950,000 as 1950M 

(1950 in rp 25-28 and an “M” in rp 29).

2/QTY02/080

Document Number 30-43 Use the document number from the 

MRO/LRO/DRO or cancellation request.

2/REF01/105, Code TN Transaction 

Reference Number

Suffix 44 Use suffix from the MRO/LRO/DRO or 

cancellation request. If no code, leave 

blank.

2/REF04/105, Code W8 Suffix

Supplementary Address 45-50 Use SUPADD from the MRO/DRO or 

cancellation request. The shipping activity 

will enter the DODAAC of the 

predesignated DRMO for shipments to 

DRMOs. If used as a DI AS6, enter the 

DODAAC of the activity to which the 

credit for the materiel and reimbursement 

for the PCH&T costs is to be provided.

2/LQ01/180, Code A9 Supplemental 

Data

Hold 51 If used as a DI AS6, enter Signal Code B. 

Otherwise, enter the shipment hold code, 

when applicable.

Not mapped

Fund 52-53 Enter fund as shown in the MRO/DRO or 

cancellation request. If used as a DI AS6, 

enter the fund code to which the credit for 

the materiel and reimbursement for the 

PCH&T costs is to be provided.

2/FA201/200, Code B5 Fund Code

Distribution 54-56 Enter the distribution as shown in the 

MRO/LRO/DRO or cancellation request.

2/LQ01/180, Code AK Distribution 

Code 

Release Date 57-59 Enter the date the materiel is released to the 

carrier.

2/DTM01/030, Code 168 Release

Transportation Control 

Number

60-76 Enter the shipment unit TCN as prescribed 

in DOD 4500.9-R.

2/REF01/105, Code TG 

Transporation Control Number 
8

FIELD LEGEND RP (S)

MILSTRIP ENTRY 

AND INSTRUCTIONS

DLMS MAPPING 

INSTRUCTIONS

Mode of Shipment 77 Enter the code identifying the mode of 

shipment. (See DOD 4500.9-R.) (Leave 

blank when transmitting DI AS3 through 

DAAS to DRMS.) 

2/LQ01/180, Code 39

Transportation Mode or Method 

Code 

Port of Embarkation 78-80 a. CONUS. Leave blank.

b. OCONUS:

(1) For shipments moving to OCONUS 

designations through the DTS, GBL/CBL, 

parcel post (except APO/FPO); and small 

package carrier shipments entering the DTS 

at the POE, enter the POE or SEAVAN CCP. 

(See DOD 4500.9-R, Part II, Appendices 

DD-4, DD-14, and EE-2.)

(2) Leave blank for parcel post movement 

through an APO or FPO.

(3) Enter the POE for SAP transactions 

moving through the DTS; otherwise, leave 

blank.

Not mapped

ENTRIES REQUIRED FOR DODAAC INFORMATION – DI ASY 

TRANSACTIONS1

Blank 57-64 Leave blank.

Status Code 65-66 Enter Status Code DY if the DI AFY followup transaction is being rejected; otherwise, 

leave blank.

Not mapped

Blank 67-74 Leave blank.

DODAAC of Initial 

Transportation Activity

75-80 Enter the DODAAC of the initial (origin) 

transportation shipping activity. If the DI 

AFY follow-up transaction is being rejected 

with Status Code DY, leave blank.

Not mapped

ENTRIES REQUIRED FOR SHIPMENTS TO DISPOSAL

Unit Price 62-68 Enter the unit price of the item identified in 

rp 8-22. Enter an estimated unit price if 

pricing information is not available. If the 

value for a part-numbered item exceeds the 

seven-position unit price field, enter the 

price manually on the DI AS3 shipment 

status transaction and forward off-line to 

the DRMS for manual processing.

Not mapped

Blank 69-76 Leave blank.