Retro is creating three entries with gross sum of element input value as zero

(Doc ID 2360497.1)

Last updated on FEBRUARY 13, 2018

Applies to:

Oracle Fusion Global Payroll Cloud Service - Version 11.12.1.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 11.12.1.0.0 version, AE - United Arab Emirates Legislation

ACTUAL BEHAVIOR
---------------
Retro Unusual entries over previous month Retro

We have run retro for December month and couple of unusual entries has come up for three set of employee. Costing has also not happened correctly for these employees.
We have further checked into retro event notification but could not find any.

We have attached a log file for retro , element details, original date earned, and employee details for your reference.

EXPECTED BEHAVIOR
-----------------------

Identifying the root cause so that appropriate action can be taken. As of now these 14 transactions has errored in core banking. Finance would need a justified reasoning for the same

Expectation : These entries should not have been created at all

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

Retro is creating three entries with gross sum of element input value as zero. ie. like -100, 30, 70 i.e three entries are created for one element.
Now it do not have impact on actual payout but when costing is generated for the same, it add Secondary offset account as a concatenated segment which is not correct

Person Number Element Name Input Name Result Value Effective Start Date Effective End Date Entry Sequence Creator Type Original Earned Date Parent Element Name Parent Entry Number
XXX Basic Salary Retro Pay Value -68103 2017-12-01 2017-12-31 1 Retroactive Pay Run Result 2017-06-30 Basic Salary 1
XXX Basic Salary Retro Pay Value 45402 2017-12-01 2017-12-31 2 Retroactive Pay Element Entry 2017-06-30 Basic Salary 1
XXX Basic Salary Retro Pay Value 22701 2017-12-01 2017-12-31 3 Retroactive Pay Element Entry 2017-06-30 Basic Salary 1

We had just run the retro with effective date of 31-Dec-2017 which is a standard process. There has not been any change in the system which could have triggered these elements.

Expectation :These entries should not have been created at all


There has not been any error and it has successfully processed but it gives wrong picture in the costing & general ledger i.e. core banking

In this example - if you sum the value -68103, 45402, 22701 ,it would sum as zero.

What does it essentially mean that there is no triggering event but still values are processed for this element.

This has happened only for 3 employee and has not been processed correctly for other eligible employees.


Further observation:

one entry of "Retroactive Pay Run Result" creator type is equal to sum of two entries of "Retroactive Pay Element Entry" creator type

BUSINESS IMPACT
-----------------------
The issue has the following business impact:

Due to this issue, users cannot reconcile GL balances in production. Year end is approaching and Bank needs to close year end reporting with in current year itself

Cause

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