Browser version scriptSkip Headers

Oracle® Fusion Applications Project Management Implementation Guide
11g Release 5 (11.1.5)
Part Number E20384-05
Go to contents  page
Go to Feedback page

Go to previous page
Go to previous page

1 Overview

This chapter contains the following:

Project Management Offering: Overview

Define Common Applications Configuration for Project Management: Overview

Getting Started with an Implementation: Overview

Manage Application Implementation

Project Management Offering: Overview

Using the Project Management business process area, your enterprise can configure how you manage projects, including how to plan, budget, forecast, collect costs, bill customers, and report performance.

Before you begin, use the Getting Started page in the Setup and Maintenance work area to access reports for each offering, including full lists of setup tasks, descriptions of the options and features you can select when you configure the offering, and lists of business objects and enterprise applications associated with the offering.

The first implementation step is to configure the offerings in the Setup and Maintenance work area by selecting the offerings and options that you want to make available to implement. For the Project Management offering, you can select the following options and configure the feature choices:



Project Management

  • Enterprise Structures Guided Flow

  • Governance, Risk and Compliance

  • Local Installation of Help

  • Access to Internet-Based Help Features

  • Help Customization

  • Custom Help Security

  • Maintain Common Reference Objects

  • Subledger Accounting Rules

  • WebCenter Integration

  • Labor Costing Extensions

  • Project Extensions

  • Application Toolkit Component Maintenance

  • Click To Dial


Burdening Extensions

Cross-Charge Transactions


Cross-Charge Transactions: Borrowed and Lent

  • Borrowed and Lent Extensions

  • Transfer Price Extensions

Cross-Charge Transactions: Intercompany Billing

  • Intercompany Billing Extensions

  • Transfer Pricing

  • Transfer Price Extensions

Project Costing

  • Expenditure Extensions

  • Application Integrations

Project Costing: Allocations

Allocation Extensions

Project Costing: Capital Projects

  • Retirement Processing

  • Capital Asset Extensions

  • Capital Interest

  • Capital Interest Extensions

Project Billing

Billing Extensions

Project Billing: Interproject Billing


Project Billing: Estimated Tax Calculation


Project Control

Budgeting and Forecasting Extensions

Project Performance Reporting

Performance Reporting Extensions

Project Integration Gateway


Project Business Intelligence Analytics


Project Business Intelligence Analytics: Project Revenue and Billing Business Intelligence Analytics


Project Business Intelligence Analytics: Project Performance Business Intelligence Analytics


Project Business Intelligence Analytics: Project Control and Costing Business Intelligence Analytics


Next, create one or more implementation projects for the offerings and options that you want to implement first, which generates task lists for each project. The application implementation manager can customize the task list and assign and track each task.

If you select all of the options, the generated task list for this offering contains the groups of tasks listed in the following table:

Task List


Define Common Applications Configuration for Project Management

Define the configuration for common setup such as users, enterprise and HR structures, security, and common reference objects for Oracle Fusion Projects.

You can find other information that supports the common implementation tasks in the Oracle Fusion Applications Concepts Guide.

Define Common Project Configuration

Configure components from other product offerings that are used by Oracle Fusion Projects.

Define Project Foundation Configuration

Configure all foundation components for creating and maintaining projects in Oracle Fusion Projects.

Define Project Costing Configuration

Configure Oracle Fusion Project Costing to collect, monitor, and influence the costs associated with the delivery of the project.

Define Project Control Configuration

Configure Oracle Fusion Project Control to monitor project execution, progress, budgeting, and forecasting.

Define Project Billing Configuration

Configure Oracle Fusion Project Billing to invoice customers and recognize revenue for project contracts.

Define Project Performance Reporting Configuration

Configure Oracle Fusion Project Performance Reporting to collect and review project data against defined performance areas.

Define Project Integration Gateway Configuration

Configure Oracle Fusion Project Integration Gateway to integrate with third-party scheduling tools such as Primavera P6 Enterprise Project Portfolio Management.

Define Project Templates

Create and maintain project templates that have features common in the projects you want to create.

Define Transactional Business Intelligence Configuration

Define the configuration for Oracle Transactional Business Intelligence to enable business intelligence reporting with the Oracle Fusion Applications.

Define Extensions for Project Management

Define extensions such as custom Oracle Enterprise Scheduler jobs.

You can also customize and extend applications using other tools. For more information, see the Oracle Fusion Applications Extensibility Guide.

Define Common Applications Configuration for Project Management: Overview

In the Define Common Applications Configuration for Project Management activity, you perform common setup steps such as defining users, enterprise and human resource structures, security, and common reference objects for Oracle Fusion Projects.

Define Common Applications Configuration for Project Management

Setup tasks in the Define Common Applications Configuration for Project Management activity are grouped into the following task lists:

Task List


Define Synchronization of Users and Roles from LDAP

Run a process to populate the product tables containing user and role information with the users and roles held in LDAP. This process is always the first implementation task but can also run periodically to keep the product tables synchronized with subsequent updates to LDAP.

Define Implementation Users

Create implementation users and roles. Provision implementation users with job and data roles.

Define Currencies and Currency Rates

Define the currencies and currency rates that your organization does business in.

Define Enterprise Structures for Project Management

Access your enterprise organization, such as legal entities, legal jurisdictions and authorities, and business units, and specify their use in Oracle Fusion Projects. Define the accounting configuration and chart of accounts that serve as a framework for how financial records are maintained for an organization.

Define Social Networking

Review options related to social networking and update as necessary.

Define Security for Project Management

Enable users to perform functions related to their job roles.

Define Automated Governance, Risk, and Performance Controls

Define the controls that automate the analysis of data-related and address-related issues to mitigate risk and optimize performance of an organization.

Define Approval Management for Project Management

Define approval routing structures and controls to match your organization's needs.

Define Help Configuration

Define what users can see and do in a local deployment of Oracle Fusion Applications Help.

Define Application Toolkit Configuration

Set up Oracle Fusion Application Toolkit features, which are common across Oracle Fusion applications.

Maintain Common Reference Objects

Review and manage common objects, for example profiles and lookups, that affect the functionality and look of applications.

Define WebLogic Communication Services Configuration

Configure WebLogic Communication Services, security, and gateways for third-party call control, session initiation protocol telephony, or soft switch serving the users within that domain, and automated dialing.

Getting Started with an Implementation: Overview

To start an Oracle Fusion Applications implementation, you must setup one or more initial users using the super user that was created during installation and provisioning of the Oracle Fusion Applications environment. Because Oracle Fusion Applications is secure as delivered, the process of enabling the necessary setup access for initial users requires several specialized steps when getting started with an implementation.

The following high level steps are required for starting an implementation.

  1. As the Oracle Identity Management Administration user, provision the IT Security Manager job role with roles for user and role management.

    This step enables the super user account, which is provisioned with the IT Security Manager job role, to create implementation users.

  2. As the Oracle Fusion Applications installation super user, perform the following tasks once you have selected an offering to implement and generated the setup tasks needed to implement the offering.

    1. Synchronize users and roles in the Lightweight Directory Access Protocol (LDAP) store with HCM user management by using the Run User and Roles Synchronization Process task.

    2. Create an IT security manager user by using the Create Implementation Users task.

    3. Provision the IT security manager with the IT Security Manager role by using the Provision Roles to Implementation Users task.

  3. As the newly created IT security manager user, sign in to Oracle Fusion Applications and set up at least one implementation user for setting up enterprise structures.

    1. Create an implementation user by using the Create Implementation Users task.

    2. Provision the implementation user with the Application Implementation Manager job role or the Application Implementation Consultant job role by using the Provision Roles to Implementation Users task. The Application Implementation Consultant job role inherits from all product-specific application administrators and entitles the necessary View All access to all secured object.

    3. Optionally, create a data role for an implementation user who needs only the limited access of a product-specific Application Administrator by using the Create Data Role for Implementation Users. Then assign the resulting data role to the implementation user by using the Provision Roles to Implementation Users task.

The figure shows the task flow from provisioning the IT Security Manager job role with the user and role management entitlement to creating and provisioning implementation users for enterprise setup.

Three swim lanes for the OIM Administrator
user, the installation super user, and the IT Security Manager or
Security Administrator user, if available, show the tasks each type
of user performs to create and provision one or more implementation
users for setting up enterprise structures.

Manage Application Implementation

Manage Application Implementation: Overview

The Manage Applications Implementation business process enables rapid and efficient planning, configuration, implementation, deployment, and ongoing maintenance of Oracle Fusion applications through self-service administration.

The Setup and Maintenance work area offers you the following benefits:

With Oracle Fusion Functional Setup Manager you can:

There are several documentation resources available for learning how to configure Oracle Fusion Applications.

Implementation Projects: Explained

An implementation project is the list of setup tasks you need to complete to implement selected offerings and options. You create a project by selecting the offerings and options you want to implement together. You manage the project as a unit throughout the implementation lifecycle. You can assign these tasks to users and track their completion using the included project management tools.

Maintaining Setup Data

You can also create an implementation project to maintain the setup of specific business processes and activities. In this case, you select specific setup task lists and tasks

Exporting and Importing

Implementation projects are also the foundation for setup export and import. You use them to identify which business objects, and consequently setup data, you will export or import and in which order.

Selecting Offerings

When creating an implementation project you see the list of offerings and options that are configured for implementation. Implementation managers specify which of those offerings and options to include in an implementation project. There are no hard and fast rules for how many offerings you should include in one implementation project. The implementation manager should decide based on how they plan to manage their implementations. For example, if you will implement and deploy different offerings at different times, then having separate implementation projects will make it easier to manage the implementation life cycles. Furthermore, the more offerings you included in an implementation project, the bigger the generated task list will be. This is because the implementation task list includes all setup tasks needed to implement all included offerings. Alternatively, segmenting into multiple implementation projects makes the process easier to manage.

Offerings: Explained

Offerings are application solution sets representing one or more business processes and activities that you typically provision and implement as a unit. They are, therefore, the primary drivers of functional setup of Oracle Fusion applications. Some of the examples of offerings are Financials, Procurement, Sales, Marketing, Order Orchestration, and Workforce Deployment. An offering may have one or more options or feature choices.

Implementation Task Lists

The configuration of the offerings will determine how the list of setup tasks is generated during the implementation phase. Only the setup tasks needed to implement the selected offerings, options and features will be included in the task list, giving you a targeted, clutter-free task list necessary to meet your implementation requirements.

Enabling Offerings

Offerings and their options are presented in an expandable and collapsible hierarchy to facilitate progressive decision making when specifying whether or not an enterprise plans to implement them. An offering or its options can either be selected or not be selected for implementation. Implementation managers decide which offerings to enable.

Provisioning Offerings

The Provisioned column on the Configure Offerings page shows whether or not an offering is provisioned. While you are not prevented from configuring offerings that have not been provisioned, ultimately the users are not able to perform the tasks needed to enter setup data for those offerings until appropriate enterprise applications (Java EE applications) are provisioned and their location (end point URLs) is registered.

Options: Explained

Each offering in general includes a set of standard functionality and a set of optional modules, which are called options. For example, in addition to standard Opportunity Management, the Sales offering includes optional functionality such as Sales Catalog, Sales Forecasting, Sales Prediction Engine, and Outlook Integration. These optional functions may not be relevant to all application implementations. Because these are subprocesses within an offering, you do not always implement options that are not core to the standard transactions of the offering.

Feature Choices: Explained

Offerings include optional or alternative business rules or processes called feature choices. You make feature selections according to your business requirements to get the best fit with the offering. If the selected offerings and options have dependent features then those features are applicable when you implement the corresponding offering or option. In general, the features are set with a default configuration based on their typical usage in most implementations. However, you should always review the available feature choices for their selected offerings and options and configure them as appropriate for the implementation.

You can configure feature choices in three different ways:

Yes or No

If a feature can either be applicable or not be applicable to an implementation, a single checkbox is presented for selection. Check or uncheck to specify yes or no respectively.

Single Select

If a feature has multiple choices but only one can be applicable to an implementation, multiple choices are presented as radio buttons. You can turn on only one of those choices.


If the feature has multiple choices but one or more can be applicable to an implementation then all choices are presented with a checkbox. Select all that apply by checking the appropriate choices.