1 Package Body ben_xct_del as
2 /* $Header: bexctrhi.pkb 115.12 2002/12/31 20:39:06 stee ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' ben_xct_del.'; -- Global package name
9
10 --
11 -- ----------------------------------------------------------------------------
12 -- ----------------------< delete_app_ownerships >----------------------------|
13 -- ----------------------------------------------------------------------------
14 --
15 -- Description:
16 -- Deletes row(s) from hr_application_ownerships depending on the mode that
17 -- the row handler has been called in.
18 --
19 -- ----------------------------------------------------------------------------
20 PROCEDURE delete_app_ownerships(p_pk_column IN varchar2
21 ,p_pk_value IN varchar2) IS
22 --
23 BEGIN
24 --
25 IF (hr_startup_data_api_support.return_startup_mode
26 IN ('STARTUP','GENERIC')) THEN
27 --
28 DELETE FROM hr_application_ownerships
29 WHERE key_name = p_pk_column
30 AND key_value = p_pk_value;
31 --
32 END IF;
33 END delete_app_ownerships;
34 --
35 -- ----------------------------------------------------------------------------
36 -- ----------------------< delete_app_ownerships >----------------------------|
37 -- ----------------------------------------------------------------------------
38 PROCEDURE delete_app_ownerships(p_pk_column IN varchar2
39 ,p_pk_value IN number) IS
40 --
41 BEGIN
42 delete_app_ownerships(p_pk_column, to_char(p_pk_value));
43 END delete_app_ownerships;
44
45 --
46 -- ----------------------------------------------------------------------------
47 -- |------------------------------< delete_dml >------------------------------|
48 -- ----------------------------------------------------------------------------
49 -- {Start Of Comments}
50 --
51 -- Description:
52 -- This procedure controls the actual dml delete logic. The functions of
53 -- this procedure are as follows:
54 -- 1) To set and unset the g_api_dml status as required (as we are about to
55 -- perform dml).
56 -- 2) To delete the specified row from the schema using the primary key in
57 -- the predicates.
58 -- 3) To trap any constraint violations that may have occurred.
59 -- 4) To raise any other errors.
60 --
61 -- Prerequisites:
62 -- This is an internal private procedure which must be called from the del
63 -- procedure.
64 --
65 -- In Parameters:
66 -- A Pl/Sql record structre.
67 --
68 -- Post Success:
69 -- The specified row will be delete from the schema.
70 --
71 -- Post Failure:
72 -- On the delete dml failure it is important to note that we always reset the
73 -- g_api_dml status to false.
74 -- If a child integrity constraint violation is raised the
75 -- constraint_error procedure will be called.
76 -- If any other error is reported, the error will be raised after the
77 -- g_api_dml status is reset.
78 --
79 -- Developer Implementation Notes:
80 -- None.
81 --
82 -- Access Status:
83 -- Internal Row Handler Use Only.
84 --
85 -- {End Of Comments}
86 -- ----------------------------------------------------------------------------
87 Procedure delete_dml(p_rec in ben_xct_shd.g_rec_type) is
88 --
89 l_proc varchar2(72) := g_package||'delete_dml';
90 --
91 Begin
92 hr_utility.set_location('Entering:'||l_proc, 5);
93 --
94 ben_xct_shd.g_api_dml := true; -- Set the api dml status
95 --
96 -- Delete the ben_ext_crit_typ row.
97 --
98 delete from ben_ext_crit_typ
99 where ext_crit_typ_id = p_rec.ext_crit_typ_id;
100 --
101 ben_xct_shd.g_api_dml := false; -- Unset the api dml status
102 --
103 hr_utility.set_location(' Leaving:'||l_proc, 10);
104 --
105 Exception
106 When hr_api.child_integrity_violated then
107 -- Child integrity has been violated
108 ben_xct_shd.g_api_dml := false; -- Unset the api dml status
109 ben_xct_shd.constraint_error
110 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
111 When Others Then
112 ben_xct_shd.g_api_dml := false; -- Unset the api dml status
113 Raise;
114 End delete_dml;
115 --
116 -- ----------------------------------------------------------------------------
117 -- |------------------------------< pre_delete >------------------------------|
118 -- ----------------------------------------------------------------------------
119 -- {Start Of Comments}
120 --
121 -- Description:
122 -- This private procedure contains any processing which is required before
123 -- the delete dml.
124 --
125 -- Prerequisites:
126 -- This is an internal procedure which is called from the del procedure.
127 --
128 -- In Parameters:
129 -- A Pl/Sql record structre.
130 --
131 -- Post Success:
132 -- Processing continues.
133 --
134 -- Post Failure:
135 -- If an error has occurred, an error message and exception will be raised
136 -- but not handled.
137 --
138 -- Developer Implementation Notes:
139 -- Any pre-processing required before the delete dml is issued should be
140 -- coded within this procedure. It is important to note that any 3rd party
141 -- maintenance should be reviewed before placing in this procedure.
142 --
143 -- Access Status:
144 -- Internal Row Handler Use Only.
145 --
146 -- {End Of Comments}
147 -- ----------------------------------------------------------------------------
148 Procedure pre_delete(p_rec in ben_xct_shd.g_rec_type) is
149 --
150 l_proc varchar2(72) := g_package||'pre_delete';
151 --
152 Begin
153 hr_utility.set_location('Entering:'||l_proc, 5);
154 --
155 hr_utility.set_location(' Leaving:'||l_proc, 10);
156 End pre_delete;
157 --
158 -- ----------------------------------------------------------------------------
159 -- |-----------------------------< post_delete >------------------------------|
160 -- ----------------------------------------------------------------------------
161 -- {Start Of Comments}
162 --
163 -- Description:
164 -- This private procedure contains any processing which is required after the
165 -- delete dml.
166 --
167 -- Prerequisites:
168 -- This is an internal procedure which is called from the del procedure.
169 --
170 -- In Parameters:
171 -- A Pl/Sql record structre.
172 --
173 -- Post Success:
174 -- Processing continues.
175 --
176 -- Post Failure:
177 -- If an error has occurred, an error message and exception will be raised
178 -- but not handled.
179 --
180 -- Developer Implementation Notes:
181 -- Any post-processing required after the delete dml is issued should be
182 -- coded within this procedure. It is important to note that any 3rd party
183 -- maintenance should be reviewed before placing in this procedure.
184 --
185 -- Access Status:
186 -- Internal table Handler Use Only.
187 --
188 -- {End Of Comments}
189 -- ----------------------------------------------------------------------------
190 Procedure post_delete(
191 p_effective_date in date,p_rec in ben_xct_shd.g_rec_type) is
192 --
193 l_proc varchar2(72) := g_package||'post_delete';
194 --
195 Begin
196 hr_utility.set_location('Entering:'||l_proc, 5);
197 --
198 --
199 -- Delete ownerships if applicable
200 --
201 delete_app_ownerships('EXT_CRIT_TYP_ID', p_rec.ext_crit_typ_id);
202 --
203 -- Start of API User Hook for post_delete.
204 --
205 begin
206 --
207 ben_xct_rkd.after_delete
208 (
209 p_ext_crit_typ_id =>p_rec.ext_crit_typ_id
210 ,p_crit_typ_cd_o =>ben_xct_shd.g_old_rec.crit_typ_cd
211 ,p_ext_crit_prfl_id_o =>ben_xct_shd.g_old_rec.ext_crit_prfl_id
212 ,p_business_group_id_o =>ben_xct_shd.g_old_rec.business_group_id
213 ,p_legislation_code_o =>ben_xct_shd.g_old_rec.legislation_code
214 ,p_object_version_number_o =>ben_xct_shd.g_old_rec.object_version_number
215 ,p_excld_flag_o =>ben_xct_shd.g_old_rec.excld_flag
216 );
217 --
218 exception
219 --
220 when hr_api.cannot_find_prog_unit then
221 --
222 hr_api.cannot_find_prog_unit_error
223 (p_module_name => 'ben_ext_crit_typ'
224 ,p_hook_type => 'AD');
225 --
226 end;
227 --
228 -- End of API User Hook for post_delete.
229 --
230 --
231 hr_utility.set_location(' Leaving:'||l_proc, 10);
232 End post_delete;
233 --
234 -- ----------------------------------------------------------------------------
235 -- |---------------------------------< del >----------------------------------|
236 -- ----------------------------------------------------------------------------
237 Procedure del
238 (
239 p_effective_date in date,
240 p_rec in ben_xct_shd.g_rec_type
241 ) is
242 --
243 l_proc varchar2(72) := g_package||'del';
244 --
245 Begin
246 hr_utility.set_location('Entering:'||l_proc, 5);
247 --
248 -- We must lock the row which we need to delete.
249 --
250 ben_xct_shd.lck
251 (
252 p_rec.ext_crit_typ_id,
253 p_rec.object_version_number
254 );
255 --
256 -- Call the supporting delete validate operation
257 --
258 ben_xct_bus.delete_validate(p_rec
259 ,p_effective_date);
260 --
261 -- Call the supporting pre-delete operation
262 --
263 pre_delete(p_rec);
264 --
265 -- Delete the row.
266 --
267 delete_dml(p_rec);
268 --
269 -- Call the supporting post-delete operation
270 --
271 post_delete(
272 p_effective_date,p_rec);
273 End del;
274 --
275 -- ----------------------------------------------------------------------------
276 -- |---------------------------------< del >----------------------------------|
277 -- ----------------------------------------------------------------------------
278 Procedure del
279 (
280 p_effective_date in date,
281 p_ext_crit_typ_id in number,
282 p_legislation_code in varchar2 default null,
283 p_object_version_number in number
284 ) is
285 --
286 l_rec ben_xct_shd.g_rec_type;
287 l_proc varchar2(72) := g_package||'del';
288 --
289 Begin
290 hr_utility.set_location('Entering:'||l_proc, 5);
291 --
292 -- As the delete procedure accepts a plsql record structure we do need to
293 -- convert the arguments into the record structure.
294 -- We don't need to call the supplied conversion argument routine as we
295 -- only need a few attributes.
296 --
297 l_rec.ext_crit_typ_id:= p_ext_crit_typ_id;
298 l_rec.object_version_number := p_object_version_number;
299 l_rec.legislation_code := p_legislation_code;
300 --
301 -- Having converted the arguments into the ben_xct_rec
302 -- plsql record structure we must call the corresponding entity
303 -- business process
304 --
305 del(
306 p_effective_date,l_rec);
307 --
308 hr_utility.set_location(' Leaving:'||l_proc, 10);
309 End del;
310 --
311 end ben_xct_del;
[Home] [Help]