APPS.HR_ENTRY_API dependencies on PAY_DYT_ELEMENT_ENTRY_VAL_PKG

Line 4185: hr_utility.trace(' Hard call PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_insert');

4181: for new_vals in pay_ele_shd.csr_get_eevals(p_element_entry_id,l_effective_date) loop
4182: begin
4183: --
4184: if g_debug then
4185: hr_utility.trace(' Hard call PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_insert');
4186: hr_utility.trace(' Ele ent Val ID: '||new_vals.element_entry_value_id);
4187: hr_utility.trace(' New Screen Val: '||new_vals.screen_entry_value);
4188: end if;
4189:

Line 4193: PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_insert

4189:
4190: -- Reason Insert has seemingly irregular parameters is that as
4191: -- element entry values has no hook packages, the generator util of the called
4192: -- pkg, will use an alternate param gen method and defaults lots eg _o
4193: PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_insert
4194: (
4195: P_EFFECTIVE_END_DATE => new_vals.effective_end_date
4196: ,P_EFFECTIVE_START_DATE => new_vals.effective_start_date
4197: ,P_ELEMENT_ENTRY_ID => new_vals.element_entry_id

Line 6903: hr_utility.trace(' Hard call PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_update');

6899: begin
6900: g_counter := g_counter + 1;
6901: --
6902: if g_debug then
6903: hr_utility.trace(' Hard call PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_update');
6904: hr_utility.trace(' Ele ent Val ID: '||new_vals.element_entry_value_id);
6905: hr_utility.trace(' New Screen Val: '||new_vals.screen_entry_value);
6906: hr_utility.trace(' Old Screen Val: '||l_old_val_tab(g_counter).screen_entry_value);
6907: end if;

Line 6909: PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_update

6905: hr_utility.trace(' New Screen Val: '||new_vals.screen_entry_value);
6906: hr_utility.trace(' Old Screen Val: '||l_old_val_tab(g_counter).screen_entry_value);
6907: end if;
6908:
6909: PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_update
6910: (
6911: P_EFFECTIVE_END_DATE => new_vals.effective_end_date
6912: ,P_EFFECTIVE_START_DATE => new_vals.effective_start_date
6913: ,P_ELEMENT_ENTRY_ID => new_vals.element_entry_id

Line 9035: -- 2) Now make a call to PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_delete

9031: -- for element entries vals have been made for after insert and after update. At this
9032: -- time after delete will not be made as CC does not require it. At a future
9033: -- juncture this can be added, methodology....
9034: -- 1) Before delete of eev above, create cache of values
9035: -- 2) Now make a call to PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_delete
9036: -- -use current values if end dated or nulls if row has been blown away
9037: --
9038: if g_debug then
9039: hr_utility.trace(' NO Hard call PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_delete');

Line 9039: hr_utility.trace(' NO Hard call PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_delete');

9035: -- 2) Now make a call to PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_delete
9036: -- -use current values if end dated or nulls if row has been blown away
9037: --
9038: if g_debug then
9039: hr_utility.trace(' NO Hard call PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_delete');
9040: hr_utility.set_location('Leaving: delete_element_entry', 900);
9041: end if;
9042:
9043: end delete_element_entry;