|
|
846F |
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 |
Use for 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/2 |
|
|
846F |
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 |
Use for integrated material management. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
1/1 |
|
|
846F |
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 |
Use for special inventory reporting. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
1/1 |
|
|
846F |
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 |
This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
2/2 |
|
|
846I |
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. Future Streamlined data; see introductory DLMS note 4c. 2. The DLSS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. |
3/3 |
|
|
846I |
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 supplemental address/data. 2. During the DLSS/DLMS transition, this field will be used to perpetuate/populate the DLSS Supplemental Address (SUPAAD) field. During this time, field size is restricted to 6 positions; see introductory DLMS note 4d. 3. Expanded use of this field for supplemental data without size restriction is a DLMS enhancement; see introductory DLMS note 4a. 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 SUPAAD will be reflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 4c. |
6/6 |
|
|
846I |
LQ01 |
AJ |
Utilization Code |
Use to identify a specialized purpose of the transaction |
1. Under DLSS, this is the first position of the document serial number. 2. DLMS enhancement; see introductory DLMS note 4a. |
1/1 |
|
|
846I |
LQ01 |
EA |
Asset Status or Transaction Reporting Code |
Use to identify the type of asset status report required |
Use to identify the type of asset status report required. |
1/1 |
|
|
846I |
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) |
1. Use to identify the Materiel Management Aggregation Code (MMAC) for NSNs to be managed by a specific manager (i.e., system, program, aggregation, selected FSC, technology group). 2. This is an AirForce-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate without action. 3. The code source is identified as the Air Force Manual (AFMAN) 23-110, Volumes 1 and 2. |
2/2 |
|
|
846I |
LQ01 |
SC |
Source |
Use to identify a method to obtain the materiel consumed as Government Furnished Material (GFM) |
For Intra-Army use to indicate the Supply Source Method Code (BIA02=62/DIC BZE functionality) Refer to ADC 431. Available codes are: P–Requisitioned through MCA. J–Obtained by cannibalization of Government materiel. |
1/1 |
|
|
846I |
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 |
Use for 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/2 |
|
|
846I |
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 |
Use for integrated material management. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
1/1 |
|
|
846I |
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 |
Use for special inventory reporting. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
1/1 |
|
|
846I |
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 |
This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
2/2 |
|
|
846I |
LQ01 |
78 |
Project Code |
Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes |
1. DLMS enhancement. See introductory DLMS note 4a. 2. For intra-Army use only, Army uses to identify the project code associated with Logistics Reassignment actions and for reporting from Single Stock Fund sites to the National level. (Army DIC BSS, rp 55-57.) Refer to ADC 308. 3. For intra-Army use to identify the Project Code associated with Asset Status Reports. Associated with Army use of MILSTRAP legacy DZA, rp 55-57. Refer to ADC 458. |
3/3 |
|
|
846I |
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 |
|
1/1 |
|
|
846I |
LQ01 |
87 |
Subsistence Type of Pack Code |
Use to indicate the degree of protection to be provided subsistence items |
1. Use only for subsistence items. 2. DLMS enhancement. See introductory DLMS note 4a. |
1/1 |
|
|
846I |
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 |
|
1/1 |
|
|
846I |
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 |
|
1/1 |
|
|
846I |
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 supplemental address/data. 2. During the DLSS/DLMS transition, this field will be used to perpetuate/populate the DLSS Supplemental Address (SUPAAD) field. During this time, field size is restricted to 6 positions; see introductory DLMS note 4d. 3. Expanded use of this field for supplemental data without size restriction is a DLMS enhancement; see introductory DLMS note 4a. 4. Under full DLMS, the requirement to pass activity address information within the supplemental data field will be streamlined. Activity address data previousl y contained in the SUPAAD will be reflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 4c. |
6/6 |
|
|
846I |
LQ01 |
AJ |
Utilization Code |
Use to identify a specialized purpose of the transaction |
1. Under DLSS, this is the first position of the document serial number. 2. DLMS enhancement; see introductory DLMS note 4a. |
1/1 |
|
|
846I |
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) |
1. Use to identify the Materiel Management Aggregation Code (MMAC) for NSNs to be managed by a specific manager (i.e., system, program, aggregation, selected FSC, technology group). 2. This is an AirForce-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate without action. 3. The code source is identified as the Air Force Manual (AFMAN) 23-110, Volumes 1 and 2. |
2/2 |
|
|
846I |
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 |
Use for 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/2 |
|
|
846I |
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 |
Use for integrated material management. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
1/1 |
|
|
846I |
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 |
Use for special inventory reporting. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
1/1 |
|
|
846I |
LQ01 |
SLC |
Stockage List Code |
Use to review requirements and identify stocking criteria for items on the Authorized Stockage List (ASL) |
1. For intra-Army use only. See introductory DLMS note 4f. Use of this data is meaningful to Army only and equates to intra-Army DIC BSS, rp 78, and MILSTRAP legacy DZA, rp 78. The code source for Stockage List Code is Army Regulation 710-2, Supply Policy Below the National Level. Refer to ADC 308 and ADC 458. 2. Approved for use in X12 version 6020. |
1/1 |
|
|
846I |
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 |
Use to identify the Special Material Identification Code (SMIC) for an end item. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
2/2 |
|
|
846M |
LQ01 |
FG |
Source Maintenance and Recoverability Code |
Use to indicate whether or not the item has reparable characteristics and whether or not the item has been subjected to reparable characteristics review |
|
1/1 |
|
|
846P |
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. Future Streamlined data; see introductory DLMS note 4c. 2. The DLSS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. |
3/3 |
|
|
846P |
LQ01 |
78 |
Project Code |
Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes |
1. Enter the project code in LQ02 if stocks are segregated and maintained by project codes. 2. Future Streamlined data; see introductory DLMS note 4c. |
3/3 |
|
|
846P |
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 |
|
1/1 |
|
|
846P |
LQ01 |
84 |
Management Code |
Provides supplemental data not indicated through the transaction coding structure |
Use in physical inventory request, physical inventory report/response, to provide supplemental management information. |
1/1 |
|
|
846P |
LQ01 |
87 |
Subsistence Type of Pack Code |
Use to indicate the degree of protection to be provided subsistence items |
Use in physical inventory request and physical inventory response transactions. |
1/1 |
|
|
846P |
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 |
1. Enter the purpose code in LQ02 if stocks are segregated and maintained by purpose codes. |
1/1 |
|
|
846P |
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 |
1. Enter the ownership code in LQ02 if stocks are segregated and maintained by ownership codes. |
1/1 |
|
|
846P |
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 supplemental address/data. 2. Future streamlined data; see introductory DLMS note 4c. |
6/6 |
|
|
846P |
LQ01 |
AJ |
Utilization Code |
Use to identify a specialized purpose of the transaction |
1. Under DLSS, this is the first position of the document serial number. 2. DLMS enhancement; see introductory DLMS note 4a. |
1/1 |
|
|
846P |
LQ01 |
AK |
Distribution Code |
Use to identify the activity that will receive a supply status and other management data |
1. Enter the distribution code in LQ02 if stocks are segregated and maintained by distribution codes. 2. Future Streamlined data; see introductory DLMS note 4c. |
1/3 |
|
|
846P |
LQ01 |
DF |
Media and Status Code |
Identifies the desired status recipient(s) and the type of status to be provided |
The DLMS provides the capability to carry additional status recipients beyond those identified by the DLSS. The Media and Status Code and the Distribution Code will be retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS environment. Additional status recipients identified here cannot be passed to DLSS users. |
1/1 |
|
|
846P |
LQ01 |
FC |
Type Physical Inventory or Transaction History Code |
|
1. For Physical Inventory Request Transaction, Response to Physical Inventory Request Transaction, and Transaction History Request (1/BIA02/20 Report Type Codes TC, DD, and TF respectively), cite appropriate code. 2. For Response to Transaction History Request (No History Available) (BIA02 Report Type Code AD), code value 8 or 9 is required; in addition, a second iteration of qualifier FC is used to perpetuate the code which appeared on the Transaction History Request or cite code W or Y (DLA only) for a utomatic submission of transaction history. Refer to ADC 198 and ADC 393. |
1/1 |
|
|
846P |
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) |
1. Use to identify the Materiel Management Aggregation Code (MMAC) for NSNs to be managed by a specific manager (i.e., system, program, aggregation, selected FSC, technology group). 2. This is an AirForce-unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate without action. 3. The code source is identified as the Air Force Manual (AFMAN) 23-110, Volumes 1 and 2. |
2/2 |
|
|
846P |
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 |
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/2 |
|
|
846P |
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 |
Use for integrated material management. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
1/1 |
|
|
846P |
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 |
Use for special inventory reporting. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
1/1 |
|
|
846P |
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 |
Use for an end item. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
2/2 |
|
|
846R |
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. Future Streamlined data; see introductory DLMS note 4c. 2. The DLSS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 3. In a mixed DLSS-DLMS environment, when including BG1/BG2 data for Inter-Service Ammunition interface, must use 2 iterations of LQ to provide DIC DZH as well as either DIC BG1 or BG2 as applicable, to alert DAAS of BG1/ BG2 requirement for non-DLMS Ammunition system trading partners: Naval Operational L ogistics 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 Complex Combat Ammunition System (CAS). |
3/3 |
|
|
846R |
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 supplemental address/data. 2. Future streamlined data; see introductory DLMS note 4c. |
6/6 |
|
|
846R |
LQ01 |
AJ |
Utilization Code |
Use to identify a specialized purpose of the transaction |
1. Under DLSS, this is the first position of the document serial number. 2. DLMS enhancement; see introductory DLMS note 4a. |
1/1 |
|
|
846R |
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 supplemental address/data. 2. Future streamlined data; see introductory DLMS note 4c. |
6/6 |
|
|
846R |
LQ01 |
AJ |
Utilization Code |
Use to identify a specialized purpose of the transaction |
1. Under DLSS, this is the first position of the document serial number. 2. DLMS enhancement; see introductory DLMS note 4a. |
1/1 |