Self Service Payment Summaries Are Not Displaying Correctly After RUP 8
(Doc ID 2072385.1)
Last updated on MARCH 08, 2017
Applies to:Oracle HRMS (Australia) - Version 12.1.3 to 12.2.5 [Release 12.1 to 12.2]
Information in this document applies to any platform.
On : 12.1.3 version, Australian Payroll
From RUP8, Oracle now provides the flexibility to choose the start year from when they wish to view the Payment Summary. A new segment 'Start Year Enabled' is now available on the 'Self Service PS Display' Organization Information at GRE / Legal Entity level that enables users to select the financial year from which they want to view the Payment Summary.
Under Legal Employer say you have 'Self Service PS Display' set to:
Financial Year Enabled: 2014/2015
Start Year Enabled: 2013/2014
Log into AU Employee Self-Service > AU View Payment Summary
- Select Year : 2014/2015
Find you get two rows returned in 'Selected Payment Summary' LOV instead of one:
Assignment Number Legal Employer
156 Vision Australia
156 Vision Australia
Select the first record above and click 'Go' - find Payment Summary opened is for 2014/2015
Select the second record above and click 'Go' - find Payment Summary opened is for 2013/2014
So Payment Summary returned is not restricted based on the 'Year' user selected.
Expect system to only return the Payment Summary based on the Year value.
1. If new segment 'Start Year Enabled' is not populated then the user will not get the available Payment Summaries returned in Self Service.
2. If the Manager / Payroll Profession does not have an employee assigned to their User Name under System Administrator responsibility (N: Security - User - Define) then when you click on PRINT icon for the employee to open the Payment Summary, you will get error "Report not available for online viewing. Please contact your Administrator for further information" and unable to proceed.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|