DEFENSE LOGISTICS AGENCY HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

March 22, 2017

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

SUBJECT: Administrative Approved Defense Logistics Management Standards (DLMS) 

Change (ADC) 1254, Remove Unit of Measure Code Validation from DLMS XML 

Schemas

The attached change to DLM 4000.25, Defense Logistics Management Standards, is 

approved for implementation. The updated DLMS schema file will be posted to the DLMS 

Program Office Website at http://www.dlmso.dla.mil/elibrary/TransFormats/140_997.asp, within 

10 days from the above date.

Addressees may direct questions to Sylvia Williams, DLMSSupply@dla.mil. Others 

must contact their designated Supply PRC representative available at 

http://www.dlmso.dla.mil/eLibrary/ServicePoints/allpoc.asp. 

HEIDI M. DAVEREDE

Program Manager

Enterprise Business Standards Office

Attachment

As stated

cc:

ODASD(SCI)
Attachment, ADC 1254

Page 1

ADC 1254

Remove Unit of Measure Code Validation from DLMS XML Schemas

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Sylvia Williams, DLMS Data Manager, Enterprise Business Standards 

Office, (571) 363-9282, Sylvia.Williams@dla.mil

b. Functional POC: Sylvia Williams, DLMS Data Manager, Enterprise Business Standards 

Office, (571) 363-9282, Sylvia.Williams@dla.mil

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Inventory/Issue

b. Primary/Secondary Functional Process: Disposal

3. REFERENCE:

a. Defense Logistics Manual (DLM) 4000.25, Defense Logistics Management Standards 

(DLMS), Volume 1, Concepts and Procedures

b. Defense Logistics Manual (DLM) 4000.25, Volume 1, Chapter 7, C7.4.1.3. Migration Code

c. Unit of Materiel Measure (Unit of Issue/Purchase Unit) Conversion Guide

4. REQUESTED CHANGE(S):

a. Brief Overview of Change: This administrative change modifies DLMS schema files 

using X12 Data Element (DE) 355, Unit or Basis for Measurement Code. The inclusion of unit of 

measure (UoM) code values under Data Element 355 will be turned off in all applicable XML schema 

files. This change lifts the UoM code restrictions in XML schemas that currently have this restriction 

in place.

b. Background: The manner in which UoM is handled in DLMS transactions complicates the 

inclusion of UoM codes in DLMS XML schemas. Reference 3.a. notes that UoM is one of the few 

coded elements that require a conversion between a DOD code list and the commercial standard X12 

code values. Certain code values are failing validation because UoM uses migration codes1. A 

migration code is a code used from a higher ASC X12 version/release (e.g. 5030) that is used in a 

lower version/release (e.g. 4010). There is no easy method to add just the unique set of code values to 

the individual schemas without replacing the entire UoM validation table with a new validation table. 

For a number of DLMS transactions, the decision was made to not include this validation and leave it 

to the implementing system to validate the UoM code values. This change applies this principle to all 

DLMS transactions with Data Element 355, Unit or Basis for Measurement Code. Implementers are 

expected to use the DLMS XML schemas in combination with the DLMS Implementation 

Conventions (ICs) and the Unit of Materiel Measure (Unit of Issue/Purchase Unit) Conversion Guide

(Reference 3.c.) for their programming effort, in order to guarantee proper validation of UoM code 

values.

 1 For definition of migration code, please refer to Reference 3.b.
Attachment, ADC 1254

Page 2

c. Requested Change in Detail:

(1) When the DLMS Program Office builds the underlying file used to manage DLMS 

ICs and XML schemas that convey Data Element 355, the data element will be used, but the code 

validation will be turned off. This change results in XSD files (XML schemas) without embedded X12 

code values for validation. This change affects the DLMS XML schemas that correspond to the 

following DLMS ICs, which use DE 355 and have UoM code lists. 

Number X12 

Version Title

511M 4010 Requisition Modification

511R 4010 Requisition

527D 4010 Due-in/Advance Receipt /Due Verification

536L 4010 Logistics Reassignment Management Data

650A 4030 Assembly Component Maintenance Structure

832N 4030 Catalog Data Support

841W 4030 Hazardous Material/Hazardous Waste (HM/HW) Profile

842C/R 4030 Stock Screening Reply

842P 4030 Product Quality Deficiency Report (PQDR) Data Exchange

842S/Q 4030 Storage Quality Control Report

846C 4030 Disposition Category Update

846F 4010 SMCA Freeze/Unfreeze Action

846I 4010 Asset Status Inquiry/ Report

846P 4010 Physical Inventory Request

846S 4010 Logistics Reassignment Storage Transfer/Order/Reply

856 4010 Advance Shipment Notice (ASN)

856N 4010 Notice of Availability

945A 4010 Materiel Release Advice

945A 4030 Materiel Release Advice

(2) The DLMS Program Office will add the following note manually to the opening 

lines of all XSD files, prior to the start of the actual structural components of the XML schemas: 

"Proper implementation of this schema is dependent on applying business rules 

documented in DLMS Notes for the same transaction structure of the source DLMS IC. 

Refer to the corresponding DLMS IC for more information. Use DLMS/ASC X12 

conversion guides when applicable."

d. Revisions to DLM 4000.25 Manuals: None 

e. Alternatives: None

5. REASON FOR CHANGE: The Air Force Integrated Logistics Systems-Supply (ILS-S) is not 

able to use current schemas because the generated schemas are missing certain code values in the UoM 

table validation.
Attachment, ADC 1254

Page 3

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Corrects problem with the validation of DLMS XML schemas with Data 

Element 355.

b. Disadvantages: This change may, on rare occasions, result in Component systems turning 

off code validation for all code values. This very low risk is mitigated by the fact that DAAS validates 

codes and would reject transactions with invalid code values.

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Authorized for immediate 

implementation.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH IMPLEMENTATION 

OF THIS CHANGE: None noted.

9. IMPACT:

a. New DLMS Data Elements: This change does not introduce any new DLMS data 

elements.

b. Changes to DLMS Data Elements: This change does not change any DLMS data 

elements. 

c. Automated Information Systems (AIS): All systems using the DLMS XML schemas 

affected by this change must implement this change. See a list of affected DLMS XML schemas under 

4.c.(1).

d. Defense Automatic Addressing System (DAAS): DAAS must implement the changes 

affecting DLMS XML schemas with unit of measure listed under 4.c.(1).

e. Non-DLM 4000.25 Series Publications: None