PeopleTools

PeopleSoft PeopleTools related articles.

PeopleSoft Object Type List

Below is a complete list of all PeopleTools object types with value number and description.

VALUE   DESCRIPTION
0       Record
1       Index
2       Field
3       Field Format
4       Translate Value
5       Page
6       Menu
7       Component
8       Record PeopleCode
9       Menu PeopleCode
10      Query
11      Tree Structure
12      Tree
13      Access Group
14      Color
15      Style
16      Business Process Map
17      Business Process
18      Activity
19      Role
20      Process Definition
21      Process Server Definition
22      Process Type Definition
23      Process Job Definition
24      Process Recurrence Definition
25      Message Catalog
26      Dimension
27      Cube Definition

Unlock PeopleSoft Objects All at Once (Change Control Locking)

Change control is used in Application Designer to lock definitions and track history changes for each object. Change control can be activated through Application Designer using Tools > Change Control > Administrator.

After few good size projects, you can easily have hundreds if not thousands of locked objects. Attempting to unlock the objects one by one is very time consuming, so here is a way to speed up the process.

Locked objects are stored on PSCHGCTLLOCK table. Here is how PeopleSoft describes the table:

PeopleSoft Object Types Definitions

PeopleSoft stores object definitions types such as Record, Field and SQL definitions as numbers in PeopleTools meta-tables. Here is a list of what each number means with respect to its definition.

Definitions for Record Object Types

The following are stored on the PSRECDEFN table on RECTYPE field.
RECTYPE = 0
Corresponds to: SQL Table
Comments: The record will be built as an actuall database table.

Records used in Tree Manager in HCM

Below given are the important records used in the tree manager.

PSTREEDEFN - Tree Definition and Properties
PSTREEDEFNLEVELS -- Tree Levels
PSTREEBRANCH -- branches of the tree
PSTREENODE -- Contains the nodes of the tree
PSTREELEAF
PSTREELEVEL

Compare Report in CSV or HTML format

Click here -> Compare Report in HTML format to see how you can generate compare reports in HTML or CSV format.

PeopleSoft PeopleTools Meta-Tables

This is an attempt to list PeopleSoft meta-tables along with some kind of description for every table. The list will be broken into categories (pages, records, components, and so forth). Please feel free to add to or correct the list, this is a wiki page, so jump in!

PeopleSoft Projects

PSPROJECTDEFN table stores information about projects created in Application Designer.
Try it out:

SELECT * FROM PSPROJECTDEFN
WHERE PROJECTNAME = 'Your_Project_name';

Security Tables

PSOPRDEFN - UserIds created.
PSCLASSDEFN - Permission List definition.
PSROLEDEFN - Role Definition table
PSAUTHITEM - Menus, Components and Pages attached to a permission list.
PSROLEUSER - Contains user and role mapping.
PSROLECLASS - Role Permission List mapping.

PSAUTHBUSCOMP -- Component Interfaces Permissions
PSAUTHCHNLMON - Message Channels tagged to any particular PLs
PSAUTHMP - Mobile Pages tagged to a particular Permission List

PSUSERATTR
PSUSEREMAIL
PSOPRALIAS
PSOPRALIASTYPE
PSOPRALIASFIELD
PSROLECANGRANT
PSAUTHCUBE
PSAUTHOPTN
PSAUTHPRCS
PSAUTHSIGNON

Bypass Component Search Page

We can bypass the component search page in different ways.
1. One way is to set the key values using peoplecode and use the peoplecode function SetSearchDialogBehavior. You can write the code in the SearchInit PeopleCode. Suppose Employee Id is the only key, then the code will look like,

EMPLID = %EmployeeId;
SetSearchDialogBehavior(0);

2. There is another method of using a record with no keys as the component search record. This will also bypass the search.

Based on the requirement you can use any of the above methods.

Dynamic View and Drop Down Menu

This was kind of interesting to figure out. What I was going after is the following. I had a drop down box on a page that shows some Business Units. The values however need to be dynamic and change depending on the user viewing/accessing the page.

For example, user1 should only see 52024, 12456 but user2 should be allowed to see 52024, 12456, 45648, and 10235.

To accomplish this I've created a table to store values for each user (lets call it TABLE_1). TABLE_1 has 2 fields (oprid, and business_unit). So now, we have 2 users on the table along with their associated business units.

The 2nd step is to create the dynamic view to pull business units specific to each user. The view will only have one field and that is the business_unit field.

record view

PeopleSoft PeopleTools Meta-Tables

THE CONTENT OF THIS PAGE HAS BEEN MOVED TO A NEW WIKI STYLE PAGE.