1 Package Body ben_pet_ins as
2 /* $Header: bepetrhi.pkb 120.1 2006/03/07 23:43:30 abparekh noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' ben_pet_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_pet_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_popl_enrt_typ_cycl_f t
70 where t.popl_enrt_typ_cycl_id = p_rec.popl_enrt_typ_cycl_id
71 and t.effective_start_date =
72 ben_pet_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_popl_enrt_typ_cycl_f.created_by%TYPE;
77 l_creation_date ben_popl_enrt_typ_cycl_f.creation_date%TYPE;
78 l_last_update_date ben_popl_enrt_typ_cycl_f.last_update_date%TYPE;
79 l_last_updated_by ben_popl_enrt_typ_cycl_f.last_updated_by%TYPE;
80 l_last_update_login ben_popl_enrt_typ_cycl_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_popl_enrt_typ_cycl_f',
90 p_base_key_column => 'popl_enrt_typ_cycl_id',
91 p_base_key_value => p_rec.popl_enrt_typ_cycl_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_pet_shd.g_api_dml := true; -- Set the api dml status
130 --
131 -- Insert the row into: ben_popl_enrt_typ_cycl_f
132 --
133 insert into ben_popl_enrt_typ_cycl_f
134 ( popl_enrt_typ_cycl_id,
135 effective_start_date,
136 effective_end_date,
137 business_group_id,
138 enrt_typ_cycl_cd,
139 pl_id,
140 pgm_id,
141 pet_attribute_category,
142 pet_attribute1,
143 pet_attribute2,
144 pet_attribute3,
145 pet_attribute4,
146 pet_attribute5,
147 pet_attribute6,
148 pet_attribute7,
149 pet_attribute8,
150 pet_attribute9,
151 pet_attribute10,
152 pet_attribute11,
153 pet_attribute12,
154 pet_attribute13,
155 pet_attribute14,
156 pet_attribute15,
157 pet_attribute16,
158 pet_attribute17,
159 pet_attribute18,
160 pet_attribute19,
161 pet_attribute20,
162 pet_attribute21,
163 pet_attribute22,
164 pet_attribute23,
165 pet_attribute24,
166 pet_attribute25,
167 pet_attribute26,
168 pet_attribute27,
169 pet_attribute28,
170 pet_attribute29,
171 pet_attribute30,
172 object_version_number
173 , created_by,
174 creation_date,
175 last_update_date,
176 last_updated_by,
177 last_update_login
178 )
179 Values
180 ( p_rec.popl_enrt_typ_cycl_id,
181 p_rec.effective_start_date,
182 p_rec.effective_end_date,
183 p_rec.business_group_id,
184 p_rec.enrt_typ_cycl_cd,
185 p_rec.pl_id,
186 p_rec.pgm_id,
187 p_rec.pet_attribute_category,
188 p_rec.pet_attribute1,
189 p_rec.pet_attribute2,
190 p_rec.pet_attribute3,
191 p_rec.pet_attribute4,
192 p_rec.pet_attribute5,
193 p_rec.pet_attribute6,
194 p_rec.pet_attribute7,
195 p_rec.pet_attribute8,
196 p_rec.pet_attribute9,
197 p_rec.pet_attribute10,
198 p_rec.pet_attribute11,
199 p_rec.pet_attribute12,
200 p_rec.pet_attribute13,
201 p_rec.pet_attribute14,
202 p_rec.pet_attribute15,
203 p_rec.pet_attribute16,
204 p_rec.pet_attribute17,
205 p_rec.pet_attribute18,
206 p_rec.pet_attribute19,
207 p_rec.pet_attribute20,
208 p_rec.pet_attribute21,
209 p_rec.pet_attribute22,
210 p_rec.pet_attribute23,
211 p_rec.pet_attribute24,
212 p_rec.pet_attribute25,
213 p_rec.pet_attribute26,
214 p_rec.pet_attribute27,
215 p_rec.pet_attribute28,
216 p_rec.pet_attribute29,
217 p_rec.pet_attribute30,
218 p_rec.object_version_number
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_pet_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_pet_shd.g_api_dml := false; -- Unset the api dml status
233 ben_pet_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_pet_shd.g_api_dml := false; -- Unset the api dml status
238 ben_pet_shd.constraint_error
239 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
240 When Others Then
241 ben_pet_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_pet_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_pet_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 Cursor C_Sel1 is select ben_popl_enrt_typ_cycl_f_s.nextval from sys.dual;
319 --
320 Begin
321 hr_utility.set_location('Entering:'||l_proc, 5);
322 --
323 --
324 Open C_Sel1;
325 Fetch C_Sel1 Into p_rec.popl_enrt_typ_cycl_id;
326 Close C_Sel1;
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_pet_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_pet_rki.after_insert
382 (
383 p_popl_enrt_typ_cycl_id =>p_rec.popl_enrt_typ_cycl_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_enrt_typ_cycl_cd =>p_rec.enrt_typ_cycl_cd
388 ,p_pl_id =>p_rec.pl_id
389 ,p_pgm_id =>p_rec.pgm_id
390 ,p_pet_attribute_category =>p_rec.pet_attribute_category
391 ,p_pet_attribute1 =>p_rec.pet_attribute1
392 ,p_pet_attribute2 =>p_rec.pet_attribute2
393 ,p_pet_attribute3 =>p_rec.pet_attribute3
394 ,p_pet_attribute4 =>p_rec.pet_attribute4
395 ,p_pet_attribute5 =>p_rec.pet_attribute5
396 ,p_pet_attribute6 =>p_rec.pet_attribute6
397 ,p_pet_attribute7 =>p_rec.pet_attribute7
398 ,p_pet_attribute8 =>p_rec.pet_attribute8
399 ,p_pet_attribute9 =>p_rec.pet_attribute9
400 ,p_pet_attribute10 =>p_rec.pet_attribute10
401 ,p_pet_attribute11 =>p_rec.pet_attribute11
402 ,p_pet_attribute12 =>p_rec.pet_attribute12
403 ,p_pet_attribute13 =>p_rec.pet_attribute13
404 ,p_pet_attribute14 =>p_rec.pet_attribute14
405 ,p_pet_attribute15 =>p_rec.pet_attribute15
406 ,p_pet_attribute16 =>p_rec.pet_attribute16
407 ,p_pet_attribute17 =>p_rec.pet_attribute17
408 ,p_pet_attribute18 =>p_rec.pet_attribute18
409 ,p_pet_attribute19 =>p_rec.pet_attribute19
410 ,p_pet_attribute20 =>p_rec.pet_attribute20
411 ,p_pet_attribute21 =>p_rec.pet_attribute21
412 ,p_pet_attribute22 =>p_rec.pet_attribute22
413 ,p_pet_attribute23 =>p_rec.pet_attribute23
414 ,p_pet_attribute24 =>p_rec.pet_attribute24
415 ,p_pet_attribute25 =>p_rec.pet_attribute25
416 ,p_pet_attribute26 =>p_rec.pet_attribute26
417 ,p_pet_attribute27 =>p_rec.pet_attribute27
418 ,p_pet_attribute28 =>p_rec.pet_attribute28
419 ,p_pet_attribute29 =>p_rec.pet_attribute29
420 ,p_pet_attribute30 =>p_rec.pet_attribute30
421 ,p_object_version_number =>p_rec.object_version_number
422 ,p_effective_date =>p_effective_date
423 ,p_validation_start_date =>p_validation_start_date
424 ,p_validation_end_date =>p_validation_end_date
425 );
426 --
427 exception
428 --
429 when hr_api.cannot_find_prog_unit then
430 --
431 hr_api.cannot_find_prog_unit_error
432 (p_module_name => 'ben_popl_enrt_typ_cycl_f'
433 ,p_hook_type => 'AI');
434 --
435 end;
436 --
437 -- End of API User Hook for post_insert.
438 --
439 --
440 hr_utility.set_location(' Leaving:'||l_proc, 10);
441 End post_insert;
442 --
443 -- ----------------------------------------------------------------------------
444 -- |-------------------------------< ins_lck >--------------------------------|
445 -- ----------------------------------------------------------------------------
446 -- {Start Of Comments}
447 --
448 -- Description:
449 -- The ins_lck process has one main function to perform. When inserting
450 -- a datetracked row, we must validate the DT mode.
451 -- be manipulated.
452 --
453 -- Prerequisites:
454 -- This procedure can only be called for the datetrack mode of INSERT.
455 --
456 -- In Parameters:
457 --
458 -- Post Success:
459 -- On successful completion of the ins_lck process the parental
460 -- datetracked rows will be locked providing the p_enforce_foreign_locking
461 -- argument value is TRUE.
462 -- If the p_enforce_foreign_locking argument value is FALSE then the
463 -- parential rows are not locked.
464 --
465 -- Post Failure:
466 -- The Lck process can fail for:
467 -- 1) When attempting to lock the row the row could already be locked by
468 -- another user. This will raise the HR_Api.Object_Locked exception.
469 -- 2) When attempting to the lock the parent which doesn't exist.
470 -- For the entity to be locked the parent must exist!
471 --
472 -- Developer Implementation Notes:
473 -- None.
474 --
475 -- Access Status:
476 -- Internal Row Handler Use Only.
477 --
478 -- {End Of Comments}
479 -- ----------------------------------------------------------------------------
480 Procedure ins_lck
481 (p_effective_date in date,
482 p_datetrack_mode in varchar2,
483 p_rec in ben_pet_shd.g_rec_type,
484 p_validation_start_date out nocopy date,
485 p_validation_end_date out nocopy date) is
486 --
487 l_proc varchar2(72) := g_package||'ins_lck';
488 l_validation_start_date date;
489 l_validation_end_date date;
490 --
491 Begin
492 hr_utility.set_location('Entering:'||l_proc, 5);
493 --
494 -- Validate the datetrack mode mode getting the validation start
495 -- and end dates for the specified datetrack operation.
496 --
497 dt_api.validate_dt_mode
498 (p_effective_date => p_effective_date,
499 p_datetrack_mode => p_datetrack_mode,
500 p_base_table_name => 'ben_popl_enrt_typ_cycl_f',
501 p_base_key_column => 'popl_enrt_typ_cycl_id',
502 p_base_key_value => p_rec.popl_enrt_typ_cycl_id,
503 p_parent_table_name1 => 'ben_pl_f',
504 p_parent_key_column1 => 'pl_id',
505 p_parent_key_value1 => p_rec.pl_id,
506 p_parent_table_name2 => 'ben_pgm_f',
507 p_parent_key_column2 => 'pgm_id',
508 p_parent_key_value2 => p_rec.pgm_id,
509 p_enforce_foreign_locking => true,
510 p_validation_start_date => l_validation_start_date,
511 p_validation_end_date => l_validation_end_date);
512 --
513 -- Set the validation start and end date OUT arguments
514 --
515 p_validation_start_date := l_validation_start_date;
516 p_validation_end_date := l_validation_end_date;
517 --
518 hr_utility.set_location(' Leaving:'||l_proc, 10);
519 --
520 End ins_lck;
521 --
522 -- ----------------------------------------------------------------------------
523 -- |---------------------------------< ins >----------------------------------|
524 -- ----------------------------------------------------------------------------
525 Procedure ins
526 (
527 p_rec in out nocopy ben_pet_shd.g_rec_type,
528 p_effective_date in date
529 ) is
530 --
531 l_proc varchar2(72) := g_package||'ins';
532 l_datetrack_mode varchar2(30) := 'INSERT';
533 l_validation_start_date date;
534 l_validation_end_date date;
535 --
536 Begin
537 hr_utility.set_location('Entering:'||l_proc, 5);
538 --
539 -- Call the lock operation
540 --
541 ins_lck
542 (p_effective_date => p_effective_date,
543 p_datetrack_mode => l_datetrack_mode,
544 p_rec => p_rec,
545 p_validation_start_date => l_validation_start_date,
546 p_validation_end_date => l_validation_end_date);
547 --
548 -- Call the supporting insert validate operations
549 --
550 ben_pet_bus.insert_validate
551 (p_rec => p_rec,
552 p_effective_date => p_effective_date,
553 p_datetrack_mode => l_datetrack_mode,
554 p_validation_start_date => l_validation_start_date,
555 p_validation_end_date => l_validation_end_date);
556 --
557 -- Call the supporting pre-insert operation
558 --
559 pre_insert
560 (p_rec => p_rec,
561 p_effective_date => p_effective_date,
562 p_datetrack_mode => l_datetrack_mode,
563 p_validation_start_date => l_validation_start_date,
564 p_validation_end_date => l_validation_end_date);
565 --
566 -- Insert the row
567 --
568 insert_dml
569 (p_rec => p_rec,
570 p_effective_date => p_effective_date,
571 p_datetrack_mode => l_datetrack_mode,
572 p_validation_start_date => l_validation_start_date,
573 p_validation_end_date => l_validation_end_date);
574 --
575 -- Call the supporting post-insert operation
576 --
577 post_insert
578 (p_rec => p_rec,
579 p_effective_date => p_effective_date,
580 p_datetrack_mode => l_datetrack_mode,
581 p_validation_start_date => l_validation_start_date,
582 p_validation_end_date => l_validation_end_date);
583 end ins;
584 --
585 -- ----------------------------------------------------------------------------
586 -- |---------------------------------< ins >----------------------------------|
587 -- ----------------------------------------------------------------------------
588 Procedure ins
589 (
590 p_popl_enrt_typ_cycl_id out nocopy number,
591 p_effective_start_date out nocopy date,
592 p_effective_end_date out nocopy date,
593 p_business_group_id in number,
594 p_enrt_typ_cycl_cd in varchar2,
595 p_pl_id in number default null,
596 p_pgm_id in number default null,
597 p_pet_attribute_category in varchar2 default null,
598 p_pet_attribute1 in varchar2 default null,
599 p_pet_attribute2 in varchar2 default null,
600 p_pet_attribute3 in varchar2 default null,
601 p_pet_attribute4 in varchar2 default null,
602 p_pet_attribute5 in varchar2 default null,
603 p_pet_attribute6 in varchar2 default null,
604 p_pet_attribute7 in varchar2 default null,
605 p_pet_attribute8 in varchar2 default null,
606 p_pet_attribute9 in varchar2 default null,
607 p_pet_attribute10 in varchar2 default null,
608 p_pet_attribute11 in varchar2 default null,
609 p_pet_attribute12 in varchar2 default null,
610 p_pet_attribute13 in varchar2 default null,
611 p_pet_attribute14 in varchar2 default null,
612 p_pet_attribute15 in varchar2 default null,
613 p_pet_attribute16 in varchar2 default null,
614 p_pet_attribute17 in varchar2 default null,
615 p_pet_attribute18 in varchar2 default null,
616 p_pet_attribute19 in varchar2 default null,
617 p_pet_attribute20 in varchar2 default null,
618 p_pet_attribute21 in varchar2 default null,
619 p_pet_attribute22 in varchar2 default null,
620 p_pet_attribute23 in varchar2 default null,
621 p_pet_attribute24 in varchar2 default null,
622 p_pet_attribute25 in varchar2 default null,
623 p_pet_attribute26 in varchar2 default null,
624 p_pet_attribute27 in varchar2 default null,
625 p_pet_attribute28 in varchar2 default null,
626 p_pet_attribute29 in varchar2 default null,
627 p_pet_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_pet_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_pet_shd.convert_args
643 (
644 null,
645 null,
646 null,
647 p_business_group_id,
648 p_enrt_typ_cycl_cd,
649 p_pl_id,
650 p_pgm_id,
651 p_pet_attribute_category,
652 p_pet_attribute1,
653 p_pet_attribute2,
654 p_pet_attribute3,
655 p_pet_attribute4,
656 p_pet_attribute5,
657 p_pet_attribute6,
658 p_pet_attribute7,
659 p_pet_attribute8,
660 p_pet_attribute9,
661 p_pet_attribute10,
662 p_pet_attribute11,
663 p_pet_attribute12,
664 p_pet_attribute13,
665 p_pet_attribute14,
666 p_pet_attribute15,
667 p_pet_attribute16,
668 p_pet_attribute17,
669 p_pet_attribute18,
670 p_pet_attribute19,
671 p_pet_attribute20,
672 p_pet_attribute21,
673 p_pet_attribute22,
674 p_pet_attribute23,
675 p_pet_attribute24,
676 p_pet_attribute25,
677 p_pet_attribute26,
678 p_pet_attribute27,
679 p_pet_attribute28,
680 p_pet_attribute29,
681 p_pet_attribute30,
682 null
683 );
684 --
685 -- Having converted the arguments into the ben_pet_rec
686 -- plsql record structure we call the corresponding record
687 -- business process.
688 --
689 ins(l_rec, p_effective_date);
690 --
691 -- Set the OUT arguments.
692 --
693 p_popl_enrt_typ_cycl_id := l_rec.popl_enrt_typ_cycl_id;
694 p_effective_start_date := l_rec.effective_start_date;
695 p_effective_end_date := l_rec.effective_end_date;
696 p_object_version_number := l_rec.object_version_number;
697 --
698 --
699 hr_utility.set_location(' Leaving:'||l_proc, 10);
700 End ins;
701 --
702 end ben_pet_ins;