V1.4 SP5.0

The user reported an issue not being able to create a Modification to the Award ‘DJA04B000694’. The following message is being displayed while creating an Award referencing an IDV:

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

FPDS-NG shall allow a Civilian user to create a Delivery/Task Order or a BPA Call against any unrevealed DoD IDV (Base or Vendor Mod) and the following message shall not be displayed:

“The Referenced IDV with Agency: 9700, PIID: <<piid>>, and ModNumber 0 does not exist.”

• The existing functionality for Civilian DOs/BPA Calls referencing revealed DoD IDVs shall remain unchanged.

• The existing functionality for DOs/BPA Calls referencing base/Vendor modification of an IDV based on date signed shall remain unchanged.

• Requirement 1 and 2 shall apply for ‘create’, ‘createFromTemplate’ through Business Services for base and modifications for all referencing awards on Version 1.3 and Version 1.4.

• Requirement 1 and 2 shall apply for ‘Save Draft’ on Web Portal scenarios and for base and modifications for all referencing awards on Version 1.3 and Version 1.4.

The selected vendor with “DUNS Number” <<dunsNumber>> has expired on <<dateSigned>>. Please select a valid vendor..

• The above requirement shall apply for ‘Validate’, ‘Approve’ and ‘Correct’ operations through GUI Services and Web Portal. It shall apply on ‘Correct’ only if the “Date Signed” or DUNS Number is changed.
• The above requirement shall apply to ‘isComplete’, ‘isExistingIDVComplete’, ‘isExistingAwardComplete’, ‘approve’ and ‘correct’ operations through Business Services. It shall apply on ‘Correct’ operation only if the “Date Signed” or DUNS Number is changed.
• The above requirements shall apply only on the following base documents and their vendor modifications for all versions:

Award: PO, DCA, OT Agreement, Cooperative Agreement, Grant For Research, Intragovernmental, Funded Space Act Agreement, Training Grant. IDV: IDC, BOA, Stand-alone BPA, GWAC, FSS, OT IDV.

• The Version 1.4 and 1.3 Validation Rules document shall be updated to include the changes.

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

• FPDS-NG shall suppress the following Validation Rule for contracts having “Date Signed” prior to ‘08/04/2006’ for all versions. The rule shall continue to fire for contracts having “Date Signed” greater than ‘08/04/2006’.

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

• FPDS-NG shall ensure that the following validation rules are displayed on Version 1.4 based on the “Date Signed” of the contract:

‘10U01’ – “The Local Area Set Aside” must be selected if the “Date Signed” is later than "08/04/2006".”

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

• The above validation rules shall fire for ‘Validate’, ‘Approve’ and ‘Correct’ operations through GUI Services and Web Portal.
• The above validation rules shall fire for‘isComplete’, ‘isExistingIDVComplete’, ‘isExistingAwardComplete’, ‘approve’ and ‘correct’ operations through Business Services.
• The Version 1.4 and 1.3 Validation Rules document shall be updated to include the changes.
• FPDS-NG shall have a Data Management fix to remove all the values for “Local Area Set Aside” from contracts having “Date Signed” prior than ‘08/04/2006’.

“The value "64133 4676" for Data Element "Place of Performance (PoP) ZIP Code" is invalid.”

• Through Business Services, FPDS-NG shall validate the “Place of Performance Zip Code” on ‘create’ and ‘update’ only when the Zip Code is sent in the request.
• The following Validation Rule shall be displayed when the Zip Code sent is invalid or end dated and the document shall be saved in error status:

“The value <<zipCode>> for Data Element “Place of Performance ZIP Code” is invalid.”

• Through Business Services, FPDS-NG shall propagate the “Place of Performance Zip Code” from the latest modification document on ‘create’ of Modification when the Zip Code is not sent in the request. The propagated Zip Code shall not be validated on ‘create’ and the document shall be saved in ‘draft’ status successfully.
• FPDS-NG shall display and validate the “Place of Performance Zip Code” on ‘Save Draft’, ‘Validate’, ‘Approve’ and ‘Correct’ through Web Portal and GUI Services.
• FPDS-NG shall validate the “Place of Performance Zip Code” on ‘isComplete’, ‘isExistingAwardComplete’, ‘approve’ and ‘correct’ through Business Services.
• All the above requirements apply on Modifications and to Version 1.3 and 1.4.