APPS.HR_ENTRY_API dependencies on PAY_DYT_ELEMENT_ENTRY_VAL_PKG

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

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

Line 4190: PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_insert

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

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

6883: begin
6884: g_counter := g_counter + 1;
6885: --
6886: if g_debug then
6887: hr_utility.trace(' Hard call PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_update');
6888: hr_utility.trace(' Ele ent Val ID: '||new_vals.element_entry_value_id);
6889: hr_utility.trace(' New Screen Val: '||new_vals.screen_entry_value);
6890: hr_utility.trace(' Old Screen Val: '||l_old_val_tab(g_counter).screen_entry_value);
6891: end if;

Line 6893: PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_update

6889: hr_utility.trace(' New Screen Val: '||new_vals.screen_entry_value);
6890: hr_utility.trace(' Old Screen Val: '||l_old_val_tab(g_counter).screen_entry_value);
6891: end if;
6892:
6893: PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_update
6894: (
6895: P_EFFECTIVE_END_DATE => new_vals.effective_end_date
6896: ,P_EFFECTIVE_START_DATE => new_vals.effective_start_date
6897: ,P_ELEMENT_ENTRY_ID => new_vals.element_entry_id

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

8960: -- for element entries vals have been made for after insert and after update. At this
8961: -- time after delete will not be made as CC does not require it. At a future
8962: -- juncture this can be added, methodology....
8963: -- 1) Before delete of eev above, create cache of values
8964: -- 2) Now make a call to PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_delete
8965: -- -use current values if end dated or nulls if row has been blown away
8966: --
8967: if g_debug then
8968: hr_utility.trace(' NO Hard call PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_delete');

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

8964: -- 2) Now make a call to PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_delete
8965: -- -use current values if end dated or nulls if row has been blown away
8966: --
8967: if g_debug then
8968: hr_utility.trace(' NO Hard call PAY_DYT_ELEMENT_ENTRY_VAL_PKG.after_delete');
8969: hr_utility.set_location('Leaving: delete_element_entry', 900);
8970: end if;
8971:
8972: end delete_element_entry;