Administering PeopleSoft Human Resources Integration with Clairvia
PeopleSoft Human Resources publishes an employee's personal, job, and person profile information to Clairvia. The system uses application messaging to publish the information to Clairvia via PeopleSoft Integration Broker messaging.
When you establish the integration between your PeopleSoft system and Clairvia, Oracle recommends that you perform the following steps:
Run the Full Data Publish process for the following messages:
DEPT_FULLSYNC
JOBCODE_FULLSYNC
JPM_CAT_FULLSYNC
POSITION_FULLSYNC
Enroll the existing employees in your PeopleSoft system into Clairvia via the Job Data page or using the ADD_CLAIRVIA_EMPLOYEES DataMover script provided by Oracle.
The ADD_CLAIRVIA_EMPLOYEES PeopleTools DataMover script enables you to add the initial employee and employee record instances that you want to integrate with Clairvia at one time. You modify the DataMover script to include the employee information for the desired employees, and then initiate the DataMover process to insert the employee information into the PS_PER_ORG_ASG_INT integration table.
For example, assume your hospital has 3,000 nurses that you wish to enroll in Clairvia. Rather than manually updating the Job Data for each of those employees, use the ADD_CLAIRVIA_EMPLOYEES DataMover script to complete a mass enrollment of the employees.
Run the Full Data Publish process again, to send any enrolled employee data from your PeopleSoft system to Clairvia.
Run the process for the following messages:
PERSON_BASIC_CV_FULLSYNC_EFF
WORKFORCE_CV_FULLSYNC
JPM_JP_CV_FULLSYNC_EFF
When any of the fields required by Clairvia in the Personal, Job, and Profile contributing components are updated, the following messages are published to Clairvia:
PERSON_BASIC_CV_SYNC_EFF
WORKFORCE_CV_SYNC
JPM_JP_CV_SYNC_EFF
The system publishes the messages to the Clairvia node after removing any future-dated and history rows using the Enterprise Components method Process Effdt Msg, for Person and HR Manage Profiles data. Clairvia only accepts current effective-dated information for these messages. Future-dated rows are published using the Enterprise Components Effective Dated Publish utility.
Clairvia accepts all historic, current and future dated messages for job related information
Clairvia does not integrate with organizational-related setup tables such as Business Unit, and Location, as well as other setup tables for Job Profile Management such as Rating Model, School, School Type and Major. If no integration point exists between PeopleSoft and Clairvia, you must manually map any desired setup table data. For subsequent change to a PeopleSoft table value, you must manually update the information in the Clairvia system. For example: adding a new location.
The following table describes the Clairvia fields and the corresponding Human Resources field data that is sent to Clairvia:
Clairvia Field Name |
Clairvia Description |
PeopleSoft Field Name |
---|---|---|
ProfileID/CostCenter |
Links Employee to a Profile |
DEPTID (External Dept ID) |
EmployeeID |
Employee's ID |
EmplID |
FirstName |
Employee's first name |
First Name |
LastName |
Employee's last name |
Last Name |
Initial/MI |
Employee's middle initial |
Middle Name |
|
Employee's email address |
Email_Addr |
HireDate |
The date on which the employee was hired. For example: 19960702 for July 2, 1996 |
Orig Start Date, Last Start Date |
BirthDate |
The date on which the employee was born. For example: 19730202 for February 2, 1973 |
Birth Date |
Street/Address |
Employee's street address |
Address Line 1 |
Apt |
Employee's apartment address |
Address Line 2 |
City |
City in which the employee lives |
City |
State/Province/Region |
State in which the employee lives |
State |
ZIP/Postal Code |
Employee's ZIP code |
Postal Code |
Country |
Country in which the employee lives |
Country |
Period* |
The type of period for employee hours, shifts, point and pay limits 0 - None, 1 - Day, 2 - Week, 3 - Month, 4 - Years, 5 - Bi Weekly |
Work Period |
HoursPerPeriod |
The max. no. of hours to be worked per period |
Standard Hours |
MinPeriod |
Type of period for Employee minimum limit. 0 - None, 1 - Day, 2 - Week, 3 - Month, 4 - Years, 5 - Bi Weekly |
Work Period |
Skill/JobCode |
Maps Job code to skill code |
Job Code |
HourRate |
Rate per hour |
Hourly Rate |
DeptID |
Employee Department ID |
DEPTID (External Dept ID) |
FTE |
Employee FTE status |
FTE |
EmpAction |
Employee action: 1-Transfer; 2 - Terminate; 3 - Change in Job |
Action Action_Descr |
ActionStartDate |
The date on which the employee action starts. For example: 19730202 for February 2, 1973 |
Effective Date Termination Date |
PhoneType |
Employee phone type: 1-HomeNum, 2-WorkNum, 3-PageNum, 4-OtherNum |
Phone Type |
PhoneNumber |
Employee phone number. Uses format: 1234567890 |
Phone |
CompetencyName |
Competency name |
Content Type |
CompetencyValue |
Competency value |
Content Items |
CompetencyExpDate |
Date on which the competency expires |
Expiration Date |
Years of Experience |
Years of Exp |
|
Seniority Date |
Company Seniority Date or Union Seniority Date |
|
Start Date |
Start Date LST_ASGN_START_DT |
|
Job Type |
Primary, Secondary |
Job Indicator |
This topic provides an overview of the message design for many of the sync and full-sync Integration Broker messages generated for Human Resources.
PERSON_BASIC_CV_FULLSYNC_EFF Message Design
For the Person Basic Clairvia FullSync Current Effective dated message (PERSON_BASIC_CV_FULLSYNC_EFF) the system uses the Enterprise Components Full Data Publish Utility. The system uses the mapping views on the Full Publish Rule to override the actual message records with views that extract only current effective dated rows for Clairvia employees.
The standard PERSON_BASIC_FULLSYNC message publishes information for all employees, regardless of their enrollment in Clairvia, as well as all past, present and future dated rows of information that is not relevant to Clairvia. Using the mapping views publishes only the current effective-dated information needed by Clairvia to the PERSON_BASIC_CV_FULLSYNC_EFF message immediately. The Full Data Publish Utility ignores historical data and writes future-dated rows to the EO_EFFDELAY delay record. The Enterprise Components Effective Date Publish utility picks up any records from the delay table that are now current and generates PERSON_BASIC_CV_SYNC_EFF messages.
The full data publish utility publishes a data message with all of the PERSON_DATA information for all Clairvia integrated employees.
WORKFORCE_CV_FULLSYNC Message Design
For the Workforce Clairvia FullSync message (WORKFORCE_CV_FULLSYNC) the system uses the Enterprise Components Full Data Publish Utility. The system uses the mapping views on the Full Publish Rule to override the actual message records with views that extract all historical, current and future dated rows for Clairvia employees.
Using the mapping views publishes only the information needed by Clairvia to the WORKFORCE_CV_FULLSYNC message immediately. This message does not use ‘_EFF’ in the message name, so it does not use current effective dating logic and passes all rows over to the new Clairvia message.
The full data publish utility publishes a data message with the workforce information for all Clairvia integrated employees.
JPM_JP_CV_FULLSYNC_EFF Message Design
For the HR Manage Profiles JP Clairvia FullSync Current Effective dated message (JPM_JP_CV_FULLSYN_EFF), the system uses the Enterprise Components Full Data Publish Utility. The system uses the mapping views on the Full Publish Rule to override the actual message records with views that extract only current effective dated rows for Clairvia employees for the desired HR Manage Profiles content type, using the highest ranking qualifier instance content items.
The standard JPM_JP_FULLSYNC message publishes information for all employees, regardless of their enrollment in Clairvia, as well as all qualifier instances and all past, present and future dated rows of information that is not relevant to Clairvia. Using the mapping views publishes only the current effective-dated information needed by Clairvia to the JPM_JP_CV_FULLSYNC_EFF message immediately. The Full Data Publish Utility ignores historical data and writes future dated rows to the EO_EFFDELAY Delay record. The Enterprise Components Effective Date Publish utility picks up any records from the delay table that are now current and generates JPM_JP_CV_SYNC_EFF messages.
The full data publish utility publishes a data message with all of the Profile information for all Clairvia integrated employees.
PERSON_BASIC_CV_SYNC_EFF Message Design
For the Person Basic Clairvia Sync Current Effective-dated message (PERSON_BASIC_CV_SYNC_EFF), the system makes two passes to place the generic data into a format that Clairvia can use. A handler was added to PERSON_BASIC_SYNC for the first pass and a handler added to PERSON_BASIC_CV_SYNC for the second pass.
In the first pass, the data in the PERSON_BASIC_SYNC message is copied to an interim PERSON_BASIC_CV_SYNC message that contains all data except for the PERS_ORG_REL_WK work record, which is not required by Clairvia.
In the second pass, an Enterprise Components routine reads the PERSON_BASIC_CV_SYNC message and determines if the message contains the current effective-dated row. Current effective-dated rows are copied to the PERSON_BASIC_CV_SYNC_EFF message for publishing. Future-dated rows are copied to the EO_EFFDELAY Delay record. The EC Effective Dating utility compares the future dated row to the date on the utility and if the date is now current, generates the PERSON_BASIC_CV_SYNC_EFF message. Historical rows are ignored and not copied to PERSON_BASIC_CV_SYNC_EFF. The Effective Dating utility creates three messages: a header message where PSCAMA. MSG_SEQ_FLG = H, a data message containing the actual data needed by Clairvia and a trailer message where PSCAMA. MSG_SEQ_FLG = T.
JPM_JP_CV_SYNC_EFF Message Design
For the HR Manage Profiles Profile Clairvia Sync Current Effective-dated message (JPM_JP_CV_SYNC_EFF), the system makes two passes to place the generic data into a format that Clairvia can use. A handler was added to JPM_JP_SYNC for the first pass and a handler added to JPM_JP_CV_SYNC for the second pass.
In the first pass, the data in the JPM_JP_SYNC message is copied to an interim JPM_JP_CV_SYNC message after the system removes any content types that are not one of the Clairvia installation table content types.
In the second pass, an Enterprise Components routine reads the JPM_JP_CV_SYNC message and determines if the message contains the current effective-dated row. Current effective-dated rows are copied to the JPM_JP_CV_SYNC_EFF message for publishing. Future-dated rows are copied to the EO_EFFDELAY Delay record. The Effective Dating utility compares the future dated row to the date on the utility and if the date is now current, generates the JPM_JP_CV_SYNC_EFF messages. Historical rows are ignored and not copied to JPM_JP_CV_SYNC_EFF. The Effective Dating utility creates three messages: a header message where PSCAMA. MSG_SEQ_FLG = H, a data message containing the actual data needed by Clairvia and a trailer message where PSCAMA. MSG_SEQ_FLG = T.
WORKFORCE_CV_SYNC Message Design
For the Workforce Sync Clairvia message (WORKFORCE_CV_SYNC), a handler for the message reads the generic WORKFORCE_SYNC message and copies all rows over to WORKFORCE_CV_SYNC that are for Clairvia Employees. All past, present and future data is copied to the WORKFORCE_CV_SYNC message.