Difference between revisions of "V1.5 SP 24.0"

From FPDS-NG

Line 24: Line 24:
 
</table>
 
</table>
  
==SPR Listing==
+
==Federal Procurement Data System (FPDS) Version 1.5 Service Pack Requirements (SPR) Listing==
 
<TABLE id="box-table-a" border=2 style="width: 1080px">
 
<TABLE id="box-table-a" border=2 style="width: 1080px">
 
<th width=12% 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 on Users and Integrators</b></th>
 
<th width=12% 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 on Users and Integrators</b></th>
<tr>
 
<td style="width:95px" valign="top">IAEMOD-37171
 
</td>
 
<td valign="top">Assistance Listings added after record goes to USAspending should be editable until next report</td>
 
<td valign="top">The FAADC application shall be updated so that Assistance Listings added after an Award is sent to USAspending remain editable until the next time the Award is sent. Currently, the editability of newly-added Assistance Listings is not operating as expected. New Assistance Listings become “locked” upon clicking ‘Save,’ but they should not be “locked” until the Award is sent to USAspending again.</td>
 
<td align="center">Yes</td>
 
</tr>
 
 
<tr>
 
<td style="width:95px" valign="top">IAEREQ-10106 / IAEMOD-37763
 
</td>
 
<td valign="top">Create new Validation Rule (4B5) comparing "Non-Federal Funding Amount" vs. "Total Federal Award Value" on Aggregate records</td>
 
<td valign="top">The FAADC application shall be updated to display a new validation rule (4B5) when the user clicks ‘Validate’, ‘Approve’ or ‘Save’ on an Aggregate Assistance Award if “Non-Federal Funding Amount” exceeds “Total Federal Award Value.”
 
<b>New Rule (4B5)</b> - The sum of "Non-Federal Funding Amount" for all actions with the same URI must be less than or equal to the sum of the “Total Federal Award Value” for all the actions with the same URI.
 
 
Currently, when the user validates, approves or corrects an Aggregate Assistance Award, no message displays if “Non-Federal Funding Amount” exceeds “Total Federal Award Value.”
 
 
<u>Note:</u> This rule will make the behavior of Aggregate awards consistent with the behavior of Non-Aggregate and Non-Aggregate Individual awards.
 
</td>
 
<td align="center">Yes</td>
 
</tr>
 
  
 
<tr>
 
<tr>
Line 92: Line 71:
 
<td align="center">Yes</td>
 
<td align="center">Yes</td>
 
</tr>
 
</tr>
 +
</table>
 +
 +
==Federal Assistance Award Data Collection (FAADC) Version 1.2 Service Pack Requirements (SPR) Listing==
 +
<TABLE id="box-table-a" border=2 style="width: 1080px">
 +
<th width=12% 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 on Users and Integrators</b></th>
 +
 +
<tr>
 +
<td style="width:95px" valign="top">IAEREQ-10106 / IAEMOD-37763
 +
</td>
 +
<td valign="top">Validation Rule for FAADC V1.2 will be corrected related to Aggregate Records</td>
 +
<td valign="top">An update to the validation rule (4B5) shall be implemented for "Aggregate" records in FAADC V1.2. This rule displays an error message when the "Non-Federal Amount" exceeds the "Total Federal Award Value." Currently, no message displays on “Aggregate” records. This fix will ensure that the behavior of "Aggregate" records is consistent with the behavior of “Non-Aggregate” and “Non-Aggregate Individual” records.</td>
 +
<td align="center">Yes</td>
 +
</tr>
 +
 +
 +
<tr>
 +
<td style="width:95px" valign="top">IAEMOD-37171
 +
</td>
 +
<td valign="top">Editable Assistance Listings after Award Submission</td>
 +
<td valign="top">Currently, when a Federal Assistance Award(s) is submitted to USAspending and later corrected to add new Assistance Listings, the newly added Assistance Listings records become locked (grayed out) upon clicking ‘Save’, preventing further modifications. This behavior is unintended and restricts necessary updates. To resolve this, the FAADC application shall be updated to ensure that newly added Assistance Listings remain editable until the next FABS report publication, allowing users to make necessary adjustments before the next reporting cycle occurs.</td>
 +
<td align="center">Yes</td>
 +
</tr>
 +
  
 
</table>
 
</table>

Revision as of 21:57, 19 March 2025

Schedule

DescriptionStart Date End Date
Beta DeploymentMarch 31, 2025March 31, 2025
Government Acceptance Testing April 8, 2025April 11, 2025
Production Deployment April 19, 2025April 19, 2025

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data DictionaryYes
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesNo
ezSearchNo
Atom FeedsNo
Online HelpNo
User ManualNo

Federal Procurement Data System (FPDS) Version 1.5 Service Pack Requirements (SPR) Listing

SPR #Enhancement/ProblemSolutionImpact on Users and Integrators
IAEENH-1294 / IAEMOD-39084 Add Product Service Code (PSC) 9105 version April 2025 The FPDS application shall be updated to add a new Product Service Code, 9105, for Electric Power Supply from Third Party Generation Entity, creating a clear distinction from electricity procured as part of a utility service.

Details of the above changes will be available here after the production deployment.

Yes
IAEMOD-39466 Updated Unique Entity ID does not save new Address when the “Reason for Modification” is ‘Novation’ on Other Transaction IDV Modifications The FPDS application shall be updated to retain the new Unique Entity Address on an Other Transaction IDV modification when ‘Novation Agreement’ is selected as the “Reason for Modification.” Yes
IAEMOD-39468 Ellipsis search does not return existing Other Transaction Indefinite Delivery Vehicle The FPDS application shall be updated to return an existing Other Transaction IDV PIID, when the user searches for it by clicking the “Ellipsis” button. When creating an Other Transaction Order, the user may enter an Other Transaction IDV PIID as the “Reference IDV” manually or click the “Ellipsis” button to search for one. Currently, the “Ellipsis” button search does NOT return an existing Other Transaction IDV PIID. Yes
IAEMOD-39487 “Other OT Award ID” and “Other OT IDV ID” fields not filled in Search Results for Other Transaction records created as ‘Change PIID’ Modifications The FPDS application shall be updated so the "Other OT Award ID" or "Other OT IDV ID" field displays the original PIID in the Advanced Search Results for Other Transaction records created as ‘Change PIID’ modifications. Currently, when the user searches for an Other Transaction record created as a 'Change PIID' modification, the base and existing modifications appear in the Advanced Search Results list, but the "Other OT Award ID" or "Other OT IDV ID" field, respectively, does not display the original PIID as expected. Yes
IAEMOD-40488 Value for “Information Technology Commercial Category” is removed on Award Modifications when Corrected The FPDS application shall be updated to retain the value of the "Information Technology Commercial Category" data element on a finalized Award modification (which propagated from the Base record when the modification was created) when the Award modification is corrected. Currently, when a finalized Award modification is corrected, the value of the "Information Technology Commercial Category" data element (which propagated from the Base record) disappears from that modification only upon clicking ‘Save.’ Yes

Federal Assistance Award Data Collection (FAADC) Version 1.2 Service Pack Requirements (SPR) Listing

SPR #Enhancement/ProblemSolutionImpact on Users and Integrators
IAEREQ-10106 / IAEMOD-37763 Validation Rule for FAADC V1.2 will be corrected related to Aggregate Records An update to the validation rule (4B5) shall be implemented for "Aggregate" records in FAADC V1.2. This rule displays an error message when the "Non-Federal Amount" exceeds the "Total Federal Award Value." Currently, no message displays on “Aggregate” records. This fix will ensure that the behavior of "Aggregate" records is consistent with the behavior of “Non-Aggregate” and “Non-Aggregate Individual” records. Yes
IAEMOD-37171 Editable Assistance Listings after Award Submission Currently, when a Federal Assistance Award(s) is submitted to USAspending and later corrected to add new Assistance Listings, the newly added Assistance Listings records become locked (grayed out) upon clicking ‘Save’, preventing further modifications. This behavior is unintended and restricts necessary updates. To resolve this, the FAADC application shall be updated to ensure that newly added Assistance Listings remain editable until the next FABS report publication, allowing users to make necessary adjustments before the next reporting cycle occurs. Yes