ADC 221A, Attachment Page 1

 

ADC 221A 

Revised Procedures associated with the DLMS Enhancement for 

Communication of Unit Price 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: NAVSUP E3, 

DSN 430-5070, commercial (717) 605-5070 or (717) 571-0516

2. FUNCTIONAL AREA: Primary/Secondary Functional Area: Supply 

3. REFERENCE: DLA Logistics Management Standards Office Memorandum, subject: 

Approved DLMS Change (ADC) 221, DLMS Enhancement for Communication of Unit Price 

and Total Price (Supply/MILSTRIP), dated February 01, 2007.

4. BACKGROUND: 

a. ADC 221 (referenced above) expanded the field size for the unit price and total dollar 

value on the Issue Release/Receipt Document (IRRD) (DD Form 1348-1A) and established a 

corresponding field size for the unit price in DLMS transactions. Under DLMS, the identified 

transactions adopt an 11 position unit price which will be transmitted as 9 digits dollars, decimal 

point, and 2 digits cents. However, MILSTRIP transactions continued to carry the unit price as 

currently defined for 80 record position transactions. No acceptable means to vary the business 

rules for processing an alternative field length within the 80 record position formats was 

identified. This meant that there would continue to be times where the data content is truncated, 

losing the leading dollar positions. 

b. Procedures, transactions, data elements, processing details in use today: 

 (1) Legacy Navy systems change the supply status unit price to all “9”s when it is 

larger than will fit into the MILSTRIP AE_ transaction. This indicates to the receiving system 

that they should not update the price on their order. 

 (2) When a DLMS transaction supply status (DLMS 870S) is translated to a 

MILSTRIP legacy 80 record position transaction (Document Identifier (DI) Code AE_) by 

DLA Transaction Services the price is truncated. When the supply status truncated price is 

transmitted to the receiving system they update their order with this erroneous price. This 

results in under-obligation of funds. 

 (3) In addition to the supply status, the legacy unit price field length constraint is also 

applicable to the shipment status (DLMS 856S/DI Code AS_) and the materiel release 

confirmation (DLMS 945A/DI Code AR_) addressed in ADC 221. 

 (4) Multiple additional DLMS transactions carry the unit price with no guidance for 

expansion of the legacy data element length under DLMS. 
ADC 221A, Attachment Page 2

5. APPROVED CHANGE(S): 

a. Procedures: This change supplements ADC 221 with more appropriate business rules 

for conversion of transaction formats between DLMS and MILS. All other aspects of ADC 221 

are unchanged. This change also provides business rules for additional DLMS transactions 

supporting MILSTRAP and MILSBILLS functionality that were not addressed in the original 

ADC 221.

 (1) Revise procedures for DLA Transaction Services Defense Automatic Addressing 

System (DAAS) conversion mapping from DLMS to MILS legacy 80 record position formats to 

block the perpetuation of any price exceeding 7 positions (5 digits dollars and 2 digits cents). 

 (2) Revise procedures for conversion mapping from MILS to DLMS to block the 

perpetuation of any price consisting of all “9”s. 

 (3) Revise DLMS Supplements to include new business rules as shown in Enclosure 1. 

 b. Alternatives: Revise conversion mapping to use all “9”s rather than blocking 

conversion dollars that exceed the available space. However, without specific programming 

changes, all “9”s may be misinterpreted by some applications as a valid price and is not 

supported by DLA Logistics Management Standards. 

 6. REASON FOR CHANGE: 

a. Navy modernized system development is being programmed to be DLMS compliant. 

Navy has a number of items whose price is larger than $100,000.00. DLA Transaction Services 

has been truncating the price when forwarding the status to a legacy system. The legacy system 

then updates the price on their order and de-obligates funds. This puts the ordering activity in a 

risk of not having funds obligated to be able to pay the bill when it arrives. 

b. This change was requested by the Navy for the supply status only. It is believed that 

other Component systems are encountering similar problems as they transition between MILS 

and DLMS. This solution works for all Components and is planned for global use where unit 

price is contained in the original MILS format and conversion is required. 

c. Establishes standard rules across DLMS. 

7. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages (tangible/intangible): Prevents erroneous de-obligation of funds by 

ordering activity. Prevents erroneous data from being transmitted due to DLMS conversion to 

legacy formats. 

 b. Disadvantages: None identified. 

c. Staffing Note for All Components: Unlike the Navy process described above, some 

Components may carry truncated prices in their MILS legacy transactions. If truncated by the 
ADC 221A, Attachment Page 3

source system, the resulting DLMS transaction will continue to perpetuate the bad data 

represented by the truncated price. 

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Implementation of 

conversion rules is requested no later than October, 2011. 

9. IMPACT: 

a. Automated Information Systems. Components should review procedures for 

truncation of unit prices within legacy systems and ensure that DLMS implementation can 

handle the larger field length for unit price. 

b. Automated information technology (AIT). AIT requirements associated with the unit 

price were addressed in ADC 221. This change reiterates the original requirement in that 

Components are required to complete the necessary updates to accommodate the larger DLMS 

field length within their AIT processing. Components must assure that AIT read and write 

capability will not fail due to unit price field length regardless of the interfacing system 

capability to support DLMS. 

c. DAAS Conversion Mapping. Revised as discussed above. 

d. DLMS Data. There are no new data elements applicable to this change. DLMS field 

lengths may be revised as noted in the enclosure. 

e. DLMS Supplement updates are shown at Enclosure 1 as follows: 

 511R, Requisition 

 511M, Requisition Modification 

 527D, Due-in/Advance Receipt /Due Verification 

 527R, Receipt, Inquiry, Response and MRA 

 536L, Logistics Reassignment Management Data 

 810L, Logistics Bill 

 812L, Logistics Bill Adjustment Request Reply 

 812R, Logistics Bill Adjustment Request 

 846D, Logistics Reassignment Transfer and Decapitalization 

 856S, Shipment Status 

 869F, Requisition Follow-Up 
ADC 221A, Attachment Page 4

 870M, Material Returns Supply Status 

 870S, Supply Status 

 940R, Material Returns 

 945A, Material Release Advice 
Proposed Addendum to 

ADC 221A, Enclosure Page 1 

Enclosure 1, DLMS Revisions

(1) Update the 870S DLMS Supplement as shown: 

# Location Revision to 

870S Supply Status

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/PO104 and 

05/150 

Add the following Data Element level note:

PO104 Unit Price 

PO105 Basis of Unit Price Code 

Federal Note: Use to identify the correct unit price associated 

with the status provided. 

DLMS Note: 1. A field size exceeding 7 positions (5 digits 

dollars and 2 digits cents) may not be received or understood by 

the recipient’s automated processing system. 

2. 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. Under DLMS the unit price will be 

expressed as R9.2. Authorized DLMS migration enhancement; see 

introductory DLMS 3f. Refer to ADC 221A. 

Clarification 

provided for new 

business rule and 

data construct. 

(2) DS 856S, Shipment Status: 

# Location Revision to 

856S Shipment Status

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/REF01/1500 Add the following Data Element level note:

PA, Price Area Number 

DLMS Note: 1. Use for shipments to disposal to indicate actual 

or estimated pricing information. 

2. Available for all other shipment status as an optional data field 

to perpetuate the actual or estimated unit price from the 

associated supply status or material release order. This is an 

authorized DLMS enhancement. 

Clarification 

provided for new 

business rule and 

data construct. 
ADC 221A, Enclosure 1, Page 2

3. A field size exceeding 7 positions (5 digits dollars and 2 digits 

cents) may not be received or understood by the recipient’s

automated processing system. 

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. Under DLMS the unit price 

will be expressed as R9.2. Authorized DLMS migration 

enhancement; see introductory DLMS 2f. Refer to ADC 221A. 

5. Use to identify the unit of use price when the unit of use 

indicator (1/BSN01/0200) is present. Authorized DLMS 

enhancement under DLA industrial activity support agreement. 

Refer to ADC 381. 

(3) Update DS 940R, Material Release Order: 

# Location Revision to 

940R Material Release Order

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify 

changes in the DS. 

2 2/AMT01/0800 Add the following Data Element level note:

AMT01, Amount Qualifier Code 

LI Line Item Unit Price 

DLMS Note: 1. Use with material release order transactions to 

indicate the unit price. 

2. A field size exceeding 7 positions (5 digits dollars and 2 digits 

cents) may not be received or understood by the recipient’s 

automated processing system. 

3. 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. Under DLMS the unit price 

will be expressed as R9.2. Authorized DLMS migration 

enhancement; see introductory DLMS 4f. Refer to ADC 221A. 

4. The DLMS field length is authorized when this transaction 

supports the Retail Transportation and Supply Receipt and 

Acknowledgement Interchange SBSS interface with CMOS. 

5. Use to identify the unit of use price when the unit of use 

indicator (W0501=Z) is present. Authorized DLMS 

enhancement under DLA industrial activity support agreement. 

Refer to ADC 381. 

Clarification 

provided for new 

business rule and 

data construct. 
ADC 221A, Enclosure 1, Page 3

(4) Update DS 511R, Requisition: 

# Location Revision to 

511R Requisition

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/PO104/30 Add the following Data Element level note:

PO104 Unit Price 

DLMS Note: 1. For nonreimbursable material (free issue), 

indicate 0 dollars. 

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

3. Estimated unit price for nonstandard material is a DLMS 

enhancement, see introductory note 3a. 

4. 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. 

5. Under DLMS, the unit price will be expressed as R9.2. 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. Under DLMS the unit price 

will be expressed as R9.2.

Clarification 

provided for new 

business rule and 

data construct. 

(5) Update DS 511M, Requisition Modification: 

# Location Revision to 

511M Requisition Modification

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/PO104/30 Add the following Data Element level note:

PO104 Unit Price 

DLMS Note: 1. For nonreimbursable material (free issue), 

indicate 0 dollars. 

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

Clarification 

provided for new 

business rule and 

data construct. 
ADC 221A, Enclosure 1, Page 4

3. Estimated unit price for nonstandard material is a DLMS 

enhancement, see introductory note 3a. 

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

requisition modifier. 

5. Under DLMS, the unit price will be expressed as R9.2. 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. 

(6) Update DS 527D, Due-in/Advance Receipt /Due Verification: 

# Location Revision to 

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

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/AMT01/100 Add new DLMS Note 4 to qualifier NT:

NT Unit Value 

DLMS Note: 1. Use to identify the standard unit price in 

Advance Receipt Information (ARI)/Prepositioned materiel 

Receipt (PMR) transactions. DLMS enhancement. 

2. Authorized for intra-Component use as needed. Component 

level procedures are required. 

3. 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 Navy 

Supply Procedures, NAVSUP Publication 485. See introductory 

DLMS note 4a for inter-Component use of this data. 

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. 

5. Authorized for use as needed for DLA industrial activity support 

agreement. Refer to ADC 419.

Clarification 

provided for new 

business rule and 

data construct. 
ADC 221A, Enclosure 1, Page 5

(7) Update DS 527R, Receipt, Inquiry, Response and MRA: 

# Location Revision to 

527R, Receipt, Inquiry, Response and MRA

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/AMT01/100 Add the following Data Element level note:

AMT01, Amount Qualifier Code 

DLMS Note: 1. DLMS transactions authorize an expanded unit 

price field size of 9 digits for dollars and 2 digits for cents. This is 

expressed as “R9.2” (R is the data element type indicating a 

decimal numeric data element). The decimal point is passed 

within the transaction; leading and trailing zeros are not 

transmitted. Use of the expanded field size is an authorized 

DLMS migration enhancement. See DLMS introductory note 5g. 

2. Until the expanded unit price field size is fully implemented, a 

field size exceeding 7 positions (5 digits dollars and 2 digits 

cents) may not be received or understood by the recipient’s 

automated processing system. DAAS will truncate the price for 

MILS users. If conversion to MILS legacy format is required, 

unit prices exceeding the legacy field size constraint will not be 

perpetuated.. Refer to ADC 221A. 

3. For DLMS use only the following codes are authorized. 

Clarification 

provided for new 

business rule and 

data construct. 

(8) Update DS 536L, Logistics Reassignment Management Data: 

# Location Revision to 

536L, Logistics Reassignment Management Data

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/CTP03/90 Add the following Data Element level note:

CTP03, Unit Price 

Federal Note: Do not use if no price applies. Express the contract 

unit price in dollars and cents, including the decimal. 

DLMS Note: DLMS transactions authorize an expanded unit 

price field size of 9 digits for dollars and 4 digits for cents. The 

decimal point is passed in the transaction. If conversion to 

Clarification 

provided for new 

business rule and 

data construct. 

Standardizes data 

element length for 

dollars across 

DLMS. This 
ADC 221A, Enclosure 1, Page 6

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. 

transaction supports 

up to 4 decimal 

positions in the 

legacy format 

(MILSTRAP 

DLW). 

(9) Update DS 810L, Logistics Bill: 

# Location Revision to 

810L, Logistics Bill

Reason for Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/IT104/010 Add the following Data Element level note:

IT104, Unit Price 

Federal Note: Use the billing unit price, including those cases 

wherein the item was issued either without charge or on a 

nonreimbursable basis. Use a decimal point to indicate amounts 

that are not in whole dollars. Use a "0" when the item is issued 

without charge. 

DLMS Note: 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. 

Clarification 

provided for new 

business rule and 

data construct. 

Standardizes data 

element length 

across DLMS. 

(10) Update DS 812L, Logistics Bill Adjustment Request Reply: 

# Location Revision to 

812L, Logistics Bill Adjustment Request Reply

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/CDD11/160 Add the following Data Element level note:

CDD11, Unit Price 

Federal Note: Use to identify the unit price of the adjustment 

quantity. Use a decimal point if the unit price is other than whole 

dollars. 

DLMS Note: DLMS transactions authorize an expanded unit 

Clarification 

provided for new 

business rule and 

data construct. 

Standardizes data 

element length 

across DLMS. 
ADC 221A, Enclosure 1, Page 7

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. 

(11) Update DS 812R, Logistics Bill Adjustment Request: 

# Location Revision to 

812R, Logistics Bill Adjustment Request

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/CDD11/160 Add the following Data Element level note:

CDD11, Unit Price 

Federal Note: Use to indicate the billed unit price. A decimal 

point must be used if the unit price is other than whole dollars. 

DLMS note: 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. 

Clarification 

provided for new 

business rule and 

data construct. 

Standardizes data 

element length 

across DLMS. 

(12) Update DS 846D, Logistics Reassignment Transfer and Decapitalization: 

# Location Revision to 

846D, Logistics Reassignment Transfer and Decapitalization

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/CTP03/110 Add the following Data Element level note:

CTP03, Unit Price 

Federal Note: Express the unit price in dollars and cents, 

including the decimal. 

DLMS Note: 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 

Clarification 

provided for new 

business rule and 

data construct. 

Standardizes data 

element length 

across DLMS. 
ADC 221A, Enclosure 1, Page 8

221A. 

(13) Update DS 869F, Requisition Follow-Up: 

# Location Revision to 

869F, Requisition Follow-Up

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/GF04/100 Add the following Data Element level note:

GF04, Monetary Amount 

DLMS Note: 1. Use for nonstandard and nonreimbursable 

material. For nonstandard material, express the estimated dollar 

amount in whole dollars. Do not include decimals or cents. For 

nonreimbursable (free issue) material, indicate "0" dollars. 

2. Estimated unit price for nonstandard material 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. Under DLMS, the unit price will be expressed as R9.2. 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. 

Clarification 

provided for new 

business rule and 

data construct. 

(14) Update DS 870M, Material Returns Supply Status: 

# Location Revision to 

870M, Material Returns Supply Status

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/PO104/150 Add the following Data Element level note:

PO104, Unit Price 

DLMS Note: 1. Applicable to the reply to the customer. 

2. Under DLMS the unit price will be expressed as R9.2. DLMS 

Clarification 

provided for new 

business rule and 

data construct. 
ADC 221A, Enclosure 1, Page 9

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; see introductory DLMS 4f. Refer to ADC 221A. 

(15) Update DS 945A, Material Release Advice: 

# Location Revision to 

945A, Material Release Advice

Reason for 

Change 

1 DLMS 

Introductory 

Note 

Add Addendum to ADC 221A to DLMS Introductory note:

- ADC 221A, Revised Procedures associated with the DLMS 

Enhancement for Communication of Unit Price 

To identify changes 

in the DS. 

2 2/AMT01/60 Add the following Data Element level note:

AMT01, Amount Qualifier Code 

NT Unit Value 

DLMS Note: 1. Use in CAV Material Release Confirmation 

transactions to indicate the unit price of an item. 

2. Use to identify the unit price applicable to the materiel 

identified by the release confirmation supporting NSYs and FRC 

under DLA industrial activity support agreement. Authorized 

DLMS enhancement; Refer to ADC 381. 

3. 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. 

Clarification 

provided for new 

business rule and 

data construct. 
 ADC 221A, Enclosure 2, Page 1

Enclosure 2, Comment Resolution 

Originator Concurrence/Comments Response 

1. DLA DLA concurs with this PDC without comment. 

There will be system testing (which may indicate 

required changes) in DLA systems (EBS/SAP, DSS, 

and MEBS). 

Noted. 

See response to Navy comments. 

Systems Change Request (SCR) 

may not have been documented 

for ADC 221. An SCR is 

required for this change. 

2. Army HQDA DCS G-44(S) Concurs with ADC 221 

(referenced above) expanded the field size for the 

unit price and total dollar value on the Issue 

Release/Receipt Document (IRRD) (DD Form 1348-

1A) and established a corresponding field size for 

the unit price in DLMS transactions as stated 

without comment. 

Noted. 

3. Navy The Navy concurs with Addendum to ADC221A as 

written and submits no additional changes or 

amendments. 

Initial comments. 

After reviewing PDC 221A, (addendum to ADC 

221) we are in need of clarification on portions of 

the content. 

Section 4 “Background:” stated that the original 

ADC 221 changed NOT ONLY the identified 

DLMS transactions by having them adopt an 11 

position unit price, (vice the 7 position price) but 

also changed the 1348-1A form in the same regard. 

 Section ‘5.a.‘ “Proposed Change(s):/Proposed 

procedures:” makes it clear that this addendum 

(221A) will rescind the portion of the original ADC 

221 dealing with the conversion/sending of prices 

between DLMS and MILS if the DLMS transaction 

price is greater than 7 digits, or if the MILS 

transaction price is specified as all 9’s. However, 

that section also states: “All other aspects of ADC 

221 are unchanged.” This seems to be saying that 

Noted. 

Refer to ADC 221 (see blue 

highlighting on page 5-7, there 

was a requirement for all 

Components to assure that 

scanners could handle the 

extended pricing if implemented 

by the originating system. We 

tried to leave flexibility 

wherever we could. It has 

become impossible to establish 

coordinated implementation 

dates but we need to allow those 

systems that are capable of 

moving forward to do so. 

Therefore, we discussed 

alternatives and interim 

procedures in the ADC, but the 

scanners were to be adjusted to 

preclude failure. There was a 

preference for blanking an 

extended price rather than 
ADC 221A, Enclosure 1, Page 2

the change to the 1348-1A form established by the 

original ADC 221 is not being rescinded. 

Question 1: Is that reading of the content accurate? 

A change to this form would adversely affect our 

system since we scan the standard bar codes on the 

form with our Automated Data Collection (ADC) 

devices to capture the relevant info including the 

price value. The programming for those devices 

cannot accommodate more than 7 positions for the 

price value. 

Question 2: Was the original ADC 221 ever 

implemented (including the change to the 1348-1A 

form)? We see that section 3 “Reference:” of the 

Addendum document states that ADC 221 was dated 

February 01, 2007, but we assume that was the 

submittal date rather than the implementation date. 

We have not encountered any 1348-1A forms with a 

price unit field having more than 7 positions. We 

have accessed P-485 via one of the NAVSUP 

websites, and find that the 1348-1A form shown in 

Volume 1 at paragraph 4114 still depicts 7 positions 

for the Price unit field. We also verified that the 

1348-1A form included on a recent receipt 

(3/23/2011) showed a 7 position Price unit field. 

Question 3: If ADC 221 has not been implemented, 

will it be? (If so, When?) 

Question 4: In the following circumstance, what will 

the 1348-1A show as a price after implementation of 

this addendum? The Circumstance is this: A DLMS 

856S is converted to a MILS ‘AS_’ to indicate 

shipment of a material to one of our NEMAIS sites. 

The price on the 856S is greater than 7 positions, so 

the price is not sent on the MILS ‘AS_ ‘ doc. But the 

material will physically arrive and will include a 

1348-1A. (Currently, the 1348-1A would show a 

series of 9’s. Will it still show that after this 

addendum is implemented? – or will it instead be 

blank spaces?, all zero’s?, or the actual price?) 

Question 5: What is the implementation date of this 

Addendum? Section 8 of this document states 

“Expected implementation date is June, 2010.” 

truncating it. 

The DD 1348-1A requirements 

from the original ADC 221 are 

still applicable. 

The implementation date has 

been updated. 

Under this ADC, the unit price 

(or total amount) should be left 

blank when the extended price 

cannot be accommodated. 

Regarding DSS implementation 

status, the following information 

has been provided: We have not 

really done anything to 

accommodate larger Unit Price 

or Total Price fields in DSS. We 

expanded one field on one table 

which is a drop in the bucket to 

what we would have to do to 

allow DSS to handle a 12 

position Unit Price. There will 

be lots of changes necessary in 

DSS to satisfy this requirement. 

We have not seen an SCR for 

these changes. We have not 

expanded bar codes either. For 

printing on the form, the values 

are currently truncated from the 

left. 
ADC 221A, Enclosure 1, Page 3

Since this date has already passed, we are wondering 

if this is a typo that should have indicated 2011, or if 

it actually refers to the original ADC 221 rather than 

this addendum. 

Navy ERP feedback: We are printing the extended 

price on the 1348-1A. I have an old mail to Deb 

Norman requesting her thoughts on the 2D barcode 

and if the mapping was going to change. I asked the 

integrator for the length. He says it is eight plus 2 

for the cents. This issue came up a couple of years 

ago and I believe I sent new mapping to Annapolis 

to expand the field. I guess it never happened. I 

reviewed ADC 221 again. The direction is to 

expand the extended price to 12 positions (10 whole 

dollars and 2 cents - no decimal point). 

4. Air Force Concurs Noted. 

5. USMC Concurs Noted. 

6. DPAP/IUID/ 

WAWF 

We have no comments/concerns at this time. Noted. 

7. DSCA The subject PDC does impact the Navy FMS MISIL 

System. NAVICP P761 supports the processing 

rule that no price will be forwarded on the MILS 

transactions when the actual price exceeds the actual 

number of positions in the MILS transaction. 

Noted.