Difference between revisions of "V1.5 SP 5.0 Fast Path"
From FPDS-NG
(Created page with "__NOEDITSECTION__ ==Schedule== <TABLE id="box-table-a" border=2> <tr><th width=30% align="center"><b>Description</b></th><th width=34% align="center"><b>Start Date</b></th> <...") |
|||
| Line 52: | Line 52: | ||
</td> | </td> | ||
| + | |||
| + | <td align="center">No</td> | ||
| + | |||
| + | <tr> | ||
| + | <td style="width:95px" valign="center"> | ||
| + | RTC-52860 | ||
| + | </td> | ||
| + | |||
| + | <td>The message that is currently firing when a record does not exist in FPDS is not clear. This is for Business Services only. This is for FAADC only. | ||
| + | |||
| + | <td>The message that is currently firing when a record does not exist in the system is as follows: <br> | ||
| + | : • When performing a DELETE, the Assistance record must have a status of "FINAL"<br> | ||
| + | <br> | ||
| + | The message was changed to now fire the following: <br> | ||
| + | : • Assistance with Agency Code: "XXXX", FAIN: "XXXXXXXXX", Amendment Number: "XXXX", or URI: "" does not exist. | ||
<td align="center">No</td> | <td align="center">No</td> | ||
<tr> | <tr> | ||
Revision as of 19:04, 10 January 2020
Schedule
| Description | Start Date | End Date |
|---|---|---|
| BETA Installation | January 06, 2020 | January 06, 2020 |
| Government Acceptance Testing | January 07, 2020 | January 09, 2020 |
| Installation in Production | January 17, 2020 | January 17, 2020 |
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 |
| ezSearch | No |
| Atom Feeds | No |
| Online Help | No |
| User Manual | No |
SPR Listing
| SPR # | Enhancement/Problem | Solution | Impact to Users and Integrators |
|---|---|---|---|
|
IAESAM-724, RTC-49443 |
A Vendor Change (VC) Mod is any modification that has a Reason for Modification as either Novation Agreement, Vendor DUNS or Name Change, Vendor Address Change, Rerepresentation or Rerepresentation of Non-Novated Merger.
All other types are considered a Non-Vendor Change (Non-VC) Mod. When performing a correction to a finalized Non-VC mod and changing it to a VC mod, the updated Vendor data is not being retained on the VC mod after saving the correction. | The system shall have the necessary code changes completed to ensure that any updated Vendor data is retained on a modification when a final Non-VC mod is corrected to a VC mod (and vice versa). Also, the updated Vendor data will propagate to the proper subsequent modifications and any awards referencing that VC mod. | No |
|
RTC-53185 |
Effective Date is propagating from the Base record on NASA Specific Award Modifications after the users performs a Correct and Save action.
Date Signed of Modification must be >= 10/25/2019. | This is incorrect behavior. Effective Date will be open and required on all NASA Specific Award documents. | No |
|
RTC-52860 |
The message that is currently firing when a record does not exist in FPDS is not clear. This is for Business Services only. This is for FAADC only. | The message that is currently firing when a record does not exist in the system is as follows: : • When performing a DELETE, the Assistance record must have a status of "FINAL" | No |