Page 1 Attachment, ADC 433 

ADC 433 

Requirements for Estimated Shipment Date in the DLMS Shipment Status (856S) 

Supporting the Estimated Shipment Date

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Technical POC: Pete Talamonti, Department of the Air Force, 754th ELSG/ILSS 

b. Functional POC: Olaf Mitchel, Department of the Air Force, 754th ELSG/ILSS 

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply 

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

Accountability 

3. REFERENCES:

a. DoD 4000.25-M, Defense Logistics Management System (DLMS), Volume 2, 

Chapter 5 

b. DoD 4000.25-1-M, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP), Appendix 3.19 

c. AFMAN 23-110 Air Force Supply Manual, Volume 2, Part 2, Chapter 15, Att15E-15. 

d. AFMAN 23-110 Air Force Supply Manual, Volume 3, Part 2, Chapter 18, Att 18C-1. 

e. DLA Logistics Management Standards Memorandum, subject: Approved Defense 

Logistics Management System (DLMS) Change (ADC) 411, Update Functionality for DLMS 

856S Shipment Status and DLMS 945A Material Release Advice, dated April 12, 2011. 

4. BACKGROUND:

a. Intent of the transaction: 

1) The purpose of this action is to provide DLA Disposition Services an 

estimated shipment date for items that are transferred to DLA Disposition Service Field Offices 

when the retail supply system does not automatically send the shipment status. 

2) DLA Disposition Services requires the shipment status transaction to create a 

due-in record within DAISY in order to process the receipt of the shipment. 

3) NOTE: Changes incorporated into this ADC, based on the staffing of PDC 

457, are highlighted in YELLOW. 

 
Page 2 Attachment, ADC 433 

b. Scenario for which the transaction is used: 

1) Integrated Logistics Support – Supply (ILS-S), which is the Air Force Retail 

Supply System, generates Document Identifier (DI) Code AS3 Supply Shipment Status 

transactions to provide shipment status for transfers to DLA Disposition Service Field Offices. 

AS3 transactions are usually automatically produced when the disposal transfer is processed by 

CMOS (Cargo Movement Operation System). This processing through CMOS also updates the 

Air Force’s retail supply system with transportation data. ILS-S has shipment suspense records 

that are automatically populated with transportation data sent from CMOS. 

 

 Figure 1 

2) The 945A Material Release Confirmation from CMOS is normally received 

by ILS-S. When ILS-S does not receive either the 945A or the Shipment Suspense Card (SSC) 

from CMOS within designated timeframes, ILS-S users may manually input the data. The user 

identifies this situation by ascertaining that the disposal transfer detail has not received shipment 

information and there is no shipment information available (e.g., it shows up on exception 

listing). When personnel in the Logistics Readiness Squadron (LRS)/transportation activity are 

certain that a shipment occurred on or about a given day but are unable to provide a 

Transportation Control Number (TCN), an asterisk (*) and estimated shipment date is entered on 

the SSC input to ILS-S. This is illustrated in figure 1 above by the dashed box. This manual 

processing is done to update the ILS-S shipment suspense records. 

3) Currently, the manual processing of the material release confirmation via the 

user inputting an SSC transaction results in the production of an AS3 with an estimated shipment 

date. This is the crux of this ADC. DLA Disposition Services requires an AS3 for each inbound 

shipment; thus ILS-S users must process shipment suspense updates manually when applicable. 

ILS-S needs to let DLA Disposition Services know that the date provided is only an estimated 

shipment date and there is no TCN and no shipment priority and no unit cost being provided on 

the MILS AS3 transaction. The resulting AS3 has an ‘*’ in position 60 and the estimated 

shipment date in positions 61-64 of the MILS legacy transaction. This is in accordance with 

ILS-S 

CMOS 

DLA 

Disposition 

Services 

Field 

Offices 

940R (CMOS)

945A (CMOS)

856S (AS3) SSC (Manual) 
Page 3 Attachment, ADC 433 

AFMAN 23-11- Air Force Supply Manual, Volume 3, Part 2, Chapter 18, Attachment 18C-1; 

however, this conflicts with DOD 4000.25-1-M, MILSTRIP. 

c. Procedures, transactions, data elements, processing details in use today: With the 

exception of the estimated shipment date in rp 61-64, the use of an “*”, and the missing unit 

price, the DI Code AS3 transaction that is generated by ILS-S is in IAW DoD 4000.25-1-M. 

1) The format of the ILS-S DI Code AS3 does not comply with the format 

provided in DOD 4000.25-1-M, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP), Appendix 3.19. This ADC addresses these differences. See figure 2 below that 

illustrates 3 AS3s. The data found after position 59 is different in each case. 

 12345678901234567980123456798012345678901234567890123456789012345678901234567890 

 1 2 3 4 5 6 7 

(1)AS3F01 1680015053906FREA00001FB480010120328ASYE364 901012*1012 

(2)AS3F01 1680015053906FREA00001FB480010120328ASYE364 901012150000999 J 

(3)AS3F01 1680015053906FREA00001FB480010120328ASYE364 901012 0000999 

(1) MILS – When AS3 results from user manual input of shipment suspense card input 

(2) MILS – When AS3 results from ILS-S processing CMOS 945A 

(3) MILS – Format as prescribed in DoD 4000.25-1-M 

 Figure 2 

2) Tables 1, 2, 3 below describe the data that is contained in each of the 3 AS3’s 

shown above. 

Pos Data Example Data 

60 Estimated Ship Date Indicator * 

61 - 64 Estimated Shipment Date 1012 (YDDD) 

65-80 Blank 

 Table 1 - When AS3 results from user manual input of shipment suspense card input 

 
Page 4 Attachment, ADC 433 

Pos Data Example Data 

60-61 Shipment Priority 15 

62 - 68 Unit Price 0000999 

69-76 Blank 

77 Mode of Shipment J 

 

 Table 2 - When AS3 results from ILS-S processing CMOS 945A 

Pos Data Example Data 

60-61 Blank 

62 - 68 Unit Price 0000999 

69-80 Blank 

 

 Table 3 - Format as prescribed in DOD 4000.25-1-M 

5. REQUESTED CHANGE(S):

a. Requested changes in detail: 

(1) Add the estimated shipment date in the DS 856S (DIC AS3) Shipment Status 

transaction. When the 856S (AS3) contains an estimated shipment date it will not contain the 

actual carrier release date or mode of shipment. 

(2) ILS-S will implement a system change to ensure the 856S contains the unit 

price. 

b. Approved procedures:

(1) When there is no material release confirmation from CMOS or any other 

shipper system operating on behalf of the Air Force, and the retail supply activity has confirmed 

that the shipment did lift, but is lacking the actual transportation data, ILS-S will generate the 

DLMS 856S (AS3) with a new date field that is populated with the estimated shipment date. 

(2) DLA Transaction Services will convert the 856S to a DIC AS3 for routing to 

DAISY, with the Estimated Shipment Date mapped to rp 57-59. This will be only a one-way 

map conversion, DLMS-MILS. In fall 2011, when DAISY migrates its warehousing function to 
Page 5 Attachment, ADC 433 

DLA’s Distribution Standard System (DSS), DLA Transaction Services will route the 856S with 

the estimated shipment date clearly identified in the DLMS transaction. 

(3) If ILS-S obtains the actual shipment date and other related transportation data 

(e.g., TCN, transportation mode/method, secondary transportation tracking numbers) subsequent 

to the release of the original 856S with an estimated shipment date, it will follow procedures 

outlined in ADC 411 to create an updated 856S with the updated transportation data. 

Update the DLMS Supplement as shown: 

# Location Revision to 

856S Shipment Status

Reason for 

Change 

/SBSS Notes

1 DLMS 

Introductory 

Note 

Add ADC 433 to DLMS Introductory note:

- ADC 433, Requirements for estimated 

Shipment Date in the DS 856S Supporting 

Shipments to DLA Disposition Service Field Offices 

To identify 

changes in the 

DS. 

2 2/DTM01/2000 Add Qualifier 369 and DLMS Note 

369 Estimated Departure Date 

DLMS Note: 

Use to identify the Estimated Shipment Date (ESD) 

for turn-ins to disposal when the actual date is 

unknown. See ADC 433

To indicate date 

is an estimated 

shipped date 

c. Transaction flow: See figure 1. The transaction flow does not change. 

d. Alternatives: Send a DI Code AS3 transaction with the estimated shipment date 

(no “*”). 

6. REASON FOR CHANGE: AS3 transactions were generated in this format (as MILSTRIP 

images) prior to the DLMS implementation. During the DLMS implementation it was discovered 

that there was no way to represent the estimated shipment AS3 in a DLMS format. 

7. ADVANTAGES AND DISADVANTAGES:

a. Advantages (tangible/intangible): Enables ILS-S to send an estimated shipment 

date by using the DLMS transaction (856S). 

b. Disadvantages: During the short transition period until DSS takes over the DAISY 

warehousing function, there will be no indication that the shipment date is estimated. 

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: June 30, 2011 90 days 

from date of the issuance of ADC 433 
Page 6 Attachment, ADC 433 

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: N/A 

10. IMPACT: 

a. New DLMS Data Elements: Estimated Shipment Date. 

b. Changes to DLMS Data Elements: None 

c. DLA Transaction Services: Update AS3 Shipment Status map to show DTM01=369 

mapped to rp 57-59. This is a one-way DLMS-MILS conversion, which is needed on a 

temporary basis until DAISY transfers its warehousing functions to DSS. 

d. DoD 4000.25-M, Volume 2, Chapter 5. 
Page 1 Enclosure 1, ADC 433 

ADC 433 

Enclosure 1: DLMS Manual Changes 

Add the following new paragraph to Volume 2 of DOD 4000.25-M 

 C5.2.3.1.10. The estimated shipment date may be used, in the absence of the actual 

shipment date, when generating the 856S (DI Code AS3) for disposal turn-ins.1

 Upon 

availability of the actual shipment date and other related transportation data (e.g., TCN, 

transportation mode/method, secondary transportation tracking numbers) subsequent to the 

release of the original 856S with an estimated shipment date, an updated 856S with the updated 

transportation data must be generated.2

 

1

 Refer to ADC 433 

2

 Refer to ADC 411 
Page 1 Enclosure 2, ADC 433 

Enclosure 2, RESPONSE/COMMENTS RESOLUTION: 

Organization Response/Comment Disposition 

DLA Concurs without comment. Noted 

Army Concurs with PDC 457 as 

written. 

Noted 

Navy Concurs with PDC 457 as 

written and submits no 

additional changes or 

amendments. 

Noted 

Air Force Approved Noted 

USMC Concurs as written. Noted 

DFAS DFAS has no comment on 

this.  

Noted 

USTRANSCOM Approves with comment. 

The proposed change 

requires changes to 

processing logic in IGC. 

Request a minimum of 90 

days from time of ADC 

approval to time that the IC 

changes are effective, in 

order for IGC to have the 

minimum acceptable time to 

add the logic to parse the 

estimated shipment date into 

their integrated database. 

ADC Cover letter and 

paragraph 8 of the ADC 

reflect a 90 day delay to 

enable IGC to complete 

programming changes prior 

to implementation of the 

changes to the 856S.