Attachment, ADC 431 

Page 1 

ADC 431 

To Map Intra-Army DI Code BZE, Consumption Report (GFM), to the DLMS 846I 

1. ORIGINATING SERVICE/AGENCY AND POS INFORMAITON: 

 a. Technical POC: LOGSA Contractor, EDI Support, Jacobs Technology, DSN 

256.645.9807, Commercial 256.955.9807 

 b. Functional POC: USAMC LOGSA, Process Integration Division, DSN 256-645-0718, 

Commercial 256-955-0718

2. FUNCTIONAL AREA: 

 a. Primary/Secondary Functional Area: Supply 

3. BACKGROUND: 

 a. Intent of the transaction: For contractors to report quantities of GFM consumed to the 

supporting Management Control Activity (MCA) for the Life Cycle Management Command 

(LCMC). The contractor is required to submit consumption data (listed by items and quantities) 

monthly during the contract performance period. 

 b. Scenario for which the transaction is used: Each MCA shall prepare the DoD materiel 

status report, reflecting consumption of Government furnished items, required for the quarterly 

reporting periods ending March 31, June 30, September 30, and December 31, using DD Form 

2543, "Government Furnished Material (GFM) status report," in accordance with DoD 

4140.1-R, chapter 5, paragraph c 5.11. Although consumption of GFM is not included as part of 

the report, in compliance with Federal Acquisition Regulations (FAR) and Defense Federal 

Acquisition Regulations (DFAR), disposition of residual materiel must be covered in the 

contract, and accomplished as part of contract close-out. In order to identify what residual 

materiel exists at contract termination, the Inventory Control Point (ICP)/MCA must maintain 

records of consumption, as reported by the contractor. In the past, the Army has used DI Code 

BZE, Consumption Report (Government Furnished Materiel), to enable the contractors to report 

consumption, and now requires a DLMS format to accomplish that reporting. 

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

(1) Army transaction BZE allows contractors to submit their GFM consumption data to 

the MCA for the LCMCs. That information is captured in the Commodity Command Standard 

System (CCSS). The BZE can either flow from a contractor's own system or be input manually 

into CCSS. CCSS records the consumption information in the MCA database, and that 

information is used to generate the consumption report. 

(2) Under modernization, contractors will have the ability to use the Centralized 

Contractor Receipt system (CCRS) to generate BZEs. CCRS is a Web-based tool that was 
 Attachment, ADC 431 

Page 2 

developed by LOGSA at the direction of Army Materiel Command (AMC) as the result of GAO 

Audit 06-209. In order for CECOM and AMCOM to receive this data, and for TACOM and 

Army Joint Munitions and Lethality Life Cycle Management Command (JM&L LCMC) to 

receive the data after October 1, 2011, it is necessary that a DLMS transaction be available, in 

order for the data to pass to Army Logistics Modernization Program (LMP). 

 (3) When CCRS passes the data to DLA Transaction Services (formerly Defense 

Automatic Addressing System), a DLMS equivalent is needed to translate from the DI Code 

BZE to the approved DLMS transaction. CCRS has already been implemented and all AMC 

LCMCs are on LMP as of October 2010. 

4. APPROVED CHANGES(S): 

 

 a. Requested change in detail: 

 (1) Army requested that Army-unique DI Code BZE, Consumption Report (GFM), data 

requirements be incorporated into DLMS 846I Asset Status Inquiry/Report. Army DI Code BZE 

allows contractors to report consumption of parts by National Stock Number (NSN) 

consumed/incorporated and the associated end item. Data content for the existing BZE 

transaction is shown at Enclosure 1. DLMS mapping of the BZE data for DLA Transaction 

Services legacy-to-DLMS conversion processing is shown at Enclosure 2. DLMS Supplement 

updates for the 846I are shown at Enclosure 3. 

 (2) Under the legacy format the contract number is not included in the transaction, 

although the contractor DoDAAC is provided. The Army is able to recognize the contract 

number because there is a one-for-one relationship between contractor and the assigned Army 

contractor DoDAAC. If originated in the DLMS format (in lieu of the legacy format), this 

transaction will be required to include the contract number. 

 (3) A document number is not included in the legacy format due to the length constriction 

of the 80 record position (rp) transaction. Under DLMS, legacy formats that lacked a controlling 

document number were enhanced to add the document number data field. If originated in the 

DLMS format, this transaction will be required to include a document number. For conversion 

from MILS to DLMS, the document number will be constructed by DLA Transactions Services 

during transaction conversion using the contractor DoDAAC and the transaction processing date. 

The document number serial number will be a constant “U” (which identifies a constructed 

document number, and, therefore, will not conflict with any requisition document numbers), 

followed by the Report Sequence Number. (Note: The Army confirmed prior to staffing that the 

construction of the document number during conversion is acceptable.) 

 (4) Staffing Note for All Components: During PDC staffing Components were asked to 

determine applicability of this change to their methodology for contractor reporting of GFM 

consumption. Components were requested to provide a statement regarding how this aspect of 

monitoring GFM is accomplished for documentation in the approved DLMS change. To date 

only DLA has provided response (see Enclosure 3). Although too late for inclusion in the ADC, 

response to this request is still appropriate if wider use of the approved change is desired. 
 Attachment, ADC 431 

Page 3 

 b. Alternatives: None known 

5. REASON FOR CHANGE:  This change documents and incorporates the intra-Army use 

DI Code BZE data requirements in DLMS. The data provides value-added information for 

Army. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Supports Army implementation of DLMS migration effort by 

incorporating Army-unique DI Code BZE, Consumption Report (GFM).

 b. Disadvantages: Lack of standardized approach among the Components. 

7. NOTE ANY REGULATIONS OR GUIDANCE: DoD 4140.1-R, DoD Supply Chain 

Materiel Management Regulation.

8. IMPACT: 

a. Army system change: Subsequent to staffing, USAMC Logistics Support Activity 

(LOGSA) agreed to the addition of the contract number in the BZE format. LOGSA will submit 

an ECP to change system to accommodate for this change which could take up to year.

b. New DLMS Data Elements: 

(1) 846I Data Updates: The new data requirements identified for 846I to support this 

requirement are: Quantity Consumed (BZE, RP 25-29), End Item NSN (BZE, RP 30-42), 

Supply Source Method Code (BZE, RP 44), Report Sequence (BZE, RP 67-69), Contract 

Number (not included on the BZE, but added as a DLMS enhancement) Contract Call Order 

Number (BZE, RP 70-73), Contract Line Item Number (BZE, RP 74-77), and Sub-contract Line 

Item Number (BZE, RP 78-79). 

(2) New DLMS Data Elements: The following data elements are new to the DLMS: 

 (a) Report Sequence Number – A three digit sequential number assigned to each 

consumption report to ensure all transactions are accounted for during the reporting period. 

(b) Quantity Consumed – The quantity of GFM consumed by the contractor 

during the reporting period. 

(c) Supply Source Method Code – A code identifying the method used to obtain 

the materiel consumed as GFM. Available codes are: 

 P–Requisitioned through MCA. 

 J–Obtained by cannibalization of Government materiel. 
 Attachment, ADC 431 

Page 4 

c. Changes to DLMS Data Elements: Establishes a new value for the existing Report 

Type Code to correspond to the BZE functional requirement and update DLMS-DLSS crossreference tables accordingly. 

 62–Asset Account Statement 

d. DLA Transaction Services: This change requires new legacy format-to-DLMS 

conversion mapping. Reverse mapping is not required.
Enclosure 1, ADC 431 

Page 1

Enclosure 1 to ADC 431 

Army DI Code BZE Format 

Record 

Position 

Field Legend Explanation 

1-3 Document Identifier Code Enter DI Code BZE 

4-6 Management Control Activity (MCA) 

RIC 

Enter RIC of proper MCA (To be specified in the 

contract). 

7 Blank Blank 

8-22 Item Number of GFM/GFE Enter the 13 digit Item Number of the item 

consumed/incorporated 

23-24 Unit of Issue Enter the unit of issue of the GFM (To be 

specified in the contract). 

25-29 Quantity Quantity Consumed 

30-42 Item Number of End Item Enter NSN of end item upon which GFM was 

used. 

43 Blank Blank 

44 Supply Source (renamed for DLMS as 

Supply Source Method Code) 

Enter proper code to identify source of 

consumable. 

P–Requisitioned through MCA. 

J–Obtained by cannibalization of government 

materiel. 

45-50 DODAAC To be specified in the contract. 

51-66 Blank Blank 

67-69 Report Sequence Number Number each report sequentially through duration 

of the contract, beginning with 001. 

70-73 Contract Call Order Number – portion 

of contract being executed. 

Enter 4–position contract call order number; 

otherwise, leave blank. 

74-77 Contract Line Item Number (CLIN) Enter 4–position CLIN; otherwise, leave blank 

78-79 Subordinate CLIN (Sub–CLIN) Enter 2–position Sub–CLIN; otherwise, leave 

blank. 

80 Blank Blank 

 
Enclosure 2, ADC 431 

 Page 1

Enclosure 2 to ADC 431 

Proposed DLA Transaction Services Mapping for Intra-Army DI Code BZE to DLMS 846I 

Field Name DI Code BZE 

Record 

Position 

Conditions DLMS Data Element 

Transaction Set 

Identifier 

None None ST01=846 

Transaction Set 

Control Number 

None None ST02=Serial Number 

Beginning Segment None If RP1-3=BZE BIA01=00 

BIA02=62 

BIA03=Z 

BIA04=CCYYMMDD 

BIA05=HHMM 

Reporting Location 45-50 If RP1-3=BZE N101=RL 

N103=10 

N104=RP45-50 

N106=FR 

National Stock 

Number of GFM 

8-20 If RP1-3=BZE LIN02=FS 

LIN03=RP8-20 

Contract Call Order 

Number 

70-73 If RP1-3=BZE CS03=RP70-73 

Contract Line Item 

Number and 

SubCLIN 

74-79 If RP1-3=BZE and RP74-79 not 

blank 

CS04=C7 

CS05=RP74-79 

Report Sequence 

Number 

67-69 If RP1-3=BZE REF01=55 

REF02=RP67-69 

Document Number None If RP1-3=BZE REF01=TN 

REF02= RP45-50, followed 

by Julian date of transaction 

processing, followed by “ U”, 

followed by RP67-69 

Source of Supply 

Method Code 

44 If RP1-3=BZE LQ01= SC

LQ02=RP44 

Code Source 

Information 

None Department of Defense LM01=DF 

Document 

Identification Code 

1-3 None LQ01=0 

LQ02=RP1-3 

Quantity Consumed 25-29 If RP1-3=BZE QTY01=99 

QTY02=RP 25-30 

Unit of Issue 23-24 None QTY03=RP23-24 

National Stock 

Number of End Item 

30-42 If RP1-3=BZE LIN04=EP 

LIN05=RP30-42 

Management Control 4-6 If RP1-3=BZE N101=Z5 
Enclosure 2, ADC 431 

 Page 2

Activity N103=M4 

N104=RP4-6 

N106=TO 

Number of Included 

Segments 

None None SE01=Total Number of 

Segments 

Serial Number None Must Equal to ST02 SE02=Serial Number 
Enclosure 3, ADC 431 

Page 1

Enclosure 3 to ADC 431 

Revise DS 846I Asset Status Report as shown in Change Table 

# Location DS 846I Change Table 

Asset Status Inquiry/Report 

Reason 

1. DLMS 

Introductory 

Note 6 

Added ADC 431 to DLMS Introductory note 6.

- ADC 431, To Map Intra-Army Unique Document Identifier (DI) Code 

BZE, Consumption Report (Government Furnished Materiel (GFM)), to 

the DLMS 846I 

To identify DLMS 

changes included in 

the DS. 

2. 1/BIA02/020 Add new qualifier “62” with DLMS notes:

62 Asset Account Statement 

DLMS Note: Use to identify a Consumption Report (Government 

Furnished Materiel (GFM)) transaction for intra-Army use (Army unique 

DI Code BZE functionality). Refer to ADC 431.

Supports Army unique 

requirement. Assigns 

a distinct transaction 

purpose code to 

clearly identify the 

new functionality for 

GFM consumption 

reporting. 

3. 1/N101/080 Add new DLMS qualifier “RL” with DLMS notes:

RL Reporting Location 

DLMS Note: 

For Intra-Army use to identify the DoDAAC of the contractor reporting 

GFM consumption (BIA02=62/DI Code BZE functionality). Refer to ADC 

431.

Supports Army unique 

requirement. 

4. 1/N106/080 Revise DLMS note 1 to existing qualifier “FR”:

FR Message From 

DLMS Note: 1. Use to identify the activity preparing the consumption 

report (GFM) or asset status report, except as noted at DLMS note 3 below. 

(subsequent notes not shown here) 

Administrative. 

Incorporates 

additional transaction 

within note text. 

5. 2/LIN04/010 Add new qualifier “EP” with DLMS notes:

EP Buyer's End Product Number 

For Intra-Army, use with LIN02=FS to indicate NSN of the associated end 

item (BIA02=62/DI Code BZE functionality) Refer to ADC 431.

Supports Army unique 

requirement. 

6. 2/REF01/140 Add new qualifier “55” with DLMS notes:

55 Sequence Number 

DLMS Note: For Intra-Army use to identify the report sequence number 

associated with the report of GFM consumption. Number each report 

sequentially through duration of the contract, beginning with 001. 

(BIA02=62/DI Code BZE functionality) Refer to ADC 431.

Supports Army unique 

requirement. 

7. 2/CS/240 Mark CS segment as Used and segment level DLMS note:

DLMS Note: Use only for intra-Army contractor reporting of GFM 

consumption to provide contract information (BIA02=62/DI Code BZE 

functionality). Refer to ADC 431.

Supports Army unique 

requirement. 
Enclosure 3, ADC 431 

Page 2

# Location DS 846I Change Table 

Asset Status Inquiry/Report 

Reason 

8. 2/CS01/240 Mark Data Element Used and add DLMS note:

Contract Number 

DLMS Note: For Intra-Army use to identify the contract number when 

reporting GFM consumption. This is a DLMS enhancement (contract 

number is not provided in the legacy BZE format and may not be available 

pending update to Army systems). 

Clarification of usage. 

9. 2/CS03/240 Mark Data Element Used and add DLMS note:

Release Number 

DLMS Note: For Intra-Army use to identify the call number or order 

number (may include the respective call or order modification) when 

reporting GFM consumption. 

Supports Army unique 

requirement. 

10. 2/CS04/240 Mark Data Element Used and add new qualifier “C7” w/ DLMS notes:

C7 Contract Line Item Number 

DLMS Note: For Intra-Army use to identify the CLIN (or CLIN 

including the Sub Contract Line Item Number (SUBCLIN), as 

appropriate, when reporting GFM/GFE consumption. 

Supports Army unique 

requirement. 

11. 2/LQ01/270 Add new qualifier “SC” with DLMS notes:

SC Source 

DLMS Note: For Intra-Army use to indicate the Supply Source Method 

Code (BIA02=62/DI Code BZE functionality) Refer to ADC 431. 

Available codes are: 

P–Requisitioned through MCA. 

J–Obtained by cannibalization of Government materiel.

Supports Army unique 

requirement. 

12. 2/QTY01/320 Add new qualifier “99” with DLMS note:

99 Quantity Used 

DLMS Note: For Intra-Army use to indicate GFM quantity consumed 

(BIA02=62/DI Code BZE functionality). Refer to ADC 431.

Supports Army unique 

requirement. 

13. 2/N101/450 Add new DLMS qualifier “Z5”:

Z5 Management Control Activity 

DLMS Note: 

For Intra-Army use to identify the RIC of the MCA to receive the report of 

GFM consumption (BIA02=62/DI Code BZE functionality). Refer to 

ADC 431.

Supports Army unique 

requirement. 
Enclosure 4, ADC 431 

Page 1

Enclosure 4, Concurrence and Comment Resolution 

 Originator Concurrence/Comments/Response to Staffing Note 

(Requesting feedback on comparable procedures 

within other Components) 

Response 

1. DLA Concur 

DLA tracks consumption via the Bill of Material 

(BOM) that is established prior to awarding the 

contract. Once end items are received & receipted at 

the depot (or by the customer) from the vendor, the 

raw material record in DSS is decremented 

accordingly. Vendors are charged for excess materials 

required over the BOM, and credited for any returns. 

Noted. 

2. USMC Concur Noted. 

3. USAF Concur Noted. 

4. DPAP 

(contractor 

support) 

We have no comments on this PDC. Noted. 

5. Army HQDA DCS G-44(s) concur w/comments below: 

LOGSA concedes the addition of the contract number 

in the BZE. LOGSA will just have to submit an ECP 

to change system to accommodate for this change 

which could take up to year. 

Initial Response: We would prefer the contract 

number not be part of the DLMS transaction or at least 

be considered optional. The CLIN is already on the 

transaction and Army knows what contract applies to 

the particular consumption transaction. 

We believe that approving 

the inclusion of the contract 

number as ‘optional’ would 

be a contradiction of the 

intent of OSD/DPAP for 

DLMS transactions. OSD 

has directed us to issue 

change proposals to include 

the contract number in all 

the transactions supporting 

GFP. That means that the 

requisition which drops the 

contract number after MCA 

review will have to be 

modified to keep the 

contract number. The MRO 

to a depot will have to have 

the contract number so that 

the depot can add it to the 

shipment status. This will 

mean extensive changes. 

We cannot publish the ADC 

without making the 

contract number required in 

the DLMS format. The 

only exception will be for 

interim use if a BZE is sent 
Enclosure 4, ADC 431 

Page 2

in 80-position legacy format 

for DAAS conversion to 

DLMS. In this scenario the 

contract number will not be 

available. 

6. DLA 

Transaction 

Services 

According to Appendix 2.7 The use of "U" in RP 40 is 

reserved to identify Quality Deficiency Report (QDR) 

related transactions when the original requisition is not 

known. 

It is the indication of a 

"constructed document 

number." (The U can also 

be used on SDRs.) This 

was a way to ensure that the 

document number 

would not be interpreted as 

matching a prior requisition, 

and the U is the only value 

we have to do that...the 

change would be expanding 

its use. We don’t see any 

problems with pursuing this 

usage (other than minor 

confusion because the ‘U’ is 

so closely associated with 

PQDRs). 

7. USTRANSCOM Abstain Noted. 

8. IDE/GTN 

Convergence 

(IGC) Program 

IGC does not currently process the 846I. We abstain 

in the vote for this change.