To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Seniority Date Issue
Summary:
Seniority Date Issue
Content (required):
Seniority Date Issue
Hi Team,
Greetings!
We have a requirement to have a given seniority date applicable only for full-time population i.e. it will be 01/01/1900 for non full-time population.
We have below check included, but still the seniority date is getting marked with the different date for the employee -
if l_curr_asg_category <> 'XX_HR_01_FULL_TIME' then
(
l_default = to_date('1900/01/01','YYYY/MM/DD')
EFF_DATE = l_default
SENIORITY_ADJUST_IN_DAYS = (days_between(EFF_DATE,l_default))
seniority_adjust_comment = 'Default to 1/1/1900 - Adjustment done'
log = ess_log_write ('[KR_BDCS_DT] 4 seniority_adjust_in_days => '+ to_char(seniority_adjust_in_days))