1 Package Body ame_rlu_del as
2 /* $Header: amrlurhi.pkb 120.5 2005/11/22 03:19 santosin noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' ame_rlu_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_rlu_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_rule_usages
72 where rule_id = p_rec.rule_id
73 and item_id = p_rec.item_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_rule_usages
84 where rule_id = p_rec.rule_id
85 and item_id = p_rec.item_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_rlu_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_rlu_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_rlu_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_rlu_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_rlu_shd.upd_end_date
182 (p_effective_date => p_effective_date
183 ,p_rule_id => p_rec.rule_id
184 ,p_item_id => p_rec.item_id
185 ,p_old_start_date => p_rec.old_start_date
186 ,p_new_end_date => p_rec.end_date
187 ,p_object_version_number => p_rec.object_version_number
188 );
189 Else
190 p_rec.start_date := null;
191 p_rec.end_date := null;
192 End If;
193 hr_utility.set_location(' Leaving:'||l_proc, 10);
194 End dt_pre_delete;
195 --
196 -- ----------------------------------------------------------------------------
197 -- |------------------------------< pre_delete >------------------------------|
198 -- ----------------------------------------------------------------------------
199 -- {Start Of Comments}
200 --
201 -- Description:
202 -- This private procedure contains any processing which is required before
203 -- the delete dml.
204 --
205 -- Prerequisites:
206 -- This is an internal procedure which is called from the del procedure.
207 --
208 -- In Parameters:
209 -- A Pl/Sql record structure.
210 --
211 -- Post Success:
212 -- Processing continues.
213 --
214 -- Post Failure:
215 -- If an error has occurred, an error message and exception will be raised
216 -- but not handled.
217 --
218 -- Developer Implementation Notes:
219 -- Any pre-processing required before the delete dml is issued should be
220 -- coded within this procedure. It is important to note that any 3rd party
221 -- maintenance should be reviewed before placing in this procedure. The call
222 -- to the dt_delete_dml procedure should NOT be removed.
223 --
224 -- Access Status:
225 -- Internal Row Handler Use Only.
226 --
227 -- {End Of Comments}
228 -- ----------------------------------------------------------------------------
229 Procedure pre_delete
230 (p_rec in out nocopy ame_rlu_shd.g_rec_type
231 ,p_effective_date in date
232 ,p_datetrack_mode in varchar2
233 ,p_validation_start_date in date
234 ,p_validation_end_date in date
235 ) is
236 --
237 l_proc varchar2(72) := g_package||'pre_delete';
238 --
239 --
240 --
241 Begin
242 hr_utility.set_location('Entering:'||l_proc, 5);
243 --
244 --
245 --
246 ame_rlu_del.dt_pre_delete
247 (p_rec => p_rec
248 ,p_effective_date => p_effective_date
249 ,p_datetrack_mode => p_datetrack_mode
250 ,p_validation_start_date => p_validation_start_date
251 ,p_validation_end_date => p_validation_end_date
252 );
253 --
254 hr_utility.set_location(' Leaving:'||l_proc, 10);
255 End pre_delete;
256 --
257 -- ----------------------------------------------------------------------------
258 -- |----------------------------< post_delete >-------------------------------|
259 -- ----------------------------------------------------------------------------
260 -- {Start Of Comments}
261 --
262 -- Description:
263 -- This private procedure contains any processing which is required after
264 -- the delete dml.
265 --
266 -- Prerequisites:
267 -- This is an internal procedure which is called from the del procedure.
268 --
269 -- In Parameters:
270 -- A Pl/Sql record structure.
271 --
272 -- Post Success:
273 -- Processing continues.
274 --
275 -- Post Failure:
276 -- If an error has occurred, an error message and exception will be raised
277 -- but not handled.
278 --
279 -- Developer Implementation Notes:
280 -- Any post-processing required after the delete dml is issued should be
281 -- coded within this procedure. It is important to note that any 3rd party
282 -- maintenance should be reviewed before placing in this procedure.
283 --
284 -- Access Status:
285 -- Internal Row Handler Use Only.
286 --
287 -- {End Of Comments}
288 -- ----------------------------------------------------------------------------
289 Procedure post_delete
290 (p_rec in ame_rlu_shd.g_rec_type
291 ,p_effective_date in date
292 ,p_datetrack_mode in varchar2
293 ,p_validation_start_date in date
294 ,p_validation_end_date in date
295 ) is
296 --
297 l_proc varchar2(72) := g_package||'post_delete';
298 --
299 Begin
300 hr_utility.set_location('Entering:'||l_proc, 5);
301 begin
302 --
303 ame_rlu_rkd.after_delete
304 (p_effective_date
305 => p_effective_date
306 ,p_datetrack_mode
307 => p_datetrack_mode
308 ,p_validation_start_date
309 => p_validation_start_date
310 ,p_validation_end_date
311 => p_validation_end_date
312 ,p_item_id
313 => p_rec.item_id
314 ,p_rule_id
315 => p_rec.rule_id
316 ,p_start_date
317 => p_rec.start_date
318 ,p_end_date
319 => p_rec.end_date
320 ,p_usage_type_o
321 => ame_rlu_shd.g_old_rec.usage_type
322 ,p_start_date_o
323 => ame_rlu_shd.g_old_rec.start_date
324 ,p_end_date_o
325 => ame_rlu_shd.g_old_rec.end_date
326 ,p_security_group_id_o
327 => ame_rlu_shd.g_old_rec.security_group_id
328 ,p_priority_o
329 => ame_rlu_shd.g_old_rec.priority
330 ,p_approver_category_o
331 => ame_rlu_shd.g_old_rec.approver_category
332 ,p_object_version_number_o
333 => ame_rlu_shd.g_old_rec.object_version_number
334 );
335 --
336 exception
337 --
338 when hr_api.cannot_find_prog_unit then
339 --
340 hr_api.cannot_find_prog_unit_error
341 (p_module_name => 'AME_RULE_USAGES'
342 ,p_hook_type => 'AD');
343 --
344 end;
345 --
346 hr_utility.set_location(' Leaving:'||l_proc, 10);
347 End post_delete;
348 --
349 -- ----------------------------------------------------------------------------
350 -- |---------------------------------< del >----------------------------------|
351 -- ----------------------------------------------------------------------------
352 Procedure del
353 (p_effective_date in date
354 ,p_datetrack_mode in varchar2
355 ,p_rec in out nocopy ame_rlu_shd.g_rec_type
356 ) is
357 --
358 l_proc varchar2(72) := g_package||'del';
359 l_validation_start_date date;
360 l_validation_end_date date;
361 --
362 Begin
363 hr_utility.set_location('Entering:'||l_proc, 5);
364 --
365 -- Ensure that the DateTrack delete mode is valid
366 --
367 dt_api.validate_dt_del_mode(p_datetrack_mode => p_datetrack_mode);
368 --
369 -- We must lock the row which we need to delete.
370 --
371 ame_rlu_shd.lck
372 (p_effective_date => p_effective_date
373 ,p_datetrack_mode => p_datetrack_mode
374 ,p_rule_id => p_rec.rule_id
375 ,p_item_id => p_rec.item_id
376 ,p_old_start_date => p_rec.old_start_date
377 ,p_object_version_number => p_rec.object_version_number
378 ,p_validation_start_date => l_validation_start_date
379 ,p_validation_end_date => l_validation_end_date
380 );
381 --
382 -- Call the supporting delete validate operation
383 --
384 ame_rlu_bus.delete_validate
385 (p_rec => p_rec
386 ,p_effective_date => p_effective_date
387 ,p_datetrack_mode => p_datetrack_mode
388 ,p_validation_start_date => l_validation_start_date
389 ,p_validation_end_date => l_validation_end_date
390 );
391 --
392 -- Call to raise any errors on multi-message list
393 hr_multi_message.end_validation_set;
394 --
395 -- Call the supporting pre-delete operation
396 --
397 ame_rlu_del.pre_delete
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 --
405 -- Delete the row.
406 --
407 ame_rlu_del.delete_dml
408 (p_rec => p_rec
409 ,p_effective_date => p_effective_date
410 ,p_datetrack_mode => p_datetrack_mode
411 ,p_validation_start_date => l_validation_start_date
412 ,p_validation_end_date => l_validation_end_date
413 );
414 -- Call the supporting post-delete operation
415 --
416 ame_rlu_del.post_delete
417 (p_rec => p_rec
418 ,p_effective_date => p_effective_date
419 ,p_datetrack_mode => p_datetrack_mode
420 ,p_validation_start_date => l_validation_start_date
421 ,p_validation_end_date => l_validation_end_date
422 );
423 --
424 -- Call to raise any errors on multi-message list
425 hr_multi_message.end_validation_set;
426 --
427 hr_utility.set_location(' Leaving:'||l_proc, 5);
428 End del;
429 --
430 -- ----------------------------------------------------------------------------
431 -- |--------------------------------< del >-----------------------------------|
432 -- ----------------------------------------------------------------------------
433 Procedure del
434 (p_effective_date in date
435 ,p_datetrack_mode in varchar2
436 ,p_item_id in number
437 ,p_rule_id in number
438 ,p_object_version_number in out nocopy number
439 ,p_start_date in out nocopy date
440 ,p_end_date in out nocopy date
441 ) is
442 --
443 l_rec ame_rlu_shd.g_rec_type;
444 l_proc varchar2(72) := g_package||'del';
445 --
446 Begin
447 hr_utility.set_location('Entering:'||l_proc, 5);
448 --
449 -- As the delete procedure accepts a plsql record structure we do need to
450 -- convert the arguments into the record structure.
451 -- We don't need to call the supplied conversion argument routine as we
452 -- only need a few attributes.
453 --
454 l_rec.rule_id := p_rule_id;
455 l_rec.item_id := p_item_id;
456 l_rec.start_date := p_start_date;
457 l_rec.end_date := p_end_date;
458 l_rec.old_start_date := p_start_date;
459 l_rec.object_version_number := p_object_version_number;
460 --
461 -- Having converted the arguments into the ame_rlu_rec
462 -- plsql record structure we must call the corresponding entity
463 -- business process
464 --
465 ame_rlu_del.del
466 (p_effective_date
467 ,p_datetrack_mode
468 ,l_rec
469 );
470 --
471 --
472 -- Set the out arguments
473 --
474 p_object_version_number := l_rec.object_version_number;
475 p_start_date := l_rec.start_date;
476 p_end_date := l_rec.end_date;
477 --
478 hr_utility.set_location(' Leaving:'||l_proc, 10);
479 End del;
480 --
481 end ame_rlu_del;
[Home] [Help]