DBA Data[Home] [Help]

PACKAGE BODY: APPS.BEN_BCI_DEL

Source


1 Package Body ben_bci_del as
2 /* $Header: bebcirhi.pkb 120.0 2005/05/28 00:35:20 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |                     Private Global Definitions                           |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package  varchar2(33)	:= '  ben_bci_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_bci_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_bci_shd.g_api_dml := true;  -- Set the api dml status
59   --
60   -- Delete the ben_batch_bnft_cert_info row.
61   --
62   delete from ben_batch_bnft_cert_info
63   where batch_benft_cert_id = p_rec.batch_benft_cert_id;
64   --
65   ben_bci_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_bci_shd.g_api_dml := false;   -- Unset the api dml status
73     ben_bci_shd.constraint_error
74       (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
75   When Others Then
76     ben_bci_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_bci_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(
155 p_effective_date in date,p_rec in ben_bci_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_bci_rkd.after_delete
168       (
169   p_batch_benft_cert_id           =>p_rec.batch_benft_cert_id
170  ,p_benefit_action_id_o           =>ben_bci_shd.g_old_rec.benefit_action_id
171  ,p_person_id_o                   =>ben_bci_shd.g_old_rec.person_id
172  ,p_actn_typ_id_o                 =>ben_bci_shd.g_old_rec.actn_typ_id
173  ,p_typ_cd_o                      =>ben_bci_shd.g_old_rec.typ_cd
174  ,p_enrt_ctfn_recd_dt_o           =>ben_bci_shd.g_old_rec.enrt_ctfn_recd_dt
175  ,p_object_version_number_o       =>ben_bci_shd.g_old_rec.object_version_number
176       );
177     --
178   exception
179     --
180     when hr_api.cannot_find_prog_unit then
181       --
182       hr_api.cannot_find_prog_unit_error
183         (p_module_name => 'ben_batch_bnft_cert_info'
184         ,p_hook_type   => 'AD');
185       --
186   end;
187   --
188   -- End of API User Hook for post_delete.
189   --
190   --
191   hr_utility.set_location(' Leaving:'||l_proc, 10);
192 End post_delete;
193 --
194 -- ----------------------------------------------------------------------------
195 -- |---------------------------------< del >----------------------------------|
196 -- ----------------------------------------------------------------------------
197 Procedure del
198   (
199   p_effective_date in date,
200   p_rec	      in ben_bci_shd.g_rec_type
201   ) is
202 --
203   l_proc  varchar2(72) := g_package||'del';
204 --
205 Begin
206   hr_utility.set_location('Entering:'||l_proc, 5);
207   --
208   -- We must lock the row which we need to delete.
209   --
210   ben_bci_shd.lck
211 	(
212 	p_rec.batch_benft_cert_id,
213 	p_rec.object_version_number
214 	);
215   --
216   -- Call the supporting delete validate operation
217   --
218   ben_bci_bus.delete_validate(p_rec
219   ,p_effective_date);
220   --
221   -- Call the supporting pre-delete operation
222   --
223   pre_delete(p_rec);
224   --
225   -- Delete the row.
226   --
227   delete_dml(p_rec);
228   --
229   -- Call the supporting post-delete operation
230   --
231   post_delete(
232 p_effective_date,p_rec);
233 End del;
234 --
235 -- ----------------------------------------------------------------------------
236 -- |---------------------------------< del >----------------------------------|
237 -- ----------------------------------------------------------------------------
238 Procedure del
239   (
240   p_effective_date in date,
241   p_batch_benft_cert_id                in number,
242   p_object_version_number              in number
243   ) is
244 --
245   l_rec	  ben_bci_shd.g_rec_type;
246   l_proc  varchar2(72) := g_package||'del';
247 --
248 Begin
249   hr_utility.set_location('Entering:'||l_proc, 5);
250   --
251   -- As the delete procedure accepts a plsql record structure we do need to
252   -- convert the  arguments into the record structure.
253   -- We don't need to call the supplied conversion argument routine as we
254   -- only need a few attributes.
255   --
256   l_rec.batch_benft_cert_id:= p_batch_benft_cert_id;
257   l_rec.object_version_number := p_object_version_number;
258   --
259   -- Having converted the arguments into the ben_bci_rec
260   -- plsql record structure we must call the corresponding entity
261   -- business process
262   --
263   del(
264     p_effective_date,l_rec);
265   --
266   hr_utility.set_location(' Leaving:'||l_proc, 10);
267 End del;
268 --
269 end ben_bci_del;