Your customer has set up a contract project with a distribution rule Work/Work. Identify three setup options to:
1. Charge labor transactions revenue and all other nonlabor transactions revenue to separate accounts
2. Generate separate invoice line amounts for labor and nonlabor transactions
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.
Identify two predefined transaction sources that Oracle Projects uses to import the transactions generated within Oracle Projects.
Oracle Projects uses predefined transaction sources to import project allocations and capitalized interest transactions that it generates internally.
Refer to the exhibit.
In your company's Expenditure/Event Organization Hierarchy, organization labor costing rules are assigned to all organizations except San Jose. What happens when you run the "PRC: Distribute labor costs" program for a timecard transaction entered by an employee from the San Jose organization?
Which two options are not task attributes for financial task structure?
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
A new contract project is created for work for a customer by using event-based billing. A decision has been made to give a discount to the customer on a particular invoice. You want to apply this discount and reduce the invoice without affecting revenue. Which event type should be used to achieve this?
Event Type Classification is: Scheduled Payment, Deferred Revenue, Invoice Reduction, Manual, or Automatic (for billing events only)
