Difference between revisions of "V1.5 SP 27.0"

Revision as of 22:41, 1 July 2025

Schedule

Description	Start Date	End Date
Beta Deployment	July 11, 2025	July 11, 2025
Production Deployment	July 19, 2025	July 19, 2025

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	Yes
ezSearch	No
Atom Feeds	No
Online Help	No
User Manual	No

Federal Procurement Data System (FPDS) Version 1.5 Service Pack Requirements (SPR) Listing

SPR #	Enhancement/Problem	Solution	Impact on Users and Integrators
IAEMOD-40134	Other Transaction Awards/IDVs in "error" status are not included in ‘Error Document Search Results’	The FPDS application shall be updated to ensure that the ‘Error Document Search Results’ include all Awards or Indefinite Delivery Vehicles which are in “error” status, including Other Transaction Awards or Other Transaction Indefinite Delivery Vehicles in "error" status. Currently, the counts displayed for Error Awards and Error IDVs include Other Transaction Awards and Other Transaction Indefinite Delivery Vehicles in “error” status, but when the user clicks the associated link, the count on the ‘Error Document Search Results’ screen excludes Other Transaction Awards or Other Transaction Indefinite Delivery Vehicles in “error” status, and those records are not displayed.	Yes

Federal Assistance Award Data Collection (FAADC) Version 1.2 Service Pack Requirements (SPR) Listing

SPR #

Enhancement/Problem

Solution

Impact on Users and Integrators

IAEMOD-43030

FAADC “Action Date” data element accepts years with more than 4 digits

Currently, the FAADC “Action Date” data element accepts a date where the year portion has more than four (4) digits through the Web Portal or Business Services. When the user attempts to save the award, an unclear message displays:

The system cannot save the changes. Please check the input xml sent.

The FAADC application shall be updated to add another constraint to the logic for Validation Rule FAADC:2B1 so that an informative message displays when the user attempts to save a new award where the year portion of the “Action Date” data element exceeds four (4) digits, and the Screen Name of the “Action Date” data element turns red. The message shall read:

FAADC:2B1: “Action Date” must be a valid date.

Yes

IAEMOD-44317

DoD User update does not derive Parent Organization when office is changed

Currently, the Contract Writing Systems receive an error when they submit a User update request on a DoD user account to change the Office code present to certain Grants Office codes. The error occurs in two different scenarios (below), and the User update request fails, displaying the same message:

The combination of Organization "xxxxx" and Grants Office "XXXXXX" is not valid.

The new Office code is designated as both a Grants Office and a Contracting Office, but the the Contracting Office entry has been end-dated.
The new Office code is designated as both a Grants Office and a Contracting Office, but the Grants Office Parent Organization and the Contracting Office Parent Organization differ, and the system cannot determine which Parent Organization to return.

The FAADC application shall be updated, so the system derives the correct Parent Organization when a User update request is submitted to change the Office code on a DoD User account to a Grants Office with either of these scenarios, or to identify the attempted office change as invalid.

Yes

@@ Line 16: / Line 16: @@
 <tr><td nowrap>NASA Specific Data Dictionary</td><td align="center">No</td></tr>
 <tr><td nowrap>Use Case Summary</td><td align="center">No</td></tr>
-<tr><td nowrap>Validation Rules</td><td align="center">No</td></tr>
+<tr><td nowrap>Validation Rules</td><td align="center">Yes</td></tr>
 <tr><td nowrap>ezSearch</td><td align="center">No</td></tr>
 <tr><td nowrap>Atom Feeds</td><td align="center">No</td></tr>