DEFENSE LOGISTICS AGENCY

HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

FORT BELVOIR, VIRGINIA 22060-6221

June 4, 2018 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

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

Revise DLMS 830D to Accommodate Gross Demand Plan (GDP) for 

Implementation by All DOD Components (Supply) 

We are forwarding the attached approved change to DLM 4000.25, Defense Logistics 

Management Standards, for implementation. This change is to be implemented no later than 

December 31, 2019. Request DOD Components provide projected implementation date. 

Addressees may direct questions to Mr. Rafael Gonzalez, e-mail: 

Rafael.Gonzalez@dla.mil. Others may direct questions to their Service or Agency designated 

Supply PRC representative available at 

http://www.dla.mil/HQ/InformationOperations/DLMS/allpoc/. 

HEIDI M. DAVEREDE

Director

Enterprise Business Standards Office

Attachment

As stated 

cc: 

ODASD (SCI)
Attachment, ADC 1267

Page 1

Attachment to ADC 1267

Revise DLMS 830D to Accommodate Gross Demand Plan (GDP) for 

Implementation by All DOD Components

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Louis Jackson HQ DLA J343, 804-357-8727

b. Functional POC: Pearlis Sturgis HQ DLA J343, 703-767-0138

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply

b. Primary/Secondary Functional Process: Demand Data Exchange (DDE) Projected Gross 

Demand Plan (GDP), Army Supply Plan (ASP) 

3. REFERENCES:

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

Procedures, June 13, 2012

b. DOD Directive 8190.01E, Defense Logistics Management Standards (DLMS), January 9, 

2015

c. DLM 4000.25, Military Standard Transaction Reporting and Accountability Procedures 

(MILSTRAP) Appendix 2.8 Reject Advice Codes

4. APPROVED CHANGE(S): Green highlighting identifies substantive updates subsequent to 

staffing.

a. Brief Overview of Change: Revise procedures under Reference 3.a. to authorize the use of 

DLMS 830D Demand Data Exchange (DDE) as the primary exchange method for reporting GDP 

between DOD Components. Upon implementation of this change, the DLMS 830D is the only 

authorized transaction for DDE, GDP, and ASP. DOD Components are authorized to use Legacy 

Document Identifier Code (DIC) CDD as an alternative until they can fully implement use of the 

DLMS 830D. This change also revises DLMS 830D DDE projected supply plan procedures,

authorizes submission of 60 month plan periods using a 0 (zero) for those months with no plan data, 

and allows two (2) decimal positions in all quantity fields to include zeros at the end. In addition, 

using the 830D IC requires the Defense Automatic Addressing System (DAAS) to use Federal 

Logistics Information System (FLIS) data to populate data in the 830D and route it to the appropriate 

source of supply routing identifier code (RIC). The General Services Administration (GSA) informed 

DLA that they have no plans to implement the DLMS transactions or the procedures documented in 

this change. Any change in this posture will be coordinated with the relevant DOD organizations in a 

subsequent PDC.
Attachment, ADC 1267

Page 2

b. Background:

(1) DOD Acquisition and Logistics Functional Strategy FY 2013, and DOD Directive 

8190.01E (Reference 3.b.) identify the DLMS transactions as enterprise standards. Consequently, 

DOD Component automated information systems must fully comply with DLMS standards by 2019, 

which will increase data throughput and facilitate interoperability of logistics business functions across 

the global supply chain management systems.

(2) The Navy currently uses a flat file for demand data exchange. The Navy GDP flat 

file does not meet DLMS standards. Accordingly, the Navy must convert their GDP flat file format to 

a DLMS transaction. Additionally, fleet readiness centers’ (FRCs) current agreement with DLA under 

Base Realignment and Closure (BRAC) Law 2005, Supply, Storage, and Distribution Concept of 

Operations maintains the DLA role in coordinating transactions governed by BRAC Law and Concept 

of Operations (CONOPS).

(3) The Commander Fleet Readiness Center (COMFRC) Naval Air Systems Command 

(NAVAIR) Depot Maintenance System (NDMS) cannot program RIC information for a DOD source 

of supply other than the DLA RIC SMS. NDMS is Functional Area Manager (FAM) certified and 

funded by the FRCs as a Depot Level Maintenance System. Consequently, NDMS is limited to 

maintenance and maintenance reporting system changes. The limited BRAC funding used for the 

Inventory Management and Stock Positioning (IMSP) design was expended years ago and the FAM 

certification limits new development to maintenance requirements. Several supply chain functions 

(including routing) were never included in the NDMS design as the Naval Supply Systems Command 

(NAVSUP) U2 system performed those functions for all Navy maintenance activities. The BRAC 

IMSP transitioned the NDMS routing functions to DLA via RIC SMS with exception of the Navy 

depot level reparables (DLR), which route to Navy ERP via RIC NRP. Navy DLRs only provided the 

NRP exception during the IMSP design because of the carcass tracking requirements and the high 

volume of Navy DLRs.

(4) Routing for DLMS 830D. The DOD component initiating the demand data 

exchange request must identify the appropriate source of supply for each NIIN in the DLMS 830D. If 

the originating system cannot identify the source of supply, Components must use RIC SGA for 

DAAS. DAAS will validate the transaction and/or correct the RIC as necessary. DAAS will then 

route the DLMS 830D by RIC to the respective source of supply.

c. APPROVED Change in Detail:

(1) Implement the DLMS 830D DDE as the primary method for communicating GDP 

Projected Supply Plans between DOD Components. Systems that are not DLMS compliant may 

continue using the legacy DIC CDD until they implement the DLMS 830D, but not after 2019. DOD 

Components reporting a projected supply plan will use the organization’s RIC, the Forecast Schedule

(FST) segment forecast timing qualifiers, and the Destination Quantity (SDQ) segment.

(a) All DOD Components must implement the DLMS 830D. Systems unable 

to identify the proper source of supply RIC must use the RIC-TO SGA as a generic RIC.

(b) Upon submission, DAAS will match the 830D NIIN with FLIS data to 

determine and populate the 830D with the appropriate source of supply RIC (replacing RIC-TO SGA)

and forward the DLMS 830D transaction to the appropriate source of supply. DAAS will route all 

forecasted requirements with local stock numbers (LSNs) (i.e., alpha characters in the NIIN field) to 
Attachment, ADC 1267

Page 3

DLA RIC-TO SMS. If DAAS is unable to match NIINs without alpha characters, DAAS will reject 

the transaction back to the originator via DLMS 824R Reject with the appropriate reject advice code.

(2) DAAS will configure quantity fields to accept two (2) position decimals to include 

values equal to zero (0) or greater.

(3) Add new qualifier F1 to DLMS 830D transaction beginning segment (1/BFR/0200) 

and authorize the use of an image transaction. DAAS will provide an image of the DLMS 830D 

transaction to DLA RIC-TO SMS for all outgoing DLMS 830D regardless of source of supply. This 

will allow DLA to retain a history of all DLMS 830D DDE Projected Supply Plan transactions.

(4) Add new data element called “Stock Number” in DLMS 830D; segment 

2/LIN02/0100, to identify an LSN. 

(5) Add new data element called “National Stock Number” in DLMS 830D; segment 

2/LIN02/0100, to identify a National Stock Number (NSN). 

(6) Add new data element called “Demand Planning Status Code” in DLMS 870L;

segment LQ01/330 to report the status of a DDE, GDP, or ASP requirement. The source of supply 

will use the status code to confirm or reject the forecasted requirements and communicate the decision 

to the originator. For an authorized list of status codes, see Appendix 7.33 

(7) Authorize submission of DLMS 870L Demand and Supply Planning 

Status/Notification transaction beginning segment (1/BSR01/20) to confirm or reject a forecasting 

activity due to one of the valid reason codes documented under DLMS 4000.25 Volume 2, Appendix 

7.33. 

(8) Authorize submission of DLMS 870L Demand and Supply Planning 

Status/Notification transaction to report DDE status to a forecasting activity.

(9) Revise DLMS 830D mapping when converting into a CDD transaction. Under 

DLMS, the Fund Identification Number under 2/REF01/1400 will map to record position 953 and the 

first instance of 2/PWK07/1000 will map to record position 954 – 972 when converting into a CDD 

transaction. The first occurrence of 2/PWK07/1000 will not exceed 19 characters when providing a 

fund identification number. 

(10) Add Reject Advice Code BB in reference 3.c. to reject the transaction due to an 

unidentifiable/invalid source of supply. DAAS will use Advice Code BB when the originator 

submitted an unidentifiable/invalid source of supply and they are unable to route the transaction to the 

noted RIC. 

(11) Revise current transaction title for DLMS 870L to read Demand and Supply 

Planning Status/Notification in support of the new functionality under the Demand Data Exchange 

process. 

(12) Add appendix 2.73 Demand Planning Status Code under DLM 4000.25, Military 

Standard Transaction Reporting and Accountability Procedures (MILSTRAP). 

d. Revisions to DLM 4000.25 Manuals: 

(1) Revise DLM 4000.25, DLMS, Volume 2, Chapter 2 as shown in Enclosure 1. 
Attachment, ADC 1267

Page 4 

(2) Revise DLM 4000.25, Military Standard Transaction Reporting and Accountability

Procedures (MILSTRAP) Appendix 2.8 Reject Advice Codes. 

(3) Add appendix 2.73 Demand Planning Status Code under DLM 4000.25, Military

Standard Transaction Reporting and Accountability Procedures (MILSTRAP) as shown in Enclosure 

3. 

e. Approved Transaction Flow:

(1) The originating system calculates forecasted requirements and transmits a DLMS

830D transaction with the appropriate RIC-TO by NIIN via DAAS. If the originating system is 

unable to identify the proper source of supply, use RIC-TO SGA. DAAS receives and validates the 

transaction. Customers using FEDMALL will not be able to receive reject transactions from DAAS 

or the applicable source of supply. DOD customers may need to return to FEDMALL in order to 

review any communication with DAAS or the source of supply. 

(2) DAAS will send an 824R Reject Advice transaction to the originating system if

the NIIN, Source of Supply, or Quantity fails validation. 

(3) DAAS will select the appropriate reject advice code. See reference 3.c. for a

complete list of authorized codes. Once notified, the originator will correct and re-submit the 

transaction via DAAS.

(4) Upon submission, DAAS evaluates the NIIN (830D 2/LIN02-03/0100 code ZZ)

in the transaction and uses FLIS data to determine and populate the appropriate source of supply. 

DAAS will then create a DLMS 830D transaction based on the original request. The forecasted 

requirement may contain only one NIIN, or LSN in the same transaction. When there is an invalid 

NIIN, DAAS will reply to the originator with DLMS 824R Reject Advice transaction, using reject 

advice code DB (Rejected. NIIN Missing/Invalid). 

(5) Once the validation of NIIN is complete, DAAS routes the DLMS 830D to the

applicable source of supply RIC (2/N1/3200) and transmits an image to DLA. DAAS will route all 

forecasted requirements with LSNs (830D 2/LIN02-03/0100 (new) Code SW) to RIC-TO SMS. 

The image transaction will allow DLA to retain historical records and maintain full visibility of the 

forecasted request sent. If DAAS is unable to validate a NIIN, DAAS will reject the transaction and 

report to the originator using a DLMS 824R Reject.

(6) Each source of supply receives and processes the DLMS 830D transaction and

proceeds accordingly with the forecasted requirements. The source of supply can either accept or 

reject the request via DLMS 870L Demand and Supply Planning Status/Notification. DLMS 

4000.25, Volume 2, Appendix 7.33 identifies all authorized status codes for acceptance or rejection 

of any DDE, GDP, or ASP forecasted requirement. 

(7) Prior to submitting a forecasted request, Originators must ensure the recipient

source of supply has a service agreement in place as DAAS is unable to identify which recipients 

are participants. Consequently, forecasted requirements without positive confirmation from the 

source of supply will process as rejects. The originator may conduct offline communications 

with the source of supply in order to obtain positive confirmation and achieve resolution. 

f. Alternative: None
Attachment, ADC 1267

Page 5 

5. REASON FOR CHANGE: DOD Acquisition and Logistics Functional Strategy FY 2013, and

DOD Directive 8190.01E (Reference 3.b.), identify the DLMS transactions as an enterprise standard,

and requires that Component automated information systems must achieve full compliance by

December 2019. Use of the DLMS will increase throughput of data and facilitate interoperability of

logistics business functions across the global Supply Chain Management Systems.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: The changes in this document will improve the automation of current

procedures under a DLMS environment. 

b. Disadvantages: None identified.

7. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW DEVELOPMENT:

a. DLMS implementation of the DDE Projected Supply Plan requires implementation of the

DLMS 830D Implementation Convention. 

b. The expectation is that all participating DOD Components receiving requirements via DLMS

830D consider planning and supporting the needed materiel or Components in support of the planned 

maintenance programs. 

8. ADDITIONAL COMMENTS TO CONSIDER:

a. This is a new requirement for the Services to receive and process DLMS 830D Demand Data

Exchange Projected Supply Plan transactions. Previously, only DLA SMS received the DLMS 830D. 

b. DLA is not yet DLMS compliant for DDE Projected Supply Plan. DLA must address

implementation status of DLMS 830D through the ODASD (SCI) DLMS Implementation Integrated 

Process Team (IPT). In addition, DLA must coordinate their implementation of DLMS 830D with 

DAAS. DAAS translates DLMS 830D into DIC CDD for DLA, until DLA implements DLMS 830D. 

c. Several DOD Components reported the lack of available RICs within their authorized

Service/Agency. The lack of RICs is due to longstanding practices of using the RIC beyond its 

original purpose of identifying a “TO” or “FROM” activity within a transaction. EBSO is 

collaborating with DAAS to document and develop the necessary capabilities to route all transactions 

by DoDAAC in lieu of the RIC. This capability will most likely begin as a pilot implementation with 

only selected transactions and will later transition to support all transaction exchanges between DLMS 

compliant systems. Components should be aware of this long-term initiative and consider proactively 

transitioning to routing by DoDAAC as their systems become DLMS compliant. Transaction routing 

will remain by RIC until further notice.

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: NLT December 31, 2019.

Request DOD Components provide projected implementation date.

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH

IMPLEMENTATION OF THIS CHANGE: None identified.
Attachment, ADC 1267

Page 6

11. IMPACT:

a. New DLMS Data Elements:

(1) Add new DLMS Qualifier DV, Demand Planning Status Code (alphanumeric, MIN 

2/MAX 2), to data element 1270 for use in DLMS 870L transaction. Definition – Used in response to 

a Demand Data Exchange (DDE), Gross Demand Plan (GDP), or Army Supply Plan (ASP) 

transaction. The status code will report to the originator, acceptance or rejection of the forecasted

request. See Enclosure 3 for details of the new DV qualifier, including its code list. 

(2) Add new DLMS element Program Funding Indicator (alphanumeric, MIN 1/Max 1) 

represented in the DLMS 830D by 2/REF01/1400, and DLMS 870L 2/REF01/87 Code FG Fund 

Identification Number. For Navy, this is a Program Funding Indicator associated with a GDP. The 

program funding indicator is the standard Customer Order Number (CON) for all Navy Fleet 

Readiness Centers required to use Navy Working Capital Funding. 

b. Changes to DLMS Data Elements: Adjust the data attributes of the Demand Data 

Quantity to allow for two decimal positions.

c. Automated Information Systems (AIS):

(1) Updates to Component applications are required to support using the DLMS 830D 

DDE Projected Supply Plan as described in this change. 

(2) FedMall (formerly DOD EMALL): DLA provides a module within FedMall called 

MILSTRIP Order Entry System (MOES) where customers can upload transactions to include DDE 

Projected Supply Plan. MOES uses the DLA legacy DIC CDD format. The use of the CDD is 

available via FedMall until FedMall MOES implements the DLMS transactions, to include DLMS 

830D.

d. Defense Automatic Addressing System (DAAS):

(1) DAAS must implement system changes in order to associate FLIS data and to

validate each source of supply RIC by NIIN included in the DLMS 830D. Upon validation, DAAS 

will route the DLMS 830D by source of supply and send an image transaction to DLA RIC-TO SMS.

(2) Requires DLMS mapping updates. No impact to legacy formats. Under DLMS

830D, the Fund Identification Number under 2/REF01/1400 will map to record position 953 and the 

first instance of the PWK loop 2/PWK01/1000 will map to record position 954 – 972 when converting 

into a CDD transaction. The first occurrence of 2/PWK07/1000 will not exceed 19 characters when 

providing a funding identification number (Navy use for Program Funding Indicator).

e. Non-DLM 4000.25 Series Publications:

(1) DLA J3 will recommend appropriate changes to the DODM 4140.01 to incorporate 

the changes described in this DLMS change. 

(2) DOD Components may need to update internal guidance to comply with this DLMS 

change.
Attachment, ADC 1267

Page 7

12. PROPOSED DLMS CHANGE (PDC) 1267 STAFFING RESPONSE/COMMENT 

RESOLUTION

Originator Response/Comment Disposition

1. Army No Response Received

2. Navy The verbiage in section 4.c.(8) should reference 

1/REF01/1400 vice 1/REF01/87

In 4.e.(4) “DAAS will reply to the originator with 

DLMS 824R Reject Advice transaction, using reject 

advice code DB (Rejected. NIIN Missing/Invalid).

Comment: The PDC only provides a reject status 

code for the 824R if the NIIN fails; will the 824R 

failures on the other data elements be narrative

Navy requires the addition to Appendix 7.33 of a 

new code defined as "Forecast accepted and 

processed". Currently, code 00 states, "Forecast 

accepted, processed, and planned". The new code 

excludes 'planned', as Navy is unsure of future plans 

to count this type of demand in its forecast.

In section 4.c.(5) (page 3), the terms 'accept' and 

'reject' need to be more specifically defined. In the 

case that the recipient receives the file but does not 

'plan' for it, what type of response is required?

Navy requires the addition of a new optional data 

elements to both the 830D and 870L ICs to 

accommodate the following item:

 - Program Funding indicator to describe a program 

using Job Order Number (JON) attributes (3, C or 

D); etc., for Components program, 2, B; etc., for 

Engines

Noted: This was fixed in an 

earlier version.

Text in the previous subparagraph 4.e.(3) was modified 

to point to the complete list of 

reject advice codes

Per subsequent discussion with 

DLA and Navy, the Appendix 

7.33 Demand Planning Status 

Code list was updated to reflect: 

00 Forecast received; awaiting 

evaluation

01 Forecast accepted, 

processed, and planned.

The wording in 4.c.(6) and (7) 

was updated to reflect “confirm 

or reject” 

Program Funding indicator was 

added to ADC 1267 for the 830D 

and 870L

2. Air Force Concur without comment Noted

3. Marine Corps Concur without comment Noted.

4. DLA Concur without comment Noted

5. DAAS Concur without comment Noted

6. USTRANSCOM Abstain Noted.

7. GSA Concur with comment: Remove "GSA" from the 

title, and the other instances in which "GSA" appears 

in the document. Add a separate sentence, at 

paragraph 2 a. ("Brief Overview of Change"), as:

The GSA supply system contains no current or 

planned use of this DLMS transaction. Any change 

to this posture will be coordinated with DOD.

GSA comments are incorporated 

in ADC 1267.
Enclosure 1, ADC 1267

Page 1

ENCLOSURE 1 TO ADC 1267

A. Revise DLM 4000.25, Volume 2 Supply Standards and Procedures Chapter 2, Special 

Program Requirements and Demand Data Exchange Projected Supply Plan as follows:

Administrative update throughout the chapter to replace “shall” with “will” or “must” as appropriate.

(Preceding text not shown) 

C2.3. DEMAND DATA EXCHANGE PROJECTED SUPPLY PLAN. This section provides 

procedures for the exchange of DDE projected supply plan data between DoD CustomersDLA and DoD 

customers. The two components of this business process are the transmission of customer requirements 

via DDE and DLA customer collaboration. Business rules for the submission and processing of DDE 

shall be documented in a DLA, in collaboration with participating Components, will document the 

business rules for submitting and processing DDE, GDP, and ASP via a Joint Collaboration 

Agreement or Memorandum of Agreement. DLA customer support agreement., (e.g., Joint 

Collaboration Agreement). This agreement must be in place prior to the initial submission. DLA shall

will use the DDE collaboration process to improve the accuracy of DLA’s demand planning to support 

customer requirements.

C2.3.1. DDE supply planning activities may submit to DLA their projected supply 

plan/collaboration data for future requirements expected to be obtained from DLA using the DLMS

830D, DDE Projected Supply Plan Transaction. Separate DDE projected supply plans into monthly 

periods based on the projected requirement date materiel is expected for a planned maintenance 

schedule dates that the materiel will be ordered from DLA. Types of demands for which Use of the 

formal collaboration process is restricted to Class IX materiel. Condition guidelines data may be 

submitted include, for collaborative forecasting include, but are not limited to:

C2.3.1.1. Requirements for which the DoD Component has a recurring demand.

C2.3.1.2. Subsistence, all categories.

C2.3.1.3. One-time training exercises or maneuvers.

C2.3.1.4. Repair or rebuild programs that are either nonrecurring or seldom or irregularly 

programmed. 

C2.3.1.5. New constructions (e.g., ships, buildings). Acquisition of new programs (e.g.,

Weapon System, Component Equipment).

C2.3.1.6. One-time alterations, modifications, or conversion programs.

C2.3.1.7. Initial issue of existing items (e.g., outfittings, activations, and changes in 

authorized allowances).

C2.3.1.8. Initial requirements for special operational projects.

C2.3.1.9. Requirements for initial testing.

C2.3.1.10. Requirements for infrequently planned support operations such as Arctic and 

Antarctic resupply missions.
Enclosure 1, ADC 1267

Page 2

C2.3.1.11. Special situations of a nonrepetitive nature when required in support of authorized 

Security Assistance Program requirements (e.g., initial pipeline stockage requirements in support of 

approved CLSSA).

C2.3.1.11. Zero or reduced requirements, which are different from past customer demand 

history patterns.

C2.3.2. DDE, GDP, ASP Projected Supply Submission and Routing

C2.3.2.1. Submission Timeframe. DDE Transactions must be submitted each month. 

Demand forecasting data should be submitted by the first of the month and may be submitted up to 5 

business days prior to the first of each month, with a buffer until the third of the month to accommodate 

transmission errors or failures Submit DDE forecasting transactions each month during the period of 

the 22nd through the 28th day of each month.

C2.3.2.2. DDE Projected Supply Plan. DDE supply planning activities Participating DoD 

Components will prepare the DLMS 830D DDE projected supply plan for each item Demand Forecast 

Unit (e.g., NIIN, Ship to DoD activity address code (DoDAAC), and requisitioner (Sold To) DoDAAC) 

for which the customer wishes to collaborate with DLA. Each transaction set must include the projected 

supply plan period beginning date and the projected supply plan period ending date. The projected 

supply plan period span can be as short as 12 months or as long as 60 months; however, DLA 

recommends DDE projected supply plans be provided for 60 months in the plan period., must include 

zero quantity projections filling those mMonths with no plan data must include zero quantity 

projections.

C2.3.2.3. Intra-Component optional fields. Components may use optional fields available 

in DLMS 830D and 870L to carry intra-Service information as necessary. Optional information 

received in a DLMS 830D must be perpetuated in the response back to the originator using DLMS 

870L. 

C2.3.2.4. DAAS Processing. The originator calculates forecasted requirements and transmits

a DLMS 830D DDE Projected Supply Plan transaction with the appropriate RIC-TO by NIIN via DAAS. 

When the originator is unable to identify the RIC-TO, use the DAAS routing identifier code (RIC) SGA. 

DAAS will receive and validate the transaction. If the 830D data fail DAAS edit during evaluation, DAAS 

will reply to the originator with an 824R Reject Advice transaction. Once notified, the originator will 

correct and resubmit the transaction.

C2.3.2.5. Validation of NIIN. After successful submission, DAAS will evaluate the NIIN

(830D 2/LIN02-03/0100 code ZZ) in the transaction with RIC-TO SGA and use FLIS data to determine 

and populate the appropriate source of supply. DAAS will route all transactions with LSN (alpha 

characters in the NIIN field) to RIC-TO SMS. If DAAS is unable to validate the NIIN, DAAS will reject 

the transaction and report to the originator with appropriate reject advice code (MILSTRAP Appendix 2.8 

Reject Advice Codes) via DLMS 824R Reject. After the evaluation is complete, DAAS will create a DLMS 

830D transaction by source of supply based on the original transaction and route it to the applicable 

source of supply RIC. DAAS will transmit an image of each DLMS 830D for which RIC SMS was not the 

source of supply to DLA RIC-TO SMS in order to maintain full visibility of the initial forecasted request. 

C2.3.2.6. Source of Supply Response. Upon successful transmission of the forecasted

requirement, the source of supply will submit a response back to the originator via DLMS 870L

Demand and Supply Planning Status/Notification transaction. The source of supply can either 

accept or reject any DDE, GDP, or ASP forecasted requirement using one of the status codes under 
Enclosure 1, ADC 1267

Page 3

DLMS 4000.25, Volume 2, Appendix 7.33. As part of the response, the source of supply will 

perpetuate any optional information provided in the initial request. 

C2.3.2.7. Forecasting Request without a response. Prior to submitting a forecasting 

request, originators must ensure the recipient source of supply has a service agreement in place as 

DAAS is unable to identify which recipients are participants. Consequently, forecasting 

requirements without positive confirmation from the source of supply will be process as rejects. The 

originator may conduct offline communications with the source of supply in order to obtain positive 

confirmation and achieve resolution. 

C2.3.3. DLA Transaction Services Processing. DLA Transaction Services shall route all 

DDE transactions to DLA’s Enterprise Processing Center, source of supply “SMS.”

C2.3.4. DLA Validation of NIIN. DLA shall screen transaction sets and will only accept 

valid NIINs for processing.

C2.3.5C2.3.3. DLA Processing of DDE Data. DLA shall will compare the collaboration 

customer’s projected supply plan to the projected customer supply plan calculated by the Planning and 

Collaboration Subsystem or the previous collaborative projected supply plan if the NIIN is a recurring 

Demand Forecast Unit.

C2.3.4. Collaboration Interaction. All Collaborative items (which may or may not exceed system 

tolerance parameters) shall will be available for monthly collaboration interaction with the customer and 

DLA. The point of contact for the customer shall will be alerted, via e-mail by the Collaboration lead at 

the DLA Field Activity (DLA Aviation, Richmond, VA, DLA Land and Maritime, Columbus, OH, DLA 

Troop Support, Philadelphia, PA, by the seventh business day of every month, to notify the customer of 

the open and close dates of the monthly collaboration window. The customer will have until the fourth 

Thursday of the month to complete the review (specific open and close dates will be cited in the e-mail). 

The DLA demand planner will then have until the fourth Friday of the month (also known as “Demand 

Month End”) to complete the review and publish the demand plan for inclusion in the projected supply 

plan.
Enclosure 1, ADC 1267

Page 4

B. DLM 4000.25, Military Standard Transaction Reporting and Accountability Procedures 

(MILSTRAP) Appendix 2.8 Reject Advice Codes as follows:

AP2.8. APPENDIX 2.8

REJECT ADVICE CODES

AP2.8.1. All A B, D and H series reject advice codes not listed in this appendix are reserved for future 

use and are not to be used unless authorized and disseminated by the DoD MILSTRAP Administrator. 

All other series are reserved for intra-Component use.

NUMBER OF CHARACTERS: Two

TYPE OF CODE: Alphabetic 

EXPLANATION: Identifies to the originator of a transaction, the reason for 

rejection, and indicates return of the transaction for correction 

and resubmission.1

MILSTRAP RECORD POSITION: 79-80

DLMS SEGMENT/QUALIFIER: LQ Segment, LQ01 Data Element ID 1270

Qualifier “ET – Reject Advice Code”

CODE EXPLANATION

AA Rejected. Document identifier code invalid. 

AB Rejected. Submitted to incorrect manager; routing identifier code of correct 

manager indicated in record positions 54-56, if known. (When known, 

incorrect manager is identified in MILSTRAP recorded positions 54-56 or 

appropriate DLMS segment.)

AC Rejected. Type of physical inventory code invalid or blank.

AD Rejected. Stock or part number unidentifiable.

AE Rejected. Quantity field invalid.

AF Rejected. Document number invalid.

AG Rejected. Ship-to address unidentifiable.

AH Rejected. Required signal code invalid or blank. 

AI Rejected. Procurement instrument identifier (PIID) (contract number) invalid 

or blank.

AJ Rejected. Required fund code invalid or blank. 

AK Rejected. Ownership/purpose code invalid or blank.

 1 Codes in the A_, B_, D_, and H_, series not listed above are reserved for future use and are not to be used unless 

authorized and disseminated by the DoD MILSTRAP Administrator. All other series are reserved for intra-Component 

use.
Enclosure 1, ADC 1267

Page 5

CODE EXPLANATION

AL Rejected. Unauthorized owning DoDAAC or RIC (use for Air Force 

Government Furnished Property - Accountability (GFP-A) only).

AM Rejected. Supply condition code invalid or blank.

AN Rejected. Physical location of property not provided.

AO Rejected. Insufficient inventory in the accountable property system of 

record (APSR) due to potential mismatch.

AP Rejected. Required management code invalid or blank. 

AQ Rejected. Processing/count date invalid or blank. Location Reconciliation 

Request cutoff date invalid.

AR Rejected. Unit of issue incorrect. 

AS Rejected. Support date invalid. Location Reconciliation Request and/or 

Transaction History Transmittal received past scheduled deadline.

AT Reserved for DoD assignment.

AU Rejected. Invalid Country Code. The code is not valid in the Geopolitical 

Entities, Names, and Codes (GENC) Standard. Originator must update the 

transaction with a valid country code and resend.

AV Rejected. Activity identified in location reconciliation request record 

positions 67-69 (RIC (From)) not valid.

AW Rejected. Logistic Reassignment Transaction (DEE, DEF, DDX) received 

more than 1 year after the ETD. (The D4X will be rejected if no 

memorandum due-in is on record at the gaining item manager (GIM) to 

indicate it is a valid procurement receipt.) 

AX Rejected. Government Services Administration (GSA) is source of supply 

for requested SPR. GSA does not participate in MILSTRAP SPR 

procedures. If required, submit funded DoD MILSTRIP requisition citing 

applicable required delivery date.

AY Rejected. Location Reconciliation Request and/or Transaction History 

Transmittal does not equal the number of transactions recorded in the 

Location Reconciliation Notification and/or Location Reconciliation History 

Notification. 

AZ Rejected. Number of Location Reconciliation Requests received from 

storage activity exceed reasonable variance from owner/manager.

BA Rejected. Serial Number or UII (when available) invalid or missing (use for 

Air Force Government Furnished Property - Accountability (GFP-A) only). 

BB Rejected. Unidentifiable/Invalid Source of Supply.

BN Rejected. Invalid logistics bill number.

BU Rejected. Failed validation with SFIS Fund Code to Fund Account 

Conversion Table.
Enclosure 1, ADC 1267

Page 6

CODE EXPLANATION

(1) Discrete values for the SLOA data elements in the transaction do not 

match data elements from the SFIS Fund Code to Fund Account 

Conversion Table for the Fund Code cited in the transaction.

(2) Invalid/missing fund code. Resubmit with a valid fund code.

Note: Issues with content of the SFIS Fund Code to Fund Account 

Conversion Table are to be communicated to the Fund Code Monitor of the 

cognizant Component.

BV Rejected. DoDAAC in the transaction does not have the appropriate 

authority code for its intended use

BW Rejected. Suspense account is not authorized for Interfund use 

BX Rejected. Total dollar value detail of bills is not equal to total dollar value of 

the summary bill

BY Rejected. Count of detail bills is not equal to the count in the summary bill 

(MILS RP 5-7, DLMS 810L 3/CTT01/070)

BZ Rejected. DoDAAC is not valid in DAAS

DA Rejected. FSC Missing/Invalid.

DB Rejected. NIIN or LSN Missing/Invalid.

DC Rejected. Unit of Issue Missing/Invalid.

DD Rejected. Quantity Missing/Invalid.

DE Rejected. Hazardous Waste/Material Code Missing/Invalid.

DF Rejected. Unit Price Missing/Invalid.

DG Rejected. Supply Condition Code Missing/Invalid.

DH Rejected. Demil Code Missing/Invalid.

DI Rejected. Contact Name Missing/Invalid.

DJ Rejected. Contact Phone Missing/Invalid.

DK Rejected. Chemical Abstract Service Number is Missing/Invalid.

DL Rejected. Fund Code Missing/Invalid.

DZ Rejected. Turn-in activity cannot process DLMS-formatted transactions. 

DTID rejection must be communicated through alternative methods.

HA Rejected. Waste Profile Sheet Invalid or Missing/Invalid.

HB Rejected. Generator Name Missing/Invalid.

HC Rejected. Facility Address Missing/Invalid.

HD Rejected. Facility City and State Missing/Invalid.

HE Rejected. Facility Zip Code Missing/Invalid.

HF Rejected. Technical Contact Missing/Invalid.

HG Rejected. Technical Phone is Missing/Invalid.

HH Rejected. Chemical Name Missing/Invalid.

HI Rejected. Chemical Concentration is Missing/Invalid.

HJ Rejected. Chemical Range is Missing/Invalid.
Enclosure 1, ADC 1267

Page 7

CODE EXPLANATION

HK Rejected. Chemical Abstract Service Number is Missing/Invalid.

HL Rejected. EPA HW Number Missing/Invalid.

HM Rejected. Range of Concentration Missing/Invalid.

HN Rejected. Unit of Issue Incorrect.

HO Rejected. Container Number Missing/Invalid.

HZ Rejected. Turn-in activity cannot process DLMS-formatted transactions. 

HWPS acknowledgment must be communicated through alternative 

methods.
Enclosure 2, ADC 1267

Page 1

ENCLOSURE 2 TO ADC 1267

a. Revise 830D DLMS IC as shown:

Location Change Table for 

830D Demand Data Exchange (DDE) Projected Supply Plan

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1267 to DLMS Introductory notes: 

- ADC 1267, Revise DLMS 830D to Accommodate Navy Fleet 

Readiness Centers (FRC) Gross Demand Plan (GDP) for 

Implementation by all DOD Components and GSA.

To identify DLMS 

changes included in 

the implementation 

convention.

2. 1/BFR13/0200 Delete current DLMS data element Note and add qualifier and 

DLMS Note:

DLMS Note: For DLMS use there is no requirement for an action 

code at this time. Reserved for future DLMS use.

F1 File

DLMS Note: Authorized only for DAAS use to provide an 

information only image of the demand data exchange projected 

supply plan transaction to DLA RIC-TO SMS when DLA is not 

the source of supply.

Identifies new 

functional 

requirement.

3. 2LIN02/0100 Add qualifiers and DLMS Note:

FS National Stock Number

SW Stock Number

DLMS Note: Use to identify a local stock number (LSN). 

Supports Navy/DLA 

requirement for 

Navy to be able to 

submit transaction 

using NSN and 

LSNs.

4. 2/PWK/1000 Revise Segment Note 2 and add new Note 3:

DLMS Note:

1. This segment contains free form text which the DDE submitter 

may use to provide information of value to the collaboration

participants. This field may also be used by the submitter to provide 

information deemed useful to their planners during collaboration as 

it will be available for their viewing in the Collaborate tool. This 

segment is optional and informational in nature; the information in 

this segment shall be perpetuated into the Collaborate tool and can 

be viewed by all participants in the collaboration process. DLA will 

perpetuate the information in this segment and it will be visible in 

the online Collaborate tool as a drill down field.

2. On an interim basis, to accommodate DLA’s DIC CDD format in 

a mixed DLMS/non-DLMS CDD environment, the free form text

in the PWK segment is limited to a total of 110 characters which 

maps to DIC CDD Optional fields 1 through 4 in record positions

953-1062. To accommodate DLA DIC CDD fixed format, this 

requires restricting use of PWK segment to a maximum 4 iterations,

with maximum 20 characters each in 3 iterations and maximum of 

50 characters in one iteration. This supports DLA DIC CDD which 

has 3 optional fields of 20 characters and 1 optional field of 50 

characters. Use of PWK segment, other than as described by

this note, is a DLMS enhancement.

Supports Navy 

requirements and 

allows proper 

mapping between a 

DLMS and a CDD 

transaction.
Enclosure 2, ADC 1267

Page 2

3. When providing a Fund Identification Number (2/REF/1400 

Code FG), the first occurrence of 2/PWK02/1000 cannot exceed 

19 characters. Refer to ADC 1267. Use of PWK segment, other 

than as described in notes 2 and 3 is a DLMS enhancement. See 

introductory DLMS note 4a.

5. 2/REF01/1400 Add qualifier FG and DLMS Note:

FG Fund Identification Number 

DLMS Note: For Navy, this is a Program Funding Indicator 

associated to a Gross Demand Plan (GDP). See ADC 1267.

Add to support Navy 

requirements to 

provide a Program 

Funding Indicator 

associated to a 

forecasting 

requirement. 

6. 2/N103/3200 Add DLMS Note to existing qualifier M4:

M4 Department of Defense Routing Identifier Code (RIC)

DLMS Note: 

1. Use with existing code KA.

2. Use RIC-TO SGA when the item manager (source of supply) is 

unknown.

Add clarification to 

use the DAAS RIC 

when the source of 

supply is unknown

7. 2/LQ01/4000 Add qualifier and DLMS Note:

0 Document Identification Code

DLMS Note:

2. Use “CDD” to indicate the data reflects DDE Projected Supply 

Plan requirements. Continued support of the DIC in a full DLMS 

environment will be assessed at a future date.

Identify legacy DIC 

CCD. 

8. 2/FST01/4100 Revise DLMS Note 2:

DLMS Note: 

1. Use up to 60 repetitions in Demand Data Exchange transactions 

to identify the quantity for each interval/bucket.

2. Express quantity as a number with no two decimal places (e.g., 

1.50; 0.50; 0.00).

Allow 2 position 

decimal.

9. 2/FST03/4100 Revise DLMS Notes for existing qualifier M:

M Monthly Bucket (Calendar Months)

DLMS Note:

1. Use to submit up to 5 years (60 months) of projected supply plan 

data. (e.g., for a 5 year projection, 60 monthly buckets will be 

submitted, to include zero entries for plan months with no data; for 

a 3 year projection, 36 monthly buckets will be submitted, to 

include zero entries, etc.). The beginning segment defines the 

projected supply plan period start and end dates (BFR06 and 

BFR07 respectively). The monthly buckets must be provided in 

chronological sequence in the transaction and must include zero 

quantity projections must be included.

2. While DDE projected supply plans can be as short as 12 months, 

DLA recommends that DDE projected supply plans have 60 

Administrative 

update to clarify 

intent for DLMS 

requirement is to 

enter a zero for each 

bucket with no 

forecast quantity, 

not to zero-fill the 

bucket. DLMS does 

not require a 

quantity field to be 

zero-filled.
Enclosure 2, ADC 1267

Page 3

b. Revise 870L DLMS IC as shown: 

Location Change Table for 

870L Demand and Supply Planning Status/Notification

Reason

1. IC Name Change the title of the 870L Implementation Convention

Demand and Supply Planning Special Program Requirements 

(SPR) Status/orNotification

Expand functionality 

of transaction.

2. DLMS

Introductory 

Notes

Add ADC 1267 to DLMS Introductory notes: 

- ADC 1267, Revise DLMS 830D to Accommodate Navy Fleet 

Readiness Centers (FRC) Gross Demand Plan (GDP) for 

Implementation by all DOD Components and GSA.

To identify DLMS 

changes included in 

the implementation 

convention.

3. DLMS 

Introductory 

Notes

Modify existing DLMS Note 1 to 1a and add Note 1b:

DLMS Note:

1a. Inventory Control Points (ICPs) or Integrated Material 

Managers (IMMs) use this transaction set to provide Special 

Program Requirements (SPR) status on SPR requests (corresponds 

to MILSTRAP Document Identifier Code (DIC) DYK 

functionality). DLA Transaction Services Defense Automatic 

Addressing System (DAAS) uses this transaction set to notify the 

organization originating the SPR transaction that the transaction 

was rerouted or that the Federal Supply Classification (FSC) in the 

original transaction was revised (corresponds to MILSTRAP DIC 

DZ9 functionality).

1b. ICPs or IMMs (source of supply) also use this transaction to 

provide status to a forecasting requirement (accept or reject) for a 

Demand Data Exchange (DDE) Projected Gross Demand Plan 

(GDP), or Army Supply Plan (ASP) (DLMS 830D transaction). 

Allows the use of 

this transaction to 

respond to a DLMS 

830D transaction

4. 1/BSR01/20 Add DLMS Note:

9 Response to a Requirement Forecast

DLMS Note:

1. SPR Status. ICP/IMM uses SPR Status transactions to provide 

SPR status to a forecasting activity in response to a DS DLMS 

830R SPR transaction. (MILSTRAP DIC DYK functionality.)

2. For DDE, GDP, ASP status, use to provide status to a 

forecasting requirement in response to DLMS 830D Demand 

Data Exchange Projected Supply Plan transaction.

Allows the use of 

this code to respond 

to a DLMS 830D 

transaction.

months plan periods, citing a 0 ( zero) filling for months with no 

plan.
Enclosure 2, ADC 1267

Page 4

Location Change Table for 

870L Demand and Supply Planning Status/Notification

Reason

5. 1/N101/50 Revise existing DLMS Note for existing :

Z4 Owning Inventory Control Point

DLMS Note:

1. Use to identify the ICP or IMM providing SPR status (BSR01 

Status Report Code 9).

2. Use to identify the source of supply providing DDE, GDP or 

ASP status (BSR01 Status Report Code 9).

Authorizes the use 

of this code to report 

status in response to 

DLMS 830D. 

5. 2/REF01/87 Remove Federal Note and add qualifier FG with DLMS note:

Federal Note: Use any code. 

FG Fund Identification Number

DLMS Note: For Navy use, this is the Program Funding 

Indicator associated to a Gross Demand Plan (GDP). See ADC 

1267.

Add to support Navy 

requirements to 

provide a Program 

Funding Indicator 

associated to a 

forecasting 

requirement.

6. 2/PID/180 Mark Segment PID as “Used” and add the following DLMS note:

DLMS Note:

1. This segment contains free form text which the DDE submitter 

may use to provide information of value to the collaboration

participants. The submitter may also use this segment to provide 

information deemed useful to their planners during collaboration 

as it will be available for their viewing in the Collaborate tool. 

This segment is optional and informational in nature and can be 

viewed by all participants in the collaboration

process.

2. Use to perpetuate optional field information provided by the 

originator via DLMS 830D. See ADC 1267.

3. On an interim basis, to accommodate DLA’s DIC CDD format 

in a mixed DLMS/non-DLMS CDD environment, the free form 

text in the PID segment is limited to a total of 110 characters 

which maps to DIC CDD Optional fields 1 through 4 in record 

positions 953-1062. To accommodate DLA DIC CDD fixed 

format, this requires restricting use of 2/PID/180 segment to a 

maximum of 4 iterations, with maximum 20 characters each in 3 

iterations and maximum of 50 characters in one iteration. This 

supports DLA DIC CDD which has 3 optional fields of 20 

characters and 1 optional field of 50 characters. Use of PID

segment, other than as described by this note, is a DLMS

enhancement. See introductory DLMS note 3a.

Authorize PID 

segment to 

perpetuate optional 

information 

provided by the 

originator via 

DLMS 830D.

7. 2/PID01/180 Mark data element PID01 as “Used” and add qualifier F with 

DLMS Note:

F Free-form

DLMS Note: Use to perpetuate optional information provided by 

the originator via DLMS 830D. See ADC 1267.

Authorize PID 

segment to 

perpetuate optional 

information 

provided by the 

originator via 

DLMS 830D.
Enclosure 2, ADC 1267

Page 5

Location Change Table for 

870L Demand and Supply Planning Status/Notification

Reason

8. 2/PID05/180 Mark data element PID05 as “Used” and add the following DLMS 

Note:

DLMS Note: Use with PID01 to provide narrative information to 

the collaboration participants.

Authorize PID 

segment to 

perpetuate optional 

information 

provided by the 

originator via 

DLMS 830D.

9. 2/LQ01/330 Add the following qualifier code and DLMS note:

DV Demand Planning Status Code

DLMS Note:

1. Local code DV is established for use in the 870L, version 4010. 

A data maintenance action will be submitted to establish ‘DV –

Demand Planning Status Code’ in a future version. 

2. Use to identify the status of a Demand Data Exchange (DDE), 

Gross Demand Plan (GDP), or Army Supply Plan (ASP). See 

DLMS Volume 2, Appendix 13 for a full list of authorized codes. 

See ADC 1267.

Informs the 

originator of a 

confirmation or 

reject by the source 

of supply
Enclosure 3, ADC 1267

Page 1

Enclosure 3 to ADC 1267

Add new DLMS Volume2, Appendix 7.33 as shown:

AP 7.33. APPENDIX 7.33

Demand Planning Status Code

NUMBER OF CHARACTERS: Two

TYPE OF CODE: Alphabetic 

EXPLANATION: Used in response to a Demand Data Exchange (DDE), 

Gross Demand Plan (GDP), or Army Supply Plan 

(ASP) transaction. The status code will report to the 

originator, acceptance or rejection of the forecasting 

request. 

LEGACY MILSTRIP and 

MILSTRAP DOCUMENT 

IDENTIFIER CODE (DIC):

Not Applicable

RECORD POSITION: Not Applicable

DLMS SEGMENT/QUALIFIER: LQ Segment, LQ01 Data Element ID 1270 Qualifier

DV Demand Planning Status Code

CODE EXPLANATION

00 Forecast received; awaiting evaluation.

01 Forecast accepted, processed, and planned.

02 Rejected. Unit of Measure/Unit of Use does not 

match.

03 Rejected. Item does not exist in Source of Supply 

Item Master.

04 Rejected. Nuclear or reparable item. For DLA use 

only.

05 Rejected. Non-stocked item by Source of Supply 

Item.

06 Rejected. Invalid submitter DoDAAC/Sold-To 

DoDAAC combination. DLA managed for Fleet 

Readiness Center (FRC) requirements use only.

07 Reserve for future use.

08 Reserve for future use.
Enclosure 3, ADC 1267

Page 2

CODE EXPLANATION

09 Rejected. Item has future requirements with no 

requisition history within the past 12 months. 

FRC use only.

10 Rejected. Hazardous item. FRC use only.

11 Rejected. Item planned via other business processes 

as agreed upon with Formal Collaborative partners. 

DLA managed items only.

12 Rejected. Item excluded by Supply Chain or Profit 

Center from the Formal Collaborative Process. DLA 

managed items only.

13 Rejected. Item not managed by Source of Supply.