Tables (PeopleTools.

HRMS,Benfits,,Payroll)
PeopleTools Tables
Projects
* PSPROJECTDEFN Project header table
* PSPROJECTITEM Definitions in the project
Fields
* PSDBFIELD Fields in the system
* PSXLATITEM Translate Values
Records
* PSRECDEFN Record header table
* PSRECFIELD Fields in the record (subrecords not expanded)
* PSRECFIELDALL Fields in the record (subrecords expanded)
* PSKEYDEFN Indexes
* PSTBLSPCCAT Tablespaces
* PSRECTBLSPC Records tablespace assignments
Pages
(Note: Pages still have the name panels in the PeopleTools table names)
* PSPNLDEFN Page header table
* PSPNLFIELD Page controls (field types/FIELDTYPE)
* PSPNLHTMLAREA Static HTML Areas on Pages
Components
(Note: Components still have the name panel group in the PeopleTools table names)
* PSPNLGRPDEFN Component header table
* PSPNLGROUP Pages in the components
Component Interface

* PSBCDEFN header record; one row for each component interface

* PSBCITEM one row for each property
Menus
* PSMENUDEFN Menu header table
* PSMENUITEM Items (components) on the menu
Security
* PSCLASSDEFN Permission List header table
* PSAUTHITEM Menu items granted security by permission lists
* PSROLEDEFN Role header table
* PSROLECLASS Permission Lists in roles
* PSOPRDEFN User ID header table
* PSROLEUSER Roles granted to users
Process Scheduler
* PS_PRCSDEFN Process Definition Header
* PS_PRCSDEFNGRP Process Group
* PS_PRCSDEFNPNL Component
* PS_PRCSJOBDEFN Job Header
* PSPRCSRQST Process Request Instances
* PS_PRCSJOBITEM Job Processes
Portal
* PSPRSMDEFN Content References and Folders
* PSPRUHTABPGLT Portal User HP Tab Pagelet
Change Control
* PSCHGCTLHIST shows history of locked definitions with project name, incident, and

description
* PSCHGCTLLOCK shows definitions that are currently locked
Application Engine
* PSAEAPPLDEFN header record; 1 row per app engine
* PSAEAPPLSTATE state records assigned to app engines
* PSAEAPPLTEMPTBL temp tables assigned to app engines
* PSAESECTDEFN sections
* PSAESTEPDEFN steps
* PSAESTEPMSGDEFN
* PSAESTMTDEFN actions (action types)
List Log Messages
HTML Definitions
* PSCONTDEFN header record; last update time, etc.
* PSCONTENT stores actual text in the HTML definition
SQL Definitions
* PSSQLDEFN header record; last update time, etc.
* PSSQLTEXTDEFN stores actual text in the SQL definition
File Layout Definitions
* PSFLDDEFN header record; last update time, etc.
* PSFLDSEGDEFN stores the segments for each layout
* PSFLDFIELDDEFN stores the fields for each layout
Workflow
* APPR_RULE_DETL - Approval Rule Defn Details
* APPR_RULE_FIELD - Approval Rule Defn Route Cntl
* APPR_RULE_AMT - Approval Rule Amounts

* RTE_CNTL_LN - Route Control Profile Line

* RTE_CNTL_RUSER - RoleUser Route Cntl Profiles
* RTE_CNTL_TYPE - Route Control Type
* RTE_CNTL_HDR - Routing Control Type

PeopleSoft HR Tables
PS_EMPLOYEES
PS_EMPLOYEES_LNG
PS_EMPLOYMENT
PS_EMPLOYMENT_LNG
PS_EMPLOYMENT_LNG1
PS_EMPLOYMENT_LNG2
PS_EMPLOYMENT_LNG3
PS_HS_EMPLOYMENT
PS_HS_EMPL_REL_CAN
PS_HS_EMPL_REL_LNG
PS_HS_EMPL_SUB_CAN
PS_HS_EMPL_SUB_LNG
PS_INJ_CLMADDR_CAN
PS_JOB
PS_PERSONAL_DATA
PS_PERSONL_DTA_LNG
PS_PERS_DATA_AET
PS_PERS_DATA_EFFDT
PS_PERS_DTAEFF_LNG
PS_PERS_NID
PS_JOB_EARNS_DIST
PS_JOB_APPROVALS
PS_BEN_PROG_PARTIC

PeopleSoft Base Benefits Tables

PS_BAS_PARTIC
PS_BAS_PARTIC_COST
PS_BAS_PARTIC_DPND

PS_BAS_PARTIC_INVT
PS_BAS_PARTIC_OPTN
PS_BAS_PARTIC_PLAN
PS_BENEF_COMMENT
PS_BEN_PROG_PARTIC
PS_DEPENDENT_BENEF
PS_DISABILITY_BEN
PS_FSA_BENEFIT
PS_FSA_PAYMENT
PS_HEALTH_BENEFIT
PS_HEALTH_DEPENDNT
PS_LEAVE_ACCRUAL
PS_LEAVE_PLAN
PS_LIFE_ADD_BEN
PS_LIFE_ADD_BENEFC
PS_PENSION_BENEFC
PS_PENSION_PLAN
PS_RTRMNT_PLAN
PS_SAVINGS_BENEFIC
PS_SAVINGS_INVEST
PS_SAVINGS_PLAN
PS_VACATION_BEN

People Payroll Tables

PS_STATE_TAX_DATA
PS_GENL_DEDUCTION
PS_BAL_ADJ_UI_CAN
PS_CAN_CHECK_YTDPS_CAN_DED_BALANCE
PS_CAN_ERN_BALANCE
PS_CAN_TAX_BALANCE
PS_CAN_TAX_DATA
PS_CHECK_YTDPS_DEDUCTION_BAL
PS_EARNINGS_BAL
PS_FED_TAX_DATA

PS_TAX_BALANCE
PS_LOCAL_TAX_DATAPS_BAL_ADJ_ARR
PS_BAL_ADJ_CHK
PS_BAL_ADJ_CN_CHK
PS_BAL_ADJ_CN_DED
PS_BAL_ADJ_CN_ERN PS_BAL_ADJ_CN_TAX
PS_BAL_ADJ_DED
PS_BAL_ADJ_ERN
PS_BAL_ADJ_GRN
PS_BAL_ADJ_TAXPS_DED_ARREARS
PS_GARN_RULE
PS_GARN_SCHED
PS_GARN_SPEC
PS_GENL_DED_CD

Complete PeopleSoft Tables

PS_EMPLOYEES
PS_EMPLOYEES_LNG
PS_EMPLOYMENT
PS_EMPLOYMENT_LNG
PS_EMPLOYMENT_LNG1
PS_EMPLOYMENT_LNG2
PS_EMPLOYMENT_LNG3
PS_HS_EMPLOYMENT
PS_HS_EMPL_REL_CAN
PS_HS_EMPL_REL_LNG
PS_HS_EMPL_SUB_CAN
PS_HS_EMPL_SUB_LNG
PS_INJ_CLMADDR_CAN
PS_JOB, PS_PERSONAL_DATA
PS_PERSONL_DTA_LNG
PS_PERS_DATA_AET
PS_PERS_DATA_EFFDT
PS_PERS_DTAEFF_LNG

PS_PERS_NID
PS_JOB_EARNS_DIST
PS_JOB_APPROVALS
PS_STATE_TAX_DATA
PS_GENL_DEDUCTION
PS_BAL_ADJ_UI_CAN
PS_CAN_CHECK_YTD
PS_CAN_DED_BALANCE
PS_CAN_ERN_BALANCE
PS_CAN_TAX_BALANCE
PS_CAN_TAX_DATA
PS_CHECK_YTD
PS_DEDUCTION_BAL
PS_EARNINGS_BAL
PS_FED_TAX_DATA
PS_TAX_BALANCE
PS_LOCAL_TAX_DATA
PS_BAL_ADJ_ARR
PS_BAL_ADJ_CHK
PS_BAL_ADJ_CN_CHK
PS_BAL_ADJ_CN_DED
PS_BAL_ADJ_CN_ERN
PS_BAL_ADJ_CN_TAX
PS_BAL_ADJ_DED
PS_BAL_ADJ_ERN
PS_BAL_ADJ_GRN
PS_BAL_ADJ_TAX
PS_DED_ARREARS
PS_GARN_RULE
PS_GARN_SCHED
PS_GARN_SPEC
PS_GENL_DED_CD
PS_BAS_PARTIC
PS_BAS_PARTIC_COST
PS_BAS_PARTIC_DPND

PS_BAS_PARTIC_INVT
PS_BAS_PARTIC_OPTN
PS_BAS_PARTIC_PLAN
PS_BENEF_COMMENT
PS_BEN_PROG_PARTIC
PS_DEPENDENT_BENEF
PS_DISABILITY_BEN
PS_FSA_BENEFIT
PS_FSA_PAYMENT
PS_HEALTH_BENEFIT
PS_HEALTH_DEPENDNT
PS_LEAVE_ACCRUAL
PS_LEAVE_PLAN
PS_LIFE_ADD_BEN
PS_LIFE_ADD_BENEFC
PS_PENSION_BENEFC
PS_PENSION_PLAN
PS_RTRMNT_PLAN
PS_SAVINGS_BENEFIC
PS_SAVINGS_INVEST
PS_SAVINGS_PLAN
PS_VACATION_BEN

A quick list of Absence Management Tables

I was thinking of writing a short yet extremely useful post and the first thing that came to my
mind is Application Tables....For a table driven product like peoplesoft, getting to know the main
records and their function is a huge plus.
So here is a very quick list of important tables in Absence Management.
1. PS_GP_PIN - Table that stores the pin details of all elements in GP/AM. Use to retrieve the
Pin Name or Pin Code corresponding to a pin number.
2. PS_GP_ABS_EVENT - Major transaction table in Absence Management. All absences
reported get stored in this table. The data in this table the raw reported absence. This table is
analogous to the TL_RPTD_TIME table in Time and Labor.

3. PS_GP_RSLT_ABS - Table containing the calculated result of reported absence takes. The
source for this table is GP_ABS_EVENT. This table is analogous to the TL_PAYABLE_TIME
table. This table will contain one row for each day of the absence event. For example, an
employee might report sick leave from the 1st to 5th of a month. GP_ABS_EVENT will have a
single entry for the above event with a start date and end date. But, GP_RSLT_ABS will have
five rows with each row containing the number of hours or days of absence.
4. PS_GP_RSLT_ACUM - Table containing the results of the accumulators in GP/AM.
Accumulators can be used to track absence balances, cumulative takes, cumulative paid hours
etc. This table is populated only after the absence calculation COBOL is run.
5. PS_GP_CAL_RUN - Table containing details regarding the Calendar Group ID. The
Calendar Group ID is the major run control parameter used for running the absence processes
and is a collection of various calendars.
6. PS_GP_PI_GEN_DATA - Any absence event that need to be sent to payroll will require a
positive input (in terms of an Earning Code) to be defined. The positive input can be attached to
a take in the Absence Take setup page. This table contains the corresponding positive input for
the processed absences.
7. PS_GP_ABS_SS_STA - This table is coupled with the GP_ABS_EVENT table and is a
workflow table. This table can be used to know the workflow status of an absence event. A
separate entry is created for each workflow actions like Submit, Approval etc. This table can be
very useful to track details regarding the approval/workflow status of an absence event.
e would like to point out to customers who are on v9.1 (and excellent if you are on 8.52 tools as
there are significant enhancements to related content framework in 8.52), that they should be
making use of the related content feature to build similar usability enhancements. The 'related
actions' framework delivered in 9.1 Feature Pack 2,can be further used to develop enhanced
usability features, even within version 9.1.
These are the enhancements to existing features of Time and Labor that we identified from the
various resources available on PeopleSoft HCM v9.2. In the next part of this series, we will
discuss some of the brand new features for Time and Labor in v9.2.

Time and Labor/Absence Management Integration Part I

This is the first part of a two part article dealing with the integration of PeopleSoft Time and
Labor and Absence Management as well as implementation considerations to reduce time
leakages between the two modules. This series is published by HRoi Consulting and sponsored
by Accu-Time Systems Cesium Solution. - Time clocks for PeopleSoft Time and Labor.
Prior to the introduction of Absence Management as a standalone module, customers who
wanted a complete Time and Attendance solution in PeopleSoft were limited by choice. Time
and Labor was of course designed to handle worked time, but did not have specialized

capabilities to handle absence management requirements. It lead to most implementations using

either the Monitor Absence module in Workforce Administration or Leave Plans in Benefits to
handle the absence management requirements. Needless to say, these were not optimum
solutions and often entailed heavy customization to make these modules work like a true absence
management module.
The Time and Attendance system design in PeopleSoft took a critical turn with the introduction
of Absence Management. Now, customers could use specialized modules for handling both
worked time as well as absences and it meant that sites could now implement a
comprehensive Time and Attendance solution using PeopleSoft Time and Labor and Absence
Management. It is noteworthy to mention here that the Time and Attendance solution got reinforced in version 9.1 with the out of the box integration to Oracle Workforce Scheduler
(OWS).
Overview of the integration
The integration between Absence Management and Time and Labor can be broadly classified to
fall under the following categories:
1. Integration of absence reporting and approval on Time and Labor timesheets.
2.

Integration of absence management and time and labor data in the various MSS
Schedule views.

3. Integration of absence event data in Time Administration processing.

4.

Integration of absence management and time and labor data for payroll processing.

The nature and extent of the integration is primarily dependent on the payroll system attached to
the employee in Workforce Administration. This integration is only supported if the payroll
system is either Payroll for North America or Global Payroll. This means that if the payroll
system is selected as Payroll Interface, you lose the ability to integrate these two modules in an
effective manner. This is indeed an important decision point in the design of the entire solution
for an implementation having a third party payroll vendor.
Let us examine the integration details with Payroll for North America and Global Payroll as the
pay systems.

1.
2.
3.
4.

Global Payroll:
With Global Payroll as the pay system, the following integration points are possible for Time and
Labor and Absence Management:
Report and Approve absence requests on Timesheet.
Absence Event data brought over to payable time by Time Administration process.
Absence Management and Time and Labor data available as an integrated view in the various
MSS scheduling pages like Manage Schedules, Monthly Calendar, Weekly Calendar etc.
Payable time data integrated back to Global Payroll as positive input for payroll processing.
The diagram below gives a high level overview of the various integration points between Time
and Labor and Absence Management using Global Payroll as the pay system.

Payroll for North America:

When using Payroll for North America as the

payroll system, the integration points between Time and Labor and Absence Management
remains almost same as that for Global Payroll but with the difference that absence management
data is brought over to Time and Labor for payment in Payroll for North America. In this case,

absence management related positive input that is generated in the GP_PI_GEN_DATA table is
sent over to Time and
Labor by the To Payroll for North America conversion process at Absence Management side.
The conversion process populates Payable Time table with data from Absence Management and
this is further sent to Payroll for North America when the Load Time and Labor data process is
run in the Payroll for North America module. The other integration points like absence event
entry in Timesheet, integration to the various scheduling views etc. remain the same as that for
Global Payroll. Thus, the various integration points between the two modules with Payroll for
North America as the pay system can be summarised below:
1. Report and Approve absence requests on Timesheet.
2.

Absence Event data brought over to payable time by Time Administration process.

3. Absence Management and Time and Labor data available as an integrated view in the
various MSS scheduling pages like Manage Schedules, Monthly Calendar, Weekly
Calendar etc.
4. Absence Management positive input paid through Payroll for North America after being
first brought over as payable time in Time and Labor.
Handling the integration with a third party payroll system
With payroll outsourcing gaining popularity, a common configuration is to have PeopleSoft Time
and Labor and Absence Management with a third party payroll system. As mentioned in the
article earlier, the integration between T&L and Absence Management is not well supported if
you select Payroll Interface as the pay system of the employee. In this case, what are the
options available for integration?
1. Consider if you can use Global Payroll as a dummy pays system. Even if you are not
actually using GP, you can select Global Payroll as the payroll system for an employee.
This decision gives you the added flexibility to turn on the Global Payroll related
integration points between these two modules. Note that this may not be possible if the
customer is using the Payroll Interface engine to generate files for third party payroll
systems.
2. The second option is to choose Payroll Interface as the payroll system and then customize
the system to make the delivered integration points work for Payroll Interface. A good
cost benefit analysis will have to be done to ascertain the exact benefits of this
customization before treading this path.
In this post, I have tried to give an introduction to the various integration points and possibilities
with Time and Labor and Absence Management. The next post will deal with unique challenges
in implementing an integrated Time and Labor and Absence Management system, especially
with regards to reduction of payroll leakage
How Absences are Processed in PeopleSoft Absence Management System

A Module like Absence Management isn't easy to get along with when you have just
started learning it through People Books without actually working on it. Well, not to
worry as I have an easier approach to tackle the challenge.
PeopleSoft HRMS Online Training
For now, forget about going through it's Set UP part and let's first get a hold on how
exactly the absence process works and explore on what are it's phases and what is the
life cycle of an absence request.
When we run the Calculate Absence and Payroll process with the options Identify
and Calculate selected the process:
1. Picks the Calender Group ID provided in the Run Control Page and checks what
are all the Calenders added into this group from the Calender Group setup page
(Root > Set UP HRMS > Product Related > Global Payroll and Absence Mgmt >
Framework > Calendars > Calendar Groups).
2. Once it has the Calendars, it gets the Pay Group, Pay Entity and Run Type from
the Calendar set up page (Root > Set UP HRMS > Product Related > Global
Payroll and Absence Mgmt > Framework > Calendars > Calendars).
3. Once the process has the Pay Group, it gets the Eligibility Group mapped with
this Pay Group from the Pay Group Set UP Page (Root > Set UP HRMS > Product
Related > Global Payroll and Absence Mgmt > Framework > Organizational > Pay
Groups).
4. Once the Eligibility Group is identified, system checks how many Element
Groups are added in this Eligibility Group form the Eligibility Group Setup page
(Root > Set UP HRMS > Product Related > Global Payroll and Absence Mgmt >
Framework > Organizational > Eligibility Group)
5. After the Element Group is identified, systems checks what are all the Absence
Elements (Absence Entitlements, Absence Takes) added in this Element Group
from the Element Group Setup page (Root > Set UP HRMS > Product Related >
Global Payroll and Absence Mgmt > Framework > Organizational > Element
Groups)
6. Once the Elements are identified, system concludes that these Element will be
resolved for all those Payees who are added to this Pay Group which was
identified in Step 2. Note that each payee has a Absence Pay Group assigned to
them in their Job Data page.
7. After system has all the details like what are all the Element to resolve for
which Payee, It hands over this information to the Calculation Process that has
been mapped with the Run Type (Root > Set UP HRMS > Product Related >

Global Payroll and Absence Mgmt > Framework > Processing > Run Type). Note
that Run Type was Identified from the Calendars set up page in Step 2.
8. Once the Calculation Process has all the details like what are all the elements
to be resolved for a particular payee, It processes those elements and then
calculate the Absence and then updates all the accumulators like Absence Take,
Absence Entitlement, Entitlement Balance Absence Adjustment etc...

PeopleSoft Absence Management

Oracle's PeopleSoft Enterprise Absence Management gives you control over your organization's
time-off processes in a single, powerful Web-deployed product. PeopleSoft Absence
Management enables you to automate leave planning and related compensation for your entire
workforce, even in a multinational operating environment.
PeopleSoft Absence Management is part of Oracle's PeopleSoft Enterprise Human Capital
Management family of applications.

BENEFITS

PeopleSoft Absence Management combines employee and manager self-service absence

management functionality in one highly configurable, flexible, and scalable Web-based product
to help you track and analyze consolidated absence and leave accrual information.

Submit absence requests for approval and view status.

View current and projected absence balances.

Configure request approval functionality, including multilevel approvals and

alternate approvers.

Configure absence accrual and consumption functionality, including a rules

engine to compute the most complex accrual and consumption logic.

Configure absence terminology.

Automate your leave donations administration programs.

Reduce the cost of administering extended leave and minimize the risk of
compliance related to legislated leave laws.

Improve workforce productivity with Absence Management integration to

Oracle Workforce Scheduling.

Export computed absence accruals and consumption (by employee and by

pay period) to Oracle's PeopleSoft Enterprise Time and Labor for payable time
generation and to both Payroll for North America and Payroll Interface for
payment.

Key Concepts in Absence Management

TriTriggers
You can create triggers in Absence Management to detect changes made to data in Human
Resources. This enables Absence Management to identify payees automatically who needs to
be recalculated during an absence run.

Iterative Trigger

An iterative trigger tells the system to process (or reprocess) a payee in the current open
calendar, possibly because payee data has changed or the payee was terminated or payee has
raised another absence request during the same calendar period.
PeopleSoft HRMS Online Training

Retro Trigger

A retroactive (or retro) trigger tells the system to reprocess previously calculated (closed)
calendars.

Example:

An employee has raised an absence request for the month of Oct which is a past dated
absence request. This absence request will be detected Retro Trigger and processed.

Segmentation Trigger

This trigger tells the system to process a payees absence when a data change occur in the
middle of the pay period, by dividing the pay period in two segments for the correct result.

Example:

A person gets promoted to a higher grade on 17th of the current month and now they are
eligible for more number of leaves hence, Segmentation trigger will detect this change and
two segments will be created for this pay period 1) 1st to 16th and another from 17th to 31st of
the month

Retro Processing Methods

Retro is a term used in Absence when the absence is recalculated for the already closed
calendars.

Corrective Retro Processing

This method recalculates all the past dated absences from the month in which the retro even
has occurred and update the accumulator for each month with re-calculated results.

Example:

This is the absence data for an employee as on Month of March which is current month.

Jan Entitlement = 1
Jan take = 0
Jan balance = 1
Feb Entitlement = 2
Feb take = 0
Feb balance = 2
March Entitlement = 3
Jan take = 1
March balance = 2

Now, the employee raises an absence request for the month of January so this is how the
absence data will look like when this request is processed through corrective method.

Jan Entitlement = 1
Jan take = 1 - recalculated
Jan balance = 0 recalculated

Feb Entitlement = 2
Feb take = 1 recalculated
Feb balance = 1 recalculated

March Entitlement = 3
Mar take = 1 recalculated
March balance = 2 recalculated

Forward Processing
How Absences are Processed in PeopleSoft Absence Management System
Visit this page to know more on this - How Absences are Processed in PeopleSoft Absence
Management System

Setting Up Absence Management

Here is what you all need to do in sequence to set up Absence Management
Security Setup
This is the first thing we do when we start the Global Payroll and Absence Management set
up. There are two types of security setup for Global Payroll and Absence Management
Element-level security (Set Up HRMS, Security, User Maintenance, Global Payroll User Profile,
User Rules Profile )

Restricts the elements that a user can view or update, based on the User Rules Profile
page and the Used By, Owner, and Override Levels fields on the Element Name page.

Payee-level security (Set Up HRMS, Product Related, Global Payroll & Absence Mgmt,
Elements - All Element Definition Components)

Restricts the payees that a user can view, based on the standard HR security in
PeopleSoft Enterprise Human Resources.

Setting Up Absences
There are broadly areas from where the setup is done:
1. System Setting
2. Elements

3. Framework
4. Schedules
5. Triggers

System Setting
This is where the setup begins. In this area some installation and schedule settings are done
along with countries setup like what will be the default retroactive method that should be
used in absence processing etc...
Elements
Primary Elements - Absence Take and Absence Entitlements
Supporting Elements - Accumulators, Formula, Variable, Bracket, Array etc...
below diagrams shows in what order the elements are created:

Navigation: Set Up HRMS Product Related Global Payroll & Absence Mgmt Elements

Generation Controls

If we want to have a control on the element that during absence processing, it should be
resolved only when it meets certain criteria then we use generation control elements.

Generation control works as a switch for another element to be resolved, if the switch is on
then the element will be resolved, if switch is off then it wont.

Scenarios where Generation Control element is used:

If an employee is on Leave of Absence (LOA) then the annual leave entitlement shouldnt be
given to them in which case we can create a Generation Control element which will find out
whether an employee is on LOA and based on that it can decide whether the Annual Leave
Entitlement element should be resolved or not.

Framework
Once the elements have been defined, the framework for processing various absences is
setup. Below snapshot is showing the order in which this setup has to be done:

Navigation: Set Up HRMS Product Related Global Payroll & Absence Mgmt Framework

Schedules

Schedules define workplace attendance expectations for groups of employees, and include
definition of

The workdays, scheduling units, and holidays. This information is important to the absence
process because it tells the system whether a reported absence occurred during a scheduled
work time. Absences during

Scheduled work periods may be paid if they meet your organization's absence rules.

Navigation: Set Up HRMS Product Related Global Payroll & Absence Mgmt Schedules

Triggers

We Setup various triggers to detect changes occurred in the absence/employees data so that
that they can be processed during Absence Run.

Navigation: Set Up HRMS Product Related Global Payroll & Absence Mgmt Triggers

Self Service Setups

We configure the absence take elements for Self-Self service users as to how the page will
look like, whether forecasting to be used, what will be the error message to be thrown when
employee is not eligible for leave, what are all the fields to display in absence request page
etc

Absence management:: Process flow for setting up absence management module

Absence management module I am told is the most complicated module to configure. And I did
find it a challenge with so many setup to configure. So to ensure I dont forget I have mapped out
all the different configuration items that are required to setup this module.
Below is process diagram on how to go about implementing the Absence Management in PS
v9.1. This should help you setup the the module easily.

Below is the way to setup processing calendars.

One thing missing in this is the Absence Pay Group Mapping. This is required to get the
calendars to process.