1 Package Body ame_gpi_del as
2 /* $Header: amgpirhi.pkb 120.4 2006/03/01 03:10 pvelugul noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' ame_gpi_del.'; -- Global package name
9 --
10 -- ----------------------------------------------------------------------------
11 -- |----------------------------< dt_delete_dml >-----------------------------|
12 -- ----------------------------------------------------------------------------
13 -- {Start Of Comments}
14 --
15 -- Description:
16 -- This procedure controls the actual dml delete logic for the datetrack
17 -- delete modes: ZAP, DELETE, FUTURE_CHANGE and DELETE_NEXT_CHANGE. The
18 -- execution is as follows:
19 -- 1) To set and unset the g_api_dml status as required (as we are about to
20 -- perform dml).
21 -- 2) If the delete mode is DELETE_NEXT_CHANGE then delete where the
22 -- effective start date is equal to the validation start date.
23 -- 3) If the delete mode is not DELETE_NEXT_CHANGE then delete
24 -- all rows for the entity where the effective start date is greater
25 -- than or equal to the validation start date.
26 -- 4) To raise any errors.
27 --
28 -- Prerequisites:
29 -- This is an internal private procedure which must be called from the
30 -- delete_dml procedure.
31 --
32 -- In Parameters:
33 -- A Pl/Sql record structure.
34 --
35 -- Post Success:
36 -- The specified row will be delete from the schema.
37 --
38 -- Post Failure:
39 -- On the delete dml failure it is important to note that we always reset the
40 -- g_api_dml status to false.
41 -- If any other error is reported, the error will be raised after the
42 -- g_api_dml status is reset.
43 --
44 -- Developer Implementation Notes:
45 -- This is an internal private procedure which must be called from the
46 -- delete_dml procedure.
47 --
48 -- Access Status:
49 -- Internal Row Handler Use Only.
50 --
51 -- {End Of Comments}
52 -- ----------------------------------------------------------------------------
53 Procedure dt_delete_dml
54 (p_rec in out nocopy ame_gpi_shd.g_rec_type
55 ,p_effective_date in date
56 ,p_datetrack_mode in varchar2
57 ,p_validation_start_date in date
58 ,p_validation_end_date in date
59 ) is
60 --
61 l_proc varchar2(72) := g_package||'dt_delete_dml';
62 --
63 Begin
64 hr_utility.set_location('Entering:'||l_proc, 5);
65 If (p_datetrack_mode = hr_api.g_delete_next_change) then
66 --
67 --
68 -- Delete the where the effective start date is equal
69 -- to the validation end date.
70 --
71 delete from ame_approval_group_items
72 where approval_group_item_id = p_rec.approval_group_item_id
73 and start_date = p_validation_start_date;
74 --
75 --
76 /*Else
77 --
78 --
79 -- Delete the row(s) where the effective start date is greater than
80 -- or equal to the validation start date.
81 --
82 delete from ame_approval_group_items
83 where approval_group_item_id = p_rec.approval_group_item_id
84 and start_date >= p_validation_start_date;*/
85 --
86 --
87 End If;
88 --
89 hr_utility.set_location(' Leaving:'||l_proc, 20);
90 --
91 End dt_delete_dml;
92 --
93 -- ----------------------------------------------------------------------------
94 -- |------------------------------< delete_dml >------------------------------|
95 -- ----------------------------------------------------------------------------
96 Procedure delete_dml
97 (p_rec in out nocopy ame_gpi_shd.g_rec_type
98 ,p_effective_date in date
99 ,p_datetrack_mode in varchar2
100 ,p_validation_start_date in date
101 ,p_validation_end_date in date
102 ) is
103 --
104 l_proc varchar2(72) := g_package||'delete_dml';
105 --
106 Begin
107 hr_utility.set_location('Entering:'||l_proc, 5);
108 --
109 ame_gpi_del.dt_delete_dml
110 (p_rec => p_rec
111 ,p_effective_date => p_effective_date
112 ,p_datetrack_mode => p_datetrack_mode
113 ,p_validation_start_date => p_validation_start_date
114 ,p_validation_end_date => p_validation_end_date
115 );
116 --
117 hr_utility.set_location(' Leaving:'||l_proc, 10);
118 End delete_dml;
119 --
120 -- ----------------------------------------------------------------------------
121 -- |----------------------------< dt_pre_delete >-----------------------------|
122 -- ----------------------------------------------------------------------------
123 -- {Start Of Comments}
124 --
125 -- Description:
126 -- The dt_pre_delete process controls the execution of dml
127 -- for the datetrack modes: DELETE, FUTURE_CHANGE
128 -- and DELETE_NEXT_CHANGE only.
129 --
130 -- Prerequisites:
131 -- This is an internal procedure which is called from the pre_delete
132 -- procedure.
133 --
134 -- In Parameters:
135 -- A Pl/Sql record structure.
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 -- This is an internal procedure which is required by Datetrack. Don't
146 -- remove or modify.
147 --
148 -- Access Status:
149 -- Internal Row Handler Use Only.
150 --
151 -- {End Of Comments}
152 -- ----------------------------------------------------------------------------
153 Procedure dt_pre_delete
154 (p_rec in out nocopy ame_gpi_shd.g_rec_type
155 ,p_effective_date in date
156 ,p_datetrack_mode in varchar2
157 ,p_validation_start_date in date
158 ,p_validation_end_date in date
159 ) is
160 --
161 l_proc varchar2(72) := g_package||'dt_pre_delete';
162 --
163 Begin
164 hr_utility.set_location('Entering:'||l_proc, 5);
165 --
166 If (p_datetrack_mode <> hr_api.g_zap) then
167 --
168 p_rec.start_date
169 := ame_gpi_shd.g_old_rec.start_date;
170 --
171 If (p_datetrack_mode = hr_api.g_delete) then
172 p_rec.end_date := p_validation_start_date;
173 Else
174 p_rec.end_date := p_validation_end_date;
175 End If;
176 --
177 -- Update the current effective end date record
178 --
179 ame_gpi_shd.upd_end_date
180 (p_effective_date => p_effective_date
181 ,p_approval_group_item_id => p_rec.approval_group_item_id
182 ,p_new_end_date => p_rec.end_date
183 ,p_object_version_number => p_rec.object_version_number
184 );
185 Else
186 p_rec.start_date := null;
187 p_rec.end_date := null;
188 End If;
189 hr_utility.set_location(' Leaving:'||l_proc, 10);
190 End dt_pre_delete;
191 --
192 -- ----------------------------------------------------------------------------
193 -- |------------------------------< pre_delete >------------------------------|
194 -- ----------------------------------------------------------------------------
195 -- {Start Of Comments}
196 --
197 -- Description:
198 -- This private procedure contains any processing which is required before
199 -- the delete dml.
200 --
201 -- Prerequisites:
202 -- This is an internal procedure which is called from the del procedure.
203 --
204 -- In Parameters:
205 -- A Pl/Sql record structure.
206 --
207 -- Post Success:
208 -- Processing continues.
209 --
210 -- Post Failure:
211 -- If an error has occurred, an error message and exception will be raised
212 -- but not handled.
213 --
214 -- Developer Implementation Notes:
215 -- Any pre-processing required before the delete dml is issued should be
216 -- coded within this procedure. It is important to note that any 3rd party
220 -- Access Status:
217 -- maintenance should be reviewed before placing in this procedure. The call
218 -- to the dt_delete_dml procedure should NOT be removed.
219 --
221 -- Internal Row Handler Use Only.
222 --
223 -- {End Of Comments}
224 -- ----------------------------------------------------------------------------
225 Procedure pre_delete
226 (p_rec in out nocopy ame_gpi_shd.g_rec_type
227 ,p_effective_date in date
228 ,p_datetrack_mode in varchar2
229 ,p_validation_start_date in date
230 ,p_validation_end_date in date
231 ) is
232 --
233 l_proc varchar2(72) := g_package||'pre_delete';
234 --
235 --
236 --
237 Begin
238 hr_utility.set_location('Entering:'||l_proc, 5);
239 --
240 --
241 --
242 ame_gpi_del.dt_pre_delete
243 (p_rec => p_rec
244 ,p_effective_date => p_effective_date
245 ,p_datetrack_mode => p_datetrack_mode
246 ,p_validation_start_date => p_validation_start_date
247 ,p_validation_end_date => p_validation_end_date
248 );
249 --
250 hr_utility.set_location(' Leaving:'||l_proc, 10);
251 End pre_delete;
252 --
253 -- ----------------------------------------------------------------------------
254 -- |----------------------------< post_delete >-------------------------------|
255 -- ----------------------------------------------------------------------------
256 -- {Start Of Comments}
257 --
258 -- Description:
259 -- This private procedure contains any processing which is required after
260 -- the delete dml.
261 --
262 -- Prerequisites:
263 -- This is an internal procedure which is called from the del procedure.
264 --
265 -- In Parameters:
266 -- A Pl/Sql record structure.
267 --
268 -- Post Success:
269 -- Processing continues.
270 --
271 -- Post Failure:
272 -- If an error has occurred, an error message and exception will be raised
273 -- but not handled.
274 --
275 -- Developer Implementation Notes:
276 -- Any post-processing required after the delete dml is issued should be
280 -- Access Status:
277 -- coded within this procedure. It is important to note that any 3rd party
278 -- maintenance should be reviewed before placing in this procedure.
279 --
281 -- Internal Row Handler Use Only.
282 --
283 -- {End Of Comments}
284 -- ----------------------------------------------------------------------------
285 Procedure post_delete
286 (p_rec in ame_gpi_shd.g_rec_type
287 ,p_effective_date in date
288 ,p_datetrack_mode in varchar2
289 ,p_validation_start_date in date
290 ,p_validation_end_date in date
291 ) is
292 --
293 l_proc varchar2(72) := g_package||'post_delete';
294 --
295 Begin
296 hr_utility.set_location('Entering:'||l_proc, 5);
297 begin
298 --
299 ame_gpi_rkd.after_delete
300 (p_effective_date
301 => p_effective_date
302 ,p_datetrack_mode
303 => p_datetrack_mode
304 ,p_validation_start_date
305 => p_validation_start_date
306 ,p_validation_end_date
307 => p_validation_end_date
308 ,p_approval_group_item_id
309 => p_rec.approval_group_item_id
310 ,p_start_date
311 => p_rec.start_date
312 ,p_end_date
313 => p_rec.end_date
314 ,p_approval_group_id_o
315 => ame_gpi_shd.g_old_rec.approval_group_id
316 ,p_parameter_name_o
317 => ame_gpi_shd.g_old_rec.parameter_name
318 ,p_parameter_o
319 => ame_gpi_shd.g_old_rec.parameter
320 ,p_order_number_o
321 => ame_gpi_shd.g_old_rec.order_number
322 ,p_start_date_o
323 => ame_gpi_shd.g_old_rec.start_date
324 ,p_end_date_o
325 => ame_gpi_shd.g_old_rec.end_date
326 ,p_security_group_id_o
327 => ame_gpi_shd.g_old_rec.security_group_id
328 ,p_object_version_number_o
329 => ame_gpi_shd.g_old_rec.object_version_number
330 );
331 --
332 exception
333 --
334 when hr_api.cannot_find_prog_unit then
335 --
336 hr_api.cannot_find_prog_unit_error
337 (p_module_name => 'AME_APPROVAL_GROUP_ITEMS'
338 ,p_hook_type => 'AD');
339 --
340 end;
341 --
342 hr_utility.set_location(' Leaving:'||l_proc, 10);
343 End post_delete;
344 --
348 Procedure del
345 -- ----------------------------------------------------------------------------
346 -- |---------------------------------< del >----------------------------------|
347 -- ----------------------------------------------------------------------------
349 (p_effective_date in date
350 ,p_datetrack_mode in varchar2
354 l_proc varchar2(72) := g_package||'del';
351 ,p_rec in out nocopy ame_gpi_shd.g_rec_type
352 ) is
353 --
355 l_validation_start_date date;
356 l_validation_end_date date;
357 --
358 Begin
364 --
359 hr_utility.set_location('Entering:'||l_proc, 5);
360 --
361 -- Ensure that the DateTrack delete mode is valid
362 --
363 dt_api.validate_dt_del_mode(p_datetrack_mode => p_datetrack_mode);
365 -- We must lock the row which we need to delete.
366 --
367 ame_gpi_shd.lck
368 (p_effective_date => p_effective_date
372 ,p_validation_start_date => l_validation_start_date
369 ,p_datetrack_mode => p_datetrack_mode
370 ,p_approval_group_item_id => p_rec.approval_group_item_id
371 ,p_object_version_number => p_rec.object_version_number
373 ,p_validation_end_date => l_validation_end_date
374 );
375 --
376 -- Call the supporting delete validate operation
377 --
378 ame_gpi_bus.delete_validate
379 (p_rec => p_rec
380 ,p_effective_date => p_effective_date
381 ,p_datetrack_mode => p_datetrack_mode
382 ,p_validation_start_date => l_validation_start_date
383 ,p_validation_end_date => l_validation_end_date
384 );
385 --
386 -- Call to raise any errors on multi-message list
387 hr_multi_message.end_validation_set;
388 --
389 -- Call the supporting pre-delete operation
390 --
391 ame_gpi_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
396 ,p_validation_end_date => l_validation_end_date
397 );
398 --
399 -- Delete the row.
400 --
401 ame_gpi_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
406 ,p_validation_end_date => l_validation_end_date
407 );
408 -- Call the supporting post-delete operation
409 --
410 ame_gpi_del.post_delete
411 (p_rec => p_rec
415 ,p_validation_end_date => l_validation_end_date
412 ,p_effective_date => p_effective_date
413 ,p_datetrack_mode => p_datetrack_mode
414 ,p_validation_start_date => l_validation_start_date
416 );
417 --
418 -- Call to raise any errors on multi-message list
419 hr_multi_message.end_validation_set;
420 --
421 hr_utility.set_location(' Leaving:'||l_proc, 5);
422 End del;
423 --
424 -- ----------------------------------------------------------------------------
425 -- |--------------------------------< del >-----------------------------------|
426 -- ----------------------------------------------------------------------------
427 Procedure del
428 (p_effective_date in date
429 ,p_datetrack_mode in varchar2
430 ,p_approval_group_item_id in number
431 ,p_object_version_number in out nocopy number
432 ,p_start_date out nocopy date
433 ,p_end_date out nocopy date
434 ) is
435 --
436 l_rec ame_gpi_shd.g_rec_type;
437 l_proc varchar2(72) := g_package||'del';
438 --
439 Begin
440 hr_utility.set_location('Entering:'||l_proc, 5);
441 --
442 -- As the delete procedure accepts a plsql record structure we do need to
443 -- convert the arguments into the record structure.
444 -- We don't need to call the supplied conversion argument routine as we
445 -- only need a few attributes.
446 --
447 l_rec.approval_group_item_id := p_approval_group_item_id;
448 l_rec.start_date := p_start_date;
449 l_rec.end_date := p_end_date;
450 l_rec.object_version_number := p_object_version_number;
451 --
452 -- Having converted the arguments into the ame_gpi_rec
453 -- plsql record structure we must call the corresponding entity
454 -- business process
455 --
456 ame_gpi_del.del
457 (p_effective_date
458 ,p_datetrack_mode
459 ,l_rec
460 );
461 --
462 --
463 -- Set the out arguments
464 --
465 p_object_version_number := l_rec.object_version_number;
466 p_start_date := l_rec.start_date;
467 p_end_date := l_rec.end_date;
468 --
469 hr_utility.set_location(' Leaving:'||l_proc, 10);
470 End del;
471 --
472 end ame_gpi_del;
[Home] [Help]