PeopleSoft
HRMS vs HCM
Introduction to the
Enterprise HCM
Person Model
in
Release 8.9
HCM – Person Model
WHAT IS THE PERSON MODEL?
The Person Model is a term used to describe the information
captured about a person and how the person is related to the
organization. This model includes the core tables that are used by
all products that are directly related to a person and their
organizational relationships in the Enterprise HCM system.
HCM – Person Model –Terminology
Person
Field: PERSON.EMPLID
– Any human being with a relationship to the
organization that you wish to track in your system.
HCM – Person Model –Terminology
Organizational Relationship
Field: PER_ORG_INST.PER_ORG
– How a person is related to the organization as
represented in the database. There are three major
categories of people that HCM tracks information on:
• Employee
• Contingent Worker
• Person of Interest
– A person can have one or more of these relationships
at any one time, including multiple occurrences of the
same relationship.
– Each distinct relationship that includes a Job Data
record is uniquely identified by an EMPL_RCD.
– Note. The relationships of people of interest do not
always include a Job Data record.
HCM – Person Model –Terminology
Employee (EMP)
Field: PER_ORG_ASGN.PER_ORG
– (Plural: Employees / Employed Workforce)
– The relationship of a person who is hired to provide services to a
company on a regular basis in exchange for compensation and who
does not provide these services as part of an independent business.
– An employee can work under a contract.
– The exact definition of what defines an employee is left to the
customer since each country has different rules. You will want to
make the determination based on your regulatory requirements.
– Each employee relationship must have a distinct EMPL_RCD.
HCM – Person Model –Terminology
Contingent Worker (CWR)
Field: PER_ORG_ASGN.PER_ORG
– (Plural: Contingent Workers / Contingent Workforce)
– The relationship of a person who provides services to another
entity under terms specified in a contract on a non-permanent
basis. Contingent workers include independent contractors,
temporary workers, and leased workers.
– The exact definition of what defines a contingent worker is left to
the customer since each country has different rules. You will want
to make the determination based on your regulatory requirements.
– Each Contingent Worker’s relationship must have a distinct
EMPL_RCD.
HCM – Person Model –Terminology
Person of Interest (POI)
Field: PER_POI_TYPE.PER_ORG
– A person who does not have aan employment or a
contingent worker relationship but who is still of interest
to the organization. HRMS has the need to track
information on non-workforce people in many areas
such as Cobra Participants, Pension Payees, GP
Dependents, External Students and Instructors, and so
on. Some POI relationships have job data records that
are identified with a distinct EMPL_RCD. Others (the
ones that do not need JOB information) are identified by
the POI_TYPE.
Navaigation to Define POI Type:
Set Up HRMS -> Foundation Tables -> Organization ->
Person of Interest Types -> Person of Interest Type
Tbl
HCM – Person Model –Terminology
Person of Interest Type
Field: PER_POI_TYPE.POI_TYPE
– This field identifies the different types of Persons of Interest that
you need to track. PeopleSoft supplies many defined POI types to
which you can add others.
– Some POI Types will require JOB information and others will not.
This is defined as an attribute of the POI_TYPE.
Workforce
Field: PER_ORG_ASGN.PER_ORG (values EMP, CWR)
– The combination of your employees and contingent workers is
collectively called your workforce (singularly, they are known as
workers).
HCM – Person Model –Terminology
Organizational Instance
Also known as Controlling Instance
Field: PER_ORG_INST.ORG_INSTANCE_ERN
– An occurrence of an organizational relationship.
– Also referred to as an Employment Instance, a Contingent
Workforce Instance, or a POI Instance.
– Organizational instances can be limited to one assignment
(EMPL_RCD) or include multiple assignments, depending on your
needs.
– When an organizational instance includes more than one assignment,
one of those assignments is identified as the controlling instance.
This EMPLID/EMPL_RCD combination stores the HIRE_DT,
general SERVICE_DT, and the TERMINATION_DT.
– For example, a person can have a single Employment Instance with
a company, but as part of that employment instance, they have three
separate assignments, each identified by different EMPL_RCD
numbers. One of these EMPL_RCDs is identified as the controlling
instance containing the overall dates. The others refer only to the
particular assignment.
HCM – Person Model –Terminology
Assignment
Field: PER_ORG_ASGN.EMPL_RCD
– A unique numeric identifier for each relationship that a
person has that requires JOB information. The value of
the EMPL_RCD is not used for anything other than to
identify a separate relationship; it does not rank or
otherwise give precedence to one assignment over
another
HCM – Person Model –Terminology
Additional Assignment
Identified by the EMPL_RCD and the ORG_INSTANCE_ERN
combination.
– An concurrent assignment in addition to, and under an existing
assignment
– Also referred to as Multiple Assignments.
– Some organizations allow their workforce to have multiple,
concurrent assignments. Each of these assignments needs to be
tracked under a distinct EMPL_RCD. In cases where the
customer does not want to treat these additional assignments
as a new employment relationship (with a Hire action), they
can be tied to a controlling instance, the first assignment the
person had (containing the Hire Date). Additional assignments
are treated specially in certain situations.
HCM – Person Model –Terminology
Multiple Instances
EMPL_RCD will always equal the
ORG_INSTANCE_ERN.
– An concurrent assignment in addition to an existing
assignment Some organizations allow their workforce
to have multiple, concurrent assignments and do wish
to track each as a separate assignment with an action
of hire. In this case, create each assignment as a
separate instance (either of Employment or Contingent
Workforce). The multiple instances are not related in
any way to the others instances this person has.
HCM – Personal Model – at a glance
PERSON
Key: EMPLID
Other: BIRTHDATE etc
With Assignments With out Assignments
PER_ORG_INST
Keys: EMPLID, PER_POI_TYPE
ORG_INSTANCE_ERN Keys: EMPLID, POI_TYPE
Other: PER_ORG, POI_TYPE etc
Employee, External Students and Instructors etc.
Contigent Worker
POI with job (Pension Payee, COBRA Payee
etc)
PER_ORG_ASSGN
Keys: EMPLID, EMPL_RCD
Other: PER_ORG, POI_TYPE etc
Setup HRMS
Set Up HRMS -> Install -> Installation
Table -> HRMS ->Options
Specify how to drive your system:
by person,
By position, or both.
Enter the PeopleSoft HRMS
defaults that are related to
your organizational policies.
Setup HRMS
PeopleSoft HRMS
•About HRMS
•Designing Organization structure
•Working with various HR Pages like SetID, BU,
Company, Dept, Location, Job codes ect
HRMS Table Types:
Control Tables:
SetID, Business Unit,
Transaction Tables:
Job, Personal_Data, Employement
Reporting Tables
Employees
Prompt Tables
Views
HR SETUP
SetID
PeopleTools -> Utilities -> Use ->
TableSetID (8.3)
PeopleTools ->Utilities ->Administration -
> TableSet IDs (8.9)
Business Unit
Business units are logical units that you create to
track and report specific business information.
Business units have no predetermined restrictions
or requirements
Navigation:
Business Unit
Define Business Rules-> Manage Human
Resources -> Setup -> Business Unit (8.x)
Set Up HRMS -> Foundation Tables ->
Organization ->Business Unit (8.9)
Business Unit HR Defaults
Define Business Rules ->Define
General Options ->Setup ->Business
Unit HR Default (8.x)
Set Up HRMS -> Foundation Tables
-> Organization->Business Unit
Options Defaults
Table Sets
A table set is a group of rows (set of data)
in a control table that is identified by the
same high-level key.
Record Group sharing
Data residing in the control tables can be shared
among the BU using record group sharing.
HR SETUP
Operator Preference Defaults
Define Business Rules -> Define General
Options -> Setup-> Operator
Preferences(8.3)
PeopleSoft Menus
Foundation Tables(Define Business Rules)
Set Up HRMS (Define General Options)
Installation Table
Country Table
State & Province Table
Set Up HRMS (Manage Human Resources)
Company Table
Department Table
Job Code Table
Location Table
Work Force Administration
(Administer workforce)
Action Reason
Bank Table
Salaray Grade Table
Salary Plan Table
Rating Scale Table
Rating Model Table
Company Property ect….
PS HRMS System
Effective Dated
Effective Date, Effective Sequence,
Empl_Rcd#
Position vs Person
Regulatory Regions
Set Up HRMS -> Install ->Regulatory
Region ->Regulatory Region
Defining Regulatory Regions
Regulatory Transaction Types
Regulatory Regions to a Transaction
PeopleSoft Menus
Define Business Rules – Contd…
Define Base Benefits
Benefit Plan Table
Benefit/Deduction Program Table
Define Payroll Taxes
Company State Tax Table
Company Local Tax Table
Federal/State Tax Table
Local Tax Table
PeopleSoft Menus
Define Business Rules – Contd…
Define Payroll Process
Account Code Table
Bank Table
Earnings, Earnings Program Table
Deduction Table
Pay Calendar Table*
Pay Group Table*
Pay Run Table*
Tax Location Table
*Will be discussed in detail as part of payroll
PeopleSoft Menus
Develop Workforce
Recruit Workforce
Applicant Personal Data
Applicant Checklist
Checklist Setup
Manage Positions (if applicable)
Create/Update Positions
PeopleSoft Menus
Administer Workforce
Administer Workforce
All EDM transactions (Hire/Rehire/Terminate etc)*
Capture Time and Labor
Employee Time Entry*
*Will be discussed in detail as part of payroll
PeopleSoft Menus
Compensate Employees
Administer Base Benefits
Benefit Program Participation
Maintain Payroll Process
Absence Input
Additional Pay
Direct Deposit
Employee Tax Data (Federal & State)
General Deduction Data
Garnishment Spec. Data
Inquire>Pay Check Data
PeopleSoft Menus
Compensate Employees – Contd…
Manage Payroll Process*
Pay Sheet
Pay line
Pay Sheet Creation process
Pay Calculation Process
Pay Confirmation Process
Pay Check Reprint process
Pay Check Reversal/Adjustment process
Pay UnConfirm process
Pay Unsheet process
Inquire>Pay Check data
*Will be discussed in detail as part of payroll
Questions / Suggestions
Person Vs Position Management.
PeopleSoft HRMS enables you to structure or
drive your PeopleSoft Enterprise Human
Resources system by person or by position.
Position Management System
When system is derived by position it define specific
attributes of various positions and then move
workers in and out of those positions.
