Generating Revenue (Oracle Projects Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Generating Revenue

You can generate revenue for a single project, or for a range of projects using the PRC: Generate Draft Revenue process.

Note: You can also delete the revenue of a single project using the PRC: Delete Draft Revenue of a Single Project process. See: Delete Draft Revenue of a Single Project.

When you generate revenue, Oracle Projects first selects projects, tasks, and their associated events and expenditure items that are eligible for revenue generation. Oracle Projects next calculates the potential revenue and then creates revenue events and expenditure items. See: Revenue Generation Process.

Oracle Projects also calculates the bill amounts of each expenditure item, based on the revenue distribution rule associated with a particular project.

When Oracle Projects creates revenue, it also searches for available funding for each revenue item. We discuss each of these topics in detail below after we tell you how to generate revenue.

To generate revenue across a range of projects:

Submit the PRC: Generate Draft Revenue for a Range of Projects process in the Submit Request window to run multiple revenue generation processes. See: Submitting Requests.

Suggestion: You should run Generate Draft Revenue on a specified processing cycle (for example, weekly) to calculate revenue for projects across the company. You can also run the process on demand by project to process adjustments.

Use the rescheduling parameters to configure the Generate Draft Revenue process to run automatically, according to a defined schedule.

To generate revenue for a single project:

Submit the PRC: Generate Draft Revenue for a Single Project process from the Submit Request window. See: Submitting Requests.

Revenue Accrual and Invoicing

Generate Draft Revenue uses the overrides and schedules to process projects using As Work Occurs revenue accrual and/or invoicing. These projects are assigned one of the following distribution rules: WORK/WORK, WORK/EVENT, EVENT/WORK.

Burden Schedules

Generate Draft Revenue follows the burden schedule precedence for items charged to tasks that use a burden schedule; it does not use bill rate overrides for these items.

Burden Schedules and Labor Multipliers

You may decide to use labor multipliers instead of a labor burden schedule if you are using a one tier multiplier for labor items. With a one tier labor multiplier, the use of labor multipliers and burden schedule overrides for labor will result in same bill amounts but the method of processing will be different.

You can also use labor multipliers with a standard burden schedule for multiplier-tier revenue accrual and billing. This allows you to define one negotiated labor multiplier on top of the standard cost buildup provided by the standard burden schedule. The labor multiplier is treated as another burden multiplier. The calculation is:

Bill Amount = Burdened Amount X (1 + Labor Multiplier)

You can also report this labor multiplier as another burden cost component in the PA_INV_BURDEN_DETAILS_LM_V view. The labor multiplier component is not displayed in the PA_INV_BURDEN_DETAILS_V view. See: Oracle Projects Technical Reference Manual.

Bill Rate Schedules

Generate Draft Revenue follows the standard bill rate precedence for items charged to tasks that use a bill rate schedule. This precedence includes employee bill rate overrides, job bill rate overrides, non-labor bill rate overrides, job assignment overrides, and task schedules.