DBA Data[Home] [Help]

PACKAGE BODY: APPS.AME_ACF_DEL

Source


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