V1.4 SP13.2

From FPDS-NG

Schedule

DescriptionStart Date End Date
BETA Installation Thursday Feb 09, 2012Friday Feb 10, 2012
Functional Qualification TestingMonday Feb 13, 2012Tuesday Feb 14, 2012
Installation in ProductionFriday Feb 24, 2012Friday Feb 24, 2012

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
User ManualNo

SPR Listing

SPR #ProblemSolutionImpact to Users and Integrators
FPDSHD-82054-97442 “CREATED_VIA” is not populated for actions that are errored out. When these actions move into draft/final status, they do not have “CREATED_VIA” stamped on them. Data Fix: For the existing documents that have a null value for “CREATED_VIA”, but have a value for “UPDATED_VIA”, data fix shall be performed to consider the ‘CREATE:<value>’ part of the “UPDATED_VIA” to update the value of “CREATED_VIA”.

Examples:

1.CREATE:BS,UPDATE:GS,UPDATE:BS,UPDATE:GS,UPDATE:BS,UPDATE:BS

2.CREATE:GS,UPDATE:GS,UPDATE:GS,UPDATE:GS,UPDATE:GS,UPDATE:BS,UPDATE:BS

3.CREATE:WP

Software Fix: For all the new Awards that are first errored out and then are updated into Draft Status, or are finalized, “CREATED_VIA” shall be displayed when “Prepared Date” or “Date Signed” is on or later than the Production deployment date for this Service Pack.

No
FPDSHD-85557 In the “Status of Actions” report, documents with a null Contracting Office Code are not being displayed, and actions/dollars are being double counted for the documents that have Contracting Agencies having two different names between date ranges. In the “Status of Actions” report, documents with a null Contracting Office Code shall be displayed, and actions/dollars shall not be double counted for the documents that have Contracting Agencies having two different names between date ranges. No
FPDSHD-87276 FPDS-NG documents that are awarded to foreign vendors are displaying a value for the “Vendor Congressional District” in the Standard and Adhoc reporting, and Atom Feeds. Since “Congressional District” does not apply to foreign vendors, Standard and Adhoc reporting, and Atom Feeds shall not display a value for “Vendor Congressional District”. No
FPDSHD-91612 “Change PIID” IDV modifications are not going through with the error, “Record does not exist” during “Approve”. “Change PIID” IDV modifications shall not display the error, “Record does not exist” during “Approve”. No
FPDSHD-81913 Certain documents exist in both Error and Final Status, and hence they are being displayed in the “Status of Actions” Report in the “ERROR” column.

Additionally, certain documents exist in both Error and Draft Status, and hence they are being displayed in the “Status of Actions” Report both in the “DRAFT” and “ERROR” columns.

This happens when the documents are initially created in the Error Status and then they are changed into the Draft Status or are finalized. The Error Tables are not automatically updated to remove these documents.

NOT FINALIZED

Data Fix: Delete the documents from the ERROR_AWARD or ERROR_IDV tables when they are found in the AWARD or IDV tables in the Draft or Final Status.

Software Fix: Since the issue with the documents existing in both Error and Draft/Error and Final Status is not replicable, there is no software fix for this issue.

No