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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Position setup optimization
Summary
One Business Unit vs multi Busines Unit when creating positionContent
Experts...need your opinion
Position is driven by business unit. Client is setup to have one to one relationship of LE and BU. If client wants to share the same position attributes between the business units. Client will need to setup another position with the exact attributes. That will mean there is a lot duplicate positions with just different BU. Would it be better to create a over arching business unit that allows user to use same positions across different LE/BU? By creating this over arching busies unit is there downstream impact? GL interface client is using the default expense account field so what's setup
Tagged:
2