|
|
870M |
N103 |
A2 |
Military Assistance Program Address Code (MAPAC) |
Use to identify the consignee in transportation documents and to obtain clear-text address and other shipment information from the military assistance program address directory (MAPAD) |
Use with code RL to indicate the Security Assistance (SA) structured address data. Interpretation of this data may require additional codes cited elsewhere in the transaction. |
|
|
870M |
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 |
|
|
|
870M |
N106 |
FR |
Message From |
Use to identify the party originating the transaction set |
Must use with the appropriate 1/N101/050 code to indicate that the organization cited in N104 is originating the transaction set. |
|
|
870M |
HL03 |
W |
Transaction Reference Number |
|
Use to identify the individual transaction status lops. |
|
|
870M |
REF01 |
86 |
Operation Number |
|
1. Use to identify the Key Operation (KO) Number associated with the JO. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. |
|
|
870M |
REF01 |
9R |
Job Order Number |
|
Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. |
|
|
870M |
REF01 |
CO |
Customer Order Number |
|
1. Use to identify the Customer Order Acceptance Record (COAR) applicable to the Job Order Number. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381 (or as applicable). |
|
|
870M |
REF01 |
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 |
Must use to identify the materiel returns transaction number. |
|
|
870M |
REF01 |
PWC |
Preliminary Work Candidate Number |
|
1. Use to identify a Requisition Alert Document Number. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. |
|
|
870M |
REF04-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 |
When used in association with the Requisition Alert Document Number (Qualifier PWC, above), this will be the requisition alert document suffix. The Requisition Alert Document Number Suffix is an Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. |
|
|
870M |
N101 |
77 |
Service Location |
Use for materiel availability reports and automatic shipment notifications to identify the party to receive packing, crating , and handling credit when different from the party to receive credit for materiel |
Use for materiel availability reports and automatic shipment notifications to identify the party to receive packing, crating , and handling credit when different from the party to receive credit for materiel. Data maintenance action to ad qualifier CRP for this purpose has been approved for version 4020. |
|
|
870M |
N101 |
KK |
Registering Party |
|
1. Use to identify the Component UIT registry. May be used by a Component when their UIT process requires that a copy of the transaction also be sent to a UIT registry for information purposes. Must be used with 2/N106/90 code ‘PK-Party to Receive Copy’ to identify that this is only an information copy of the transaction, for use with the Component UIT registry. 2. DLMS enhancement. See introductory DLMS note 4a. |
|
|
870M |
N101 |
N1 |
Notify Party no. 1 |
|
Use to identify the organization to receive packing, crating, and handling credit. Data Maintenance action has been initiated to obtain an appropriate qualifier. |
|
|
870M |
N101 |
N2 |
Notify Party no. 2 |
|
Use to identify the organization to receive transportation credit. Data Maintenance action has been initiated to obtain an appropriate qualifier. |
|
|
870M |
N101 |
RL |
Reporting Location |
|
Use to indicate the reporting organization when providing status on open materiel returns reports. |
|
|
870M |
N101 |
ST |
Ship To |
|
ICPs/IMs use to identify the receiving depot to which the reported materiel is to be shipped. |
|
|
870M |
N101 |
Z1 |
Party to Receive Status |
The entity to receive status for the designated document number |
Use multiple iterations to identify all additional status recipients, as required. |
|
|
870M |
N101 |
Z4 |
Owning Inventory Control Point |
Use to indicate the source of supply |
1. Use to identify the ICP/IM. 2. Authorized DLMS enhancement for Army use to identify the Inventory Control Point that the transaction is to be routed to when acting as an Exchange Pricing Delta Bill Trigger (used in conjunction with LQ01/30 = SEC (Stock Exchange Code). |
|
|
870M |
N101 |
Z8 |
Last Known Source of Supply |
|
Use to identify the ICP/IM to receive all future transactions. |
|
|
870M |
N101 |
ZB |
Party to Receive Credit |
Use to identify the Business Partner Number (BPN) of the party to receive credit |
Use to identify the organization to receive materiel credit. |
|
|
870M |
N101 |
ZS |
Monitoring Party |
|
Use to identify the ILCO. ZZ - Mutually Defined: Use for materiel availability reports and automatic shipment notifications to identify the party to receive transportation credit when different from the party to receive credit for materiel. An ANSI data maintenance was approved in version 5010. The approved code/name is “AEJ - Party to Receive Transportation Credit". |
|
|
870M |
N103 |
10 |
Department of Defense Activity Address Code (DODAAC) |
Use to identify specific units, activities, and/or organizations. The first position indicates the Component or other Government element of ownership or sponsorship. The remaining five positions are assigned under established products by the Service point of the participating Component |
DLMS enhancement; see introductory DLMS note 4a. |
|
|
870M |
N103 |
A2 |
Military Assistance Program Address Code (MAPAC) |
Use to identify the consignee in transportation documents and to obtain clear-text address and other shipment information from the military assistance program address directory (MAPAD) |
Use to indicate the SA structured address data. Interpretation of this data may require additional codes cited elsewhere in the transaction. |
|
|
870M |
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 |
|
|
|
870M |
N103 |
UR |
Uniform Resource Locator (URL) |
|
1. Use when appropriate to identify the Component UIT registry. 2. DLMS enhancement; see introductory DLMS note 4.a. |
|
|
870M |
N106 |
PK |
Party to Receive Copy |
|
1. Use when appropriate to send an information copy of the transaction to a Component UIT registry. For use with N101 code K. 2. DLMS enhancement. See introductory DLMS note 4a. |
|
|
870M |
N106 |
TO |
Message To |
Use to identify the party to receive the transaction set |
Use in conjunction with the appropriate 2/N101/090 code to indicate the organization cited in N104 is to receive the transaction. |
|
|
870M |
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. |
|
|
|
870M |
LQ01 |
0 |
Document Identification Code |
Identifies transaction specific operation to which they apply and indicates the intended purpose and use of the transaction data |
|
|
|
870M |
LQ01 |
67 |
Type of Assistance Code |
|
For Security Assistance (SA) transactions, use when the coded address in the transaction number does not identify the type of assistance. |
|
|
870M |
LQ01 |
78 |
Project Code |
Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes |
ICPs/IMs use to identify the project code assigned when shipment of the reported materiel is directed. |
|
|
870M |
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. |
|
|
870M |
LQ01 |
85 |
Country and Activity Code |
|
For SA, use when the coded address in the transaction number does not identify the country or activity. |
|
|
870M |
LQ01 |
87 |
Subsistence Type of Pack Code |
Use to indicate the degree of protection to be provided subsistence items |
ICPs/IMs and reporting organizations use to identify the type of pack associated with the reported subsistence items. |
|
|
870M |
LQ01 |
89 |
Cooperative Logistics Program Support Code |
|
For SA, use as applicable. |
|
|
870M |
LQ01 |
A2 |
Customer Within Country Code |
|
For SA, use when the coded address in the transaction number does not identify the customer-within-country. |
|
|
870M |
LQ01 |
A6 |
Freight Forwarder Number |
|
For SA, use to identify the country representative or freight forwarder. |
|
|
870M |
LQ01 |
A7 |
Record Control Number |
|
For SA, use as applicable. |
|
|
870M |
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. 1. Future streamlined data; see introductory DLMS note 4c. |
|
|
870M |
LQ01 |
AJ |
Utilization Code |
Use to identify a specialized purpose of the transaction |
1. Under legacy MILSTRIP, this is the first position of the document serial number. 2. DLMS enhancement; see introductory DLMS note 4a. |
|
|
870M |
LQ01 |
AK |
Distribution Code |
|
|
|
|
870M |
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 legacy MILSTRIP, this is caried in the required delivery date field. 3. DLMS enhancement; see introductory DLMS note 4a. |
|
|
870M |
LQ01 |
DE |
Signal Code |
Use to indicate the bill-to and ship-to DoDAAC (Department of Defense Activity Address Code) for an item |
|
|
|
870M |
LQ01 |
DF |
Media and Status Code |
Identifies the desired status recipient(s) and the type of status to be provided |
|
|
|
870M |
LQ01 |
DG |
Fund Code |
Designation of the billing method (interfund or non-interfund) and the fund account to be charged (disbursed) or credited (refunded) |
|
|
|
870M |
PO106 |
A2 |
Department of Defense Identification Code (DoDIC) |
Use to identify specific types of ammunition and explosives, indicating both the item and its packaging |
Use to identify ammunition items. |
|
|
870M |
PO106 |
A4 |
Subsistence Identification Number |
Use to identify a brand name resale subsistence item |
Use to identify subsistence items. |
|
|
870M |
PO106 |
FB |
Form Number |
A unique stock number associated with a specific Approved Code form |
Use to identify the form stock number. |
|
|
870M |
PO106 |
FS |
National Stock Number |
A number assigned under the federal cataloging program to each Approved Code United States Federal Item Identification |
|
|
|
870M |
PO106 |
MG |
Manufacturer's Part Number |
A number assigned by a manufacturer to an item of production |
Use to identify nonstandard materiel. |