Skip Headers

Oracle E-Business Suite Upgrade Guide
Release 11i to 12.1.1
Part Number E16342-04
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Projects Upgrade Impact

This appendix describes the way the upgrade affects your existing Oracle Projects products, and highlights the impact of these functional changes on your day-to-day business. It is arranged by alphabetically by products in the Projects product family.

This appendix covers the following topics:

About Business Impact and Functional Changes

An Applications upgrade alters both the technical and functional aspects of your Oracle E-Business Suite system. In addition to changes to the technology stack and file system, an upgrade also initiates specific changes that affect the way your existing products work after the upgrade and the way they look and feel. These functional changes have an impact on the way you use the products as you conduct your daily business.

Note: This appendix describes some of the ways the upgrade changes your existing products. We assume that you have read about the new features and products delivered in this release, which is included in the product-specific Release Content Documents (RCDs) and TOI on My Oracle Support.

The discussions of the functional aspects of the upgrade in this chapter are arranged by products within the Projects product family.

Projects

Your Projects applications specialists should be completely familiar with the information in this section and should have made appropriate plans to accommodate the associated changes before you begin your upgrade.

Daily Business Intelligence for Projects

Oracle Daily Business Intelligence for Projects provides reporting in secondary global currencies, support for contingent workers, additional drill-down capabilities to transaction pages and improved summarization programs. The changes enable users to drill down directly into project details in Oracle Project Management. Contingent worker support allows companies to perform useful utilization analysis for both employees and contingent workers. Support for additional global currency enables multi-national corporations to view their project intelligence reports in another global currency.

Note: See Oracle Applications System Administration Guide for more information.

Summarization for Concurrent Programs

The functionality achieved through the PRC: Update Project Intelligence Data concurrent process has been split between two concurrent processes so that it fits into the request scheduling time slots. Incremental updates of the base summary tables are performed by PRC: Update Project and Resource Base Summaries, where as the incremental update of project intelligence reports data is performed by PRC: Update Project Intelligence Data.

To ease the implementation for customers using the reporting capabilities of Oracle Project Management, as well as Oracle Daily Business Intelligence for Projects, both applications now share common concurrent programs:

You can now use the new and modified programs with the Request Set Generator making scheduling easier. Instead of submitting individual programs, Oracle Projects strongly recommends you use request sets generated by the Request Set Generator.

Grants Accounting

This section outlines changes made to Oracle Grants Accounting.

Note: See Oracle Grants Accounting User Guide, Oracle Project Costing User Guide, Oracle Projects Implementation Guide, Oracle Projects Fundamentals, and Oracle Subledger Accounting Implementation Guide for more information on the changes discussed in this section.

Supplier Cost Integration

Supplier cost integration now uses new functionality introduced by Oracle Payables and Oracle Subledger Accounting. The following changes may impact your implementation.

Supplier Cost Adjustments

Supplier cost adjustment uses new functionality introduced by Oracle Payables and Oracle Subledger Accounting. The following changes may impact your implementation.

Integration with Subledger Accounting

In Release 11i, Oracle Grants Accounting accounted cost and revenue through a set of interface processes. In this release, Oracle Subledger Accounting provides a common accounting engine that replaces the existing accounting processes in the different subledgers and allows you to determine the accounts, lines, descriptions, summarization, and dates of journal entries. Oracle Grants Accounting supports the integration with Oracle Subledger Accounting.

You can also add detailed transaction information to journal headers and lines. Detailed subledger accounting journals are available for analytics, auditing, and reporting. They are summarized, transferred, imported, and posted to Oracle General Ledger.

Account Generation Rules

During the upgrade, Oracle Grants Accounting creates default accounting definitions that allow the system to continue using existing AutoAccounting rules without additional setup steps. You may choose to create your own accounting definitions using Accounting Methods Builder.

Cost Processing Flows

As part of the Oracle Subledger Accounting integration, existing interface cost processes and tieback processes have been replaced with new processes that raise Oracle Subledger Accounting events, generate accounting entries, and interface them to Oracle General Ledger.

View Accounting Details

With the integration to Oracle Subledger Accounting, you now have the option to define account derivation rules within Oracle Subledger Accounting that will replace the default accounts generated by the Oracle Projects AutoAccounting feature. This changes how you can view accounting information of transaction lines. You can view the default accounting created for specific transaction lines from the details window on Expenditure Inquiry. However, to view the actual accounting that was interfaced to Oracle General Ledger, you must either use the View Accounting option from the Tools menu on Expenditure Inquiry or by using the inquiry pages provided by Oracle Subledger Accounting.

Tax Default Hierarchy Setup

Oracle Grants Accounting is integrated with Oracle E-Business Tax. This module provides the ability to define tax setup centrally. The Projects Tax Default Hierarchy used by Oracle Grants Accounting is migrated to centralized tax setup to ensure a consistent user experience across applications.

Note: See Oracle E-Business Tax Implementation Guide and Oracle E-Business Tax User Guide. See also the section on E-Business Tax in Appendix A for information about the Projects Tax Hierarchy migration.

Project Billing

This section outlines changes made to Oracle Project Billing.

Accounting for Revenue

In Release 11i, you generated revenue and accounted for it using this set of interface programs:

After the upgrade, the revenue generation process is unchanged. However, new concurrent programs replace the existing ones as part of the integration with Oracle Subledger Accounting. You run the following programs instead of the Interface Revenue to General Ledger process:

The Tieback Revenue to General Ledger process is now obsolete.

Note: See Oracle Project Billing User Guide and Oracle Projects Fundamentals for more information.

Accounting for Intercompany Invoices

In this release, the Generate Intercompany Invoices process continues to use AutoAccounting to generate the Revenue account, and the Interface Invoices to Receivables process to generate the Receivables. The Interface Cross Charge Distributions to General Ledger process, which creates accounting events for cross charge transactions, is renamed as Generate Cross Charge Accounting Events.

Additionally, when cost reclassification is enabled, you must run the Tieback Invoices from Receivables process followed by Generate Cross Charge Accounting Events process. The tieback process creates the account events necessary to create provider cost reclassification journal entries. Subsequent submission of the Create Accounting process will create accounting entries for provider cost reclassification.

Note: See Oracle Project Billing User Guide for more information.

View Accounting Details

With the integration with Oracle Subledger Accounting, you can define account derivation rules within Oracle Subledger Accounting to replace the default accounts generated by Auto Accounting in Oracle Project Billing. To view the actual accounting that was interfaced to Oracle General Ledger, you must either use the View Accounting option from the Tools menu on Revenue Review, or use the inquiry pages provided by Oracle Subledger Accounting.

Note: See Oracle Project Billing User Guide for more information.

MRC Migration Impact

In Release 11i, all MRC columns could be defined as part of custom folders. As a result of the migration of MRC to the Oracle Subledger Accounting model, Oracle Projects has eliminated all MRC-related reporting columns from inquiry windows such as Events, Revenue Review, Invoice Review, and Funding Inquiry.

Tax Default Hierarchy Setup

In this release, Oracle Projects is integrated Oracle E-Business Tax, which provides you with the ability to define tax setup centrally. The Projects Tax Default Hierarchy is migrated to a centralized tax setup to ensure consistent user experience across applications.

Note: See Oracle E-Business Tax Implementation Guide and Oracle E-Business Tax User Guide for more information. See also E-Business Tax in Appendix A for details about Projects Tax Hierarchy Migration.

Project Costing

This section describes the changes made to Oracle Project Costing.

Supplier Cost Integration

Supplier cost integration functionality in Oracle Project Costing has been modified to use new functionality introduced in this release by Oracle Payables and Oracle Subledger Accounting. The following describes changes that may impact your implementation.

Note: See Oracle Project Costing User Guide for more information on these new features. See also Oracle Projects Implementation Guide and Oracle Projects Fundamentals.

Supplier Cost Adjustments

Supplier cost adjustment features now use new Oracle Payables and Oracle Subledger Accounting functionality. The following changes may impact your implementation.

Integration with Subledger Accounting

In this release, Oracle Subledger Accounting provides a common accounting engine that replaces the existing accounting processes in the different subledgers and allows you to determine the accounts, lines, descriptions, summarization, and dates of journal entries. You can also add detailed transaction information to journal headers and lines. Detailed subledger accounting journals are available for analytics, auditing, and reporting. They are summarized, transferred, imported and posted to Oracle General Ledger. Oracle Project Costing supports the integration with Oracle Subledger Accounting.

Account Generation Rules

During the upgrade, Oracle Project Costing provides Oracle Subledger Accounting with default definitions that allow the system to continue utilizing existing AutoAccounting rules without additional setup steps. You may choose to create your own accounting rules in Oracle Subledger Accounting in order to take advantage of additional flexibility provided by the application.

Cost Processing Flows

As part of the Oracle Subledger Accounting integration, existing interface cost processes and tieback processes have been replaced with new processes that raise Oracle Subledger Accounting events, generate accounting entries, and interface them to Oracle General Ledger.

View Accounting Details

With the integration to Oracle Subledger Accounting, you now have the option to define account derivation rules within Oracle Subledger Accounting that will replace the default accounts generated by Oracle Projects AutoAccounting. This changes how you can view accounting information of transaction lines. You can view the default accounting created for specific transaction lines from the details window on Expenditure Inquiry. However, to view the actual accounting that was interfaced to Oracle General Ledger, you must either use the View Accounting option from the Tools menu on Expenditure Inquiry or by using the inquiry pages provided by Oracle Subledger Accounting.

Migration of Multiple Reporting Currencies (MRC)

Oracle Project Costing multiple reporting currency functionality has migrated to reporting currency functionality in Oracle Subledger Accounting. Oracle Subledger Accounting provides a single repository where you can view amounts in reporting currencies. As a result, Oracle Project Costing no longer needs to separately support MRC functionality. This affects MRC support for costs and capital projects in the following ways:

Reporting currency accounting journals for both cost and cross charge transactions are created in Oracle Subledger Accounting by the Create Accounting program. You do not need to run separate programs for maintaining reporting currency journals.

Project Management

This section describes the changes for Oracle Project Management.

Web-based Budgeting and Forecasting

If you are using web-based budgeting and forecasting, note the following changes:

Note: See Projects in Appendix F for more information.

Project Forecasting

The feature for forecasting based on staffing plans in Oracle Project Resource Management has been fully integrated with the enhanced Budgeting and Forecasting feature.

Work Management

Note these changes to workplan management:

Property Manager

This section describes the changes to Oracle Property Manager.

Integration with E-Business Tax

Payment and Billing terms now contain the tax-related information through the Tax Classification Code instead of the Tax Code/Tax Group values as in previous releases. Tax information is consolidated using the E-Business Tax application.

The new rule-based tax engine is designed to fully replace and substantially enhance the existing tax code-based tax calculation. Tax calculation is accomplished using the Global Tax Engine and tax codes and the defaulting hierarchy approach are migrated and supported in E-Business Tax.

Integration with Subledger Accounting

This release introduces Oracle Subledger Accounting for managing accounting across subledger transactions. During the upgrade, accounting options and their settings, and the existing accounting entries in the Oracle Property Manager data model, are moved to the new accounting data model to ensure a continuous business operation between the two releases. All accounting lines related to the transactions are also migrated. Oracle Property Manager has been enhanced to fully support Oracle Subledger Accounting.

Legal Entity in Oracle Property Manager

In order to consolidate legal-entity data into a central repository, Oracle Property Manager has incorporated Legal Entity stamping on its Payment and Billing terms. The legal entity can now be associated with the ledger when it is set up.

In an accounting setup that contains only one legal entity, a ledger represents the legal entity. The operating unit does not have a direct relationship to the legal entity, but will have a direct relationship to a ledger. Because the operating unit cannot always determine a unique legal entity, both the legal entity and the business entity are now explicitly defined on the transactions.

Projects Foundation

This section describes the changes to Oracle Projects Foundation.

Project List and Alternate Project Search Page

In Release 11i, both the Project List and Alternate Project Search pages displayed financial amounts from Project Status Inquiry. In this release, these pages display financial amounts only from project performance reporting.

New Resource Model

In Release 11i, resource lists, which could be of one or two levels, were used for budgeting and reporting. In this release, there are separate structures for budgeting and reporting:

A planning resource list consists of planning resources that are based on planning resource formats. A resource breakdown structure is a multi-level hierarchy of resources that is used for reporting the planned and actual amounts on a project.

The upgrade automatically converts all resource lists used in self-service budgets to planning resource lists and creates resource breakdown structures. The result is that self-service budgeting is now performed based on the planning resource list. The new resource breakdown structures have no impact on existing functionality. They are used only by project performance reporting.

Note: See Oracle Projects Fundamentals for more information. See also Oracle Project Management User Guide.