to select, the beginning revenue formula
for the range to compute. Twenty-six revenue formulas are available via
. This field is available only if you selected One,
Range, or To
End as the Range
Option.Use this screen to control the process of computing revenue for projects. The following revenue formulas are available: Do Not Compute, Contract Value Less Backlog, Labor Cost times Multiplier plus Non-Labor times Multiplier, Cost Plus Fee On Cost, Cost Plus Fee on Cost Current Month Fee, Fee On Hours Plus Cost Incurred, Contract Value Times Percent Complete, Contract Value Times % Complete Vs. Rate Schedule, Cost Incurred Using Estimate at Completion, Equal to Billings Before Retainage, Equal to Billings After Retainage, Cost Incurred Using Estimate to Complete, Equal to Deliveries, Equal to Project Ledger Sales, Fixed Amount Contract to Date, Fixed Amount Month to Date, Fixed Amount Year to Date, Loaded Labor Rate, Loaded Labor Rate W/Burden W/Fee Plus Non-Labor W/Burden W/Fee, Loaded Labor Plus Non-Labor W/Burden W/Fee, Loaded Labor Rate Plus Cost Incurred On Non-Labor (T&M), Loaded Labor Plus Non-Labor Plus Burden on Non-Labor, Loaded Labor Rate W/Fee Plus Non-Labor W/Burden W/Fee, Rate Schedule times Multiplier Plus Non-labor times Multiplier, and Unit Revenue Only. All computations performed by this process are controlled by the revenue formula you assigned to the project in the Basic Revenue Info screen (Projects » Project Setup » Revenue Setup).
For more information on Revenue Computations, see Projects Special Topic PJ-12, "Revenue Computations."
You can start this process only after completing the Compute Burden Cost screen (Projects » Cost and Revenue Processing » Project Cost Processing) and before printing a Project Status Report containing revenue or profit information. Also run it before initiating either of the Redistribute Revenue programs in the Revenue Processing menu.
If you are computing revenue for a new fiscal year, execute the Update Prior Year History screen (Projects » Project Setup » Project History) to update the prior year's data before you compute revenue for the new year. Otherwise, your revenue calculations for the new year could be misstated. The Update Prior Year History screen combines the current year project tables (PROJ_SUM and PROJ_BURD_SUM) with the prior year project tables (PSR_PY_SUM and PSR_PY_BURD_SUM). The prior year project tables are the source for prior year cost and revenue amounts in the Compute Revenue process (Projects » Cost and Revenue Processing » Revenue Processing). If you do not update the prior year tables, revenue calculations for the new year may be incorrect. You may also want to check projects that have Fixed Amount Year to Date revenue formulas before running the Compute Revenue program for the first period of a new fiscal year. The program will recognize the amount in the YTD Revenue field of the Basic Revenue Info screen (Projects » Project Setup » Revenue Setup), and this may result in overstated revenue.
Use this group box to select which periods to include in the revenue calculation.
Use this drop-down list to select any open fiscal year. This is a required field.
Use this drop-down list to select any open accounting period. This is a required field.
Use this drop-down list to select an open accounting subperiod. You can compute revenue only one subperiod at time. You can select any open subperiod; however, you must run the Compute Burden Cost screen (Projects » Cost and Revenue Processing » Project Cost Processing) for the subperiod selected. This is a required field.
Use this group box to identify which projects should be included in the Compute Revenue process. You should compute revenue for all projects at least once during the period close process.
Use this drop-down list to select the range of projects to include. Valid options are:
All
One
Range
From Beginning
To End
Use the drop-down list to select the starting project number.
Use the drop-down list to select the ending project number.
Use this group box if you would like to limit which revenue formulas are included in the calculation.
Use this drop-down list to select the range of revenue formulas to include. Valid options are:
All
One
Range
From Beginning
To End
From
Enter, or use to select, the beginning revenue formula
for the range to compute. Twenty-six revenue formulas are available via
. This field is available only if you selected One,
Range, or To
End as the Range
Option.
Enter, or use to select, the ending revenue formula
for the range to compute. Twenty-six revenue formulas are available via
. This field is available only if you selected Range
or From Beginning as the Range
Option.
Use this group box to select various processing options. The Validate Only option examines the revenue setups for direct cost ceilings that are above the revenue level.
Select this option to compute revenue without setup validation. This selection is the default and is the fastest if there are no direct cost ceilings above the revenue level. Therefore, you should select the Validate Only option and run this process after completing the initial setup. Ceilings above the revenue level are ignored with the exception of zero ceilings because zero ceilings work more like overrides. The Compute Revenue program will ignore any other ceilings above the revenue level.
Select this option to validate the revenue setup. If you select this option, all project setups that have a direct cost ceiling above the revenue level will be printed on the error report. This is the only validation that is performed. To speed up the process, change the RBA code to B in the Maintain Cost Fee Overrides screen (Projects » Project Setup » Revenue Setup) for any ceilings above the revenue level.
Select this option to validate the revenue setup and compute revenue, if the revenue setup is correct. You should select this option if you are running Compute Revenue on the process server. The process will not be stopped to print the error report.
Click 
to compute revenue for the subperiod and range
of projects selected.
Changes to this screen update the following tables:
PROJ_SUM
PROJ_BURD_SUM
PROJ_HIERARCHY
PROJ_REV_PROJ