V1.4 SP 20.0
From FPDS-NG
Schedule
| Description | Start Date | End Date |
|---|---|---|
| BETA Installation | Thursday June 13, 2013 | Friday June 14, 2013 |
| Functional Qualification Testing | Monday June 17, 2013 | Friday June 21, 2013 |
| Installation in Production | Friday June 28, 2013 | Friday June 28, 2013 |
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 | Yes |
| Atom Feeds | Yes |
| Online Help | No |
| Computer-Based Training | No |
| User Manual | No |
SPR Listing
| SPR # | Enhancement/Problem | Solution | Impact to Users and Integrators |
|---|---|---|---|
| FPDSIRB-191 | Change PIID modification after the Transfer Action is not firing the IGF rules during Create, but is firing them during Correct. The IGF rules are 6M12, 6M13, 6M14, 6M15 and 6M16. | In-Progress | No |
| FPDSIRB-192 | Other Transaction documents (Other Transaction IDV, Other Transaction Order and Other Transaction Agreement) are allowing a PSC that is less than 4 characters in length. | In-Progress | No |
| FPDSHD-116158 | It is reported that records are missing from FPDS-NG Standard Reports, but the data exists in the Award database. The records missing from reports are found to not have data in two of the tables containing vendor information about each record. The missing data in these tables has caused the records to not be included in the nightly refresh that would include them in the Standard Reports, Ad Hoc reports, ezSearch, and Atom Feeds. | FPDS-NG shall store complete Vendor information on all Final records to ensure the records appear in Standard Reports, Ad Hoc reports, ezSearch, and Atom Feeds. | No |
| FPDSHD-115807 | FPDS-NG is incorrectly propagating the value for TOSA on an ‘update’ XML request when “Fair Opportunity/Limited Sources” is either ‘Competitive Set Aside’ or ‘Sole Source’. | FPDS-NG shall not propagate the value for TOSA from the IDV when “Fair Opportunity/Limited Sources” is either ‘Competitive Set Aside’ or ‘Sole Source’. | No |
| FPDSHD-115803 | When the length of the “Maximum Order Limit” value is greater than ‘15’, the Atom Feeds are not displaying the value as expected. |
1. FPDS-NG shall display a validation rule on the IDVs indicating that the length of the “Maximum Order Limit” shall not exceed 20. The length includes the two decimal places. Sample edit: Length of the “Maximum Order Limit” shall not exceed 20. The maximum value allowable value is ‘999,999,999,999,999,999.99’. 2. Atom Feed requests (DoD and Public) shall display the “Maximum Order Limit” value as provided on the IDVs. The value shall be retrieved with two decimal places. E.g.: 99999999999999.00. 3. The Data Validation Rules document for V 1.3 and V 1.4 shall be updated with the new validation rule. |
No |
| FPDSHD-114881 | The validation rules for "Inherently Governmental Function" are firing when the "Product or Service Code" is corrected from a 'Service' to a 'Product'. | On the base document:
1. FPDS-NG shall not fire 6M12, 6M13, 6M14 when the PSC is corrected from a Service to a Product. This applies to ‘Correct’ of the documents. 2. FPDS-NG shall not fire 6M16 when the Date Signed is prior to 03/01/2012 and when the PSC is a Product. This applies to ‘Create-Update-Validate-Approve’ of the documents. On the non-Change PIID modification done against a base (mod 0) document: 1. FPDS-NG shall not fire 6M14 (6M15 shall continue to display) when the PSC is corrected from a Product to a Service, and when the Date Signed on the base document is earlier than 03/01/2012. This applies to ‘Correct’ of the documents. |
No |
| FPDSHD-116863 | The business size is not being propagated from the base to the vendor address change; it is incorrectly stopping here. | In-Progress | No |