Oracle 1Z0-511 Exam Dumps

When you implement Oracle Projects, you can select the calendar used to maintain PA periods.

PA Period Type

Specify a Period Type, which is used to copy Project Accounting Periods from the calendar associated with the ledger. If you copy PA Periods from GL, Oracle Projects copies all of the periods of this Period Type to set up the PA Periods.

In a multiple organization environment, the PA Period Type is specified for each operating unit.

Note:

* Enable Budgetary Controls and Encumbrance Accounting

To use budgetary controls, you must implement budgetary control and encumbrance accounting for the ledger in Oracle General Ledger and enable encumbrance accounting in Oracle Payables or Oracle Purchasing. Encumbrance accounting automatically creates encumbrances for requisitions, purchase orders, and invoices.

* PSA: Budgetary Control Report Template

This profile option can be set at the site, application, responsibility, and user levels. You must select Budgetary Control Results Template as the value for this profile option to enable users to view funds check results from Oracle Purchasing and Oracle Payables after a funds check.

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.

C: The multi-currency billing option can be set both at the operating unit level and at the project level. To enter agreements and rate schedules in any currency for a project, you must enable the multi-currency billing functionality for the operating unit. To enter events in any currency for a project, you can enable the functionality at the project level only. This value defaults from the project template You can override the default value for an individual project template or project.

Note:

Oracle Projects gives you the option to bill in a global environment when the multi-currency billing is enabled for an operating unit and for a project. When multi-currency billing is enabled, you can:

* Enter agreements, bill rates, and events in any currency regardless of the project functional currency (B)

* Designate the project functional currency, project currency, or funding currency as the invoice processing currency for a project

* Designate the project functional currency and the invoice transaction currency as the revenue transaction currency

* Define currency conversion attributes for converting revenue and invoicing amounts to the project currency, project functional currency, and funding currency

* Define currency conversion attributes for converting funding amounts to the project functional currency, and the project currency

* Define a default invoice currency for a project customer that is different from the project functional currency and assign conversion attributes for deriving revenue in this currency

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

C: As part of a project template definition setup, you can choose which Quick Entry fields you want to define. Oracle Projects prompts you to enter information in these Quick Entry fields when you create a new project from a template. Choose Quick Entry fields for project information you want to enter (instead of accepting the template default) each time you create a project.

Order: Enter a number to indicate the sequence in which you want the Quick Entry fields to appear.

Field name: Choose the fields you want to appear in the Quick Entry window when you create a new project.

Specification: You enter a specification for the following field names:

Key Member: Select the project role type to use when creating the key member

Classification: Select the class category to use when creating the classification

Customer Name: Select the customer relationship to use when creating the project customer

Prompt: You can enter a field name that is different from the predefined field name to display when you use Quick Entry.

Required: Choose whether you want to require entry for the Quick Entry field.