Data Published to Clairvia
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 |