ADC 221 

Communication of Unit Price and Total Price under DLMS 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Management Standards Office (DLMSO) 

b. Originator: Supply PRC, Chair: Ellen Hilert, DLA DLMSO/J-6251, Defense Logistics 

Management Standards Office (DLMSO), 703-767-0676 (DSN 427), ellen.hilert@dla.mil 

2. FUNCTIONAL AREA: Primary: Supply (MILSTRIP) 

3. REFERENCE: DLMSO memorandum dated June 6, 2006, subject: Approved Addendum 

44B to Approved DLMS Change (ADC) 44, Inclusion of Supplemental information for Unique 

Item Tracking/Serialized Item Management (UIT/SIM) in the Two-Dimensional Symbol on the 

Issue Release/Receipt Document (IRRD) (DD Form 1348-1A) (Supply/MILSTRIP) 

4. REQUESTED CHANGE: 

a. Title: Communication of Unit Price and Total Price under DLMS 

b. Description of Change: This change expands the field size for the unit price and total 

dollar value on the Issue Release/Receipt Document (IRRD) (DD Form 1348-1A). This change 

establishes a corresponding field size for the unit price in the DLMS transactions. This change is 

identified as a DLMS enhancement; the necessary implementation details are established by this 

document. This change applies to all the formats and transactions identified in the attachments; 

separate individual change documents will not be provided. Revisions to published guidance are 

identified in bold italics. Significant revisions resulting from the staffing process are highlighted. 

(Yellow and blue highlights are used because there were iterative changes to this document; the 

blue highlights were made subsequent to the “advance copy” distribution). 

c. Background: Currently, MILSTRIP transactions restrict the size of the unit price due to the 

space limitation within the 80 record position transactions. The current field size is 7 digits, 

structured with 5 digits for dollars and 2 digits for cents. The current total (extended) price field 

size for the IRRD is 9 digits, with 7 digits for dollars and 2 digits for cents. Although the DLMS, 

using variable-length transactions and the commercial X12 EDI standards or XML, could 

accommodate larger field lengths, there is no clear target field size documented for transition to 

DLMS. In addition, X12 field sizes vary among different transactions. Enclosure 1 provides 

examples of the current IRRD and package labels reflecting a truncated price resulting from lack of 

space on the MILSTRIP transaction. 

d. General Procedures: 

(1) DLMS transactions identified in this document will adopt an 11 position unit price 

which will be transmitted as 9 digits dollars, decimal point, and 2 digits cents. This is 
3

expressed as “R9.2” (R is the American National Standards Institute (ANSI) designation for the 

data element type indicating a decimal numeric data element. The number after the period indicates 

the number of decimal positions permitted. The decimal point is passed within the transaction; 

leading and trailing zeros are not transmitted. The transmission of the decimal point within the 

transaction is necessary under the ANSI syntax rules.) 

(2) The printed IRRD will be modified to allow a unit price as 11 positions, with 9 digits 

dollars and 2 digits cents, across the image bar at the top of the form (decimal point not printed on 

the IRRD). The linear bar code and 2D symbol on the IRRD will adopt the unit price as 9 digits 

dollars and 2 digits cents. Record position identification on the IRRD format will be disregarded 

for display of the expanded unit price within/overlapping the block lines for the unit price display. 

Leading and Trailing zeros are displayed in the unit price text. Retain display of leading zeroes up 

to the current 7 digit unit price on the image bar; otherwise, display leading zeros based upon 

available space.* Pink correction 2/8/2007

(3) Total (extended) price on the IRRD will be modified to 12 positions consisting of 10 

digits for dollars and 2 digits cents (decimal point not printed on the IRRD). The current IRRD 

block for total price does not have adequate space for display of 12 positions. If the total price 

exceeds 9 positions, implementing applications may leave blank on the printed form until such time 

as the block can be enlarged. Do not print a truncated total price. 

(4) MILSTRIP transactions will continue to carry the unit price as currently defined for 80 

record position transactions. There is no acceptable means to vary the business rules for processing 

an alternative field length within the 80 record position formats. This means that there will 

continue to be times where the data content is truncated, losing the leading dollar positions. 

5. DETAILED PROCEDURES: 

a. Update DLMS notes in each of the DLMS supplements as shown in Enclosure 2. 

b. Modify MILSTRIP Chapter 5, Release and Receipt of Materiel, Figure C5.F3 as shown in 

Enclosure 3. 

c. Modify each of the following MILSTRIP appendix formats, and corresponding formats as 

incorporated in the DLMS manual, as shown in Enclosure 4: 

(1) Appendix AP1.1, Forms/Message Formats (Introduction). 

(2) Appendix 1.25, Issue Release/Receipt Document Laser Printed Form With LOGMARS 

Bar Coding 

(3) Appendix 1.26 Issue Release/Receipt Document Preprinted Form With LOGMARS 

Bar Coding By Dot Matrix 

(4) Appendix 1.27, Issue Release/Receipt Document Preprinted Form Without LOGMARS 

Bar Coding Data 

(5) Appendix 1.28, Issue Release/Receipt Document Preprinted Form With LOGMARS 

Bar Coding By Dot Matrix Foreign Military Sales 

(6) Appendix 1.29, Issue Release/Receipt Document Laser Printed Form With 
4

LOGMARS Bar Coding Foreign Military Sales 

(7) Appendix 1.35, Issue Release/Receipt Document (IRRD) (1348-1A) With Three-OfNine Bar Coding and Two-Dimensional (2D) (PDF-417) Symbol 

(8) Appendix 3.48, Materiel Release Document DD Form 1348-1a or DD Form 

1348-2 

(9) Appendix 3.49, Transfers To Defense Reutilization And Marketing Office On DD Form 

1348-1a or DD Form 1348-2 (Single-Line Item Turn-Ins) 

d. IRRD. A mock-up to show the expanded unit price field on the IRRD is shown at 

Enclosure 5. This example uses a small font to fit the 11 digit unit price within the available space. 

Refer to 7.c, Concerns/Staffing Comments, below, for discussion of flexibility available for IRRD 

design. 

6. REASON FOR CHANGE: 

a. There is a negative DOD-wide impact of MILS field size restrictions for unit price resulting 

in the wrong price being communicated and perpetuated as a result of the space restriction on the 

original MILS transaction. 

b. The approved field lengths are based upon several factors. 

(1) DLMS transactions and printed forms are being revised to accommodate the 9 digits 

for dollars which is consistent with the unit price on electronic shipment notices for new 

procurements on contracts administered by Mechanization of Contract Administration Services 

(MOCAS). Components did not identify an alternative length during staffing. 

(2) There is no known requirement for more than two digits for cents on the logistics 

transactions modified by this change. There would be a potential for confusion in the printed price 

if additional decimals for cents were included at this time without redesigning the manner in which 

the display boxes are constructed. Components did not identify a requirement for additional 

decimal positions during staffing. 

(3) The total price was expanded from 9 to12 positions (10 digits for dollars and 2 digits 

cents) rather than 16 positions. It is understood that a16 position total price length is the result of 

the mathematical calculation using a maximum unit price at 11 positions (99999999999), times the 

quantity at 5 positions (99999), therefore requiring a 16-position field to store the sum total price. 

Components did not identify requirements for such a significant change in the size of the total price

data element; therefore, the originally proposed size of 12 is adopted for the approved change. 

e. Example of Negative Impact: Refer to the Enclosure 1 example of a DD Form 1348-1A 

where the total price field for 1 each is $130,420.00, but the unit price is listed as $30.420.00, as is 

the bar code unit price. The cents are retained, but the dollars are truncated; the actual price is 

$130,420.00, but the unit price is reflected as $30.420.00 because only 5 positions is allowed for 

dollars. In this specific example, where the price is scanned with a bar code reader, then the wrong 

price goes into Aviation Roundout Maintenance Management Information System (ARMMIS), 

causing problems in accounting exchanged using standard DOD logistics transactions and systems 

for individual items across the supply chain. 
5

7. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages: Supports consistent adoption of a DLMS enhancement for expanded field 

sizes and eliminates confusion within affected processes. 

b. Disadvantages: None identified. 

c. Concerns/Staffing Comments: 

 (1) Several comments were submitted during staffing expressing concern for the reference 

to truncating the unit price under MILS. This is a pre-existing condition; this change cannot modify 

the MILSTRIP transaction formats themselves. (Such a change would not be cost-effective, would 

be nearly impossible to coordinate and implement, and is expressly forbidden under the OSD 

guidance for transition to DLMS.) Note that when the MILSTRIP 80 rp format is used (whether 

generated by the sending application or the result of DAAS translation from the DLMS), the cents 

are always retained because that is the prescribed format recognized by MILS applications. It is the 

dollar figure which becomes truncated (refer to the Enclosure 1 example). 

 (2) The following comments were received from DLA J6UEA: 

... our interpretation of this ADC ... This is a phased/staggered approved ADC for which systems 

that choose to can, any time at their discretion, start generating/accepting the longer Unit Price 

and Total Price in the respective DLMS transactions, stretch the Linear Bar Code on the IRRD, 

stretch the corresponding HRI on the IRRD, stretch the 2D Bar Code on the IRRD, and squish the 

Unit Price of 11 into the 7 byte price within the image at the top of the IRRD (with disregard to the 

74-80 column headings. They are not to squish the Total Price however until the IRRD form is 

redesigned. We are however to ensure that when DAASC cuts over in 6 months that it is at least 

tame to not blow us out of the water (even if we aren't using the expanded data). 

Now for our questions: 

1) The cover letter cites that this is approved for phased/staggered implementation and that 

DAASC will change in 6 months. That will probably work for the DLMS transaction lengths and 

such, but is it really that simple for the physical IRRD printing? If some systems start to stretch the 

Linear Bar Code, respective HRI, and the 2D Bar Code, can you ensure that all systems around the 

world can interpret the data (bar code reader equipment, software which the data comes into, 

database lengths, etc)? It would almost seem that the new IRRD form would have to be provided 

and a major worldwide cut over of systems at some point to work? I know you have had many 

discussions for a long time about this, so maybe this is simpler and more forgiving than we think. 

DLMSO Response/Coordinated with AIT Office: The ADC will alert Components that they 

have six months to ensure that DLMS transactions and AIT driven process must be checked to 

ensure that they do not fail due to the expanded field length. They may need to modify the interface 

from the scanner to drop the extra digits if their application data base cannot accept the larger size. 

2) Some of the wording in the ADC, and I think your intent, is to allow 11 digits of Unit Price not 

counting the decimal itself (123456789.01) and 12 digits of Total Price (1234567890.12) correct? 

We then refer to that as the decimal is "implied" on a database for example (decimal is not stored 

as part of the data). However, on Page 3 it states that the decimal itself is carried within the DLMS 
6

transaction itself (we call that a "literal" decimal). That is correct, the decimal is in fact passed as 

data in DLMS transactions, however, it is then also accounted for within the IC as such. Hence, in 

our opinion, the ICs for Unit Price should say "12" and the Total Price should say "13" to make 

room for the digits and decimals. Even though typical system databases will be 11 and 12 

respectively. Is that how the ICs will read? 

DLMSO Response: The ADC has now been updated to be consistent in referring to the field size 

for the unit price as 11 digits and total price as 12 digits. The decimal is added for passing the 

transaction in the DLMS format as required by X12 syntax rules. Components may make internal 

decisions for storing of the decimal or storing a larger data field (e.g. commercial software may predetermine available space). 

3) Is this mandating that systems squish the 11 byte Unit Price within the image bar on the current 

IRRD form right away, or at their discretion, or never and can wait until the new IRRD form is out 

if the prefer? 

DLMSO Response: The intent of this ADC is to mandate the printing of the 11 digit price on the 

image bar at the same time program changes are made to expand the linear bar code and HRI. In 

order to print the unit price on the image bar it may be necessary to “type” over the existing line 

outlining the box surrounding the unit price data field or reduce the size of the font. This would 

only be necessary when the unit price uses full the length of the allowed dollars (leading zeros need 

not be displayed beyond the current 5 digits which easily fit). A mock-up example using reduced 

font size to fit within the available space is shown at Enclosure 5, at the end of this document. In 

addition, the intent is to also change the 2D symbol to carry the expanded size concurrently. In 

other words, when changes are made to allow for the expanded field sizes, this information should 

be consistently displayed in all formats/displays/AIT associated with the IRRD. 

4) Similar to 3 above, are you saying that we should never squish the Total Price on the current 

IRRD? 

DLMSO Response: Without some re-engineering, it may be very difficult to insert the full12 digit 

extended price so this change does allow flexibility to leave this field blank. Where possible, it is 

preferred that the total price be displayed (leading zeros need not be displayed where space is not 

available). The intent of the flexibility allowed is to eliminate the display of truncated total prices

during transition to an improved IRRD which may take more significant re-programming than 

would be feasible at this time. It is preferred that the field be left blank rather than provide 

incorrect information. Since the unit price would be correct, the customer, or the receiving 

application, will be able to calculate the correct extended price. 

5) On Page 3, and throughout the document in other places, it states that if the Total Price exceeds 

9 positions "applications may leave blank on the printed form until such time as the block can be 

enlarged". Today we truncate and were not planning to change that. Are you saying that we 

"must" set to spaces or it is at our discretion? 

DLMSO Response: Same issue as discussed in 4) above. Yes, program changes are required to 

eliminate truncated values during implementation of any portion of this change. 
7

6) What is the status of a new IRRD form and who is participating?` 

DLMSO Response: An earlier effort to redesign the IRRD to support DLMS was tabled. DLMSO 

is not currently addressing this aspect of modernization. 

8. IMPACT: 

a. General: This change impacts DLMS-capable applications and those in the process of 

planning for migration. This change may be implemented on a phased and staggered basis without 

prior coordination with trading partners. Components may implement selected portions of this 

change while delaying implementation of others for a later date. DLMS-capable receiving 

applications which have not yet adopted the DLMS expanded field length should adjust their 

programs to ensure that the expanded length in an incoming transaction will not cause transactions 

to reject. Components implementing DLMS may determine the best approach for their application 

pending full implementation. It is conceivable that a Component may receive a DLMS format 

containing a unit price value which makes use of the increased field size, prior to any necessary 

internal database modifications. It will be the responsibility of the Component to convert the unit 

price in the transaction to fit the available space in their database. There may also be an impact 

resulting from inclusion of the expanded unit price field in the linear bar code and 2D PDF 417 

symbol. This is addressed in paragraph 8.d. below. 

b. Near Term: It is hoped that this change will provide immediate relief for some applications 

using the price as reflected on the IRRD or communicated via DLMS. DLA Business Systems 

Modernization (BSM) uses DLMS formats and has a database which supports expanded field sizes. 

Therefore, BSM would be target for near-term implementation of portions of this change. Since the 

Distribution Standard System (DSS) for Defense Distribution Depot shipments is DLMS-based and 

is in the process of expanding their database field sizes, initial implementation of at least some 

portions of this change are also targeted at DSS. 

c. Distribution Standard System (DSS) Near Term: DLA is working to implement a 

systems change request (SCR) for DSS 7.2 (DSS-HQ5-053) for which they will be providing some 

of the described revisions, but exclusively for Air Force when they provide us bigger prices within 

exception data. DSS will recognize the situation and stretch the Linear Bar Code and human 

readable interpretation (HRI). However, DSS will not be “squishing” the larger unit price size into 

the image bar (font would be too small), nor does it go into the 2D as that was not a requirement. 

DSS is not stretching the Linear Bar Code and HRI for all customers, just these unique data driven 

situations. All other IRRDs will remain current length due to uncertainty of impact on other users. 

DLA may reconsider stretching the fields on all IRRDs, but is concerned about impact and because 

the IRRD form on Intermec printers in particular has no room to stretch without HQ/DDC reengineering their desired data and placement. (Additional programming requires development of an 

SCR from HQ/DDC.) 

d. Interim AIT Requirement Pending Full Implementation: Components are responsible 

for updating AIT reader software, to include filters or edit sequences, which restrict the unit price 

field length to 7 digits. Components must ensure that scanners will not fail if they encounter a 

linear bar code or 2D symbol containing a unit price with a maximum of 9 digits for dollars (current 

maximum for dollars is 5 digits) and 2 digits for cents. How the unit price is transferred to the 

processing system may depend upon limitations of the processing system. At a minimum, the 
8

current unit price field length may be extracted until such time as the application data base is 

modified or replaced under modernization. This capability (ensuring scanners will not fail) must be 

available within 6 months of the date of ADC publication. 

e. MILS/DLMS Transition: This change provides guidance for Components adopting the 

DLMS. This change should be integrated in the design as Components adopt DLMS. During 

transition, if necessary for high unit price items, the Defense Automatic Addressing System 

(DAAS) will truncate unit price created under DLMS and converted to the original 80-rp format to 

accommodate MILS users. 

f. Long Term: The adoption of DLMS with expanded field size will eliminate price confusion 

and inaccuracies for high dollar value material DOD-wide. 

g. Requires update to Component implementing guidance. 

h. Requires update to MIL-STD-129. 

i. This change impacts the Defense Automatic Addressing System (DAAS), Global 

Transportation Network (GTN), and other applications maintaining a historical database and query 

capability so that appropriate field sizes may be saved and displayed. For example, DAAS must 

adjust the WebVLIPS screen to permit the accurate display of the unit price. 

j. In addition to transaction and database field lengths, changes will need to be made to 

programs using these fields, screens displaying these fields, print programs, and forms. 

k. This change may also impact transactions used in other functional processes, such as 

transportation, or which are internal to the Components, and perpetuate the price/cost information 

derived from the transactions identified in this change. 

Enclosures 
9
10
11

Enclosure 2 – DLMS Supplement (DS) Updates

(1) Add new cover page introductory note to DSs listed below (number as 

applicable): 

Data associated with a DLMS enhancement authorized for implementation by 

modernized systems under DLMS migration. This data (including expanded 

field sizes) should be adopted during, or subsequent, to modernization when 

applicable to the Component’s business process. Prior coordination is not 

required. Components should ensure that inclusion of this data in a DLMS 

transaction does not cause inappropriate rejection of the transaction.

 (2) Update DS 511R, Requisition: 

2/P01/30 PO104, Unit Price

DLMS Note: 

1. For nonreimbursable material (free issue), indicate 0 dollars. 

2. Use for nonstandard and nonreimbursable (free issue) material to 

indicate an estimated price. For nonstandard material, express the 

estimated dollar amount in whole dollars. Do not include decimals 

or cents.

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. 

PO105, Basis of Unit Price Code 

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

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

price. 

AA Bill 

DLMS Note: 

Used on the first iteration of the PO1 segment on DoD 

EMALL/part-numbered catalog orders to indicate the unit price that 

the requisitioner is to be billed. 

CT Contract 

DLMS Note: 

Used on the second iteration of the PO1 segment on DoD 

EMALL/part-numbered catalog orders to indicate the contract unit 

price that the vendor/supplier of the part can invoice. 

ES Estimated 

DLMS Note: 

Use to indicate an estimated unit price for the nonstandard material. 

NC No Charge 

Original note 

wording 

rearranged for 

clarity. 

Note 3a is the 

note which 

requires 

coordination 

prior to use. 
12

DLMS Note: 

Use to indicate nonreimbursable (free issue) material. 

 (3) Update DS 511M, Modification: 

2/P01/30 PO104, Unit Price

DLMS Note: 

1. For nonreimbursable material (free issue), indicate 0 dollars. 

2. Use for nonstandard and nonreimbursable (free issue) material to 

indicate an estimated price. For nonstandard material, express the 

estimated dollar amount in whole dollars. Do not include decimals 

or cents.

3. Estimated unit price for nonstandard material is a DLMS 

enhancement, see introductory note 3a. 

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

PO105, Basis of Unit Price Code 

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

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

price. 

ES Estimated 

DLMS Note: 

Use to indicate an estimated unit price for the nonstandard material. 

NC No Charge 

DLMS Note: 

Use to indicate nonreimbursable (free issue) material. 

Original note 

wording 

rearranged for 

clarity. 

Note 3a is the 

note which 

requires 

coordination 

prior to use.

(4) DS 869F, Requisition Follow-up: 

2/GF/100 GF04, Monetary Amount

DLMS Note: 1. Use for nonstandard and nonreimbursabe 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. 
13

(5) DS 870S, Supply Status 

Location Update Comments 

2/P01/150 PO104, Unit Price 

PO105, Basis of Unit Price Code 

Federal Note: 

1. Use to identify the correct unit price associated with the status 

provided. 

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

Authorized DLMS migration enhancement; see introductory 

DLMS 3f. 

ES Estimated 

DLMS Note: 

Use to indicate the estimated unit price billed when Code ST does 

not apply. 

ST Standard 

DLMS Note: 

Use to identify the standard unit price billed for the material. 

(6) DS 870M, Material Returns Supply Status 

2/P01/150 PO104, Unit Price 

DLMS Note: 

1. Applicable to the reply to the customer asset report. 

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

Authorized DLMS migration enhancement; see introductory 

DLMS 4f. 

(7) DS 856S, Shipment Status: 

2/REF/1500 PA, Price Area Number 

DLMS Note: 

1. Use for shipments to disposal to indicate actual or estimated 

pricing information. 

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. See introductory DLMS note 2d. 

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

Authorized DLMS migration enhancement; see introductory 

DLMS 2f. 
14

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

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

Authorized DLMS migration enhancement; see introductory 

DLMS 4f. 

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

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

CAV specific 

implementation. 

Request 

verification that 

DAAS 

conversion is 

not applicable. 
15

DOD 4000.25-1-M

Enclosure 3 - MILSTRIP Chapter 5, Figure C5.F3

RECORD POSITION(S) ENTRY AND INSTRUCTIONS 

1-3 Perpetuate from source document or blank. 

4-7 Leave blank. 

8-22 Enter the stock or part number. 

23-24 Enter the U/I. 

25-29 Enter the quantity. 

30-43 Enter the document number of the consignor (shipper.) 

44-73 Leave blank. 

74-80 Enter the unit price1

. 

Blocks 3 and 27 Enter DoDAAC of the activity to which the materiel is 

directed. The in-the-clear name, number, and address may be 

in Block 27. 

Block 27 Enter the supply condition code reflecting the condition of the 

materiel. (See DoD 4000.25-2-M (MILSTRAP).) 

Block 27 Enter activity account number of the activity to be credited (if 

applicable) and the appropriate fund code (if applicable). 

(See DoD 4000.25-7-M (MILSBILLS).) Enter applicable 

IUID content in conjunction with application of a 2D symbol 

as listed in AP1.1 and illustrated in AP1.35 2

. 

Figure C5.F3. Instructions for completion of DD Form 1348-1A (or DD Form 1348-2) used 

for Returns to Stock Transfers (excluding Transfers to Defense Reutilization 

and Marketing Offices) 

 

1 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will 

reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for 

display on the printed form, the generating application may leave blank. Refer to ADC 221. 

2 See Footnote 1.
16

DOD 4000.25-1-M 

Enclosure 4

AP1.1. APPENDIX 1.1

FORMS/MESSAGE FORMATS

(INTRODUCTION)

Following is an extract from AP1.1: 

AP1.1.6.6.3. The Issue Release/Receipt Document data elements, configuration and locations 

are as follows: 

DATA ELEMENT NAME LENGTH RECORD POSITION(S)

Document Identifier 3 1-3 

Routing Identifier (From) 3 4-6 

Media and Status 1 7 

Unit of Issue 2 23-24 

Quantity 5 25-29 

Service 1 45 

Supplementary Address 5 46-50 

Signal 1 51 

Fund 2 52-53 

Distribution 3 54-56 

Project 3 57-59 

Priority 2 60-61 

Required Delivery Date 3 62-64 

Advice 2 65-66 
17

DATA ELEMENT NAME LENGTH RECORD POSITION(S)

Routing Identifier 3 67-69 

Ownership/Purpose 1 70 

Condition 1 71 

Management 1 72 

 1 73 

Unit Price1 7 74-80 

 

1 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will 

reflect the unit price as 9 digits for dollars and 2 digits for cents. Refer to ADC 221. 
18

BLOCK ELEMENT NAME

BLOCK SIZE/

NO. OF 

CHARACTERS BLOCK NUMBER

Total Price 10 122 1 

Ship-From 10 2 

Ship-To 9 3 

Mark-For 19 4 

Doc Date 5 5 

NMFC 9 6 

Freight Rate 8 7 

Type Cargo 10 8 

Physical Security 4 9 

Quantity 7 10 

Unit Pack 3 11 

Unit Weight 10 12 

Unit Cube 7 13 

UFC 6 14 

Shelf Life 3 15 

Freight Classification Nomenclature 36 16 

Item Nomenclature 36 17 

Type Container 5 18 

No. of Containers 8 19 

Total Weight 13 20 

Total Cube 10 21 

 

2 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will 

reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for 

display on the printed form, the generating application may leave blank. Refer to ADC 221. 
19

BLOCK ELEMENT NAME

BLOCK SIZE/

NO. OF 

CHARACTERS BLOCK NUMBER

Received By 26 22 

Date Received 10 23 

Document Number and Suffix (30-44) 44 24 

National Stock Number and Additional (8-22) 44 25 

RI (4-6) UI (23-24) QTY (25-29) COND Code 

(71) Dist (55-56) UP (74-80)3

80 26 

Additional Data 

For IUID to support UIT/serialized item 

management, include the following4: 

Unique Item Identifier (UII) 

and/or 

Serial Number 

The following additional data elements may be 

included in support of IUID: 

Manufacturer’s CAGE 

Current Part Number 

 Batch/Lot 

Clear text labeling of IUID information must be 

provided using the following acronyms: CAGE, 

P/N, BT/LT, S/N, and UII. 

Various 

Field size and 

characteristics of 

item unique 

identification data 

content and 

specific policy 

guidance is 

available at: 

http://www.acq.os

d.mil/dpap/UID/. 

27 

 

3 See Footnote 1. 

4 Capability to support IUID data content within the 2D symbol has been approved for staggered and phased 

implementation under ADC 44B. Components have not reported implementation at this time. 
20

AP1.25. APPENDIX 1.25

ISSUE RELEASE/RECEIPT DOCUMENT

LASER PRINTED FORM WITH LOGMARS BAR 

CODING1

____________________

1

 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will 

reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for 

display on the printed form, the generating application may leave blank. Refer to ADC 221.

1
21

AP1.26. APPENDIX 1.26 

ISSUE RELEASE/RECEIPT DOCUMENT

PREPRINTED FORM WITH LOGMARS BAR CODING 

BY DOT MATRIX1

____________________

1

 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will 

reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for 

display on the printed form, the generating application may leave blank. Refer to ADC 221.

1
22

AP1.27. APPENDIX 1.27

ISSUE RELEASE/RECEIPT DOCUMENT

PREPRINTED FORM WITHOUT LOGMARS BAR 

CODING DATA1

____________________ 

1

 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will 

reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for 

display on the printed form, the generating application may leave blank. Refer to ADC 221. 
23

AP1.28. APPENDIX 1.28

ISSUE RELEASE/RECEIPT DOCUMENT

PREPRINTED FORM WITH LOGMARS BAR CODING 

BY DOT MATRIX FOREIGN MILITARY SALES1

____________________ 

1

 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will 

reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for 

display on the printed form, the generating application may leave blank. Refer to ADC 221. 
24

AP1.29. APPENDIX 1.29

ISSUE RELEASE/RECEIPT DOCUMENT

LASER PRINTED FORM WITH LOGMARS BAR 

CODING FOREIGN MILITARY SALES1

____________________

1

 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will 

reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for 

display on the printed form, the generating application may leave blank. Refer to ADC 221.
25

 DOD 4000.25-1-M 

AP1.35 APPENDIX 1.35 

ISSUE RELEASE/RECEIPT DOCUMENT (IRRD) (1348-1A) 

WITH THREE-OF-NINE BAR CODING AND 

TWO-DIMENSIONAL (PDF-417) SYMBOL1

[Note: Above data content is provided for illustration only. Implemented 

version may differ in placement and size of 2D symbol]. 

____________________

1 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will 

reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for 

display on the printed form, the generating application may leave blank. Refer to ADC 221.

00001 05020 0 0 05020 0 0

S9IEA0001A7V0502000

UII UN077991289S123TS001100223 

CAGE 12345 P/N 9988771212SP 

LOT MGU12345 S/N 123TS001100223

PARTIAL
26

AP1.35-1

DOD 4000.25-1-M 

Two-Dimensional (PDF-417) Label Format 

Compliance 

Character

Data 

Identifier/ 

Data Element 

Identifier [1]/

Data Field 

(DoD Usage)

Data Format 

(Type/Length)

Sample Data 

(Identifier and

Data Field)

Element 

Separators

Total 

Characters[2]/

[)> Compliance 

Indicator 

a3 [)> R

S 4

06 Format Indicator 

(ANSI Standard)

n2 06 G

S 3

12S Document Number 

Includes Suffix 

Code when 

applicable

an14..an15 W90GF882962058 G

S 19

N National/NATO 

Stock Number 

(NSN) or Stock 

Identification 

Elements 

May reflect NSN, 

CAGE Code/part 

number, FSC, etc., 

as applicable. May 

also include 

associated coding, 

e.g., Type of Pack, 

USN Special 

Material 

Identification Code 

(SMIC) or USAF 

Materiel 

Management 

Aggregation Code 

(MMAC) This data 

content is analogous 

to the MILSTRIP 

stock number field. 

For unique item 

tracking/serialized 

item management 

use this identifier 

an..15 5340013145957 G

S 17
27

for the NSN and use 

separate identifiers 

listed below to 

uniquely identify a 

specific individual 

item. 

7Q Quantity1 and Unit 

of Issue 

Do not include 

leading zeros

An..5+an2 7Q1EA G

S 10

V Routing Identifier 

Code

an3 VS9I G

S 5

2R Condition Code an1 2RA G

S 4

12Q Unit Price 

 Configured as 5 9

digits whole dollars, 

decimal, and 2 

digits cents 

followed by “USD” 

indicating U.S. 

dollars. Do not 

include leading 

blanks.

n..5.n2+an3

n..9.n2+an3

12Q5020.20USD G

S 15

19

5P National Motor 

Freight 

Classification 

Commodity 

Number

n6 5P999912 G

S 9

25S Unique Item 

Identifier (UII) 

The unique 

identification 

assigned by the 

supplier or DoD to 

an entity for its 

lifetime. 

an..78 25SUN077991289S123TS001100223 G

S 82 

S Serial Number an..30 S123TS001100223 G

S 32 

IT Traceability Number 

Assigned by the 

supplier (or DoD) to 

identify/trace a unique 

group of entities (e.g. 

lot, batch, etc.). May 

be used separately or 

in conjunction with 

UII. 

an..17 ITMGU12345 G

S 20 

 

1 The item quantity will be “1” if serial number and/or UII is provided within the 2D symbol. 
28

17V Manufacturer ID 

Commercial and 

Government Entity 

Code (CAGE). 

The manufacturer’s 

Commercial and 

Government Entity 

Code (CAGE) 

applicable to the 

identified item. If 

CAGE is not 

available, may use 

DUNS (12V) or 

UCC/EAN (3V) to 

identify the 

manufacturer. 

an..5 17V12345 G

S 9 

1P Part Number 

The part number 

currently in use to 

identify this item. 

an..16 1P9988771212SP R

S 19 

07 Format Indicator 

(ANSI Free Text)

n2 07 G

S 3

03 Project Code an3 03ZCN G

S 6

B6 DoD Distribution 

Code 

Three-position field 

must reflect blanks 

as applicable. 

Blanks may be 

located in any 

position. 

an3 B6_7V G

S 6

27 Consignee 

DoDAAC 

Reflects ship-to 

DoDAAC (Block 3)

an6 27WK4FV9 G

S 9

38 Nomenclature an..20 38LOOP, STRAP G

S 23

32 Required Delivery 

Date (RDD) 

May reflect RDD in 

DDD format or 

special codes, e.g., 

expedited shipment 

and handling (Code 

999), Not Mission 

Capable Supply 

(NMCS) (Code 

N__), etc. 

an..3 32999 G

S 6

B7 Requisition Priority 

Designator (PD)

n2 B702 G

S 5

B8 Partial Shipment 

Indicator

a1 B8P G

S 4
29

81 Supplementary 

Address 

Derived from rp 45-

50 of the requisition

an6 81WK4FV9 R

S EOT 10

All data identifiers are alphanumeric characters. 

a = Alphabetic Data 

an = Alphanumeric Data. May include special characters. 

n = Numeric Data 

.. = Variable Length (up to maximum shown)

R

S = Nonprintable hexadecimal code indicating next entry is a new compliance character indicating a new data 

identifier format follows

R

S EOT = Nonprintable hexadecimal code indicating end of transmission 

_ = Denotes a blank in sample data above 

Sample data stream: 

[)>R

S06GS12SW90GF882962058GSN5340013145957GS7Q1EAGSVS9IGS2RAGS 12Q05020.20USDGS5P999912GS 

25SUN077991289S123TS001100223G

S S123TS001100223GS ITMGU12345GS17V12345GS1P9988771212S RS

07G

S03ZCNGSB6 7VGS27WK4FV9GS38LOOP, STRAPGS32999GSB702GSB8PGS 81WK4FV9RSEOT 

Sample PDF 417 symbol (contents do not match above data stream - for illustrative purpose only): 

(Estimated Size) 
AP3.48. APPENDIX 3.48

MATERIEL RELEASE DOCUMENT

DD FORM 1348-1A OR DD FORM 1348-2

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier 1-31 Perpetuate from requisition or source document 

unless otherwise indicated. 

Routing Identifier (From) 4-62

 Enter the RI code of the shipping activity. 

Media and Status 7 Enter the M&S code assigned to the requisition or 

source document. 

Stock or Part Number 8-22 Indicate the NSN or part number being released. 

See Block 25. 

Unit of Issue 23-24 Indicate the U/I of the NSN or part number being 

released. 

Quantity 25-29 Indicate the quantity being released. See Block 26. 

Document Number 30-43 Enter the document number of requisition. See 

Block 24. 

Suffix Code 44 Leave blank if the document represents release of 

the total quantity requisitioned. Indicate the 

appropriate suffix code assigned to indicate a 

partial quantity release. See Block 24. 

Supplementary Address 45-503

 Perpetuate from the original requisition or source 

document. See Block 26. 

Signal 514

 Perpetuate from the original requisition or source 

document. 

 

 

1

 Procedures, formats, and codes for requisitioning material from disposal last reported as not implemented by DLA. Refer 

to AMCL 139A. 

2

 See Footnote 1. 

3

 See Footnote 1. 

4

 See Footnote 1.
31

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Fund 52-535 Perpetuate from the original requisition or source 

document. 

Distribution 54-566 Perpetuate from the original requisition or source 

document. 

Project 57-597 Perpetuate from the original requisition or source 

document. 

Priority 60-618

 Perpetuate from the original requisition or source 

document. 

Required 62-649

 Perpetuate from the original requisition or source 

document. 

Advice 65-6610 Perpetuate from the original requisition or source 

document. 

Routing Identifier 67-6911 Perpetuate from the original requisition or source 

document. 

Management 70-73 Perpetuate from the original requisition or source 

document. 

Unit Price12 74-80 Indicate the unit price of item being released. 

See Block 26. 

BLOCK(S) ENTRIES

1 Total price (10 digits dollars and 2 digits cents).12 

2 DoDAAC of shipping activity/DRMO. If reduced print in used, in-the-clear address 

may be entered in addition to the DoDAAC. 

3 DoDAAC of the activity to receive the shipment, if applicable. If reduced print is 

used, in-the-clear address may be entered in addition to the DoDAAC. 

 

5

 See Footnote 1. 

6

 See Footnote 1. 

7

 See Footnote 1. 

8

 See Footnote 1. 

9

 See Footnote 1. 

10 See Footnote 1. 

11 See Footnote 1. 

12 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will reflect the 

unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for display on the printed 

form, the generating application may leave blank. Refer to ADC 221. 
32

4 DoDAAC of the MARK FOR recipient, if applicable. If reduced print is used, in-theclear address may be entered in addition to the DoDAAC. 

5 Document preparation date (enter numerical day of year). 

BLOCK(S) ENTRIES

6 National Motor Freight Classification Commodity Number. 

7 Freight rate for the shipment. 

8 Type of cargo code (see DTR, DoD 4500.9-R). 

9 Enter applicable controlled inventory item code which describes the classified and/or 

sensitive or pilferage classification of the shipment from DoD 4100.39-M (FLIS 

Procedures Manual), volume 10, chapter 4, Table 61. (Mandatory Entry)13

10 Actual quantity received. 

11 Unit pack of item shipped. 

12 Unit weight of item shipped. 

13 Unit cube of item shipped. 

14 Uniform Freight Classification (UFC) Commodity Number. 

15 Shelf life of item shipped. Enter “SL” (for shelf life) followed by applicable shelf-life 

code from DoD 4100.39-M (FLIS Procedures Manual) Volume 10, Chapter 4, Table 

50. (Mandatory Entry)14

16 Freight classification nomenclature. 

17 Item nomenclature. 

18 Type of container used for the shipment. 

19 Number of containers that make up the shipment. 

20 Total weight of all containers that make up the shipment. 

21 Total cube of all containers that make up the shipment. 

22 Received by, signature of receiver, or call sign/code of individual authorized access to 

the automated file. 

23 Date received, date shipment was received. 

24 Document Number - The document number assigned to the requisition.15

 

13 Mandatory requirement to enter the controlled inventory item code (CIIC) and shelf-life code on the DD Form 1348-1A 

for issues from stock last reported as not implemented by USN. Refer to AMCL 32. 

14 See Footnote 13.

15Prepare data from blocks 24-26 in two configurations; (1) three-of-nine bar code and (2) in-the-clear. When prepared 

manually, do not include bar code. 
33

 Suffix Code - Blank if the document represents release of the total quantity 

requisitioned. If partial shipment, the appropriate suffix code assigned to indicate 

partial quantity released. 

 

25 National Stock Number - Enter the stock or part number being released. 

 Add - For subsistence items, enter the type of pack code in position 21.16

FOR OTHER THAN FMS SHIPMENTS

26 Routing Identifier - The RI code of the shipping activity. 

 Unit of Issue - The unit of issue of the stock or part number being released. 

 Quantity - The quantity being released. 

 Condition Code - The supply condition code of materiel being released. 

 Distribution - Perpetuate from record positions 55 and 56. 

 Unit Price17 - The unit price for the NSN/part number being released..

18

27 This block may contain additional data including bar coding for internal use. This 

block may contain a 2D symbol which repeats bar coded data content. Data entered in 

this block is as required by shipping activity by commodity. When data is entered in 

this block, it will be clearly identified. 

 DTID or ERN - On issues from DRMO, enter DTID or ERN, if applicable.19

 

16See Footnote 14. 

17 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will reflect the 

unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for display on the printed 

form, the generating application may leave blank. Refer to ADC 221. 

18See Footnote 14. 

19 See Footnote 1.
34

 USML Items – This block will contain clear-text information to identify shipments of 

USML items which may require filing of export licenses and SEDs per 22CFR126.4 

and 22CFR123.22 as follows: “USML item—may need SED.” 

For IUID to support UIT/serialized item management20: 

Unique Item Identifier (UII) and/or Serial Number 

The following additional data elements may be included in support of IUID: 

Manufacturer’s CAGE 

Current Part Number 

 Batch/Lot 

Clear text labeling of IUID information must be provided using the following 

acronyms: CAGE, P/N, BT/LT, S/N, and UII. 

FOR FMS SHIPMENTS21

26 Unit of Issue - two positions - the unit of issue of the stock or part number being 

released. 

 Quantity - five positions - the quantity being released. 

 Condition - one position - the supply condition code of materiel being released. 

 Unit Price 22 - seven positions - the unit price for the NSN/part number being released. 

 Supplementary Address - the first position and last three positions of the 

supplementary address. 

27 This block may contain additional data including bar coding for internal use. This 

block may contain a 2D symbol which repeats bar coded data content. Data entered in 

this block is as required by shipping activity by commodity. When data is entered in 

this block, it will be clearly identified. 

 USML Items – This block will contain clear-text information to identify shipments of 

USML items which may require filing of export licenses and SEDs per 22CFR126.4 

and 22CFR123.22 as follows: “USML item—may need SED.” 

 

20 Capability to support IUID data content within the 2D symbol has been approved for staggered and phased 

implementation under ADC 44B. Components have not reported implementation at this time. 

21 Requirement to add bar-coded Foreign Military Sales data to the Issue Release/Receipt Document last reported as not 

implemented by USN and USMC. Refer to AMCL 8. 

22 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will reflect the 

unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for display on the printed 

form, the generating application may leave blank. Refer to ADC 221. 
35

 For IUID to support UIT/serialized item management23: 

Unique Item Identifier (UII) and/or Serial Number 

The following additional data elements may be included in support of IUID: 

Manufacturer’s CAGE 

Current Part Number 

Batch/Lot 

Clear text labeling of IUID information must be provided using the following 

acronyms: CAGE, P/N, BT/LT, S/N, and UII. 

 

23 See footnote 18. 
DoD 4000.25-1-M 

36 

AP3.49. APPENDIX 3.49

TRANSFERS TO DEFENSE REUTILIZATION AND 

MARKETING OFFICE ON DD FORM 1348-1A OR

DD FORM 1348-2

(SINGLE-LINE ITEM TURN-INS)

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier 1-3 Perpetuate from the source document. For locally 

determined excesses generated at a base, post, 

camp, or station, assign a DI as determined by S/A 

procedures. 

Routing Identifier 4-6 Enter the RI of the shipping activity or leave blank 

when the shipping activity is not assigned an RI. 

Media and Status 7 Leave blank. 

Stock or Part Number 8-22 Enter the stock or part number being turned in. 

For subsistence items, enter the type of pack in rp 

21. See Block 25. 

Unit of Issue 23-24 Enter the unit of issue of the stock or part number 

being turned in. 

Quantity 25-29 Enter the quantity being turned in to DRMO. 

Document Number 30-43 Perpetuate from source document. This cannot be 

the same document number that was used to 

receive the materiel. For locally determined 

excess generated at base, post, camp, or station, 

assign as determined by S/A procedures. See 

Block 24. 

Suffix 44 Leave blank. 

Supplementary Address 45-50 Enter DoDAAC of predesignated consignee 

DRMO. 
37

Signal 51 For hazardous materiel and waste turn-ins, enter 

the applicable signal code; otherwise, leave blank. 

Signal Codes A, B, C, and L are authorized; if 

using Signal Code B, bill-to office must be 

identified in block 27. Refer to Appendix AP2.10, 

Signal Codes, for bill-to identification rules 

associated with DTID. 

Fund 52-53 For Hazardous materiel and waste turn-ins, enter 

the MILSBILLS fund code designating the fund to 

be charged. 

Distribution 54 Perpetuate from source document or leave blank. 

Retention Quantity 55-61 Enter the quantity to be retained in inventory or 

leave blank. 

Precious Metals 62 Enter applicable code from appendix AP2.23. 

Automated Data Processing 

Equipment Identification 

63 Enter applicable code from appendix AP2.24. 

Disposal Authority 64 Enter applicable code from appendix AP2.21. 

Demilitarization 65 Enter code assigned as required by DoD 4160.21-

M-1. Note: When demilitarization has been 

accomplished prior to transfer to DRMO, the 

appropriate demilitarization certification, as 

required by DoD 4160.21-M-1, must be reflected 

in Block 27. 

Reclamation 66 Enter code “Y” if reclamation was performed prior 

to release to a DRMO. Enter “R” if reclamation is 

to be performed after turn-in to DRMO. Enter 

code “N” if reclamation is not required. 

Routing Identifier 67-69 Perpetuate from DRO. 

Ownership 70 Enter applicable code or leave blank. 

Supply Condition 71 Enter the applicable MILSTRAP code. 

Management 72 Perpetuate from source document or leave blank. 

Flight Safety Critical 

Aircraft Parts 

731

 Enter criticality code E to indicate Flight Safety 

Critical Aircraft Parts or Code F to indicate Flight 

Safety Critical Aircraft Parts. 

 

1

Identification of FSCAP codes on the DTID and disposal release transactions last reported as not implemented by USA 

and USN. Refer to Approved DLSS/DLMS Change 6. 
38

Unit Price 74-80 Enter the unit price for the NSN or part number in 

rp 8-22.2 

BLOCK(S) ENTRIES

1 Enter the extended value of the transaction.3

2 Enter the shipping point by DoDAAC; if reduced printing is used, in-the-clear 

address may be entered in addition to the DoDAAC. 

3 Enter the consignee DRMO by DoDAAC. This will be the predesignated DRMO 

and will be entered by the shipping activity; if reduced printing is used, the in-theclear address may be entered in addition to the DoDAAC. 

4 Insert HM, if the turn-in is hazardous materiel or HW, if the turn-in is hazardous 

waste. 

5 Enter the date of document preparation, if required by the shipper. 

6 Enter the NMFC, if required by the shipper. 

7 Enter the freight rate, if required by the shipper. 

8 Enter coded cargo data, if required by the shipper. 

9 Enter applicable controlled inventory item code which describes the 

security/pilferage classification of the shipment from DoD 4100.39-M, volume 

10, chapter 4, table 61. 

10 Enter the quantity actually received by the DRMO, if different from positions 25-

29. 

11 Enter the number of units of issue in a package, if required by the shipper. 

12 Enter the unit weight applicable to the unit of issue, if required by the shipper. 

13 Enter the unit cube applicable to the unit of issue, if required by the shipper. 

14 Enter the uniform freight classification, if required by the shipper. 

15 Enter the shelf life, if appropriate; otherwise, leave blank. 

16 Enter in-the-clear freight classification nomenclature, if required by the shipper. 

17 Enter the item nomenclature. For non-NSN items; enter as much descriptive 

information as possible. Specified additive data or certification from the 

generating source for specific types of property should be entered. 

 

2 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will reflect the 

unit price as 9 digits for dollars and 2 digits for cents. Refer to ADC 221. 

3 If total price exceeds available space for display on the printed form, the generating application may leave blank. 

Refer to ADC 221. 
39

BLOCK(S) ENTRIES

18 Enter type of container, if required by the shipper. 

19 Enter number of containers that makes up the shipment, if required by the shipper. 

20 Enter total weight of shipment, if required by the shipper. 

21 Enter total cube of shipment, if required by the shipper. 

22 Received By - Enter the signature of person receiving the materiel. 

23 Date Received - Enter date materiel was received and signed for. 

24 Document Number - Perpetuate from source document. This cannot be the same 

document number that was used to receive the materiel. For locally determined 

excesses generated at base, post, camp, or station, assign a document number as 

determined by Service/Agency procedures. 

Suffix Code - Leave blank.4

25 National Stock Number - Enter the stock number or part number being turned in. 

Additional - For subsistence items, enter the type of pack code rp 21.5

26 For turn-in to DRMO - This block will not contain bar code data, it is reserved for 

internal DRMO/DRMS. 

27 This block may contain additional data including bar coding for internal. This 

block may contain a 2D symbol which repeats bar coded data content. Enter data 

in this block as required by the shipping activity or the DRMO receiving the 

material. When data is entered in the block, it will be clearly identified. 

HM/HW Turn-Ins – For hazardous materiel and waste turn-ins, enter the 

DoDAAC of the bill-to office (required for Signal Code B), the contract line item 

number (CLIN) for the item, and the total cost of the disposal. 

FSCAP Items –This block will contain both coding and clear-text information to 

identify Flight Safety Critical Aircraft Parts (FSCAP) shipments to DRMOs using 

Criticality Code E or F as follows: AFSCAP E - Flight Safety Critical Aircraft 

Part-Nuclear Hardened or AFSCAP F - Flight Safety Critical Aircraft Part.6

For IUID to support UIT/serialized item management7: 

 

4

Data from blocks 24-25 will be displayed in two configurations; (1) three-of-nine bar code and (2) in-the-clear. When 

prepared manually, bar code will not be included. 

5

See Footnote 2. 

6

See Footnote 1. 

7

 Capability to support IUID data content within the 2D symbol has been approved for staggered and phased 

implementation under ADC 44B. Components have not reported implementation at this time. 
40

BLOCK(S) ENTRIES

Unique Item Identifier (UII) and/or Serial Number 

The following additional data elements may be included in support of IUID: 

Manufacturer’s CAGE 

Current Part Number 

Batch/Lot 

Clear text labeling of IUID information must be provided using the following 

acronyms: CAGE, P/N, BT/LT, S/N, and UII. 
41

Enclosure 5

 

IRRD Examples

99999999999

99999999999

Example 1: This example shows a unit price using all available digits. The total price 

is blank because it is preferred to leave blank rather than truncate to fit the available 

space. 

Double click on form to display full size document. 

This is a mock-up. Price information is not accurate.
42

00999999999

999999999 999999999

Example 2: This example shows a unit price which exceeds current field size, but is 

not the full 11 digits. Leading zeros beyond the current field size for unit price (7) or 

total price (9) need not be displayed due to space limitations. The total price is 

included because it will fit within the available space. 

Double click on form to display full size document. 

This is a mock-up. Price information is not accurate.