APPS.HR_CA_FF_UDFS dependencies on PER_ASSIGNMENTS_F

Line 216: FROM per_assignments_f ASG,

212: NVL(ASG.normal_hours, 0),
213: NVL(HRL.meaning, 'NOT ENTERED'),
214: NVL(HRL.lookup_code, 'NOT ENTERED'),
215: NVL(SCL.segment4, 'NOT ENTERED')
216: FROM per_assignments_f ASG,
217: per_assignment_status_types AST,
218: hr_soft_coding_keyflex SCL,
219: hr_lookups HRL
220: WHERE ASG.assignment_id = p_asst_id

Line 720: FROM per_assignments_f ASG,

716: FCL.lookup_code
717: INTO v_inpval_id,
718: v_pay_basis,
719: v_pay_basis_code
720: FROM per_assignments_f ASG,
721: per_pay_bases PYB,
722: hr_lookups FCL
723: WHERE FCL.lookup_code = PYB.pay_basis
724: AND FCL.lookup_type = 'PAY_BASIS'

Line 990: FROM per_assignments_f ASG,

986: select 1 INTO l_asg_info_changes
987: from dual
988: where exists (
989: SELECT 1
990: FROM per_assignments_f ASG,
991: per_assignment_status_types AST,
992: hr_soft_coding_keyflex SCL
993: WHERE ASG.assignment_id = p_asst_id
994: AND ASG.effective_start_date <= p_period_start

Line 1070: FROM per_assignments_f ASG,

1066: select 1 INTO l_asg_info_changes
1067: from dual
1068: where exists (
1069: SELECT 1
1070: FROM per_assignments_f ASG,
1071: per_assignment_status_types AST,
1072: hr_soft_coding_keyflex SCL
1073: WHERE ASG.assignment_id = p_asst_id
1074: AND ASG.effective_start_date > p_period_start

Line 1164: FROM per_assignments_f ASG,

1160: -- Check assignment status of current asg record.
1161:
1162: SELECT AST.per_system_status
1163: INTO v_asg_status
1164: FROM per_assignments_f ASG,
1165: per_assignment_status_types AST,
1166: hr_soft_coding_keyflex SCL
1167: WHERE ASG.assignment_id = p_asst_id
1168: AND p_period_start BETWEEN ASG.effective_start_date

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

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

Line 1267: FROM per_assignments_f ASG,

1263: v_asst_std_hrs,
1264: v_asst_std_freq,
1265: v_asst_std_freq_code,
1266: v_work_schedule
1267: FROM per_assignments_f ASG,
1268: per_assignment_status_types AST,
1269: hr_soft_coding_keyflex SCL,
1270: hr_lookups HRL
1271: WHERE ASG.assignment_id = p_asst_id

Line 1387: per_assignments_f ASG,

1383: v_asst_std_freq_code,
1384: v_work_schedule
1385: FROM hr_soft_coding_keyflex SCL,
1386: per_assignment_status_types AST,
1387: per_assignments_f ASG,
1388: hr_lookups HRL
1389: WHERE ASG.assignment_id = p_asst_id
1390: AND ASG.business_group_id + 0 = p_bus_grp_id
1391: AND ASG.effective_start_date > p_period_start

Line 1520: FROM per_assignments_f ASG,

1516: v_asst_std_hrs,
1517: v_asst_std_freq,
1518: v_asst_std_freq_code,
1519: v_work_schedule
1520: FROM per_assignments_f ASG,
1521: per_assignment_status_types AST,
1522: hr_soft_coding_keyflex SCL,
1523: hr_lookups HRL
1524: WHERE ASG.assignment_id = p_asst_id

Line 1776: per_assignments_f ASG,

1772: v_asst_std_freq_code,
1773: v_work_schedule
1774: FROM hr_soft_coding_keyflex SCL,
1775: per_assignment_status_types AST,
1776: per_assignments_f ASG,
1777: hr_lookups HRL
1778: WHERE ASG.assignment_id = p_asst_id
1779: AND ASG.business_group_id + 0 = p_bus_grp_id
1780: AND ASG.effective_start_date > p_period_start