This document provides campuses with guidance and best practices for identifying and resolving duplicate records.
A User Profile is required for every CHRS ID.
Duplicate: What Kind Are You Dealing With?
A non-duplicate occurs when a person is created in both CHRS and Campus Solutions (CS) but is not a duplicate, such as a student applicant or POI. If the person declines a job offer, withdraws an application, or is no longer needed, they are still not considered a duplicate.
Previously, campuses could delete the Person/User ID from both CS and HR 9.0, but this is not recommended in CHRS. SWHR advises that non-duplicates remain in both CHRS and CS, regardless of their status.
Pancake has no association with any campus and is hired through CHRS Recruiting for Stanislaus. Stanislaus uses the CHRS Recruiting Staging Table to create Pancake as a Future Hire POI. Pancake receives CHRS ID 100044444 and CS Empl ID 005555555. However, 4 days before Pancake is set to begin, Stanislaus learns that Pancake is now declining the offer.
Pancake has no association with any campus and is hired by Stanislaus. Stanislaus decides to manually create Pancake as a Future Hire POI. Pancake receives CHRS ID 100044444 and CS Empl ID 005555555. However, 4 days before Pancake is set to begin, Stanislaus learns that Pancake is now declining the offer.
Pancake has no association with any campus and is hired through CHRS Recruiting for Maritime. Maritime uses the CHRS Recruiting Staging Table to put Pancake directly in Job Data. Pancake receives CHRS ID 100044444 and CS Empl ID 005555555. However, 4 days before Pancake is set to begin, Maritime learns that Pancake is now declining the offer.
Pancake has no association with any campus and is hired by Maritime. Maritime manually creates Pancake in Job Data rather than creating a Future Hire POI. Pancake receives CHRS ID 100044444 and CS Empl ID 005555555. However, 4 days before Pancake is set to begin, Maritime learns that Pancake is now declining the offer.
A Duplicate in CHRS Only occurs when a duplicate Person ID (CHRS Empl ID) is created solely within CHRS and not in Campus Solutions (CS).
POI:
Waffle Cone preexisted in CS and CHRS, with SSN ending is 9999. Waffle has CS Empl ID 885555555, and CHRS ID 100044444. Waffle is being hired and completes the Base Data Form in CHRS Recuriting (PageUp) and puts the SSN ending as 9991. When Waffle was created via the CHRS Recruiting Staging table, the CHRS Empl ID 100033333 was created when the record was loaded as a POI. A duplicate is also created in CS with the CS Empl ID 887777777 created.
Waffle Cone preexisted in CS and CHRS with SSN ending is 9999. Waffle has CS Empl ID 885555555, and CHRS ID 100044444. Maritime forgets to check CSU ID Search to see if Waffle already exists in CHRS and begins creating Waffle manually. While creating Waffle in CHRS and puts the SSN ending as 9991, when the “Carry ID” option appeared because of the duplicate data, instead of leaving the page completely, the person continued entry and created a POI. A duplicate is created in CHRS with CHRS Empl ID 100033333, and CS with the CS Empl ID 887777777.
Job Data:
Waffle preexists in CHRS with SSN ending 9999, CHRS ID 100044444, an inactive job record for Fullerton. Waffle does not exist in the CS environment for Stanislaus, who is hiring him. Stanislaus forgets to check CSU ID Search to see if Waffle already exists in CHRS and begins creating Waffle manually. While creating Waffle in CHRS, with all details being the same, when the “Carry ID” option appeared because of the duplicate data, instead of leaving the page completely, the person continued entry and created a Job Record with the new CHRS Empl ID 100033333. Waffle now has two CHRS Empl ID in CHRS but only one CS Empl ID for Stanislaus.
Waffle preexists in CHRS with SSN ending 9999, CHRS ID 100044444, an inactive job record for Fullerton. Waffle does not exist in the CS environment for Stanislaus, who hiring him. Waffle completes the Base Data Form in CHRS Recuriting (PageUp) and puts the SSN ending as 9991. When Waffle was created via the CHRS Recruiting Staging table, the CHRS Empl ID 100033333 was created when the record was loaded into Job Data. Waffle now has two CHRS Empl ID in CHRS but only one CS Empl ID for Stanislaus.
A duplicate in Campus Solutions (CS) occurs when a duplicate Person ID (CS Empl ID) is created exclusively in CS and becomes linked to the CHRS Empl ID as the User Profile in CHRS.
Waffle Cone preexisted in CS with CS Empl ID 885555555. In CS, Waffle has no SSN, a DOB of 1/1/1991, and the cell number 258/664-6525. Waffle is being hired and completes the Base Data Form in CHRS Recuriting (PageUp) and puts the SSN ending in 1988, DOB 1/1/1991, and cell 258/664-6525. When Waffle was created via the CHRS Recruiting Staging table, the CHRS ID 100044444 was created in CHRS, and a duplicate CS Empl ID 887777777 was also created causing the User Profile in CHRS to have the wrong Campus ID number.
Waffle Cone preexisted in CS with CS Empl ID 885555555. In CS, Waffle has no SSN, a DOB of 1/1/1991, a postal code of 95337, and cell 258/664-6525. Waffle is manually entered in CHRS with the SSN ending in 1988, DOB 1/1/1991, and address with postal code 95337, and cell 258/664-6525. This creates the CHRS ID 100044444, and a duplicate CS Empl ID 887777777 is also created causing the User Profile in CHRS to have the wrong Campus ID number.
Waffle Cone preexisted in CS with SSN ending is 9999, CS Empl ID 885555555, and does not exist in CHRS. Waffle is being hired and completes the Base Data Form in CHRS Recuriting (PageUp) and puts the SSN ending in 1991. When Waffle was created via the CHRS Recruiting Staging table, the CHRS ID 100044444 was created in CHRS and a duplicate CS Empl ID 887777777 was also created causing the User Profile in CHRS to have the wrong Campus ID number.
Waffle Cone preexisted in CS with SSN ending is 9999, CS Empl ID 885555555, and does not exist in CHRS. When Waffle was created in CHRS the SSN was entered manually ending in 9991. In CHRS ID 100044444 was created in CHRS and a duplicate CS Empl ID 887777777 was also created causing the User Profile in CHRS to have the wrong Campus ID number.
A duplicate in both CHRS and Campus Solutions (CS) occurs when duplicate Person IDs (CHRS Empl ID and CS Empl ID) are created in both systems and linked together in CHRS as a User Profile.
POI:
- Waffle Cone preexisted in CS and CHRS, with SSN ending is 9999. Waffle has CS Empl ID 885555555, and CHRS ID 100044444. Waffle is being hired and completes the Base Data Form in CHRS Recuriting (PageUp) and puts the SSN ending as 9991. When Waffle was created via the CHRS Recruiting Staging table, the CHRS Empl ID 100033333 was created when the record was loaded as a POI. A duplicate is also created in CS with the CS Empl ID 887777777 created.
- Waffle Cone preexisted in CS and CHRS with SSN ending is 9999. Waffle has CS Empl ID 885555555, and CHRS ID 100044444. Maritime forgets to check CSU ID Search to see if Waffle already exists in CHRS and begins creating Waffle manually. While creating Waffle in CHRS and puts the SSN ending as 9991, when the “Carry ID” option appeared because of the duplicate data, instead of leaving the page completely, the person continued entry and created a POI. A duplicate is created in CHRS with CHRS Empl ID 100033333, and CS with the CS Empl ID 887777777.
Job Data:
- Waffle Cone preexisted in CS with SSN ending is 9999 and had CS Empl ID 885555555. Waffle also preexists in CHRS with SSN ending 9999 and CHRS Empl ID 100044444. Stanislaus forgets to check CSU ID Search to see if Waffle already exists in CHRS and begins creating Waffle manually. While creating Waffle in CHRS, with all details being the same, when the “Carry ID” option appeared because of the duplicate data, instead of leaving the page completely, the person continued entry and created a Job Record with the new CHRS Empl ID 100033333. Waffle now has two CHRS Empl ID and two CS Empl ID.
- Waffle Cone preexisted in CS with SSN ending is 9999 and had CS Empl ID 885555555. Waffle also preexists in CHRS with SSN ending 9999 and CHRS Empl ID 100044444. Waffle completes the Base Data Form in CHRS Recuriting (PageUp) and puts the SSN ending as 9991. When Waffle was created via the CHRS Recruiting Staging table, the CHRS Empl ID 100033333 was created when the record was loaded into Job Data. Waffle now has two CHRS Empl ID and two CS Empl ID.
Tips to Prevent
Search for the employee in CHRS (see Find Employees with CSU ID Search) before you create a new POI or Employee in CHRS.
Search for the employee in the Campus Solution (CSU ID Search) before you create a new POI or Employee in CHRS.
When a duplicate is created there are specific steps a campus should take to resolve that duplicate. The only time a campus should rename a duplicate to “Duplicate” is if the duplicate cannot be deleted from the system. The only time a campus should change the SSN to a fake set of numbers is if the duplicate cannot be deleted from the system. The more duplicates a campus has in CS the higher probability of incorrect matching to occur within CS. The same can be said about CHRS. The more duplicates in CHRS, the higher probability of incorrect matching occurring.
The recommended SQL has been created for campuses to leverage for monitoring duplicates. This SQL is looking for individuals that have matching First Name, Last Name, and Date of Birth. This SQL will produce possible duplicates, but campuses will need to research the results to confirm if a true duplicate has been identified.
SELECT FIRST_NAME_SRCH, LAST_NAME_SRCH, A.BIRTHDATE, COUNT(*)
FROM PS_PERSON A, PS_NAMES B
WHERE A.EMPLID = B.EMPLID
AND NAME_TYPE = 'PRI'
AND B.EFFDT = (SELECT MAX(B_ED.EFFDT) FROM PS_NAMES B_ED
WHERE B.EMPLID = B_ED.EMPLID
AND B.NAME_TYPE = B_ED.NAME_TYPE
AND B_ED.EFFDT <= SYSDATE)
GROUP BY FIRST_NAME_SRCH, LAST_NAME_SRCH, A.BIRTHDATE
HAVING COUNT(*) > 1
ORDER BY 2, 1, 3;
Steps to Resolve
Step 1: Locate the correct Empl ID in both CHRS and Campus Solutions (CS), and identify the specific type of duplicate involved.
Step 2: Follow the appropriate resolution steps based on the duplicates situation.
Step 1: In CHRS - Change the person’s POI status from "Active" to "Inactive" by navigating to the Maintain POI page in correction mode. Update the Planned Exit Date to the current date, then click “Save.”
Step 1: In CHRS - In Job Data add a TER/ERR (Termination/Error) row using the same effective date as the original hire row. In the PPT Comments, include a brief note explaining the reason for the TER/ERR action—for example: “Declined offer after being created.”
Step 1: In CHRS - Under Modify a Person, change the Person Name of the duplicate record to "DO NOT USE"
Step 2: In CHRS - Update the CHRS Empl ID in the User Profile linked to the duplicate record with the correct CHRS Empl ID.
Navigation: Menu > PeopleTools > Security > User Profiles
Step 3: In CHRS - Create a POI record for your campus using the correct CHRS Empl ID.
Step 4: In CS - Run SQL to update Crosswalk Table in CS
Crosswalk Refresh SQL for CS
DELETE FROM PS_CSU_CHRS_XREF;
INSERT INTO PS_CSU_CHRS_XREF(CSU_CHRS_ID, CSU_CS_ID)
SELECT CSU_CHRS_ID, CSU_CS_ID
FROM PS_CSU_EMPL_MAP_VW@CSU_CS_HR_LINK A , PS_INSTALLATION B
WHERE (B.COMPANY = 'FUL' AND A.BUSINESS_UNIT = 'FLCMP')
OR (B.COMPANY = 'STA' AND A.BUSINESS_UNIT = 'STCMP')
OR (B.COMPANY = 'CMA' AND A.BUSINESS_UNIT = 'MACMP')
OR (B.COMPANY = 'CI' AND A.BUSINESS_UNIT = 'CICMP')
OR (B.COMPANY = 'CHI' AND A.BUSINESS_UNIT = 'CHICO')
OR (B.COMPANY = 'CMA' AND A.BUSINESS_UNIT = 'MACMP')
OR (B.COMPANY = 'SAC' AND A.BUSINESS_UNIT = 'SACST')
OR (B.COMPANY = 'BAK' AND A.BUSINESS_UNIT = 'BKCMP')
OR (B.COMPANY = 'CHO' AND A.BUSINESS_UNIT = 'COCSU')
OR (B.COMPANY = 'DOM' AND A.BUSINESS_UNIT = 'DHCMP')
OR (B.COMPANY = 'EBY' AND A.BUSINESS_UNIT = 'EBCMP')
OR (B.COMPANY = 'FRE' AND A.BUSINESS_UNIT = 'FRSNO')
OR (B.COMPANY = 'HSU' AND A.BUSINESS_UNIT = 'HMCMP')
OR (B.COMPANY = 'LBH' AND A.BUSINESS_UNIT = 'LBCMP')
OR (B.COMPANY = 'LAS' AND A.BUSINESS_UNIT = 'LACMP')
OR (B.COMPANY = 'MBY' AND A.BUSINESS_UNIT = 'MB000')
OR (B.COMPANY = 'NOR' AND A.BUSINESS_UNIT = 'NRCMP')
OR (B.COMPANY = 'CPP' AND A.BUSINESS_UNIT = 'POCMP')
OR (B.COMPANY = 'SBU' AND A.BUSINESS_UNIT = 'SBCMP')
OR (B.COMPANY = 'SDS' AND A.BUSINESS_UNIT = 'SDCMP')
OR (B.COMPANY = 'SFO' AND A.BUSINESS_UNIT = 'SFCMP')
OR (B.COMPANY = 'SJS' AND A.BUSINESS_UNIT = 'SJ000')
OR (B.COMPANY = 'SLO' AND A.BUSINESS_UNIT = 'SLCMP')
OR (B.COMPANY = 'CSM' AND A.BUSINESS_UNIT = 'SMCMP')
OR (B.COMPANY = 'SSU' AND A.BUSINESS_UNIT = 'SOCMP');
COMMIT;
Step 5: In CS - Confirm correct mapping on the Crosswalk Table in CS
Navigation: Menu > CSU SA Baseline > CSU Campus Community > CHRS Cross Reference
Step 6: In ServiceNow - Submit a ticket.
Category: CMS-CHRS
Subcategory: Integration
Short Description: Delete Person (CHRS ID)
Description:
Environment: HCHRPRD (CHRS Production)
Duplicate Type: CHRS-only duplicate; POI-only; person record needs to be deleted
Created By: [Name of Creator], User Profile Number: [Creator's User Profile #]
Duplicate Record: [Duplicate's Name], User Profile Number: [Duplicate's User Profile #], Incorrect CHRS Empl ID: [Incorrect Empl ID]
Date Created: [Date the duplicate was created]
A duplicate entry in Job Data cannot be deleted and must retain its associated User Profile.
Step 1: In CHRS - Under Modify a Person, change the Person Name of the duplicate record to DO NOT USE (First Name) Duplicate- Campus Initials (Last Name). (Example: DO NOT USE DuplicateSAC)
Step 2: In CHRS - Under User Profile, change the description of the duplicate record to DO NOT USE (First Name) Duplicate- Campus Initials (Last Name). (Example: DO NOT USE DuplicateSAC)
Step 3: In CHRS - In Job Data, add a TER/ERR row for the duplicate record using the same effective date as the hire row and set the effective sequence to 1. Document in the PPT comments the valid CHRS ID and User Profile. (example: Correct CHRS ID 100033344 and User Profile 630000021 )
Step 4: In CHRS - Create a Job Record for your campus using the correct CHRS Empl ID for the employee, and note in the PPT comments that a duplicate CHRS Empl ID and User Profile was previously created.(example: Duplicate CHRS ID 100033333 and User Profile 630000001)
Step 5: In CHRS - Confirm a User Profile is created in CHRS attached to a different CS Empl ID.
Step 6: In CS - Lock the CS ID associated with the CHRS Duplicate.
The CS Empl ID cannot be deleted because it is linked to a record in Job Data.
Step 7: In ServiceNow - Submit a ticket.
Category: CMS-CHRS
Subcategory: Integration
Short Description: Lock User Profile (Put User Profile Number)
Description:
Environment: HCHRPRD (CHRS Production)
Duplicate Type: CS and CHRS Duplicate, exists in Job Data; User Profile needs to be locked in CHRS
Created By: [Name of Creator], User Profile Number: [Creator's User Profile #]
Duplicate Record: [Duplicate's Name], User Profile Number: [Duplicate's User Profile #], Incorrect CHRS Empl ID: [Incorrect Empl ID]
Date Created: [Date the duplicate was created]
Step 1: In CHRS - Remove the CHRS Empl ID from the ID tab of User Profile
Navigation: Menu > PeopleTools > Security > User Profiles > User Profiles
Step 2: In ServiceNow - Submit a ticket and wait for response.
Category: CMS-CHRS
Subcategory: Integration
Short Description: Delete User Profile (Put User Profile Number)
Description:
Environment: HCHRPRD (CHRS Production)
Duplicate Type: CS-only duplicate
Created By: [Name of Creator], User Profile Number: [Creator's User Profile #]
Duplicate Record: [Duplicate's Name], User Profile Number: [Duplicate's User Profile #], Correct CHRS Empl ID: [Empl ID]
Date Created: [Date the duplicate was created]
Step 3: In CHRS - Manually create the User Profile using the correct CS Empl ID, including the campus number prefix (e.g., 07003085411).
Job Aid: Add and Maintain User Profiles
Step 4: In CS - Delete the duplicate
Navigation: Menu > Set Up SACR > System Administration > Database Processing
Step 5: In CS - Update the correct CS Empl ID in the Add/Update Person page by entering the correct SSN, if it is missing or incorrect.
Step 6: In CS - Run SQL to update Crosswalk Table in CS
Crosswalk Refresh SQL for CS
DELETE FROM PS_CSU_CHRS_XREF;
INSERT INTO PS_CSU_CHRS_XREF(CSU_CHRS_ID, CSU_CS_ID)
SELECT CSU_CHRS_ID, CSU_CS_ID
FROM PS_CSU_EMPL_MAP_VW@CSU_CS_HR_LINK A , PS_INSTALLATION B
WHERE (B.COMPANY = 'FUL' AND A.BUSINESS_UNIT = 'FLCMP')
OR (B.COMPANY = 'STA' AND A.BUSINESS_UNIT = 'STCMP')
OR (B.COMPANY = 'CMA' AND A.BUSINESS_UNIT = 'MACMP')
OR (B.COMPANY = 'CI' AND A.BUSINESS_UNIT = 'CICMP')
OR (B.COMPANY = 'CHI' AND A.BUSINESS_UNIT = 'CHICO')
OR (B.COMPANY = 'CMA' AND A.BUSINESS_UNIT = 'MACMP')
OR (B.COMPANY = 'SAC' AND A.BUSINESS_UNIT = 'SACST')
OR (B.COMPANY = 'BAK' AND A.BUSINESS_UNIT = 'BKCMP')
OR (B.COMPANY = 'CHO' AND A.BUSINESS_UNIT = 'COCSU')
OR (B.COMPANY = 'DOM' AND A.BUSINESS_UNIT = 'DHCMP')
OR (B.COMPANY = 'EBY' AND A.BUSINESS_UNIT = 'EBCMP')
OR (B.COMPANY = 'FRE' AND A.BUSINESS_UNIT = 'FRSNO')
OR (B.COMPANY = 'HSU' AND A.BUSINESS_UNIT = 'HMCMP')
OR (B.COMPANY = 'LBH' AND A.BUSINESS_UNIT = 'LBCMP')
OR (B.COMPANY = 'LAS' AND A.BUSINESS_UNIT = 'LACMP')
OR (B.COMPANY = 'MBY' AND A.BUSINESS_UNIT = 'MB000')
OR (B.COMPANY = 'NOR' AND A.BUSINESS_UNIT = 'NRCMP')
OR (B.COMPANY = 'CPP' AND A.BUSINESS_UNIT = 'POCMP')
OR (B.COMPANY = 'SBU' AND A.BUSINESS_UNIT = 'SBCMP')
OR (B.COMPANY = 'SDS' AND A.BUSINESS_UNIT = 'SDCMP')
OR (B.COMPANY = 'SFO' AND A.BUSINESS_UNIT = 'SFCMP')
OR (B.COMPANY = 'SJS' AND A.BUSINESS_UNIT = 'SJ000')
OR (B.COMPANY = 'SLO' AND A.BUSINESS_UNIT = 'SLCMP')
OR (B.COMPANY = 'CSM' AND A.BUSINESS_UNIT = 'SMCMP')
OR (B.COMPANY = 'SSU' AND A.BUSINESS_UNIT = 'SOCMP');
COMMIT;
Step 7: In CHRS - Update the CHRS Empl ID in Modify a Person page by entering the correct SSN, if it is missing or incorrect.
Step 8: In CHRS - Temporarily change the cell phone number to 222-222-2222, in Modify a Person. Be sure to copy and save the original cell phone number so it can be restored later.
Step 9: In CS - Confirm correct mapping on the Crosswalk Table in CS.
Navigation: Menu > CSU SA Baseline > CSU Campus Community > CHRS Cross Reference
Step 10: In CHRS - In Modify a Person Restore the original cell phone number that was previously saved, replacing the temporary number (i.e. 222-222-2222).
Step 1: In ServiceNow - Submit a ticket and wait for response.
Category: CMS-CHRS
Subcategory: Integration
Short Description: Delete User Profile and Person (Put User Profile Number and CHRS Empl ID)
Description:
Environment: HCHRPRD (CHRS Production)
Duplicate Type: CS and CHRS Duplicate, POI-only
Created By: [Name of Creator], User Profile Number: [Creator's User Profile #]
Duplicate Record: [Duplicate's Name], User Profile Number: [Duplicate's User Profile #], Incorrect CHRS Empl ID: [Incorrect Empl ID]
Date Created: [Date the duplicate was created]
Step 2: In CS - Delete the duplicate
Navigation: Menu > Set Up SACR > System Administration > Database Processing
Step 3: In CS - Run SQL to update Crosswalk Table in CS
Crosswalk Refresh SQL for CS
DELETE FROM PS_CSU_CHRS_XREF;
INSERT INTO PS_CSU_CHRS_XREF(CSU_CHRS_ID, CSU_CS_ID)
SELECT CSU_CHRS_ID, CSU_CS_ID
FROM PS_CSU_EMPL_MAP_VW@CSU_CS_HR_LINK A , PS_INSTALLATION B
WHERE (B.COMPANY = 'FUL' AND A.BUSINESS_UNIT = 'FLCMP')
OR (B.COMPANY = 'STA' AND A.BUSINESS_UNIT = 'STCMP')
OR (B.COMPANY = 'CMA' AND A.BUSINESS_UNIT = 'MACMP')
OR (B.COMPANY = 'CI' AND A.BUSINESS_UNIT = 'CICMP')
OR (B.COMPANY = 'CHI' AND A.BUSINESS_UNIT = 'CHICO')
OR (B.COMPANY = 'CMA' AND A.BUSINESS_UNIT = 'MACMP')
OR (B.COMPANY = 'SAC' AND A.BUSINESS_UNIT = 'SACST')
OR (B.COMPANY = 'BAK' AND A.BUSINESS_UNIT = 'BKCMP')
OR (B.COMPANY = 'CHO' AND A.BUSINESS_UNIT = 'COCSU')
OR (B.COMPANY = 'DOM' AND A.BUSINESS_UNIT = 'DHCMP')
OR (B.COMPANY = 'EBY' AND A.BUSINESS_UNIT = 'EBCMP')
OR (B.COMPANY = 'FRE' AND A.BUSINESS_UNIT = 'FRSNO')
OR (B.COMPANY = 'HSU' AND A.BUSINESS_UNIT = 'HMCMP')
OR (B.COMPANY = 'LBH' AND A.BUSINESS_UNIT = 'LBCMP')
OR (B.COMPANY = 'LAS' AND A.BUSINESS_UNIT = 'LACMP')
OR (B.COMPANY = 'MBY' AND A.BUSINESS_UNIT = 'MB000')
OR (B.COMPANY = 'NOR' AND A.BUSINESS_UNIT = 'NRCMP')
OR (B.COMPANY = 'CPP' AND A.BUSINESS_UNIT = 'POCMP')
OR (B.COMPANY = 'SBU' AND A.BUSINESS_UNIT = 'SBCMP')
OR (B.COMPANY = 'SDS' AND A.BUSINESS_UNIT = 'SDCMP')
OR (B.COMPANY = 'SFO' AND A.BUSINESS_UNIT = 'SFCMP')
OR (B.COMPANY = 'SJS' AND A.BUSINESS_UNIT = 'SJ000')
OR (B.COMPANY = 'SLO' AND A.BUSINESS_UNIT = 'SLCMP')
OR (B.COMPANY = 'CSM' AND A.BUSINESS_UNIT = 'SMCMP')
OR (B.COMPANY = 'SSU' AND A.BUSINESS_UNIT = 'SOCMP');
COMMIT;
Step 4: In CHRS - Create a POI record for your campus using the correct CHRS Empl ID.
Step 5: In CHRS - Confirm a User Profile is created in CHRS attached to the correct CS Empl ID.
A duplicate entry in Job Data cannot be deleted and must retain its associated User Profile.
Step 1: In CHRS - Under Modify a Person, change the Person Name of the duplicate record to DO NOT USE (First Name) Duplicate- Campus Initials (Last Name). (Example: DO NOT USE DuplicateSAC)
Step 2: In CHRS - Under User Profile, change the description of the duplicate record to DO NOT USE (First Name) Duplicate- Campus Initials (Last Name). (Example: DO NOT USE DuplicateSAC)
Step 3: In CHRS - In Job Data, add a TER/ERR row for the duplicate record using the same effective date as the hire row and set the effective sequence to 1. Document in the PPT comments the valid CHRS ID and User Profile. (example: Correct CHRS ID 100033344 and User Profile 630000021 )
Step 4: In CHRS - Create a Job Record for your campus using the correct CHRS Empl ID for the employee, and note in the PPT comments that a duplicate CHRS Empl ID and User Profile was previously created.(example: Duplicate CHRS ID 100033333 and User Profile 630000001)
Step 5: In CHRS - Confirm a User Profile is created in CHRS attached to a different CS Empl ID.
Step 6: In CS - Lock the CS ID associated with the CHRS Duplicate.
The CS Empl ID cannot be deleted because it is linked to a record in Job Data.
Step 7: In ServiceNow - Submit a ticket.
Category: CMS-CHRS
Subcategory: Integration
Short Description: Lock User Profile (Put User Profile Number)
Description:
Environment: HCHRPRD (CHRS Production)
Duplicate Type: CS and CHRS Duplicate, exists in Job Data; User Profile needs to be locked in CHRS
Created By: [Name of Creator], User Profile Number: [Creator's User Profile #]
Duplicate Record: [Duplicate's Name], User Profile Number: [Duplicate's User Profile #], Incorrect CHRS Empl ID: [Incorrect Empl ID]
Date Created: [Date the duplicate was created]
End of Article
0 Comments
Add your comment