Previous  Next          Contents  Index  Navigation  Glossary  Library

Implementation Steps To Repeat for Each Operating Unit

The following implementation steps must be performed for each operating unit.

See Also

Oracle Projects Implementation Checklist

1. Define implementation options

Each operating unit has its own implementation options. Oracle Projects implementation options determine how data is interfaced with other Oracle Applications and control cross-charging capability across operating units. In a multi-organization environment, expenditures can be charged to a project in a different operating unit from the expenditure operating unit, as long as the two operating units are associated with the same:

   Automatic Project Numbering

If you use automatic project numbering, note that project numbers (including project template numbers) are unique across operating units. If a value is entered for next project number, the same number will be shown for all operating units that also use the automatic project numbering method.

   Automatic Invoice Numbering

Unlike project numbers, invoice numbers are unique within an operating unit, not across operating units. If automatic invoice numbering method is selected, the next invoice number is operating unit-specific.

See also: Implementation Options

2. Define PA periods

Starting in Release 10.7, you define your PA Periods in the calendar associated with your GL set of books. When the PA Period Type is defined for the operating unit, the system will copy accounting periods from the calendar of the GL set of books. For more information on how to define Period Type and Accounting Periods, see Define Period Types and Adding Periods to a Calendar, Oracle General Ledger User's Guide.

Each operating unit maintains its own PA period status. You use the Maintain PA Periods Status window to maintain the period status and the current reporting period. Additional PA Periods can be copied from the calendar by choosing the Copy from GL button. Once a transaction is posted to a PA period from any of the operating units, the Calendar window will not allow changes to the period date range.

Note: You must open and save a period before you can define it as the current reporting period.

See Also: PA Periods

3. Define cost rates for expenditure types

Expenditure types are set up once and are shared across all operating units. However, the cost rates for expenditure types are specific to each operating unit. Each operating unit must have cost rates set up for expenditure types in which expenditures are expected to be incurred.

See also: Expenditure Type Cost Rates

4. Define usage cost rate overrides

Non-Labor resources are set up once and are shared across all operating units. For each of the non-labor resources that an operating unit may put in service, you must set up a cost rate for the associated expenditure type. If you wish to have a non-labor resource with different cost rates in different operating units, you can define operating unit-specific usage cost rate overrides for organizations in the business group associated with an operating unit.

See also: Usage Cost Rate Overrides

5. Define employee cost rates

Employees are associated with a business group. An employee's work can be charged to any of the operating units that are associated with the employee's business group. If your business process allows an employee to work in a subset of these operating units, you must set up labor rates for each of the operating units in which the employee works. The system allows you to have different labor rates for the same employee in different operating units.

See also: Employee Cost Rates

6. Define bill rate schedules

Bill rate schedules work similarly to cost rates. Each operating unit must have its own bill rates. You can have different bill rates for the same resource in different operating units.

See also: Bill Rate Schedules

7. Define project types

You must set up project types for each operating unit. It is possible to have the same project type names in multiple operating units. However, each project type has it own attributes to control project processing by operating unit.

See also: Project Types

8. Define project templates

Like project types and projects, project templates belong to only one operating unit. For each project type class, you must define at least one project template in order to define a project with that project type class. Project templates can only be maintained and copied within an operating unit. However, project template numbers are unique across operating units. A project template number cannot duplicate any project or project template number within the Oracle Projects installation.

See also: Project Templates

9. Set up AutoAccounting for costs

AutoAccounting rules for costs are set up once for each chart of accounts. However, accounting rule assignments are operating unit-specific. The multi-organization Replicate Seed Data process will replicate system-defined function transactions in each operating unit you set up. For each operating unit, you must enable cost function transactions and assign proper accounting rules for Oracle Projects to use when automatically generating your cost accounting entries.

Note: Be sure to use partitioned tables (ending in _ALL) if you use SQL statement rules for your AutoAccounting or Account Generator. Since accounting rules may depend on data elements across operating unit boundaries, using the _ALL tables will maintain your ability to use the cross-charging feature supported by Oracle Projects in a multiple organization installation.

See Also

Accounting for Labor Costs

Accounting for Expense Report Costs

Accounting for Usage Costs

Accounting for Supplier Invoice Adjustment Costs

Accounting for Burdened Costs

10. Set up AutoAccounting for revenue and billing

AutoAccounting rules for revenue and billing are set up once for each Chart of Accounts. However, accounting rule assignments are operating unit-specific. The multi-organization Replicate Seed Data process will replicate system-defined function transactions in each operating unit you set up. For each operating unit, you must enable the revenue and billing function transactions and assign proper accounting rules for Oracle Projects to use when automatically generating your revenue and billing accounting entries.

See Also

Accounting for Labor Revenue

Accounting for Expense Report Revenue

Accounting for Usage Revenue

Accounting for Supplier Invoices Revenue

Accounting for Event Revenue

Accounting for Revenue and Invoices

11. Define indirect projects for cost collection

Projects are owned by an operating unit. If you want to use Oracle Projects to track costs your operating unit incurs, including work that is not directly associated with project work, you can define as many indirect projects as you need to record indirect costs.

See also: Accounting for Indirect Costs

12. Specify profile option values

You use profile options to specify default values that affect system processes, system controls, and data entry. In a multi-organization environment, you can confine a profile option value to a specific operating unit by defining the profile options at the responsibility level. You should review the following Oracle Projects system profile options to determine if you want to define responsibility-level profile options values:

See also: Profile Options

Additional Steps Required If the Operating Unit Is Associated With a New Business Group:

The following implementation steps must be performed for each business group.

13. Define project burdening organization hierarchy

Starting in Release 10.7, Oracle Projects now uses the project burdening hierarchy defined for each business group to compile burden schedules. Each business group must have one and only one version of the organization hierarchy designated as its project burdening hierarchy.

See also: Specifying a Project Burdening Hierarchy

14. Define burden schedules

You must set up and compile burden schedules for each business group. Burden schedules are shared among operating units associated with the same business group. If organization burden multipliers are not explicitly defined in the Define Burden Schedule window, they will default from the next higher level organization in the Project Burdening Hierarchy defined for the business group.

See also: Burden Schedules

15. Define resource lists

You must set up resource lists for each business group. Resource lists are shared among operating units associated with the same business group. You can define a resource list by copying it from an existing resource list in the same business group.

See also: Resources and Resource Lists


         Previous  Next          Contents  Index  Navigation  Glossary  Library