Session 104620 COLLABORATE 13Sweta GanatraOracle Certified HCM SpecialistHCM Practice Lead

(925)285.8486. sganatra@beastute.com

HITCHHIKER'S GUIDE TO

PEOPLESOFTORGANIZATIONAL RELATIONSHIPS

Organizational Relationships – Overview• Key Person Model Terms and

Foundational Concepts

Person Model Delta Features• Key Changes• Core table Impacts• External Module Impacts

Challenges & Solutions• Impact Analysis

AGENDA

Overview

WHAT• Defined as links between organizations and people working for them

WHY• Report, track and retain persons and job movements• Determining factor in most search records, prompts, and selections

HOW• employees and contingent workers now reside in one common structure• combine or separate records for reporting• provides a framework to allow HRMS to move Dependents, Beneficiaries,

and Emergency Contacts into Person at some point

ORGANIZATIONAL RELATIONSHIPS

PRE 8.9 8.9 AND UP

• Couldn’t track a person unless they had a JOB record

• Couldn’t track students, interns, COBRA beneficiaries, external training administrators

• Didn’t allow the use of a single ID for a person across

• Repeated data entry of Personal Data when the person exists in multiple modules

• Can track a person with basic Personal Information

• Can track anyone with or without JOB record including Emergency Contacts

• Single unique tracking ID across multiple relationships to the organization

• Eliminates redundancy in tracking data

PRE 8.9 PERSON MODELOVERVIEW AND DRAWBACKS

PeopleSoft uses 3 main Organizational Relationships•Employee (EMP) - A direct employee of the company•Contingent Worker (CWR) - A non-employee worker (Contractor etc.)•Person of Interest (POI) - A non-worker (COBRA Beneficiary etc)

Separation of Person from Employment and Job• A Person’s basic data is saved, establishing Person ID• A Person’s organizational relationships are added as next step (e.g. Employee, Contingent Worker, Person of Interest)• Job Data is added where applicable

MUST have at least one of these.

CAN have more than one. CAN change over time

BASIC CONSTRUCTS

Each organizational assignment can be

associated to a unique benefit record number

Organizational Instance: An relationship instance

Organizational Assignment: An employment / job instance

Person Checklist: A checklist is a list of additional componentsthat need to be completed for a person

PERSON MODELUNDERSTANDING THE DESIGN

PE

RS

ON Organizational

Instance

OrganizationalInstance

OrganizationalAssignment

OrganizationalAssignment

AssignmentHistory

AssignmentHistory

EXAMPLE

• Person Record created• No Job Record created

• Existing Person Record updated• Job Record created• Can have multiple Job Rows to depict concurrent jobs

• Existing Person Record updated• Existing Job record updated

Drew Baker

Takes a Course(POI Instance)

Joins the Company(Employee Instance)

Returnsto Consult(Contingent

WorkerInstance)

Impact

PERSON MODELCORE PERSON TABLES DETAIL

Record Name Category DescriptionPERSON Core, Required Contains the ID and a person’s static data

(such as birthdate and birthplace

PERS_DATA_EFFDT Core, Required Contains a person’s core personal datathat can change over time

NAMES Core, Required Contains a person’s name data tracked across history and in multiple name types

Organization Relationship

PER_ORG_ASGN orPER_POI_TYPE

Core, Required

Each person must have at least one organizational relationship defined. These relationships aredefined in one of two tables, depending onwhether assignment data (JOB) is required

PERSON MODELFUNCTIONAL CHANGES

Creating a Person• Several HCM Portal Components• Searches already existing persons, first

EMPL_RCD #• Unique identifier within an EMPLID for separate assignments

Benefit Record #Multiple Instance – A concurrent assignment in addition to an existing assignment

PERSONAL_DATA is retained as a table with data from the Core andExtension tables

PERSON MODELFUNCTIONAL CHANGES

JOB key structure has remained the same

ESS

• Ability for all person types (EMP, CWR, POI) to securely access their data online just like employees and add or update information

Security

• A single person can have many different types of organizational relationships and security can be granted based on these relationships and their attributes

ABILITY TO CREATE EMPLIDWITHOUT JOB DATA

ORGANIZATIONAL RELATIONSHIPSUMMARY PAGE

RELATED MODULE IMPACTS

Workforce Development

Benefits Administration

Global Payroll and Absence Management

Talent Solutions

• Recruiting Solutions• ELM

Pension Administration

Stock Administration

Campus Solutions

PERSON MODELIMPACTS TO CUSTOM OBJECTS

PERSONAL_DATA Snapshot Reporting Table

EMPLOYMENT Table has been replaced by a real-time view

Reports

Interfaces

Batch Programs

Customizations / Enhancements

• Objects/programs retrieving employee and non-employee information

Action Plan: Thoroughly evaluate custom code for person modeltouch points and update accordingly

IMPROVED FUNCTIONALITY IN 9.2

Improved Talent Management

Template-based hire

New Profile Management

• Setup content catalogs for age related competencies, licenses & certifications, performance evaluations and tie in with Person profiles

Improved Benefits Functionality

Effective dating of dependent / beneficiary data

• Dependent/Beneficiary type, Relationship to Employee, Dependent’s Student, Smoker, Marital Status etc

IMPROVED FUNCTIONALITY IN 9.2

EMPL_STATUS is split in two categories: HR Status and PAYROLL Status

Configurable job actions and action reasons• Creation of business validation rules that depend on organizational

relationships and a person’s HR and Payroll Status

ADDITIONAL IMPLEMENTATION/UPGRADE CONSIDERATIONS

Data Cleanup issues when moving from an existing pre-8.9 database to 9.x• Same person may reside with multiple EMPLIDs

A Person cannot be created with a future date• A Person can still can be hired in the future – the first JOB can have a

future date

The Hire, Rehire, Termination, Last Date Worked fields have moved from EMPLOYMENT to the JOB level so they can be tracked historically

ADDITIONAL IMPLEMENTATION/UPGRADE CONSIDERATIONS

Detailed data mapping exercise to tie current workforce to EMP, CWR or POI relationships

• Map current non-employees to the new person model• More than one non-employee groups being mapped

as CWRs

How to Get There

AUTOMATE THROUGH CONFIGURATION

• Workflow, IB,　 Web Services

MORE CONFIG= Less

MAINTENANCE= Lower Cost= More Stability

Drive ROI through

Automation

• LDAP, OAM/SSO　 Integration

• BI Dashboards　 within PS

• Portals and Content

• Social Media　 Integration

CORPORATE OVERVIEW

• Oracle Partner – Focused on PeopleSoft,

　 Oracle EBS, OBIEE and Microsoft

• Clients and Operations in USA, Canada, 　 Middle East and India

• 150+ employees, Minority Certified,　 SB Certified

• Global Delivery Model

OVERVIEW – ABOUT ASTUTE

COMPETENCY OVERVIEW

• Lines of Business – IT Consulting, 　 Business Consulting, Temporary Staffing

• ERP – PeopleSoft, Oracle

• BI – Oracle, Microsoft, IBM

• Portals – SharePoint

• Process – HCM, Financials,　 Supply Chain and Risk

• Implementations and Global Rollouts – All PeopleSoft Apps• Upgrades – Fast Track Accelerated Upgrade for V9.1• Application Management Services – Lifecycle Management

• Project Management, Change Management• Fit-Gap Analysis, Business Requirements Gathering• Functional and Technical Design, Development• Testing, Training and Documentation (UPK)

• Fast Track Upgrade Impact Analyzer• Upgrade Test Scripts, Performance Tuning Scripts• Data SPII for Data Privacy Compliance

IMPLEMENT INTEGRATE MAINTAIN OPTIMIZE UPGRADE

OVERVIEW – PEOPLESOFT SERVICES

TurnkeySolutions

ConsultingServices

Tools &Accelerators

Recent Upgrades

• National Healthcare Organization – HCM 8.8 to 9.1

• Global Financial Services Firm – HCM 8.8 to 9.1

• International Consumer Electronics Firm – FSCM 8.0 to 9.0

• International Financial Services Firm – FIN 8.8 to 9.1

• More information online at http://www.beastute.com

Thank You

Questions? Comments?