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 1045: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

1041: -- ii) Future dated proposals exist for this assignment.
1042: --
1043:
1044: IF p_flow_mode IS NOT NULL and
1045: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
1046: THEN
1047: hr_utility.set_location(l_proc,10);
1048: NULL;
1049: ELSE

Line 1091: p_flow_mode := hr_process_assignment_ss.g_hire_an_applicant;

1087: ln_payroll_id := null;
1088: p_old_pay_basis_id := null;
1089: lv_old_salary_basis_name := null;
1090: ln_old_pay_annual_factor := null;
1091: p_flow_mode := hr_process_assignment_ss.g_hire_an_applicant;
1092: END IF;
1093:
1094: -- Bug 2355929 Fix Ends
1095:

Line 1262: --HR_PROCESS_ASSIGNMENT_SS.PROCESS_API

1258:
1259: -- Must set the element warning to TRUE so that the ASG wrapper will not
1260: -- roll back the ASG changes if element_warning = 'TRUE' whenever there
1261: -- is element entries changed.
1262: --HR_PROCESS_ASSIGNMENT_SS.PROCESS_API
1263: -- (p_validate => FALSE
1264: -- ,p_transaction_step_id => ln_transaction_step_id
1265: -- ,p_flow_mode => p_flow_mode); -- 2355929 Fix
1266: -- Bug 2547283: need to update person info and asg info.

Line 1268: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration)

1264: -- ,p_transaction_step_id => ln_transaction_step_id
1265: -- ,p_flow_mode => p_flow_mode); -- 2355929 Fix
1266: -- Bug 2547283: need to update person info and asg info.
1267: IF NOT (p_flow_mode IS NOT NULL and
1268: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration)
1269: THEN
1270: hr_utility.set_location(l_proc,95);
1271: hr_new_user_reg_ss.process_selected_transaction
1272: (p_item_type => p_item_type,

Line 3971: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

3967: -- 04/24/02 Change Ends
3968:
3969: if(p_save_mode = 'SAVE_FOR_LATER') then
3970: if p_flow_mode is not null and
3971: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
3972: then
3973: hr_utility.set_location(l_proc,10);
3974: rollback;
3975: end if;

Line 4125: --HR_PROCESS_ASSIGNMENT_SS.PROCESS_API

4121:
4122: -- Must set the element warning to TRUE so that the ASG wrapper will
4123: -- not roll back the ASG changes if element_warning = 'TRUE' whenever
4124: -- there is element entries changed.
4125: --HR_PROCESS_ASSIGNMENT_SS.PROCESS_API
4126: -- (p_validate => FALSE
4127: -- ,p_transaction_step_id => ln_transaction_step_id
4128: -- ,p_flow_mode => p_flow_mode);
4129: -- Bug 2547283: need to update person info and asg info.

Line 4300: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

4296: -- request phase of the assignment page for the new user registration.
4297: -- The rollback is only for New Hire, not for Applicant Hire because
4298: -- there is no dummy person created in Applicant Hire in the txn.
4299: IF p_flow_mode is not null and
4300: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
4301: THEN
4302: hr_utility.set_location(l_proc,45);
4303: rollback;
4304: END IF;

Line 4339: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

4335: -- request phase of the assignment page for the new user registration.
4336: -- The rollback is only for New Hire, not for Applicant Hire because
4337: -- there is no dummy person created in Applicant Hire in the txn.
4338: IF p_flow_mode is not null and
4339: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
4340: THEN
4341: rollback;
4342: END IF;
4343: --end registration

Line 4363: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

4359: -- The rollback is only for New Hire, not for Applicant Hire because
4360: -- there is no dummy person created in Applicant Hire in the txn.
4361:
4362: IF p_flow_mode is not null and
4363: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
4364: THEN
4365: rollback;
4366: END IF;
4367: --end registration

Line 4385: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration

4381: -- The rollback is only for New Hire, not for Applicant Hire because
4382: -- there is no dummy person created in Applicant Hire in the txn.
4383:
4384: IF p_flow_mode is not null and
4385: p_flow_mode = hr_process_assignment_ss.g_new_hire_registration
4386: THEN
4387: rollback;
4388: END IF;
4389: --end registration

Line 6092: hr_process_assignment_ss.g_date_format);

6088: -- of a Save For Later transaction and the user has changed the date. We
6089: -- should use the l_effective_date which is set to either the input parm
6090: -- p_effective_date value or the WF effective date.
6091: ld_date := to_date(l_effective_date,
6092: hr_process_assignment_ss.g_date_format);
6093:
6094: PER_PAY_PROPOSALS_POPULATE.get_element_id
6095: (p_assignment_id => ltt_salary_data(1).assignment_id
6096: ,p_business_group_id => ltt_salary_data(1).business_group_id