Costing For Retropay Elements Can Produce Invalid Code Combinations
Last updated on JANUARY 05, 2017
Applies to:Oracle Payroll - Version 126.96.36.199 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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms