[Home] [Help]
99: --
100: -- If the datetrack_mode is not INSERT then we must populate the WHO
101: -- columns with the 'old' creation values and 'new' updated values.
102: --
103: If (p_datetrack_mode <> hr_api.g_insert) then
104: hr_utility.set_location(l_proc, 10);
105: --
106: -- Select the 'old' created values
107: --
241: per_spp_shd.g_api_dml := false; -- Unset the api dml status
242: hr_utility.set_location(' Leaving:'||l_proc, 15);
243: --
244: Exception
245: When hr_api.check_integrity_violated Then
246: -- A check constraint has been violated
247: per_spp_shd.g_api_dml := false; -- Unset the api dml status
248: per_spp_shd.constraint_error
249: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
245: When hr_api.check_integrity_violated Then
246: -- A check constraint has been violated
247: per_spp_shd.g_api_dml := false; -- Unset the api dml status
248: per_spp_shd.constraint_error
249: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
250: When hr_api.unique_integrity_violated Then
251: -- Unique integrity has been violated
252: per_spp_shd.g_api_dml := false; -- Unset the api dml status
253: per_spp_shd.constraint_error
246: -- A check constraint has been violated
247: per_spp_shd.g_api_dml := false; -- Unset the api dml status
248: per_spp_shd.constraint_error
249: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
250: When hr_api.unique_integrity_violated Then
251: -- Unique integrity has been violated
252: per_spp_shd.g_api_dml := false; -- Unset the api dml status
253: per_spp_shd.constraint_error
254: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
250: When hr_api.unique_integrity_violated Then
251: -- Unique integrity has been violated
252: per_spp_shd.g_api_dml := false; -- Unset the api dml status
253: per_spp_shd.constraint_error
254: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
255: When Others Then
256: per_spp_shd.g_api_dml := false; -- Unset the api dml status
257: Raise;
258: End dt_insert_dml;
404: l_object_version_number := c_future_spp.object_version_number;
405: --
406: hr_sp_placement_api.delete_spp
407: (p_effective_date => c_future_spp.effective_start_date
408: ,p_datetrack_mode => hr_api.g_zap
409: ,p_placement_id => c_future_spp.placement_id
410: ,p_object_version_number => l_object_version_number
411: ,p_effective_start_date => l_effective_start_date
412: ,p_effective_end_date => l_effective_end_date);
578: --
579: -- Keep the SPPs in synchronous with Assignment updates.
580: --
581: l_validation_start_date := p_effective_date+1;
582: l_validation_end_date := nvl(l_end_date,hr_api.g_eot);
583: --
584: FOR asg_rec in asg_updates(p_assignment_id, l_validation_start_date, l_validation_end_date) LOOP
585: --
586: l_asg_eff_start_date := asg_rec.effective_start_date;
867: );
868: --
869: exception
870: --
871: when hr_api.cannot_find_prog_unit then
872: --
873: hr_api.cannot_find_prog_unit_error
874: (p_module_name => 'PER_SPINAL_POINT_PLACEMENTS_F'
875: ,p_hook_type => 'AI');
869: exception
870: --
871: when hr_api.cannot_find_prog_unit then
872: --
873: hr_api.cannot_find_prog_unit_error
874: (p_module_name => 'PER_SPINAL_POINT_PLACEMENTS_F'
875: ,p_hook_type => 'AI');
876: --
877: end;
915: --
916: -- Post Failure:
917: -- The Lck process can fail for:
918: -- 1) When attempting to lock the row the row could already be locked by
919: -- another user. This will raise the HR_Api.Object_Locked exception.
920: -- 2) When attempting to the lock the parent which doesn't exist.
921: -- For the entity to be locked the parent must exist!
922: --
923: -- Developer Implementation Notes:
1037: ,p_replace_future_spp in boolean -- Added for bug 2977842.
1038: ) is
1039: --
1040: l_proc varchar2(72) := g_package||'ins';
1041: l_datetrack_mode varchar2(30) := hr_api.g_insert;
1042: l_validation_start_date date;
1043: l_validation_end_date date;
1044: --
1045: Begin