1 Package Body pay_frr_ins as
2 /* $Header: pyfrrrhi.pkb 120.3.12020000.2 2012/07/06 14:00:07 asnell ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' pay_frr_ins.'; -- Global package name
9 --
10 -- The following global variables are only to be used by
11 -- the set_base_key_value and pre_insert procedures.
12 --
13 g_formula_result_rule_id_i number default null;
14 --
15 -- ----------------------------------------------------------------------------
16 -- |------------------------< set_base_key_value >----------------------------|
17 -- ----------------------------------------------------------------------------
18 procedure set_base_key_value
19 (p_formula_result_rule_id in number) is
20 --
21 l_proc varchar2(72) := g_package||'set_base_key_value';
22 --
23 Begin
24 hr_utility.set_location('Entering:'||l_proc, 10);
25 --
26 pay_frr_ins.g_formula_result_rule_id_i := p_formula_result_rule_id;
27 --
28 hr_utility.set_location(' Leaving:'||l_proc, 20);
29 End set_base_key_value;
30 --
31 --
32 -- ----------------------------------------------------------------------------
33 -- |----------------------------< dt_insert_dml >-----------------------------|
34 -- ----------------------------------------------------------------------------
35 -- {Start Of Comments}
36 --
37 -- Description:
38 -- This procedure controls the actual dml insert logic for datetrack. The
39 -- functions of this procedure are as follows:
40 -- 1) Get the object_version_number.
41 -- 2) To set the effective start and end dates to the corresponding
42 -- validation start and end dates. Also, the object version number
43 -- record attribute is set.
44 -- 3) To set and unset the g_api_dml status as required (as we are about to
45 -- perform dml).
46 -- 4) To insert the row into the schema with the derived effective start
47 -- and end dates and the object version number.
48 -- 5) To trap any constraint violations that may have occurred.
49 -- 6) To raise any other errors.
50 --
51 -- Prerequisites:
52 -- This is an internal private procedure which must be called from the
53 -- insert_dml and pre_update (logic permitting) procedure and must have
54 -- all mandatory arguments set.
55 --
56 -- In Parameters:
57 -- A Pl/Sql record structure.
58 --
59 -- Post Success:
60 -- The specified row will be inserted into the schema.
61 --
62 -- Post Failure:
63 -- On the insert dml failure it is important to note that we always reset the
64 -- g_api_dml status to false.
65 -- If a check or unique integrity constraint violation is raised the
66 -- constraint_error procedure will be called.
67 -- If any other error is reported, the error will be raised after the
68 -- g_api_dml status is reset.
69 --
70 -- Developer Implementation Notes:
71 -- This is an internal datetrack maintenance procedure which should
72 -- not be modified in anyway.
73 --
74 -- Access Status:
75 -- Internal Row Handler Use Only.
76 --
77 -- {End Of Comments}
78 -- ----------------------------------------------------------------------------
79 Procedure dt_insert_dml
80 (p_rec in out nocopy pay_frr_shd.g_rec_type
81 ,p_effective_date in date
82 ,p_datetrack_mode in varchar2
83 ,p_validation_start_date in date
84 ,p_validation_end_date in date
85 ) is
86 -- Cursor to select 'old' created AOL who column values
87 --
88 Cursor C_Sel1 Is
89 select t.created_by,
90 t.creation_date
91 from pay_formula_result_rules_f t
92 where t.formula_result_rule_id = p_rec.formula_result_rule_id
93 and t.effective_start_date =
94 pay_frr_shd.g_old_rec.effective_start_date
95 and t.effective_end_date = (p_validation_start_date - 1);
96 --
97 l_proc varchar2(72) := g_package||'dt_insert_dml';
98 l_created_by pay_formula_result_rules_f.created_by%TYPE;
99 l_creation_date pay_formula_result_rules_f.creation_date%TYPE;
100 l_last_update_date pay_formula_result_rules_f.last_update_date%TYPE;
101 l_last_updated_by pay_formula_result_rules_f.last_updated_by%TYPE;
102 l_last_update_login pay_formula_result_rules_f.last_update_login%TYPE;
103 --
104 Begin
105 hr_utility.set_location('Entering:'||l_proc, 5);
106 --
107 -- Set the effective start and end dates to the corresponding
108 -- validation start and end dates
109 --
110 p_rec.effective_start_date := p_validation_start_date;
111 p_rec.effective_end_date := p_validation_end_date;
112 --
113 -- If the datetrack_mode is not INSERT then we must populate the WHO
114 -- columns with the 'old' creation values and 'new' updated values.
115 --
116 If (p_datetrack_mode <> hr_api.g_insert) then
117 hr_utility.set_location(l_proc, 10);
118 --
119 -- Get the object version number for the insert
120 --
121 p_rec.object_version_number :=
122 dt_api.get_object_version_number
123 (p_base_table_name => 'pay_formula_result_rules_f'
124 ,p_base_key_column => 'formula_result_rule_id'
125 ,p_base_key_value => p_rec.formula_result_rule_id
126 );
127 --
128 -- Select the 'old' created values
129 --
130 Open C_Sel1;
131 Fetch C_Sel1 Into l_created_by, l_creation_date;
132 If C_Sel1%notfound Then
133 --
134 -- The previous 'old' created row has not been found. We need
135 -- to error as an internal datetrack problem exists.
136 --
137 Close C_Sel1;
138 fnd_message.set_name('PAY', 'HR_6153_ALL_PROCEDURE_FAIL');
139 fnd_message.set_token('PROCEDURE', l_proc);
140 fnd_message.set_token('STEP','10');
141 fnd_message.raise_error;
142 End If;
143 Close C_Sel1;
144 --
145 -- Set the AOL updated WHO values
146 --
147 l_last_update_date := sysdate;
148 l_last_updated_by := fnd_global.user_id;
149 l_last_update_login := fnd_global.login_id;
150 Else
151 p_rec.object_version_number := 1; -- Initialise the object version
152 End If;
153 --
154 pay_frr_shd.g_api_dml := true; -- Set the api dml status
155 --
156 -- Insert the row into: pay_formula_result_rules_f
157 --
158 insert into pay_formula_result_rules_f
159 (formula_result_rule_id
160 ,effective_start_date
161 ,effective_end_date
162 ,business_group_id
163 ,legislation_code
164 ,element_type_id
165 ,status_processing_rule_id
166 ,result_name
167 ,result_rule_type
168 ,legislation_subgroup
169 ,severity_level
170 ,input_value_id
171 ,object_version_number
172 ,created_by
173 ,creation_date
174 ,last_update_date
175 ,last_updated_by
176 ,last_update_login
177 )
178 Values
179 (p_rec.formula_result_rule_id
180 ,p_rec.effective_start_date
181 ,p_rec.effective_end_date
182 ,p_rec.business_group_id
183 ,p_rec.legislation_code
184 ,p_rec.element_type_id
185 ,p_rec.status_processing_rule_id
186 ,p_rec.result_name
187 ,p_rec.result_rule_type
188 ,p_rec.legislation_subgroup
189 ,p_rec.severity_level
190 ,p_rec.input_value_id
191 ,p_rec.object_version_number
192 ,l_created_by
193 ,l_creation_date
194 ,l_last_update_date
195 ,l_last_updated_by
196 ,l_last_update_login
197 );
198 --
199 pay_frr_shd.g_api_dml := false; -- Unset the api dml status
200 hr_utility.set_location(' Leaving:'||l_proc, 15);
201 --
202 Exception
203 When hr_api.check_integrity_violated Then
204 -- A check constraint has been violated
205 pay_frr_shd.g_api_dml := false; -- Unset the api dml status
206 pay_frr_shd.constraint_error
207 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
208 When hr_api.unique_integrity_violated Then
209 -- Unique integrity has been violated
210 pay_frr_shd.g_api_dml := false; -- Unset the api dml status
211 pay_frr_shd.constraint_error
212 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
213 When Others Then
214 pay_frr_shd.g_api_dml := false; -- Unset the api dml status
215 Raise;
216 End dt_insert_dml;
217 --
218 -- ----------------------------------------------------------------------------
219 -- |-----------------------< create_app_ownerships >--------------------------|
220 -- ----------------------------------------------------------------------------
221 --
222 -- Description:
223 -- This procedure inserts a row into the HR_APPLICATION_OWNERSHIPS table
224 -- when the row handler is called in the appropriate mode.
225 --
226 -- ----------------------------------------------------------------------------
227 PROCEDURE create_app_ownerships(p_pk_column IN varchar2
228 ,p_pk_value IN varchar2) IS
229 --
230 CURSOR csr_definition IS
231 SELECT product_short_name
232 FROM hr_owner_definitions
233 WHERE session_id = hr_startup_data_api_support.g_session_id;
234 --
235 BEGIN
236 --
237 IF (hr_startup_data_api_support.return_startup_mode IN
238 ('STARTUP','GENERIC')) THEN
239 --
240 FOR c1 IN csr_definition LOOP
241 --
242 INSERT INTO hr_application_ownerships
243 (key_name
244 ,key_value
245 ,product_name
246 )
247 VALUES
248 (p_pk_column
249 ,fnd_number.number_to_canonical(p_pk_value)
250 ,c1.product_short_name
251 );
252 END LOOP;
253 END IF;
254 END create_app_ownerships;
255 --
256 -- ----------------------------------------------------------------------------
257 -- |-----------------------< create_app_ownerships >--------------------------|
258 -- ----------------------------------------------------------------------------
259 PROCEDURE create_app_ownerships(p_pk_column IN varchar2
260 ,p_pk_value IN number) IS
261 --
262 BEGIN
263 create_app_ownerships(p_pk_column, to_char(p_pk_value));
264 END create_app_ownerships;
265 --
266 -- ----------------------------------------------------------------------------
267 -- |------------------------------< insert_dml >------------------------------|
268 -- ----------------------------------------------------------------------------
269 Procedure insert_dml
270 (p_rec in out nocopy pay_frr_shd.g_rec_type
271 ,p_effective_date in date
272 ,p_datetrack_mode in varchar2
273 ,p_validation_start_date in date
274 ,p_validation_end_date in date
275 ) is
276 --
277 l_proc varchar2(72) := g_package||'insert_dml';
278 --
279 Begin
280 hr_utility.set_location('Entering:'||l_proc, 5);
281 --
282 pay_frr_ins.dt_insert_dml
283 (p_rec => p_rec
284 ,p_effective_date => p_effective_date
285 ,p_datetrack_mode => p_datetrack_mode
286 ,p_validation_start_date => p_validation_start_date
287 ,p_validation_end_date => p_validation_end_date
288 );
289 --
290 hr_utility.set_location(' Leaving:'||l_proc, 10);
291 End insert_dml;
292 --
293 -- ----------------------------------------------------------------------------
294 -- |------------------------------< pre_insert >------------------------------|
295 -- ----------------------------------------------------------------------------
296 -- {Start Of Comments}
297 --
298 -- Description:
299 -- This private procedure contains any processing which is required before
300 -- the insert dml. Presently, if the entity has a corresponding primary
301 -- key which is maintained by an associating sequence, the primary key for
302 -- the entity will be populated with the next sequence value in
303 -- preparation for the insert dml.
304 -- Also, if comments are defined for this entity, the comments insert
305 -- logic will also be called, generating a comment_id if required.
306 --
307 -- Prerequisites:
308 -- This is an internal procedure which is called from the ins procedure.
309 --
310 -- In Parameters:
311 -- A Pl/Sql record structure.
312 --
313 -- Post Success:
314 -- Processing continues.
315 --
316 -- Post Failure:
317 -- If an error has occurred, an error message and exception will be raised
318 -- but not handled.
319 --
320 -- Developer Implementation Notes:
321 -- Any pre-processing required before the insert dml is issued should be
322 -- coded within this procedure. As stated above, a good example is the
323 -- generation of a primary key number via a corresponding sequence.
324 -- It is important to note that any 3rd party maintenance should be reviewed
325 -- before placing in this procedure.
326 --
327 -- Access Status:
328 -- Internal Row Handler Use Only.
329 --
330 -- {End Of Comments}
331 -- ----------------------------------------------------------------------------
332 Procedure pre_insert
333 (p_rec in out nocopy pay_frr_shd.g_rec_type
334 ,p_effective_date in date
335 ,p_datetrack_mode in varchar2
336 ,p_validation_start_date in date
337 ,p_validation_end_date in date
338 ) is
339 --
340 Cursor C_Sel1 is select pay_formula_result_rules_s.nextval from sys.dual;
341 --
342 Cursor C_Sel2 is
343 Select null
344 from pay_formula_result_rules_f
345 where formula_result_rule_id =
346 pay_frr_ins.g_formula_result_rule_id_i;
347 --
348 l_proc varchar2(72) := g_package||'pre_insert';
349 l_exists varchar2(1);
350 --
351 Begin
352 hr_utility.set_location('Entering:'||l_proc, 5);
353 --
354 If (pay_frr_ins.g_formula_result_rule_id_i is not null) Then
355 --
356 -- Verify registered primary key values not already in use
357 --
358 Open C_Sel2;
359 Fetch C_Sel2 into l_exists;
360 If C_Sel2%found Then
361 Close C_Sel2;
362 --
363 -- The primary key values are already in use.
364 --
365 fnd_message.set_name('PER','PER_289391_KEY_ALREADY_USED');
366 fnd_message.set_token('TABLE_NAME','pay_formula_result_rules_f');
367 fnd_message.raise_error;
368 End If;
369 Close C_Sel2;
370 --
371 -- Use registered key values and clear globals
372 --
373 p_rec.formula_result_rule_id :=
374 pay_frr_ins.g_formula_result_rule_id_i;
375 pay_frr_ins.g_formula_result_rule_id_i := null;
376 Else
377 --
378 -- No registerd key values, so select the next sequence number
379 --
380 --
381 -- Select the next sequence number
382 --
383 Open C_Sel1;
384 Fetch C_Sel1 Into p_rec.formula_result_rule_id;
385 Close C_Sel1;
386 End If;
387 --
388 --
389 hr_utility.set_location(' Leaving:'||l_proc, 10);
390 End pre_insert;
391 --
392 -- ----------------------------------------------------------------------------
393 -- |----------------------------< post_insert >-------------------------------|
394 -- ----------------------------------------------------------------------------
395 -- {Start Of Comments}
396 --
397 -- Description:
398 -- This private procedure contains any processing which is required after
399 -- the insert dml.
400 --
401 -- Prerequisites:
402 -- This is an internal procedure which is called from the ins procedure.
403 --
404 -- In Parameters:
405 -- A Pl/Sql record structure.
406 --
407 -- Post Success:
408 -- Processing continues.
409 --
410 -- Post Failure:
411 -- If an error has occurred, an error message and exception will be raised
412 -- but not handled.
413 --
414 -- Developer Implementation Notes:
415 -- Any post-processing required after the insert dml is issued should be
416 -- coded within this procedure. It is important to note that any 3rd party
417 -- maintenance should be reviewed before placing in this procedure.
418 --
419 -- Access Status:
420 -- Internal Row Handler Use Only.
421 --
422 -- {End Of Comments}
423 -- ----------------------------------------------------------------------------
424 Procedure post_insert
425 (p_rec in pay_frr_shd.g_rec_type
426 ,p_effective_date in date
427 ,p_datetrack_mode in varchar2
428 ,p_validation_start_date in date
429 ,p_validation_end_date in date
430 ) is
431 --
432 l_proc varchar2(72) := g_package||'post_insert';
433 --
434 Begin
435 hr_utility.set_location('Entering:'||l_proc, 5);
436 begin
437 --
438 -- insert ownerships if applicable
439 create_app_ownerships
440 ('FORMULA_RESULT_RULE_ID', p_rec.formula_result_rule_id
441 );
442 --
443 --
444 pay_frr_rki.after_insert
445 (p_effective_date
446 => p_effective_date
447 ,p_validation_start_date
448 => p_validation_start_date
449 ,p_validation_end_date
450 => p_validation_end_date
451 ,p_formula_result_rule_id
452 => p_rec.formula_result_rule_id
453 ,p_effective_start_date
454 => p_rec.effective_start_date
455 ,p_effective_end_date
456 => p_rec.effective_end_date
457 ,p_business_group_id
458 => p_rec.business_group_id
459 ,p_legislation_code
460 => p_rec.legislation_code
461 ,p_element_type_id
462 => p_rec.element_type_id
463 ,p_status_processing_rule_id
464 => p_rec.status_processing_rule_id
465 ,p_result_name
466 => p_rec.result_name
467 ,p_result_rule_type
468 => p_rec.result_rule_type
469 ,p_legislation_subgroup
470 => p_rec.legislation_subgroup
471 ,p_severity_level
472 => p_rec.severity_level
473 ,p_input_value_id
474 => p_rec.input_value_id
475 ,p_object_version_number
476 => p_rec.object_version_number
477 );
478 --
479 exception
480 --
481 when hr_api.cannot_find_prog_unit then
482 --
483 hr_api.cannot_find_prog_unit_error
484 (p_module_name => 'PAY_FORMULA_RESULT_RULES_F'
485 ,p_hook_type => 'AI');
486 --
487 end;
488 --
489 hr_utility.set_location(' Leaving:'||l_proc, 10);
490 End post_insert;
491 --
492 -- ----------------------------------------------------------------------------
493 -- |-------------------------------< ins_lck >--------------------------------|
494 -- ----------------------------------------------------------------------------
495 -- {Start Of Comments}
496 --
497 -- Description:
498 -- The ins_lck process has one main function to perform. When inserting
499 -- a datetracked row, we must validate the DT mode.
500 --
501 -- Prerequisites:
502 -- This procedure can only be called for the datetrack mode of INSERT.
503 --
504 -- In Parameters:
505 --
506 -- Post Success:
507 -- On successful completion of the ins_lck process the parental
508 -- datetracked rows will be locked providing the p_enforce_foreign_locking
509 -- argument value is TRUE.
510 -- If the p_enforce_foreign_locking argument value is FALSE then the
511 -- parential rows are not locked.
512 --
513 -- Post Failure:
514 -- The Lck process can fail for:
515 -- 1) When attempting to lock the row the row could already be locked by
516 -- another user. This will raise the HR_Api.Object_Locked exception.
517 -- 2) When attempting to the lock the parent which doesn't exist.
518 -- For the entity to be locked the parent must exist!
519 --
520 -- Developer Implementation Notes:
521 -- None.
522 --
523 -- Access Status:
524 -- Internal Row Handler Use Only.
525 --
526 -- {End Of Comments}
527 -- ----------------------------------------------------------------------------
528 Procedure ins_lck
529 (p_effective_date in date
530 ,p_datetrack_mode in varchar2
531 ,p_rec in pay_frr_shd.g_rec_type
532 ,p_validation_start_date out nocopy date
533 ,p_validation_end_date out nocopy date
534 ) is
535 --
536 l_proc varchar2(72) := g_package||'ins_lck';
537 l_validation_start_date date;
538 l_validation_end_date date;
539 --
540 Begin
541 hr_utility.set_location('Entering:'||l_proc, 5);
542 --
543 -- Validate the datetrack mode mode getting the validation start
544 -- and end dates for the specified datetrack operation.
545 --
546 dt_api.validate_dt_mode
547 (p_effective_date => p_effective_date
548 ,p_datetrack_mode => p_datetrack_mode
549 ,p_base_table_name => 'pay_formula_result_rules_f'
550 ,p_base_key_column => 'formula_result_rule_id'
551 ,p_base_key_value => p_rec.formula_result_rule_id
552 ,p_enforce_foreign_locking => true
553 ,p_validation_start_date => l_validation_start_date
554 ,p_validation_end_date => l_validation_end_date
555 );
556 --
557 -- Set the validation start and end date OUT arguments
558 --
559 p_validation_start_date := l_validation_start_date;
560 p_validation_end_date := l_validation_end_date;
561 --
562 hr_utility.set_location(' Leaving:'||l_proc, 10);
563 --
564 End ins_lck;
565 --
566 -- ----------------------------------------------------------------------------
567 -- |---------------------------------< ins >----------------------------------|
568 -- ----------------------------------------------------------------------------
569 Procedure ins
570 (p_effective_date in date
571 ,p_rec in out nocopy pay_frr_shd.g_rec_type
572 ) is
573 --
574 l_proc varchar2(72) := g_package||'ins';
575 l_datetrack_mode varchar2(30) := hr_api.g_insert;
576 l_validation_start_date date;
577 l_validation_end_date date;
578 --
579 Begin
580 hr_utility.set_location('Entering:'||l_proc, 5);
581 --
582 -- Call the lock operation
583 --
584 pay_frr_ins.ins_lck
585 (p_effective_date => p_effective_date
586 ,p_datetrack_mode => l_datetrack_mode
587 ,p_rec => p_rec
588 ,p_validation_start_date => l_validation_start_date
589 ,p_validation_end_date => l_validation_end_date
590 );
591 --
592 -- Set the effective end date of the FRR according to the
593 -- business rule.
594 --
595 pay_frr_bus.set_effective_end_date
596 (p_effective_date => p_effective_date
597 ,p_result_rule_type => p_rec.result_rule_type
598 ,p_result_name => p_rec.result_name
599 ,p_status_processing_rule_id => p_rec.status_processing_rule_id
600 ,p_element_type_id => p_rec.element_type_id
601 ,p_input_value_id => p_rec.input_value_id
602 ,p_datetrack_mode => null
603 ,p_validation_end_date => l_validation_end_date
604 );
605 --
606 -- Call the supporting insert validate operations
607 --
608 pay_frr_bus.insert_validate
609 (p_rec => p_rec
610 ,p_effective_date => p_effective_date
611 ,p_datetrack_mode => l_datetrack_mode
612 ,p_validation_start_date => l_validation_start_date
613 ,p_validation_end_date => l_validation_end_date
614 );
615 --
616 -- Call to raise any errors on multi-message list
617 hr_multi_message.end_validation_set;
618 --
619 -- Call the supporting pre-insert operation
620 --
621 pay_frr_ins.pre_insert
622 (p_rec => p_rec
623 ,p_effective_date => p_effective_date
624 ,p_datetrack_mode => l_datetrack_mode
625 ,p_validation_start_date => l_validation_start_date
626 ,p_validation_end_date => l_validation_end_date
627 );
628 --
629 -- Insert the row
630 --
631 pay_frr_ins.insert_dml
632 (p_rec => p_rec
633 ,p_effective_date => p_effective_date
634 ,p_datetrack_mode => l_datetrack_mode
635 ,p_validation_start_date => l_validation_start_date
636 ,p_validation_end_date => l_validation_end_date
637 );
638 --
639 -- Call the supporting post-insert operation
640 --
641 pay_frr_ins.post_insert
642 (p_rec => p_rec
643 ,p_effective_date => p_effective_date
644 ,p_datetrack_mode => l_datetrack_mode
645 ,p_validation_start_date => l_validation_start_date
646 ,p_validation_end_date => l_validation_end_date
647 );
648 --
649 -- Call to raise any errors on multi-message list
650 hr_multi_message.end_validation_set;
651 --
652 hr_utility.set_location('Leaving:'||l_proc,10);
653 end ins;
654 --
655 -- ----------------------------------------------------------------------------
656 -- |---------------------------------< ins >----------------------------------|
657 -- ----------------------------------------------------------------------------
658 Procedure ins
659 (p_effective_date in date
660 ,p_status_processing_rule_id in number
661 ,p_result_name in varchar2
662 ,p_result_rule_type in varchar2
663 ,p_business_group_id in number default null
664 ,p_legislation_code in varchar2 default null
665 ,p_element_type_id in number default null
666 ,p_legislation_subgroup in varchar2 default null
667 ,p_severity_level in varchar2 default null
668 ,p_input_value_id in number default null
669 ,p_formula_result_rule_id out nocopy number
670 ,p_object_version_number out nocopy number
671 ,p_effective_start_date out nocopy date
672 ,p_effective_end_date out nocopy date
673 ) is
674 --
675 l_rec pay_frr_shd.g_rec_type;
676 l_proc varchar2(72) := g_package||'ins';
677 --
678 Begin
679 hr_utility.set_location('Entering:'||l_proc, 5);
680 --
681 -- Call conversion function to turn arguments into the
682 -- p_rec structure.
683 --
684 l_rec :=
685 pay_frr_shd.convert_args
686 (null
687 ,null
688 ,null
689 ,p_business_group_id
690 ,p_legislation_code
691 ,p_element_type_id
692 ,p_status_processing_rule_id
693 ,p_result_name
694 ,p_result_rule_type
695 ,p_legislation_subgroup
696 ,p_severity_level
697 ,p_input_value_id
698 ,null
699 );
700 --
701 -- Having converted the arguments into the pay_frr_rec
702 -- plsql record structure we call the corresponding record
703 -- business process.
704 --
705 pay_frr_ins.ins
706 (p_effective_date
707 ,l_rec
708 );
709 --
710 -- Set the OUT arguments.
711 --
712 p_formula_result_rule_id := l_rec.formula_result_rule_id;
713 p_effective_start_date := l_rec.effective_start_date;
714 p_effective_end_date := l_rec.effective_end_date;
715 p_object_version_number := l_rec.object_version_number;
716 --
717 --
718 hr_utility.set_location(' Leaving:'||l_proc, 10);
719 End ins;
720 --
721 end pay_frr_ins;
[Home] [Help]