1 of 4 

 ADC 325 

Attachment 

ATTACHMENT TO ADC 325 

Revise DS 867D, Demand Reporting to Address Navy BHJ Transaction Requirements 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

 a. Technical POC: Navy Supply Process Review Committee (SPRC) representative on behalf of 

Navy ERP, NAVSUP E4, DSN 430-7510, commercial (717) 605-7510

 b. Functional POC: Navy SPRC representative on behalf of Navy ERP, NAVSUP E4, DSN 

430-7510, commercial (717) 605-7510 

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

3. REFERENCE: Naval Supply (NAVSUP) Systems Command, Naval Supply Information 

System Activity (NAVSISA), Interface Design Description (IDD) for Uniform Inventory 

Control Point (UICP), 867D Demand Reporting – BHJ ICP/IMM Report of Purchase of NonNSN Material Transactions, Version 1.0, February 2009.

4. BACKGROUND: 

a. Intent of the transaction: Organizations use this transaction set to record demand for 

items that are obtained locally. 

b. Scenario for which the transaction is used: Reporting sales of product to an end 

customer. 

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

systems use the BHJ transaction to notify the Navy Inventory Control Point (NAVICP) about 

sales of non-NSN material to customers. These transactions allow the NAVICP to keep track of 

the demand for these items. If there is enough demand for the item then NAVICP will request 

that the item be catalogued by FLIS. Navy-ERP needs to provide the ICPs with the capability to 

accept, record, and control demand data for non-stock numbered actions resulting from local 

purchase or manufacture. The collection and recording of this demand is an important element in 

identifying future material requirements and in positioning material. Data mapping requirements 

between Navy BHJ and DS 867D are provided at the enclosure. 

5. PROPOSED CHANGE(S): 

a. Revise DLMS Supplement (DS) 867D, Demand Reporting, as shown in DS 867D 

Change Table Below: 

Item # Location DS 867D Revision Reason Federal IC 

Impact 

1. DLMS 

Introductory 

Note 1 

Revise DLMS Note 1 to read:

DLMS Note: 1. Use a single occurrence of this 

transaction set to transmit demand transactions to 

one or more activities. This transaction 

encompasses the functionality of MILSTRAP 

Document Identifier (DI) Code DHA and nonDLSS Navy DI Code BHJ. 

Add Navy unique 

BHJ transaction 

to the 867D. 

No Impact. 
2 of 4 

ADC 325

Attachment

Item # Location DS 867D Revision Reason Federal IC 

Impact 

2. DLMS 

Introductory 

Note 

Add ADC 325 to DLMS Introductory note 5:

- ADC 325, Revise DS 867D, Demand Reporting, 

to Address Navy BHJ Transaction Requirements. 

To identify 

PDC/ADC in the 

DS. 

No Impact. 

3. 1/PER/130 Add a DLMS Segment level note:

DLMS Note: Use of the PER segment is a DLMS 

enhancement. See introductory DLMS note 4a.

DLMSO 

administrative 

update to 

document that use 

of PER is a DLMS 

enhancement.

No impact. 

4. 2/REF01/30 Revise DLMS Note for qualifier ‘TN’:

DLMS Note: Must use to identify the transaction 

number from the source document. This is also 

known as the document number. 

DLMSO 

Administrative 

update to pick up 

language used in 

MILSTRAP. 

No Impact. 

5. 2/QTY02/110 Number existing DLMS Note as #1, and add new 

DLMS note 2:

DLMS Note: 2. For Navy only, when interfacing 

with Navy legacy system using Navy DI Code 

BHJ, in a mixed DLSS-DLMS environment, the 

BHJ quantity field is only 2 positions and Navy 

enters ‘99’ in BHJ if the quantity was greater than 

99. (Navy DI Code BHJ, rp 43-44; See ADC 325.) 

To note Navy 

restriction on 

quantity field entry 

when interfacing 

with Navy legacy 

systems using 

Navy DI Code 

BHJ. 

No Impact. 

6. 2/LIN02/120 Add qualifiers OT and W2 with DLMS notes:

OT Internal Number 

DLMS Note: Authorized for intra-Navy use in a 

mixed DLSS-DLMS environment to identify when 

Navy DI Code BHJ, rp 45-47 cited ‘TWC’ 

indicating both type equipment code and work unit 

code were available. Future streamlined data 

since in a DLMS environment, both 

codes/numbers can be cited in the transaction with 

qualifiers EM and W2 using the next available 

combination of data element 235/234 pairs as 

needed to provide all the necessary data. See the 

future streamlined data introductory DLMS note 

4c. See ADC 325. 

W2 Work Unit Number

DLMS Note: Authorized for intra-Navy use to 

identify the work unit code. For all other use this 

is a DLMS enhancement; see introductory DLMS 

note 4a. See ADC 325. 

To add qualifier for 

Navy requirement 

to identify Work 

Unit Code used in 

Navy DI Code 

BHJ. 

Also adds qualifier 

OT-Internal 

Number for use in 

a mixed DLMSDLSS environment 

as described in 

DLMS note at left. 

Qualifier OT 

would be 

streamlined out in 

a full DLMS 

environment. 

No Impact. 
3 of 4 

ADC 325

Attachment

Item # Location DS 867D Revision Reason Federal IC 

Impact 

7. 2/LIN02/120 Add DLMS note 3 to qualifiers ‘MN’ and ‘YP’ to 

note that these DLMS enhancements are 

authorized for intra-Navy use.

MN Model Number 

YP Publication Number 

DLMS Note 3. Authorized for intra-Navy use; 

see ADC 325. 

To acknowledge 

intra-Navy use of 

DLMS 

enhancements. 

No Impact. 

8. 2/REF01/190 Add DLMS note to existing qualifier BB:

BB Authorization Number 

DLMS Note: 

1. Use to identify an allowance list or 

authorization document that justifies the need for 

the material. 

2. DLMS enhancement; see introductory DLMS 

note 4a. 

3. Authorized for intra-Navy use. Navy uses to 

identify the allowance parts list; see ADC 325. 

To authorize 

qualifier for 

intra-Navy use. 

No impact. 

9. 2/REF01/190 Add qualifier ‘AL’ with DLMS note:

AL - Accounting (Equipment) Location 

Number 

DLMS Note: Authorized for intra-Navy use. 

Navy uses to identify Navy’s allowance equipage 

code; see ADC 325.

To authorize 

qualifier for 

intra-Navy use 

for Navy’s 

allowance 

equipage code. 

No impact. 

b. Proposed procedures: DAASC translate Navy DI Code BHJ transactions to DLMS 

867D transactions when sending them to a DLMS compliant Navy system. This is a one-way 

translation requirement since Navy does not require translation from DLMS 867D to DI Code 

BHJ. Navy Uniform Automated Data Processing System (UADPS) II (U2) and Navy R-Supply 

are two of the primary legacy systems creating DI Code BHJ. 

 c. Alternatives: 

 1) Develop modernized Navy system using non-DLMS transaction. 

 2) Change multiple legacy Navy systems to output DHA DIC or 867D DLMS transactions. 

6. REASON FOR CHANGE: Navy modernized system development is being programmed 

to be DLMS compliant. The legacy systems DI Code BHJ matches well with the DLMS 

equivalent 867D Demand Reporting transaction, but has never been mapped to it. 

7. ADVANTAGES AND DISADVANTAGES: 
4 of 4 

ADC 325

Attachment

 a. Advantages (tangible/intangible): Allows development of only a DLMS compliant 

solution for the 867D functionality. 

 b. Disadvantages: None. 

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Expected implementation 

date is February 2010. Expected testing is April 2009. 

9. IMPACT: 

a. DOD 4000.25-M, DS 867D. No revision required to Federal IC. 

b. DAASC mapping. 

10. FOR XML DEVELOPMENT: 

 If applicable, provide transaction and processing details: 

DIC and Full Name DLMS IC 

Navy BHJ Report of Purchase of Non-NSN Material 867D 

Enclosure
ADC 325 

Enclosure 

ENCLOSURE TO ADC 325 

Revise DLMS Supplement (DS) 867D, Demand Reporting to Address Navy BHJ 

Transaction Requirements 

1. Imbedded spreadsheet identifies DS 867D data mapping to Navy DI Code BHJ: 

BHJ to 867D Map 

(2).xls 

2. Navy DI Code BHJ data mapping to 867D Demand Transaction which DLMSO extracted 

from information in referenced NAVSUP/NAVSIS IDD for 867D/BHJ is provided below: 

Navy DI Code BHJ data mapping to 867D Demand Transaction 

Field Legend Navy DI Code 

BHJ rp 

867D location (Table/Segment/Position) 

Document Identifier 1-3 1/BPT04/20 Report Type Code ‘TO’ = Demand 

Transaction 

DI Code is available in DLMS for an interim 

transition period in a mixed DLSS/DLMS 

environment. DI Code is identified for 

streamlining in a full DLMS environment. 

DI Code is at 1/LQ01/150 

Qualifier ‘0’. 

1/LQ/150/01=0/02=RP 1-3

Routing Identifier (TO) 4-6 2/N1/50/01=Z4/03=M4/ 04=RP 4-6/ 06=TO 

Part Number 7-28 2/REF/30/01=MF/02=RP=7-28

Document Number 29-42 2/REF/30/01=TN/02=RP 29-42

Quantity 43-44 2/QTY/110/01=YA/02=RP 43-44 

Technical Reference 

Document/Number 

Abbreviation 

45-58 NOTE: 2/LIN/120 provides for use of multiple 234/234 

pairs of data as needed. Hence rp 67-69 will show map 

to LIN02/03 and when rp 45-47 maps to LIN, it maps to 

LIN04, with rp 48-58 = LIN05: 

rp45-47 PUB=2/LIN/120/04=YP and LIN05=rp 48-58 

rp45-47 TEC=2/LIN/120/04=EM and LIN05=rp 48-58 

rp45-47 WUC=2/LIN/120/04=W2 and LIN05=rp 48-58 

rp45-47 TWC=2/LIN/120/04=OT and LIN05=rp 48-58 

rp45-47 MDL= 2/LIN/120/04=MN and LIN05=rp 48-58 

rp45-47 DWG=2/LIN/120/04=PT and LIN05=rp 48-58 

rp45-47 TEM=2/LIN/120/04=F3 and LIN05=rp 48-58 

rp45-47 APL=2/REF01/190=BB and REF02=rp 48-58

rp45-47 AEL=2/REF01/190=AL and REF02=rp 48-58

Added LIN04 qualifier ‘W2’ 

for Work Unit Code 

(WUC). 

Added LIN04 qualifier ‘OT’ 

for TWC (TWC is used in 

BHJ when both TEC and 

WUC are available) 

Use existing REF01 

qualifier ‘BB’ for Allowance 

Parts List Parts List (APL). 

Add REF01 qualifier ‘AL’ 

for Allowance Equipage 

Code (AEL). 

rp 45-47 PUB for Technical Publication Reference = LIN04 YP-Publication Number 

rp 45-47 TEC for Type Equipment Code = LIN04 EM-Equipment Identification Code 

rp 45-47 WUC for Work Unit Code = LIN04 W2-Work Unit Number 

rp 45-47 TWC for Type Eqpt Code and Work Unit Code (required when both TEC & WUC are available) = LIN04 OT-Internal Number 

rp 45-47 MDL for Model Number/Code = LIN04 MN-Model Number 

rp 45-47 DWG for Drawing Number = LIN04 PT-Print or Drawing Number 

rp 45-47 TEM for Technical Manual = LIN04 F3-Technical Manual Number 

rp 45-47 APL for Allowance Parts List = 2/REF01/190 BB-Authorization Number 

rp 45-47 AEL for Allowance Equipage Code = 2/REF01/190 AL-Accounting (Equipment) Location Number 
2 of 2 

ADC 325

Encl

Field Legend Navy DI Code 

BHJ rp 

867D location (Table/Segment/Position) 

CAGE Code 59-63 2/REF/30/04-01=W7/04-02/RP59-63

Routing Identifier (FROM) 64-66 1/N1/80/01=SB/03=M4/04=RP 64-66/06=FR

Nomenclature 67-79 2/LIN/120/02=CN/03=RP 67-79

Demand Code 80 2/DD/240/01= RP 80 DD02=74 

3. Navy BHJ format from NAVSUP P-485 Volume II - Supply Appendices, Appendix 28, 

MILSTRIP/MILSTRAP Formats, Section III: 

DI BHJ REPORT OF PURCHASE OF NON-NSN MATERIAL

cc Field Legend Explanation

1-3 Document Identifier Enter DI BHJ. 

4-6 Routing Identifier Enter RIC of the ICP/IMM. 

7-28 Part Number Enter part Number of item requested/purchased. 

29-42 Document Number Enter document number of the requisition. 

43-44 Quantity Enter 99 if Quantity greater than 99. 

45-47 Technical Reference Document/Number Abbreviation Enter abbreviations for 

type of number entered in cc 48-58: 

 PUB for Technical Publication Reference. 

 APL for Allowance Parts List. 

 TEC for Type Equipment Code. 

 WUC for Work Unit Code. 

 TWC for Type Equipment Code and Work Unit Code (required when both TEC and WUC are available). 

 AEL for Allowance Equipage Code. 

 MDL for Model No./Code. 

 DWG for Drawing Number. 

 TEM for Technical Manual. 

If other than above use, define in remarks space and mail document. If there is an APL it is mandatory. 

48-58 Technical Reference Document/Number Enter technical reference document/ 

number that will aid in identification of this part to its end item application. Preferred identifications are 

APL/CID/EIC for NAVICP MECH; or Technical Publication Reference/Work Unit Code/ Type Equipment 

Code for NAVICP PHIL. 

59-63 Federal Supply Code for Manufacturers Enter the FSCM. Mandatory entry. 

64-66 Routing Identifier Enter RIC of the activity submitting the transaction. 

67-79 Item Nomenclature Self-explanatory. 

80 Demand Code Enter N (nonrecurring) or R (recurring) as appropriate. 
Filename: ADC325_DS867D_NavyBHJ.doc 

Directory: C:\Documents and Settings\HPO0020\Desktop 

Template: C:\Documents and Settings\HPO0020\Application 

Data\Microsoft\Templates\Normal.dot 

Title: Change Proposal Format 

Subject: DLMS 

Author: Gower 

Keywords: process, review, committee, DLMSO, change, proposal, 

format 

Comments: 

Creation Date: 6/1/2009 10:42:00 AM 

Change Number: 2 

Last Saved On: 6/1/2009 10:42:00 AM 

Last Saved By: HPO0020 

Total Editing Time: 0 Minutes 

Last Printed On: 6/1/2009 10:46:00 AM 

As of Last Complete Printing 

 Number of Pages: 7 

 Number of Words: 2,455 (approx.) 

 Number of Characters: 13,996 (approx.)