Oracle 1Z0-511 Exam Dumps

B: Provider and Receiver Controls Setup

For each provider operating unit or receiver operating unit involved in the cross charge, the Provider/Receiver Controls window Provider Controls and Receiver Controls tabs specify:

The cross charge method to use to process intercompany cross charges and to override default cross charge method for inter-operating unit cross charges.

Attributes required for the provider operating unit to process intercompany billing to each receiver operating unit. This includes the Intercompany Billing Project and Invoice Group.

Attributes required for the receiver operating unit to process intercompany billing from each provider operating unit. This includes the supplier site, expenditure type and expenditure organization.

* (C) Intercompany Billing Accounting

Companies choose the intercompany billing method largely due to legal and statutory requirements. When you use this method, Oracle Projects generates physical invoices and corresponding accounting entries at legal transfer prices between the internal seller (provider) and buyer (receiver) organizations when they cross a legal entity boundary or operating units.

* (D) Overview of Cross Charge

When projects share resources within an enterprise, it is common to see those resources shared across organization and country boundaries. Further, project managers may also divide the work into multiple projects for easier execution and management. The legal, statutory, or managerial accounting requirements of such projects often present complex operational control, billing, and accounting challenges.

Oracle Projects enables companies to meet these challenges by providing timely information for effective project management. Project managers can easily view the current total costs of the project, while customers receive bills as costs are incurred, regardless of who performs the work or where it is performed.

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.

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.

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

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.