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