Difference between revisions of "V1.5 SP 5.0 Fast Path"
From FPDS-NG
| Line 67: | Line 67: | ||
The message was changed to now fire the following: <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.<br> | : • Assistance with Agency Code: "XXXX", FAIN: "XXXXXXXXX", Amendment Number: "XXXX", or URI: "" does not exist.<br> | ||
| + | |||
| + | <td align="center">No</td> | ||
| + | |||
| + | <tr> | ||
| + | <td style="width:95px" valign="center"> | ||
| + | RTC-52860 | ||
| + | </td> | ||
| + | |||
| + | <td>FAADC Atom Feeds are missing the below vendor information.<br> | ||
| + | : • Recipient State Name | ||
| + | : • Recipient Country Name | ||
| + | : • Recipient City Name from zip code | ||
| + | |||
| + | <td>The additional data requested by DoD has been added.<br> | ||
| + | : <nowiki><ns1:city>Example City</ns1:city></nowiki> | ||
| + | : <nowiki><ns1:state>EX</ns1:state></nowiki> | ||
| + | : <nowiki><ns1:ZIPCode>11111</ns1:ZIPCode></nowiki> | ||
| + | : <nowiki><ns1:countryCode>USA</ns1:countryCode></nowiki> | ||
<td align="center">No</td> | <td align="center">No</td> | ||
<tr> | <tr> | ||
Revision as of 20:48, 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:
| No |
|
RTC-52860 |
FAADC Atom Feeds are missing the below vendor information.
| The additional data requested by DoD has been added.
| No |