eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.PER_ABV_SHD dependencies on HR_UTILITY

Line 19: hr_utility.set_location('Entering:'||l_proc, 5);

15: --
16: l_proc varchar2(72) := g_package||'return_api_dml_status';
17: --
18: Begin
19: hr_utility.set_location('Entering:'||l_proc, 5);
20: --
21: Return (nvl(g_api_dml, false));
22: --
23: hr_utility.set_location(' Leaving:'||l_proc, 10);

Line 23: hr_utility.set_location(' Leaving:'||l_proc, 10);

19: hr_utility.set_location('Entering:'||l_proc, 5);
20: --
21: Return (nvl(g_api_dml, false));
22: --
23: hr_utility.set_location(' Leaving:'||l_proc, 10);
24: End return_api_dml_status;
25: --
26: --
27: -- ----------------------------------------------------------------------------

Line 51: hr_utility.set_location('Entering:'||l_proc, 5);

47: l_proc varchar2(72) := g_package||'convert_args';
48: --
49: Begin
50: --
51: hr_utility.set_location('Entering:'||l_proc, 5);
52: --
53: -- Convert arguments into local l_rec structure.
54: --
55: l_rec.assignment_budget_value_id := p_assignment_budget_value_id;

Line 70: hr_utility.set_location(' Leaving:'||l_proc, 10);

66: l_rec.object_version_number := p_object_version_number;
67: --
68: -- Return the plsql record structure.
69: --
70: hr_utility.set_location(' Leaving:'||l_proc, 10);
71: Return(l_rec);
72: --
73: end convert_args;
74:

Line 205: hr_utility.set_location('Entering:'||l_proc, 5);

201: --
202: l_proc varchar2(72) := g_package||'find_dt_upd_modes';
203: --
204: Begin
205: hr_utility.set_location('Entering:'||l_proc, 5);
206: --
207: -- Call the corresponding datetrack api
208: --
209: dt_api.find_dt_upd_modes

Line 220: hr_utility.set_location(' Leaving:'||l_proc, 10);

216: ,p_update_override => p_update_override
217: ,p_update_change_insert => p_update_change_insert
218: );
219: --
220: hr_utility.set_location(' Leaving:'||l_proc, 10);
221: End find_dt_upd_modes;
222: --
223: -- ----------------------------------------------------------------------------
224: -- |---------------------------< find_dt_del_modes >--------------------------|

Line 248: hr_utility.set_location('Entering:'||l_proc, 5);

244: and p_effective_date
245: between t.effective_start_date and t.effective_end_date;
246: --
247: Begin
248: hr_utility.set_location('Entering:'||l_proc, 5);
249: Open C_sel1;
250: Fetch C_Sel1 Into
251: l_parent_key_value1;
252: If C_Sel1%NOTFOUND then

Line 277: hr_utility.set_location(' Leaving:'||l_proc, 10);

273: ,p_future_change => p_future_change
274: ,p_delete_next_change => p_delete_next_change
275: );
276: --
277: hr_utility.set_location(' Leaving:'||l_proc, 10);
278: End find_dt_del_modes;
279: --
280: -- ----------------------------------------------------------------------------
281: -- |-----------------------< upd_effective_end_date >-------------------------|

Line 296: hr_utility.set_location('Entering:'||l_proc, 5);

292: l_proc varchar2(72) := g_package||'upd_effective_end_date';
293: l_object_version_number number(9);
294: --
295: Begin
296: hr_utility.set_location('Entering:'||l_proc, 5);
297: --
298: -- Because we are updating a row we must get the next object
299: -- version number.
300: --

Line 307: hr_utility.set_location(l_proc, 10);

303: (p_base_table_name => 'per_assignment_budget_values_f',
304: p_base_key_column => 'assignment_budget_value_id',
305: p_base_key_value => p_base_key_value);
306: --
307: hr_utility.set_location(l_proc, 10);
308: g_api_dml := true; -- Set the api dml status
309: --
310: --
311: -- Update the specified datetrack row setting the effective

Line 323: hr_utility.set_location(' Leaving:'||l_proc, 15);

319: --
320:
321: g_api_dml := false; -- Unset the api dml status (bug 8506130)
322: p_object_version_number := l_object_version_number;
323: hr_utility.set_location(' Leaving:'||l_proc, 15);
324: --
325: End upd_effective_end_date;
326: --
327: -- ----------------------------------------------------------------------------

Line 370: hr_utility.set_location('Entering:'||l_proc, 5);

366: --
367: --
368: --
369: Begin
370: hr_utility.set_location('Entering:'||l_proc, 5);
371: --
372: -- Ensure that all the mandatory arguments are not null
373: --
374: hr_api.mandatory_arg_error(p_api_name => l_proc

Line 414: hr_utility.set_message(801, 'HR_7155_OBJECT_INVALID');

410: Close C_Sel1;
411: --
412: --
413: If (p_object_version_number <> g_old_rec.object_version_number) Then
414: hr_utility.set_message(801, 'HR_7155_OBJECT_INVALID');
415: hr_utility.raise_error;
416: End If;
417: --
418: -- Validate the datetrack mode mode getting the validation start

Line 415: hr_utility.raise_error;

411: --
412: --
413: If (p_object_version_number <> g_old_rec.object_version_number) Then
414: hr_utility.set_message(801, 'HR_7155_OBJECT_INVALID');
415: hr_utility.raise_error;
416: End If;
417: --
418: -- Validate the datetrack mode mode getting the validation start
419: -- and end dates for the specified datetrack operation.

Line 451: hr_utility.set_location(' Leaving:'||l_proc, 30);

447: --
448: p_validation_start_date := l_validation_start_date;
449: p_validation_end_date := l_validation_end_date;
450: --
451: hr_utility.set_location(' Leaving:'||l_proc, 30);
452: --
453: -- We need to trap the ORA LOCK exception
454: --
455: Exception