APPS.HR_ELEMENTS dependencies on HR_INPUT_VALUES

Line 667: hr_input_values.chk_del_input_values(p_mode,

663: --
664: if g_debug then
665: hr_utility.trace(to_char(iv_rec.input_value_id));
666: end if;
667: hr_input_values.chk_del_input_values(p_mode,
668: p_val_start_date,
669: p_val_end_date,
670: iv_rec.input_value_id);
671: end loop;

Line 795: l_pay_value_name := hr_input_values.get_pay_value_name

791: hr_utility.set_location('hr_elements.ins_input_value', 2);
792: end if;
793: --
794: -- Obtain Pay value name from hr_lookups
795: l_pay_value_name := hr_input_values.get_pay_value_name
796: (p_legislation_code);
797: --
798: c_user_id := fnd_global.user_id;
799: c_login_id := fnd_global.login_id;

Line 1302: procedure relies on the hr_input_values.del_3p_input_values being called

1298: related balance feeds.
1299: NOTES
1300: Element types cannot be subject to a future change delete. They can, however,
1301: be subject to a next change delete and this is handled in the code. This
1302: procedure relies on the hr_input_values.del_3p_input_values being called
1303: in the same commit unit as this will tidy up the balance feeds that may have
1304: been created by the sub_classification rules.
1305: */
1306: --

Line 1441: hr_input_values.del_3p_input_values(p_delete_mode,

1437: for iv_rec in c_input_value(p_element_type_id,
1438: p_val_start_date,
1439: p_val_end_date) loop
1440: --
1441: hr_input_values.del_3p_input_values(p_delete_mode,
1442: iv_rec.input_value_id,
1443: iv_rec.db_items_flag,
1444: p_val_end_date,
1445: p_val_session_date,