APPS.HR_PAY_RATE_SS dependencies on HR_PROCESS_ASSIGNMENT_SS

Line 27: default 'HR_PROCESS_ASSIGNMENT_SS.PROCESS_API';

23: p_trans_rec_count INTEGER;
24: g_data_error exception;
25: g_exceeded_grade_range exception;
26: g_asg_api_name constant varchar2(80)
27: default 'HR_PROCESS_ASSIGNMENT_SS.PROCESS_API';
28: -- 04/12/02 Salary Basis Enhancement Change Begins
29: g_mid_pay_period_change constant varchar2(30) := 'HR_MID_PAY_PERIOD_CHANGE';
30:
31: function check_ele_eligibility(p_asg_id in number,

Line 734: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

730:
731: -- Read from the database to determine if there is an existing
732: -- assignment and also grade ladder assignment.
733: IF p_flow_mode IS NOT NULL and
734: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
735: THEN
736: hr_utility.set_location(l_proc,10);
737: NULL;
738: ELSE

Line 756: --p_flow_mode := hr_process_assignment_ss.g_hire_an_applicant;

752: THEN
753: hr_utility.set_location(l_proc,25);
754: -- zap the p_old_grade_ladder_pgm_id
755: p_old_grade_ladder_id := null;
756: --p_flow_mode := hr_process_assignment_ss.g_hire_an_applicant;
757: END IF;
758:
759: IF p_asg_txn_step_id IS NOT NULL
760: THEN

Line 1068: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

1064: -- ii) Future dated proposals exist for this assignment.
1065: --
1066:
1067: IF p_flow_mode IS NOT NULL and
1068: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
1069: THEN
1070: hr_utility.set_location(l_proc,10);
1071: NULL;
1072: ELSE

Line 1118: p_flow_mode := hr_process_assignment_ss.g_hire_an_applicant;

1114: p_old_pay_basis_id := null;
1115: lv_old_salary_basis_name := null;
1116: ln_old_pay_annual_factor := null;
1117: ln_old_fte_factor := null;
1118: p_flow_mode := hr_process_assignment_ss.g_hire_an_applicant;
1119: END IF;
1120:
1121: -- Bug 2355929 Fix Ends
1122:

Line 1304: --HR_PROCESS_ASSIGNMENT_SS.PROCESS_API

1300:
1301: -- Must set the element warning to TRUE so that the ASG wrapper will not
1302: -- roll back the ASG changes if element_warning = 'TRUE' whenever there
1303: -- is element entries changed.
1304: --HR_PROCESS_ASSIGNMENT_SS.PROCESS_API
1305: -- (p_validate => FALSE
1306: -- ,p_transaction_step_id => ln_transaction_step_id
1307: -- ,p_flow_mode => p_flow_mode); -- 2355929 Fix
1308: -- Bug 2547283: need to update person info and asg info.

Line 1310: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration)

1306: -- ,p_transaction_step_id => ln_transaction_step_id
1307: -- ,p_flow_mode => p_flow_mode); -- 2355929 Fix
1308: -- Bug 2547283: need to update person info and asg info.
1309: IF NOT (p_flow_mode IS NOT NULL and
1310: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration)
1311: THEN
1312: hr_utility.set_location(l_proc,95);
1313: if p_proc_sel_txn is null then
1314: hr_new_user_reg_ss.process_selected_transaction

Line 4130: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

4126: -- 04/24/02 Change Ends
4127:
4128: if(p_save_mode = 'SAVE_FOR_LATER') then
4129: if p_flow_mode is not null and
4130: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
4131: then
4132: hr_utility.set_location(l_proc,10);
4133: rollback;
4134: end if;

Line 4284: --HR_PROCESS_ASSIGNMENT_SS.PROCESS_API

4280:
4281: -- Must set the element warning to TRUE so that the ASG wrapper will
4282: -- not roll back the ASG changes if element_warning = 'TRUE' whenever
4283: -- there is element entries changed.
4284: --HR_PROCESS_ASSIGNMENT_SS.PROCESS_API
4285: -- (p_validate => FALSE
4286: -- ,p_transaction_step_id => ln_transaction_step_id
4287: -- ,p_flow_mode => p_flow_mode);
4288: -- Bug 2547283: need to update person info and asg info.

Line 4461: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

4457: -- request phase of the assignment page for the new user registration.
4458: -- The rollback is only for New Hire, not for Applicant Hire because
4459: -- there is no dummy person created in Applicant Hire in the txn.
4460: IF p_flow_mode is not null and
4461: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
4462: THEN
4463: hr_utility.set_location(l_proc,45);
4464: rollback;
4465: END IF;

Line 4500: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

4496: -- request phase of the assignment page for the new user registration.
4497: -- The rollback is only for New Hire, not for Applicant Hire because
4498: -- there is no dummy person created in Applicant Hire in the txn.
4499: IF p_flow_mode is not null and
4500: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
4501: THEN
4502: rollback;
4503: END IF;
4504: --end registration

Line 4524: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

4520: -- The rollback is only for New Hire, not for Applicant Hire because
4521: -- there is no dummy person created in Applicant Hire in the txn.
4522:
4523: IF p_flow_mode is not null and
4524: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
4525: THEN
4526: rollback;
4527: END IF;
4528: --end registration

Line 4546: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

4542: -- The rollback is only for New Hire, not for Applicant Hire because
4543: -- there is no dummy person created in Applicant Hire in the txn.
4544:
4545: IF p_flow_mode is not null and
4546: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
4547: THEN
4548: rollback;
4549: END IF;
4550: --end registration

Line 6394: hr_process_assignment_ss.g_date_format);

6390: -- of a Save For Later transaction and the user has changed the date. We
6391: -- should use the l_effective_date which is set to either the input parm
6392: -- p_effective_date value or the WF effective date.
6393: ld_date := to_date(l_effective_date,
6394: hr_process_assignment_ss.g_date_format);
6395:
6396: PER_PAY_PROPOSALS_POPULATE.get_element_id
6397: (p_assignment_id => ltt_salary_data(1).assignment_id
6398: ,p_business_group_id => ltt_salary_data(1).business_group_id