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.
Non-recurring elements have incorrect costing due to element entry end date being end of period
Summary:
Element entries for non-recurring elements run from the effective date to the end of the period. If the employee transfers to another job between those dates, the element is costed to the new job, not the old job.
Content (required):
The expectation is that non-recurring element entries should be costed on the element start date. But the standard behaviour is that the end date of element entries is set to the period end date and costing appears to run as at the element end date. If the employee transfers to a different job between those dates, the wrong costing is used.
0