PeopleSoft HCM — Basic Concepts III

Some more important basics of PS HCM before we move onto the functional topics

basics3

we begin with Company

A Company is used to represent a legal entity in PS HCM, depending on the size of your organisation in terms of employee head count and geographical distribution and also the way your organisation functions, you can go in for a single or multi company organisation. Business Units and Departments are organised under the Company.If you are a multi Company organisation, all Companies are at the same level and there is no hierarchy possible.
Default values for the Payroll system(if your organisation is implementing it) can be associated with a Company definition along with defaults for Currency Code, Regulatory Region etc

A Regulatory Region in PS HCM drives functionality and hence determines what data the power user sees for certain fields. it is used to represent a geographical region having a bunch of laws and regulations that influence the functionality (through configuration and PeopleCode)in PS HCM. Health benefits, ethnicity driven functionality etc are part of the regulatory region driven features.

Departments are used to group employees together and also allocate or deny access to power users based on it. So when you think Department in PS HCM think access. A power user will thus have access to a particular employee’s data using the PS HCM portal only if the power user has been allocated access to the department to which the employee belongs. Departments are organised in the form of a security tree to establish and maintain a hierarchical relation between the departments.
So it means that if a power user has access to a department A with departments A1, A2, A3 under it then the user will have access to A1, A2 and A3 as well.

Let us delve deeper into the topic of user access in PS HCM.

When an user is allocated access in PS HCM, it has two aspects, for the pages which he requires access to perform his/her tasks and to the data which he/she should be allowed to access. Access to the pages is allocated using Roles which are made up of permission lists and access to data is granted using row level data permissions which typically begin with HCDP, so a user with HCDPALL will have access to data of all departments in the im plementation and a user with HCDPIND will have access to all those departments which are mapped to the permission list HCDPIND.

Reverting to Roles that govern the Menus and hence Components pages to which an user has access, a Role is a set of permission lists or even a single permission list, a permission list in PS HCM determines the pages to which the user will have access, while creating a permission list, first the Menu and then Component within the Menu containing the particular page has to be selected, the permission list also has options to specify if the access to the user in question will be Read Only or Read/Write and also the actions that the user can perform on this page i.e. Add, Update/Display All, Update /Display or Correction(Correct historical records).

So as we can see, an user should be assigned Roles and a row level data permission to enable him/her to use PS HCM, three other permissions which we will discuss next make up the user access. And please note that the Roles and the 4 types of permission lists will be assigned to the user’s User ID which is different from Person ID. The user will used this User ID to logon to and access the PS HCM application.

The other 3 permission lists are as follows,
Navigator Home Page
Used by PS Workflow and determnes how the Workflow homepage looks lke for the user. ths can also be left blank without any impact
Process Profile Permissions
Determines if the user has permissions to run reports and programs using the Process Scheduler and also the levels of these permissions like permission to download to excel, access to create new queries or restricting Run access to particular Process Groups only. Also Process Groups can be created from here.(Process tab in the Page)
Primary Permissions,
Determines the default values for certain fields like Country, Company, Business Unit, Regulatory Region, Set ID etc that will be populated by the system for the user on certain components and also the system settings for the user and starts with HCPP

Phew , that is quite a lot for this post, next post we will focus on a case study to create a Company in
PS HCM along with the bells and whistles that go with it.

PeopleSoft HCM — Basic Concepts II

Diving straight into the topic,

basics2

An Effective Date is the date from which the row of data associated with the date becomes valid for use and or becomes effective.Before the corresponding effective date occurs any data if present in the application will not be picked up by the system for any processing.
for example, if your PS_LOCATION_TBL has rows with an effective date of 01.01.2016 then till end of 31st Dec 2015 these rows will not show up in any of the pages where the PS_LOCATION_TBL is used.
Another example, if an employee has a row in the PS_JOB table with an effective data of 01.01.2016 with an action “Transfer to Afflilate”, the employee shows up on the rolls of the parent company till end of day 31st Dec 2015 and reflects on the rolls of the affilate company from 01.01.2016.

Care has to be taken while choosing effective dates for control tables especially, because in many cases inbuilt peoplecode compares effective dates of control data and may ignore any data which is greater than a particular effective date. Hence for particular control tables care should be taken to chose the earliest possible effective date.01.01.1900 is a safe bet which many implementations follow.

Effective Status is a value associated with an effective dated row, the possible values are “Active” and “Inactive”. The default value is “Active”, you can mark a row as “Inactive” when is does not hold any value for your implementation.
for e.g. if you organisation revises the list of designations and decides to stop using a set of 50 designations, then the effective status of these 50 designations can be set to “Inactive”, by doing so the 50 designations aka Jobcodes will not show up in the Jobcode prompts on the relevant pages.

When you go through planning your implementation of PS HCM, it is important to conceptualise the way in which your organisation’s data will be represented in HCM, if your organisation is spread across various countries or if your organisation has various business areas like manufacturing,logistics, pharmaceuticals etc you may opt for a multi company representation at the highest level.
Once this is out of the way next you may want to look at then grouping data with some similarities in business rules, payroll processing etc together , these logical groups are what are referred to as Business Unit. so you may group all KPO under one business unit for example, you may group Sales into another and all corporate functions into another, Business units are thus flexible structures that enable you to put together data which can be handled uniformly together. As another example if you are an IT organisation, you may want to group each of your verticals as BUs or another approach would be to organise each of your client accounts as a BU or even each geographical location of your organisation can be a BU. There is thus this flexibilty but do remember that a BU always ties to an employee’s job data and an user will be able to see other control data like Jobcodes, Salary plans etc for an employee based on the employee’s BU so take cognizance of this fact while planning the data setup. And do remember your PS HCM implementation requires atleast one BU to be created.

Set IDs & Table Sets

A set ID is a primary key present in all the control tables and a set ID lets you to control which set of rows in a control table can be shared across BUs.

The set of all the rows in a control table having the same set id is a Table Set.

And sharing table sets across various BUs is table set sharing.