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.

Impact of moving from a position based structure to a Job based structure

Summary:What are some of the things to consider when moving from a position based structure to a Job based structure


Content (please ensure you mask any confidential information):

I am looking for the best approach while changing the model from position-based to job-based. Currently Client system has position Based enterprise implementation and they are using the system for over the years. Now they want to remove Positions and go with only job-based implementation.

If anyone has come across this scenario please share the reference documents like Questionnaire, Impact analysis, etc. and the recommended approach

Version (include the version you are using, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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