What is Oracle PeopleSoft

Oracle’s People Soft Enterprise applications are designed to

address the most complex business requirements
They provide comprehensive business and industry solutions,
enabling organization to

Increase Productivity
Accelerate Business performance
Lower Cost of Ownership

Applications
Human Capital Campus Solutions Supplier Relationship
management Management

Financial management Enterprise Service Supply Chain Management

Automation
Customer Relationship Enterprise Portals PeopleSoft EnterpriseTools
Management andTechnology
Enterprise Performance Asset Life Cycle
management Management
Human Capital Management
Solution is:
# 1 in HRMS, Benefits, Employee and manager seif-service,
Talent management, Learning management and HR Business
Intelligence
Award winning for payroll services
Out perform industry Average in Best in Class KPI s
PeopleSoft Customers are 41% more likely to be satisfied with
their HCM system
Ranked leading Choice in HCM solutions

Product Line
Human Resources
Benefit Administration
Payroll Interface
Global payroll
Payroll for North America
Pension Administration
Stock administration
Country Extensions
Understanding HRMS

HCM Application-Business Process

The Human Resources application is composed of the following
business process categories
Business Processes Within HCM
Workforce Administration
 Global Assignment
 Labor Administration
 Absence and Vacation
 Flexible Service

Workforce Development
 Competency Management
 Performance Management
 Faculty Events
 Career planning

Organizational Development
 Succession Planning
 Position Management

Business Processes Within HCM -

Enterprise Learning
 Training Budget
 Student Enrollment
 Course Details

Workforce Monitoring
 Health and Safety
 Regulatory Requirements
 Professional Compliance
Self-service Applications

A
Component P P
R P
Component O L
System Catalog D I
tables Component U C
C A
People Tools T T
tables S I
Control Tables O
N
ApplicationTables TransactionTables
S
Working on

Implementation

Upgrade

Support

Implementation Life cycle

1.Identify the Module Requirements

2. Customize the module according to the Fit Gap Report

3. Set up the Security

4. Setup the Module

5.Data Migration

6. Run the Processes

7. Test run Reports

8. End User Training

Terminology
 Global
- Control Table
- Transaction table
- Table Sharing
- Data Sharing
- Business unit
- Set ID
- Record Group
- Table Set Control
- Table Sets
- Effective Date/ Eff Status/ Eff Sequence

Hcm Terminology
Company
Regulatory region
Location
Department
Establishment
Job code
Pay Group
Earning & Deduction Code
Control Table
Control tables (Masters) store information that is used to
process and validate the day-to-day business activities
(transactions) users perform with PeopleSoft HRMS
applications.

The information stored in control tables is generally static

and is updated only when fundamental changes occur to
business policies, organizational structures, or processing
rules.

Transaction tables
Transaction tables store information about the day-to-day
business activities (transactions) users perform with
PeopleSoft HRMS applications

The information stored in transaction tables often changes

and is updated more frequently than the information stored
in control tables
Table Sharing
This is common in all applications which will support multi
entities.

In PeopleSoft both control and transaction tables

support table sharing
-Control tables can maintain more than one set of data.
PeopleSoft is using SETID field to identify data in control
table as sets.
-Transaction tables can maintain more than one entity
data.Peoplesoft is using Bussiness Unit field to identify data
in Transaction tables.

Data Sharing
PeopleSoft supports Data sharing in Control Tables. Not in
Transaction tables.
It means Same Rules, regulations, policies and procedures
can be used by more than one Entity (Business Unit).
Advantages:
- minimize data redundancy
- maintain data consistency
- reduce system maintenance tasks.
Data sharing cont..

Business Unit
An identification code that represents a high-level
organization of business information. You can use a business
unit to define regional or departmental units within a larger
organization.
Business unit is an entity represents set of transaction data of
a legal entity
Determining Business Units
 Business units offer a flexible structuring device through which you
can implement PeopleSoft HRMS based on the way your business is
organized.

 You can decide how to implement business units for PeopleSoft

HRMS applications to reflect your own enterprise’s structure.

 Your entire organization may have only one business unit, if every
department uses the same processing rules. But multinational or
otherwise diversified companies, such as those that have multiple cost
centers, divisions, or subsidiaries, usually have multiple business
units.

Concept of Tablesets
 Set of rows on a control table, grouped by setID, that is available
to specific business units.

 TableSets enable you to share control table information and

processing options among business units. For example, with
TableSets, you can define a group of common job codes for several
business units. The goal is to minimize redundant data and system
maintenance tasks.

 SetIDs are the labels that are used to identify a TableSet. For
example, with a SetID you can define departments 1, 2, and 3 in the
Department Table and have another key that separates the data by
saying that this is a U.S. department 1 and a Canadian department.
This enables you to have different high-level keys.
Tablesets….

 ATableSet is a group of rows across

your control tables that are identified
by the same SetID.All rows of data in
your control tables that are keyed by
the same SetID compose a TableSet.
When you want to look up U.S.
information, enter the highest-level
key or SetID for the U.S. to retrieve all
the rows that are identified by that
SetID.

 For example, in the diagram, each

pattern represents a SetID, and all
rows with the same pattern represent
aTableSet. There are five TableSets in
this diagram:

Set ID
 Set ID is a Label of a field.
 Set ID field is use full to identify the rows in a control table as
Sets.
 Set id is a high level key for Control tables

 An identification code that represents a set of control table

information. SetIDs enable the sharing of a set of control table
information across two or more Business Units.
Record Group
Record group represents a group of Control Tables having
similar Fuctionality.
Record group can have one or more Control Tables.
Control table should have a Set id Key field to include into
the record group.

Table set Control

Set control value represents a set of control tables data across
database.
Effective date
Effective date Enable you to keep historical, current and future information
in tables.
There are three types of effective dates
Future Data rows that have effective dates that are after the
system date, which is usually today’s date

Current Data row with the most recent effective date that is closest
to today’s effective date, but not a future effective date.
Only one row is the Current row
History Data rows that have effective dates before the current date
row.

Effective date
Action Type View Change Insert New Rows

Update/ Display History, Current, Future only Effective Date

Future Greater
Than the Current
Row
Update/ DisplayAll History, Current, Future only Effective Date
Future Greater
Than the Current
Row

Correction History, Current, All Existing Rows Add New Rows with
Future No Effective Date
Restrictions
Eff status
In prompt tables, EFF_STATUS (Effective Date Status)
usually accompanies. EFFDT. When used with EFFDT, it’s
part of the mechanism that enables the system to select the
appropriate effective-dated rows.
You can also use EFF_STATUS by itself as a simple status
field.

Effective Sequence
If EFFSEQ is paired with EFFDT, it enables you to enter
more than one row with the same effective date. You assign a
unique sequence number to each row that has the same
effective date
The EFFSEQ (Effective Sequence) field serves different
purposes, depending on whether it’s paired with EFFDT. If
EFFSEQ isn’t paired with EFFDT,EFFSEQ has no special
function and can be used as a simple sequencing field
wherever you need one.
Hcm Terminology - Company
A business organization. Normally represents legal entity. For
Global payroll company is a pay entity

 For US companies using PeopleSoft Enterprise Payroll for

North America or PeopleSoft Enterprise Pension
Administration

Regulatory Region

A regulatory region can be any region where there are

specific laws and regulations that are addressed by
functionality in PeopleSoft Enterprise Human Resources.
Many country-specific transactions are driven by regulatory
requirements where Regulatory Region is used for
transaction processing.
Majority cases each country is a Regulatory region.
With in the Country Laws are extremly different between
states/ counties, there may be more regulatory regions with
in the country.
Establishment
It is required in countries USA and France
In PeopleSoft Human Resources, you define establishments
that are consistent with the regulatory requirements of your
business operations.
In PeopleSoft Human Resources, an establishment:
-Has an address.
-Is associated with a company.
-Is used for regulatory purposes

Establishment cont..
An establishment isn’t necessarily a single building or
location; it could be an entire industrial or office complex,
but it is usually a physical place for which information is
reported as a consolidated unit.
Two examples of how establishments are used:
- Occupational Illness and Injury Record keeping (OSHA
200) and Equal Employment Opportunity/ Affirmative
Action reporting in the United States.
- Social Security and business statistical reporting in France
Location
To establish physical locations in your organization, such as
corporate headquarters, branch offices, remote sales offices,
and so forth.

 For PeopleSoft Global Payroll, you may want to report certain information by
location.
 For Pension Administration, you can create one or more locations specifically for
pension payees
 applicants can specify work preference by location.
 In career planning, you can assign training courses to locations.
 Tying Salary administration Plan , regulatory region, Holiday Schedule,
Establishment.

Department
define business entities in your organization.
If you’re using PeopleSoft Payroll for North America or
PeopleSoft Global Payroll, you must set up department codes
according to your cost centers where you charge wages.
If you use PeopleSoft Pension Administration, you need
departments to house your pension payees.
Otherwise, you can set up departments using any groupings
you like.
Using Departments for Data Permission Security
(Row Level security by using Department security trees)
Positions
 You can structure your human resources system by position instead of by job.
 Use positions to track details on a particularjob in a particular department or
location that usually have a one-to-one relationship with employees.
 When you structure your system by position, you attach data to the positions
and move employees in and out of those positions
 When deciding when to use the Manage Positions business process, consider the
following
- If your organization is fluid.
- If your organization is fairly static
Government agencies and hospitals, which plan positions based on
budgets, find this method useful
- If both methods serve you well in different areas of your organization.
(partial position management)

Position cont..
Pay group
 A pay group is a logical grouping of qualifying individuals for payment
and contains payees who share pay characteristics.

 All payees in a pay group must have the same pay frequency (begin, end,
and payment dates) and payroll calculation process and belong to the
same pay entity.

 while creating pay groups consider the following:

- pay frequency
- Country
- Currency ?
- Regulatory Region

Job code
The Hrms is Designed with job code and position Centric.
Positions are optional.
maintain information about jobs independent of the person
or group .
Job codes have a one-to-many relationship with workers.
in the Absence of positions , lot of importence is there for
jobcodes. If you are not design and define job codes
properly, the implementation of majority products in hrms
will be unsuccessful.
Job code Cont..

Determining System Default Values

On the Component How the System Determines Defaults

Select a business unit. The system enters the default values from the
Business Unit Default Options component.
Select an EmplID value, but no business unit The system determines the person’s business unit
value. by checking the person's JOB record for that
EmplID/ ERN combination and then enters the
default values from the Business Unit Default
Options component.
component does not have either the Business Unit The system enters the default values from the Org
or EmplID fields. Defaults by Permission List component.
The component uses a setID without an associated The system enters the default values from the Org
business unit or EmplID value Defaults by Permission List component.