Difference between revisions of "V1.4 SP14.0"
From FPDS-NG
| (6 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
<tr><th width=30% align="center"><b>Description</b></th><th width=34% align="center"><b>Start Date</b></th> | <tr><th width=30% align="center"><b>Description</b></th><th width=34% align="center"><b>Start Date</b></th> | ||
<th width=34% align="center"><b>End Date</b></th></tr> | <th width=34% align="center"><b>End Date</b></th></tr> | ||
| − | <tr><td nowrap>BETA Installation </td><td nowrap> | + | <tr><td nowrap>BETA Installation </td><td nowrap>Monday Mar 19, 2012</td><td nowrap>Monday Mar 19, 2012</td></tr> |
<tr><td nowrap>Functional Qualification Testing</td><td nowrap>Tuesday Mar 20, 2012</td><td nowrap>Thursday Mar 22, 2012</td></tr> | <tr><td nowrap>Functional Qualification Testing</td><td nowrap>Tuesday Mar 20, 2012</td><td nowrap>Thursday Mar 22, 2012</td></tr> | ||
<tr><td nowrap>Installation in Production</td><td nowrap>Friday Mar 30, 2012</td><td nowrap>Friday Mar 30, 2012</td></tr> | <tr><td nowrap>Installation in Production</td><td nowrap>Friday Mar 30, 2012</td><td nowrap>Friday Mar 30, 2012</td></tr> | ||
| Line 40: | Line 40: | ||
<td style="width:95px" valign="center">Enhancement</td> | <td style="width:95px" valign="center">Enhancement</td> | ||
<td>eZSearch and ICD modules to export up to 30,000 records in CSV format</td> | <td>eZSearch and ICD modules to export up to 30,000 records in CSV format</td> | ||
| − | <td>CSV limit will be extended from 5000 records to 30,000 records. PDF export limit will continue to be 5000 records. | + | <td> |
| + | '''EZSearch''' | ||
| + | |||
| + | CSV limit will be extended from 5000 records to 30,000 records. PDF export limit will continue to be 5000 records. | ||
The following fields will be added to the CSV export | The following fields will be added to the CSV export | ||
*PIID Agency ID | *PIID Agency ID | ||
| Line 46: | Line 49: | ||
*Transaction Number | *Transaction Number | ||
*IDV PIID Agency ID | *IDV PIID Agency ID | ||
| + | *Contracting Agency ID | ||
| + | '''ICD''' | ||
| + | *Modification Number | ||
| + | *Max Order limit | ||
| + | |||
</td> | </td> | ||
<td align="center">No</td> | <td align="center">No</td> | ||
| Line 53: | Line 61: | ||
<td>FPDS-NG Validation to check the validity of CCR Vendors on Contracts</td> | <td>FPDS-NG Validation to check the validity of CCR Vendors on Contracts</td> | ||
<td> | <td> | ||
| − | FPDS-NG will start validating the Vendor CCR expiration date against the | + | FPDS-NG will start validating the Vendor CCR expiration date against the date signed and/or the created/modified/approved (action/system) date on new Contracts. |
| − | If the Vendor’s renewal date is earlier than the date signed and the | + | If the Vendor’s renewal date is earlier than the date signed and the date when the contract is being created/modified/approved (action date), the following Validation rule will be displayed |
| − | '''''This contract is awarded to the vendor that is not active in CCR. Please contact the vendor to renew their registration in CCR.''''' | + | '''''This contract is awarded to the vendor that is not active in CCR. Please contact the vendor to renew their registration in CCR before submitting this action.''''' |
| − | |||
| + | This Validation is effective 03/30/2011 and will fire on V 1.4 stand-alone base documents,''''' Novation, Vendor DUNS Change, and Rerepresentation type Modifications''''' | ||
The operations and Document types that have an impact are ‘Create-isComplete’, ‘Update-isComplete’, ‘Approve’ and ‘Correct’, only if the vendor is changed. | The operations and Document types that have an impact are ‘Create-isComplete’, ‘Update-isComplete’, ‘Approve’ and ‘Correct’, only if the vendor is changed. | ||
*PO | *PO | ||
| Line 76: | Line 84: | ||
*OT IDV | *OT IDV | ||
| − | </td> | + | '''Note: |
| + | <ol><li> | ||
| + | This applies only from the software deployment date | ||
| + | </li><li>This does not apply on non-vendor and Vendor Address change type modifications | ||
| + | </li><li>This does not apply for Delivery Orders, BPA Calls, Part 8 BPAs | ||
| + | </li></ol>'''</td> | ||
<td align="center">No</td> | <td align="center">No</td> | ||
</tr> | </tr> | ||
| Line 83: | Line 96: | ||
<td style="width:95px" valign="center">FPDSPMOS-106</td> | <td style="width:95px" valign="center">FPDSPMOS-106</td> | ||
<td>Add a new metric “Number of Records” to Adhoc reports</td> | <td>Add a new metric “Number of Records” to Adhoc reports</td> | ||
| − | <td>Currently a metric “Number of Actions” is available for users. A new metric “Number of Records” will be made available for the users to retrieve the count of records. | + | <td>Currently a metric “Number of Actions” is available for users. A new metric “Number of Records” will be made available for the users to retrieve the count of records. |
| + | |||
| + | A new filter “Last Modified Date” will be available as a prompted filter. | ||
| + | |||
| + | When running Adhoc reports, user will have to enter Date Signed or Last Modified Date. | ||
| − | + | These fields will primarily be helpful for Atom feed users who might want to consolidate their pull numbers with the Adhoc report | |
</td> | </td> | ||
<td align="center">No</td> | <td align="center">No</td> | ||
| Line 101: | Line 118: | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
| − | <td | + | <td>FPDSPMOS-81</td> |
| − | <td> | + | <td>End-date dummy zip codes</td> |
| + | <td> | ||
| + | *FPDS-NG has ZIP Codes that have the “ZIP” and “ZIP + 4” information, but are not associated with any Congressional District, Country, or State. These “dummy” ZIP Codes are not valid ZIP Codes; however, they are active in FPDS-NG. | ||
| + | *FPDS-NG shall “End Date” the dummy ZIP Codes with the software implementation date. Users shall not be able to approve documents with a dummy ZIP Code if the “Date Signed” of the document is after the “End Date” of the ZIP Code. | ||
</td> | </td> | ||
| − | |||
<td align="center">No</td> | <td align="center">No</td> | ||
| + | |||
</tr> | </tr> | ||
</TABLE> | </TABLE> | ||
Latest revision as of 21:57, 21 March 2012
Schedule
| Description | Start Date | End Date |
|---|---|---|
| BETA Installation | Monday Mar 19, 2012 | Monday Mar 19, 2012 |
| Functional Qualification Testing | Tuesday Mar 20, 2012 | Thursday Mar 22, 2012 |
| Installation in Production | Friday Mar 30, 2012 | Friday Mar 30, 2012 |
Document Changes
| Documentation | Changes Required |
|---|---|
| XML Specifications | Yes |
| Web Services | Yes |
| Data Dictionary | Yes |
| NASA Specific Data Dictionary | No |
| Use Case Summary | No |
| Validation Rules | Yes |
| Online Help | No |
| Computer-Based Training | No |
| User Manual | No |
SPR Listing
| SPR # | Problem | Solution | Impact to Users and Integrators |
|---|---|---|---|
| Enhancement | New Version will be released for Atom feeds | Version 1.4.3 will be released for Atom feed users which will incorporate the following data elements
|
No |
| Enhancement | eZSearch and ICD modules to export up to 30,000 records in CSV format |
EZSearch CSV limit will be extended from 5000 records to 30,000 records. PDF export limit will continue to be 5000 records. The following fields will be added to the CSV export
ICD
|
No |
| FPDSIRB-129 | FPDS-NG Validation to check the validity of CCR Vendors on Contracts |
FPDS-NG will start validating the Vendor CCR expiration date against the date signed and/or the created/modified/approved (action/system) date on new Contracts. If the Vendor’s renewal date is earlier than the date signed and the date when the contract is being created/modified/approved (action date), the following Validation rule will be displayed This contract is awarded to the vendor that is not active in CCR. Please contact the vendor to renew their registration in CCR before submitting this action. This Validation is effective 03/30/2011 and will fire on V 1.4 stand-alone base documents, Novation, Vendor DUNS Change, and Rerepresentation type Modifications The operations and Document types that have an impact are ‘Create-isComplete’, ‘Update-isComplete’, ‘Approve’ and ‘Correct’, only if the vendor is changed.
Note:
|
No |
| FPDSPMOS-106 | Add a new metric “Number of Records” to Adhoc reports | Currently a metric “Number of Actions” is available for users. A new metric “Number of Records” will be made available for the users to retrieve the count of records.
A new filter “Last Modified Date” will be available as a prompted filter. When running Adhoc reports, user will have to enter Date Signed or Last Modified Date. These fields will primarily be helpful for Atom feed users who might want to consolidate their pull numbers with the Adhoc report |
No |
| FPDSHD-71054 FPDSHD-71289 | Contracting Office Name is not auto-populated on the Contract screen when it is end dated as the Funding Office
Funding Office Search on the Small Business Goaling Report is retrieving Contracting Offices as well as the Funding Offices. |
Contracting Office Name will not be null if it is still valid as a Contracting office
The Office lookup on the Small Business Goaling Report Search screen will include Funding only offices and Funding/Contracting offices |
No |
| FPDSPMOS-81 | End-date dummy zip codes |
|
No |