Repair Invalid Pools in Project Ledger
Use this toolkit to compare your project burden summary table (PROJ_BURD_SUM) with your cost pool setup table (ALLOC_APPLIC) for a given fiscal year.
If you have made modifications to your cost pool bases, you must execute the Build Rate Application Table screen to update the ALLOC_APPLIC table. The ALLOC_APPLIC table directs how the Compute Burden Costs screen allocates. When you run the Compute Burden Costs screen, PROJ_BURD_SUM is updated with the burden for the appropriate direct cost. If you have deleted any account/organization/pool combinations from your cost pool base (and ALLOC_APPLIC) that already exist in PROJ_BURD_SUM, year-to-date burden still exists for projects using those combinations. Invalid combinations are displayed in the table window and written to the Z_PJPTOOL_ERRORS table. This toolkit then inserts a row into PROJ_BURD_SUM, into the fiscal year/period/subperiod selected, that contains the reversed year-to-date burden for each unique project/organization/account/pool combination. Note that the period that is selected on this screen must be your current period and have an Open status. After running this toolkit, execute the Compute Revenue screen for all projects. This captures the revenue for any burden that has been inserted by the toolkit.
The Fix Invalid Pools toolkit does not delete the affected rows in the PROJ_BURD_SUM table, but zeros out the sum of the sub_tgt_amt and sub_act_amt fields on a YTD basis in the subperiod in which the toolkit is run. Therefore, when the View Invalid Pools in Project Ledger toolkit is run again, it still finds rows to return since those rows are not in ALLOC_APPLIC table. However, the Repair Invalid Pools in Project Ledger toolkit does not find any rows to fix if the sum of the sub_tgt_amt and sub_act_amt fields is zero YTD.