Difference between revisions of "V1.4 SP 21.0"

From FPDS-NG
Line 57: Line 57:
 
<tr>
 
<tr>
  
−
<td style="width:95px" valign="center">FPDSHD-116158</td>
+
<td style="width:95px" valign="center">FPDSHD-101109</td>
−
<td>It is reported that records are missing from FPDS-NG Standard Reports, but the data exists in the Award database.  The records missing from reports are found to not have data in two of the tables containing vendor information about each record. The missing data in these tables has caused the records to not be included in the nightly refresh that would include them in the Standard Reports, Ad Hoc reports, ezSearch, and Atom Feeds. This does not impact the Data Archives as they are generated from the transactional tables.
+
<td>The “Contracting Office Report” is displaying the “Contracting Offices” as ‘Inactive’, when they are not. This is the case when the office is active as the “Contracting Office” and is inactive as the “Funding Office”.
  
−
Vendor information is saved to 4 different tables when an Award or IDV is saved in FPDS-NG: Vendor, Vendor Location, Socio-Economic Indicators, and Business Types.  The issue has occurred because a server has thrown an exception that was not handled and data was not stored to all 4 tables for a given transaction.
+
<td>1. If the civilian office is active as the “Funding Office” and is inactive as the “Contracting Office”, the “Contracting Office” report shall display both the entries as they are.
  
−
<td>1. FPDS-NG shall not store partial information of the vendor while finalizing a contract. FPDS-NG shall store complete Vendor information in all four tables (Vendor, Vendor Location, Socio-Economic Indicators, and Business Types) on all final records. This will ensure that records appear in Standard Reports, Ad Hoc reports, ezSearch, and Atom Feeds.
+
2. If the civilian office is active as the “Funding Office” and is active as the “Contracting Office”, the “Contracting Office” report shall display both the entries as they are.
  
−
2. The exception that has occurred to cause the issue shall be handled so that if the transaction cannot be completed with data in all 4 Vendor tables (Vendor, Vendor Location, Socio-Economic Indicators, and Business Types), then the transaction shall be rolled back and no partial entry shall be permitted.CWS will get the system error when the transaction rolls back.  System shall throw an exception so that production operations team can perform the maintenance on the server.
+
3. If the civilian office is inactive as the “Funding Office” and is active as the “Contracting Office”, the “Contracting Office” report shall display both the entries as they are.
  
−
3. FPDS-NG shall add a verification process to catch discrepancies in counts between the Award/IDV transaction tables and the Reports Repository from which Standard and Ad Hoc Reports are generated. (A verification check between the Reports Repository and the ezSearch index already exists).
+
4. For the DoD office SPM8CP (agency is 97AS) that is inactive as the “Funding Office” and is active as the “Contracting Office”, the “Contracting Office” shall be end dated as of 11/04/2010.
  
−
4. FPDS-NG shall perform a Data Management fix to populate the Vendor tables that are missing data so that the records shall become available in the Standard Reports, Ad Hoc reports, ezSearch, and Atom Feeds.
+
5. For the civilian and DoD offices that are inactive as the “Funding Office” and are inactive as the “Contracting Office”, the “Contracting Office” report shall display both the entries as they are.
 +
 
 +
6. The DoD “Funding Offices” that are under ‘9700’ but the corresponding “Contracting Offices” are shown under the appropriate ‘97xx’ agency, the agency code of the “Funding Offices” shall be updated to fall under the agency code of their “Contracting Offices”.
  
 
</td>
 
</td>

Revision as of 18:39, 15 July 2013

Schedule

DescriptionStart Date End Date
BETA Installation Monday October 07, 2013Tuesday October 08, 2013
Functional Qualification Testing Tuesday October 08, 2013Thursday October 10, 2013
Installation in ProductionFriday October 18, 2013Friday October 18, 2013

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data Dictionary No
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesYes
ReportingYes
ezSearchYes
Atom FeedsYes
Online HelpNo
Computer-Based TrainingNo
User ManualNo

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators
FPDSHD-117314, 17999 FPDSHD-117999: The “Rerepresentation Eligible Actions Report” is displaying actions that are marked “JWOD”, “HBCU”, “Tribal Government”, “Local Government”, “State Government” or “Federal Government”.

FPDSHD-117314: The search criteria screen for the “Rerepresentation Eligible Actions Report” is putting the user provided dates back to 5 years.

1. The filter set when saved on the search criteria screen shall not set the date range back to 5 years.

2. The “Rerepresentation Eligible Actions Report” shall not display the actions that are marked with any of the following vendor flags:

• JWOD (The AbilityOne Program)

• HBCU

• U.S. Tribal Government

• U.S. Local Government (City, County, Inter-Municipal, Local Government Owned, Municipality, School District and/or Township)

• U.S. State Government

• U.S. Federal Government (Federal Agency and/or Federally Funded Research and Development Corp)

3. The report Appendix shall be updated to indicate the above condition.

No
FPDSHD-101109 The “Contracting Office Report” is displaying the “Contracting Offices” as ‘Inactive’, when they are not. This is the case when the office is active as the “Contracting Office” and is inactive as the “Funding Office”. 1. If the civilian office is active as the “Funding Office” and is inactive as the “Contracting Office”, the “Contracting Office” report shall display both the entries as they are.

2. If the civilian office is active as the “Funding Office” and is active as the “Contracting Office”, the “Contracting Office” report shall display both the entries as they are.

3. If the civilian office is inactive as the “Funding Office” and is active as the “Contracting Office”, the “Contracting Office” report shall display both the entries as they are.

4. For the DoD office SPM8CP (agency is 97AS) that is inactive as the “Funding Office” and is active as the “Contracting Office”, the “Contracting Office” shall be end dated as of 11/04/2010.

5. For the civilian and DoD offices that are inactive as the “Funding Office” and are inactive as the “Contracting Office”, the “Contracting Office” report shall display both the entries as they are.

6. The DoD “Funding Offices” that are under ‘9700’ but the corresponding “Contracting Offices” are shown under the appropriate ‘97xx’ agency, the agency code of the “Funding Offices” shall be updated to fall under the agency code of their “Contracting Offices”.

No
FPDSHD-115807 FPDS-NG is incorrectly propagating the value for TOSA on an ‘update’ XML request when “Fair Opportunity/Limited Sources” is either ‘Competitive Set Aside’ or ‘Sole Source’. FPDS-NG shall not propagate the value for TOSA from the IDV when “Fair Opportunity/Limited Sources” is either ‘Competitive Set Aside’ or ‘Sole Source’. No
FPDSHD-115803 When the length of the “Maximum Order Limit” value is greater than ‘15’, the Atom Feeds are not displaying the value as expected.

1. FPDS-NG shall display a validation rule on the IDVs indicating that the length of the “Maximum Order Limit” shall not exceed 20. The length includes the two decimal places.

Sample edit: Length of the “Maximum Order Limit” shall not exceed 20. The maximum value allowable value is ‘999,999,999,999,999,999.99’.

2. Atom Feed requests (DoD and Public) shall display the “Maximum Order Limit” value as provided on the IDVs. The value shall be retrieved with two decimal places. E.g.: 99999999999999.00.

3. The Data Validation Rules document for V 1.3 and V 1.4 shall be updated with the new validation rule.

No
FPDSHD-114881 The validation rules for "Inherently Governmental Function" are firing when the "Product or Service Code" is corrected from a 'Service' to a 'Product'. On the base document:

1. FPDS-NG shall not fire 6M12, 6M13, 6M14 when the PSC is corrected from a Service to a Product. This applies to ‘Correct’ of the documents.

2. FPDS-NG shall not fire 6M16 when the Date Signed is prior to 03/01/2012 and when the PSC is a Product. This applies to ‘Create-Update-Validate-Approve’ of the documents.

On the non-Change PIID modification done against a base (mod 0) document:

1. FPDS-NG shall not fire 6M14 (6M15 shall continue to display) when the PSC is corrected from a Product to a Service, and when the Date Signed on the base document is earlier than 03/01/2012. This applies to ‘Correct’ of the documents.

No
FPDSHD-116863-114046 FPDSHD-116863: The correction of “Contracting Officer’s Determination of Business Size” on the base documents is not being propagated to the modifications, as expected.

FPDSHD-114046: Novation modifications that were signed prior to 06/30/2007 are not retaining the user provided value for “Contracting Officer’s Determination of Business Size”.


1. Correction of the value for “Contracting Officer’s Determination of Business Size” on the base (modification number = 0) documents shall propagate the value for all types of modifications, except:

i. Novation Agreement

ii. Rerepresentation

iii. Rerepresentation of non-Novated Merger/Acquisition

iv. Any modifications that are signed on or later than the above three modifications

2. Correction of the value for “DUNS Number” on the base (modification number = 0) documents shall propagate the Vendor data (Vendor DUNS, name, address and socio-economic data) for all types of modifications, except:

i. Novation Agreement

ii. Vendor DUNS Change (Vendor socio-economic data and Contracting Officer’s Determination of Business Size shall propagate from the base)

iii. Any modifications that are signed on or later than the above two modifications

3. When a Novation is submitted without changing the DUNS Number, a validation rule shall be displayed indicating that the DUNS Number should be changed. The sample validation rule is indicated here:

The DUNS Number on the Novation modification must be different from that on the previous modification.

No
FPDSHD-116533 FPDS-NG is incorrectly displaying an error when attempting to approve a ‘Change PIID’ Modification when it is the first Modification (New Base) after a Transfer Action. FPDS-NG shall allow a ‘Change PIID’ Modification to be successfully approved when it is the first Modification (New Base) after a Transfer Action and it has been validated successfully. No
Retrieved from "https://www.fpds.gov/wiki/index.php?title=V1.4_SP_21.0&oldid=4355"