Difference between revisions of "Data Management SP4.0"
From FPDS-NG
Line 19: | Line 19: | ||
</td> | </td> | ||
<td> | <td> | ||
− | Extent competed values will be | + | Extent competed values will be populated from the parent contracts. |
</td> | </td> | ||
<td align="center">700 records</td> | <td align="center">700 records</td> | ||
</tr> | </tr> | ||
</table> | </table> |
Revision as of 23:58, 22 July 2010
Listed below are the data management fixes that will be completed on July 22, 2010:
SPR # | Problem | Solution | Awards/IDVs Fixed |
---|---|---|---|
FPDSNG-3636 |
Due to Change PIID action contracts have been populated with blank TAS codes |
All contracts that have been finalized with an action obligation value other than zero will be populated with the TAS codes. |
100 records |
FPDSHD-75965 |
Extent competed values are not getting populated for delivery orders from Parent contracts due to a bug fix deployed on SP4.0 |
Extent competed values will be populated from the parent contracts. |
700 records |