eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.HR_TERMINATION_SS dependencies on HR_EX_EMPLOYEE_API

Line 391: || hr_ex_employee_api.actual_termination_emp

387: ||---------------------------------------------------------------------------
388: ||
389: || Description:
390: || This procedure will call the actual API -
391: || hr_ex_employee_api.actual_termination_emp
392: ||
393: || Pre Conditions:
394: ||
395: || In Arguments:

Line 533: -- before calling hr_ex_employee_api.actual_termination_emp.

529:
530: -- Bug 2098595 Fix Begins: 12/03/2001
531: -- Need to switch the order of calling the api. We need to call
532: -- hr_termination_ss.update_pds_details first to set the flex segments
533: -- before calling hr_ex_employee_api.actual_termination_emp.
534: -- Otherwise, when there is a mandatory segment, we'll get an error
535: -- as follows:
536: -- The mandatory column Attribute??(also known as xxxx) has not been
537: -- assigned a value.

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

534: -- Otherwise, when there is a mandatory segment, we'll get an error
535: -- as follows:
536: -- The mandatory column Attribute??(also known as xxxx) has not been
537: -- assigned a value.
538: -- The reason is because in hr_ex_employee_api.actual_termination_emp,
539: -- it validates flex segments and there are no parameters to receive
540: -- flex segments in hr_ex_employee_api.actual_termination_emp. So, we
541: -- need to flip the order to set the value of flex segments.
542: -- Call update_pds_details;

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

536: -- The mandatory column Attribute??(also known as xxxx) has not been
537: -- assigned a value.
538: -- The reason is because in hr_ex_employee_api.actual_termination_emp,
539: -- it validates flex segments and there are no parameters to receive
540: -- flex segments in hr_ex_employee_api.actual_termination_emp. So, we
541: -- need to flip the order to set the value of flex segments.
542: -- Call update_pds_details;
543: --
544: -- Need to set a savepoint. Call update_pds_details and

Line 552: -- hr_ex_employee_api.actual_termination_emp.

548:
549: SAVEPOINT terminate_ee;
550: -- Set p_validate to false to commit the desc flex segments, especially
551: -- the mandatory segments to avoid the following error issued by
552: -- hr_ex_employee_api.actual_termination_emp.
553: -- The mandatory column Attribute??(also known as xxxx) has not been
554: -- assigned a value.
555:
556: --------------------------------------------------------------

Line 659: -- before calling "hr_ex_employee_api.actual_termination_emp"

655: );
656:
657: -- Fix for the bug 13846099 Starts
658: -- Moved this piece of code "update rehire" info
659: -- before calling "hr_ex_employee_api.actual_termination_emp"
660:
661:
662: -- Core HR API will not support update of field Rehire Recommendation
663: -- and Rehire Reason. Hence we make following call to Person API

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

677:
678: -- Fix for the bug 13846099 Ends
679:
680: -- Now actually call API
681: hr_utility.trace('Calling hr_ex_employee_api.actual_termination_emp ' || l_proc);
682:
683: hr_ex_employee_api.actual_termination_emp
684: (p_validate => false
685: ,p_effective_date => p_effective_date

Line 683: hr_ex_employee_api.actual_termination_emp

679:
680: -- Now actually call API
681: hr_utility.trace('Calling hr_ex_employee_api.actual_termination_emp ' || l_proc);
682:
683: hr_ex_employee_api.actual_termination_emp
684: (p_validate => false
685: ,p_effective_date => p_effective_date
686: ,p_period_of_service_id => p_period_of_service_id
687: ,p_object_version_number => p_object_version_number

Line 733: hr_ex_employee_api.final_process_emp(

729: l_final_process_date := p_final_process_date;
730:
731: IF l_final_process_date IS NOT NULL
732: THEN
733: hr_ex_employee_api.final_process_emp(
734: p_validate => false,
735: p_period_of_service_id => p_period_of_service_id,
736: p_object_version_number => p_object_version_number,
737: p_final_process_date => l_final_process_date,

Line 2037: -- before calling hr_ex_employee_api.actual_termination_emp.

2033:
2034: -- Bug 2098595 Fix Begins: 11/12/2001
2035: -- Need to switch the order of calling the api. We need to call
2036: -- hr_termination_ss.update_pds_details first to set the flex segments
2037: -- before calling hr_ex_employee_api.actual_termination_emp.
2038: -- Otherwise, when there is a mandatory segment, we'll get an error
2039: -- as follows:
2040: -- The mandatory column Attribute??(also known as xxxx) has not been
2041: -- assigned a value.

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

2038: -- Otherwise, when there is a mandatory segment, we'll get an error
2039: -- as follows:
2040: -- The mandatory column Attribute??(also known as xxxx) has not been
2041: -- assigned a value.
2042: -- The reason is because in hr_ex_employee_api.actual_termination_emp,
2043: -- it validates flex segments and there are no parameters to receive
2044: -- flex segments in hr_ex_employee_api.actual_termination_emp. So, we
2045: -- need to flip the order to set the value of flex segments.
2046: --

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

2040: -- The mandatory column Attribute??(also known as xxxx) has not been
2041: -- assigned a value.
2042: -- The reason is because in hr_ex_employee_api.actual_termination_emp,
2043: -- it validates flex segments and there are no parameters to receive
2044: -- flex segments in hr_ex_employee_api.actual_termination_emp. So, we
2045: -- need to flip the order to set the value of flex segments.
2046: --
2047: -- Call update_pds_details;
2048: hr_periods_of_service_api.update_pds_details (

Line 2116: -- before calling "hr_ex_employee_api.actual_termination_emp"

2112: -- Bug Fix 2089615 Ends
2113:
2114: -- Fix for the bug 13846099 Starts
2115: -- Moved this piece of code "update rehire" info
2116: -- before calling "hr_ex_employee_api.actual_termination_emp"
2117:
2118: -- Core HR API will not support update of field Rehire Recommendation
2119: -- and Rehire Reason. Hence we make following call to Person API
2120: -- to update the Fields.

Line 2132: hr_ex_employee_api.actual_termination_emp (

2128: );
2129:
2130: -- Fix for the bug 13846099 Ends
2131:
2132: hr_ex_employee_api.actual_termination_emp (
2133: p_validate => FALSE,
2134: p_effective_date => ld_actual_term_date,
2135: p_period_of_service_id => ln_period_of_service_id,
2136: p_object_version_number => ln_object_version_number,

Line 2163: hr_ex_employee_api.final_process_emp(

2159: l_entries_changed_warning := 'N';
2160:
2161: if ld_final_process_date is not null
2162: THEN
2163: hr_ex_employee_api.final_process_emp(
2164: p_validate => false,
2165: p_period_of_service_id => ln_period_of_service_id,
2166: p_object_version_number => ln_object_version_number,
2167: p_final_process_date => ld_final_process_date,