1 of 5

ADC 461

Attachment

ATTACHMENT TO ADC 461

Revision for Commercial Asset Visibility-Organic Repairables Module (CAV-ORM) Estimated 

Completion Date (ECD) on MILSTRAP DAC/DLMS 947I and Administrative Update to 527D, 527R, 

856S, and 867I (Supply/MILSTRAP) (Staffed as PDC 475)

1. ORIGINATOR SERVICE/AGENCY AND POC INFORMATION:

a. Service/Agency: Navy, NAVSUP

b. Managing POC: Program Manager, CAV-ORM, NAVSUP, 717-605-6863; DSN 430-6863; and 

Project Manager, CAV-ORM, NAVSUP Business Systems Center (BSC), 717-605-4710; DSN: 430-4710

c. Technical POC: Technical leads, CAV-ORM, NAVSUP Business Systems Center, 717-605-2907; 

DSN: 430-2907; CAV-ORM, NAVSUP BSC, 717-605-8139; DSN: 430-8139

d. Functional POC: Functional Lead, CAV-ORM, NAVSUP Business Systems Center, 717-605-1389; 

DSN: 430-1389

2. FUNCTIONAL AREA: Primary: Supply/Repair

3. REFERENCE: DLMSO memorandum, October 7, 2009, subject: Approved DLMS Change 

(ADC) 343, Revise DLMS Supplement (DS) 947I Inventory Adjustment Transaction in Support of Navy 

Enterprise Resource Program (ERP) and Commercial Asset Visibility II (CAV II) Systems with Interim 

Measure for CAV Detail Inventory Adjustment Transaction.

NOTE: THROUGHOUT ADC, Significant changes from PDC are highlighted in yellow.

4. BACKGROUND:

a. Intent of the transaction: For the purposes of more accurate planning and scheduling of repair, 

the NAVSUP Weapons Systems Support (NAVSUP WSS) is requiring the CAV-ORM application to 

accept and pass a repair item’s Estimated Completion Date (ECD) and updated ECD. This capability was 

added, for CAV II use, to the DLMS 947I Inventory Adjustment transaction by ADC 343 (reference 3). 

This change expands the ECD applicability to CAV-ORM.

b. Scenario for which the transaction is used: When CAV-ORM receives a workload, the initial 

ECD data is saved to the database. When an item is receipted in CAV-ORM the inducted supply condition 

code (SCC) is changed to M, to indicate that the item is “in repair” [SCC M = Suspended (In Work)]. At 

that time CAV-ORM creates and sends a MILSTRAP Document Identifier Code (DIC) DAC (Dual 

Inventory Adjustment-SCC Change) transaction in User Defined File (UDF) format to reflect the move of 

the National Item Identification Number (NIIN) from inducted SCC to SCC ‘M’. The ECD value will be 

included on the MILSTRAP DIC DAC transaction. The DAC will be translated by DLA Transaction 

Services into DLMS 947I Inventory Adjustment transaction.

When CAV-ORM receives an updated ECD value for an item in repair, CAV-ORM will send the 

updated ECD value on an “ECD” transaction (947I DLMS) to Navy ERP. This “ECD” transaction will 

not need a DIC, but will be in DLMS format from CAV-ORM. It will bypass the usual DLA 

Transaction Services Micro Automated Routing System (DMARS) authorization because it will be in 

DLMS format. It will go through the usual X12 format validation.
2 of 5

ADC 461

Att

c. Procedures, transactions, data elements, processing details in use today: Today, CAVORM receives the initial ECD data and stores it but does not pass it to any other system, nor does 

CAV-ORM accept updated ECD data.

5. APPROVED CHANGE:

a. Requested change in detail:

1) For CAV-ORM UDF DAC transactions that translate into DLMS 947I Inventory 

Adjustment – Dual (SCC change), CAV-ORM will include the ECD value, formatted as YDDD, in the 

MILSTRAP DAC record position 77-80 to be translated by DLA Transaction Services into the DLMS 

947I’s G62 segment with the “KA” qualifier for “Scheduled Service Completion” and formatted as 

CCYYMMDD. Currently, the DLMS Notes in the 947I transaction specify that only CAV and CAV 

trading Partner NAVICP (now known as NAVSUP WSS) can use this segment. For CAV-ORM to use the 

“KA” qualifier, CAV-ORM must be identified in the 947I DLMS notes as an authorized user.

2) When CAV-ORM receives updated ECD data and they need to change an ECD that was 

previously provided by an Inventory Adjustment – Dual (SCC change) transaction, they require the 

capability to send a DLMS 947I ECD transaction. This change authorizes CAV-ORM to use the 947I 

ECD Transaction functionality developed for CAV II by ADC 343. The ECD transaction is identified by 

947I beginning segment Transaction Type Code ‘A5’. Use of 947I with W1505 Code ‘A5’ indicates that 

only the ECD is being changed by the transaction. The date will be in the DLMS 947I format of 

CCYYMMDD. 

3) Today, CAV-ORM passes the PO, Project Order Number, as required by Navy ERP, in the 

947I CS segment as CS01 Contract Number. DLA Logistics Management Standards office position was 

that since the PO is not a contract number, it should not be mapped to the contract number field. A more 

appropriate qualifier in the N9 segment should be used. DLA Logistics Management Standards identified 

several possible N901 qualifiers that could be used depending on what the Project Order Number actually 

represented. Navy selected qualifier ‘16- Military Interdepartmental Purchase Request (MIPR)’ for the 

CAV-ORM Project Order Number, based on what the project order represented for CAV-ORM/Navy ERP.

b. Approved procedures: 

1) Revise DLMS 947I as shown in change table at Enclosure 1.

2) Revise DLMS 527D Pre-positioned Materiel Receipt (PMR), 527R Receipt, 867I Issue, 

and 856S Shipment Status to standardize use of ‘Q9 - Repair Order Number’ for CAV and CAV-ORM 

Repair Document Number as shown in change table at Enclosure 2. The CAV Repair Cycle Document 

Number (RCDN) is a data element used in several DLMS transactions. Hence, redefining and 

standardizing RCDN as this change approves also affects the DLMS notes for RCDN in other 

transactions. Refer to paragraph 12.c.2) of this change for the revised DLMS data element name and 

definition. 

3) Revise DOD 4000.25-2-M, MILSTRAP, Appendix 3.8, DIC DAC, Inventory Adjustment –

Dual (Condition/Purpose Transfer), as shown in Enclosure 3.
3 of 5

ADC 461

Att

c. Alternatives: The possibility of putting the updated ECD on another DAC transaction with 

matching supply condition codes (M to M and G to G) was discussed. It was determined that the 

matching SCCs were an improper use of the DAC and could not be accommodated by Navy ERP. 

6. REASON FOR CHANGE: NAVSUP WSS requires CAV-ORM to send ECD data to the Navy 

ERP system.

7. ADVANTAGES AND DISADVANTAGES:

a. Advantages: 

1) Expands the CAV ECD capability to CAV-ORM. NAVSUP WSS will have more accurate 

dates from which to determine a repair planning schedule.

2) Supports Navy’s requirement to redefine RCDN to support both CAV and CAV-ORM. 

Standardizes Navy use of this data field in DLMS. 

b. Disadvantages: None identified.

8. DEFENSE AUTOMATIC ADDRESSING SYSTEM (DAAS): Update DLA Transaction Services DAAS 

maps to allow new data to pass any applicable edits. Navy proposed mapping is shown at enclosure 2.

9. ADDITIONAL FUNCTIONAL REQUIREMENTS: Interface Design Descriptions (IDDs) for 

the ECD field on the DAC transaction and the new DLMS 947I ECD transaction will be provided to 

CAV-ORM’s partners at DLA Transaction Services for mapping. CAV-ORM receives ECD data either 

from update transactions from its Aviation partners or manual input from any of its partners (Maritime 

or Aviation). Those initial and updated ECD values will be provided to its trading partner (Navy ERP).

10. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW DEVELOPMENT:

Navy ERP will be able to accept and process initial and updated ECD data from CAV-ORM.

11. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: January 22, 2012.

12. IMPACT:

a. Publications. Revise DLMS 947I and MILSTRAP Appendix 3.8 as noted. 

b. Automated Information Systems (AIS): 

1) Navy: Impacts Navy CAV-ORM and Navy ERP. 

2) DLA Transaction Services

3) Integrated Data Environment (IDE)/Global Transportation Network (GTN) Convergence 

(IGC). IGC may receive these transactions in their Enterprise Data Warehouse.

4) Other Services and DOD Agency AIS: No impact. Navy advises this is an intra-Navy change 

impacting Navy CAV-ORM system and Navy systems interfacing with Navy CAV-ORM. No other services 

use CAV-ORM.
4 of 5

ADC 461

Att

c. New or revised DLMS Data Content: 

1) CAV-ORM Project Order Number is a funding authorization number created and assigned by 

Navy ERP to repair item/NIIN that has a format of 15 positions starting with the owning NAVSUP WSS 

DoDAAC. STAFFING NOTE: CAV-ORM indicated that Project Order Number should map to the qualifier 

for MIPR.

2) Redefining Repair Cycle Document Number (RCDN) as Associated Commercial Asset 

Visibility (CAV) Repair Document Number - contains either the CAV Repair Cycle Document Number 

or the CAV - Organic Repair Module (CAV-ORM) Repair Component Document Number, depending 

upon applicability. Helps to identify CAV and CAV-ORM repair items(s) on workloads. Single DLMS 

data element that is populated differently based upon Navy guidance. 

13. PDC 475 COMMENTS DISPOSITION TABLE:

Organization Comment to PDC 475 Disposition

1

USTRANSCOM USTRANSCOM approves with the 

following comment:

Due to required updates to USTRANSCOM 

systems in support of this PDC it is

requested that the approved ADC, when 

released, include instructions that

implementation date occur no sooner than 

90 days from ADC release. This request 

will allow sufficient time to make necessary 

changes to affected systems.

Navy Disposition:

Navy and USTRANSCOM have coordinated 

and agreed to an implementation date. When 

PDC 475 is an approved ADC and released, 

we’ve agreed to implement the ADC on 22 

January 2012, which supports Navy's efforts.

MILSTRAP Administrator comment:

Jan 22, 2012 Implementation Date added to 

ADC cover memorandum.

2

DLA 

Logistics 

Management 

Standards 

Revise mapping for the Project Order 

Number line item number and amendment 

number from the CS-Contract Summary 

segment to a composite for the PO Number 

in the N9 segment. DLA Logistics 

Management Standards office discussed 

revised mapping with Navy and DLA 

Transaction Services during Nov 9, 2011 

telecon.

Rationale: Contract Summary segment is 

used in DLMS for contracts established

IAW Defense Federal Acquisition 

Regulation Supplement (DFARS). Navy 

CAV-ORM PO Number is not a DFARS 

contract number.

MILSTRAP Administrator Disposition:

Line Item Number mapped to: 

2/N907-01/0400, qualifier ‘FJ-Line Item 

Control Number’. Refer to 947I Change 

Table at Enclosure 1, row 6.

Amendment number mapped to:

2/N907-03/0400, qualifier ‘2G-Amendment’. 

Refer to 947I Change Table at Enclosure 1, 

row 7.
5 of 5

ADC 461

Att

Organization Comment Disposition

3 Navy Concurs with version in draft ADC 461. Noted.

Navy

comment:

Request that use of the N9 segment for 

Project Order Number/MIPR, and the 

associated Line Item number and 

Amendment number; be allowed for both 

CAV and CAV-ORM.

Rationale: 

CAV II has the ability to report commercial 

(contract number structure) and organic (PO 

number structure). CAV-ORM only 

reports organic (PO number structure).

We feel it's best to have the two 

applications report the PO number structure 

using the same mapping. CAV II's contract 

number structure will NOT change. 

CAV II would send data either using 

contract number structure OR PO number 

structure on one transaction; never would 

they use both data structures on the same 

transaction.

If the repair vendor is a commercial 

contractor, the transaction(s) (DAC & ECD) 

would include contract number structure.

If the repair vendor is an organic 

site, the transaction(s) (DAC & ECD) 

would include PO number structure.

Updated DLMS Notes in DS authorize the 

requested 2/N9/0400 segment data for both 

CAV and CAV-ORM.

CAV II does use structure contract 

numbers IAW DFARS for commercial 

vendors.

See Enclosure 1, DS 947I Change Table, 

row 9: segment level DLMS note 

acknowledging optional CAV use of the 

segment. 

4 Army Concurs as written. Noted.

5 Air Force Concurs without comment. Noted.

6 DLA Concur as written. Noted.

Enclosures
1 of 3

ADC 461

Enclosure 1

ENCLOSURE 1 to ADC 461

DS 947I, Inventory Adjustment, Change Table 

(Changes from PDC are in yellow highlight at rows 5, 6, 7, 8, 9, 10)

# Location

Ver. 4030

DLMS 947I Inventory Adjustment Revision

(Corresponding changes will be made to version 4010)

Reason

1. DLMS 

Intro Note 

Add ADC 461 to Introductory note 6:

- ADC 461, Revision for Commercial Asset Visibility-Organic Repairables 

Module (CAV-ORM) Estimated Completion Date (ECD) on MILSTRAP 

DAC/DLMS 947I and Administrative Update to 527D, 527R, 856S, and 867I 

(Supply/MILSTRAP) 

Identifies PDC/ADC in 

the DLMS Supplement

2. 1/W1505/

0200

Add to Type Code ‘A5’ DLMS note:

A5 Notice of Charge

DLMS Notes: 1. This is the Change Estimated Completion Date (ECD) 

Transaction. Authorized for use by Commercial Asset Visibility (CAV) and by 

organizations interfacing with CAV by mutual agreement. Also authorized for 

use by the CAV–Organic Repairables Module (CAV-ORM) and by organizations 

interfacing with CAV-ORM by mutual agreement. CAV and CAV-ORM must 

ensure that trading partners can accept this CAV/CAV-ORM unique data. Use 

only when changing or establishing the estimated completion date for a previously 

submitted ‘Inventory Adjustment (Dual-Supply Condition Code Change)’ 

transaction. Use only with 2/W1901/0200 Quantity Adjustment Reason Code AC 

with W1916 Inventory Transaction Type Code DU – Inventory Adjustment (Dual). 

No inventory adjustment is taking place by this date change transaction. 

Duplicate detail data from original inventory adjustment transaction, as needed, 

with exception of the estimated completion date which is being revised by this 

transaction. Refer to ADC 343 and ADC 461.

2. Authorized DLMS migration enhancement for use by CAV, CAV-ORM and by 

CAV/CAV-ORM trading partners by mutual agreement. See introductory DLMS 

note 4.e.

To reflect that CAVORM is permitted to 

use the ECD 

transaction (beginning 

segment Transaction 

Type Code ‘A5’). 

3. 2/N901/

0400

Add qualifier 16 with DLMS note: 

16 Military Interdepartmental Purchase Request (MIPR)

DLMS Note: CAV and CAV-ORM uses to identify the CAV-ORM Project 

Order Number. This is a funding authorization number created and 

assigned by Navy ERP to repair an item. The CAV-ORM Project Order 

Number identifies a specific form that is used to transmit obligation authority 

(dollars) and requirements between a service or agency requiring a purchase 

and a military service or agency responsible for procuring the requirement. 

DLMS enhancement authorized for use by CAV and CAV-ORM. Refer to ADC 

461.

Allow Navy ERP PO 

data on the CAV and 

CAV-ORM 947I ECD 

transaction.

CAV-ORM indicated 

that PO number is 

essentially a MIPR.

The CAV-ORM PO

number has a format of 

15 positions starting 

with the owning 

NAVSUP WSS 

DoDAAC.
2 of 3

ADC 461

Encl 1

# Location

Ver. 4030

DLMS 947I Inventory Adjustment Revision

(Corresponding changes will be made to version 4010)

Reason

4. 2/N901/

0400

Replace DLMS note for qualifier‘Q9’:

Q9 Repair Order Number

DLMS Note: Commercial Asset Visibility (CAV) uses to cite the unique Repair 

Cycle Document Number (RCDN) assigned by the CAV II System. The RCDN 

identifies an individual item at the contractor’s plant and isused for tracking 

purposes. Position (1-6) identifies the Contractor’s DODAAC, (pos 7-10) 

identifies the Julian Date, and (pos 11-14) identifies the Serial Number. It is 

assigned when the item(s) is receipted into CAV. Each item has its own unique 

RCDN. Refer to ADC 343. 

DLMS Note: Identifies the Associated Commercial Asset Visibility (CAV) 

Repair Document Number. Use to cite the appropriate repair document 

numbers (i.e., CAV Repair Cycle Document Number or CAV-Organic Repair 

Module (CAV-ORM) Repair Component Document Number, depending 

upon applicability. Helps identify CAV and CAV-ORM repair items(s) on 

workloads. Refer to ADC 343 and ADC 461.

Supports Navy’s 

requirement to 

redefine RCDN to 

support both CAV and 

CAV-ORM.

Standardizes Navy use 

of the data field in 

DLMS. 

5. 2/N907-

01/ 0400

Add standard data Notes:

Federal Note: Use any code.

DLMS Note: For DLMS, only the following codes are authorized.

Administrative update.

6. 2/N907-

01/ 0400

Add qualifier FJ with DLMS note:

FJ Line Item Control Number

DLMS Note: CAV and CAV-ORM use to identify the line item number 

associated with the MIPR/Project Order Number. Used in conjunction with 

N901 code 16. Refer to ADC 461

Supports Navy CAV 

and CAV-ORM use of 

Line Item Number 

with MIPR/PO 

Number.

7. 2/N907-

03/ 0400

Add standard data Notes:

Federal Note: Use any code.

DLMS Note: For DLMS, only the following codes are authorized.

Administrative update.

8. 2/N907-

03/ 0400

Add qualifier 2G with DLMS note:

2G Amendment

DLMS Note: CAV and CAV-ORM use to identify the amendment number 

associated with the line item number for the MIPR/Project Order Number. 

Used in conjunction with N907-01 code FJ. Refer to ADC 461

Supports Navy CAV 

and CAV-ORM use of 

amendment Number 

with MIPR/PO 

Number and line item 

number.
3 of 3

ADC 461

Encl 1

# Location

Ver. 4030

DLMS 947I Inventory Adjustment Revision

(Corresponding changes will be made to version 4010)

Reason

9. 2/CS/

0500

Add new segment level DLMS note:

DLMS Notes:

1. Use only with W1901 code AC inventory adjustment transactions to identify the contract 

number and Contract Line Item Number (CLIN), or the CLIN, including the Subcontract 

Line Item Number (SUBCLIN), associated with the transaction. Use of this segment is a 

DLMS enhancement. See introductory DLMS note 4a.

2. DLA has identified a requirement to use this segment for intra-DLA procurement related 

adjustments for condition transfer. DLA use the contract number, CLIN and Call Order 

Number for these transactions.

3. CAV has identified a requirement to use this segment when the repair vendor 

is a commercial contractor. Refer to ADC 461.

Acknowledges CAV 

use of the CS segment 

to provide contract 

number information 

when the when the 

repair vendor is a 

commercial contractor.

If the repair vendor is 

an organic site, CAV 

would cite a Project 

Order number in 

2/N9/0400.

10. 2/CS01/

0500

Change usage for CS01 Contract Number from “Used” to “Must Use”.

 Usage

CS01 Contract Number Used Must Use

Administrative Update. 

CS01 is ‘Must Use’ in 

version 4010, but when 

947I was migrated to 

version 4030, the 

software did not pick 

up the ‘Must Use’. This 

corrects the usage.

The CS segment is 

optional, but if the 

segment is used, then 

the Contract Number 

must be cited.

11. 2/G6201/

0800

Revise DLMS Notes for existing qualifier ‘KA’:

KA Scheduled Service Completion

DLMS Notes: 1. Only authorized for use by Commercial Asset Visibility (CAV), 

CAV-Organic Repairables Module (CAV-ORM); and CAV/CAV-ORM trading 

partner ICP by mutual agreement. CAV contractor uses to indicate the estimated 

completion date (ECD) for an Inventory Adjustment (Dual-Supply Condition Code 

(SCC) Change). Use only with 2/W1901/0200 Quantity Adjustment Reason Code 

AC with W1916 Inventory Transaction Type Code DU – Inventory Adjustment 

(Dual) (this equates to functionality of MILSTRAP DI Code DAC). In CAV, when 

the ECD requirement is set to 'Required', the CAV reporter will be required to 

enter a valid ECD in the inventory adjustment transaction which lets their trading 

partner ICP know the ECD. Refer to ADC 343 and ADC 461. CAV-ORM will 

automatically receive an initial ECD at request time and pass that value to its 

trading partners on a MILSTRAP DI Code DAC transaction; any updates to an 

item’s ECD will be passed to trading partners via the 947I Change ECD 

Transaction (W1505 Transaction Type Code A5).

2. To change an ECD that was previously provided by an Inventory Adjustment –

Dual (SCC change) transaction, use with W1505 Transaction Type Code A5 -

Change ECD Transaction. Use of W1505 Transaction Type Code ‘A5’ indicates 

that only the ECD is being changed by the transaction. 

3. Authorized DLMS migration enhancement for use by CAV and CAV-ORM. See 

introductory DLMS note 4.e.

To reflect that CAVORM is permitted to 

use the KA identifier 

for Estimated 

Completion Date data.
1 of 2

ADC 461

Enclosure 2

ENCLOSURE 2 TO ADC 461

DLMS 527D PMR, 527R Receipt, 867I Issue, and 856S Shipment Status Change Table

Revise DLMS 527D PMR, 527R Receipt, 867I Issue, and 856S Shipment Status to standardize use of ‘Q9 -

Repair Order Number’ for CAV and CAV-ORM Repair Document Number as shown in this change table. 

# Location DLMS Reason

1. DLMS 

Introductory 

Note 

Add ADC 461 to Introductory note :

- ADC 461, Revision for Commercial Asset Visibility-Organic Repairables 

Module (CAV-ORM) Estimated Completion Date (ECD) field on the MILSTRAP 

DAC and DLMS 947I ECD transaction , and Administrative Update to 527D, 

527R, 867I , 856S (Supply/MILSTRAP/MILSTRIP).

Identifies 

PDC/ADC in 

the DLMS 

Supplement

2. 527D

2/N901/

090

Revise the 527D DLMS note for qualifier Q9:

Q9 Repair Order Number

DLMS Note: Commercial Asset Visibility (CAV) uses to cite the Repair 

Cycle Document Number (RCDN) assigned by the CAV II System. 

Identifies the Associated Commercial Asset Visibility (CAV) Repair 

Document Number. Use to cite the appropriate repair document number 

(i.e., CAV Repair Cycle Document Number or CAV-Organic Repair 

Module (CAV-ORM) Repair Component Document Number), depending 

upon applicability. CAV uses with prepositioned materiel receipt/advance 

receipt information transactions. The RCDN identifies an individual item at 

the contractor’s plant and is used for tracking purposes. Position (1-6) 

identifies the Contractor’s DODAAC, (pos 7-10) identifies the Julian Date, and 

(pos 11-14) identifies the Serial Number. Each item has its own unique RCDN.

Refer to ADC 342 and ADC 461.

Supports Navy’s 

requirement to 

redefine RCDN 

to support both 

CAV and CAVORM.

Standardizes 

Navy use of the 

data field in 

DLMS. 

3. 527R

2/N901/

090

Revise the 527R DLMS note for qualifier Q9:

Q9 Repair Order Number

DLMS Note: CAV uses to cite the Repair Cycle Document Number 

(RCDN) assigned by the CAV II System. Identifies the Associated 

Commercial Asset Visibility (CAV) Repair Document Number. Use to cite 

the appropriate repair document number (i.e., CAV Repair Cycle 

Document Number or CAV-Organic Repair Module (CAV-ORM) Repair 

Component Document Number), depending upon applicability. CAV uses

with CAV Detail record, which is Navy CAV nonstandard use of a receipt 

transaction for a non balance affecting transaction. The RCDN identifies an 

individual item at the contractor’s plant and is used for tracking purposes Each 

item has its own unique RCDN. Only authorized for use with LIN01 code 

‘Y-CAV Detail Record’. Position (1-6) identifies the Contractor’s DODAAC, 

(pos 7-10) identifies the Julian Date, and (pos 11-14) identifies the Serial 

Number. Refer to ADC 342 and ADC 461.

Supports Navy’s 

requirement to 

redefine RCDN 

to support both 

CAV and CAVORM.

Standardizes 

Navy use of the 

data field in 

DLMS. 
2 of 2

ADC 461

Encl 2

# Location DLMS Reason

4. 867I

2/REF01/30

Replace the 867I DLMS note for qualifier Q9 with new DLMS:

Q9 Repair Order Number

DLMS Note: Commercial Asset Visibility (CAV) uses to cite the Repair Cycle 

Document Number (RCDN). The CAV RCDN identifies an individual item at 

the contractor’s plant. It also indicates the unique number assigned by the CAV 

System to identify and track CAV transactions. Position (1-6) identifies the 

Contractor’s DODAAC, (pos 7-10) identifies the Julian Date, and (pos 11-14) 

identifies the Serial Number. Refer to ADC 341.

DLMS Note: Identifies the Associated Commercial Asset Visibility (CAV)

Repair Document Number. Use to cite the appropriate repair document 

number (i.e., CAV Repair Cycle Document Number or CAV-Organic 

Repair Module (CAV-ORM) Repair Component Document Number), 

depending upon applicability. CAV uses with Issue transactions. Refer to 

ADC 341 and ADC 461.

Supports Navy’s 

requirement to 

redefine RCDN 

to support both 

CAV and CAVORM.

Standardizes 

Navy use of the 

data field in 

DLMS. 

5. 856S

2/REF01/

1500

Revise the 856S DLMS note for qualifier Q9:

Q9 Repair Order Number

DLMS Note: Identifies the Associated Commercial Asset Visibility (CAV) 

Repair Document Number. Use to cite the appropriate repair document 

number (i.e., CAV Repair Cycle Document Number or CAV-Organic 

Repair Module (CAV-ORM) Repair Component Document Number), 

depending upon applicability. Must use for CAV shipment status to indicate 

the unique CAV Repair Cycle Document Number (RCDN) assigned by the 

CAV II System. The CAV RCDN identifies an individual item at the 

contractor’s plant and is used for tracking purposes. Position (1-6) identifies the 

Contractor’s DODAAC, Julian Date (pos 7-10) and Serial Number (pos 11-14). 

It is assigned when the item(s) is receipted into CAV. Each item has its own 

unique RCDN. A ‘POS’ is created for each item citing that item's unique CAV 

Repair Document Number RCDN (e.g., N994179077002). Refer to ADC 

344 and ADC 461.

Supports Navy’s 

requirement to 

redefine RCDN 

to support both 

CAV and CAVORM.

Standardizes 

Navy use of the 

data field in 

DLMS. 
1 of 2

ADC 461

Enclosure 3

ENCLOSURE 3 TO ADC 461

DOD 4000.25-2-M, MILSTRAP

AP3.8. APPENDIX 3.8

INVENTORY ADJUSTMENT – DUAL (CONDITION/PURPOSE TRANSFER)

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier 1-3 Enter DI Code DAC or DAD, as appropriate.

Routing Identifier (TO) 4-6 Enter RI code of the ICP to which this 

transaction is being forwarded.

Blank 7 Leave blank.

Stock or Part Number 8-22 Enter stock or part number of item being 

adjusted.

Unit of Issue 23-24 Enter UI of item.

Quantity 25-29 Enter quantity being adjusted, preceding 

significant digits with zeros.1/2

Document Number 30-43 For reclassification of previously suspended 

receipts, enter document number under which 

the materiel originally was received. For other 

adjustments, enter appropriate document 

number.

3

Suffix 44 For reclassification of previously suspended 

receipts, enter suffix code under which the 

materiel was originally received. For other 

adjustments, enter consecutive alpha codes A 

through Z when assignment of suffix codes is 

necessary.

4

Routing Identifier 

(Losing)

45-47 For intra-Component, enter code prescribed by 

the Component.

5 For inter-Component, leave 

blank.

Multiuse 48-50 For intra-Component, enter data prescribed by 

the Component.5 For inter-Component use, 

leave blank.

Blank 51 Leave blank.

 1

See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1. 

2

See Appendix AP3 - Formats Introduction, Paragraph AP3.3.2. 

3 For intra-DLA use only, if DAC is applicable to Supply Condition Code (SCC) L, enter PIIN in rp 30-42. 4

See Appendix AP3 - Formats Introduction, Paragraph AP3.3.3. 5 For intra-DLA use only, if DAC is applicable to SCC L, enter the intra-DLA Contract Line Item Number in rp 45-50.
2 of 2

ADC 461

Encl 3

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Fund 52-53 For intra-Component use, enter appropriate code. 

For inter-Component use, leave blank.

Distribution 54-56 Enter distribution code if stocks are segregated and 

maintained by codes reflected in the distribution 

field; otherwise, leave blank.

Project 57-59 Enter project code if stocks are segregated and 

maintained by codes reflected in the project field; 

otherwise, leave blank.

Multiuse 60-64 For intra-Component use, enter data prescribed by 

the Component. For inter- Component use, leave 

blank.

Ownership/Purpose (TO) 65 Enter appropriate TO ownership purpose code, if 

applicable.

Supply Condition (TO) 66 Enter the TO supply condition code.

Routing Identifier 

(Storage Activity)

67-69 Enter RI code of the storage activity at which item is 

stored.

Ownership/Purpose 

(FROM)

70 Enter appropriate FROM ownership/ purpose code, 

if applicable.

Supply Condition (FROM) 71 Enter the FROM supply condition code.

Management 72 Enter appropriate management code; otherwise, 

leave blank.

Day of Year 73-75 Enter the ordinal day of the calendar year that the 

adjustment is processed by the initiating activity.

Multiuse 76-80 For intra-Component use, enter data prescribed by 

the Component. For inter- Component use, leave 

blank.

For Navy Commercial Asset Visibility- Organic Repairables Module (CAV-ORM), the following data 

is entered in the rp 76-80 multi-use field: 6

 Materiel Control 

Code (MCC)

76 Navy CAV-ORM system enters the MCC.

 Estimated Completion 

Date (ECD)

77-80 Navy CAV-ORM system enters the ECD in YDDD 

format.

 6 Refer to ADC 461.
1 of 2

ADC 461

Enclosure 4

ENCLOSURE 4 TO ADC 461

Navy IDD for DAC with inclusion of ECD –

Navy CAV-ORM MILS DAC TO EDI 947I CROSS-REFERENCE

MILS POSITION PICTURE EDI SEGMENT

DOCUMENT ID

ROUTING ID (TO)

(Blank)

NSN

SMIC

U/I

QUANTITY

DOCUMENT NUMBER

SUFFIX

LOSING ICP

(Blank)

FUND CODE

DISTRIBUTION CODE

COG SYMBOL

PROJECT CODE

(Blank)

PURPOSE CODE (TO)

SUPPLY COND. (TO)

ROUTING IDENTIFIER

PURPOSE CODE (FROM)

SUPPLY COND. (FROM)

MANAGEMENT CODE

TRANSACTION DATE

MCC

ECD (YDDD)*

RCDN

PROJECT ORDER NUM

CLIN

AMENDMENT NUMBER

1-3

4-6

7

8-20

21-22

23-24

25-29

30-43

44

45-48

49-51

52-53

54

55-56

57-59

60-64

65

66

67-69

70

71

72

73-75

76

77-80

81-93

94-108

109-114

115-116

X(3)

X(3)

X(1)

X(13)

X(2)

X(2)

9(5)

X(14)

X(1)

X(4)

X(3)

X(2)

X(1)

X(2)

X(3)

X(5)

X(1)

X(1)

X(3)

X(1)

X(1)

X(1)

9(3)

X(1)

X(4)

X(13)

X(15)

X(6)

XX

2/LQ/1000/01=0/02=RP 1-3

2/N1/1100/01=Z4/03=M4/04=RP 4-6/06=TO

-------

2/W19/0200/01=AC/05=FS/06=RP8-20/16=DU

2/LQ/1000/01=SMI/02=RP21-22

2/W19/0200/01=AC/03=RP23-24/16=DU

2/W19/0200/01=AC/02=RP25-29/16=DU

2/N9/0400/01=TN/02=RP30-43

2/N9/0400/07-01=W8/07-02=RP 44

N/A

--------

2/FA2/2060/01=B5/02=RP52-53

N/A

2/LQ/1000/01=COG/02=RP55-56

N/A

--------

2/LQ/1000/01=99/02=RP65

2/LQ/1000/01=83/02=RP66

1/N1/070/01=SB/03=M4/04=RP/67-69/ 06=FR

2/LQ/1000/01=RE/02=RP70

2/LQ/1000/01=BG/02=RP71

N/A

1/W15/0200/01=RP73-75 /04=00 /05=NU

2/LQ/1000/01=MCC/02=RP76

2/G62/0800/01=KA/02=RP77-80(CCYYMMDD)

2/N9/0400/01=Q9/02=RP81-93

2/N9/0400/01=16/02=RP94-108

2/N9/0400/N907-01/0400=FJ N907-02=RP109-114

2/N9/0400/N907-03=2G N907-04=RP115-116

*Note: DLA Transaction Services has agreed that on the 947I translation for the CAV-ORM DAC, the 

ECD field will be in format YDDD and will be translated and put into the KA qualifier as CCYYMMDD.

For Navy Commercial Asset Visibility-Organic Repairables Module (CAV-ORM), the DAC transaction is 

extended as a UDF (User Defined File) with the following data entered into fields 81-116: RCDN, Project 

Order Number, Line Item Number, and Amendment Number.
2 of 2

ADC 461

Encl 4

Navy states that there are several document numbers for CAV-ORM as follows: 

Unique Component Document Number (UCDN)

Format: 

14 positions - no spaces or special characters

Aviation – DoDAAC of repair site (pos 1-6), Julian date (YDDD)(pos 7-10), 2 pos 00-99 

(pos 11-12), letter C (pos 13) , and Q, R, U, V, W, X, or Z (pos 14). 

Maritime - DoDAAC of repair site (pos 1-6), Julian date (YDDD) (pos 7-10), 1 pos 0-9 

(pos 11), 2 pos OO-ZZ (pos 12-13), last pos always R (pos 14).

Business Rules: 

Unique within CAV-ORM per item and site.

UCDN is created by CAV-ORM when an item is requested (or when receipting an item 

that was never requested). 

Repair Component Document Number (RCDN) 

Format: 

14 positions - no spaces or special characters 

Positions 1-3 must equal NWC, NWH, NWL, NWP, NWR, NWS, or NPB. 

(Note: The ‘N’ in position 1 is taken off before being sent to Navy ERP, making the 

CAV-ORM RCDN a 13 pos value in the DLMS translation.)

Positions 7-10 are a Julian date. Cannot be all zeroes or alphabetic.

Positions 11-14 can be numeric or alphabetic.

Business Rules: 

An RCDN is NOT UNIQUE; it does not apply to a single repair item. It often has a oneRCDN-to-many-items relationship. An RCDN comes into CAV-ORM on a WSSauthorized repair workload. Each RCDN represents a particular NIIN’s repair quantity 

for a particular Fiscal Quarter.

CAV-ORM cannot request an item be moved into repair without an RCDN, nor can any 

item be receipted into CAV-ORM (even without a request) without an RCDN.

Project Order Number (PO)

Format: 

15 positions

Positions 1-6 DoDAAC.

Business Rules: 

Funding authorization number created and assigned by Navy ERP to repair item/NIIN.

STAFFING NOTE: CAV-ORM indicated the CAV-ORM Project Order Number is a 

MIPR.