2Define Common Project Execution Management Options

This chapter contains the following:

In the Define Common Project Execution Options activity, you perform setup steps such as creating the project application administrator, project users, and roles, defining calendars, and creating project enterprise resources.

This table lists the tasks and task lists that the setup tasks in the Define Common Project Execution Options activity are grouped into.

Task or Task List Description

Manage Project Implementation Administrator

Create or identify a project application administrator to manage and control access to Oracle Fusion Project Management applications.

Manage Project User Provisioning

Create and update project users and assign enterprise roles, such as Project Execution and Team Collaborator, to provide access to Oracle Fusion Project Portfolio Management applications.

Manage Project Roles

Create and update roles that are used to control access to project-level information and for defining project resource requests.

Define Project and Resource Calendars

Define calendars to assign to projects and resources to establish work schedules.

Manage Project Enterprise Resources

Create and update enterprise resources to assign to projects, tasks, issues, and deliverables.

Project User Provisioning

Use the Manage Project User Provisioning page to request user accounts and assign job or abstract roles for project enterprise labor resources. This action enables resources to sign into Project Execution Management applications to plan projects, manage resources, review, track, and collaborate on work.

You can also request user accounts and assign job or abstract roles when you create or edit resources on the Manage Project Enterprise Resources page.

During implementation you can provision a set of users and assign the Project Application Administrator role so that these administrators can initiate the provisioning process for the rest of the project enterprise labor resources.

Resources to Provision

A resource that you provision typically falls into one of these categories:

  • Resource is an employee or contingent worker in Oracle Fusion HCM and is a project enterprise labor resource in Oracle Fusion Project Management.

    User accounts for these resources are typically created in Oracle Fusion HCM. You can associate the employee or contingent worker with a project enterprise labor resource and assign project-related roles when you create the resource in Oracle Fusion Project Management.

    Note: You can't create a user account in Oracle Fusion Project Management for an existing HCM employee or contingent worker. HCM persons are registered in Oracle Fusion HCM.
  • Resource is a project enterprise labor resource in Oracle Fusion Project Management, but isn't an HCM employee or contingent worker.

    You can maintain resource details and add resources to projects even if the resources aren't HCM employees or contingent workers. Create user accounts to register the resources in the identity management system, and assign project-related job or abstract roles to the resources.

  • Resource is an HCM employee or contingent worker, but isn't a project enterprise labor resource in Oracle Fusion Project Management.

    You can assign project-related job or abstract roles to resources who have user accounts that were created in Oracle Fusion HCM. However, you must create the resources in Oracle Fusion Project Management before you can assign them to projects, or before the resources can open project or resource management pages in the application.

Job or Abstract Roles

You can provision the following predefined job or abstract roles to resources:

  • Project Application Administrator: Collaborates with project application users to maintain consistent project application configuration, rules, and access.

  • Project Execution: Manages projects in Project Execution Management applications. Manages issues, deliverables, changes, and the calendar.

  • Resource Manager: Manages a group of project enterprise labor resources. Monitors the utilization of resources and manages the assignment of resources to work on projects. Collaborates with project managers to find suitable resources to fulfill project resources requests.

  • Team Collaborator: Performs, tracks, and reports progress on project and nonproject work. Collaborates with other team members or project managers to perform project tasks and to-do tasks. Manages issues, deliverables, changes, and the calendar.

  • Project Executive: Establishes key performance indicators and other project performance criteria for a business area or organization. Manages business area performance. Owns profit and loss results for an organization, service line, or region.

In addition, you can provision custom job roles for resources. For example, you can provision a Custom Team Member role that contains a different set of security permissions than the Team Member role.

Default Role Assignments

You can select project-related predefined and custom roles to provision by default. The application assigns the default roles to project enterprise labor resources that you create using any of the following methods:

  • Import Project Enterprise Resource process for Oracle Cloud

  • Project Enterprise Resource External Service

  • Import HCM Persons as Project Enterprise Resources process

  • Export Resources and Rates process that moves resources from the planning resource breakdown structure in Project Financial Management applications to Project Management

  • Maintain Project Enterprise Labor Resources process in Project Resource Management

Go to the Manage Project User Provisioning page > Default Provisioning Attributes tab > Default Role Assignments section to select the default roles. Then select the option to Automatically provision roles when mass creating project enterprise labor resources.

This topic describes project user account and role provisioning statuses in Project Execution Management applications.

Project User Account Statuses

The user account status indicates whether a project enterprise labor resource can access Project Execution Management applications based on assigned roles. The following table lists the project user account statuses.

User Account Status Description

Active

The user is active and can access the application.

A project user account is active for a resource in either of these scenarios:

  • You create a user account for the resource in Oracle Fusion Project Management.

  • The resource is an employee or contingent worker with an active account in Oracle Fusion Human Capital Management (HCM).

Inactive

The user is inactive and cannot access the application.

A project user account is inactive for a resource in either of these scenarios:

  • The resource is an employee or contingent worker who is no longer active in HCM, such as when the employee is terminated.

  • The resource isn't an employee or contingent worker and you disable the resource in the identity management system.

Role Provisioning Statuses

When you create a user account in Oracle Fusion Project Management and assign project job or abstract roles to the resource, the application sends a provisioning request to the identity management system. The role provisioning status indicates the processing status of the request. The following table lists the role provisioning statuses.

Role Provisioning Status Description

Requested

Role provisioning is requested for a resource.

Completed

Role provisioning completed without errors or warnings.

Failed

Role provisioning failed because of errors or warnings.

Partially completed

Role provisioning is partially complete.

Pending

Role provisioning is in progress.

Provisioned

The role is provisioned in the identity management system.

Rejected

The role provisioning request is rejected by the identity management system.

Suppressed

Status used in HCM for user accounts aren't created automatically.

You can view project user account and role provisioning statuses on the Manage Project User Provisioning page and Manage Project Enterprise Resources page.

Use the Manage Project User Provisioning page to create and update project users, request user accounts, and assign job or abstract roles to resources. This action enables resources to sign into Project Execution Management applications to plan projects, manage resources, and review, track, and collaborate on work.

Creating and Provisioning a User

Perform these steps to create a project user, request a user account, and provision roles on the Manage Project User Provisioning page.

  1. Navigate to the Setup and Maintenance work area and search for the Manage Project User Provisioning task.

  2. On the Search page, click the Manage Project User Provisioning link to open the Manage Project User Provisioning page > User Provisioning tab.

  3. Click the Create icon to open the Create Project User window.

  4. Enter the required fields and click the Request user account option.

    When you select the Request user account option, the roles that you specified to provision by default appear in the Role Details table for the resource.

  5. Select the Assign administrator role option to assign the Project Application Administrator role to the resource.

    This action adds the Project Application Administrator role to the Role Details table.

  6. Add predefined or custom roles to the Role Details table, as needed. The following table lists the predefined roles.

    Role Description

    Project Application Administrator

    Collaborates with project application users to maintain consistent project application configuration, rules, and access.

    Project Execution

    Manages projects in project management applications and is not assigned the project manager job role. Manages issues, deliverables, changes, and the calendar.

    Resource Manager

    Performs functions in Oracle Fusion Project Resource Management.

    Team Collaborator

    Performs, tracks, and reports progress on project and nonproject work. Manages issues, deliverables, changes, and the calendar.

    Project Executive

    Establishes key performance indicators and other project performance criteria for a business area or organization. Manages business area performance. Owns profit and loss results for an organization, service line, or region.

    Tip: The Team Collaborator and Project Execution roles appear in the Role Details table by default. You can change the default roles on the Manage Project User Provisioning page > Default Provisioning Attributes tab.
  7. Click Save and Create Another or Save and Close.

    This action:

    • Sends a request for a user account to the identity management system

    • Sends the resource an e-mail notification when the provisioning process is successful

Additional points to consider:

  • You can add or remove roles for a resource with an existing user account. Use the Edit feature to add roles. Use the Actions menu to remove roles.

    Note: You must wait until the previous provisioning request is complete for a resource before you add or remove roles for the resource.
  • Use the Assign Resource as Project Manager action in the Search Results region to add a resource to a project as a project manager. When you add a project manager with the Assign Resource as Project Manager action, the application provisions the Project Execution role for the resource.

  • Click the link in the Last Request Status column to view the details of the most recent provisioning action for a resource.

  • On the Manage Project User Provisioning page > Default Provisioning Attributes tab, you can:

    • Select project-related predefined and custom roles to provision by default when you create project users.

    • Select the Automatically provision roles when mass creating project enterprise labor resources option to assign the default roles when creating users with import processes and services for employees and contingent workers.

You can provision a resource on the Manage Project Enterprise Resources page when you create or edit a resource who is not an employee or contingent worker in Oracle Fusion Human Capital Management.

Provisioning a Resource

You can request a user account from the Create Project Enterprise Resource window or Edit Project Enterprise Resource window.

  • On the Create Project Enterprise Resource window, select the Request user account option.

  • On the Edit Project Enterprise Resource window, click Activate User Account.

When you request a user account from the Create or Edit Project Enterprise Resource window, the application:

  • Provisions the default role assignments for the resource

  • Sends a request for a user account to Oracle Identity Management

  • Sends the resource an e-mail notification when the provisioning process is successful

Click the link in the User Account Status column to view the role provisioning status of the most recent provisioning action for a resource.

A project application administrator can use the Assign Resource as Project Manager action in the Manage Project User Provisioning page > Search Results region to add a resource to a project as a project manager. For example, assume that a project team member takes over the project manager responsibilities while the manager is away on leave. The administrator can add the team member as a project manager and provision the Project Execution role for the team member.

When the administrator adds the resource as a project manager:

  • If the resource is an existing project user, doesn't have a pending provisioning request, and doesn't have the Project Execution role, then role provisioning is requested to assign the Project Execution role to the resource. The resource is added to the project as a project manager with a Planned assignment status.

  • If the resource is an existing project user with the Project Execution role, then the resource is added to the project as a project manager and no provisioning occurs.

  • If a resource isn't an existing project user, or if a resource has a pending provisioning request, then you can't assign the resource as a project manager from the Manage Project User Provisioning page.

FAQs for Project User Provisioning

Why can't I view project management or resource management pages?

To view project management or resource management pages, you must be a project enterprise labor resource with an active user account. In addition, you must have a job or abstract role with the security privilege to access specific pages in Project Execution Management applications.

For more information, refer to the Securing Project Execution Management Applications section in the Implementing Project Portfolio Management Security: Overview topic.

Project Management Roles

A project role is a classification of the relationship that a person has to a project, such as project manager, functional consultant, or technical lead.

Following are examples of predefined project roles that you can't edit or delete:

  • Project manager

  • Team member

  • Staffing owner

You can create additional project roles to meet the needs of your organization. However, you can't delete a project role that's designated as a resource's primary project role, specified on a project resource request, or assigned to a resource on a project.

Use project roles for the following purposes:

  • To identify the type of work that a person performs on project assignments

  • To set up default resource qualifications

  • As criteria when searching for resources to fulfill project resource requests

  • As a resource's primary project role

  • To allow access to project management information for project managers

  • To identify the default staffing owner of project resource requests for a project

Project Assignments

You select a project role when you add a resource to a project. The primary project role for a project enterprise resource is the default project role when you add the resource to the Manage Project Resources page.

When you fulfill a project resource request in the Project Resources work area and create an assignment for the resource, the project role specified on the request is the default project role on the assignment. You can change the project role on assignment before you submit the assignment for approval.

Default Resource Qualifications

On the Manage Project Roles page, select a set of default qualifications, proficiency, and keywords for each project role. Default qualifications, proficiency, and keywords that you associate with a project role automatically appear as requirements on a project resource request when you select the project role for the request.

Project Resource Requests

When searching for resources to fulfill a project resource request on the Search and Evaluate Resources page, you can filter the resource search results by the resource's primary project role to focus the results.

Primary Project Roles

You can designate a primary project role for a resource that represents the work that the resource typically performs on project assignments.

You can use the resource's primary project role in the following areas:

  • As a resource search option filter when viewing resources on the Search and Evaluate Resources page

  • When viewing resource information on the Resource Details page

  • When comparing the attributes of multiple resources against the requirements specified in the project resource request on the Compare Resources page

  • As an attribute value to assign to new resources that the Maintain Project Enterprise Labor Resources process creates

  • As search criteria when searching for a project enterprise labor resource to designate as a resource pool owner on the Manage Resource Pools page

  • As advanced search criteria when searching for resource pool members on the Manage Resource Pools page

  • When sorting open project resource requests on the Resource Manager Dashboard

To limit the actions that are available when managing project resources, project application administrators can create custom project roles with different privileges. For example, you want a project manager to have full access for creating and editing project resource requests. But you might not want a junior project manager to have all these capabilities.

Before you can create custom project roles with limited resource management capabilities, you must opt in for the Define Project Roles with Limited Actions for Managing Resources on a Project feature.

Users can be assigned different roles for different projects and therefore have different access across their projects. For example, a user can be the senior project manager, with complete access, for one project and be an assistant project manager, with limited resource management capability, for a different project.

To create roles with different resource management capabilities, create various custom project manager roles with the Manage Project Resource Assignment functional privilege and one of the following data privileges:

  • View Project Team Members for Project Data: Provides view-only access.

  • Edit Project Team Members for Project: Provides the ability to add, update, replace, and delete resources.

  • Manage Project Resource Assignment Data: Provides the ability to add, update, replace, delete resources, create resource requests, view resource request details, view assignment details, request extensions, cancel assignments, and manage project resource requests. It also provides the ability to search in case of placeholder resources.

You might be wondering what happens to existing roles. When you opt into the feature:

  • Manage Project Work Plan Resource Assignments Data is automatically rolled up to the predefined Project Manager role and the Project Execution abstract role.

  • By default, users with custom roles will see only a view-only version of the Manage Project Resources page. You can update the role definitions of custom manager roles to include additional functional and data privileges. For example, you can add the Manage Project Resource Assignment Data privilege to a custom role.

Note: The ability of a project manager to directly confirm a resource or edit a confirmed resource is available only to users with a role that includes the Assign Project Resource to Project and Assign Project Resource to Project Data privileges.

Project Plan Calendars

Project and resource calendars define the standard working and nonworking time for projects and resources. Working times are the days and total hours in a calendar during which work can occur. Nonworking times in a calendar are days and total hours for which work isn't scheduled, such as weekends and holidays.

Note: When you set up calendars for Project Management and Project Resource Management, you can select only the Elapsed schedule type to use in project and resource calendars.

Features of project and resource calendars include:

  • Default calendars

  • Project calendars

  • Resource calendars

  • Standard calendar

Default Calendars

Your implementation team selects a default project calendar and resource calendar on the Define Project Management Implementation Options page. The default project calendar is automatically assigned to new projects, and the default resource calendar is automatically assigned to new project enterprise labor resources.

If the default project calendar doesn't meet the schedule requirements for a specific project, a project manager can select another calendar during project creation. Similarly, if the default resource calendar doesn't meet the scheduling requirements for a specific project enterprise labor resource, the project application administrator can assign another calendar to the resource.

Project Calendars

A project manager can select the calendar for a project during project creation or when managing the project plan. The working days and total hours in the calendar are used to schedule the project plan. The calendar also works with the project start and finish dates to determine the project duration.

If required, associate a schedule exception with the selected calendar for the project plan. If you create an off period exception, then the exception overrides any nonworking days and makes them working days. If you create a work period exception, then the exception overrides any working days and makes them nonworking days. The project plan uses the schedule exceptions for calculating dates or duration.

Create a schedule exception using the Manage Project Schedule Exceptions task and associate the exception to the project calendar using the Manage Project Schedules task in the Setup and Maintenance work area.

Resource Calendars

The project application administrator can select a resource calendar when creating or editing a project enterprise resource. The working days and total working hours in a resource calendar are used to determine resource availability.

The Project Resources work area uses the resource calendar to determine a resource's available hours for a project. The Update Resource Utilization Data process calculates the resource's projected utilization with the available hours.

Standard Calendar

Project Execution Management provides a standard calendar of 8 hours per day, 5 days per week that you can assign to projects and resources.

FAQs for Project Plan Calendars

What happens if project resource request dates are outside the resource calendar effective dates?

The application can't calculate a resource's available capacity if the project resource request dates are outside of the resource calendar effective dates. The resource will have no Available Capacity score.

Project Enterprise Resources

A project enterprise labor resource is a resource that you can assign to multiple projects. If you manage resource availability and staffing in Project Resource Management, use project enterprise labor resources to fulfill project resource requests.

Consider the following attributes and options when creating a resource in the Create Project Enterprise Resources window.

  • Resource details

  • Personal details

  • Resource Management details

  • Rate details

Resource Details

Resource details include the following attributes:

  • Type

    You can create both labor and expense type resources to add to a project.

    Select the Create from expenditure type option to create an expense resource from an expenditure type in Project Financial Management.

  • Create From HCM Person

    Select this option to create a project enterprise labor resource from an employee or contingent worker in Oracle Fusion HCM.

    Note: The employee or contingent worker must have a unique e-mail in a valid format and an active primary assignment in HCM.
  • From Date and To Date

    The resource's From Date is the date from which you can assign the resource to a project. The To Date is the last date that you can assign the resource to a project.

  • Request User Account and Provision Project Roles

    Select these options to request a user account for a new resource and provision the resource with default role assignments. You can request a user account only for a resource who isn't associated with an employee or contingent worker in HCM.

    Click Activate User Account to request a user account for an existing resource. This action provisions the default role assignments for the resource and sends the resource an e-mail notification.

Personal Details

Personal details include the following attributes:

  • Calendar

    Resource calendars are used to:

    • Determine resource availability

    • Schedule tasks

    • Assign resources to tasks

    • Calculate cost and bill amounts based on hourly rates

    Daily work on a resource's calendar is measured in hours per day. Task duration is measured in days.

    You set up calendars to assign to projects and resources, or use the predefined calendar with eight hours per day and five days per week with no holidays. You select the default calendar on the Define Project Management Implementation Options page.

  • Primary Project Role

    The primary project role is the role that a resource most often fulfills on a project. The default value is Team Member.

  • Resume Attachments

    The application searches the text in a resource resume to find matches for keywords that are entered as requirements on a project resource request. The keyword occurrences are used in the resource qualification score calculation that indicates how well a resource meets the requested qualifications.

Resource Management Details

Resource Management details consist of the following attributes:

  • Manage Resource Availability and Staffing

    Select this option for the resource to be eligible to fulfill project resource requests in Oracle Fusion Project Resource Management.

  • Resource Pool

    You must select a resource pool if you select the Manage resource availability and staffing option. The default resource pool value is Resources with No Pool Membership.

  • Membership From Date

    A resource's first pool membership from date must be equal to or later than the resource from date.

    Tip: Manage pool memberships for a resource on the Manage Resource Pool Memberships window.

Rate Details

The rate types on a resource definition are:

  • Cost Rate: The rate for a unit of work that determines the cost for a resource on a project. To calculate the resource cost amount, the application multiplies the resource's labor effort in hours on the project by the resource's cost rate.

  • Bill Rate: The rate for a unit of work that determines the invoice or revenue recognized amount for a resource on a project. To calculate the bill amount for a resource on a project, the application multiplies the labor effort by the project resource bill rate.

When you add a planning resource to a project, the application copies the resource cost and bill rates to the project if the resource rate currency is the same as the project currency.

You can edit planning resource rates directly on the project. You can edit rates for assigned resources, or resources who have pending assignment adjustments, directly on the assignment. The new rates are reflected in the labor cost and bill amounts on the resource's tasks. Rate changes that you make on the project or assignment don't affect the rates on the resource definition.

Import Project Enterprise Resources

The Import Project Enterprise Resources process creates resources based on data from third-party applications that you load into the Project Enterprise Resource Interface table (PJT_PRJ_ENT_RES_INTERFACE).

The Import Project Enterprise Resources process:

  • Validates and creates project enterprise labor or expense resources in Oracle Fusion Project Management based on the data that you load into the interface table

  • Creates user accounts for labor resources

  • Assigns default project roles to labor resources

  • Reports process exceptions for invalid resources in an output report

To import resources:

  1. Prepare data for loading and importing by using the Project Enterprise Resources Import Template or Project Enterprise Expense Resources Import Template macro-enabled Excel workbooks.

  2. Click Generate CSV File in the templates to create worksheets to load to the interface table.

    Optionally bypass the Excel templates and manually create CSV files.

  3. From the Scheduled Processes page, run the Load Interface File for Import process followed by the Import Project Enterprise Resources process.

For more information about file-based data import, see the File Based Data Import for Oracle Project Portfolio Management Cloud guide.

Import Project Enterprise Resources Execution Report

The Import Project Enterprise Resources Execution Report summarizes the number of successful transactions and errors encountered when you imported the resources. If the report has error messages, then:

  1. Review the error message details for each resource and fix the issues.

  2. Load the data that you fixed in the CSV file into the interface table again.

  3. Resubmit the Import Project Enterprise Resources process.

Use either of these methods to import resources from HCM:

Importing in Oracle Fusion Project Management

In Oracle Fusion Project Management:

  1. Select the Import HCM Persons as Project Enterprise Resources action on the Manage Project User Provisioning page.

  2. The process:

    • Creates project enterprise resources based on specified criteria for business unit, organization, and HCM manager

    • Provisions the default project-related enterprise roles to each resource

    • Assigns default attribute values such as resource calendar and project role

    • Assigns the employee hire date, or contingent worker placement date, as the resource from date

    • Assigns the termination date in HCM as the resource to date

    • Imports only active HCM employees and contingent workers

Importing in Oracle Fusion Project Resource Management

In Oracle Fusion Project Resource Management:

  1. Specify your import criteria on the Manage Project Enterprise Labor Resource Maintenance Conditions page.

  2. Click Maintain Project Enterprise Labor Resources and enable the option to create and update project enterprise labor resources.

  3. The process imports employees and contingent workers based on your specified criteria and HCM hire and termination dates.

Update HCM Information for a Project Enterprise Resources

To update project enterprise resource information in Oracle Fusion Project Management from HCM:

  1. Select the resources on the Manage Project Enterprise Resources page that you want to update.

  2. Select the Update Information from HCM action.

  3. The process updates the following resource information from information in HCM:

    • Name

    • E-mail

    • Manager

    • Phone

    • Image

Use project enterprise expense resources to manage expense resources that can be assigned to projects or tasks in the Project Execution Management applications in Oracle Fusion Project Portfolio Management. You can use predefined project enterprise resource expense type options, create your own expense resource type, or create from expenditure type resources existing in project financial management in Oracle Fusion Project Foundation.

Consider the following attributes when creating a project enterprise expense resource:

  • Type attribute

  • Expenditure type option

  • Expenditure type

  • Expenditure type resource

  • Unit of measure

Selecting the Type Attribute

You can add an expense type resource to a project. Project enterprise expenditure type resources are the Expense resource type.

Creating from Expenditure Type Option

Use the Create from expenditure type option to create expense type resources from expenditure type planning resources created in Oracle Fusion Project Foundation.

Selecting the Expenditure Type

Expenditure types can track various expenses on projects or tasks. You can link to existing expenditure types for expenses that are used regularly including hotel, airfare, and meals.

You can't edit predefined expenditure types.

Creating an Expenditure Type Resource

Identify unique expense requirements for your organization. For example, you may want to track cell phone expenses separately from home phone expenses on a specific project.

Managing Unit of Measure

You can't edit the unit of measure for expense resources on a project because the default value is currency.

During the search and evaluation of resources to fulfill a project resource request, a resource manager can view resource cost and bill rates and select a resource that meets the financial requirements of a project. Project assignment rates provide the data to calculate labor resource cost and bill amounts for analyzing margins and revenue forecasts. Resource and project managers can adjust the rates on project assignments to provide the most current reporting information.

Aspects of project enterprise labor resource cost and bill rates include:

  • Defining resource rates

  • Comparing rates when evaluating resources

  • Populating project assignment cost and bill rates

  • Adjusting project assignment rates

  • Calculating project labor cost and bill amounts

Defining Resource Rates

Project application administrators can define cost and bill rates for a resource in the Manage Project Enterprise Resources page > Create Project Enterprise Resource window. Administrators can also define rates when importing resources from external sources such as third-party applications.

Resource rates are optional.

The resource rate types are:

  • Cost Rate: The rate for a unit of work that determines the cost for a resource on a project.

  • Bill Rate: The rate for a unit of work that determines the invoice or revenue recognized amount for a resource on a project.

Units of work are stated in hours.

Comparing Rates when Evaluating Resources

A project resource request can contain the following resource rates:

  • Target cost and bill rates: Project managers can specify target cost and bill rates on a project resource request. Rates are optional on the request.

  • Resource cost and bill rates: When you specify a resource for a request, the application copies the resource's cost and bill rates to the request.

When a resource manager searches for resources to fulfill a request, the resource's cost and bill rates appear on the Search and Evaluate Resources page for all resources in the search results. The resource manager uses the Compare Resources page to compare the target rates to the rates for selected resources.

Tip: Project and resource managers can also view the resource rates on the Resource Details page. This is especially useful if the resource manager doesn't perform a search for resources, but instead is considering only one resource to fulfill a request.

Populating Project Assignment Cost and Bill Rates

Assignment rate currency is based on the project currency. The application doesn't copy rates from the resource or project resource request to the assignment if the rate currency is different than the project currency. If rates aren't specified for the resource or project resource request, or if all available rates are in a currency other than the project currency, then the assignment is created without bill or cost rates.

The following table describes the methods of populating cost and bill rates on project assignments.

Method of Creating Assignment Method of Populating Assignment Cost Rate Method of Populating Assignment Bill Rate

Resource fulfills a project resource request

Assignment uses the resource cost rate

  • Assignment uses the target bill rate from the project resource request

  • If a target bill rate isn't specified on the request, then the assignment uses the resource bill rate

Resource is assigned directly to a project

Assignment uses the resource cost rate

Assignment uses the resource bill rate

Adjusting Project Assignment Rates

Project managers can adjust resource rates on the Manage Project Resources page for resources who are directly assigned to the project. Project managers can adjust the rates for any project resource on the Edit Project Resource Assignment page. Rate changes that you make in Oracle Fusion Project Management for confirmed resources are reflected on the assignment in Oracle Fusion Project Resource Management.

Resource managers can adjust resource rates on the Edit Project Resource Assignment page. Rate changes are reflected on the assignment in Oracle Fusion Project Management.

You can't adjust the assignment rate currency.

Adjusted rates are reflected in the labor cost and bill amounts on the resource's tasks.

Note: Cost and bill rate changes on the project or assignment don't affect the resource's cost and bill rates on the Manage Project Enterprise Resources page.

Calculating Project Labor Cost and Bill Amounts

To calculate the cost or bill amount of project labor resources, the application multiplies each resource's labor effort in hours by the resource's cost or bill rate.

Adjust Cost and Bill Rates for a Project Enterprise Resource

Project application administrators can adjust resource cost and bill rates for project enterprise labor resources.

Adjusting Rates for One Resource

To adjust cost and bill rates for one resource:

  1. Select the resource and on the Manage Project Enterprise Resources page.

  2. Click Edit to open the Edit Project Enterprise Resource window.

Adjusting Rates for Multiple Resources

To adjust cost and bill rates for multiple resources:

  1. Select the resources and click Adjust Resources on the Manage Project Enterprise Resources page.

  2. In the Adjust Resources window, select one or both rate types in the Resource Attribute drop-down list.

  3. Enter new rates in the Cost Rate and Bill Rate fields and click Save and Close.

    The new rates apply to all resources listed in the Adjust Resources window.

Note: You can't change currency in the Adjust Resources window.

Adjusting Cost Rates for All Resources in a Business Unit

If you use Project Financial Management applications, you can adjust cost rates for all resources in a business unit as follows:

  1. Select the resources on the Manage Project Enterprise Resources page.

  2. In the Actions menu, select Update Resource Cost Rates.

  3. Select the business unit, resource class rate schedule, and effective rate date.

  4. Click Update Resource Cost Rates to run a process to update the cost rates for all project enterprise resources within a business unit, using the selected rate schedule.

Note: The Update Resource Rates for Project Enterprise Resources process updates cost rates only for employees and contingent workers.

FAQs for Project Enterprise Resources

How can I remove a role from a resource?

To revoke a project-related role from a project user, select the role in the Manage Project User Provisioning page > Edit Project User window > Role Details table, and click the Remove icon.

Go to the Manage Project User Provisioning page, Default Provisioning Attributes tab, Default Project Role Provisioning for Project Execution Management Labor Resources section. Select the option to Automatically provision roles when mass creating project enterprise labor resources. The application automatically assigns the predefined and custom roles that you selected on the Define Role Assignments table to each resource when you create project users using any of these methods:

  • Import HCM Persons as Project Enterprise Resources process

  • Import Project Enterprise Resource process for Oracle Cloud

  • Project Enterprise Resource External Service

  • Maintain Project Enterprise Labor Resources

  • Export Resources and Rates process from the planning resource breakdown structure in Oracle Project Financial Management to Oracle Fusion Project Management

Can I edit the name and email for a project enterprise labor resource?

You can edit a resource name and email if the resource was created in Oracle Fusion Project Management, doesn't have a user account, and isn't an employee or contingent worker.

You can't edit the name and e-mail once you start the process to create a user account and provision roles for the resource.

How can I diagnose issues with project resources?

Run the Project Resource Validation diagnostic test from the Settings and Actions > Troubleshooting > Run Diagnostic Tests menu to determine whether a specific project or all projects have valid project resources and resource allocations, project roles exist, placeholder resources are associated with project resource requests, and expense resources are valid. The test generates a report showing the results of five eligibility parameters.

  • Project Enterprise Resource Test: Validates that project resources are valid project enterprise resources.

  • Project Role Setup Test: Validates that project roles exist.

  • Labor Resource Allocation Test: Validates that project resources have a valid allocation percentage. The resource assignment from and to date are within the project date range. All of the project resource allocation percentages are greater than zero and result in assigning the resource for less than or equal to 24 hours a day. All project resources are assigned valid project roles.

  • Project Resource Requests for Placeholder Resources Test: Validates that placeholder resources that are associated with a resource request are in a Requested status. None of the placeholder resources that are in a Planned status are associated with resource requests.

  • Expense Resource Test: Validates that project expense resources have no value for percentage allocation, effort, bill rate, cost rate, project role, e-mail, from date, and to date.

What's the difference between a project enterprise labor resource and a managed project enterprise labor resource?

A project enterprise labor resource is a resource that you can assign to multiple projects.

A managed project enterprise labor resource is a project enterprise labor resource whose availability and staffing are managed in Oracle Fusion Project Resource Management. You use managed project enterprise labor resources to fulfill project resource requests and directly assign to one or more projects.

What's the difference between a project enterprise labor resource and a project-specific resource?

You can assign a project enterprise labor resource to multiple projects. If you manage the availability and staffing of a project enterprise labor resource in Oracle Fusion Project Resource Management, then the resource is eligible to fulfill project resource requests. You can select the Manage Resource Availability and Staffing option for a project enterprise labor resource, and subsequently deselect the option. However, you can't change a managed project enterprise labor resource to a project-specific resource.

You can assign a project-specific resource to only one project, and subsequently change the project reference to a different project. You can't select the Manage Resource Availability and Staffing option for a project-specific resource. However, if you remove the project reference to change the resource to a project enterprise labor resource, then you can select the Manage Resource Availability and Staffing option.

Application Composer

Configure Project Execution Management Applications

A project application administrator can add additional attributes to standard objects or create new custom objects to meet specific business needs using Application Composer. In Project Execution Management applications, you can configure project resource requests, deliverables, issues, and backlog items. For example, you can add an issue category attribute to drive additional information that you need to collect for a particular type of issue in the standard Issues object. You can also create a custom Risk object to capture and track risks.

After you create a custom object, you can:

  • Use the REST service to create, view, and update the custom object.

  • Create a new subject area to report on the custom object.

Since your organization can view the changes you make at runtime immediately, you must first create or select a sandbox and isolate your changes. A sandbox provides an independent development environment so that you can fully test your changes before publishing the sandbox and making the changes available to your organization.

Navigate to Application Composer from Tools and select ERP and SCM Cloud in the Application field. You can view the objects for Project Execution Management applications under Standard Objects menu.

Standard Objects Available for Configuration

The following table summarizes the objects, pages, and regions that you can configure. The objects listed here are available in Application Composer for configuration.

Standard Object Corresponding Page or Region Maximum Custom Attributes Allowed

Project Resource Requests

  • Manage Project Resource Request page in Project Management work area

  • Manage Project Resource Request page in Project Resources work area

  • Create and Edit Project Resource Request page in Project Management work area

  • Create and Edit Project Resource Request page in Project Resources work area

50 number fields (Any combination of Number, Percentage, Currency, Dynamic Choice List)

100 Variable character fields (Any combination of Text, Check box, Fixed Choice List)

20 Time stamp (Any combination of Date, Date Time)

Project Issues

  • Create and Edit Issue page in My Work work area

  • Create and Edit Issue windows in Team Member Dashboard Issues section

50 number fields (Any combination of Number, Percentage, Currency, Dynamic Choice List)

100 Variable character fields (Any combination of Text, Check box, Fixed Choice List)

20 Time stamp (Any combination of Date, Date Time)

Project Deliverables

Create and Edit Deliverables page in My Work work area

50 number fields (Any combination of Number, Percentage, Currency, Dynamic Choice List)

100 Variable character fields (Any combination of Text, Check box, Fixed Choice List)

20 Time stamp (Any combination of Date, Date Time)

Backlog Items

Manage Backlog Items page

50 number fields (Any combination of Number, Percentage, Currency, Dynamic Choice List)

100 Variable character fields (Any combination of Text, Check box, Fixed Choice List)

20 Time stamp (Any combination of Date, Date Time)

Create a Text Field

Use Application Composer to add a text field to an existing Projects object as per your business requirement.

Note: Once you create a field, you can't change the field's Name and API Name. Even if the Display Label changes, the name used to refer to this field in Groovy expressions doesn't change.

Adding a Text Field

Use the following steps to create a text field.

  1. Ensure that you're working in a sandbox.

  2. Click Navigator > Tools > Application Composer.

  3. Select ERP and SCM Cloud from the Application list, enable PPM as the Object Tags and expand Standard Objects.

  4. Expand any of the following objects and click Fields to add a text field:

    • Backlog Item

    • Project Deliverable

    • Project Issue

    • Project Resource Request

    We will explain the following steps to show how a text field is added to the Project Resource Request object for Project Management work area.

  5. Click the Fields link under the Project Resource Request object.

  6. In the Custom tab, click the Create a custom field icon.

  7. In the Select Field Type window, select Text and click OK.

  8. In the Create Text Field page, enter the information for the field. You must enter values for the Display Label and Name fields. The attributes for the text field are described in the following table.

    Property Description

    Display Label

    Display label for the field. For example, create a text field named Travel Location.

    Help Text

    Information displayed in the tool tip.

    Display Width

    Character width for the text field.

    Display Type

    Determines the type of text field displayed to the users. You can choose Simple Text Box that's a single-line text field, or Multiline Text Area, a larger text area that spans multiple lines.

    Name

    Unique identifier for the field. This field is used for internal purposes and not displayed to the users. The Display Label is the default value for this field but you can change the name. The application programming interface (API) name that you use to identify the field in Groovy expressions is derived from this name.

    Description

    Optional description of the object. This field is used for internal purposes.

    Required

    Indicates if the field is required. Optionally, use the expression builder to write an expression that specifies when the field must be required.

    Updatable

    Indicates if the field is updatable. Optionally, use the expression builder to write an expression that specifies when the field can be updated.

    Searchable

    Indicates whether to make the field available for selection as additional search criteria in the Add Fields list in Advanced Search mode.

    Depends On

    Indicates the fields whose data changes will cause the field's constraint expressions to be re- evaluated.

    Minimum Length

    Indicates the minimum number of characters allowed in the text field.

    Maximum Length

    Indicates the maximum number of characters allowed in the text field.

    Fixed Value

    Literal default value for the field. Do not enter a fixed value if the field is both required and intended to be unique because that causes runtime errors.

    Expression

    Expression that dynamically sets the default value.

  9. Click Save and Close. You can view the new text field (Travel Location) under the Custom tab on the Fields page.

  10. Expand the Project Resource Request object and click the Pages link.

  11. On the Project Resource Requests: Pages page, click the Duplicate icon in the Landing Page Layouts section of the Project Management work area.

  12. In the Duplicate Layout window, enter the new layout and source layout name. For now, keep the new layout name and the source layout to the default value.

  13. Click Save and Close. You can now see the Default custom layout link under the Landing Page Layouts section of the Project Management work area.

  14. Click the Default custom layout link from the Landing Page Layouts section of the Project Management work area.

  15. On the Landing Page Layout: Default custom layout page, click the Edit icon next to the Project Resource Requests Table in Project Management work area heading.

  16. In the Configure Summary Table section, select the new text field (Travel Location) from the Available Fields table and move it to the Selected Fields table.

  17. Click Save and Close. You can now see the new text field (Travel Location) on the Project Resource Requests page in the Project Management work area.

Note: After you make your changes in a sandbox, work with your applications administrator to either delete or publish the sandbox. Deleting the sandbox reverts your changes. Publishing the sandbox applies the changes you made across your organization.

Create a Fixed Choice List Field

Use Application Composer to add a fixed choice list field for an existing Projects object as per your business requirements.

Note: The Name and API Name of a field can't be changed after it's created. Even if the Display Label changes, the name used to refer to this field in Groovy expressions doesn't change.

Creating and Describing the Fixed Choice List Field

Use the following steps to create and describe a fixed choice list field.

  1. Ensure that you're working in a sandbox.

  2. Click Navigator > Tools > Application Composer.

  3. Select ERP and SCM Cloud from the Application list, enable PPM as the Object Tags and expand Standard Objects.

  4. Expand any of the following objects and click Fields to add a fixed choice list:

    • Backlog Item

    • Project Deliverable

    • Project Issue

    • Project Resource Request

    We will explain the following steps to show how a fixed choice list field is added to the Project Resource Request object for Project Management work area.

  5. Click the Fields link under the Project Resource Request object.

  6. In the Custom tab, click the Create a custom field icon.

  7. In the Select Field Type window, select Choice List (Fixed), and click OK.

  8. In the Create Fixed Choice List page, enter the basic information for the field, such as Display Label, Name, and the Constraints.

  9. Select the display type:

    • If the users can select only one value, then select Single Select Choice List.

    • If the users can select multiple values, then select Multiple Select Choice List.

      For example, create a single select choice list named Travel Required for Project Resource Request in Project Management work area with values Yes and No.

  10. If the lookup type was previously defined, click the Search and Select Lookup Type icon next to the Lookup Type field, search for the lookup type, select it, and click OK. Otherwise, create the lookup type as described in the next section.

  11. Click Save and Close. You can view the new fixed choice list field (Travel Required) under the Custom tab on the Fields page.

  12. Expand the Project Resource Request object and click the Pages link.

  13. On the Project Resource Requests: Pages page, click the Duplicate icon in the Landing Page Layouts section of the Project Management work area.

  14. In the Duplicate Layout window, enter the new layout and source layout name. For now, keep the new layout name and the source layout to the default value.

  15. Click Save and Close. You can now see the Default custom layout link under the Landing Page Layouts section of the Project Management work area.

  16. Click the Default custom layout link from the Landing Page Layouts section of the Project Management work area.

  17. On the Landing Page Layout: Default custom layout page, click the Edit icon next to the Project Resource Requests Table in Project Management work area heading.

  18. In the Configure Summary Table section, select the new fixed choice list field (Travel Required) from the Available Fields table and move it to the Selected Fields table.

  19. Click Save and Close. You can now see the new fixed choice list field (Travel Required) on the Project Resource Requests page in the Project Management work area.

Creating the Lookup Type

If the lookup type isn't defined, then use the Create Lookup Type window to add lookups and to specify the list of values. Note that you can reuse lookup types for other fields.

Note: Although you're working in a sandbox, lookup types are created outside of a sandbox and become part of the mainline metadata.
  1. Click the Create a New Lookup Type icon that's displayed next to the Lookup Type field.

  2. Enter the lookup type properties listed in the following table.

    Property Description

    Meaning

    Unique name for the lookup type. Use a name that enables others to search for a lookup type that meets their needs for other fixed choice fields.

    Description

    Optional description that enables others to determine if the lookup type meets their needs for other fixed choice fields.

    Lookup Type

    Unique internal identifier for this lookup.

    Lookup Code

    Value for the lookup type.

  3. In the Lookup Codes table, from the Action menu, click Create to add an item to the list of valid values. For the fixed choice list field (Travel Required) you need to create the values, Yes and No.

  4. In the Meaning column, enter the value to display in the list of valid values. The value must be unique to the list.

  5. In the Lookup Code column, enter the internal code for the item. The value must be unique to the list. Use headline case without spaces to make it obvious in Groovy scripts that the lookup code isn't a string displayed in the interface.

  6. Enter the Display Sequence and Description for the lookup code.

  7. Create additional items to complete the list.

  8. Click Save.

  9. Click Save and Close. The fixed choice list field (Travel Required) is displayed on the Project Resource Request page in the Project Management work area.

Note: After you make your changes in a sandbox, work with your applications administrator to either delete or publish the sandbox. Deleting the sandbox reverts your changes. Publishing the sandbox applies the changes you made across your organization.

Create a Projects Custom Object

This example shows how to create a projects custom object using Application Composer. You can create:

  • An entirely new object (work area) to capture additional business requirements for your organization.

  • A child object under an existing standard object or the newly created custom object.

This table contains a summary of key decisions.

Decision to Consider In this Example

Why you need a custom object?

  • To track data for an object that isn't delivered with Oracle Project Portfolio Management Cloud.

  • To capture and track risks using the new Project Risk object.

Which users will have access to the custom object?

  • Decide which users should have access to custom object and whether it maps to existing roles the users have or if you need to create a new custom role.

  • In this example, the implementor will get access to the new object to illustrate the capabilities.

Prerequisites

  • You must be a project application administrator (ORA_PJF_PROJECTS_APPLICATION_ADMINISTRATOR_JOB) with the ZCX_MANAGE_EXTENSIBLE_OBJECT_PRIV privilege.

  • You must create or select a sandbox and create custom object within it.

Custom Project Risk Object

Creating custom Project Risk object involves:
  1. Creating the custom Risk object.

  2. Adding pages to the custom Risk object.

  3. Adding fields to the pages within the custom Risk object.

  4. Adding action links to the pages.

  5. Adding child objects and linking them to the custom Risk object.

  6. Adding the custom Risk object to the Project Portfolio Management work area.

Creating a Custom Object
The following steps explains how to create a custom object named Project Risks.
  1. Navigate to Tools > Configuration > Application Composer.

  2. From the Application drop down, select ERP and SCM Cloud.

  3. Under Objects menu, click the Create icon next to Custom Objects.

  4. Enter the information for your new object.

    Field Field Value

    Display Label

    Project Risk

    Plural Name

    Project Risks

    Record Label Name

    Project Risk Name

    Record Name Data Type

    Text

    Prevent Duplicate Values

    Enable

    Treat "ABC" and "Abc" as distinct values

    Disable

    Object Name

    ProjectRisk<yourinitials>. For example, ProjectRiskMP

    Description

    As required

  5. Click OK. The application creates the object. Note the Name as it is required to identify privileges and the API.

  6. Select the Change Icon link to select an icon that will appear in the Navigator.

  7. Select a display icon of your choice for the object.

Adding Fields to the Project Risk Custom Object
The following steps explains how to add fields to the Project Risks custom object.
  1. Under Objects > Custom Objects > Project Risk, click Fields.

  2. Click the Create a custom field icon.

  3. Create the following fields. See the procedures in related links for creating fields.

    Field Name Field Type

    Risk Number

    Number

    Mitigate Date

    Date

    Risk Description

    Long Text

    Severity Values: Low, High, and Medium

    Fixed Choice List

    Risk Percentage

    Percentage

    Project Name

    Text

    Escalated to Management

    Check box

    Status Values: New, Working, and Resolved

    Fixed Choice List

Creating an Action for the Project Risk Custom Object
  1. Under Objects > Custom Objects > Project Risk > Actions and Links, select Pages.

  2. Click the Create icon.

  3. Enter the action information as mentioned in the following table.

    Field Type Values

    Display Label

    Review Risk Policies

    Name

    Review_Risk_Policies

    Type

    Link

    Description

    Description for the Action Link.

    Source

    URL

    Display Mode

    New Window

    URL Definition

    https://en.wikipedia.org/wiki/Project_risk_management

  4. Click Save.

Creating Pages for the Project Risk Custom Object

  1. Under Objects > Custom Objects > Project Risk, click Pages.

  2. Click Create Default Pages.

  3. In the Landing Page Layouts section, click the Default custom layout link.

  4. Click the Edit icon next to the summary table.

  5. Configure the summary table. Select the following fields and enable them to display in the summary table. Do not display the Risk Description by default.

    • Project Risk Name

    • Risk Number

    • Project Name

    • Status

    • Severity

    • Risk Percentage

    • Creation Date

    • Mitigate by Date

    • Risk Description (Hidden)

  6. Configure the buttons and actions.

    • Toolbar

      • Create

    • Actions menu

      • Export

      • Update

  7. Configure Mass Edit Fields

    • Mitigate by Date

    • Risk Percentage

    • Severity

    • Status

  8. Click Save and Close.

  9. Click Done.

  10. In the Creation Page Layouts section, click the Default custom layout link.

  11. Click the Edit icon.

  12. Select the creation page fields:

    • Review Risk Policies- Link

    • Project Risk Name

    • Project Name

    • Risk Number

    • Status

    • Severity

    • Risk Percentage

    • Escalated to Management

    • Mitigate by Date

    • Risk Description

    • Risk Mitigation Strategy

  13. Click Save and Close.

  14. Click Done.

  15. In the Details Page Layouts section, click the Default custom layout link.

  16. Select the Edit icon for the main subtab and again select the creation page fields.

  17. Click Save and Close.

  18. Click Done.

Creating a Child Object for the Project Risk Custom Object
  1. Under Objects > Custom Objects, click the Default custom layout link.

  2. Click Create Child Object.

  3. Enter the information for your new object.

    Field Value

    Display Label

    Risk Log

    Plural Name

    Risk Logs

    Record Label Name

    Risk Log Name

    Record Name Data Type

    Risk Log Name

    Prevent Duplicate Values

    Enable

    Treat "ABC" and "Abc" as distinct values

    Disable

    Object Name

    RiskLog<yourinitials>. For example, RiskLogMP

    Description

    As required

    Parent Object

    Project Risk

    Child Collection Name

    RiskLogCollection

  4. click OK.

  5. Click OK and wait for the application to create the object.

  6. Click the Change Icon link to select an icon for the child object that will appear in the Navigator.

  7. Select an icon of your choice.

Adding Fields to the Risk Log Child Object
  1. Under Objects > Custom Objects > Project Risk > Risk Log, click Fields.

  2. Click the Create a custom field icon.

  3. Create the following fields. See the procedures in related links to create fields.

    Field Name Field Type

    Log Date

    Datetime

    Log Entry

    Text

Creating Pages for the Risk Log Child Object
  1. Under Objects > Custom Objects > Project Risk > Risk Log, click Pages.

  2. Click Create Default Pages.

  3. In the Creation Page Layouts section, click the Default custom layout link.

  4. Click the Edit icon and select the creation page fields.

    • Log Date

    • Risk Log Name

    • Log Entry

  5. Click Save and Close.

  6. Click Done.

  7. In the Details Page Layouts section, click the Default custom layout link.

  8. Click the Edit icon and select the creation page fields

    • Log Date

    • Created By

    • Last Update Date

    • Last Updated By

    • Risk Log Name

    • Log Entry

  9. Click Save and Close.

  10. Click Done.

Adding Child Object to Project Risk Custom Object Page

  1. Under Objects > Custom Objects > Project Risk, select Pages.

  2. In the Details Page Layouts section, click the Default custom layout link.

  3. Click the Add subtab icon.

  4. Select the Child object option.

  5. Click Next.

  6. Enter the subtab information.

    Field Type Field Name

    Direct Object

    Risk Log

    Direct Label

    Risk Log

    Display Icon

    Select the previously selected icon.

    Summary Table

    • Log Date

    • Risk Log Name

    • Log Entry

    • Last Update date

    Summary Table Search Region

    Log Date

    Summary Table Buttons and Actions

    • Show Create = Yes (Checked)

    • Show Edit = Yes (Checked)

    • Show Remove = Yes (Checked)

  7. Click Save and Close.

  8. Click Done.

Adding the Page to the Projects Navigator and Springboard

  1. Navigate to Tools > Configuration > Application Composer.

  2. Scroll to the bottom of the table and select the Project Risks link.

  3. Change the Group to Projects.

  4. Click Save and Close.

    Next, you must test your sandbox configurations. When you are satisfied with the results, you can publish the sandbox to make the custom object available to users with the appropriate access.

Testing Your Pages

  1. From the springboard, select Projects and then Project Risks.

  2. Scroll to the bottom of the table and select the Project Risks link.

  3. Click Create.

  4. Test the page, for example, check default values, click the link, and enter data.

  5. Click Save and Continue.

  6. Review and edit the information. Add an attachment.

  7. Select the Risk Logs subtab and review the fields.

  8. Click Create and enter a log entry.

  9. Click Save and Close.

  10. Review the results.

  11. Add additional risks. Test search and deletion of risks.

  12. Add multiple logs for a risk and test the filter and deleting.

Create a Dynamic Choice List

You can create a custom dynamic choice list field by referencing the objects such as, project, task, deliverable, issue, requirement, backlog, resource, or resource request. Then add it to a custom object or to an existing standard object. Imagine that you add an issue auditor based on the project enterprise resource to the Project Issue standard object.

  1. Ensure that you're working in a sandbox.

  2. Click Navigator > Configuration > Application Composer.

  3. Select ERP and SCM Cloud from the Application list and enable PPM as the Object Tags.

  4. Expand the standard object or custom object to which you want to add a dynamic choice list. For example, expand Project Issue.

  5. Click the Fields link under the object.

  6. In the Custom tab, click the Create a custom field icon.

  7. In the Select Field Type window, select Choice List (Dynamic), and click OK.

  8. In the Create Dynamic Choice List page, enter the basic information for the field, such as Display Label, Name, and the Constraints. For example, enter Issue Auditor in the Display Label field.

  9. Click Next to navigate to the page where you create a dynamic choice list for the field.

  10. From the Related Object list, select the object based on which you want to create the dynamic choice list. For example, select Project Enterprise Resource.

  11. From the List Selection Display Value list, select the option that should appear on the UI as values for the dynamic choice list field. For example, Name.

  12. Click Submit. You can now see the dynamic choice list field under the Custom tab on the Fields page

  13. Click the Pages link under the object.

  14. On the Pages page, click the Duplicate Creation Page Layout icon under the work area where you want to add the dynamic choice list.

  15. In the Duplicate Layout window, enter the new layout name and click Save and Close. You can now see the Default custom layout link under the Landing Page Layouts section of the selected work area. You can also click Save and Edit instead and go directly to step 17.

  16. Click the Default custom layout link from the Landing Page Layouts section of the Project Management work area.

  17. On the Landing Page Layout: Default custom layout page, click the Edit icon next to the work area name.

  18. In the Configure Summary Table section, select the dynamic choice list field you just created from the Available Fields table and move it to the Selected Fields table.

  19. Click Save and Close.

  20. Click Done. The dynamic choice list field now appears in the selected work area.

  21. Go to the work area, test your changes, and publish the sandbox.

Create a Dependent Dynamic Choice List

You can create a dependent dynamic choice list where the value of one dynamic choice list is dependent on another dynamic choice list. As a prerequisite you must create two dynamic choice lists. Suppose you:

  • Create Tracking Project field based on Related Object Project under the Project Issue standard object.

  • Create Tracking Task field based on Related Object Project Task under the Project Issue standard object.

  1. Open a dynamic choice list field in edit mode. For example, Tracking Task.

  2. In the Basic Information > Constraints > Depends On, select the first dynamic choice list. For example, Tracking Project field.

  3. Click Next.

  4. On the List of Values page, in the Data Filter section, enable Advanced Filter.

  5. Click Add Bind Variable and select Create new bind variable option.

  6. Enter a variable name and click OK. For example, enter Project_Name.

  7. Click Add Search Field and select a value from the list. For example, select the value Project_Name. The value displays in the text box below the Add Search Field.

  8. Append equal to (=) sign to the value in the text box below the Add Search Field . For example, Project_Name=.

  9. Click Add Bind Variable and select the value created in step 6. The text box below the Add Search field now shows an expression. For example, Project_Name=:Project_Name.

  10. Once you create the expression, you can view a table with the Variable Name and the Expression field.

  11. Click the xyz icon below the Expression text box that opens the Expression Builder window.

  12. In the Expression Builder window, click Show/Hide Expression Palette icon.

  13. Open Fields tab.

  14. Expand the object under which you created the dynamic choice lists and select a dynamic choice list. For example, expand Project Issue and select Tracking Project.

  15. In the Fields table, select the field and click Insert to provide a value to the bind variable. For example, select Project Name field. An expression displays in the left pane.

  16. Click OK.

  17. Click Submit.

  18. Add both the dynamic choice list to the appropriate pages. If you are adding fields to a standard object, then you will have to duplicate the predefined layout and edit the duplicate layout. For example, add the Tracking Project and Tracking Task field to the Manage Project Issues work area. You can now track an issue against a task within a specific project.

  19. Go to the work area, test your changes, and publish the sandbox.

Public Business Events

Overview of Public Business Events

A public event, also known as business event, is a definable logical occurrence in a business scenario. It can be a high-level occurrence such as project creation or a specialized event such as status change.

If you want to perform operations in other systems based on public events in Oracle Project Portfolio Management cloud, then you can use public event features. Project application administrators must enable public event features if they aren't enabled by default.

After you enable these features, Oracle PPM Cloud sends a signal, along with a payload containing information about the public event, whenever an event occurs. The public event signal is also known as public event.

Note: Oracle PPM Cloud sends signals irrespective of the source or cause of the event. For example, the application sends a project creation signal when a project is created using file-based data import, REST service, SOAP service, or user interface.

Integration developers and administrators can subscribe to public events from the Oracle Integration Cloud using the Oracle ERP Cloud Adapter. Then, they can use the information in the payload to configure event handlers that perform business operations. For more information, refer to Oracle ERP Cloud Adapter Capabilities and Developing Integrations with Oracle Integration Cloud Service.

Public event payload contains specific information pertaining to the event. You can use callback services to retrieve additional information from Oracle PPM cloud.

Public Events for Project Execution Management

This table describes the public events supported by Project Execution Management.

Cloud Product Supported Public Event Description Enabled by Default First Release Available Callback Service

Project Management

Project Deliverable Status Changes

Signals whenever project deliverables' status or priority changes. Creating or deleting deliverables doesn't generate signals.

No

19A

REST Service: Deliverables

Method: Get a deliverable

Task Management

Project Task Progress Status Changes

Signals whenever project task progress status changes. Creating or deleting tasks doesn't generate signals.

No

19A

REST Service: Project Plans

Resource: Tasks

Operation: Get a task of a project

Task Management

Project Milestone Completion

Signals whenever a project milestone is completed. Completing financial tasks that are flagged as milestones doesn't generate signals.

No

19A

REST Service: Project Plans

Resource: Tasks

Operation: Get a task of a project

Public Events for Project Deliverable Status Changes

If you want Oracle Project Portfolio Management Cloud to signal whenever project deliverables' status or priority changes, then enable the Generate Public Events on Project Deliverable Status Changes feature. You can enable it from the Edit Features: Project Execution Management page. Keep in mind that creating or deleting deliverables doesn't generate signals.

For example, if you want to send an email notification whenever the status of a deliverable changes to completed, then:

  1. You, as a project application administrator, must enable this feature. Oracle PPM Cloud signals when a project deliverable's status or priority changes.

  2. Integration developers must create event handlers that subscribe to these signals and send an email notification whenever the status of a deliverable changes to completed.

Attributes in the Payload for Project Deliverable Status Change Event

This table lists and describes the attributes in the payload.

Attribute Description

DeliverableId

Identifier of the deliverable.

ShortName

Short name of the deliverable.

OwnerName

Name of the person who owns the deliverable.

CreatedBy

Name of the person who created the deliverable.

CreationDate

Date when the deliverable was created. The format is MM-DD-YYYY.

NeedByDate

Due date of the deliverable. The format is MM-DD-YYYY.

PriorityCode

Internal code of the priority assigned to the deliverable.

StatusCode

Internal code of the status for the deliverable.

AssociationsCount

Total number of associations of the deliverable with project tasks and backlog items.

LastUpdatedBy

Name of the person who last updated the attachment.

LastUpdateDate

Date when the attachment was last updated.

Sample Payload for Project Deliverable Status Changes Event

Let's look at a sample payload that's generated when the status of a deliverable, Deliverable 1, changes from NEW to WORKING.

<content>
	<ProjectDeliverableStatusChangedInfo xmlns="http://oracle/apps/projects/projectManagementControl/deliverables/publicModel/entity/events/schema/DeliverableEO">
		<DeliverableId>
			<oldValue value="300100023181201"/>
			<newValue value="300100023181201"/>
		</DeliverableId>
		<ShortName>
			<oldValue value="Deliverable 1"/>
			<newValue value="Deliverable 1"/>
		</ShortName>
		<OwnerName>
			<oldValue value="Connor.Horton"/>
			<newValue value="Connor.Horton"/>
		</OwnerName>
		<CreatedBy>
			<oldValue value="Connor.Horton"/>
			<newValue value="Connor.Horton"/>
		</CreatedBy>
		<CreationDate>
			<oldValue value="01-12-2018"/>
			<newValue value="01-12-2018"/>
		</CreationDate>
		<NeedByDate>
			<oldValue value="02-12-2018"/>
			<newValue value="02-12-2018"/>
		</NeedByDate>
		<PriorityCode>
			<oldValue value="MEDIUM"/>
			<newValue value="MEDIUM"/>
		</PriorityCode>
		<StatusCode>
			<oldValue value="NEW"/>
			<newValue value="WORKING"/>
		</StatusCode>
		<AssociationsCount>
			<oldValue value="1"/>
			<newValue value="1"/>
		</AssociationsCount>
		<LastUpdatedBy>
			<oldValue value="Connor.Horton"/>
			<newValue value="Connor.Horton"/>
		</LastUpdatedBy>
		<LastUpdateDate>
			<oldValue value="01-12-2018"/>
			<newValue value="01-12-2018"/>
		</LastUpdateDate>
	</ProjectDeliverableStatusChangedInfo>
<\content>	

Public Events for Project Task Progress Status Changes

If you want Oracle PPM Cloud to signal whenever project task progress status changes, enable the Generate Public Events for Project Task Progress Status Changes feature. You can enable it from the Edit Features: Project Execution Management page. Keep in mind that creating or deleting tasks doesn't generate signals.

For example, if you want to initiate an activity in another application whenever task status changes to In Progress, then:

  1. You, as a project application administrator, must enable this feature. Oracle PPM Cloud signals when project task progress status changes.

  2. Integration developers must create event handlers that subscribe to these signals and initiate an activity whenever the project task progress status changes to In Progress.

Attributes in the Payload for Project Task Progress Status Changes Event

This table lists and describes the attributes in the payload.

Attribute Description

ProjElementId

Unique identifier of the task. This value is the same as Task ID.

ProjectId

Unique identifier of the project.

ElementType

Indicates if the task is financially tracked or tracked for execution only. Valid values are EXECUTION and FINANCIAL.

ProgressStatusCode

The code for the status of work completed on the task. Valid values are NOT_STARTED, IN_PROGRESS, and COMPLETED.

OldProgressStatusCode

The previous code for the status of work completed on the task. Valid values are NOT_STARTED, IN_PROGRESS, and COMPLETE.

BillableFlag

Indicates that transactions charged to the task can be billed to customers. Valid values are Y, N, and null. The value is Y when the transactions are billable. The value is N or null when the transactions aren't billable.

ChargeableFlag

Indicates that something is eligible to be charged to a task. Valid values are Y, N, and null. The value is Y when the transactions are chargeable. The value is N when the transactions aren't chargeable.

ActualStartDate

The date that work commenced on a task as opposed to the planned start date for the task.

ActualFinishDate

The actual finish date for the task as opposed to a planned finish date for the task.

StartDate

The date that work or information tracking begins on a project. The format is DD-MM-YYYY.

FinishDate

The date that work or information tracking completes for a project. The format is DD-MM-YYYY.

PercentComplete

Indicates the percentage of work completed for the task.

LastUpdatedBy

Name of the person who last updated the task.

Sample Payload for Project Task Progress Status Changes Event

Let's look at a sample payload that's generated when the status of a Project Task changes from Not Started to In Progress.

<content>
      <ProjectTaskProgressStatusChangedInfo xmlns="http://oracle/apps/projects/projectManagement/common/publicModel/entity/events/schema/ProjPlanLineEO">
         <ProjElementId>
            <oldValue value="300100111675917"/>
            <newValue value="300100111675917"/>
         </ProjElementId>
         <ProjectId>
            <oldValue value="300100082280694"/>
            <newValue value="300100082280694"/>
         </ProjectId>
         <ElementType>
            <oldValue value="EXECUTION"/>
            <newValue value="EXECUTION"/>
         </ElementType>
         <ProgressStatusCode>
            <oldValue value="NOT_STARTED"/>
            <newValue value="IN_PROGRESS"/>
         </ProgressStatusCode>
        <OldProgressStatusCode>
            <oldValue value="NOT_STARTED"/>
            <newValue value="NOT_STARTED"/>
         </OldProgressStatusCode>
         <BillableFlag>
            <oldValue value="N"/>
            <newValue value="N"/>
         </BillableFlag>
         <ChargeableFlag>
            <oldValue value="N"/>
            <newValue value="N"/>
         </ChargeableFlag>
         <ActualStartDate>
            <oldValue value="False"/>
            <newValue value="01-01-2019"/>
         </ActualStartDate>
         <ActualFinishDate>
            <oldValue value=""/>
            <newValue value=""/>
         </ActualFinishDate>
         <StartDate>
            <oldValue value="01-01-2019"/>
            <newValue value="01-01-2019"/>
         </StartDate>
         <FinishDate>
            <oldValue value="05-01-2019"/>
            <newValue value="05-01-2019"/>
         </FinishDate>
         <PercentComplete>
            <oldValue value="0"/>
            <newValue value="25"/>
         </PercentComplete>
         <LastUpdatedBy>
            <oldValue value="Connor.Horton"/>
            <newValue value="Connor.Horton"/>
         </LastUpdatedBy>
      </ProjectTaskProgressStatusChangedInfo>
</content>

Public Events for Project Milestone Completion

If you want Oracle PPM Cloud to signal whenever a project milestone is completed, enable the Generate Public Events on Project Milestone Completion feature. You can enable it from the Edit Features: Project Execution Management page. Keep in mind that completing financial tasks that are flagged as milestones doesn't generate signals.

For example, if you want to create a billing event whenever a project milestone is completed, then:

  1. You, as a project application administrator, must enable this feature. Oracle PPM Cloud signals when a project milestone is completed.

  2. Integration developers must create event handlers that subscribe to these signals and create a billing event whenever a project milestone is completed.

Attributes in the Payload for Project Milestone Completion Event

This table lists and describes the attributes in the payload.

Attribute Description

ProjElementId

Unique identifier of the task. This value is the same as Task ID.

Description

Text description of the project milestone.

ProjectId

Unique identifier of the project.

FinishDate

The date when work is scheduled to end for a project milestone. The format is DD-MM-YYYY.

ActualFinishDate

The actual finish date for the project milestone as opposed to a planned finish date for the project milestone. The format is DD-MM-YYYY.

LastUpdatedBy

Name of the person who last updated the record.

Sample Payload for Project Milestone Completion Event

Let's look at a sample payload that's generated when a project milestone is completed.

<content>
      <ProjectMilestoneCompletionInfo xmlns="http://oracle/apps/projects/projectManagement/common/publicModel/entity/events/schema/ProjPlanLineEO">
         <ProjElementId>
            <oldValue value="300100111675917"/>
            <newValue value="300100111675917"/>
         </ProjElementId>
         <Description>
            <oldValue value="Milestone: Customer Sign Off of Tested Software"/>
            <newValue value="Milestone: Customer Sign Off of Tested Software"/>
         </Description>
         <ProjectId>
            <oldValue value="300100082280694"/>
            <newValue value="300100082280694"/>
         </ProjectId>
         <FinishDate>
            <oldValue value="31-01-2019"/>
            <newValue value="31-01-2019"/>
         </FinishDate>
         <ActualFinishDate>
            <oldValue value=""/>
            <newValue value="31-01-2019"/>
         </ActualFinishDate>
         <LastUpdatedBy>
            <oldValue value="Connor.Horton"/>
            <newValue value="Connor.Horton"/>
         </LastUpdatedBy>
      </ProjectMilestoneCompletionInfo>
</content>