APPS.GHR_CORR_CANC_SF52 dependencies on PAY_INPUT_VALUES_F

Line 3793: FROM PAY_INPUT_VALUES_F IPV

3789: ,cp_eff_date in date
3790: ,p_bg_id in NUMBER)
3791: IS
3792: SELECT IPV.NAME
3793: FROM PAY_INPUT_VALUES_F IPV
3794: WHERE TRUNC(cp_eff_date)
3795: BETWEEN IPV.EFFECTIVE_START_DATE AND IPV.EFFECTIVE_END_DATE
3796: AND IPV.INPUT_VALUE_ID = cp_input_value_id;
3797: -- AND (IPV.BUSINESS_GROUP_ID IS NULL OR IPV.BUSINESS_GROUP_ID=P_BG_ID);

Line 3834: l_ipv_name pay_input_values_f.name%type;

3830: AND INFORMATION3 = cp_information3
3831: AND TABLE_NAME = cp_table_name
3832: ORDER BY PROCESS_DATE DESC; -- Line Added by ENUNEZ (04/11/2000) bug# 1235958
3833:
3834: l_ipv_name pay_input_values_f.name%type;
3835: l_element_name pay_element_types_f.element_name%type;
3836: l_proc_warn boolean;
3837: l_proc varchar2(30):='update_eleentval';
3838: l_eff_date date;

Line 3848: pay_input_values_f ipv

3844: ,eff_date in date
3845: ,p_bg_id in number) is
3846: select ipv.uom
3847: from pay_element_types_f elt,
3848: pay_input_values_f ipv
3849: where trunc(eff_date) between elt.effective_start_date
3850: and elt.effective_end_date
3851: and trunc(eff_date) between ipv.effective_start_date
3852: and ipv.effective_end_date