APPS.HR_ASSIGNMENT_ATT dependencies on PER_ASG_SHD

Line 942: per_asg_shd.lck

938: -- specified effective date. we only lock the current row so the
939: -- CORRECTION datetrack mode is used
940: -- b) to populate the l_validation_start_date which is used
941: -- in determining the correct datetrack mode on an update operation
942: per_asg_shd.lck
943: (p_effective_date => l_constant_effective_date
944: ,p_datetrack_mode => hr_api.g_correction
945: ,p_assignment_id => p_assignment_id
946: ,p_object_version_number => p_object_version_number

Line 966: per_asg_shd.find_dt_upd_modes

962: -- mode
963: -- otherwise, select CORRECTION as the mode
964: -- ------------------------------------------------------------------------
965: -- step 1.1
966: per_asg_shd.find_dt_upd_modes
967: (p_effective_date => l_constant_effective_date
968: ,p_base_key_value => p_assignment_id
969: ,p_correction => l_correction
970: ,p_update => l_update

Line 1550: per_asg_shd.lck

1546: -- specified effective date. we only lock the current row so the
1547: -- CORRECTION datetrack mode is used
1548: -- b) to populate the l_validation_start_date which is used
1549: -- in determining the correct datetrack mode on an update operation
1550: per_asg_shd.lck
1551: (p_effective_date => l_constant_effective_date
1552: ,p_datetrack_mode => hr_api.g_correction
1553: ,p_assignment_id => p_assignment_id
1554: ,p_object_version_number => p_object_version_number

Line 1574: per_asg_shd.find_dt_upd_modes

1570: -- mode
1571: -- otherwise, select CORRECTION as the mode
1572: -- ------------------------------------------------------------------------
1573: -- step 1.1
1574: per_asg_shd.find_dt_upd_modes
1575: (p_effective_date => l_constant_effective_date
1576: ,p_base_key_value => p_assignment_id
1577: ,p_correction => l_correction
1578: ,p_update => l_update