DBA Data[Home] [Help]

PACKAGE BODY: APPS.BEN_BLI_DEL

Source


1 Package Body ben_bli_del as
2 /* $Header: beblirhi.pkb 115.7 2002/12/10 15:17:02 bmanyam ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |                     Private Global Definitions                           |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package  varchar2(33)	:= '  ben_bli_del.';  -- Global package name
9 --
10 -- ----------------------------------------------------------------------------
11 -- |------------------------------< delete_dml >------------------------------|
12 -- ----------------------------------------------------------------------------
13 -- {Start Of Comments}
14 --
15 -- Description:
16 --   This procedure controls the actual dml delete logic. The functions of
17 --   this procedure are as follows:
18 --   1) To set and unset the g_api_dml status as required (as we are about to
19 --      perform dml).
20 --   2) To delete the specified row from the schema using the primary key in
21 --      the predicates.
22 --   3) To trap any constraint violations that may have occurred.
23 --   4) To raise any other errors.
24 --
25 -- Prerequisites:
26 --   This is an internal private procedure which must be called from the del
27 --   procedure.
28 --
29 -- In Parameters:
30 --   A Pl/Sql record structre.
31 --
32 -- Post Success:
33 --   The specified row will be delete from the schema.
34 --
35 -- Post Failure:
36 --   On the delete dml failure it is important to note that we always reset the
37 --   g_api_dml status to false.
38 --   If a child integrity constraint violation is raised the
39 --   constraint_error procedure will be called.
40 --   If any other error is reported, the error will be raised after the
41 --   g_api_dml status is reset.
42 --
43 -- Developer Implementation Notes:
44 --   None.
45 --
46 -- Access Status:
47 --   Internal Row Handler Use Only.
48 --
49 -- {End Of Comments}
50 -- ----------------------------------------------------------------------------
51 Procedure delete_dml(p_rec in ben_bli_shd.g_rec_type) is
52 --
53   l_proc  varchar2(72) := g_package||'delete_dml';
54 --
55 Begin
56   hr_utility.set_location('Entering:'||l_proc, 5);
57   --
58   ben_bli_shd.g_api_dml := true;  -- Set the api dml status
59   --
60   -- Delete the ben_batch_ler_info row.
61   --
62   delete from ben_batch_ler_info
63   where batch_ler_id = p_rec.batch_ler_id;
64   --
65   ben_bli_shd.g_api_dml := false;   -- Unset the api dml status
66   --
67   hr_utility.set_location(' Leaving:'||l_proc, 10);
68 --
69 Exception
70   When hr_api.child_integrity_violated then
71     -- Child integrity has been violated
72     ben_bli_shd.g_api_dml := false;   -- Unset the api dml status
73     ben_bli_shd.constraint_error
74       (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
75   When Others Then
76     ben_bli_shd.g_api_dml := false;   -- Unset the api dml status
77     Raise;
78 End delete_dml;
79 --
80 -- ----------------------------------------------------------------------------
81 -- |------------------------------< pre_delete >------------------------------|
82 -- ----------------------------------------------------------------------------
83 -- {Start Of Comments}
84 --
85 -- Description:
86 --   This private procedure contains any processing which is required before
87 --   the delete dml.
88 --
89 -- Prerequisites:
90 --   This is an internal procedure which is called from the del procedure.
91 --
92 -- In Parameters:
93 --   A Pl/Sql record structre.
94 --
95 -- Post Success:
96 --   Processing continues.
97 --
98 -- Post Failure:
99 --   If an error has occurred, an error message and exception will be raised
100 --   but not handled.
101 --
102 -- Developer Implementation Notes:
103 --   Any pre-processing required before the delete dml is issued should be
104 --   coded within this procedure. It is important to note that any 3rd party
105 --   maintenance should be reviewed before placing in this procedure.
106 --
107 -- Access Status:
108 --   Internal Row Handler Use Only.
109 --
110 -- {End Of Comments}
111 -- ----------------------------------------------------------------------------
112 Procedure pre_delete(p_rec in ben_bli_shd.g_rec_type) is
113 --
114   l_proc  varchar2(72) := g_package||'pre_delete';
115 --
116 Begin
117   hr_utility.set_location('Entering:'||l_proc, 5);
118   --
119   hr_utility.set_location(' Leaving:'||l_proc, 10);
120 End pre_delete;
121 --
122 -- ----------------------------------------------------------------------------
123 -- |-----------------------------< post_delete >------------------------------|
124 -- ----------------------------------------------------------------------------
125 -- {Start Of Comments}
126 --
127 -- Description:
128 --   This private procedure contains any processing which is required after the
129 --   delete dml.
130 --
131 -- Prerequisites:
132 --   This is an internal procedure which is called from the del procedure.
133 --
134 -- In Parameters:
135 --   A Pl/Sql record structre.
136 --
137 -- Post Success:
138 --   Processing continues.
139 --
140 -- Post Failure:
141 --   If an error has occurred, an error message and exception will be raised
142 --   but not handled.
143 --
144 -- Developer Implementation Notes:
145 --   Any post-processing required after the delete dml is issued should be
146 --   coded within this procedure. It is important to note that any 3rd party
147 --   maintenance should be reviewed before placing in this procedure.
148 --
149 -- Access Status:
150 --   Internal table Handler Use Only.
151 --
152 -- {End Of Comments}
153 -- ----------------------------------------------------------------------------
154 Procedure post_delete(p_effective_date in date,
155                       p_rec in ben_bli_shd.g_rec_type) is
156 --
157   l_proc  varchar2(72) := g_package||'post_delete';
158 --
159 Begin
160   hr_utility.set_location('Entering:'||l_proc, 5);
161 --
162   --
163   -- Start of API User Hook for post_delete.
164   --
165   begin
166     --
167     ben_bli_rkd.after_delete
168       (p_batch_ler_id            =>p_rec.batch_ler_id
169       ,p_benefit_action_id_o     =>ben_bli_shd.g_old_rec.benefit_action_id
170       ,p_person_id_o             =>ben_bli_shd.g_old_rec.person_id
171       ,p_ler_id_o                =>ben_bli_shd.g_old_rec.ler_id
172       ,p_lf_evt_ocrd_dt_o        =>ben_bli_shd.g_old_rec.lf_evt_ocrd_dt
173       ,p_replcd_flag_o           =>ben_bli_shd.g_old_rec.replcd_flag
174       ,p_crtd_flag_o             =>ben_bli_shd.g_old_rec.crtd_flag
175       ,p_tmprl_flag_o            =>ben_bli_shd.g_old_rec.tmprl_flag
176       ,p_dltd_flag_o             =>ben_bli_shd.g_old_rec.dltd_flag
177       ,p_open_and_clsd_flag_o    =>ben_bli_shd.g_old_rec.open_and_clsd_flag
178       ,p_clsd_flag_o             =>ben_bli_shd.g_old_rec.clsd_flag
179       ,p_not_crtd_flag_o         =>ben_bli_shd.g_old_rec.not_crtd_flag
180       ,p_stl_actv_flag_o         =>ben_bli_shd.g_old_rec.stl_actv_flag
181       ,p_clpsd_flag_o            =>ben_bli_shd.g_old_rec.clpsd_flag
182       ,p_clsn_flag_o             =>ben_bli_shd.g_old_rec.clsn_flag
183       ,p_no_effect_flag_o        =>ben_bli_shd.g_old_rec.no_effect_flag
184       ,p_cvrge_rt_prem_flag_o    =>ben_bli_shd.g_old_rec.cvrge_rt_prem_flag
185       ,p_per_in_ler_id_o         =>ben_bli_shd.g_old_rec.per_in_ler_id
186       ,p_business_group_id_o     =>ben_bli_shd.g_old_rec.business_group_id
187       ,p_object_version_number_o =>ben_bli_shd.g_old_rec.object_version_number);
188     --
189   exception
190     --
191     when hr_api.cannot_find_prog_unit then
192       --
193       hr_api.cannot_find_prog_unit_error
194         (p_module_name => 'ben_batch_ler_info'
195         ,p_hook_type   => 'AD');
196       --
197   end;
198   --
199   -- End of API User Hook for post_delete.
200   --
201   --
202   hr_utility.set_location(' Leaving:'||l_proc, 10);
203 End post_delete;
204 --
205 -- ----------------------------------------------------------------------------
206 -- |---------------------------------< del >----------------------------------|
207 -- ----------------------------------------------------------------------------
208 Procedure del
209   (
210   p_effective_date in date,
211   p_rec	      in ben_bli_shd.g_rec_type
212   ) is
213 --
214   l_proc  varchar2(72) := g_package||'del';
215 --
216 Begin
217   hr_utility.set_location('Entering:'||l_proc, 5);
218   --
219   -- We must lock the row which we need to delete.
220   --
221   ben_bli_shd.lck
222 	(
223 	p_rec.batch_ler_id,
224 	p_rec.object_version_number
225 	);
226   --
227   -- Call the supporting delete validate operation
228   --
229   ben_bli_bus.delete_validate(p_rec,p_effective_date);
230   --
231   -- Call the supporting pre-delete operation
232   --
233   pre_delete(p_rec);
234   --
235   -- Delete the row.
236   --
237   delete_dml(p_rec);
238   --
239   -- Call the supporting post-delete operation
240   --
241   post_delete(p_effective_date,p_rec);
242   --
243 End del;
244 --
245 -- ----------------------------------------------------------------------------
246 -- |---------------------------------< del >----------------------------------|
247 -- ----------------------------------------------------------------------------
248 Procedure del
249   (
250   p_effective_date in date,
251   p_batch_ler_id                       in number,
252   p_object_version_number              in number
253   ) is
254 --
255   l_rec	  ben_bli_shd.g_rec_type;
256   l_proc  varchar2(72) := g_package||'del';
257 --
258 Begin
259   hr_utility.set_location('Entering:'||l_proc, 5);
260   --
261   -- As the delete procedure accepts a plsql record structure we do need to
262   -- convert the  arguments into the record structure.
263   -- We don't need to call the supplied conversion argument routine as we
264   -- only need a few attributes.
265   --
266   l_rec.batch_ler_id:= p_batch_ler_id;
267   l_rec.object_version_number := p_object_version_number;
268   --
269   -- Having converted the arguments into the ben_bli_rec
270   -- plsql record structure we must call the corresponding entity
271   -- business process
272   --
273   del(p_effective_date,l_rec);
274   --
275   hr_utility.set_location(' Leaving:'||l_proc, 10);
276 End del;
277 --
278 end ben_bli_del;