Difference between revisions of "V1.4 SP 20.0"

From FPDS-NG
Line 26: Line 26:
 
<th width=18% align="center"><b>SPR #</b></th><th width=30% align="center"><b>Enhancement/Problem</b></th><th width=38% align="center"><b>Solution</b></th><th width=25% align="center"><b>Impact to Users and Integrators</b></th>
 
<th width=18% align="center"><b>SPR #</b></th><th width=30% align="center"><b>Enhancement/Problem</b></th><th width=38% align="center"><b>Solution</b></th><th width=25% align="center"><b>Impact to Users and Integrators</b></th>
 
<tr>
 
<tr>
−
<td style="width:95px" valign="center">FPDSHD-113057</td>
+
<td style="width:95px" valign="center">FPDSIRB-191</td>
−
<td>Users cannot correct the New Base after a Transfer Action if there are existing mods after it.
+
<td>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.
  
−
<td>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.
+
<td>In-Progress
−
 
 
−
This requirement shall apply to all Awards/IDVs.
 
  
 
</td>
 
</td>
Line 37: Line 35:
  
 
<tr>
 
<tr>
−
<td style="width:95px" valign="center">FPDSHD-113670</td>
+
<td style="width:95px" valign="center">FPDSIRB-192</td>
−
<td>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.
+
<td>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.
  
−
<td>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.
+
<td>In-Progress
  
 
</td>
 
</td>
Line 47: Line 45:
 
<tr>
 
<tr>
  
−
<td style="width:95px" valign="center">FPDSIRB-173</td>
+
<td style="width:95px" valign="center">FPDSIRB-193</td>
−
<td>The values for the "National Interest Action" (NIA) and "Local Area Set Aside" (LASA) are defaulted as "Select One" on error records.
+
<td>Other Transaction Standard Report offers only 2009 as the value for the search filter "Fiscal Year"
−
 
 
−
<td>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.
+
<td>In-Progress
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
Line 71: Line 54:
 
<tr>
 
<tr>
  
−
<td style="width:95px" valign="center">FPDSHD-84802</td>
+
<td style="width:95px" valign="center">FPDSHD-112915</td>
−
<td>The user reported a conflict between the posted requirement state and the behavior of the Referenced IDV Modification Number on the Other Transaction documents.
+
<td>If Recovery is the selected search criteria when running an ezSearch, no data is returned when data is downloaded via CSV or PDF.
  
−
<td>
+
<td>In-Progress
  
−
<b>Web Portal</b>:
+
</td>
 +
<td align="center">No</td>
  
−
1. FPDS-NG shall auto-populate the Referenced IDV Modification Number as per the Date Signed on the Order.
+
<tr>
  
−
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.
+
<td style="width:95px" valign="center">FPDSHD-116158</td>
 +
<td>Some documents are in the FPDS-NG live database, but not in the reporting database - discrepancies with live data in FPDS-NG versus the Data in the Standard Reports.
  
−
<b>Business Services</b>:
+
<td>In-Progress
 +
</td>
 +
<td align="center">No</td>
  
−
1. FPDS-NG shall auto-populate the Referenced IDV Modification Number as per the Date Signed on the Order in the following cases:
+
<tr>
−
 
 
−
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:
+
<td style="width:95px" valign="center">FPDSHD-115807</td>
−
 
+
<td>The user provided value for "Type of Set Aside" is being removed during the "Update" operation, when the tag is not sent. The "Approve" operation then fails as a result of the missing value.
−
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.
 
  
 +
<td>In-Progress
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
Line 105: Line 82:
 
<tr>
 
<tr>
  
−
<td style="width:95px" valign="center">FPDSHD-108437</td>
+
<td style="width:95px" valign="center">FPDSHD-115803</td>
−
<td>Modifications to the Other Transaction Order, Agreement and IDV are validating the PSC code although it propagates from the base.  
+
<td>Atom Feeds are showing the value for the "Maximum Order Limit" as '##################', where as the actual value is '$999,999,999,999,999,999.00'.  
  
−
<td>1. FPDS-NG shall not validate the PSC code on the modifications for the following documents:
+
<td>In-Progress
−
 
 
−
    Other Transaction IDV
 
−
    Other Transaction Order
 
−
    Other Transaction Agreement
 
−
 
 
−
2. The resolution applies to the FPDS-NG actions - Create, Update and Correct.
 
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
Line 120: Line 91:
 
<tr>
 
<tr>
  
−
<td style="width:95px" valign="center">FPDSHD-91657</td>
+
<td style="width:95px" valign="center">FPDSHD-114881</td>
−
<td>The Place of Performance Zip Code is retained when the Place of Performance Country Code is corrected from USA to a foreign country.
+
<td>The validation rules for "Inherently Governmental Function" are firing when the "Product or Service Code" is changed from a 'Service' to a 'Product'.
−
 
 
−
<td>
 
−
<b>For all agencies</b>:
 
−
 
 
−
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.
 
−
 
 
−
<b>For DHS and DoD</b>:
 
−
 
 
−
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.
 
−
 
 
−
<b>For NASA</b>:
 
−
 
 
−
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.
 
−
 
 
−
<b>For all agencies</b>:
 
−
 
 
−
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
 
  
 +
<td>In-Progress
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
  
 
<tr>
 
<tr>

Revision as of 14:12, 16 April 2013

Schedule

DescriptionStart Date End Date
BETA Installation Thursday June 13, 2013Thursday June 13, 2013
Functional Qualification Testing Friday June 14, 2013Thursday June 20, 2013
Installation in ProductionFriday June 28, 2013Friday June 28, 2013

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data Dictionary No
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesNo
ReportingNo
Online HelpNo
Computer-Based TrainingNo
User ManualNo

SPR Listing

SPR #Enhancement/ProblemSolutionImpact 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
FPDSIRB-193 Other Transaction Standard Report offers only 2009 as the value for the search filter "Fiscal Year" In-Progress No
FPDSHD-112915 If Recovery is the selected search criteria when running an ezSearch, no data is returned when data is downloaded via CSV or PDF. In-Progress No
FPDSHD-116158 Some documents are in the FPDS-NG live database, but not in the reporting database - discrepancies with live data in FPDS-NG versus the Data in the Standard Reports. In-Progress No
FPDSHD-115807 The user provided value for "Type of Set Aside" is being removed during the "Update" operation, when the tag is not sent. The "Approve" operation then fails as a result of the missing value. In-Progress No
FPDSHD-115803 Atom Feeds are showing the value for the "Maximum Order Limit" as '##################', where as the actual value is '$999,999,999,999,999,999.00'. In-Progress No
FPDSHD-114881 The validation rules for "Inherently Governmental Function" are firing when the "Product or Service Code" is changed from a 'Service' to a 'Product'. In-Progress No
Retrieved from "https://beta.fpds.gov/wiki/index.php?title=V1.4_SP_20.0&oldid=4325"