APPS.AME_GCF_DEL dependencies on AME_GCF_DEL

Line 1: Package Body ame_gcf_del as

1: Package Body ame_gcf_del as
2: /* $Header: amgcfrhi.pkb 120.5 2006/10/05 16:08:09 pvelugul noship $ */
3: --
4: -- ----------------------------------------------------------------------------
5: -- | Private Global Definitions |

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

4: -- ----------------------------------------------------------------------------
5: -- | Private Global Definitions |
6: -- ----------------------------------------------------------------------------
7: --
8: g_package varchar2(33) := ' ame_gcf_del.'; -- Global package name
9: --
10: -- ----------------------------------------------------------------------------
11: -- |----------------------------< dt_delete_dml >-----------------------------|
12: -- ----------------------------------------------------------------------------

Line 111: ame_gcf_del.dt_delete_dml

107: --
108: Begin
109: hr_utility.set_location('Entering:'||l_proc, 5);
110: --
111: ame_gcf_del.dt_delete_dml
112: (p_rec => p_rec
113: ,p_effective_date => p_effective_date
114: ,p_datetrack_mode => p_datetrack_mode
115: ,p_validation_start_date => p_validation_start_date

Line 245: ame_gcf_del.dt_pre_delete

241: hr_utility.set_location('Entering:'||l_proc, 5);
242: --
243: --
244: --
245: ame_gcf_del.dt_pre_delete
246: (p_rec => p_rec
247: ,p_effective_date => p_effective_date
248: ,p_datetrack_mode => p_datetrack_mode
249: ,p_validation_start_date => p_validation_start_date

Line 391: ame_gcf_del.pre_delete

387: hr_multi_message.end_validation_set;
388: --
389: -- Call the supporting pre-delete operation
390: --
391: ame_gcf_del.pre_delete
392: (p_rec => p_rec
393: ,p_effective_date => p_effective_date
394: ,p_datetrack_mode => p_datetrack_mode
395: ,p_validation_start_date => l_validation_start_date

Line 401: ame_gcf_del.delete_dml

397: );
398: --
399: -- Delete the row.
400: --
401: ame_gcf_del.delete_dml
402: (p_rec => p_rec
403: ,p_effective_date => p_effective_date
404: ,p_datetrack_mode => p_datetrack_mode
405: ,p_validation_start_date => l_validation_start_date

Line 410: ame_gcf_del.post_delete

406: ,p_validation_end_date => l_validation_end_date
407: );
408: -- Call the supporting post-delete operation
409: --
410: ame_gcf_del.post_delete
411: (p_rec => p_rec
412: ,p_effective_date => p_effective_date
413: ,p_datetrack_mode => p_datetrack_mode
414: ,p_validation_start_date => l_validation_start_date

Line 458: ame_gcf_del.del

454: -- Having converted the arguments into the ame_gcf_rec
455: -- plsql record structure we must call the corresponding entity
456: -- business process
457: --
458: ame_gcf_del.del
459: (p_effective_date
460: ,p_datetrack_mode
461: ,l_rec
462: );

Line 474: end ame_gcf_del;

470: --
471: hr_utility.set_location(' Leaving:'||l_proc, 10);
472: End del;
473: --
474: end ame_gcf_del;