APPS.HR_TERMINATION_SS dependencies on HR_EX_EMPLOYEE_API

Line 343: || hr_ex_employee_api.actual_termination_emp

339: ||---------------------------------------------------------------------------
340: ||
341: || Description:
342: || This procedure will call the actual API -
343: || hr_ex_employee_api.actual_termination_emp
344: ||
345: || Pre Conditions:
346: ||
347: || In Arguments:

Line 485: -- before calling hr_ex_employee_api.actual_termination_emp.

481:
482: -- Bug 2098595 Fix Begins: 12/03/2001
483: -- Need to switch the order of calling the api. We need to call
484: -- hr_termination_ss.update_pds_details first to set the flex segments
485: -- before calling hr_ex_employee_api.actual_termination_emp.
486: -- Otherwise, when there is a mandatory segment, we'll get an error
487: -- as follows:
488: -- The mandatory column Attribute??(also known as xxxx) has not been
489: -- assigned a value.

Line 490: -- The reason is because in hr_ex_employee_api.actual_termination_emp,

486: -- Otherwise, when there is a mandatory segment, we'll get an error
487: -- as follows:
488: -- The mandatory column Attribute??(also known as xxxx) has not been
489: -- assigned a value.
490: -- The reason is because in hr_ex_employee_api.actual_termination_emp,
491: -- it validates flex segments and there are no parameters to receive
492: -- flex segments in hr_ex_employee_api.actual_termination_emp. So, we
493: -- need to flip the order to set the value of flex segments.
494: -- Call update_pds_details;

Line 492: -- flex segments in hr_ex_employee_api.actual_termination_emp. So, we

488: -- The mandatory column Attribute??(also known as xxxx) has not been
489: -- assigned a value.
490: -- The reason is because in hr_ex_employee_api.actual_termination_emp,
491: -- it validates flex segments and there are no parameters to receive
492: -- flex segments in hr_ex_employee_api.actual_termination_emp. So, we
493: -- need to flip the order to set the value of flex segments.
494: -- Call update_pds_details;
495: --
496: -- Need to set a savepoint. Call update_pds_details and

Line 504: -- hr_ex_employee_api.actual_termination_emp.

500:
501: SAVEPOINT terminate_ee;
502: -- Set p_validate to false to commit the desc flex segments, especially
503: -- the mandatory segments to avoid the following error issued by
504: -- hr_ex_employee_api.actual_termination_emp.
505: -- The mandatory column Attribute??(also known as xxxx) has not been
506: -- assigned a value.
507:
508: --------------------------------------------------------------

Line 611: hr_utility.trace('Calling hr_ex_employee_api.actual_termination_emp ' || l_proc);

607: );
608:
609:
610: -- Now actually call API
611: hr_utility.trace('Calling hr_ex_employee_api.actual_termination_emp ' || l_proc);
612:
613: hr_ex_employee_api.actual_termination_emp
614: (p_validate => false
615: ,p_effective_date => p_effective_date

Line 613: hr_ex_employee_api.actual_termination_emp

609:
610: -- Now actually call API
611: hr_utility.trace('Calling hr_ex_employee_api.actual_termination_emp ' || l_proc);
612:
613: hr_ex_employee_api.actual_termination_emp
614: (p_validate => false
615: ,p_effective_date => p_effective_date
616: ,p_period_of_service_id => p_period_of_service_id
617: ,p_object_version_number => p_object_version_number

Line 675: hr_ex_employee_api.final_process_emp(

671: l_final_process_date := p_final_process_date;
672:
673: IF l_final_process_date IS NOT NULL
674: THEN
675: hr_ex_employee_api.final_process_emp(
676: p_validate => false,
677: p_period_of_service_id => p_period_of_service_id,
678: p_object_version_number => p_object_version_number,
679: p_final_process_date => l_final_process_date,

Line 1896: -- before calling hr_ex_employee_api.actual_termination_emp.

1892:
1893: -- Bug 2098595 Fix Begins: 11/12/2001
1894: -- Need to switch the order of calling the api. We need to call
1895: -- hr_termination_ss.update_pds_details first to set the flex segments
1896: -- before calling hr_ex_employee_api.actual_termination_emp.
1897: -- Otherwise, when there is a mandatory segment, we'll get an error
1898: -- as follows:
1899: -- The mandatory column Attribute??(also known as xxxx) has not been
1900: -- assigned a value.

Line 1901: -- The reason is because in hr_ex_employee_api.actual_termination_emp,

1897: -- Otherwise, when there is a mandatory segment, we'll get an error
1898: -- as follows:
1899: -- The mandatory column Attribute??(also known as xxxx) has not been
1900: -- assigned a value.
1901: -- The reason is because in hr_ex_employee_api.actual_termination_emp,
1902: -- it validates flex segments and there are no parameters to receive
1903: -- flex segments in hr_ex_employee_api.actual_termination_emp. So, we
1904: -- need to flip the order to set the value of flex segments.
1905: --

Line 1903: -- flex segments in hr_ex_employee_api.actual_termination_emp. So, we

1899: -- The mandatory column Attribute??(also known as xxxx) has not been
1900: -- assigned a value.
1901: -- The reason is because in hr_ex_employee_api.actual_termination_emp,
1902: -- it validates flex segments and there are no parameters to receive
1903: -- flex segments in hr_ex_employee_api.actual_termination_emp. So, we
1904: -- need to flip the order to set the value of flex segments.
1905: --
1906: -- Call update_pds_details;
1907: hr_periods_of_service_api.update_pds_details (

Line 1973: hr_ex_employee_api.actual_termination_emp (

1969: );
1970:
1971: -- Bug Fix 2089615 Ends
1972:
1973: hr_ex_employee_api.actual_termination_emp (
1974: p_validate => FALSE,
1975: p_effective_date => ld_actual_term_date,
1976: p_period_of_service_id => ln_period_of_service_id,
1977: p_object_version_number => ln_object_version_number,

Line 2015: hr_ex_employee_api.final_process_emp(

2011: l_entries_changed_warning := 'N';
2012:
2013: if ld_final_process_date is not null
2014: THEN
2015: hr_ex_employee_api.final_process_emp(
2016: p_validate => false,
2017: p_period_of_service_id => ln_period_of_service_id,
2018: p_object_version_number => ln_object_version_number,
2019: p_final_process_date => ld_final_process_date,