Release Notes
Federal Procurement Data System – Next Generation
Service Pack 37.0
For Versions: 1.0, 1.1, and 1.2
BETA Installation Date: May 15, 2006
Production Installation Date: May 26, 2006
FINAL
Prepared by:
Global Computer Enterprises, Inc.
10780 Parkridge Boulevard, Suite 300
Reston, VA 20191
May 26, 2006
FPDS-NG Version 1.2, Service Pack 37.0 Release Notes
Table of Contents
Section Page
1 Introduction 1
1.1 Overview 1
1.2 Documentation 1
1.3 Impact to Users 1
1.4 Impact to Integrators 1
1.5 FPDS-NG Updates and Notices 1
1.6 Support Line 1
2 Bug Fixes Completed 2
3 Updates Completed 8
4 New Reports 8
5 Report enhancements 9
i
FPDS-NG Version 1.2, Service Pack 37.0 Release Notes
1 Introduction
1.1 Overview
This document describes the enhancements and changes made to the FPDS-NG system in the software release for Service Pack 37.0. The Software Problem Report (SPR) tracking number is included for each change.
1.2 Documentation
Changes to documentation required by this version included:
· XML Specifications – The XML Specifications has not been modified for this service pack.
· Web Services – Web Services has not been modified for this service pack.
· Data Dictionary – The Data Dictionary has not been modified for this service pack.
· NASA Specific Data Dictionary – The NASA Data Dictionary has not been modified for this service pack.
· Use Case Summary – The Use Case Summary has not been modified for this service pack.
· Validation Rules – The Validation Rules has not been modified for this service pack.
· Batch Format – The Batch Format document has not been modified for this service pack.
· Online Help – Online Help has been modified for this service pack.
· Computer-Based Training – The Computer-Based Training modules has not been modified for this service pack.
· Report Manual – The Reports Manual has not been modified for this service pack.
For more information on 1.0, 1.1, or 1.2 version changes, please visit the project website located at http://www.fpdsng.com/downloads.html.
1.3 Impact to Users
The impact to the users is addressed for each change made to the system.
1.4 Impact to Integrators
The impact to the integrators is addressed for each change made to the system.
1.5 FPDS-NG Updates and Notices
All updates and notices are posted to the FPDS-NG website at http://www.fpdsng.com/downloads.html. The most recent updates and anticipated changes are posted at http://www.fpds-ng.com/status.html.
1.6 Support Line
If you have questions about the FPDS-NG system, please call the FPDS-NG Support Line at (703) 773-4810 or (866) 490-3737. You may fax us at (703) 773-1218 or visit the FPDS-NG website at https://www.fpds.gov.
2 Bug Fixes Completed
SPR Number / DescriptionFPDSHD-14836 / Problem: When an award document with a CCR exception is opened to correct the vendor socio economic information the business flags do not reflect the changes made after it is saved. The socio economic information reverts back to what was originally entered when the document was first created, saved, and finalized.
Solution: When a document with a Vendor CCR Exception is opened with the correct function and changes for the Vendor section are made the changes be retained upon saving the document.
Impact Analysis for Users and Integrators
Batch / No Impact
GUI Interface / When a document with a Vendor CCR Exception is opened with the correct function and changes for the Vendor section are made the changes be retained upon saving the document.
Business Services / When a document with a Vendor CCR Exception is opened with the correct function and changes for the Vendor section are made the changes be retained upon saving the document.
Reports and Report Services / No Impact
Data Dissemination / No Impact
SPR Number / Description
FPDSHD-17195 / Problem: When the user sends a document through a contract writing system for and IDV and an error generates, the response XML is sent to the contract writing system with an error message. The list that is being sent contains a duplicate list of errors elements within list of errors elements.
Solution: The response XML that contains the list of errors that is being returned will be fixed to eliminate the duplicate list of errors elements.
Impact Analysis for Users and Integrators
Batch / No Impact
GUI Interface / No Impact
Business Services / The response XML that contains the list of errors that is being returned will be fixed to eliminate the duplicate list of errors elements.
Reports and Report Services / No Impact
Data Dissemination / No Impact
SPR Number / Description
FPDSNG – 2557
FPDSNG - 1526
FPDSHD – 18926 / Problem: When validating DUNS number for Vendors that are not required to register in CCR through Dun & Bradstreet an error occurs in FPDS-NG. This error is due to the country codes in D & B not matching the country codes in FPDS-NG. The problem exists because D&B uses ISO country codes for their representation and our system uses FIPS 55 codes. This causes the country name to be populated wrong or as “undefined” for certain foreign vendors like Germany, Japan etc.
Solution: When the user selects the CCR Exception and enters a DUNS Number for a foreign vendor the 2-character ISO code returned by D & B must map to the 2 character FIPS 55 code used in FPDSNG.
The corresponding country name derived for the above country code (FIPS 55 code in FPDS-NG) will then populate on the screen. This functionality only works upon approval when the JavaScript is turned on for the browser.
I addition, some Awards/IDVs reported with a CCR Exception for foreign vendors and approved in FPDS-NG after March 31st have incorrect country names for the country codes on the Award/IDV. These documents need correcting with a data fix script to derive the correct country name for that country code by verifying the data against the Mapping from a 2-character ISO code and a 2-character FIPS 55 country code.
Impact Analysis for Users and Integrators
Batch / No Impact
GUI Interface / When the user selects the CCR Exception and enters a DUNS Number for a foreign vendor the 2-character ISO code returned by D & B must map to the 2 character FIPS 55 code used in FPDSNG.
Business Services / No Impact
Reports and Report Services / No Impact
Data Dissemination / No Impact
SPR Number / Description
FPDSHD - 11767 / Problem: When searching for a document using the Advanced Search screen the Referenced IDV number does not display on the Contract Search Results Screen.
Solution: The Advanced Search screen is not calling the referenced IDV Number. This function will be updated to display the Referenced IDV when applicable for document searches.
Impact Analysis for Users and Integrators
Batch / No Impact
GUI Interface / The Advanced Search function will be updated to display the Referenced IDV when applicable for document searches.
Business Services / No Impact
Reports and Report Services / No Impact
Data Dissemination / No Impact
SPR Number / Description
FPDSHD - 1788 / Problem: Users from any Department/Agency are able to create, modify, and correct Federal Supply Schedules (FSS) in FPDS-NG. All Users are allowed to view documents in FPDS-NG including FSS documents. However, the department that originally created the document in FPDS-NG is supposed to be the only ones allowed to do modifications and corrections.
Solution: Currently, FPDS-NG privileges are designed to allow creation of documents at the Award/IDV level. If the user has permission to create an IDV then they are able to create all kinds of IDVs including FSS. This is same with modify and correct privileges too.
To correct this the system must not allow other agencies to Create, Update, Validate, Approve, Correct and Modify IDV type ‘FSS’ through any services (WP,BS,GS,FB) except GSA/FSS & VA.
If the document is created, Updated, Validated, Approved, Corrected or Modified by other agencies through Business services (except GSA/FSS & VA), FPDS-NG must not save IDV type ‘FSS’ document and must fire the following valid error message.
Error Message: IDV type ‘FSS’ can only be created by ‘GSA/FSS’ or ‘VA’
The web portal access for the IDV type ‘FSS’ must be grayed for all agencies except GSA/FSS and VA.
Impact Analysis for Users and Integrators
Batch / No Impact
GUI Interface / Other agency users (except GSA/FSS & VA) can not create/modify/correct FSS documents
Business Services / Other agency users (except GSA/FSS & VA) can not create/modify/correct FSS documents
Reports and Report Services / No Impact
Data Dissemination / No Impact
SPR Number / Description
FPDSHD - 19005 / Problem: FPDS-NG corrects invalid Agency ID tags by using the following
When the agency ID tag is:
· Blank and the PIID tag contains dashes, the system puts the correct agency code and removes the dashes in the PIID.
· Blank and the PIID tag does not contain dashes, FPDS-NG inputs the correct agency code.
· Invalid and the PIID tag does not contain dashes, the system corrects the agency code.
However, when and agency ID tag is invalid and the PIID tag contains dashes, FPDS-NG is supposed to correct the agency code and remove the dashes from the PIID. Instead, it is returning a message that the document does not exist.
Solution: When an incorrect agency ID and hyphens in the PIID are provided in the request XML for the ‘referenced IDV ID’ tag, FPDS-NG will correct the agency code and strip the hyphens off.
This functionality should apply to all the versions (1.0/1.1/1.2), all the document types and the applicable APIs.
Impact Analysis for Users and Integrators
Batch / When an incorrect agency ID and hyphens in the PIID are provided in the request XML for the ‘referenced IDV ID’ tag, FPDS-NG will correct the agency code and strip the hyphens off.
GUI Interface / No Impact
Business Services / When an incorrect agency ID and hyphens in the PIID are provided in the request XML for the ‘referenced IDV ID’ tag, FPDS-NG will correct the agency code and strip the hyphens off.
Reports and Report Services / No Impact
Data Dissemination / No Impact
SPR Number / Description
FPDSNG – 2508
FPDSNG – 2507
FPDSNG - 2506 / Problem: The FPDS-NG report views have some columns that do not match the filters created in Adhoc. FPDS-NG allows the user to generate a report using Award and IDVs on the same query. A few of the columns collect the data differently.
For example, in Awards the Contracting Officer’s Business Size Determination is decoded as ‘SMALL’ for ‘S’ and ‘OTHER’ for ‘O’. In the IDVs the contracting Officer’s Business Size Determination has values of ‘S’ and ‘O’ (these values are not decoded). ‘
Solution: Informatica Adhoc reports will retrieve all document types of Awards and IDVs based on query and filters. The Award and IDV view columns will remain consistent with column descriptions and codes (if applicable).
For example, The reports must retrieve both Awards and IDVs if Contracting Officer’s Business Size Determination is ‘SMALL’ or ‘OTHER’.
The following new fields are added to DoD BI Views:
IDV:
a. Extent_competed_description
b. Evaluated_pref_description
c. Reason_not_comp_description
d. Research_description
e. Solicitation_proc_description
f. Fair_opportunity_description
g. Type_of_set_aside_description
h. Version
Award:
a. Extent_competed_description
b. Evaluated_pref_description
c. Reason_not_comp_description
d. Research_description
e. Solicitation_proc_description
f. Fair_opportunity_description
g. Type_of_set_aside_description
h. Version
Impact Analysis for Users and Integrators
Batch / No Impact
GUI Interface / No Impact
Business Services / No Impact
Reports and Report Services / FPDS-NG will retrieve IDV records for Contracting Officer’s Business Size Determination value is ‘SMALL’ or ‘OTHER’.
Data Dissemination / No Impact
SPR Number / Description
FPDSNG – 2493 / Problem: The data dictionary is published for government and public user to access. Public Users have a different Home screen than the Government Users when accessing FPDS-NG. The Public access the data dictionary through a link provided on the main screen of FPDS-NG. The Data dictionary link for the public is accessing an older version from October 22, 2004.
Solution: The public user link will be updated to reference the Data Dictionary Version 1.2 April 28, 2006. When the Public Users access the data dictionary from the FPDS-NG web site, the latest version of the Data Dictionary will display.
Impact Analysis for Users and Integrators
Batch / No Impact
GUI Interface / The public user link will be updated to reference the Data Dictionary Version 1.2 April 28, 2006.
Business Services / No Impact
Reports and Report Services / No Impact
Data Dissemination / No Impact
SPR Number / Description
FPDSNG – 2528 / Problem: The FPDS-NG User community relies on reports generated from the data reported by various federal agencies. FPDS-NG coexists with Business Objects and Informatica until all the existing reports are migrated to Informatica. Each existing report should be available in both Business Objects and Informatica until Informatica begins to support multiple browsers.
Solution: Currently in FPDS-NG, Informatica is supporting the Internet Explorer web browser only. If the request is invoked from another browser such as, Mozilla, Netscape, or Opera FPDS-NG is directing to Business Objects server. The following message will display.
This FPDSNG report is a newer version of the Next Generation Reporting Module. Next Generation reports provide advanced features such as drill down, dynamic sorting, detail navigation and more
To access this report, please use one of the following browsers, with JavaScript enabled
§ Microsoft Internet Explorer 5.0 and above
§ Mozilla 1.4 or higher
If JavaScript is not enabled when using Internet Explorer, the system must fire the following message when accessing the Informatica reports.
‘JavaScript must be enabled to run report’
Impact Analysis for Users and Integrators
Batch / No Impact
GUI Interface / This FPDSNG report is a newer version of the Next Generation Reporting Module. Next Generation reports provide advanced features such as drill down, dynamic sorting, detail navigation and more
To access this report, please use one of the following browsers, with JavaScript enabled