1 Package Body ben_bvr_ins as
2 /* $Header: bebvrrhi.pkb 120.0 2005/05/28 00:54:44 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' ben_bvr_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_bvr_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_bnft_vrbl_rt_f t
70 where t.bnft_vrbl_rt_id = p_rec.bnft_vrbl_rt_id
71 and t.effective_start_date =
72 ben_bvr_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_bnft_vrbl_rt_f.created_by%TYPE;
77 l_creation_date ben_bnft_vrbl_rt_f.creation_date%TYPE;
78 l_last_update_date ben_bnft_vrbl_rt_f.last_update_date%TYPE;
79 l_last_updated_by ben_bnft_vrbl_rt_f.last_updated_by%TYPE;
80 l_last_update_login ben_bnft_vrbl_rt_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_bnft_vrbl_rt_f',
90 p_base_key_column => 'bnft_vrbl_rt_id',
91 p_base_key_value => p_rec.bnft_vrbl_rt_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 hr_utility.set_message(801, 'HR_6153_ALL_PROCEDURE_FAIL');
116 hr_utility.set_message_token('PROCEDURE', l_proc);
117 hr_utility.set_message_token('STEP','10');
118 hr_utility.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_bvr_shd.g_api_dml := true; -- Set the api dml status
130 --
131 -- Insert the row into: ben_bnft_vrbl_rt_f
132 --
133 insert into ben_bnft_vrbl_rt_f
134 ( bnft_vrbl_rt_id,
135 effective_start_date,
136 effective_end_date,
137 cvg_amt_calc_mthd_id,
138 vrbl_rt_prfl_id,
139 business_group_id,
140 bvr_attribute_category,
141 bvr_attribute1,
142 bvr_attribute2,
143 bvr_attribute3,
144 bvr_attribute4,
145 bvr_attribute5,
146 bvr_attribute6,
147 bvr_attribute7,
148 bvr_attribute8,
149 bvr_attribute9,
150 bvr_attribute10,
151 bvr_attribute11,
152 bvr_attribute12,
153 bvr_attribute13,
154 bvr_attribute14,
155 bvr_attribute15,
156 bvr_attribute16,
157 bvr_attribute17,
158 bvr_attribute18,
159 bvr_attribute19,
160 bvr_attribute20,
161 bvr_attribute21,
162 bvr_attribute22,
163 bvr_attribute23,
164 bvr_attribute24,
165 bvr_attribute25,
166 bvr_attribute26,
167 bvr_attribute27,
168 bvr_attribute28,
169 bvr_attribute29,
170 bvr_attribute30,
171 object_version_number,
172 ordr_num
173 , created_by,
174 creation_date,
175 last_update_date,
176 last_updated_by,
177 last_update_login
178 )
179 Values
180 ( p_rec.bnft_vrbl_rt_id,
181 p_rec.effective_start_date,
182 p_rec.effective_end_date,
183 p_rec.cvg_amt_calc_mthd_id,
184 p_rec.vrbl_rt_prfl_id,
185 p_rec.business_group_id,
186 p_rec.bvr_attribute_category,
187 p_rec.bvr_attribute1,
188 p_rec.bvr_attribute2,
189 p_rec.bvr_attribute3,
190 p_rec.bvr_attribute4,
191 p_rec.bvr_attribute5,
192 p_rec.bvr_attribute6,
193 p_rec.bvr_attribute7,
194 p_rec.bvr_attribute8,
195 p_rec.bvr_attribute9,
196 p_rec.bvr_attribute10,
197 p_rec.bvr_attribute11,
198 p_rec.bvr_attribute12,
199 p_rec.bvr_attribute13,
200 p_rec.bvr_attribute14,
201 p_rec.bvr_attribute15,
202 p_rec.bvr_attribute16,
203 p_rec.bvr_attribute17,
204 p_rec.bvr_attribute18,
205 p_rec.bvr_attribute19,
206 p_rec.bvr_attribute20,
207 p_rec.bvr_attribute21,
208 p_rec.bvr_attribute22,
209 p_rec.bvr_attribute23,
210 p_rec.bvr_attribute24,
211 p_rec.bvr_attribute25,
212 p_rec.bvr_attribute26,
213 p_rec.bvr_attribute27,
214 p_rec.bvr_attribute28,
215 p_rec.bvr_attribute29,
216 p_rec.bvr_attribute30,
217 p_rec.object_version_number,
218 p_rec.ordr_num
219 , l_created_by,
220 l_creation_date,
221 l_last_update_date,
222 l_last_updated_by,
223 l_last_update_login
224 );
225 --
226 ben_bvr_shd.g_api_dml := false; -- Unset the api dml status
227 hr_utility.set_location(' Leaving:'||l_proc, 15);
228 --
229 Exception
230 When hr_api.check_integrity_violated Then
231 -- A check constraint has been violated
232 ben_bvr_shd.g_api_dml := false; -- Unset the api dml status
233 ben_bvr_shd.constraint_error
234 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
235 When hr_api.unique_integrity_violated Then
236 -- Unique integrity has been violated
237 ben_bvr_shd.g_api_dml := false; -- Unset the api dml status
238 ben_bvr_shd.constraint_error
239 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
240 When Others Then
241 ben_bvr_shd.g_api_dml := false; -- Unset the api dml status
242 Raise;
243 End dt_insert_dml;
244 --
245 -- ----------------------------------------------------------------------------
246 -- |------------------------------< insert_dml >------------------------------|
247 -- ----------------------------------------------------------------------------
248 Procedure insert_dml
249 (p_rec in out nocopy ben_bvr_shd.g_rec_type,
250 p_effective_date in date,
251 p_datetrack_mode in varchar2,
252 p_validation_start_date in date,
253 p_validation_end_date in date) is
254 --
255 l_proc varchar2(72) := g_package||'insert_dml';
256 --
257 Begin
258 hr_utility.set_location('Entering:'||l_proc, 5);
259 --
260 dt_insert_dml(p_rec => p_rec,
261 p_effective_date => p_effective_date,
262 p_datetrack_mode => p_datetrack_mode,
263 p_validation_start_date => p_validation_start_date,
264 p_validation_end_date => p_validation_end_date);
265 --
266 hr_utility.set_location(' Leaving:'||l_proc, 10);
267 End insert_dml;
268 --
269 -- ----------------------------------------------------------------------------
270 -- |------------------------------< pre_insert >------------------------------|
271 -- ----------------------------------------------------------------------------
272 -- {Start Of Comments}
273 --
274 -- Description:
275 -- This private procedure contains any processing which is required before
276 -- the insert dml. Presently, if the entity has a corresponding primary
277 -- key which is maintained by an associating sequence, the primary key for
278 -- the entity will be populated with the next sequence value in
279 -- preparation for the insert dml.
280 -- Also, if comments are defined for this entity, the comments insert
281 -- logic will also be called, generating a comment_id if required.
282 --
283 -- Prerequisites:
284 -- This is an internal procedure which is called from the ins procedure.
285 --
286 -- In Parameters:
287 -- A Pl/Sql record structre.
288 --
289 -- Post Success:
290 -- Processing continues.
291 --
292 -- Post Failure:
293 -- If an error has occurred, an error message and exception will be raised
294 -- but not handled.
295 --
296 -- Developer Implementation Notes:
297 -- Any pre-processing required before the insert dml is issued should be
298 -- coded within this procedure. As stated above, a good example is the
299 -- generation of a primary key number via a corresponding sequence.
300 -- It is important to note that any 3rd party maintenance should be reviewed
301 -- before placing in this procedure.
302 --
303 -- Access Status:
304 -- Internal Row Handler Use Only.
305 --
306 -- {End Of Comments}
307 -- ----------------------------------------------------------------------------
308 Procedure pre_insert
309 (p_rec in out nocopy ben_bvr_shd.g_rec_type,
310 p_effective_date in date,
311 p_datetrack_mode in varchar2,
312 p_validation_start_date in date,
313 p_validation_end_date in date) is
314 --
315 l_proc varchar2(72) := g_package||'pre_insert';
316 --
317 --
318 --
319 cursor c1 is
320 select ben_bnft_vrbl_rt_f_s.nextval
321 from sys.dual;
322 Begin
323 hr_utility.set_location('Entering:'||l_proc, 5);
324 --
325 --
326 --
327 --
328
329 open c1;
330 fetch c1 into p_rec.bnft_vrbl_rt_id;
331 close c1;
332 hr_utility.set_location(' Leaving:'||l_proc, 10);
333 End pre_insert;
334 --
335 -- ----------------------------------------------------------------------------
336 -- |-----------------------------< post_insert >------------------------------|
337 -- ----------------------------------------------------------------------------
338 -- {Start Of Comments}
339 --
340 -- Description:
341 -- This private procedure contains any processing which is required after the
342 -- insert dml.
343 --
344 -- Prerequisites:
345 -- This is an internal procedure which is called from the ins procedure.
346 --
347 -- In Parameters:
348 -- A Pl/Sql record structre.
349 --
350 -- Post Success:
351 -- Processing continues.
352 --
353 -- Post Failure:
354 -- If an error has occurred, an error message and exception will be raised
355 -- but not handled.
356 --
357 -- Developer Implementation Notes:
358 -- Any post-processing required after the insert dml is issued should be
359 -- coded within this procedure. It is important to note that any 3rd party
360 -- maintenance should be reviewed before placing in this procedure.
361 --
362 -- Access Status:
363 -- Internal Row Handler Use Only.
364 --
365 -- {End Of Comments}
366 -- ----------------------------------------------------------------------------
367 Procedure post_insert
368 (p_rec in ben_bvr_shd.g_rec_type,
369 p_effective_date in date,
370 p_datetrack_mode in varchar2,
371 p_validation_start_date in date,
372 p_validation_end_date in date) is
373 --
374 l_proc varchar2(72) := g_package||'post_insert';
375 --
376 Begin
377 hr_utility.set_location('Entering:'||l_proc, 5);
378 --
379 --
380 -- Start of API User Hook for post_insert.
381 --
382 begin
383 --
384 ben_bvr_rki.after_insert
385 (
386 p_bnft_vrbl_rt_id =>p_rec.bnft_vrbl_rt_id
387 ,p_effective_start_date =>p_rec.effective_start_date
388 ,p_effective_end_date =>p_rec.effective_end_date
389 ,p_cvg_amt_calc_mthd_id =>p_rec.cvg_amt_calc_mthd_id
390 ,p_vrbl_rt_prfl_id =>p_rec.vrbl_rt_prfl_id
391 ,p_business_group_id =>p_rec.business_group_id
392 ,p_bvr_attribute_category =>p_rec.bvr_attribute_category
393 ,p_bvr_attribute1 =>p_rec.bvr_attribute1
394 ,p_bvr_attribute2 =>p_rec.bvr_attribute2
395 ,p_bvr_attribute3 =>p_rec.bvr_attribute3
396 ,p_bvr_attribute4 =>p_rec.bvr_attribute4
397 ,p_bvr_attribute5 =>p_rec.bvr_attribute5
398 ,p_bvr_attribute6 =>p_rec.bvr_attribute6
399 ,p_bvr_attribute7 =>p_rec.bvr_attribute7
400 ,p_bvr_attribute8 =>p_rec.bvr_attribute8
401 ,p_bvr_attribute9 =>p_rec.bvr_attribute9
402 ,p_bvr_attribute10 =>p_rec.bvr_attribute10
403 ,p_bvr_attribute11 =>p_rec.bvr_attribute11
404 ,p_bvr_attribute12 =>p_rec.bvr_attribute12
405 ,p_bvr_attribute13 =>p_rec.bvr_attribute13
406 ,p_bvr_attribute14 =>p_rec.bvr_attribute14
407 ,p_bvr_attribute15 =>p_rec.bvr_attribute15
408 ,p_bvr_attribute16 =>p_rec.bvr_attribute16
409 ,p_bvr_attribute17 =>p_rec.bvr_attribute17
410 ,p_bvr_attribute18 =>p_rec.bvr_attribute18
411 ,p_bvr_attribute19 =>p_rec.bvr_attribute19
412 ,p_bvr_attribute20 =>p_rec.bvr_attribute20
413 ,p_bvr_attribute21 =>p_rec.bvr_attribute21
414 ,p_bvr_attribute22 =>p_rec.bvr_attribute22
415 ,p_bvr_attribute23 =>p_rec.bvr_attribute23
416 ,p_bvr_attribute24 =>p_rec.bvr_attribute24
417 ,p_bvr_attribute25 =>p_rec.bvr_attribute25
418 ,p_bvr_attribute26 =>p_rec.bvr_attribute26
419 ,p_bvr_attribute27 =>p_rec.bvr_attribute27
420 ,p_bvr_attribute28 =>p_rec.bvr_attribute28
421 ,p_bvr_attribute29 =>p_rec.bvr_attribute29
422 ,p_bvr_attribute30 =>p_rec.bvr_attribute30
423 ,p_object_version_number =>p_rec.object_version_number
424 ,p_ordr_num =>p_rec.ordr_num
425 ,p_effective_date =>p_effective_date
426 ,p_validation_start_date =>p_validation_start_date
427 ,p_validation_end_date =>p_validation_end_date
428 );
429 --
430 exception
431 --
432 when hr_api.cannot_find_prog_unit then
433 --
434 hr_api.cannot_find_prog_unit_error
435 (p_module_name => 'ben_bnft_vrbl_rt_f'
436 ,p_hook_type => 'AI');
437 --
438 end;
439 --
440 -- End of API User Hook for post_insert.
441 --
442 --
443 hr_utility.set_location(' Leaving:'||l_proc, 10);
444 End post_insert;
445 --
446 -- ----------------------------------------------------------------------------
447 -- |-------------------------------< ins_lck >--------------------------------|
448 -- ----------------------------------------------------------------------------
449 -- {Start Of Comments}
450 --
451 -- Description:
452 -- The ins_lck process has one main function to perform. When inserting
453 -- a datetracked row, we must validate the DT mode.
454 -- be manipulated.
455 --
456 -- Prerequisites:
457 -- This procedure can only be called for the datetrack mode of INSERT.
458 --
459 -- In Parameters:
460 --
461 -- Post Success:
462 -- On successful completion of the ins_lck process the parental
463 -- datetracked rows will be locked providing the p_enforce_foreign_locking
464 -- argument value is TRUE.
465 -- If the p_enforce_foreign_locking argument value is FALSE then the
466 -- parential rows are not locked.
467 --
468 -- Post Failure:
469 -- The Lck process can fail for:
470 -- 1) When attempting to lock the row the row could already be locked by
471 -- another user. This will raise the HR_Api.Object_Locked exception.
472 -- 2) When attempting to the lock the parent which doesn't exist.
473 -- For the entity to be locked the parent must exist!
474 --
475 -- Developer Implementation Notes:
476 -- None.
477 --
478 -- Access Status:
479 -- Internal Row Handler Use Only.
480 --
481 -- {End Of Comments}
482 -- ----------------------------------------------------------------------------
483 Procedure ins_lck
484 (p_effective_date in date,
485 p_datetrack_mode in varchar2,
486 p_rec in ben_bvr_shd.g_rec_type,
487 p_validation_start_date out nocopy date,
488 p_validation_end_date out nocopy date) is
489 --
490 l_proc varchar2(72) := g_package||'ins_lck';
491 l_validation_start_date date;
492 l_validation_end_date date;
493 --
494 Begin
495 hr_utility.set_location('Entering:'||l_proc, 5);
496 --
497 -- Validate the datetrack mode mode getting the validation start
498 -- and end dates for the specified datetrack operation.
499 --
500 dt_api.validate_dt_mode
501 (p_effective_date => p_effective_date,
502 p_datetrack_mode => p_datetrack_mode,
503 p_base_table_name => 'ben_bnft_vrbl_rt_f',
504 p_base_key_column => 'bnft_vrbl_rt_id',
505 p_base_key_value => p_rec.bnft_vrbl_rt_id,
506 p_parent_table_name1 => 'ben_vrbl_rt_prfl_f',
507 p_parent_key_column1 => 'vrbl_rt_prfl_id',
508 p_parent_key_value1 => p_rec.vrbl_rt_prfl_id,
509 p_parent_table_name2 => 'ben_cvg_amt_calc_mthd_f',
510 p_parent_key_column2 => 'cvg_amt_calc_mthd_id',
511 p_parent_key_value2 => p_rec.cvg_amt_calc_mthd_id,
512 p_enforce_foreign_locking => true,
513 p_validation_start_date => l_validation_start_date,
514 p_validation_end_date => l_validation_end_date);
515 --
516 -- Set the validation start and end date OUT arguments
517 --
518 p_validation_start_date := l_validation_start_date;
519 p_validation_end_date := l_validation_end_date;
520 --
521 hr_utility.set_location(' Leaving:'||l_proc, 10);
522 --
523 End ins_lck;
524 --
525 -- ----------------------------------------------------------------------------
526 -- |---------------------------------< ins >----------------------------------|
527 -- ----------------------------------------------------------------------------
528 Procedure ins
529 (
530 p_rec in out nocopy ben_bvr_shd.g_rec_type,
531 p_effective_date in date
532 ) is
533 --
534 l_proc varchar2(72) := g_package||'ins';
535 l_datetrack_mode varchar2(30) := 'INSERT';
536 l_validation_start_date date;
537 l_validation_end_date date;
538 --
539 Begin
540 hr_utility.set_location('Entering:'||l_proc, 5);
541 --
542 -- Call the lock operation
543 --
544 ins_lck
545 (p_effective_date => p_effective_date,
546 p_datetrack_mode => l_datetrack_mode,
547 p_rec => p_rec,
548 p_validation_start_date => l_validation_start_date,
549 p_validation_end_date => l_validation_end_date);
550 --
551 -- Call the supporting insert validate operations
552 --
553 ben_bvr_bus.insert_validate
554 (p_rec => p_rec,
555 p_effective_date => p_effective_date,
556 p_datetrack_mode => l_datetrack_mode,
557 p_validation_start_date => l_validation_start_date,
558 p_validation_end_date => l_validation_end_date);
559 --
560 -- Call the supporting pre-insert operation
561 --
562 pre_insert
563 (p_rec => p_rec,
564 p_effective_date => p_effective_date,
565 p_datetrack_mode => l_datetrack_mode,
566 p_validation_start_date => l_validation_start_date,
567 p_validation_end_date => l_validation_end_date);
568 --
569 -- Insert the row
570 --
571 insert_dml
572 (p_rec => p_rec,
573 p_effective_date => p_effective_date,
574 p_datetrack_mode => l_datetrack_mode,
575 p_validation_start_date => l_validation_start_date,
576 p_validation_end_date => l_validation_end_date);
577 --
578 -- Call the supporting post-insert operation
579 --
580 post_insert
581 (p_rec => p_rec,
582 p_effective_date => p_effective_date,
583 p_datetrack_mode => l_datetrack_mode,
584 p_validation_start_date => l_validation_start_date,
585 p_validation_end_date => l_validation_end_date);
586 end ins;
587 --
588 -- ----------------------------------------------------------------------------
589 -- |---------------------------------< ins >----------------------------------|
590 -- ----------------------------------------------------------------------------
591 Procedure ins
592 (
593 p_bnft_vrbl_rt_id out nocopy number,
594 p_effective_start_date out nocopy date,
595 p_effective_end_date out nocopy date,
596 p_cvg_amt_calc_mthd_id in number,
597 p_vrbl_rt_prfl_id in number,
598 p_business_group_id in number default null,
599 p_bvr_attribute_category in varchar2 default null,
600 p_bvr_attribute1 in varchar2 default null,
601 p_bvr_attribute2 in varchar2 default null,
602 p_bvr_attribute3 in varchar2 default null,
603 p_bvr_attribute4 in varchar2 default null,
604 p_bvr_attribute5 in varchar2 default null,
605 p_bvr_attribute6 in varchar2 default null,
606 p_bvr_attribute7 in varchar2 default null,
607 p_bvr_attribute8 in varchar2 default null,
608 p_bvr_attribute9 in varchar2 default null,
609 p_bvr_attribute10 in varchar2 default null,
610 p_bvr_attribute11 in varchar2 default null,
611 p_bvr_attribute12 in varchar2 default null,
612 p_bvr_attribute13 in varchar2 default null,
613 p_bvr_attribute14 in varchar2 default null,
614 p_bvr_attribute15 in varchar2 default null,
615 p_bvr_attribute16 in varchar2 default null,
616 p_bvr_attribute17 in varchar2 default null,
617 p_bvr_attribute18 in varchar2 default null,
618 p_bvr_attribute19 in varchar2 default null,
619 p_bvr_attribute20 in varchar2 default null,
620 p_bvr_attribute21 in varchar2 default null,
621 p_bvr_attribute22 in varchar2 default null,
622 p_bvr_attribute23 in varchar2 default null,
623 p_bvr_attribute24 in varchar2 default null,
624 p_bvr_attribute25 in varchar2 default null,
625 p_bvr_attribute26 in varchar2 default null,
626 p_bvr_attribute27 in varchar2 default null,
627 p_bvr_attribute28 in varchar2 default null,
628 p_bvr_attribute29 in varchar2 default null,
629 p_bvr_attribute30 in varchar2 default null,
630 p_object_version_number out nocopy number,
631 p_ordr_num in number default null,
632 p_effective_date in date
633 ) is
634 --
635 l_rec ben_bvr_shd.g_rec_type;
636 l_proc varchar2(72) := g_package||'ins';
637 --
638 Begin
639 hr_utility.set_location('Entering:'||l_proc, 5);
640 --
641 -- Call conversion function to turn arguments into the
642 -- p_rec structure.
643 --
644 l_rec :=
645 ben_bvr_shd.convert_args
646 (
647 null,
648 null,
649 null,
650 p_cvg_amt_calc_mthd_id,
651 p_vrbl_rt_prfl_id,
652 p_business_group_id,
653 p_bvr_attribute_category,
654 p_bvr_attribute1,
655 p_bvr_attribute2,
656 p_bvr_attribute3,
657 p_bvr_attribute4,
658 p_bvr_attribute5,
659 p_bvr_attribute6,
660 p_bvr_attribute7,
661 p_bvr_attribute8,
662 p_bvr_attribute9,
663 p_bvr_attribute10,
664 p_bvr_attribute11,
665 p_bvr_attribute12,
666 p_bvr_attribute13,
667 p_bvr_attribute14,
668 p_bvr_attribute15,
669 p_bvr_attribute16,
670 p_bvr_attribute17,
671 p_bvr_attribute18,
672 p_bvr_attribute19,
673 p_bvr_attribute20,
674 p_bvr_attribute21,
675 p_bvr_attribute22,
676 p_bvr_attribute23,
677 p_bvr_attribute24,
678 p_bvr_attribute25,
679 p_bvr_attribute26,
680 p_bvr_attribute27,
681 p_bvr_attribute28,
682 p_bvr_attribute29,
683 p_bvr_attribute30,
684 null,
685 p_ordr_num
686 );
687 --
688 -- Having converted the arguments into the ben_bvr_rec
689 -- plsql record structure we call the corresponding record
690 -- business process.
691 --
692 ins(l_rec, p_effective_date);
693 --
694 -- Set the OUT arguments.
695 --
696 p_bnft_vrbl_rt_id := l_rec.bnft_vrbl_rt_id;
697 p_effective_start_date := l_rec.effective_start_date;
698 p_effective_end_date := l_rec.effective_end_date;
699 p_object_version_number := l_rec.object_version_number;
700 --
701 --
702 hr_utility.set_location(' Leaving:'||l_proc, 10);
703 End ins;
704 --
705 end ben_bvr_ins;
[Home] [Help]