|
|
180M |
ST01 |
180 |
Return Merchandise Authorization and Notification |
Use to report the availability of materiel to the wholesale distribution system, to report the automatic shipment of materiel to storage or repair facilities, to request cancellation of previously submitted report, and to inquire about the status of previously submitted transactions. Use a single occurrence of this transaction set to transmit single or multiple materiel returns information transactions to one or more Inventory Control Points (ICPs) or Integrated Material Managers (IMMs). A single transaction set may contain a combination of transactions for standard and nonstandard materiel. |
|
|
|
180M |
ST02 |
|
|
|
|
|
|
180M |
BGN01 |
00 |
Original |
Indicates the initial transaction |
|
|
|
180M |
BGN01 |
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 do not process as action documents which affect accountable records. |
|
|
180M |
BGN02 |
|
|
|
|
|
|
180M |
BGN03 |
|
|
|
|
|
|
180M |
BGN04 |
|
|
|
|
|
|
180M |
BGN07 |
FT |
Material Returns |
Use to indicate the transaction set contains materiel returns program transactions |
Use to indicate the transaction set contains materiel returns program transactions. No action code required when used for initial asset report (MILSTRIP DIC FTE/FTG). |
|
|
180M |
BGN08 |
C |
Cancelled |
|
Use to indicate a request to cancel a previously submitted report of materiel availability (MILSTRIP DIC FTC). |
|
|
180M |
BGN08 |
T |
Status Query |
Use to indicate an inquiry to the ICP/IMM requesting a reply to a previously submitted report of materiel availability |
Use to indicate an inquiry to the ICP/IMM requesting a reply to a previously submitted report of materiel availability (MILSTRIP DIC FTF). |
|
|
180M |
BGN08 |
RF |
Returned to Shipper's Facility (Other Than Original Shipping Location) |
Use to indicate a notification of an automatic return shipment ( |
Use to indicate a notification of an automatic return shipment (MILSTRIP DIC FTA). |
|
|
180M |
BGN08 |
RS |
Report Status |
Use for customer followup indicating a request to provide receipt status for materiel previously reported as shipped |
Use for customer followup indicating a request to provide receipt status for materiel previously reported as shipped (MILSTRIP DIC FTT). |
|
|
180M |
N101 |
41 |
Submitter |
Use to identify participating activity which submits proposed data directly to the DLA logistics information service for approval. The submitting activity may be the activity which originates the data, or an intermediate monitoring activity, e.g., DLA supply center, defense atomic support agency, through which the originating activity is required to submit its proposals to DLA logistics information service |
|
|
|
180M |
N103 |
10 |
Department of Defense Activity Address Code (DODAAC) |
Use to identify specific units, activities, and/or organizations |
DLMS enhancement; see introductory DLMS note 2a. |
|
|
180M |
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 Security Assistance structured address data. |
|
|
180M |
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 |
|
|
|
180M |
N104 |
|
|
|
|
|
|
180M |
N106 |
FR |
Message From |
Use to identify the party originating the transaction set |
Must use to indicate that the organization cited in N104 originated the transaction set. |
|
|
180M |
BLI01 |
A2 |
Department of Defense Identification Code (DoDIC) |
Use to identify specific types of ammunition and explosives, indicating both the item and its packaging |
1. Use to identify ammunition items.
2. DLMS enhancement; see introductory DLMS note 2a. |
|
|
180M |
BLI01 |
A4 |
Subsistence Identification Number |
Use to identify a brand name resale subsistence item |
Use to identify subsistence items. |
|
|
180M |
BLI01 |
FB |
Form Number |
A unique stock number associated with a specific Approved Code form |
1. Use to identify the form stock number.
2. DLMS enhancement; see introductory DLMS note 2a. |
|
|
180M |
BLI01 |
FS |
National Stock Number |
A number assigned under the federal cataloging program to each Approved Code United States Federal Item Identification |
|
|
|
180M |
BLI01 |
MG |
Manufacturer's Part Number |
A number assigned by a manufacturer to an item of production |
Use to identify nonstandard materiel. |
|
|
180M |
BLI01 |
YP |
Publication Number |
Reference number assigned to a publication or catalog |
1. Use to identify the publication stock number.
2. DLMS enhancement; see introductory DLMS note 2a. |
|
|
180M |
BLI01 |
ZZ |
Mutually Defined |
Use to identify nonstandard materiel when all other authorized codes do not apply or cannot be determined (includes management control numbers and locally assigned control numbers) |
Use to identify nonstandard materiel when all other authorized codes do not apply or cannot be determined (includes management control numbers and locally assigned control numbers). May be used for legacy MILSTRIP-to-DLMS conversion when the translator cannot determine a more appropriate code. |
|
|
180M |
BLI02 |
|
|
|
|
|
|
180M |
BLI05 |
ACT |
Actual |
Use to indicate the actual price |
|
|
|
180M |
BLI05 |
EST |
Estimated Price |
Use to identify the estimated unit cost or estimated unit price |
|
|
|
180M |
BLI06 |
|
|
|
|
|
|
180M |
BLI08 |
ZB |
Commercial and Government Entity (CAGE) Code |
Code assigned to establishments which either fabricates items of production and/or have design control of items procured by the federal government, or to identify certain military specifications or standards, and certain numbering systems developed by government agencies, panels or committees |
Use with BLI01 code MG to uniquely identify a manufacturer's part number. |
|
|
180M |
BLI09 |
|
|
|
|
|
|
180M |
N901 |
TG |
Transportation Control Number (TCN) |
A 17-position alphanumeric assigned to control and manage every shipment unit throughout the transportation pipeline |
1. Enter the shipment unit TCN on customer follow up due to nonreceipt of receipt acknowledgement.
2. Future streamlined data; see introductory DLMS note 2c. |
|
|
180M |
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 |
Must use to identify the transaction number for each transaction. This is the document number. |
|
|
180M |
N902 |
|
|
|
|
|
|
180M |
N907 |
|
|
|
|
|
|
180M |
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 with N901 code TN in cancellation requests (BGN08 code C) and inquiries (BGN08 code RS), to identify the transaction number suffix. |
|
|
180M |
N907-02 |
|
|
|
|
|
|
180M |
TD504 |
|
|
|
|
|
|
180M |
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. |
|
|
|
180M |
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 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. Future streamlined data; see introductory DLMS note 2c. |
|
|
180M |
LQ01 |
78 |
Project Code |
Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes |
1. Use as needed 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. |
|
|
180M |
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) |
Use for notification for automatic returns. |
|
|
180M |
LQ01 |
80 |
Advice Code |
Use to transmit instructions considered by the creators of requisitions to be essential to the desired supply action |
|
|
|
180M |
LQ01 |
87 |
Subsistence Type of Pack Code |
Use to indicate the degree of protection to be provided subsistence items |
Use with subsistence items only. |
|
|
180M |
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.
2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the MILSTRIP Supplemented Address (SUPAAD) field. During this time, field size is restricted to 6 positions; see introductory DLMS note 2d.
3. Expanded use of this field for supplemental data with out size restriction is a DLMS enhancement; see introductory DLMS note 2a.
4. Under full DLMS, the requirement to pass activity address information within the supplement data field will be streamlined. Activity address data previously contained in the SUPAAD will be reflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 2c. |
|
|
180M |
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 2a. |
|
|
180M |
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 2a. |
|
|
180M |
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 2c. |
|
|
180M |
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 2c. |
|
|
180M |
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 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-Materiel Management Aggregation code”. The code source is identified as the Air Force Manual (AFMAN) 23-110, Volumes 1 and 2. |