Difference between revisions of "V1.4 SP11.0"

1. FPDS-NG does not store the values for “Base and Exercised Options Value” and “Non-Government Dollars” fields correctly on OT IDVs and “Non-Government Dollars” on OT Agreement and Orders.

2. FPDS-NG is propagating the dollar values on Modifications when XML tags are not sent through Business Services even when the use case is ‘Required’.

3. FPDS-NG allows a user without OT privileges to update/create OT contracts for users.

4. FPDS-NG considers the time stamps in dates for the following date related Validation Rules:

• OT2B02 - Effective Date cannot be earlier than the Date Signed on the base document.

• OT2C03 – “Current Completion Date” must be less than or equal to “Ultimate Completion Date”.

5. FPDS-NG currently displays Contractor Name on the Web Portal screen for all OTs but it does not get saved through Business Services.

6. FPDS-NG displays the mandatory Validation error for “Place of Performance Zip Code” even when “Place of Performance Country” is not US.

7. FPDS-NG considers the Dollar values on that specific action instead of considering the Total dollars for the following rule:

• 3B02 - The "Change in Base And Exercised Options Value" must be less than or equal to the "Base And All Options" value.

2. FPDS-NG should not propagate the dollar values on Modifications on OTs.

3. FPDS-NG should not allow a user without OT privileges to ‘update’/’create’ OT contracts.

4. FPDS-NG should not consider the time stamps in date fields for date related Validation Rules.

5. FPDS-NG should deprecate the data element “Contractor Name from Contract” from the screen for all OTs and ensure that this XML tag is not sent in the Response XMLs.

6. FPDS-NG should not display the mandatory Validation error for “Place of Performance Zip Code” even when “Place of Performance Country” is not US.

7. FPDS-NG should consider the Total dollars instead of Dollar values on that specific action for the following rule:

• 3B02 - The "Change in Base And Exercised Options Value" must be less than or equal to the "Base And All Options" value.

This IDC was signed on 07/23/2007 and was finalized to a CCR Exception vendor. Between then and now, the vendor has registered in CCR. When the user was trying to correct the IDC for the data element “Contracting Officer’s Determination of Business Size”, FPDS-NG is performing the vendor validation. Since the vendor has changed from a non-CCR vendor to a CCR vendor, FPDS-NG is displaying the above mentioned error.

• If the Type of Set Aside is 8a Competed or 8(a) Sole Source, then Business Type must be 8(a) Firm or 8(a) Joint Venture.

Between the original contract and the time when the Transfer Base was done, the vendor had graduated from being an SBA Certified 8(a) Program Participant. FPDS-NG is validating the vendor data against CCR and is displaying the above error message.

1. DOD10R02 - If the transaction is type Delivery Order referencing a Multiple Award IDV (FSS, GWAC, Multiple Award IDC) and "Solicitation Procedures" is 'Multiple Award Fair Opportunity' then "Statutory Exception to Fair Opportunity" must be 'No exception - Fair Opportunity given'.

2. DOD10R03 - If transaction is type Delivery Order referencing a Multiple Award IDV (FSS, GWAC, Multiple Award IDC) and "Solicitation Procedures" is 'Multiple Award Fair Opportunity' then "Number of Offers" must be greater than or equal to one.

3. DOD10R05 - If the transaction is of type Delivery Order referencing a multiple award IDV (FSS, GWAC, Multiple Award IDC) then Statutory Exception to Fair Opportunity must have a value.

When such IDV Modifications are corrected and accessed again, either a blank page or a System Error is displayed. This is because the value for the data element, “Fee for Use of Service” is not saved in the database.

Data Fix: IDVs with “Fee for Use of Service” chosen as either ‘Varies by Amount’ or ‘Varies by Other Factor’, but having a null value for “Lower Value” and/or “Upper Value” shall be marked with the values obtained from the Audit Log table. IDVs that do not exist in the Audit Log table shall be sent to the agencies.

When a Part 8 BPA is approved, the vendor information on the BPA is updated from the FSS correctly but is not propagated to the Part 8 BPA Call and the BPA Call still references the older BPA.

A data management script will be executed to update reference mod number and vendor information on DO and BPA Calls referencing wrong Part 8 BPAs mods based on date signed.This script will update 53,000 contracts approxmimately.

TAS is currently ‘Optional’ for DoD. It is a requirement from GSA to apply the civilian behavior of TAS to DoD.

1. The validation rule, '"Agency Identifier" and "Main Account Code" are required when "Action Obligation" is either greater than zero or less than zero' shall start to display for DoD.

2. The above validation rule shall start firing on all existing DoD contracts in Version 1.3 and 1.4 when and “Action Obligation” is greater than or less than zero (0) and TAS is empty.

3. For Version 1.4 actions, TAS can be entered through the TAS Data Elements on Web-Portal or the XML tags in Business Services.

4. For Version 1.3 actions, if the CWS is Business Services only TAS and “Initiative” (for recovery actions) can be entered through “descriptionOfRequirements” XML tag else TAS should be entered through the TAS fields on the Web Portal.

5. For Version 1.2 actions, TAS and “Initiative” (for recovery actions) has to be entered through “descriptionOfRequirements” XML tag or “Description Of Requirements” data element on the Web Portal. Format through Description of Requirements: TAS::XX XXXX XXX::TAS, ARRA::YES::ARRA

6. FPDS-NG shall not automatically mark recovery actions. Users need to specify “Initiative” as ‘American Recovery and Reinvestment Act’ to mark them as such (V1.4 Business Services Code: ‘ARRA’ for the XML tag “initiative”). In Version 1.3 and 1.2, to mark actions as recovery the following has to be sent: ARRA::YES::ARRA and in Version 1.4: <initiative>ARRA<initiative>