1 of 3

ADC 63

Attachment

APPROVED DLMS CHANGE (ADC) 63 

REVISION TO DLMS SUPPLEMENT 527D TO SATISFY AN 

INTRA-NAVY REQUIREMENT FOR STANDARD UNIT PRICE ON THE 

ADVANCE RECEIPT INFORMATION TRANSACTION.

1. ORIGINATOR:

a. Service/Agency: Navy

b. Originator: Ross Burton, Naval Inventory Control Point M0411

2. FUNCTIONAL AREA: Primary. Supply

3. REQUESTED CHANGE:

a. Title: Revision to DLMS Supplement 527D to Satisfy an Intra-Navy Requirement 

for inclusion of 'Standard Unit Price' on the Advance Receipt Information 

Transaction. 

b. Description of Change: 

(1) To support Navy legacy system requirements, NAVSUP requires that the 

'standard unit price' be added to the 527D for use with the DLMS Advance Receipt 

Information (ARI) transaction. The 527D ARI transaction is the DLMS equivalent of 

the MILSTRAP Prepositioned Materiel Receipt (PMR) transaction. Navy currently 

cites the 'standard unit price' in MILSTRAP PMR transactions, using an intraComponent data field.

(2) This data requirement is being incorporated to accommodate a Navy 

specific requirement, and does not require DoD-level business rules. IntraComponent procedures/business rules must be in place identifying the purpose/use 

of the 'standard unit price' in an ARI transaction. Use of the data is optional and 

marked as a Navy requirement to accommodate their documented intra-Component 

requirement. If other Components choose to use this optional data in DLMS, the 

data cannot be mapped back to DLSS during operation in a mixed DLMS/DLSS 

environment, unless the placement in the DLSS transaction is identified to DLMSO. 

Further, the data will not be acted upon by trading partners outside your Component 

as no DoD-level requirement or procedures have been established. In response to 

this proposal request addresses, other than Navy, that have a requirement for 

including the 'standard unit price' in ARI transactions on an intra-Component basis, 

document that requirement to DLMSO.
2 of 3

ADC 63

Attachment

c. Procedures: 

(1) DoD level procedures are not required for this intra-Component requirement.

(2) NAVSUP procedures are defined in the Naval Supply Procedures, NAVSUP 

Publication 485 (Revision 3). To the maximum extent, Navy transactions follow existing 

DLSS/DLMS transaction formats; however, Navy use of DLSS intra-service fields 

requires the use of data not included in the DoD standard DLSS transaction. 

 d. Alternatives: None

4. REASON FOR CHANGE: 

 a. DLMSO memorandum, November 7, 2001, subject: Inclusion of Defense 

Logistics Standard Systems (DLSS) Data/Business Processes in the Defense Logistics 

Management System (DLMS), highlights the need for Components to document their intraComponent data requirements to DLMSO for inclusion in the DLMS. Without such 

documentation, DLMSO has no visibility of the requirement. One of the categories 

identified in the memorandum is data which is transmitted in DLSS intra-Component use 

fields, but which is undocumented in the DLMS. Navy originated this change proposal in 

response to the November 7, 2001 memorandum. 

 b. Navy currently includes 'standard unit price' in MILSTRAP PMR transactions 

(Document Identifier Codes DU_ and DW_). Navy cites the data in a multi-use field which 

allows entry of Component prescribed data for intra-Component use. Navy indicates that 

their wholesale system uses the PMR transaction to provide the 'standard unit price' to 

Navy's retail system, where it is recorded in the stock point’s Master Item Stock Record. 

The DLMS Supplement (DS) to the 527D Federal Implementation Convention 

accommodates the majority of Navy's data requirements, however Navy's unique 

requirement for data exchange of the 'standard unit price' is not currently carried in the DS 

527D. Changes to the DLMS procedures are not required.

5. ADVANTAGES and DISADVANTAGES:

a. Advantages: 

(1) Incorporates a documented intra-Navy data requirement into DLMS. 

(2) Establishes data element for standard unit price in the 527D. Data 

element can be opened up for use by additional DoD Components if requirement is 

identified to DLMSO.

b. Disadvantages: None known.
3 of 3

ADC 63

Attachment

6. IMPACT:

a. Transaction Set(s): The 004010 version of the 527D Material Due-In and Receipt 

IC is affected by this change.

b. Segment(s): AMT segment. Open optional segment 2/AMT/100 for use. Add 

the following segment level note: DLMS Note: "This segment is for optional use as needed 

to support intra-Component requirements."

c. Data Elements(s): 2/AMT01/100. Add Code NT – Unit Value. Add DLMS notes 

1 and 2 as follows:

1. " Use as needed to cite the standard unit price in Advance Receipt 

Information (ARI) transactions for intra-Component use. Component level 

procedures are required." 

2. "DLMS enhancement to allow for entry of an intra-Navy data requirement 

cited in DLSS DI Code DU/DW, record positions 60-66. Navy has 

identified a requirement for standard unit price for intra-Navy use. 

NAVSUP procedures are defined in the Naval Supply Procedures, 

NAVSUP Publication 485. See introductory DLMS note 4.a. for interComponent use of this data”

Justification: In its use of an intra-Component use field in the PMR, DI 

Codes DU_ and DW_ (rp 60-66), the Navy record layout contains a data 

field for the standard unit price of an item listed in a Prepositioned Material 

Receipt. 

d. Publication(s): DoD 4000.25-M, DLMS Supplement to the 527D Federal 

Implementation Convention.