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.
Managing Costing Data in Core HR
Content
In the current configuration we have, we are managing costing data such as entity, division, department code, etc at employee level via Costing for a person task under Payroll (see attached screenshot). This is causing a lot of issue in terms of data integrity or inaccuracy of data as Employment page may have been updated with a new department on employee but costing still refers old values. When we designed the core configuration, we were told by our support vendor that this was the best option to store department code and finace's other costing data for GL. Due to constant
1