Difference between revisions of "V1.4 SP 20.0"

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.

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. 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. 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.

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.

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.

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”.

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.