|
|
812L |
N901 |
TN |
Transaction Reference Number |
A unique number generated by the original submitter of a pre-defined transaction and assigned to any pre-defined information exchange within the department of defense The transaction reference number retains its identity for the life of the generated transaction |
Use to identify the document number associated with the billing adjustment request reply. For bills in response to requisitions, this must be the requisition document number. See Addendum to ADC 473B. |
14/14 |
|
|
812L |
N902 |
|
|
|
|
|
|
|
812L |
N903 |
|
|
|
|
|
|
|
812L |
N907 |
|
|
|
|
|
|
|
812L |
N907-01 |
W8 |
Suffix |
Use to identify supply transaction partial actions taken on the original document without duplicating or causing loss of identity of the original document number |
Use in conjunction with code TN (N901) to identify the suffix of the transaction reference number. |
1/1 |
|
|
812L |
N907-02 |
|
|
|
|
|
|
|
812L |
N907-03 |
FJ |
Line Item Control Number |
Use to identify the line item number associated with the MIPR/Project Order Number |
1. Use with N901 code 3H to identify the excess plant property reference number.
2. DLMS enhancement applicable to PCARSS requisitioning; see introductory DLMS note 4a. |
1/30 |
|
|
812L |
N907-04 |
|
|
|
|
|
|
|
812L |
N907-05 |
|
|
|
|
|
|
|
812L |
N907-06 |
|
|
|
|
|
|
|
812L |
DTM01 |
188 |
Credit Advice |
Use to identify the date credit was issued |
Use to identify the credit date. |
8/8 |
|
|
812L |
DTM01 |
368 |
Submittal |
|
Use to identify the originator's reply date when it differs from BCD01. |
|
|
|
812L |
DTM01 |
703 |
Retransmission Time Stamp |
Use to identify the date of the first invoice where this billing was recorded |
Use to identify the date of the first invoice where this billing was recorded. |
8/8 |
|
|
812L |
DTM02 |
|
|
|
|
|
|
|
812L |
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. |
|
|
|
|
812L |
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 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.
2. Future streamlined data; see introductory DLMS note 4c |
3/3 |
|
|
812L |
LQ01 |
53 |
Billing Status Code |
Identifies the type of response to requests for billing adjustment, duplicate billing, or billing status |
Use to indicate the request's approval or disapproval. |
3/3 |
|
|
812L |
LQ01 |
78 |
Project Code |
Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes |
Use to identify special programs, exercises, projects, operations, and other purposes. |
3/3 |
|
|
812L |
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) |
Recommend using in all requisitions. |
2/2 |
|
|
812L |
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) |
|
2/2 |
|
|
812L |
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 only for intra-service or agency transactions to identify service or agency-unique data as required.
2. Use to identify supplemental address/data.
3. Future streamlined data; see introductory DLMS note 4c. |
6/6 |
|
|
812L |
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 |
|
|
812L |
LQ01 |
AL |
Special Requirements Code |
Use to identify precedence, special handling, and processing requirements |
1. Use to identify the precedence, special handling, and processing requirements.
2. Under DLSS, this is carried in the required delivery date field.
3. DLMS enhancement; see introductory DLMS note 4a. |
1/3 |
|
|
812L |
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 |
|
1/1 |
|
|
812L |
LQ01 |
DF |
Media and Status Code |
Identifies the desired status recipient(s) and the type of status to be provided |
For DLSS and conversion purposes, use to identify the party to receive status. |
1/1 |
|
|
812L |
LQ01 |
DG |
Fund Code |
Designation of the billing method (interfund or non-interfund) and the fund account to be charged (disbursed) or credited (refunded) |
|
2/2 |
|
|
812L |
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. |
2/2 |
|
|
812L |
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 materiel 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 |
|
|
812L |
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 |
|
|
812L |
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 |
|
|
812L |
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 |
|
|
812L |
LQ02 |
|
|
|
|
|
|
|
812L |
SE01 |
|
|
|
|
|
|
|
812L |
SE02 |
|
|
|
|
|
|
|
812R |
ST01 |
812 |
Credit/Debit Adjustment |
Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit Conversion Table and the Transportation Mode of Shipment Conversion Table which can be found on the Defense Enterprise Data Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS. |
|
|
|
|
812R |
ST02 |
|
|
|
|
|
|
|
812R |
BCD01 |
|
|
|
|
|
|
|
812R |
BCD02 |
|
|
|
|
|
|
|
812R |
BCD03 |
H |
Notification Only |
|
1. Use to identify a request for an information copy of an invoice.
2. DLMS enhancement; see introductory DLMS note 5a. |
|
|
|
812R |
BCD03 |
T |
Adjustment Requested |
|
1. Use to identify a request for adjustment of an invoice.
2. DLMS enhancement; see introductory DLMS note 5a. |
|
|
|
812R |
BCD04 |
|
|
|
|
|
|
|
812R |
BCD05 |
C |
Credit |
Use when credits or refunds are sought |
DLMS enhancement; see introductory DLMS note 5a. |
1/1 |
|
|
812R |
BCD05 |
D |
Debit |
|
DLMS enhancement; see introductory DLMS note 5a. |
|
|
|
812R |
BCD06 |
|
|
|
|
|
|
|
812R |
BCD07 |
|
|
|
|
|
|
|
812R |
BCD11 |
00 |
Original |
Indicates the initial transaction |
|
|
|
|
812R |
BCD11 |
01 |
Cancellation |
Use to indicates the reversal, cancellation, or voiding of a prior submission or status |
|
2/30 |
|
|
812R |
BCD11 |
45 |
Follow-up |
Use to identify a follow-up on a transaction |
|
Non-DLMS |
|
|
812R |
BCD11 |
77 |
Simulation Exercise |
Use to identify a simulated mobilization exercise transaction set |
Activities simulating mobilization exercises must ensure complete coordination with all activities involved. All transaction set recipients must use caution to ensure that transactions do not process as action documents which affect accountable records. |
|
|
|
812R |
BCD12 |
CA |
Cash |
|
1. Use to indicate the reference invoice as noninterfund.
2. DLMS enhancement; see introductory DLMS note 5a. |
|