1 of 8

ADC 320 

Attachment 

ATTACHMENT TO ADC 320 

Revises DS 846P to Add Transaction Creation Date; and for Intra-Navy Changes to Migrate Navy 

BZA/BZC Data Requirements to 846P End of Day Transaction Count Function (Staffed by PDC 272) 

1. ORIGINATOR:

a. Service/Agency: Navy. Naval Supply Information Systems Activity 

b. Originator: Navy Supply Process Review Committee representative, NAVSUP 421, DSN 

430-7510, commercial (717) 605–7510 

2. FUNCTIONAL AREA: Primary: Supply

3. REFERENCE: 

 a. NAVSUP P-485, Naval Supply Procedures 

 b. Interface Design Description (IDD) for Commercial Asset Visibility II (CAV II) (CAVWEBPM71) and Commercial Asset Visibility Organic Repairables Module (CAV-ORM). 

4. REQUESTED CHANGE: 

 a. Title: Revises DS 846P to Add Transaction Creation Date and for Intra-Navy Change to 

Migrate Navy BZA/BZC Data Requirements to 846P End of Day Transaction Count Function 

(Supply/MILSTRAP)

 b. Description of Change. 

 1). Adds the ‘transaction creation date’ to 846P. This supports both MILSTRAP 

 Document Identifier (DI) Codes DZM (rp 70-73) and DZJ (rp 73-76). 

2). Map Navy DI Codes BZA and BZC data to DLMS 846P for Commercial Asset VisibilityOrganic Repairables Module (CAV-ORM), and Ordnance Information System (OIS); Military 

Sealift Command (MSC) applications – Shipboard Configuration and Logistics Information 

Program (ShipCLIP), Web Configuration and Logistics Information Program (WebCLIP) and 

Financial Management System (FMS); Space and Naval Warfare Systems Command (SPAWAR) 

Relational Supply Optimized (Rsupply), Naval Facilities Engineering Command (NAVFAC) 

Supply Management Information System (SUPMIS), and Commercial Asset Visibility II (CAV 

II) usage. These applications are migrating from MILS to DLMS transactions. Navy currently 

uses (1) CAV II (BZC) and (2) CAV- ORM (BZA/BZC ) transactions, and requests that 

DLMSO revise 846P to accommodate the BZA/BZC data, and that data maps be developed to 

map BZA and BZC to DLMS 846P. 

3). This change also maps Navy DI Code BZC and BZA data to DLMS 846P for CAV-ORM. 

In response to staffing of PDC 272, Navy also requested the addition of a qualifier in segment 
2 of 8

ADC 320 

Attachment 

2/REF/140 to identify when the End of Day Count transaction was generated by CAV-ORM to 

satisfy the Navy ICP and ERP requirements. This supports Navy DI Code BZC and BZA data 

requirement by means of mapping the "C" in position 80 of BZA/BZC transactions which is 

currently used to indicate that the BZA/BZC was generated by CAV-ORM. 

 c. Procedures: 

1) Revise DoD 4000.25-M, DLMS, Volume 2, chapter 6, subparagraph C6.2.6.2. as follows 

(change is identified by red, bold, italicized text): 

“C6.2.6.2. Preparing Location Reconciliation and End of Day Accountable Transaction 

Count. Storage activities shall prepare location reconciliation request transactions (DS 846R) 

by line-item (stock number + supply condition code = line item), type of pack, and date 

packed/expiration date for subsistence, for each record transaction affecting the balance 

(including zero balance), and for no physical inventory adjustment required (DS to Federal IC 

947I, Inventory Adjustment, with zero quantity). The storage activity shall also send an End 

of Day Accountable Transaction Count (DS to Federal IC 846P) to advise the owner/IMM of 

the number of balance affecting transactions that were forwarded during the daily course of 

business. This end of day count transaction is compared to the actual number of transactions 

received by the owner/IMM to identify missing transactions and aid in unreconciled balance 

(URB) research. The five accountable transaction types for which the storage activity shall 

provide the owner/IMM end of day transaction counts using a single DS 846P are as follows: 

 C6.2.6.2.1. Receipts (DS 527R with 1/BR02 Transaction Type Code D4). 

 C6.2.6.2.2. Issues (DS 867I). 

 C6.2.6.2.3. Inventory Adjustment-Increases (DS 947I with 2/W1916 Inventory 

Transaction Type Code AJ). 

 C6.2.6.2.4. Inventory Adjustment-Decreases (DS 947I with 2/W1916 Inventory 

Transaction Type Code AD). 

 C6.2.6.2.5. Inventory Adjustment-Dual (DS 947I with 2/W1916 Inventory Transaction 

Type Code DU). 

 C6.2.6.2.5. For intra-Navy use only, Navy also provides end of day transaction count 

for Asset Status Reports (DS 846I).” 

 2) Revise DS 846P to accommodate Navy BZA/BZC data (changes from the PDC are 

highlighted): 

Item 

# 

Location DS 846P CHANGE TABLE Reason Federal IC 

Impact 

1. DLMS 

Introductory

Note 1 

Revise DLMS introductory note 1 to add a new last 

sentence as follows:

...This transaction also accommodates the functionality 

of non-DLSS Navy DI Codes BZA and BZC. 

To identify Navy 

transaction 

functionality 

accommodated in 

DS. 

No impact. 
3 of 8

ADC 320 

Attachment 

Item 

# 

Location DS 846P CHANGE TABLE Reason Federal IC 

Impact 

2. DLMS 

Introductory

Note 4 

Add standard DLMS introductory notes at 4.e and 4.f.

4e. Data required to accommodate Component-unique 

transaction requirements (e.g., B-series transactions). 

Data does not apply to DLSS transactions. 

4f. Repetition of data (using multiple iterations or loops) 

which is not compatible with existing DLSS capability. 

Although supported by the use of the ANSI X12 standard, 

such data is not compatible with DLSS/DLMS conversion 

and may not be supported by the recipient's automated 

processing system. Components must coordinate 

implementation of enhanced capability with DLMSO prior 

to use. 

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

Administrative

to add standard 

DLMS 

introductory 

notes. 

No impact 

3. DLMS 

Introductory

Note 5 

Added ADC to DLMS Introductory note 5: 

- ADC 320, Revises DS 846P to Add Transaction Creation 

Date; Intra-Navy Change to Migrate Navy BZA/BZC Data 

Requirements to 846P End of Day Transaction Count 

Function (Supply) 

To identify 

changes in the 

DLMS 

Supplements 

No impact. 

4. 1/BIA05/20 Delete Federal Note 2: Express time in a four-position 

(HHMM) format. 

Add DLMS Notes: 

DLMS Notes: 1. Express time in a four-position 

(HHMM) format, except for CAV II. CAV II expresses 

time in an eight-position Format (HHMMSSDD).

2. DLMS enhancement; see introductory DLMS note 4a. 

Authorized for use with CAV II.

Identify CAV II 

use of 8-position 

time format. 

Change 

required. 
4 of 8

ADC 320 

Attachment 

Item 

# 

Location DS 846P CHANGE TABLE Reason Federal IC 

Impact 

5. 1/BIA06/20 Open BIA06 Action Code, add Federal Note and DLMS 

note, and add code ‘ND’ with DLMS note:

Federal Note: Use any code.

DLMS Note: For DLMS use, only the following code is 

authorized. 

ND No Change 

DLMS Notes: 1. Authorized for intra-Navy use only for a 

Navy requirement; see introductory DLMS note 4e. Use in 

conjunction with BIA02 code ‘B1’. Navy reporting activities 

use with end of day processing to advise Navy ICPs that no 

balance affecting transactions were submitted that day. (An 

ANSI data maintenance request has been prepared to 

establish a new data element 1270 code qualifier assignment 

for 'No Balance Affecting Transactions’. (Navy DI Code 

BZA functionality. Refer to ADC 320) 

2. Use other than as noted above is a DLMS enhancement. 

See introductory DLMS note 4a. 

To provide for 

existing 

intra-Navy 

functionality 

Change 

Required 

6. 1/N101/80 Revise DLMS Note 1:

DLMS Note 1: Use only one of codes SB or Z4; or for 

intra-Navy use, Navy may use code FA as noted. 

Supports Navy 

BZA/BZC 

requirement. 

No impact. 

7. 1/N101/80 Add qualifier ’FA-Facility’ with DLMS note:

FA Facility 

DLMS Notes: 1. Authorized for intra-Navy use. 

Commercial Asset Visibility-Organic Repair Module 

(CAV-ORM) uses with 1/BIA01/20 Report Type Code B1, 

End of Day Transaction Count transactions, to identify an 

organic repair facility (e.g., shipyard or Fleet Readiness 

Center (FRC)). Authorized DLMS migration 

enhancement for intra-Navy use; see introductory DLMS 

note 4g. Refer to ADC 320. 

2. Use other than as noted above is a DLMS enhancement. 

See introductory DLMS note 4a.

Adds qualifier to 

support Navy 

BZA/BZC 

requirement. For 

intra-Navy use, 

activities other 

than storage 

activities may 

send End of Day 

Transaction 

Count 

transactions. 

No impact. 
5 of 8

ADC 320 

Attachment 

Item 

# 

Location DS 846P CHANGE TABLE Reason Federal IC 

Impact 

8. 2/LIN02/10 Add new DLMS note 2 for qualifier A2, and renumber 

note 2 as 3:

A2 DoD Identification Code (DoDIC) 

DLMS Notes: 

2. Authorized migration enhancement for intra-Navy 

use only; see introductory DLMS note 4g. Refer to ADC 

320. 

3. DLMS enhancement; see introductory DLMS note 4a. 

To authorize 

DLMS enhanced 

data, DoDIC, for 

intra-Navy use. 

No impact. 

9. 2/DTM01/100 Add qualifier 097 with DLMS note: 

097 Transaction Creation 

DLMS Note: Use to identify the date the transaction 

was prepared.

Supports 

MILSTRAP DI 

Codes DZM (rp 

70-73) and DZJ 

(rp 73-76) 

functionality. 

No impact. 

10. 2/REF/140 Revise segment level DLMS Note 2:

2. For End of Day Accountable Transaction Counts 

(1/BIA02/20 code B1) use to cite the accountable 

transaction count information (except do not use to cite 

count information with intra-Navy BIA06 Action Code 

‘ND’ which Navy uses to indicate no accountable 

transactions were submitted that day). 

To clarify that 

count information 

is not provided 

with Navy’s 

BIA06 Action 

Code ND. 

No impact. 
6 of 8

ADC 320 

Attachment 

Item 

# 

Location DS 846P CHANGE TABLE Reason Federal IC 

Impact 

11. 2/REF01/140 Revise DLMS Note for 8X’ to accommodate intra-Navy 

BZC requirement:

8X Transaction Category or Type 

DLMS Note: Use to identify the specific accountable 

transaction types for which transaction counts are being 

provided in 2/QTY/320 (i.e., receipt, issue, inventory 

adjustment increase, inventory adjustment decrease, 

inventory adjustment dual.)

For Receipts (DS 527R with 1/BR02 code D4); Issues (DS 

867I); Inventory Adjustment-Increases (DS 947I with 

2/W1916 code AJ); Inventory Adjustment-Decreases (DS 

947I with 2/W1916 code AD); Inventory AdjustmentsDual (DS 947I with 2/W1916 code DU), cite the 

appropriate code in REF02 as follows: 

For Receipts, cite 527R in REF02. 

For Issues, cite 867I in REF02. 

For Inventory Adjustment Increases, cite 947IAJ in 

REF02. 

For Inventory Adjustment Decreases, cite 947IAD in 

REF02. 

For Inventory Adjustments Dual, cite 947IDU in REF02.

For intra-Navy use, Navy also provides transaction 

counts for nonaccountable Asset Status Report 

transactions (DS 846I with BIA02 code TJ), cite 846I in 

REF02. Refer to ADC 320. 

To incorporate 

intra-Navy 

requirement to 

provide count 

information for 

Asset Status 

Report 

transactions. 

No impact. 

12. 2/REF01/140 Add new qualifier ‘L1’ with DLMS Note:

L1 Letter or Notes 

DLMS Note: For Intra-Navy use only, Navy uses to 

identify that End of Day Transaction Count transaction 

was generated by applications other than CAV II. Navy 

cites ‘C’ in REF02 to indicate non CAV II transactions. 

Navy uses with 1/BIA02/20 Code B1. Refer to ADC 320. 

To incorporate 

intra-Navy 

requirement to 

identify that End 

of Day 

Transaction 

Count was 

generated by 

CAV-ORM. 

No impact. 
7 of 8

ADC 320 

Attachment 

Item 

# 

Location DS 846P CHANGE TABLE Reason Federal IC 

Impact 

13. 2/QTY01/320 Add new qualifier ‘02’ with DLMS note:

02 Cumulative Quantity 

DLMS Note: For intra-Navy use only, Navy Commercial 

Asset Visibility (CAV) uses with 1/BIA02/20 code ‘B1-End 

of Day Transaction Count’, to identify the summary 

quantity for the transactions being reported. This equates 

to Navy DI Code BZC, rp 7-11. Not used with intra-Navy 

BIA06 Action Code ‘ND’. Refer to ADC 320. 

To incorporate 

intra-Navy CAV 

requirement. 

No impact. 

14. 2/QTY01/320 Revise DLMS Note for existing qualifier 46:

46 Total transactions 

DLMS Note: Use with BIA02 code B1 End of Day 

Transaction Count and 2/REF01 code FI to indicate the 

total number of balance affecting transaction types being 

reported in this transaction. For the purpose of this 

transaction there are 5 possible transaction types for 

which end of day counts can be reported (receipts, 

issues, inventory adjustment increases, inventory 

adjustment decreases, and inventory adjustment dual.). 

Not used with intra-Navy BIA06 Action Code ‘ND’. 

To clarify that 

count information 

is not provided 

with Navy’s 

BIA06 Action 

Code ND. 

No impact. 

15. 2/QTY01/320 Revise DLMS Note for existing qualifier TT:

TT Total Production Volume 

DLMS Note: Use with BIA02 code B1 End of Day 

Transaction Count to indicate to indicate the daily volume 

of balance affecting transactions applicable to the 

transaction category/type identified in 2/REF01/140 code 

8X (e.g. if 36 receipt transactions are being reported, 

REF01 = 8X; REF02 = 527R; QTY01 = TT; QTY02 = 

36.) Not used with intra-Navy BIA06 Action Code ‘ND’. 

To clarify that 

count information 

is not provided 

with Navy’s 

BIA06 Action 

Code ND 

No impact. 

16. 2/QTY01/320 Revise DLMS Note for existing qualifier UU:

UU Used 

DLMS Note: For BIA02 codes AD, DD, TC, DF, and 

BIA06 Action Code ND, use to comply with X12 syntax 

requirements. Cite “1” in QTY02. Do not use with BIA02 

code B1 (except when B1 is used in conjunction with 

intra-Navy BIA06 Action Code ‘ND’). 

To clarify use 

with BIA06 

Action Code ND. 

No impact. 

 
8 of 8

ADC 320 

Attachment 

d. ALTERNATIVE METHOD FOR CONVEYING DOD Identification Code (DoDIC), which is 

used to identify ammunition items, was identified in PDC 272, but is not being pursued as part of 

ADC 320. Any change to use of DoDIC in DLMS would need to be pursued as a separate PDC and 

would impact all DLMS transactions, not just 846P, and would impact all Services. Accordingly, 

no action is being taken on general DLMS use of DODIC by ADC 320. 

5. REASON FOR CHANGE: The existing DS 846P does not contain all the data elements Navy uses with 

BZA/BZC, and the existing DAASC mappings do not accommodate the Navy-unique BZA/BZC 

transactions. Navy submits DI Code BZA, Negative Transaction Reports, and DI Code BZC, Stock Point 

Reported Total Item Record (TIR) Counts. These transactions correspond to DS 846P with beginning 

segment 1/BIA02/20 Report Type Code B1 for End of Day Transaction Count. The formats for the BZA 

and BZC transactions are published in NAVSUP P-485 (reference 3.a) and the IDD for CAV II 

(CAVWEB-PM71) (reference 3.b). The formats are shown at the Enclosure. Navy requests that the data 

elements unique to BZA/BZC be added to DS 846P to support Navy implementation of DLMS. Navy also 

requests that DAASC maps to convert the DS 846P into the corresponding BZA and BZC formats be 

developed for use until the Navy fully transitions to DLMS transactions. 

DI Code BZA is a “Negative Transaction Report” (or Negative Asset Status Card) The BZA is 

created for the Navy ICPs for one processing day when no transaction or audit trail affecting items 

under a specific Inventory Manager's control have been processed. A BZA is created during end-of-day 

batch processing when there is no TIR activity for an Inventory Manager from a reporting site. 

DI Code BZC is a “Stock Point Reported TIR Counts” transaction. Count Cards (or DI 

Code BZC) are generated during end-of-day batch processing for the ICPs for one processing day. 

For retail, BZC count cards are generated for MILSTRAP DI Codes D4_, D6_, D7_, D8_, D9_, 

and DZA. For wholesale cogs, Count Cards are accumulated for DI Codes D4_, D6_, D7_, D8_, 

D9_, DA_, and DZA. [DLMSO NOTE: DS 846P End of Day Count transaction currently 

provides for counts for the following balance affecting transactions: receipts (527R-D4_/D6_); 

Issue (867I-D7_); and Inventory Adjustments (947I-D8_/D9_ /DA_). DS 846P and MILSTRAP 

do not provide for transaction count of non-accountable transactions (i.e., transactions which 

do not affect the balance) such as Asset Status Reports (846I-DZA)]. 

6. ADVANTAGES AND DISADVANTAGES: 

 

 a. Advantages: Offers the Navy the opportunity for technological advancement by implementing 

DLMS. The additional advantage of DAASC creating the BZA/BZC from a single X12 transaction 

set would be in keeping with the intent of utilizing the DLMS format and DAASC’s mission of 

translating and routing various supply actions to and from trading partners. 

 b. Disadvantages: The disadvantage of not incorporating BZA/BZC requirements in DLMS would be 

that DLMS compliant systems generating BZA/BZC transactions for the Navy would be required to 

perpetuate the Navy’s 80-record position fixed format transactions in addition to migrating to DLMS. 

7. IMPACT: 

 a. Data/Content/Procedures: Revise DoD 4000.25-M (DLMS), DS 846P, and DAASC maps. 

 b. Publication(s): None. 

Enclosures 
1 of 2

ADC 320 

Enclosure 1 

ENCLOSURE 1 TO ADC 320 

Mapping the fields of the X12 846P to Navy “BZA” 

NEGATIVE TRANSACTION REPORT 

Record 

Position

(BZA)

Field Name Definition Conditions/Comments

DLMS Data Element 

Segment/Position Table 

1-3 DI Code Enter DI BZA. None 2/LQ01-2/270

LQ01=0 

LQ02=RP 1-3 (BZA) 

DI Code only available for a 

transition period in a mixed DLSSDLMS environment. DI Code is 

identified for streamlining in a full 

DLMS environment. 

Functionality equates to 

1/BIA02/20 Report Type Code B1 

in conjunction with 1/BIA06/20 

Action Code ND 

2 

4-6 Routing 

Identifier 

Code 

Enter RIC of 

the ICP/IMM. 

 2/N1/450

N101=Z4 (Owning Inventory 

Control Point)

N103=M4 (DOD Routing 

Identifier Code (RIC)) 

N104=RP 4-6 

N106=TO (Message To) 

2 

7 Blank Leave blank. BLANK 

8-13 Report Enter 

"NEGTIR." 

 NEGTIR 

14-66 Blank Leave blank BLANK 
2 of 2

ADC 320 

Enclosure 1 

Record 

Position

(BZA)

Field Name Definition Conditions/Comments

DLMS Data Element 

Segment/Position Table 

67-69 Routing 

Identifier 

Code 

Enter RIC of 

the stock 

point 

submitting the 

document. 

1/N1/080 

N101=FA (Facility)

N103=M4 (DOD Routing 

Identifier Code (RIC)) 

N104=RP 67-69 

N106=FR (Message From) 

Proposed Note: Add code “FA” to 

N101 of 846P IC. 

N1*FA**M4*Q6S**FR 

CAV-ORM note: this transaction 

would be coming from a repair site 

like FRC San Diego which is Q6S.

1 

70-72 Blank Leave blank. BLANK 2 

73-75 Julian Day Enter specific 

date report 

submitted. 

2/DTM01-2/100 

DTM01=097 –Transaction 

Creation Date

Proposed Note: Add code “097” 

to DTM01 of 846P 

IC.

Example: 

DTM*097*263 

2 

76-79 Blank Leave blank. BLANK 2 

80 Special 

transaction 

Identifier 

Enter value “C” 

for 

CAV-ORM 

application. 

2/REF01-2/REF02/140

REF01=L1 –Letter or Notes

REF02=’C’ to indicate transaction 

generated by CAV-ORM. 

2 
1 of 3

ADC 320 

Enclosure 2 

ENCLOSURE 2 TO ADC 320 

Cross reference table 

Mapping the fields of the X12 846P to Navy “BZC” 

STOCK POINT REPORTED TIR COUNTS for Navy applications, except CAV II.

Record 

Position

(BZC)

Field Name Definition Conditions 

DLMS Data Element 

Segment/Position Table 

1-3 DI Code Enter DI BZC. None 2/LQ01-2/270

LQ01=0 (Stock Point Reported TIR 

Counts)

LQ02=RP 1-3 

Example: 

LQ*BZC~ 

DI Code only available for a 

transition period in a mixed DLSSDLMS environment. DI Code is 

identified for streamlining in a full 

DLMS environment. 

1/BIA02/20 Report Type Code B1 

for End of Day Transaction Count

2 

4-6 Routing 

Identifier 

Enter RIC of the 

ICP/IMM. 

 2/N1/450

N101=Z4 (Owning Inventory 

Control)

N103=M4 (Department of 

Defense Routing Identifier Code 

(RIC)) 

N104=RP 4-6 

N106=TO (Message To) 

Example: 

N1*Z4**M4*N35**TO~ 

2 

7-27 Blank Leave blank. BLANK 2 
2 of 3

ADC 320 

Enclosure 2 

Record 

Position

(BZC)

Field Name Definition Conditions 

DLMS Data Element 

Segment/Position Table 

28-29 Reported 

DIC 

 

Enter the first two 

codes of the TIR 

transactions (D4, 

D6, D7, D8, D9, 

DA or DZ). 

 2/REF01/140 

REF01 = 8X 

REF02 = 867I 

 (or 846I or 527R , etc) 

The Transaction Type is carried in 846P 

2/REF01/140 as shown below (and in 

the DS 846P Change Table in this 

ADC):

2 

 8X Transaction Category or Type 

DLMS Note: 

Use to identify the specific accountable transaction types for which 

transaction counts are being provided in 2/QTY/320 (i.e., receipt, 

issue, inventory adjustment increase, inventory adjustment decrease, 

inventory adjustment dual.) 

For Receipts (DS 527R with 1/BR02 code D4); Issues (DS 867I); 

Inventory Adjustment-Increases (DS 947I with 2/W1916 code AJ); 

Inventory Adjustment-Decreases (DS 947I with 2/W1916 code AD); 

Inventory Adjustments-Dual (DS 947I with 2/W1916 code DU), cite the 

appropriate code in REF02 as follows: 

For Receipts, cite 527R in REF02. 

For Issues, cite 867I in REF02. 

For Inventory Adjustment Increases, cite 947IAJ in REF02. 

For Inventory Adjustment Decreases, cite 947IAD in REF02. 

For Inventory Adjustments Dual, cite 947IDU in REF02. 

For intra-Navy use, Navy also provides transaction counts for 

nonaccountable Asset Status Report transactions (DS 846I with BIA02 

code TJ), cite 846I in REF02. Refer to ADC 320. 

30 Blank Leave blank. BLANK 2 

31-35 Enter the word "COUNT." 

36-37 Blank Leave blank. BLANK 2 

38-43 Stock Point 

TIR Count 

Enter the daily 

volume of 

transactions 

applicable to the 

reported TIR 

transaction DIC. 

 2/QTY01-02/320 

QTY01=46-Total Transactions 

QTY02=RP 38-43 

Example: 

QTY*46*26 ~ 

2 

44-66 Blank Leave blank. BLANK 2 
3 of 3

ADC 320 

Enclosure 2 

Record 

Position

(BZC)

Field Name Definition Conditions 

DLMS Data Element 

Segment/Position Table 

67-69 Routing 

Identifier 

Enter RIC of 

activity 

submitting report. 

If RP1-

2=DD, DF, 

DL, DU, or 

DW 

1/N1/080 

N101 = FA (Facility) 

N103=M4 (Department of 

Defense Routing Identifier Code 

(RIC)) 

Proposed Note: Add code “FA” to 

N101 of 846P IC. 

Example: 

N1*FA**M4*Q6S**FR 

CAV-ORM note: this transaction 

would be coming from a repair site 

like FRC San Diego which is Q6S.

1 

70-72 Blank Leave blank. Blank 2 

73-75 Transaction 

Date 

 

Enter the Julian 

date that the 

transactions took 

place. 

 2/DTM01-2/100

DTM01=097 (Transaction creation 

date) 

DTM02= RP 73-75 

Proposed Note: Add code “097” to 

DTM01 of 846P.

Example: DTM*097*263 

NAVSISA Comment: Agree. 

2 

76-79 Blank Leave blank. Blank 

80 Special 

transaction 

Identifier 

Enter value “C” 

for 

CAV-ORM 

application.

2/REF01-2/REF02/140

REF01=L1 –Letter or Notes

REF02=’C’ to indicate CAV-ORM 

application. 

2 
1 of 3

ADC 320 

Enclosure 3 

ENCLOSURE 3 TO ADC 320 

Cross reference table 

Mapping the fields of the X12 846P to Navy “BZC”- STOCK POINT REPORTED TIR COUNTS 

Cross reference table 

Mapping the fields of the X12 846P to Navy “BZC 

STOCK POINT REPORTED TIR COUNTS for CAV-II application. 

YELLOW= IS CAV II CHANGES 

Record 

Position

(BZC) 

from 

UDF

Field Name Definition Conditions 

DLMS Data Element 

Segment/Position Table 

41-43 DI Code Enter DI BZC. None DI Code only available for a 

transition period in a mixed 

DLSS-DLMS environment. 

DI Code is identified for 

streamlining in a full DLMS 

environment. 

1/BIA02/20 Report Type 

Code B1 is for End of Day 

Transaction Count 

2/LQ01-2/270

LQ01=0 (Stock Point Reported TIR 

Counts) 

LQ02=RP 41-43 (CAV II UDF 

positions) 

Example: 

LQ*BZC~ 

2 

601-603 Routing 

Identifier 

Enter Contractor’s 

RIC for CAV only. 

 2/N1/80

N101=SB (Storage Area)

N103=M4 (Department of Defense 

Routing Identifier Code (RIC)) 

N104=RP 601-603 (CAV II UDF 

positions) 

N106=FR (Message From ) 

Example: 

N1*SB**M4*W22**FR~ 

2 
2 of 3

ADC 320 

Enclosure 3 

Record 

Position

(BZC) 

from 

UDF

Field Name Definition Conditions 

DLMS Data Element 

Segment/Position Table 

45-64 

45-52 

53 

54-61 

62-64 

Transaction 

Date 

BLANK 

Transaction 

Time 

Enter the Julian Date 

this transaction was 

generated. 

DLMSO Comment/

The Format identifies 

20 positions for the 

“Julian” date, yet at 

right Navy indicates it 

is an 8 position date, 

plus an 8-pos time, 

PLUS a blank space 

at 53 as follows:. 

Enter the 8-position 

date (CCYYMMDD) 

that the transaction 

was created. 

BLANK 

Enter the 8-position 

time (HHMMSSDD) 

that the transaction 

was created. 

BLANK 

Only CAV II 

use it. 

1/BIA/020; 

 

BIA04 =45-52 ; 

+ space + BIA05=54-64; 

(CCYYMMDD HHMMSSDD) 

2 

721-723 Owning ICP Enter the Routing 

Identifier (RI) of the 

ICP. Note: Enter 

value of Owning ICP 

RIC. 

CAV II only 

Note: Enter 

value of 

Owning ICP 

RIC. 

2/N1/080 

N101=Z4 (Owning ICP) 

N103=M4 (DOD Routing 

Identifier Code (RIC)) 

N104=RP 721-723 (CAV II UDF 

positions); 

2 
3 of 3

ADC 320 

Enclosure 3 

Record 

Position

(BZC) 

from 

UDF

Field Name Definition Conditions 

DLMS Data Element 

Segment/Position Table 

640-642 ICP Routing 

Identifier To Routing Identifier of 

the ICP. 

CAV only. 2/N1/450 

N101=Z4 (Owning ICP)

N103=M4 (DOD Routing 

Identifier Code (RIC) 

N104=RP 640-642 (CAV II UDF 

positions); 

N106=TO (Message To) 

Example: 

N1*Z4**M4*N35**TO~ 

DLMSO COMMENT: THIS 

SAME DATA WAS ALSO 

MAPPED TO rp 721-723 

ABOVE. Please explain. 

NAVSISA RESPONSE: 

640-642 = ICP RI TO 

721-723 = Owning ICP RIC 

2 
1 of 1

ADC 320 

Enclosure 4 

ENCLOSURE 4 TO ADC 320 

BZA and BZC FORMATS 

The Navy currently utilizes the BZA and BZC in the following formats: 

DI BZA NEGATIVE TRANSACTION REPORTS (NAVSUP P-485 FORMAT not used by CAV-II) 

cc Field Legend Explanation

1-3 Document Identifier Enter DI BZA. 

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

7 Blank Leave blank. 

8-13 Report Enter "NEGTIR." 

14-66 Blank Leave blank. 

67-69 Routing Identifier Enter RIC of activity submitting report. 

70-72 Blank Leave blank. 

73-75 Julian Day Enter specific date report submitted. 

76-80 Blank Leave blank. 

DI BZC STOCK POINT REPORTED TIR COUNTS (NAVSUP P-485 FORMAT) 

cc Field Legend Explanation

1-3 Document Identifier Enter DI BZC. 

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

7-27 Blank Leave blank. 

28-29 Reported DIC Enter the first two codes of the TIR 

 transactions (D4, D6, D7, D8, D9, DA or DZ). 

30 Blank Leave blank. 

31-35 Enter the word "COUNT." 

36-37 Blank Leave blank. 

38-43 Stock Point TIR Count Enter the daily volume of transactions 

applicable to the reported TIR transaction DIC. 

44-66 Blank Leave blank. 

67-69 Routing Identifier Enter RIC of the stock point submitting the document. 

70-72 Blank Leave blank. 

73-75 Transaction Date Enter the Julian date that the transactions took place. 

76-80 Blank Leave blank.