Learn about the new Oracle AI Agent Studio for Fusion Applications: Watch Now
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
Progress with Redwood: Redwood Resources for Oracle Cloud HCM - Go Here
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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Impact of using Busniess Group rather than Department to create Groups
Summary:
Hello,
We are currently implementing Core HR for a client and would like to know the impact of using Business Unit rather than Department to store their Groups.
Problem Description:
The client has a hierarchical structure of Department in 3 levels: Group --> Department --> Sub-Department.
We proposed the client to define the Groups, Departments and Sub-Departments under the Department object. However, their concern is that they want to see the hierarchical structure of these departments displayed when creating a new Position.
Since the Position screen has a field to input Business Unit, they wanted to use this field to include their Groups.
Tagged:
0