Introduction
The CHRS ePerformance Configuration Guide is provided to describe the setup tables and values needed to successfully implement ePerformance for your campus.
This guide contains snapshots of the PeopleSoft web pages reviewed during the HCM 9.2 PUM 30 Fit Gap sessions, along with a brief description of any issues and /or recommended approaches for the table setups. In addition to this documentation, please refer to the appropriate sections in PeopleBooks for additional details for configuring and maintaining the HCM product.
If a campus has a need to update ePerformance tables manually they should LOG A HELP DESK TICKET and report the issue to CMS.
In general, the CHRS ePerformance Configuration Guides should be setup in the following order:
Below are examples of how list of Tables are displayed for each Setup Task:
Tables for DMS
The following tables are configured through use of this guide. The chart below is being provided as a quick reference for listing the contents of the guide, as well as defining table ownership.
| Sample Table for DMS | |
| Frequency: One-time or Ongoing |
Owner: CMS |
| Table Name | Description |
|
EP_INSTALLATION |
|
| EP_INSTALL_TERM | |
| EP_ALERT_DTLS | |
1.0 Install
1.1 Products
- Specify the PeopleSoft applications for your installation. The installation table controls which products are active and which features are activated for those products.
- Navigation: Menu > Set Up HCM > Install > Installation Table > Products tab
1.2 Product Specific
- Enter product- and industry-specific installation information.
- Navigation: Menu > Set Up HCM > Install > Product Specific > ePerformance Installation
- Click on eperformance Tab at top of page
| Table for DMS | |
| Frequency: One-time |
Owner: CMS |
| Table Name |
Table Name |
|
EP_INSTALLATION |
|
| EP_INSTALL_TERM | |
| EP_ALERT_DTLS | |
| EP_NOTIFY_DTLS | |
| EP_INSTAL_MGR_X | |
| EP_INSTAL_EE_X |
Additional Information
- Please refer to the General Tables Configuration guide for more detailed information on the other features of this page.
2.0 Common Definitions
This section is used to setup tables under Common Definitions. It is used by CSU programs to identify the campus specific information and options. This is a system wide setup. Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
2.1 Generic Templates
- Navigation: Menu > Set Up HCM > Common Definitions > Approvals > Generic Templates
- Field Information
| Field Information | ||
|
Field / Owner Enter field / owner info |
Description Enter description of what the field is used for. |
Values Enter recommended values or processes |
|
Recent Searches |
Choose from recent searches | |
| Saved Searches | Choose from saved searches | |
| Search by: Template Name begins with | ||
| Show fewer options | Case Sensitive checkbox | |
| Table for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name (PS Name) |
Description |
|
WL_TEMPL_GEN_RS |
|
| WL_TEMPL_GEN_TK | |
| WL_TEMPLATE_GEN | |
| WL_TEMPLATE_GLN | |
2.2 Configure Direct Reports UI
- The Direct Reports UI is to identity the Employee Manager Relationship. Only setup relevant to ePerformance was updated to identify the Employee Manager Relationship.
- This is setup at the system level. Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses
- Navigation: Menu > Set Up HCM > Common Definitions > Direct Reports for Managers > Direct Reports for UI
- The Component names that start with EP_ are relevant for ePerformance.
| Table for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name (PS Name) |
Description |
|
HR_DR_UI_CFG |
|
| SS_LINK_TBL | |
2.3 Group Build - Group Definition
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- The System admins will need to work with the campus to create group build queries and align them with the group definition IDs.
- Navigation: Menu > Set Up HCM > Common Definitions > Group Build > Group Definition
| Table for DMS | |
|
Frequency: Ongoing |
Owner: CMS |
|
Table Name (PS Name) |
Description |
|
GB_GROUP_TBL |
|
| GB_WHERE_TBL | |
| GB_VALUES_TBL | |
| GB_VERSION_MGMT | |
| GB_GRP_INC_EXC | |
| GB_FROMCRIT_TBL | |
2.4 Group Security Default
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- The System admins will need to work with the campus to create group definition IDs and grant security to campus users so that campus Admin users can use ePerformance related functionality for creating documents and running reports for group IDs.
- Navigation: Menu > Set Up HCM > Common Definitions > Group Build > Group Security Default
- This is system default. No changes need to be done on this page.
2.5 Security by Group
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- The System admins will need to work with the campus to create group definition IDs and grant security to campus users so that campus Admin users can use ePerformance related functionality for creating documents and running reports for group IDs.
- Navigation: Menu > Set Up HCM > Common Definitions > Group Build > Security by Group
| Table for DMS | |
|
Frequency: Ongoing |
Owner: CMS |
|
Table Name (PS Name) |
Description |
|
GB_SECGRPOPR_TB |
|
| GB_SECPNLG_TBL | |
| GB_PNLGRDFT_TBL | |
2.6 Security by Operator
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- The System admins will need to work with the campus to create group definition IDs and grant security to campus users so that campus Admin users can use ePerformance related functionality for creating documents and running reports for group IDs
- Navigation: Menu > Set Up HCM > Common Definitions > Group Build > Security by Operator
2.7 Configure HR Notepad
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- This is a one-time setup and should not be changed. Only the 2 rows related to ePerformance were configured.
- Navigation: Menu > Set Up HCM > Common Definitions > Text Catalog and Notepad > Configure HR Notepad
| Table for DMS | |
| Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
HR_NP_CONFIG |
|
| HR_NP_CONFIG_LK | |
| HR_NP_CFG_KEYS | |
2.8 Maintain Text Catalog
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- The System admins can make changes as necessary.
- Navigation: Menu > Set Up HCM > Common Definitions > Text Catalog and Notepad > Maintain Text Catalog
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
HR_SSTEXT_EFFDT |
|
| HR_SSTEXT_MSGID | |
| HR_SSTEXT_TEXT | |
2.9 Configure Simple Person Search
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- This is a one-time setup and should not be changed. Only rows related to ePerformance were configured. Object owner ID is HEP.
- Navigation: Menu > Set Up HCM > Common Definitions > Person Search Match > Configure Simple Person Search
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
HR_PSS_CONFIG |
|
2.10 Direct Reports Pagelet Setup
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- Navigation: Menu > Set Up HCM > Common Definitions > Manager Dashboard > Direct Reports Pagelet Setup
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
UX_APPR_PLT_CFG |
|
| UX_APPR_PLT_TXN | |
| UX_DIR_PLT_CFG | |
| UX_DIRECTS | |
2.11 Installation Settings
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- This is a one-time setup and should not be changed. This setup is related to time-based email reminder notifications for courtesy, warning and critical reminders.
- Navigation: Menu > Set Up HCM > Common Definitions > HR Notification > Installation Settings
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
HCSC_NOTIF_INST |
|
| HCSC_ANN_ROLE | |
| HCSC_NTF_ACCESS | |
2.12 Notification Recipient Setup
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- This is a one-time setup and should not be changed.
- Navigation: Menu > Set Up HCM > Common Definitions > HR Notification > Notification Recipient Setup
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
HCSC_RECIPIENT |
|
| HCSC_RCPNT_ROLE | |
| HCSC_RCPNT_LOOK | |
| HCSC_RCPNT_LIST | |
2.13 Define Notification Category
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- This is a one-time setup and should not be changed.
- Navigation: Menu > Set Up HCM > Common Definitions > HR Notification > Notification Recipient Setup
2.14 Configure Embedded Link
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- This is a one-time setup and should not be changed. We are currently not using this setup.
- Navigation: Menu > Set Up HCM > Common Definitions > HR Notification > Configure Embedded Link
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name (PS Name) |
Description |
|
HCSC_LINK_SETUP |
|
2.15 Assign Embedded Links
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- This is a one-time setup and should not be changed. We are currently not using this setup.
- Navigation: Menu > Set Up HCM > Common Definitions > HR Notification > Assign Embedded Links
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
HCSC_LINK_ASSIG |
|
2.16 Configure Email Template
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- This is a one-time setup and should not be changed.
- Navigation: Menu > Set Up HCM > Common Definitions > HR Notification > Configure Email Template
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
HCSC_NOTIF_TMPL |
|
| HCSC_TMPL_ROLE | |
| WL_TEMPLATE_GEN | |
2.17 HR Notification
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- This is a one-time setup and should not be changed.
- Navigation: Menu > Set Up HCM > Common Definitions > HR Notification > HR Notification
| Tables for DMS | |
|
Frequency: Ongoing |
Owner: CMS |
|
Table Name |
Description |
|
HCSC_NOTIF |
|
| HCSC_NOTIF_TO | |
| HCSC_NOTIF_CC | |
| HCSC_NOTIF_BCC | |
| HCSC_RCPNT_LIST | |
| HCSC_NOTIF_LINK | |
| HCSC_NOTIF_ATCH | |
| HCSC_NOTIF_RCPT | |
2.18 Process Notifications
- Informational for CO only. Campus does not have access to change set up. Configuration is the same for all campuses.
- This is a one-time setup and should not be changed. This will process the 33 notifications that are defined for ePerformance. They need to be run on a daily basis.
- Navigation: Menu > Set Up HCM > Common Definitions > HR Notification > Process Notifications
3.0 Product Related
- The system users will work with the campus to create the necessary content items (mostly competencies) that will be used on the profile setup that will be integrated with ePerformance Content Items.
- Navigation: Menu > Set Up HCM > Product Related > Profile Management > Content Catalog > Content Items
| Tables for DMS | |
|
Frequency: Ongoing |
Owner: CMS |
|
Table Name |
Description |
|
JPM_CAT_ITEMS |
|
| JPM_CAT_ITEM_RD | |
| JPM_CAT_T_RLAT | |
| JPM_CAT_I_RLAT | |
| JPM_CAT_GMEMB | |
3.1 Rating Model
- The rating model is used for competency rating and overall performance rating.
- Navigation: Menu > Set Up HCM > Product Related > Profile Management > Content Catalog > Rating Model
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
RATING_MDL_TBL |
|
| REVW_RATING_TBL | |
3.2 Custom Prompt
- The custom prompt is used to add drop down values for items within a section in a performance document. (Goals can be identified as current year or next year on the goals/items).
- Navigation: Menu > Set Up HCM > Product Related > Profile Management > Profiles > Custom Prompt
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
JPM_C_LIST_DEFN |
|
| JPM_C_LIST_ITEM | |
3.3 Profile Actions
- We are currently using limited functionality for Profile setup.
- Navigation: Menu > Set Up HCM > Product Related > Profile Management > Profiles > Profile Actions
3.4 Profile Types
- We are using Non Person profile type. This is used to create non person profiles for different groups for storing competencies for different groups
- Navigation: Menu > Set Up HCM > Product Related > Profile Management > Profiles > Profile Types
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
JPM_JP_PROPS |
|
| JPM_JP_ROLES | |
| JPM_JP_SECTION | |
| JPM_JP_TAB | |
| JPM_JP_TYP_PAOS | |
| JPM_JP_TYP_PIDS | |
| JPM_JP_TYPES | |
3.5 Assign Default Profile Type
- We are setting up Primary Person profile and Primary Non Person Profile. These are system defaults.
- Navigation: Menu > Set Up HCM > Product Related > Profile Management > Profiles > Assign Default Profile Types
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
JPM_JP_PRI_TYPE |
|
3.6 Template Definition
- The template setup is used to create annual, Probationary and PIP review documents.
- Navigation: Menu > Set Up HCM > Product Related > ePerformance > Document Structure > Template Definition
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name (PS Name) |
Description |
|
EP_TMPL_DEFN |
EP_TMPL_DEFN WHERE EFFDT = '2020-01-01' |
| EP_TMPL_ITEM | EP_TMPL_ITEM WHERE EFFDT = '2020-01-01' |
| EP_TMPL_PARTIC | EP_TMPL_PARTIC WHERE EFFDT = '2020-01-01' |
| EP_TMPL_ROLE | EP_TMPL_ROLE WHERE EFFDT = '2020-01-01' |
| EP_TMPL_ROLE_EC | EP_TMPL_ROLE_EC WHERE EFFDT = '2020-01-01' |
| EP_TMPL_SECTION | EP_TMPL_SECTION WHERE EFFDT = '2020-01-01' |
| EP_TMPL_SUBITEM | EP_TMPL_SUBITEM WHERE EFFDT = '2020-01-01' |
| EP_TMPL_CHECKPT | EP_TMPL_CHECKPT WHERE EFFDT = '2020-01-01' |
| EP_TMPL_ROLE_TP | EP_TMPL_ROLE_TP WHERE EFFDT = '2020-01-01' |
| EP_TAB_DTL | EP_TAB_DTL WHERE EFFDT = '2020-01-01' |
3.7 Document Types
- The document type setup is used to define the default usage for annual, Probationary and PIP review documents.
- Navigation: Menu > Set Up HCM > Product Related > ePerformance > Document Structure > Document Types
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
EP_REVW_TYP_TBL |
|
3.8 Participant Roles
- Participant roles are setup for 360 Participant and Previous Manager roles. Employee and Manager roles are delivered by PeopleSoft
- Navigation: Menu > Set Up HCM > Product Related > ePerformance > Document Structure > Participant Roles
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
EP_ROLE_TBL |
|
3.9 Section Defintion
- The section definition setup is used in the template for creating the performance review document.
- Navigation: Menu > Set Up HCM > Product Related > ePerformance > Document Structure > Section Definition
| Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
EP_SECTION_DEFN |
|
3.10 Assign Document Defaults
- This setup needs to be changed every year to define the ePerformance begin and end dates.
- Navigation: Menu > Set Up HCM > Product Related > ePerformance > Document Structure > Assign Document Defaults
|
Tables for DMS | |
|
Frequency: One-time |
Owner: CMS |
|
Table Name |
Description |
|
EP_DEFAULT |
|
4.0 Workforce Development
- This section is used to setup tables under Workforce Development. It is used by CSU programs to identify the campus specific information and options. The campus does not have access to these pages.
- The system admins will work with the campus admins to identify the content items (competencies) for each JOB profile for each unique group. Currently the items are identified by Position. This integrates with the Performance document to integrate the correct items (competencies) on the user's performance review document. Job Profiles
- Specify the PeopleSoft applications for your installation. The installation table controls which products are active and which features are activated for those products.
- Navigation: Menu > Set Up HCM > Workforce Development > Profile Management > Non-person Profiles > Job Profiles
| Tables for DMS | |
|
Frequency: Ongoing |
Owner: CMS |
|
Table Name |
Description |
|
JPM_PROFILE |
|
| JPM_JP_CAT_TYPE | |
| JPM_JP_ITEMS | |
| JPM_JP_X_RLAT | |
5.0 Enterprise Components – Events and Notifications
5.1 Event Registry
- We are using delivered functionality. The events are set to active. They are used to trigger the cancel document functionality for terminated employees (that have an active document) and for transfer documents for termed managers (that have an active document).
- Navigation: Menu > Enterprise Components > Events & Notifications > Event Framework > Event Registry
End of Article
0 Comments
Add your comment