Difference between revisions of "V1.4 SP3.0"

From FPDS-NG
Line 48: Line 48:
 
The above validation rule is applicable for the following services:
 
The above validation rule is applicable for the following services:
 
<TABLE>
 
<TABLE>
−
Business Services
+
<tr><td>Business Services</td>
−
  isComplete, isExistingAwardComplete, isExistingIDVComplete,
+
  <td>isComplete, isExistingAwardComplete, isExistingIDVComplete,
−
 
 
 
approve and  
 
approve and  
−
 
+
correct</td>
−
correct’
+
<td> Version 1.3 & 1.4</td>
−
Version 1.3 & 1.4
+
</tr>
−
 
 
Gui Services  
 
Gui Services  
 
  Correct and validate
 
  Correct and validate

Revision as of 20:48, 2 June 2010

Schedule

DescriptionStart Date End Date
BETA Installation Monday May 24, 2010Monday May 24, 2010
Functional Qualification TestingTuesday May 25, 2010Thursday May 27, 2010
Installation in ProductionFriday June 04, 2010Friday June 04, 2010

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data Dictionary No
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesNo
Online HelpNo
Computer-Based TrainingNo
Report ManualNo

SPR Listing

SPR #ProblemSolutionImpact to Users and Integrators
FPDSHD-71390, FPDSHD-69612, FPDSHD-69190, FPDSHD-72585, FPDSHD-68838 User reported an issue with the Novation Agreement functionality. A new Novation on the IDV updated all the Delivery Order Modifications against that IDV regardless of the date signed.

The IDV is NAS598145 and the Novation mod is 26 with a date signed of 03/23/2010.

  • Upon ‘Approve’ or ‘Correct’ of an IDV Vendor Modification, FPDS-NG shall propagate the respective vendor information and the IDV Modification Number to its successive Modifications and Referencing Orders based on the “Date Signed” and “Reason for Modification” on the documents.
  • Upon ‘Correct’ of a Delivery Order, FPDS-NG Shall fetch the respective vendor information from the latest Vendor Modification or the base of the referenced IDV based on the “Date Signed”.
  • Upon ‘Approve’ or ‘Correct’ of an Award or IDV Vendor Modification, FPDS-NG shall propagate the respective vendor information and “Contracting Officers Business Size Selection” to its successive Modifications based on the “Date Signed” and “Reason for Modification” on the documents.
 No
FPDSNG-3624, FPDSNG-3625 FAST book data has to be loaded into FPDS-NG and the TAS codes will be validated against the FAST book.
  • FPDS-NG shall load FAST book TAS codes into FPDS-NG.
  • FPDS-NG shall validate the TAS codes against the FAST book and display an error message "The “Treasury Account Symbol” code is not valid. Please enter a valid “Treasury Account Symbol” code or contact your Agency Administrator.” if the code submitted does not exist in FAST book.

The above validation rule is applicable for the following services:

Gui Services Correct and validate Version 1.3 & 1.4 Web Portal Correct ,validate and approve Version 1.3 & 1.4
Business Services isComplete, isExistingAwardComplete, isExistingIDVComplete,

approve and

correct		 Version 1.3 & 1.4
Yes
Retrieved from "https://fpds.gov/wiki/index.php?title=V1.4_SP3.0&oldid=3401"