|
|
867I |
DD03 |
W2 |
Weapon System Number |
|
|
|
|
867I |
DD06 |
71 |
Service and Agency Code |
|
|
|
|
867I |
DD10 |
98 |
Reason for Requisitioning Code |
|
|
|
|
867I |
LM01 |
DF |
Department of Defense (DoD) |
Executive department of the U.S. federal government charged with coordinating and supervising the U.S. Armed Forces and related functions and agencies. |
|
|
|
867I |
LQ01 |
0 |
Document Identification Code |
Identifies transaction specific operation to which they apply and indicates the intended purpose and use of the transaction data |
1. The DLS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. In a mixed DLS-DLMS environment, for Inter-Service Ammunition interface, when including BG1/BG2 data, must use 2 iterations of LQ to provide DIC D7_ as well as either DIC BG1 or BG2 as applicable, to alert DAS of BG1/ BG2 requirement for non-DLMS Ammunition system trading partners: Naval Operational Logistics Support Center (NOLSC) Ordnance Information System-Wholesale (OIS-W), Program Manager for Ammunition, Marine Corps Systems Command (MARCORSYSCOM) Ordnance Information System-Marine Corps (OIS-M),and Warner Robins Air Logistics Center Combat Ammunition System (CAS). 3. Future streamlined data; see introductory DLMS note 5c. |
|
|
867I |
LQ01 |
Z |
Cancelation Reason |
|
1. Use for the Reason for Reversal Code. 2. Navy uses the Reason for Reversal Code for Navy issue reversal codes B and S in support of legacy requirements. Refer to ADC 259. 3. By DLMS enhancement, DLA storage activities must cite the Reason for Reversal Code on all issue reversals associated with a validated SDR. Refer to ADC 160. 4. A data maintenance action was approved in version 5050. The approved code/name is “RC - Reason for Reversal Code”. |
|
|
867I |
LQ01 |
78 |
Project Code |
Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes |
1. Use for all issue transactions to identify special programs, exercises, projects, operations, and other purposes; except issues to DLA Disposition Services. 2. For DoD SLOA/Accounting Classification compliance the Project Code may be repeated as a Project Identifier (FA201 Qualifier 90). Refer to ADC 1043. , , . |
|
|
867I |
LQ01 |
79 |
Priority Designator Code |
A code to communicate the relative importance to the requisitioner's mission based upon its force activity designator (FAD) and urgency of need designator (UND) |
Use for all issue transactions except issues to DRMO to identify the supply priority of the transaction. |
|
|
867I |
LQ01 |
80 |
Advice Code |
Use to transmit instructions considered by the creators of requisitions to be essential to the desired supply action |
Use for all issue transactions except issues to DRMO to convey information which was significant to processing the requirement. |
|
|
867I |
LQ01 |
83 |
Supply Condition Code |
Classifies materiel in terms of readiness for issue and use or to identify action underway to change the status of materiel |
|
|
|
867I |
LQ01 |
84 |
Management Code |
|
|
|
|
867I |
LQ01 |
87 |
Subsistence Type of Pack Code |
Use to indicate the degree of protection to be provided subsistence items |
|
|
|
867I |
LQ01 |
88 |
Disposal Authority Code |
|
1. Use only for disposal issue transactions to identify that items being transferred to disposal are authorized for transfer by the proper authority. 2. Authorized DLMS enhancement; see introductory DLMS note 5e. on IC cover page. |
|
|
867I |
LQ01 |
90 |
Precious Metals Indicator Code |
|
1. Use only for disposal issue transactions. 2. Authorized DLMS enhancement; see introductory DLMS note 5e. on IC cover page. |
|
|
867I |
LQ01 |
91 |
Automated Data Processing Equipment Identification Code |
|
1. Use only for disposal issue transactions. 2. Authorized DLMS enhancement; see introductory DLMS note 5e. on IC cover page. |
|
|
867I |
LQ01 |
92 |
Reason for Disposal Code |
|
1. Use only for disposal issue transactions. 2. Authorized DLMS enhancement; see introductory DLMS note 5e. on IC cover page. |
|
|
867I |
LQ01 |
97 |
Ultimate Recipient Code |
|
1. Use to identify the buyer of DoD materiel to allow full payment for materiel supplied to a non-DoD customer. 2. DLMS enhancement; see introductory DLMS note 5a. |
|
|
867I |
LQ01 |
98 |
Reason for Requisitioning Code |
|
DLMS enhancement; see introductory DLMS note 5a. |
|
|
867I |
LQ01 |
99 |
Purpose Code |
Provides the owner of materiel with a means of identifying the purpose or reason for which an inventory balance is reserved |
|
|
|
867I |
LQ01 |
A1 |
Ownership Code |
Provides a means of segmenting inventory balances, accounted for in inventory control records of a Military Service/DLA, but which are owned by others |
When used for inter-Service ammunition-related ownership transfer with no physical movement of materiel, use to identify the new/gaining (to) ownership code. Refer to ADC 1020. |
|
|
867I |
LQ01 |
A7 |
Record Control Number |
|
Commercial Asset Visibility (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 trans-shipment. Authorized for CAV use. See PDC 351. |
|
|
867I |
LQ01 |
A9 |
Supplemental Data |
A distinctive identification of specific units, activities and organizations within the Department of Defense (DoD), commercial activities which enter into materiel and service contracts with the DoD and activities of other Federal agencies which maintain logistics support arrangements with the DoD |
1. Use to identify supplementary address/supplemental data. 2. During the DLS/DLMS transition, this field will be used to perpetuate/populate the DLS , , Supplementary Address (SUPAD) field. During this time, field size is restricted to 6 positions; see introductory DLMS note 3d. 3. Expanded use of this field for supplemental data without size restriction is a DLMS enhancement; see introductory DLMS note 3a. 4. Under full DLMS, the requirement to pass activity address information within the supplemental data field will be streamlined. Activity address data previously contained in the SUPAD will be reflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 5c. 5. During DLS/DLMS transition, use on issue transactions for inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel and no billing. Cite Signal Code M in conjunction with the supplemental data field constructed as follows: Service/Agency Code Y followed by the old (from) ownership code, the RIC to which ownership is transferred, and the new/gaining (to) ownership code. Refer to ADC 1020. |
|
|
867I |
LQ01 |
AK |
Distribution Code |
|
Future streamlined data; see introductory DLMS note 5c. |
|
|
867I |
LQ01 |
DE |
Signal Code |
Use to indicate the bill-to and ship-to DoDAAC (Department of Defense Activity Address Code) for an item |
Future streamlined data; see introductory DLMS note 5c. |
|
|
867I |
LQ01 |
DF |
Media and Status Code |
Identifies the desired status recipient(s) and the type of status to be provided |
Future streamlined data; see introductory DLMS note 5c. |
|
|
867I |
LQ01 |
FC |
Type Physical Inventory or Transaction History Code |
|
1. Use only with 1/BPT07/20 Action Code W1. 2. DLMS enhancement. See introductory DLMS note 5a. |
|
|
867I |
LQ01 |
FD |
Demilitarization Code |
|
1. Use only for DRMO issue transactions. 2. DLMS enhancement; see introductory DLMS note 5a. |
|
|
867I |
LQ01 |
GQ |
Group Qualifier Code |
Use to identify the Materiel Management Aggregation Code (MMAC) for National Stock Number (NSN) to be managed by a specific manager (i.e., system, program, aggregation, selected FSC, technology group) |
Use to identify the MAC for NSNs to be managed by a specific manager (i.e., system, program, aggregation, selected FSC, technology group). This is an Air Force-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate without action. A - data maintenance action was approved in version 5010. The approved code/name is “MAC-Material Management Aggregation code”. The code source is identified as the Air Force Manual (AFMAN) 23-10, Volumes 1 and 2. |
|
|
867I |
LQ01 |
RD |
Property Ownership Type Code |
|
Use only for inter-Service ammunition-related ownership transfer with no physical movement of materiel. Use to identify the old (from) ownership code. DLMS enhancement. Refer to ADC 1020. |
|
|
867I |
LQ01 |
RT |
Request Type |
|
Use for the Navy Issue on Request Code. DLMS enhancement authorized for use by Navy and DLA Distribution Standard System. |
|
|
867I |
LQ01 |
121 |
Ordnance Expenditure Reason |
|
Code 121 provides details about the reason for the ordnance expenditure. |
|
|
867I |
LQ01 |
COG |
Cognizance Symbol |
Use for internal Navy management purposes to classify items by technical program, type of fund, and to indicate the cognizant Inventory Control Point (ICP) and technically responsible command |
1. Use to identify the material cognizance symbol (COG) of the end item. Indicate NSL for non-stock , , numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. 2. DLMS enhancement. |
|
|
867I |
LQ01 |
IMC |
Item Management Code |
Use to indicate whether an item of supply shall be subject to integrated management or shall be retained by the individual military service or other DoD Component for their management |
1. Use for integrated material management. Indicate NSL for non-stock numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. 2. DLMS enhancement. |
|
|
867I |
LQ01 |
MCC |
Material Control Code |
Use to denote the expendability, repairability, recoverability, and cost category employed in the management of an item of supply within the Navy |
1. Use for special inventory reporting. Indicate NSL for non-stock numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. 2. DLMS enhancement. |
|
|
867I |
LQ01 |
SMI |
Special Material Identification Code |
Use to categorize material on the basis of requirements for source or quality control; technical design or configuration control; procurement, stocking, and issue control; special receipt, inspection, testing, storage, or handling |
1. Use for an end item. Indicate NSL for non-stock numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. 2. DLMS enhancement. |
|
|
867I |
LQ01 |
SRC |
Serialized Report Type Codes |
|
1. Use to cite the Air Force Serialized Report Code. The Air Force uses this code to indicate that an item requires serialized management. Applicable to property identified by national stock number (NSN) or Air Force-assigned local stock number (LSN) in accordance with CICP contract requirements. Authorized for Air Force GFP-A. Refer to ADC 1230A. 2. Approved for use in X12 version 8010. The following values will be conveyed in 2/LQ02/130:. AA - Small Arms C - Communications Security (COMSEC) |
|
|
867I |
LQ01 |
DD |
Reserved |
|
R - Nuclear Weapons Related Material (NWRM) COMSEC |
|
|
867I |
LQ01 |
WW |
NWRM |
|
|
|
|
867I |
LQ01 |
T05 |
Inspection Parameters |
|
1. Use to identify the Quality Inspection Code indicating the quality level of inspection which the item must be procured and inspected to. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. |
|
|
867I |
REF01 |
BT |
Batch Number |
A quantity of material all of which was manufactured under identical conditions and assigned an identifying batch number |
Use to identify the batch, lot, or other number identifying the production run. The batch/lot number may not exceed 20 characters in accordance with IUID policy. |
|
|
867I |
REF01 |
SE |
Serial Number |
A value assigned for identification of an item |
Place serial number value in REF02. May not exceed 30 characters in accordance with IUID policy. |
|
|
867I |
REF01 |
U3 |
Unique Supplier Identification Number (USIN) |
|
1. Use to identify the UI. Place UI value in REF03. The UI may not exceed 50 characters in accordance with IUID Policy. 2. Data maintenance action was approved in version 5020. The approved code/name is "UI - Department of Defense Unique Item Identifier. |
|
|
867I |
REF04-01 |
0N |
Attached To |
|
Authorized DLMS enhancement for Inter-Service Ammunition use. Use when REF01=BT to identify the Lot Size for the lot number identified in REF02. DLMS Component unique enhancement (DIC BG1/BG2, rp 25-29). See introductory DLMS note 5f. Refer to ADC 261 and ADC 45. |
|
|
867I |
DTM01 |
36 |
Expiration |
|
Authorized DLMS enhancement for Inter-Service Ammunition use to identify the expiration date of the reported item. DLMS Component unique enhancement (DIC BG1/BG2, rp 9-1). See introductory note 5f. Refer to ADC 261 and ADC 45. |
|
|
867I |
DTM01 |
94 |
Manufacture |
|
1. Use to identify the date of manufacture for the materiel identified 2. DLMS enhancement; see introductory DLMS note 5a. |
|
|
867I |
DTM01 |
302 |
Maintenance |
|
Use to identify the maintenance due date (the date that maintenance is due on the item). Authorized DLMS enhancement for Inter-Service Ammunition use. DLMS Component unique enhancement (DIC BG1/BG2, rp 9-1). See introductory note 5f. Refer to ADC 261 and ADC 45. |
|
|
867I |
DTM01 |
512 |
Warranty Expiration |
|
1. Use to identify the Warranty expiration date associated with the materiel reported. 2. DLMS enhancement; see introductory DLMS note 5a. |
|
|
867I |
DTM05 |
D8 |
Date Expressed in Format CCYYMMDD |
|
|
|
|
867I |
N101 |
MF |
Manufacturer of Goods |
Use to identify the manufacturer of the identified item |
DLMS enhancement; see introductory DLMS note 5a. |
|
|
867I |
N103 |
33 |
Commercial and Government Entity (CAGE) |
|
DLMS enhancement; see introductory DLMS note 5a. |