Primary Assignment Bug
(Doc ID 2314021.1)
Last updated on OCTOBER 04, 2017
Applies to:Oracle Fusion Global Human Resources Cloud Service - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
The user has a primary assignment (let us say A1). He creates a temporary assignment (A2) and makes it primary. Now A1 has become secondary. User then deletes the temporary assignment. A1 is still secondary. A1 is not switched over to primary because of this scenario. Suppose there is a A3 which is also secondary, then the system won't be able to determine whether to switch A1 or A3 as primary. This was the reason the enhancement request 24969946 was rejected.
Customer has to do a primary flag change explicitly every time they delete a temporary assignment.
Customer wants the below behavior to be implemented.
1) When they delete a temporary primary assignment, a pop-up message asks them to choose a new primary assignment.
2) An error message is thrown when they delete a temporary primary assignment without switching any other assignment to primary.
Their primary concern is that the system should not allow such data problems to occur and they should not come back to Oracle for data fix scripts.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!