IN REPLY 

REFER TO 

DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

October 09, 2012 

MEMORANDUM FOR SUPPLY AND FINANCE PROCESS REVIEW COMMITTEE (PRC) 

MEMBERS 

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

Unit of Measure (UoM) Transition from Borrowed Codes to Migration Codes and 

Establishment of New UoM for DLA Energy (Supply/Finance/Contract 

Administration) 

We are forwarding the attached approved change to Defense Logistics Manual (DLM) 

4000.25, Defense Logistics Management System (DLMS), for implementation. Transition to 

migration codes requires joint implementation and is targeted for December 1, 20 12. The new 

UoM value established by this ADC for DLA Energy is effective immediately. The UoM value 

must be added to the DLMS conversion guide used by DLA Transaction Services and Wide Area 

Workflow (WA WF) no later than October 31, 2012 to preclude operational impact. 

Addressees may direct questions to Ms. Ellen Hilert, Supply PRC Co-chair, 703-767-0676, 

DSN 427-0676, e-mail: ellen.hilert@dla.mil; Mr. Robert Hammond, Finance Process Review 

Committee Chair, 703-767-2117, DSN 427-2117, email: robert.hammond@dla.mil; or Ms. 

Samantha Khuon, 703-767-5288, DSN 427-5288, e-mail: samantha.khuon@dla.mil. Others may 

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

Attachment 

ADC 1008 

cc: 

ODASD(SCI) 

ODASD DP AP (PDI) 

WAWFPM 

/)1$!/J~ -C ( DONALD C. PIPP 

Director 

DLA Logistics Management 

Standards Office 

Federal Recycling Program G Printed on Recycled Paper 
ADC 1008 Attachment Page 1

Attachment to ADC 1008

Unit of Measure (UoM) Transition from Borrowed Codes to Migration Codes and 

Establishment of New UoM for DLA Energy

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Ellen Hilert, 

Defense Logistics Management Standards Office, 703-767-0676 (DSN 427), e-mail: 

ellen.hilert@dla.mil

2. FUNCTIONAL AREAS: Supply, Finance, Contract Administration

3. REFERENCES:

a. ADC 239/239A, DLMS Unit of Material Measure (Unit of Issue/Purchase Unit) 

Conversion Guide Update, May 14, 2007/July 2, 2007.

b. PDC 274, Establishment of Borrowed Codes for DLMS Unit of Measure (Unit of 

Issue/Purchase Unit) Conversion Guide, dated August 9, 2007.

c. PDC 328, Administrative Update to American National Standards Institute Accredited 

Standards Committee X12 Unit of Material Measure (Unit of Issue/Purchase Unit) Conversion 

Guide 

d. ADC 329, Use of Borrowed and Migration Codes in DLMS Supplements, dated June 

23, 2009.

e. Deputy Chief Management Officer (DCMO) Unit of Measure Data Standard 

Initiative, DCMO Enterprise Business Integration Briefing, September 11, 2012. Refer to 

Enclosure 3.

f. ADC 476, New UoM Conversion Codes for DLA Energy, dated March 21, 2012.

4. REQUESTED CHANGE(S):

a. Overview of Change: This ADC revises the DLMS guidance to use migration codes 

for the data elements associated with the X12 Unit of Measure (UoM). In accordance with this 

change current borrowed UoM codes are to transition to migration codes, including borrowed 

codes approved in References 3.a. and 3.d. Significant changes since staffing are identified in 

green highlighting.

b. Background:

(1) DLMS transactions are based upon the commercial standard for Electronic 

Data Exchange (EDI) as approved by the American National Standards Institute (ANSI) 

Accredited Standards Committee (ASC) X12. When the commercial standard does not have an 

available code identifying a data element or a code value within a data element, a decision must 

be made to use a “borrowed” code, “migration” code, or “local” code. (See section 4.d. below, 

for the DLMS Volume 1 explanation of borrowed, migration, and local codes.)
ADC 1008 Attachment Page 2

(2) In order for DLMS transactions to comply with EDI X12 syntax, the UoM 

passed in the DLMS must use code values assigned by ASC X12. The optimum situation occurs 

where the DOD UoM and the commercial standard carry the same code values for a specific 

UoM definition. However, this is not always the case, and so a conversion guide is required to 

align the DOD and X12 codes. In some cases the DOD UoM code is converted to an X12 UoM 

code that clearly has the same semantic meaning (e.g. DOD UoM Code BI, Belt, is converted to 

X12 UoM Code BT, Belt). In other cases there may not be an X12 UoM code that reasonably 

equates to the DOD UoM code. When there is no semantically equivalent X12 code in the same 

version/release of the X12 standard being used, the established practice set by reference 3.a. was

to “borrow” an existing X12 code from the same X12 version/release and request that ASC X12 

create a semantically equivalent code for a future version/release of the X12 standard. 

(3) Even though X12 creates an equivalent code in a future release of the 

standard, the DLMS Supplement (and thus implementers) can only migrate to the new UoM 

code if there is a DOD enterprise decision to migrate the entire supplement to a current version 

of the standard. Due to the complexity and cost associated with migrating to new X12 

versions/releases, this would occur only for a significant functional need that could not be met by 

the currently employed standard. Such circumstances are not considered likely; DLMS 

Supplements are very rarely migrated to a higher version. DLMS Supplements in current use are 

X12 version/releases 4010 and 4030. X12 4030 was released in December 1999. The current 

X12 standard is now at version 6040.

(4) The use of borrowed codes causes complications in sorting out the X12 codes 

among differences in the UoM lists recorded by DLMS, Wide Area Workflow (WAWF), and the 

Procurement Data Standard (PDS). The PDS uses text names and is not X12 version/release

specific, but does align with the higher version code equivalents. WAWF authorized use of the 

higher version codes within the WAWF version 4010 transactions when conversion codes were 

not previously established within the DLMS UoM conversion guide. The DLMS borrowed 

codes lead to confusion since the X12 code and name have no semantic relationship to its DOD 

use, and can cause problems should the code borrowed in X12 later be identified as the proper 

equivalent for a new DOD UoM code. The difficulty in establishing UoM values for DLA 

Energy highlighted the need for a better business process. The DLA Logistics Management 

Standards Office concluded that the best course for the assignment of new codes needed by DLA 

Energy was for DOD to use a migration code strategy (Reference 3.f). 

(5) The DOD Enterprise issues associated with UoM were presented to the 

BECCM COI for discussion on March 14, 2012. The BECCM COI provides governance for the 

DOD’s end-to-end business process enterprise standards. The DLA Logistics Management 

Standards Office provided input to the BECCM COI recommending a single authoritative source 

be established for the DOD Enterprise and that the use of borrowed codes should be eliminated 

as a method of aligning DOD UoM codes with an X12 equivalent. The BECCM endorsed the 

use of migration rather than borrowed codes. The Deputy Chief Management Officer (DCMO) 

subsequently provided status to the BECCM on August 29, 2012 and briefed the Federal

Cataloging Committee on September 11, 2012 (latest slides shown at Enclosure 3). 

(6) This ADC enables continued progress toward achieving the BECCM 

objective.
ADC 1008 Attachment Page 3

(7) Subsequent to staffing of PDC 1008, DLA Energy identified the need for a 

new UoM value in association with Transportation and Distribution (TD) Shipments interfacing 

with IS-Oil (an SAP Enterprise Resource Program (ERP) module). IS-Oil uses specific 

documents created to process movements of temperature (gravity, density, etc.) dependent 

materials and properly compensate for any quantity conversions that has to be done, as well as be 

able to determine that a difference in quantity loaded vs. quantity unloaded is or is not due to the 

difference in temperature between the load and discharge locations and, therefore, should or 

should not be processed as a gain/loss. For this process all documentation for petroleum 

products is assigned at a base unit of measure reflected as UG6 within the DLA application 

representing gallons at 60 degrees Fahrenheit. Since there is no available X12 value equivalent 

to UG6 a local code U6 will be assigned pending submission and approval for use in X12. U.S. 

Gallons @ 60 Degrees Fahrenheit identified by UoM Code U6 must be available for use in new 

contracts no later than November 1, 2012. This UoM must also be made available in the 

Procurement Data Standard (PDS) and WAWF.

(8) Subsequent to staffing of PDC 1008, a problem was identified concerning the 

UoM Exposure. WAWF and DCMO representatives identified a conflict for the code value EX: 

WAWF accepts the X12 definition of EX for “Feet, Inches and Fraction” without conversion to 

another value for internal DOD use. However, the DLMS conversion guide showed EX as the

DOD code for Exposure. After research, it was determined that there would be no need to 

continue including Exposure in the DLMS conversion guide because the only use of EX at this 

time is as a quantitative express for non-definitive units of issue, e.g. a roll of film with 24 

exposures. Removing the Exposure from the DLMS conversion guide has no negative impact 

and allows WAWF to continue using EX for Feet, Inches and Fraction. Eventually, it is planned 

that the duplicative use of EX will be remedied by aligning DOD code values with X12 code 

values and eliminating the need for code conversion.

c. Approved Change in Detail:

(1) Revise DLM 4000.25, DLMS, Volume 1, Chapter 5, Standards and

Conventions, to clarify the preference of borrowing codes only where the X12 code has 

reasonable semantic equivalency, and insert guidance for the use of migration codes for the 

UoM.

(2) Establish a target date to cease use of borrowed codes in the UoM. See 

Enclosure 2 for the list of current borrowed codes to be replaced by migration codes for all 

implemented versions of the X12 standard. Where a migration code does not yet exist, DLA 

Logistics Management Standards Office submitted a request to create one and the local code is 

identified pending X12 approval.

(3) In conjunction with publication of this change, PDC 274 (Reference 3.b.) is 

formally withdrawn. This change addressed multiple borrowed codes as pending adoption of a 

higher version of X12 and is now obsolete.

(4) In conjunction with publication of this change, PDC 328 (Reference 3.c.) is 

formally withdrawn. This change established borrowed and migration codes for UoM Five and 

is now no longer applicable.
ADC 1008 Attachment Page 4

(5) Assign new UoM “United States Gallons @ 60 Degrees Fahrenheit” using 

local code U6 and equivalent two-position DOD value U6 (equivalent to internal DLA threeposition UoM UG6). 

d. Revisions to DLM 4000.25: Refer to Enclosure 2. 

5. REASON FOR CHANGE: To revise the DLMS guidance on the use of borrowed and 

migration codes. Avoid contractual and coordination complications that come from the use of 

borrowed codes in the UoM.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Migration codes provide greater semantic clarity for UoM codes. Use 

of migration codes is consistent with WAWF approach for UoM values not previously assigned a 

conversion code. Use of migration codes closely aligns with PDS use of the text name. Use of 

migration codes avoids potential future conflicts with a borrowed code being unavailable as the 

proper mapping to a new DOD UoM.

b. Disadvantages:

(1) If the code does not already exist in the latest release of X12, then a code 

request must be submitted to ASC X12 to create a code in the UoM code list. A reasonable 

expectation would be about 3-6 months for a new code to be approved by ASC X12. A change 

to an existing code might take 6-9 months. In the interim a local code may be used, but there is a 

potential for the code value to be disapproved or changed during the X12 coordination.

(2) EDI transactions using migration or local codes are not fully compliant with 

the X12 standard. However, it is common practice among trading partners to support this 

method of identifying data content not available in the standard. Manual effort is required to 

update the X12 UoM code list so that migration codes or local codes pass syntax edits.

7. ADDITIONAL COMMENTS TO CONSIDER: Transitioning from borrowed to migration 

codes requires a coordinated start date so that all systems properly recognize codes. 

Retransmission of records created in the DLMS format prior to the transition may result in 

improper interpretation of the UoM. Additionally, there are multiple conflicting code usages 

among trading partners/authoritative code sources that will require re-alignment to prevent 

miscommunication of the UoM intent. Refer to Enclosure 3 for details and additional

considerations.

8. ADDITIONAL FUNCTIONAL REQUIREMENTS: This change does not impact 

Component functional applications containing only the DOD UoM value and not the X12 code 

employed for DLMS transaction exchange. Refer to Enclosure 3 for next steps toward planned 

transition to X12 UoM codes within DOD.

9. TIME LINE/IMPLEMENTATION TARGET:

a. Transition to Migration Codes. The target date for transition to migration codes is 

December 1, 2012. Coordination between DLA Transaction Services and other trading partners 
ADC 1008 Attachment Page 5

is required. This requirement is applicable to all systems using the DLMS conversion guide for 

transaction exchange in the DLMS format. Staggered implementation will not be authorized. 

b. New UoM U. S. Gallons @ 60 Degrees Fahrenheit. The DLMS UoM conversion 

guide will be updated to add the new UOM for DLA Energy effective immediately. The new

UoM value must be added to the DLMS conversion guide used by DLA Transaction Services 

and WAWF no later than October 31, 2012 to preclude operational impact. The text name must 

be added concurrently to the Procurement Data Standard.

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not available.

11. IMPACT:

a. New DLMS Data Elements: None

b. Changes to DLMS Data Elements: The conversion guide must be updated to 

replace the borrowed codes with the migration codes as shown in Enclosure 1. A new UoM is 

established for United States Gallons @ 60 Degrees.

c. Component DLMS-Compliant Automated Information Systems (AIS):

Component applications will need to implement the conversion guide to change from the 

borrowed codes to the migration codes for transaction exchange.

d. DLA Transaction Services: Implement the conversion guide to change from the 

borrowed codes to the migration codes and add the new value for United States Gallons @ 60 

Degrees. DLA Transaction Services must coordinate implementation with other parties as 

applicable (see DLA and Navy comment at Enclosure 4).

e. WAWF: Implement the conversion guide to change from the borrowed codes to the 

migration codes and add the new value for United States Gallons @ 60 Degrees Fahrenheit. 

DCMO and DPAP to resolve impact of this change on historical records.

f. Procurement Data Standard (PDS): Add new UoM for United States Gallons @ 60 

Degrees Fahrenheit.
PDC 1008 Enclosure 1 Page 1

Enclosure 1, DLMS Unit of Measure Conversion Guide Revisions

This table represents revisions to the Unit of Issue and Purchase Unit Conversion Guide (Unit or 

Basis for Measurement). The changes remove the use of borrowed codes in favor of migration 

codes and add one new local code.

UoM Text Name

DOD 

UoM 

Code

ASC X12 UoM Codes

(X12 Data Element 355) Replacement DLMS Dictionary 

Borrowed Note

Code

Borrowed Code 

X12 Name

Migration/

Local

Code

Apothecary Grain GX UG OG

X12 Version Release 005030

Migration Code. Refer to ADC 1008.

[Code UG was previously assigned as

local code. The existing mapping to 

the ASC X12 Migration Code OG 

will be the code to use across all ASC 

X12 version releases.]

Apothecary Ounce AO 32 Kilograms per Air 

Dry Metric Tons 9O X12 Version Release 005020 

Migration Code. Refer to ADC 1008. 

Apothecary Pound AP 33 Kilopascal Square 

Meters per Gram 9A X12 Version Release 005020 

Migration Code. Refer to ADC 1008.

Apothecary Scruple AS 34 Kilopascals per 

Millimeter ZY X12 Version Release 005020 

Migration Code. Refer to ADC 1008.

Barrel, Dry B2 35

Milliliters per 

Square Centimeter 

Second

ZW X12 Version Release 005020 

Migration Code. Refer to ADC 1008.

Barrel, Liquid B1 36

Cubic Feet per 

Minute per Square 

Foot

ZX X12 Version Release 005020 

Migration Code. Refer to ADC 1008.

Briquet BQ 4J Meters Per Second 

Per Second 9B X12 Version Release 005020 

Migration Code. Refer to ADC 1008.

Exposure EX IW

Inches Per Second 

Per Second 

(Vibration 

Acceleration)

JX

Deleted. 

[UoM Exposure was shown in PDC 

1008 with a planned transition to 

migration value JX; however, it was 

later learned that DOD UoM EX 

conflicts with existing use of EX as

the DOD/WAWF/X12 UoM Feet 

Inches Fraction. Because Exposure is 

not currently required as a DOD unit 

of issue or purchase unit it is removed 

from the DLMS conversion guide at 

this time. See Enclosure 4.] 

Five FV R1 Pica Q9 X12 Version Release 005030 

Migration Code. Refer to ADC 1008.
PDC 1008 Enclosure 1 Page 2

UoM Text Name

DOD 

UoM 

Code

ASC X12 UoM Codes

(X12 Data Element 355) Replacement DLMS Dictionary 

Borrowed Note

Code

Borrowed Code 

X12 Name

Migration/

Local

Code

Fold FD IW

Inches Per Second 

Per Second 

(Vibration 

Acceleration)

9F X12 Version Release 005020 

Migration Code. Refer to ADC 1008.

Hospital Beds HB K3 Kilovolt Amperes 

Reactive Hour HX X12 Version Release 005020 

Migration Code. Refer to ADC 1008.

Kilovolt KV IU Inches Per Second 

(Linear Speed) K8

X12 Version Release 006050

Migration Code. Refer to ADC 1008.

Operating Unit OU JE Joule Per Kelvin OU X12 Version Release 005020 

Migration Code. Refer to ADC 1008.

Outlet OL JK Mega Joule per 

Kilogram OB X12 Version Release 005030Migration Code. Refer to ADC 1008.

Pellet PX KO

Millequivalence 

Caustic Potash per 

Gram of Product

I2 X12 Version Release 005030 

Migration Code. Refer to ADC 1008.

Pillow PI KQ Kilopascal 9P X12 Version Release 005030 

Migration Code. Refer to ADC 1008.

Retinal Unit UR UR Application

Deleted. 

[Retinal Unit was shown in the 

conversion guide, but does not equate 

to a FLIS or X12 UoM value. Retinal 

Unit does not appear to be a valid 

UoM for DOD use.] 

Seat ST JG Joule per Gram 9S X12 Version Release 005020 

Migration Code. Refer to ADC 1008.

Thousand Gallons 

Per Day GT 5C Gallons per Thousand NZ X12 Version Release 005030Migration Code. Refer to ADC 1008.

United States 

Gallons @ 60 

Degrees Fahrenheit

U6 U6

Local code pending X12 approval. 

Refer to ADC 1008.

[A code request will be submitted to 

ASC X12 establishing United States 

Gallons @ 60 Degrees Fahrenheit as a 

UoM and requesting U6 as the code 

value. However, ASC X12 may 

assign a different code.]

United States 

Pharmacopoeia 

(USP) Unit

US US Dosage Form 9Z

X12 Version Release 005020 

Migration Code. Refer to ADC 1008.

[The DOD UoM Code US for United 
PDC 1008 Enclosure 1 Page 3

UoM Text Name

DOD 

UoM 

Code

ASC X12 UoM Codes

(X12 Data Element 355) Replacement DLMS Dictionary 

Borrowed Note

Code

Borrowed Code 

X12 Name

Migration/

Local

Code

JM Megajoule/Cubic 

Meter

States Pharmacopoeia (USP) Unit has 

three entries in the conversion guide. 

Two mappings to borrowed codes are 

being removed and the existing 

mapping to the ASC X12 Migration 

Code 9Z will be the code to use 

across all ASC X12 version releases.]
ADC 1008 Enclosure 2, Page 1

Enclosure 2, DLMS Manual Revisions

Revise DLM 4000.25, DLMS, Volume 1, Chapter 5, Standards and Conventions, as shown 

below in red-bold-italics. 

“C5.1.6. DLMS Qualifiers

C5.1.6.1. DLMS qualifiers are codes used in the ASC X12 based DLMS Supplement 

to identify a specific data element. The qualifier value is selected from codes approved for use 

by ASC X12 in the version/release applicable to the DLMS Supplement. At times there is no 

suitable qualifier available within the X12 dictionary and an alternative code must be used to 

identify and pass the data associated with the business process. There are three methods used to 

accomplish this:

C5.1.6.1.1. Borrowed Code. Use of a “borrowed code” refers to establishing an 

agreement among all trading partners to use a valid X12 code at the correct version by altering 

the code’s semantic meaning (i.e., the code is used because it conforms to syntax rules, even 

though its intended meaning is different from its use in the identified context). The borrowed 

value must be a value that is otherwise unused by the trading partners allowing its definition to 

be mutually changed. When a borrowed code is identified for DLMS use, DLA Logistics 

Management Standards shall submit an ASC X12 data maintenance (DM) action to establish a 

new qualifier to be approved for use in a higher (future) ASC X12 version/release. The 

borrowed code may be used indefinitely until DoD migrates to a higher version of ASC X12, 

but, more likely, will be permanent since migration to higher versions is very rare. Data element 

1270, codes are associated with a specific industry code list, when they are over ridden by 

DLMS use, the specific DLMS use must be identified.

C5.1.6.1.2. Migration Code. A “migration code” is a code from a higher (but 

existing) ASC X12 version that is used in a lower version. The semantic meaning and syntax are 

consistent with the higher version. Use of a migration code refers to establishing agreement among all 

trading partners to use a valid X12 code from a higher version, with its approved X12 definition, at a 

lower version of X12. ASC X12 refers to the use of a migration code within implementation guidance 

as a superset. Manual intervention may be needed for some commercial applications to accept the 

higher version code.

C5.1.6.1.3. Local Code. A “local code” is a code value that is not in the current 

version, and has not been established at a higher ASC X12 version. A Data Maintenance (DM) action 

may be in process to establish the code in a higher version. Once approved by ASC X12, the local 

code becomes a migration code. Manual intervention may be needed for some commercial 

applications to accept the local code. 

C5.1.6.2. DLMS Preference for Borrowed Codes over Migration or Local Codes. To 

maintain consistency between the logistics and transportation domains, the DLMS will use codes 

from the current version of ASC X12 whenever feasible. The preference for documentation of 

new codes when they are not available in the current version is to use borrowed codes, where 
ADC 1008 Enclosure 2, Page 2

there is a reasonable contextual equivalent. When the list of borrowed codes for a data element 

has been exhausted or a suitable code cannot be found, migration codes or local codes are an 

acceptable alternative and will be approved by the PRC Chair/Administrator on a case-by-case 

basis. An exception to this preference is for unit of measure codes. Unit of measure codes will

map to the matching ASC X12 code for the applicable version/release or a migration code. 

Where ASC X12 lacks a unit of measure code in the current version/release or a migration 

code, a DM must be submitted to ASC X12 to create the code and a local code will be assigned

until such time as that migration code is approved by ASC X12. When codes are borrowed in 

the logistics domain, DLA Logistics Management Standards shall continue to submit code 

changes to ASC X12 to add the code to a future version. Local codes shall only be used where a 

DM action has been submitted, but the associated DLMS Supplement and system applications

must be updated as soon as practical after ASC X12 completes the approval of the requested 

value. It is possible that the approved code value will differ from the local code; in this case, 

the DLMS Supplement and system applications shall be updated to reflect the approved 

migration code based upon issuance of an administrative ADC.”
ADC 1008 Enclosure 3, Page 1

Enclosure 3 DCMO UoM Data Standard Initiative Briefing

Problem: 

• DoD needs to establish one Data Standard for UoM/UI and one Authoritative Master Reference 

Data repository for both Functional(s) and Systems Integrators

– Currently, translation tables and data is maintained by various Functional communities 

(Logistics, Procurement, Finance, Real Property, WSLM, HRM)

– Nearly all ERP programs building interface to Entitlement and Financial systems have 

expressed invoice challenges at Entitlement for UoM

– Approximately 31% of suspended invoices from WAWF to IAPS are due to a Unit of Issue 

problem

– End to End data integration across Logistics, Procurement and Financial domains has 

been problematic for numerous modernizing ERP programs

– Lack of Enterprise-wide mediation strategy or roadmap to reduce mapping to Legacy 

DoD data codes 

– There are currently 134 unit of issue codes that have a conflict between the DoD code 

and the X12 code

Recommendation: 

 Establish ANSI ASC X12 as the Data Standard for UoM

 DoD needs to move forward and transition away from the Legacy DoD Codes for Unit of Issue 

(UI) and Unit of Measure to enable cross-domain interoperability for information exchanges and 

to support E2E cross-functional alignment for system implementation

 Establish BEA web site as DoD Reference Master Data

 Leverage FLIS Portfolio Data Warehouse (FPDW) to enable system migration to target values

 Work with ERPs and AISs to ensure system changes are in place to be compliant to BEA

Discussion Points: 

 The DoD Logistics, Procurement, Financial communities and Commercial Industry have moved 

almost exclusively to the ANSI X12 Standard (or xml equivalent) for information exchange

o Example: Procurement Data Standard and DLMS are based on X12 UoM values/data 

codes

 Most Logistics systems have set up the interface to the FLIS NSN catalogue, so the UI data code 

associated with the item should be an automated update based on the feed from FPDW

o DCMO in coordination with FLIS for impact and feasibility analysis

 Most DoD Components are moving to Master Data strategies, the Federal Logistics Information 

Service (FLIS) Portfolio Data Warehouse (FPDW) enables a publish/subscribe for Customer, Item 

and Vendor master records from Authoritative Data Sources

Challenges to Transition to ANSI X12: 

• Several Unit of Issue(s) and their related codes, listed below, are already resident in FLIS and the 

recommended UI codes are already assigned to another Unit of Issue.
ADC 1008 Enclosure 3, Page 2

• There is a DB2 Table “BUOM_CONVERSION” that FLIS maintains that shows what UI codes can 

be used in the Quantitative Expression for a non-definitive UI that would need to be updated.

• FLIS, EBS, and all the Service legacy systems will need to be updated with the new codes if this 

recommendation goes forward.

Challenges to Transition to ANSI X12: 

• Other Unit of Issue(s) and their related codes, listed below, are not resident in FLIS but the 

recommended UI codes are assigned to a U/I that is already resident in FLIS.

Next Steps

 Resolve data code challenges listed on previous slides 

 Determine how to establish Enterprise Mediation capability until DoD can transition the 

data codes to ANSI (leverage DLA Transaction Services and GEX)

Unit of Issue UI Recommended UI from ASC X12

Belt BI BT

Beam BM BE

Block BZ BL

Combo C3 CZ

Connector CR CK

Cassette CX CS

Gram GM GR

Half Dozen HZ HD

Hundred Kilograms KH HK

Carat KR CD

Linear Inch LN LI

Long Ton LO LG

Microgram M5 MC

Milligram MG ME

Mixed MZ MX

Pounds, Gross PO PG

Shipment SB SX

Section SN SE

Sleeve SV SL

Thousand Square Feet TZ TS
ADC 1008 Enclosure 3, Page 3

 DLA Logistics Management Standards (DLMSO) Proposed Change (PDC 1008) UoM Transition 

from Borrowed Codes to Migration Codes and ADC 476, New UoM Conversion Codes for DLA 

Energy

www.dla.mil/j-6/dlmso/eLibrary/changes/DLMS/PDC/PDC_1008UoMTransitionBorrowedMigrationCodes4.pdf

www.dla.mil/j-6/dlmso/elibrary/changes/DLMS/ADC/ADC_476_New_UoM_ConvCodes_DLA_Energy(final).pdf

 DCMO will sponsor an update to the Federal Logistics Information Service (FLIS) Portfolio Data 

Warehouse (FPDW) to include a UoM/UoI Master table for the business term and X12 Code for 

systems to consume as a part of this transformation (SOA Publish/Subscribe service)

 Publish UoM Reference Master Data in BEA 10.0 for Compliance

http://dcmo.defense.gov/products-and-services/business-enterprise-architecture/9.0/index.htm

 DCMO will sponsor the UoM data element going forward and work with FLIS to ensure that the 

Reference Master data is maintained both in the BEA and at the FPDW
ADC 1008 Enclosure 4, Page 1

Enclosure 4, Comment Resolution

Originator Response/Comment Disposition

1. DLA 1. No impact on DLA Enterprise Business System (EBS); DLA 

Transaction Services will ensure proper code is used during 

translation performed as DLA service.

2. DLA Energy requires a new UoM be established in support of 

the new Oil and Gas functionality. It seems the two digit X12

code of "U6" is available and we are requesting that be our EBS 

unit "UG6" (US Gal @60deg) standard. We have a short 

turnaround timeline and are requesting we get this added to 

Transaction Services by OCT 26th. This is prior to the weekend 

will be bring Petroleum materials into EBS with a UG6 Base Unit 

of Measure. It seems we may need to have this for certain 

Contract awards posted to EDA. (New contract awards will not 

be posted until about 2 weeks beyond the above date, so we may 

be able to be a little more flexible). Ultimately we will need to 

add this to WAWF coding as well for certain contract receipts.

1. Noted. 

2. This ADC is updated 

for a new local value for 

UoM U6 indicating US 

Gal @60 degrees and 

we will submit a data 

maintenance request to 

X12. Will request this 

UoM be added to the 

procurement data 

standard. We have 

established October 31, 

2012 for joint 

implementation.

2. Army Concur Noted.

3. Air Force Concur Noted.

4. Marine Corps Concur Noted.

5. DLA Concur Noted.

6. Navy The Navy concurs with the PDC as written. 

However, Navy ERP is currently using the borrowed codes and 

will require a change to adhere to this PDC. The change is going 

to require Navy ERP to stop all inbound and outbound traffic in 

order to achieve the needed results. We will also need to do some

coordination to have RSupply Ashore updated properly. As such, 

it is going to be necessary for DLA Transaction Services to have 

further discussion with us to determine the proper timing of the 

changes in our legacy systems. We will need to be kept apprised 

of the timeline for implementation and will need to work together 

to ensure everything is implemented properly.

Noted.

7. DCMO Concur. 

Resolution is required for the conflicting UoM assignments for 

the value EX used in X12 and WAWF for UoM "Feet Inches 

Noted.

Conflict resolved. See 

below.
ADC 1008 Enclosure 4, Page 2

Originator Response/Comment Disposition

Fraction” (but also listed as the DOD value for Exposure).

8. DLA Logistics 

Information 

Service

Clarification provided: The codes EX and JX are not in FLIS as 

Units of Issue (UIs) but EX is used as a Unit of Measure (UM) on 

372 NIINs, JX is not recorded as a UoM in FLIS. What that 

means is that even though FLIS does not record UoMs they are 

used in the quantitative expression on items that have a nondefinitive UI.

Example: UI = RL (Roll) and the quantitative expression is 

recorded with a 'K' phrase code "00000000024EX" (e.g., 24 

exposures per roll of film).

To make the change from EX to JX the following actions would 

be needed.

1. Update the BUOM CONVERSION Table in FLIS.

2. Determine who is the PICA of the 372 items and get their 

concurrence to update the NIINs 3. Update the 372 NIINs with 

the new quantitative expression.

Because EX is NOT 

currently communicated 

in a DLMS transaction 

as a unit of issue or a 

purchase unit, it can be 

removed from the 

DLMS conversion 

guide. This eliminates 

the need to establish the 

migration code JX in 

association with the 

UOM Exposure in the 

DLMS conversion 

guide. Removing the 

Exposure from the 

DLMS conversion guide 

will prevent continued 

confusion and 

duplicative assignment 

of the value EX. 

Eventually, the DOD 

EX will be replaced by 

the X12 migration code 

JX for Exposure (under 

DCMO way ahead). 

9. WAWF Concur (based upon updates provided in ADC) Noted.

10. DPAP (PDI) Concur (based upon updates provided in ADC) Noted.