1 Package Body pay_ppr_upd as
2 /* $Header: pypprrhi.pkb 115.3 2004/02/25 21:33 adkumar noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' pay_ppr_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 pay_ppr_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 => 'pay_status_processing_rules_f'
79 ,p_base_key_column => 'status_processing_rule_id'
80 ,p_base_key_value => p_rec.status_processing_rule_id
81 );
82 --
83 pay_ppr_shd.g_api_dml := true; -- Set the api dml status
84 --
85 -- Update the pay_status_processing_rules_f Row
86 --
87 update pay_status_processing_rules_f
88 set
89 status_processing_rule_id = p_rec.status_processing_rule_id
90 ,business_group_id = p_rec.business_group_id
91 ,legislation_code = p_rec.legislation_code
92 ,element_type_id = p_rec.element_type_id
93 ,assignment_status_type_id = p_rec.assignment_status_type_id
94 ,formula_id = p_rec.formula_id
95 ,processing_rule = p_rec.processing_rule
96 ,comment_id = p_rec.comment_id
97 ,legislation_subgroup = p_rec.legislation_subgroup
98 ,object_version_number = p_rec.object_version_number
99 where status_processing_rule_id = p_rec.status_processing_rule_id
100 and effective_start_date = p_validation_start_date
101 and effective_end_date = p_validation_end_date;
102 --
103 pay_ppr_shd.g_api_dml := false; -- Unset the api dml status
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 pay_ppr_shd.g_api_dml := false; -- Unset the api dml status
116 pay_ppr_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 pay_ppr_shd.g_api_dml := false; -- Unset the api dml status
121 pay_ppr_shd.constraint_error
122 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
123 When Others Then
124 pay_ppr_shd.g_api_dml := false; -- Unset the api dml status
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 pay_ppr_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 pay_ppr_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 pay_ppr_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 pay_ppr_shd.upd_effective_end_date
244 (p_effective_date => p_effective_date
245 ,p_base_key_value => p_rec.status_processing_rule_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 pay_ppr_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 pay_ppr_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 pay_ppr_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 -- Insert the comment text if comments exist
326 --
327 If (p_rec.comments is not null and p_rec.comment_id is null) then
328 hr_comm_api.ins(p_comment_id => p_rec.comment_id
329 ,p_source_table_name => 'PAY_STATUS_PROCESSING_RULES_F'
330 ,p_comment_text => p_rec.comments
331 );
332 -- Update the comments if they have changed
333 ElsIf (p_rec.comment_id is not null and p_rec.comments <>
334 pay_ppr_shd.g_old_rec.comments) then
335 hr_comm_api.upd(p_comment_id => p_rec.comment_id
336 ,p_source_table_name => 'PAY_STATUS_PROCESSING_RULES_F'
337 ,p_comment_text => p_rec.comments
338 );
339 End If;
340 --
341 dt_pre_update
342 (p_rec => p_rec
343 ,p_effective_date => p_effective_date
344 ,p_datetrack_mode => p_datetrack_mode
345 ,p_validation_start_date => p_validation_start_date
346 ,p_validation_end_date => p_validation_end_date
347 );
348 --
349 hr_utility.set_location(' Leaving:'||l_proc, 10);
350 End pre_update;
351 --
352 -- ----------------------------------------------------------------------------
353 -- |----------------------------< post_update >-------------------------------|
354 -- ----------------------------------------------------------------------------
355 -- {Start Of Comments}
356 --
357 -- Description:
358 -- This private procedure contains any processing which is required after
359 -- the update dml.
360 --
361 -- Prerequisites:
362 -- This is an internal procedure which is called from the upd procedure.
363 --
364 -- In Parameters:
365 -- A Pl/Sql record structure.
366 --
367 -- Post Success:
368 -- Processing continues.
369 --
370 -- Post Failure:
371 -- If an error has occurred, an error message and exception will be raised
372 -- but not handled.
373 --
374 -- Developer Implementation Notes:
375 -- Any post-processing required after the update dml is issued should be
376 -- coded within this procedure. It is important to note that any 3rd party
377 -- maintenance should be reviewed before placing in this procedure.
378 --
379 -- Access Status:
380 -- Internal Row Handler Use Only.
381 --
382 -- {End Of Comments}
383 -- ----------------------------------------------------------------------------
384 Procedure post_update
385 (p_rec in pay_ppr_shd.g_rec_type
386 ,p_effective_date in date
387 ,p_datetrack_mode in varchar2
388 ,p_validation_start_date in date
389 ,p_validation_end_date in date
390 ,p_formula_mismatch_warning in boolean
391 ) is
392 --
393 l_proc varchar2(72) := g_package||'post_update';
394 --
395 Begin
396 hr_utility.set_location('Entering:'||l_proc, 5);
397 begin
398 --
399 pay_ppr_rku.after_update
400 (p_effective_date => p_effective_date
401 ,p_datetrack_mode => p_datetrack_mode
402 ,p_validation_start_date => p_validation_start_date
403 ,p_validation_end_date => p_validation_end_date
404 ,p_status_processing_rule_id => p_rec.status_processing_rule_id
405 ,p_effective_start_date => p_rec.effective_start_date
406 ,p_effective_end_date => p_rec.effective_end_date
407 ,p_business_group_id => p_rec.business_group_id
408 ,p_legislation_code => p_rec.legislation_code
409 ,p_element_type_id => p_rec.element_type_id
410 ,p_assignment_status_type_id => p_rec.assignment_status_type_id
411 ,p_formula_id => p_rec.formula_id
412 ,p_comment_id => p_rec.comment_id
413 ,p_comments => p_rec.comments
414 ,p_legislation_subgroup => p_rec.legislation_subgroup
415 ,p_object_version_number => p_rec.object_version_number
416 ,p_formula_mismatch_warning => p_formula_mismatch_warning
417 ,p_effective_start_date_o => pay_ppr_shd.g_old_rec.effective_start_date
418 ,p_effective_end_date_o => pay_ppr_shd.g_old_rec.effective_end_date
419 ,p_business_group_id_o => pay_ppr_shd.g_old_rec.business_group_id
420 ,p_legislation_code_o => pay_ppr_shd.g_old_rec.legislation_code
421 ,p_element_type_id_o => pay_ppr_shd.g_old_rec.element_type_id
422 ,p_assignment_status_type_id_o => pay_ppr_shd.g_old_rec.assignment_status_type_id
423 ,p_formula_id_o => pay_ppr_shd.g_old_rec.formula_id
424 ,p_processing_rule_o => pay_ppr_shd.g_old_rec.processing_rule
425 ,p_comment_id_o => pay_ppr_shd.g_old_rec.comment_id
426 ,p_comments_o => pay_ppr_shd.g_old_rec.comments
427 ,p_legislation_subgroup_o => pay_ppr_shd.g_old_rec.legislation_subgroup
428 ,p_object_version_number_o => pay_ppr_shd.g_old_rec.object_version_number
429 );
430 --
431 exception
432 --
433 when hr_api.cannot_find_prog_unit then
434 --
435 hr_api.cannot_find_prog_unit_error
436 (p_module_name => 'PAY_STATUS_PROCESSING_RULES_F'
437 ,p_hook_type => 'AU');
438 --
439 end;
440 --
441 hr_utility.set_location(' Leaving:'||l_proc, 10);
442 End post_update;
443 --
444 -- ----------------------------------------------------------------------------
445 -- |-----------------------------< convert_defs >-----------------------------|
446 -- ----------------------------------------------------------------------------
447 -- {Start Of Comments}
448 --
449 -- Description:
450 -- The Convert_Defs procedure has one very important function:
451 -- It must return the record structure for the row with all system defaulted
452 -- values converted into its corresponding parameter value for update. When
453 -- we attempt to update a row through the Upd process , certain
454 -- parameters can be defaulted which enables flexibility in the calling of
455 -- the upd process (e.g. only attributes which need to be updated need to be
456 -- specified). For the upd process to determine which attributes
457 -- have NOT been specified we need to check if the parameter has a reserved
458 -- system default value. Therefore, for all parameters which have a
459 -- corresponding reserved system default mechanism specified we need to
460 -- check if a system default is being used. If a system default is being
461 -- used then we convert the defaulted value into its corresponding attribute
462 -- value held in the g_old_rec data structure.
463 --
464 -- Prerequisites:
465 -- This private function can only be called from the upd process.
466 --
467 -- In Parameters:
468 -- A Pl/Sql record structure.
469 --
470 -- Post Success:
471 -- The record structure will be returned with all system defaulted parameter
472 -- values converted into its current row attribute value.
473 --
474 -- Post Failure:
475 -- No direct error handling is required within this function. Any possible
476 -- errors within this procedure will be a PL/SQL value error due to
477 -- conversion of datatypes or data lengths.
478 --
479 -- Developer Implementation Notes:
480 -- None.
481 --
482 -- Access Status:
483 -- Internal Row Handler Use Only.
484 --
485 -- {End Of Comments}
486 -- ----------------------------------------------------------------------------
487 Procedure convert_defs
488 (p_rec in out nocopy pay_ppr_shd.g_rec_type
489 ) is
490 --
491 Begin
492 --
493 -- We must now examine each argument value in the
494 -- p_rec plsql record structure
495 -- to see if a system default is being used. If a system default
496 -- is being used then we must set to the 'current' argument value.
497 --
498 If (p_rec.business_group_id = hr_api.g_number) then
499 p_rec.business_group_id :=
500 pay_ppr_shd.g_old_rec.business_group_id;
501 End If;
502 If (p_rec.legislation_code = hr_api.g_varchar2) then
503 p_rec.legislation_code :=
504 pay_ppr_shd.g_old_rec.legislation_code;
505 End If;
506 If (p_rec.element_type_id = hr_api.g_number) then
507 p_rec.element_type_id :=
508 pay_ppr_shd.g_old_rec.element_type_id;
509 End If;
510 If (p_rec.assignment_status_type_id = hr_api.g_number) then
511 p_rec.assignment_status_type_id :=
512 pay_ppr_shd.g_old_rec.assignment_status_type_id;
513 End If;
514 If (p_rec.formula_id = hr_api.g_number) then
515 p_rec.formula_id :=
516 pay_ppr_shd.g_old_rec.formula_id;
517 End If;
518 If (p_rec.processing_rule = hr_api.g_varchar2) then
519 p_rec.processing_rule :=
520 pay_ppr_shd.g_old_rec.processing_rule;
521 End If;
522 If (p_rec.comment_id = hr_api.g_number) then
523 p_rec.comment_id :=
524 pay_ppr_shd.g_old_rec.comment_id;
525 End If;
526 If (p_rec.comments = hr_api.g_varchar2) then
527 p_rec.comments :=
528 pay_ppr_shd.g_old_rec.comments;
529 End If;
530 If (p_rec.legislation_subgroup = hr_api.g_varchar2) then
531 p_rec.legislation_subgroup :=
532 pay_ppr_shd.g_old_rec.legislation_subgroup;
533 End If;
534 --
535 End convert_defs;
536 --
537 -- ----------------------------------------------------------------------------
538 -- |---------------------------------< upd >----------------------------------|
539 -- ----------------------------------------------------------------------------
540 Procedure upd
541 (p_effective_date in date
542 ,p_datetrack_mode in varchar2
543 ,p_rec in out nocopy pay_ppr_shd.g_rec_type
544 ,p_formula_mismatch_warning out nocopy boolean
545 ) is
546 --
547 l_proc varchar2(72) := g_package||'upd';
548 l_validation_start_date date;
549 l_validation_end_date date;
550 l_processing_rule varchar2(1);
551 l_formula_mismatch_warning boolean;
552 --
553 Begin
554 hr_utility.set_location('Entering:'||l_proc, 5);
555 --
556 -- Ensure that the DateTrack update mode is valid
557 --
558 dt_api.validate_dt_upd_mode(p_datetrack_mode => p_datetrack_mode);
559 --
560 -- We must lock the row which we need to update.
561 --
562 pay_ppr_shd.lck
563 (p_effective_date => p_effective_date
564 ,p_datetrack_mode => p_datetrack_mode
565 ,p_status_processing_rule_id => p_rec.status_processing_rule_id
566 ,p_object_version_number => p_rec.object_version_number
567 ,p_validation_start_date => l_validation_start_date
568 ,p_validation_end_date => l_validation_end_date
569 );
570 --
571 -- 1. During an update system defaults are used to determine if
572 -- arguments have been defaulted or not. We must therefore
573 -- derive the full record structure values to be updated.
574 --
575 -- 2. Call the supporting update validate operations.
576 --
577 pay_ppr_upd.convert_defs(p_rec);
578 --
579 pay_ppr_bus.update_validate
580 (p_rec => p_rec
581 ,p_effective_date => p_effective_date
582 ,p_datetrack_mode => p_datetrack_mode
583 ,p_validation_start_date => l_validation_start_date
584 ,p_validation_end_date => l_validation_end_date
585 ,p_processing_rule => l_processing_rule
586 ,p_formula_mismatch_warning => l_formula_mismatch_warning
587 );
588 --
589 p_rec.processing_rule := l_processing_rule;
590 p_formula_mismatch_warning := l_formula_mismatch_warning;
591 --
592
593 -- Call to raise any errors on multi-message list
594 hr_multi_message.end_validation_set;
595 --
596 -- Call the supporting pre-update operation
597 --
598 pre_update
599 (p_rec => p_rec
600 ,p_effective_date => p_effective_date
601 ,p_datetrack_mode => p_datetrack_mode
602 ,p_validation_start_date => l_validation_start_date
603 ,p_validation_end_date => l_validation_end_date
604 );
605 --
606 -- Update the row.
607 --
608 update_dml
609 (p_rec => p_rec
610 ,p_effective_date => p_effective_date
611 ,p_datetrack_mode => p_datetrack_mode
612 ,p_validation_start_date => l_validation_start_date
613 ,p_validation_end_date => l_validation_end_date
614 );
615 --
616 -- Call the supporting post-update operation
617 --
618 post_update
619 (p_rec => p_rec
620 ,p_effective_date => p_effective_date
621 ,p_datetrack_mode => p_datetrack_mode
622 ,p_validation_start_date => l_validation_start_date
623 ,p_validation_end_date => l_validation_end_date
624 ,p_formula_mismatch_warning => l_formula_mismatch_warning
625 );
626 --
627 -- Call to raise any errors on multi-message list
628 hr_multi_message.end_validation_set;
629 End upd;
630 --
631 -- ----------------------------------------------------------------------------
632 -- |------------------------------< upd >-------------------------------------|
633 -- ----------------------------------------------------------------------------
634 Procedure upd
635 (p_effective_date in date
636 ,p_datetrack_mode in varchar2
637 ,p_status_processing_rule_id in number
638 ,p_object_version_number in out nocopy number
639 ,p_formula_id in number default hr_api.g_number
640 ,p_comments in varchar2 default hr_api.g_varchar2
641 ,p_effective_start_date out nocopy date
642 ,p_effective_end_date out nocopy date
643 ,p_formula_mismatch_warning out nocopy boolean
644 ) is
645 --
646 l_rec pay_ppr_shd.g_rec_type;
647 l_proc varchar2(72) := g_package||'upd';
648 l_formula_mismatch_warning boolean;
649 --
650 Begin
651 hr_utility.set_location('Entering:'||l_proc, 5);
652 --
653 -- Call conversion function to turn arguments into the
654 -- l_rec structure.
655 --
656 l_rec :=
657 pay_ppr_shd.convert_args
658 (p_status_processing_rule_id
659 ,null
660 ,null
661 ,hr_api.g_number
662 ,hr_api.g_varchar2
663 ,hr_api.g_number
664 ,hr_api.g_number
665 ,p_formula_id
666 ,hr_api.g_varchar2
667 ,hr_api.g_number
668 ,p_comments
669 ,hr_api.g_varchar2
670 ,p_object_version_number
671 );
672 --
673 -- Having converted the arguments into the
674 -- plsql record structure we call the corresponding record
675 -- business process.
676 --
677 pay_ppr_upd.upd
678 (p_effective_date
679 ,p_datetrack_mode
680 ,l_rec
681 ,p_formula_mismatch_warning => l_formula_mismatch_warning
682 );
683 --
684 -- Set the out parameters
685 --
686 p_object_version_number := l_rec.object_version_number;
687 p_effective_start_date := l_rec.effective_start_date;
688 p_effective_end_date := l_rec.effective_end_date;
689 p_formula_mismatch_warning := l_formula_mismatch_warning;
690 --
691 hr_utility.set_location(' Leaving:'||l_proc, 10);
692 End upd;
693 --
694 end pay_ppr_upd;