APPS.GHR_CORR_CANC_SF52 dependencies on PAY_INPUT_VALUES_F

Line 4101: FROM PAY_INPUT_VALUES_F IPV

4097: ,cp_eff_date in date
4098: ,p_bg_id in NUMBER)
4099: IS
4100: SELECT IPV.NAME
4101: FROM PAY_INPUT_VALUES_F IPV
4102: WHERE TRUNC(cp_eff_date)
4103: BETWEEN IPV.EFFECTIVE_START_DATE AND IPV.EFFECTIVE_END_DATE
4104: AND IPV.INPUT_VALUE_ID = cp_input_value_id;
4105: -- AND (IPV.BUSINESS_GROUP_ID IS NULL OR IPV.BUSINESS_GROUP_ID=P_BG_ID);

Line 4142: l_ipv_name pay_input_values_f.name%type;

4138: AND INFORMATION3 = cp_information3
4139: AND TABLE_NAME = cp_table_name
4140: ORDER BY PROCESS_DATE DESC; -- Line Added by ENUNEZ (04/11/2000) bug# 1235958
4141:
4142: l_ipv_name pay_input_values_f.name%type;
4143: l_element_name pay_element_types_f.element_name%type;
4144: l_proc_warn boolean;
4145: l_proc varchar2(30):='update_eleentval';
4146: l_eff_date date;

Line 4156: pay_input_values_f ipv

4152: ,eff_date in date
4153: ,p_bg_id in number) is
4154: select ipv.uom
4155: from pay_element_types_f elt,
4156: pay_input_values_f ipv
4157: where trunc(eff_date) between elt.effective_start_date
4158: and elt.effective_end_date
4159: and trunc(eff_date) between ipv.effective_start_date
4160: and ipv.effective_end_date