APPS.FF_FGL_INS dependencies on HR_API

Line 116: If (p_datetrack_mode <> hr_api.g_insert) then

112: --
113: -- If the datetrack_mode is not INSERT then we must populate the WHO
114: -- columns with the 'old' creation values and 'new' updated values.
115: --
116: If (p_datetrack_mode <> hr_api.g_insert) then
117: hr_utility.set_location(l_proc, 10);
118: --
119: -- Get the object version number for the insert
120: --

Line 197: When hr_api.check_integrity_violated Then

193: ff_fgl_shd.g_api_dml := false; -- Unset the api dml status
194: hr_utility.set_location(' Leaving:'||l_proc, 15);
195: --
196: Exception
197: When hr_api.check_integrity_violated Then
198: -- A check constraint has been violated
199: ff_fgl_shd.g_api_dml := false; -- Unset the api dml status
200: ff_fgl_shd.constraint_error
201: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

Line 201: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

197: When hr_api.check_integrity_violated Then
198: -- A check constraint has been violated
199: ff_fgl_shd.g_api_dml := false; -- Unset the api dml status
200: ff_fgl_shd.constraint_error
201: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
202: When hr_api.unique_integrity_violated Then
203: -- Unique integrity has been violated
204: ff_fgl_shd.g_api_dml := false; -- Unset the api dml status
205: ff_fgl_shd.constraint_error

Line 202: When hr_api.unique_integrity_violated Then

198: -- A check constraint has been violated
199: ff_fgl_shd.g_api_dml := false; -- Unset the api dml status
200: ff_fgl_shd.constraint_error
201: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
202: When hr_api.unique_integrity_violated Then
203: -- Unique integrity has been violated
204: ff_fgl_shd.g_api_dml := false; -- Unset the api dml status
205: ff_fgl_shd.constraint_error
206: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

Line 206: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));

202: When hr_api.unique_integrity_violated Then
203: -- Unique integrity has been violated
204: ff_fgl_shd.g_api_dml := false; -- Unset the api dml status
205: ff_fgl_shd.constraint_error
206: (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
207: When Others Then
208: ff_fgl_shd.g_api_dml := false; -- Unset the api dml status
209: Raise;
210: End dt_insert_dml;

Line 469: when hr_api.cannot_find_prog_unit then

465: );
466: --
467: exception
468: --
469: when hr_api.cannot_find_prog_unit then
470: --
471: hr_api.cannot_find_prog_unit_error
472: (p_module_name => 'FF_GLOBALS_F'
473: ,p_hook_type => 'AI');

Line 471: hr_api.cannot_find_prog_unit_error

467: exception
468: --
469: when hr_api.cannot_find_prog_unit then
470: --
471: hr_api.cannot_find_prog_unit_error
472: (p_module_name => 'FF_GLOBALS_F'
473: ,p_hook_type => 'AI');
474: --
475: end;

Line 504: -- another user. This will raise the HR_Api.Object_Locked exception.

500: --
501: -- Post Failure:
502: -- The Lck process can fail for:
503: -- 1) When attempting to lock the row the row could already be locked by
504: -- another user. This will raise the HR_Api.Object_Locked exception.
505: -- 2) When attempting to the lock the parent which doesn't exist.
506: -- For the entity to be locked the parent must exist!
507: --
508: -- Developer Implementation Notes:

Line 563: l_datetrack_mode varchar2(30) := hr_api.g_insert;

559: ,p_rec in out nocopy ff_fgl_shd.g_rec_type
560: ) is
561: --
562: l_proc varchar2(72) := g_package||'ins';
563: l_datetrack_mode varchar2(30) := hr_api.g_insert;
564: l_validation_start_date date;
565: l_validation_end_date date;
566: --
567: Begin