1 of 4 

ADC 341 

Attachment 

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

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

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

(2) Description of Change: Revise DLMS to support CAV II data requirements by adding 

specific data elements and code values to DS 867I Issue transaction, and provides interim process for 

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

accommodate CAV in Navy ERP release 1.1. Changes from PDC 351A are gray highlighted in this 

attachment and in Enclosure 1.

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

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

identification number (NIIN) for issue transactions has the total issue quantity that causes the asset balance to 

change. In addition Navy CAV also processes associated individual “detail” issue 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: Navy ERP Summary-Detail requirement for CAV is also addressed in ADC 342 (reference 3a) 

for DLMS 527R receipt and ADC 343 (reference 3b) for 947I Inventory Adjustment.

 (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 
2 of 4 

ADC 341 

Attachment 

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

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

transactions as a means to track each one of those 4 items issued 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 D7X, the use of D7X as 

described 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 issue quantity should reflect a valid MILSTRAP DI Code, and the breakout of 

that issue 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 D7_ 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 867I Issue transaction for both the summary and associated detail information. using 

the standard DLMS 867I issue function as the CAV II Summary information with appropriate 2/PTD01 

Product Transfer Type Code, with document number and NSN/NIIN at 2/REF/30; and include the detail 

information RCDN in the 2/REF/290 segment in Loop ID LX which is imbedded in LOOP ID PTD. The 

2/REF/290 segment at the Loop ID LX could provide the unique RCDNs associated with each individual 

item issued (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/REF/290 segment in Loop ID LX imbedded in LOOP ID PTD.

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

DLMS Issue 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 867I Issue 

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/PTD01/10 Product Transfer Type Code “SM-Sample’ for 

nonstandard use of a non-balance affecting detail issue transaction by unique RCDN for each item. 

(5) Shipment indicator code. Initially Navy has proposed inclusion of a shipment indicator 

code in DS 867I issue. The description Navy provided for shipment indicator (in table below) 

appeared to DLMSO to be satisfied by the supply condition code. Upon further consideration, Navy 
3 of 4 

ADC 341 

Attachment 

ERP determined they did not need the shipment indicator on the DS 867I Issue transaction as the 

condition code field is already captured on the issue. 

Navy Shipment Indicator Code DLMSO Position NAVY ERP 

Disposition 

Originally Navy proposed adding 867I 

2/LQ01/270 qualifier for ‘Shipment Indicator’ 

which identifies status and current condition 

code of the item being shipped as follows: 

CAV Shipment Indicator Codes:

1- ‘A’ condition materiel 

2- ‘J’ to ‘F’ condition material 

3- ‘J’ to ‘A’ condition materiel 

4- Non-worked ‘F’ Condition Material 

5- ‘L’ to ‘F’ Condition Material 

 BLANK - ‘H’ Condition Material 

1. DLMSO recommended using Supply 

Condition Code (existing LQ01 

qualifier 83) to identify the supply 

condition of item issued (information 

conveyed by CAV Shipment Indicator 

codes 1, 4, and BLANK). 

2. CAV codes 2, 3 & 5 convey 

information on condition code change, 

which should be available from the 947I 

Inventory Adjustment transaction, and 

should not be provided in an Issue 

transaction. 

Navy ERP does not 

need the shipment 

indicator on the 

subject transaction. 

The condition code 

field is already 

captured on the D7 

[Issue transaction]. 

Shipment indicator is 

redundant data.

 c. REVISE DS 867I AS SHOWN IN THE CHANGE TABLE AT ENCLOSURE 1. 

 d. NAVY’S ORIGINAL PROPOSAL FOR 867I MAPPING IS AT ENCLOSURE 2. Strikethrough and 

gray highlight in the enclosure show deviations from Navy’s original proposed mapping. 

5. PDC 351A COMMENTS. Navy provided the following comments: 

a. During staffing Navy commented they also require the ‘Previous Movement Document Number’ in 

DS 867I. Navy indicates that this number is required in addition to the three reference numbers already 

provided in the issue transaction: 1) Document Number, 2) CAVRCDN, and 3) CAV Contractor’s 

Reference Number. Repair Cycle Document is therefore added at 2/REF01/30 qualifier ‘RV’. 

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

 c. 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 issue transaction contains data requirements not accommodated by the existing DS 

867I Issue. Navy submitted complimentary changes to accommodate CAV II data requirements in the 

following transaction sets: DS 527D/527R (ADC 342), DS 947I Inventory Adjustment (ADC 343) and DS 

856S Shipment Status (PDC 350). 

7. ADVANTAGES AND DISADVANTAGES: 
4 of 4 

ADC 341 

Attachment 

 a. Advantages: Clarifies CAV data requirements for DS 867I Issue. 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 D7X 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 Code D7X is not valid. 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.

8. IMPACT: 

a. Publication(s): DS 867I. 

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: 

Segment Data Element ID Code/Name CAV Use 

2/REF01/30 128 TF Transfer Number Advanced Traceability and Control (ATAC) 

Indicator 

2/REF01/30 128 RV Receiving Number Previous Movement Document Number

2/REF04-01 128 W8 Suffix Previous Movement Document Number Suffix 

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

867I Data Element ID Code/Name Interim Use Only Comment 

2/PTD01/10 SM Sample This code 

is used as a “Nonbalance Effecting CAV 

Detail Flag"

Code ‘SM’ authorized for interim 

use by Navy as a flag to identify 

CAV non-balance affecting 

‘detail’ issue transactions. 

Authorized for Navy 

temporary use only. 

PTD01 Code ‘SM’ will be 

deleted at a future date. 

Enclosures: 

1) DS 867I Change Table 

2) Navy Mapping Proposal
1 of 5 

ADC 341 

Encl 1 – DS 867I Changes 

ENCLOSURE 1 TO ADC 341 

Item # Location CHANGE TABLE for 

DS 867I ISSUE 

Reason 

1. DLMS 

Introductory 

Note 

Add ADC to Introductory note 7

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

To identify DLMS changes included 

in the DS 

2. 2/DTM01/20 Add qualifier ‘938-Order’ with DLMS note:

938 Order 

DLMS Note: Use in commercial asset 

visibility (CAV) to indicate an order date. 

Documents CAV II use of the 

Order Date in Issue transactions. 

3. 2/PTD01/10 Add qualifier ‘SM’ with DLMS note: 

SM Sample 

DLMS Note: Used for CAV Detail Record. 

Authorized for INTERIM USE by Navy as a 

flag to identify CAV non-balance affecting 

‘detail’ issue transactions. The balance 

affecting CAV “summary” issue transaction 

must use the appropriate standard product 

transfer type code. Code ‘SM’ is nonstandard 

and is authorized for intra-Navy interim use 

pending implementation of “detail” 

information within a standard DLMS issue 

transaction 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. PTD01 code ‘SM’ 

will be deleted from 867I at that time. Refer 

to ADC 341.

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 receipt 

processing for the CAV detail 

information, at which time this code 

will be eliminated from DS 867I. 

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 nonbalance affecting detail transaction, and 

provides for nonstandard Navy use of 

the MILSTRAP D7X transaction for a 

“summary” issue balance affecting 

transaction. Navy CAV process for use 

of D7X deviates from established DOD 

policy and procedure. DI Code D7X 

does not exist in MILSTRAP which is 

the authoritative source for D-series DI 

Codes. 

Navy ERP to negotiate with DAASC on 

whether DAASC can flip, or will Navy 

ERP perform the flip. 
2 of 5 

ADC 341 

Encl 1 – DS 867I Changes 

Item # Location CHANGE TABLE for 

DS 867I ISSUE 

Reason 

4. 2/REF01/30 Revise the data element level note and add 

qualifier ‘NIN’ with DLMS note: 

Reference Identification Qualifier 

DLMS Note: 1. Must use National Stock 

Number (NSN), when known, to identify the 

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

NIN National Item Identification Number

DLMS Notes: 1. Use only for CAV when the 

NSN (FSC plus NIIN) is not available. Refer 

to ADC 341.

2. Qualifier NIN 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 867I. 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/REF01/30 Revise DLMS Note for qualifier ‘TN’:

TN Transaction Reference Number 

DLMS Note: Must use to identify the 

document number from the source document. 

DLMSO Administrative update to 

pick up document number language 

used in MILSTRAP DI Code D7_ 

issue transaction, record position 30-

43, for clarification 
3 of 5 

ADC 341 

Encl 1 – DS 867I Changes 

Item # Location CHANGE TABLE for 

DS 867I ISSUE 

Reason 

6. 2/REF01/30 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). 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. 

CAV requirement. 

NAVY ERP COMMENT: For the Issue 

supplemental Information transaction 

being sent to ERP from WEBCAV 

contractors there is a requirement for this 

transaction to contain the Previous 

Movement Document Number, the 

RCDN number created by WEBCAV 

when the receipt document number is 

posted, and the Shipment Document 

Number. 

DLMSO STAFFING NOTE FOR 

NAVY: Note that the transaction # (aka 

document #) in the issue transaction 

(REF01 code TN) is the document 

number from the source transaction per 

MILSTRAP, Appendix 3.3, Issue (DI 

Code D7_), rp 30-43. 

7. 2/REF01/30 Add qualifier ‘RV’ with DLMS note:

RV Receiving Number 

DLMS Note: Used in CAV to identify a 

Previous Movement Document Number. Refer 

to ADC 341.

CAV requirement. 

Navy identifies the Previous Movement 

Document Number’ as the “document 

number that the material was moved to 

the repair facility on prior to starting 

repair.” Navy uses it to close the loop 

from sending the material to be repaired 

to getting it back. 

8. 2/REF01/30 Revise DLMS Note for existing qualifier ‘X9’:

X9 Internal Control Number 

Delete: 1. Use in CAV transactions to identify 

a unique contractor reference number. 2 

DLMS enhancement. See introductory DLMS 

note 5a.

Replace with: 

DLMS Note: Used in CAV to identify a 

contractor’s reference number. 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 341. 

Revises note for Navy CAV-unique 

‘Contractor’s Reference Number’ for 

consistency with DLMS note for this 

data requirement in DS 856S, 527R, 

and 947I (see PDC 350, ADC 342 and 

ADC 343 respectively). 
4 of 5 

ADC 341 

Encl 1 – DS 867I Changes 

Item # Location CHANGE TABLE for 

DS 867I ISSUE 

Reason 

9. 2/REF01/30 Add qualifier ‘TF’ with DLMS note:

TF Transfer Number 

DLMS note: CAV uses to identify the 

Advanced Traceability and Control (ATAC) 

Indicator. CAV cites ATAC Indicator ‘1’ for 

ATAC Reporter which indicates that this 

shipment is to the ATAC hub for transshipment. DLMS migration enhancement 

authorized for CAV use only. See introductory 

DLMS note 5e. Refer to ADC 341. 

Supports Navy requirement for an 

“Advanced Traceability and Control

(ATAC) Indicator”: 

NAVSISA COMMENT: 

The CAV ATAC indicator is used by 

the NAVICPs to eliminate the 

following: (1) wait time for GBL from 

DCMA, (2) proof of shipment entry to 

CAV, and (3) Supply Discrepancy 

Reports (SDRS) to the CAV site for 

Proof of Shipment. The Government 

pays for the transportation. 

Navy identified the following values: 

 1 = ATAC Reporter 

 BLANK = NON-ATAC Reporter, 

hence in DLMS 867I, the absence of an 

ATAC indicator data element means 

NON-ATAC Reporter.

NAVY PUBLICATION sources for 

ATAC Indicator=CAV II 

Documentation: Operation Concept 

Description (OCD), CAV II, Version 7.3; 

Interface Design Description (IDD), CAV 

II, Version 7.3; Software Design 

Description (SDD), CAV II , Version 7.3; 

Data Base Design Description (DBDD), 

CAV II, Version 7.3. 

10. 2/REF04-

01/30 

For existing qualifier ‘W8’, revise current DLMS 

note and add DLMS note 2:

W8 Suffix 

DLMS notes: 

1. Use with REF01 code TN to identify the issue

document number suffix. 

2. Use with REF01 code RV to identify the

Previous Movement Document Number Suffix.

DLMS Note: 2. CAV uses with REF01 code 

Q9. Refer to PDC 351A.

Per CAV requirement. 

Added note for RV and deleted note to 

use with Q9. Navy clarified that their 

intent in their proposal was that suffix 

code would be used with the ‘previous 

movement document number’ rather 

than with the RCDN.

11. 2/MEA/160 OPEN MEA segment for optional use and add 

DLMS segment level note:

DLMS Note: 1. DLMS enhancement. See 

introductory DLMS note 5a. 

2. Authorized DLMS migration enhancement for 

CAV use only. See introductory DLMS note 5e. 

Refer to ADC 341. 

Documents CAV II requirement for 

MEA segment. 
5 of 5 

ADC 341 

Encl 1 – DS 867I Changes 

Item # Location CHANGE TABLE for 

DS 867I ISSUE 

Reason 

12. 2/MEA01/160 Open MEA01 and add codes ‘SD’ and ‘WT’ and 

Federal and DLMS Notes:

Add Federal Note: Use any code. 

Add DLMS note: For DLMS use, only the 

following codes are authorized. 

SD Shipped Dimensions 

DLMS Note: CAV uses to identify the Cube 

Value which represents the dimension of the item 

issued. Expressed as 10 numeric, 6v4 (6 

positions to the left of the decimal and 4 positions 

to the right. Do not enter leading zeros, nor a 

decimal point. 

WT Weights 

DLMS Note: CAV uses to identify the gross size 

or weight of the tem issued. Expressed as 9 

numeric, 7v2 (7 positions to the left of the 

decimal and 2 positions to the right. Do not 

enter leading zeros, nor a decimal point. 

Documents CAV II requirements for 

including the dimension and weight of a 

shipped item in an Issue transaction. 

13. 2/MEA02/160 Open MEA02 and add qualifiers ‘U’ and ‘UCB’ 

and DLMS notes:

Add Federal Note: Use any code. 

Add DLMS note: For DLMS use, only the 

following codes are authorized. 

U Weight per Unit 

DLMS Note: Use with MEA01 code WT. 

UCB Cube 

DLMS Note: Use with MEA01 code SD. 

Documents CAV II requirements for 

including the dimension and weight of a 

shipped item in an Issue transaction. 

14. 2/MEA03/160 Open MEA03. Supports CAV II requirement. 
1 of 4 

ADC 341 

Encl 2 – Navy’s Proposed Mapping

 

ENCLOSURE 2 to ADC 341 

Strikethrough and gray highlights identify deviations from original Navy CAV 527D/527R 

proposal.

TRANSACTION SET (867I) 

DATA ELEMENT CHARS A/N 

1. Assigned Document Identifier 2 A/N 

a. DIC(s): D7 

b. EDI (ASC X12) Segment(s): 2/PTD/010 

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

 2/PTD/010 Mandatory Product Transfer Type Code 

 01 2 position Enter Product Transfer Type Code (Assigned Doc Identifier) 

Note: Product Transfer Type Codes are assigned based on the 

 Doc ID as follows: 

 Doc ID Product Transfer Type Code

 D7A SS 

 D7J BI 

 D7K BJ 

 D7M BL 

 D7X SU D7X is invalid DI Code 

 ----- SM – Sample’ Used for Detail transactions. May 

require flipping when interfacing with legacy Navy CAV

Example: PTD*SU SM

d. System: CAV II 

e. Definition: Assigned Document Identifier represents the type of D7 Doc Id or transaction set; 

D7X (SU-SummaryTransaction). Valid PTD01 Product Transfer Type Codes = Summary 

transactions 

 New interim PTD01 Code ‘SM-Sample’ = Detail transactions 

DATA ELEMENT CHARS A/N 

2. Award/Order Date 8 N 

a. DIC(s): D7 

b. EDI (ASC X12) Segment(s): 2/DTM/020

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

2/DTM/020 Optional 

 01 103 938 Date Qualifier (Award Date) (Order) 

 02 CCYYMMDD Enter Award/Order Date

Example: DTM*938*20070801 d. System: CAV II 

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

ADC 341 

Encl 2 – Navy’s Proposed Mapping

 

TRANSACTION SET (867I) CONT’D 

DATA ELEMENT CHARS A/N 

3. Source Document Number 14 A/N 

a. DIC(s): D7 

b. EDI (ASC X12) Segment(s): 2/REF/030

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

 2/REF/030 Mandatory 

 01 RV Reference Identification Qualifier (Receiving Number) 

 02 14 position Enter Source Previous Movement Document Number 

 Optional 

04 C040 Composite 

 REF04-01 W8 Reference Identification Qualifier (Suffix) 

 REF04-02 1 position Enter Previous Movement Document Number Suffix Code 

Note: Added Navy-ERP requirement based on PM73 Meeting (10/15/08). 

Example: REF*RV*V2302772901701**W8:A 

 

d. System: CAV II 

e. Definition: ‘Source Document Number’ describes the document on the paperwork that accompanied 

the repairable when it was received at the contractor’s site. The repairable has an identity before it arrives at the 

contractor’s site. This is the source document number.

e. Navy Definition: ‘Previous Movement Document Number’ describes the document on the paperwork that 

accompanied the repairable when it was received at the contractor’s site. The repairable has an identity before it 

arrives at the contractor’s site. This is the previous movement source document number. Navy identifies this as 

the document number that the material was moved to the repair facility on prior to starting repair. Navy uses this 

to close the loop from sending the material to be repaired to getting it back. 

DATA ELEMENT CHARS A/N 

4. Shipping Weight Value 9 N 

a. DIC(s): D7 

b. EDI (ASC X12) Segment(s): 2/MEA/160 

c. Request the following Segment be added: 

2/MEA/160 Optional 

01 WT Weight Qualifier 

02 U Weight Per Unit 

03 9 position Enter Shipping Weight Value

Note: Weight format: 9 numeric, 7v2: 

 7 positions to the left of the decimal and 2 positions to the right. 

 Do not enter leading zeros, nor a decimal point. 

Example: MEA*WT*U*11300 

d. System: CAV II 

e. Definition(s): Shipping Weight Value represents the gross size or weight of a shipped item. 
3 of 4 

ADC 341 

Encl 2 – Navy’s Proposed Mapping

 

TRANSACTION SET (867I) CONT’D 

DATA ELEMENT CHARS A/N 

5. Shipping Cube Value 10 N 

a. DIC(s): D7 

b. EDI (ASC X12) Segment(s): 2/MEA/160 

c. Request the following Segment be added: 

2/MEA/160 Optional 

 01 SD Shipping Dimension 

 02 UCB Cube 

 03 10 position Enter Cube Value 

Note: Cube format: 10 numeric, 6v4: 

 6 positions to the left of the decimal and 4 positions to the right. 

 Do not enter leading zeros, nor a decimal point. 

Example: MEA*SD*UCB*170000 

d. System: CAV II 

e. Definition(s): Shipping Cube Value represents the dimension of a shipped item. 

DATA ELEMENT CHARS A/N 

NAVY WITHDREW THIS REQUIREMENT FOR 867I AS NOTED IN ADC: 

6. Shipment Indicator 1 A/N

a. DIC(s): D7 

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

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

 2/LQ/270 Optional

01 96 Code List Qualifier Code (Shipment Release Code)

02 1 position Enter Shipment Indicator

Note: Shipping Options Description

 

1 ‘A’ Condition Material

2 ‘J’ to ‘F’ Condition Material

3 ‘J’ to ‘A’ Condition Material

4 Non-worked ‘F’ Condition Material

5 ‘L’ to ‘F’ Condition Material 

 Blank ‘H’ Condition Material

Example: LQ*96*4

d. System: CAV II

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

ADC 341 

Encl 2 – Navy’s Proposed Mapping

 

TRANSACTION SET (867I) CONT’D 

DATA ELEMENT CHARS A/N 

7. ATAC Indicator 1 A/N 

a. DIC(s): D7 

b. EDI (ASC X12) Segment(s): 2/LQ/270 2/REF01/30 

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

2/LQ/270 2/REF01/30 Optional 

 01 BD TF Code List Qualifier Code (Transportation Priority Code) Transfer Number

 02 1 position Enter ATAC Implementation Indicator 

Example: LQ*BD*Y REF*TF*1 

d. System: CAV II 

e. Definition: ‘ATAC Indicator’ identifies if this shipment is to the ATAC hub for trans-shipment. 

Note: The possible ATAC Indicator entries include: 

 1 – ATAC Reporter 

 Blank – Non ATAC Reporter [In DLMS 867I, the 

absence of an ATAC indicator data 

element means NON-ATAC Reporter.]