V1.4 SP 24.0
From FPDS-NG
Schedule
| Description | Start Date | End Date |
|---|---|---|
| BETA Installation | Friday June 13, 2014 | Monday June 16, 2014 |
| Functional Qualification Testing | Tuesday June 17, 2014 | Thursday June 19, 2014 |
| Installation in Production | Saturday June 28, 2014 | Saturday June 28, 2014 |
Document Changes
| Documentation | Changes Required |
|---|---|
| XML Specifications | No |
| Web Services | No |
| Data Dictionary | No |
| NASA Specific Data Dictionary | No |
| Use Case Summary | No |
| Validation Rules | Yes |
| Reporting | Yes |
| ezSearch | No |
| Atom Feeds | No |
| Online Help | No |
| Computer-Based Training | No |
| User Manual | No |
SPR Listing
| SPR # | Enhancement/Problem | Solution | Impact to Users and Integrators |
|---|---|---|---|
| FPDSNGIN-35 (SAM Entity Management File Load) | System for Award Management (SAM) will no longer be supporting the CCR legacy extracts after August 1, 2014. FPDS currently processes the CCR legacy extracts for vendor details in FPDS on a daily basis (daily delta extracts). | FPDS-NG daily vendor load process will be updated to integrate with the SAM Entity Management file format (daily delta files extracts). | No |
| FPDSNGIN-24(Google Chrome Browser Compatibility) | Informatica is not compatible with Google Chrome Version 34.0.1847.116 m. The user has the ability to execute Standard reports, but the report will not be displayed on the screen. The user has lost the ability to drill down the report, but it can be exported. This does not impact the user’s ability to report data to FPDS.
The Ad Hoc reports cannot be created in Google Chrome because the metrics and attributes cannot be selected | A software fix shall be performed, so the Informatica reporting tool is compatible with Google Chrome Version 34.0.1847.116 m.
Previous versions of Google Chrome will not be supported. |
Yes |
| FPDSNG-9125 (BPA Call Transfer Action) | The "Base and All Options Value" is closed on a V1.4 BPA Call Transfer Action, not allowing user input.
The "Base and All Options Value" from the Base record is incorrectly populated in the closed field on the Transfer Action Modification. | The "Base and All Options Value" shall be open for user input when using either Web Portal, Business Services, or GUI Services for a V1.4 BPA Call Transfer Action.
The "Base and All Options Value" provided by the user shall be retained and shall not be populated with the value from the Base. (modification number = '0') |
Yes |
| FPDSNG-8265 (Base and All Options Value Validation Rule) | The system incorrectly fires the validation rule “The "Base and All Options Value" cannot be '0.00' on a base document.” on the first modification after the transfer action (new base). This requires the user to input a value to approve the record. | The validation rule: 3A10: “The ‘Base and All Options Value’ cannot be ‘0.00’ on a base document” shall only fire on the base documents (modification number = '0'). The validation rule shall not fire on the first modification after the transfer action (new base). | Yes |
| FPDSNG-7256 (OT Order Referenced IDV Modification Number) | An OT Order cannot be successfully created via Business Services when the XML tag for Reference IDV Modification Number is not included in the XML request with a valid Modification Number value. The Reference IDV Modification Number is not required to be sent by the user because FPDS-NG shall select the correct IDV Modification for the OT Order to reference. The OT Order shall reference either the Base IDV or the latest Modification based on Date Signed of the OT Order.
FPDS-NG performs a check to ensure the Referenced IDV exists before creating the OT Order. Due to the software bug, this step fails if the user does not provide the Referenced IDV Modification Number, and the error that is returned is that the Referenced IDV does not exist. The OT Order is not created as a result. |
While using Business Services, FPDS-NG shall not require the user to send Referenced IDV Modification number in the XML Create request, and FPDS-NG shall select the correct Modification of the Referenced IDV, based on the Date Signed of the OT Order. |
Yes |
| FPDSNGIN-37 (Vendor Data Quality Enhancement) | To enhance the vendor data quality, FPDS-NG shall process the Monthly Complete SAM Entity Management Extracts in addition to the daily delta extracts. Monthly Complete Entity Management Extracts package is a complete file of active vendors in SAM. |
FPDS will establish a new process that will reconcile the differences between the Monthly Complete Entity Management Extracts refresh file and the FPDS vendor database |
No |