PeopleSoft Learning

Calculating Benefits Deductions for Multiple Jobs
Set Up HRMS > Product Related > Base Benefits > Rates and Rules >Calculation
Rules Table > Calculation Rules

When calculating benefit deductions or coverage amounts based on the employee’s salary
you need to determine which job salaries to use. You can calculate deduction and
coverage amounts based on:
• Primary: The salary from the Primary Job
• Flagged BR: The sum of the salaries from a group of jobs within the same benefit
record number selected for deduction processing
• All Flagged: The sum of salaries across all benefit record numbers selected for
deduction processing.

Note. The Combined Salaries check box and Grouping Method on the Calculation Rules
page along with the employee’s Include Deductions flag from the Primary Jobs Flags
page determine the deduction or coverage amount for salary based plans.

Primary Jobs in Peoplesoft
There are 2 types of the Primary Jobs in the Peoplesoft HCM
1) HR - Primary Job Indicator in the Job data component.
2) Benefits - Primary Job Indicator.
One of the Employee job will be considered as the HR -Primary job for an employee and this is mainly for reporting purpose.

One of the Employee Job will be considered as the Benefits - Primary Job for Jobs under particulary Benefit Record number of an employee. If employees' Jobs are assigned to more than one Benefit record number and for each set of the Employees' Jobs under the particular Benefit record number one Benefits Primary Job should be selected.

Job - Data - Benefit Program Participation Page can be used to set the Benefit Record number.

Note : - Benefit Record Number is Zero by default. You manually change this field when appropraite. Because you are maintaning an effective-dated history of primary jobs benefits according to a set of strict rules , don't change the benefit record number of an existing job.
Doing so invalidates the primary job inicators that reside on the effective - dated primary jobs table and can result in erroneous processing within Benefits Adminstration and payroll for north america, resulting in abnormal termination of some processes.

Multiple Job Options can be set in the below Component.
Setup HRMS > Product Releated > Base Benefits > Multiple Job Options > Mutliple- Job optns

Following page can be used to view and update an employee's primary Job flag inculde deduction flag.
Benefits > Maintain Primary Jobs > Maintain Flags > Primary Jobs Flags

Primary Jobs table, Which is automatically created when ever a job is added using the Add concurrent Job pages updated whenever the job is terminated, based upon rules that you define in the multiple- Job optns (multiple Job options) page.

Primary Jobs table has following flags as well.

Include Eligibility : For Benefits Administration only. Select this check box if you want this job to be included by the system when determining the employee’s benefit eligibility.

Include Deductions: Select this check box if you want this job to be included when the system calculates the employee’s benefit deduction and coverage.

Why Benefits Primary Job is requried.
1) Determine to which Job the system applies the benefit deducation.
2) Identify the job that will provide the service date and the termination date.
3) Search record on all the Benefits search page shows only the jobs which has primary job flag is selected.

Automatically Building Primary Job Data for Multiple Employees
Run the Primary Job Utility process whenever you add a new employee population to the database through an external interface or database load (such as when implementing employee groups in phases or acquiring another company).

Benefits > Maintain Primary Jobs > Rebuild Primary Job Flags > Primary Job Maint
Process Name :- BN_BEN500_AE
When the utility runs, all existing data for the indicated employee population (if any) in the Primary Jobs Table is deleted. For each employee, a new effective-dated entry is made, assigning the primary job designation to the lowest active employee record within a benefit record number. Primary Job information is created for a time span bounded by the earliest and latest job effective dates for all jobs within a benefit record. If all jobs within a benefit record are terminated, the job with the lowest employee record is designated as the primary job.

Warning! All manual changes made through the Primary Jobs Flags page for the selected employee population are lost, because the complete Primary Job history is rebuilt for each employee.

New Module to be introduced in the peoplesoft 9.1 - Workforce communication (WFC).
WFC is outcome of an market research to Manage different HR programs and
initiatives whcih helps to increased invlovment workforce and sucess of initiatives.
PeopleSoft Workforce Communications could be used include:
• Organizational change management communications
• Cultural brand awareness
• Open enrollment communications
• Policy and compliance communications
• Manager-assessed workforce planning
• Health and wellness programs
• Alumni community communications and development

Surveys
Surveys can dynamically branch based on how the recipient has answered the questions, and can trigger automated follow-up actions that are specific to the recipient’s response. The ability
to target survey communications to workforce groups and to personalize survey.

PeopleSoft Workforce Communications can enable you to answer the following
questions:
• Which initiatives were most successful?
• Has the initiative resulted in the committed goal of cost reduction?
• What percentage of recipients responded to the survey?
• How many people opened the email communication? Who didn’t open it?
• Which workforce demographic is the most and least satisfied or engaged?
• How is satisfaction and engagement related to other factors?
• How do you get the right talent in the right position?
• How many contractors have we hired as a result of alumni programs?

Jobcode in the Position data Management in Peoplesoft.
You can associate an jobcode to an position number only when the position management indicator for Job code is selected. Business unit in the position management table should map to the SETID in the Jobcode table through the Set control recrod.

BENEFIT_NBR field is not implement in the peoplesoft base benefit records.
EMPL_RCD in the Base Benefit Tables doesn't store EMPL_RCD instead store the Benefit record Number and Benefit number (BENEFIT_NBR) field in these records are dummy ( not implemented )and they always store zero. It's seems to be some sort of the design flaw in the Peoplesoft.

All the Base Benefit (Benefit Program participation , Health Benefit ..etc )
record's schema shows that it is keyed by EMPL_RCD. This is not logically or functionally accurate. Throughout all of Base Benefits, when in the context of benefit enrollment, EMPL_RCD must be interpreted as an alias for BENEFIT_RCD_NBR. All benefit enrollment-related records are logically keyed by BENEFIT_RCD_NBR, so here EMPL_RCD actually contains the value of the appropriate BENEFIT_RCD_NBR. It is CRITICAL that all joins, comparisons, and updates to this record be against BENEFIT_RCD_NBR. Thus a typical driving join for benefit participation is PS_PER_ORG_ASGN.BENEFIT_RCD_NBR = PS_BEN_PROG_PARTIC.EMPL_RCD, and a typical join for benefit enrollment is PS_PER_ORG_ASGN.BENEFIT_RCD_NBR = PS_HEALTH_BENEFIT.EMPL_RCD. The security and search views used in Base Benefits perform this "mapping" internally.

PER099 - Employees Record

PER099 - This Application Engine program re-fresh the snapshot of the employee data stored in the in PS_EMPLOYEES table and PS_EMPLOYEES_LNG

Employee - EMPLOYEES is a table populated by PER099 AppEngine process.

It is a snapshot of emploees' personal/demographic data, employment data, and job/salary data as of the date indicated when the program is run.

This table is primarily for reporting. Only employees with EMPL_STATUS (A,P,L,S,W) are included with all their EMPL_RCDs and the most current JOB row as of the ASOFDATE.

EMPLOYEES_LNG is the language record related to EMPLOYEES.

A related language record enables text fields on a table to be translated into various languages for use in other countries.

Note :- It is not preferred to modify these record during implementation. If you need custom fields for the reporting purpose create the child record with the same set of keys and the custom fields in to these and create Job process including the PER099 and custom process which populates custom field in the child record. Simple join on the Employees record and custom child record will give you all the fields for reporting purpose.

In the Installation table fill the the last assigned value with 9's.

Eg:- Last Employee ID Assigned field on the Last ID Assigned tab should be filled with only 9's.

(Applicable for most version of PeopleSoft HRMS 8 and for all version HRMS 8.3 and higher)

For these symptoms:

1. A user cannot view data that they have been granted access to on the Department Security Tree.

2. A user can view data they have not been granted access to on the Department Security Tree.

3. User is receiving "No Matching Entries Found" when using a search record

4. The PS_SCRTY_TBL_DEPT becomes empty

Here are the troubleshooting steps :

1. Have you run the app engine process HR_FASTVIEW (via Setup HRMS > Security > Department Security > Update Dept Security)?

2. Is the Update Row Level Security checkbox enabled when running the HR_FASTVIEW process (via Setup HRMS > Security > Department Security > Update Dept Security)?

3. Is the As Of Date designated on HR_FASTVIEW the same date as your current Department Security Tree?

4. Are the effective dates of your departments less than or equal to the effective date of your current Department Security Tree?

5. Does the SETID and TREE_EFFDT of your Department Security Tree appear via the following SQL after running HR_FASTVIEW -> SELECT * FROM PS_R_PER505 and is TREE_EFFDT equal to the effective of your tree via Tree Manager?

6. Is your Department Security Tree named "DEPT_SECURITY"?

7. If you've added a new department via the Department Table, have you also added it to the DEPT_SECURITY tree?

8. Do your users have the appropriate Row Security permission list assigned to their user profile (via PeopleTools > Security > User Profiles > User Profiles > General Tab > Row Security field)?

9. Does the Row Security permission list assigned to your user contain the appropriate setids and associated departments (the setid/departments per each department security tree that the user should have access to), and do the departments have Read/Write access (via Setup HRMS > Security > Department Security > Setup Security Access)?

10. If updating Fast Security, are all three checkboxes enabled via the Update Dept Security run control page (Re-Fresh Type 1, 2 and 3)?

11. Are there any departments via Setup HRMS > Security > Department Security > Setup Security Access (PS_SCRTY_TBL_DEPT) that do not exist on your department security tree (these need to be in sync)?

12. For an employee that isn't retrieved via Job Data (for example), sql PS_JOB for the employee (SELECT EMPLID, SETID_DEPT FROM PS_JOB WHERE EMPLID = 'xxx'). Does the employee's setid value in SETID_DEPT on PS_JOB equal the SETID of the department security tree(s) entered on the user's row security permission list (HRMS > Security > Department Security > Setup Security Access)?

A pay group consists of a group of employees who are paid together with the same pay characteristics ( pay period, same pay date, frequency, and so on). Pay group is used by payroll and payroll interface.

Although this information may seem specific to payroll processing - with either People Soft Payroll or your own system - you also need it for PeopleSoft Human Resources because it enables you to set up job records and Benefit program. serveral of the fields on the job data component contain default values that you specify on this table.

1)Employee Type Defualt
2)Default Benefit Program
3)Holiday Schedule.

Refresh Employee compensation

Workforce Administration, Collective processes, Refresh compensation, Refresh Employee Compensation.

Refresh Employee Compensation Process.

This process recalculates compensation based on the current values in the system and automatically populates the correct compensation amount by inserting a new job row (unless there is no change to an employee's compensation). The process replaces manual changes with the new default values.

The refresh employee compensation process executes the same steps as the default pay components button on the compensation page, but you can update several records at once.

1) Inserts a new job row when you click the add new effective Date options with the effective date you entered in the as of date field.
2) Updates the job that is effective as of date you selected in the As of Date field.
3) Updates any future rows (rows are considered to be future if they come into effect after the As of Date ) When you select the update future rows check box.

1) Peoplesoft Reporting
Connects 2 or more PS/Queries.
n level nesting,Schedulable.
Parent-Child relationships
Underlying structure for XML Publisher subreport support & XML Output.

2) PeopleSoft Query Access Services
Standard Web Services to run and create PS/Queries Planned for PT 8.50

How to choosse a particular reporting tool for developing the reports in Peoplesoft ?

What are the advantages / Disadvantages of
different Reporting Tools.

This picture gives information about which Reporting tool to be used based on the type of the report.