We return to exploring PS HCM now, do excuse the break in blogging, was into the festive season here.
In today’s post we will look at PS HCM and how and where it fits into an organisation’s implementation and also explore the different modules of PS HCM that we will focus on in this blog.
When we look at the ERP implementation of a typical organisation, we are sure to find a HCM, a FSCM, a CRM and a ticketing system. And of course a mail exchange system will be in place and probably an AD (Active Directory) would be implemented and maybe a Single Sign On as well.
So a typical organisation may implement a few of the above tools , all of them or perhaps more, in many such implementations, a HCM may provide the User ID and Employee ID(we shall use EmplID in our posts) to be used across the ERP platforms, other software like ticketing systems , legacy applications if any, mail exchange tool , AD etc.
Thus in many implementation, a HCM like PS HCM would be the mother publishing system for employee identification, personal and basic employment data.
The figure next explains how EmplID and UserID(OPRID in PS HCM) are the key fields shared across an implementation with PS HCM being the mother publishing application also called as single source of truth.
Please note Exchange, AD etc systems subscribe to first name, last name, role etc data as well depending on your implementation, I have focused on the key fields in the diagram, and other ERP applications, legacy systems etc will subscribe to a whole lot of data from PS HCM depending on their own functionality and the overall system design.
And this User ID and Employee ID/Person ID data for every employee in your organisation is created and maintained as a result of the Administer Workforce business process.
Administer Workforce business process is a part of the core HCM functionality and starts with generating an Employee ID also referred to as a Person ID for every employee hired into the organisation. If your implementation includes Talent Acquisition Manager then the Person ID for the to be hired employee will flow in through internal IB , when it is in TAM the Person ID belongs to an applicant, now and here it represents an employee. An EmplID is used to refer to and access an employee’s personal, employment, compensation, benefits, training etc. data in PS HCM across all the modules.
Figure following represents the EmplID being used across all PS HCM modules,
Also please note the term EmplID is used in older versions of PS HCM, the term Person ID has replaced EmplID on all PS HCM pages ver 9.0 onwards, I am using EmplID to emphasise that it is used for an employee, we will look at the difference between Person ID for an employee and non-employee in later posts.
As is evident from the figure above, the Administer Workforce module generates EmplID and this EmplID along with employee personal and employment information (stored in tables PS_PERSONAL_DATA and PS_JOB) are shared with and used by all modules in PS HCM, most of these modules also share data back with the core HCM tables, especially PS_JOB and the tables underlying PS_EMPLOYMENT.
Depending on the module the data is either shared by underlying PeopleCode when the component loads or by internal IB.
Also please note that Core HCM is more a concept than a rigid set of modules , hence the modules I have indicated in the figure above are a fluid depiction of the components of a core HCM system, it could include more or less at any times.
That is all for today folks, we will return soon with focus on Administer Workforce.