Recently someone reached out to us stating that he is getting the A Person Number with this value already exists error when entering a new person:
As you can see in the screenshot below, the complete error message states: A Person Number with this value already exists. Enter a unique value
This mainly happens when sequence specified at the enterprise HCM information screen is trying to use a number that is already assigned. See the screenshot of the enterprise HCM Information page.
When you encounter such a scenario, you need to identify what is the maximum number used by the sequence. To do that go to your Reports and analytics area:
Click on the Browse catalog icon
Click on New > Data Model
Click + and choose the SQL Query option
Run the query to get the highest person number
Make sure to select the ApplicationDB_HCM and click OK.
Query used in the screenshot:
select min(person_number), max(person_number), length(person_number) from per_all_people_f where person_number not like ‘U%’ and person_number not like ‘W%’ group by length(person_number)
Then go to the Data tab and click View. Click on the Table view for easy viewing.
As you can see in the above screenshot, that 3009 is the highest person number used in the application. You can then either set the next number in the enterprise HCM Info page or any higher starting number.
Save the information and you should be able to avoid the “A Person Number with this value already exists error”.
For complete training on Fusion visit our Fusion HCM Courses
We also recommend you to visit Oracle Forums and explore Oracle Support to learn more scenarios and solutions.
Disclaimer: The query shown is for demonstration purpose only. Make sure to do changes as per your client requirements
2 responses on "A Person Number with this value already exists error"
Leave a Message
You must be logged in to post a comment.
Thanks for the post. I have a question, what could be the reason for this? When I saw the first screen shot of this post I was thinking max number would be 9999. But It is not. Changing the HCM information page to 3009 is correct?
The max number is not necessarily 9999. Any specific reason why you thought it should be 9999?