This process summarizes the burden costs and creates the expenditure items for the burden transactions. The burden transactions are created on different projects depending on the method you use to store burden costs.
If you store burden costs as separate, summarized burden transactions, the burden transactions are created on the same project that incurred the costs. If you choose to store burden costs as a value along with raw cost on the expenditure item on the project that incurred the transactions, the burden transactions are created on the collection project and task used for collecting burden transactions intended for accounting by burden cost components only.
The burden transactions created by this process can be billable or non-billable, depending on the Transaction Control logic you have entered. See: Controlling Expenditures.
The process also computes the costs and determines the default GL account to which to post the cost for the burden transactions that it creates.
When you use budgetary controls, this process performs funds validation for burden costs. The burden multipliers can change between when you approve a commitment transaction, and when you generate burden cost distribution lines in Oracle Projects. This process validates whether the cost changes are within the budgeted amount. If top-down budget integration is defined for a project, then you run the process PRC: Generate Cost Accounting Events to generate encumbrance accounting events to reverse existing encumbrances and to create new encumbrances that result from changes in burden rate multipliers. See: Using Top-Down Budget Integration.
Note: If you define your own detailed accounting rules in Oracle Subledger Accounting, then Oracle Subledger Accounting overwrites default accounts, or individual segments of accounts, that Oracle Projects derives using AutoAccounting.
You submit the PRC: Create and Distribute Burden Transactions process from the Submit Request window. To submit the process for multiple projects, use PRC: Create and Distribute Burden Transactions for a Range of Projects. See: Submitting Requests.
You can submit the process as part of a streamline process. For information about streamline processes, see: Submitting Streamline Processes.
From Project Number / To Project Number. Enter the range of project numbers that you want to include. You can leave either or both parameters blank. See: Entering a Project Number Range Parameter.
Project Number. (For PRC: Create and Distribute Burden Transactions only). Enter the number of the project for which you want to run the process.
Through Date. The process only selects those expenditure items dated on or before the date that you enter here.
Use the rescheduling parameters to configure a process to run automatically, according to a defined schedule. You can specify rescheduling parameters when you submit the process from the Submit Request window.
The following reports show you the results of this process:
The Distribute Burden Transactions Report. Lists all items that were successfully cost distributed. For each item, this report displays the resource and expenditure type that was used, the date on which the resource was used, the project and task to which the item is charged, the quantity of the usage utilized (measured by the units of the expenditure type), the cost rate of the resource, and total cost.
The Distribute Burden Transactions Exception Report. Lists all items that could not be processed by the Create and Distribute Burden Transactions process. This report lists the rejection reason for each of the items that fails cost distribution.
Note: You can also review rejection reasons from the Expenditure Items window by using the Show Field option in the Folder menu to display Cost Distr. Rejection. See: Viewing Expenditure Items, .