Difference between revisions of "V1.5 SP 9.0 Fast Path"

From FPDS-NG

(Created page with "__NOEDITSECTION__ ==Schedule== February 20, 2021 Fast Path <TABLE id="box-table-a" border=2> <tr><th width=30% align="center"><b>Description</b></th><th width=34% align="cent...")
 
 
Line 8: Line 8:
 
<tr><td nowrap>Production Deployment </td><td nowrap>Feburary 20, 2021</td><td nowrap>Feburary 20, 2021</td></tr>
 
<tr><td nowrap>Production Deployment </td><td nowrap>Feburary 20, 2021</td><td nowrap>Feburary 20, 2021</td></tr>
 
</table>
 
</table>
 +
 +
 
March 6, 2021 Fast Path
 
March 6, 2021 Fast Path
 
<TABLE  id="box-table-a" border=2>
 
<TABLE  id="box-table-a" border=2>
Line 15: Line 17:
 
<tr><td nowrap>Production Deployment </td><td nowrap>March 6, 2021</td><td nowrap>March 6, 2021</td></tr>
 
<tr><td nowrap>Production Deployment </td><td nowrap>March 6, 2021</td><td nowrap>March 6, 2021</td></tr>
 
</table>
 
</table>
 +
 
==Document Changes==
 
==Document Changes==
 
<TABLE border=2 id="box-table-a">
 
<TABLE border=2 id="box-table-a">
Line 29: Line 32:
 
<tr><td nowrap>Online Help</td><td align="center">No</td></tr>
 
<tr><td nowrap>Online Help</td><td align="center">No</td></tr>
 
<tr><td nowrap>User Manual</td><td align="center">No</td></tr>
 
<tr><td nowrap>User Manual</td><td align="center">No</td></tr>
 +
 
</table>
 
</table>
 
==SPR Listing==
 
==SPR Listing==
Line 35: Line 39:
 
<tr>
 
<tr>
 
</table>
 
</table>
 +
 
<TABLE id="box-table-a" border=2 style="width: 1080px" align="center">
 
<TABLE id="box-table-a" border=2 style="width: 1080px" align="center">
 
<td>The following items were originally scheduled to be deployed as part of FPDS V1.5 Service Pack (SP) 9. However due to the schedule re-assessment of FPDS SP 9, items that are not tied to UEI changes are being deployed ahead of the final SP9 release. The following items were deployed to production FPDS on Saturday, February 20, 2021:
 
<td>The following items were originally scheduled to be deployed as part of FPDS V1.5 Service Pack (SP) 9. However due to the schedule re-assessment of FPDS SP 9, items that are not tied to UEI changes are being deployed ahead of the final SP9 release. The following items were deployed to production FPDS on Saturday, February 20, 2021:
 
</td>
 
</td>
 
</table>
 
</table>
 +
 
<tr>
 
<tr>
 +
 +
 +
 +
 +
 
<TABLE id="box-table-a" border=2 style="width: 1080px">
 
<TABLE id="box-table-a" border=2 style="width: 1080px">
 
<tr>
 
<tr>
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
IAEREQ-3348, IAEREQ- 3475, RTC 56706
 
IAEREQ-3348, IAEREQ- 3475, RTC 56706
 +
 
</td>
 
</td>
 
<td>Business Size is not being saved on a Novation Agreement.
 
<td>Business Size is not being saved on a Novation Agreement.
−
<td>This item will resolve a defect for a subset of contract actions, when selecting "Reason for Modification" of 'Novation Agreement', and the user selects a different value for the data element 'Contracting Officer's Business Size Selection,' the new selected value is not retained when saving the modification when the DUNS is unchanged from the base Contract Action Report. This defect is only present on Awards and is not present on IDV contract action reports.
+
 
 +
<td>This item will resolve a defect for a subset of contract actions, when selecting “Reason for Modification” of 'Novation Agreement', and the user selects a different value for the data element 'Contracting Officer's Business Size Selection,' the new selected value is not retained when saving the modification when the DUNS is unchanged from the base Contract Action Report. This defect is only present on Awards and is not present on IDV contract action reports.
 +
 
 
</td>
 
</td>
 +
 
<td align="center">No</td>
 
<td align="center">No</td>
 
<tr>
 
<tr>
 +
 
<tr>
 
<tr>
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
RTC-57885
 
RTC-57885
 +
 
</td>
 
</td>
 +
 
<td>The correction functionality is not working on the Data Element Solicitation Date
 
<td>The correction functionality is not working on the Data Element Solicitation Date
 +
 
 
<td>Solicitation Date is being removed from Awards when the referenced IDV is corrected
 
<td>Solicitation Date is being removed from Awards when the referenced IDV is corrected
 +
 
</td>
 
</td>
 +
 
<td align="center">No</td>
 
<td align="center">No</td>
 
<tr>
 
<tr>
 +
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
RTC- 56501
 
RTC- 56501
 +
 
</td>
 
</td>
 +
 
<td>Part 13 BPA is not retaining the correct DUNS when the Date Signed is changed on a modification.
 
<td>Part 13 BPA is not retaining the correct DUNS when the Date Signed is changed on a modification.
 +
 
 
<td>This item will resolve a defect where a 'Novation Agreement' modification DUNS number reverts back to the original/base document DUNS number after a new modification document is corrected to a Date Signed earlier than the Novation Agreement document.
 
<td>This item will resolve a defect where a 'Novation Agreement' modification DUNS number reverts back to the original/base document DUNS number after a new modification document is corrected to a Date Signed earlier than the Novation Agreement document.
 +
 
</td>
 
</td>
 +
 
<td align="center">No</td>
 
<td align="center">No</td>
 
<tr>
 
<tr>
 +
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
RTC-48831
 
RTC-48831
 +
 
</td>
 
</td>
−
<td>"Subcontract Plan" retention on a Part 13 BPA Call.
+
 
−
<td>This item will resolve a defect where the Data Element "Subcontract Plan" value is not being retained on a BPA Call 13.
+
<td>“Subcontract Plan” retention on a Part 13 BPA Call.
 +
 
 +
<td>This item will resolve a defect where the Data Element “Subcontract Plan” value is not being retained on a BPA Call 13.
 +
 
 
</td>
 
</td>
 +
 
<td align="center">No</td>
 
<td align="center">No</td>
 
<tr>
 
<tr>
 +
 +
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
RTC-57538
 
RTC-57538
 +
 
</td>
 
</td>
 +
 
<td>System error incorrectly firing on Contract Action Report (CAR)
 
<td>System error incorrectly firing on Contract Action Report (CAR)
 +
 
 
<td>Invalid XML System error message firing on PIID W912DY10F0692, requiring code fix to resolve
 
<td>Invalid XML System error message firing on PIID W912DY10F0692, requiring code fix to resolve
 +
 
</td>
 
</td>
 +
 
<td align="center">No</td>
 
<td align="center">No</td>
 
<tr>
 
<tr>
 +
 
<TABLE id="box-table-a" border=2 style="width: 1080px" align="center">
 
<TABLE id="box-table-a" border=2 style="width: 1080px" align="center">
 
<td>The following items were originally scheduled to be fixed with Service Pack (SP) 9. However due to the schedule re-assessment of FPDS SP9, items that are not tied to UEI changes are being deployed ahead of the final SP9  release. The following items shall be deployed to production FPDS on Saturday, March 6, 2021:
 
<td>The following items were originally scheduled to be fixed with Service Pack (SP) 9. However due to the schedule re-assessment of FPDS SP9, items that are not tied to UEI changes are being deployed ahead of the final SP9  release. The following items shall be deployed to production FPDS on Saturday, March 6, 2021:
 
</td>
 
</td>
 
</table>
 
</table>
 +
 
<TABLE id="box-table-a" border=2 style="width: 1080px">
 
<TABLE id="box-table-a" border=2 style="width: 1080px">
−
<td style="width:95px" valign="center">
+
 
−
IAESAM-849, RTC 55778
 
−
<td>Display "Approved Date" at the top of FPDS CAR screens.
 
−
<td>The "Approved Date" and "Approved By" will be displayed on the FPDS Screens in the Transaction Information Section.
 
−
See screenshot below:
 
−
https://beta.fpds.gov/downloads/ApprovedDate_onscreen.png
 
−
Note: Currently, these values are saved in applicable FPDS database tables but are not displayed on the screens.
 
−
</td>
 
−
<td align="center">No</td>
 
−
<tr>
 
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
RTC-57378
 
RTC-57378
 
</td>
 
</td>
−
<td>IDV Modification records signed after a 'Novation Agreement' modification do not retain the correct "Subcontract Plan" value.  
+
 
−
<td>This item will resolve a defect where the value for "Subcontract Plan" does not propagate to subsequent modifications that are signed after a 'Novation Agreement' modification. This occurs only when the 'Novation Agreement' modification is corrected, the DUNS number is unchanged, and the user updates the value for "Subcontract Plan." A data management update will be performed to correct existing records affected by this defect.
+
<td>IDV Modification records signed after a ‘Novation Agreement’ modification do not retain the correct “Subcontract Plan” value.  
 +
 
 +
<td>This item will resolve a defect where the value for “Subcontract Plan” does not propagate to subsequent modifications that are signed after a ‘Novation Agreement’ modification. This occurs only when the ‘Novation Agreement’ modification is corrected, the DUNS number is unchanged, and the user updates the value for “Subcontract Plan.” A data management update will be performed to correct existing records affected by this defect.
 
</td>
 
</td>
 +
 
<td align="center">No</td>
 
<td align="center">No</td>
 
<tr>
 
<tr>
 +
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
RTC-56838
 
RTC-56838
 
</td>
 
</td>
−
<td>Other Transaction Awards are omitting the "Congressional District Place of Performance" field when using the Print function.
+
 
−
<td>This item will resolve a defect where the selected value for data element "Congressional District Place of Performance" is not displaying when printing Other Transaction Awards.
+
<td>Other Transaction Awards are omitting the “Congressional District Place of Performance” field when using the Print function.
 +
 
 +
<td>This item will resolve a defect where the selected value for data element “Congressional District Place of Performance” is not displaying when printing Other Transaction Awards.
 
</td>
 
</td>
 +
 
<td align="center">No</td>
 
<td align="center">No</td>
 +
 
<tr>
 
<tr>
 +
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
RTC-56499
 
RTC-56499
 
</td>
 
</td>
−
<td>"Simplified Procedures for Certain Commercial Items" is grayed out on a Delivery Order (DO) against a Basic Order Agreement (BOA).
+
 
−
<td>This item will resolve a defect where the required data element "Simplified Procedures for Certain Commercial Items" is closed on a DO against BOA.<br>
+
<td>“Simplified Procedures for Certain Commercial Items” is grayed out on a Delivery Order (DO) against a Basic Order Agreement (BOA).
 +
 
 +
<td>This item will resolve a defect where the required data element “Simplified Procedures for Certain Commercial Items” is closed on a DO against BOA.<br>
 
</td>
 
</td>
 +
 
<td align="center">No</td>
 
<td align="center">No</td>
 +
 
<tr>
 
<tr>
 +
 
<tr>
 
<tr>
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
RTC-46829
 
RTC-46829
 
</td>
 
</td>
−
<td>"Additional Reporting" is unavailable for selection when "SAM Exception" is selected.
+
 
−
<td>This item will resolve a defect where the data element "Additional Reporting" is being closed when a user selects a value for the data element "SAM Exception."<br>
+
<td>“Additional Reporting” is unavailable for selection when “SAM Exception” is selected.
 +
 
 +
<td>This item will resolve a defect where the data element “Additional Reporting” is being closed when a user selects a value for the data element “SAM Exception.”<br>
 
</td>
 
</td>
 +
 
<td align="center">No</td>
 
<td align="center">No</td>
 +
 
<tr>
 
<tr>
 +
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
RTC-57820
 
RTC-57820
 
</td>
 
</td>
 
<td>Invalid XML System error message firing on Web Services Create request when trying to provide <congressionalDistrictCode> information
 
<td>Invalid XML System error message firing on Web Services Create request when trying to provide <congressionalDistrictCode> information
−
<td>This item will resolve a defect where an invalid error message ('Please check the xml sent ()') is firing on web services create requests.  This error is being shown when a user tries to provide <congressionalDistrictCode> information in the web services response.
+
<td>This item will resolve a defect where an invalid error message (‘Please check the xml sent ()’) is firing on web services create requests.  This error is being shown when a user tries to provide <congressionalDistrictCode> information in the web services response.
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
 
<tr>
 
<tr>
 +
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
RTC-57713
 
RTC-57713
Line 144: Line 197:
 
<td>FAADC GUI Service errors for '<getNewAssistanceURL>' and '<getExistingAssistanceURL>' request types
 
<td>FAADC GUI Service errors for '<getNewAssistanceURL>' and '<getExistingAssistanceURL>' request types
 
<td>This item will resolve a defect with the FAADC GUI Web Services interface where the following errors are occurring:
 
<td>This item will resolve a defect with the FAADC GUI Web Services interface where the following errors are occurring:
 +
 
(1)  When sending the <getNewAssistanceURL> request, the returned URL is producing a blank white screen.
 
(1)  When sending the <getNewAssistanceURL> request, the returned URL is producing a blank white screen.
 
(2) When sending the <getExistingAssistanceURL> request, the returned URL shows a page with a screen that says "There was an error opening the document".
 
(2) When sending the <getExistingAssistanceURL> request, the returned URL shows a page with a screen that says "There was an error opening the document".
 +
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
 
<tr>
 
<tr>
 +
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
RTC-57531
 
RTC-57531
 
</td>
 
</td>
 
<td>Government User IDs incorrectly created without an assigned Agency ID, Unable to be corrected by user
 
<td>Government User IDs incorrectly created without an assigned Agency ID, Unable to be corrected by user
−
<td>This item will resolve a defect in the Government User ID creation where the 'Agency ID' is incorrectly allowed to be left blank upon creation.
+
<td>This item will resolve a defect in the Government User ID creation where the ‘Agency ID’ is incorrectly allowed to be left blank upon creation.
−
As 'Agency ID' is a required field on the Government User Registration page.
+
 
 +
As ‘Agency ID’ is a required field on the Government User Registration page.
 
But currently, a validation rule will be triggered to enforce that users are only able to create government FPDS accounts with an Agency ID.
 
But currently, a validation rule will be triggered to enforce that users are only able to create government FPDS accounts with an Agency ID.
 +
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
 
<tr>
 
<tr>
 +
 
<td style="width:95px" valign="center">
 
<td style="width:95px" valign="center">
 
RTC-58119
 
RTC-58119
 
</td>
 
</td>
−
<td>Suppress 'Date Signed' validation rule firing incorrectly on Other Transaction (OT) contracts as compared to Awards/IDV's
+
<td>Suppress ‘Date Signed’ validation rule firing incorrectly on Other Transaction (OT) contracts as compared to Awards/IDV's
 
</td>
 
</td>
−
<td>This item will suppress Other Transactions (OT) validation rule 'OT2B02' to align the validation rule behavior with the FPDS Awards/IDV's:
+
<td>This item will suppress Other Transactions (OT) validation rule ‘OT2B02’ to align the validation rule behavior with the FPDS Awards/IDV’s:
 +
 
 
Validation Rule Code: OT2B02
 
Validation Rule Code: OT2B02
−
Validation Rule Message:  'Period of Performance Start Date cannot be earlier than the Date Signed on the base document.'
+
Validation Rule Message:  ‘Period of Performance Start Date cannot be earlier than the Date Signed on the base document.’
−
This validation rule does not trigger for FPDS Awards and IDV's, and for consistency the validation rule will be suppressed for Other Transactions contract actions.  Currently, in situations where this is a valid scenario, OT users are unable to validate and finalize the OT contract action report.
+
 
 +
This validation rule does not trigger for FPDS Awards and IDV’s, and for consistency the validation rule will be suppressed for Other Transactions contract actions.  Currently, in situations where this is a valid scenario, OT users are unable to validate and finalize the OT contract action report.
 +
 
 
</td>
 
</td>
 
<td align="center">No</td>
 
<td align="center">No</td>
 
<tr>
 
<tr>
 +
 
</table>
 
</table>

Latest revision as of 18:29, 22 March 2021

Schedule

February 20, 2021 Fast Path

DescriptionStart Date End Date
Beta Implementation Feburary 17, 2021Feburary 17, 2021
Production Deployment Feburary 20, 2021Feburary 20, 2021


March 6, 2021 Fast Path

DescriptionStart Date End Date
Beta Implementation March 3, 2021March 3, 2021
Production Deployment March 6, 2021March 6, 2021

Document Changes

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

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators
The following items were originally scheduled to be deployed as part of FPDS V1.5 Service Pack (SP) 9. However due to the schedule re-assessment of FPDS SP 9, items that are not tied to UEI changes are being deployed ahead of the final SP9 release. The following items were deployed to production FPDS on Saturday, February 20, 2021:

IAEREQ-3348, IAEREQ- 3475, RTC 56706

Business Size is not being saved on a Novation Agreement. This item will resolve a defect for a subset of contract actions, when selecting “Reason for Modification” of 'Novation Agreement', and the user selects a different value for the data element 'Contracting Officer's Business Size Selection,' the new selected value is not retained when saving the modification when the DUNS is unchanged from the base Contract Action Report. This defect is only present on Awards and is not present on IDV contract action reports. No

RTC-57885

The correction functionality is not working on the Data Element Solicitation Date Solicitation Date is being removed from Awards when the referenced IDV is corrected No

RTC- 56501

Part 13 BPA is not retaining the correct DUNS when the Date Signed is changed on a modification. This item will resolve a defect where a 'Novation Agreement' modification DUNS number reverts back to the original/base document DUNS number after a new modification document is corrected to a Date Signed earlier than the Novation Agreement document. No

RTC-48831

“Subcontract Plan” retention on a Part 13 BPA Call. This item will resolve a defect where the Data Element “Subcontract Plan” value is not being retained on a BPA Call 13. No

RTC-57538

System error incorrectly firing on Contract Action Report (CAR) Invalid XML System error message firing on PIID W912DY10F0692, requiring code fix to resolve No
The following items were originally scheduled to be fixed with Service Pack (SP) 9. However due to the schedule re-assessment of FPDS SP9, items that are not tied to UEI changes are being deployed ahead of the final SP9 release. The following items shall be deployed to production FPDS on Saturday, March 6, 2021:

RTC-57378

IDV Modification records signed after a ‘Novation Agreement’ modification do not retain the correct “Subcontract Plan” value. This item will resolve a defect where the value for “Subcontract Plan” does not propagate to subsequent modifications that are signed after a ‘Novation Agreement’ modification. This occurs only when the ‘Novation Agreement’ modification is corrected, the DUNS number is unchanged, and the user updates the value for “Subcontract Plan.” A data management update will be performed to correct existing records affected by this defect. No

RTC-56838

Other Transaction Awards are omitting the “Congressional District Place of Performance” field when using the Print function. This item will resolve a defect where the selected value for data element “Congressional District Place of Performance” is not displaying when printing Other Transaction Awards. No

RTC-56499

“Simplified Procedures for Certain Commercial Items” is grayed out on a Delivery Order (DO) against a Basic Order Agreement (BOA). This item will resolve a defect where the required data element “Simplified Procedures for Certain Commercial Items” is closed on a DO against BOA.
 No

RTC-46829

“Additional Reporting” is unavailable for selection when “SAM Exception” is selected. This item will resolve a defect where the data element “Additional Reporting” is being closed when a user selects a value for the data element “SAM Exception.”
 No

RTC-57820

Invalid XML System error message firing on Web Services Create request when trying to provide <congressionalDistrictCode> information This item will resolve a defect where an invalid error message (‘Please check the xml sent ()’) is firing on web services create requests. This error is being shown when a user tries to provide <congressionalDistrictCode> information in the web services response. No

RTC-57713

FAADC GUI Service errors for '<getNewAssistanceURL>' and '<getExistingAssistanceURL>' request types This item will resolve a defect with the FAADC GUI Web Services interface where the following errors are occurring:

(1) When sending the <getNewAssistanceURL> request, the returned URL is producing a blank white screen. (2) When sending the <getExistingAssistanceURL> request, the returned URL shows a page with a screen that says "There was an error opening the document".

No

RTC-57531

Government User IDs incorrectly created without an assigned Agency ID, Unable to be corrected by user This item will resolve a defect in the Government User ID creation where the ‘Agency ID’ is incorrectly allowed to be left blank upon creation.

As ‘Agency ID’ is a required field on the Government User Registration page. But currently, a validation rule will be triggered to enforce that users are only able to create government FPDS accounts with an Agency ID.

No

RTC-58119

Suppress ‘Date Signed’ validation rule firing incorrectly on Other Transaction (OT) contracts as compared to Awards/IDV's This item will suppress Other Transactions (OT) validation rule ‘OT2B02’ to align the validation rule behavior with the FPDS Awards/IDV’s:

Validation Rule Code: OT2B02 Validation Rule Message: ‘Period of Performance Start Date cannot be earlier than the Date Signed on the base document.’

This validation rule does not trigger for FPDS Awards and IDV’s, and for consistency the validation rule will be suppressed for Other Transactions contract actions. Currently, in situations where this is a valid scenario, OT users are unable to validate and finalize the OT contract action report.

No
Retrieved from "https://fpds.gov/wiki/index.php?title=V1.5_SP_9.0_Fast_Path&oldid=4796"