APPS.HR_CA_FF_UDFS dependencies on PER_ASSIGNMENTS_F

Line 222: FROM per_assignments_f ASG,

218: NVL(ASG.normal_hours, 0),
219: NVL(HRL.meaning, 'NOT ENTERED'),
220: NVL(HRL.lookup_code, 'NOT ENTERED'),
221: NVL(SCL.segment4, 'NOT ENTERED')
222: FROM per_assignments_f ASG,
223: per_assignment_status_types AST,
224: hr_soft_coding_keyflex SCL,
225: hr_lookups HRL
226: WHERE ASG.assignment_id = p_asst_id

Line 726: FROM per_assignments_f ASG,

722: FCL.lookup_code
723: INTO v_inpval_id,
724: v_pay_basis,
725: v_pay_basis_code
726: FROM per_assignments_f ASG,
727: per_pay_bases PYB,
728: hr_lookups FCL
729: WHERE FCL.lookup_code = PYB.pay_basis
730: AND FCL.lookup_type = 'PAY_BASIS'

Line 996: FROM per_assignments_f ASG,

992: select 1 INTO l_asg_info_changes
993: from dual
994: where exists (
995: SELECT 1
996: FROM per_assignments_f ASG,
997: per_assignment_status_types AST,
998: hr_soft_coding_keyflex SCL
999: WHERE ASG.assignment_id = p_asst_id
1000: AND ASG.effective_start_date <= p_period_start

Line 1076: FROM per_assignments_f ASG,

1072: select 1 INTO l_asg_info_changes
1073: from dual
1074: where exists (
1075: SELECT 1
1076: FROM per_assignments_f ASG,
1077: per_assignment_status_types AST,
1078: hr_soft_coding_keyflex SCL
1079: WHERE ASG.assignment_id = p_asst_id
1080: AND ASG.effective_start_date > p_period_start

Line 1199: FROM per_assignments_f ASG,

1195: IF l_proc_reg_sal <> 'Y' THEN
1196:
1197: SELECT AST.per_system_status
1198: INTO v_asg_status
1199: FROM per_assignments_f ASG,
1200: per_assignment_status_types AST,
1201: hr_soft_coding_keyflex SCL
1202: WHERE ASG.assignment_id = p_asst_id
1203: AND p_period_start BETWEEN ASG.effective_start_date

Line 1256: -- **are reflected in per_assignments_f**. Also need to know what other

1252: -- So the start date of the work info record w/the same tax unit must be less
1253: -- than or equal to the start date of the asst rec. That's all we have to
1254: -- check since a change to tax unit will cause date-effective update to asst.
1255: -- ^^^ Need to verify that tax-unit changes are date-effective and that they
1256: -- **are reflected in per_assignments_f**. Also need to know what other
1257: -- changes result in date-effective update to work_info tab and whether
1258: -- or not all changes date-effectively affect assignment. They SHOULD be
1259: -- reflected in asst since this would be consistent w/SCL keyflex behaviour.
1260: -- A: Yes they are. (13 May 1994 HParicha)

Line 1304: FROM per_assignments_f ASG,

1300: v_asst_std_hrs,
1301: v_asst_std_freq,
1302: v_asst_std_freq_code,
1303: v_work_schedule
1304: FROM per_assignments_f ASG,
1305: per_assignment_status_types AST,
1306: hr_soft_coding_keyflex SCL,
1307: hr_lookups HRL
1308: WHERE ASG.assignment_id = p_asst_id

Line 1424: per_assignments_f ASG,

1420: v_asst_std_freq_code,
1421: v_work_schedule
1422: FROM hr_soft_coding_keyflex SCL,
1423: per_assignment_status_types AST,
1424: per_assignments_f ASG,
1425: hr_lookups HRL
1426: WHERE ASG.assignment_id = p_asst_id
1427: AND ASG.business_group_id + 0 = p_bus_grp_id
1428: AND ASG.effective_start_date > p_period_start

Line 1557: FROM per_assignments_f ASG,

1553: v_asst_std_hrs,
1554: v_asst_std_freq,
1555: v_asst_std_freq_code,
1556: v_work_schedule
1557: FROM per_assignments_f ASG,
1558: per_assignment_status_types AST,
1559: hr_soft_coding_keyflex SCL,
1560: hr_lookups HRL
1561: WHERE ASG.assignment_id = p_asst_id

Line 1813: per_assignments_f ASG,

1809: v_asst_std_freq_code,
1810: v_work_schedule
1811: FROM hr_soft_coding_keyflex SCL,
1812: per_assignment_status_types AST,
1813: per_assignments_f ASG,
1814: hr_lookups HRL
1815: WHERE ASG.assignment_id = p_asst_id
1816: AND ASG.business_group_id + 0 = p_bus_grp_id
1817: AND ASG.effective_start_date > p_period_start