Previous  Next          Contents  Index  Navigation  Glossary  Library

Accounting for Burden Cost as Separate, Summarized Expenditure Items

You can choose to hold the burden cost components as separate expenditure items. The expenditure items storing the burden cost components are identified with a different expenditure type that is classified by the expenditure type class Burden Transaction.

Table 1 - 46 illustrates burden cost as a separate, summarized expenditure item on the same project.


Note: The expenditure items that incur the raw cost have a burdened cost equal to the raw cost, because the burden cost of those transactions are included in the burden transactions. The burden transactions have a raw cost of zero and a summarized burden cost from the incurred raw costs.

Oracle Projects creates the burden transactions by summarizing the burden cost components by project, lowest task, expenditure organization, PA period, and burden cost code. If you use this method of storing burden costs, you must assign an expenditure type to each burden cost code. You may also want to define an expenditure type for each burden cost code to use for reporting and budgeting purposes. The Create and Distribute Summarized Burden Component Items process summarizes the burden costs for all costed, burdened items. If you are processing new items for a task that already has burden transactions, Oracle Projects will create new burden transactions. The existing burden transactions are not updated. Each new transaction will be assigned the system date when the process is run.

See also: Create and Distribute Summarized Burden Component Items.


         Previous  Next          Contents  Index  Navigation  Glossary  Library