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