V1.3 SP11.0 (July 10, 2009)
From FPDS-NG
Schedule
| Description | Start Date | End Date |
|---|---|---|
| BETA Installation | Wednesday June 17, 2009 | Wednesday June 17, 2009 |
| Final Quality Testing (FQT) | Monday June 22, 2009 | Thursday June 25, 2009 |
| Installation in Production | Friday July 10, 2009 | Friday July 10, 2009 |
Document Changes
| Documentation | Changes Required |
|---|---|
| XML Specifications | No |
| Web Services | No |
| Data Dictionary | Yes |
| NASA Specific Data Dictionary | No |
| Use Case Summary | No |
| Validation Rules | Yes |
| Online Help | Yes |
| Computer-Based Training | No |
| Report Manual | No |
SPR Listing
| SPR # | Problem | Solutions | Impact to Users and Integrators |
|---|---|---|---|
| FPDSHD-51773 | Template is not able to save the user provided value for the data element, “Commercial Item Test Program”.Documents created from a template are not saving the user provided value for the data element, “Local Area Set Aside”. | Template created from a document shall continue to inherit the values from the document. Additionally, user provided values shall be saved.Documents created from a template shall continue to inherit the values from the template. Additionally, user provided values shall be saved. | No |
| FPDSHD-51902 | FPDS-NG does not allow selection of the PSC code, S208 (Landscaping/Groundskeeping Services) and the NAICS code, 561730 (Landscaping Services). The validation rules 8A21 and 8G04 prevent the selection. | FPDS-NG shall allow the combinations of PSC codes and NAICS codes for an ‘Emerging Small Business Set Aside’ as stated in Table 4. | No |
| FPDSNG-3563 | When sending an invalid value for the Treasury Account Symbol (TAS) in the “Description of Contract Requirements”, documents can be approved through business services/ web portal. | FPDS-NG shall throw the following validation error when the user sends an invalid TAS symbol in the “Description of Requirement” field when approving the contract. “Treasury Account Symbol should be of format TAS::XX XXXX::TAS or TAS::XX XXXX XXX::TAS and should not contain special characters.” | No |
| FPDSHD-51222 | When the base Indefinite Delivery Vehicle (IDV) is corrected for the Legislative Mandate values, the corrected values are not being pushed (populated) to the IDV modification documents and the referencing awards. | When an IDV is corrected, the updated values for the Legislative Mandates shall propagate from the IDV to its modifications and to the referencing awards. | No |
| FPDSHD-50685 | The awards archive reports 1,295,530 records, but only contains 1,295,529 awards. The XML file contains 1,295,536 lines with six lines for the header, and one line for the footer. Hence, there are only 1,295,529 lines containing record data. | XML archives shall display the correct number of records. The number of records in the file should match the number of records mentioned in the file header. | No |
| FPDSHD-51805 | Whenever a correction or a modification is made to a finalized FPDS-NG contract, and user has accessed the Vendor Selection screen to edit the Doing Business as Name (DBAN), the system does not save the changes. | The user selected DBAN value shall be persisted on the contract when editing vendor information on a base or on a modification with reason for modification as “Novation Agreement” or “Vendor DUNS Change.” | No |
| FPDSHD-52440 | The dollar amounts in the “Total” column on modifications are being displayed as “$0.00” for public user accounts regardless of the calculated value for each field. | For public user accounts, the dollars shall be displayed correctly in the “Total” column on all contract modifications. | No |
| FPDSHD-55569 | Voiding an FPDS-NG document locks the PIID so that it may not be used again. From the perspective of the user, this action is permanent and the document cannot be deleted, restored, or recreated. If the “Void” function is chosen incorrectly by the user for a contract that he or she wishes to delete and recreate, the user must request a Data Management fix to delete the “Void” contract. Therefore, deprecation of the “Void” function shall be considered. | As per the decision made by the FPDS-NG CCB, the “Void” function shall be deprecated from the system. | No |
| FPDSHD-52132 | The Federal Information Processing Standards (FIPS) Character code has been changed for the country ‘Serbia’ from ‘RB’ to ‘RI’ as per the FIPS 10-4 Change Notice number 14 dated July 31, 2008.
http://earth-info.nga.mil/gns/html/Change_Notice_14.pdf. This information needs to reflect correctly in FPDS-NG. Click here to download the Adode Acrobat Reader |
FPDS-NG shall end date the FIPS code value 'RB' for the country code 'SRB' and add the FIPS Code 'RI' for Country Code 'SRB'. | No |
| FPDSHD-56589 | The user reported receiving the following error while correcting Version 1.0 and Version 1.1 contracts: “The last transaction could not be completed successfully.” | The ‘Correct’ operation on Version 1.0 and Version 1.1 Awards and IDVs shall not display the following error message:
“The last transaction could not be completed successfully.” The user should be able to either successfully correct the contract or should get business rule validation errors if any. |
No |
| FPDSHD-51798 | The “Local Area Set Aside” is a required element for DOs and BOAs in the Version 1.3 Data Dictionary. | For the “BPA Call”, the Use Case needs to be changed from “Not Required” to "Required" as described in the Local Area Set Aside Requirements Document.
The modification use case for both Civilian and DoD shall be updated to “Not Required” in the 1.3 Data Dictionary. The warning messages for not required elements shall be updated to mention whether the element is not required on a Base or a Modification. "<Element_Name>" is not applicable on <Base_or_Mod> for <Contract_Type> type: <Contract_Action_Type>. |
No |