Converting Job data from legacy system into peoplesoft HR is one of the most common and the most important steps for any HR implementation.
The delivered Excel-to-CI template has a known issue when used with JOB_DATA component interface.
E.g For an employee, you may have 2 rows with 12/25/08 and 12/31/08 effective dates.
When you are loading a row with effective date 12/27/08 for the same person, excel-to-CI behaves incorrectly. It is supposed to insert a row on 12/25/08 row and change the date to 12/27/08; but it copies the future dated row 12/31/08 and changes the date to 12/27/08, which is incorrect.
So beware!!! When you are using excel-to-CI for higher peopletools versions you would need to verify every single field value in the component buffer once the data upload is over.
We had this issue on HCM 9.0 with 8.49.10 peopletools on sql server 2005.
My personal repository of PeopleSoft related findings. They cover various modules in CRM/HR/PeopleTools and whatever reusable useful information I can find to make my job easy.
Showing posts with label HCM / HRMS. Show all posts
Showing posts with label HCM / HRMS. Show all posts
Tables Accessed and Updated in HCM
HCM 8.8 / 8.9 / 9.0 / 9.1
Wondering how to find out all the tables incluing peopletools tables that are accessed in a COBOL or app engine in PS HCM application?
This is PS delivered SQR report to find out the tables accessed by any process in peoplesoft HR application, e.g. Application engine programs, COBOLs
Set Up HRMS > System Administration > Utilities > Tables Accessed and Updated
The pdf output generated is very descriptive and it categorizes the tables in different sections with 'select', 'update', 'insert', 'delete' operations on the tables.
SQR Report name is TBLUSAGE.
Wondering how to find out all the tables incluing peopletools tables that are accessed in a COBOL or app engine in PS HCM application?
This is PS delivered SQR report to find out the tables accessed by any process in peoplesoft HR application, e.g. Application engine programs, COBOLs
Set Up HRMS > System Administration > Utilities > Tables Accessed and Updated
The pdf output generated is very descriptive and it categorizes the tables in different sections with 'select', 'update', 'insert', 'delete' operations on the tables.
SQR Report name is TBLUSAGE.
Personal data integration between HR 9.0 and CRM 9.0
Scenario 1
Add a new employee with eff dt (sysdate-3) – back dated row
Result 1
One row each in
BO_CM – start date as (sysdate-3) and end date 12/31/2999
BO_CM_USE - start date as (sysdate-3) and end date 12/31/2999 and for role 4 and primary as ‘Y’
CM
BO_NAME
Two rows in BO_ROLE - Role 1 and 4
Scenario 2
Add a new row with eff dt (sysdate) for name change – today’s date
Result 2
BO_NAME has two rows with sysdate as seq nbr 2 and primary as ‘Y’
Scenario 3
Add a new row with eff dt (sysdate+3) for name change
Result 3
BO_NAME has two rows with 04/23 as seq nbr 3 and primary as ‘N’
Scenario 4
Add a row for phone number – Type Main – Preferred check box ‘Y’
Result 4
It creates one row each in: (There is no Effdt for phone grid, by default it takes system date)
BO_CM – start date as (sysdate) and end date 12/31/2999
BO_CM_USE - start date as (sysdate) and end date 12/31/2999 and for role 4 and primary as ‘Y’
CM
Scenario 5
Add a row for phone number – Type Work- Preferred check box ‘N’
Result 5
It creates one row each in: (There is no Effdt for phone grid, by default it takes system date)BO_CM – start date as (sysdate) and end date 12/31/2999
BO_CM_USE - start date as (sysdate) and end date 12/31/2999 and for role 4 and primary as ‘N’
CM
Scenario 6
Change the row for phone number – Type Work- Preferred check box ‘Y’
Result 6
Updated successfully in CRM
Scenario 7
Add one more effective dated row (sysdate-1) under Home Address type
Result 7
One row is inserted in BO_CM without changing the end date of the previous effective row (!)
In BO_CM_USE the end date of the previous effective row is changed to system date
Also new PROFILE_CM_SEQ is also created
Scenario 8
In Correct History Mode change effective dated row (sysdate-3) under Home Address type – make status as ‘I’
Result 8
In BO_CM the end date of the row is changed to system date
In BO_CM_USE the end date of the row is changed to system date
Scenario 9
In Correct History Mode change effective dated row (sysdate-2) under Home Address type
Result 9
In BO_CM the end date of the row is NOT changed to the new date but is row is updated with the latest timestamp
In BO_CM_USE the end date of the row is changed to the changed date and one more row is inserted for the same profile cm seq number with end date as 12/31/2999
Notes:
When just a person is created BO_CM_USE has Role 1
When a person is created with job data BO_CM_USE has Role 4 only and no role 1
Add a new employee with eff dt (sysdate-3) – back dated row
Result 1
One row each in
BO_CM – start date as (sysdate-3) and end date 12/31/2999
BO_CM_USE - start date as (sysdate-3) and end date 12/31/2999 and for role 4 and primary as ‘Y’
CM
BO_NAME
Two rows in BO_ROLE - Role 1 and 4
Scenario 2
Add a new row with eff dt (sysdate) for name change – today’s date
Result 2
BO_NAME has two rows with sysdate as seq nbr 2 and primary as ‘Y’
Scenario 3
Add a new row with eff dt (sysdate+3) for name change
Result 3
BO_NAME has two rows with 04/23 as seq nbr 3 and primary as ‘N’
Scenario 4
Add a row for phone number – Type Main – Preferred check box ‘Y’
Result 4
It creates one row each in: (There is no Effdt for phone grid, by default it takes system date)
BO_CM – start date as (sysdate) and end date 12/31/2999
BO_CM_USE - start date as (sysdate) and end date 12/31/2999 and for role 4 and primary as ‘Y’
CM
Scenario 5
Add a row for phone number – Type Work- Preferred check box ‘N’
Result 5
It creates one row each in: (There is no Effdt for phone grid, by default it takes system date)BO_CM – start date as (sysdate) and end date 12/31/2999
BO_CM_USE - start date as (sysdate) and end date 12/31/2999 and for role 4 and primary as ‘N’
CM
Scenario 6
Change the row for phone number – Type Work- Preferred check box ‘Y’
Result 6
Updated successfully in CRM
Scenario 7
Add one more effective dated row (sysdate-1) under Home Address type
Result 7
One row is inserted in BO_CM without changing the end date of the previous effective row (!)
In BO_CM_USE the end date of the previous effective row is changed to system date
Also new PROFILE_CM_SEQ is also created
Scenario 8
In Correct History Mode change effective dated row (sysdate-3) under Home Address type – make status as ‘I’
Result 8
In BO_CM the end date of the row is changed to system date
In BO_CM_USE the end date of the row is changed to system date
Scenario 9
In Correct History Mode change effective dated row (sysdate-2) under Home Address type
Result 9
In BO_CM the end date of the row is NOT changed to the new date but is row is updated with the latest timestamp
In BO_CM_USE the end date of the row is changed to the changed date and one more row is inserted for the same profile cm seq number with end date as 12/31/2999
Notes:
When just a person is created BO_CM_USE has Role 1
When a person is created with job data BO_CM_USE has Role 4 only and no role 1
Department Security Tree
HCM 8.9 / 9.0
A word of caution: Always create a department security tree with the name "DEPT_SECURITY" as it is hardcoded in various views and very important in implementing Row level security. If this naming is not followed then departments under newly created tree will not be available while setting up the security on "Security by Dept Tree" page.
A word of caution: Always create a department security tree with the name "DEPT_SECURITY" as it is hardcoded in various views and very important in implementing Row level security. If this naming is not followed then departments under newly created tree will not be available while setting up the security on "Security by Dept Tree" page.
Add a person in HR 8.9 or 9.0
If you get the below warning while saving the Person Data :
Warning -- No Relationship was created. An Unknown Person of Interest Type will be created (1000,1178)
If the Save is continued, then a Person of Interest Type of Unknown will be created for this person.
-------------------------------------------------------------------------------
Check here to see what is the Person's Organizational Relationship..
Main Menu > Workforce Administration >Personal Information > Person Organizational Summary
if no rows are visible then..you did not add him in Job Data.
In order to add this unknown POI as Employee, go to
Main Menu > Workforce Administration >Organizational Relationships> New Employment Instance
or
Main Menu > Workforce Administration > Job Information > Add Employment Instance
make sure that the Empl Rcd is 0 and then enter all Job Data details.
If you have done with job data while hiring, then you might have picked a department for which you do NOT have security.
Verify PS_JOB in SQL tool (not PSQUERY tool) to see if the person data exist. if yes, then you need to run all SJT security process. Make sure that your Department is in the Security Department Tree Setup.
Warning -- No Relationship was created. An Unknown Person of Interest Type will be created (1000,1178)
If the Save is continued, then a Person of Interest Type of Unknown will be created for this person.
-------------------------------------------------------------------------------
Check here to see what is the Person's Organizational Relationship..
Main Menu > Workforce Administration >Personal Information > Person Organizational Summary
if no rows are visible then..you did not add him in Job Data.
In order to add this unknown POI as Employee, go to
Main Menu > Workforce Administration >Organizational Relationships> New Employment Instance
or
Main Menu > Workforce Administration > Job Information > Add Employment Instance
make sure that the Empl Rcd is 0 and then enter all Job Data details.
If you have done with job data while hiring, then you might have picked a department for which you do NOT have security.
Verify PS_JOB in SQL tool (not PSQUERY tool) to see if the person data exist. if yes, then you need to run all SJT security process. Make sure that your Department is in the Security Department Tree Setup.
EMPLOYEES table and PERSONAL_DATA table
/*JOB and Person data snapshot reporting tables*/
PS_EMPLOYEES (HCM 8.8 / 9.1)
It stores all the current active jobs for all the employees.
Keys:
EMPLID
EMPL_RCD
This table is populated using an application engine process PER099.
Very useful table to avoid self-joining the JOB table to find out most effective dated/seq JOB record for employees.
Navigation in 9.1:
Set Up HRMS > System Administration > Database Processes > Refresh Employees Table
PERSONAL_DATA (HCM 9.1)
It stores all the current personal data information for all the employees.
Keys:
EMPLID
This table is populated using an application engine process PERS_REFRESH.
Navigation in 9.1:
Set Up HRMS > System Administration > Database Processes > Refresh Personal Data
This app engine in turn uses the following setup to refresh only the selective data based on
user inputs:
Set Up HRMS > System Administration > Database Processes > PERSONAL_DATA settings
PS_EMPLOYEES (HCM 8.8 / 9.1)
It stores all the current active jobs for all the employees.
Keys:
EMPLID
EMPL_RCD
This table is populated using an application engine process PER099.
Very useful table to avoid self-joining the JOB table to find out most effective dated/seq JOB record for employees.
Navigation in 9.1:
Set Up HRMS > System Administration > Database Processes > Refresh Employees Table
PERSONAL_DATA (HCM 9.1)
It stores all the current personal data information for all the employees.
Keys:
EMPLID
This table is populated using an application engine process PERS_REFRESH.
Navigation in 9.1:
Set Up HRMS > System Administration > Database Processes > Refresh Personal Data
This app engine in turn uses the following setup to refresh only the selective data based on
user inputs:
Set Up HRMS > System Administration > Database Processes > PERSONAL_DATA settings
NA Payroll Guide
Screenshots are from HCM 8.8
This is a nice presentation for understanding the NA payroll setup.
View the steps here:
NA Payroll setup
This is a nice presentation for understanding the NA payroll setup.
View the steps here:
NA Payroll setup
Person Model in HRMS 8.9 / 9.0
There is a nice red paper available on Oracle-peoplesoft site on Person Model in HR8.9 onwards.
This model is an enhancement over the earlier HR releases in the sense that, a person in HR can exist without having a JOB record in new Person Model.
The red paper details on those different terms like Person of interest, Contingent workers, employees, significance of EMPL_RCD field, global assignments.
Person Model in HR 8.9 / 9.0
Red Paper - Person Model in HR 8.9
This model is an enhancement over the earlier HR releases in the sense that, a person in HR can exist without having a JOB record in new Person Model.
The red paper details on those different terms like Person of interest, Contingent workers, employees, significance of EMPL_RCD field, global assignments.
Person Model in HR 8.9 / 9.0
Red Paper - Person Model in HR 8.9
Subscribe to:
Posts (Atom)