Fusion Global HR: Duplicate Assignment Number Detection During Convert Pending Worker Action
(Doc ID 2993426.1)
Last updated on DECEMBER 15, 2023
Applies to:
Oracle Fusion Global Human Resources Cloud Service - Version 11.13.23.10.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
----------------------
During the conversion of pending workers via Responsive UI action, the system does not validate assignment number duplication, thus permitting users to create multiple employees/contingent workers with the same assignment number.
When trying to perform any further actions for a worker that was converted, the duplicate assignment number error is showing, not allowing to submit the transaction.
EXPECTED BEHAVIOR
-----------------------
Each assignment must have a unique Assignment Number.
The application should throw the error, as the assignment number already exists:
STEPS
-----------------------
1. Hire an employee with person number e.g. 123. Auto-generated assignment number will be E123.
2. Correct the hire record and change the assignment number to E123-2.
3. Add a pending worker work relationship for the same person. For this, the assignment number will be P123.
4. Convert the pending worker. Do not touch the assignment number field. Assignment number will be auto generated for converted employee assignment and will be E123-2 (as this is the second employee assignment of the person).
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |