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.AME_RLU_INS dependencies on AME_RLU_INS

Line 1: Package Body ame_rlu_ins as

1: Package Body ame_rlu_ins as
2: /* $Header: amrlurhi.pkb 120.5 2005/11/22 03:19 santosin noship $ */
3: --
4: -- ----------------------------------------------------------------------------
5: -- | Private Global Definitions |

Line 8: g_package varchar2(33) := ' ame_rlu_ins.'; -- Global package name

4: -- ----------------------------------------------------------------------------
5: -- | Private Global Definitions |
6: -- ----------------------------------------------------------------------------
7: --
8: g_package varchar2(33) := ' ame_rlu_ins.'; -- Global package name
9: --
10: -- The following global variables are only to be used by
11: -- the set_base_key_value and pre_insert procedures.
12: --

Line 28: ame_rlu_ins.g_item_id_i := p_item_id;

24: --
25: Begin
26: hr_utility.set_location('Entering:'||l_proc, 10);
27: --
28: ame_rlu_ins.g_item_id_i := p_item_id;
29: ame_rlu_ins.g_rule_id_i := p_rule_id;
30: --
31: hr_utility.set_location(' Leaving:'||l_proc, 20);
32: End set_base_key_value;

Line 29: ame_rlu_ins.g_rule_id_i := p_rule_id;

25: Begin
26: hr_utility.set_location('Entering:'||l_proc, 10);
27: --
28: ame_rlu_ins.g_item_id_i := p_item_id;
29: ame_rlu_ins.g_rule_id_i := p_rule_id;
30: --
31: hr_utility.set_location(' Leaving:'||l_proc, 20);
32: End set_base_key_value;
33: --

Line 274: ame_rlu_ins.dt_insert_dml

270: --
271: Begin
272: hr_utility.set_location('Entering:'||l_proc, 5);
273: --
274: ame_rlu_ins.dt_insert_dml
275: (p_rec => p_rec
276: ,p_effective_date => p_effective_date
277: ,p_datetrack_mode => p_datetrack_mode
278: ,p_validation_start_date => p_validation_start_date

Line 338: ame_rlu_ins.g_item_id_i

334: Cursor C_Sel2 is
335: Select null
336: from ame_rule_usages
337: where item_id =
338: ame_rlu_ins.g_item_id_i
339: and rule_id =
340: ame_rlu_ins.g_rule_id_i
341: and p_effective_date between start_date
342: and nvl(end_date - ame_util.oneSecond , p_effective_date);

Line 340: ame_rlu_ins.g_rule_id_i

336: from ame_rule_usages
337: where item_id =
338: ame_rlu_ins.g_item_id_i
339: and rule_id =
340: ame_rlu_ins.g_rule_id_i
341: and p_effective_date between start_date
342: and nvl(end_date - ame_util.oneSecond , p_effective_date);
343: --
344: l_proc varchar2(72) := g_package||'pre_insert';

Line 350: If (ame_rlu_ins.g_item_id_i is not null or

346: --
347: Begin
348: hr_utility.set_location('Entering:'||l_proc, 5);
349: --
350: If (ame_rlu_ins.g_item_id_i is not null or
351: ame_rlu_ins.g_rule_id_i is not null) Then
352: --
353: -- Verify registered primary key values not already in use
354: --

Line 351: ame_rlu_ins.g_rule_id_i is not null) Then

347: Begin
348: hr_utility.set_location('Entering:'||l_proc, 5);
349: --
350: If (ame_rlu_ins.g_item_id_i is not null or
351: ame_rlu_ins.g_rule_id_i is not null) Then
352: --
353: -- Verify registered primary key values not already in use
354: --
355: Open C_Sel2;

Line 371: ame_rlu_ins.g_item_id_i;

367: --
368: -- Use registered key values and clear globals
369: --
370: p_rec.item_id :=
371: ame_rlu_ins.g_item_id_i;
372: ame_rlu_ins.g_item_id_i := null;
373: p_rec.rule_id :=
374: ame_rlu_ins.g_rule_id_i;
375: ame_rlu_ins.g_rule_id_i := null;

Line 372: ame_rlu_ins.g_item_id_i := null;

368: -- Use registered key values and clear globals
369: --
370: p_rec.item_id :=
371: ame_rlu_ins.g_item_id_i;
372: ame_rlu_ins.g_item_id_i := null;
373: p_rec.rule_id :=
374: ame_rlu_ins.g_rule_id_i;
375: ame_rlu_ins.g_rule_id_i := null;
376: End If;

Line 374: ame_rlu_ins.g_rule_id_i;

370: p_rec.item_id :=
371: ame_rlu_ins.g_item_id_i;
372: ame_rlu_ins.g_item_id_i := null;
373: p_rec.rule_id :=
374: ame_rlu_ins.g_rule_id_i;
375: ame_rlu_ins.g_rule_id_i := null;
376: End If;
377: --
378: --

Line 375: ame_rlu_ins.g_rule_id_i := null;

371: ame_rlu_ins.g_item_id_i;
372: ame_rlu_ins.g_item_id_i := null;
373: p_rec.rule_id :=
374: ame_rlu_ins.g_rule_id_i;
375: ame_rlu_ins.g_rule_id_i := null;
376: End If;
377: --
378: --
379: hr_utility.set_location(' Leaving:'||l_proc, 10);

Line 575: ame_rlu_ins.ins_lck

571: hr_utility.set_location('Entering:'||l_proc, 5);
572: --
573: -- Call the lock operation
574: --
575: ame_rlu_ins.ins_lck
576: (p_effective_date => p_effective_date
577: ,p_datetrack_mode => l_datetrack_mode
578: ,p_rec => p_rec
579: ,p_validation_start_date => l_validation_start_date

Line 598: ame_rlu_ins.pre_insert

594: hr_multi_message.end_validation_set;
595: --
596: -- Call the supporting pre-insert operation
597: --
598: ame_rlu_ins.pre_insert
599: (p_rec => p_rec
600: ,p_effective_date => p_effective_date
601: ,p_datetrack_mode => l_datetrack_mode
602: ,p_validation_start_date => l_validation_start_date

Line 608: ame_rlu_ins.insert_dml

604: );
605: --
606: -- Insert the row
607: --
608: ame_rlu_ins.insert_dml
609: (p_rec => p_rec
610: ,p_effective_date => p_effective_date
611: ,p_datetrack_mode => l_datetrack_mode
612: ,p_validation_start_date => l_validation_start_date

Line 618: ame_rlu_ins.post_insert

614: );
615: --
616: -- Call the supporting post-insert operation
617: --
618: ame_rlu_ins.post_insert
619: (p_rec => p_rec
620: ,p_effective_date => p_effective_date
621: ,p_datetrack_mode => l_datetrack_mode
622: ,p_validation_start_date => l_validation_start_date

Line 675: ame_rlu_ins.ins

671: -- Having converted the arguments into the ame_rlu_rec
672: -- plsql record structure we call the corresponding record
673: -- business process.
674: --
675: ame_rlu_ins.ins
676: (p_effective_date
677: ,l_rec
678: );
679: --

Line 690: end ame_rlu_ins;

686: --
687: hr_utility.set_location(' Leaving:'||l_proc, 10);
688: End ins;
689: --
690: end ame_rlu_ins;