1 of 4 

ADC 342 

Attachment

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

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, 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 Receipt Transaction (Supply) 

b. DLMSO memorandum, October 7, 2009, subject: 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 Receipt Transaction (Supply) 

4. APPROVED CHANGE: 

a. TITLE/DESCRIPTION: 

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

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

by adding specific data elements and code values to DS 527D Advance Receipt Information (ARI)/ 

Prepositioned Materiel Receipt (PMR) and 527R receipt transactions. Includes interim process for Navy 

ERP requirement for separate, multiple “detail” transactions for a given receipt transaction to 

accommodate CAV in Navy ERP release 1.1. 

b. NAVY CAV AND ERP DETAIL AND SUMMARY TRANSACTIONS FOR RECEIPT: 

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

identification number (NIIN) for receipt transactions has the total receipt quantity that causes the asset 

balance to change. In addition Navy CAV also processes associated individual “detail” receipt 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 summary receipt transaction set 

identifies the 'RCDN Range Start' and 'RCDN Range End' associated with the corresponding detail 

transactions. 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: Navy ERP Summary-Detail requirement for CAV is also addressed in ADC 341 

(reference 3a) for DLMS 867I Issue and ADC 343 (reference 3b) for DLMS 947I Inventory 

Adjustment (for DI Code DAC equivalent functionality). 
2 of 4 

ADC 342 

Attachment

 (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 receipt 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 is no 

cumulative summaries that cross runs. The detail 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 receipt 

summary transaction for the total quantity receipted (e.g., a quantity of 4), and uses a ‘detail’ receipt 

transactions as a means to track each one of those 4 items receipted by its unique RCDN

 (3) The DOD MILSTRAP Administrator notes that while Navy’s proposed change addressed 

their ‘summary’ transactions as MILSTRAP Document Identifier (DI) Code D4X/D6X, the use of 

D4X/D6X as described with CAV II is a violation of MILSTRAP. MILSTRAP DI Code D4X/D6X is a 

Logistics Reassignment transaction which the Losing Item Manager (LIM) sends to the Gaining Item 

Manager (GIM). DLMSO also noted in an August 19, 2009 telecon with CAV the DLMSO position that 

the balance affecting “summary” transaction for the full receipt quantity should reflect a valid 

MILSTRAP DI Code, and the CAV breakout of that receipt 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 receipt D4_/D6_ 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 under DLMS, DLMSO recommends Navy ERP use a single 

DLMS 527R Receipt transaction for both the summary and associated detail information by providing 

the controlling document number/NIIN and summary quantity in the LOOP ID LIN and include the 

detail information RCDN in Loop ID REF imbedded in LOOP ID LIN (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 the imbedded LOOP ID REF. 

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

DLMS Receipt transaction through looping structure as identified in subparagraph (3)(a) above, and Navy 

ERP reexamine purpose of the RCDN to track an individual item at 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 527R Receipt 

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 LIN01 code ‘Y’ for nonstandard use of a non-balance affecting detail receipt 

transaction by unique RCDN for each item. 
3 of 4 

ADC 342 

Attachment

 c. REVISE DS 527R AS SHOWN IN THE CHANGE TABLE AT ENCLOSURE 1. 

 d. REVISE DS 527D AS SHOWN IN THE CHANGE TABLE AT ENCLOSURE 2. 

 e. NAVY’S ORIGINAL PROPOSAL FOR 527D/527R MAPPING IS AT ENCLOSURE 3. 

Strikethrough and yellow highlight in Enclosure 3 show deviations from Navy’s original proposed mapping. 

5. PDC 352A COMMENTS: 

a. DLA DDC provided the following comment: 

DLA DDC Comment: DLMSO RESPONSE 

“Operationally, the DDC has concerns with shipments of these assets to 

our depots where the contractor is attaching DD250's and 1348's to the 

documentation, which causes the receiving operators confusion. It also has 

been found that these small contractors have DODAAC's that are not 

registered with DODAAD. My understanding is that these are CAGE 

codes of the vendors used by Navy, which usually start with a Q. 

Transactions are not rejected, but when DSS attempts to process a receipt, 

we validate DODAAC against the DODAAD and receive a reject. We then 

must use a workaround to process this materiel into stock with the 

Document number DODAAC supplied, which also causes confusion and 

poises our receivers for a higher error rate in receipts.”

Concern is noted. 

DLMSO is planning a meeting 

with Navy, DAASC, 

DLA/DDC/DSS regarding 

another Navy DoDAAC issue. 

DLMSO will add this topic to 

the agenda. Meeting date TBD. 

b. Navy provided the following comments: 

 1) 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. 

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

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

The new fields like RCDN are just used during the repair process - not by the receiving process at 

the Distribution Depot (DD). The National Item Identification Number (NIIN) is also only used 

between Navy ERP and CAV. Navy ERP will send a PMR to DSS that has the full NSN. 

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 527D/527R transaction contains data requirements not accommodated by 

the existing DS. Navy submitted complimentary changes to accommodate CAV II data requirements in the 

following transaction sets: DS 867I Issue (ADC 341), DS 947I Inventory Adjustment (ADC 343) and DS 

856S Shipment Status (PDC 350).

7. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages: Clarifies CAV data requirements for DS 527D Materiel Due-In and DS 527R 

Material Receipt. Provides for Navy CAV/ERP requirement for summary–detail transactions on an 

interim basis to accommodate CAV legacy system requirement. 
4 of 4 

ADC 342 

Attachment

b. Disadvantages: Navy CAV II legacy system continues to use MILSTRAP DI Code D4X-D6X 

logistics reassignment related transactions as part of their receipt Summary-Detail process in a nonstandard 

manner that deviates from DOD procedure. Navy ERP perpetuates the nonstandard concept of separate 

summary (balance affecting receipt) and detail (non-balance affecting receipt) transactions for Navy ERP 

release 1.1. See Navy comment at paragraph 5.b.1).

8. IMPACT: 

a. Publication(s): DS 527D and DS527R. 

b. Systems/Applications: Changes impacts 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 Element not 

included in any previous DLMS transactions: 

527R Data Element ID Code/Name Navy CAV/ERP Use 

2/N901/90 128 UV Range Number Used to provide the RCDN Range 

e. Interim Code. This change revised use of LIN01 coding to provide an interim use for Navy ERP/CAV: 

527R Data Element ID Code/Name Interim Use Comment 

2/LIN01/10 350 

Revised note for value 

of 527R LIN01 to add 

value ‘Y’ 

527R LIN01 Value ‘Y’

This code is used as a 

“Non-balance 

Effecting CAV Detail 

Flag"

Value ‘Y’ Authorized for 

interim use by Navy to 

identify CAV nonbalance affecting ‘detail’ 

receipt transactions. 

Authorized for 

temporary use only. 

Value ‘Y’ will be 

deleted at a future 

date. 

Enclosures: 

1) DS 527R Change Table 

2) DS 527D Change Table 

3) Navy Mapping Proposal
1 of 4 

ADC 342 

Encl 1 – 527R Changes 

ENCLOSURE 1 TO ADC 342 

DLMS Supplement 527R Change Table 

Item # Location CHANGE TABLE for 

DS 527R Receipt

Reason 

1. DLMS 

Introductory

Note 

Add ADC 342 to Introductory note 7

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

To identify DLMS changes included 

in the DS 

2. 2/LIN01/10 Revise existing LIN01 DLMS Note to add 

new entry #24 ‘Y’ to address Navy ‘detail’ 

records for interim basis: 

24. Y – CAV Detail Record. 

Authorized for INTERIM USE by Navy as a 

flag to identify CAV non-balance affecting 

‘detail’ receipt transactions. The balance 

affecting CAV “summary” receipt transaction 

must use the appropriate standard LIN01 

code. Value ‘Y’ is nonstandard and is 

authorized for intra-Navy interim use pending 

implementation of “detail” information within 

a standard DLMS receipt through looping 

structure. Navy will address CAV becoming 

compliant with DLMS standard after Navy 

ERP completes the Single Supply Solution 

Release 1.1 implementation in 2012. LIN01 

code ‘Y’ will be deleted from 527R at that 

time. Refer to ADC 342. 

Needed on a interim basis to support 

an existing Navy CAV process in 

Navy ERP’s DLMS Migration effort. 

The existing 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 receipt 

transaction for the CAV detail 

information, at which time this code 

will be eliminated from DS 527R. 

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 

receipt as a non-balance affecting 

detail transaction, and CAV uses 

MILSTRAP D4X/D6X logistics 

reassignment receipt transactions for 

a “summary” receipt balance 

affecting transaction. Navy CAV 

process for use of D4X/D6X deviates 

from established DOD policy and 

procedure. 

Navy ERP to negotiate with DAASC 

on whether DAASC can flip, or will 

Navy ERP perform the flip.
2 of 4 

ADC 342 

Encl 1 – 527R Changes 

Item # Location CHANGE TABLE for 

DS 527R Receipt

Reason 

3. 2/LIN02/10 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, FT, MG, NN, YP or ZZ 

to identify the materiel. Must use National 

Stock Number (NSN) (code FS) when known, 

except when appropriate brand name 

subsistence items are identified by the 

Subsistence Identification Number (code A4). 

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 342.

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 CAVNavy ERP processes. 

Staffing Note: A migration code is 

added for identification of the NIIN 

when passed in the 527R 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) 
3 of 4 

ADC 342 

Encl 1 – 527R Changes 

Item # Location CHANGE TABLE for 

DS 527R Receipt

Reason 

4. 2/N901/90 Add qualifier ‘Q9’ with DLMS note:

Q9 Repair Order Number 

DLMS Note: CAV uses to cite the Repair 

Cycle Document Number (RCDN) assigned by 

the CAV II System. 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. 

Documents CAV II requirement for a 

Repair Cycle Document Number 

(RCDN). Documents that RCDN is 

used in receipt transaction for the 

detail records only. 

Contains administrative changes for 

consistency with wording of DLMS 

note for qualifier ‘Q9’ in PDC 350, 

and ADCs 341, & 343. 

NOTE: The standard receipt 

(‘summary”) transaction contains 

the RCDN range at 2/N901/90 

‘UV’. 

5. 2/N901/90 Add qualifier ‘UV’ with DLMS note:

UV Range Number 

DLMS Note: CAV uses with receipt 

transactions to cite the CAV Repair Cycle 

Document Number (RCDN) range. The 

RCDN range is a 28 position field. The first 

14 positions identify the RCDN Range Start. 

The remaining 14 positions identify the 

RCDN Range End. Refer to ADC 342. 

Documents CAV II requirement for the 

28 position range for the Repair Cycle 

Document Number (RCDN) in the 

standard balance affecting ‘summary’ 

receipt transaction. 

Staffing note: Navy may have to “flip” 

this when interfacing with Navy CAV 

legacy using ‘MILS’ to reflect their 

MILSTRAP use of summary-detail 

transaction which uses the MILSTRAP 

standard receipt as a non-balance 

affecting detail transaction, and 

provides for CAV use of the 

MILSTRAP D4X/D6X logistics 

reassignment receipt transaction for a 

“summary” receipt transactions. This 

Navy CAV process deviates from 

established DOD policy and procedure. 

6. 2/N901/90 Revise DLMS note 3 for existing 

qualifier ‘X9’:

X9 Internal Control Number 

DLMS Note: 3. Contractor’s Reference 

Number is used to indicate the unique 

number used by the CAV II System to 

identify and track EDI transactions. 

Refer to ADC 342. 

Administrative change to DLMS 

note for consistency with wording 

of DLMS note for qualifier ‘X9’ 

in PDC 350, and ADCs 341 & and 

343.
1 of 5 

ADC 342 

Encl 2 - 527D Changes 

ENCLOSURE 2 TO ADC 342 

DLMS Supplement 527D Change Table 

Item # Location CHANGE TABLE for 

DS 527D 

Reason 

1. DLMS 

Introductory 

Note 

Add ADC 342 to Introductory note 7

- 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 

To identify DLMS changes included in the 

DS 

2. 1/N101/70 Revise N101 DLMS note:

DLMS Notes: 

1. For logistics reassignment transactions 

associated with 1/BR01/20 codes LC, TI, TJ, and 

TK, use only one of codes ZN, or ZP. For logistics 

reassignment memorandum due-in 

transactions (1/BR02/20 code DA with 

2/LIN01/10 code T), use only code ZN. 

2. For Prepositioned Materiel Receipt/Advance 

Receipt Information (PMR/ARI) transactions 

(1/BR02/20 code DE), use code KA to identify the 

ICP to which the receipt will be reported. This will 

normally be the organization generating the 

PMR/ARI transaction. Repeat the N1 loop to use 

qualifier 41 when the organization returning the 

materiel and preparing the PMR/ARI transaction is 

different from the organization to which the receipt 

will be reported. 

Add new code ’41-Submitter’ with DLMS notes: 

41 Submitter

DLMS Note 1. Use to identify the party preparing 

the PMR/ARI when the receipt is to be reported to 

another organization. 

2. DLMS enhancement; see introductory DLMS note 

4a. Refer to PDC 331. 

3. CAV uses with PMR/ARI transaction to identify 

that the CAV contractor maintenance site shipping 

the item is generating the transaction. Authorized 

DLMS migration enhancement for CAV use. See 

introductory DLMS note 4.g. Refer to ADC 342. 

Administrative update at note 1

clarifies that codes ZN and ZP (LIM 

and GIM) are only used with logistics 

reassignment transaction functions. 

Navy Business Logic: When the CAV 

contractor returns an asset to a stock point; 

the asset is issued (867I/DI Code D7_) and 

under MILS, CAV also creates a PMR. 

CAV generates PMR based on a ‘CAV User 

Preference’ which is set by the ICP CAV 

Administrator. 

NOTE: CAV sends this PMR transaction 

set via DAASC to Navy-ERP. 

 

DLMSO NOTE: The addition of code ’41-

submitter’ provides a generic code, as a 

DLMS enhancement, for use when the 

PMR/ARI is generated by the party 

originating the return and the resulting 

receipt will be reported to the ICP. 

Navy originally proposed adding qualifier 

‘SB-Storage activity to represent CAV, 

however this change authorizes the new 

generic code ‘submitter’ for the PMR. 

The CAV maintenance contractor can use 

this code to support the existing CAV 

requirement for the contractor to generate 

the PMR/ARI. 
2 of 5 

ADC 342 

Encl 2 - 527D Changes 

Item # Location CHANGE TABLE for 

DS 527D 

Reason 

3. 2/LIN01/10

PDC 352A Staffing note: DOES NAVY USE 

the DETAIL/SUMMARY CONCEPT WITH 

THE ARI/PMR? If yes, new LIN01 code ‘Y’ as 

added to 527R will be required. Requested that

Navy advise DLMSO of requirement in response 

to PDC 352A. 

No Navy response. No requirement 

identified. No action taken to add code 

to 527D. 

4. 2/LIN02/10 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, 

A4, FB, FS, FT, MG, NN, YP or ZZ to identify 

the materiel. Must use National Stock Number 

(NSN) (code FS) when known except when 

appropriate, brand name subsistence items are 

identified by the Subsistence Identification 

Number (code A4). 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. 

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 

added for identification of the NIIN 

when passed in the 527D. 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) 

5. 2/G6201/50 Add qualifier ‘52’ with DLMS note.

52 Order 

DLMS Note: Commercial Asset Visibility (CAV) 

uses to indicate an order date in the prepositioned 

materiel receipt/advance receipt information 

transaction. 

To document CAV use of order date. 
3 of 5 

ADC 342 

Encl 2 - 527D Changes 

Item # Location CHANGE TABLE for 

DS 527D 

Reason 

6. 2/G6201/50 Add qualifier ‘BB’ with DLMS note.

BB Transaction Control Date 

DLMS Note: Use to cite the date the transaction 

was prepared. 

To provide for transaction preparation 

date consistent with other DLMS 

transactions. 

7. 2/G6203/50 Open G6203 and add data element level notes and 

qualifier ‘W’ with DLMS note:

Add Federal and DLMS notes: 

Federal Note: Use any code. 

DLMS Note: For DLMS, only the following codes 

are authorized. 

W Effective Time 

DLMS Notes: Use in conjunction with G6201 code 

BB only to establish unique date/time stamp. 

Express time in six-position format (HHMMSS). 

This is an authorized DLMS enhancement; see 

introductory DLMS 5g. 

To provide for time of transaction 

preparation and stipulate a specific time 

qualifier when G6203 is used. 

8. 2G6204/50 Open Data Element G6204 To accommodate ASC X12 syntax rule: 

If either G6203 or G6204 is present, 

then the other is required. 

9. 2/N901/90 Add qualifier ‘Q9’ with DLMS note:

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. 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. 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. Each item has its own unique RCDN. 

Refer to ADC 342. 

Documents CAV II requirement for a 

Repair Cycle Document Number 

(RCDN). Documents that RCDN is used 

in receipt transaction for the detail 

records only. 

Contains administrative changes for 

consistency with wording of DLMS 

note for qualifier ‘Q9’ in PDC 350, and 

ADCs 341, & 343. 

Staffing Note: Does Navy use 

Detail/Summary concept with PMR 

transactions? If yes, is the RCDN 

range included in the PMR Summary 

transaction? 

Requested Navy advise DLMSO of

requirement in response to PDC 352A. 

No requirement was identified
4 of 5 

ADC 342 

Encl 2 - 527D Changes 

Item # Location CHANGE TABLE for 

DS 527D 

Reason 

10 2/N901/90 Combine current DLMS notes 1 and 2, and add a 

DLMS note 2 for CAV for existing qualifier ‘X9’:

X9 Internal Control Number 

Current DLMS Notes 1 and 2 combined into 

note 1: 1. Use with procurement source 

transactions when a transaction number (aka 

document number) is needed in addition to the

contract number for transaction tracking purposes. 

Identify the controlling contract number in the

2/CS/020 segment. DLMS enhancement; see 

introductory DLMS note 4a. 

New DLMS Note: 2. Contractor’s Reference 

Number is used to indicate the unique number 

used by the CAV II System to identify and track 

EDI transactions. Refer to ADC 342. 

Administrative change for consistency 

with wording of other DS. 
1 of 4 

ADC 342 

Encl 3 - Navy’s Proposed Mapping 

ENCLOSURE 3 TO ADC 342 

Strikethrough and yellow highlights identify deviations from original Navy CAV 

527D/527R proposal.

TRANSACTION SET (527R) 

DATA ELEMENT CHARS A/N 

1. Repair Cycle 

 Document Number (RCDN) 14 min-28 max A/N 

a. DIC(s): D4, D6 

b. EDI (ASC X12) Segment(s): 2/N9/090 

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

 

RCDN: 

2/N9/090 Mandatory 

 01 WF Q9 Repair Order Number Locally Assigned Document Number 

 02 14 or 28 Enter Repair Cycle Document Number (RCDN) 

 position 

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

identify and track CAV transactions. 

Note 2: D4S will consist of a 14 position field (14 min/max). 

Q9 Repair Order Number 

DLMS Note: CAV uses to cite the Repair Cycle Document Number (RCDN) assigned 

by the CAV II System. 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. 

 

RCDN Range: 

2/N9/090 

 01 WF UV Range Number Locally Assigned Document Number 

 02 14 or 28 Enter the Repair Cycle Document Number (RCDN) range

 position 

Note 3: D4X will consist of a 28 position field. The first 14 positions will identify

 the RCDN Range Start. The remaining 14 positions will identify the

 RCDN Range End. 

UV Range Number 

DLMS Note: CAV uses with the balance affecting standard receipt transaction to cite the 

range for the Repair Cycle Document Numbers (RCDN). The RCDN range is a 28 position 

field. The first 14 positions identify the RCDN Range Start. The remaining 14 positions 

identify the RCDN Range End. Refer to ADC 342. 

DLMSO STAFFING NOTE: The DLMS 527R standard transaction, e.g., 
2 of 4 

ADC 342 

Encl 3 - Navy’s Proposed Mapping 

D4S equivalent, must be used for the full receipt quantity (i.e., CAV 

Summary transaction)

[e.g., D4S = 527R with BR02 Transaction Type Code D4 with 2/CS01/020 Contract number, and 

LIN01 code A] 

Example D4S: N9*WF*Q9959373601234

Example D4X: N9*WF*Q9959373601234Q9504073601444

 Note 4: D6A/K will consist of a 14 position field (14-min/14-max). 

Note 5: D6X will consist of a 28 position field (14-min/28-max). The first 14

 positions will identify the RCDN Range Start. The remaining 14

 positions will identify the RCDN Range End. 

Example D6A/K: N9*WF*Q9966681200015

Example D6X: N9*WF*Q9966681200015Q9966681200016

d. System: CAV II 

e. Definition: Repair Cycle Document Number(RCDN) identifies an individual item at the contractor’s 

plant. It also indicates the unique number assigned by the CAV II System to identify and track CAV 

transactions. Position (1-6) identifies the Contractor’s DODAAC, Julian Date (pos 7-10) and Serial Number 

(pos 11-14). 

TRANSACTION SET (527D) 

DATA ELEMENT CHARS A/N 

1. Owning ICP RIC 3 A/N 

a. DIC(s): DWK 

b. EDI (ASC X12) Segment(s): 1/N1/070 

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

1/N1/70 Mandatory

 01 SB 41 Entity Identifier Code (Submitter) 

 03 M4 Identification Code Qualifier (RIC) 

 04 3 positions Contractor’s RIC 

 

Example: N1*41**M4*N32 

d. System: CAV II 

e. Definition: Owning ICP RIC identifies the source of supply. 

Staffing Note: Generic qualifier ‘41-Submitter’ was previously added to 527D and can be used 

for the CAV repair facility.

TRANSACTION SET (527D) CONT’D 
3 of 4 

ADC 342 

Encl 3 - Navy’s Proposed Mapping 

DATA ELEMENT CHARS A/N 

2. Repair Cycle Doc No. (RCDN) 14 min-14 max A/N 

a. DIC(s): DWK 

b. EDI (ASC X12) Segment(s): 2/N9/090 

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

 2/N9/90 Mandatory 

 01 WF Q9 Locally Assigned Document Number 

 02 14 position Enter Repair Cycle Document Number (RCDN) 

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

 identify and track CAV transactions. 

Note 2: DWK will consist of a 14 position field (14 min/max). 

Example: N9*Q9*Q9504073601234 

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

d. System: CAV II 

e. Definition: Repair Cycle Document Number(RCDN) identifies an individual item at the contractor’s plant. 

It also indicates the unique number assigned by the CAV II System to identify and track CAV transactions. 

Position (1-6) identifies the Contractor’s DODAAC, Julian Date (pos 7-10) and Serial Number (pos 11-14). 
4 of 4 

ADC 342 

Encl 3 - Navy’s Proposed Mapping 

TRANSACTION SET (527D) CONT’D 

DATA ELEMENT CHARS A/N 

3. Due-In Receipt Date 8 N 

a. DIC(s): DWK 

b. EDI (ASC X12) Segment(s): 2/G62/050 

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

 2/G62/050 Mandatory 

 01 BB Date Qualifier (Transaction Control Date) 

 02 CCYYMMDD Enter Date contractor received material 

 03 W Effective Time 

 04 HHMMSSDD Enter Time contractor received material 

Note: The “HHMMSS” (6 position field) is used to indicate the unique Date 

Timestamp.

Example: G62*35*20080429*W*132328

d. System: CAV II 

e. Definition: ‘Due–In Receipt Date’ identifies the date an item was received at the contractor’s plant. 

Staffing Note: Qualifier ‘BB’ is added as the date the transaction was prepared. Does Navy 

require a ‘date item received at contractor plant’ in a PMR transaction? For what purpose? How is 

this date known/used in a PMR/Advance Receipt Information transaction? 

Requested Navy advise DLMSO in response to PDC 352A---No response. 

DATA ELEMENT CHARS A/N 

4. Award/Order Date 8 N 

a. DIC(s): DWK 

b. EDI (ASC X12) Segment(s): 2/G62/050 

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

 2/G62/50 Optional

 01 52 Date Qualifier (Ordered-Award/Order Date) 

02 CCYYMMDD Enter Award/Order Date 

Example: G62*52*20000808 

 

d. System: CAV II 

e. Definition: ‘Award/Order Date’ identifies the date the contract or order against a contract was issued.