Setting Up Program Management Control Data

This chapter provides overviews of general control data and project request options, and discusses how to:

• Set up general control data.

• Set up project request options.

Understanding General Control Data

This section provides an overview of general control data and change control templates.

General Control Data

Program Management control data consists of optional information—releases, applications, application areas, and categories—that you can use to further classify new programs, projects, or project requests. Applications identify a module or specialty within a software product. Application areas group similar applications together. Categories further classify a project or project request. For example, you can use categories to identify strategic projects from operational ones.

Control data also consists of setup information required to create new issues and risks.

Change Control Templates

Program Management provides you with the ability to track changes to projects and budgets. A change control template defines the level of control for attributes that are to be monitored. You can select which changes to track, whether they require a reason for the change, and whether a formal change request is required. You assign a default template at the business unit level, but it can be overridden at the project or activity level.

Understanding Project Request Options

This section provides an overview of project request options.

Project Request Options

The project request options establish which records to use for various prompt tables, control how project request IDs are generated, define discount rates and currency conversion rate types, establish identifiers that map each type of project initiative to a project owner, establish project request priorities, and specify which users can edit project request data.

Note. If you intend to install and use Project Portfolio Management in conjunction with Program Management, users enter, update, review, and approve project requests in the Project Portfolio Management application in the PeopleSoft EPM database. In this case, you do not need to set up the project request options in the PeopleSoft Financials database for Program Management. Instead, you set up the project request options in the Project Portfolio Management application. For instructions regarding the setup of project request options that are in the EPM database, refer to the PeopleSoft Enterprise Project Portfolio Management PeopleBook.

Setting Up General Control Data

To set up general control data, use these components:

• Change Control Management (PC_CHC).

• Issue Priorities (PC_IM_PRIORITY).

• Issue Status (PC_IM_STATUS).

• Issue Types (PC_IM_TYPE).

• Project Category Setup (PGM_CATEGORY_SETUP).

• Application Area Setup (PGM_APPLAREA_SETUP).

• Application Setup (PGM_APPLICAT_SETUP).

• Project Risk Type (PGM_RISK_TYPE).

• Release Type (PGM_RELEASE_TYPE).

• Release Management (PGM_RELEASE).

• Root Cause Area Setup (PGM_RCA_SETUP).

This section discusses how to:

• Define change control templates

• Define issue priorities

• Define issue statuses

• Define issue types

• Define categories

• Define application areas

• Define applications

• Define project risk types

• Define release types

• Define releases

• Define root cause areas

Pages Used to Set Up General Control Data

Defining Change Control Templates

Access the Change Control Template page.

Use this page to specify which change control attributes are to be monitored and to what extent. Options for the fields on this page are:

Defining Issue Priorities

Access the Issue Priority page.

Program Management delivers issue priority values of HIGH, MEDIUM, and LOW. Add a new row on this page to inactivate a priority or enter a different priority description.

Select a Description value of High, Medium, or Low for the priority that you are defining. You can select these priorities when you enter or edit an issue using the Issue page.

Issue priorities are represented by these colored visual indicators when issues appear on pagelets:

See Also

Using Pagelets Enabled by Program Management

Defining Issue Statuses

Access the Issue Status page.

The statuses that you define on this page are available for selection when you enter or edit an issue using the Issue page. You must define issue statuses before you can enter an issue. Enter the effective date, status, and description for the issue status. You can select from only active issue statuses when you create an issue.

Defining Issue Types

Access the Issue Type page.

The issue types that you define on this page are available for selection when you enter or edit an issue using the Issue page. You must define issue types before you can enter an issue. Enter the effective date, status, and description for the issue type. You can select from only active issue types when you create an issue.

Defining Categories

Access the Category page.

The categories that you define on this page are available for selection when you create or edit a project using the Project Definitions - General Information page. Enter the status and description for the category.

Defining Application Areas

Access the Application Areas page.

The application areas that you define on this page are available for selection when you create or edit a project using the Project Definitions - General Information page. Specify the status and description for the application area. You can select from only active application areas when you create applications.

Defining Applications

Access the Application page.

The application that you define on this page are available for selection when you create or edit a project using the Project Definitions - General Information page.

Define Risk Types

Access the Project Risk Types page.

Specify the description and status for the project risk type. You can select from only active project risk types when you create risks.

Define Release Types

Access the Release Type page.

Specify the status and description for the release type. You can select from only active release types when you define a release.

Define Releases

Access the Release page.

Release Manager	Enter the employee ID of the person responsible for managing this release.
Release Status	Select the status of this release from these options: Active: Indicates that this is a current release. This is the default status for new releases. Inactive: Indicates that this is an old or cancelled release that remains in the system for historical purposes. Pending: Indicates that this is an upcoming release. Note. For all of the online pages containing release information, the system displays only active or pending releases.
Original Release Date	Enter the date on which this release is due. If the release date changes, enter the revised release date into the Current Target Release Date field.
Current Target Release Date	Enter the revised target release date. For a new release, the default value for this field is the current date. For all of the online pages containing release information, the system displays the current target release date.
Release Type	Enter the type of release. You must define release types on the Release Type page before you can select a release type for a release.
Additional Fields	Click to access the Release Additional Fields page and enter additional information. The fields on the Release Additional Fields page are user-defined fields for informational purposes only.

Attachments

Defining Root Cause Areas

Access the Root Cause Area Setup page.

You can specify a root cause area for informational purposes when you enter a project change request or a budget change request. Enter the root cause area description and status.

Setting Up Project Request Options

To set up project request options, use these components:

• Setup Prompt Tables (BC_GENERAL_PREF)

• Initiative Type Mapping (PPK_INITYPE_TBL)

• Setup Priority (PPK_PRIORITY_UPD)

• Project Request - Setup Update (BC_PROJ_ROL_ST)

• Project Request - Setup View (BC_PROJ_ROL_ST_VW)

This section discusses how to:

• Define prompt tables for department and account data.

• Define how the system generates project request IDs.

• Define the discount rate.

• Define the currency conversion rate type.

• Define initiative types.

• Define project request priorities.

• Define project request edit privileges.

• View edit privileges.

Pages Used to Set Up Project Request Options

Defining Prompt Tables for Department and Account Data

Access the Setup Prompt Tables page.

Department Prompt Table

Select the PeopleSoft record name that contains department data. The system uses this record as a prompt for valid department values on the Cost and Benefit pages of the Project Request component (BC_PROJ_REQUEST). Selecting the record that accurately depicts the department hierarchy as defined within the general ledger business unit is critical. The record that you enter must be keyed by setID and contain a DESCR field. Note. Program Management is delivered with the value DEPT_TBL in this field. Most organizations accept this value, which is the standard department record that is used in the Financials database by all of the PeopleSoft Financials applications.

Account Prompt Table

Select the table that contains account data. The system uses this table as a prompt for valid account values on the Cost and Benefit pages of the Project Request component. Selecting the table that accurately depicts the account hierarchy as it's defined within the general ledger business unit is critical. The table must be keyed by setID and contain a DESCR field. Note. Program Management is delivered with the value GL_ACCOUNT_TBL in this field. Most organizations accept this value, which is the standard account record that is used in the Financials database by all of the PeopleSoft Financials applications.

Defining How the System Generates Project Requests IDs

Access the Project Request ID Sequencing page.

Project Request ID Sequencing

Overrides

Complete this grid to specify different project request ID prefixes for individual business units. Sequence numbers increase by one across all business units; only the prefix can differ. This grid is unavailable for entry when the sequence type is set to Manually Entered.

Defining the Discount Rate

Access the Discount Rate page.

Effective Date	Enter the date on which the discount percentage goes into effect. This allows you to change over time the rate at which the organization discounts cash flows.
Discount% (discount percentage)	Enter the rate that the system can use to discount the project request cost and benefit amounts to calculate financial metrics. This rate is not currently used in the delivered Program Management interactive reports or project request.

Defining the Currency Conversion Rate Type

Access the Conversion Rate Type page.

Rate Type

Select the rate type to use for currency conversions that occur within the Project Request component, and for conversions that are completed by using the Process Currency Conversions page.

Defining Initiative Types

Access the Initiative Type Mapping page.

Initiative Type ID	Displays the unique identifier for the initiative type.
Owner ID	Select the individual that is associated with this initiative type.

When you create project requests, you can associate them with an initiative type.

Defining Project Request Priorities

Access the Setup - Priority Description page.

Five priority levels and their corresponding descriptions are delivered in Program Management, but you can modify the descriptions to suit your implementation. These descriptions are the valid priorities that appear in the Priority drop-down list box that is on the Project Request page.

Defining Project Request Edit Privileges

Access the Privileges for Project Request page.

Edit Page	Select to permit this role to edit a project request when it is in the status that is listed in the current row. When this option is not selected, the role has view access only. Note. Use the sample data that is delivered with the Program Management application as a guideline for how you should establish edit privileges for the various roles that participate in the project request entry and approval business process. The key roles to consider emulating in the implementation are Project Requester, Project Owner, Project Manager, and Manager.
View Privileges for All Roles	Click to access the Privileges for Project Request page on which you can view a list of roles with their defined privileges. The list only displays roles for which you have defined privileges.
Delete Privileges of this Role	Click to delete this role's edit privileges.

See Also

Establishing Project Requests

Viewing Edit Privileges

Access the Privileges for Project Request - Role Selection page.

This page displays currently defined roles and their edit privileges, based on the project request status value. Users can add a role or modify an existing privilege definition.

Note. Use PeopleSoft security for limiting access to this page to the appropriate users within the organization.