Costing For Retropay Elements Can Produce Invalid Code Combinations
(Doc ID 753570.1)
Last updated on JUNE 24, 2019
Applies to:Oracle Payroll - Version 188.8.131.52 and later
Information in this document applies to any platform.
Retro elements are created by the Retropay by Element process. When running the Costing process, the segment values are derived from the original element as at the date earned even where one or more of the values may have been end dated.
Is this intended functionality? I would have expected that where a value was no longer valid, the process would have used the suspense account as occurs for non-retro elements.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document