APPS.HR_ASSIGNMENT_ATT dependencies on PER_ASG_SHD

Line 970: per_asg_shd.lck

966: -- specified effective date. we only lock the current row so the
967: -- CORRECTION datetrack mode is used
968: -- b) to populate the l_validation_start_date which is used
969: -- in determining the correct datetrack mode on an update operation
970: per_asg_shd.lck
971: (p_effective_date => l_constant_effective_date
972: ,p_datetrack_mode => hr_api.g_correction
973: ,p_assignment_id => p_assignment_id
974: ,p_object_version_number => p_object_version_number

Line 994: per_asg_shd.find_dt_upd_modes

990: -- mode
991: -- otherwise, select CORRECTION as the mode
992: -- ------------------------------------------------------------------------
993: -- step 1.1
994: per_asg_shd.find_dt_upd_modes
995: (p_effective_date => l_constant_effective_date
996: ,p_base_key_value => p_assignment_id
997: ,p_correction => l_correction
998: ,p_update => l_update

Line 1588: per_asg_shd.lck

1584: -- specified effective date. we only lock the current row so the
1585: -- CORRECTION datetrack mode is used
1586: -- b) to populate the l_validation_start_date which is used
1587: -- in determining the correct datetrack mode on an update operation
1588: per_asg_shd.lck
1589: (p_effective_date => l_constant_effective_date
1590: ,p_datetrack_mode => hr_api.g_correction
1591: ,p_assignment_id => p_assignment_id
1592: ,p_object_version_number => p_object_version_number

Line 1612: per_asg_shd.find_dt_upd_modes

1608: -- mode
1609: -- otherwise, select CORRECTION as the mode
1610: -- ------------------------------------------------------------------------
1611: -- step 1.1
1612: per_asg_shd.find_dt_upd_modes
1613: (p_effective_date => l_constant_effective_date
1614: ,p_base_key_value => p_assignment_id
1615: ,p_correction => l_correction
1616: ,p_update => l_update