Implementing Oracle Project Resource Management

This chapter contains instructions for implementing Oracle Project Resource Management.

This chapter covers the following topics:

Oracle Project Resource Management Implementation Checklists

Oracle Project Resource Management is an integrated project staffing application to help you manage project resource needs, profitability, and organization utilization by locating and deploying qualified resources to your projects across your enterprise. Project Resource Management empowers key project stakeholders, such as project managers, resource managers, and staffing managers with key information to make better use of their single most critical asset: their people. Oracle Project Resource Management is part of the Oracle E-Business Suite, an integrated set of applications that are engineered to work together.

Note: To find out how to access a window, refer to the Navigation Paths index, Oracle Projects Fundamentals.

Oracle Project Resource Management Product Implementation Checklist

The following checklist shows the steps required to implement Oracle Project Resource Management. The product setup checklist is organized by area of functionality. The Required/Optional column indicates if the step is required or optional for use of the product.

To implement Oracle Project Resource Management, complete the steps in the following order:

  1. Licensing

  2. Project Staffing

1. Licensing

The following table lists the step required for licensing:

Step Description Required /Optional Setup Level Responsibility
PJR-P1.1 Set the profile option PA: Licensed to Use Project Resource Management Required Site System Administrator

Note: For details about the licensing step, see Licensing Oracle Project Resource Management.

2. Project Staffing

The following table lists the steps required for project staffing:

Step Description Required /Optional Setup Level Responsibility
PJR-P2.1 Define additional requirement statuses, candidate statuses, assignment approval statuses, and assignment scheduling statuses. Optional Site Projects Implementation Super User
PJR-P2.2 Set the requirement status, candidate status, and assignment status profile options Required Site System Administrator
PJR-P2.3 Define advertisement rules Optional Site Project Super User
PJR-P2.4 Define team templates Optional Site Project Super User
PJR-P2.5 Define staffing priority codes Optional Site Projects Implementation Super User
PJR-P2.6 Implement assignment approval workflow Optional Site  
PJR-P2.7 Implement assignment approval workflow extensions Optional Site  
PJR-P2.8 Implement candidate notification workflow Optional Site  
PJR-P2.9 Implement candidate notification workflow extension Optional Site  

Note: For details about the project staffing steps, see Project Staffing.

Oracle Project Resource Management Features Implementation Checklist

The following checklist shows the steps required to implement each Oracle Project Resource Management feature. The list is organized by feature. The Required/Optional column indicates if the step is required or optional for each use of the feature.

To implement Oracle Project Resource Management features, complete the steps in the following order:

  1. Organization Forecasting for Resources

  2. Reporting

1. Organization Forecasting for Resources

Prerequisites: Before you set up organization forecasting for resources, you must define the following entities in the Project Costing application:

The following table lists the step required for organization forecasting for resources:

Step Description Required /Optional Setup Level Responsibility
PJR-F1.1 Define forecasting options Required OU Projects Implementation Super User

Note: For details about the forecasting based on staffing plan step, see Implementing Organization Forecasting for Resources.

2. Reporting

The following table lists the steps required for reporting:

Step Description Required /Optional Setup Level Responsibility
PJR-F2.1 Implement Discoverer reporting Required Site  
PJR-F2.2 Perform Oracle Discoverer post-installation tasks Required Site  

Note: For details about the forecasting based on reporting steps, see Reporting.

Licensing Oracle Project Resource Management

The following instructions give details about the Licensing steps in the Oracle Project Resource Management Product Implementation Checklist.

To indicate to the system that Project Resource Management is licensed, set the profile option PA: Licensed to Use Project Resource Management.

See: PA: Licensed to Use Project Resource Management.

Project Staffing

The following instructions give details about the Project Staffing steps in the Oracle Project Resource Management Product Implementation Checklist.

Staffing Status Definitions

This section describes the following setup topics:

For information on using the Statuses window to define statuses, see: Defining Statuses and Status Profile Options.

Predefined Statuses and Status Controls

A status is the state of an object. Objects can have only one status at a time. Your implementation of Oracle Project Resource Management includes predefined statuses for the following objects:

You can create new user statuses based on the available system statuses to meet your business needs and create process flows that support those needs. You can also modify the default status controls for each user status.

For each existing user status, you must define the next allowable statuses. Defining the next allowable statuses determines the process flow for your objects.

For example, you can specify that a requirement with the user status Open can have its status changed only to either Filled or Canceled. This example shows that you have just determined two possible process flows of a requirement:

Requirement Statuses

The requirement status indicates the state or condition of the requirement in the staffing life cycle.

Predefined Requirement Statuses

The following table shows the predefined requirement statuses and suggested next allowable statuses.

System Status User Status Description Suggested Next Allowable Statuses
Open Open Available for resource assignments Filled, Canceled
Filled Filled A resource is assigned Canceled
Canceled Canceled Canceled None

The status controls for requirement statuses are:

Use these status controls to restrict allowable actions on requirements based on status.

Assignment Statuses

The assignment status is the daily assignment status. Therefore, each day of the assignment has its own schedule status.

Predefined Assignment Statuses

The following table shows predefined assignment schedule system statuses and suggested next allowable statuses:

System Status User Status Description Suggested Next Allowable Statuses
Provisional Provisional A resource is assigned to the assignment on a provisional basis. Confirmed, Canceled
Confirmed Confirmed The resource is confirmed and scheduled for the assignment. Canceled
Canceled Canceled The assignment was canceled. None

The status controls for assignment statuses are:

Use this status control to include assignments in project forecasts based on the status.

Candidate Statuses

Each candidate has a status that indicates the state of consideration in the nomination process on a given requirement.

Predefined Candidate Statuses

The following table shows the predefined candidate statuses with and suggested next allowable statuses:

System Status User Status Description Suggested Next Allowable Statuses
Pending Review Pending Review Nominated for the requirement and ready for review Suitable, Under Review, Declined, Withdrawn, or Assigned
System Nomination System Nomination Nominated by the automated candidate search and nomination process. You cannot modify the attributes of this status. Also, you cannot create user statuses with the System Nomination system status. Suitable, Under Review, Declined, Withdrawn, or Assigned
Under Review Under Review In the review process Under Review, Declined, Withdrawn, or Assigned
Suitable Suitable A suitable match for the requirement Under Review, Declined, Withdrawn, or Assigned
Declined Declined Unsuitable for the requirement (the default status control Requires Change Reason requires the user who declines the candidate to enter a reason) Suitable or Under Review
Withdrawn Withdrawn Withdrawn from consideration Under Review
Assigned Assigned Assigned to fill the requirement. This status is used only by the workflow process after the candidate has been assigned to fill the requirement. None

There is one status control for the candidate statuses:

This status control requires entry of a reason when a user changes the status of a candidate.

Assignment Approval Statuses

Each assignment has a status that indicates the state of the assignment in the staffing life cycle.

Predefined Assignment Approval Statuses

Assignment approval statuses are used by workflow processes. The assignment approval status represents the approval status for the entire assignment.

You cannot add, modify, or delete these statuses. The status is applied to an assignment based on the action being undertaken.

The following table shows predefined assignment approval statuses and their next allowable statuses:

System Status Description Next Allowable Statuses
Working The assignment is new and has not yet been submitted for approval, or the canceled assignment was changed and needs to be resubmitted for approval. Submitted
Submitted The assignment is submitted for approval. Approval can be sought either manually or by using a workflow process. Approved or Rejected
Approved The assignment is approved and the resource is confirmed. Requires Resubmission
Canceled The assignment is canceled. None
Rejected The assignment is rejected. The user can modify the assignment and resubmit it for approval. Requires Resubmission
Requires Resubmission The approved assignment has been changed and requires a resubmission for approval. Submitted

Setting the Staffing Status Profile Options

Set the following profile options to specify default values for staffing statuses. For details about each profile option, see: Profile Options in Oracle Projects.

Requirement Status Profile Options

Candidate Status Profile Options

Assignment Status Profile Options

Implementing Advertisement Rules

Advertisement rules control the visibility of a requirement to resources and managers of an organization over a period of time. Each advertisement rule is a list of actions that are performed when the condition associated with each action is met.

Implementation of advertisement rule functionality is optional.

Implementing Advertisement Rule Functionality

One advertisement rule, Publish to Everyone, is predefined in Oracle Project Resource Management. This rule has the following attributes:

If you are not using advertisement rule functionality, leave the Start Advertisement Rule box selected for each requirement. If a user deselects this box, then the requirement will not be visible in requirement searches or Requirement List pages.

Defining Advertisement Rules

You can optionally define your own advertisement rules.

To define advertisement rules:

  1. Navigate to the Advertisement Rules page.

  2. Choose Create Advertisement Rule.

  3. Enter the name, description, and effective dates. Choose Add Action.

  4. For each action you want to define for the advertisement rule, enter action and condition information and choose Apply. After you apply each action, the Create Advertisement Rule page is displayed with the updated information.

  5. When you have finished entering all actions, choose Apply on the Create Advertisement Rule page to save the entire advertisement rule.

Specifying the Default Advertisement Rule

After you define your advertisement rules, you can specify the default rule on the Staffing tab in the system Implementation Options window.

Users can set advertisement rules at various levels. The value defined at each level is the default value for the next subsequent level. The hierarchy for default values is:

  1. Implementation Options

  2. Project Template

  3. Project

  4. Requirement

You set the overall default advertisement rule in the Implementation Options. When a user creates a project template, the project template retrieves the advertisement rule from the Implementation Options. When a user creates a project, the project advertisement rule is copied from either the project template or from the original project from which the new project is being copied. Any new requirements added to the project also adopt the project advertisement rule.

You can override the default advertisement rule at any of the levels from the project template to the requirement. In addition, you can modify the actions of the advertisement rule on individual requirements without affecting the original default advertisement rule.

Processing Advertisement Actions

An advertisement rule action on a requirement is performed only if the associated condition is met and the advertisement rule status is Started or Resumed. The associated condition for advertisement actions is validated under the following conditions:

Concurrent Program is Run: The concurrent program PRC: Perform Action Rules, set at regular frequency, performs the advertisement actions of the open requirements that have met the associated condition.

Online update is performed: The associated conditions of the actions on a requirement are re-evaluated online if the start date of the requirement is changed or if the advertisement rule on the requirement is updated. The qualified actions are performed if the advertisement rule status is Started or Resumed.

Advertisement Rule is Started or Resumed: When a requirement advertisement rule is first activated or resumed, the system validates the advertisement actions to check if they meet the associated condition. The qualifying actions are performed.

Submitting the PRC: Perform Action Rules Process

The PRC: Perform Action Rules process evaluates the action conditions for each action on a scheduled basis. You should schedule this process to run on a regular basis.

For more information about this process, see: Perform Action Rules., Oracle Projects Fundamentals

Team Templates

A team template contains attributes that you can use to create requirements on a project. If you need to create multiple project teams with similar requirements, you can use team templates to avoid duplicate entry of requirements.

Creating Team Templates

To create a team template:

Note: You must define work types before you can create team templates. See: Defining Work Types.

  1. Navigate to the Team Templates page.

  2. Enter the information for the new team template.

The following table shows selected fields that you complete when you create a team template:

Field Description
Effective Dates The period of time during which a template can be applied to projects (regardless of the project actual start date)
Calendar Default calendar for the requirement
Work Type Default work type for the requirement
Role List The list of roles that you can select for each requirement on the team template. In addition to requirements, you can add subteams to the template that also will be created on a project once the template is applied.

Applying Team Templates

When you apply a team template to a project, the requirements on the template are created on the project.

If the system date falls between the team template effective dates, you can apply the template to a project. You can apply the team template from the Apply Team Template page (accessible through the Schedule Resource page). Or, if your selected project template has an associated team template, then it is applied during the project creation.

If a project has an associated role list, you can apply only team templates with matching role lists to the project. If a project has no associated role list, then you can apply any current team templates to the project.

The process of applying a team template and its associated requirements to a project can take some time. Therefore, an Oracle Workflow process, PA Apply Team Template, handles the application process.

Start and End Dates for Requirements on a Project

The interval between the team template start date and the dates of the template requirements is used to determine the dates of the requirements created on a project. When the team template is applied to a project, the start date for the new requirement is:

The end date for the new requirement is:

Example: You have a team template called Fast Forward Team with a March 1, 1990 start date.

The template has a requirement called DBA with the following attributes:

You apply this template to a project with a start date of June 1, 2006.

The interval from the team template start date (March 1) to the template requirement start date (April 1) is 31 days. The DBA requirement is added to the project with a start date of July 2, 2006 (June 1, 2006 plus 31 days) and an end date of July 31, 2006 (June 1, 2006 plus 60 days).

Staffing Priority Codes

Staffing priority codes on a requirement specify the priority for filling the requirement.

You can select staffing priorities when you add or updat requirements. An assignment retains the staffing priority allocated to the original requirement before it became an assignment (filled requirement).

Defining Staffing Priorities

You use the Oracle Projects Lookups window to define staffing priorities.

To define staffing priorities:

  1. Navigate to the Oracle Projects Lookups window.

  2. Query the lookups for the lookup type STAFFING_PRIORITY_CODE.

  3. Enter the codes you want to add.

  4. For each code, enter a meaning and description.

  5. Select the Enabled box.

  6. Save your work.

For more information on defining and updating lookups in Oracle Projects, see: Oracle Projects Lookups.

Implementing Staffing Workflow and Extensions

You can use the following workflows and client extensions to extend the staffing functionality.

Assignment Approval Workflow

You can use the Assignment Approval Workflow to obtain approvals for a resource assignment. For more information, see: Assignment Approval Workflow Process.

Assignment Approval Workflow Extensions

You can use the following client extensions to extend the functionality of the Project Assignment Workflow:

For details about these client extensions, see: Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.

Candidate Notification Workflow

You can use the Candidate Notification Workflow to send notifications pertaining to candidates. For details, see: Candidate Notification Workflow Processes.

Candidate Notification Workflow Extensions

You can use the Candidate Notification Workflow Extension to extend the functionality of the Candidate Notification Workflow. For details, see: Candidate Notification Workflow Extension, Oracle Projects APIs, Client Extensions, and Open Interfaces Reference.

Implementing Organization Forecasting for Resources

The following instructions give details about the Organization Forecasting for Resources steps in the Oracle Project Resource Management Feature Implementation Checklist.

Oracle Project Resource Management provides an organization forecast process that performs calculations based on your predefined bill and cost rates. These rates are evaluated in the time frame of the assignments, requirements, and scheduled work patterns to provide forecast totals. Predefined bill rates can be overridden for individual requirements and assignments.

Prerequisites for Organization Forecasting for Resources

To generate forecasts totals, you must define information on which the forecasts are based. The following steps are required:

Defining Unassigned Time Tracking

Oracle Project Resource Management automatically generates totals for unassigned time for all utilization jobs. The calculation for unassigned time subtracts both provisional and confirmed assignment hours from the total capacity for each available day. Any remaining hours generated from this calculation are assigned to projects specifically implemented for the purpose of tracking unassigned hours.

To define unassigned time tracking projects, complete the following steps:

  1. Navigate to the Project Types window.

  2. Create a project type using the indirect project type class.

  3. In the Details window, select the following options:

  4. Administrative

  5. Unassigned Time

  6. Create a project template using the unassigned project type. This type of project is used solely for tracking unassigned time for utilization and forecasting calculations. Therefore, users cannot manually add any scheduled roles to this project and the Add Requirement and Add Assignment options are not available for this project.

  7. Create a project using the unassigned project template. Optionally, you can create two unassigned projects: one for billable jobs and one for non-billable jobs.

  8. Complete the options on the Unassigned Time Options tab. For more information, see: Defining Unassigned Time Options.

Forecasting Implementation Options

Use the forecasting implementation options to specify implementation settings for resource scheduling, resource utilization, and organization forecasting.

The forecasting implementation options include:

You define forecast and unassigned time options for each operating unit.

Complete the options according to the guidelines shown in the following table:

Field Description
Operating Unit Select the operating unit for which you are defining forecasting options
Include Administrative Projects Select this box to indicate that you want to include administrative projects in project forecast totals.
You must enable this option to avoid errors because the application does not yet exclude administrative projects.
Maximum Historical Versions Enter the maximum number of historical forecast versions that you want to store. At minimum, you must enter a value of 1. The suggested starting value is 5.
Expenditure Type Class Select the Expenditure Type Class to classify the forecast items.
Expenditure Type Select the Expenditure Type to apply to all generated forecast items.
Transfer Price Amount Type This field is for future use in forecasting functionality.
Job-Based Cost Rate Schedule Select the job-based cost rate schedule for assignments.
Forecast Generation and Display Enter values for forecast generation.

For information about expenditure types and project classifications, see: Expenditure Types and Project Classifications.

Unassigned Time Implementation Options

The Unassigned Time Options page has two regions, one for Billable People and the other for Non-Billable People. You complete the same fields for both regions. The following table shows the Unassigned Time Options fields.

Field Description
Include in Forecast Select this box to indicate that you want to summarize unassigned time in the project financial forecast totals. If you select this option, enter values for the following fields.
Unassigned Time Project Enter the name of the project for reporting of unassigned time.
Expenditure Type Class Specify the expenditure type class for unassigned time.
Expenditure Type Enter the expenditure type for unassigned time.

Implementing Reporting Functionality

The following instructions give details about the Reporting steps in the Oracle Project Resource Management Feature Implementation Checklist.

Implementing Discoverer Reporting

Oracle Project Resource Management transactional reporting is supported by a web based Oracle Discoverer solution. The predefined workbooks, worksheets and End User Layer (EUL) provide you and your users the ability to query and manipulate transactional data to proactively measure and analyze corporate performance.

After you implement the reporting solution, you can access the predefined Oracle Discoverer reports from the self-service Project Resource Management menu structure.

Note: If you want to use the enhanced functionality of Discoverer, set the profile option ICX_DISCOVERER_USE_VIEWER to Yes.

Installation instructions for Oracle Discoverer 4i are available on OracleMetaLink.

Note: To get the maximum benefit of the reporting solution of PJR we recommend that you use Oracle Discoverer 4i.

Oracle Discoverer Post-Installation Tasks

Perform the Discoverer post-installation tasks that correspond to the Discoverer release that you have installed. This section describes post-installation tasks for the following Discoverer releases:

Oracle Discoverer 4i Post-Installation Tasks

For the post-installation tasks titled Import using adupdeul.sh mode = complete and Import using adupdeul.sh mode = driver, you can use one of the following sets of parameters to import all shipped Project Resource Management executable files:

More information about post-installation tasks for Oracle Discoverer 4i is available on OracleMetaLink.

Oracle Discoverer 3i Post-Installation Tasks

Install and set up Oracle Discoverer for integration with Oracle Project Resource Management. To set up the reporting solution, you must use the Administrator Edition or client/server version of Discoverer. To set up the User Edition, you must use the Web Discoverer version, with a few exceptions, which are noted.

Before you start, you must complete the following prerequisites:

  1. Install Oracle Discoverer Administration Edition.

    To access the Discoverer workbooks provided with Oracle Project Resource Management, install Oracle Discoverer.

  2. Install Oracle Web Discoverer.

    For installation instructions, refer to the Oracle Discoverer 3.1 Installation and Administration Guide.

Oracle Discoverer Post-Installation Tasks Checklist

Complete the following tasks:

  1. Create the End User Layer. (EUL)

  2. Modify the End User Layer Owners Indexes.

  3. Copy files to Discoverer Administration Tier.

  4. Connect to Discoverer Administration Edition.

  5. Import the End User Layer EEX File.

  6. Set up access to Business Areas and End User Discoverer Edition.

  7. Refresh Business Areas.

  8. Connect to Discoverer User Edition.

  9. Install the Reporting workbooks.

When you have completed these steps, verify that:

Create the End User Layer

To create the End User Layer (EUL):

  1. Create a database user that you want to designate as the End User Layer owner and grant database access to the user.

  2. Create the application mode EUL.

Creating the Database User: Set the name of the end user layer owner (database user) to EUL_<language> (for example: EUL_US). Use the following script to perform this task:

 create user eul_us 
identified by eul 
default tablespace user_data 
temporary tablespace temp;

Creating the Applications Mode EUL

  1. Issue a set of grants to allow the EUL owner select access to certain Applications Object Library tables. This step is necessary for Discoverer to support the structure of Applications user IDs and responsibilities. To do this, connect to the database using the account specified in the FNDNAM environment variable (typically APPS) and execute the following statements:

    connect system/manager@<database> 
        grant connect, resource to &EULOWNER
connect apps/apps@<database> 
        grant select on FND_USER to &EULOWNER
  grant select on FND_APPLICATION to &EULOWNER
  grant select on FND_USER_RESP_GROUPS to &EULOWNER
  grant select on FND_RESPONSIBILITY_VL to &EULOWNER
  grant select on FND_ORACLE_USERID to &EULOWNER
  grant select on FND_DATA_GROUP_UNITS to &EULOWNER
  grant select on FND_PRODUCT_INSTALLATIONS to &EULOWNER
  grant select on FND_SECURITY_GROUPS_VL to &EULOWNER
  grant execute on FND_CLIENT_INFO to &EULOWNER

  2. Create an Applications mode from the Discoverer Administration Edition.

    An Applications mode EUL is one that can be administered using the Oracle Applications security model in place of the database security model. There are two ways of doing this, both invoking the Administration edition from the command line:

     DIS31ADM.exe /APPS_MODE

    Starts the Administration Edition in Applications mode. Any EULs created will by default be Applications mode EULs.

    DIS31ADM.exe /APPS_MODE /CREATE_EUL /CONNECT eul_owner/password@database

    This command creates an Applications mode EUL from the command line in batch mode.

  3. Note that the EUL owner must be an Oracle database user ID, not an Oracle Applications user ID. The easiest way to create an EUL with a new database user ID as the owner is to log onto the Discoverer Administration edition as the SYSTEM user, and in step two of the Create EUL Wizard choose Create a new user. It is recommended that you create the EUL in a separate schema from the APPS schema that contains the Oracle Applications tables and views. The primary reason for this is that by creating the EUL in a separate schema it is easier to migrate the EUL from test environment to production environment using database import/export.

  4. Next you need to ensure that the EUL owner has select access to the appropriate Applications tables and views where the data is stored. If you are interested in creating Discoverer folders that span multiple tables you may want to grant select any table privilege to the EUL owner. Otherwise, grant select access to just the tables you wish to create Discoverer folders on.

Modify the Indexes of the End User Layer Owner

Complete the following steps from the R11 Admin tier to modify the maximum extents of the indexes in the End User Layer.

  1. Connect to your database server using SQL/Plus as the End User Layer (for example, EUL_US) owner.

  2. At the SQL prompt, enter the following command:

     $BIS_TOP/admin/sql/BISALTIN.sql

Copy Files to Discoverer Administration Tier

To access Discoverer-related files through the Discoverer Administration and End User Editions, you must copy the files to the Discoverer Administration Tier. The file PAPRMEUL.eex is created in the $AU_TOP/discover/<language>/ directory when you install the Oracle Project Resource Management Reporting product.

  1. Copy the file PAPRMEUL.eex from the $AU_TOP/discover/<language>/ directory to an appropriate directory from where it can be imported into the Discoverer Administration Edition.

  2. Copy the sql script BISEULBA.sql from the $BIS_TOP/admin/sql/ directory into the same temporary directory you used in step 1. Optionally, mount the $AU_TOP/discover/<language> directory on to the Discovery Administration Tier.

  3. Copy the Discoverer Workbooks from the $AU_TOP/discover/<language>/ directory to a new directory where they can be saved to the database using the Discoverer User Edition. The workbooks installed are:

    • PASCHRES.dis

    • PAAVLRES.dis

    • PAOVCRES.dis

    • PASALPIP.dis

    • PAREQPRJ.dis

Connect to Discoverer Administration Edition

  1. Log in to the Discoverer Administration Edition in application mode, for example:

    D:\orant\DISCVR31\DIS31ADM.EXE /APPS_MODE

  2. Connect to the database. For example:

     eul_us/eul@cus115

  3. Select File > Set Default EUL.

Import the End User Layer EEX File

The Project Resource Management EEX file must be imported into the Discoverer End User Layer. Select the EUL for which you want the EEX file to be imported, for example, EUL_US.

Note: Before you begin the import process, increase the size of the Rollback Segments to a minimum of 10 megabytes. After the import has been completed, reset the Rollback Segments to their original sizes.

To import the EEX file, complete the following steps:

  1. Open an MS-DOS command window and navigate to the directory in which the EEX file is located. Enter the following commands:

    start /wait <ORACLE_HOME>\discvr31\dis31adm /APPS_MODE /CONNECT
 <EUL_Owner>/EUL_Owner_password>@<Connect_string> /IMPORT paprmeul.eex
 /eul<EUL_Owner_in_uppercase> /log eulimport.log

    Where:

    • <ORACLE_HOME> is the top directory for Oracle products installed on the NT server

    • <EUL Owner> is the database user created above

    • <EUL Owner password> is the database owner password

    • <Connect_string> is SQL*Net database connect string

    • <EUL_Owner_in_uppercase>

    Note: Enter the EUL owner schema in uppercase after the key/EUL when invoking the second command. For example:

    start /wait d:\orant\discvr31\dis31amd /APPS_MODE
 /CONNECT eul_us/eul@apps /IMPORT PAPRMEUL.eex /eul EUL_US
 /log eulimport.log

  2. Check on the progress of the import process by pointing to the Discoverer icon in the right lower corner of your toolbar.

    Inspect the eulimport.log file to ensure that the Project Resource Management EEX file was imported into the End User Layer successfully.

Alternatively, you can log in to the Discoverer Administration Edition and select File > Import. Specify the location of the PAPRMEUL.eex file to complete the import.

Set Up Access to Business Areas and End User Discoverer Edition

You must grant users access to the Discoverer Administrator and User Editions in order for the users to open these applications. However, the users also need user and responsibility access to the Business Areas in order to perform any reporting activities on the Project Resource Management data.

To grant user access to Oracle Discover Administration and User Editions:

  1. Log in to the Discoverer Administration Edition in application mode. For example:

     D:\orant\DISCVR31\DIS31ADM.EXE/APPS_MODE

  2. Select Tools > Privileges.

  3. Select the user/responsibility (role) to which you need to grant access, for example, Project Resource Management Super User.

  4. Grant the responsibility either the User Edition or the Administration Edition access.

    Note: If this responsibility is not a Self-Service responsibility, it cannot be accessed through the Self-Service logon.

To grant user/responsibilities access to Business Areas:

  1. Log in to the Discoverer Administration Edition in application mode. For example:

     D:\orant\DISCVR31\DIS31ADM.EXE/APPS_MODE

  2. Select Tools > Security.

  3. Select the user/responsibility (role) to which you need to grant access, for example, Project Resource Management Super User.

  4. Select the business areas to which you want to grant this user/responsibility access.

  5. Check the Allow Administration checkbox for the business areas if this responsibility needs administration access for tasks such as Refresh from the database.

Refresh Business Areas

The following steps synchronize the information in the Discoverer End User Layer and the underlying Oracle Applications data model.

  1. Connect to Discoverer Administration Edition by invoking from the command line:

     D:\orant\DISCVR31\DIS31ADM.EXE /APPS_MODE

  2. Connect to the database as an application user. For example:

    SERVICES:Project Resource Management Super User:Standard
/welcome@cus115

  3. Set Default EUL.

  4. Select all your business areas.

  5. Select File > Refresh

  6. Verify that the folders refresh is successful.

Connect to Discoverer User Edition

To invoke Discoverer User Edition:

  1. Log in to the Discoverer User Edition in application mode. For example:

     \orant\DISCVR31\DIS31USR.EXE

  2. Connect to the database. For example:

    SERVICES:Project Resource Management Super User:Standard
/welcome@cus115

  3. Select Tools > Options.

  4. Select the EUL tab and check the default EUL. For example, EUL_US.

Install the Project Resource Management Reporting Workbooks for Discoverer

The following steps explain how to save the workbooks to your database so that users can access the workbooks through Oracle Web Discoverer.

  1. Log in to the Discoverer User Edition in application mode. For example:

     D:\orant\DISCVR31\DIS31USR.EXE

    For login information, select Cancel.

  2. While in Discoverer 3.1 User Edition, select Tools > Options and ensure that the check box labeled Display warning when opening workbook saved in a different database account is checked.

  3. Exit the Discoverer User Edition.

  4. To save the Discoverer workbooks from the temporary staging area to the database, open an MS-DOS window and change directories to the staging area where the workbooks were saved. Refer to the section To copy files to the Discoverer Administration Tier for more information.

  5. Execute the following command from the command prompt:

    start /wait for %%f in (*.dis) do
<ORACLE_HOM>\discvr31\dis31usr /connect "<EUL_Owner>"
/EUL_Owner_password>@<Connect_string> /savedb %%f /batch

    For example:

    start /wait for %%f in (*dis) do
c:\orant\discvr31\dis31usr /connect"SERVICES:Project Resource 
Management Super User:Standard/welcome@apps /savedb %%f /batch

    Note: Use quotation marks when you enter the EUL_Owner parameter in the command string.

Alternatively, log in to the Discoverer User Edition and select File > Open > My computer. Specify the location of the workbook file. After the workbook opens, select File > Save As > Database to save the workbook in the database. You must repeat this step for all workbooks.

After the workbooks are saved in the database, change the EUL Owner (eul_us) End User Layer (eul) password from the default password.

Set Up Access to the Reporting Workbooks

The following steps instruct you on how to set up access to Discoverer workbooks through the Discoverer User Edition.

  1. Log in to the Discoverer User Edition in application mode. For example:

     D:\orant\DISCVR31\DIS31USR.EXE

  2. Open the workbook to which you need to grant other users/responsibilities access.

  3. Select File > Manage Workbooks > Sharing.

  4. Select the User > Workbook tab.

  5. Select the user/responsibility to grant access.

  6. Select the workbooks you want to grant access to and move them to the Shared section of the Share workbook dialog box.