Oracle 1Z0-511 Exam Dumps

Structure Integration Setup

If you enable both a workplan structure and a financial structure for your project or project template, you can decide whether or not they are integrated, and if so, to what degree. You do this by choosing one of the following options on the Structures setup page:

* Shared Structures: Enables you to generate a financial structure with a task hierarchy that is fully shared by the workplan structure task hierarchy. Workplan and financial structures are fully shared by default.

* Partially Shared Structures: Enables you to generate a financial structure that is partially shared by the workplan structure hierarchy.

* Non-Shared: Task-Based Mapping: Enables you to map individual workplan structure tasks to individual financial structure tasks.

* Non-Shared: No Mapping: Choose this if you do not want to integrate your project workplan and financial structures in any way.

* Integrating Projects with Inventory without Project Manufacturing

You can implement Inventory to Projects integration so that you can issue from inventory to projects without installing Project Manufacturing. To implement this integration, follow these steps:

1. Enable Project Cost Collection. In the Organization Parameters window in Oracle Inventory, enable the Project Cost Collection Enabled box. See Defining Costing Information,Oracle Inventory User's Guide.

2. Create a Project-Enabled Transaction Type.

3. Set the INV: Project Miscellaneous Transaction Expenditure Type Profile Option. In Oracle Inventory, set the value of this profile option to User Entered. With this setting, You must enter expenditure types for project miscellaneous transactions.

4. Create an Inventory Expenditure Type. In Oracle Projects, create an expenditure type with the transaction type class Inventory.

* Oracle Inventory Integration

The following steps are required for Oracle Inventory integration:

1. Install and implement Oracle Inventory

2. Define project-related transaction types in Oracle Inventory

Oracle Projects Implementation Guide

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.

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.

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.