PeopleSoft HCM

What is ERP ?
• Enterprise resource planning software, or ERP. • It attempts to integrate all departments and functions across a company onto a single computer system that can serve all those different departments' particular needs. Why PeopleSoft ? • PeopleSoft is the second largest enterprise applications software company in the world owned by Oracle. • PeopleSoft is the undisputed leader in applications for Human Capital Management. • Also a leader in software for Manufacturing, Customer Relationship Management, Real Estate, Analytics, Financial Management, Supplier Relationship Management, Distribution, and Asset Management.

PeopleSoft explained
• Pillars
– – – – – HRMS (HCM) FSCM CRM Campus Solutions E- App (e-recruitment, e-pay, e-benefits etc)

• HRMS Modules
– – – – – – – HR Payroll Benefits Time and Labor Talent Acquisition Management Enterprise Learning Management Self Service (ESS & MSS)

Technical Vs Functional

Inside PeopleSoft
• • • • • • • • Homepage Navigation Personalization Installation Setup and configuration Security Peopletools Process scheduler

PeopleSoft Internet Architecture
PeopleSoft Internet Architecture is comprised of a variety of components ranging from the browser to the database server, including the following:

– – – – –

Web browser Web server Application server Batch server Database server

System Architecture (RDBMS)

Peopletools
• Proprietary software development environment created by PeopleSoft. • Consist of Application Designer, Application Engine, Data Mover, PeopleCode etc. • Classification
– – – – Development Tools Integration Tools Reporting tools Third party tools

Development Tools
• • • • • • Application Designer Application Engine PeopleCode Data Mover Change assistant Change Impact Analyzer

Integration Tools
• • • • • Component Interface Integration Broker File layout Web services Application Messaging

Reporting Tools
• • • • • • • SQR PSQUERY XML publisher Crystal Reports N Vision Cube manager Process Scheduler

Pages and components
• • • • • • Working with pages and components Using keys and search pages Effective Dating and Effective Sequence Correct history modes Prompt values Tabs

Configuration – Set Up HRMS is used to configure the application for Master Data. Mostly these sections are classified as follows: • Installation • Security • Foundation Tables – Used across the system(s) • Product Specific – Configuration specific to functions within HRMS like Workforce Administration, Benefits, Payroll for North America etc. • Common Definitions – Used across modules. Transactions – EE level Data Management Transactions performed by Administrators/specialists • Job Data Transactions happen with in “Workforce Administration” • Benefits Enrollment, Management etc happens with in “Benefits” • So on Self Service– EE having access to certain pages where he/she himself/herself can modify certain data (which may be routed through approval process) • eProfile (Personal Related Information) • eBenefits (Enrollment, management) • so on

Configuration

Configuration

Configuration

Configuration

Configuration

Transactions

Self Service

Transaction

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, ORG_INSTANCE_ERN Other: PER_ORG, POI_TYPE etc
Employee, Contigent Worker POI with job (Pension Payee, COBRA Payee etc) External Students and Instructors etc.

PER_POI_TYPE
Keys: EMPLID, POI_TYPE

PER_ORG_ASSGN
Keys: EMPLID, EMPL_RCD
Other: PER_ORG, POI_TYPE etc

Business Unit & SetID
• Business Unit
– Business Units are logical units created within your organization for reporting purposes and don't have any predetermined restrictions or requirements. – Define Business Units that reflect the specific functional needs of your internal human resources departments, or reflect the actual business structure of your enterprise. – Ex: companies, agencies, subsidiaries, divisions, departments, or branch offices within the organization

SetID
– TableSets, or groups of tables, for your system-wide control tables, so that you can share the same code values among multiple Business Units within your enterprise – You can use Business Units and TableSets to associate a Business Unit with employees in your enterprise and to specify how default values for currencies and country codes will behave throughout the HRMS system

Business Unit

SetID

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.

Questions/Discussions

Sign up to vote on this title
UsefulNot useful