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.

Action/Action Reason Removal

edited Apr 14, 2017 5:20PM in Human Capital Management 6 comments

Summary

Action/Action Reason Removal

Content

Hello,

 

We are looking to reduce the # of action and action reason codes we have available. For example, we would have a generice 'Assignment Change' (Action)/Other (Action Reason) that would be used for Manager Change, Location Change, Department Change, etc.

 

I know we would have to update the historical assignment records that are tied to the ones we disable, but is there any other negative impact to the system we should be aware of? 

 

The SUI Action shortcuts for Manager Change, Location Change, etc. would be disabled.

 

Please let me know your thoughts. Also, I'm looking to see what other companies are doing - are their action/action reasons generalized or very specific?

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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