End-dating Position Using HR_POSITION_API.UPDATE_POSITION is Creating More Records.
(Doc ID 3036928.1)
Last updated on JULY 24, 2024
Applies to:
Oracle Human Resources - Version 12.2.10 and laterInformation in this document applies to any platform.
Symptoms
PROBLEM STATEMENT
Observed that, Position is not getting end-dated.
The issue can be reproduced at will with the following steps:
1. Login to Database.
2. Execute "hr_position_api.update_position" API as below.
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
3. Before executing this script, the position records were like this.
POSITION_ID | EFFECTIVE_START_DATE | EFFECTIVE_END_DATE |
100 | 21-MAR-2024 | 10-MAY-2024 |
100 | 11-MAY-2024 | 31-DEC-4712 |
4. After the script was executed, the position records are looking like this.
POSITION_ID | EFFECTIVE_START_DATE | EFFECTIVE_END_DATE |
100 | 21-MAR-2024 | 10-MAY-2024 |
100 | 11-MAY-2024 | 31-DEC-4712 |
100 | 01-JUN-2024 | 31-DEC-4712 |
5. User's expectation is that the Position should get end dated and new record should NOT get created.
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 |
Cause |
Solution |
References |