*DLM 4000.25, Volume 2, April 29, 2016*

*Change 7*

**C25. CHAPTER 25**

**SECURITY ASSISTANCE PROGRAM**

C25.1  GENERAL

	C25.1.1.  Purpose.  The provisions of Military Standard Requisitioning and Issue Procedures (MILSTRIP) apply to all phases of requisitioning and issue to support the Security Assistance Program (also known as the Security Cooperation Program); however, this chapter provides special procedures and instructions for preparing and processing foreign military sales (FMS) and Grant Aid requirements (see Appendix 7.19), which are exceptions to other areas of the manual.

	C25.1.2.  Transactions.  This chapter addresses the procedures and applicable transactions relevant to Security Assistance.  See the Defense Enterprise Data Standards Office Website for available formats on the DLMS IC page. The corresponding MILSTRIP legacy 80 record position transaction functionality is also provided for ease of interpretation by DLMS users and to support those working in a legacy environment.  In addition to the listed MILSTRIP legacy transactions, the DLMS formats may incorporate functionality to support Component-unique transactions as noted in the implementation convention.

		C25.1.2.1.  The Requisition Transaction is identified by the DLMS 511R by beginning segment (1/BR02/020 Code A0).  This transaction provides the functionality of MILSTRIP legacy document identifier codes (DIC) A01, A02, A04, A05, A0A, A0B, A0D, and A0E.

		C25.1.2.2.  The Passing Order Transaction is identified by the DLMS 511R by beginning segment (1/BR02/020 Code BM.  This transaction provides the functionality of MILSTRIP legacy DIC A31, A32, A34, A35, A3A, A3B, A3D, and A3E.

		C25.1.2.3.  The Referral Order Transaction is identified by the DLMS 511R by beginning segment (1/BR02/020 Code BN.  This transaction provides the functionality of MILSTRIP legacy DIC A41, A42, A44, A45, A4A, A4B, A4D, and A4E.

		C25.1.2.4.  The 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.

		C25.1.2.5.  The Requisition Follow-Up Transaction is identified by the DLMS 869F by beginning segment (1/BSI08/020 Code IN.  This transaction provides the functionality of MILSTRIP legacy DIC AT1, AT2, AT4, AT5, ATA, ATB, ATD, and ATE.    

		C25.1.2.6.  The Supply Status Transaction is identified by the DLMS 870S by three different beginning segment (1/BSR01/020) Transaction Type Codes.

			C25.1.2.6.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.  

			C25.1.2.6.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.

			C25.1.2.6.3.  Transaction Type Code 6 – Notice of Response to Supply Assistance.  This transaction provides the functionality of MILSTRIP legacy DIC AE1, AE2, AE3, AE8, AE9, AEA, AEB, AED, and AEE.

		C25.1.2.7.  The Shipment Status Transaction is identified by the DLMS 856S by beginning segment (1/BSN06/0200 Code AS.  This transaction provides the functionality of MILSTRIP legacy DIC AS1, AS2, AS3, AS8, AU1, AU2, AU3, and AU8.

		C25.1.2.8.  The Notice of Availability Transaction is identified by the DLMS 856N by beginning segment (1/BSN06/0200 Code AD.  This transaction provides the functionality of MILSTRIP legacy DIC AD1, AD2, AD3, AD4, and ADR.		

		C25.1.2.9.  The Notice of Availability Reply Transaction is identified by the DLMS 856N by beginning segment (1/BSR01/20 Code  8.  This transaction provides the functionality of MILSTRIP Legacy DIC AD5.

C25.2.  REQUISITION FORMATS

	C25.2.1.  Requisitions for FMS and Grant Aid materiel vary from the construction of requisitions in support of U.S. Forces.  Codes peculiar to FMS and Grant Aid requisitions are listed in the designated appendices and in the military assistance program address directory (MAPAD) found in DLM 4000.25 Volume 6, Chapter 3, together with their meanings and applications.  Specific FMS and Grant Aid requisition entries are as follows:

		C25.2.1.1.  Grant Aid

			C25.2.1.1.1.  Requisitioner Field (first six positions of the document number).  All Grant Aid requisitions will contain a unique six-position identification code consisting of a combination of codes that identifies the SC implementing agency and provides specific requisitioning and shipping instructions for the source of supply and shipping activities.  This identification code is the first six positions of the document number.  DLM 4000.25 Volume 6, Chapter 3, Military Assistance Program Address Directory (MAPAD); DoD 5105.38-M, Security Assistance Management Manual (SAMM); and DoD 7000.14-R, DoD Financial Management Regulation, in combination, provide the interpretation of these codes.

				C25.2.1.1.1.1.  The first position will contain the FMS and Grant Aid service assignment code (Appendix 7.2) of the SC implementing agency responsible for administering the Grant Aid Program line.

				C25.2.1.1.1.2.  The second and third positions will contain the SC customer code (Appendix 7.18)[footnoteRef:1]. [1:  Refer to Approved Defense Logistics Management Standards (DLMS) Change (ADC) 448B] 

				C25.2.1.1.1.3.  The fourth position will contain the mark-for code, also known as the in-country code, to indicate the recipient or place of discharge within the country/activity (see MAPAD), with the exception of DLMS 511R (MILSTRIP legacy DIC A05/AOE) Requisition with Exception Data containing special one-time shipping instructions entered in the Remarks block of the requisition.  In this instance, a requisition may contain a zero in the fourth position of the requisitioner field.  The special instruction will include an address to receive documentation when documents are not to be forwarded to the ship-to address.  The use of Requisitions with Exception Data will be limited to one-time situations where it is not practicable to designate the addresses by coded entries in the requisition and in the MAPAD.

				C25.2.1.1.1.4.  The fifth position will contain a numeric zero (0).

				C25.2.1.1.1.5.  The sixth position will contain the appropriate Grant Aid type of assistance/financing code (Appendix 7.19).

			C25.2.1.1.2.  Supplementary Address Field (six character field)

				C25.2.1.1.2.1.  The first position will contain Y to indicate that the data entered in the second through sixth positions are nonsignificant to the overall systems but are to be perpetuated in all subsequent documentation.

				C25.2.1.1.2.2.  The second through fifth positions will contain the record control number (RCN).  This number is assigned by the appropriate Service activity and is constructed as follows:

						C25.2.1.1.2.2.1.  The first position of the RCN will contain the last digit of the program year in which the requisitioned item was approved and funded.

						C25.2.1.1.2.2.2.  The second through fifth positions of the RCN will contain the four-position program line item number (alpha/numeric) of the program.

		C25.2.1.2.  Foreign Military Sales

			C25.2.1.2.1.  Requisitioner Field (first six positions of the document number).  All FMS requisitions will contain a unique six-position identification code consisting of a combination of codes that identifies the requisitioning country or international organization and provides specific requisitioning and shipping instructions for the source of supply and shipping activities.  This identification code is the first six positions of the document number.  DLM 4000.25 Volume 6, Chapter 3, Military Assistance Program Address Directory (MAPAD); DoD 5105.38-M, Security Assistance Management Manual (SAMM); and DoD 7000.14-R, DoD Financial Management Regulation, in combination, provide the interpretation of these codes.  

				C25.2.1.2.1.1.  The first position will contain the FMS and Grant Aid Service assignment code (Appendix 7.2) of the SC implementing agency responsible for administering the FMS case.

				C25.2.1.2.1.2.  The second and third positions will contain the SC customer code (Appendix 7.18) [footnoteRef:2]. [2:  Ibid.] 

				C25.2.1.2.1.3.  The fourth position will contain the mark-for code, also known as the in-country code .  This code will be assigned and recognized in conjunction with the FMS offer release option code and the freight forwarder/country representative (FF/CR) code; see explanation in paragraph C25.2.1.2.3..  When a mark-for code is not applicable, a zero must be entered.

				C25.2.1.2.1.4.  The fifth position will contain the FMS delivery term code (see DTR 4500.9-R, “Defense Transportation Regulation” (DTR) or DLMS Dictionary Logistics Data Resources Management System (LOGDRMS) for code definition and applicable values) to convey the point of delivery condition negotiated under the case agreement, and must correspond to delivery terms specified in the applicable letter of offer and acceptance.

				C25.2.1.2.1.5.  The sixth position will contain the appropriate FMS type of assistance/financing code (Appendix 7.19).

			C25.2.1.2.2.  Supplementary Address Field (SUPADD) (six character field).Use of the legacy SUPADD will be retained until full DLMS implementation by all trading partners.  DLMS transactions will carry redundant mapping of the discrete data element content concatenated to configure the SUPAAD.

				C25.2.1.2.2.1.  The first position will contain the security assistance program customer service designator (derived from Appendix 7.2).  This is the customer country’s requisitioning Service, which is published in the DLMS Dictionary and MAPAD.

				C25.2.1.2.2.2.  The second position will contain the applicable FMS offer release option code (A, Y, or Z) or Code X to denote that the United States is responsible for transportation arrangements as determined by negotiations between the customer CR and the U.S. Service responsible for administering the FMS case, and as reflected in the case agreement.  FMS offer release option codes are listed in DLMS Dictionary and DLM 4000.25, Volume 1, Appendix 2, Definitions with explanations of their application and recognition under FMS offer and release procedures.

				C25.2.1.2.2.3.  The third position will contain the FF/CR code to designate the recipient of shipments and documentation as published in the MAPAD.  This entry or the use of code X or W will be applied and recognized in conjunction with the mark-for code entry as explained in Paragraph C25.2.1.2.3.

				C25.2.1.2.2.4.  The fourth through sixth positions will contain the specific SC  case designator consisting of a three-position alpha/numeric code.  The first position must be alphabetic, and the second and third positions may be alphabetic or numeric.   All correspondence (such as letters and messages) must include the appropriate case identifier composed of the two-digit SC customer code, one-digit SC implementing agency code, the three-digit case designator, and the three-digit SC case line item identifier as part of the identification data.   

			C25.2.1.2.3.  Designation of Shipment Addresses for Foreign Military Sales.  The means of expressing ship-to and/or mark-for addresses in requisitions are the entries shown in mark-for and FF/CR, respectively.  The designation of such addresses will be consistent with delivery terms contained in the case agreement.  Specific codes must not be utilized in requisitions until such time as the codes and corresponding addresses are published in the MAPAD.

				C25.2.1.2.3.1.  The Defense Automatic Addressing System (DAAS) will reject Requisitions, Referral Orders, Passing Orders, Requisition Follow-Ups, and Requisition Modifications containing Military Assistance Program Address Codes (MAPAC) that do not have valid ship-to and mail-to addresses in the MAPAD, to the submitting International Logistics Control Office (ILCO) using DLMS 870S (MILSTRIP legacy DIC AE9 Supply Status with Supply Status Code DP.

				C25.2.1.2.3.2.  The inventory control points (ICP) may reject requisitions received off-line (mail, message, courier, fax, telephone) which contain MAPACs that do not have valid ship-to and mail-to addresses in the MAPAD, to the submitting ILCO using DLMS 870S (MILSTRIP Legacy DIC AE3) Supply Status with Supply Status Code CX.  This includes requisitions with exception data directing materiel to various shipping points.  

				C25.2.1.2.3.3.  When shipment is to be made to a FF/CR or to a point designated by a FF/CR in response to a notice of availability (NOA), a specific code other than an X or W will be entered in the third position of the supplementary address.  In this instance, the ship-to address will be the address listed in the MAPAD for the FF/CR or the address provided in response to the NOA.  The mark-for address will be the address listed in the MAPAD for the code in the mark-for field (fourth position of the requisition document number).  For those countries that do not publish clear-text addresses for mark-for codes, there will be no mark-for address, but supply and shipping activities will perpetuate the mark-for code in all related documentation.  When a mark-for code is not applicable, a zero will be entered.

				C25.2.1.2.3.4.  When shipment is to be made to an assembly point or staging area, an XW will be entered in the second and third positions of the supplementary address and a clear-text address will be conveyed in a requisition with exception data.  See paragraph C25.2.1.2.3.2.  The mark-for field, if required, will designate the mark-for address.

				C25.2.1.2.3.5.  When shipment is to be made to an address within the customer country, an XX will be entered in the second and third positions of the supplementary address and the in-country ship-to address will be the address listed in the MAPAD for the designated mark-for code.  See paragraph C25.2.1.2.4.3.

				C25.2.1.2.3.6.  The foregoing instructions apply to all customer countries except Canada.  For Canada, shipment address codes are contained in the second and third positions of the supplementary address.

			C25.2.1.2.4.  FMS Offer Release Option Codes

				C25.2.1.2.4.1.  FMS offer release option codes are used in requisitions for shipments to be made or offered to FF/CRs.  These codes specify whether shipments are to be made automatically or under one of two types of NOAs and will be consistent with the conditions of the FMS case agreements.  FMS Offer release option codes are not applicable to requisitions for Canada since FFs are not utilized for Canada and both the second and third positions of the supplementary address are used to denote shipment addresses.

				C25.2.1.2.4.2.  FMS offer release option codes and their explanations are listed in DLMS Dictionary and further clarified in DLM 4000.25, Volume 1, Appendix 2, Definitions.

				C25.2.1.2.4.3.  If, consistent with the conditions of the FMS case agreements, transportation arrangements for shipments are to be accomplished by the U.S. Service, an X will be entered in second position of the supplementary address in lieu of an FMS offer release option code.  When an X is authorized and entered in second position of the supplementary address, an X or W, denoting shipment to an address within the customer country or shipment to an assembly point or staging area, must be entered in the third position of the supplementary address.

C25.3.  REQUIRED AVAILABILITY DATES

	C25.3.1.  Requisitions for FMS and Grant Aid requirements for major weapons systems, end items, and concurrent spares will be prepared to reflect the amount of time remaining from dates of requisitions until required availability dates (RADs) become effective.  In FMS cases, compute the RAD by adding the lead time stated on the letter of offer and acceptance (LOA) to the date of acceptance by the purchaser.  For Grant Aid, compute the RAD by adding the ICP determined lead time to the date of the order.

	C25.3.2.  The requisition RAD is a three position value consisting of the character A in the first position followed by the number of months remaining from the date of the requisition to the computed RAD in the second and third positions.  The RAD is identified in the DLMS 511R Requisition by the Date/Time segment (2/G6201/80 Code BD; in MILSTRIP legacy DIC A0_ transactions, it is identified in rp 62-64.   The concatenated RAD value enables the source of supply, ILCO, and customer control of requisitions, provides for recognition of firm commitments to foreign governments, and helps ensure that materiel requirements are ready for delivery by the approved RAD.  The actual date for calculation of the RAD will be the last day of the month depicted by the RAD entries in the requisition.  Shipment of materiel will be made at the time of initial requisition processing to the extent that releasable assets are available, regardless of the number of lead time months shown in the RAD entry.  Materiel not immediately available should be acquired and shipped by the last day of the month depicted by the RAD entries.  However, depending on availability, materiel may be acquired and shipped after the RAD expires and cancellations are submitted.  Appropriate status will be provided to the address(es) designated in the requisition.

	C25.3.3.  For Grant Aid, as soon as practicable, but not later than 120 days after receipt of an approved funded order, the Service/Agency (S/A) Departments will place a RAD on the requisitions for major items, and the associated support equipment and initial issue parts, as determined by the S/A.

	C25.3.4.  RAD time begins with the date of the requisition (i.e., the date contained in the requisition document number (See Appendix 7.14)) and does not have the effect of holding release of the materiel.

	C25.3.5.  Requisition originators will modify the RADs when contract forecast delivery dates indicate availability of items at a time other than designated by the previously established RADs.  In inter-S/A actions, when requisitions or other documents bear a RAD with a shorter lead time than when the materiel will be available, the supplying S/A will promptly provide the requesting S/A with status reflecting the true availability date.  This will be accomplished by use of DLMS 870S Supply Status (MILSTRIP legacy DIC AE_) with Supply Status Code BB, BV, or B3, as appropriate.  The requesting S/A will adjust all records to reflect the new availability date information.  When the supplying S/A is aware that the established RAD will not be met, that S/A’s source of supply will advise the appropriate ILCO that the RAD will not be met due to slippage and internal processing.  The advice of RAD slippage will be furnished to the ILCO by letter, message, or DLMS 870S Supply Status (MILSTRIP legacy DIC AE_) with Supply Status Code B3.

	C25.3.6.  An extended required delivery date (RDD) in an FMS requisition will be expressed with the letter S in the first position, followed by the number of months from the date of the requisition before which delivery is required in the second and third positions.  The extended RDD is identified in the DLMS 511R Requisition by the special requirements code (2/LQ01/140 Code AL); in MILSTRIP legacy DIC A0_ transactions it is identified in rp 62-64.   

		C25.3.6.1.  The release date is defined as five days prior to the last day of the month indicated in the last two positions of the extended RDD.  Releasable assets will be held until 50 days prior to the last day of the indicated month.

		C25.3.6.2.  In the case of DLA support, the extended RDDs will cause intentional holding of support.  For those orders, the support date is calculated externally by DAAS upon receipt of the transaction and fed to DLA (RIC SMS).  DAAS sends RIC SMS the actual Standard Delivery Date, which in the case of extended RDDs will cause the order to go into BP status and be held until 50 days prior to the release date.

C25.4.  REQUISITION PREPARATION AND SUBMISSION

	C25.4.1.  Requisitions will be prepared and transmitted by Security Assistance countries and security assistance organizations (SAO) to the applicable ILCO in the appropriate MILSTRIP format as prescribed by the U.S. Service.  The ILCO will transmit FMS and Grant Aid requisitions to the appropriate source of supply in the prescribed DoD MILSTRIP format.

	C25.4.2.  Requisitions prepared by the U.S. Service for FMS and Grant Aid requirements will be transmitted to the appropriate source of supply in the prescribed MILSTRIP format.

	C25.4.3.  ILCOs will enter a cooperative logistics program support category code (CLPSC) (Appendix 7.22) to applicable requisitions and passing orders, in order to convey programmed/non-programmed status of a requisition to an ICP/integrated materiel manager (IMM).  The CLPSC is identified in the DLMS 511R Requisition by the cooperative logistics program support code (2/LQ01/140 Code 89) ; in MILSTRIP legacy DIC A0_ transactions it is identified in rp 72.  Supply support provided under cooperative logistics supply support arrangement (CLSSA) agreements is intended to provide support to the requiring nation on the same basis that support is provided to U.S. Forces, within assigned priority (based upon force or activity designator (F/AD)) and with all other coding being equal.  However, such support cannot be provided if it will impair the combat effectiveness of U.S. Forces.  Consequently, CLSSA support is not to be provided on the same basis as for U.S. Forces until after the expiration of a lead time period necessary to augment U.S. Stocks to support the agreement.  CLSSA requisitions received before the expiration of required lead time may be filled from existing supply source stocks only if stock levels do not drop below the established reorder point.  If sufficient stock balances are not available to fill such requisitions without dropping below the reorder point, sources of supply will initiate procurement action to fill the CLSSA requirement.  CLSSA requisitions received prior to expiration of the established lead times are considered to be “un-programmed” requirements.  Un-programmed CLSSA requisitions and passing orders will contain CLPSC 2 (Appendix 7.22).  CLSSA requisitions and passing orders received after expiration of the lead time required to augment stock levels will be processed in the same manner as U.S. demands.  Such requisitions and passing orders are considered to be “programmed” requirements and will contain CLPSC 1.  If the requisition does not identify a CLPSC code, the ICP/IMM will process it as an un-programmed requirement.

	C25.4.4.  Certain FMS and Grant Aid requisitions will be subject to a restriction in quantity when it is determined that the total requirement for an item will result in more than 25 shipment units.  This constraint is employed to preclude the assignment of non-MILSTRIP transportation control numbers (TCN) that occur when the number of shipment units exceeds 25 and that cause a loss of identity to the shipment.  The DoD Components must specify the items of equipment to which the quantity restriction applies.  Generally, these items are equipment such as wheeled/tracked vehicles or other items when a unit of issue of one each constitutes a single shipment unit.

	C25.4.5.  SA requisitions (identified by Service/Agency Code B, D, I, K, P, or T in the document number) will be reviewed for appropriate PD assignment by the ILCO prior to release.  Specific procedures to accomplish this may be deferred until implementation of the Defense Security Assistance Management System (DSAMS).  SA will not be revalidated by DAAS against the established edit table.  However, any SA requisitions with PD 01, 04, or 11 will be displayed as suspected abuse in the Unauthorized Priority Designator Report under the appropriate Service/Agency heading with no activity name.

***C25.4.6.  Security Cooperation Enterprise Solution (SCES) Interim State Logistics Routing Solution***

***C25.4.6.1.  Under the Security Cooperation Enterprise Solution (SCES) interim state logistics routing solution, if the Security Cooperation (SC) case designator indicates the FMS case is managed by SCES, the ILCO management information system will recode the FMS or Grant Aid requisition as a passing order (DIC A3_) and update the transaction with the applicable Defense Security Cooperation Agency (DSCA) RIC, distribution code, and fund code values based on the SC implementing agency code.[footnoteRef:3]*** [3:  Refer to Approved DLMS Change (ADC) 1177.] 

***C25.4.6.2.  After validation, SCES will convert the passing order to a requisition and transmit the FMS and Grant Aid requisitions to the appropriate source of supply.[footnoteRef:4]*** [4:  Ibid] 

C25.5.  STATUS IN GENERAL

	C25.5.1.  Sources of supply will provide status only to the ILCO or other monitoring activities identified by the distribution code.  The DLMS 870S (MILSTRIP legacy DIC AE3) will be used to provide supply status, and the DLMS 856S (MILSTRIP legacy DIC AS3) will be used to provide shipment status in response to follow-ups.  However, the DLMS 870S (MILSTRIP legacy DIC AE8)/DLMS 856S (MILSTRIP legacy DIC AS8) will be used for status initiated by the source of supply or as otherwise delegated.  It is the responsibility of the ILCO or monitoring activity to furnish status to the appropriate country status recipient.

	C25.5.2.  Status from the ILCO/monitoring activity to the MAPAD country status recipient will be transmitted through DAAS.

	C25.5.3.  Status to FMS customers is sent to the MAPAD type address code (TAC) 4 country status recipient.

	C25.5.4.  Status to Grant Aid customers is sent to the MAPAD TAC 3 purchaser/in-country SAO status recipient.

	C25.5.5.  The media and status (M&S) entry should be zero to preclude unnecessary status output.  The transmission medium is determined by DAAS.

C25.6.  STATUS UPON REQUISITION INITIATION OR SUBMISSION

	C25.6.1.  General.  Status is provided by the ILCO to the customer when the requisition enters the supply system.

	C25.6.2.  Service Initiated Requisitions.  When FMS requisitions are prepared and introduced by a U.S. Military Service, a supply status document representing the U.S. prepared requisition will be transmitted by the introducing U.S. Military Service to the appropriate MAPAD status recipient.  The supply status document may also be prepared for Continental United States (CONUS)-generated Grant Aid transactions and, when prepared, will be transmitted to the appropriate in-country SAO.  

		C25.6.2.1.  For MILSTRIP legacy DIC AE_, the supply status will contain code A, B, D, or E in the third position of the DIC to reflect the type of stock number being requisitioned.  

		C25.6.2.2.  The latest available unit price should be entered in the DLMS 870S in the Baseline Item Data segment (2/PO104/150); in MILSTRIP legacy DIC AE_ transactions, it is identified in rp 74-80; however, this is an optional entry depending on the capability of the involved Military Service.  

		C25.6.2.3.  Status Code BU will be entered in the DLMS 870S in the status code 2/LQ01/330 Code 81); in MILSTRIP legacy DIC AE_ transactions, it is identified in  rp 65-66.

		C25.6.2.4.  The estimated shipping date (ESD) may be left blank.  If provided, it is entered in the DLMS 870S in the Date/Time Reference segment (2/DTM01/240 Code 369; in MILSTRIP legacy DIC AE_ transactions, it is identified in rp 70-73.  

	C25.6.3.  Customer Initiated Requisitions

		C25.6.3.1.  When country prepared FMS requisitions are forwarded to sources of supply by the ILCO, a DLMS 870S (MILSTRIP legacy DIC AE2) citing Status Code BW will be provided to the customer.

		C25.6.3.2.  When Grant Aid requisitions prepared by the in-country SAO are forwarded to sources of supply by the ILCO, a DLMS 870S (MILSTRIP legacy DIC AE1) citing Status Code BW will be provided to the customer/SAO.

		C25.6.3.3.  The latest available unit price may be entered in the DLMS 870S in the Baseline Item Data segment (2/PO104/150); in MILSTRIP legacy DIC AE_ transactions, it is identified in rp 74-80.

		C25.6.3.4.  The ESD may be left blank.  If provided, it is entered in the DLMS 870S in the Date/Time Reference segment (2/DTM01/240 Code 369; in MILSTRIP legacy DIC AE_ transactions, it is identified in rp 70-73.

C25.7.  FOLLOW-UPS AND STATUS RESPONSES

	C25.7.1.  As authorized, follow-ups, modifiers, and cancellations for FMS and Grant Aid transactions may be submitted by the CR or in-country SAOs to the sources(s) designated by the individual U.S. Military Service administering the FMS case or Grant Aid program line.

	C25.7.2.  When follow-ups are submitted to the ILCO/monitoring activity, the latest status information will be furnished to the CR by the ILCO/monitoring activity.

	C25.7.3.  FMS requisition status will be provided in the DLMS 870S Supply Status (MILSTRIP Legacy DIC AE2) or the DLMS 856S Shipment Status (MILSTRIP legacy DIC AS2).

	C25.7.4.  Grant Aid requisition status will be provided in the DLMS 870S (MILSTRIP Legacy DIC AE1) or DLMS 856S (MILSTRIP legacy DIC AS1).

	C25.7.5.  When current status information is not available on requisitions that were submitted to the supply system, the ILCO/monitoring activity may transmit the follow-up to the appropriate source of supply or provide interim status to the customer pending completion of ILCO/monitoring activity follow-up action.  In either case, a supply status document containing Supply Status Code BW or BM (as indicated by the U.S. Military Service) and a blank ESD field may be provided to the customer.  When requisitions have not been introduced into the supply system, the ILCO/monitoring activity will provide a written reply to the customer originated follow-ups.

***C25.7.6.  Security Cooperation Enterprise Solution (SCES) Interim State Logistics Routing Solution.  Under the SCES interim state logistics routing solution, the ILCO management information system will forward follow-ups, modifiers, and cancellations to the applicable DSCA RIC based on the SC implementing agency code if the SC case designator indicates the FMS case is managed by SCES.[footnoteRef:5]*** [5:  Ibid] 

C25.8.  CANCELLATION AND REJECTION STATUS

	C25.8.1.  Cancellation and rejection status from the source of supply will be provided to the ILCO/monitoring activity using the DLMS 870S (MILSTRIP legacy DIC AE3) and the appropriate status code.

	C25.8.2.  DLMS 870S (MILSTRIP Legacy DIC AE1/AE2) supply status transactions will not be produced by the source of supply on FMS and Grant Aid requisitions.

C25.9.  STATUS ON FOREIGN MILITARY SALES NOTICE OF AVAILABILITY

	C25.9.1.  When FMS requisitions are processed and a NOA is forwarded to the FF/CR, a DLMS 870S (MILSTRIP legacy DIC AE2) supply status transaction containing Status Code BL will be furnished to authorized status recipients at the same time the NOA is forwarded.  

	C25.9.2.  The BL status advises that the item is available for shipment and was offered to the FF/CR on the date entered in the DLMS 870S in the Date/Time Reference segment (2/DTM01/240) Date/Time Qualifier 169 – Product Availability Date; in MILSTRIP legacy DIC AE2 transactions, it is identified in rp 70-73.

C25.10.  MODIFICATION OF FOREIGN MILITARY SALES OFFER RELEASE OPTION OR FREIGHT FORWARDER/COUNTRY REPRESENTATIVE

	C25.10.1.  Unusual circumstances may require a change in the country FMS offer release option code or FF/CR code for an FMS case or for individual requisitions within an FMS case.  When this condition exists, either FMS customers or ILCO/monitoring activity may initiate a DLMS 511M (MILSTRIP legacy DIC AM_) Requisition Modification to change the coded data in FMS requisitions that have been released to the supply system.

	C25.10.2.  FMS requisition modification transactions will be initiated under standard MILSTRIP procedures.  Entries in the requisition modifier transaction may differ from those in the original requisition only to reflect changes to one or any combination of the following:[footnoteRef:6] [6:  Revised requisition modifier procedures last reported as not implemented by the United States Marine Corps (USMC).  Refer to AMCL 123C.] 

		C25.10.2.1.  Media and status, Industry Code segment (2/LQ01/140 Code DF) (MILSTRIP legacy  rp 7)

		C25.10.2.2.  FMS offer release option code, Industry Code segment (2/LQ01/140 Code 95) (MILSTRIP legacy rp 46)

		C25.10.2.3.  Freight forwarder, Industry Code segment (2/LQ01/140 Code A6) (MILSTRIP legacy  rp 47)

		C25.10.2.4.  Signal code, Industry Code segment (2/LQ01/140 Code DE) (MILSTRIP legacy  rp 51)

		C25.10.2.5.  Fund code, Accounting Data segment (2/FA201/286 Code B5) – Fund Code (MILSTRIP legacy  rp 52-53)

		C25.10.2.6.  Distribution code, Industry Code segment (2/LQ01/140 Code AK) (MILSTRIP legacy  rp 54)

		C25.10.2.7.  Project code, Industry Code segment (2/LQ01/140 Code 78) (MILSTRIP legacy  rp 57-59)

		C25.10.2.8.  Priority designator, Industry Code segment (2/LQ01/140 Code 79) (MILSTRIP legacy  rp 60-61)

		C25.10.2.9.  Required availability date, Date/Time segment (2/G6201/80 Code BD) (MILSTRIP legacy  rp 62-64)

		C25.10.2.10.  Advice code, Industry Code segment (2/LQ01/140 Code 80) (MILSTRIP legacy  rp 65-66)

	C25.10.3.  Modifiers that change the country FMS offer release option or FF/CR must be submitted to procurement for manual amendment of contracts.  Customers are responsible for additional charges that may accrue.  To limit manual processing and avoid additional contract charges, modifiers that change the country FMS offer release options or FF/CRs should be submitted only when the change is mandatory.  When LOAs have not been amended to reflect the changes, FMS customers must coordinate with the Service ILCO/monitoring activity before requesting requisition modification.

C25.11.  RELEASE OF FOREIGN MILITARY SALES SHIPMENTS[footnoteRef:7] [7:  Refer to ADC1098, Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding DLMS 856N NOA and 870N NOA Reply.  DLMS implementation for SCES may be delayed until fully fielded to all the ILCOs (estimated for January 2019) ] 

	C25.11.1.  General. U.S. shipping activities use the NOA to notify the designated FF/CR addressee and the International Logistics Control Office (ILCO) (identified by the SC Implementing Agency) that materiel is ready for shipment.

		C25.11.1.1.  The procedures for releasing shipments of FMS materiel from storage activities are normally dependent upon the entry in the FMS offer release option field of requisitions or related transactions.  The exceptions to use of the FMS offer release option code in the release of shipments are:

			C25.11.1.1.1.  When the shipment is unclassified and is to be accomplished by parcel post/small parcel delivery service, the shipment will be released automatically without an NOA and should be either insured, certified, or registered.  Evidence of shipment must be provided for all FMS shipments regardless of shipment size, weight, or value.  Classified shipments always require use of an NOA, as indicated below.

			C25.11.1.1.2.  When an export release is required from the Military Surface Deployment and Distribution Command (SDDC) under DTR 4500.9-R, Chapter 203 (Shipper, Transshipper, and Receiver Requirements and Procedures), the shipping activity will submit a request for export release to the SDDC Operations Center before shipment.  An NOA will be furnished to the FF/CR and will indicate that an export release has been requested.  The export release provided by the SDDC releasing authority will include shipping instructions as coordinated with the FF/CR.

			C25.11.1.1.3.  When the shipping activity determines a need for a high degree of protection or control, or FMS Offer Release Option Code Z is indicated, the shipment must not be made until a response from the NOA is received.  Examples of a shipment requiring a high degree of protection or control include materiel that is dangerous/hazardous, or sensitive; these types of shipments may not require an export release.  Note that FMS offer release option Z procedures must be followed if any unusual transportation factors apply.  This includes oversize or overweight shipments, hazardous materiel shipments, classified shipments, sensitive shipments, and ammunition, arms and explosives shipments or any other factor that mandates coordinated release procedures (this does include Canada).  

			C25.11.1.1.4.  From SDDC, an NOA will be furnished to the FF/CR and the shipment will be held pending receipt of release and shipping instructions from the FF/CR.  NOAs for classified shipments will be forwarded to the CR identified in the MAPAD.

		C25.11.1.2.  For shipments not subject to the exceptions outlined in Paragraph C25.11.1.1., the entry in the FMS offer release option field will prescribe procedures to be followed in releasing shipments of FMS materiel from storage activities.  For FMS offer release options Y and Z, notification to the designated FF/CR is required prior to release of the shipment.  For FMS offer release option A or X, the shipment will be released automatically, without providing an NOA to the FF/CR.

		C25.11.1.3.  U.S. shipping activities use the NOA to notify both the designated FF/CR addressee and the ILCO that materiel is ready for shipment.  A manual NOA will be prepared for all FMS purchases except those customers specifically requesting mechanized NOAs such as the Federal Republic of Germany.  Countries desiring to receive the mechanized NOA will submit a request to the Director, Defense Enterprise Data Standards Office.  All purchasers requesting the mechanized NOA will be identified in this paragraph.  Procedures for NOA preparation are contained in Paragraphs C25.11.2. and C25.11.3.

		C25.11.1.4.  The NOA will identify the TCN assigned to the shipment, which will be created in accordance with guidance in DTR 4500.9-R, Appendix L.  The manual or mechanized NOA document will be assigned an NOA notice number to reflect the number of times the NOA has been sent to the FF/CR.

		C25.11.1.5.  ILCO Notifications.

			C25.11.1.5.1.  To provide the ILCO visibility to NOAs, shipping activities will send a DLMS 856N (No MILSTRIP Legacy DIC equivalent for this notification process) to the ILCO, even if a manual DD Form 1348-5 was sent to the FF/CR.  

			C25.11.1.5.2.  The ILCO will be identified as a party to receive copy in the DLMS 856N.  The ILCO will be identified by the SC Implementing Agency Code in the first position of the document number.  Authorized SC Implementing Agency codes are restricted to those identified in Appendix 7.2.  When the ILCO is identified as a party to receive copy, DAAS will route a copy of the DLMS 856N to the Security Cooperation Enterprise System (SCES).  SCES will then have the ability to associate NOA information with the applicable ILCO and FMS Case Designator. 

			C25.11.1.5.3.  For those systems not capable of sending a mechanized NOA, send an information copy of the NOA to the ILCO via offline methods (e.g., phone, fax, email).

	C25.11.2.  Manual Notice of Availability

		C25.11.2.1.  DD Form 1348-5, Notice of Availability/Shipment, will serve as a cover document for individual copies of DD Form 1348-1A, DD Form 250, or DD Form 1149 applicable to each line item in a shipment unit.  Together, these documents comprise the original NOA.  The data to be entered on DD Form 1348-5 (See Appendix 6.4) are those that describe the shipment unit, while the supporting copies of the DD Form 1348-1A provide individual item data.  All blocks of the DD Form 1348-5 from the top of the form to the portion captioned “CONSIGNEE INFORMATION” will be completed by initiating activities.  All data blocks are self-explanatory, except that the “NOA Notice Number” reflects the number of times the NOA has been sent to the FF/CR.  The TCN block represents the transportation control number, which is the TCN assigned to track the shipment.  The shipping activity must complete the “SPECIAL REQUIREMENTS” section for materiel discussed in Paragraph C25.11.1.1.3.  The manual NOA will be mailed to the notice recipient specified in the MAPAD, except that the NOAs covering classified shipments will be forwarded to the country representative.  Distribution of DD Form 1348-5 is as follows:

		C25.11.2.2.  Replies to manual NOAs will be performed by two different methods, contingent on the need for an export release.  When an export release is required, the FF/CR will furnish specifying consignment instructions, if any, and coordinate these or other shipment or delivery instructions with the SDDC releasing authority.  When an export release is not required, the reply will be accomplished by insertion of shipment release instructions on the third copy, which will be returned to the shipping activity.  Shipment release instructions will provide for shipment or delivery of materiel to a single destination by shipment unit.  Shipping activities will not split shipment units identified by shipment unit numbers to accommodate shipments or deliveries to multiple points.  Instructions to FF/CRs regarding replies to NOAs will specify the need for coordinated instructions when an export release is required and include provisions for the following minimum data in the replies to other NOAs:

			C25.11.2.2.1.  The complete name and address of the consignee except when materiel will be picked up by the FF/CR.

			C25.11.2.2.2.  The date materiel is to be shipped or the date the materiel will be picked up by the FFCR.

			C25.11.2.2.3.  The complete name and telephone number(s) of the individual(s) who will be available and authorized to receive materiel on behalf of the purchasing country, for the specific classified shipment covered by the NOA advising of the availability of a classified shipment.

		C25.11.2.3.  In instances where the shipment does not require an export release or the shipping activity determines there is no requirement for a high degree of protection or control and the FMS offer release option Y is indicated for the materiel, the shipment will be released to the FF/CR on the 15th calendar day after the NOA date, unless alternate shipping instructions are received.  When an export release is required, the shipment will be held pending receipt of release and shipping instructions from the SDDC releasing authority, and if such instructions are not received within 15 calendar days after the NOA date, follow-up to both SDDC and the ILCO in lieu of transmitting a duplicate NOA.  In instances where the shipping activity has determined a need for a high degree of protection or control or FMS offer release option Z is indicated, the shipment must be held pending receipt of release and shipping instructions from the FF/CR.  If an NOA response is not received within 15 calendar days of the NOA date, the shipping activity will send a follow-up to the designated NOA recipient using the same TCN.  The duplicate NOA will be annotated with the number 2 in the NOA Notice Number field to denote the second communication of the NOA and to indicate that release has been delayed due to non-response to the original NOA.  Two copies of the annotated DD Form 1348-5 (Notice of Availability/ Shipment), together with the applicable DD Form(s) 1348-1A, DD Form(s) 250, or DD Form(s) 1149 will be held as a record of the non-response to the original NOA.  If no response is received within 15 calendar days of the follow-up NOA, another follow-up will be sent with the number 3 in the NOA Notice Number field to indicate that release continues to be delayed due to non-response to the original and follow-up NOAs.  File copies will be updated to reflect the non-response and submission of a second follow-up.  Simultaneous with the second follow-up, the appropriate ILCO will be contacted (offline) for assistance and follow-up action to obtain the NOA response.  Upon receipt of the offline contact from the shipping activity, the ILCO must intervene, on behalf of the shipping activity, to obtain a response to the NOA so the open shipment action can be closed.  NOTE:  This follow-up procedure does not apply to Delivery Term Code (DTC) 8 releases.  DTC 8 releases involve materiel, usually Sensitive Arms, Ammunition and Explosives, which follow special export procedures that require more time to process than can be encompassed by the above follow-up procedure.

	C25.11.3.  Mechanized Notice of Availability.  Except for classified shipments or unclassified shipments to be accomplished by parcel post/small parcel delivery service, the mechanized FMS NOA is provided to customers having a need to receive mechanized data for FMS shipments when FMS offer release option Y or Z is indicated in requisitions or when an export release is required.  The mechanized NOA consists of the following documents:

		C25.11.3.1.  The initial DLMS 856N (MILSTRIP legacy DIC AD1 and ADR) contains both shipment unit information and line item information as contained in the DD Form 1348-1A.  When an export release is not required, indicate in the DLMS 856N beginning segment (1/BSN07/020 Code ENR); for MILSTRIP legacy transactions, use DIC AD1.  When an export release is required, indicate in the DLMS 856N beginning segment (1/BSN07/020 Code ERR); for MILSTRIP legacy transactions, use DIC ADR.  When export release instructions have not been received within 15 days of the NOA date, a follow-up will be made to the SDDC releasing authority.  If the FMS offer release option Y applies, do not prepare or transmit to the FF/CR a DLMS 856N Delay NOA (MILSTRIP legacy DIC AD3).  When FMS offer release option Z applies and release instructions have not been received within 15 calendar days of the initial NOA date, prepare and transmit a DLMS 856N Delay NOA citing beginning segment (1/BSN07/020 Code D50); for MILSTRIP Legacy transactions, a DIC AD3 will accompany the delay NOA detail documents.

		C25.11.3.2.  The DLMS 856N FMS NOA contains line item information as contained in the issue/release document (e.g., the MRO or DD Form 1348-1A).  For MILSTRIP legacy transactions, the initial detail document contains a DIC AD2.  When FMS offer release option Z applies and release instructions have not been received within 15 calendar days of the NOA date, a DLMS 856N Delay NOA will document all the line items using the hierarchical level loop (2/HL03/010 Code I); for MILSTRIP legacy transactions, a DIC AD4 will be prepared for each initial detail document that accompanied the initial key document.

		C25.11.3.3.  The DLMS 870N Notice of Availability Reply (MILSTRIP Legacy (DIC AD5) will always be used when replying to a mechanized NOA other than those requiring export release.  When replying to a DLMS 856N (MILSTRIP legacy DIC ADR), the specifying consignment instructions and/or other shipment or delivery instructions will be provided to the SDDC releasing authority to facilitate provision of a coordinated (export) release to the shipping activity.  In replying to mechanized NOAs other than those requiring export release, the following rules apply:

			C25.11.3.3.1.  When shipment release is to be made to the addresses identified by coded entries in the MAPAD, the NOA Reply will contain a Shipment Release Code R in the industry code segment (2/LQ01/145 Code 96).  For MILSTRIP legacy DIC AD5, the Shipment Release Code R is conveyed in rp 60.

			C25.11.3.3.2.  When shipment release instructions are being mailed under separate cover, the NOA Reply will contain a Shipment Release Code E in the industry code segment (2/LQ01/145 Code 96).  For MILSTRIP Legacy DIC AD5, the Shipment Release Code E is conveyed in rp 60.  The shipment release instructions may be communicated by letter, country designated forms, or other appropriate communications; however, such instructions must reach the shipping activity within 15 days for transactions coded with FMS offer release option Y.  Otherwise, the shipment will be released automatically to the appropriate address contained in the MAPAD.  The S/A implementation of these procedures will provide for such replies to be transmitted to the activity designated by the Routing Identifier Code (RIC) contained in the DLMS 856N Name segment (2/N101/220 Code CI).  For MILSTRIP legacy NOA documents, the RIC is in rp 4-6.

			C25.11.3.3.3.  When a country replies to an NOA and rejects the shipment because the shipment unit contains materiel that will constitute a duplicate shipment, the shipping activity will withdraw the rejected materiel from the shipment and prepare a new DLMS 856N NOA (MILSTRIP legacy DIC AD1 and AD2 or ADR and AD2).

			C25.11.3.3.4.  Shipments from Procurement.  RESERVED.

			C25.11.3.3.5.  Storage or staging charges may accrue when a NOA response (or failure to respond) requires the items to be held for an extended period of time.  Any storage costs are charged to the FMS case.

C25.12.  CONSOLIDATION AND MARKING OF FOREIGN MILITARY SALES AND GRANT AID SHIPMENTS

	C25.12.1.  Consolidation Requirements.  The shipment planning process should recognize and assure compatibility of codes in requisitions and related documents when configuring shipment units.  

		C25.12.1.1.  Exception to Consolidation.  Requisitions beginning with an N (Not Mission Capable Supply (NMCS)) or E (Anticipated Not Mission Capable Supply (ANMCS)) in the Special Requirements Code or containing the value 777 (N or E in MILSTRIP Legacy rp 62, or 777 in rp 62-64), will not be held for consolidation, but the NOA requirements remain in effect.  

		C25.12.1.2.  FMS Assembly Shipment Consolidation Eligibility.  FMS assembly shipments may be consolidated into containers or shipment units if under the same SC implementing agency, SC customer code, mark-for code, FMS delivery term code, Security Assistance program customer service designator (in-country service code), FMS offer release option code, FMS FF/CR code, FMS case and case line number, project code (if applicable), priority designator (PD), and distribution code.

		C25.12.1.3.  FMS Non-Assembly Shipment Consolidation Eligibility.  The criteria for FMS non-assembly shipments are the same as for FMS assembly shipments with the following exceptions:  non-assembly shipments may be consolidated regardless of case line number (CLN) and the distribution code is not considered.

		C25.12.1.4.  Grant Aid assembly and non-assembly shipments may be consolidated into containers or shipment units if under the same SC implementing agency, SC customer code, mark-for code, Grant Aid type of assistance/financing code, project code (if applicable), and PD.

		C25.12.1.5.  Consolidation will also be limited by the following conditions:

			C25.12.1.5.1.  Physical characteristics of items should be compatible with other items in the same shipment unit.

			C25.12.1.5.2.  Explosives or other dangerous articles must not be consolidated with other items.

			C25.12.1.5.3.  Aircraft, missiles, engines, and large (excess dimension) spares or assemblies for any item of equipment subject to special handling or construction, or requiring movement as a single shipment unit must not be consolidated with other line items.

			C25.12.1.5.4.  Radioactive or magnetic materiel must not be consolidated together or with other materiel.

			C25.12.1.5.5.  When shelf-life items are included in a consolidated shipment, the exterior of the consolidated shipping container must be marked under the multipack requirements of MIL-STD-129, "Military Standard Marking for Shipment and Storage.”

	C25.12.2.  Address Marking.  The manner of designating ship-to and/or mark-for addresses in requisitions is described in paragraph C25.2.1.2.3.  After determining the specific coded entries and their use as a ship-to and/or mark-for address in a given requisition, the corresponding clear-text address for container markings must be obtained from the MAPAD.

	C25.12.3.  Issue Release/Receipt Document (IRRD) (DD Form 1348-1A or DD Form 1348-2) Continuation Page.  All references in this chapter to DD Form 1348-1A and DD Form 1348-2 and its distribution will by direct association also apply to its continuation page as described in Chapter 29.  The continuation page contains encoded information for the automated processing of multiple serialized items in a shipment.

C25.13.  DOCUMENT DISTRIBUTION

	C25.13.1.  Military Assistance Program Grant Aid Documents

		C25.13.1.1.  DD Form 1348-1A.  Documentation to accompany shipments will be two copies of DD Form 1348-1A, Issue Release/Receipt Document.  See Figure C25.F1.

		C25.13.1.2.  DD Form 250.  On direct deliveries from vendors, a copy of DD Form 250, Material Inspection and Receiving Report, procurement shipping and receiving document, will be forwarded to the SAO of the country.

	C25.13.2.  Foreign Military Sales Documents.  DD Form 1348-1A.  Documentation to accompany shipments will be two copies of the IRRD.  See Figure C25.F1.  For shipments requiring an NOA, three copies of DD Form 1348-1A will accompany the NOA.

C25.14.  SPECIAL GRANT AID PROCEDURES

	C25.14.1.  When issues of excess materiel are made in support of reimbursable Grant Aid requisitions, the following actions must be initiated:

		C25.14.1.1.  Change signal code to D.

		C25.14.1.2.  Furnish BN supply status to designated address(es).

	C25.14.2.  When issues of DoD Defense Working Capital Fund (DWCF) stocks are made in support of reimbursable Grant Aid requisitions, type of assistance/financing code C is currently being used.  DWCF activities are billing for those after the fact.

C25.15.  CANCELLATION OF REQUISITIONS

	C25.15.1.  The rules governing cancellation of requisitions (see DLM 4000.25 Volume 2, Chapter 4, Paragraphs C4.4., C4.7.24, and C4.7.25) apply to FMS and Grant Aid except for special procedures herein.

	C25.15.2.  When individual line items with a Grant Aid program RCN are to be canceled, or FMS cases/programs are to be canceled, the canceling Agency/activity will submit single-line cancellation requests under the appropriate Service policy.

	C25.15.3.  FMS/Grant Aid single-line cancellation requests will be processed under DLM 4000.25 Volume 2, Chapter 4, Paragraph C4.7.24., except that:

		C25.15.3.1.  No tracer action will be initiated for FMS shipments to foreign purchasers that move in commercial transportation channels to commercial freight forwarders; they are therefore not available for cancellation after turnover to the commercial transportation carrier, post office, or freight forwarder.  For shipments that have already shipped, storage activities will furnish supply sources with a DLMS 856S shipment status (MILSTRIP Legacy DIC AU_).

		C25.15.3.2.  Sources of supply must advise the ILCO of contractual agreements that will result in cost conditions if cancellations, diversions, or holding are accomplished.  The ILCO decides whether the cancellation, diversion, or hold actions will be suspended or continued.  Decisions to continue cancellations or diversions must be provided to the source of supply by narrative message containing the notation:  “Decision for cancellation or diversion by ILCO.”

	C25.15.4.  FMS/Grant Aid mass cancellation requests will be processed under DLM 4000.25 Volume 2, Chapter 4, Paragraph C4.7.25, except that Security Assistance Program mass cancellation requests will be submitted with the required codes for identification of one of the following, for which cancellation of all requisitions is requested:

		C25.15.4.1.  SC implementing agency code and SC customer code

		C25.15.4.2.  SC implementing agency code and SC customer code and project code

		C25.15.4.3.  Federal supply classification (FSC) or federal supply group (FSG) when associated with a SC implementing agency code and SC customer code

	C25.15.5.  Transportation (such as the terminal costs associated with stopping, holding, and returning materiel to depots or storage) and procurement termination costs incident to actual diversion/cancellation of FMS requisitions will be charged under DoD 7000.14-R, “DoD Financial Management Regulation.”

	C25.15.6.  Grant Aid shipments that meet the criteria for shipment diversion under mass cancellation conditions will be diverted to the pre-designated storage sites of the canceling Service by the Defense Transportation Service (DTS).  Storage sites in receipt of Grant Aid cancellation shipment(s) will report the receipt(s) to the applicable Service ICP/ILCO and the materiel will be accounted for as suspended materiel pending receipt of disposition instructions.  Service ILCOs will provide disposition instructions under the provisions of DoD 5105.38-M, “Security Assistance Management Manual” (Part II).

	C25.15.7.  Navy-sponsored FMS shipments from vendor sources will be diverted to pre-designated Navy storage sites by the DTS.  FMS shipments sponsored by the other Services and Navy sponsored shipments from DoD/General Services Administration (GSA) storage activities will be diverted under DLM 4000.25 Volume 2, Paragraph C4.7.25.10.

C25.16.  REPAIR AND REPAIR/REPLACE PROGRAM

	C25.16.1.  General.  Purchasing countries can establish FMS cases to get items repaired, most commonly at the depot level.  Purchasing country repair requirements are integrated with the repair programs of the military services and are accomplished by organic military repair facilities (i.e., Army maintenance depots, Air Force logistics centers, Naval aviation depots, Naval shipyards) or by civilian contractors.  There are two concepts used in obtaining repairs under the FMS repairable program: 

		C25.16.1.1  Repair and Return.  The FMS customer must request approval for repair through the ILCO from the item/repair manager before shipping materiel to the U.S. for repair.  After receiving approval and shipping instructions from the item manager, the purchaser ships the materiel to the designated repair facility where it is entered into the repair queue.  After repairs are completed, the item is shipped back to the FMS customer.  In the repair and return program, the cost to the country is the actual cost of the repair in accordance with DoD 7000.14-R, Financial Management Regulation (FMR), Volume 15, Chapter 7.

		C25.16.1.2  Repair and Replace.  Under the repair and replace program, the unserviceable item is returned to the repair activity and, if it can be economically repaired or overhauled, a replacement item is issued from the U.S. Military Service’s stocks.  The country’s unserviceable item is repaired or overhauled and returned to the U.S. military service’s stocks. Under this program, countries are charged the estimated average cost of repairs (also referred to as net cost or exchange price).

	C25.16.2.  Repair Service Value.  The repair service value is the cost to repair or replace an FMS-origin item returned by an FMS customer.  The estimated or actual repair unit cost, as appropriate for the type of repair program, will be identified for use in specific business processes including status, shipment, and preparation of the subsequent billing statement by Defense Finance and Accounting Services (DFAS).  If actual cost varies among multiple items in a shipment, off-line manual processing may be used to communicate the applicable values.

		C25.16.2.1.  Supply Status.  When supply status (DLMS 870S/DIC AE_) is provided in association with a repair or repair/replace program, the repair service unit cost will be provided in place of the unit cost for the NSN (MILSTRIP legacy rp 74-80).

		C25.16.2.2.  Materiel Release Order (MRO).  When the repaired or replacement item is located in a DoD storage activity, the activity directing shipment must include the repair service unit cost on the release order (DLMS 940R/MILSTRIP legacy DIC A5_) so that it can be perpetuated to the shipment documentation.  The Air Logistics Complex has comparable ability via direct interface with a shipping Distribution Depot; for non-Air Logistics Complex locations, offline communications will be required to convey the repair cost information to the depot.

	C25.16.2.3.  Shipment Document.  The repair facility and/or the storage activity will include the estimated or actual repair service unit cost on the shipping document.  This is required for U.S. Customs export purposes.  For DoD storage activities, the repair service value will be perpetuated from the MRO and will be properly identified on the DD 1348-1A/2 (see Appendices 6.1, 6.35, and 8.48).

C25.17.  RETURN OF DISCREPANT FOREIGN MILITARY SALES MATERIEL

	C25.17.1.  Discrepancies in FMS shipments are reported on a Supply Discrepancy Report (SDR) (via SF 364, Report of Discrepancy, or equivalent under DLMS), by the receiving FMS customer through the applicable ILCO.  The required data entries and procedures for processing SDRs are provided in DLM 4000.25, DLMS Manual Volume 2, Chapter 17.

	C25.17.2.  When it is determined that materiel reported on an SDR is to be returned to U.S. supply systems stocks, the U.S. source of supply will provide the SDR reply to the applicable ILCO for distribution to the FMS customer.  The source of supply or the applicable ILCO will prepare DD Form 1348-1A to be used to return the materiel. The prepared form will contain entries shown in Appendix 8.50.  All DLA shipments resulting in an SDR due to a wrong item received will be returned to a CONUS DLA depot as part of the SDR process.

	C25.17.3.  The DTS will be used to return discrepant FMS materiel when appropriate.  This can be accomplished in two ways:

		C25.17.3.1.  If a transshipment point has not been specified and the SAO has the capability/capacity to perform this function, the SAO will arrange for movement through the DTS.

		C25.17.3.2.  If a transshipment point has been designated, the transshipment point will arrange for movement through the DTS.

		C25.17.3.3.  The transshipment point should be a U.S. Activity located in the FMS country that submitted the SDR and/or be reasonably accessible to the FMS country.

		C25.17.3.4.  At a minimum, the transshipment point will provide legible copies of the signed DD Form 1348-1A (evidencing receipt) to the U.S. source of supply, the appropriate CR listed in the MAPAD, and, if requested, to the consignor.  The latter two copies may be reproductions of the copy furnished to the source of supply.

		C25.17.3.5.  Coordination between the U.S. source of supply and the ILCO is required prior to initial designation as a transshipment point of an S/A other than that of the source of supply.

		C25.17.3.6.  When the DTS is not used for return of discrepant FMS materiel, the holding FMS country will arrange for movement through the FF/CR to the activity designated in Block 3 of DD Form 1348-1A.  CONUS inland shipments will be effected by the use of a collect commercial bill of lading (CCBL).  Reimbursement of transportation charges between the holding FMS country and the FF/CR will be requested by the CR to the U.S. supply source identified in the DD Form 1348-1A.

		C25.17.3.7.  Regardless of the method of transporting return-eligible discrepant FMS materiel, all shipments pursuant to these procedures must be completed within 180 days of the date of document preparation entered in Block 5 of the DD Form 1348-1A.

C25.18.  FMS TRANSPORTATION.  FMS transportation guidance may be found in the Security Assistance Management Manual (SAMM), DoD 5105.38M and the DTR 4500.9-R, Part II.

	C25.18.1.  FMS detention and demurrage charges are located in the Security SAMM, Chapter 7.

	C25.18.2.  FMS document retention requirements are defined in the DTR 4500.9-R, Appendix E, Paragraph Q.

C25-20	CHAPTER 25