1 Package Body per_pgs_upd as
2 /* $Header: pepgsrhi.pkb 120.0 2005/05/31 14:12:49 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' per_pgs_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 per_pgs_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 dt_api.get_object_version_number
78 (p_base_table_name => 'per_grade_spines_f'
79 ,p_base_key_column => 'grade_spine_id'
80 ,p_base_key_value => p_rec.grade_spine_id
81 );
82 --
83 per_pgs_shd.g_api_dml := true; -- Set the api dml status
84 --
85 -- Update the per_grade_spines_f Row
86 --
87 update per_grade_spines_f
88 set
89 grade_spine_id = p_rec.grade_spine_id
90 ,business_group_id = p_rec.business_group_id
91 ,parent_spine_id = p_rec.parent_spine_id
92 ,grade_id = p_rec.grade_id
93 ,ceiling_step_id = p_rec.ceiling_step_id
94 ,starting_step = p_rec.starting_step
95 ,request_id = p_rec.request_id
96 ,program_application_id = p_rec.program_application_id
97 ,program_id = p_rec.program_id
98 ,program_update_date = p_rec.program_update_date
99 ,object_version_number = p_rec.object_version_number
100 where grade_spine_id = p_rec.grade_spine_id
101 and effective_start_date = p_validation_start_date
102 and effective_end_date = p_validation_end_date;
103 --
104 per_pgs_shd.g_api_dml := false; -- Unset the api dml status
105 --
106 -- Set the effective start and end dates
107 --
108 p_rec.effective_start_date := p_validation_start_date;
109 p_rec.effective_end_date := p_validation_end_date;
110 End If;
111 --
112 hr_utility.set_location(' Leaving:'||l_proc, 15);
113 Exception
114 When hr_api.check_integrity_violated Then
115 -- A check constraint has been violated
116 per_pgs_shd.g_api_dml := false; -- Unset the api dml status
117 per_pgs_shd.constraint_error
118 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
119 When hr_api.unique_integrity_violated Then
120 -- Unique integrity has been violated
121 per_pgs_shd.g_api_dml := false; -- Unset the api dml status
122 per_pgs_shd.constraint_error
123 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
124 When Others Then
125 per_pgs_shd.g_api_dml := false; -- Unset the api dml status
126 Raise;
127 End dt_update_dml;
128 --
129 -- ----------------------------------------------------------------------------
130 -- |------------------------------< update_dml >------------------------------|
131 -- ----------------------------------------------------------------------------
132 -- {Start Of Comments}
133 --
134 -- Description:
135 -- This procedure calls the dt_update_dml control logic which handles
136 -- the actual datetrack dml.
137 --
138 -- Prerequisites:
139 -- This is an internal private procedure which must be called from the upd
140 -- procedure.
141 --
142 -- In Parameters:
143 -- A Pl/Sql record structre.
144 --
145 -- Post Success:
146 -- Processing contines.
147 --
148 -- Post Failure:
149 -- No specific error handling is required within this procedure.
150 --
151 -- Developer Implementation Notes:
152 -- The update 'set' arguments list should be modified if any of your
153 -- attributes are not updateable.
154 --
155 -- Access Status:
156 -- Internal Row Handler Use Only.
157 --
158 -- {End Of Comments}
159 -- ----------------------------------------------------------------------------
160 Procedure update_dml
161 (p_rec in out nocopy per_pgs_shd.g_rec_type
162 ,p_effective_date in date
163 ,p_datetrack_mode in varchar2
164 ,p_validation_start_date in date
165 ,p_validation_end_date in date
166 ) is
167 --
168 l_proc varchar2(72) := g_package||'update_dml';
169 --
170 Begin
171 hr_utility.set_location('Entering:'||l_proc, 5);
172 --
173 per_pgs_upd.dt_update_dml
174 (p_rec => p_rec
175 ,p_effective_date => p_effective_date
176 ,p_datetrack_mode => p_datetrack_mode
177 ,p_validation_start_date => p_validation_start_date
178 ,p_validation_end_date => p_validation_end_date
179 );
180 --
181 hr_utility.set_location(' Leaving:'||l_proc, 10);
182 End update_dml;
183 --
184 -- ----------------------------------------------------------------------------
185 -- |----------------------------< dt_pre_update >-----------------------------|
186 -- ----------------------------------------------------------------------------
187 -- {Start Of Comments}
188 --
189 -- Description:
190 -- The dt_pre_update procedure controls the execution
191 -- of dml for the datetrack modes of: UPDATE, UPDATE_OVERRIDE
192 -- and UPDATE_CHANGE_INSERT only. The execution required is as
193 -- follows:
194 --
195 -- 1) Providing the datetrack update mode is not 'CORRECTION'
196 -- then set the effective end date of the current row (this
197 -- will be the validation_start_date - 1).
198 -- 2) If the datetrack mode is 'UPDATE_OVERRIDE' then call the
199 -- corresponding delete_dml process to delete any future rows
200 -- where the effective_start_date is greater than or equal to
201 -- the validation_start_date.
202 -- 3) Call the insert_dml process to insert the new updated row
203 -- details.
204 --
205 -- Prerequisites:
206 -- This is an internal procedure which is called from the
207 -- pre_update procedure.
208 --
209 -- In Parameters:
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 -- This is an internal procedure which is required by Datetrack. Don't
220 -- remove or modify.
221 --
222 -- Access Status:
223 -- Internal Row Handler Use Only.
224 --
225 -- {End Of Comments}
226 -- ----------------------------------------------------------------------------
227 Procedure dt_pre_update
228 (p_rec in out nocopy per_pgs_shd.g_rec_type
229 ,p_effective_date in date
230 ,p_datetrack_mode in varchar2
231 ,p_validation_start_date in date
232 ,p_validation_end_date in date
233 ) is
234 --
235 l_proc varchar2(72) := g_package||'dt_pre_update';
236 l_dummy_version_number number;
237 --
238 Begin
239 hr_utility.set_location('Entering:'||l_proc, 5);
240 If (p_datetrack_mode <> hr_api.g_correction) then
241 --
242 -- Update the current effective end date
243 --
244 per_pgs_shd.upd_effective_end_date
245 (p_effective_date => p_effective_date
246 ,p_base_key_value => p_rec.grade_spine_id
247 ,p_new_effective_end_date => (p_validation_start_date - 1)
248 ,p_validation_start_date => p_validation_start_date
249 ,p_validation_end_date => p_validation_end_date
250 ,p_object_version_number => l_dummy_version_number
251 );
252 --
253 If (p_datetrack_mode = hr_api.g_update_override) then
254 --
255 -- As the datetrack mode is 'UPDATE_OVERRIDE' then we must
256 -- delete any future rows
257 --
258 per_pgs_del.delete_dml
259 (p_rec => p_rec
260 ,p_effective_date => p_effective_date
261 ,p_datetrack_mode => p_datetrack_mode
262 ,p_validation_start_date => p_validation_start_date
263 ,p_validation_end_date => p_validation_end_date
264 );
265 End If;
266 --
267 -- We must now insert the updated row
268 --
269 per_pgs_ins.insert_dml
270 (p_rec => p_rec
271 ,p_effective_date => p_effective_date
272 ,p_datetrack_mode => p_datetrack_mode
273 ,p_validation_start_date => p_validation_start_date
274 ,p_validation_end_date => p_validation_end_date
275 );
276 End If;
277 hr_utility.set_location(' Leaving:'||l_proc, 20);
278 End dt_pre_update;
279 --
280 -- ----------------------------------------------------------------------------
281 -- |------------------------------< pre_update >------------------------------|
282 -- ----------------------------------------------------------------------------
283 -- {Start Of Comments}
284 --
285 -- Description:
286 -- This private procedure contains any processing which is required before
287 -- the update dml.
288 --
289 -- Prerequisites:
290 -- This is an internal procedure which is called from the upd procedure.
291 --
292 -- In Parameters:
293 -- A Pl/Sql record structure.
294 --
295 -- Post Success:
296 -- Processing continues.
297 --
298 -- Post Failure:
299 -- If an error has occurred, an error message and exception will be raised
300 -- but not handled.
301 -- Developer Implementation Notes:
302 -- Any pre-processing required before the update dml is issued should be
303 -- coded within this procedure. It is important to note that any 3rd party
304 -- maintenance should be reviewed before placing in this procedure. The call
305 -- to the dt_update_dml procedure should NOT be removed.
306 --
307 -- Access Status:
308 -- Internal Row Handler Use Only.
309 --
310 -- {End Of Comments}
311 -- ----------------------------------------------------------------------------
312 Procedure pre_update
313 (p_rec in out nocopy per_pgs_shd.g_rec_type
314 ,p_effective_date in date
315 ,p_datetrack_mode in varchar2
316 ,p_validation_start_date in date
317 ,p_validation_end_date in date
318 ) is
319 --
320 l_proc varchar2(72) := g_package||'pre_update';
321 --
322 Begin
323 hr_utility.set_location('Entering:'||l_proc, 5);
324 --
325 --
326 --
327 dt_pre_update
328 (p_rec => p_rec
329 ,p_effective_date => p_effective_date
330 ,p_datetrack_mode => p_datetrack_mode
331 ,p_validation_start_date => p_validation_start_date
332 ,p_validation_end_date => p_validation_end_date
333 );
334 --
335 hr_utility.set_location(' Leaving:'||l_proc, 10);
336 End pre_update;
337 --
338 -- ----------------------------------------------------------------------------
339 -- |----------------------------< post_update >-------------------------------|
340 -- ----------------------------------------------------------------------------
341 -- {Start Of Comments}
342 --
343 -- Description:
344 -- This private procedure contains any processing which is required after
345 -- the update dml.
346 --
347 -- Prerequisites:
348 -- This is an internal procedure which is called from the upd procedure.
349 --
350 -- In Parameters:
351 -- A Pl/Sql record structure.
352 --
353 -- Post Success:
354 -- Processing continues.
355 --
356 -- Post Failure:
357 -- If an error has occurred, an error message and exception will be raised
358 -- but not handled.
359 --
360 -- Developer Implementation Notes:
361 -- Any post-processing required after the update dml is issued should be
362 -- coded within this procedure. It is important to note that any 3rd party
363 -- maintenance should be reviewed before placing in this procedure.
364 --
365 -- Access Status:
366 -- Internal Row Handler Use Only.
367 --
368 -- {End Of Comments}
369 -- ----------------------------------------------------------------------------
370 Procedure post_update
371 (p_rec in per_pgs_shd.g_rec_type
372 ,p_effective_date in date
373 ,p_datetrack_mode in varchar2
374 ,p_validation_start_date in date
375 ,p_validation_end_date in date
376 ) is
377 --
378 l_proc varchar2(72) := g_package||'post_update';
379 --
380 Begin
381 hr_utility.set_location('Entering:'||l_proc, 5);
382 begin
383 --
384 per_pgs_rku.after_update
385 (p_effective_date
386 => p_effective_date
387 ,p_datetrack_mode
388 => p_datetrack_mode
389 ,p_validation_start_date
390 => p_validation_start_date
391 ,p_validation_end_date
392 => p_validation_end_date
393 ,p_grade_spine_id
394 => p_rec.grade_spine_id
395 ,p_effective_start_date
396 => p_rec.effective_start_date
397 ,p_effective_end_date
398 => p_rec.effective_end_date
399 ,p_business_group_id
400 => p_rec.business_group_id
401 ,p_parent_spine_id
402 => p_rec.parent_spine_id
403 ,p_grade_id
404 => p_rec.grade_id
405 ,p_ceiling_step_id
406 => p_rec.ceiling_step_id
407 ,p_starting_step
408 => p_rec.starting_step
409 ,p_request_id
410 => p_rec.request_id
411 ,p_program_application_id
412 => p_rec.program_application_id
413 ,p_program_id
414 => p_rec.program_id
415 ,p_program_update_date
416 => p_rec.program_update_date
417 ,p_object_version_number
418 => p_rec.object_version_number
419 ,p_effective_start_date_o
420 => per_pgs_shd.g_old_rec.effective_start_date
421 ,p_effective_end_date_o
422 => per_pgs_shd.g_old_rec.effective_end_date
423 ,p_business_group_id_o
424 => per_pgs_shd.g_old_rec.business_group_id
425 ,p_parent_spine_id_o
426 => per_pgs_shd.g_old_rec.parent_spine_id
427 ,p_grade_id_o
428 => per_pgs_shd.g_old_rec.grade_id
429 ,p_ceiling_step_id_o
430 => per_pgs_shd.g_old_rec.ceiling_step_id
431 ,p_request_id_o
432 => per_pgs_shd.g_old_rec.request_id
433 ,p_program_application_id_o
434 => per_pgs_shd.g_old_rec.program_application_id
435 ,p_program_id_o
436 => per_pgs_shd.g_old_rec.program_id
437 ,p_program_update_date_o
438 => per_pgs_shd.g_old_rec.program_update_date
439 ,p_object_version_number_o
440 => per_pgs_shd.g_old_rec.object_version_number
441 );
442 --
443 exception
444 --
445 when hr_api.cannot_find_prog_unit then
446 --
447 hr_api.cannot_find_prog_unit_error
448 (p_module_name => 'PER_GRADE_SPINES_F'
449 ,p_hook_type => 'AU');
450 --
451 end;
452 --
453 hr_utility.set_location(' Leaving:'||l_proc, 10);
454 End post_update;
455 --
456 -- ----------------------------------------------------------------------------
457 -- |-----------------------------< convert_defs >-----------------------------|
458 -- ----------------------------------------------------------------------------
459 -- {Start Of Comments}
460 --
461 -- Description:
462 -- The Convert_Defs procedure has one very important function:
463 -- It must return the record structure for the row with all system defaulted
464 -- values converted into its corresponding parameter value for update. When
465 -- we attempt to update a row through the Upd process , certain
466 -- parameters can be defaulted which enables flexibility in the calling of
467 -- the upd process (e.g. only attributes which need to be updated need to be
468 -- specified). For the upd process to determine which attributes
469 -- have NOT been specified we need to check if the parameter has a reserved
470 -- system default value. Therefore, for all parameters which have a
471 -- corresponding reserved system default mechanism specified we need to
472 -- check if a system default is being used. If a system default is being
473 -- used then we convert the defaulted value into its corresponding attribute
474 -- value held in the g_old_rec data structure.
475 --
476 -- Prerequisites:
477 -- This private function can only be called from the upd process.
478 --
479 -- In Parameters:
480 -- A Pl/Sql record structure.
481 --
482 -- Post Success:
483 -- The record structure will be returned with all system defaulted parameter
484 -- values converted into its current row attribute value.
485 --
486 -- Post Failure:
487 -- No direct error handling is required within this function. Any possible
488 -- errors within this procedure will be a PL/SQL value error due to
489 -- conversion of datatypes or data lengths.
490 --
491 -- Developer Implementation Notes:
492 -- None.
493 --
494 -- Access Status:
495 -- Internal Row Handler Use Only.
496 --
497 -- {End Of Comments}
498 -- ----------------------------------------------------------------------------
499 Procedure convert_defs
500 (p_rec in out nocopy per_pgs_shd.g_rec_type
501 ) is
502 --
503 Begin
504 --
505 -- We must now examine each argument value in the
506 -- p_rec plsql record structure
507 -- to see if a system default is being used. If a system default
508 -- is being used then we must set to the 'current' argument value.
509 --
510 If (p_rec.business_group_id = hr_api.g_number) then
511 p_rec.business_group_id :=
512 per_pgs_shd.g_old_rec.business_group_id;
513 End If;
514 If (p_rec.parent_spine_id = hr_api.g_number) then
515 p_rec.parent_spine_id :=
516 per_pgs_shd.g_old_rec.parent_spine_id;
517 End If;
518 If (p_rec.grade_id = hr_api.g_number) then
519 p_rec.grade_id :=
520 per_pgs_shd.g_old_rec.grade_id;
521 End If;
522 If (p_rec.ceiling_step_id = hr_api.g_number) then
523 p_rec.ceiling_step_id :=
524 per_pgs_shd.g_old_rec.ceiling_step_id;
525 End If;
526 If (p_rec.starting_step = hr_api.g_number) then
527 p_rec.starting_step :=
528 per_pgs_shd.g_old_rec.starting_step;
529 End If;
530 If (p_rec.request_id = hr_api.g_number) then
531 p_rec.request_id :=
532 per_pgs_shd.g_old_rec.request_id;
533 End If;
534 If (p_rec.program_application_id = hr_api.g_number) then
535 p_rec.program_application_id :=
536 per_pgs_shd.g_old_rec.program_application_id;
537 End If;
538 If (p_rec.program_id = hr_api.g_number) then
539 p_rec.program_id :=
540 per_pgs_shd.g_old_rec.program_id;
541 End If;
542 If (p_rec.program_update_date = hr_api.g_date) then
543 p_rec.program_update_date :=
544 per_pgs_shd.g_old_rec.program_update_date;
545 End If;
546 --
547 End convert_defs;
548 --
549 -- ----------------------------------------------------------------------------
550 -- |---------------------------------< upd >----------------------------------|
551 -- ----------------------------------------------------------------------------
552 Procedure upd
553 (p_effective_date in date
554 ,p_datetrack_mode in varchar2
555 ,p_rec in out nocopy per_pgs_shd.g_rec_type
556 ) is
557 --
558 l_proc varchar2(72) := g_package||'upd';
559 l_validation_start_date date;
560 l_validation_end_date date;
561 --
562 Begin
563 hr_utility.set_location('Entering:'||l_proc, 5);
564 --
565 -- Ensure that the DateTrack update mode is valid
566 --
567 dt_api.validate_dt_upd_mode(p_datetrack_mode => p_datetrack_mode);
568 --
569 -- We must lock the row which we need to update.
570 --
571 per_pgs_shd.lck
572 (p_effective_date => p_effective_date
573 ,p_datetrack_mode => p_datetrack_mode
574 ,p_grade_spine_id => p_rec.grade_spine_id
575 ,p_object_version_number => p_rec.object_version_number
576 ,p_validation_start_date => l_validation_start_date
577 ,p_validation_end_date => l_validation_end_date
578 );
579 --
580 -- 1. During an update system defaults are used to determine if
581 -- arguments have been defaulted or not. We must therefore
582 -- derive the full record structure values to be updated.
583 --
584 -- 2. Call the supporting update validate operations.
585 --
586 per_pgs_upd.convert_defs(p_rec);
587 --
588 per_pgs_bus.update_validate
589 (p_rec => p_rec
590 ,p_effective_date => p_effective_date
591 ,p_datetrack_mode => p_datetrack_mode
592 ,p_validation_start_date => l_validation_start_date
593 ,p_validation_end_date => l_validation_end_date
594 );
595 --
596 -- Call to raise any errors on multi-message list
597 hr_multi_message.end_validation_set;
598 --
599 -- Call the supporting pre-update operation
600 --
601 pre_update
602 (p_rec => p_rec
603 ,p_effective_date => p_effective_date
604 ,p_datetrack_mode => p_datetrack_mode
605 ,p_validation_start_date => l_validation_start_date
606 ,p_validation_end_date => l_validation_end_date
607 );
608 --
609 -- Update the row.
610 --
611 update_dml
612 (p_rec => p_rec
613 ,p_effective_date => p_effective_date
614 ,p_datetrack_mode => p_datetrack_mode
615 ,p_validation_start_date => l_validation_start_date
616 ,p_validation_end_date => l_validation_end_date
617 );
618 --
619 -- Call the supporting post-update operation
620 --
621 post_update
622 (p_rec => p_rec
623 ,p_effective_date => p_effective_date
624 ,p_datetrack_mode => p_datetrack_mode
625 ,p_validation_start_date => l_validation_start_date
626 ,p_validation_end_date => l_validation_end_date
627 );
628 --
629 -- Call to raise any errors on multi-message list
630 hr_multi_message.end_validation_set;
631 End upd;
632 --
633 -- ----------------------------------------------------------------------------
634 -- |------------------------------< upd >-------------------------------------|
635 -- ----------------------------------------------------------------------------
636 Procedure upd
637 (p_effective_date in date
638 ,p_datetrack_mode in varchar2
639 ,p_grade_spine_id in number
640 ,p_object_version_number in out nocopy number
641 ,p_business_group_id in number default hr_api.g_number
642 ,p_parent_spine_id in number default hr_api.g_number
643 ,p_grade_id in number default hr_api.g_number
644 ,p_ceiling_step_id in number default hr_api.g_number
645 ,p_starting_step in number default hr_api.g_number
646 ,p_request_id in number default hr_api.g_number
647 ,p_program_application_id in number default hr_api.g_number
648 ,p_program_id in number default hr_api.g_number
649 ,p_program_update_date in date default hr_api.g_date
650 ,p_effective_start_date out nocopy date
651 ,p_effective_end_date out nocopy date
652 ) is
653 --
654 l_rec per_pgs_shd.g_rec_type;
655 l_proc varchar2(72) := g_package||'upd';
656 --
657 Begin
658 hr_utility.set_location('Entering:'||l_proc, 5);
659 --
660 -- Call conversion function to turn arguments into the
661 -- l_rec structure.
662 --
663 l_rec :=
664 per_pgs_shd.convert_args
665 (p_grade_spine_id
666 ,null
667 ,null
668 ,p_business_group_id
669 ,p_parent_spine_id
670 ,p_grade_id
671 ,p_ceiling_step_id
672 ,p_starting_step
673 ,p_request_id
674 ,p_program_application_id
675 ,p_program_id
676 ,p_program_update_date
677 ,p_object_version_number
678 );
679 --
680 -- Having converted the arguments into the
681 -- plsql record structure we call the corresponding record
682 -- business process.
683 --
684 per_pgs_upd.upd
685 (p_effective_date
686 ,p_datetrack_mode
687 ,l_rec
688 );
689 --
690 -- Set the out parameters
691 --
692 p_object_version_number := l_rec.object_version_number;
693 p_effective_start_date := l_rec.effective_start_date;
694 p_effective_end_date := l_rec.effective_end_date;
695 --
696 --
697 hr_utility.set_location(' Leaving:'||l_proc, 10);
698 End upd;
699 --
700 end per_pgs_upd;
[Home] [Help]