V1.4 SP 20.0
From FPDS-NG
Schedule
| Description | Start Date | End Date |
|---|---|---|
| BETA Installation | Thursday June 13, 2013 | Thursday June 13, 2013 |
| Functional Qualification Testing | Friday June 14, 2013 | Thursday June 20, 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 | No |
| Reporting | No |
| Online Help | No |
| Computer-Based Training | No |
| User Manual | No |
SPR Listing
| SPR # | Enhancement/Problem | Solution | Impact to Users and Integrators |
|---|---|---|---|
| FPDSHD-113057 | Users cannot correct the New Base after a Transfer Action if there are existing mods after it. | For the FPDS-NG action ‘correct’, FPDS-NG shall not restrict users from correcting a ‘New Base’ irrespective of the Award/IDV Status of any subsequent Modifications.
This requirement shall apply to all Awards/IDVs. |
No |
| FPDSHD-113670 | When correcting base contracts, the “Contracting Officer’s Determination of Business Size” value on any Rerepresentation mods is getting overridden with that from the base. | When the base contract is corrected, FPDS-NG shall not propagate “Contracting Officer's Business Size Selection” from the base to the ‘Rerepresentation’ or ‘Rerepresentation of non-Novated Merger/Acquisition’ modification. | No |
| FPDSIRB-173 | The values for the "National Interest Action" (NIA) and "Local Area Set Aside" (LASA) are defaulted as "Select One" on error records. | 1. FPDS-NG shall retain the user provided values for NIA and LASA on the base errored out documents.
2. FPDS-NG shall retain the user provided values for NIA and the propagated value of LASA on the modification errored out documents. 3. The following documents shall be addressed: Purchase Order Delivery/Task Order Definitive Contract BPA Call FSS GWAC BOA BPA Call IDC 4. The resolution applies the FPDS-NG actions - Create and Update. |
No |
| FPDSHD-84802 | The user reported a conflict between the posted requirement state and the behavior of the Referenced IDV Modification Number on the Other Transaction documents. |
Web Portal: 1. FPDS-NG shall auto-populate the Referenced IDV Modification Number as per the Date Signed on the Order. 2. If the Date Signed is not provided on the Order, but an attempt is made to select the Referenced IDV, then FPDS-NG shall consider the System Date and auto-populate the respective Referenced IDV Modification Number. Business Services: 1. FPDS-NG shall auto-populate the Referenced IDV Modification Number as per the Date Signed on the Order in the following cases: a. The Referenced IDV Modification Number is provided as ‘0’. b. The Referenced IDV Modification Number is provided as not ‘0’. c. The Referenced IDV Modification Number tag is not sent. d. The Referenced IDV Modification Number tag is sent, but the value is not provided. 2. If the Date Signed is not provided on the Order, but an attempt is made to select the Referenced IDV, then FPDS-NG shall consider the System Date and auto-populate the respective Referenced IDV Modification Number in the following cases: a. The Referenced IDV Modification Number is provided as ‘0’. b. The Referenced IDV Modification Number is provided as not ‘0’. c. The Referenced IDV Modification Number tag is not sent. d. The Referenced IDV Modification Number tag is sent, but the value is not provided. All the above requirements shall apply to the ‘Create’ operation. They also apply to the ‘Update’ and ‘Correct’ operations when the “Date Signed’ is changed on the Order. |
No |
| FPDSHD-108437 | Modifications to the Other Transaction Order, Agreement and IDV are validating the PSC code although it propagates from the base. | 1. FPDS-NG shall not validate the PSC code on the modifications for the following documents:
Other Transaction IDV Other Transaction Order Other Transaction Agreement 2. The resolution applies to the FPDS-NG actions - Create, Update and Correct. |
No |
| FPDSHD-91657 | The Place of Performance Zip Code is retained when the Place of Performance Country Code is corrected from USA to a foreign country. |
For all agencies: If the “Place of Performance Country Code” is changed from ‘USA’ to a foreign country, then the values for “Place of Performance Zip Code” and “Place of Performance Zip +4 Code” shall be cleared out for the following documents: Purchase Order Delivery/Task Order Definitive Contract BPA Call Note: US Territories are not foreign. For DHS and DoD: If the “Place of Performance Country Code” is changed from ‘USA’ to a foreign country, then the values for “Place of Performance Zip Code” and “Place of Performance Zip +4 Code” shall be cleared out for the following documents: Other Transaction IDV Other Transaction Order Other Transaction Agreement Note: US Territories are not foreign. For NASA: If the “Place of Performance Country Code” is changed from ‘USA’ to a foreign country, then the values for “Place of Performance Zip Code” and “Place of Performance Zip +4 Code” shall be cleared out for the following documents: Intragovernmental Cooperative Agreement Training Grant Funded Space Act Agreement Grant for Research Note: US Territories are not foreign. For all agencies: The above requirements shall apply to the 'Update' and 'Correct' FPDS-NG actions, and through Web Portal and Business Services. For Business Services, the Zip Code value must be cleared out for the following scenarios: When the tag is not sent When the tag is sent without the value When the tag is sent with a value |
No |