Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Person Number Generation Method from Automatic Upon Final Save to Automatic Prior to Submission

in Human Capital Management 2 comments

Summary:

What is the impact or the Pros and Cons of changing Person Number Generation Method from Automatic Upon Final Save to Automatic Prior to Submission?

Content (required):

We noticed that on our action process 'Add Contingent Worker', the FYI notification post approval did not render any person number or values from the standard FYI notification. That is fine from our Customer Payroll team who are receiving such notification on the auditing of changes. The Oracle SR suggested to change the Person Number Generation Method from Automatic Upon Final Save to Automatic Prior to Submission. We have tested this change and it now displayed the Person Number values from the notification, but they want to know the Pros and Cons of this change. Please advise.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!