2 of 6 

ADC 343 

Attachment

ATTACHMENT TO 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 

1. ORIGINATOR: Navy; NAVSISA, CAV II Program, Code 924, 717-605-5660

2. FUNCTIONAL AREA: Supply

3. REFERENCES: 

a. DLMSO memorandum, October 7, 2009, subject: ADC 341, Revise DLMS 

Supplement (DS) 867I Issue in Support of Navy Enterprise Resource Program (ERP) and 

Commercial Asset Visibility II (CAV II) Systems with Interim Measure for CAV Detail Issue 

Transaction (Supply) 

b. DLMSO memorandum, October 7, 2009, subject: ADC 342, Revise DLMS 527D 

Advance Receipt Information and 527R Receipt in Support of Navy Enterprise Resource 

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

for CAV Detail Receipt Transaction (Supply) 

4. APPROVED CHANGE: 

a. TITLE/DESCRIPTION: 

(1) Title: 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 (Supply) 

(2) Description of Change: Revise DLMS to support Navy ERP and CAV II data 

requirements by adding specific data elements and code values to DS947I. Includes interim process

for Navy ERP requirement for separate, multiple “detail” transactions for a given inventory 

adjustment transaction to accommodate CAV in Navy ERP release 1.1. 

b. CAV II ESTIMATED COMPLETION DATE (ECD): 

(1) DoD CAV II/CAV-ORM/RTIC Program Manager email of 8/12/2009 ECD explanation: 

“The Navy's response, to how the "Estimated Completion Date" (ECD) is used is provided below: 

CAV II Repair Process - Estimated Completion Date (ECD) 

Background: Within the functionality of CAV II, the 'Estimated Completion Date' (ECD) transaction is used by 

Navy CAV contractors during the Repair Process. The ECD is a contractor's best estimate as to when an asset 

will be returned to ready-for-issue condition. 

When the 'Est Completion Date Requirement' is set to 'Required', the CAV reporter will be required to enter a 

valid Estimated Completion Date. This data entry will take place on the following CAV screens: (1) Induct (F to 

M condition code change), (2) Await Parts (M to G condition code change), (3) Re-induct (G to M condition 

code change) and (4) Item Maintenance. 
3 of 6 

ADC 343 

Attachment

The following 'ECD' Business logic applies: 

If the ECD preference has been set to 'required', a CAV output transaction (Doc-ID ECD) is created during the 

CAV End-of-Day processing simultaneously with the DAC transaction. 

When the Item Maintenance screen is used to enter an Estimated Completion Date, only an ECD transaction is 

created at CAV EOD. These 'ECD' transactions will be passed to the ICPs legacy system or may be available for 

interface with any other system necessary. 

CAV has the ability to annotate on the Main Menu screen the fact that there are assets in inventory that have reached the 

Estimated Completion Date, but have yet to be completed. When this occurs, the Item Maintenance function in CAV 

should be used to issue a new 'Estimated Completion Date'. This action is performed in order to continually supply 

pertinent data to the legacy systems. 

ECD was originally placed in CAV to interface with Navy's SMART project. Now, with the development of Navy ERP 

and the use of SAP software, ECD is a mandatory interface for CAV. 

    

ECD data output by CAV II includes: 

Document Number 

Contractor's Routing Identifier 

NIIN 

Unit of Issue 

Repair Cycle Document Number (RCDN) 

Transaction Date 

Contract Number 

Order Number 

ECD data output by CAV II includes (con’t): 

Award/Order Date 

Action Date 

Estimated Completion Date 

Contractor Reference Number 

Contract Line Item Number 

Furnished by Code 

ICP RIC 

Serial Number 

 (2) Additional explanation for ECD provided by DoD CAV II/CAV-ORM/RTIC PM 

email 9/4/2009: 

“Currently the ECD is an optional field used by contractors upon induction of the item into repair. It can be 

updated any time. 

The field is used to aid planning, in knowing, when the item will come out of repair, and it helps them with how 

much they need to order or buy. Planners will request that the contractor populate the field, or contractors can 

populate the field to aid with their internal processes. 

The future course makes it a mandatory field for all but PBLs and it is required for forecasting and planning.”

 (3) ECD PROCEDURE. Revise DOD 4000.25, DLMS, to add a procedure for ECD 

to Volume 2, chapter 7, Inventory Adjustments (paragraph TBD): 

C7.xx. Commercial Asset Visibility (CAV) Estimated Completion Date (ECD). 

 C7.xx.1. CAV may include an ECD in the Inventory Adjustment transaction, associated 

with a dual adjustment for SCC change, to establish the estimated completion date for an 

item in the repair facility. CAV includes ECD as required when item is undergoing repair or 

awaiting parts. CAV uses ECD, when required, for the following dual SCC changes: SCC 

F to M, SCC M to G, SCC G to M. 

 C7.xx.2. CAV may also generate a Change ECD Transaction. The Change ECD 

Transaction is used to change or establish the ECD for a previously submitted ‘Inventory 

Adjustment (Dual-Supply Condition Code Change)’ transaction. 
4 of 6 

ADC 343 

Attachment

 c. NAVY CAV AND ERP DETAIL AND SUMMARY TRANSACTIONS FOR INVENTORY 

ADJUTEMNT (SINGLE ADJUSTMENTS): 

 (1) In Navy CAV system, a “summary” transaction by document number by national item 

identification number (NIIN) for an inventory adjustment transaction (single adjustment) (MILSTRAP 

D8s and D9s) has the total inventory adjustment quantity that causes the asset balance to change. In 

addition Navy CAV also processes associated individual “detail” inventory adjustment transactions for 

that document number/NIIN. Each “detail” transaction is for a quantity of 1, has a unique repair cycle 

document number (RCDN), and does not affect the balance. The CAV RCDN is assigned by the CAV 

II System when the item(s) is receipted into CAV. 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.

Staffing note: Detail-Summary process is not used with Dual Inventory Adjustment (e.g., MILSTRAP 

DI Code DAC and corresponding 947I functionality). 

Staffing Note: Navy ERP Summary-Detail requirement for CAV is also addressed in ADCs 341 and 

342 (references 3a and 3b respectively) for DLMS 867I Issue and 527R Receipt. 

 (2) CAV II sends “detail” and “summary” transactions together in their “end of day” 

process. For that "end of day" run there will be a summary transaction for each Document Number 

along with the detail transactions for that Document Number. CAV will run "end of day" throughout 

the day - for example every hour - and each time they will output sets of detail/summary inventory 

adjustment transactions for whatever happened during that hour. The details always add up to the 

summary for that "end of day" run - i.e. make a complete set. The summaries are just for the 

transactions in that hourly run - there are no cumulative summaries that cross runs. The transactions 

are all individual DLMS transactions so they are processed as they arrive at Navy ERP throughout the 

day. There is no batching process on the ICP side. The detail and summary transactions will be 

processed in close proximity to each other - but in no specific order - details could be processed 

before summary and vice versa. CAV II uses the summary transaction for the total quantity adjusted 

(e.g., a quantity of 4), and uses a ‘detail’ inventory adjustment transactions as a means to track each 

one of those 4 items for the inventory adjustment by its unique RCDN. 

 (3) While Navy addresses their ‘summary’ transactions as MILSTRAP Document 

Identifier (DI) Code D8X/D9X, the use of D8X/D9X with CAV II is a violation of MILSTRAP as no 

such DI Code exists. DLMSO also noted, in an August 19, 2009 telecon with CAV, the DLMSO 

position that the balance affecting “summary” transactions for the full inventory adjustment quantity 

should reflect a valid MILSTRAP DI Code, and the CAV breakout of that adjustment into detail 

records for 1 each which do not affect the balance, should have used some other designation. 

Further, by definition in DOD 4000.25-2-M, MILSTRAP DI Codes with a numeric second position 

are balance affecting transactions; hence the CAV use of valid MILSTRAP D8_/D9_ for detail 

transactions which do not affect balance also deviates from DOD policy. 

DLMSO made the following recommendation for Navy ERP which Navy indicated 

they could not incorporate in time for Navy ERP 1.1:

(a) To accommodate this requirement under DLMS, DLMSO recommends Navy 

ERP use a single DLMS 947I Inventory Adjustment transaction for both the summary and associated 

detail information. Using the standard DLMS 947I Inventory Adjustment function include the CAV 
5 of 6 

ADC 343 

Attachment

II Summary information in LOOP ID 0300 with appropriate 2/W1901/0200 Quantity or Status 

Adjustment Reason Code, NSN/NIIN at W1905, and document number at 2/N901/0400; and include 

the detail information RCDN in the 2/N901/1600 segment in Loop ID 0330 which is imbedded in 

LOOP ID 0300. The 2/N9/1600 segment could provide the unique RCDNs associated with each 

individual item (if RCDN is required --see RCDN recommendation below). 

(b) RCDN: Navy indicated that the RCDN identifies an individual item at the 

contractor’s plant and is used for tracking purposes. DLMSO recommends that Navy use the Item 

Unique Identification (IUID) unique item identifier (UII) to track an item in maintenance repair 

facility rather than an RCDN. The UII is available in 2/N9/1600 segment in Loop ID 0330 

imbedded in LOOP ID 0300. 

(c) Recommend Navy ERP transition to providing detail information within the 

standard DLMS Inventory Adjustment transaction through the looping structure as identified in 

subparagraph (3)(a) above, and Navy ERP reexamine purpose of the RCDN to track an individual 

item a the repair facility in light of established DOD policy for IUID UII which can be used to 

track an individual item. 

 (4) Interim Measure. Since Navy ERP cannot accommodate the recommended 947I 

Inventory Adjustment processing in subparagraph (3)(a) , (3)(b) and (3)(c) above for Navy ERP 1.1, 

as an interim measure to accommodate Navy ERP’s immediate requirement for interface with 

Navy CAV II legacy system, DLMSO is providing for interim use of 2/W1901/0200 ‘Quantity or 

Status Adjustment Reason Code CS’ for nonstandard use of a non-balance affecting detail inventory 

adjustment transaction by unique RCDN for each item. 

d. REVISE DS 947I AS SHOWN IN THE CHANGE TABLE AT ENCLOSURE 1. 

e. NAVY’S ORIGINAL PROPOSAL FOR 947I MAPPING IS AT ENCLOSURE 2. 

Strikethrough and yellow highlight in the enclosure show deviations from navy’s original proposed 

mapping.

5. COMMENTS to PDC 353 and the Addendum to PDC 353. Navy provided the following 

comments: 

 a. DLMS Compliant Standards changes, estimated implementation date - NAVSUP 

HQ will insure funding is in place for CAV and begin re-engineering changes to the CAV 

program(s) to correct Transaction Sets addressed by ADCs 341, 342, and 343 [formerly PDCs 

351A, 352A, 353 and Addendum to PDC 353] for compliance with DLMS standards, or 

incorporate/subsume CAV in a Navy ERP spiral release, after Navy ERP completes the Single 

Supply Solution Release 1.1 implementation in 2012. 

 b. DLMSO asked if ADCs 341, 342, 343 would impact DLA DSS. Navy confirmed there is 

no impact to DSS. These ADCs only deal with transactions between Navy ERP and CAV. 

6. REASON FOR CHANGE: Navy-ERP has requested that CAV II transmit DLMS transaction 

sets for all requisition/repair transactions which are identified to a Navy-ERP NIIN during the CAV II 

“End of Day” Process. CAV use of the inventory adjustment transaction contains data requirements 

not accommodated by the existing DS 947I Inventory Adjustment transaction. Navy submitted 
6 of 6 

ADC 343 

Attachment

complimentary changes to accommodate CAV II data requirements in the following transaction sets: 

DS 527R Material Receipt/527D Material Due-In (refer to ADC 342), DS 867I Issue (refer to ADC 

341), and DS 856S Shipment Status (refer to PDC 350).

7. ADVANTAGES AND DISADVANTAGES 

 a. Advantages: Adds CAV data requirements for the 947I Inventory Adjustment. 

Provides for Navy CAV/ERP requirement for summary–detail transactions on an interim basis to 

accommodate CAV legacy system requirement.

b. Disadvantages: Navy CAV II legacy system continues to use DI Code D8X/D9X as part of 

their Issue Summary-Detail process in a nonstandard manner that deviates from DOD procedure. 

DOD 4000.25-2-M, MILSTRAP, is the authoritative source for all D-series DI Codes, and DI Codes 

D8X and D9X are not valid. Navy ERP perpetuates the nonstandard concept of separate summary 

(balance affecting inventory adjustment) and detail (non-balance affecting inventory adjustment) 

transactions for Navy ERP release 1.1. See Navy comment at paragraph 5.a.

8. IMPACT: 

a. Publication(s): DLMS Supplement 947I. 

b. Systems/Applications: Changes impact DAAS, Navy ERP and CAV II Systems. CAV II 

changes have been incorporated and documented in the CAV II mapping. Updates based upon the 

approved change will be made. No impact to DLA DSS. 

c. DAASC Mapping: Updates required to DAASC mapping from CAV legacy transactions to 

DLMS. 

d. New DLMS Data Elements. This change adds the following new DLMS Data Elements; these 

data elements are not included in any previous DLMS transactions: 

Data Element ID Code/Name Use Comment 

98 Entity Identifier 

Code 

Q9 Repair Order 

Number 

To identify CAV Repair Cycle 

Document Number (RCDN) 

98 Entity Identifier 

Code 

RN Repair or 

Refurbish Location 

To identify repair facility 

128 Reference 

ID Qualifier 

P5 Position Code To identify CAV unique 

Payback Indicator 

640 Transaction 

Type Code 

A5 Notice of Charge Used to revise estimated 

completion dates for Inventory 

Adjustment (Dual SCC change) 

181 

(2/W1901/0200) 

CS Product Samples This code is used as a “Nonbalance affecting CAV Detail 

Flag" 

Authorized for Navy 

temporary use only. 

W1901 Code ‘CS’ will be 

deleted at a future date. 

Enclosures: 

1) DS 947I Change Table 

2) Navy Mapping Proposal 
ADC 343 Enclosure 1 

ENCLOSURE 1 TO ADC 343 

DS 947I Change Table 

Item # Location CHANGE TABLE for 

DS 947I 

Reason 

1. DLMS 

Introductory

Note 

Add ADC 343 to Introductory note 7

- 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 (Supply)

To identify DLMS changes included in 

the DS 

2. 1/W1505/0200 Add new Transaction Type Code ‘A5’ with 

DLMS note:

A5 Notice of Charge 

DLMS Notes: 1. Change Estimated 

Completion Date (ECD) Transaction. 

Authorized for use by Commercial Asset 

Visibility (CAV) and by organizations 

interfacing with CAV by mutual agreement. 

CAV must assure that trading partners can 

accept this CAV 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/020 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. 

2. Authorized DLMS migration 

enhancement for use by CAV and by CAV 

trading partners by mutual agreement. See 

introductory DLMS note 4.e.

To add capability to change the 

estimated completion date previously 

provided in a 947I inventory 

adjustment transaction. Authorized 

only for CAV use with CAV ICP 

trading partners by mutual agreement. 

Navy must assure mutual agreement 

with the Navy CAV trading partners. 
ADC 343 Enclosure 1 

Item # Location CHANGE TABLE for 

DS 947I 

Reason 

3. 2/W1901/0200 Add Quantity or Status Adjustment Reason 

Code ‘CS’ with DLMS note:

CS Product Samples 

DLMS Note: Used for CAV Detail 

Record. Authorized for INTERIM USE by 

Navy as a flag to identify CAV nonbalance affecting ‘detail’ inventory 

adjustment transactions. The balance 

affecting CAV “summary” inventory 

adjustment transaction must use the 

appropriate standard ‘Quantity or Status 

Adjustment Reason’ code. Code ‘CS’ is 

nonstandard and is authorized for intraNavy interim use pending implementation 

of “detail” information within a standard 

DLMS inventory adjustment transaction 

through looping structure. Used with 

W1916 Inventory Transaction Type ‘AD’ 

and ‘AJ’; not used with ‘DU - Dual 

Inventory Adjustment’. Navy will address 

CAV becoming compliant with DLMS 

standard after Navy ERP completes the 

Single Supply Solution Release 1.1 

implementation in 2012. W1901 code ‘CS’ 

will be deleted from 947I at that time. 

Refer to ADC 343.

Needed on an interim basis to support 

an existing Navy CAV process in Navy 

ERP’s DLMS Migration effort. The 

existing CAV process is a nonstandard 

use of the DLSS and DLMS 

transactions, and is only being 

authorized in DLMS for a temporary 

period until Navy ERP can migrate to a 

standard use of DLMS processing for the 

CAV detail information, at which time 

this code will be eliminated from DS 947I. 

Staffing note: Navy may have to “flip” 

this when interfacing with Navy CAV 

legacy using ‘MILS’ to reflect their 

nonstandard use of summary-detail 

transaction. Navy CAV uses the 

MILSTRAP standard DI Codes 

D8_/D9_ as a non-balance affecting 

detail transaction, and provides for 

nonstandard Navy use of the 

MILSTRAP D8X/D9X transaction for a 

“summary” issue balance affecting 

transaction. Navy CAV process for use 

of D8X/D9X deviates from established 

DOD policy and procedure. DI Codes 

D8X /D9X do not exist in MILSTRAP 

which is the authoritative source for Dseries DI Codes. 

Navy ERP to negotiate with DAASC on 

whether DAASC can flip, or will Navy 

ERP perform the flip.

 4. 1/N101/0400 Add new code with DLMS notes:

RN Repair or Refurbish Location 

DLMS Note: Must use to identify the 

CAV repair site. 

To remove confusion regarding the 

standard use of the ‘SB’ qualifier for 

distribution depots/storage activities, 

DLMSO proposes use of a different 

qualifier to identify CAV repair site. 
ADC 343 Enclosure 1 

Item # Location CHANGE TABLE for 

DS 947I 

Reason 

5. 2/W1905/0200 Revise the data element level note and add 

qualifier ‘NN’ with DLMS note: 

Product/Service ID Qualifier 

DLMS Note: 1. Use only one of codes A1, 

A2, A3 , A4, FB, FS, MG, NN, YP or ZZ 

to identify the materiel shipped. Must use 

National Stock Number (NSN) when 

known, except, when appropriate, brand 

name subsistence items are identified by 

the subsistence identification number. An 

exception is also authorized for CAV 

where materiel may be identified by 

the National Item Identification 

Number (NIIN) when the Federal 

Supply Code (FSC) is not available.

NN National Item Identification 

Number 

DLMS Notes: 1. Use only for CAV when 

the NSN (FSC plus NIIN) is not 

available. Refer to ADC 343.

2. Qualifier NN is a migration code 

approved for use in X12 version 5020. 

This is an authorized DLMS 

enhancement for use by CAV and by CAV 

trading partners by mutual agreement.

Navy CAV-unique requirement: 

FSC is not included in the CAV 

database, and the submitter of the 

CAV transaction does not have 

access to it. If he/she happens to 

know it, then he/she could provide 

it, but it is highly unlikely that the 

CAV user (a contractor at the CAV 

site) will have that information. It 

would require a significant change 

to the CAV system to be able to 

access that information from either 

Navy ERP or FLIS. 

NAVSUP will explore including the 

FSC in this field when we make the 

changes in CAV and Navy ERP to 

become fully DLMS compliant, 

after we complete Navy ERP 

implementation in FY12. However, 

Navy cannot make those changes 

right now, because we are in the 

midst of integrated system testing of 

the CAV-Navy ERP processes. 

Staffing Note: A migration code is 

used for identification of the NIIN 

when passed in the 947I. Use of a 

“migration code” refers to establishing 

an agreement with all trading partners 

to use a valid X12 code from a higher 

version, with its approved X12 

definition, at a lower version of X12. 

Manual intervention may be needed for 

some commercial applications to accept 

the higher version code. (Approved 

DLMS Change 329, Use of Borrowed 

and Migration Codes in DLMS 

Supplements) 
ADC 343 Enclosure 1 

Item # Location CHANGE TABLE for 

DS 947I 

Reason 

6 2/N901/0400 Add new qualifier with DMS note:

P5 Position Code 

DLMS Note: Commercial Asset Visibility 

(CAV) unique data. CAV uses to indicate 

the CAV ‘payback indicator’. The 

payback indicator will always equal 1 

(one). Authorized for CAV use only. Refer 

to ADC343. 

To accommodate Navy CAV 

requirement for a “payback indicator”. 

7. 2/N901/0400 Add qualifier with DLMS note: 

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 

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. It is 

assigned when the item(s) is receipted into 

CAV. Each item has its own unique RCDN. 

Refer to ADC 343. 

To add CAV RCDN to 947I. 

8 2/N901/0400 Revise DLMS note for existing qualifier 

‘X9’:

X9 Internal Control Number 

DLMS Note: Use in CAV transactions to 

identify the unique contractor reference 

number.

Replace note with: 

DLMS Notes: 1. Contractor’s Reference 

Number is used to indicate the unique 

number used by the CAV II System to 

identify and track EDI transactions. 

2. If the Contractor’s Reference Number is 

not available, no entry will be provided. 

Refer to ADC 343. 

Navy CAV-unique requirement. 

Revising DLMS note for existing 

qualifier ‘X9’ for consistency with 

DLMS note in DS 856S. 

Staffing Note: This data field requires 

a new business rule under DLMS to 

suppress this data element from the 

DLMS transaction when not available 

(rather than duplicating the RCDN as 

filler under current CAV-process) 
ADC 343 Enclosure 1 

Item # Location CHANGE TABLE for 

DS 947I 

Reason 

9. 2/G6201/0800 Delete current DLMS note for existing 

qualifier ‘KA’ and replace with new 

DLMS notes as follows: 

KA Scheduled Service Completion 

DLMS Note: Use in CAV transactions to 

indicate the estimated date of the repair 

action completion.

DLMS Notes: 1. Only authorized for use 

by CAV and CAV trading partner ICP by 

mutual agreement. CAV contractor uses to 

indicate the estimated completion date 

(ECD) for an Inventory Adjustment (DualSupply Condition Code (SCC) Change). 

Use only with 2/W1901/020 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 the CAV trading 

partner ICP know the ECD. Refer to ADC 

343. 

2. To change an ECD that was previously 

provided by an Inventory Adjustment – 

Dual (SCC change) transaction, use with 

W1505 Transaction Type Code A5 – 

Notice of Change. Use of W1505 Code 

‘A5’ indicates that only the ECD is being 

changed by the transaction.. 

3. Authorized DLMS migration 

enhancement for use by CAV. See 

introductory DLMS note 4.e. 

To more fully explain CAV use of 

existing qualifier ‘KA’ which CAV uses 

to provide the estimated completed date 

for an inventory adjustment (DualSupply Condition code); and to explain 

how the estimated completion date 

provided can later be updated . 

10. 2/G6203/0800 Add Federal and DLMS notes: 

Federal Note: Use any code. 

DLMS Note: For DLMS, only the 

following codes are authorized. 

DMSO administrative update to add 

standard DLMS notes. 
ADC 343 Enclosure 1 

Item # Location CHANGE TABLE for 

DS 947I 

Reason 

11. 2/G6203/0800 Add qualifier W with DLMS note: 

W Effective Time 

ASC X12 syntax rule states that: 

if either G6203 or G6204 is present, 

then the other is required. This change 

stipulates a qualifier for when G6203 is 

used. 

12. 2/G6204/0800 Add DLMS Note:

DLMS Note: CAV uses “HHMMSS” (6 

position field) for unique date/time stamp. 

To document CAV use of time field. 

13. 2/N901/1600 Add DLMS note 3 to existing qualifier SE:

SE Serial Number 

DLMS Notes: 1. Use to identify the serial 

number. The serial number may not exceed 

30 characters in accordance with IUID 

policy. 

2. DLMS enhancement. See introductory 

DLMS note 4a. 

3. Authorized for use by CAV. 

Documents current CAV use of serial 

number. 

Staffing Note: Recommend Navy ERP 

consider use of IUID UII. 
1 of 7 

ADC 343 Enclosure 2 

ENCLOSURE 2 TO ADC 343 

Strikethrough and yellow highlights identify deviations from original Navy CAV 947I 

proposal.

TRANSACTION SET (947I) 

NAVY WITHDREW THIS REQUIREMENT FOR 947I: 

DATA ELEMENT CHARS A/N 

1. Shipment Indicator 1 A/N

a. DIC(s): D9 

b. EDI (ASC X12) Segment(s): 2/LQ/1000

c. Request the following Qualifier/Data Element be added:

2/LQ/1000 Mandatory

01 96 Code List Qualifier Code (Shipment Release Code)

02 1 position Enter Payback Shipment Indicator Code

Note: Payback Shipment Indicator Code Description 

 1 ‘A’ Condition

 4 ‘ F’ Condition 

Example: LQ*96*1

d. System: CAV II

e. Definition: ‘Shipment Indicator’ identifies status and current condition code of the item being shipped. 

 

 

DATA ELEMENT CHARS A/N 

2. Payback Indicator 1 A/N 

a. DIC(s): D9 

b. EDI (ASC X12) Segment(s): 2/LQ/1000 

c. Request the following Qualifier/Data Element be added: 

2/LQ/1000 Mandatory

01 GD Code List Qualifier Code (Gain or Loss Indicator Code)

02 1 position Enter Payback Indicator Code DLMSO NOTE: LQ is 

intended for DoD code lists. Added ‘payback indicator’ to 2/N901/0400 instead of LQ. 

Note 1: The Payback Indicator Code is transmitted on the D9A and D9X

(Payback) transactions only. 

Note 2: The Payback Indicator Code will always = 1. 

2/N9/0400 01 P5 Position Code 

DLMS Note: CAV uses to indicate the CAV ‘payback indicator’. The payback indicator will always equal 1 

(one). Authorized for CAV use only. Refer to PDC353

Example: LQ*GD*1 N9*P5*1

d. System: CAV II 

e. Definition: Payback Indicator identifies if this transaction is a payback transaction. 
2 of 7 

ADC 343 Enclosure 2 

TRANSACTION SET (947I) CONT’D 

NAVY WITHDREW THIS REQUIREMENT FOR 947I: 

DATA ELEMENT CHARS A/N

3. Consignor’s RIC 3 A/N

a. DIC(s): D8 

b. EDI (ASC X12) Segment(s): 2/N1/1100

c. Request the following Qualifier/Data Element be added:

2/N1/1100 Conditional 

01 CI Entity Identifier Code (Consignor) 

03 M4 Identification Code Qualifier (RIC)

04 3 position Enter RIC From

Note: Transmitted on the D8A/D8X(Borrow) transactions only;

input is optional.

Example: N1*CI**M4*ABC**FROM

d. System: CAV II

e. Definition: Consignor’s RIC identifies the Routing Identifier of the activity where the material was shipped.

NAVY WITHDREW THIS REQUIREMENT FOR 947I:

DATA ELEMENT CHARS A/N

4. Ship To DODAAC 6 A/N

a. DIC(s): D8, D9 

b. EDI (ASC X12) Segment(s): 2/N1/1100

c. Request the following Qualifier/Data Element be added:

2/N1/1100 Optional

01 ST Entity Identifier Code

03 10 Identification Code Qualifier (DODAAC)

04 6 position Enter Ship To DODAAC

Note: Ship To DODAAC is transmitted on the D9X (Payback) only.

Example: N1*ST**10*Q99555

d. System: CAV II

e. Definition: Ship To DODAAC identifies the DoDAAC of the activity where the material is to be shipped. 
3 of 7 

ADC 343 Enclosure 2 

TRANSACTION SET (947I-Estimated Completion Date) 

a. DIC: ECD 

b. EDI (ASC X12) Segment(s): See Below 

c. Request the following Qualifier(s)/Data Element(s) be added: See Below 

d. System: CAV II 

e. Definition: Estimated Completion Date (ECD) record establishes/updates the estimated completion 

date of an item being repaired. The DAC - Induction (F to M) condition establishes the estimated completion 

date. The DAC – Await Parts (M to G) or DAC- Reinduct (G to M) condition updates the estimated completion 

date. It also lets the ICP know when an item will be Ready for Issue (RFI). 

CAV-II IMPLEMENTATION FOR 947I (ECD) 

This appendix lists the data segments that the CAV-II system requires at the Header, Detail, and Trailer levels. 

It identifies the data values expected for each segment. The segment reference is formatted as Table 

Reference/Segment ID/Position Number.

Header Level Requirements

SEGMENT VALUE DESCRIPTION

1/ST/0100 Mandatory 

 01 947 Transaction Set Identifier Code (Warehouse Inventory 

 Adjustment Advice) 

 02 4-9 position Enter Transaction Set Control Number 

Note: Transaction Set Control Number is used to identify the control number 

including the batch and sequential number within the batch file. The 

originator of the Transaction Set assigns the control number. 

Example: ST*947*000012577 

 1/W15/0200 Mandatory 

 01 CCYYMMDD Enter Date of Transaction 

 04 00 Transaction Set Purpose Code (Original) 

 05 NO Transaction Type Code (Notice – Estimated

Completion Date) 

05 A5 Transaction Type Code ‘A5’ = Notice of 

Charge 

Example: W15*20040115***00*A5 
4 of 7 

ADC 343 Enclosure 2 

Header Level Requirements (Cont’d)

SEGMENT VALUE DESCRIPTION

1/N1/0400 Mandatory 

 01 SB Entity Identifier Code (Storage Area)  See DLMS 

note below. Qualifier ‘RN’ will be used for CAV site rather than ‘SB’ 

 03 M4 Identification Code Qualifier (RIC) 

 04 3 position Enter Contractor’s RIC 

 06 FR Entity Identifier Code (Message From) 

Example: N1*RN**M4*QS5**FR 

 RN Repair or Refurbish Location 

DLMS Note: Must use to identify the CAV repair site. 

Detail Level Requirements

SEGMENT VALUE DESCRIPTION

 2/W19/0200 Mandatory 

 01 AH Quantity or Status Adjustment Reason Code 

(Other) 

02 1 Enter Quantity

 03 2 position Enter Unit of Issue 

 05 FS Product/Service ID Qualifier (National Stock Number) 

 06 9 13 position Enter NIIN only NSN 

OR for NIIN use: 

 05 NN Product/Service ID Qualifier (NIIN) 

 06 9 position Enter NIIN only

*** Action Item: Awaiting Navy-ERP response concerning the transmission of the NSN. 

Navy CAV indicated NIIN qualifier was required. 

DLMSO NOTE: Qualifier ‘FS’ is intended for NSN only. Full NSN is required under DLMS when qualifier 

FS is used. DLMSO added migration code ‘NN’ for use with NIIN when NSN is not available. 

Example: W19*AH*1*EA**NN*599901230 

 

2/N9/0400 Mandatory 

 01 X9 Reference Identification Qualifier 

(Internal Control Number) 

 02 1-25 position Enter Contractor’s Unique Reference Number 

Note: If Contractor’s Unique Reference Number is not present, the RCDN will be 

transmitted. 

The RCDN will consist of a 14 position field. <== DLMSO note: Cannot send an 

RCDN under qualifier ‘X9’ which is intended for the ‘contractor reference number’. 

If ‘contractor reference number’ is not available, do not send qualifier ‘X9’ data in 

DLMS transaction. See replacement notes below. 

Note 1: Contractor’s Reference Number is used to indicate the unique number 

 used by the CAV II System to identify and track EDI transactions. 

Note 2: If the Contractor’s Reference Number is not available, no entry will be 

provided. Refer to PDC 353. 

Example: N9*X9* N0036708M1234 
5 of 7 

ADC 343 Enclosure 2 

Detail Level Requirements (Cont’d)

 

SEGMENT VALUE DESCRIPTION

2/N9/0400 Mandatory 

 01 WF Locally Assigned Document Number  For consistency with 

856S and other transactions, qualifier ‘Q9’ will be used for RCDN rather than ‘WF’ 

 02 14 position Enter Repair Cycle Document Number (RCDN) 

Note : Used to indicate the unique number assigned by the CAV II System to 

 identify and track CAV transactions. 

DLMSO adding qualifier/note for RCDN: 

01 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 PDC 353.

Example: N9*Q9*Q9504073601234 

2/N9/0400 Conditional 

 01 ZA Reference Identification Qualifier (Supplier) 

 02 1 position Enter Furnished By Code 

Note: Enter Furnished By Code as follows: 

 A – Material in Administrative Hold 

 B – Material Furnished by both the Government and Contractor 

 C – Material Furnished by the Contractor 

 G – Material Furnished by the Government 

STAFFING Note: DLMSO does not know what bearing this code has on an inventory adjustment 

transaction and recommends Navy ERP not design for this data in 947I. Where the materiel came from 

is addressed by processes unrelated to inventory adjustment transaction. Recommend this be an 

interim use only to accommodate legacy system. 

Example: N9*ZA*C 

2/CS/0500 Conditional 

 01 13 position Enter Contract Number 

 03 4 position Enter Call/Order Number 

 Conditional 

04 C7 Contract Line Item Number 

 05 4 or 6 position Enter CLIN/SUBCLIN 

 

Note: A 4 position CLIN (e.g. 0001) or 6 position SUBCLIN (e.g. 0001AA) will be 

transmitted. 

Example: CS*N0010304D1234**5357*C7*0001AA 
6 of 7 

ADC 343 Enclosure 2 

Detail Level Requirements (Cont’d)

SEGMENT VALUE DESCRIPTION

2/G62/0800 Optional 

 01 04 Date Qualifier (Purchase Order Date) 

 02 CCYYMMDD Enter Award/Order Date 

Example: G62*04*20041122 

 

 2/G62/0800 Mandatory 

 01 09 Date Qualifier (Process Date) 

 02 CCYYMMDD Enter Process Date of Inventory Adjustment (ECD) 

 03 W Time Qualifier (Process Time) 

 04 HHMMSSDD Enter Process Time of Inventory Adjustment (ECD) 

 (Universal Time Coordinate) 

Note: The CAV-EDI application uses “HHMMSS” (6 position field) to indicate 

the unique Date Timestamp.

Example: G62*09*20040904*W*16393500 

 2/G62/0800 Mandatory 

01 KA Date Qualifier (Scheduled Service Completion) 

 (Estimated Completion Date) 

 02 CCYYMMDD Enter Estimated Completion Date 

Example: G62*KA*20081125 

 

2/LM/0900 Mandatory 

 01 DF Agency Qualifier Code (DOD) 

Example: LM*DF 

 

2/LQ/1000 Mandatory

01 0 Code List Qualifier Code (Doc ID)

02 ECD Enter Doc ID (Estimated Completion Date)

Example: LQ*0*ECD

For mapping from DLMS to Navy CAV legacy inventory adjustment and ECD transactions, if that is 

required, the presence of 2/G6201/0800/KA indicates an ECD transaction will be required in addition to 

MILSTRAP DI Code DAC. The G62 date qualifier ‘KA’ estimated completion date (ECD) is only used by 

CAV. 

DLMSO Staffing Note: Navy ERP should plan to provide the 2/G6201/0800/KAECD (the date) as part of 

the inventory adjustment transaction (W1505 Transaction Type Code ‘NU-Inventory Adjustment’) when 

ECD is required with the inv adjustment transaction, rather than as 2 separate transactions. 

When changing the ECD, then W1505 Transaction Type Code ‘A5-Notice of Charge’ should be used. 

Notice of change should only be used to change an ECD associated with an inventory adjustment 

transaction (Dual-SCC change) that was already processed. 
7 of 7 

ADC 343 Enclosure 2 

Detail Level Requirements (Cont’d)

SEGMENT VALUE DESCRIPTION

2/N1/1100 Mandatory

 01 Z4 Entity Identifier Code (Owning Inventory Control 

Point) 

 03 M4 Identification Code Qualifier (RIC) 

 04 3 position Enter ICP RIC 

 06 TO Entity Identifier Code (Message To) 

Example: N1*Z4**M4*N32**TO 

 2/LX/1500 Conditional Assigned Number 

 01 1-6 position 1st and only iteration of loop 

Note: This segment must be used with any occurrence of the 2/N9/1600 

segments below. 

Example: LX*1 

2/N9/1600 Optional 

 01 SE Reference Identification Qualifier (Serial Number) 

 02 1-32 position Enter Serial Number 

 

Example: N9*SE*1313132160000A1112000987654321 

Trailer Level Requirements

SEGMENT VALUE DESCRIPTION

 

 

2/SE/2100 Mandatory 

 01 1-10 position Number of Included Segments 

(Total number of segments in this transaction 

set including ST and SE segments) 

02 4-9 position Transaction Set Control Number 

 (Contains the same number cited in ST02) 

Example: SE*31*000012577