IN REPLY 

REFER TO 

DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

November 02, 2012 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

SUBJECT: Approved Defense Logistics Management System (DLMS) Change (ADC) 1020, 

Inter-Service Ownership Transfer of Ammunition! Ammunition Related Materiel 

(Supply/Logistics) 

The attached change to Defense Logistics Manual (DLM) 4000.25, Defense Logistics 

Management System (DLMS) and DLM 4000.25-1, Military Standard Requisitioning and Issue 

Procedures (MILSTRIP), is approved for implementation March 2013. The updated DLMS 

Supplement will be posted to the DLA Logistics Management Standards Office Web at 

www.dla.mil/j-6/dlmso/elibraTy/TransFormats/140 997.asp within 10 days from the above date. 

Addressees may direct questions to Ms. Ellen Hilert, DOD MILS TRIP Administrator, 

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

MILSTRIP Alternate, 703-767-5111; DSN 427-5111, email heidi.daverede@dla.mil. Others 

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

Attachment 

As stated 

cc: 

ODASD(SCI) 

Pipeline Measurement PRC 

Director 

DLA Logistics Management 

Standards Office 

Federal Recycling Program G Printed on Recycled Paper 
Attachment, ADC 1020

Page 1

Attachment to ADC 1020

Inter-Service Ownership Transfer of 

Ammunition/Ammunition Related Materiel

1. ORIGINATING SERVICE/AGENCY: PEO EIS LMP, (856) 988-6826. 

Change coordinated with Joint Munitions Command (JMC) at focused Defense Connect Online 

(DCO) session with Supply PRC members.

2. FUNCTIONAL AREA:

 a. Primary/Secondary Functional Area: Supply/Logistics 

 b. Primary/Secondary Functional Process: Order Fulfillment/Requisition Processing 

3. REFERENCES:

 a. DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP) 

Manual

 b. DOD 5160.65-M, Single Manager for Conventional Ammunition (Implementation Joint 

Conventional Ammunition Policies and Procedures), cancelled March 16, 2011 and replaced by 

Joint Conventional Ammunition Policies and Procedures (JCAPP)

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

(MILSTRAP)

4. APPROVED CHANGE(S): Significant revisions subsequent to staffing are highlighted in 

green.

 a. Overview of Change: This change documents procedures for the ownership change of 

Single Manager for Conventional Ammunition (SMCA) managed and non-SMCA managed 

materiel ammunition and ammunition-related items only, where there is no shipment or billing 

associated with the ownership change. Existing procedures are identified in this change as well 

as new procedures requiring a deviation from standard MILSTRIP edits at DLA Transaction 

Services. The process discussed in this change employs a combination of Signal Code M (free 

issue) with a supplementary address starting with the non-significant Service/Agency Code Y on 

a referral order or materiel release order to request the change in ownership. A new MILSTRIP 

Category C project code is established to better recognize the process involved. No shipment is 

required because assets for both the losing and gaining Service are located at the same storage 

activity. No billing is required because ammunition is considered non-consumable for financial 

processes.

 b. Background: 

(1) The Joint Munitions and Lethality Command (JM&LC) is responsible for managing 
Attachment, ADC 1020

Page 2

the DOD conventional ammunition as the SMCA. The supply related functions that are 

performed are storage, distribution, packing and preservation of SMCA-assigned conventional 

ammunition and non-SMCA-assigned ammunition stored at SMCA sites.

(2) The guidance for inter-Service ownership transfer of SMCA materiel was originally 

published in DOD 5160.65-M (Reference 3.b.). This manual authorized the use of a 

supplementary address beginning with a non-significant Service/Agency Code Y followed by the 

ownership code for the losing Service on the SMCA-prepared materiel release order. The use of 

the supplementary address for this purpose was never formally coordinated for adoption under 

MILSTRIP, but was successfully processed using a materiel release order (MRO) because of the 

lack of an edit requiring a valid ship-to activity with the use of Signal Code M on the MRO.

 c. Scenario for which the transaction is used: This change of ownership is required for 

“payback” of assets from one Service to another and cross leveling of excess assets between 

Services. This process applies to both SMCA and non-SMCA managed materiels. For SMCA 

materiels, the requesting Service provides a Referral Order to the SMCA supported by the Army 

Logistics Modernization Program (LMP) enterprise resource program, which in turn processes 

an internal MRO to the SMCA storage activity where the assets to be transferred are located. 

For non-SMCA materiels, the owning Service submits an MRO to the storage activity where the 

assets to be transferred are located.

 d. Procedures, transactions, data elements, processing details in use today: Manual offline coordination is required today to accomplish the communication of the referral order 

because it cannot be successfully processed via DLA Transaction Services’ Defense Automatic 

Addressing System (DAAS) using the desired construct because it does not contain a valid shipto DoDAAC in conjunction with signal code M; instead it contains the concatenated data 

elements prefaced with Service/Agency Code Y. Under this change, the JM&LC will be able to 

automate the off-line process that is required when there are separate systems for item 

management and inventory storage. None of the existing Signal Codes adequately represent the 

business process being used, but Signal Code M is the most accurate. There is no billing 

involved in these transactions. Following the guidance for using the supplementary address 

previously implemented for the SMCA MRO, using a Y in rp 45 in conjunction with Signal 

Code M comes closest to fulfilling the business process within a legacy transaction environment. 

 e. Requested change in detail:

(1) Modify DLA Transaction Services’ edits to allow the processing of Service-initiated 

referral orders using project code CYK, Signal Code M, and supplementary 

address/supplemental data that starts with Y (eliminating the requirement for a valid ship to 

address when this combination is used). For DAAS conversion, when used in this combination, 

the value in the legacy supplemental address field will be carried only in the DLMS 

supplementary address/supplemental data field and will not be moved (as normally done for 

Signal Code M) to the ship-to activity.
Attachment, ADC 1020

Page 3

(2) Authorize the use of the supplementary address/supplemental data as a concatenated 

data field for use in a mixed DLMS/legacy environment: 

• First position: Service/Agency Code Y.

• Second position: Old (from) ownership code.

• Third-fifth position: New owner RIC.

• Last position: New/gaining (to) ownership code 

(3) Modify DLMS 511R Requisition, 511M Requisition Modification, 869F Requisition 

Follow-up, 867I Issue, 870S Supply Status, 940R Materiel Release, and 945A Materiel Release 

Advice transactions to support the required discrete data elements needed to communicate a 

request for ownership transfer with no physical shipment of materiel. This will include the new 

owner RIC, the old (from) ownership code, and the new (to) ownership code. Additionally, the 

DLMS supplemental data field is redefined to identify the concatenated data elements 

representing ownership transfer under this process to accommodate processing in a mixed 

DLMS/legacy environment.

(4) Modify Component ammunition systems to initiate inter-Service ownership transfer by 

use of the procedures below. 

(5) Modify LMP to recognize and properly process referral orders using the new 

procedures.

(6) Establish Project Code CYK as a MILSTRIP Category C project code for use in this 

process.

(7) Modify LMP to provide image copies of internal materiel release orders/materiel 

release advice to DLA Transaction Services. The Army is directed to use the specific 

Communications Routing Identifier (COMMRI) RUEOZZH as receiver ID for the images to 

ensure DAAS will recognize image transactions (versus live operational transactions). The 

Army will provide the Document Identifier Code (DIC) applicable to the materiel release 

confirmation image once it is assigned. 

 f. Transaction flow: 

(1) Scenario 1: Non-SMCA-owned/SMCA-managed materiels stored at SMCA 

storage activities.

(a) The Service ammunition Inventory Control Point (ICP) identifies the requirement 

to transfer SMCA-managed assets under its ownership to another military component to meet its

operational requirements. The transfer is to take place at an SMCA storage activity with no 

shipment or billing of materiel required.

(b) The Service ammunition ICP submits a Referral Order (DLMS 511R/Document 

Identifier Code (DIC) A4_) to the SMCA using project code CYK. Information in the 

supplementary address field will contain the old ownership code (from) of the losing service, the

new owner RIC, and the new/gaining ownership code (to) of the receiving service. Signal Code 

M in conjunction with the supplementary address/supplementary data beginning with Y indicates 
Attachment, ADC 1020

Page 4

no shipping/no billing. Services shall utilize Media & Status (M&S) codes to ensure follow on 

status is not provided to the supplementary address (example M&S Code B). The legacy 

MILSTRIP supplementary address will be perpetuated in the DLMS 511R if conversion is 

required. DAAS conversion mapping for DLMS enhancements will also map the data elements 

that comprise the supplementary address to the appropriate DLMS data elements.

(c) Upon approval by the SMCA, an internal Materiel Release Order (MRO) to the 

SMCA storage activity is processed to change the owner of the inventory and ownership code to 

the identified gaining service. An internal materiel release confirmation is provided to the 

SMCA and an image transaction transmitted to DLA Transaction Services. Standard status, 

issue, and receipt transactions (DLMS 870S/DIC AE_, DLMS 867I/DIC D7_, and DLMS 

527R/DIC D6_, DIC BG1/BG2) are sent to the losing and gaining activities.

(2) Scenario 2: Non-SMCA-owned/managed materiels stored at SMCA storage 

activities.

(a) The owning Service ICP identifies the requirement to transfer non-SMCA-managed 

assets under their ownership to another military component to meet their operational 

requirements. The transfer is to take place at a SMCA storage activity, with no shipment or 

billing of materiel required.

(b) The owning Service submits an MRO (DLMS 940R/DIC A5_) to the SMCA 

storage activity to change the owner of the inventory and ownership code to the identified 

gaining service. Information in the supplementary address field will contain the old ownership 

code (from) of the losing service, the new owner RIC, and the new/gaining ownership code (to) 

of the receiving service. Use of Signal Code M in conjunction with the supplementary 

address/supplementary data beginning with Y indicates no shipping/no billing. The legacy 

MILSTRIP supplementary address will be perpetuated into the DLMS 940R if conversion is 

required. DAAS conversion mapping for DLMS enhancements will also map the data elements 

that comprise the supplementary address to the appropriate DLMS data elements. Standard 

status, issue, and shipping transactions (DLMS 870S/DIC AE_, DLMS 945A/Materiel Release 

Advice/DIC AR_, and DIC BG1/BG2) are sent to the losing and gaining activities. Staffing 

Note: Inclusion of DIC BG1/BG2 in the DLMS 945A is a DLMS enhancement currently being 

staffed under PDC 1040, Migrate Inter-Service Ammunition Serial Number and Lot Number 

Transactions (NAVSUP P-724 BG 1/BG2) to DLMS 945A Materiel Release Advice.

(3) Scenario 3: SMCA-owned/managed materiels in SMCA storage activity.

(a) SMCA identifies the requirement to transfer SMCA-managed assets under SMCA 

ownership to or from another military component to meet their operational requirements. The 

transfer is to take place at a SMCA storage activity, with no shipment or billing of materiel 

required.

(b) The SMCA initiates an Inventory Adjustment - Dual (Ownership Transfer) (DLMs 

947I/DIC DAS) transaction for processing internal adjustments to custodial/accountable records 

and for notification of SMCA storage activity. Inventory adjustment transactions (DLMS 
Attachment, ADC 1020

Page 5

947I/DIC D8S/D9S) are prepared and sent to the losing and gaining activities. These procedures 

are authorized under MILSTRAP (see Reference 3.c., Chapter 5).

 g. Revisions to DLM 4000.25 series of Manuals: The following revisions apply to DLM 

4000.25-1, MILSTRIP, and DLM 4000.25, DLMS. Paragraph numbering shown below applies 

to the legacy MILSTRIP manual for comparable placement in the DLMS manual.

(1) Update MILSTRIP procedures for the preparation of referral orders as follows:

“C.3.19.4. Inter-Service Ownership Transfer of Ammunition/Ammunition-related Materiel. 

When used for Service-initiated inter-Service ownership transfers of Single Manager for 

Conventional Ammunition (SMCA) ammunition and ammunition related materiel with no 

physical movement of materiel or billing, the initiating referral order shall cite Project Code 

CYK and Signal Code M indicating a free issue, in conjunction with the additional data 

required to accomplish the transfer. This includes the old (from) ownership code associated 

with the service transferring ownership, the RIC of the Service receiving ownership, and the 

new/gaining (to) ownership code associated with the Service receiving ownership. Pending 

transition to DLMS discrete data enhancements, the ownership to/from and new owner RIC 

will be identified in the supplementary address/supplemental data field beginning with 

Service/Agency Code Y (see Appendix 2.9, Supplementary Address/Supplemental Data, for 

proper sequencing of these data elements into a single, concatenated field). The referral order 

will include an M&S code or distribution code ensuring follow-on status is directed 

appropriately (e.g., M&S Code B); do not designate status to the supplementary address. No 

shipment status will be provided.”

(2) Update MILSTRIP procedures for MRO as follows:

“C3.15.3. Inter-Service Ownership Transfer of Ammunition/Ammunition-related Materiel.

When used for inter-Service ownership transfers of non-Single Manager for Conventional 

Ammunition (SMCA) owned ammunition and ammunition-related materiel stored in a SMCA

storage facility with no physical movement of materiel or billing, the MRO shall contain 

Signal Code M indicating a free issue. The MRO shall also include the associated data 

required to accomplish the transfer including the old (from) ownership code associated with 

the service transferring ownership, the RIC of the Service receiving ownership, and the 

new/gaining (to) ownership code associated with the Service receiving ownership. Pending

transition to DLMS discrete data enhancements, the ownership to/from and new owner RIC 

will be identified in the supplementary address/supplemental data field beginning with 

Service/Agency Code Y (see the Appendix 2.9, Supplementary Address/Supplemental Data, for 

proper sequencing of these data elements into a single, concatenated field). The storage 

activity will update the custodial/accountable records for the materiel and quantity identified 

to reflect the new ownership code and RIC of the Service receiving ownership. No shipment 

status will be provided. See MILSTRAP procedures (DLM 4000.25-2, Chapter 7) for interService ownership transfer initiated by the SMCA for SMCA-owned materiel.”

(3) Replace DLM 4000.25-1; Appendix AP 2.9, Supplementary Address, with DLMS

guidance for Supplementary Address/Supplemental data as shown at Enclosure 1.
Attachment, ADC 1020

Page 6

(4) Revise DLM 4000.25-1; Appendix AP 2.10, Signal Codes, as follows:

“AP2.10.2.2. When the materiel is to be shipped to the activity indicated in rp 45-50, the 

signal code shall be as follows:

AP2.10.2.2.1. Code J - Bill to the activity in rp 30-35.

AP2.10.2.2.2. Code K - Bill to the activity in rp 45-50.

AP2.10.2.2.3. Code L - Bill to the activity in rp 52 and 53.

AP2.10.2.2.4. Code M - No billing required - free issue. (Not to be used by DoD 

activities when submitting requisitions on GSA.) When used to identify ownership transfer of 

ammunition and ammunition-related materiel with no physical movement of materiel or 

billing, Signal Code M is used in conjunction with the supplementary address/supplemental 

data field beginning with Service/Agency Code Y and will not require inclusion of a valid shipto DoDAAC.

1

 

AP2.10.2.2.5. Code X - (For intra-Service use only.)

________________

1 Upon transition to DLMS discrete data enhancements this process will also require separate 

identification of the applicable ownership codes (to/from) and the new owner RIC. Refer to 

ADC 1020.”

(5) Revise DLM 4000.25-1; Appendix 3.24, Referral Order/Lateral Redistribution Order 

for Retail Assets as shown at Enclosure 2.

(6) Revise DLMS Supplements 511R, 511M, 867I, 869F, 870S, 940R, 945A as shown at 

Enclosure 

(7) Update MILSTRIP Service/Agency Code (Appendix AP2.2) as follows.

SERVICE CODES

CODE 4 5 30 31 45 46 67 68 74 75 S/A REMARKS

Y Y1 Reserved (Nonsignificant) See Footnote

----------------- 1 Identifies Security Assistance Grant Aid when used in a Security Assistance requisition (as 

designated by rp 30). Otherwise, considered nonsignificant except by coordinated prior 

agreement or authorized procedures for inter-Service ownership transfer of 

ammunition/ammunition-related materiel. See MILSTRIP Appendix 2.9 for details.

(8) Update MILSTRIP Category C and D Project Code Master List to reflect Project 

Code CYK:
Attachment, ADC 1020

Page 7

CYK

Service

Codes:

All

01 Nov 12 to 

Continuing

Use on referral orders to identify 

inter-Service ownership transfers of 

non-Single Manager for 

Conventional Ammunition (SMCA)–

owned/SMCA-managed ammunition 

and ammunition related materiel 

located in an SMCA storage activity 

with no physical movement of 

materiel and no associated billing. 

DoD MILSTRIP Administrator

Comm 703.767.0600

(See DLM 4000.25-1)

h. Alternatives:

 (1) None identified for near-term implementation. If an alternate procedure is required 

to be performed, functional changes would be required to several legacy systems. Although not 

requested by the PDC initiator, the DLMS breakdown of the required data elements is provided 

as an alternative to the legacy concatenation of separate data elements within the supplementary 

address. 

 (2) Use of existing multi-use management data fields in the legacy MILSTRIP referral 

order format was considered. However, local system changes would have to be implemented by 

other services, as well as Army LMP, to utilize the management data fields on the MILSTRIP 

DIC A4_ itself to request an inter-Service inventory ownership change. Use of the 

supplementary address field does not require immediate system changes by other Services and 

will allow a transition period for implementation of discrete data fields by DLMS-compliant 

applications. 

 (3) Also explored was a policy change to expand the use of the current SMCA 

exception for use of the dual inventory adjustment for ownership change directed by the owning 

Service (rather than the JM&L). MILSTRAP (Reference 3.c) procedures state that changes 

between ownership codes will not be made by an adjustment action. The applicable storage 

activity must process appropriate issue and receipt transactions to make the necessary accounting 

actions. An exception to this rule is the use of the dual Inventory Adjustment Transaction to 

affect ownership gain/loss under the SMCA concept. However, the Joint Service ammunition 

community believes that the use of inventory adjustment transactions (DLMS 947I, DIC 

D8S/D9S) for SMCA managed items is only allowed to be initiated by JM&L as the SMCA 

manager. The use of issue and receipt transactions, is used for ownership changes initiated by 

the other Services. In the scenario described in the DLMS Change, the DIC A4_ is initiated by 

the other Service owner to advise JM&L (as SMCA manager) to transfer ownership for SMCAmanaged items. 

5. REASON FOR CHANGE: 

a. At this time not all participating users are capable of generating DLMS referral orders. 

Army LMP is DLMS-capable, but cannot make the necessary changes to the DLMS input/output 

formats without significant lead time. Therefore, transaction rules support legacy formats and 

DAAS conversion requirements for use during transition to DLMS.

b. A DLA Transaction Services edit change is needed to allow the processing of Service-
Attachment, ADC 1020

Page 8

initiated referral orders using Signal Code M, and a supplementary address/supplemental data 

that starts with Y (rather than a valid ship-to DoDAAC) when requesting ownership transfer with 

no billing and no physical movement of ammunition/ammunition related materiel.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: 

(1) Facilitates logistics processing of ammunition business practice to use referral 

orders to initiate a transfer of SMCA-managed assets under their ownership to another military 

component to meet their operational requirements. The transfer is to take place at an SMCA 

storage activity, with no shipment or billing of materiel required.

(2) Documents existing SMCA processing rules, not previously addressed under 

MILSTRIP.

(3) Transmission of image copies of internal LMP release order will ensure Enterprise 

visibility and inclusion as applicable within pipeline metrics.

(4) Project Code CYK was previously assigned by the SMCA for use in ordering 

ammunition and ammunition related materiel and was partially implemented. Rather than 

assigning a new 3-series MILSTRIP Category C project code, this change leverages the existing 

code reducing the programming/training impact. 

(5) The dedicated MILSTRIP project code for this process enables a DAAS edit based 

upon the appropriate combination of transaction data, while restricting use of the Signal Code M 

without a valid ship-to location to this use. 

b. Disadvantages: None identified.

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

DEVELOPMENT: The project code assigned for recognition of this process is applicable to 

the referral order and will be perpetuated to subsequent transactions. However, when the 

combination of Signal Code M and supplementary address/supplementary data beginning with Y 

is employed in Scenario 2 and Scenario 3 described in the transaction flows (paragraph 4.f) the

Project Code CYK is not included in the MRO. 

8. ADDITIONAL FUNCTIONAL REQUIREMENTS: Currently, LMP processes internal 

transactions equivalent to the materiel release orders (DLMS 940R) and materiel release advice 

(DLMS 945A). Because these transactions are not processed through the DLA Transaction 

Services DAAS, there is no enterprise visibility. DOD pipeline metrics cannot be accumulated 

under Logistics Metric Analysis Reporting System (LMARS) (as required when the release 

order/confirmation is associated with physical movement of materiel). To correct this situation, 

LMP shall provide image transactions to DLA Transaction Services. While there is no shipment 

status transaction, when LMARS gets the receipt transaction, it will go back and compute the 

applicable segments (DAAS, ICP, storage activity, and receipt take-up). Refer to Enclosure 3 for 

minor revisions to the DLMS notes in these two transactions.
Attachment, ADC 1020

Page 9

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: DAAS implementation of 

the edit revision to allow the use of Signal Code M without a valid ship-to address (in 

conjunction with Project Code CYK and Service/Agency Code Y supplementary 

address/supplemental data) is required for initial testing/implementation. Implementation is 

requested in 2013, with partner testing currently scheduled for the March 2013 timeframe.

Phased implementation is authorized for Army LMP for all elements of this change including use 

of the discrete data fields and transmission of image transactions. Staggered implementation is 

authorized for Services transitioning from legacy to DLMS procedures. 

"IGC requests a 90 day period between the time this ADC is approved and when it can be 

implemented by systems using it to create transactions. This time is needed to code our system to 

accept the changes described in the ADC".

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None identified.

11. IMPACT: 

a. New DLMS Data Elements: The data element “new owner RIC” will be established 

as a variant of the existing data element RIC.

b. Changes to DLMS Data Elements: The existing data elements “old ownership code 

(from)” and “ownership code (to)” (where not previously included) will be available for use in 

the DLMS 511R, 511M, 867I, 869F, 870S, 940R, and 945A. There is no shipment status 

provided for this process. 

c. Automated Information System (AIS):

(1) Component systems submitting referral orders for ammunition/ammunition-related 

materiels to initiate ownership transfer to another Component without physical shipment shall:

(a) ensure near-term capability to construct the supplementary address as 

indicated in this DLMS change,

(b) develop modifications as required for DLMS-compliant applications to 

support use of discrete data fields as shown in Enclosure 3. 

(2) Army LMP supporting the JM&LC and associated storage activities shall:

(a) implement capability to interpret the legacy supplementary address 

concatenated format for near-term implementation,

(b) develop modifications for capture and transmission of DLMS-compliant

transactions using discrete data fields as shown in Enclosure 3. 
Attachment, ADC 1020

Page 10

(c) provide DLMS transaction image (file copy) of materiel release order and 

materiel release advice to DLA Transaction Services. To ensure DAAS interpretation as an 

image and not an active transaction, LMP must direct this transaction to the DLA Transaction 

Services (Communications Routing Identifier (COMMRI) RUEOZZH).

d. DLA Transaction Services:

(1) Modify DAAS edits to allow use of Signal Code M with a supplementary 

address/supplemental data beginning with Service/Agency Code Y in conjunction with Project 

Code CYK for ammunition/ammunition-related materiels used on referral orders submitted via 

DLMS or legacy format (DLMS 511R (DIC A4_)). The DAAS edit revision is also applicable 

to the DLMS 511M (DIC AM_), Requisition Modification, and DLMS 869F (DIC AT_), 

Requisition Follow-up. Although the data combination is perpetuated in subsequent 

transactions, no DAAS edit applies to these.

(2) Modify DAAS conversion maps to support conversion capability from the 

concatenated legacy supplementary address to the discrete DLMS data elements. When 

separated into discrete data fields, the original concatenated data construct will be retained in the 

supplementary data field of the DLMS transaction.

(3) Modify WebVLIPS to display data fields for Ownership Code-To, Ownership 

Code-From, and New Owner RIC.

(4) Use file images originated in the DLMS formatted materiel release order and 

materiel release advice for preparation of LMARS pipeline metrics. There is no physical 

movement involved in ownership transfers identified by Signal Code M and Y-series 

supplementary address/supplemental data; therefore, LMP does not provide a “pseudo” shipment 

status as part of this process. Transportation segments will not be computed. When LMARS 

receives the receipt transaction, it will then compute the segments and the Total Pipeline Time 

based on available data. 

Staffing Note on Pipeline Measurement: 

• Further study is required by the Pipeline Measurement PRC to evaluate impact on the 

receipt take-up time metric (when based upon a receipt where no physical shipment occurs). 

In addition to the procedures prescribed under this change, there are multiple operational 

scenarios where receipt is provided instantaneously because no movement has occurred. 

When a DLA Distribution Depot is the storage activity, a shipment status is provided, but 

various mapping approaches are used in the MRO sent to the DLA Distribution Standard 

System to trigger the ownership change with shipment/receipt in place. Consideration should 

be given to identifying when the ship-in-place scenario applies so that the metrics are not 

distorted by the immediate nature of the receipt. 

• DLA Transaction Services has indicated that the use of the supplementary address 

beginning with Y/lack of a ship-to DoDAAC will prevent determination of the applicable

area within LMARS. Consideration should be given to identifying the ship-in-place scenario 

and using the storage activity to determine the area (the storage activity processing the

release order and the receipt are the same so could be used to identify the applicable area). 
Attachment, ADC 1020

Page 11

e. Non-DLA Logistics Management Standards Publications: Requires revisions to 

JCAPP and any applicable internal Component guidance.
Enclosure 1, ADC 1020

Page 1

Enclosure 1, MILSTRIP Manual Appendix Revisions

Replace Appendix 2.9 in its entirety. This enclosure contains numerous administrative updates 

to the MILSTRIP appendix to clarify usage under DLMS and during a mixed legacy 

format/DLMS environment. Only those updates specific to the usage and concatenated data

requested by this ADC are shown in red italics. 

AP2.9. APPENDIX 2.9

SUPPLEMENTARY ADDRESS/SUPPLEMENTAL DATA

AP2.9.1. The supplementary address (SUPADD)/supplemental data field is a multi-purpose data 

element. Usage rules vary for U.S. Forces and Security Assistance, by the intent of the 

transaction originator, as well as based upon the transaction format (legacy MILSTRIP vs. 

DLMS) used to communicate the information. Regardless of usage or format, the originator’s 

SUPADD/supplementary data shall be perpetuated in all subsequent transactions and 

documentation.

AP2.9.2. U.S. Forces

AP2.9.2.1. Under legacy MILSTRIP, the SUPADD (located in rp 45-50) in transactions 

for support of U.S. Forces, when significant, will contain a DoD activity address code 

(DoDAAC). The entry in the first position (Service) or first and second position (Federal

Agency, if numeric-numeric, or special program activity, if numeric-alpha) shall always be the 

appropriate character(s) identifying the Service/Agency (S/A) or program (see Appendix 2.2. 

Service and Agency Codes). The DoDAAC shall be established in the authoritative DLA 

Transaction Services DoD Activity Address Directory (DoDAAD) database by S/A designated 

DoDAAD Central Service Points for dissemination in a variety of formats. Each code so 

established will contain address(es) in detail to permit the shipping and billing of materiel. (See 

the DLM 4000.25, Volume 6, Chapter 2, DoD Activity Address Directory (DoDAAD).)

Service/Agency

Activity Address Code

45 46 47 48 49 50

AP2.9.2.2. Under DLMS, the SUPADD shall be replaced by a generic supplemental data 

field. DoDAACs provided for the purpose of identifying a ship-to and/or bill-to activity are 

carried as discrete data elements in the DLMS transaction address segment with specific data

qualifiers indicating the exact purpose. 

AP2.9.2.2.1. In a mixed legacy/DLMS environment, the supplemental data field 

is used to perpetuate/populate the legacy MILSTRIP SUPADD. During this time, field size for 

the supplemental data field is restricted to 6 positions. When containing a DoDAAC, the value 
Enclosure 1, ADC 1020

Page 2

carried in the supplemental data field must also be repeated in the applicable DLMS address 

segment to identify the ship-to/bill-to activity.

AP2.9.2.2.2. Under full DLMS, the requirement to pass activity address 

information within the supplement data shall be terminated and the supplementary data field will 

be used for miscellaneous data only. Under full DLMS, the field length shall be expanded to 30 

positions. 

AP2.9.2.3. Non-significant Supplemental Data. The Service/Agency Code Y in the first 

position shall be used to denote that the field is being used for data rather than a ship-to/bill-to 

DoDAAC. When the originator of the transaction uses the SUPADD/supplemental data field for 

data rather than addressing, the entry shall be considered non-significant to the receiving activity 

except by coordinated prior agreement or authorized procedures for inter-Service ownership 

transfer of ammunition/ammunition-related materiel. 

AP2.9.2.4. Inter-Service Ownership Transfer of Ammunition/Ammunition-related 

Materiel 

AP2.9.2.4.1 When used for inter-Service ownership transfer of ammunition or 

ammunition-related materiel located in a Single Manager for Conventional Ammunition 

(SMCA) storage activity where no physical movement of materiel or billing applies, the

Referral Order (DLMS 511R/DIC A4_) shall cite Signal Code M and Project Code CYK in 

conjunction with a SUPADD/supplemental data field beginning with Service/Agency Code Y 

(a ship-to DoDAAC is not applicable). In a mixed DLMS/legacy environment, the required 

additional data content to support this process will be concatenated in the 

SUPADD/supplemental data field as follows: 

• First position: Service/Agency Code Y

• Second position: Old (from) ownership code

• Third-fifth position: New owner RIC

• Last position: New/gaining (to) ownership code

AP2.9.2.4.2 Materiel release orders (MROs) (DLMS 940R/DIC A5_) directed to 

an SMCA storage activity for inter-Service transfer of ammunition or ammunition-related 

materiel with no physical movement or billing will cite the SUPADD/supplemental data 

constructed as in AP2.9.4.1 in combination with Signal Code M. All subsequent transactions 

will perpetuate this construct. 

AP2.9.2.4.3 Under DLMS, the originating system will also provide the discrete 

data elements where applicable, mirroring those contained in the supplemental data. This 

redundancy will be retained until all parties are using DLMS and the supplemental data field 

may be repurposed for unrelated information. 
Enclosure 1, ADC 1020

Page 3

AP2.9.2.5. When the first position of the document number contains a valid S/A alpha 

designator and the first position of the SUPADD/data field contains a zero (0), DAAS shall 

change the zero (0) to Y.

AP2.9.3. Security Assistance 

AP2.9.3.1. For Security Assistance transactions, the legacy MILSTRIP SUPADD, as 

well as the mixed environment DLMS supplemental data field, is used for a concatenation of 

multiple distinct data elements. 

AP2.9.3.1.1. For Foreign Military Sales (FMS), the first position (legacy format 

rp 45) shall contain the in-country Service designating the military service within the Security 

Assistance customer country. For Grant Aid, the first position shall contain Service/Agency 

Code Y. Note that the Y is subsequently converted to an X for establishment of the applicable

Military Assistance Program Address Code (MAPAC).

AP2.9.3.1.2. The contents of the remaining positions vary for both FMS and 

Grant Aid, according to the Security Assistance country and the originator’s intent. (See 

MILSTRIP Chapter 6 and AP3.03 or DLM 4000.25, Volume 6, Chapter 3, Military Assistance 

Program Address Directory (MAPAD), for detailed guidance.)

AP2.9.3.2. In a mixed legacy/DLMS environment, the supplemental data field shall be 

interpreted during DLA Transaction Services’ DAAS processing and separated into its discrete 

data elements for transmission to DLMS-compliant applications. Under full DLMS, the 

originating system shall provide the discrete data elements applicable to the transaction

including: customer within country code, offer and release option code, FMS case number, 

program line number, record control number.
Enclosure 2, ADC 1020

Page 1

Enclosure 2, Referral Order Legacy Format

Changes associated with this DLMS change are shown in red, italics.

AP3.24. APPENDIX 3.24

REFFERRAL ORDER/LATERAL REDISTRIBUTION ORDER FOR RETAIL ASSETS

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier Code 1-3 Enter DIC A4_.

Routing Identifier Code 4-6 Enter RIC of the supply source activity to 

which the transaction is being sent.

---------------------------

Supplementary Address 45-50 Enter data from the original requisition.1

 1 When used on a referral order to initiate an inter-Service ammunition-related ownership transfer with no 

physical movement of materiel and no billing, cite Signal Code M and Project Code CYK in conjunction with the 

supplementary address constructed as follows: Service/Agency Code Y followed by the old (from) ownership 

code, the RIC to which ownership is transferred, and the new/gaining (to) ownership code. Refer to ADC 1020.
Enclosure 3, ADC 1020

Page 1

Enclosure 3, DLMS Supplement Revisions

a. Revise DLMS 511M as follows:

Item # Location 511M, Requisition Modification 

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1020 to DLMS Introductory notes:

- ADC 1020, Inter-Service Ownership Transfer of Ammunition/ 

Ammunition Related Materiel

Identifies DLMS 

Changes included in 

the DLMS Supplement

2. 2/PO104/30 Add additional DLMS note to existing data element:

Unit Price

DLMS Note:

1. For nonreimbursable materiel (free issue), indicate 0 dollars. Use with 

P0105 Code NC, No Charge. DLMS migration enhancement. This 

usage is comparable to Signal Code D or M.

2. Use for nonstandard materiel to indicate an estimated price.

3. Estimated unit price for nonstandard materiel is a DLMS 

enhancement, see introductory note 3a.

3. For intra-Air Force, the unit price will be perpetuated to the 

requisition modifier.

4. DLMS transactions authorize an expanded unit price field size of 9 

digits for dollars and 2 digits for cents. The decimal point is passed in 

the transaction. If conversion to MILS legacy format is required, unit 

prices exceeding the legacy field size constraint will not be perpetuated. 

Authorized DLMS migration enhancement. Refer to ADC 221A.

Administrative update 

for clarification.

3. 2/PO105/30 Add additional DLMS note to existing data element:

Basis of Unit Price Code

DLMS Note: 

Use for nonstandard and nonreimbursable (free issue) materiel. For 

nonstandard materiel, use to identify an estimated unit price.

NC No Charge

DLMS Note:

Use to indicate nonreimbursable (free issue) materiel. DLMS migration 

enhancement. This usage is comparable to Signal Code D or M.

Administrative update 

for clarification.
Enclosure 3, ADC 1020

Page 2

Item # Location 511M, Requisition Modification 

Revision

Reason

4. 2/LQ01/140 Add new Qualifier RD and new DLMS note 2 for existing Qualifier A1:

A1 Ownership Code

DLMS Note:

1. Use in requisition or referral order to identify the ownership of 

previously purchased materiel. This is a restricted use applicable when 

a Service has entered into an MOA with DLA relative to Service-owned 

stocks, centrally-managed/stored by DLA (1BR06/020, Code RI).

2. Use on a referral order to initiate an inter-Service ammunition or 

ammunition-related ownership transfer with no physical movement of 

materiel. Use to identify the new/gaining (to) ownership code. DLMS 

enhancement. Refer to ADC 1020.

3. Also authorized on an intra-Army basis with BR02 Transaction 

Type Code A0 and BR06 Action Code J for identification of the 

ownership of materiel post-post issued by Army Single Stock Fund 

activities.

RD Property Ownership Type Code

DLMS Note:

Use only on a referral order modification to initiate an inter-Service 

ammunition or ammunition-related ownership transfer with no 

physical movement of materiel. Use to identify, or to modify, the old 

(from) ownership code. DLMS enhancement. Refer to ADC 1020.

Provides DLMS 

capability to distinctly 

identify the old and 

new ownership codes 

for DLMS compliant 

applications.

Identifies these fields 

as modifiable.

5. 2/LQ01/140 Revise DLMS notes as shown:

A9 Supplemental Data

DLMS Note:

1. Use to identify, or to modify, supplemental supplementary

address/supplemental data.

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

perpetuate/populate the DLSS Supplemented Supplementary Address 

(SUPADD) field. During this time, field size is restricted to 6 positions; 

see introductory DLMS note 3d.

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

restriction is a DLMS enhancement; see introductory DLMS note 3a.

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

information within the supplemental data field will be streamlined. 

Activity address data previously contained in the SUPADD will be 

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

introductory DLMS note 3c.

5. During DLSS/DLMS transition, use on a referral order 

modification to initiate an inter-Service ammunition or ammunitionrelated ownership transfer with no physical movement of materiel and 

no billing. Cite Signal Code M and Project Code CYK in conjunction 

with the supplemental data field constructed as follows: 

Service/Agency Code Y followed by the old (from) ownership code, the 

RIC to which ownership is transferred, and the new/gaining (to) 

Administrative updates 

and clarification of 

usage. 

The DLMS 

Supplement guidance 

for inclusion of 

supplementary 

address/supplemental 

data describes 

redundant 

functionality during 

mixed DLSS/DLMS 

transition period. This 

is intended to 

minimize impact on 

implementing systems. 
Enclosure 3, ADC 1020

Page 3

Item # Location 511M, Requisition Modification 

Revision

Reason

ownership code. Refer to ADC 1020.

6. 2/N101/180 Add new Qualifier UQ and associated notes:

UQ Subsequent Owner

DLMS Note:

Use only on a referral order modification to initiate an inter-Service 

ammunition or ammunition-related ownership transfer with no 

physical movement of materiel. Use to identify, or to modify, the RIC 

to which ownership is being transferred (the New Owner RIC). DLMS 

enhancement. Refer to ADC 1020.

Provides DLMS 

capability to distinctly 

identify the new owner 

RIC for DLMS 

compliant 

applications.

b. Revise DLMS 511R as follows:

Item # Location 511R, Requisition 

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1020 to DLMS Introductory notes:

- ADC 1020, Inter-Service Ownership Transfer of Ammunition/ 

Ammunition Related Materiel

Identifies DLMS 

Changes included in 

the DLMS Supplement

2. 2/PO104/30 Add additional DLMS note to existing data element:

Unit Price

DLMS Note:

1. For nonreimbursable materiel (free issue), indicate 0 dollars. Use with 

P0105 Code NC, No Charge. DLMS migration enhancement. This 

usage is comparable to Signal Code D or M.

2. Use for nonstandard materiel to indicate an estimated price.

3. Estimated unit price for nonstandard materiel is a DLMS enhancement, 

see introductory note 3a.

3. Use for DoD EMALL/part-numbered catalog orders to specify the 

contract price and the billed price. Must use a second repetition of the 

PO1 segment to identify second price.

4. DLMS transactions authorize an expanded unit price field size of 9 

digits for dollars and 2 digits for cents. The decimal point is passed in 

the transaction. If conversion to MILS legacy format is required, unit 

prices exceeding the legacy field size constraint will not be perpetuated. 

Authorized DLMS migration enhancement. Refer to ADC 221A.

Administrative update 

for clarification.
Enclosure 3, ADC 1020

Page 4

Item # Location 511R, Requisition 

Revision

Reason

3. 2/PO105/30 Add additional DLMS note to existing data element:

Basis of Unit Price Code

DLMS Note: Use for nonstandard and nonreimbursable (free issue) 

materiel. For nonstandard materiel, use to identify an estimated unit 

price.

NC No Charge

DLMS Note:

Use to indicate nonreimbursable (free issue) materiel. DLMS migration 

enhancement. This usage is comparable to Signal Code D or M.

Administrative update 

for clarification.

4. 2/LQ01/140 Add new Qualifier RD and new DLMS note 2 for existing Qualifier A1:

A1 Ownership Code

DLMS Note:

1. Use in requisition or referral order to identify the ownership of 

previously purchased materiel. This is a restricted use applicable when 

a Service has entered into an MOA with DLA relative to Service-owned 

stocks, centrally-managed/stored by DLA (1BR06/020, Code RI).

2. Use on a referral order to initiate an inter-Service ammunition or 

ammunition-related ownership transfer with no physical movement of 

materiel. Use to identify the new/gaining (to) ownership code. DLMS 

enhancement. Refer to ADC 1020.

3. Also authorized on an intra-Army basis with BR02 Transaction 

Type Code A0 and BR06 Action Code J for identification of the 

ownership of materiel post-post issued by Army Single Stock Fund 

activities.

RD Property Ownership Type Code

DLMS Note:

Use only on a referral order to initiate an inter-Service ammunition or 

ammunition-related ownership transfer with no physical movement of 

materiel. Use to identify the old (from) ownership code. DLMS 

enhancement. Refer to ADC 1020.

Provides DLMS 

capability to distinctly 

identify the old and 

new ownership codes 

for DLMS compliant 

applications.

5. Revise DLMS notes as shown:

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental supplementary address/supplemental 

data.

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

perpetuate/populate the DLSS Supplemented Supplementary Address 

(SUPADD) field. During this time, field size is restricted to 6 positions; 

see introductory DLMS note 3d.

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

restriction is a DLMS enhancement; see introductory DLMS note 3a.

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

Administrative updates 

and clarification of 

usage. 

The DLMS 

Supplement guidance 

for inclusion of 

supplementary 

address/supplemental 

data describes 

redundant functionality 

during mixed 

DLSS/DLMS 
Enclosure 3, ADC 1020

Page 5

Item # Location 511R, Requisition 

Revision

Reason

within the supplemental data field will be streamlined. Activity address 

data previously contained in the SUPADD will be reflected exclusively 

in the N1 segment. Future streamlined data; see introductory DLMS note 

3c.

5. During DLSS/DLMS transition, use on a referral order to initiate an 

inter-Service ammunition or ammunition-related ownership transfer 

with no physical movement of materiel and no billing. Cite Signal 

Code M and Project Code CYK in conjunction with the supplemental 

data field constructed as follows: Service/Agency Code Y followed by 

the old (from) ownership code, the RIC to which ownership is 

transferred, and the new/gaining (to) ownership code. Refer to ADC 

1020.

transition period. This 

is intended to minimize 

impact on 

implementing systems. 

6. 2/N101/180 Add new Qualifier UQ and associated notes:

UQ Subsequent Owner

DLMS Note:

Use only on a referral order to initiate an inter-Service ammunition or 

ammunition-related ownership transfer with no physical movement of 

materiel. Use to identify the RIC to which ownership is being 

transferred (the New Owner RIC). DLMS enhancement. Refer to 

ADC 1020.

Provides DLMS 

capability to distinctly 

identify the new owner 

RIC for DLMS 

compliant applications.
Enclosure 3, ADC 1020

Page 6

c. Revise DLMS 867I as follows:

Item # Location DLMS 867I Issue

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1020 to DLMS Introductory notes:

- ADC 1020, Inter-Service Ownership Transfer of Ammunition/ 

Ammunition Related Materiel

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/N101/50 Add new Qualifier UQ and associated notes:

UQ Subsequent Owner

DLMS Note:

Use for inter-Service ammunition or ammunition-related ownership 

transfer with no physical movement of materiel. Use to identify the 

RIC to which ownership is being transferred (the New Owner RIC). 

DLMS enhancement. Refer to ADC 1020.

Provides DLMS 

capability to distinctly 

identify the new owner 

RIC for DLMS 

compliant applications.

3. 2/LQ01/270 Add DLMS note for existing Qualifier A1 and add new Qualifier RD 

and associated note:

A1 Ownership Code

DLMS Note:

When used for inter-Service ammunition-related ownership transfer 

with no physical movement of materiel, use to identify the 

new/gaining (to) ownership code. Refer to ADC 1020.

RD Property Ownership Type Code

DLMS Note:

Use only for inter-Service ammunition-related ownership transfer 

with no physical movement of materiel. Use to identify the old 

(from) ownership code. DLMS enhancement. Refer to ADC 1020.

Provides DLMS 

capability to distinctly 

identify the old and 

new ownership codes 

for DLMS compliant 

applications.

4. 2/LQ01/270 Revise DLMS notes as shown:

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental supplementary address/supplemental 

data.

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

perpetuate/populate the DLSS Supplementary Address (SUPADD) 

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

introductory DLMS note 3d.

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

restriction is a DLMS enhancement; see introductory DLMS note 

3a.

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

information within the supplemental data field will be streamlined. 

Activity address data previously contained in the SUPADD will be 

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

introductory DLMS note 5c.

Administrative updates 

and clarification of 

usage. 

Provides format rules 

for SMCA and nonSMCA materiel release 

orders. 

The DLMS Supplement 

guidance for inclusion 

of supplementary 

address/supplemental 

data describes 

redundant functionality 

during mixed 

DLSS/DLMS transition 

period. This is intended 

to minimize impact on 
Enclosure 3, ADC 1020

Page 7

Item # Location DLMS 867I Issue

Revision

Reason

5. During DLSS/DLMS transition, use on issue transactions for

inter-Service ammunition or ammunition-related ownership transfer 

with no physical movement of materiel and no billing. Cite Signal 

Code M in conjunction with the supplemental data field constructed 

as follows: Service/Agency Code Y followed by the old (from) 

ownership code, the RIC to which ownership is transferred, and the 

new/gaining (to) ownership code. Refer to ADC 1020.

implementing systems. 

LMP shall continue 

using the concatenated 

SUPAAD pending 

adoption of the discrete 

data elements.

d. Revise DLMS 869F as follows:

Item # Location 869F Requisition Follow-up

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1020 to DLMS Introductory notes:

- ADC 1020, Inter-Service Ownership Transfer of Ammunition/ 

Ammunition Related Materiel

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/GF04/100 Add additional DLMS note to existing data element:

Monetary Amount

DLMS Note: 

1. Use for nonstandard and nonreimbursable materiel. For 

nonstandard materiel, express the estimated dollar amount in whole 

dollars. Do not include decimals or cents. 

2. For nonreimbursable (free issue) materiel, indicate "0" dollars. 

Use with P0105 Code NC, No Charge. DLMS migration 

enhancement. This usage is comparable to Signal Code D or M.

2. Estimated unit price for nonstandard materiel is a DLMS 

enhancement, see introductory note 3a.

3. Use in Commercial Asset Visibility (CAV) transactions to indicate 

the item unit price.

4. Use for USMC contractor provided maintenance program to 

indicate the special unit pricing.

5. For other than estimated price for nonstandard materiel, the DLMS 

transactions authorize an expanded unit price field size of 9 digits for 

dollars and 2 digits for cents. The decimal point is passed in the 

transaction. If conversion to MILS legacy format is required, unit 

prices exceeding the legacy field size constraint will not be 

perpetuated. Refer to ADC 221A.

Administrative update 

for clarification.

3. 2/GF06/100 Add additional DLMS note to existing data element:

Reference Identification

DLMS Note: When used, enter "ES" to indicate an estimated unit 

price is being provided for the materiel or "NC" to indicate the 

materiel is nonreimbursable (free issue). DLMS enhancement. Use 

of NC is comparable to Signal Code D or M.

Administrative update 

for clarification.
Enclosure 3, ADC 1020

Page 8

Item # Location 869F Requisition Follow-up

Revision

Reason

4. 2/LQ01/180 Add new Qualifier RD and new DLMS note 2 for existing Qualifier 

A1:

A1 Ownership Code

DLMS Note:

1. Use in requisition or referral order to identify the ownership of 

previously purchased materiel. This is a restricted use applicable 

when a Service has entered into an MOA with DLA relative to 

Service-owned stocks, centrally-managed/stored by DLA 

(1BR06/020, Code RI).

2. Use on a referral order to initiate an inter-Service ammunition 

or ammunition-related ownership transfer with no physical 

movement of materiel. Use to identify the new/gaining (to) 

ownership code. DLMS enhancement. Refer to ADC 1020.

3. Also authorized on an intra-Army basis with BR02 Transaction 

Type Code A0 and BR06 Action Code J for identification of the 

ownership of materiel post-post issued by Army Single Stock Fund 

activities.

RD Property Ownership Type Code

DLMS Note:

Use only on a referral order follow-up to initiate an inter-Service 

ammunition or ammunition-related ownership transfer with no 

physical movement of materiel. Use to identify, or to modify, the 

old (from) ownership code. DLMS enhancement. Refer to ADC 

1020.

Provides DLMS 

capability to distinctly 

identify the old and new 

ownership codes for 

DLMS compliant 

applications.

Identifies these fields as 

modifiable.

5. 2/LQ01/180 Revise DLMS notes as shown:

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental supplementary address/supplemental 

data.

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

perpetuate/populate the DLSS Supplemented Supplementary

Address (SUPADD) field. During this time, field size is restricted to 

6 positions; see introductory DLMS note 3d.

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

restriction is a DLMS enhancement; see introductory DLMS note 3a.

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

information within the supplemental data field will be streamlined. 

Activity address data previously contained in the SUPADD will be 

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

introductory DLMS note 3c.

5. During DLSS/DLMS transition, use on a referral order followup to initiate an inter-Service ammunition or ammunition-related 

ownership transfer with no physical movement of materiel and no 

billing. Cite Signal Code M and Project Code CYK in conjunction 

with the supplemental data field constructed as follows: 

Administrative updates 

and clarification of 

usage. 

The DLMS Supplement 

guidance for inclusion of 

supplementary 

address/supplemental 

data describes redundant 

functionality during 

mixed DLSS/DLMS 

transition period. This is 

intended to minimize 

impact on implementing 

systems. 
Enclosure 3, ADC 1020

Page 9

Item # Location 869F Requisition Follow-up

Revision

Reason

Service/Agency Code Y followed by the old (from) ownership code, 

the RIC to which ownership is transferred, and the new/gaining 

(to) ownership code. Refer to ADC 1020.

6. 2/N101/110 Add new Qualifier UQ and associated notes:

UQ Subsequent Owner

DLMS Note:

Use only on a referral order follow-up to initiate an inter-Service 

ammunition or ammunition-related ownership transfer with no 

physical movement of materiel. Use to identify the RIC to which 

ownership is being transferred (the New Owner RIC). DLMS 

enhancement. Refer to ADC 1020.

Provides DLMS 

capability to distinctly 

identify the new owner 

RIC for DLMS 

compliant applications.

e. Revise DLMS 870S as follows:

Item # Location 870S Supply Status

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1020 to DLMS Introductory notes:

- ADC 1020, Inter-Service Ownership Transfer of Ammunition/ 

Ammunition Related Materiel

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/N101/90 Add new Qualifier UQ and associated notes:

UQ Subsequent Owner

DLMS Note:

Use only on supply status subsequent to a referral order to initiate an 

inter-Service ammunition or ammunition-related ownership transfer 

with no physical movement of materiel. Use to identify the RIC to 

which ownership is being transferred (the New Owner RIC). DLMS 

enhancement. Refer to ADC 1020.

Provides DLMS 

capability to distinctly 

identify the new owner 

RIC for DLMS 

compliant applications.

3. 2/LQ01/145 Add new Qualifier A1 and RD and their associated notes:

A1 Ownership Code

DLMS Note:

Use only on supply status subsequent to a referral order to initiate an 

inter-Service ammunition or ammunition-related ownership transfer 

with no physical movement of materiel. Use to identify the

new/gaining (to) ownership code. DLMS enhancement. Refer to 

aDC 1020.

RD Property Ownership Type Code

DLMS Note:

Use only on supply status subsequent to a referral order to initiate an 

inter-Service ammunition or ammunition-related ownership transfer 

with no physical movement of materiel. Use to identify the old (from) 

ownership code. DLMS enhancement. Refer to ADC 1020.

Provides DLMS 

capability to distinctly 

identify the old and new 

ownership codes for 

DLMS compliant 

applications.
Enclosure 3, ADC 1020

Page 10

Item # Location 870S Supply Status

Revision

Reason

4. Revise DLMS notes as shown:

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental supplementary address/supplemental 

data.

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

perpetuate/populate the DLSS Supplemented Supplementary Address 

(SUPADD) field. During this time, field size is restricted to 6 

positions; see introductory DLMS note 3d.

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

restriction is a DLMS enhancement; see introductory DLMS note 3a.

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

information within the supplemental data field will be streamlined. 

Activity address data previously contained in the SUPADD will be 

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

introductory DLMS note 3c.

5. During DLSS/DLMS transition, use on a supply status for interService ammunition or ammunition-related ownership transfer with 

no physical movement of materiel and no billing. Cite Signal Code 

M in conjunction with the supplemental data field constructed as 

follows: Service/Agency Code Y followed by the old (from) 

ownership code, the RIC to which ownership is transferred, and the 

new/gaining (to) ownership code. Refer to ADC 1020.

Administrative updates 

and clarification of 

usage. 
Enclosure 3, ADC 1020

Page 11

f. Revise DLMS 940R as follows:

Item 

#

Location DLMS 940R Materiel Release

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1020 to DLMS Introductory notes:

- ADC 1020, Inter-Service Ownership Transfer of Ammunition/ 

Ammunition Related Materiel

Identifies DLMS 

Changes included in 

the DLMS Supplement

2. 1/W0507/0200 Revise DLMS note for existing Qualifier FI

FI File

DLMS Note:

1. Use to identify an image transaction provided for information.

2. Authorized to be used in association with intra-Army transaction 

processing with W0506 Transaction Type Code NA, ND, NE, and NG

to identify an internal/Offline Materiel Release Order (MRO) Image. 

DIC B99 will be at LQ02 in association with LQ01 qualifier 0, 

Document Identification Code.

3. 2/N101/1100 Add new Qualifier UQ and associated notes:

UQ Subsequent Owner

DLMS Note:

Use only for inter-Service ammunition or ammunition-related 

ownership transfer with no physical movement of materiel. Use to 

identify the RIC to which ownership is being transferred (the New 

Owner RIC). DLMS enhancement. Refer to ADC 1020.

Provides DLMS 

capability to distinctly 

identify the new owner 

RIC for DLMS 

compliant applications.

4. 2/LQ01/1300 Revise DLMS note for existing Qualifier A1 and add new Qualifier RD 

and associated note:

A1 Ownership Code

DLMS Note:

When used for inter-Service ammunition or ammunition-related 

ownership transfer with no physical movement of materiel, use to 

identify the new/gaining (to) ownership code. Refer to ADC 1020.

RD Property Ownership Type Code

DLMS Note:

Use only for inter-Service ammunition or ammunition-related 

ownership transfer with no physical movement of materiel. Use to 

identify the old (from) ownership code. DLMS enhancement. Refer to 

ADC 1020.

Provides DLMS 

capability to distinctly 

identify the old and 

new ownership codes 

for DLMS compliant 

applications.

5. 2/LQ01/1300 Revise DLMS notes as shown:

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental supplementary address/supplemental 

data.

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

perpetuate/populate the DLSS Supplemented Supplementary Address 

Administrative updates 

and clarification of 

usage. 

Provides format rules 

for SMCA and nonSMCA materiel release 

orders. 
Enclosure 3, ADC 1020

Page 12

Item 

#

Location DLMS 940R Materiel Release

Revision

Reason

(SUPADD) field. During this time, field size is restricted to 6 positions; 

see introductory DLMS note 3d.

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

restriction is a DLMS enhancement; see introductory DLMS note 3a.

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

information within the supplemental data field will be streamlined. 

Activity address data previously contained in the SUPADD will be 

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

introductory DLMS note 3c.

5. During DLSS/DLMS transition, use on a release order for interService ammunition or ammunition-related ownership transfer with 

no physical movement of materiel and no billing. Cite Signal Code M 

in conjunction with the supplemental data field constructed as follows: 

Service/Agency Code Y followed by the old (from) ownership code, the 

RIC to which ownership is transferred, and the new/gaining (to) 

ownership code. Refer to ADC 1020.

The DLMS 

Supplement guidance 

for inclusion of 

supplementary 

address/supplemental 

data describes 

redundant functionality 

during mixed 

DLSS/DLMS 

transition period. This 

is intended to minimize 

impact on 

implementing systems. 

g. Revise DLMS 945A as follows:

Item # Location DLMS 945A Materiel Release Advice

Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1020 to DLMS Introductory notes:

- ADC 1020, Inter-Service Ownership Transfer of Ammunition/ 

Ammunition Related Materiel

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 1/W0612/20 Revise DLMS note for existing Qualifier FI

FI File

DLMS Note:

FI File

DLMS Note:

1. Use to identify an image transaction provided for information.

2. Authorized for Air Force and DSS use with PIC NWRM UIT, 

except when the distribution code = 111 and the message supports the 

Retail Transportation and Supply Receipt and Acknowledgement 

Interchange (See DoD 4000.25-M, Volume 3, Chapter 2). Use with 

W0611 Code NJ, NK, and Code NM to identify a materiel or disposal 

release confirmation and materiel release denial image transactions 

where the original transaction has bypassed the normal DAAS 

transaction flow. All transaction set recipients must use extreme 

caution to ensure that individual transactions with this code do not 

process as action documents which affect accountable records. Must 

use with 2/N101/80 code ‘KK’ and

2/N106/80 code ‘PK’. There will be no 2/N106/80 code ‘TO’ for this 

transaction. Refer to ADC 347.

3. Authorized to be used in association with intra-Army transaction 
Enclosure 3, ADC 1020

Page 13

Item # Location DLMS 945A Materiel Release Advice

Revision

Reason

processing to identify an internal Materiel Release Advice image. 

Refer to ADC 1020. 

3. 2/LQ01/100 Revise DLMS note for existing Qualifier A1 and add new Qualifier 

RD and associated note:

A1 Ownership Code

DLMS Note:

When used for inter-Service ammunition-related ownership transfer 

with no physical movement of materiel, use to identify the 

new/gaining (to) ownership code. Refer to ADC 1020.

RD Property Ownership Type Code

DLMS Note:

Use only for inter-Service ammunition-related ownership transfer 

with no physical movement of materiel. Use to identify the old 

(from) ownership code. DLMS enhancement. Refer to ADC 1020.

Provides DLMS 

capability to distinctly 

identify the old and 

new ownership codes 

for DLMS compliant 

applications.

4. 2/LQ01/100 Revise DLMS notes as shown:

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental supplementary address/supplemental 

data.

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

perpetuate/populate the DLSS Supplemented Supplementary Address 

(SUPAAD) field. During this time, field size is restricted to 6 

positions; see introductory DLMS note 3d.

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

restriction is a DLMS enhancement; see introductory DLMS note 3a.

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

information within the supplemental data field will be streamlined. 

Activity address data previously contained in the SUPADD will be 

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

introductory DLMS note 3c.

5. During DLSS/DLMS transition, use on materiel release advice to 

for inter-Service ammunition or ammunition-related ownership 

transfer with no physical movement of materiel and no billing. 

Cite Signal Code M in conjunction with the supplemental data field 

constructed as follows: Service/Agency Code Y followed by the old 

(from) ownership code, the RIC to which ownership is transferred, 

and the new/gaining (to) ownership code. Refer to ADC 1020.

Administrative updates 

and clarification of 

usage. 

Provides format rules 

for SMCA and nonSMCA materiel release 

orders. 

The DLMS Supplement 

guidance for inclusion 

of supplementary 

address/supplemental 

data describes 

redundant functionality 

during mixed 

DLSS/DLMS transition 

period. This is intended 

to minimize impact on 

implementing systems. 

LMP shall continue 

using the concatenated 

SUPAAD pending 

adoption of the discrete 

data elements.

5. 2/N101/180 Add new Qualifier UQ and associated notes:

UQ Subsequent Owner

DLMS Note:

Use for inter-Service ammunition or ammunition-related ownership 

transfer with no physical movement of materiel. Use to identify the 

RIC to which ownership is being transferred (the New Owner RIC). 

DLMS enhancement. Refer to ADC 1020.

Provides DLMS 

capability to distinctly 

identify the new owner 

RIC for DLMS 

compliant applications.
Enclosure 3, ADC 1020

Page 14
Enclosure 4, ADC 1020

Page 1

Enclosure 4, Comment Resolution

Originator Response/Comment Disposition

1. DLA Concur Noted.

2. Marine Corps Concur with comment:

1. Page 6 paragraph 5.g.(5) change 

“869R” to “869F” the requisition follow 

up referenced in the PDC is 869F. There 

is no 869R.

2. Page 6 paragraph 5.g.(5) identifies a 

revision to DLMS Supplement 527R 

(Receipt Inquiry Response and MRA); 

recommend include details of this 

revision in enclosure (3)

3. Page 8 paragraph 7 requested 

feedback. The proposed aspect described 

in this paragraph is acceptable.

Noted.

1. Corrected.

2. During development of this PDC, 

changes to the 527R were envisioned to 

mirror those made to other transactions. 

However, it was later determined that no 

changes were needed. It would be 

unnecessary to carry-over to the receipt 

the original owner or original condition 

code and the new owner and condition 

code applicable to the receipt are already 

identified. The supplementary address 

will be perpetuated under current rules 

and there is no need to break out the 

discrete data. The references to changes 

to the 527R are now removed.

3. Noted.

3. Army Concur Noted.

4. Air Force Concurs with comment:

1. The AF will continue to use manual 

forms to request transfer of ownership 

within the Army depots, utilizing the 

Army MB11 Form.

Rational: The AF systems (CAS) does 

not have the ability to send "Exception 

Data" at this time. Approximately 95% 

of our transfers require additional data 

directing specific lot numbers or serial 

numbers (exception data). Once CAS 

transitions from MILSRIP to Defense

Logistics Management Standards 

(DLMS) we will comply with this 

guidance/format.

2. Question: Page 2, para C; There is no 

Noted.

Response to comments provided by 

Army Supply Integrated System Team 

Lead, LMP Product Management Office:

1. In the case of Air Force, the bulk of 

their transfers require additional data 

directing specific lot numbers or serial 

numbers (exception data). The AF CAS 

system cannot currently transmit their 

transactions in the DLMS format with 

exception data, so they will continue to 

use offline procedures for that scenario. 

This is known and acceptable to the 

AMMO community.

2. The DEMIL process is accomplished 

via MROs using a valid supplementary 
Enclosure 4, ADC 1020

Page 2

Originator Response/Comment Disposition

mention of a scenario for transfers to 

DEMIL. The USAF frequently transfers 

ownership of Class V assets from AF to 

the US Army B5A DEMIL account as 

the Single Manager for Conventional 

Ammunition (SMCA). These DEMIL 

transfers follow the same general process 

as transfers to a sister service would take. 

What process will be used to request 

transfers from Service ownership to 

DEMIL?

address (same as always). Therefore, it 

is not included as part of this PDC.

5. DLA 

Transaction 

Services

General Comments:

1. Page 4, para 4.f.(2)(b) - What is 

reference to BG1/BG2 here? I don't 

think they are mapped in these 

transactions?

2. Page 8. Para 7. - This states Project 

Code "CYK" will not be used in the 

MRO but then how would translation 

know when to map discrete data elements 

to DLMS if inbound MRO to DLA 

Transaction Services is in MILS?

3. RE the process for LMP to provide 

"image" of MRO and materiel release 

advice to DLA Transaction Services,

designation of file copy by itself will not 

accomplish this. Is the implication the 

940R will be document identifier "B99" 

for the 945A what RIC will be used in 

the N1*KK as the party to receive copy? 

Army must use the DLA Transaction 

Services communications routing 

identifier (COMMRI) RUEOZZH as 

receiver ID for the images.

Clarification from LMARS Review:

4. Since this does not apply to the 

beginning A0 if it is ever received (not 

1. Inclusion of DIC BG1/BG2 in the 

DLMS 945A is a DLMS enhancement 

currently being staffed under PDC 1040, 

Migrate Inter-Service Ammunition Serial 

Number and Lot Number Transactions 

(NA VSUP P-724 BG 1/BG2) to DLMS 

945A Materiel Release Advice. A 

staffing note is added to the ADC for 

clarification.

2. Inclusion of Project Code CYK on the 

MRO is not essential. If not present 

DAAS will not map the discrete data. 

Although such data is desirable for an 

enterprise view, it is not essential for 

operational support. In checking with the 

Services, they indicated that they use a

variety of project codes on their nonSMCA MROs. Therefore, the distinct

use of Project Code CYK would not be 

feasible the majority of the time. 

3. The Army will be directed to use a 

specific COMMRI RUEOZZH as 

receiver ID for the images to ensure 

DAAS will recognize that the transaction 

is an image only. The RIC will be the 

value applicable to the functional 

transaction (not the DLA Transaction 

Services RIC). The DIC for the 945A 

image is not yet determined.
Enclosure 4, ADC 1020

Page 3

Originator Response/Comment Disposition

sure that it is), the Signal Code M, 

Project Code CYK, and Y SUPADD of 

any of the follow on transactions will 

overwrite the original Signal Code, 

Project Code, and SUPADD. The 

original data will no longer be available 

in WEBVLIPS or to LMARS or MRA. 

5. Since there is no shipment, these will 

not be measured in MRA. To be 

included in MRA, you must have a 

shipment.

6. Unless the business rules are changed, 

these will only be included in LMARS if 

and when a DRA/DRB is received. 

Normally, we need to receive a shipment. 

But if we receive a MRA receipt, we will 

include the transaction at that point. 

7. Without changing anything in 

LMARS, we will include all the 

segments that can be computed in 

LMARS, including receipt take up time. 

I couldn't tell if the transportation 

segments will not be sent or if the 

transportation segments should be 

excluded if they are received. To exclude 

them, or any others, will require a 

business rule change. 

8. With the Y SUPADD we will not be 

able to use the SUPADD as a ship to. 

The ship to must be the DoDAAC to 

determine area, state, and country. 

DLA Transaction Services has no issues 

with this PDC, just clarifying everything 

so that it will be implemented correctly. 

4. Noted.

5. Noted.

6. The LMP storage activity will provide 

a receipt to the owner (not a receipt 

acknowledgement).

7. No transportation transactions will be 

provided.

8. The storage activity processing the 

release order and the receipt and could be 

used to determine physical area/location.

6. USTRANSCOM Concur Noted.

7. Integrated 

Development 

Environment

1. If this PDC is approved, and IGC does 

nothing, it will dirty our data. Here is 

why. This PDC proposes using a 

1. We understand your concerns about 

how the SUPADD field is being used in 

this situation. Having said that, the 
Enclosure 4, ADC 1020

Page 4

Originator Response/Comment Disposition

(IDE)/ Global 

Transportation 

Network(GTN) 

Convergence

(IGC)

supplementary address field for 

something other than DODAACs. Since 

we currently expect to see DODAACS in 

this field, when this is approved, and data 

starts flowing, we will be storing 

something other than DoDAACs in the 

column we currently store DoDAACs in. 

There are other impacts as well. When 

pallet ownership changes - which this 

PDC addresses - it will look to us like 

there is a material release order. 

At first blush the changes are significant. 

In short:

1. Using field for other than its intended 

purpose (sup address) (i.e., overloading 

the current use and purpose of a 

particular field). 

2. Creating the illusion that certain events 

have occurred (material release order) 

when it didn't really happen (overloading 

the current intended purpose of an IC). 

We think that is bad practice. 

It will require ETL changes, mapping 

changes, potentially report changes. 

2. If this PDC is approved, we would 

like the ADC to have this included: "IGC 

requests a 90 day period between the time 

this ADC is approved and when it can be 

implemented by systems using it to create 

transactions. This time is needed to code 

our system to accept the changes 

described in the PDC". 

challenge that we encountered is that the 

transactions and the SUPADD usage in 

this scenario were previously prescribed 

and implemented by the ammunition 

community under DOD 5160.65-M. One 

of the things our office is trying to do 

with this PDC is get MILSTRIP caught 

up with those previously implemented 

procedures. 

Prior to sending this PDC out for 

staffing, there was extensive dialogue 

with the ammunition community on this, 

trying to determine how best to handle 

the original issue raised by the 

ammunition community -- the need to 

modify the DAAS edits to allow the 

processing of Service-initiated referral 

orders that had a Signal Code M and 

SUPADD beginning with a "Y". 

Previously, these transactions were being 

worked off-line due to the DAAS edit 

issue. Further compounding the issue is 

that we have a mixed DLMS-legacy 

operating environment. Most legacy 

systems are not being modified, while 

their ERP replacements are being 

developed and fielded.

Of note, the use of a "Y" in the first 

position of the SUPADD is authorized 

and indicates that the originator of the 

transaction desires to utilize rp 46-50 for 

data other than the activity address code. 

This is a longstanding MILSTRIP 

practice.

While we did explore use of inventory 

adjustment transactions to satisfy this 

requirement, it was subsequently ruled 

out (see paragraph 4.h of the ADC). This 

group of transactions does fit for this 
Enclosure 4, 

ADC 1020

Page 5

Originator Response/Comment Disposition

situation. The materiel is released from 

one set of inventory books to another, the 

difference being that the materiel is not 

physically shipped since it stays in the 

bunker (it just now belongs to someone 

else's inventory books). We had actually 

tried to get LMP to release an 856S with 

a shipment hold code of R to show a 

receipt in place, similar to what we did 

for the DLA Disposition Services 

business processes, so that we could 

show action taken on the release order. 

Of course, we would have had to make a 

minor change to the shipment hold code 

definition to make that happen. Ammo 

community couldn't support that due to 

impact to legacy systems.

Regarding the SUPADD impact, while 

our preference was to use unique data 

elements for each of the elements 

contained within the concatenated 

SUPADD that was not an option for the 

legacy systems/transactions. In paragraph 4.h. (Alternatives), you'll see 

where our office discussed various 

alternatives for satisfying this 

requirement and the rationale for 

discounting the alternatives. We did go 

ahead and provide a way ahead, once 

legacy systems migrate to DLMS 

compliant systems, to use the DLMS to 

breakdown each of these required data 

elements into individual elements. The 

PDC explains how DAAS will handle 

their DLMS-legacy mapping for this data 

element. We're hoping that once the 

ERPs are up and running and the ammo 

legacy systems are retired, that this 

concatenation issue will resolve itself 

through use of the individual DLMS data 

elements as proposed in the DLMS 

supplements enclosed with this ADC.

2. The ammo community is targeting 

testing of this change in March 2013, so 
Enclosure 4, ADC 1020

Page 6

Originator Response/Comment Disposition

90 days for IGC preparation will be 

available. You'll need to stay close with 

DLA Transaction Services, as your direct 

trading partner, on this; after approval, 

they'll have a better feel as to when 

exactly this will implement.

8. Navy

The provisions of PDC1020 may impact 

Navy ERP. It would require a new 

expanded SUPADD field along with 

some new qualifier codes within the 

Electronic Data Interchange. The Navy 

would like to question, why there is an 

expanded SUPADD field which appears 

to contain other separate fields? Why is 

it not more appropriate to place these 

values in their own fields rather than 

placing them within the SUPADD?

The expanded use of the SUPADD has 

been a goal under the DLMS since day 1, 

but we just aren't there yet...the PDC was 

attempting to clarify the differences 

between where we are now and were we 

want to get eventually. The DLMS 

concept is that the N1 segment should be 

used independently for all DoDAACs 

and then the data that goes into some 

SUPADDs today could go in the DLMS 

Supplemental Data field and the 

available space could be expanded. 

We are moving the ammo data into 

appropriate data fields for DLMS, but 

there are MILS legacy trading partners 

who will need to use the Y-SUPADD 

construct. During mixed environment we 

will allow for the data in both places.

The impact for Navy ERP in 

transitioning the Supplementary Address 

to only Supplemental Data only is still in 

the future. We will provide a separate 

PDC to drive this transition, but we 

needed to make everyone more aware of 

the intent, so it is discussed in this 

change.

In the interim, for this change, we are 

authorizing the new separate data fields

and the continued use of the YSUPADD. We are giving everyone time 

to make the change within DLMS and 

allowing for legacy transactions to pass 

the DAAS edits.