APPS.PAY_PBF_INS dependencies on HR_API

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

121: --
122: -- If the datetrack_mode is not INSERT then we must populate the WHO
123: -- columns with the 'old' creation values and 'new' updated values.
124: --
125: If (p_datetrack_mode <> hr_api.g_insert) then
126: hr_utility.set_location(l_proc, 10);
127: --
128: -- Select the 'old' created values
129: --

Line 195: When hr_api.check_integrity_violated Then

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

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

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

Line 200: When hr_api.unique_integrity_violated Then

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

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

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

Line 467: when hr_api.cannot_find_prog_unit then

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

Line 469: hr_api.cannot_find_prog_unit_error

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

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

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

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

562: ,p_exist_run_result_warning out nocopy boolean
563: ) is
564: --
565: l_proc varchar2(72) := g_package||'ins';
566: l_datetrack_mode varchar2(30) := hr_api.g_insert;
567: l_validation_start_date date;
568: l_validation_end_date date;
569: l_effective_date date;
570: --

Line 577: -- from hr_api.g_sot. The parents must also exist as of this date.

573:
574: pay_pbf_bus.g_balance_init_flag := null;
575:
576: -- When initial balance feed is being created, the effective start date must be
577: -- from hr_api.g_sot. The parents must also exist as of this date.
578:
579: if pay_pbf_bus.get_balance_init_flag ( p_input_value_id => p_rec.input_value_id ) then
580: l_effective_date := hr_api.g_sot;
581: else

Line 580: l_effective_date := hr_api.g_sot;

576: -- When initial balance feed is being created, the effective start date must be
577: -- from hr_api.g_sot. The parents must also exist as of this date.
578:
579: if pay_pbf_bus.get_balance_init_flag ( p_input_value_id => p_rec.input_value_id ) then
580: l_effective_date := hr_api.g_sot;
581: else
582: l_effective_date := p_effective_date;
583: end if;
584: