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