*DLM 4000.25, October 23, 2015*

*Change 6*

**C27. CHAPTER 27**

**MASS OR UNIVERSAL CANCELLATION OF REQUISITIONS**

C27.1. GENERAL

	C27.1.1.  Purpose.  This chapter provides procedures for the request, generation, submission, and processing of mass and universal cancellations of requisitions.  It also provides procedures for the disposition of frustrated shipments and materiel resulting from mass and universal cancellation actions.

	C27.1.2.  Transactions

		C27.1.2.1.  Request for Mass Cancellation of Requisitions Transaction is identified by the DLMS 869C by beginning segment (1/BSI08/20 Code AC and 1/BSI09/20 Code AW).[footnoteRef:1]  This transaction provides the functionality of the MILSTRIP Mass Cancellation Message (See Appendix 6.23).  There is no MILSTRIP legacy document identifier code (DIC) equivalent.  [1:  Mass cancellation and follow-on transactions are DLMS enhancements.  Refer to ADC 1132.  Delayed implementation authorized.] 

		C27.1.2.2.  Request for Universal Cancellation of Requisitions Transaction is identified by the DLMS 869C by beginning segment (1/BSI08/20 Code AC and 1/BSI09/20 Code C).[footnoteRef:2]  This transaction provides the functionality of the MILSTRIP Universal Cancellation Message (See Appendix 6.23).  There is no MILSTRIP legacy DIC equivalent. [2:  Universal cancellation and follow-on transactions are DLMS enhancements.  Refer to ADC 1132.  Delayed implementation authorized.] 

		C27.1.2.3.  Requisition Modification Transaction is identified by the DLMS 511M by beginning segment (1/BR02/020 Code AM).  This transaction provides the functionality of MILSTRIP legacy DIC AM1, AM2, AM4, AM5, AMA, AMB, AMD, and AME.

		C27.1.2.4.  Materiel Release Order Modification Transaction is identified by the DLMS 940R by beginning segment (1/W0506/0200 Code NA and 1/W0507/0200 Code 2).  This transaction provides the functionality of passing the MILSTRIP legacy DIC AM1, AM2, AM4, AM5, AMA, AMB, AMD, and AME from the source of supply (SoS) to the storage activity.

		C27.1.2.5.  Disposal Release Order Modification Transaction is identified by the DLMS 940R by beginning segment (1/W0506/0200 Code NE and 1/W0507/0200 Code 2).  This transaction provides the functionality of passing the MILSTRIP legacy DIC AMJ.  

		C27.1.2.6.  Inventory Control Point Requisition Modification Transaction is identified by the DLMS 511M by beginning segment (1/BR02/020 Code AM and 1/BR06/020 Code 2).  This transaction provides the functionality of MILSTRIP legacy DIC AMP.

		C27.1.2.7.  Universal Requisition Cancellation to Storage Activity Transaction is identified by the DLMS 940R by beginning segment (1/W0506/0200 Code ND) and DIC AC7 (2/LQ01/1300 Code 0).  This transaction provides the functionality of MILSTRIP legacy DIC AC7. 

		C27.1.2.8.  Universal Requisition Cancellation to Procurement Activity Transaction is identified by the DLMS 869C by beginning segment (1/BSI08/20 Code AC and 1/BSI09/20 Code C) and DIC ACM (2/LQ01/180 Code 0).  This transaction provides the functionality of MILSTRIP legacy DIC ACM.

		C27.1.2.9.  Mass Requisition Cancellation to Storage Activity Transaction is identified by the DLMS 940R by beginning segment (1/W0506/0200 Code ND) and DIC AC6 (2/LQ01/1300 Code 0).  This transaction provides the functionality of MILSTRIP legacy DIC AC6. 

		C27.1.2.10.  Mass Requisition Cancellation to Procurement Activity Transaction is identified by the DLMS 869C by beginning segment (1/BSI08/20 Code AC and 1/BSI09/020 Code AW) and DIC ACP (2/LQ01/180 Code 0).  This transaction provides the functionality of MILSTRIP legacy DIC ACP.

		C27.1.2.11.  Follow-Up to Storage Activity for Mass/Universal Requisition Cancellation Transaction is identified by the DLMS 940R by beginning segment (1/W0506/0200 Code ND and 1/W0507/0200 Code 82).  There is no MILSTRIP legacy equivalent DIC.

		C27.1.2.12.  The Supply Status Transaction is identified by the DLMS 870S by two different beginning segment (1/BSR01/020) Transaction Type Codes.

			C27.1.2.12.1.  Transaction Type Code 4 – Response to Requisition.  This transaction provides the functionality of MILSTRIP legacy DIC AE1, AE2, AE3, AE8, AE9, AEA, AEB, AED, and AEE.  

			C27.1.2.12.2.  Transaction Type Code 5 – Notice of Response to Direct Vendor Delivery.  This transaction provides the functionality of MILSTRIP legacy DIC AB1, AB2, AB3, and AB8.

		C27.1.2.13.  The Reply to Cancellation Request – Shipment Status is identified by the DLMS 856S by beginning segment (1/BSN06/0200 Code AS) and DICs AU1, AU2, AU3, AU4, AU5, AU8 (2/LQ01/3500 Code 0).  This transaction provides the functionality of MILSTRIP Legacy DIC AU1, AU2, AU3, AU4, AU5, and AU8.

		C27.1.2.14.  The Reply to Cancellation Request – Materiel Release Confirmation is identified by the DLMS 945A by beginning segment (1/W0611/0200 Code NJ).  This transaction provides the functionality of MILSTRIP Legacy DIC AU0, AUA, and AUB.

		C27.1.2.15.  The Reply to Cancellation Request is identified by the DLMS 945A by beginning segment (1/W0611/20 Code NR).  This transaction provides the functionality of MILSTRIP Legacy DIC AG6.

		C27.1.2.16.  The Storage Activity Supply Status is identified by the DLMS 945A by beginning segment (1/W0611/20 Code NL).  This transaction provides the functionality of MILSTRIP Legacy DIC AE6. 

C27.2.  APPLICABILITY

	C27.2.1.  Events such as base closures, termination of special projects, ship and unit inactivation, termination of agreements, and termination of vessel outfitting or construction can necessitate the requirement for mass or universal cancellation.  

	C27.2.2.  Although these events may ultimately require mass or universal cancellation action, they are normally known to the affected activities well in advance of the effective date of such closures or termination action.  In these instances, every effort will be made by the requisitioning activity to minimize the continued processing of requisitions by the sources of supply (SoS), and the subsequent entry of unwanted shipments into the Defense Transportation System (DTS), through initiation and processing of single line-item cancellations (See Chapter 4).

	C27.2.3.  When a total project (or total requirement for a single base) is no longer required and should be canceled and it is known that insufficient time remains to permit continued cancellation on a single line basis, a mass cancellation or universal cancellation request may be initiated.

		C27.2.3.1.  A mass cancellation permits continued supply action and shipment processing for selected requisitions.

		C27.2.3.2.  A universal cancellation serves to terminate all such processing, even requisitions previously identified for continued supply action and shipment processing under mass cancellation situations.

		C27.2.3.3.  Under extreme conditions, a mass cancellation may be superseded by a universal cancellation.

	C27.2.4.  Requisitions that require continued supply action and shipment processing under mass cancellation situations must be identified by the requiring activity at the earliest date through submission of a Requisition Modification (DLMS 511M) citing Special Requirements Code 555[footnoteRef:3]. [3:  Code 555 identified in the required delivery date field for MILSTRIP legacy transactions.] 

		C27.2.4.1.  The requisition may not be modified to cite Special Requirements Code 555 after the effective date of the requested mass cancellation; however, requisition modifications submitted to change other data elements when the Special Requirements Code 555 was previously entered must perpetuate the Special Requirements Code 555.[footnoteRef:4] [4:  Revised requisition modifier procedures last reported as not implemented by U.S. Marine Corps (USMC).  Refer to Approved MILSTRIP Change Letter (AMCL) 123C.] 

		C27.2.4.2.  Requisitions containing, or modified to contain, Special Requirement Code 555 will receive processing precedence under Chapter C4.

	C27.2.5.  When a universal cancellation is initiated to supersede a mass cancellation and there are outstanding requisitions or requisition modifications citing Special Requirements Code 555, the SoS will provide a Universal Requisition Cancellation to Storage Activity (DLMS 940R/DIC AC7) or a Universal Requisition Cancellation to Procurement Activity (DLMS 869C/DIC ACM) for all outstanding requisitions, regardless of the presence of a Special Requirements Code 555.

C27.3.  INITIATION OF MASS OR UNIVERSAL CANCELLATION OF REQUISITIONS

	C27.3.1.  Only designated personnel within an organization may initiate requests for mass or universal cancellation of requisitions.  The Component’s requisitioning system will ensure that only authorized users initiate these requests.  If there are any questions regarding the authenticity of a mass/universal cancellation, contact either the Component Supply PRC Representative or the customer support representative for the source of supply.  Component Supply PRC Representatives are identified on the DLMS Website on the Supply Committee page.  The mass or universal cancellation request will be accomplished by preparation of the DLMS 869C or the message format reflected in Appendix AP6.23.

		C27.3.1.1.  Inter-Component dissemination of requests for mass or universal cancellation must be coordinated in advance to determine if the DLMS 869C or message format will be used.  If using the message format, the requesting Component must identify the authorized recipient from the Component to process the mass or universal cancellation.  If it is not known, contact either the Component’s Supply PRC representative or the customer support representative for the source of supply to identify the point of contact. 

		C27.3.1.2.  Intra-Component dissemination of requests for mass or universal cancellations must be performed by the authorized Component contact point.  Intra-Component dissemination will include all Component supply sources, storage sites, and other activities within the DoD Component processing MILSTRIP documentation or shipments with capability to cancel requisitions or divert shipments.  In addition, the designated Component contact points must ensure that the appropriate overseas theater, force, logistics, or type commanders are cognizant of mass or universal cancellation actions affecting their areas of responsibility.

	C27.3.2.  Due to the requirement to ensure that mass/universal cancellation requests are only initiated by authorized personnel, these cancellations must not be initiated through use of DOD EMALL, or its replacement system FEDMALL.

	C27.3.3.  Required Data Content.  Requests for mass or universal cancellation action will be submitted to the applicable SoS for cancellation of all open requisitions applicable to specific projects or bases.  The request for mass or universal cancellations will contain identification of the activity submitting the request, the effective date, and the required codes for identification of one of the following, for which cancellation of all applicable requisitions is requested:

		C27.3.3.1.  One Project code and one ship-to DoDAAC

		C27.3.3.2.  No project code and one ship-to DoDAAC

		C27.3.3.3.  One project code and multiple ship-to DoDAACs

		C27.3.3.4.  No project code and multiple ship-to DoDAACs

		C27.3.3.5.  Multiple project codes and one ship-to DoDAAC

		C27.3.3.6.  Federal supply classification (FSC), national stock number (NSN), local stock number (LSN), or CAGE/part number when associated with the address of the original requisition document number ship-to address and/or project code.

	C27.3.4.  Customers retain the authority to submit single line-item cancellation requests via DLMS 869C/DICs AC1/AC2/AC3 at any time before, during, or after the mass cancellation effective date.

C27.4.  CONTINUING HIGH PRIORITY DEMANDS DURING A MASS CANCELLATION

	C27.4.1.  A need may exist to continue the processing of certain requisitions and shipments during mass cancellations such as high priority demands to satisfy not mission capable supply (NMCS) conditions (identified by Special Requirements Code 999 or N in the requisition).  In addition, a need may exist to allow continued processing of requisitions for materiel required to effect base closure.  In these instances, submit a requisition modification citing Special Requirements Code 555 to the SoS prior to the submission of the mass cancellation request.  For Security Assistance, use of Special Requirements Code 555 is restricted to approved cooperative logistics supply support arrangement (CLSSA) requisitions with Type of Assistance Code U or V (the buying government has made cash payment to buy equity in DoD stocks).  Sources of supply will not cancel requisitions that have been modified to contain Special Requirements Code 555 during a mass cancellation process.  If submitting the mass cancellation request via offline message, then cite one of the following selective criteria in the special instructions segment of the message:

		C27.4.1.1.  Project code(s) when associated with the ship-to DoDAAC being canceled

		C27.4.1.2.  Special Requirements Code 999 or N when associated with the ship-to DoDAAC being canceled

		C27.4.1.3.  FSC, NSN, or CAGE/part number when associated with the ship-to DoDAAC being canceled

		C27.4.1.4.  Specific requisition document number(s) and routing identifier code (RIC)-From the status received or the RIC-To which the requisition has been transmitted if status has not been received

		C27.4.1.5.  Specific priority designator (PD) when associated with the ship-to address  DoDAAC being canceled

		C27.4.1.6.  Required delivery period (RDP) when associated with the ship-to address  DoDAAC being canceled - conventional ammunition only.[footnoteRef:5] [5:  Use of RDP for conventional ammunition last reported as not implemented by U.S. Air Force (USAF).  Refer to AMCL 148.] 

	C27.4.2.  Upon receipt of Requisition Modifications citing continued processing action during a mass cancellation, SoS, storage activities, and procurement sources must annotate the affected requisition(s) and all associated transactions/records with Special Requirements Code 555.

	C27.4.3.  Upon receipt of either the Request for Mass Cancellation transaction or the offline Mass Cancellation message citing selective criteria for continued processing action in the special instructions segment, the SoS must review all prospective cancellations to identify those for which continued processing has been requested.  For continued processing of requisitions at storage activities, the SoS will provide a Materiel Release Order Modification (for MILSTRIP legacy processing, pass the Requisition Modification) to the Storage Activity.  In the case of items scheduled for direct vendor delivery, the SoS must forward ICP Requisition Modifications (DIC AMP) to procurement sources.  

	C27.4.4.  The DTS will continue movement of materiel to which Special Requirements Code 555 has been applied except when a universal cancellation has been announced.

C27.5.  SOURCE OF SUPPLY PROCESSING MASS OR UNIVERSAL CANCELLATION REQUESTS

	C27.5.1.  Sources of supply are responsible for ensuring that requisition processing, procurement, and storage activities exercise the fullest practical resourcefulness in preventing the issue and shipment of unwanted materiel.  The practical considerations involved in the processing of cancellation requests include such factors as time, packing and handling, related costs, and location of materiel for which cancellation is requested.

	C27.5.2.  The SoS must cancel all requisitions dated on or prior to the effective date announced in mass or universal cancellation requests for which materiel release orders (MROs), and/or purchase requests have not been submitted to storage or procurement activities.  Provide a Supply Status transaction citing Status Code BQ or B4, as appropriate, as notice of accomplished cancellations to all eligible status recipients under Chapter 5 within the timeframe for furnishing status.

	C27.5.3.  The SoS will furnish Supply Status transactions citing Status Code B9 to all eligible recipients under Chapter 5 within the timeframes for furnishing status for:

		C27.5.3.1.  Unconfirmed cancellation of open MROs and open procurement actions.

		C27.5.3.2.  Materiel release confirmations (MRCs) that indicate shipment to OCONUS activities within 45 days of the effective date of the mass cancellation.

	C27.5.4.  Provide subsequent Supply Status transactions citing Status Codes BQ, B4, or B6 as notification for each line-item canceled or diverted.  Cite Status Code B8 for each line-item that was not canceled or diverted.

	C27.5.5.  The SoS will provide storage activities with mass requisition cancellation transactions (DLMS 940R/DIC AC6) and universal requisition cancellation transactions (DLMS 940R/DIC AC7) for all unconfirmed MROs and MRCs that indicate shipment to OCONUS activities within 45 days of the effective date of the mass or universal cancellation. 

	C27.5.6.  The SoS will provide procurement activities with mass requisition cancellation transactions (DLMS 869C/DIC ACP) and universal requisition cancellation transactions (DLMS 869C/DIC ACM) for all open procurement actions.  These transactions are mandatory when purchase requests have been issued to another Component.  If processed within an integrated Component system, equivalent internal transactions may be used.

	C27.5.7.  The SoS will not provide storage and procurement activities with cancellation requests when:

		C27.5.7.1.  In receipt of MRCs that show shipment has been accomplished by parcel post (USPS),

		C27.5.7.2.  In receipt of MRCs that show shipment to CONUS activities has been accomplished, and

		C27.5.7.3.  In receipt of MRCs that show shipment to OCONUS customers was accomplished more than 45 days prior to the receipt of the mass or universal cancellation request.

	C27.5.8.  The SoS will follow-up with the procurement or storage activity, as applicable, when no response to the original universal or mass requisition cancellation request has been received within three days.  The SoS will follow-up to procurement activities via internal system communications or offline means (e.g., email, phone).  For follow-ups to a storage activity, the SoS will use the DLMS 940R Follow-Up to Storage Activity for Mass/Universal Requisition Cancellation (there is no MILSTRIP legacy equivalent).

C27.6.  STORAGE ACTIVITY PROCESSING OF MASS OR UNIVERSAL REQUISITION CANCELLATIONS

	C27.6.1.  Upon receipt of the mass or universal requisition cancellation transaction(s) from the SoS, the storage activity will identify all affected MROs where the items have not been released to a carrier for delivery to the consignee.

		C27.6.1.1.  For mass cancellation, the storage activity will not suspend processing of MROs identified for continued processing under paragraph C27.4.

		C27.6.1.2.  For universal cancellation, the storage activity will suspend further processing of all MROs, including any citing Special Requirements Code 555.

	C27.6.2.  For CONUS shipments, storage activities will accomplish cancellation for all items for which mass or universal requisition cancellation transactions are received from SoS and the items have not been released to a carrier for delivery to the consignee.

	C27.6.3.  Storage activities will advise the SoS of actions taken in response to cancellation requests.  When a shipment has not been released to the carrier for delivery to consignee and cancellation is accomplished, the storage activity will send the SoS a Reply to Cancellation Request transaction (DIC AG6) citing Status Code BQ.

	C27.6.4.  For shipments already released to a carrier for delivery to the consignee not meeting the criteria stipulated in paragraph C27.5.7., the storage activity will generate a Reply to Cancellation Request – Shipment Status (DLMS 856S/DIC AU_) for routing by DAAS under standard MILSTRIP procedures for shipment status.  It will also generate the Storage Activity Supply Status (DLMS 945A/DIC AE6) to the SoS.

		C27.6.4.1.  For CONUS shipments and those OCONUS shipments that meet the mass or universal cancellation criteria and have entered the DTS within 45 calendar days of the date of the mass or universal requisition cancellation request, the storage activity will cite Action Code W10 in the Reply to Cancellation Request – Shipment Status to indicate actions are being taken to divert the shipment.  

		C27.6.4.2.  The Storage Activity Supply Status transaction to the SoS will cite Status Code B9 indicating that action is being taken to cancel/divert the shipment.

	C27.6.5.  When storage activities do not accomplish cancellation, the source of supply will be furnished a Storage Activity Supply Status transaction (DLMS 945A/DIC AE6) citing Status Code B8.

	C27.6.6.  Storage activities in receipt of transportation confirmation of shipment diversion transactions will send to the appropriate SoS a Reply to Cancellation Request transaction (DIC AG6) citing Status Code B6 for each requisition contained within the shipment unit.  The transaction will also cite the DoD activity address code (DoDAAC) of the new consignee.

	C27.6.7.  Storage activities in receipt of transportation denial of shipment diversion transactions will generate a Reply to Cancellation Request – Materiel Release Confirmation (DIC AU0/AUA/AUB to the appropriate source of supply.  This transaction will be prepared under Appendix AP8.14.

	C27.6.8.  Upon receipt of a DLMS 940R Follow-Up to Storage Activity for Mass/Universal Requisition Cancellation, the storage activity will respond with the appropriate transaction as outlined in the preceding procedures for storage activity processing of these cancellation requests.

C27.7.  DIRECT VENDOR DELIVERY PROCESSING OF MASS OR UNIVERSAL REQUISITION CANCELLATIONS

	C27.7.1.  All rules governing the single-line cancellation of shipments from procurement also apply to requests for mass or universal requisition cancellation, except as modified herein.  Where DLMS/DIC transactions are identified for exchange of reporting events between the SoS and the procurement activity, internal system or off-line communications (e.g., email, phone), are authorized when procurement systems are not capable of supporting the MILSTRIP transactions.

	C27.7.2.  The SoS will initiate universal requisition cancellation transactions (DIC ACM) and mass requisition cancellation transactions (DIC ACP) for all items scheduled for direct delivery, and for which purchase requests have been submitted, regardless of materiel costs, unless continued processing has been requested under Paragraph C27.4.  

		C27.7.2.1.  Mass cancellation will not be requested for requisitions citing Special Requirements Code 555.

		C27.7.2.2.  Universal cancellation will be requested regardless of the entry in the Special Requirements field.

	C27.7.3.  Procurement activities will advise the SoS of actions taken in response to cancellation requests.  When a shipment has not been released to the carrier for delivery to consignee and cancellation is accomplished, the procurement activity will send the SoS a Reply to Cancellation Request transaction (DIC AG6) citing Status Code BQ or B4.  Procurement activities will not initiate actions with the DTS to cause diversion of shipments at terminals.

	C27.7.4.  For shipments already released to a carrier for delivery to the consignee not meeting the criteria stipulated in paragraph C27.5.7., the procurement activity will generate the Storage Activity Supply Status (DLMS 945A/DIC AE6) to the SoS.  The SoS will generate, on behalf of the procurement activity, a Reply to Cancellation Request – Shipment Status (DLMS 856S/DIC AU_) for routing by DAAS under standard MILSTRIP procedures for shipment status.  

		C27.7.4.1.  For CONUS shipments and those OCONUS shipments that meet the mass or universal cancellation criteria and have entered the DTS within 45 calendar days of the date of the mass or universal requisition cancellation request, the SoS will cite Action Code W10 in the Reply to Cancellation Request – Shipment Status to indicate actions are being taken to attempt to divert the shipment.  

		C27.7.4.2.  The Storage Activity Supply Status transaction to the SoS will cite Status Code B9 indicating that action is being taken to cancel/divert the shipment.  This status will be perpetuated by the SoS in a Supply Status transaction to the requesting activity.

	C27.7.5.  Procurement activities in receipt of confirmation of shipment diversion transactions will send to the appropriate SoS a Reply to Cancellation Request transaction (DIC AG6) SoS citing Status Code B6 for each requisition contained within the shipment unit.  The transaction will also cite the DoDAAC of the new consignee.  

	C27.7.6.  Procurement activities in receipt of denial of shipment diversion transactions will send to the appropriate SoS a Reply to Cancellation Request – Materiel Release Confirmation transaction (DIC AU0/AUA/AUB).

	C27.7.7.  If the procurement activity is unable to transmit either the confirmation of shipment diversion or the denial of shipment diversion, it will be presented to the SoS via internal system communication or offline means (e.g., email, phone), at which time the SoS will update its records accordingly.

	C27.7.8.  Upon receipt of a DLMS 869C Follow-Up to Procurement Activity for Mass/Universal Requisition Cancellation, the procurement activity will respond with the appropriate transaction as outlined in the preceding procedures for procurement activity processing of these cancellation requests.

C27.8.  DTS PROCESSING OF MASS OR UNIVERSAL REQUISITION CANCELLATIONS

	C27.8.1.  Diverting Outside the Continental U.S. Shipments.  When outside the continental U.S. (OCONUS) shipments have already departed from continental U.S. (CONUS) ports, the responsibility for diversion or disposition is that of the consignee or the appropriate theater, force, logistics, or type commander.  Notice to the latter will be the transportation lift data provided by the DTS clearance authority.  (See paragraph C27.9.4.)

	C27.8.2.  Diverting Continental U.S. Shipments.  No attempt will be made to divert materiel destined to CONUS customer activities beyond the point of shipment.

	C27.8.3.  Designated Storage Points.  All shipping DoD Components will designate storage points within their distribution system to receive shipments redirected as a result of mass or universal cancellation.  Fund citations for bill of lading (BL) preparation must also be provided.  These designated points and fund citations will be provided to Air Mobility Command (AMC), Military Surface Deployment and Distribution Command (SDDC), or theater commanders and will serve as predesignated consignees for any announced mass or universal cancellation.  If more than one storage point is designated, instructions will be furnished to specify on a geographical basis the storage point designation in relation to each range of water and aerial ports (e.g., west, gulf, and east coasts).  In addition, canceling DoD Components will designate a contact point(s) to provide disposition instructions on materiel that does not meet the automatic diversion conditions specified in paragraph C27.9.  Designated points of contact will provide requested disposition instructions to DTS within 24 hours on materiel located at air terminals and within 48 hours on materiel located at water terminals.

C27.9.  DISPOSITION OF FRUSTRATED SHIPMENTS/MATERIEL

	C27.9.1.  The disposition of frustrated shipments at water ports of embarkation (WPOE)/aerial ports of embarkation (APOE)  that are the result of mass or universal cancellation action will be as follows:

		C27.9.1.1.  Shipments from DoD storage points or from commercial vendors acting under the direction of a DoD procuring activity will be diverted to the predesignated storage sites of the shipping/procuring DoD Component.

		C27.9.1.2.  Shipments from General Services Administration (GSA) commercial vendors acting under the direction of a GSA procuring activity will be disposed under normal excess/surplus/donation procedures.  The shipments will not be diverted to GSA facilities.[footnoteRef:6] [6:  Refer to ADC 1142, Update to Remove General Services Administration (GSA) from MILSTRIP Materiel Returns Program (MRP)] 

		C27.9.1.3.  DTS attempts to divert/frustrate shipments will terminate 45 calendar days from the effective date of the mass or universal cancellation request.

	C27.9.2.  Certain strategic and tactical operations or political considerations may dictate that all shipments for a given consignee be stopped or diverted.  In these most restrictive of shipment diversion situations and economic considerations (e.g., the comparison of accessorial cost of stopping, holding, and returning the materiel to storage activities), the value of the canceled materiel and the costs of the receiving activity to perform the necessary processing or reprocessing of the materiel are not controlling factors.  In most situations, however, the strategic, tactical, or political environment is such that complete disregard of these economic considerations is not warranted.

	C27.9.3.  Transportation diversion procedures are established to permit diversion only if the materiel being shipped can be identified and located by TCN.

		C27.9.3.1.  Non-Consolidated Shipment Units.  Shipment units eligible for cancellation that have not been consolidated into a container with other shipments will be stopped and diverted by the POE up to the point of lift.  Diversion of cancellation eligible shipments at or beyond the port of debarkation (POD) will be the responsibility of the appropriate theater, force, logistics, or type commander.

		C27.9.3.2.  Consolidated Multiple Shipment Units.  Individual line-items will not be removed from multiple-line shipment units (consolidated packs), nor will a shipment unit container be removed from a multi-container shipment (SEAVAN) type device.  Shipment units cannot be diverted in the DTS if stuffed or loaded with other shipment units or on multiple shipment unit devices; such as, SEAVANS, container express (CONEX), MILVANS (Military Van), and Aircraft 463L pallets.

	C27.9.4.  For mass or universal cancellation requests that specify FSC, NSNs/LSNs, or part number data, the DTS will stop and frustrate, for the DoD Component review, all shipments of the canceling DoD Component for the affected consignees.  Disposition of cancellation eligible shipments at or beyond the POD will be the responsibility of the appropriate theater, force, logistics, or type commander.

	C27.9.5.  The DTS will generate specified documentation for the following shipment categories:

		C27.9.5.1.  For all shipments that are diverted as a result of mass or universal cancellation, the DTS will contact the shipper to confirm shipment diversion.  The confirmation of shipment diversion will contain complete Transportation Control and Movement Document (TCMD) data for each shipment unit and, if available, the contract number.  In addition:

			C27.9.5.1.1.  For shipments that are diverted under pre-positioned instructions, the DTS will generate appropriate DTR 4500.9R, “Defense Transportation Regulation” transactions to the new consignee.

			C27.9.5.1.2.  For shipment units that are frustrated and were not diverted to a specific site, the DTS will send a request for disposition instructions to the appropriate Component contact points.  In situations where the designated DoD Component contact point is a collocated liaison office, the request for disposition instruction transactions will be listed and provided to the contact point directly.  After receipt of disposition instructions for such frustrated shipments, the DTS will prepare appropriate DTR transactions for the new consignee.

			C27.9.5.1.3.  For shipments in transit to, at, or between the POD and the OCONUS consignee, OCONUS DTS activities will request disposition instructions from the appropriate theater, force, logistics, or type commander’s designated contact point.

		C27.9.5.2.  For shipments in transit between WPOE/APOE and the OCONUS consignee less than 30 days, the DTS will generate a listing of the manifest shipment unit data, vessel/aircraft identification and departure date, water port of debarkation (WPOD)/aerial port of debarkation (APOD) and estimated time of arrival (ETA).  This listing will be sent to the affected OCONUS command component, the appropriate WPOD/APOD, and to the designated contact point, if requested.

	C27.9.6.  Storage sites in receipt of diverted shipments will report the receipt to the appropriate SoS under Chapter 13.  Reconsignment/disposition will be as directed.

	C27.9.7.  Specific instructions concerning materiel transportation charges and credit allowances are contained in the DoD 7000.14-R, “Department of Defense Financial Management Regulations (FMRS),” (Vol 11B), Federal Property Management Regulation (FPMR) 101-26.311, and FPMR 101-27.505.  The Component initiating the cancellation requests applicable to U.S. Forces requisitions will be charged with the following:

		C27.9.7.1.  Transportation and terminal costs associated with holding, stopping, and returning materiel to storage,

		C27.9.7.2.  Procurement termination costs when it is determined that termination is in the best interest of the Government, and

		C27.9.7.3.  Excess transportation costs that may be incurred when moving cargo that is unaffected by the mass or universal cancellation action.

C27-2	CHAPTER 27