The Calculated Salary Foundation (CSF) table contains appointment data that normally represents a portion of the ongoing salary commitment for an incumbent in a position that is funded out of a particular account, sub-account, object and sub-object. Positions that are vacant can still be associated with committed funds.
The Genesis batch process (discussed below) uses information in the CSF table to populate the Budget Construction CSF table, the BC perimeter tables, and the salary-setting-related maintenance tables used in Budget Construction.
The overrides are applied by Genesis, which first gets the set of CSF rows, then applies the overrides and stores the results in the BC CSF table. So, your institution's version of the CSF tracker process should not need to apply the overrides during the build of the regular CSF table.
When to Override the
CSF Tracker Table: The base functionality overrides only the CSF table
during the Genesis process. However, your institution should make a decision as
to where it makes sense to see the result of the CSF Tracker overrides (in CSF
or in BC CSF) and make modifications accordingly.
Indiana University's
Implementation of CSF Tracker Table: At Indiana University, each time
the CSF process runs, it re-populates the CSF table with the current set of
commitments from data contained in IU's implementation of PeopleSoft.
Optionally, the process also creates a historical picture of changes to each
position since the beginning of the fiscal
year. Your institution needs to either make a similar process to populate
its version of the CSF Tracker table or manually maintain this table for Budget
Construction. The required rows are those that are currently in the payroll
system or are currently funding a vacant budget line.
More: