Free 1Z0-511 Exam Dumps Preview

B: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.
D:Inventory - This expenditure type class is used for the following transactions: Project Manufacturing transactions that are interfaced from Manufacturing or Inventory to Oracle Projects.
Oracle Inventory Issues and Receipts that are interfaced from Oracle Inventory to Oracle Projects in a manufacturing or non-manufacturing installation. 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.

Note:
*If the Rate Required option for the selected expenditure type is enabled in Oracle Projects, then you must enter a quantity. When you interface the invoice distribution toOracle Projects, Oracle Projects copies the quantity and amount to the expenditure item and calculates the rate. If Rate Required option for the selected expenditure type is disabled, then the quantity of the expenditure item is set to the amount you enter in Oracle Payables.

You can use rates to calculate amounts for costing, billing, and workplan and financial planning. Oracle Projects determines rates from a combination of rate schedules and rate overrides. You can define the following four types of rate schedules in Oracle Projects: *Employee: Use this type of rate schedule to define standard hourly rates or percentage markups by employee. You can use employee rate schedules as planning schedules(B), cost rate schedules(C), and
bill rate schedules(D).
* Job: Use this type of rate schedule to define standard hourly rates by job title. When you enter a job- based rate schedule, you enter a job group to indicate which jobs are used to determine rates. You can use job schedules as planning rate schedules, cost rate schedules, and bill rate schedules.
* Resource Class : Use this type of rate schedule to define planning rates by resource class, or as a combination of resource class and organization. *Nonlabor: Use this type of rate schedule to define rates

or percentage markups by nonlabor expenditure type or a combination of nonlabor expenditure type and nonlabor resource. You can use nonlabor rate schedules as planning rate schedules, cost rate schedules, and bill rate schedules.

Note:
*You define project classifications to group your projects according to categories you define. A project classification includes a class category and a class code. The category is a broad subject within which you can classify projects. The code is a specific value of the category.

*(see step 3 below)Defining class categories and class codes

To define class categories and class codes:

1. Navigate to the Class Categories and Codes window.
2. Enter a unique Class Category name and a Description.
3. Specify whether the class category is mandatory for every project you define. Enable if all projects must have a code assigned to this class category. Do not enable if this class category is optional. If you do not enable this option, you cannot use this class category in your AutoAccounting rules.
4. Specify whether you want to use the class category in your AutoAccounting rules. Suggestion: For each project, you can use only one code with one class category for use with AutoAccounting rules. If an AutoAccounting category already exists within a particular date range, assign an end date to the existing AutoAccounting category and then create a new one. 5.Specify whether you want to allow entry of only one class code with this class category for a project. Note: Defining multiple class codes for one category for a project may affect reporting by class category; defining
multiple class codes may cause your numbers to be included more than once. 6.Enter the Name, Description, and Effective Dates for each class code.
7. Save your work.

One Customer, Multiple Agreements

Use multiple agreements when you have one customer, but a requirement to create a separate invoice for each top task.

You can use this method to accrue revenue cost-to-cost or impose hard or soft revenue limits by task, as well as automatically create separate invoices by task.

To create separate invoices by task, you must use a different agreement to fund each task. If you use more than one agreement for a single task, the agreements are used according to the precedence described earlier for projects.

Implement AutoAccounting to charge appropriate expense accounts

When you implement AutoAccounting, you can charge straight time costs to a labor expense account and overtime costs to an overhead or overtime expense account. To charge straight time and overtime to different accounts, you define an AutoAccounting rule based on expenditure type, expenditure category, service type, compensation rule, or labor cost multiplier.

Note:
*Labor Cost Account Function
When you run the PRC: Distribute Labor Costs process, Oracle Projects calculates labor cost amounts based upon employee labor cost rates and compensation rules. After calculating labor costs, Oracle Projects uses the Labor Cost Account transactions to debit an expense account for raw labor costs. *You need to define at least one overtime expenditure type. You use the Expenditure Types window to define overtime expenditure types classified by the Overtime expenditure type class.

You can configure transaction controls by the following:

(A)Expenditure Category
(C)Employee
(E)Expenditure Type
Non-Labor Resource

Note:
*People resources represent named persons or any grouping of named persons(E)by attributes such as job(C), organization, or role(A), whose time (effort) capacity is consumed to complete the project work.
Example: Amy Marlin

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: 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:
*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.

*AutoAccounting Parameter: ClassCode

AutoAccounting class code on the project.
Note: Since you can define many project classification categories, the Class Code parameter always corresponds to the one classification category that you specified as the AutoAccounting classification category.