PeopleSoft Learning

Customers using functionality that does a lot of processing in Java (for example, XMLPublisher) should consider setting the JVM options for the application server. The default JVM options may not be optimal. In that case, we recommend adding the following setting to psappsrv.cfg or psprcs.cfg (in addition to the already existing options):
-server -Xms128m -Xmx512m

The benefits of PSAESRV versus PSAE are a popular topic of discussion. Our studies have shown that PSAE is as good as
PSAESRV for most practical purposes.
If you have an application engine job that runs longer than 10 seconds, PSAE is equivalent to PSAESRV. PSAE has the added
advantage of being recycled at the end of each application engine job, cleaning up any outstanding SQL cursors to the database
that may have been left behind. Because PSAE recycles after each use, PSAE does not have any possible memory leakage
problem that may occupy the precious system memory. In short, PSAE is a cleaner workhorse.
To shutdown PSAESRV, when you configure the Process Scheduler, you can change the default of the PSAESRV instance to 0.
Values for config section - PSAESRV
Max Instances =0
Recycle Count=1000
Allowed Consec Service Failures=2

Here's a summary of the run status translates (from PeopleTools 8.49). Note that not all of these are active.
Value Status
1 Cancel
2 Delete
3 Error
4 Hold
5 Queued
6 Initiated
7 Processing
8 Cancelled
9 Success
10 Not Successful
11 Posted
12 Unable to Post
13 resend
14 Posting
15 Content Generated
16 Pending
17 Success with Warning
18 Blocked
19 Restart

Base Benefit Tables

PS_BEN_PROG_PARTIC - EE Benefit program participation.
PS_BENEFIT_PARTIC - Ben Plan type enrollment control
PS_BENEF_COMMENT - Benefit Comments

Dependent Details table

PS_DEPENDENT_BENEF - View Dependents/Beneficiaries
PS_DEP_BEN - EE Dependents/Beneficiaries
PS_DEP_BEN_EFF - EE Dependents Details EFFDT
PS_DEP_BENEF_VW - EE Dependent Only View
PS_DEP_BEN_ADDR - EE Dependent Address details
PS_BEN_NAME - EE Dependent Name
PS_DEP_BENEF_NID - Dependent / Benef National ID s
PS_DEPENDENT_PHONE - Dependent/Benef Phone Numbers

Health Plan Tables – Plan types – 1%

PS_HEALTH_PLAN_TBL - Health Plan Attributes Table
PS_HEALTH_PLAN_VW - Health Plans types View with its long descr plan type LIKE ‘1%’
PS_HEALTH_PLAN_LNG - Health Plans types view with its long descr lng plan type like ‘1%’

PS_HEALTH_BENEFIT - Health Benefits EE Elections
PS_HEALTH_DEPENDNT - Health Benefits EE Dependent Elections

PS_HEALTH_VW - EE Current Health Elections

Savings Plan Tables – Plan types - 4%

PS_SAVINGS_PLN_TBL -Savings Plan Attributes Table.
PS_SAVINGS_INV_TBL - Describing a specific investment option
Available within a Savings Plan type.
PS_ SAVINGS_PLN_VW -Savings Plan types view with its long description

PS_SAVINGS_PLAN -Savings Plan Enrollment Table.
PS_SAVINGS_BENEFIC -Savings Plan Beneficiaries.
PS_SAVINGS_INVEST -Savings Plan Enrollment Investment option.
PS_SAVINGS_PLAN_VW -Savings Plan Enrollment view

Life Plan Tables – Plan types - 2%

PS_LIFE_ADD_TBL -Life AD/D Ben Plan Parameters
PS_LIFE_PLAN_VW -Life AD/D Plan type views

PS_LIFE_ADD_BEN -EE Life AD/D Benefit Enrollment
PS_LIFE_ADD_BENEFC -EE Life AD/D Beneficiaries
PS_LIFE_VW -EE Current Life AD/D Benefits

FSA Plan Tables – Plan types - 6%

PS_FSA_BENEF_TBL -FSA Benefit Plan Parameters
PS_FSA_PLAN_VW -FSA Plan Type with its long description.

PS_ FSA_BENEFIT -EE FSA Benefit Enrollment View
PS_FSA_BENEFIT_VW -EE FSA Benefit Enrollment View

Retirement Plan Tables – Plan Types – 7%

PS_RTRMNT_PLAN_TBL -Retirement Plan Attributes Table
PS_RTRMNT_PLAN_VW -Retirement Plan types view

PS_RTRMNT_PLAN -EE Retirement Enrollment Table
PS_RTRMNT_VW -EE Current Retirement Benefits

Simple Plan Tables – Plan Types – A%

PS_SIMPLE_BENEFIT - EE Simple Benefits Plans Enrollments
PS_SIMPLE_PLAN_TBL - Plan attributes table.
PS_SIMPLE_PLAN_VW - Simple Plan Types view with long description.

Disability benefit plan table

PS_DISABILITY_BEN EE Disability Ben Enrollments
PS_DISABILITY_VW EE Current Disability Bens

Build Search Index - PORTAL_INDEX

PeopleTools > Portal > Build Registry Search Index
PORTAL_INDEX - is the Application Engine process which creates the search index.
The search index derives keywords from the content reference labels and long descriptions.

Associating Keywords to Content References.
Additional keywords can be assigned to a content reference by adding portal KEYWORD attributes. This is very useful if there are synonym-type keywords that are not mentioned in the title or description; for example, P.O. versus Purchase Order.

Following steps to be followed to setup for the military customers / employees

1) Set Up HRMS>Install> Installation Table> Products
check military check.

2)Modify the search views to include the Military ranks
Record MIL_SRCH_SBR - check the alternate key for all fields in the record field properties
which adds 3 new fields in the search page Military Service, Military Rank and Worn Rank
in the modify the person.

3) setup the Event manager registry for updateMilitaryNames handler

SetUp HRMS> System Administration> HCM Event Manager> Event Registry

Event name :- AssignmentMilitaryRankChanged
make this event active.

Confirm that the Handler:UpdateMilitaryNames is Active in the Registered Handlers Tab on the Event Manager – Registry page.

Handler mode:- It should be synchronous.

Find the resumes applicants based on the keywords.
Search the resumes in peoplesoft.

Recruiting > Administration > Build Applicant Index

An application engine program can be executed to run the Verity search Index to search the applicants.

under the applicants status select the group that needs to be indexed. select the index
C:\tmp for NT and /temp for UNIX scheduler.

execute the process HRS_SRCH_IDX to create the search index in the PS_HOME/data/search/HRS_ResumeText/

If the application servers and process schedulers are on separate boxes then additional steps need to be taken so that the application servers have access the files created under the PS_HOME\data\search\HRS_ResumeText\%DB NAME% directory

These files can be copied to app server as well.

To find the applicants

Recruiting > Find Applicants

In the Resume and Application Search section enter word that you are looking for in the resume in Enter Keywords field.

Refresh SJT_OPR_CLS and Refresh SJT_CLASS_ALL are Security process.

When to execute Refresh SJT_OPR_CLS process

On the Roles - Permission Lists page

• Add a permission list with data permission to a role that is already assigned to one or more users.
• Remove a permission list with data permission from a role that is already assigned to one or more users.

On the User Profile component

Add a row security permission list.
• Delete a row security permission list.
• Add a role with data permission.
• Delete a role with data permission.
• Clone an existing profile that has data permission through roles or a row security permission list.
• Deactivate a user.

You can refresh SJT_OPR_CLS in real-time by using the subscriptions on the USER_PROFILE and ROLE_MAINT messages or on demand using the SCRTY_OPRCLS app
engine process.

Run the Refresh SJT_CLASS_ALL process when

• Add a new department to a department security tree.
• Delete a department from a department security tree.
• Move a department to another parent node in a department security tree.
• Modify a department security tree.

Real-Time updates of the Transaction Security Join Tables.

One of the big enhancements for HRMS 8.9 is that the security join tables are updated in real-time instead just using an Application Engine process. This is accomplished by using a special subpage that contains the working fields that are needed. This subpage (SCRTY_SJT_UPD) needs to be put on a page that is in the components where the transaction records are updated. For the transaction record JOB, the subpage has been attached to the JOB_DATA1_WRK page. This page is included in all of the components where the JOB record is updated (either directly or as a component interface).

There are 2 type of Security Join tables

1)Transaction - Security Join Tables
2)User Side - Security Join Tables

Transaction security definitions are stored in one of the following four SJTs, depending on the kind of transaction data:
• SJT_PERSON (stores person-related transaction data)
• SJT_PERSON_USF (stores person-related transaction data for USF installations)
• SJT_DEPT (stores department-related transaction data)
• HRS_SJT_JO (stores job opening-related transaction data)

User security definitions are stored in the following two SJTs:
• SJT_CLASS_ALL The row security access assigned to a permission list (role-based or row security).
Contains the data permission information for all the permission lists that are given data access on the Security by Dept Tree page or Security by Permission List page.
Stores Data From 1)SCRTY_TBL_DEPT 2)SJT_CLASS
Following are keys
CLASSID , SCRTY_SET_CD , SCRTY_TYPE_CD , SCRTY_KEY1 , SCRTY_KEY2 , SCRTY_KEY3
• SJT_OPR_CLS Which user profiles are assigned which permission lists
Contains the user IDs of people with data permission and the permission lists with data permission that are assigned to them.
Stores Data From
1)PSOPRDEFN
2)PSROLEUSER
3)PSROLECLASS

PeopleSoft Application Engine programs use bind variables in the SQL statements, but these variables are just PeopleSoft specific. When the statement is passed to the database it sends the statement with literal values. The only way to tell the application engine program to send the bind variables is by specifying the Re-Used flag for that statement that needs to use the bind variable.

If any customizations are performed, it is recommended that the Reuse Flag be set to “Yes” for all program steps.
Before

AE Trace

AE Trace

You can get detailed AE Trace as shown above by appending the tace flags in the process definition > options page.

-TRACE 384 - will give you the detail timing of the SQL.