![]() |
DEFENSE SECURITY COOPERATION AGENCY |
11/23/2005 |
|
MEMORANDUM FOR : SEE DISTRIBUTION SUBJECT : Importance of FMS Case Delivery Reporting (DSCA 05-29) DSCA (DBO/ ADM) receives frequent and increasing requests for delivery data from the Congress, FMS customers, Security Assistance Offices, the Government Accountability Office and the DoD Inspector General (DoDIG). DSCA must rely on the integrity of the delivery data provided by the Implementing Agency (IA). Recently. however, DSCA received data showing deliveries to suspended countries, deliveries just reported for shipments that actually occurred several years prior and deliveries reported with significantly erroneous values. To help minimize recurrence of these problems and to promote awareness on the importance of FMS case delivery reporting, the following applies:
In summary, timely and accurate delivery reporting improves the integrity of the data that DSCA provides to the FMS purchasers and other stakeholders. Improved delivery reporting promotes better data integrity, increases our responsiveness to the purchaser's informational needs, enables a more efficient use of DoD resources, and facilitates case reconciliation and case closure. It is imperative that we all work together in order to provide accurate and timely delivery reporting. To that end, and as an outcome of the 25 - 27 May 2005 FMS Case Delivery Reporting Conference, DSCA is working to implement further improvements in the delivery reporting process. I encourage you to share this with your staff, particularly FMS case managers and others involved in the delivery reporting process. If you have any questions or need additional information concerning FMS case delivery reporting, please contact Alberta LaBelle, Administration and Management DSCA (DBA/ADM), telephone (703) 601-3738, DSN 329-3738, e-mail: alberta.labelle@dsca.mil. Keith B. Webster ATTACHMENT : DISTRIBUTION :
DEPUTY ASSISTANT SECRETARY OF THE ARMY CC :
DISAM |
||
|
Attachment A Table 1 - Constructive Delivery Report Generic Codes
Table 2 - 'C1' Transaction Format
|
|
Attachment B
|
|
Attachment C FOREIGN MILITARY SALES (FMS) DELIVERIES REPORTING IN DSCA 1200 SYSTEM FMS Physical (Constructive) Delivery Reporting The Implementing Agency submits FMS physical (constructive) delivery data for all major end items that have a unit of issue of "EA" for the generic codes provided in the Table below. Items are considered delivered when title passes to the purchaser. The title to FMS materiel normally transfers from the USG to the purchaser immediately upon its release from a DoD supply activity (point of origin). A supply activity can be either a DoD storage depot or a commercial vendor that furnishes materiel under a DoD-administered contract. Implementing Agencies report, within 30 days (after title passes to the purchases?), all constructive deliveries for applicable material lines to DFAS Denver's Defense Integrated Financial System (DIPS) by the 20thof each month in the Cl delivery transaction format (see Table below). DIPS, in turn, submits the data to the DSCA 1200 System. This information is used to prepare AECA required reports, respond to inquiries, and maintain a currently inventory of deliveries. Constructive Delivery Report Generic Codes
Delivery Transaction Formatt
Delivery Reporting Timelines Timely reporting of delivery information to the FMS purchaser is critical. Estimated price codes may be used to report deliveries of major end items if an actual price is not available within 30 days of the shipment date. Estimated price codes must be used to report deliveries of major end items if an actual price is not available within 90 days of the shipment date. All estimated billing must be converted to actual billings prior to closure. DIPS sends a monthly transaction file to DSCA that interfaces with DSCA 1200 Systems. This transaction file is named the SM File because the file has 'SM' in the first two characters of each record. Each record is one line on a case. DSCA keeps a static file of data here that is known as the SY File, which is identical to the SM File, with the exception that 'SY' is in the first two characters of each record. The SY File is line item data that was archived in DIPS many years ago. These two files are combined to form the data that is used to rebuild the Item Database each month. The following is the format of the two files: SM and SY Transaction
Notes:
|