|
|
870S |
DTM01 |
373 |
Order Start |
Use to indicate the effective date for requisitioning |
Use with status code CV to indicate the effective date for requisitioning. |
8/8 |
|
|
870S |
DTM01 |
514 |
Transferred |
Use to identify the date that a Material Processing Center (MPC) transships materiel to another MPC |
Use with Status Code NY to identify the date that a Material Processing Center (MPC) transships materiel to another MPC. |
8/8 |
|
|
870S |
DTM01 |
996 |
Required Delivery |
This is the customer assigned required delivery date |
Use with Supply Status BV to indicate Contract Required Delivery Date. This date may differ from the customer’s required delivery date. (Refer to ADC 465) |
8/8 |
|
|
888C |
G6201 |
BZ |
Demand Receipt Date |
Use to indicate The Date of Advice (DADV) |
Use to indicate The Date of Advice (DADV), the Transaction Date when the CX3 was 'initiated'. |
8/8 |
|
|
888I |
G6201 |
07 |
Effective Date |
Use to indicate when an item or transaction is prepared, becomes effective, or is placed into service |
|
8/8 |
|
|
888I |
G6201 |
BB |
Transaction Control Date |
Use to cite the date the transaction was prepared |
Use to identify the date of transaction preparation. |
8/8 |
|
|
888M |
G6201 |
90 |
Requested Pack Date |
Use to indicate Date Repair Part Required (DRPR) |
Use to indicate Date Repair Part Required (DRPR). |
8/8 |
|
|
888M |
G6201 |
TA |
Original Transaction |
Use to send when no Date Repair Part Required (DRPR). Send date of transaction |
Must send when no DRPR. Send date of transaction. |
8/8 |
|
|
888M |
G6201 |
FE |
Future Effective Date |
Use to identify the year and julian day denoting the date that a predetermined logistics action becomes effective in the Defense Logistics system |
1. Use to indicate the Future Effective Date (FLIS DRN 3387 - Characteristics, 2128 - Management, Airforce, Army Data, US Coast Guard, Marine Peculiar, Naval Command, Special Operations, Phrase Code, MOE Rule, Supple Collab, Depot Source of Repair, Identity).
2. Approved for use in X12 version 8060. |
8/8 |
|
|
888M |
G6201 |
BG |
Backorder Release Date |
Use to identify the date the backorder was released |
Use to indicate Oldest Back Order Date. |
8/8 |
|
|
888N |
G6201 |
90 |
Requested Pack Date |
Use to indicate Date Repair Part Required (DRPR) |
Use to indicate Date Repair Part Required (DRPR). |
8/8 |
|
|
888N |
G6201 |
TA |
Original Transaction |
Use to send when no Date Repair Part Required (DRPR). Send date of transaction |
Must send when no DRPR. Send date of transaction. |
8/8 |
|
|
888N |
G6201 |
FE |
Future Effective Date |
Use to identify the year and julian day denoting the date that a predetermined logistics action becomes effective in the Defense Logistics system |
1. Use to indicate the Future Effective Date (FLIS DRN 3387 - Characteristics, 2128 - Management, Airforce, Army Data, US Coast Guard, Marine Peculiar, Naval Command, Special Operations, Phrase Code, MOE Rule, Supple Collab, Supplemental Receiver, Depot Source of Repair, Identity).
2. A data maintenance action was approved in version 8060. |
8/8 |
|
|
888W |
G6201 |
BB |
Transaction Control Date |
Use to cite the date the transaction was prepared |
Use to indicate the date of the transaction's preparation. |
8/8 |
|
|
940R |
G6201 |
07 |
Effective Date |
Use to indicate when an item or transaction is prepared, becomes effective, or is placed into service |
Use to identify the date of transaction set preparation. This date corresponds to the Universal Time Coordinate (UTC). |
8/8 |
|
|
940R |
G6201 |
07 |
Effective Date |
Use to indicate when an item or transaction is prepared, becomes effective, or is placed into service |
1. Use to identify the map effective date.
2. Use when transaction includes Component-unique MRO exception data; see introductory DLMS note 4e. |
8/8 |
|
|
940R |
G6201 |
09 |
Process Date |
Use to indicate the date on which a transaction is processed by the relevant activity (either initiating or receiving) |
Use with the transaction history to identify the date on which the materiel release was processed by receiving activity. |
8/8 |
|
|
940R |
G6201 |
11 |
Shipped on This Date |
Use to identify date shipped |
1. Use only for Disposal Shipment Confirmation Followup to indicate the date shipped as reflected on the shipment status if received.
2. Future streamlined data; see introductory DLMS note 4c. |
8/8 |
|
|
940R |
G6201 |
53 |
Deliver Not Before Date |
Use to identify the earliest acceptable delivery date for the material requisitioned |
1. Use in redistribution orders, materiel release orders, and historical materiel release orders to identify the earliest acceptable delivery date for the materiel directed for shipment.
For conventional ammunition transactions, use to identify the earliest acceptable delivery date for the required delivery period.
Use in materiel release order modifications to identify the revised earliest acceptable delivery date.
2. DLMS enhancement; see introductory DLMS note 4a. |
8/8 |
|
|
940R |
G6201 |
54 |
Deliver No Later Than Date |
Use to identify the latest acceptable delivery date for the materiel requisitioned |
1. Use in redistribution orders, materiel release orders, and historical materiel release orders, to identify the latest acceptable delivery date for the materiel directed for shipment.
For conventional ammunition transactions, use to identify the latest acceptable delivery date for the required delivery period.
Use in materiel release order modifications, to identify the revised latest acceptable delivery date.
2. DLMS enhancement; see introductory DLMS note 4a. |
8/8 |
|
|
940R |
G6201 |
BC |
Publication Date |
Use only when requisitioning nonstandard material to cite the manufacturer's catalog publication date when a catalog is identified |
1. Use to identify the map edition date.
2. Use when transaction includes Component-unique MRO exception data; see introductory DLMS note 4e. |
8/8 |
|
|
940R |
G6201 |
BD |
Required By |
For security assistance, identifies the required availability date (a calculated date that is derived from the amount of time remaining from the date of requisition until the materiel is required) |
Use in redistribution orders, materiel release orders, and historical materiel release orders, to identify the required delivery date.
For SA transactions, use to identify the required availability date.
Use in materiel release order modifications, to identify the revised required delivery date or required availability date. |
8/8 |
|
|
940R |
G6201 |
LD |
Last Demand |
Use when transmitting misrouted requisition or when referring a requisition to another supply source to identify the date of receipt of the requisition as recorded by the initial supply source in the supply distribution system |
Use for LRO to identify the date of receipt of the demand document as recorded in that document by the initial recipient in the supply distribution system. |
8/8 |
|
|
940R |
G6201 |
TR |
Transfer |
Use as a general term for the date materiel is released or transfered |
Use only for Security Assistance materiel release administrative closure to identify the date materiel was released/tendered to the carrier as identified in the Materiel Receipt Acknowledgment. |
8/8 |
|
|
940R |
G6201 |
36 |
Expiration Date |
Use to identify the date after which something is no longer acceptable or valid |
|
8/8 |
|
|
940R |
G6201 |
BF |
Pack Date |
Use to indicate date packed |
Use to identify the date of pack for the lot identified. |
8/8 |
|
|
940R |
G6201 |
BK |
Warranty Expiration |
Use to indicate the date when the materiel warranty expires |
|
8/8 |
|
|
940R |
G6201 |
BL |
Manufacture |
Use to indicate the manufacturing date of the materiel |
|
8/8 |
|
|
940S |
G6201 |
07 |
Effective Date |
Use to indicate when an item or transaction is prepared, becomes effective, or is placed into service |
Use to identify the date of transaction set preparation. This date corresponds to the Universal Time Coordinate (UTC). |
8/8 |
|
|
940S |
G6201 |
80 |
Delivery Requested Scheduled Date |
Use to identify the requested scheduled delivery date |
|
8/8 |
|
|
943A |
G6201 |
07 |
Effective Date |
Use to indicate when an item or transaction is prepared, becomes effective, or is placed into service |
Use to identify the date of transaction set preparation. This date corresponds to the Universal Time Coordinate (UTC). |
8/8 |
|
|
945A |
G6201 |
BB |
Transaction Control Date |
Use to cite the date the transaction was prepared |
Use to identify the date of transaction set preparation. This date corresponds to the Universal Time Coordinate (UTC). |
8/8 |
|
|
945A |
G6201 |
09 |
Process Date |
Use to indicate the date on which a transaction is processed by the relevant activity (either initiating or receiving) |
Use with the transaction history to identify the date on which the materiel release advice was processed by the initiating activity. |
8/8 |
|
|
945A |
G6201 |
11 |
Shipped on This Date |
Use to identify date shipped |
Use in materiel release confirmation, historical materiel release confirmation, disposal release confirmation, and historical disposal release confirmation transactions to identify date materiel was shipped. |
8/8 |
|
|
945A |
G6201 |
17 |
Estimated Delivery Date |
Use for Materiel Obligation Validation (MOV) and excessive quantity verification inquiries to identify the estimated shipping date (ESD) |
Use in materiel release advice (DIC AE6), materiel release confirmation, disposal shipment confirmation (DIC AEJ), historical materiel release confirmation, disposal release confirmation, and historical disposal release confirmation transactions to identify the estimated shipping date or estimated date materiel will be available for shipment when shipment has not occurred. |
8/8 |
|
|
945A |
G6201 |
BD |
Required By |
For security assistance, identifies the required availability date (a calculated date that is derived from the amount of time remaining from the date of requisition until the materiel is required) |
1. Use in materiel release denials to identify the required delivery date from the original materiel release order.
2. Future streamlined data; see introductory DLMS note 4c. |
8/8 |
|
|
945A |
G6201 |
BH |
Offered for Delivery |
Use to identify the date the carrier offered materiel to the storage activity for delivery when it differs from the date materiel was released by the carrier |
Use in materiel release advice and disposal release advice transactions to identify the date materiel is tendered to the carrier for shipment. |
8/8 |
|
|
945A |
G6201 |
BU |
Rejection |
"Use in materiel release denial, historical materiel release denial, disposal release denial, and historical disposal release denial transactions to identify the date of warehouse refusal" |
1. Use in materiel release denial, historical materiel release denial, disposal release denial, and historical disposal release denial transactions to identify the date of warehouse refusal.
2. DLMS enhancement; see introductory DLMS note 4a. |
8/8 |
|
|
945A |
G6201 |
TR |
Transfer |
Use as a general term for the date materiel is released or transfered |
Use in materiel release advice and disposal release advice transactions to identify the date materiel is transferred to the carrier if a delay occurs prior to actual shipment. |
8/8 |
|
|
945A |
G6201 |
36 |
Expiration Date |
Use to identify the date after which something is no longer acceptable or valid |
1. Use for Inter-Service Ammunition to identify the expiration date of the reported item or batch/lot. Authorized DLMS enhancement for inter-service ammunition.
2. DLMS Component unique enhancement (DIC BG1/BG2, rp 9-11). See introductory DLMS note 4f. See ADC 1040. |
8/8 |
|
|
945A |
G6201 |
BK |
Warranty Expiration |
Use to indicate the date when the materiel warranty expires |
1. Use to indicate the date when the materiel warranty expires.
2. DLMS enhancement; See introductory DLMS note 4a. |
8/8 |
|
|
945A |
G6201 |
BL |
Manufacture |
Use to indicate the manufacturing date of the materiel |
1. Use to identify the date of manufacture of the materiel identified.
2. DLMS enhancement; See introductory DLMS note 4a. |
8/8 |
|
|
945A |
G6201 |
BX |
Action |
Use to identify the maintenance due date (the date that maintenance is due on the item) |
1. Use for Inter-Service Ammunition to identify the maintenance due date (the date that maintenance is due on the item). Authorized DLMS enhancement for inter-service ammunition.
2. DLMS Component unique enhancement (DIC BG1/BG2, rp 9-11). See introductory DLMS note 4f. See ADC 1040. |
8/8 |
|
|
947I |
G6201 |
04 |
Purchase Order Date |
Used to indicate the date when a purchase order is created |
|
8/8 |
|
|
947I |
G6201 |
07 |
Effective Date |
Use to indicate when an item or transaction is prepared, becomes effective, or is placed into service |
Use to identify the map effective date. Authorized DLMS enhancement. |
8/8 |
|
|
947I |
G6201 |
09 |
Process Date |
Use to indicate the date on which a transaction is processed by the relevant activity (either initiating or receiving) |
Must use to identify the date on which the inventory adjustment is processed by the initiating activity. |
8/8 |
|
|
947I |
G6201 |
85 |
Date Issued |
The date a drawing or drawing revision was issued |
Use in CAV transactions to indicate a contract date. |
8/8 |
|
|
947I |
G6201 |
BC |
Publication Date |
Use only when requisitioning nonstandard material to cite the manufacturer's catalog publication date when a catalog is identified |
Use to identify the map edition date. Authorized DLMS enhancement. |
8/8 |
|
|
947I |
G6201 |
KA |
Scheduled Service Completion |
Use to indicate the estimated completion date (ECD) for an Dual-Supply Condition Code (Supply Condition Code Change) |
1. Only authorized for use by Commercial Asset Visibility (CAV), CAV-Organic Repairables Module (CAV-ORM); and CAV/CAV-ORM trading partner ICP by mutual agreement. CAV contractor uses to indicate the estimated completion date (ECD) for an Inventory Adjustment (Dual-Supply Condition Code (SCC) Change). Use only with 2/W1901/0200 Quantity Adjustment Reason Code AC with W1916 Inventory Transaction Type Code DU – Inventory Adjustment (Dual) (this equates to functionality of MILSTRAP legacy DIC DAC). In CAV, when the ECD requirement is set to 'Required', the CAV reporter will be required to enter a valid ECD in the inventory adjustment transaction which lets their trading partner ICP know the ECD. Refer to ADC 343 and ADC 461. CAV-ORM will automatically receive an initial ECD at request time and pass that value to its trading partners on a MILSTRAP legacy DIC DAC transaction; any updates to an item’s ECD will be passed to trading partners via the 947I Change ECD Transaction (W1505 Transaction Type Code A5).
2. To change an ECD that was previously provided by an Inventory Adjustment – Dual (SCC change) transaction, use with W1505 Transaction Type Code A5 -Change ECD Transaction. Use of W1505 Transaction Type Code ‘A5’ indicates that only the ECD is being changed by the transaction.
3. Authorized DLMS migration enhancement for use by CAV and CAV-ORM. See introductory DLMS note 4.e. |
8/8 |
|
|
947I |
G6201 |
TR |
Transfer |
Use as a general term for the date materiel is released or transfered |
Use for inventory adjustments resulting from logistics reassignment to identify the effective date of logistics transfer. |
8/8 |