Use this screen to create the PROJ_SUM and PROJ_BURD _SUM tables. All processes after this point will use these tables for project information. It is very important that these tables contain the most current information. Be sure to run this process after posting all transactions.
This is the final step in collecting costs that are used in the Compute Revenue process (Projects\Process\Revenue) and that are printed on the Project Status Report (Projects\Review\Project). For cost at actual or target rates to be accurate for a project, the normal process should include computing pool rates, posting the Pool Journal, and computing burden cost.
|
|
Note: Since the base amount for any given pool is affected by two things, the posting of service center cost, and the motion of indirect cost allocations between pools, you should complete all three steps outlined in order for cost at target rates to be accurate. |
This process uses the actual, target, and cost of money rates contained in the Pool Rates subtask of the Cost Pools screen (Projects\Maintain\Allocations), the override rates in the Burd Cost Ceil screen in the Project User Flow (Projects\Maintain\Project\Project User Flow), the amounts posted to the General Ledger during the posting of the Pool Journal for each account/organization combination, and the data contained in the Rate Application table.
The system derives current subperiod and period-to-date burden costs by multiplying the current subperiod and period-to-date General Ledger costs for all accounts in the Rate Application table by the current period rate from the Pool Rates subtask of the Cost Pools screen (Projects\Maintain\Allocations). The system derives year-to-date burden cost by either multiplying the YTD General Ledger costs for all accounts contained in the Rate Application table by the YTD Rate from the Pool Rates subtask, or by calculating the sum of all current subperiod burden cost for the fiscal year to date, depending on the selection in the Apply Burdening based on group box in the Corporate Settings subtask of the Project Settings screen (Administration\Configure\Projects).
The application uses override rates from the Burd Cost Ceil screen (Projects\Maintain\Projects) to replace YTD target cost. Before this process is completed, all of the direct amounts and burden amounts for each project, for both actual and target rates, are used to update the table from which the Project Status Report is printed. Therefore, until this process is completed, the Project Status Report will not contain accurate data.
|
|
Note: The Cost of Money calculation for this version does not use O/H COM (Overhead Cost of Money) in the calculation of G/A COM (General and Administrative Cost of Money). |
Complete this process after posting all transactions, computing pool rates, and posting the pool journal, and before printing the Project Status Report (Projects\Review\Project) and computing revenue.
What data is used when the PROJ_SUM and PROJ_BURD_SUM tables are created?
The PROJ_SUM is populated when the Compute Burden Cost process is executed.
The Compute Burden Cost process uses amounts posted to the General Ledger to transfer direct costs into the PROJ_SUM table. Rows in the table are summarized by Project/Account/Organization/Fiscal Year/Period/Subperiod. Direct costs, allowable direct costs, burden amounts, allowable burden amounts, cost of money, and revenue amounts are shown in the columns of the PROJ_SUM table.
Burden amounts for the PROJ_SUM table are taken from the PROJ_BURD_SUM table. The rates in the Pool Rates subtask of the Cost Pools screen are used to create the burden columns in the PROJ_BURD_SUM table.
You must execute the Compute Revenue screen (Projects\Process\Revenue) to populate the revenue and fee columns of this table.
What level of the project should I enter in the Projects (Start) field?
You can use the exact project number to compute burden cost, or you can enter the top level of the project, and burden will be calculated for the entire project tree.
What processes use the PROJ_SUM and PROJ_BURD_SUM tables?
Almost all project reports use the PROJ_SUM and PROJ_BURD_SUM tables as the source of direct costs, indirect costs, and revenue amounts.
Revenue is generated by using data in the PROJ_SUM table. All revenue calculations will be incorrect if the burden has not been calculated for the period.
It is essential that you execute the Compute Burden Cost process after entering and posting all costs. Failure to execute in the correct order will result in incorrect revenue and project reports.
The PROJ_SUM table is also used for the Create Cost Transfer Journal Entry screen (Projects\Process\Project)and the Redistribute Revenue screen (Projects\Process\Revenue).
Do I need to run this process again if I post additional data to the General Ledger?
Yes, you must execute the Compute Burden Cost screen each time more data is posted to the General Ledger. The Compute Burden Cost process uses the data in the General Ledger to populate all the direct cost columns (Subperiod, Period, and Year-to-date) in the PROJ_SUM table.
The indirect costs and some of the revenue amounts are based on direct costs in the PROJ_SUM table.
If I change the target rates, do I need to run this process again?
If the target rates change for the period that is currently being processed, you must execute the Compute Burden Cost screen after the changes in target rates have been entered.
You should run the Compute Burden Cost process again if the direct costs on the Project Status Report and the Project Non-Labor Detail report do not match.
The direct costs on the Project Non-Labor Detail report are printed directly from data in the General Ledger. The direct costs on the Project Status Report are printed from the direct costs columns in the PROJ_SUM table. If there is a discrepancy, there was probably a posting of direct cost after the Compute Burden Cost process was executed.
You need to run the Compute Burden Cost process only if changes have been made to the prior period since the period was closed.
We recommend that you close the period once all processes have been run and reports have been produced. You cannot post data to a closed period.
Use the fields in this block to create a new parameter ID or to retrieve a previously saved parameter ID. A parameter ID represents a set of screen selection parameters. Once you have saved a parameter ID and its related parameters, you can retrieve them using Query.
You can use the retrieved parameters to produce reports and run processes more efficiently and with greater consistency. Many users save a unique set of parameters for each different way they run a report or process. If you select a previously saved parameter ID or parameter description, the associated saved screen selection parameters will automatically display as selection defaults. You can change any of the associated selection defaults as necessary.
Enter, or use Query to select, a parameter ID of up to 15 alphanumeric characters. You should choose characters for your parameter ID that help identify the type of selections you made in the screen, such as “PERIOD” or “QUARTERLY.”
When you save your record, all the selections made in the screen are stored with the parameter ID. Later, you can retrieve the parameter using Query.
You can use the parameter to produce reports and run processes more efficiently because you can select the parameter ID with its previously defined screen selections. Once the default selections display in the screen, you can override the defaults as necessary.
Enter, or use Query to select, a parameter description of up to 30 alphanumeric characters.
Use the fields in this block to select the periods and projects for which you wish to compute burden costs.
|
|
Note: During your period end closing process, you must compute burden cost on all projects at least once. |
Accounting Periods
Use this drop-down box to select the range of subperiods that you want to include in the process. The following options are available:
All - Select this option to include all available subperiods. The Start and End fields are disabled for this option.
One - Select this option to include only one subperiod. You must enter that value in the Start field. The End field is disabled for this option.
Range - Select this option to include a contiguous range of subperiods. You must enter the beginning value for the range in the Start field and the ending value of the range in the End field.
From Beginning - Select this option to include all the subperiods from the beginning of the available subperiods to a specific subperiod in the range. You must enter the last value for the range in the End field. The Start field is disabled for this option.
To End - Select this option to include all the subperiods from a specific subperiod to the end of all the available subperiods. You must enter the value from which the range should begin in the Start field. The End field is disabled for this option.
Enter, or use Lookup to select, the fiscal year for which you want to compute burden cost.
Enter, or use Lookup to select, the accounting period for which you want to compute burden cost.
Enter, or use Lookup to select, a starting subperiod number for the range that you want to include in the process.
If you select "One," "Range," or "To End," in the Option field, you must enter a subperiod number in this field.
If you select "All" or "From Beginning" in the Option field, this field will be inactive.
This non-editable field displays the subperiod ending date of the subperiod entered in the Subpd (Start) field.
Enter, or use Lookup to select, an ending subperiod number for the range that you want to include in the process.
If you select "All," "Range," or "From Beginning" in the Option field, you must enter a subperiod number in this field.
If you select "One" or "To End" in the Option field, this field will be inactive.
This non-editable field displays the subperiod ending date of the subperiod entered in the Subpd (End) field.
Projects
Use this drop-down box to select the range of project numbers that you want to include in the process. The following options are available:
All - Select this option to include all available projects. The Start and End fields are disabled for this option.
One - Select this option to include only one project. You must enter that value in the Start field. The End field is disabled for this option.
Range - Select this option to include a contiguous range of projects. You must enter the beginning value for the range in the Start field and the ending value of the range in the End field.
From Beginning - Select this option to include all the projects from the beginning of the available projects to a specific project in the range. You must enter the last value for the range in the End field. The Start field is disabled for this option.
To End - Select this option to include all the projects from a specific project to the end of all the available projects. You must enter the value from which the range should begin in the Start field. The End field is disabled for this option.
Enter, or use Lookup to select, a starting project number for the range that you want to include in the process.
If you select "One," "Range," or "To End," in the Option field, you must enter a project number in this field.
If you select "All" or "From Beginning" in the Option field, this field will be inactive.
Enter, or use Lookup to select, an ending project number for the range that you want to include in the process.
If you select "All," "Range," or "From Beginning" in the Option field, you must enter a project number in this field.
If you select "One" or "To End" in the Option field, this field will be inactive.
* A red asterisk denotes a required field.
Executing this process updates the following tables:
PROJ_SUM (Project Summary)
PROJ_BURD_SUM (Project Burden Summary)
