|
|
869F |
PER05 |
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. |
7/7 |
|
|
869F |
PER05 |
EM |
Electronic Mail |
Use to identify an internet address for distributing messages by electronic means to a person or group formatted as [identifier]@[email server internet domain name] |
|
1/256 |
|
|
869F |
PER05 |
EX |
Telephone Extension |
Use to identify a telephone extension |
Use immediately following codes AU, IT or TE. |
1/60 |
|
|
869F |
PER05 |
FX |
Facsimile |
The facsimile (FAX) telephone number |
|
10/10 |
|
|
869F |
PER05 |
IT |
International Telephone |
A number assigned to a particular telephone for making connections to it |
Include country and city code. |
1/60 |
|
|
869F |
PER05 |
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. |
10/10 |
|
|
869F |
PER05 |
TL |
Telex |
An number to a particular telegraphy machine for routing printed messages |
|
1/60 |
|
|
869F |
PER05 |
TX |
TWX |
A number to a particular teletypewriter for routing message signals |
|
1/60 |
|
|
869F |
PER06 |
|
|
|
|
N/A |
|
|
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. |
7/7 |
|
|
869F |
PER07 |
EM |
Electronic Mail |
Use to identify an internet address for distributing messages by electronic means to a person or group formatted as [identifier]@[email server internet domain name] |
|
1/256 |
|
|
869F |
PER07 |
EX |
Telephone Extension |
Use to identify a telephone extension |
Use immediately following codes AU, IT or TE. |
1/60 |
|
|
869F |
PER07 |
FX |
Facsimile |
The facsimile (FAX) telephone number |
|
10/10 |
|
|
869F |
PER07 |
IT |
International Telephone |
A number assigned to a particular telephone for making connections to it |
Include country and city code. |
1/60 |
|
|
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. |
10/10 |
|
|
869F |
PER07 |
TL |
Telex |
An number to a particular telegraphy machine for routing printed messages |
|
1/60 |
|
|
869F |
PER07 |
TX |
TWX |
A number to a particular teletypewriter for routing message signals |
|
1/60 |
|
|
869F |
PER08 |
|
|
|
|
N/A |
|
|
869F |
PER09 |
|
|
|
|
N/A |
|
|
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. |
|
N/A |
|
|
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. |
3/3 |
|
|
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. |
1/30 |
|
|
869F |
LQ01 |
74 |
Demand Code |
Indicates to the management element of a distribution system whether the demand is recurring or non-recurring |
|
1/1 |
|
|
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. |
3/3 |
|
|
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) |
|
2/2 |
|
|
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. |
2/2 |
|
|
869F |
LQ01 |
81 |
Status Code |
Use to inform activities of action taken or being taken on materiel requisitioned but not shipped, shipment consignments instructions, or disposition instructions for materiel offered under the materiel returns program (MRP) |
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. |
2/2 |
|
|
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. |
1/1 |
|
|
869F |
LQ01 |
84 |
Management Code |
Use to provide supplemental data not indicated through the transaction coding structure |
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) |
1/1 |
|
|
869F |
LQ01 |
87 |
Subsistence Type of Pack Code |
Use to indicate the degree of protection to be provided subsistence items |
Use with subsistence items. |
1/1 |
|
|
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. |
1/1 |
|
|
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). |
1/2 |
|
|
869F |
LQ01 |
95 |
Offer and Release Option Code |
Use to advise the supply source of the type of notice required prior to shipping the materiel |
For FMS transactions, must use to advise the supply source of the type of notice required prior to shipping the materiel. |
1/30 |
|
|
869F |
LQ01 |
97 |
Ultimate Recipient Code |
Use to identify the buyer of materiel so that Department of War (DoW) can be fully reimbursed for materiel supplied to a non-DoW 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. |
1/1 |
|
|
869F |
LQ01 |
98 |
Reason for Requisitioning Code |
Use to identify the reason for submission of the requisition or the type of materiel requirement applicable to a requisition, requisition alert, or materiel release order |
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. |
1/2 |
|
|
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. |
1/1 |
|
|
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. |
1/1 |
|
|
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. |
1/1 |
|
|
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. |
1/1 |
|
|
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. |
3/3 |
|
|
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. |
1/30 |
|
|
869F |
LQ01 |
A7 |
Record Control Number |
Use to identify a specific item or service within a government contract Military Assistance Program (MAP) Grant Aid (GA) case |
Must use in MAP/GA transactions to identify the program line item number. |
4/4 |
|
|
869F |
LQ01 |
A8 |
Program Year Code |
Use in Military Assistance Program (MAP)/grant aid (GA) transactions to indicate the program year in which the requisitioned item was Approved Code and funded |
Must use in MAP/GA transactions to indicate the program year in which the requisitioned item was approved and funded. |
1/80 |
|
|
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 th e 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. |
6/6 |
|
|
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. |
1/1 |
|
|
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. |
1/3 |
|
|
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. |
1/3 |
|
|
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. |
1/1 |
|
|
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. |
1/1 |
|
|
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. |
1/1 |