V1.5 SP 27.0

From FPDS-NG

Revision as of 00:23, 2 July 2025 by WikiSysop (talk | contribs)
(diff) ←Older revision | view current revision (diff) | Newer revision→ (diff)

Schedule

DescriptionStart Date End Date
Beta DeploymentJuly 11, 2025July 11, 2025
Production Deployment July 19, 2025July 19, 2025

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data DictionaryNo
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesYes
ezSearchNo
Atom FeedsNo
Online HelpNo
User ManualNo

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

SPR #Enhancement/ProblemSolutionImpact 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 corrected 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/ProblemSolutionImpact 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 corrected 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. The updated 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 message:
  • The combination of Organization "xxxxx" and Grants Office "XXXXXX" is not valid.
  1. The new Office code is designated as both a Grants Office and a Contracting Office, but the Contracting Office entry has been end-dated.
  2. 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 corrected 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