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