V1.4 SP5.0

• FPDS-NG shall allow users to correct or create the IDV successfully irrespective of the number of referencing Contracts.
• If the number of referencing contracts is less than a specific number then the referencing contracts shall be updated with the propagated information instantaneously.
• If the number of referencing contracts for the IDV is more than a specific number then upon successful correction or creation of an IDV, FPDS-NG shall the display the following informational message and update the referencing contracts with the propagated information within 48 hours:

‘IDV successfully corrected and the referencing contracts are being updated. Please contact FPDS-NG helpdesk if the referencing contracts do not get updated within the next 48 hours.’

‘IDV successfully approved and the referencing contracts are being updated. Please contact FPDS-NG helpdesk if the referencing contracts do not get updated within the next 48 hours.’

• All the requirements apply for ‘Approve’ and ‘Correct’ operations through Web Portal and Business Services for all versions.

Errors: 0: 8001 The Referenced IDV with Agency: 9700, PIID: DCA20002D5007, and ModNumber 0 does not exist.

• The system responses to create a Civilian Award against a DoD IDV shall be dependent on the value for “Who Can Use” on the referenced IDV as specified in Table 1 below.
• The requirement applies for Web Portal scenarios and for GUI Services and Business Services for all Versions.

• FPDS-NG shall use the “Renewal Date” from the CCR as the “Expiration Date” of the CCR registration for the vendor. FPDS-NG shall display the following error message if the “Date Signed” on the contract is later than the above mentioned “Renewal Date” for the vendor.

The vendor selected is inactive in CCR for the “Date Signed” provided. Please contact CCR for more information.

• The above validation rules applies for ‘Validate’, ‘Approve’ and ‘Correct’ operations through GUI Services and Web Portal. It applies on ‘Correct’ only if the “Date Signed” or DUNS Number is changed.
• The above validation rule applies to ‘isComplete’, ‘isExistingIDVComplete’, ‘isExistingAwardComplete’, ‘approve’ and ‘correct’ operations through Business Services. It applies on ‘Correct’ operation only if the “Date Signed” or DUNS Number is changed.
• All above requirements applies only on base documents and vendor modifications for all versions.
• The Version 1.4 and 1.3 Validation Rules document will be updated to include the changes.

FPDS-NG shall deprecate the following operations from GUI Services:

• getNewAwardURLFromTemplate
• getNewIDVURLFromTemplate
• FPDS-NG shall not display the above mentioned APIs as operations in any of the following WSDLs:
  • http://www.fpds.gov/FPDS/GUIServices/DataCollection/contracts/1.4/IDV.wsdl
  • http://www.fpds.gov/FPDS/GUIServices/DataCollection/contracts/1.4/Award.wsdl
• FPDS-NG shall update the Web Services Specifications documents for V 1.3 and V 1.4 to remove getNewAwardURLFromTemplate, getNewIDVURLFromTemplate.
• FPDS-NG shall update the Award and IDV WSDLs posted on the worksite for GUI Services to remove the ‘getNewAwardURLFromTemplate’ and ‘getNewIDVURLFromTemplate’ operations.

10C20 – “If "Other than Full and Open Competition" is 'Authorized by Statute' or 'SAP Non-Competition', then "Local Area Set Aside" must be 'No'.”

10U02 – “The Local Area Set Aside must not be selected if the “Date Signed” is prior to "08/04/2006".”