V1.4 SP 30.0

From FPDS-NG

Revision as of 21:08, 24 May 2016 by WikiSysop (talk | contribs)
(diff) ←Older revision | view current revision (diff) | Newer revision→ (diff)

Schedule

DescriptionStart Date End Date
BETA Installation Monday April 11, 2016Wednesday April 28, 2016
Government Acceptance Testing Tuesday April 19, 2016Thursday April 21, 2016
Installation in ProductionFriday April 29, 2016Friday April 29, 2016

Document Changes

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

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators
RTC-22070 The following Data Elements are not propagating correctly on Modifications:

Product/Service Code
Principal NAICS Code
Bundled Contract
System Equipment Code
Country of Product or Service Origin
Place of Manufacture
Recovered Materials/Sustainability
InfoTech Commercial Item Category
Claimant Program Code
Sea Transportation
EPA Designated Products


The root cause of the issue lies with the Domestic or Foreign Entity data element. This data element is propagating properly from the base document. However, if the base CAR had information in the Foreign Domestic data element and the modification removes this information, the rest of the data elements in the section are not being retained. This is only for actions with a Dated Signed on or after 1/15/2016. No
IAESAM-330 The letter “S” is not an allowable character for Position 9 in the Solicitation Data Element for DoD. Change business rule DoD1E02 to read "Position 9 of the Solicitation ID (type of instrument code) must be B, N, Q, R, S, T, or U." This is for DoD only. No
IAESAM-331 SBA is requesting that a current exclusion be deleted and a new one added to the Small Business Achievements by the Awarding Agency. Deleted the exclusion for the POP when it is outside of the USA.

Added an exclusion for contracts with Value (A) 'Contingency operation as defined in 10 U.S.C 101(a)(13)’ and Code (B) Humanitarian or peacekeeping operations as defined in 10 U.S.C 2302(8) for the Data Element "Contingency, Humanitarian and Peacekeeping Operation" and the Awarding Agency is DoD and the performance is outside of the U.S. and its territories.

Both changes are effective on 10/1/2015.


No
IAESAM-332 SBA is requesting that a current exclusion be deleted and a new one added to the Small Business Goaling Report.


Deleted the exclusion for the POP when it is outside of the USA.

Added an exclusion for contracts with Value (A) 'Contingency operation as defined in 10 U.S.C 101(a)(13)’ and Code (B) Humanitarian or peacekeeping operations as defined in 10 U.S.C 2302(8) for the Data Element "Contingency, Humanitarian and Peacekeeping Operation" and the Funding Agency is DoD and the performance is outside of the U.S. and its territories.

Both changes are effective on 10/1/2015.

Small Business Goaling Report: https://www.fpds.gov/Reports/manage/html/preview_Small_Business_Goaling_Report.html


No
RTC-20040 Update the interface that FPDS-NG uses to retrieve data from D&B The interface will be updated to use the latest D&B business services methods to retrieve FPDS-NG data from D&B. No
RTC-14743 Atom-Feeds/WSDL discrepancy for Congressional District Code. The atom feed provides the Congressional District based on the Date Signed on the award. The get service provides the latest Congressional District The get service will be changed to use the Date Signed of the contract to determine the Congressional District. No
RTC-17738 When the user sends '&nbsp' in their XML, which is a non printable ASCII character, a validation rule is being displayed. The symbol '&nbsp' represents a “non-breaking space”. In other words, when this symbol is used in a free text field such as “Description of Requirements” our system does not convert this to a blank space and a validation rule fires. When the users sends '&nbsp' in any of the following data elements, Description of Requirement, Ordering Procedure, and Other Statutory Authority the validation rule, “must not contain non-printable ASCII characters”, will not fire. No
RTC-14693 When a user enters a special charter in the XML the rule that is displayed is not descriptive enough for the users to know what the issue is that needs to be fixed. The following validation rule will fire when a hyphen is send in the XML for the Data Element “Place of Performance ZIP Code”. The Value “-”for Data Element “Place of Performance ZIP Code” is invalid. No
RTC-16981 Small Business Dashboard is not displaying correct data when the Contractor State is selected as a filter in the List of Transaction view. The functionality on the Small Business Dashboard will be corrected to display the correct data on the List of Transaction View. No
RTC-16982 The screen view is not large enough to display 2014 and 2015 without the view being distorted. This view will be fixed to display the Small Business data on the screen and the data will be able to be viewed with clarity. No
RTC-17769 When the Country Codes were changed to three characters the US was not changed to USA in the data feeds for award. Therefore, only the IDVs are being downloaded in the Data Feed request. The search functionality of the data feeds shall be updated to look for actions where the Place of Performance country code is three characters. Both IDVs and Awards will now be displayed. No
RTC-20264 Two rules are currently firing when a record is corrected when the Date Signed is earlier than the Prepared Date of 4/30/2015 for a Delivery Order or a BPA Call, and the PIID is 13 characters long. Only the following rule will fire for a Delivery and BPA Call.

DOD1A40:A:If the transaction is an initial award of a Delivery Order or a BPA Call, and the PIID is 13 characters long, then positions 7 and 8 of the PIID must be equal to the fiscal year of the date signed.


No
RTC-21175 A validation rule is not firing on a modification after a new base when the Reason for Modification is 'Definitize Letter Contract’. The following rule will fire one a 'Definitize Letter Contract’ modification on a new base contract.

DOD1B01:I: If Reason for Modification is 'Definitize Letter Contract', then position 2 of the Modification Number must = 'Z'.

No
RTC-21725 Multiple values may be selected for the Data Element Contract Administrations Delegated on the screen by holding "control" and clicking. However, the values are not displayed on the screen after the record is saved/ validated. FPDS-NG shall retain and continue to display all values selected for the data element ‘Contract Administrations Delegated’ after a CAR is saved. This is for NASA only. No