DBA Data[Home] [Help]

APPS.PAY_CA_GROUP_LEVEL_BAL_PKG dependencies on DUAL

Line 944: FROM SYS.DUAL

940: p_def_bal_id NUMBER,
941: p_start_date DATE,
942: p_end_date DATE) IS
943: SELECT 'X'
944: FROM SYS.DUAL
945: WHERE EXISTS (SELECT 'X'
946: FROM pay_payroll_actions pya,
947: pay_assignment_actions asa,
948: pay_assignment_latest_balances alb

Line 1487: FROM SYS.DUAL

1483: p_def_bal_id NUMBER,
1484: p_start_date DATE,
1485: p_end_date DATE) IS
1486: SELECT 'X'
1487: FROM SYS.DUAL
1488: WHERE EXISTS (SELECT 'X'
1489: FROM pay_payroll_actions pya,
1490: pay_assignment_actions asa,
1491: pay_assignment_latest_balances alb

Line 2453: * must sum up all the relevant individual assignment action balance

2449: p_effective_date);
2450: ELSE
2451: /*
2452: * At least one of the balance parameters is not a context so we
2453: * must sum up all the relevant individual assignment action balance
2454: * values
2455: * We will will use the _ASG_GRE_RUN route since it is faster than
2456: * _ASG_GRE_PYDATE. Note the _ASG_GRE_PYDATE balance only sums values
2457: * on the specified date, not over a date range because of the link to

Line 3016: * must sum up all the relevant individual assignment action balance

3012: hr_utility.trace('l_balance_value :'||to_char(l_balance_value));
3013: ELSE
3014: /*
3015: * At least one of the balance parameters is not a context so we
3016: * must sum up all the relevant individual assignment action balance
3017: * values
3018: * We will will use the _ASG_GRE_RUN route since it is faster than
3019: * _ASG_GRE_PYDATE. Note the _ASG_GRE_PYDATE balance only sums values
3020: * on the specified date, not over a date range because of the link to