*DLM 4000.25, Volume 2, April 09, 2022*

*Change 14*

**C5. CHAPTER 5**

STATUS REPORTING

C5.1.  SUPPLY AND SHIPMENT STATUS - GENERAL

	C5.1.1.  Status Data.  Status data is either supply status or shipment status.  Sources of supply to include inventory control point (ICP)/integrated materiel manager (IMM) and shipping activities prepare status transactions using the applicable transaction described under paragraphs C5.1.2. and C5.1.4.  Status documents from sources of supply will be forwarded to the Defense Automatic Addressing System (DAAS) for transmission to status recipients.  Status data may be informational or require additional action by organizations based on the assigned status code.  Status recipients include, but are not limited to, requisitioners, storage activities, control offices, and/or monitoring activities. 

		C5.1.1.1.  Supply Status.  Supply status informs organizations of action taken or being taken on materiel requisitioned but not shipped, shipment consignment instructions, or disposition instructions for materiel offered under the materiel returns program (MRP).

		C5.1.1.2.  Shipment Status.  Shipment status informs organizations of the actual shipping dates (such as the date released to the carrier), the release criteria for shipments, or shipment delay notifications.  It also provides for an interface with transportation and for shipment tracing by organizations under DTR 4500.9-R.

		C5.1.1.3.  Item Unique Identification.  

			5.1.1.3.1.  Shipment Status for NSNs containing an IUID Indicator Yes (Y), indicating that DoD Item Unique Identification (IUID) Supply Policy is required, must contain the Unique Item Identifier (UII) and/or serial number for each item when available. See Section C5.1.4.5 for specific shipment status requirements for IUID. 

			C5.1.1.3.2.  Capital Equipment.  In support of Financial Improvement and Audit Readiness (FIAR)***,***accountability and management of capital equipment ***assigned under an established unique Item tracking (UIT) program*** require***s*** serialization data visibility.  Submitters must prepare materiel release confirmation citing the applicable serial number(s) and include the UII when available.[footnoteRef:1] [1:  Refer to ADC 1198] 

		C5.1.1.4.  There are additional processing procedures over and above those contained in this chapter that must be applied for serially managed materiel requiring owner visibility at DLA Distribution Centers.  The identity of the materiel and the additive procedures are in Chapter 30.

	C5.1.2.  Transactions.  This chapter address procedures applicable to supply and shipment status.  The DEDSO Website provides DLMS electronic data interchange (EDI) transaction formats on the DLMS Implementation Convention (IC) page.  The IC page also includes the corresponding MILSTRIP transaction formats by document identifier code (DIC).  The corresponding MILSTRIP legacy 80 record position transaction functionality is identified for information purposes in a mixed DLSS/DLMS environment.

		C5.1.2.1.  Supply Status.  Use the DLMS 870S Supply Status transaction to provide supply status.[footnoteRef:2]   [2:  Organizations furnishing Materiel Returns Program (MRP) supply status will use the DLMS 870M transaction.  DLMS Volume 2, Chapter 11 addresses MRP procedures.] 

			C5.1.2.1.1.  Response to Requisition Transaction is DLMS 870S with Status Report Code 4 – Response to Requisition.  This transaction provides the functionality of MILSTRIP legacy DICs AE1, AE2, AE3, AE8, and AE9.

			C5.1.2.1.2.  Direct Vendor Delivery Supply Status Transaction is DLMS 870S with Status Report Code 5 – Notice of Response to Direct Vendor Delivery.  Used when direct vendor delivery notification is provided as a separate transaction.  This transaction provides the functionality of MILSTRIP legacy DICs AB1, AB2, AB3, and AB8.

			C5.1.2.1.3.  Response to a Supply Assistance Inquiry is DLMS 870S with Status Report Code 6 – Notice of Response to Supply Assistance.

		C5.1.2.2.  Shipment Status Transaction is the DLMS 856S Shipment Status with Transaction Type Code AS – Shipment Advice.[footnoteRef:3]  This transaction provides the functionality of MILSTRIP legacy DICs AS1, AS2, AS3, AS8, and AU1, AU2, AU3, and AU8 for shipment status provided in response to cancellation requests. [3:  Organizations furnishing Materiel Returns Program (MRP) shipment status transactions will use the DLMS 856R transaction.  DLMS Volume 2, Chapter 11 addresses MRP procedures.] 

		C5.1.2.3.  Requisition Inquiry/Supply Assistance Request.  Use a DLMS 869A Requisition Inquiry/Supply Assistance Request transaction to send a requisition follow-up or supply assistance request for an open requisition or cancellation request.

			C5.1.2.3.1.  Shipment Tracing Request Transaction is DLMS 869A with Transaction Type Code 71 – Filing and Search Requests.  This transaction provides the functionality of MILSTRIP legacy DIC AFT.

			C5.1.2.3.2.  Requisition Inquiry Transaction on previously submitted requisitions is DLMS 869A with Transaction Type Code AF – Requisition Follow-Up.  This transaction provides the functionality of MILSTRIP legacy DICs AF1 - AF5.

			C5.1.2.3.3.  Requisition Follow-Up for Improved Estimated Shipping Date Transaction is DLMS 869A with Transaction Type Code AF – Requisition Follow-Up and Product/Item Description (PID) 05, Code 2 to identify requisition follow-up requests for an improved estimated shipping date.  This transaction provides the functionality of MILSTRIP legacy DIC AFC.

			C5.1.2.3.4.  Requisition Follow-Up for Initial Shipping Activity transaction is DLMS 869A with Transaction Type Code AF – Requisition Follow-Up and PID05, Code 1 to identify requisition follow-up requests for the DoDAAC of the initial transportation shipping activity.[footnoteRef:4]  This transaction provides the functionality of MILSTRIP legacy DIC AFY. [4:  The Request for DoDAAC of Initial Transportation Shipping Activity transaction is applicable in a mixed DLMS/MILS environment where a separate transaction is needed to provide the requested information. Under DLMS, the distribution depot identifies the shipping activity in the shipment status transaction, eliminating the need for a follow-up.  Refer to ADC 223.] 

			C5.1.2.3.5.  Request for Supply Assistance Transaction is DLMS 869A with Transaction Type Code AR – Supply Assistance.  There is no equivalent legacy MILSTRIP transaction.

		C5.1.2.4.  Requisition and Cancellation Follow-Up when the source of supply has no record.

			C5.1.2.4.1.  Requisition Follow-Up (No Record).  Use a DLMS 869F Requisition Follow-Up transaction with Transaction Type Code IN – Inquiry to send a requisition follow-up when the source of supply provides Status Code BF in response to a DLMS 869A.  Status Code BF indicates that the source of supply has no record of the requisition.  This transaction provides the functionality of MILSTRIP legacy DICs AT1, AT2, and AT3.

			C5.1.2.4.2.  Requisition Cancellation Follow-Up (No Record).  Use a DLMS 869C Requisition Cancellation transaction with Transaction Type Code AC – Requisition Cancellation to send a requisition cancellation request follow-up when the source of supply provides Status Code BF in response to a DLMS 869C Cancellation Request.  Status Code BF indicates that the source of supply has no record of the cancellation request.  This transaction provides the functionality of MILSTRIP legacy DICs AK1, AK2, and AK3.

	C5.1.3.  Types of Supply Status

		C5.1.3.1.  Supply Status.  Use a DLMS 870S transaction, Supply Status.

			C5.1.3.1.1.  Response to Requisition

				C5.1.3.1.1.1.  Sources of supply (or management control activities (MCA)), processing GFM transactions, use the DLMS 870S with appropriate status codes to convey advice to organizations.  It is used to convey notice of action taken or being taken on requisitions and requisition-related transactions; such as, retransmitted requisitions, cancellations, modifications, and requisition inquiries (follow-ups and/or requests for supply assistance).  Organizations will identify additional status addressees in the original requisition and/or requisition-related transactions, as applicable.  DAAS generates supply status in selected situations resulting from item identification edits but will indicate their RIC as the MESSAGE FROM address in the supply status.

				C5.1.3.1.1.2.  Reporting Status Decisions.  Sources of supply or MCAs will respond to requisition(s) to advise activities of action taken (as indicated), alone or in combination, to any of the requests listed below.  This includes status upon processing a requisition inquiry (follow-up and request for supply assistance) or a cancellation request, and rejection status when rejecting transactions.

					C5.1.3.1.1.2.1.  Backorder.

					C5.1.3.1.1.2.2.  Partial issue or partial other action.

					C5.1.3.1.1.2.3.  Materiel substitution.

					C5.1.3.1.1.2.4   Unit of issue changes.

					C5.1.3.1.1.2.5.  Retransmitted (rerouted) requisitions.

					C5.1.3.1.1.2.6.  Cancellation, modification, or inquiry.

					C5.1.3.1.1.2.7.  Any circumstance that predicts that issue may not be made within the timeframes established for the assigned priority designator (PD).

			C5.1.3.1.2.  Response to Direct Vendor Delivery (DVD).  Sources of supply will use the notice of response to DVD to advise organizations materiel is being supplied by DVD from procurement.  The supply (procurement) source generates this notice for each requisition that is procured for DVD to a consignee.  The DVD, DLMS 870S notice provides a cross-reference between the requisition document number and the contract information.  Organizations may also use information in this notice to report nonreceipt of materiel using the appropriate discrepancy reporting process.

			C5.1.3.1.3.  Response to Supply Assistance.  Sources of supply will use the notice of response to supply assistance to advise organizations of action taken to expedite the shipment of the requested materiel.

			C5.1.3.1.4.  Material Processing Center (MPC) Supply Status

				C5.1.3.1.4.1.  The MPC will provide Status Code NL to notify the Navy ship/customer that materiel has arrived at the MPC for sortation and temporary storage pending delivery to the customer.

				C5.1.3.1.4.2.  The MPC will provide Status Code NW to provide systematic notification materiel has been delivered from the MPC to the Navy ship/customer.

			C5.1.3.1.5.  Air Force Integrated Logistics Solution-Supply (ILS-S) (Retail Supply).  Supply Status DLMS 870S will be used on an intra-Air Force basis to provide the latest status to the intended receiving activity.  Additionally, supply status will be used to support the unique item tracking (UIT) program for positive inventory control (PIC) nuclear weapons related materiel (NWRM) by providing UII and/or serial numbers.  For legacy items where the unique item identifiers (UIIs) have not been marked in accordance with item unique identification (IUID) policy, the serial number alone will be passed.  

				C5.1.3.1.5.1.  DAAS will enable transmission of information copies of the ILS-S Supply Status to the NWRM PIC Fusion Module UIT Registry to ensure the PIC NWRM program has near real time access to UIIs and the associated serial numbers of NWRM item movements.  

				C5.1.3.1.5.2.  DAAS will block transmission of ILS-S Supply Status to non-Air Force recipients where feasible.

				C5.1.3.1.4.3. The receiving MPC will provide Status Code NY to provide systematic notification materiel has been transshipped from the receiving MPC to another destination MPC.

		C5.1.3.2.  Materiel Returns Supply Status.  Organizations and sources of supply will use the DLMS 870M, Materiel Return Supply Status to convey advice to one another as notice of action taken or being taken on Offer of Materiel Reports (OMRs) and OMR-related transactions.  Use the DLMS 870M to send status to the ICPs/IMMs.  The ICPs/IMMs will use the DLMS 870M to provide status or disposition instructions for materiel to organizations, including disposition instructions related to discrepant materiel reported under Chapter 17.  Follow Chapter 11 to determine the processing procedures for and the prescribed usage of this status.

			C5.1.3.2.1.  Unsolicited Report.  Customer organizations will use the unsolicited report to provide status to the source of supply on open OMRs for unshipped materiel.

			C5.1.3.2.2.  Response to Materiel Returns.  Sources of supply will use the DLMS 870M to provide informational status or disposition instructions to organizations for materiel reported under the MRP.

	C5.1.4.  Types of Shipment Status

		C5.1.4.1.  Preparation of Shipment Status.  Shipment status will be provided by the shipping activity or the source of supply for direct vendor delivery (contractor direct) or in response to a requisition follow-up.  The consolidation and containerization point (CCP) and other locations performing consolidation subsequent to issuance of shipment status may also provide shipment status for the purpose of identifying passive RFID.[footnoteRef:5]  Under DLMS, the shipment status will include enhanced data content and support item unique identification (IUID) and intransit visibility requirements as directed under DoD policy/procedures (DoDM 4140.01), when available and pending full DLMS implementation/modernization.  In support of FIAR***,*** accountability and management of capital equipment ***assigned under an established UIT program*** require***s*** serialization data visibility.[footnoteRef:6]  Submitters must prepare shipment status citing the applicable serial number(s) and include the UII when available.[footnoteRef:7]  Shipment status will be provided by the DoD shipping activity, the CCP, or by the source of supply[footnoteRef:8] using the DLMS 856S.  Maintenance activities (organic and commercial) will provide shipment notification to the receiving activity and other interested parties when materiel is shipped to the distribution depot, DLA Disposition Services Field Office, or other designated receiving activity per source of supply/inventory control point guidance.  This may be accomplished using either the DLMS 856S Shipment Status, or the DLMS 856 Advance Shipment Notice (ASN), provided via Wide Area Work Flow (WAWF).[footnoteRef:9]  The DLMS Shipment Status will include asset visibility content, such as IUID, and intransit visibility requirements, such as passive RFID and the TCN as directed under DoD policy/procedures (DoDM 4140.01).  DLMS enhancements include, but are not limited to the following: [5:  Refer to ADC 257, DLMS Shipment Status Generated by Consolidation and Containerization Point]  [6:  Refer to ADC 1198B]  [7:  Refer to ADC 1198]  [8:  Direct vendor delivery shipment status using the 856S includes shipment status prepared by the DLA-sponsored Defense Planning and Management System (DPMS) application.]  [9:  Business rules for use of the 856 for GFM or Property Transfer, including internal DoD transfers, are evolving. Refer to the Defense Pricing and Contracting policy for UID.  Specific applicability and interoperability issues to be resolved by the UID Program Office and ODASD(Logistics).] 

			C5.1.4.1.1.  Passive RFID for the shipment unit/case/pallet associated at the requisition document number level.  The shipment status transaction may identify a hierarchy to clarify the relationship of passive tags within different shipment levels.

			C5.1.4.1.2.  For UIT purposes, the UII (when available) and serial number will be added to the shipment status transaction.  Serial number without the applicable UII may only be used during MILSTRIP/DLMS transition and pending implementation of IUID capability.  Refer to Chapter ***30*** for UIT guidance.

			C5.1.4.1.3.  Under the DoD IUID Supply Policy, the UII and/or serial number (when available) must be added to the shipment status transaction. Serial number without the applicable UII may be used only during MILSTRIP/DLMS transition and pending implementation of IUID capability. Paragraph C5.1.4.5 contains specific procedures to identify the UII in shipment status transactions when the NSN(s) contains the IUID Indicator Y denoting that serialized item management is required.  Capital equipment ***assigned under an established UIT program*** require***s*** serialization data visibility and therefore must cite the serial number and include the UII when available.

			C5.1.4.1.4.  Both the TCN and a secondary transportation number, such as the small package carrier number, when this is applicable.[footnoteRef:10] [10:  Refer to ADC 223, DLMS Shipment Status Enhancements: Secondary Transportation Number, Initial Shipping Activity, Carrier Identification, and POE, approved for phased and staggered implementation.] 

			C5.1.4.1.5.  Identification of the carrier when other than United States Postal Service (USPS) by name and Standard Carrier Alpha Code (SCAC).[footnoteRef:11] [11:  Ibid.] 

			C5.1.4.1.6.  Identification of the initial DoD shipping activity (origin) by DoDAAC.[footnoteRef:12] [12:  Ibid.] 

			C5.1.4.1.7.  For OCONUS shipments made via the Defense Transportation System (DTS), GBL/CBL, parcel post, and small package carrier shipments, specific identification of the POE or CCP.  The shipment status will specify air terminal, water terminal, or CCP by applicable qualifier code in the transaction.  (During MILSTRIP/DLMS transition, DAAS may substitute a generic terminal qualifier for shipment status transactions converted from legacy 80 record position transactions where the type of facility is unknown.)[footnoteRef:13] [13:  Ibid.] 

			C5.1.4.1.8.  Under DLMS, the shipment status will perpetuate data content as applicable:  project code, the special requirements code (legacy MILSTRIP required delivery date (RDD) coded entries, e.g. 999), and priority designator.[footnoteRef:14]  Shipment status applicable to shipment of GFP, including requisitioned GFM and shipment of reparables to/from commercial maintenance, will perpetuate contract data from the MRO, to include the contract number authorizing GFP, and the call/order and CLIN when provided. [14:  Refer to ADC 242, Shipment Status DS 856S:  Priority Designator (PD), Transportation Priority, Project Code, Special Requirements Code, approved for phased and staggered implementation.] 

			C5.1.4.1.9.  The transportation priority will be included in all shipment status transactions as derived under DoDM 4140.01 guidance or other pertinent criteria.[footnoteRef:15] [15:  Ibid] 

			C5.1.4.1.10.  The shipment status may include the unit price (required for Distribution Standard System (DSS)-generated shipment status; otherwise optional).[footnoteRef:16] [16:  Refer to ADC 242A, Inclusion of Unit Price on DLMS Shipment Status (DS 856S).] 

			C5.1.4.1.11.  Product Quality Deficiency Report (PQDR) Exhibit Tracking  

				C5.1.4.1.11.1.  When shipment status is prepared for shipment of a PQDR exhibit, the shipping activity will perpetuate the PQDR Report Control Number (RCN) from the MRO to the shipment status and designate a copy of the receipt transaction for distribution to the Product Data Reporting and Evaluation Program-Automated Information System (PDREP-AIS).  

				C5.1.4.1.11.2.  DAAS will recognize the inclusion of the PDREP-AIS DoDAAC in the shipment status and forward a copy of the shipment status for use in exhibit tracking.

		C5.1.4.2.  Shipment Status from the CCP or Other Locations Performing Consolidation.  Shipment status will be provided by the CCP or other locations performing consolidation subsequent to the original issuance of shipment status, for the primary purpose of providing updated RFID information.  This in turn supports intransit asset visibility and receipt processing.  Other locations include distribution depots performing consolidation of local deliveries resulting in passive RFID updates.

			C5.1.4.2.1.  Preparation of the CCP/Consolidation Shipment Status

				C5.1.4.2.1.1.  The CCP/consolidation shipment status will be identified by a unique code in the transaction and will include the information as describe below.

				C5.1.4.2.1.1.1.  Ship-To-Activity. This activity will be explicitly identified.

					C5.1.4.2.1.1.2.  Lead TCN.  This TCN may differ from that on the original shipment status.

					C5.1.4.2.1.1.3.  RFID Tag Value.  When applicable, the transaction will contain multiple passive RFID tag values using a hierarchical structure.  The original passive RFID will be repeated when it is available.  Any additional tag values available will also be provided.  

					C5.1.4.2.1.1.4.  Transaction Originator,  This will identify the routing identifier code (RIC) of the ICP perpetuated from the original shipment status.

					C5.1.4.2.1.1.5.  Consolidation Activity.  This will identify the DoDAAC of the location where the consolidation occurred, e.g. CCP or depot performing local delivery manifesting.

					C5.1.4.2.1.1.6.  Shipment Date.  This will be the CCP/consolidation point shipment date.

					C5.1.4.2.1.1.7.  Mode of Shipment.  This will be the mode shipped by the CCP/consolidation point.

					C5.1.4.2.1.1.8.  IUID Data.  UII and/or serial numbers (when available) must be included for NSNs with an IUID Indicator Y.  Capital equipment ***assigned under an established UIT program*** require***s*** serialization data visibility and therefore must cite the serial number and include the UII when available.  Requirements for including the UII in the CCP/Consolidation Shipment Status are provided in C5.1.4.5.

				C5.1.4.2.1.2.  Shipment status information content may be repeated from the original shipment status when this information is available, (e.g., when the original shipper was a co-located distribution depot).  Where access to the original shipment status information is not available, the original data content will not be perpetuated and applicable data fields will not be populated.

			C5.1.4.2.2.  DAAS Distribution of CCP/Consolidation Shipment Status.  DAAS will route the CCP/consolidation shipment status to the ship-to activity.  Standard DAAS business rules for distribution of the shipment status to status recipients do not apply.  In addition, DAAS will not distribute the CCP shipment status to Distribution Depot ship-to locations or Material Processing Center (MPC) locations supported by DSS.

			C5.1.4.2.3.  Use of the CCP/Consolidation Shipment Status by the Receiving Activity.  The value of this transaction to the receiving activity is to support passive RFID-enabled receipt processing.  DLMS applications not supporting passive RFID may disregard this status or choose to append the mode of shipment and the shipment date.  New content on the CCP/consolidation shipment status should not be viewed as replacement values for a previously received shipment status matching on document number/suffix.  Since there may not be a match on the previously identified TCN, the CCP/consolidation shipment status information will be handled in a way that does not impact quantity due or visibility of partial shipments that may not have been consolidated within the reconfigured shipment.

		C5.1.4.3.  Shipment Status for Local Delivery Manifested, Outbound MILSTRIP Shipments on Behalf of On-Base Customers, Re-warehousing actions/transshipments between Distribution Depots in support of ‘Home’ Industrial Activity and ‘Forward Support’ Industrial Activity site materiel requirements, and non-MILSTRIP Shipments (e.g., DD Form 1149) to Off-Base Customers, with Passive RFID.  For shipments prepared by the transportation office that are local delivery manifested, material processing center (MPC) deliveries, outbound MILSTRIP shipments on behalf of on-base customers, re-warehousing actions between distribution depots, and outbound non-MILSTRIP shipments (e.g., DD Form 1149) to off-base customers, the shipment status will be prepared in accordance with paragraph C5.1.4.1 using a DLMS 856S, Shipment Status, to include identifying the passive RFID information and associating the tag data to the document number of the item(s) to be transshipped or cross-docked.

			C5.1.4.3.1.  For local delivery manifested shipments, MPC deliveries, and outbound MILSTRIP shipments for On-Base Customers, the  DLMS 856S will contain the transaction status reason code (BSN07 = 091 Transship/Cross-dock Shipment Status (non-CCP)) to denote that the shipment status is being provided by a location performing transshipping/cross-docking subsequent to the original shipment.  The RIC From will be the RIC of the activity executing the local delivery manifest.  The remaining data elements for a shipment status transaction will be ascertained from the pack list/shipping documentation accompanying the shipment.  If the shipment already has a pRFID tag on it, no additional  DLMS 856S is required; the existing pRFID tag will just need to be read and an XML Visibility transaction sent to DAAS recording the tag read event.  If there is no document number either on the inbound data or on the pack list/shipping documentation, then do not generate the DLMS 856S for conveying the pRFID tag.  This is to preclude a mismatch of data with the original DLMS 856S transmitted by the ICP, that will have a document number.

			C5.1.4.3.2.  For re-warehousing actions/transshipments between distribution depots in support of ‘Home’ Industrial Activity site and ‘Forward Support’ Industrial Activity site materiel requirements, a normal DLMS 856S will be generated and transmitted to DAAS.  This transaction will carry the normal shipment status message data, along with the pRFID tag identification numbers and any extended transportation data (e.g., bill of lading number, commercial carrier tracking numbers).  Since there will never be a materiel receipt acknowledgement (MRA) for these re-warehousing actions/transshipments between the Home and Forward Industrial Activities, a status reason code (BSN07=048 Industrial Activity Re-Warehousing/Transship Shipment Status) will be included so that DAAS can flag these  DLMS 856S instances and prevent them from triggering the MRA Report.

			C5.1.4.3.3.  For outbound non-MILSTRIP shipments documented on a DD Form 1149, a DLMS 856S will be created.  Table C5.T1 lists the minimum data elements that must be included in the shipment status message; sources of the data are the DD Form 1149 and pRFID tag information.  Shipment status applicable to shipment of GFP will perpetuate all GFP contract data from the shipping documentation, to include the contract number authorizing GFP, and the call/order and CLIN when provided.  For NSNs containing the IUID Indicator Y, include the UIIs and/or serial number(s) for each item when available.  Capital equipment ***assigned under an established UIT program*** require***s*** serialization data visibility and therefore must cite the serial number and include the UII when available.

			C5.1.4.3.4.  DAAS Distribution of Shipment Status for Local Delivery Manifested, Deliveries to MPC, Outbound MILSTRIP Shipments on Behalf of On-Base Customers, and  non-MILSTRIP Shipments (e.g., DD Form 1149) to Off-Base Customers.  DAAS will route the shipment status to the ship-to activity.  Standard DAAS business rules for distribution of the shipment status to status recipients do not apply.  

			C5.1.4.3.5.  DAAS Distribution of Shipment Status for Re-warehousing actions/transshipments between Distribution Depots in support of ‘Home’ Industrial Activity and ‘Forward Support’ Industrial Activity site materiel requirements.  DAAS will route the shipment status according to standard DAAS business rules for distribution of the shipment status to status recipients.

			C5.1.4.3.6.  Receiving Activity Use of Shipment Status for Local Delivery Manifested, Deliveries to MPC, Outbound MILSTRIP Shipments on Behalf of On-Base Customers, Re-warehousing actions/transshipments between Distribution Depots in support of ‘Home’ Industrial Activity and ‘Forward Support’ Industrial Activity site materiel requirements, and non-MILSTRIP Shipments (e.g., DD Form 1149) to Off-Base Customers.  The value of this transaction to the receiving activity is to support passive RFID-enabled receipt processing.  DLMS applications not supporting passive RFID may disregard this status or choose to append the mode of shipment and the shipment date.  New content on the shipment status should not be viewed as replacement values for a previously received shipment status matching on document number/suffix.

		C5.1.4.4.  Shipment Status Materiel Returns.  The DLMS 856R, Shipment Status Materiel Returns, will be used to prepare a shipment status and be submitted promptly to the ICP/IMM after materiel directed for return is released to the carrier.  Refer to Chapter 11 for materiel returns program procedures.  Shipment status for materiel returns will include the TCN, shipment date, mode of shipment, and quantity shipped.  It will perpetuate data content from the DLMS 180M automatic return notification or the ICP/IMM DLMS 870M reply to the customer’s asset report and shipping information, as applicable, per guidance in the DLMS Supplements.  The DLMS 856R shipment status will include asset visibility content and intransit visibility requirements as directed under DoD policy/procedures (DoD 5-11.1-R).  DLMS enhancements include, but are not limited to, the following:

			C5.1.4.4.1.  Passive RFID for the shipment unit/case/pallet associated at the document number level.  The shipment status transaction may identify a hierarchy to clarify the relationship of passive tags within different shipment levels.

			C5.1.4.4.2.  For UIT purposes, the IUID and/or serial number.  Serial number without applicable IUID may be used during MILSTRIP/DLMS transition and pending implementation of IUID capability.  Refer to Chapter 19 “Procedures For Serially Managed Materiel Requiring Owner Visibility”, for UIT guidance.

			C5.1.4.4.3.  Both the TCN and a secondary transportation number, such as the small package carrier number, when this is applicable.

			C5.1.4.4.4.  Identification of the carrier, when other than USPS, by SCAC.

			C5.1.4.4.5.  Specific identification of all parties associated with the materiel return.  This includes the party to receive credit when different from the document number DoDAAC (previously carried in the MILSTRIP supplementary address) and all parties to receive status.  Transition to use of specifically identified parties facilitates full DLMS implementation, by enabling identification of multiple different activities (e.g. submitter, ship-from, credit-to, status-to).  Prior coordination for this DLMS enhanced capability is required.

		C5.1.4.5.  Item Unique Identification Shipment Status

			C5.1.4.5.1.  UII and/or Serial Number on Shipment Transactions.  For NSNs that contain the IUID Indicator Y, storage activities (or initial shipping activity) will provide the UII and/or serial number, on outbound shipment status using the DLMS 856S transaction.  If the UII is not available provide the serial number if available. The long-term end state goal is to rely on the UII only.  Table C5.T2 shows the decision matrix that applies to scenarios where the UII and/or serial number may not be available when the item is being shipped.  The overriding vision is that, pending full transition to DoD IUID Supply Policy using the UII, processing of outgoing shipments does not stop due to lack of a viable UII and/or serial number when the NSN contains an IUID Indicator Y.  Capital equipment ***assigned under an established UIT program*** require***s*** serialization data visibility and therefore must cite the serial number and include the UII when available**.**

Table C5.T2. Shipment Decision Matrix

C5.1.4.5.2.  Applicability.  The requirement applies to shipments originated by the storage activity in receipt of any of the following directions to pick, pack, and ship:  Materiel Release Orders (MRO), Lateral Redistribution Orders (LRO), or Redistribution Orders (RDO).  The scope includes materiel shipped under MILSTRIP business rules, as well as non-MILSTRIP shipments documented on a DD 1149, Requisition and Invoice/Shipping Document, when DLMS Shipment Status is provided.

			C5.1.4.5.3.  Issue Release/Receipt Document.  Shipping activities will prepare the Issue Release/Receipt Document (IRRD), when applicable, in accordance with DLM 4000.25, Volume 2, Appendix 6.35 and 6.36, providing the UII(s) and/or serial number(s) of the items shipped using automated information technology (AIT).

			C5.1.4.5.4.  Due In Record.  Receiving activities will use the UIIs and/or serial numbers in the shipment status to create or update the due-in record.  This information will be used to verify the UIIs actually received.  Receiving activities will follow the supply discrepancy reporting procedures to report mismatches as appropriate.

			C5.1.4.5.5.  Scenarios for Including the UII in the Shipment Status. Capital equipment ***assigned under an established UIT program*** require***s*** serialization data visibility and therefore must cite the serial number and include the UII when available.

				C5.1.4.5.5.1.  Shipment Status Subsequent to a Materiel Release Order.  Initial shipment status normally is prepared by the storage site on behalf of the materiel owner.  When the material is shipped, the shipping activity will prepare and transmit a DLMS 856S with UII(s) and/or corresponding serial numbers, under DoD IUID Supply Policy requirements to  DAAS.  For this scenario and the others to follow, the Defense Automatic Addressing System (DAAS) will route the shipment status to the designated status recipients per standard MILSTRIP distribution rules and to any additional parties as identified in the transaction.

				C5.1.4.5.5.2.  Shipment Status Subsequent to a Redistribution Order.  Initial shipment status is normally prepared by the storage site.  When materiel is shipped, the shipping activity will prepare and transmit the 856S to the designated receiving activity including UII and/or corresponding serial numbers, under the requirements in DoD IUID Supply Policy.

				C5.1.4.5.5.3.  Shipment Status Subsequent to a Direct Vendor Delivery.  The source of supply is responsible for providing shipment status for materiel shipped directly by the vendor to the customer.  Under this scenario, the source of supply will NOT provide IUID content on the DLMS 856S.  Instead, it is anticipated that the receiving activity will be fully DLMS compliant and will receive a copy of the Wide Area Workflow (WAWF) Advance Shipment Notice (856) containing the IUID data content.  There is no requirement for redundant transmission of IUID data to the receiving activity.

				C5.1.4.5.5.4.  Shipment Status Subsequent to a Lateral Redistribution Order with Distribution Code 2 or 3.  The LRO is a request by the manager to redistribute retail stock identified through retail level reporting or access to a retail asset visibility system.

					C5.1.4.5.5.4.1.  In response to the LRO, the shipping activity will prepare and transmit the 856S (DIC AS6) to the originator of the LRO.  The shipping activity will include IUID content, Distribution Code 2 or 3, and identification of the ship-to activity.  

					C5.1.4.5.5.4.2.  When the LRO shipment status (DLMS 856S (DIC AS6)) contains IUID content, DAAS mapping will be used to prepare a DLMS 856S to perpetuate the IUID content to the ship-to activity.  DAAS, at a minimum, will indicate the following:

•		DIC AS1 if the ship-to activity is the requisitioner.  If the ship-to activity is not the requisitioner, then indicate DIC AS2.  The ship-to will be perpetuated from the DLMS 856S (DIC AS6).

•	The RIC-To from the DLMS 856S (DIC AS6) becomes the RIC-From in the DLMS 856S (DIC AS1) (indicating that the shipment status is provided on behalf of the manager).

•	Distribution Code  2 or 3 

•	UIIs and/or serial numbers 

•	Signal Code B used in the LRO will NOT be perpetuated.

•	The Supplemental Data field will NOT be perpetuated.  

					C5.1.4.5.5.4.3.  Upon receipt of the DLMS 856S (DIC AS6), the manager will then generate the shipment status 856S (DIC AS8), without UIIs and with the distribution code from the original requisition and send to DAAS, who will route it to status recipients under MILSTRIP distribution rules and to any additional parties as identified in the transaction.

					C5.1.4.5.5.4.4.  The customer supply system must ensure that the shipment status provided by the manager without UIIs does not overlay the LRO shipping activity's shipment status with UIIs.  The Distribution Code 2 or 3 may be used to recognize the LRO shipping activity shipment status.  

				C5.1.4.5.5.5.  Shipment Status Subsequent to a Disposal Release Order (DRO).  In response to directed release of property to a DLA Disposition Services Field Office, the shipping activity will provide shipment status including UII and/or corresponding serial numbers, under the requirements in DoD IUID Supply Policy.

				C5.1.4.5.5.6.  Shipment Status in Response to a Follow-Up.  The source of supply will follow current MILSTRIP procedures to prepare the shipment status transaction based on the Materiel Release Confirmation (DLMS 945A) under DoD IUID Supply Policy.  Since the MRC does not contain IUID data, no UII/serial numbers will be in the source of supply shipment status transaction. 

				C5.1.4.5.5.7.  Shipment Status Prepared by Consolidation and Containerization Point (CCP) or Other Locations Performing Consolidation.  When the CCP or other location performing consolidation prepares the shipment status, it will include the UII and/or serial number based on DoD IUID Supply Policy.  CCP eligibility will not be altered based on the requirement to include the IUID data.

				C5.1.4.5.5.8.  Shipment Status on Multiple Freight Pieces.  For a shipment containing IUID content and shipped in multiple freight pieces, shippers are NOT authorized to execute the movement of the shipment using multiple freight piece procedures (e.g., citing the same TCN for all boxes).  Those shipments must be “partialled” by using the 16th position of the TCN to uniquely identify each freight piece.  A separate DLMS 856S Shipment Status will be transmitted for each document number – partial TCN pair, identifying the contents of each freight piece, to include pRFID tag(s) and UII(s) and/or serial numbers.

				C5.1.4.5.5.9.  Non-MILSTRIP Shipments Documented on a DD 1149.  When the shipping activity is requested to ship material documented by a DD 1149, Requisition and Invoice/Shipping Document, see paragraph C5.1.4.3.3. for procedures associated with the construct of the DLMS 856S Shipment Status.  To add the UII and/or serial number data, key aspects of the HL looping of the 856S are:

					C5.1.4.5.9.1.  The first HL loop is allocated to addressing and the second HL loop is allocated to the shipment.  If there is pRFID at the carton level, it will be passed in the third HL loop, which will be a pack loop.

					C5.1.4.5.9.2.  To identify the UIIs and/or serial numbers, use separate HL item loops to identify the UII and/or serial number information.  If there is pRFID at the item level, the pRFID tag information will be passed in a REF segment within the applicable item loop to which it applies.  A separate HL item loop will be generated for each item.  If there is a pack loop, then the item loop will identify the associated pack loop as its parent in the HL02; if there are no pack loops, then there will be no HL02.	

		C5.1.4.6.  Shipment Status Message Changes/Updates. In the event a shipment does not get lifted as originally intended (e.g., shipment is left off the truck) and the shipment is re-booked, the activities (e.g., shippers, ICPs) that originate the DLMS 856S shipment status transaction will send an updated transaction with all of the changed transportation information. The shipment status update can also be used to convey updated passive RFID tagging information, if it changed from the original erroneous submission.  Examples of changed transportation information includes transportation method code, SCAC, ship date, bill of lading information, and tracking information.

			C5.1.4.6.1.  Preparation of the Shipment Status Change/Update

				C5.1.4.6.1.1.  The shipment status change/update message will be identified by a unique code (BSN02 = RR) in the transaction to flag it as an updated shipment status message. 

				C5.1.4.6.1.2.  It will convey a new Status Reason Code (BSN07 = A40) to advise the shipment status recipient that the updated shipment status transaction corrects erroneous content data (e.g., transportation data, pRFID data).

				C5.1.4.6.1.3.  It will repeat the shipment status information from the original shipment status message, in addition to any changes to the original information.

				C5.1.4.6.1.4.  It will convey updated passive RFID information if it has changed from the original erroneous submission. When applicable, the transaction will contain multiple passive RFID tag values using a hierarchical structure.  The original passive RFID will be repeated when it is available.  Any additional tag values available to the shipment status recipient will also be provided.

				C5.1.4.6.1.5.  It will convey changed transportation information (e.g., transportation method code, SCAC, ship date, bill of lading information, and tracking information). 

			C5.1.4.6.2.  DAAS Distribution of Shipment Status Change/Update.  DAAS will route the shipment status change/update to the shipment status recipient per standard business rules for distribution of the shipment status.  

DAAS will not distribute the shipment status change/update to MILSTRIP legacy recipients. 

			C5.1.4.6.3.  Use of the Shipment Status Change/Update by the Receiving Activity.  The value of this transaction to the receiving activity is to provide corrected transportation data and to support passive RFID-enabled receipt processing.  DLMS compliant systems’ receiving applications should handle the updated transactions as the official shipment status, since they carry the corrected data. 

	C5.1.5.  Requesting Status

		C5.1.5.1.  Purpose.  Use the DLMS 869F Requisition Follow-Up to request status on a previously submitted requisition.

		C5.1.5.2.  Organizations Receiving Status.  To ensure sources of supply automatically provide status data to all organizations required to receive supply and/or shipment status, identify all additional organizations to receive status in the initial requisition or in requisition related transactions.  To obtain status on previously submitted requisitions or cancellation requests, activities may submit follow-ups.

		C5.1.5.3.  Reports.  The DoD Components will submit reports when requisition status reporting is required to designate status of a project.  Obtain special reports, when required, from an eligible recipient of status identified in requisitions.  Special reports are not required from the inter-DoD Component sources of supply.

		C5.1.5.4.  Status Code CA.  When Status Code CA is received in response to a follow-up request and no record of the previous Status Code CA and the reasons for rejection can be located, authorized status recipients may inquire off line, such as via mail, message, or telephone, to the source of supply to obtain reasons for rejection.

	C5.1.6.  Status Recording.  Organizations will promptly record all status information received (automatically and/or in response to requisition inquiries) to applicable due-in records and/or requisition history (status) files, and, in the case of the DLA Disposition Services, the disposal suspense file.  Status recipients will use supply status data to establish or update the due-in record to monitor for materiel receipts under Chapter 13.  In addition, status recipients will:

		C5.1.6.1.  Give particular attention to the supply status transaction date to ensure that records/files are updated in the proper chronological order/date sequence.

		C5.1.6.2.  Review the DLMS 870S received for any additional action required by the status code if any.  

			C5.1.6.2.1.  If supply status identifies a processing delay due to storage site denial to the source of supply’s materiel release order (Status Code BD with Management Code R), the customer/customer’s system will update/clear the local record for the suffix and quantity identified (so that later status on a next available suffix is not misinterpreted as duplicative/exceeding the quantity ordered, potentially triggering cancellation).  Estimated shipping dates will not be provided with BD status when associated with storage activity denial as indicated by Management Code R.  Further supply action to satisfy the denied quantity will be identified on later supply status transactions under the next available suffix code.  Use of Status Code BD with Management Code R allows the customer’s system to better track status and recognize the correct quantity in process.

			C5.1.6.2.2.  If a requisition has been rejected with a rejection status code, and the materiel is still required, the requirement will be submitted as a new requisition with a new document number and a current transaction date.

		C5.1.6.3.  Treat shipment status received as notice shipment has been made and that additional follow up will only result in receipt of another shipment status document.

		C5.1.6.4.  Anticipate receipt of materiel within prescribed Uniform Materiel Movement and Issue Priority System (UMMIPS) timeframe for the assigned PD, or the RDD cited in the requisition, upon receipt of supply status without an estimated shipping date (ESD).

		C5.1.6.5.  Evaluate status already received prior to submitting requisition inquires to follow up for additional status.

		C5.1.6.6.  Ensure appropriate status is sent to other activities requiring status when the only status recipient is the activity identified by a distribution code.

	C5.1.7.  Sending Status - General

		C5.1.7.1.  Requirements.  Sources of supply will automatically send a DLMS 870S when processing requisitions, redistribution orders (RDOs), cancellations, modifications, and requisition inquiries (follow-ups and requests for supply assistance).  MCAs will send reject status for requisitions they process.  Sources of supply will maintain and send current supply status as provided below.  For these purposes, MCAs and sources of supply will maintain accessible requisition history records for a minimum of 6 months after completing a shipment of materiel or canceling a requisition, to provide for timely status responses.  MCAs will maintain requisition history records until contract termination.

		C5.1.7.2.  Associated Transaction Status.  Sources of supply initiated requisition status will include all status transactions (supply and shipment) generated during source of supply processing that are not produced in response to requisition inquiries or cancellation requests.

		C5.1.7.3.  Normal Requisitioning Processing.  The sources of supply will provide supply status based on normal requisition processing, including additional supply status due to changes in requisition processing, such as, cancellation actions, modifications, item substitutions, DVD actions, changes in ESDs (when retransmitting requisitions to another source of supply), and requisition inquires (follow-ups and requests for supply assistance).  In addition, supply sources will send:

			C5.1.7.3.1.  A DLMS 870S with Status Code BB (citing the scheduled ESD for release of materiel from stock to the customer) when backordering a requisition against a due-in to stock.  The source of supply will always send additional Status Code BB to organizations with a revised ESD when adjusting shipping dates.

			C5.1.7.3.2.  A DLMS 870S with Status Code BZ with an ESD after deciding to process the requirement as a DVD shipment.  Sources of supply will give Status Code BV after effecting contracts or procurement actions and establishing an agreed to contract shipping date.  Status Code BV must contain contract shipping date and also the contract data that provides organizations with a cross-reference to the original requisition.  At a minimum, contract data will include the contract number, call/order number, notification of destination/origin acceptance, allowable quantity variances, and identification of the contractor by CAGE.  The contract required shipping date will be discretely identified and may be equal to the estimated shipment date.  Additional contract data may be included as available.[footnoteRef:17] [17:  Refer to ADC 465, Contract Data for 870S_BV Status] 

			C5.1.7.3.3.  A DLMS 870S with additional Status Code BV with a revised ESD to organizations when adjusting contract shipping dates on items scheduled for DVD.

		C5.1.7.4.  Manual Requests.  The source of supply may reject a requisition, or initiate a manual off-line request to obtain additional information, when the requisition contains insufficient information to continue processing.  Use the STATUS TO organization identified in the requisition as the action addressee on all requests for additional information.  Treat other organizations identified in the requisition, not designated as STATUS TO organizations, as information addressees on requests for additional information.  When an inquiry for additional information is made, the source of supply will send a DLMS 870S with Status Code BD, to all designated STATUS TO organizations.  Sources of supply will suspend further action on requisitions awaiting additional information until a response is received or until 30 calendar days from date of inquiry, whichever occurs first.  Upon receipt of requested information, the source of supply will continue normal processing.  If the organization does not provide needed information within 30 calendar days, the source of supply will reject the requisition using a DLMS 870S with Status Code D3.

		C5.1.7.5.  Status Frequency.  For each reinstated requisition, retransmitted (rerouted) requisition, requisition modifier, and Materiel Release Order (MRO) processed, sources of supply will automatically send supply and/or shipment status, as appropriate.

			C5.1.7.5.1.  Shipment Status to DAAS.  Sources of supply will transmit shipment status to DAAS for all source of supply requisitions to include a DLMS 856S for all DVDs, as required.  Upon receipt of shipment status, DAAS will convert the shipment status to the appropriate type of status and make distribution.  Except for cancellation and rejections, DAAS will send status to designated status recipients as identified by a significant media and status code (DoD or Component level), a significant distribution code and to any activity identified by RIC as a party to receive status.  Sources of supply will give shipment status for exception ship-to addresses.[footnoteRef:18]  As of April 1, 2014, the inclusion of a country code not valid with the current Geopolitical Entities, Names, and Codes (GENC) Standard will result in the transaction being rejected by DAAS using the DLMS 824R Reject Advice citing Reject Advice Code AU.[footnoteRef:19] [18:  Refer to ADC 242B.]  [19:  Refer to ADC 1075.] 

				C5.1.7.5.1.1.  Material Processing Center (MPC) Shipment Status.  DAAS will also provide a copy of shipment status for materiel to be delivered to any customer supported by a MPC operated by DLA Distribution at the co-located DLA Distribution Center receiving site.  In order to accomplish this, DAAS will maintain a table of DoDAACs associated with a particular copy of DSS as identified by DLA Distribution that the copy of DSS MPC supports.  DLA Distribution, in coordination with the Service, will provide updates to DAAS as needed.  When DAAS processes the DLMS 856S/AS8 and the ship-to DoDAAC begins with N, R, V, Z, M, or as otherwise identified, DAAS will match the ship-to DoDAAC to the MPC table.  When an appropriate DSS DoDAAC for MPC support is identified, shipment status will be forwarded to the DSS for establishment of pre-positioned materiel receipt (due-in) record at the applicable MPC.

				C5.1.7.5.1.2.  MPCs receiving shipment status are located at the distribution center locations identified in Table C5.T3.

				C5.1.7.5.1.3.  The MPC will use the ship-to DoDAAC, mark-for party project code, special requirements code, and transportation priority or priority designator from the due-in record or the shipment documentation to sort materiel for delivery per the Navy customer direction.

			C5.1.7.5.2.  Status of Unconfirmed Materiel Release Orders.  Sources of supply will send DLMS 856S transactions to DAAS in accordance with C5.1.7.5.1.  DAAS will send this status to the ship-to activity.  If DAAS cannot determine the ship-to activity, DAAS will return the transaction to the ICP for handling.  DAAS will route the pseudo shipment status transaction for SA requisitions to the applicable DoD Component International Logistics Control Office (ILCO).

		C5.1.7.6.  Turn-In Document Status.  For each shipment ***to DLA Disposition Services using the disposal turn-in document number (DTID), the shipping activity/storage location will provide a DLMS 945A, Disposal Release Confirmation to the materiel owner/source of supply and provide the shipment status to DLA Disposition Services.  For shipments to DLA Disposition Services, the supply condition, and other mandatory data elements for the shipment status are identified in Chapter 16***.

		C5.1.7.7.  Requisition/Reinstatement for Backorder.  When a requisition or reinstatement of a requisition is to be backordered against due-in to stock, sources of supply will furnish exception supply status.  Sources of supply will send Status Code BB and the ESD for release of materiel from stock to the customer.  Sources of supply will send Status Code BB to the customer with the revised ESD when shipping dates are adjusted.

		C5.1.7.8.  Exception Status.  Sources of supply will send a DLMS 870S Exception Supply Status when the intent to process for DVD is known.  This exception status will contain Status Code BZ and the ESD.  When contracts or procurement actions have been effected and an agreed to contract shipping date is established, sources of supply will send additional Status Code BV indicating the contract shipping date.

		C5.1.7.9.  Contract Shipping Date Adjustment.  When contract shipping dates are adjusted on items scheduled for DVD, the source of supply will provide a DLMS 870S with Status Code BV to indicate the revised shipping date.  Sources of supply use the DVD notice DLMS 870S to notify organizations of materiel being supplied by DVD.  This notice provides a cross-reference between the document number and contract data.  When delivery dates are established for DVD shipments, the source of supply will provide the DVD notice in addition to supply status.

		C5.1.7.10.  Indicating Processing Delay.  Sources of supply will furnish supply status indicating a processing delay when an MRO is denied by the storage activity.  Use Status Code BD and denial Management Code R citing the MRO denied quantity and suffix.[footnoteRef:20]  Further supply action to satisfy the denied quantity is anticipated to occur on a later suffix code. [20:  Authorized for use on an intra-Army basis (ADC 191) and later expanded to inter-Service/Agency use (ADC 312).  Not implemented by DLA and other Components.] 

		C5.1.7.11.  Mandatory Status Reporting.  The use of supply and shipment status is mandatory for all source of supply initiated requisition statuses.  Supply source initiated requisition status includes all statuses generated during source of supply processing not produced in response to follow-ups or cancellation requests.  Use of supply and shipment status in response to cancellation requests is optional when supply status distribution rules require multiple recipients of status.  Upon receipt of a DLMS 856S, DAAS will convert the request to the appropriate response transactions and make distribution to all eligible status recipients.

		C5.1.7.12.  Preparation of Status

			C5.1.7.12.1.  Late Delivery.  All supply status transactions, indicating materiel will be released for shipment later than the standard delivery date (SDD) or RDD/required delivery period (RDP) must contain an ESD.  Such supply status is applicable to materiel obligations including procurement for DVD.  Conversely, the source of supply will reject requisitions that contain Advice Code 2C, 2J, 2T, or 2W with Status Code CB when items are not available for immediate release or cannot be supplied by the SDD/RDD/RDP, with a DLMS 870S.

			C5.1.7.12.2.  Estimated Shipment.  ESDs are also mandatory entries for those transactions reporting adjusted ESDs and any circumstance that predicts that issue may not be made within the timeframes established for the PD.  Storage facilities in receipt of requisition inquiries on requirements that are in the process of being filled will use supply status to provide ESDs to the requesting source of supply.  Status transactions providing advice of such events as changes in stock numbers, unit of issue changes, rejections, and shipments will not contain an ESD.

			C5.1.7.12.3.  Rejecting Requisitions.  Sources of supply will use a DLMS 870S with status codes in the C and D series when rejecting requisitions and RDOs.

			C5.1.7.12.4.  Processing Point Response.  Processing points provide a DLMS 856S in response to receipt of a DLMS 869F, Requisition Follow-up, containing the DoDAAC of the initial (origin) transportation activity.  If the processing point is unable to provide the DoDAAC information to the requesting activity, the follow-up transaction will be rejected with Status Code DY.

			C5.1.7.12.5.  Requisition Inquiry.  Status furnished by a DLMS 870S in response to a DLMS 869A, Requisition Inquiry, will contain the most current information available regarding the status of the requisition.  Supply status in response to a requisition inquiry will contain a changed/new ESD, when applicable, and a transaction date that corresponds to the date of the reply.  A DLMS 856S in response to a requisition inquiry will contain the shipping data for the materiel shipped.

			C5.1.7.12.6.  Narrative Explanation.  Status Code CA and TD are the only status conditions to which the source of supply will provide a narrative explanation (in a free-form format) identifying the reason for rejection.  

			C5.1.7.12.7.  Abbreviated Messages.  The DoD Components may opt to use abbreviated status to activities.

			C5.1.7.12.8.  Cancellation Request.  A DLMS 870S with Status Code BF sent in response to cancellation requests, with a document number not matching source of supply records, prevents source of supply processing of later transactions for this same document number.  When providing Status Code BF in response to a cancellation request, also provide Status Code BF in response to all other transactions received containing the same transaction reference number.  Sources of supply will retain accessible history records of Status Code BF generated from processing no-record cancellation requests following the generation of Status Code BF in accordance with DoD 5015.02, DoD Records Management Program.

			C5.1.7.12.9.  Materiel Returns Status.  Use Chapter 11 procedures for providing materiel returns supply status transactions resulting from processing OMRs and OMR-related transactions.

			C5.1.7.12.10.  Free Issue.  Requisitions that fail free issue validation will be rejected with Status Code CM; a new funded requisition may be submitted if the materiel is still required.  Requisitions that fail free issue validation after materiel release (post-post requisitions/issue) may be handled as funded requirements.  In this case, the source of supply will furnish Status Code DT alerting eligible status recipients that the post-post requirement is not authorized for free issue and to adjust fund obligation records as materiel will be billed to the requisitioner.

				C5.1.7.12.10.1.  Where a post-post requisition contains a free issue Signal Code D or M and free issue is not authorized, the signal code will be modified to the applicable billable signal code.  Where the original requisition identified a valid fund code, it will be used for billing; otherwise, the fund code will be modified to indicate non-interfund billing (Fund Code XP):

					C5.1.7.12.10.1.1.  Signal Code D will be replaced with Signal Code A to show the correct shipping activity.  (Both D and A ship-to the requisitioner as identified in the document number of original submission.)

					C5.1.7.12.10.1.2.  Signal Code M will be replaced with Signal Code J to show the correct shipping activity.  (Both M and J ship-to the supplementary address identified in the original submission.)

				C5.1.7.12.10.2.  Since post-post orders are already shipped and cannot be split, if part of the quantity ordered is not eligible for free issue, the entire order will be denied free issue.

			C5.1.7.12.11.  Expedited/Replacement Shipment Subsequent to Validated Supply Discrepancy Report.  When reshipment is required (e.g. due to shortage, non-receipt, wrong item, or comparable discrepancy/deficiency), the reshipment will be processed using the original document number and the next available suffix code.  At a minimum, the SoS will provide supply status indicating the estimated shipment date for the reshipment.[footnoteRef:21] [21:  Refer to ADC 1091, SDRs Requesting Expedited or Replacement Shipment.] 

		C5.1.7.13.  Time Standards for Providing Status Transactions.  When required, sources of supply will dispatch applicable status on requisitions, retransmitted requisitions, reinstated requisitions, and responses to requisition inquiries within the times prescribed below:

			C5.1.7.13.1.  Supply Status

				C5.1.7.13.1.1.  Two calendar days from receipt of PD 01-08 transactions.

				C5.1.7.13.1.2.  Five calendar days from receipt of PD 09-15 transactions.

				C5.1.7.13.1.3.  Twenty-four hours after release of MOV requests.

			C5.1.7.13.2.  Shipment Status

				C5.1.7.13.2.1.  Twenty-four hours after shipment (or release to carrier) for PD 01-03 transactions.

				C5.1.7.13.2.2.  Forty-eight hours after shipment for PD 04-08 transactions.

				C5.1.7.13.2.3.  Three working days after shipment for PD 09-15 transactions.

				C5.1.7.13.2.4.  Twenty-four hours from receipt of PD 01-03 requisition inquiries.

				C5.1.7.13.2.5.  Forty-eight hours from receipt of PD 04-08 requisition inquiries.

				C5.1.7.13.2.6.  Three working days from receipt of PD 09-15 requisition inquiries.

	C5.1.8.  Distribution of Status

		C5.1.8.1.  Requisition Cancellations.  Sources of supply will automatically send supply and/or shipment status in response to requisition cancellations, including mass and universal cancellations.  In addition to status sent to organizations, DAAS will send shipment status to storage/procurement activities and/or the source of supply (when DVD actions with Status Code BV are applicable) on all affected shipments entering the DTS during mass or universal cancellation situations.  Sources of supply will send the status of cancellation actions within five calendar days of receipt of the requisition cancellations.  Sources of supply will revise this status as further actions are taken on the cancellation request.

		C5.1.8.2.  Procedures.  Sources of supply will address supply and shipment status sent in response to requisition cancellations as follows:

			C5.1.8.2.1.  When there is no record of the requisition cancellation, address the status transaction to the requisitioner.

			C5.1.8.2.2.  When there is a record of the requisition cancellation, address the status transaction to the organization(s) identified in the cancellation request, including any additional status organizations.

	C5-3	CHAPTER 5