Costing For Retropay Elements Can Produce Invalid Code Combinations (Doc ID 753570.1)

Last updated on JANUARY 05, 2017

Applies to:

Oracle Payroll - Version 11.5.10.2 and later
Information in this document applies to any platform.

Goal

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.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms