Yearend Archive Displaying The Incorrect End Date On The Format 37 For Terminated Employees (Doc ID 1907752.1)

Last updated on DECEMBER 20, 2016

Applies to:

Oracle HRMS (Mexico) - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

On : 12.1.3 version, Payroll Year End

ACTUAL BEHAVIOR
---------------
The Format 37 is showing this for a terminated employee
PERIODO QUE AMPARA LA CONSTANCIA:
MES INICIAL MES FINAL EJERCICIO
  01 06 2013

The 01 is the start month
The 06 is the end month
Year - 2013

The end month is using the month when the costing was processed for the employee and not the month when last paid

EXPECTED BEHAVIOR
-----------------------
The Format 37 to use Termination month as the last month the employee was paid regardless of when the costing was done

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. It was noticed that this issue can be reproduced at will for those terminated employees for whom a late payroll action like Costing or Transfer to GL is processed. If there is any payroll action with date earn greater than the employee’s actual termination date, then the Year End Archiver, DIM & Format 37 are taking the date of the last process or payroll action as end date/month.

2. CASE1:
Executed costing to 30-Apr-2014
Executed Yrend arch to 24-abr: the end date is correct
Executed Yrend arch to 30-abr: the end date is not correct
Returned Year end arch
Returned Costing to 30-apr-2014
Executed costing 16-abr to 15-may-2014: DTH CONFIANZA (case 1)
Executed yrend arch to 24-abr: (BAJAS_DTH_CONFIANZA)
Returned Year end arch

scenario 1: year end archiver effective date = 24-APR-2014 | end date = actual term. date (02-APR-2014)
scenario 2: year end archiver effective date = 30-APR-2014 | end date: 30-APR-2014
scenario 3: year end archiver effective date = 15-MAY-2014 | end date: 30-APR-2014
scenario 4: year end archiver effective date = 16-MAY-2014 | end date: 30-APR-2014

3. CASE2:
scenario 1: year end archiver effective date = 15-MAY-2013 | end date: 15-MAY-2013
scenario 2: year end archiver effective date = 15-JUN-2013 | end date: 15-JUN-2013
scenario 3: year end archiver effective date = 30-JUN-2013 | end date: 30-JUN-2013
scenario 4: year end archiver effective date = 31-DEC-2013 | end date: 30-JUN-2013
scenario 4: year end archiver effective date = 31-MAY-2013 | end date: 31-MAY-2013


None was using the actual termination date of the employee in  the Year End Archive, End Date


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot create a correct Format 37 or DIM report

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