|
|
861P |
RCD01 |
|
|
|
|
|
|
|
861P |
RCD02 |
|
|
|
|
|
|
|
861P |
RCD03 |
|
|
|
|
|
|
|
861P |
RCD03-01 |
|
|
|
|
|
|
|
861P |
RCD06 |
|
|
|
|
|
|
|
861P |
RCD07 |
|
|
|
|
|
|
|
861P |
RCD07-01 |
|
|
|
|
|
|
|
861P |
RCD08 |
09 |
Hold |
|
1. Use to indicate that discrepant quantity received has been placed in a suspended condition.
2. Not applicable to shipment level acceptance process. |
|
|
|
861P |
SN102 |
|
|
|
|
|
|
|
861P |
SN103 |
|
|
|
|
|
|
|
861P |
PID01 |
F |
Free-form |
|
Future enhancement; not used for initial implementation. |
|
|
|
861P |
PID05 |
|
|
|
|
|
|
|
861P |
REF01 |
EF |
Electronic Funds Transfer ID Number |
|
Use only when 1/N103/130 is UE Unique Entity Identifier, to provide an alternate EFT account in REF02. |
1/30 |
|
|
861P |
REF01 |
IX |
Item Number |
Use for Authorization Accounting Activity (AAA) |
1. Use for Authorization Accounting Activity (AAA).
2. Applicable to Navy acceptance only.
3. AAA may be reported for each CLIN accepted . |
1/30 |
|
|
861P |
REF02 |
|
|
|
|
|
|
|
861P |
MAN01 |
ZZ |
Mutually Defined |
|
1. Use to identify the Unique Item Identifier (UII) for each item. If the UII exceeds 48 characters, carry over the additional characters to MAN03. When MAN01 is ZZ, MAN03 may only be used as a continuation of the UII entered in MAN02.
2. The UII may not exceed 50 characters in accordance with IUID Policy. |
|
|
|
861P |
MAN02 |
|
|
|
|
|
|
|
861P |
MAN03 |
|
|
|
|
|
|
|
861P |
MAN04 |
R |
Originator Assigned |
Use to identify the serial number associated with the identified Unique Item Identifier (UII) |
1. Use to identify the serial number associated with the identified UII in MAN05. When a batch, lot, or other type of production run number is included in the UII for uniqueness, this number will be cited in MAN06.
2. Future enhancement; not used for initial implementation. |
1/48 |
|
|
861P |
MAN05 |
|
|
|
|
|
|
|
861P |
MAN06 |
|
|
|
|
|
|
|
861P |
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. |
|
|
|
|
861P |
LQ01 |
0 |
Document Identification Code |
Identifies transaction specific operation to which they apply and indicates the intended purpose and use of the transaction data |
|
3/3 |
|
|
861P |
LQ01 |
10 |
Transaction Status Indicator Code |
Use to identify the status of a transaction |
1. Use one of codes D - Interim Status, F - Final Reply Report or G - Ship To Code Differs From Contract, to indicate the transaction status.
2. Applicable during DLMS migration; not used by WAWF during initial implementation. |
1/30 |
|
|
861P |
LQ01 |
17 |
Shipment Acceptance Discrepancy Explanation Code |
Use to identify the reason for the variance between the quantity documented as shipped and the quantity accepted, or when documentation is missing or incomplete |
|
1/1 |
|
|
861P |
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 Material 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 |
|
|
861P |
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 nonstock numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action. |
2/2 |
|
|
861P |
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 |
|
|
861P |
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 |
|
|
861P |
LQ02 |
|
|
|
|
|
|
|
861P |
SE01 |
|
|
|
|
|
|
|
861P |
SE02 |
|
|
|
|
|
|
|
867D |
ST01 |
867 |
Product Transfer and Resale Report |
Organizations use this transaction set to record demand for items that are obtained locally. Use one occurrence of this transaction set to transmit a single or multiple transactions. |
|
|
|
|
867D |
ST02 |
|
|
|
|
|
|
|
867D |
BPT01 |
00 |
Original |
Indicates the initial transaction |
|
|
|
|
867D |
BPT01 |
77 |
Simulation Exercise |
Use to identify a simulated mobilization exercise transaction set |
Activities initiating simulated mobilization exercises must ensure complete coordination with all activities involved. All transaction set recipients must use caution to ensure that transactions are not processed as action documents which affect accountable records. |
|
|
|
867D |
BPT03 |
|
|
|
|
|
|
|
867D |
BPT04 |
TO |
Demand Report |
Use to indicate that the transaction set contains demand transactions for standard or nonstandard material |
Use to indicate that the transaction set contains demand transactions for standard or nonstandard material. |
4/8 |
|
|
867D |
BPT08 |
|
|
|
|
|
|
|
867D |
N101 |
OB |
Ordered By |
Use to identify the transaction originator |
1. Use to identify the requisitioner.
2. DLMS enhancement; see introductory DLMS note 4a. |
1/60 |
|
|
867D |
N101 |
QB |
Purchase Service Provider |
Use to indicate a procurement contracting office or other purchasing activity to receive or originate the transaction set |
1. Use to indicate a procurement contracting office or other purchasing activity.
2. DLMS enhancement; see introductory DLMS note 4a. |
1/60 |
|
|
867D |
N101 |
SB |
Storage Area |
Use to identify the distribution depot/storage activity |
Use to identify the depot or storage activity. |
1/60 |
|
|
867D |
N103 |
10 |
Department of Defense Activity Address Code (DODAAC) |
Use to identify specific units, activities, and/or organizations |
DLMS enhancement; see introductory DLMS note 4a. |
6/6 |
|
|
867D |
N103 |
M4 |
Department of Defense Routing Identifier Code (RIC) |
Use to serve multiple purposes; supply source codes, inter-system routing codes, intra-system routing codes, and consignor (shipper) codes |
|
3/3 |
|
|
867D |
N104 |
|
|
|
|
|
|
|
867D |
N106 |
FR |
Message From |
Use to identify the party originating the transaction set |
1. Must use with the appropriate 1/N101/080 code to indicate that the organization cited in N104 is originating the transaction set.
2. DLMS enhancement; see introductory DLMS note 4a. |
1/60 |
|
|
867D |
PER01 |
IC |
Information Contact |
Use in the first repetition to identify the primary POC and their primary communication number |
1. Use to identify the primary point of contact.
2. DLMS enhancement; see introductory DLMS note 4a. |
1/60 |
|
|
867D |
PER02 |
|
|
|
|
|
|
|
867D |
PER03 |
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 |
|
7/7 |
|
|
867D |
PER03 |
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 |