Incorrect 'Date Of Payment' In PAYG Payment Summary

(Doc ID 1968238.1)

Last updated on MARCH 08, 2017

Applies to:

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

Symptoms

On : 12.1.2 version, Australian Payroll

ACTUAL BEHAVIOR
---------------
'Date of Payment' on ETP Payment Summary changes depending on whether Costing is run before or after Payment Summary is produced.

Example to illustrate:

Pay period details:

 Period                 Start Date     End Date     Payment     Direct Entry
 -------------------------------------------------------------------
 1 2014 Bi-Week    21-JUN-14     04-JUL-14     8-JUL-14     07-JUL-14


Employee termination details:

 Actual: 27-Jun-14
 Last Standard Process: 4-Jul-14
 Final Process: 14-Jul-14


Employee was paid via a quickpay:

  Date Paid : 28-Jun-14
  Date Earned: 27-Jun-14


Ran Costing on 8-Jul-14 with:

  Start Date: 25-Jun-14
  End Date: 8-Jul-14


In the resulting ETP payment summary it shows 'Date of Payment' as 8-Jul-14.

If Payment Summary is produced prior to Costing run, 'Date of Payment' would be 28-Jun-14.


EXPECTED BEHAVIOR
-----------------------
Expect 'Date of Payment' to be 28-Jun-14.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
- Terminate the employee
- Run Quickpay
- Run Quick PrePayments
- Run Payment Summary Archive
- Run 'Produce Self Printed Payment Summary XML-PDF (Australia)
- Run 'Print Self Printed Payment Summary - PDF (Australia)'
>>> Verify 'Date of Payment' in ETP Payment Summary produced

- Rollback Payment Summary requests.

- Run Costing
- Run Payment Summary Archive
- Run 'Produce Self Printed Payment Summary XML-PDF (Australia)
- Run 'Print Self Printed Payment Summary - PDF (Australia)'
>>> Check 'Date of Payment' in ETP Payment Summary produced

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users are getting incorrect 'Date of Payment' on their ETP Payment Summary.

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