PROJECTED ASSIGNMENT END GETS SET TO 01-JAN-2012 AUTOMATICALLY
Last updated on JULY 25, 2016
Applies to:Oracle Human Resources - Version 12.1.1 to 12.1 HRMS RUP4 [Release 12.1]
Information in this document applies to any platform.
On 12.1.1, When using HR_ASSIGNMENT_API.UPDATE_US_EMP_ASG to update assignments information, projected_assignment_end field is getting updated automatically with 01-Jan-2012.
Expect projected_assignment_end field not to get updated automatically with 01-Jan-2012 value
-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Call hr_assignment_api.update_us_emp_asg to update assignments info
The Package version "peasgapi.pkb"
Header: peasgapi.pkh 120.11.12010000.3 2008/11/06 13:11:19 brsinha ship
-- Business Impact:
The issue has the following business impact:
Due to this issue, users cannot use the API to update employee assignment information
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