PeopleSoft Answers for your Questions

PeopleSoft Leave Accrual

2011-07-19T19:54:00.001-07:00

Question: How does Leave Accrual Process works in PeopleSoft? What are the different setups needed?

Answer: I will be covering the answer in different parts; This will be Part-1 which will cover the basics of Leave Accrual Process in PeopleSoft.

PeopleSoft provides Base Benefit tables where we can provide the accrual rules for Sick and Vacation Plans. The main purpose of leave accrual process in PeopleSoft is to accrue leaves based on the plan setup and maintain employee leave balances.

Every benefit plan in PeopleSoft is distinguished by a unique combination of plan type and plan name. Use the Plan Type field to enter the plan type for the employee. Plan type is a unique identification code. Valid plan types for leave plans are 50-59 and 5A - 5Z. Plan Type of 50 is for Sick Plan and 51 is for Vacation Plan.

Benefits tables store leave plans and accrual balances. The Leave Plan table allows you to define service and accrual processing rules for your leave plan

Set Up for Leave Accrual: Set up HRMS -> Product Related -> Base Benefits -> Plan Attributes -> Leave Plan Table:

On this setup table, you specify how your leave time should accrue, i.e. is it based on the length of service or based on the number of hours you work in each pay period;

For Example, if you want to accrue 8 hours per month if the service length is between 0 to 23 and should accrue 10 hours per month for any service above 24 months, then you would use the following setup:

Service Unit would be: Months

Accrual Rate Units would be: Hours per Month

In the “Accrual Rate Values” grid, you would have 2 lines. One with 0 Service Months and 8 Hours per month and second line with 24 Service Months and 10 Hours per month;

In the setup table, based on “Accrual Rate Units” the award frequency determines how often accrued time is awarded to the employees. If the award frequency indicates “First Run of Year” which means that time is awarded only once, during the first Accrual Processing run of the year for most employees, or during the first run in which a newly hired employee is eligible to be awarded accrued time. If the award frequency indicates “First Run of Month”, during the first Accrual Processing run of each month, each employee will be checked to see if time should be awarded, and if so, how many hours. Accrued hours are awarded during the first run of each week when Weekly frequency is selected. If Hourly frequency is chosen, each employee will be checked during every Accrual Processing run; if additional service hours have been posted to the employee's records by payroll processing, additional time may be calculated and awarded.

This will be Part 1; Will Continue with setups in Part 2....

Top Oracle Job Site

2010-12-28T19:35:00.000-08:00

Question:

What Job or Career , Employment Site can I search for Best , Entry Level Oracle Jobs
Search Oracle Jobs:

For Oracle Jobs:

Oracle Entry Level Jobs
Oracle Freshers Jobs
Oracle Full Time Jobs
Oracle Contract Jobs
Oracle Functional Jobs
Oracle Technical Jobs
Oracle e-Apps Jobs

Oracle HRMS Analyst/Developer

The Oracle HRMS Analyst/Developer will be responsible for delivering projects within our key Enterprise Resource Planning (ERP) initiatives and enhancements to our internal customers. The candidate will be apart of a team of Oracle Developers and interact daily with Functional and Support analysts to fulfill development and support the ERP production environment.
Responsibilities include analysis, implementation, support and customization/upgrade of various Oracle products.

Oracle Database Administrator Job

installing, patching, and upgrading Oracle Databases - Strong Data Warehousing ... - Data Warehouse, Oracle 11g, RAC, Streams/CDC, Data Guard
Oracle DBA support for Projects, - Monitoring of Oracle 8i/9i/10g/ ... and implement Job Qualification
Oracle DBA with E-Business suite

Oracle Developer
Expertise in SQL and PL/SQL development, and tuning using standard Oracle tools such as ... * Experience with batch processing using Oracle external tables, bulking techniques

Oracle Technical Developer - Permanent Job

Oracle 11i Applications (total of 5+ Oracle Applications experience) - Bachelor's ... non-Oracle source data

Oracle Functional / Technical Developer -

Oracle 11i Applications (total of 4+ Oracle Applications experience) - Bachelor's ... non-Oracle source data through the use of Oracle interfaces

Oracle Applications Developer

Java, JSP, Jdeveloper, Oracle Forms, Oracle Applications * Effective communication ... * Desired experience/skills include: Oracle PIM, Oracle EBS R12, UML, Oracle 10g DB

Senior Apps Oracle Developer

Oracle Application Developer to work on their new Oracle ... Sales Contracts extension with interfaces to Oracle Applications Modules

New PeopleSoft Jobs site

2010-12-28T18:53:00.000-08:00

Question: Where can i find Best PeopleSoft Contract Jobs, PeopleSoft Full Time Jobs , PeopleSoft Entry Level Jobs:

Answer:

PeopleSoft Entry Level Jobs
PeopleSoft Freshers Jobs
PeopleSoft Full Time Jobs
PeopleSoft Contract Jobs
PeopleSoft Functional Jobs
PeopleSoft Technical Jobs
Search PeopleSoft Jobs:

For PeopleSoft Jobs:

PeopleSoft Functional Consultant

PeopleSoft 9.0 with functional and ... multiple large full-scale, full life cycle PeopleSoft implementations
Peoplesoft Management Professional Certificate; 2 years experience in PeopleSoft 9.0, upgrade projects, PeopleSoft HRMS Modules, e-Application Designer and Query Tool.

PeopleSoft HCMS Team Lead

Providing leadership and oversight to the HR functional teams
Reviewing and providing input to the development of PROJECT test plans and scenarios
Coordinating and assisting with development and documentation of an implementation/rollout plan for the HR component of the project plan
Human Resource Management (HRM)-Payroll, HR, Recruiting, Base Benefits, e-Recruit, e-Pay, e-Profile, or e-Compensation; Portal Security.

HRMS Business Systems Analyst

To participate in PeopleSoft related projects and testing efforts to ensure solutions meet user requirements.

* To lead, coordinate and perform the functional tasks related to the development lifecycle of PeopleSoft projects including requirements definition, analysis, fit/gap resolution, process design and implementation, functional design, configuration, testing, training and validation, after implementation.

* To troubleshoot PeopleSoft issues as they come up.

* To constantly look for more efficient ways to manage HR's business processes.

* To keep up with enhancements/improvements delivered by Oracle.

* To work with end users and technical resources to build solutions.

* Owns PeopleSoft HRMS configuration that supports business processes.

* Responsible for writing test scripts and testing functionality.

* Responsible for supporting the eLearning module.

PeopleSoft Technical Developer

Senior PeopleSoft Applications Technical Developer with HCM. Requires PeopleSoft 9.0, People Tools 8.49 and Peoplecode. Must have PeopleSoft upgrade, development, support experience in HCM, and HR HelpDesk

* Experience using PeopleSoft 9.0 or higher.
* PeopleTools version 8.49 or higher.
* Experience with PeopleSoft Integration Tools (Integration Broker, Component Interface).
* Experience using the following PeopleSoft tools: SQR, People Tools, Application Engine .
* Application upgrade experience.

2010-08-14T13:40:00.000-07:00

Question:

In the Earnings Setup (Taxes page), there are two check boxes "Subject to FWT" and "withhold FWT" under the US ONLY group box.could you please explain the significance between the two checkboxes? How does it affect the earning code?
Answer:

When you setup an Earning Code, you need to see if the earnings is taxable; If the Earning is taxable and taxes are to be withheld from Employee's paycheck, then you would need to select appropriate properties during an Earning Code Setup. Most of the earnings are defined with both Subject to FWT and Withhold FWT selected.

• Subject to FWT means the earnings is part of taxable gross.
• Withhold FWT means federal income tax on the earnings must be withheld at the time of payment.

If Subject to FWT is checked, but the Withhold FWT is NOT checked, it means that, the earnings are taxable, but when pay calculation is run, payroll will not take out taxes from that earnings;

If Federal tax is not withheld because Withhold FWT is not selected on the Earnings table and the State tax is not withheld because Withholding Follows Fed Rules is selected on the Taxable Gross Definition Table page..

Changing Job-Code Standard Hours and FTE

2010-05-25T09:20:00.000-07:00

How to Change Job-Code Standard Hours and FTE:

Answer:

Please go through the link below to get screen shots and how you can establish this.

FTE (which stands for Full-Time Equivalent—1.00=full-time, .50=part-time).

Use the Rules Definition page to enter the amount of places used after the decimal to calculate FTE (full time equivalent). You are allowed to use up to 6 decimal places. This allows flexibility in FTE calculations and improves precision in FTE and FTErelated calculations such as worker compensation.

If the FTE Decimal Precision field is set to zero, FTE will default to 1 on the Job Data pages, regardless of the number of hours entered or part- or full-time status.

How to delete a Job Opening?

2010-05-11T15:35:00.000-07:00

Question:

How to deal with PeopleSoft Job Opening Ids are on Pending Status which had some approval path issue? or what is the best approach to delete that old Job Opening ID.

Answer:

In PeopleSoft, there is no direct "Delete" option available for Job Openings. The best practice is to "Data Archiving" process to archive the same.

Steps to Data Archive a old Job Opening or a Job Opening which is in “Pending Approval” status (Since you want to delete a pending job opening)

1). Create a new query of type ARCHIVE . Here you can select a new record of PS_HRS_JOB_OPENING and select one field HRS_JOB_OPENING_ID..name it DELETE_JO.This query will have a prompt field HRS_JOB_OPENING_ID whichever you want.

2). Goto PeopleTools > Data Archive Manager > Manage Archive Templates. Create a new Template. Select base object and archive object as HRS_JOB_OPENING. Select query name DELETE_JO as the new query you create with a prompt field. Save the template.

3). Go to PeopleTools > Data Archive Manager > Archive data to History. Select the newly created template. Use 'Selection' and Query as the new query created. Click on Define Binds. Select 'Reset Query Bind Variables' and enter the Job Opening ID to be deleted based on how your query is setup. Save and run the process.

This process adds all relevant PeopleSoft JO into PS_HRS_JOBOPEN_HST Table.

4). After running the selection process, now run the process using 'Delete' option

This will delete that particular Job Opening.

if you do not want to use the above option..here are the tables that you use to delete the PeopleSoft Talent Acquisition Job OPening:

Records
HRS_JOB_OPENING
HRS_G_JO_PRI
HRS_JO2_LNG
HRS_JOBINDX_CTL
HRS_JOPSTDS_LNG
HRS_JO_ANS
HRS_JO_APRV
HRS_JO_APRV_STS
HRS_JO_ATCH
HRS_JO_ATCH_LNG
HRS_JO_EDUC_EXP
HRS_JO_EXP
HRS_JO_EXP_LNG
HRS_JO_HJ_HIST
HRS_JO_ITEMS
HRS_JO_LNG
HRS_JO_LOC
HRS_JO_LOC_AREA
HRS_JO_NAME
HRS_JO_NOTE
HRS_JO_NOTE_LNG
HRS_JO_OE_EVAL
HRS_JO_POSN
HRS_JO_POSTING
HRS_JO_PROFILE
HRS_JO_PST_DSCR
HRS_JO_PST_DST
HRS_JO_PST_LNG
HRS_JO_QSTN
HRS_JO_RPL
HRS_JO_RQMT
HRS_JO_STS
HRS_JO_TEAM
HRS_PSTDSCR_LNG
HRS_SCR_HIST

Hope this helps

Future dated tax balance adjusment

2010-03-30T12:23:00.000-07:00

Question:

Hi,

We're having an issue with PeopleSoft Payroll N/A 8.9. There apparently was an adjustment made to the tax balance of one of our employees (an officer of the company). The problem is that there was an error during the adjustment and the adjustment was entered in a FUTURE period (2010 year, 10 period), so when confirming payroll, this employee errors out.

Clearing the balance by readjusting the balance didn't fix the error as there is still the future dated record with a YTD balance sitting out there, so it still won't confirm.

Any help would be appreciated!

Answer:

Well, if PeopleSoft allowed to adjust a Balance Period for which there was NO activity, then it is some kind of BUG;

Anyways, if you do take out the balance adjustment, it does NOT delete the row from Balance tables; the data will be there with certain number of rows , but with all ZERO values;

You must delete the Balance Rows from the table(s) that you did an adjustment;

Unless otherwise, you will get the below error:

SQL Error 0805: Non-Unique Data (PSPCBUPD)

Also, refer the below solution:

EPY: Payroll Process fails with Unique Constraint error 805 Master Solution [ID 607013.1]

The balance tables updated/inserted during Pay Confirm processing are:
PS_EARNINGS_BAL
PS_TAX_BALANCE
PS_DEDUCTION_BAL
PS_GARN_BALANCE
PS_CHECK_YTD

Sometimes users may make a balance adjustment to a future pay period or quarter in error. When this occurs, the next confirm process will issue an 805 error for that employee. If you zero out all of the amounts in this future balance record (row), the system will still see the future record and it will still abend. This "empty" future balance record must be deleted via SQL. Once this row is deleted, begin the Confirm process. The Confirm will begin where it left off.

Hope this helps

New PeopleSoft Jobs Site

2010-03-02T08:41:00.001-08:00

Check here for New PeopleSoft Jobs Site:

Search for your next PeopleSoft Job

Pay Proration Rules

2010-02-24T19:43:00.000-08:00

Question: How does Proration rules work in Payroll:

Answer:

Effective Date:

The effective date is critical in determining how an employee is paid. When you hire an employee, the effective date becomes the hire date and the original hire date. If an employee is hired in the middle of a pay period, the system automatically calculates the percentage of pay that the employee is due, and creates a corresponding paysheet entry.

Similarly, if you add an entry to an employee's job record, such as a promotion or pay rate change, and that change goes into effect in the middle of a pay period, the system creates two pay earnings entries on the paysheet and prorates the earnings accordingly. The system stores rules for proration on the Pay Group table.

When the effective date falls in the middle of a pay period, the paysheet process prorates the employee’s pay for the period by creating additional pay earnings records. Earnings are prorated for all frequencies. Proration rules in Payroll for North America process a single week at a time, Sunday through Saturday. Because of this, problems with proration may occur with employees whose schedule may not fit this pattern.

Proration Rules

An employee is considered eligible for partial pay whenever a job record has an effective date in the middle of a pay period. The system uses work schedule to determine the number of workdays per year and the number of workdays per week.

Mid-period Job Changes

On the Pay Group table, specify a work schedule and a proration rule to calculate prorated pay when there is a partial pay period due to mid-period job changes:

An employee is considered eligible for partial pay whenever a job record has an effective date in the middle of a pay period.Mid-period job changes that can cause partial pay include hiring, termination, or pay data changes. Transfers and promotions might result in pay data changes.

Elements of the Proration Calculations :

The work schedule and proration rule work together to calculate prorated pay. Other factors are the employees standard hours and standard work period, and frequencies specified on the Pay Group table.

This table defines the variables used in the proration rule formulas:

Proration Rules for Mid-pay Period Changes

Salaried Proration Rule and Hourly Proration Rule options on the Pay Group table define how earnings and hours are prorated during paysheet creation for employees eligible for partial pay.

• The system creates a separate pay earnings record with the corresponding hours or earnings for each part of the pay period.
• When an employee is transferred to a new pay group, the system pays the employee for the correct number of hours based on the effective dated change.
• When an employee transfers to a new tax location in the middle of a pay period, the system creates a separate pay line for each state, locality, or both on the paysheet.
• The system uses the work schedule and proration rules on the Pay Group table during paysheet creation to determine how to break out the earnings.

PeopleSoft Document Resources

2010-02-23T08:37:00.001-08:00

Helpful PeopleSoft Documents (PeopleTools/Technical Related) from Metalink:

Red Paper Topic

Description

Meta Link

Online Performance Configuration Guidelines for
PeopleTools 8.45, 8.46, 8.47, 8.48 and 8.49

Practical
guide for technical users, installers, system administrators, and programmers
who implement, maintain, or develop applications for Oracle PeopleSoft
Enterprise Applications.

rp_e_opcg_845_846_847_848_849.pdf (440.33 KB)

Online Performance
Configuration Guidelines for PeopleTools 8.1x, 8.4, and 8.44

Learn how
to diagnose a PeopleSoft Online Transaction environment, including Pure
Internet Architecture® and Enterprise Portal configuration.

Download
PeopleSoft 8.1x Red Paper (PDF: 740KB)

Download
PeopleSoft 8.4 Red Paper (PDF: 844KB)

Download
PeopleSoft 8.44 Red Paper (PDF: 930KB)

Download
UNIX shell scripts (ZIP: 5KB) that accompany these red papers.

LDAP Red Paper with Troubleshooting Tips for PeopleTools
8.x , 8.4x

LDAP Red Paper (1,820.02 KB)

Red Paper on Securing Your PeopleSoft Application
Environment

How to secure PeopleSoft
PIA environment

Red Paper (1,382.04 KB)

PeopleSoft PS/nVision Configuration & Troubleshooting
Tips

RP_nVision_guide (1,204.22 KB)

Red Paper on Implementing Clustering and High
Availability for PeopleSoft

Clustering_and_High_Availability-_840.pdf (1,983.35 KB)

Clustering and High Availability for Enterprise Tools
8.4x - 8.50

This
Red Paper provides guidance for building Webserver and Application Server
clusters.

PeopleTools Clustering Red Paper (2,827.3 KB)

Configuring a PeopleSoft Portal

This
Red Paper provides guidance on a variety of aspects involved in configuring a
PeopleSoft portal. It is organized into topics that prove to often be problematic
for portal implementation teams

configuring_ps_8_portal_v1.pdf (1,259.16 KB)

Troubleshooting WebLogic 8.1 and 9.2 Issues

Troubleshooting_Weblogic_81.pdf (234.52 KB)

Troubleshooting_Weblogic_92.pdf (1,367.93 KB)

Approval Workflow Engine (AWE) for HCM 9.0

This
White Paper discusses how to implement and set up the Approval Workflow
Engine (AWE), including how to define all the required support objects

Approval Workflow Engine (AWE) for HCM 9.0 (672.01 KB)

PeopleSoft Performance Monitor Red Paper

Performance
Monitor system for troubleshooting performance problems in your environment.

Performance_Monitor_RedPaper.pdf (3,326.46 KB)

Test E-mail workflow functionality

2010-02-22T08:59:00.000-08:00

Sometimes, you would come accross this situation:

"the mail is not going to the mail user and i am not even getting any error messages. I checked my SMTP in my server its all working fine . I dont know what is the issue. I even tried using Sent Mail function till its not working as expected.... "

Answer:

To troubleshoot this issue, there might be different reasons. You need to have appropriate setup and test the setup to see if your SMTP settings are working in the first place.

Below are setups the required for enabling or using Workflow notifications/emails:

1. The first and foremost thing is to setup: SMTP server Application server/Process scheduler used for the development.

2. E-mail should be enabled and configured for the instance in which the workflow is developed. eMail id's should exist in PSOPRDEFN and PSEXLATOPR tables; Also, emails are triggered using Person Profile.. in some places.

3. The User Profiles for the Roles are already in Place with proper Worklist ID s and Permissions.

Configure the SMTP in your psappsrv.cfg as well as in psprcs.cfg:

Setup the SMTP server ip-address and port number in App. Server / Process scheduler
Invoke the PSADMIN.exe in the PS_HOME/appserv directory and in the application server configuration, SMTP settings section specify the ip-address for the machine where SMTP server is installed.

Under the Setup WorkFlow Defaults:

Make sure the check boxes ‘Worklist Active’, ‘Worklist Active’ ‘HR installed’ and checked. If not, check the checkboxes and reboot the application server

Enable workflow for User Profiles :

For the users who will be using workflow routing (e-mail, Worklist) make sure that the following things are done.
1. They have a valid Worklist-id in PeopleSoft User profile.
2. E-mail and Worklist are enabled for the users

Test the E-mail workflow functionality :

1. Enter the User Id to whom the test mail has to be sent
2. Enter the test mail subject message
3. Save the component
Once the component is saved, it should trigger e-mail to the test users Worklist id specified in the user profile.

If mails are not generated, here are couple of things that will help you to troubleshoot the issue:

1) Since there are a lot of different reasons to get this particular error. In order to get better detail as to why the failure is occurring, you should set the LogFence=5 on the appserver to get SMTP tracing in your appserver log . This only works for the app server,not the Scheduler.

SMTP mail log is created under the PS_HOME\APPSERV\PRCS\\LOGS; This would give you a specific reason of the issue and can help you to troubleshoot the issue.

2)Make sure your SMTP server is working; to test this:

Locate an SMTP mail server that you specified in SMTP settings under your App or Prcs Server SMTP settings
Prove the mail server is accessible by connecting via telnet or pinging it.

3) Make sure the email id specified is active and exists.

PeopleSoft Benefit Rate Type Table

2010-02-20T12:24:00.000-08:00

Question:

We are on PeopleSoft version below 9.0 and we have seen that All benefit rate data like Flat Rate table, Age Graded table etc are consolidated into one table i.e Benefit Rate Type Table;

We use the PROV_COVRG_RATE field in order to establish the total amount that is paid to an insurance provider and back into the administration fees.

we used to use PROV_COVRG_RATE field under Flat-Rate table in 8.8 (also available in 8.9) , where or how do I use it in on HR 9.0 or in 9.1?

Answer:

All benefit rate data is consolidated into a single common structure. The individual Age-Graded, Flat, Salary-Percent and Service tables will be dropped, and all rate data migrated to the new Benefit Rate Tables. This refers to AGE_COVG_TBL, FLAT_RATE_TBL, SALARY_RATE_TBL and AGE_RATE_TBL are being replaced by BN_RATE_TBL and BN_RATE_DATA.

The new Ben Rate Table provides the flexibility for the user to define different rates including Provider Rates if they choose to do so. Below Screen shots would provide you some idea:

Let's take an example:

Employee Amt: 60.00 Employer Amt: 40.00 Provider Amt: 99.00
In this example, the total deduction amount (non-tax and before-tax) is not paid to the provider. The difference (in this example $1) is kept by the employer as an internal administration fee.
It is used in a custom report process that calculates vendor insurance premiums.”

Here’s the screen shot of Flat Rate Table (in PS version 8.8 or 8.9) showing the Provider Amount:

How It Can Work in 9.0 and above:

The different Rate Tables of 8.8 or 8.9 are lumped into 1 component in 9.0 and above, differentiating them by Benefit Rate Type in new Benefit Rate Table

In this case, need to define Flat Rate. Using same example from 8.8, here’s 9.0/9.1 counterpart.

what’s missing is the previous Provider Rate of 99.0. This can easily be defined in 9.0 and above by using same component with Benefit Type of Flat Rate as illustrated below with Employee Rate of 99.0:

To access the Employee Rate above that is defined as Provider Rate, use Record PS_BN_RATE_DATA field BN_EMPL_RATE.

To access the Employee and Employer Rate for ‘RT1’:

SELECT
,E.BN_EMPL_RATE
,E.BN_EMPLR_RATE
FROM PS_BN_RATE_DATA E
WHERE E.RATE_TBL_ID IN (’RT1’,’RT1P’)
AND (E.EFFDT=
(SELECT MAX(E1.EFFDT)
FROM PS_BN_RATE_DATA E1
WHERE E1.RATE_TBL_ID=E.RATE_TBL_ID
AND E1.EFFDT <= current date or whatever effective date required)

Then in your SQR or batch program, add logic to match up Employee/Employer Rates to the corresponding provider rate, e.g.:

IF RATE-TBL-ID = ‘RT1’
THEN TOTAL-DEDUCTION = BN-EMPL-RATE + BN-EMPLR-RT

IF RATE-TBL-ID = ‘RT1P’
THEN PROV-COVRG-RATE = BN-EMPL-RATE

CO-ADMIN-FEE = TOTAL-DEDUCTION - PROV-COVRG-RATE

Or if you have naming convention schema for RATE_TBL_ID’s between the Employee/Employer Rates and Provider Rates, e.g. 1st 3 characters of the RATE_TBL_ID match, then you can join or add it in the program instead of hard coding it in the program.
You can also use the Benefit Rate Type to identify Coverage Provider Rates, e.g.:

When defining the Coverage Provider Rate, use the new Provider Rate Type just created:

To extract Provider Rate Types from table and corresponding Provider Rate:

SELECT
,R.RATE_TYPE
,P.BN_EMPL_RATE
FROM PS_BN_RATE_DATA P
, PS_BN_RATE_TBL R
WHERE P.RATE_TBL_ID = R.RATE_TBL_ID
AND (P.EFFDT=
(SELECT MAX(P1.EFFDT)
FROM PS_BN_RATE_DATA P1
WHERE P1.RATE_TBL_ID=P.RATE_TBL_ID
AND P1.EFFDT <= current date or whatever effective date required)
AND P.EFFDT = R.EFFDT

In batch program, add the logic to match up the Provider Coverage Rate to its corresponding Employee/Employer Rates. In our example the Rate Table ID ‘RT1P’ Rate Type ‘RT1’ in Benefits Rate Table matches with Rate Table ID ‘RT1P’. Hence you can create a schema where the Provider’s Rate Type matches with the corresponding Rate Table ID of Employee/Employer Rate in Benefits Rate Table.

Another option is to have one Provider Rate Type that applies to multiple Employee/Employer Rates, e.g. Benefit Rate with Rate Type of ‘RT1’ contains the Provider Coverage Rate for Benefit Rate ID’s ‘RT1’, ‘RT2’ and ‘RT3’.

PeopleSoft TAM / Recruiting Site ID's

2010-02-19T06:06:00.000-08:00

TAM Question:

I have a question regarding multiple Sites. How do we enable multiple sites on the same Portal?

Answer:

What is PeopleSoft TAM related Site ID:

Site IDs define the default parameters for an organization’s online application website and determine which job openings appear on the organization’s internal and external websites.

Row security is used to determine which job openings are available to the site. Job search criteria, such as Recruiting Locations and Job Family, use Set ID to display appropriate drop-down values.

Navigation of Site Set Up > Set Up HRMS -> Product Related ->Recruiting, Sites :

Define multiple Site ID's as you need in the Site ID Setup:
Also, make a note of the Site ID here,which is 1111.

This is the Internal Career's Portal CREF (through self-service) which is linked to default site id:

The Portal structure will not allow multiple instances of the same menu.component combination. However, the use of Additional Parameters in the Component Parameters groupbox allows the Portal to recognize the entry as unique. For example, adding a CREF to the Careers Home page for TEST Site (Site ID 1111) would look like this:

When CREFs exposed, the menu would then look like this in your portal:

Also, take a note of the below point if you are HCM 9.0 and above:

The link to the Job Opening and the Site is established through the Recruitment Source. The Recruitment Source can be setup by navigating to Set Up HRMS >> Product Related >> Recruiting >> Recruitment Sources >> Recruitment Sources >> Source Setup. In the Source Setup page select the appropriate "Source Type". The source type that you select determines which pages appear in the Source Setup component. The Source Setup component consists of three pages. The Source Setup and Contacts pages appear for all source types. The third page that appears depends on the source type that you select.

The Recruitment Source is linked to the Site in the second page. Here one or more sites can be selected for a Recruitment Source. When a recruiter or hiring manager creates a job opening and selects to post the job opening to this source, the system posts the job opening to all of the sites that you select here.

Hope this helps...

Question on Shift Calculation

2010-02-11T12:09:00.001-08:00

Question:

Dear Gurus

Does PS Timekeeper allow for the assigning of percentages to specific hours in the workday, so that if a non-exempt employee works those hours, they get a differential paid to the for that hour only.

For example, Jane Doe works the even shift (6pm to 2am) one day a week. When putting her hours in the timekeeper, she records normal hours (8am to 5pm) Monday through Thursday, and 6pm to 2am on Friday. Would she be assigned a shift code at the employee level (lets say 5%) that gets applied to all hours no matter what? OR could the system recognize normal pay for Monday - Thursday, and apply the differential to the hours worked Friday night only?

I Appreciate your early response.

Thanks in Advance

Keyrun

Answer:

You need to understand how Shift Differential is paid through PeopleSoft. here's some background on how you can setup shifts and shift differential or shift premium payment.

Methods to Setup Shift Pay:

This diagram lists some methods for setting up and calculating shift pay:

Earnings Code Based on Other Earnings.

This is the preferred method if you need to express shift pay as separate earnings on the paycheck or advice. Create a separate earnings code for shift differential based on another earnings code or a special accumulator of earnings and pay it out as additional pay. You can set it up as a percentage or a flat rate. A flat rate must be hours-based. Do not select Eligible for Shift Differential on the Earnings table.

Pay Group SetID and Shift Table
Create each applicable shift type on the Shift table. Assign each employee to one of these shifts. Select Eligible for Shift Differential for eligible earnings codes.

Earnings Code With Earnings or Rate Adjustment Factor
Add a rate adjustment factor to applicable earnings on the earnings table to add that rate to the employee’s hourly rate. Or add an earnings adjustment factor to the total earnings. This method does not result in a separate earnings line on the paycheck

Compensation Rate Codes
You can define non-base compensation rate codes to indicate the rate that is paid on the paycheck when assigned to an earning. For example, if the employee is paid overtime at time and half and the employee’s hourly rate is $10.00, the paycheck would show the $15.00 rate for overtime.

Use Time and Labor Rules
Customers who license PeopleSoft Enterprise Time and Labor set up rules to define shift differential.

One important thing to note is that: The Eligible for Shift Differential check box has no bearing on PeopleSoft Enterprise Time and Labor.

So for your case, you need to define a Time and Labor rule for calculating a shift premium instead of using payroll shift differential.

You can try using the Premium Zone Templates:

1) Template 100 :

If a time reporter works between x and y o'clock, then pay premium. i.e. When a time reporter works between (1)SPECIFIED_START_TIME and (2)SPECIFIED_END_TIME, create a shift premium only for those hours worked within the specified time, to be charged to TRC (3)SPECIFIED_TRC.

2) Template 090:

If a time reporter clocks in between x and y o'clock, then pay premium. i.e When a time reporter punches IN between (1)SPECIFIED_START_TIME and (2)SPECIFIED_END_TIME, create a shift premium for all hours worked, to be charged to TRC (3)SPECIFIED_TRC.
If the time reporter punches in within the specified time period, this rule creates a TRC for all hours worked, even when the time reporter punches out after the specified time period.

So, in your case, you would put the start time and end time of friday to pay .05 percent shift premium. Your Shift Premium TRC should have .05 as the multiplication factor.

Hope this helps. Please add comments.

Presheet Audit errors with blank descriptions

2010-02-11T11:39:00.000-08:00

Question:

Hello - We are having errors show on the Presheet Audit Report pay034 where theerror description is blank. Any ideas on where the error messages are stored and how to correct this problem?

Answer:

The Presheet Audit report is used to provide a detailed error listing of set up data (employee, benefit, deductions) that can cause errors in the Create Paysheet process (PSPPYBLD). So basically you need to run to identify setup issues prior to creating and calculating paysheets

The SQR uses descriptions that are defined in PS_STRING_tbl. There are 95 rows defined for Pay034.sqr program in 9.0 version.

Navigation to the String Table is - PeopleTools -> Utilities -> Administration -> Strings Table and look for PAY034 program id.

Please take a look at the above table and see if you have this table populated?

PeopleSoft PeopleBooks

2010-02-11T11:33:00.000-08:00

Question:

Where can i find Documenation like PeopleBooks related to PeopleSoft?

Answer:

Check the below link that would give you links to PeopleBooks for PeopleSoft Application 9.0, 8.x versionsand PeopleTools 8.4x

PeopleSoft PeopleBooks

PeopleSoft 9.1 PeopleBooks

Quarterly Tax Reporting

2010-02-11T11:13:00.000-08:00

Question :

What are Quarterly Tax Reports and how to file them:

Answer:

Tax ReportsTax reports contain information related to wage reporting, and they provide the forms and formats required for reporting payroll data to federal, state, provincial, and local taxing authorities.Tax reports have the prefix TAX. The special numerical series in the TAX SQRs are as follows:

• CTX: Related to Canadian T4, T4A, RL-1, and RL-2 reporting processes.

• TAX103: W-4 exempt employees.

• TAX113: Reset W-5 EIC earned income credit (EIC) employees.

• TAX700-799: Tax tables.

• TAX800-899: Processes to create files for states that must submit quarterly state wage listings on magnetic tape.

• TAX900-999: Related to W-2 and 1099 wage reporting processes.

State Quarterly Wage Reporting FormatsUsing data generated by Payroll for North America, there are three ways that you can submit quarterly wage reports:

•Paper reporting - TAX002xx.SQR

• Electronic file - TAX810xx.SQR

•TIB-4 (old SSA format)

•ICESA (Interstate Conference of Employment Security Agencies)

• Magnetic media - TAX860xx.SQR

•State-unique formats

•EFW2 -SSA format (formerly MMREF-1 format)

TAX810XX and TAX860XX - Quarterly UI Wage Tape: The output is produce in the electronic/magnetic media format. It can be copied to diskette or tape before filing. Some states use the TAX860XX format, which creates the file using the MMREF format.

The state-specific versions of this report have self-explanatory prompts. You can specify the calendar year and quarter on the Define Tax Reporting Parameters page, found under the Quarterly Processing menu.

Where applicable, choose between the TAX810XX and TAX860XX formats from the choices displayed in the process list that appears after you click the Run button on the run control page.

To submit in Paper Format use - Quarterly State Employee Wage Listing (TAX002xx) SQR Report/Process.

Menu Path:

Payroll for North America, U.S. Quarterly Processing, State Quarterly Wage Reporting, State Wage Listing Report

To Submit in Magnetic media, not using the MMREF-1 format use Quarterly UI Wage Tape (TAX810xx) orTo Submit in Electronic or magnetic media using the MMREF-1 format use Quarterly UI Wage Tape (Tax 860xx).

Menu Path :

Payroll for North America, U.S. Quarterly Processing, State Quarterly Wage Reporting, Create Magnetic Media

When you run the Tax810xx or Tax860xx processes, you get the files as shown below:

•TAX810xx & TAX860xx

•One file created for companies with different company

•Exception is Nebraska

•TAX810xx.nnn

•One file created for companies with different company but multiple files may be created if the data will not fit diskette

•“.nnn” represents a volume number

•T810xxnn

•Separate files are created for each company EIN

•“nn” represents a volume number for each company

If you are not filing by magnetic media, use the TAX002xx report, which is designed to print directly on the state form for those states that require submission on their forms.

For Filing with different states, you need to check each state unemployment website. If your employer is multistate, then have a document with all links pointing to the state unemployment tax sites. If you file using electronic filing, your payroll or tax department should register first using your company FEIN or State Employer Identification Number with the respective state and then use the ID to submit the file. Depending on the state validation process it may take time to get back the results of the upload. Some of the tax data might be incorrect. So, your payroll or tax department must make sure that the tax balancing reports (like TAX900, TAX017, TAX010ST ,TAX010FD , TAX004, TAX004ST etc) and run at regular intervals.

Check here how PeopleSoft Quarterly balancing is done

Example: if you want to file for Wyoming, here are the steps:

1. Make sure that Quarterly tax reporting parameters are setup.

2. Run the Quarterly UI Reports Wyoming (TAX810WY.SQR) or (TAX002.SQR)

3. Get the file TAX810xx.nnn (if filing through electronic) from the server

4. This must be FTP'd to the Payroll or Tax user who submits it to state

5. Verify the tax file is correct format.

6. Use https://doe.state.wy.us/wire/ to login and upload the file

7. Get validated results if the submitted file is OK or NOT OK.

8. If file not ok, fix the TAX Data and re-submit.

Take a look at this step by step document:

Click here

PeopleSoft Query Security

2010-02-11T11:03:00.001-08:00

Question:

What do u mean by query security.How it is implemented in peoplesoft?

Answer:

When you talk about PeopleSoft Query Security, these are things that are taken into consideration:

1. Query Profiles...Specifies what query operations, such as create and run, are available to users. For example, you may want certain users to run only existing queries, not create new ones.

2. Query Access Group and Trees....Collections of record definitions in a query tree. After you build a query tree, you can query any table in the access groups that are accessible to you.

3. Define row-level security and query security records....Provides data permission security when you access data using the PeopleSoft Query tool.

All of these are utilized by PeopleSoft Query through user's security settings, row-level security, and primary permission list. Query Profiles are setup in Permission List (PTPT1000) , under Query Tab. Query Access Groups are attached to Permission List (HCSPQUERY), under Query Tab.

About Query Security Record:

One of the Security Feature in PeopleSoft is Data permission security, or row-level security

• It Controls access to user data on an individual or group basis.
• It Specifies the rows of data that user is permitted to retrieve.

For example, you might want users to be able to review personal data for employees in their own department, but not for people in other departments. You would give everyone access to the PERSONAL_DATA table, but would enforce row-level security so that they could only see rows where the DEPTID matches their own.

Since there is Query Tool, through which you can retrieve sensitive data, You can implement row-level security by having Query search for data using a query security record definition. The query security record definition adds a security check to the search.

To apply row level security:

1. Select PeopleTools, Application Designer to open the Application Designer, and open the record on which you want to apply row-level security.

2.With the record definition open in the Application Designer, click the Properties button, and select the Use tab from the Record Properties dialog box.

3.Select the security record definition (usually a view) in the Query Security Record list box.

4.Once you’ve set the query security record definition, click OK to close the Record Properties dialog box, then save the record definition.

The PeopleSoft system automatically adds a WHERE clause to the SQL, joining the user’s user ID, primary permission list, or row security permission list to the following key fields if they are present:

• OPRID
• OPRCLASS
• ROWSECCLASS

For Example, If you want to add a Query Security to PS_JOB record, you need to check the record properties (the query security comes pre-delivered)

and here's what the EMPLMT_SRCH_QRY sql looks like:

TL_TIMEADMIN runcontrol Process Thru Date

2010-02-11T08:34:00.001-08:00

Question:

I have a question regarding TL_TIMEADMIN runcontrol.

Our end users are convinced that the 'Process Thru Date' is not an important piece of the runcontrol, and that it does not matter what it is. We do check the 'Use Reported Time for POI'. We do NOT check 'Use Current Date'.

In the past, when I've filed cases with Oracle/Metalink/GSC, I was told repeatedly by them to use the last day of the current pay period. However, our end users say that a consultant told them that date did not matter and to put anything in there.

We have multiple issues that this creates. One, the earliest change date doesn't get updated properly, creating a larger period of interest when TL_TIMEADMIN runs the next time.

We have other issues that we are dealing with, and we are up to 253 batches (Utopian batch count for our org would be about 8!) While I cannot blame all of the issues on the runcontrol Process Thru Date, I don't think this is helping and is causing extraneous issues which we don't need.

I have ran multiple traces, and that date is used repetively in that app engine. Has anyone else ever dealt with this issue?

Does anyone feel this field is unimportant? Granted, people are getting paid, but it does leave extraneous issues. And, it is against what Oracle says to do. Can anyone give me specifics of issues they have encountered when that date is off?

Answer:

Here's some explantion about the Run Control Fields when you submit the Time Admin Process:

• You must select the Forecast Payable Time option to use the results of the Time Administration process for budgeting or other business purposes, but not send the results to payable time.

• You would check the Use Reported Time for POI option to have the system consider reported time after the process date; if this option is not selected, the system uses the earliest change date and the current workgroup period to calculate the period of interest.

You will select the "Use Current Date option" to use the current system date for processing, or enter a date in the Process Date field to use that date instead. The system selects time reporters with an earliest change date that is equal or less than the specified date.

For Example, if you are processing Payroll Till 09/30/2009, but an employee submits his vacation hrs for October 1st week which is for Future time, If the Use Reported Time for POI option is selected, the system includes the future vacation time in its calculations. Clear the check box to have the system ignore the future time.

How Time ADmin Processes with ECD / Process Date:The system processes only time reporters whose Run Time Administration field is Y and whose Earliest Change Date field is less than or equal to the current or process date specified on the TA Run Control page. You can set the run control date to either the current date or another date (the process date) depending on whom you want to process and what periods you want to process.

We usually put the process date as the Pay End Date. For Example, if we are processing Bi-Weekly payroll, and for week1 time entries, we put the week1 end date, and for week2, we put the Pay End Date. we DO NO select the Use Reported Time for POI option at all.

So, it is an Important field if you are not using "use current date"; and I believe whatever Oracle has said equally important..

Hope this helps

User Exits in Time and Labor

2010-02-11T07:47:00.000-08:00

Question:

how to use user exits in TL rules?Hi, We are planning to use User Exits in T & L. This is what we did:Added a section in TL_TA_RULES AE prgram - Test01Then in Rule ID creation we used user exits - Test01 mapped to AE section - Test01. Now in the rule program we are not able to find this RULE ID. So how will this Peoplecode Rule ID be triggered if we are not able to attach it in the Rule Program? Are we missing something here?Please suggest.

Answer:

In Time and Labor, there are 4 different ways to create TL Rules. One of them is by using User Exit.

What is a User Exit?
Time and Labor User Exits are simply rules that you develop outside of the Time andLabor rules interface. Instead of compiling a rule to create an AE section, you create theAE section first, and then perform a few additional steps to register the section as a rulein Time and Labor.
One of the main reason to use User Exit in TL is to exploit the rich benefits the App Engine Programming Offers which is basicallyPeopleCode. Also, you would prefer it, if you are expert/comfortable in AE programming; Whenever any program is processed, you would want some log activity put in Process Monitor message log files, so you can also include this in User Exit. when you build rules through other online tools methid, there is no log activity for the rule you develop.
When you write user exits, you must add AE sections to the AE program TL_TA_RULES. You can use all the AE constructs supported by PeopleTools (SQL, PeopleCode, looping constructs like Do When, Do While, and so on).

Steps to create user exit:1.Create an Application Engine section with steps and actions to process the rule.Open TL_TA_RULES in Application Designer, and insert a new section and add your rule logic using SQL, PeopleCode, looping constructs like Do When, Do While etc. You must have the Public Access Checked on the section name as shown below:If this option is NOT selected, Time Administration will end abnormally with a message indicating that the rule does not allow access.

2. Define the AE Section in Time and Labor.Select Set Up HRMS, Product Related, Time and Labor, Validation Criteria, AE Section Definition. Here you add a new value, and enter the AE section as a User Exit.

3. Create the rule definition.Select set Up HRMS, System Administration, Utilities, Build Time and Labor Rules, Rules. Add a new value, and make sure to check the User Exit checkbox. The AE Section Name field must match the actual section name for the rule.

4. Add the rule to a rule program.Add the rule to a rule program.

During Migration of TL Rules:If you have written user-exit rules, you will need to include those AE Sections along with AE Steps from AE program: TL_TA_RULES in a project to be exported/imported (copied).

XML Publisher : Question

2010-02-11T05:54:00.000-08:00

Question: XML Output options are disabled on the output page in XML Publisher

Hi
I am using peoplesoft HR9.In XMLP, when defining new record definition,the XML Output options are disabled on the output page. Please help Thanks

Answer:

Please make sure that you add 2 delivered permission list to the Peopletools Role:

PTPT2500 (XMLP Power User )
PTPT2600 (XMLP Report Developer )

Note that the delivered reports tend to use the PeopleSoft User role as the author ID. If you are configuring security stick to roles - rather than assigning security by individual users.

You can also change this through:Reporting Tools > XML Publisher > Setup > Report Category

Also, by default, when you load the Report Definition Page, the output page is enabled with all format output options for the template type you pick in the Definition Page. check this table to see if the data is loaded or not:

select * FROM PSXPTMPLOUTFMT

if the data is missing from PSXPTMPLOUTFMT, then you may have to get it from your Demo system.

Step by Step PeopleSoft Installation

2010-02-10T20:09:00.001-08:00

Question:

Where can i find Step by Step PeopleSoft Installation documents?

Answer:

You can use PeopleSoft deliverd Install documents, but sometime it is hard to follow all the steps there. For Simple step by step Installation instructions including what PeopleSoft Softwares to download , check the below site:

Step by Step PeopleSoft Installation

Slow performance since oracle 10g upgrade...

2010-02-10T20:03:00.001-08:00

Question:

Our IT group did an Oracle 10g upgrade and ever since they did that it has slowed everything down, especially in the Ben Admin module.. has anyone else experienced this? and if so, any ideas as to why this would be happening? Our IT group won't give us an answer...

Answer:

If you using Oracle 10g Database for your PeopleSoft Enterprise Software, please check the below Red Pepper for performance related issues.

PeopleSoft Enterprise Performance on Oracle 10g Database
It is a 56 page PDF document related to performance on Oracle 10g using Enterprise PeopleSoft products. Some of the information covered include:- Generating Statistics

- Reviewing Dedicated Temporary Tables

- Selecting Tablespaces

- Maintaining Indexes

- Using Cursor Sharing

- Selecting Batch Servers

- Capturing Traces

- Sample Script to Gather Statistics On Tables

Download it from here:

Metalink Doc ID 747254.1

Also, there are many white papers and articles on how to improve the perfermonce:

1. An Oracle 10g Upgrade Case Study: Looking at System Performance Before and After the Upgrade

2. Oracle 10g Migration:slow performance after upgrade to Oracle10g

Hope this helps...

PeopleSoft Compare Reports

2010-02-10T19:47:00.000-08:00

Question :

While iam doing compare reports ,i have received the repost saying that SOURCE is -->ABSENT and TARGET is -->Present .What does it mean ,please help me on this.

Answer:

Whether you are doing a PeopleSoft Upgrade or trying to do a compare for certain objects, you need to understand what goes behind the compare process. Below are the points explained from upgrade perspective:

One of task related to PeopleSoft Upgrade is to perform Database CompareDuring the upgrade, you run several compare processes and then review the resulting reports.

There are several steps in the compare process:

1.Determines the Status of each object in Source/Target DB

2.Assign Copy Action

3.Assign Upgrade Action

4. Insert Definitions that differ into the Compare Project

5. Report the Project

from Target Database i.e. Copy of Prod, which is at 8.3 release level:

• The LASTUPDDTTM field in our PSobjectDEFN tables—such as PSRECDEFN, PSPNLDEFN, and so on—stores a date/time stamp of when each object was last modified.

• The LASTUPDOPRID field stores the operator ID of the user who made the modification. If Oracle made the modification, the proprietary ID PPLSOFT is used.

If an object definition is defined differently in the Demo database than in the Copy of Production, the compare process will check to see whether either object definition has changed since the comparison release. If the object’s LASTUPDDTTM value is greater than the RELEASEDTTM value for the comparison release level (stored in PSRELEASE), the object has changed. If the object’s LASTUPDDTTM value is equal to or less than RELEASEDTTM, the object has not changed (since the comparison release). Whether the compared object has changed or not, if it has ever been changed prior to the comparison release by someone other than Oracle (LASTUPDOPRID <> ‘PPLSOFT’), the object is identified as a customization.

Below are the status that you would get for Source and Target Databases based on Compare report:

For Example :
When you run the below SQL in Source Database, i.e. a new version Demo Database you get the results of the PS_JOB record:

When you run the below SQL in Target Database, i.e. a Copy of Production Database you get the results of the PS_JOB record:

For Source Status: Since the LASTUPDDTTM (7/12/2006 8:06:39 AM) of PS_JOB in Source DB is less than release table's RELEASEDTTM (11/29/2006 11:38:04 AM) , and sinceLASTUPDOPRID is PPLSOFT, the status for this object in Compare Report should come as "Unchanged"

For Target Status: Since the LASTUPDDTTM (6/4/2008 3:21:51 PM) of PS_JOB in Source DB is greater than release table's RELEASEDTTM (10/18/2001 12:44:59 PM) , and since LASTUPDOPRID is NOT PPLSOFT, the status for this object in Compare Report should come as "*Changed"

Absent in Source Database indicates that either you have created a new object in Copy of prod as part of customization or the object has become obsolete in new version and hence PeopleSoft has deleted/dropped it.

During the compare process, you would create a Project in which all like-named definitions that are not the same in both databases will be populated in the compare project; you also indicate the Compare Options , by going to

1. Select Tools, Compare and Report, To Database

2. Sign on to the target database; Select Options

Use the Compare Options dialog box to indicate this is a database compare:

Use the Report Options dialog box to designate the report options:

Use the Report Filter dialog box to designate which reports will be produced:

Filtering comparison reports doesn’t affect which objects get added to a project during a database comparison, only which objects are reported. Any object defined differently in the two databases will always be added to the project.

Assign Copy Action:

The default actions for each object that you compared are reported in the Action column. The compare sets the action column based on what you need to do to make the Copy of Production database consistent with the New Release Demo database. You should not change these actions. You can decide whether or not to accept each action by setting the Upgrade value. Action types include:

Assign Upgrade Action:

The upgrade action is either on (Yes) or off (No). The system assigns the upgrade action based on the target orientation:This table summarizes the various status, action, and upgrade action possibilities that can be applied to a single definition during the upgrade compare process:

Insert Definitions that differ into the Compare Project :

Report the Project :

Review reports using one of these methods:

1.View report in Application Designer

2.Print report

3.View report in browser

For third option:

1. Navigate to the report folder in Windows Explorer.

2. Double-click CompareViewer.html.

PeopleSoft Benefits Administration

2010-02-10T19:39:00.000-08:00

Question:

I'd like to learn PeopleSoft Benefits Administration step by step. Are there any online tutorials?

Answer:

if you are looking for PeopleSoft Benefits Administration training , here's a site that has step by step tutorials:

Check here PeopleSoft Benefits Administration

Calculating Life Imputed Income

2010-02-10T19:18:00.001-08:00

Question:

How does PeopleSoft calculate the imputed income on group term life? Is the $50,000 limit on a table or is it part of the payroll calculation process (COBOL)?

Answer:

Let's try to understand what is Imputed Income when tied to Group-Term Life Insurance?

Imputed income is like a conceptual income.The value of the first 50,000 USD of group-term life insurance that a employer provides to a U.S. employee is not considered taxable income. The value of coverage in excess of 50,000 USD (computed according to Internal Revenue Service [IRS] regulations) minus premiums that the employee pays with after-tax dollars, is considered taxable income and is subject to social security and Medicare taxes. Although you must report the amount as taxable income on the employee’s Form W-2, the value of excess group-term life insurance coverage is not subject to federal income tax withholding.

i.e. premium amounts for life insurance in excess of $50,000 in coverage are considered taxable income. This conceptual income is added to the employee’s gross wages, and the employee is taxed on this amount.

For Example:

If an employee who makes 40,000 USD a year is enrolled in a group term life benefit plan of two times salary, that employee receives 80,000 USD in life insurance. The premium amount for this excess 30,000 USD is considered taxable compensation. The value of this excess group term life insurance premium is considered imputed income.

To calculate imputed income for all group-term life plans (except dependent life) the system performs the following processes when you run the Pay Calculation COBOL SQL process (PSPPYRUN):

1. Determines the total life insurace coverage for the employee, including both employer and employee paid coverage for all plans in which the employee is enrolled.

2. Substracts $50,000.00 from the total coverage (i.e. first 50,000.00 is not taxable per IRS). if the resulting amount is greater than Zero, then the cost of the coverage for that amount is considered taxable. PeopleSoft Payroll will use this cost to calculate the Imputed Income.

3. Uses the IRS Uniform Premium table. the data for this table is stored on the IRS Age Graded Rate table in the Benefit Rate (IRS as the Rate Table ID in Version 9.0). This table is maintained by PeopleSoft, and should not be changed .The age is based on the age as of December 31 of the year in which the benefit is taxable. There is no need to enter the IRS rate table in the Benefit Deduction Program table, because the system uses it automatically.

4. Substracts any employee paid after-tax constributions to the coverage. The resulting amount is considered taxable. This is the amount that will be added to the Employee's taxable gross.

IRS Uniform Premium table:

Example of Imputed Income Calculation:

An employee might be liable for imputed income, even if there is no employer contribution on all of the life insurance plans. If the employee has more than one type of life coverage, the system calculates imputed income in an iterative manner.

For example, Robert, age 60, has basic life (employer- and employee-paid) and supplemental life (employee-paid):

Plan Type	Description	Coverage	Premium
20	Life	150,000 USD	Employer-paid premium: 49 USD Employee-paid premium: 10 USD
21	Supplemental life	200,000 USD	Employer-paid premium: 0 USD Employee-paid premium: 100 USD

Plan
Type

Description

Coverage

Premium

Life

150,000 USD

Employer-paid premium: 49 USD

Employee-paid premium: 10 USD

Supplemental life

200,000 USD

Employer-paid premium: 0 USD

Employee-paid premium: 100 USD

Robert is paid monthly. The following illustrates how the system calculates Robert’s paycheck deductions:

The system calculates the basic life plan:

1. Determine the total coverage for basic life: 150,000 USD

2. Calculate the amount that is subject to imputed income by subtracting 50,000 USD from the total coverage:

3. 150,000 USD – 50,000 USD = 100,000 USD subject to imputed income.

4. Apply the IRS Uniform Premium table.

Robert is 60 years old. In this age bracket, the Uniform Premium table calls for a calculation of 1.17 USD per month per 1,000USD of coverage: 100,000 USD / 1,000 USD x 1.17 USD = 117.00 USD

5. Subtract employee-paid, after-tax contributions to the coverage:

6. 117 USD – 10 USD = 107 USD taxable benefit.

7. The system calculates the supplemental life plan:

8. Determine the total coverage:

9. 150,000 USD basic life + 200,000 USD supplemental life = 350,000 USD total coverage.

10. Subtract 50,000 USD from the total coverage to determine the imputed income:

11. 350,000 USD – 50,000 USD = 300,000 USD subject to imputed income.

12. Apply the IRS Uniform Premium table.

13. Robert’s age of 60 calls for a calculation of 1.17 USD per 1,000 USD of coverage.

14. 300,000 USD / 1,000 USD x 1.17 USD = 351.00 USD.

15. Subtract employee-paid, after-tax contributions to the coverage

16. 351 USD – 110 USD = 241 USD total taxable benefit.

17. The system subtracts the initial 107 USD taxable benefit for basic life from the 241 USD total taxable benefit to determine the supplemental life taxable benefit:

v18. 241 USD – 107 USD = 134.00 USD.

19. Robert’s Paycheck Deduction record displays:

Plan Type	Tax Class	Amount
Life	After-Tax	10 USD
Life	Nontaxable Benefit	49 USD
Life	Taxable Benefit	107 USD
Supp (supplemental)	After-Tax	100 USD
Supp	Taxable Benefit	134 USD

Plan
Type

Tax
Class

Amount

Life

After-Tax

10 USD

Life

Nontaxable Benefit

49 USD

Life

Taxable Benefit

107 USD

Supp (supplemental)

After-Tax

100 USD

Supp

Taxable Benefit

134 USD

Where is the 50,000 Limit coming from? is it in a table or in the process itself?

Well, if you look at the PSPDCLIF.cbl (part of Pay Calc Process), here's where the limit amount is taken into consideration. It is hard coded in the Cobol Program.

HRMS-Payroll for North America-Third Party Sick Pay

2010-02-10T19:12:00.001-08:00

Question:

We are starting to use 3rd party sick pay for some employees and are having a little trouble setting up the earnings code properly.Our 3rd party vendor takes EE FICA and OASDI, but not ER so when we process it in PeopleSoft we want to be able to caluculate the ER side, but not the EE. I seems to be an all or nothing set up in PS though.Has anyone else experienced this or have any ideas for a solution? Thanks

Answer:

In PeopleSoft Earning Code Setup, you can specify whether the earnings are subjected tp Federal Level taxes (FWT , FICA and FUT);

if all the Subject to FICA box is checked, then the EE and ER taxes are withheld from the Employee's paycheck; you cannot specify take only EE and dont take ER or vice-versa;

FICA includes Medicare and OASDI;

if you pay H32 earnings of 1000.00 USD, here's how the paycheck taxes look like:

If you see, both EE and ER taxes are withheld at FICA level; if you want to take only ER and not EE FICA taxes, you need to use One-Time Tax Setup at paysheet level:

if you have many employee's with this setup, then you might write a custom process to load data into PS_PAY_TAX_OVRD

Canadian Bonus Tax

2010-02-10T18:02:00.000-08:00

Canadian Bonus Tax

Question:

Hi, We are running PeopleSoft 9.0(using Payroll for North America) and PeopleTools 8.49. We ran a one time bonus that included only bonus earnings, NO regular earnings. We added an extra pay period in the Pay Calendar Table. My problem is I'm not understanding how PeopleSoft is calculating the Taxes. The earning code is setup with the Bonus Tax Method checked. Can someone please help me understand how PeopleSoft is calculating the taxes?

Answer:

This calculation method depends upon whether the bonus payment is included with the regular earnings (using the annualized tax method) or the bonus payment is paid on a separate cheque.

Bonus Included with Regular Earnings

When bonus is included with Regular Earnings (annualized tax method), in addition to the 3 Calculation Steps outlined, the first 2 Steps are to calculate pay period income taxes on the Regular Earnings using the Annualized Tax Method.

Calculation Step 1 – Determine annual taxes payable by annualizing the Regular Earnings

Calculation Input - The following will derive annual taxable gross: Regular Earnings X total pay periods in the year.

Calculation Output - Perform the annualized tax calculation to produce the annual income taxes.

Calculation Step 2 - Determine pay period income taxes for the Regular Earnings.

Calculation Input - The following will derive pay period income taxes: Annual income taxes (from Step 1) / total pay periods in the year.

Calculation Output - Pay period income taxes on the Regular Earnings.

The following table shows how the system calculates the tax payable when the bonus is included with regular earnings:

Calculation Step

Calculation Input

Calculation Output

1. Determine annual taxes payable using
annualized earnings including the bonus payment.

The following will derive annual taxable
gross:(CIT taxable earnings gross year-to-date [YTD], including YTD bonus) + (current annualized tax method earnings ? no. of pays remaining in the year including the current period) + (current bonus payment)

Perform tax calculation and the result will be annual income taxes which for this exercise will be Base Amount A.

2. Determine annual taxes payable using
annualized earnings excluding the current bonus payment.

The following will derive annual taxable gross: (CIT
taxable earnings gross YTD, including YTD bonus) + (current annualized tax method earnings ? no. of pays remaining in the year including the current period)

Perform tax calculation and the result will be annual income taxes which for this exercise will be Base Amount B.

3. Determine pay period income taxes
payable on the bonus payment.

The following will derive pay period income taxes on the bonus payment: (Base Amount A – Base Amount B)

Pay period income ax payable on bonus
payment.

4. Determine pay period income taxes for
the Regular Earnings and the Bonus payment.

The following will derive pay period income taxes for both Regular Earnings and the Bonus payment: Pay period income
taxes on the Regular Earnings + Pay period income taxes on the Bonus payment

Total pay period income taxes for this
combined payment (cheque).

Bonus Paid on a Separate Cheque

This table shows how the system calculates the tax payable when the bonus is paid on a separate cheque with no regular earnings:

Calculation Step	Calculation Input	Calculation Output
1. Determine annual taxes payable based on estimated annualized earnings including the bonus payment.	The following will derive projected annual taxable gross: (CIT taxable earnings gross YTD, including YTD bonus) + (pay period pay rate from the employee’s Job Data record X No. of pay periods remaining in the year including the current pay period)+ (current bonus payment)	Perform tax calculation and the result will be annual income taxes which for this exercise will be Base Amount A.
2. Determine annual taxes payable based on estimated annualized earnings excluding the current bonus payment.	The following will derive projected annual taxable gross: (CIT taxable earnings gross YTD, including YTD bonus) + (pay period pay rate from the employee’s Job Data record X No. of pay periods remaining in the year including the current pay period)	Perform tax calculation and the result will be annual income taxes which for this exercise will be Base Amount B.
3. Determine taxes payable on the bonus payment.	(Base Amount A – Base Amount B)	Tax payable on bonus payment.

TableSet Sharing in PeopleSoft

2010-02-10T17:27:00.001-08:00

Question:

What is SetID and how does TableSet Sharing works in PeopleSoft?

Answer:

Before we answer this question, we must try to understand the basic type of tables in PeopleSoft.

In PeopleSoft, we store information in different type of Tables. These tables serve as a repository to establish and maintain all of your company's core data online. The different types of tables that we are talking about are - Control Tables and Transaction Tables.Control tables store information that defines the company's structure and processing rules. Control tables are generally static; they change only when you perform specific maintenance appropriate to changes in your business policies, organizational structure, or processing rules. Examples of Control Tables are - PS_DEPT_TBL (Department Table), PS_LOCATION_TBL (Location Table) etcTransaction tables store data about day-to-day business activities. These tables may be updated more frequently than values in a control table. Examples of such tables are: PS_JOB, PS_NAMES and PS_ADDRESSES etc.

Difference between Transaction and Control Table:

Most data recorded in control tables is stored by Table Set ID (also called as SetID). Whenever your enter information in control table, you must enter the SetID to establish the ownership of that information. A grouping of data that is keyed by the same SetID is called a TableSet.

Establishing your SETID(s) is one of the first steps in setting up your foundation table's data within your system. The SETID table is a delivered PeopleSoft table used to label and identify Tablesets. Setids allow Business Units the option of sharing or decentralizing data in the control tables.

Once you've setup a SETID, you can create a Business Unit and link the setID to it. So, when you create a business unit in the system, you must assign it a setID. The setID determines which values in various control tables a business unit has access to. For example, suppose you have created a business unit called ABCBU, the system required you enter a setID. In this case you can enter TSTID as the setID for the business unit - ABCBU.So, what is a Business Unit? In PeopleSoft, a Business Unit is an Operation area or subset of an Organization. A business unit is an organizational entity which maintains its own transaction data. Once you define business unit, you will have control tables data that would represent for that business unit.

Definition of Tablesets and SetIDs:A TableSet is a group of rows (set of data) in a control table that is identified by the same high-level key. A setID is a label (high-level key) that identifies a TableSet. Tablesets and SetIDs are devices that enable you to share - or restrict - information across business units. For example, with TableSets and SetIDs you can centralize redundant information such a country codes while keeping information such as departments and job codes decentralized. The overall goal of TableSets and SetIDs is to minimize data redundancy, maintain data consistency, and reduce system maintenance tasks. The setID, or additional primary key, is what enables the sharing of control table information to take place across business units.

You must define at least one TableSet/setID. The SETID key field is included on all control tables

Record Groups:In order to share data among different business unit using TableSet feature, all control tables are divided into Record Groups. So, we group control tables to form something called as Record Groups. The control tables used by each of the HRMS applications are grouped by function into record groups. A record group is a set of logically and functionally related control tables and views. All tables in the same record group will have the same key on each table.

Once you have created a SetID and Business Unit, you need to map a relationship between this two using the record groups. With this you will determine which SetID you want the system to access for each of the above delivered record groups for HR or PY for each business unit. So, when you create a business unit, the system creates an entry in the TableSet Control component for the business unit, populated with every record group in the system, and associates with each record group the setID that you selected for the business unit. For Example, if we have created a business unit as ABCBU and mapped SetID as TSTID, at the TableSet Control component for ABCBU, it should have TSTID as the SetID mapped to all available record groups

All of these values defaulted from the business unit setup. Here you can modify the mapping of SetID to each individual record group, i.e. when you want the business unit to have access to the rows in other SetIDs for certain record groups, change the default setID to the appropriate setID.
So,based on this setups, when you open a Transactional page like Job Data, and you try to query any Control Table Based prompt fields like Location, Department or Job Code , you will get the results based on the Business Unit and the SetID Combination that was set in Set Control Page. So for example, if you have Location Table with 10 rows, 8 rows had TSTID as the SetID and 2 rows with USA01, and if you have ABCBU as the business unit in the Job Page, you should see 8 rows of Location Data when you click on the Prompt Table of Location Field.

How to indentify bundles that have been applied?

2010-02-10T17:18:00.000-08:00

Question: How do i know what bundles have been applied in my PeopleSoft Application System?

Answer:

All bundles update activity that are been applied to PeopleSoft system is logged into a table called PS_MAINTENANCE_LOG.you can check to this table to see what Bundles or Tax Updates have been applied. Below are the steps how to write a query in QueryTools (2 tier):

1. if you want a PS Query to be built, make sure you have access to this table. if you do not, you need to add this record into query security.

2. once you have access to PS_MAINTENANCE_LOG table, here's how to write the query, add the fields as shown in below screen shot:

3. make sure that for the descr field, you order it by descending.

4. go to expression and right click and pick new expression and enter 1 and say ok

5. go to criteria tab and drag the expression

6. right click on the query criteria expression 2 and select expression

7. enter - 1 AND upper(A.DESCRLONG) like '%BUNDLE%' in the expression box:

8. you should get the query results as shown below:

9. if you are looking to find what tax updates have been applied, either you navigate to this menu:

Set Up HRMS > Product Related > Payroll for North America > Tax Table Reports >Tax Update

or change the upper(A.DESCRLONG) like '%BUNDLE%' expressionto upper(A.DESCRLONG) like '%TAX UPDATE%';

10. alternatively, if you have access to SQL tool, run the below queries:

Bundles Query:

SELECT A.UPDATE_ID, A.DESCR, A.DTTM_IMPORTED, A.FIXOPRID, A.APPLYOPRID, A.PRODUCT_LINE, A.RELEASEDTTM, A.RELEASELABEL, A.MAINTLOGTYPE, A.DESCRLONG FROM PS_MAINTENANCE_LOG A WHERE upper(A.DESCRLONG) like '%BUNDLE%' ORDER BY 2 DESC

Tax Update Query:
SELECT A.UPDATE_ID, A.DESCR, A.DTTM_IMPORTED, A.FIXOPRID, A.APPLYOPRID, A.PRODUCT_LINE, A.RELEASEDTTM, A.RELEASELABEL, A.MAINTLOGTYPE, A.DESCRLONG FROM PS_MAINTENANCE_LOG A WHERE upper(A.DESCRLONG) like '%TAX UPDATE%' ORDER BY 2 DESC

Balance ID has not been defined for Calendar Year. (2000,258)

2010-02-10T16:25:00.000-08:00

Question:

Balance ID has not been defined for Calendar Year. (2000,258)When I try to create a pay calender automatically in HRMS 9.0, I'am getting an error "Balance ID not found". When I try to create a pay calender manually, after giving the Check date, am getting an error "Balance ID has not been defined for Calendar Year. (2000,258)"Any solutions? Thanks

Answer:

If you are using PeopleSoft Payroll Module, there are 2 places where you use SetID concept. One would be for Balance ID tables and other at Shift Table.

So,in Payroll for North America, there are two set control values that require the use setID functionality:

1. Company table setup: Companies that are associated with the same setID share the same rules for maintaining balances, as indicated on the Balance ID table.

2.Pay Group table setup: Pay groups that are associated with the same setID share the same shifts, as defined on the Shift table. You use Balance ID tables so that your organization stores month-to-date, quarter-to-date, and year-to-date balances that can be used for reporting purpose (For Example W-2 reporting)

When you define a Company, you can notice Default SetID is same as Company name. You can override this value with different SetID.If you are using a SetID of SHARE in your HR Module, you can provide SHARE here.

Once you define a company, go to Set Control values i.e under PeopleTools > Utilities > Administration > TableSet Control and check for ABC:

for PY_01 record groupm check the SetID.
Then for this SetID, you need to define a Balance ID table.

When you create Pay Calendars for the Company,Paygroup, the CALENDAR Process Selects Balance ID from these Tables

PS_BALANCE_ID_DEF
PS_BALANCE_ID_QTR
PS_BALANCE_ID_TBL

and makes sure that for the Company's SetControl Value's SetID, if there is a definetion. if not, you will get the error:

Balance ID has not been defined for Calendar Year. (2000,258)
So, make sure that the Balance ID is defined.

Trace AE and COBOL processes

2010-02-10T16:05:00.000-08:00

Question:

How to trace AE and COBOL processes using the Process Definitions instead of setting on Process Scheduler / App Server Config files.

ANSWER:

For AE, Open the Process Definition under PeopleTools, Process Scheduler. Go to the override tab, and on the Parameter list line select Append from the dropdown, and in the edit box next to it, you can use the desried combination of traces, they all are;

Parameter List Append -TRACE 7 -TOOLSTRACEPC 3596 -TOOLSTRACESQL 31

Save the Definition and hence forth this program will be traced each time it is run, until this is removed. Using Both the -TOOLSTRACEPC and -TOOLSTRACESQL together should only be done when required, as the output from both go into the same file, making it very large and difficult to read. For normal program tracing using just the;

-TRACE 7 -TOOLSTRACEPC 3596

Give the Application Engine Trace, which traces the SQL in an AE program, and the PeopleSoft Trace, which is the pcode trace.

The above settings have equivelent settings in psprcs.cfg, they are;

TraceAE= -TRACE output goes into Application Engine Trace (.AET) TracePC= -TOOLSTRACEPC output goes into the PeopleTools trace file (.trc) TraceSQL= -TOOLSTRACESQL output ALSO goes into the PeopleTools trace file (.trc)

Again, depending on what the program is doing, most commnoly we'd use the -TRACE and -TOOLSTRACEPC together.

The only time I use the -TOOLSTRACESQL is when we're looking for a problem with the psae program itself.

For COBOL the idea is similar, we won't be appending to the parameter list instead we'll be overriding it. So first step is to open the appropriate Process Type Definition, example;

Process Type defn COBOL NT/Win2000 ORACLE

Copy the whole parameter list line into you mouse clipboard;

%%PRCSNAME%%%%DBTYPE%%/%%DBNAME%%/%%OPRID%%/%%OPRPSWD%%/%%RUNCNTLID%%/%%INSTANCE%%//%%DBFLAG%%

Then open the Process Definition for the particular COBOL Process, go to the Override Tab, and on the Parameter list line, select Override from the drop down. Then in the Parameter Edit box, paste the whole parameter list from the Process Defn we just got;

%%PRCSNAME%% %%DBTYPE%%/%%DBNAME%%/%%OPRID%%/%%OPRPSWD%%/%%RUNCNTLID%%/%%INSTANCE%%//%%DBFLAG%%

Notice at the end of the line after the %%INSTANCE%% and before the %%DBFLAGS%% there are 2 // We need to insert the desired bit map number inbetween the slashes.

Choose the bitmap number you want to use for the trace, and put it between the slashes like so;

%%DBTYPE%%/%%DBNAME%%/%%OPRID%%/%%OPRPSWD%%/%%RUNCNTLID%%/%%INSTANCE%%/255/%%DBFLAG%%

Save the Process Definition and once you launch the COBOL or AE program you can go to the Process Monitor, Details, Parameter List, and see the expanded command line and you'll see your trace value inserted;

Command Line: PSRUN PTPDBTST ORACLE/E840D20P/VP1/%OPRPSWD%/1/475/255/%DBFLAG%

With both the AE and Cobol traces done like this once this is done, everytime the program runs it will be traced. Need to undo all of this setting the override back to None in both Definitions will turn it off.

Absence Management Setup

2010-02-10T15:29:00.000-08:00

Question:

I am trying to understand complete setup required for Absence Management to work for Employee /Manager self service to work. Any info will be gretly appreciated.

Answer:

You can use PeopleSoft Delivered Setup Manager to generate a list of setups required here.

Setup Manager is a tool that helps you implement PeopleSoft applications by using a project and predefined tasks to produce a setup task list that is specific to your implementation project.

Here's a short level of information on how to use Setup Manager to generate a list of setup tasks required for Absence Management Product:

Navigate to PeopleTools -> Setup Manager

Click on Manage Implementation Projects Link:

Click on Products Button:

Select Absence Management and you can click on the link to further deselect the product features list. By default 10 of 10 are selected.

Click on View Summary:

Click on Save Button

Click on Generate Setup Tasks button.

A process is submitted to Process Scheduler. Once it is completed, you can click on View Setup Tasks:

once the list is generated, you can download the list into Excel Spreadsheet:

Sample PeopleSoft Certification Questions

2010-02-10T15:25:00.000-08:00

Question:

Where can i find Sample PeopleSoft Certification Questions?

Answer:

You can get or find Sample PeopleSoft Certification Questions here at the below link:

1Z0-218 PeopleSoft Enterprise 9 HRMS Fundamentals Sample

'Salary replacement percentage' in disability plans

2010-02-10T15:13:00.000-08:00

Question:

Can anyone let me know what's the significance of salary replacement percentage field in disability plans?If employee is to be paid a percentage of salary during disability period, will this field play any role or how can it be achieved in NA payroll?

Answer:

Premiums are based on employee salary or covered salary, whichever is lower.Covered Salary = Maximum Monthly Benefit ÷ Salary Replacement Percentage.

So if a vendor like Liberty Mutual for example has a plan that provides a salary replacement value up to 50% of your annual base compensation, with a monthly maximum of $7,500.00 , you will setup that in your LTD Plan in Base Benefits Table.

In order to calculate the premium that needs to be deducted from EE who enrolled into this plan, Rate tables must be setup for this plan.

Let's assume that, EE monthly salary is 10,000.00. The benefit amount is 50 percent of that. Because the benefit amount is less than the maximum monthly benefit (7500.00) , 50 percent of salary is used to calculate the premium.

if .4 is the rate per hundred, then ($10,000 ÷ 100) × .4 × 12 = $480...This will be the annual premium.

If the Monthly Salary is 20,000.00 and the max benefit amount would be $7,500.00 , because the Salary replacement percentage of 50% which is (50% of 20,000K) is exceeding the max limit of 7500.00; the calculated base for premium amount would be 15k only;

($15,000 ÷ 100) × .4 × 12 = $720...This will be the annual premium.

Hope this helps..

Looking up a Shift in the Shift table

2010-02-10T15:03:00.000-08:00

Question:

What Table.Field is used to determine the SETID used when looking up a Shift in the Shift table during PayCalc?

Answer:

There are number of ways to define Shift in PeopleSoft Payroll as indicated in this previous post:

if you are defining Shift through the Paygroups or even some other method, PeopleSoft Payroll needs you to define at least one shift in PS_SHIFT_TBL; The shift you define is based on the SETID you select in PS_PAYGROUP_TBL; So, the Shift is connected to Paygroup that you define for your company;

When you define a paygroup, there is a Set ID in the paygroup, that is defaulted same as paygroup;you can change it to your HR SetID, but this should be defined in the SetID Table and SetControl value before you change it; or you can leave the default value as it is and come back and change it;

if you want to change it, you need to do the following setup:For the Paygroup value you are defining, go to SetControl table that is under TableSet Control (TableSet Control - PeopleTools Utilities Administration TableSet Control ) enter the paygroup value under Set Control Value: and under PY_02 record group, change the value for SetID;

For this SetID, you need to define a shift value; if you are not using the Shift Table, you must define at least one shift as shown below:

So, when a paycalc is run, it checks the paygroup's SetID; For this value it checks the SetControl Table and under PY_02 record group, for the value of the SetID, there should be a Shift Defined;

Else, you should expect a payroll error :
Message ID : 000049
Shift Not Found
The shift displayed below was not found.

Tables/Fields for Shift Defination and paycalc process: PS_SHIFT_TBL , PS_PAYGROUP_TBL , PS_SETID_TBL , PS_SET_CNTRL_REC

Hope this helps...