Last updated on JUNE 15, 2016
Applies to:Oracle Fusion Global Human Resources Cloud Service - Version 220.127.116.11.0 and later
Oracle Fusion Global Human Resources - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Global Human Resources
Legal Entity A started implementing in co-existence model and hence employee number generation set as Manual.
Till 31-Dec-2015 they were running in co-existence model and then switched over to Fusion HCM.
There are around 10-15 employees to be entered manually after go-live.
HR starts entering and forgets to change date to enter employee number manually.
HR selects Legal Entity and number sets to generate automatically.
HR goes back and changes effective hire date again but due to this bug number still set as automatic.
Now assume HR out of ignorance completes the cycle till submission and number is not synchronized with Legacy System.
Moreover practicality of the case, User have to emphasize on system accuracy. Even if chances of scenario occurring could be 1 in 1000 but system has to be accurate even for that one case.
For the point 3 if it always considers active setting then agree but Oracle provides flexibility based on date it is just the Order of event which Oracle screen is not understanding.
But it does consider Hire Date if selected in expected order and hence the point of hire date not being considered does not stand valid.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms