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

Best Practice on Person Number of Employee's Contact

in Workforce Management 5 comments

Summary: Contact Number generation upon data load is consuming client's requested Employee Person Numbers


Content (required):

We are undertaking a Global Implementation and hence receiving and loading Worker Data in batches. Clients are moving from their legacy system and all current Employee Person Numbers shall be loaded as is. However for any new hire, new person number series has been specified.

However, there are cases on loading worker data- with their contacts/family, when the data load consumes numbers for contacts loaded.

These numbers consume the upcoming employee numbers that are existing.

Please suggest best practices around these.

The workaround we propose is loading Contact's Person Numbers with a unique series altogether from our end while loading. Requesting suggestions if that has any impact moving forward.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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