Download Oracle E-Business Suite R12 Project Essentials.certkey.1z0-511.2019-02-26.1e.80q.vcex

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/CostAccrue revenue and bill using the ratio of actual cost to budgeted cost (percent spent). 
Cost/EventAccrue revenue using the ratio of actual cost to budgeted cost (percent spent), and bill based on events. 
Cost/WorkAccrue revenue using the ratio of actual cost to budgeted cost (percent spent), and bill as work occurs. 
Event/EventAccrue revenue and bill based on events. 
Event/WorkAccrue revenue based on events, and bill as work occurs. 
Work/EventAccrue revenue as work occurs, and bill based on events. 
Work/WorkAccrue revenue and bill as work occurs.

Oracle Projects uses predefined transaction sources to import project allocations and capitalized interest transactions that it generates internally. 

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

Event Type Classification is: Scheduled Payment, Deferred Revenue, Invoice Reduction, Manual, or Automatic (for billing events only)

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:
*Compute Forecast Labor Revenue 
This process calculates the potential revenue of labor expenditure items based on established bill rates and markups. The expenditure items that the process selects are billable labor expenditure items charged to contract projects that have not yet been processed by the Generate Draft Revenue process. The items do not have to be approved to be processed for forecast revenue.

Note:
*Oracle Projects fully integrates with Oracle Human Resources to keep track of employees and information relevant to them, such as bill rates and mailing address.

You can configure transaction controls by the following:
(A)Expenditure Category 
(C)Employee 
(E)Expenditure Type 
Non-Labor Resource

Note:
*Oracle Projects processes tasks based on their position in the structure. The three distinct positions are:
Top Task: A task whose parent is the project
Mid Task: A task that is not a top task or a lowest task
Lowest Task: A task that is at the bottom of the structure, without any child tasks
*You can configure transaction controls by the following:
Expenditure Category 
Employee 
Expenditure Type 
Non-Labor Resource