ID Delete Process (HR_PER502) Causes Blank EMPLID in Profile Management Tables, and Causes Manage Hire Process to Fail With Subscription Error: "The Profile Type already exists ...(18300,45)"
Last updated on FEBRUARY 15, 2018
Applies to:PeopleSoft Enterprise HRMS Human Resources - Version 9 to 9.1 [Release 9]
PeopleSoft Enterprise HRMS Talent Acquisition Manager - Version 9 to 9.1 [Release 9]
Information in this document applies to any platform.
***Checked for relevance on 23-Jun-2014***
After running Delete ID process, Post-hire Integration Broker messages fail with the following error:
'The Profile Type already exists for this person (18300,45)'
STEPS TO REPRODUCE:
1. Run ID delete Process to delete employee ID (Set Up HRMS, System Administration, Database Processes, ID Delete.)
2. Make sure EMPLID value is blank in JPM_PROFILE table.
3. Initiate Prepare for Hire, Perform Manage Hire.
4. Check Subscription Contract Error Messages and you will find that an error occurred while changing the value of the field due to empty EMPLID row in JPM_Profile table.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms