|
|
869F |
PER06 |
|
|
|
|
|
|
869F |
PER07 |
AU |
Defense Switched Network |
Use to provide the worldwide non-secure voice, secure voice, data, facsimile, and video teleconferencing services for DOD elements, their supporting activities engaged in logistics, personnel, engineering, and intelligence, as well as other federal agencies |
Use to identify the DSN telephone number. |
|
|
869F |
PER07 |
EM |
Electronic Mail |
|
|
|
|
869F |
PER07 |
EX |
Telephone Extension |
Use to identify a telephone extension |
Use immediately following codes AU, IT or TE. |
|
|
869F |
PER07 |
FX |
Facsimile |
|
|
|
|
869F |
PER07 |
IT |
International Telephone |
|
Include country and city code. |
|
|
869F |
PER07 |
TE |
Telephone |
The commercial telephone number Include the area code and number |
Use to identify the commercial telephone number. Include the area code and number. |
|
|
869F |
PER07 |
TL |
Telex |
An number to a particular telegraphy machine for routing printed messages |
|
|
|
869F |
PER07 |
TX |
TWX |
A number to a particular teletypewriter for routing message signals |
|
|
|
869F |
PER08 |
|
|
|
|
|
|
869F |
PER09 |
|
|
|
|
|
|
869F |
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. |
|
|
|
869F |
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 legacy MILSTRIP DIC is retained in the DLMS to facilitate transaction conversion in a mixed legacy MILSTRIP/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date.
2. Use two iterations to identify requisition DIC and Requisition Exception Data Transaction (DLA DIC YRZ), when applicable.
3. Future streamlined data; see introductory DLMS note 4c. |
|
|
869F |
LQ01 |
67 |
Type of Assistance Code |
Use when the coded address in the transaction number does not identify the type of assistance and financing |
1. For Security Assistance (SA) transactions, use when the coded address in the transaction number does not identify the type of assistance and financing.
2. DLMS enhancement; see introductory DLMS note 4a. |
|
|
869F |
LQ01 |
74 |
Demand Code |
Indicates to the management element of a distribution system whether the demand is recurring or non-recurring |
|
|
|
869F |
LQ01 |
78 |
Project Code |
Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes |
1. Use to identify special programs, exercises, projects, operations, and other purposes.
2. For DoD SLOA/Accounting Classification compliance the Project Code may be repeated as a Project Identifier (FA201 Qualifier 90). Refer to ADC 1043. |
|
|
869F |
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) |
|
|
|
869F |
LQ01 |
80 |
Advice Code |
Use to transmit instructions considered by the creators of requisitions to be essential to the desired supply action |
Use to convey information to the supply source which is considered essential to the supply system. |
|
|
869F |
LQ01 |
81 |
Status Code |
Inform recipients of the status of requisitions or customer asset reports and related transactions |
Used by internet ordering applications to notify DAAS that the requisition follow-up failed to receive authorization for continued processing under funds verification procedures. Only Supply Status CX is applicable. This is an authorized DLMS enhancement. Refer to ADC 328. |
|
|
869F |
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. Use to indicate the lowest acceptable condition of materiel when requisitioning from DLA Disposition Services.
2. When requisitioning specific reparables for induction under Depot Maintenance Inter-Service Agreement (DMISA) or comparable inter-Service agreement, cite the supply condition code (SCC) applicable to the reparable item requested. Authorized SCCs include D, F, G, and Q. Requisitions for induction of a Product Quality Deficiency Report (PQDR) exhibit for warrantied maintenance will cite SCC Q. Refer to ADC 1176. |
|
|
869F |
LQ01 |
84 |
Management Code |
|
1. Authorized on an Intra-Army basis to provide required management code information in order to accurately process transactions relative to image and post-post requisitions submitted by Army Single Stock Fund activities. (Refer to ADC 243)
2. Authorized DLMS enhancement under DLA industrial activity support agreement. (Refer to ADC 352, ADC 359 and ADC 375).
3. Authorized on an Intra-Air Force basis to provided required management code information on the reason for the requisition. (Refer to ADC 1390) |
|
|
869F |
LQ01 |
87 |
Subsistence Type of Pack Code |
Use to indicate the degree of protection to be provided subsistence items |
Use with subsistence items. |
|
|
869F |
LQ01 |
89 |
Cooperative Logistics Program Support Code |
Provides information as to whether or not supply support on a Cooperative Logistics Supply Support Arrangement (CLSSA) requisition or passing order should be made on a programmed or un-programmed basis |
For FMS transactions, must use to identify programmed, nonprogrammed, and termination/drawdown requirements. |
|
|
869F |
LQ01 |
94 |
Identification Code |
Use in FMS transactions to identify the customer country's requisitioning Service Code |
Must use in FMS transactions to identify the customer country's requisitioning Service Code: B, D, K, P, or T. This is the SA program Customer Service Designator (codes derived from Qualifier 71, Service and Agency Code). A DM will be submitted to create a new qualifier for this data element. |
|
|
869F |
LQ01 |
95 |
Offer and Release Option Code |
|
For FMS transactions, must use to advise the supply source of the type of notice required prior to shipping the materiel. |
|
|
869F |
LQ01 |
97 |
Ultimate Recipient Code |
The buyer of materiel so that Department of Defense (DoD) can be fully reimbursed for materiel supplied to a non-DoD customer |
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 4a. |
|
|
869F |
LQ01 |
98 |
Reason for Requisitioning Code |
|
1. Use to identify Reason for Requisitioning Code identifying the use of the materiel.
2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. |
|
|
869F |
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. Use in CAV transactions.
2. DLMS enhancement; see introductory DLMS note 4a. |
|
|
869F |
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. Use in requisition or referral order to identify the ownership of previously purchased materiel. This is a restricted use applicable when a Service has entered into an MOA with DLA relative to Service-owned stocks, centrally-managed/stored by DLA (1BR06/020, Code RI).
2. Use on a referral order to initiate an inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel. Use to identify the new/gaining (to) ownership code. DLMS enhancement. Refer to ADC 1020.
3. Also authorized on an intra-Army basis with BR02 Transaction Type Code A0 and BR06 Action Code J for identification of the ownership of materiel post-post issued by Army Single Stock Fund activities. |
|
|
869F |
LQ01 |
A2 |
Customer Within Country Code |
Use to identify the coded address in the transaction number does not identify the customer-within-country |
1. For SA customers, use when the coded address in the transaction number does not identify the customer-within-country.
2. DLMS enhancement; see introductory DLMS note 4a. |
|
|
869F |
LQ01 |
A3 |
Delivery Term Code |
A code (prescribed in FMS cases) identifying the point at which the responsibility for moving an item as an FMS shipment passes from the United States DoD to the purchasing nation or international organization |
1. For FMS, transactions, use when the coded address in the transaction number does not identify the delivery term.
2. DLMS enhancement; see introductory DLMS note 4a. |
|
|
869F |
LQ01 |
A5 |
Subcase Number |
Use in Foreign Military Sales (FMS) transactions based on Service requirements |
1. Use in FMS transactions based on Service requirements.
2. DLMS enhancement; see introductory DLMS note 4a. |
|
|
869F |
LQ01 |
A6 |
Freight Forwarder Number |
Use in Foreign Military Sales (FMS) transactions to identify the country representative or freight forwarder to receive shipments and documentation |
Must use in FMS transactions to identify the country representative or freight forwarder to receive shipments and documentation. |
|
|
869F |
LQ01 |
A7 |
Record Control Number |
|
Must use in MAP/GA transactions to identify the program line item number. |
|
|
869F |
LQ01 |
A8 |
Program Year Code |
|
Must use in MAP/GA transactions to indicate the program year in which the requisitioned item was approved and funded. |
|
|
869F |
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 legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the MILSTRIP Supplementary Address (SUPADD) 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 SUPADD will be reflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 4c.
5. During legacy MILSTRIP/DLMS transition, use on a referral order follow-up to initiate an inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel and no billing. Cite Signal Code M and Project Code CYK 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. |
|
|
869F |
LQ01 |
AJ |
Utilization Code |
Use to identify a specialized purpose of the transaction |
1. Use to identify a specialized purpose for which the requisition is submitted.
2. Under legacy MILSTRIP, this is the first position of the document serial number within the document number.
3. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
4. DLMS enhancement; see introductory DLMS note 4a. |
|
|
869F |
LQ01 |
AK |
Distribution Code |
Use to identify the activity that will receive a supply status and other management data |
Future streamlined data; see introductory DLMS note 4c. |
|
|
869F |
LQ01 |
AL |
Special Requirements Code |
Use to identify precedence, special handling, and processing requirements |
1. Under legacy MILSTRIP, this is carried in the required delivery date field.
2. DLMS enhancement; see introductory DLMS note 4a.
3. Use in conjunction with 2/LQ01/Code RC, Requirement Code, to complete the Air Force unique NMCS/MICAP data requirement. |
|
|
869F |
LQ01 |
BD |
Transportation Priority Code |
A relative precedence of movement that indicates the priority of a space available passenger or the recommended shipment mode for a requisition |
1. Use to identify a transportation priority which is different than that associated with the requisition priority.
2. DLMS enhancement; see introductory DLMS note 4a. |
|
|
869F |
LQ01 |
DE |
Signal Code |
In requisition related documents, it designates the fields containing the intended consignee (ship-to), and the activity to receive and effect payment of bills, when applicable. In the case of the Material Returns Program (MRP), it designates the fields containing the intended consignor (ship-from) and the activity to receive and process credits, when applicable |
Future streamlined data; see introductory DLMS note 4c. |
|
|
869F |
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 4c. |
|
|
869F |
LQ01 |
DJ |
Remedial Action Code |
Use to indicate the actions required by the receiving system in order to accurately process transactions and direct the types of follow-on actions authorized to occur |
Use temporary qualifier DJ - Remedial Action Code to identify Army Edit Action Code indicating the actions required by the receiving system in order to accurately process transactions and direct the types of follow-on actions authorized to occur. This is an Army unique data element, and is meaningful to the Army only. The code source is identified as the U.S. Army Materiel Command Single Stock Fund Functional User Manual, 3rd Edition. An ANSI data maintenance request has been prepared to establish a new data element 1270 code qualifier assignment for Army Edit Action Code. |
|
|
869F |
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 Materiel Management Aggregation Code (MMAC) 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-110, Volumes 1 and 2. |
|
|
869F |
LQ01 |
KJ |
Assured Delivery Indicator |
Use to communicate special processing and/or priority requirements |
1. Use to identify, or modify, the Delivery Priority/Special Processing Code for materiel that has an urgency of need within the maintenance shop and must be delivered within one hour of receipt of the issue request. Value will be X (1 hour issue) when applicable.
2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381.
3. A data maintenance action was approved in version 5030. The approved code/name is DPC – Delivery Priority Code. DoD systems will continue to use Qualifier KJ to represent the Delivery Priority/Special Processing Code until such time as a new ADC directs otherwise. |
|
|
869F |
LQ01 |
RC |
Requirement Code |
Use to identify the urgency of need and type of requirement (justification) related to a not mission capable supply/mission impaired capability awaiting parts condition |
1. Use to identify the Air Force Urgency Justification Code indicating the urgency of need and type of requirement (justification) related to a Not Mission Capable Supply/Mission Impaired Capability Awaiting Parts (NMCS/MICAP) condition.
2. Use in conjunction with Special Requirements Code N (2/LQ01/Code AL or perpetuated from legacy MILSTRIP Required Delivery Date field). This is an Air Force unique data element, meaningful to the Air Force only. Non-Air Force Components perpetuate without action. The code source is identified as the Air Force Manual (AFMAN) 23-110, Volume 1 and 2.
A data maintenance action was approved in version 5010. The approved code/name is "UJC - Urgency Justification Code". |
|
|
869F |
LQ01 |
RD |
Property Ownership Type Code |
|
Use only on a referral order follow-up to initiate an inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel. Use to identify, or to modify, the old (from) ownership code. DLMS enhancement. Refer to ADC 1020. |
|
|
869F |
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 nonstock 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. |
|
|
869F |
LQ01 |
DSI |
Disposition Services Indicator Code |
Addresses the DLA Disposition Services’ requirement to communicate unique property and/or materiel location information supporting their business processes |
1. DLA Disposition Services uses to provide relevant information applicable to the DLA Disposition Services business process supported by this transaction on an intra-DLA basis. Use multiple repetitions of the LQ Segment to include all applicable codes. Authorized DLMS enhancement for use by DLA Disposition Services. Refer to ADC 466.
2. The following Disposition Services Indicator values are available for use in the requisition transaction:
MRA – Materiel Receipt Acknowledgment Required.
DMIL – DEMIL Certification Required.
MUTL – Mutilation Certification Required.
RCYL– Certificate of Recycling Required.
CIF – Container Issued in Full.
WALK–Walk-in Customer.
PICK- Customer Pick-up Required.
3. Approved for use in X12 version 6050. |
|
|
869F |
LQ01 |
EWR |
Evaluate Work Candidate Reason Lookup |
|
1. Use to identify Requirement Churn Reason Code to identify materiel orders required by the industrial site to complete planned work above what was originally identified during the pre-planned process ordered and delivered after the start of the availability.
2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. |