1 Package Body ame_itu_upd as
2 /* $Header: amiturhi.pkb 120.6 2006/10/05 16:11:40 pvelugul noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' ame_itu_upd.'; -- Global package name
9 --
10 -- ----------------------------------------------------------------------------
11 -- |----------------------------< dt_update_dml >-----------------------------|
12 -- ----------------------------------------------------------------------------
13 -- {Start Of Comments}
14 --
15 -- Description:
16 -- This procedure controls the execution of dml from the datetrack mode
17 -- of CORRECTION only. It is important to note that the object version
18 -- number is only increment by 1 because the datetrack correction is
19 -- soley for one datetracked row.
20 -- This procedure controls the actual dml update logic. The functions of
21 -- this procedure are as follows:
22 -- 1) Get the next object_version_number.
23 -- 2) To set and unset the g_api_dml status as required (as we are about to
24 -- perform dml).
25 -- 3) To update the specified row in the schema using the primary key in
26 -- the predicates.
27 -- 4) To trap any constraint violations that may have occurred.
28 -- 5) To raise any other errors.
29 --
30 -- Prerequisites:
31 -- This is an internal private procedure which must be called from the
32 -- update_dml procedure.
33 --
34 -- In Parameters:
35 -- A Pl/Sql record structure.
36 --
37 -- Post Success:
38 -- The specified row will be updated in the schema.
39 --
40 -- Post Failure:
41 -- On the update dml failure it is important to note that we always reset the
42 -- g_api_dml status to false.
43 -- If a check or unique integrity constraint violation is raised the
44 -- constraint_error procedure will be called.
45 -- If any other error is reported, the error will be raised after the
46 -- g_api_dml status is reset.
47 --
48 -- Developer Implementation Notes:
49 -- The update 'set' arguments list should be modified if any of your
50 -- attributes are not updateable.
51 --
52 -- Access Status:
53 -- Internal Row Handler Use Only.
54 --
55 -- {End Of Comments}
56 -- ----------------------------------------------------------------------------
57 Procedure dt_update_dml
58 (p_rec in out nocopy ame_itu_shd.g_rec_type
59 ,p_effective_date in date
60 ,p_datetrack_mode in varchar2
61 ,p_validation_start_date in date
62 ,p_validation_end_date in date
63 ) is
64 --
65 l_proc varchar2(72) := g_package||'dt_update_dml';
66 --
67 Begin
68 hr_utility.set_location('Entering:'||l_proc, 5);
69 --
70 If (p_datetrack_mode = hr_api.g_correction) then
71 hr_utility.set_location(l_proc, 10);
72 --
73 -- Because we are updating a row we must get the next object
74 -- version number.
75 --
76 p_rec.object_version_number :=
77 ame_itu_shd.get_object_version_number
78 (p_item_class_id => p_rec.item_class_id
79 ,p_application_id => p_rec.application_id
80 );
81 --
82 --
83 --
84 -- Update the ame_item_class_usages Row
85 --
86 update ame_item_class_usages
87 set
88 application_id = p_rec.application_id
89 ,item_class_id = p_rec.item_class_id
90 ,item_id_query = p_rec.item_id_query
91 ,item_class_order_number = p_rec.item_class_order_number
92 ,item_class_par_mode = p_rec.item_class_par_mode
93 ,item_class_sublist_mode = p_rec.item_class_sublist_mode
94 ,object_version_number = p_rec.object_version_number
95 where item_class_id = p_rec.item_class_id
96 and application_id = p_rec.application_id
97 and start_date = p_validation_start_date
98 and ((p_validation_end_date is null and end_date is null) or
99 (end_date = p_validation_end_date));
100 --
101 --
102 --
103 -- Set the effective start and end dates
104 --
105 p_rec.start_date := p_validation_start_date;
106 p_rec.end_date := p_validation_end_date;
107 End If;
108 --
109 hr_utility.set_location(' Leaving:'||l_proc, 15);
110 Exception
111 When hr_api.check_integrity_violated Then
112 -- A check constraint has been violated
113 --
114 ame_itu_shd.constraint_error
115 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
116 When hr_api.unique_integrity_violated Then
117 -- Unique integrity has been violated
118 --
119 ame_itu_shd.constraint_error
120 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
121 When Others Then
122 --
123 Raise;
124 End dt_update_dml;
125 --
126 -- ----------------------------------------------------------------------------
127 -- |------------------------------< update_dml >------------------------------|
128 -- ----------------------------------------------------------------------------
129 -- {Start Of Comments}
130 --
131 -- Description:
132 -- This procedure calls the dt_update_dml control logic which handles
133 -- the actual datetrack dml.
134 --
135 -- Prerequisites:
136 -- This is an internal private procedure which must be called from the upd
137 -- procedure.
138 --
139 -- In Parameters:
140 -- A Pl/Sql record structre.
141 --
142 -- Post Success:
143 -- Processing contines.
144 --
145 -- Post Failure:
146 -- No specific error handling is required within this procedure.
147 --
148 -- Developer Implementation Notes:
149 -- The update 'set' arguments list should be modified if any of your
150 -- attributes are not updateable.
151 --
152 -- Access Status:
153 -- Internal Row Handler Use Only.
154 --
155 -- {End Of Comments}
156 -- ----------------------------------------------------------------------------
157 Procedure update_dml
158 (p_rec in out nocopy ame_itu_shd.g_rec_type
159 ,p_effective_date in date
160 ,p_datetrack_mode in varchar2
161 ,p_validation_start_date in date
162 ,p_validation_end_date in date
163 ) is
164 --
165 l_proc varchar2(72) := g_package||'update_dml';
166 --
167 Begin
168 hr_utility.set_location('Entering:'||l_proc, 5);
169 --
170 ame_itu_upd.dt_update_dml
171 (p_rec => p_rec
172 ,p_effective_date => p_effective_date
173 ,p_datetrack_mode => p_datetrack_mode
174 ,p_validation_start_date => p_validation_start_date
175 ,p_validation_end_date => p_validation_end_date
176 );
177 --
178 hr_utility.set_location(' Leaving:'||l_proc, 10);
179 End update_dml;
180 --
181 -- ----------------------------------------------------------------------------
182 -- |----------------------------< dt_pre_update >-----------------------------|
183 -- ----------------------------------------------------------------------------
184 -- {Start Of Comments}
185 --
186 -- Description:
187 -- The dt_pre_update procedure controls the execution
188 -- of dml for the datetrack modes of: UPDATE, UPDATE_OVERRIDE
189 -- and UPDATE_CHANGE_INSERT only. The execution required is as
190 -- follows:
191 --
192 -- 1) Providing the datetrack update mode is not 'CORRECTION'
193 -- then set the effective end date of the current row (this
194 -- will be the validation_start_date - 1).
195 -- 2) If the datetrack mode is 'UPDATE_OVERRIDE' then call the
196 -- corresponding delete_dml process to delete any future rows
197 -- where the effective_start_date is greater than or equal to
198 -- the validation_start_date.
199 -- 3) Call the insert_dml process to insert the new updated row
200 -- details.
201 --
202 -- Prerequisites:
203 -- This is an internal procedure which is called from the
204 -- pre_update procedure.
205 --
206 -- In Parameters:
207 --
208 -- Post Success:
209 -- Processing continues.
210 --
211 -- Post Failure:
212 -- If an error has occurred, an error message and exception will be raised
213 -- but not handled.
214 --
215 -- Developer Implementation Notes:
216 -- This is an internal procedure which is required by Datetrack. Don't
217 -- remove or modify.
218 --
219 -- Access Status:
220 -- Internal Row Handler Use Only.
221 --
222 -- {End Of Comments}
223 -- ----------------------------------------------------------------------------
224 Procedure dt_pre_update
225 (p_rec in out nocopy ame_itu_shd.g_rec_type
226 ,p_effective_date in date
227 ,p_datetrack_mode in varchar2
228 ,p_validation_start_date in date
229 ,p_validation_end_date in date
230 ) is
231 --
232 l_proc varchar2(72) := g_package||'dt_pre_update';
233 l_dummy_version_number number;
234 --
235 Begin
236 hr_utility.set_location('Entering:'||l_proc, 5);
237 If (p_datetrack_mode <> hr_api.g_correction) then
238 --
239 -- Update the current effective end date
240 --
241 ame_itu_shd.upd_effective_end_date
242 (p_effective_date => p_effective_date
243 ,p_item_class_id => p_rec.item_class_id
244 ,p_application_id => p_rec.application_id
245 ,p_new_effective_end_date => p_validation_start_date
246 ,p_validation_start_date => p_validation_start_date
247 ,p_validation_end_date => p_validation_end_date
248 ,p_object_version_number => l_dummy_version_number
249 );
250 --
251 If (p_datetrack_mode = hr_api.g_update_override) then
252 --
253 -- As the datetrack mode is 'UPDATE_OVERRIDE' then we must
254 -- delete any future rows
255 --
256 ame_itu_del.delete_dml
257 (p_rec => p_rec
258 ,p_effective_date => p_effective_date
259 ,p_datetrack_mode => p_datetrack_mode
260 ,p_validation_start_date => p_validation_start_date
261 ,p_validation_end_date => p_validation_end_date
262 );
263 End If;
264 --
265 -- We must now insert the updated row
266 --
267 ame_itu_ins.insert_dml
268 (p_rec => p_rec
269 ,p_effective_date => p_effective_date
270 ,p_datetrack_mode => p_datetrack_mode
271 ,p_validation_start_date => p_validation_start_date
272 ,p_validation_end_date => p_validation_end_date
273 );
274 End If;
275 hr_utility.set_location(' Leaving:'||l_proc, 20);
276 End dt_pre_update;
277 --
278 -- ----------------------------------------------------------------------------
279 -- |------------------------------< pre_update >------------------------------|
280 -- ----------------------------------------------------------------------------
281 -- {Start Of Comments}
282 --
283 -- Description:
284 -- This private procedure contains any processing which is required before
285 -- the update dml.
286 --
287 -- Prerequisites:
288 -- This is an internal procedure which is called from the upd procedure.
289 --
290 -- In Parameters:
291 -- A Pl/Sql record structure.
292 --
293 -- Post Success:
294 -- Processing continues.
295 --
296 -- Post Failure:
297 -- If an error has occurred, an error message and exception will be raised
298 -- but not handled.
299 -- Developer Implementation Notes:
300 -- Any pre-processing required before the update dml is issued should be
301 -- coded within this procedure. It is important to note that any 3rd party
302 -- maintenance should be reviewed before placing in this procedure. The call
303 -- to the dt_update_dml procedure should NOT be removed.
304 --
305 -- Access Status:
306 -- Internal Row Handler Use Only.
307 --
308 -- {End Of Comments}
309 -- ----------------------------------------------------------------------------
310 Procedure pre_update
311 (p_rec in out nocopy ame_itu_shd.g_rec_type
312 ,p_effective_date in date
313 ,p_datetrack_mode in varchar2
314 ,p_validation_start_date in date
315 ,p_validation_end_date in date
316 ) is
317 --
318 l_proc varchar2(72) := g_package||'pre_update';
319 --
320 Begin
321 hr_utility.set_location('Entering:'||l_proc, 5);
322 --
323 --
324 --
325 dt_pre_update
326 (p_rec => p_rec
327 ,p_effective_date => p_effective_date
328 ,p_datetrack_mode => p_datetrack_mode
329 ,p_validation_start_date => p_validation_start_date
330 ,p_validation_end_date => p_validation_end_date
331 );
332 --
333 hr_utility.set_location(' Leaving:'||l_proc, 10);
334 End pre_update;
335 --
336 -- ----------------------------------------------------------------------------
337 -- |----------------------------< post_update >-------------------------------|
338 -- ----------------------------------------------------------------------------
339 -- {Start Of Comments}
340 --
341 -- Description:
342 -- This private procedure contains any processing which is required after
343 -- the update dml.
344 --
345 -- Prerequisites:
346 -- This is an internal procedure which is called from the upd procedure.
347 --
348 -- In Parameters:
349 -- A Pl/Sql record structure.
350 --
351 -- Post Success:
352 -- Processing continues.
353 --
354 -- Post Failure:
355 -- If an error has occurred, an error message and exception will be raised
356 -- but not handled.
357 --
358 -- Developer Implementation Notes:
359 -- Any post-processing required after the update dml is issued should be
360 -- coded within this procedure. It is important to note that any 3rd party
361 -- maintenance should be reviewed before placing in this procedure.
362 --
363 -- Access Status:
364 -- Internal Row Handler Use Only.
365 --
366 -- {End Of Comments}
367 -- ----------------------------------------------------------------------------
368 Procedure post_update
369 (p_rec in ame_itu_shd.g_rec_type
370 ,p_effective_date in date
371 ,p_datetrack_mode in varchar2
372 ,p_validation_start_date in date
373 ,p_validation_end_date in date
374 ) is
375 --
376 l_proc varchar2(72) := g_package||'post_update';
377 --
378 Begin
379 hr_utility.set_location('Entering:'||l_proc, 5);
380 begin
381 --
382 ame_itu_rku.after_update
383 (p_effective_date => p_effective_date
384 ,p_datetrack_mode => p_datetrack_mode
385 ,p_validation_start_date => p_validation_start_date
386 ,p_validation_end_date => p_validation_end_date
387 ,p_application_id => p_rec.application_id
388 ,p_item_class_id => p_rec.item_class_id
389 ,p_item_id_query => p_rec.item_id_query
390 ,p_item_class_order_number => p_rec.item_class_order_number
391 ,p_item_class_par_mode => p_rec.item_class_par_mode
392 ,p_item_class_sublist_mode => p_rec.item_class_sublist_mode
393 ,p_start_date => p_rec.start_date
394 ,p_end_date => p_rec.end_date
395 ,p_object_version_number => p_rec.object_version_number
396 ,p_item_id_query_o => ame_itu_shd.g_old_rec.item_id_query
397 ,p_item_class_order_number_o => ame_itu_shd.g_old_rec.item_class_order_number
398 ,p_item_class_par_mode_o => ame_itu_shd.g_old_rec.item_class_par_mode
399 ,p_item_class_sublist_mode_o => ame_itu_shd.g_old_rec.item_class_sublist_mode
400 ,p_start_date_o => ame_itu_shd.g_old_rec.start_date
401 ,p_end_date_o => ame_itu_shd.g_old_rec.end_date
402 ,p_object_version_number_o => ame_itu_shd.g_old_rec.object_version_number
403 );
404 --
405 exception
406 --
407 when hr_api.cannot_find_prog_unit then
408 --
409 hr_api.cannot_find_prog_unit_error
410 (p_module_name => 'AME_ITEM_CLASS_USAGES'
411 ,p_hook_type => 'AU');
412 --
413 end;
414 --
415 hr_utility.set_location(' Leaving:'||l_proc, 10);
416 End post_update;
417 --
418 -- ----------------------------------------------------------------------------
419 -- |-----------------------------< convert_defs >-----------------------------|
420 -- ----------------------------------------------------------------------------
421 -- {Start Of Comments}
422 --
423 -- Description:
424 -- The Convert_Defs procedure has one very important function:
425 -- It must return the record structure for the row with all system defaulted
426 -- values converted into its corresponding parameter value for update. When
427 -- we attempt to update a row through the Upd process , certain
428 -- parameters can be defaulted which enables flexibility in the calling of
429 -- the upd process (e.g. only attributes which need to be updated need to be
430 -- specified). For the upd process to determine which attributes
431 -- have NOT been specified we need to check if the parameter has a reserved
432 -- system default value. Therefore, for all parameters which have a
433 -- corresponding reserved system default mechanism specified we need to
434 -- check if a system default is being used. If a system default is being
435 -- used then we convert the defaulted value into its corresponding attribute
436 -- value held in the g_old_rec data structure.
437 --
438 -- Prerequisites:
439 -- This private function can only be called from the upd process.
440 --
441 -- In Parameters:
442 -- A Pl/Sql record structure.
443 --
444 -- Post Success:
445 -- The record structure will be returned with all system defaulted parameter
446 -- values converted into its current row attribute value.
447 --
448 -- Post Failure:
449 -- No direct error handling is required within this function. Any possible
450 -- errors within this procedure will be a PL/SQL value error due to
451 -- conversion of datatypes or data lengths.
452 --
453 -- Developer Implementation Notes:
454 -- None.
455 --
456 -- Access Status:
457 -- Internal Row Handler Use Only.
458 --
459 -- {End Of Comments}
460 -- ----------------------------------------------------------------------------
461 Procedure convert_defs
462 (p_rec in out nocopy ame_itu_shd.g_rec_type
463 ) is
464 --
465 Begin
466 --
467 -- We must now examine each argument value in the
468 -- p_rec plsql record structure
469 -- to see if a system default is being used. If a system default
470 -- is being used then we must set to the 'current' argument value.
471 --
472 If (p_rec.item_id_query = hr_api.g_varchar2) then
473 p_rec.item_id_query :=
474 ame_itu_shd.g_old_rec.item_id_query;
475 End If;
476 If (p_rec.item_class_order_number = hr_api.g_number) then
477 p_rec.item_class_order_number :=
478 ame_itu_shd.g_old_rec.item_class_order_number;
479 End If;
480 If (p_rec.item_class_par_mode = hr_api.g_varchar2) then
481 p_rec.item_class_par_mode :=
482 ame_itu_shd.g_old_rec.item_class_par_mode;
483 End If;
484 If (p_rec.item_class_sublist_mode = hr_api.g_varchar2) then
485 p_rec.item_class_sublist_mode :=
486 ame_itu_shd.g_old_rec.item_class_sublist_mode;
487 End If;
488 --
489 End convert_defs;
490 --
491 -- ----------------------------------------------------------------------------
492 -- |---------------------------------< upd >----------------------------------|
493 -- ----------------------------------------------------------------------------
494 Procedure upd
495 (p_effective_date in date
496 ,p_datetrack_mode in varchar2
497 ,p_rec in out nocopy ame_itu_shd.g_rec_type
498 ) is
499 --
500 l_proc varchar2(72) := g_package||'upd';
501 l_validation_start_date date;
502 l_validation_end_date date;
503 --
504 Begin
505 hr_utility.set_location('Entering:'||l_proc, 5);
506 --
507 -- Ensure that the DateTrack update mode is valid
508 --
509 dt_api.validate_dt_upd_mode(p_datetrack_mode => p_datetrack_mode);
510 --
511 -- We must lock the row which we need to update.
512 --
513 ame_itu_shd.lck
514 (p_effective_date => p_effective_date
515 ,p_datetrack_mode => p_datetrack_mode
516 ,p_item_class_id => p_rec.item_class_id
517 ,p_application_id => p_rec.application_id
518 ,p_object_version_number => p_rec.object_version_number
519 ,p_validation_start_date => l_validation_start_date
520 ,p_validation_end_date => l_validation_end_date
521 );
522 --
523 -- 1. During an update system defaults are used to determine if
524 -- arguments have been defaulted or not. We must therefore
525 -- derive the full record structure values to be updated.
526 --
527 -- 2. Call the supporting update validate operations.
528 --
529 ame_itu_upd.convert_defs(p_rec);
530 --
531 ame_itu_bus.update_validate
532 (p_rec => p_rec
533 ,p_effective_date => p_effective_date
534 ,p_datetrack_mode => p_datetrack_mode
535 ,p_validation_start_date => l_validation_start_date
536 ,p_validation_end_date => l_validation_end_date
537 );
538 --
539 -- Call to raise any errors on multi-message list
540 hr_multi_message.end_validation_set;
541 --
542 -- Call the supporting pre-update operation
543 --
544 pre_update
545 (p_rec => p_rec
546 ,p_effective_date => p_effective_date
547 ,p_datetrack_mode => p_datetrack_mode
548 ,p_validation_start_date => l_validation_start_date
549 ,p_validation_end_date => l_validation_end_date
550 );
551 --
552 -- Update the row.
553 --
554 update_dml
555 (p_rec => p_rec
556 ,p_effective_date => p_effective_date
557 ,p_datetrack_mode => p_datetrack_mode
558 ,p_validation_start_date => l_validation_start_date
559 ,p_validation_end_date => l_validation_end_date
560 );
561 --
562 -- Call the supporting post-update operation
563 --
564 post_update
565 (p_rec => p_rec
566 ,p_effective_date => p_effective_date
567 ,p_datetrack_mode => p_datetrack_mode
568 ,p_validation_start_date => l_validation_start_date
569 ,p_validation_end_date => l_validation_end_date
570 );
571 --
572 -- Call to raise any errors on multi-message list
573 hr_multi_message.end_validation_set;
574 End upd;
575 --
576 -- ----------------------------------------------------------------------------
577 -- |------------------------------< upd >-------------------------------------|
578 -- ----------------------------------------------------------------------------
579 Procedure upd
580 (p_effective_date in date
581 ,p_datetrack_mode in varchar2
582 ,p_application_id in number
583 ,p_item_class_id in number
584 ,p_object_version_number in out nocopy number
585 ,p_item_id_query in varchar2 default hr_api.g_varchar2
586 ,p_item_class_order_number in number default hr_api.g_number
587 ,p_item_class_par_mode in varchar2 default hr_api.g_varchar2
588 ,p_item_class_sublist_mode in varchar2 default hr_api.g_varchar2
589 ,p_start_date out nocopy date
590 ,p_end_date out nocopy date
591 ) is
592 --
593 l_rec ame_itu_shd.g_rec_type;
594 l_proc varchar2(72) := g_package||'upd';
595 --
596 Begin
597 hr_utility.set_location('Entering:'||l_proc, 5);
598 --
599 -- Call conversion function to turn arguments into the
600 -- l_rec structure.
601 --
602 l_rec :=
603 ame_itu_shd.convert_args
604 (p_application_id
605 ,p_item_class_id
606 ,p_item_id_query
607 ,p_item_class_order_number
608 ,p_item_class_par_mode
609 ,p_item_class_sublist_mode
610 ,null
611 ,null
612 ,p_object_version_number
613 );
614 --
615 -- Having converted the arguments into the
616 -- plsql record structure we call the corresponding record
617 -- business process.
618 --
619 ame_itu_upd.upd
620 (p_effective_date
621 ,p_datetrack_mode
622 ,l_rec
623 );
624 --
625 -- Set the out parameters
626 --
627 p_object_version_number := l_rec.object_version_number;
628 p_start_date := l_rec.start_date;
629 p_end_date := l_rec.end_date;
630 --
631 --
632 hr_utility.set_location(' Leaving:'||l_proc, 10);
633 End upd;
634 --
635 end ame_itu_upd;
[Home] [Help]