APPS.PAY_SUB_CLASS_RULES_PKG dependencies on PAY_SUB_CLASSIFICATION_RULES_F

Line 29: from pay_sub_classification_rules_f

25: p_Creation_Date DATE) IS
26:
27: cursor csr_new_rowid is
28: select rowid
29: from pay_sub_classification_rules_f
30: where sub_classification_rule_id = p_sub_classification_rule_id
31: and effective_start_date = p_effective_start_date;
32:
33:

Line 49: insert into pay_sub_classification_rules_f(

45: close csr_next_id;
46: end if;
47:
48: hr_utility.set_location ('PAY_SUB_CLASS_RULES_PKG.INSERT_ROW',2);
49: insert into pay_sub_classification_rules_f(
50:
51: sub_classification_rule_id,
52: effective_start_date,
53: effective_end_date,

Line 141: from pay_sub_classification_rules_f

137: p_Legislation_Code VARCHAR2) IS
138:
139: cursor csr_existing_row is
140: select *
141: from pay_sub_classification_rules_f
142: where rowid = p_rowid
143: for update of sub_classification_rule_id NOWAIT;
144:
145: fetched_record csr_existing_row%rowtype;

Line 200: UPDATE pay_sub_classification_rules_f

196: p_Last_Update_Date DATE,
197: p_Last_Updated_By NUMBER,
198: p_Last_Update_Login NUMBER) IS
199: BEGIN
200: UPDATE pay_sub_classification_rules_f
201: SET
202:
203: sub_classification_rule_id = p_Sub_Classification_Rule_Id,
204: effective_start_date = p_Effective_Start_Date,

Line 306: from pay_sub_classification_rules_f

302: v_end_date date;
303: --
304: cursor csr_end_date is
305: select min(effective_start_date) -1
306: from pay_sub_classification_rules_f
307: where element_type_id = p_element_type_id
308: and classification_id = p_classification_id
309: and effective_end_date > p_session_date;
310: --

Line 406: delete from pay_sub_classification_rules_f

402: p_validation_end_date );
403: --
404: -- Delete row from base table
405: --
406: delete from pay_sub_classification_rules_f
407: where rowid = p_rowid;
408: --
409: if sql%notfound then -- system error trap
410: hr_utility.set_message (801,'HR_6153_ALL_PROCEDURE_FAIL');

Line 447: select rowid,pay_sub_classification_rules_f.*

443: -- the parent being deleted. The parent name identifies foreign key column
444: -- to use, thus the procedure is generic to any parent deletion
445: --
446: cursor csr_rows_owned_by_parent is
447: select rowid,pay_sub_classification_rules_f.*
448: from pay_sub_classification_rules_f
449: where p_parent_id = decode (p_parent_name,
450: 'PAY_ELEMENT_TYPES_F',element_type_id,
451: classification_id)

Line 448: from pay_sub_classification_rules_f

444: -- to use, thus the procedure is generic to any parent deletion
445: --
446: cursor csr_rows_owned_by_parent is
447: select rowid,pay_sub_classification_rules_f.*
448: from pay_sub_classification_rules_f
449: where p_parent_id = decode (p_parent_name,
450: 'PAY_ELEMENT_TYPES_F',element_type_id,
451: classification_id)
452: for update;

Line 482: update pay_sub_classification_rules_f

478: elsif p_delete_mode = 'DELETE'
479: and p_session_date between fetched_rule.effective_start_date
480: and fetched_rule.effective_end_date then
481: --
482: update pay_sub_classification_rules_f
483: set effective_end_date = p_session_date
484: where current of csr_rows_owned_by_parent;
485: --
486: -- Fix for bug 3660866.

Line 491: update pay_sub_classification_rules_f

487: -- If parent is deleted in DELETE_NEXT_CHANGE or FUTURE_CHANGE mode
488: -- then all child rows (Secondary balance classification) should
489: -- also be updated as per same.
490: elsif (p_delete_mode in ('DELETE_NEXT_CHANGE','FUTURE_CHANGE')) then
491: update pay_sub_classification_rules_f
492: set effective_end_date = p_validation_end_date
493: where current of csr_rows_owned_by_parent;
494: --
495: end if;