Free 1Z0-511 Practice Test Questions and Answers (2026) | Cert Empire Practice Questions

Oracle Projects uses the following expenditure type classes to process non-labor project costs:

* Usages - Asset usage costs are interfaced to Oracle General Ledger.

* Supplier Invoices - Oracle Payables supplier invoices are interfaced from Oracle Payables to Oracle

Projects.

* Miscellaneous Transaction - Miscellaneous Transactions are used to track miscellaneous project

costs. This expenditure type class is similar to usages. The difference is that, for miscellaneous

transactions expenditure items, you are not required to specify a non-labor resource or a non-labor

resource organization, as you are for usage expenditure items. Miscellaneous transactions may be

used for the following costs:

Fixed assets depreciation

Allocations

Interest charges

* Burden Transaction - Burden transactions track burden costs that are calculated in an external

system or calculated as separate, summarized transactions. These costs are created as a separate

expenditure item that has a burdened cost amount, but has a quantity and raw cost value of zero.

Burden transactions are interfaced to Oracle General Ledger. As with any other transaction in Oracle

Projects, you can adjust and capitalize burden transactions, or accrue revenue or generate invoices

for these transactions.

* Work In Process - This expenditure type class is used for Project Manufacturing WIP transactions

that are interfaced from Manufacturing to Oracle Projects. You can also use this expenditure type

class when you import other manufacturing costs via Transaction Import or when you enter

transactions via pre-approved batch entry.

Reference: Expenditure Type Classes

PA: Cross Project User - Update: Enables users to update all project information. This applies only to

the operating units the responsibility has access to through the MO: Operating Unit profile option or

the MO: Security Profile profile option.

Note: Users whose responsibilities are associated with a cross business group access security profile

can view and update project and resource information across all business groups in your enterprise.

Reference: Oracle Projects Fundamentals, Responsibility-Based Security

C: Consolidated Invoicing allows you to consolidate multiple project invoices into one single invoice.

Reference: Project Billing Made Easy Using Invoice Consolidation

You can automatically create and baseline an Approved Revenue Budget for a project by checking the

Baseline Funding without Budget check box in the Project Funding Inquiry window.

Note: Budget/Fund/Bill at Project or Top Task Level

You can create a revenue budget, funding source allocation and project agreement, and perform

billing at either the project or the top task level. After you have created an allocation line at either

level, you cannot change to another level. For example, if you have created a funding allocation for a

top task, you cannot create another funding allocation for the same project without entering a top

task.

Reference: Oracle Project Contracts Implementation Guide

Note:

* You can set this at the Inventory Organization level in the Project Manufacturing Parameters

window, the Costing tabbed region. This allows WIP employee resources and Project straight time

hours to be summarized as Straight Time Expenditure Type Class.

* expenditure type class

An additional classification for expenditure types that indicates how Oracle Projects processes the

expenditure types. For example, if you run the Distribute Labor Costs process, Oracle Projects will

calculate the cost of all expenditure items assigned to the Straight Time expenditure type class.

Formerly known as system linkage

Storing Burden Costs as a Separate Expenditure Item on the Same Project

You can choose to hold the burden cost components as a separate expenditure item on the same

project. 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.

Reference: Oracle Project Costing User Guide

The following activities take place as part of the expenditures process flow for labor costs:

1. Run the process PRC: Distribute Labor Costs. This process calculates the raw and burden cost

components for labor cost expenditure items. It also uses AutoAccounting to determine the default

debit account for each expenditure item.

2. Run the process PRC: Generate Cost Accounting Events. This process uses AutoAccounting to

determine the default credit account for each expenditure item. It also generates accounting events

for distributed transactions. You can optionally select Labor Cost as the process category to limit the

process to labor costs.

3. Run the process PRC: Create Accounting. This process creates subledger journal entries for eligible

accounting events. You can run the process in either draft or final mode. You can optionally select

Labor Cost as the process category to limit the process to labor cost accounting events. Optionally,

the process can post journal entries in Oracle General Ledger.

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.

4. Run the process PRC: Transfer Journal Entries to GL. When you run the process PRC: Create

Accounting, if you select No for the parameter Transfer to GL, then you run the process PRC: Transfer

Journal Entries to GL to transfer the final subledger journal entries from Oracle Subledger Accounting

to Oracle General Ledger. You can optionally select Labor Cost as the process category to limit the

process to labor cost accounting events. Optionally, the process can post journal entries in Oracle

General Ledger.

5. Run Journal Import in Oracle General Ledger. (optional) This process brings the final accounting

entries from Oracle Subledger Accounting into Oracle General Ledger.

Reference: Oracle Projects Fundamentals, Expenditures Process Flow Example: Labor Cost

Expenditure Item Validation

When you enter expenditure items, you are charging cost to a project and a task. Oracle Projects

validates expenditure items against predefined criteria and any transaction controls and transaction

control client extensions that you set up during the implementation.

Reference: Oracle Project Costing User Guide

A: If the revenue amounts are already interfaced to General Ledger (GL) through a different interface,

then uncheck the ‘Interface Revenue to GL’ option in the implementation options and run the

‘Interface Revenue to GL’ process in Oracle projects. This will turn the flags in the revenue records as

accepted in GL, though it is not interfaced. Once this is done, revert back the implementation option

back to its original state.

Note:

Revenue and Billing Information

When you enter revenue information for your project, you specify a revenue distribution rule for the

revenue accrual method and the billing method for this project. When you enter billing information,

you specify invoice formats, bill cycle days, and other invoicing information.

The project type determines which revenue distribution rule appears as the default value for this

field, and which other revenue distribution rules you can choose from. Oracle Projects predefines the

following revenue distribution rules:

Cost/Cost

Accrue revenue and bill using the ratio of actual cost to budgeted cost (percent

spent).

Cost/Event

Accrue revenue using the ratio of actual cost to budgeted cost (percent spent), and

bill based on events.

Cost/Work

Accrue revenue using the ratio of actual cost to budgeted cost (percent spent), and

bill as work occurs.

Event/Event

Accrue revenue and bill based on events.

Event/Work

Accrue revenue based on events, and bill as work occurs.

Work/Event

Accrue revenue as work occurs, and bill based on events.

Work/Work

Accrue revenue and bill as work occurs.

Note:

* Allow Revenue Budget Entry. Indicates if you allow entry of revenue budget types. You may choose

to not allow entry of revenue budgets for indirect or capital projects. You must enter a revenue

budget for a contract project before it can accrue revenue and be billed.

Incorrect:

Not A: Task types assign default attributes to tasks and control how Oracle Projects processes tasks.

Task types specify basic task attributes.

Not C: Work types represent a classification of work. You use work types to classify both actual and

scheduled work.

Not E: Oracle Projects uses start and finish dates to control processing, indicate estimated and

scheduled duration, and serve as tools to evaluate project performance.

The start and finish dates at the project level are:

Actual: Actual dates when work on the project started and finished. You can use these dates to drive

future timecard and earned value functionality.

(not E) Scheduled: Scheduled start and finish dates for the project.

Target: The expected lifespan of the project.

Estimated: A task manager's estimate of when work on the project will be started and finished.

Baseline: The baselined schedule

Invoice

When you run the program to interface invoices to Oracle Receivables, Oracle Projects runs

AutoAccounting to determine the appropriate default accounts. If the invoice fails AutoAccounting,

then the program marks the draft invoice with an error. See: Overview of AutoAccounting, Oracle

Projects Implementation Guide.

The following table shows entries Oracle Projects creates when the Interface Invoices to Oracle

Receivables process is run:

Account

Debit

Credit

Receivables

200.00

Unbilled Receivables and/or Unearned Revenue

200.00

Reference:

Oracle Project Billing User Guide