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