4 -- ----------------------------------------------------------------------------
1 Package Body ben_rgr_ins as
2 /* $Header: bergrrhi.pkb 120.2 2008/02/05 08:36:14 rtagarra ship $ */
3 --
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' ben_rgr_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_rgr_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_rptg_grp_f t
70 where t.popl_rptg_grp_id = p_rec.popl_rptg_grp_id
71 and t.effective_start_date =
72 ben_rgr_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_rptg_grp_f.created_by%TYPE;
77 l_creation_date ben_popl_rptg_grp_f.creation_date%TYPE;
78 l_last_update_date ben_popl_rptg_grp_f.last_update_date%TYPE;
79 l_last_updated_by ben_popl_rptg_grp_f.last_updated_by%TYPE;
80 l_last_update_login ben_popl_rptg_grp_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_rptg_grp_f',
90 p_base_key_column => 'popl_rptg_grp_id',
91 p_base_key_value => p_rec.popl_rptg_grp_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_rgr_shd.g_api_dml := true; -- Set the api dml status
130 --
131 -- Insert the row into: ben_popl_rptg_grp_f
132 --
133 insert into ben_popl_rptg_grp_f
134 ( popl_rptg_grp_id,
135 effective_start_date,
139 pgm_id,
136 effective_end_date,
137 business_group_id,
138 rptg_grp_id,
140 pl_id,
141 ordr_num, --iRec
142 rgr_attribute_category,
143 rgr_attribute1,
144 rgr_attribute2,
145 rgr_attribute3,
146 rgr_attribute4,
147 rgr_attribute5,
148 rgr_attribute6,
149 rgr_attribute7,
150 rgr_attribute8,
151 rgr_attribute9,
152 rgr_attribute10,
153 rgr_attribute11,
154 rgr_attribute12,
155 rgr_attribute13,
156 rgr_attribute14,
157 rgr_attribute15,
158 rgr_attribute16,
159 rgr_attribute17,
160 rgr_attribute18,
161 rgr_attribute19,
162 rgr_attribute20,
163 rgr_attribute21,
164 rgr_attribute22,
165 rgr_attribute23,
166 rgr_attribute24,
167 rgr_attribute25,
168 rgr_attribute26,
169 rgr_attribute27,
170 rgr_attribute28,
171 rgr_attribute29,
172 rgr_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.popl_rptg_grp_id,
182 p_rec.effective_start_date,
186 p_rec.pgm_id,
183 p_rec.effective_end_date,
184 p_rec.business_group_id,
185 p_rec.rptg_grp_id,
187 p_rec.pl_id,
188 p_rec.ordr_num, --iRec
189 p_rec.rgr_attribute_category,
190 p_rec.rgr_attribute1,
191 p_rec.rgr_attribute2,
192 p_rec.rgr_attribute3,
193 p_rec.rgr_attribute4,
194 p_rec.rgr_attribute5,
195 p_rec.rgr_attribute6,
196 p_rec.rgr_attribute7,
197 p_rec.rgr_attribute8,
198 p_rec.rgr_attribute9,
199 p_rec.rgr_attribute10,
200 p_rec.rgr_attribute11,
201 p_rec.rgr_attribute12,
202 p_rec.rgr_attribute13,
203 p_rec.rgr_attribute14,
204 p_rec.rgr_attribute15,
205 p_rec.rgr_attribute16,
206 p_rec.rgr_attribute17,
207 p_rec.rgr_attribute18,
208 p_rec.rgr_attribute19,
209 p_rec.rgr_attribute20,
210 p_rec.rgr_attribute21,
211 p_rec.rgr_attribute22,
212 p_rec.rgr_attribute23,
213 p_rec.rgr_attribute24,
214 p_rec.rgr_attribute25,
215 p_rec.rgr_attribute26,
216 p_rec.rgr_attribute27,
217 p_rec.rgr_attribute28,
218 p_rec.rgr_attribute29,
219 p_rec.rgr_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_rgr_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_rgr_shd.g_api_dml := false; -- Unset the api dml status
235 ben_rgr_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_rgr_shd.g_api_dml := false; -- Unset the api dml status
240 ben_rgr_shd.constraint_error
241 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
242 When Others Then
243 ben_rgr_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_rgr_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}
278 -- the insert dml. Presently, if the entity has a corresponding primary
275 --
276 -- Description:
277 -- This private procedure contains any processing which is required before
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_rgr_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 --
319 Cursor C_Sel1 is select ben_popl_rptg_grp_f_s.nextval from sys.dual;
320 --
321 --
322 Begin
323 hr_utility.set_location('Entering:'||l_proc, 5);
324 --
325 --
326 -- Select the next sequence number
327 --
328 Open C_Sel1;
329 Fetch C_Sel1 Into p_rec.popl_rptg_grp_id;
330 Close C_Sel1;
331 --
332 --
333 hr_utility.set_location(' Leaving:'||l_proc, 10);
334 End pre_insert;
335 --
336 -- ----------------------------------------------------------------------------
337 -- |-----------------------------< post_insert >------------------------------|
338 -- ----------------------------------------------------------------------------
339 -- {Start Of Comments}
340 --
341 -- Description:
342 -- This private procedure contains any processing which is required after the
343 -- insert dml.
344 --
345 -- Prerequisites:
346 -- This is an internal procedure which is called from the ins procedure.
347 --
348 -- In Parameters:
349 -- A Pl/Sql record structre.
350 --
351 -- Post Success:
352 -- Processing continues.
353 --
354 -- Post Failure:
355 -- If an error has occurred, an error message and exception will be raised
356 -- but not handled.
357 --
358 -- Developer Implementation Notes:
359 -- Any post-processing required after the insert dml is issued should be
360 -- coded within this procedure. It is important to note that any 3rd party
364 -- Internal Row Handler Use Only.
361 -- maintenance should be reviewed before placing in this procedure.
362 --
363 -- Access Status:
365 --
366 -- {End Of Comments}
367 -- ----------------------------------------------------------------------------
368 Procedure post_insert
369 (p_rec in ben_rgr_shd.g_rec_type,
370 p_effective_date in date,
371 p_datetrack_mode in varchar2,
372 p_validation_start_date in date,
373 p_validation_end_date in date) is
374 --
375 l_proc varchar2(72) := g_package||'post_insert';
376 --
377 Begin
378 hr_utility.set_location('Entering:'||l_proc, 5);
379 --
380 --
381 -- Start of API User Hook for post_insert.
382 --
383 begin
384 --
385 ben_rgr_rki.after_insert
386 (
387 p_popl_rptg_grp_id =>p_rec.popl_rptg_grp_id
388 ,p_effective_start_date =>p_rec.effective_start_date
389 ,p_effective_end_date =>p_rec.effective_end_date
390 ,p_business_group_id =>p_rec.business_group_id
391 ,p_rptg_grp_id =>p_rec.rptg_grp_id
392 ,p_pgm_id =>p_rec.pgm_id
393 ,p_pl_id =>p_rec.pl_id
397 ,p_rgr_attribute2 =>p_rec.rgr_attribute2
394 ,p_ordr_num =>p_rec.ordr_num --iRec
395 ,p_rgr_attribute_category =>p_rec.rgr_attribute_category
396 ,p_rgr_attribute1 =>p_rec.rgr_attribute1
398 ,p_rgr_attribute3 =>p_rec.rgr_attribute3
399 ,p_rgr_attribute4 =>p_rec.rgr_attribute4
400 ,p_rgr_attribute5 =>p_rec.rgr_attribute5
401 ,p_rgr_attribute6 =>p_rec.rgr_attribute6
402 ,p_rgr_attribute7 =>p_rec.rgr_attribute7
403 ,p_rgr_attribute8 =>p_rec.rgr_attribute8
404 ,p_rgr_attribute9 =>p_rec.rgr_attribute9
405 ,p_rgr_attribute10 =>p_rec.rgr_attribute10
406 ,p_rgr_attribute11 =>p_rec.rgr_attribute11
407 ,p_rgr_attribute12 =>p_rec.rgr_attribute12
408 ,p_rgr_attribute13 =>p_rec.rgr_attribute13
409 ,p_rgr_attribute14 =>p_rec.rgr_attribute14
410 ,p_rgr_attribute15 =>p_rec.rgr_attribute15
411 ,p_rgr_attribute16 =>p_rec.rgr_attribute16
412 ,p_rgr_attribute17 =>p_rec.rgr_attribute17
413 ,p_rgr_attribute18 =>p_rec.rgr_attribute18
414 ,p_rgr_attribute19 =>p_rec.rgr_attribute19
415 ,p_rgr_attribute20 =>p_rec.rgr_attribute20
416 ,p_rgr_attribute21 =>p_rec.rgr_attribute21
417 ,p_rgr_attribute22 =>p_rec.rgr_attribute22
418 ,p_rgr_attribute23 =>p_rec.rgr_attribute23
419 ,p_rgr_attribute24 =>p_rec.rgr_attribute24
420 ,p_rgr_attribute25 =>p_rec.rgr_attribute25
421 ,p_rgr_attribute26 =>p_rec.rgr_attribute26
422 ,p_rgr_attribute27 =>p_rec.rgr_attribute27
423 ,p_rgr_attribute28 =>p_rec.rgr_attribute28
424 ,p_rgr_attribute29 =>p_rec.rgr_attribute29
425 ,p_rgr_attribute30 =>p_rec.rgr_attribute30
426 ,p_object_version_number =>p_rec.object_version_number
427 ,p_effective_date =>p_effective_date
428 ,p_validation_start_date =>p_validation_start_date
429 ,p_validation_end_date =>p_validation_end_date
430 );
431 --
432 exception
433 --
434 when hr_api.cannot_find_prog_unit then
435 --
436 hr_api.cannot_find_prog_unit_error
437 (p_module_name => 'ben_popl_rptg_grp_f'
438 ,p_hook_type => 'AI');
439 --
440 end;
441 --
442 -- End of API User Hook for post_insert.
443 --
444 --
445 hr_utility.set_location(' Leaving:'||l_proc, 10);
446 End post_insert;
447 --
448 -- ----------------------------------------------------------------------------
449 -- |-------------------------------< ins_lck >--------------------------------|
450 -- ----------------------------------------------------------------------------
451 -- {Start Of Comments}
452 --
453 -- Description:
454 -- The ins_lck process has one main function to perform. When inserting
455 -- a datetracked row, we must validate the DT mode.
456 -- be manipulated.
457 --
458 -- Prerequisites:
459 -- This procedure can only be called for the datetrack mode of INSERT.
460 --
461 -- In Parameters:
462 --
463 -- Post Success:
464 -- On successful completion of the ins_lck process the parental
465 -- datetracked rows will be locked providing the p_enforce_foreign_locking
466 -- argument value is TRUE.
467 -- If the p_enforce_foreign_locking argument value is FALSE then the
468 -- parential rows are not locked.
469 --
470 -- Post Failure:
471 -- The Lck process can fail for:
472 -- 1) When attempting to lock the row the row could already be locked by
473 -- another user. This will raise the HR_Api.Object_Locked exception.
474 -- 2) When attempting to the lock the parent which doesn't exist.
475 -- For the entity to be locked the parent must exist!
476 --
477 -- Developer Implementation Notes:
478 -- None.
479 --
480 -- Access Status:
481 -- Internal Row Handler Use Only.
482 --
483 -- {End Of Comments}
484 -- ----------------------------------------------------------------------------
485 Procedure ins_lck
486 (p_effective_date in date,
487 p_datetrack_mode in varchar2,
488 p_rec in ben_rgr_shd.g_rec_type,
489 p_validation_start_date out nocopy date,
490 p_validation_end_date out nocopy date) is
491 --
492 l_proc varchar2(72) := g_package||'ins_lck';
493 l_validation_start_date date;
494 l_validation_end_date date;
495 --
496 Begin
497 hr_utility.set_location('Entering:'||l_proc, 5);
498 --
499 -- Validate the datetrack mode mode getting the validation start
500 -- and end dates for the specified datetrack operation.
501 --
502 dt_api.validate_dt_mode
503 (p_effective_date => p_effective_date,
504 p_datetrack_mode => p_datetrack_mode,
505 p_base_table_name => 'ben_popl_rptg_grp_f',
506 p_base_key_column => 'popl_rptg_grp_id',
507 p_base_key_value => p_rec.popl_rptg_grp_id,
508 p_parent_table_name1 => 'ben_pgm_f',
509 p_parent_key_column1 => 'pgm_id',
510 p_parent_key_value1 => p_rec.pgm_id,
511 p_parent_table_name2 => 'ben_pl_f',
512 p_parent_key_column2 => 'pl_id',
513 p_parent_key_value2 => p_rec.pl_id,
514 p_enforce_foreign_locking => true,
515 p_validation_start_date => l_validation_start_date,
516 p_validation_end_date => l_validation_end_date);
517 --
521 p_validation_end_date := l_validation_end_date;
518 -- Set the validation start and end date OUT arguments
519 --
520 p_validation_start_date := l_validation_start_date;
522 --
523 hr_utility.set_location(' Leaving:'||l_proc, 10);
524 --
525 End ins_lck;
526 --
527 -- ----------------------------------------------------------------------------
528 -- |---------------------------------< ins >----------------------------------|
529 -- ----------------------------------------------------------------------------
530 Procedure ins
531 (
532 p_rec in out nocopy ben_rgr_shd.g_rec_type,
533 p_effective_date in date
534 ) is
535 --
536 l_proc varchar2(72) := g_package||'ins';
537 l_datetrack_mode varchar2(30) := 'INSERT';
538 l_validation_start_date date;
539 l_validation_end_date date;
540 --
541 Begin
542 hr_utility.set_location('Entering:'||l_proc, 5);
543 --
544 -- Call the lock operation
545 --
546 ins_lck
547 (p_effective_date => p_effective_date,
548 p_datetrack_mode => l_datetrack_mode,
549 p_rec => p_rec,
550 p_validation_start_date => l_validation_start_date,
551 p_validation_end_date => l_validation_end_date);
552 --
553 -- Call the supporting insert validate operations
554 --
555 ben_rgr_bus.insert_validate
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 -- Call the supporting pre-insert operation
563 --
564 pre_insert
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 -- Insert the row
572 --
573 insert_dml
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 --
580 -- Call the supporting post-insert operation
581 --
582 post_insert
583 (p_rec => p_rec,
584 p_effective_date => p_effective_date,
585 p_datetrack_mode => l_datetrack_mode,
586 p_validation_start_date => l_validation_start_date,
587 p_validation_end_date => l_validation_end_date);
588 end ins;
589 --
590 -- ----------------------------------------------------------------------------
591 -- |---------------------------------< ins >----------------------------------|
592 -- ----------------------------------------------------------------------------
593 Procedure ins
594 (
595 p_popl_rptg_grp_id out nocopy number,
596 p_effective_start_date out nocopy date,
597 p_effective_end_date out nocopy date,
598 p_business_group_id in number,
599 p_rptg_grp_id in number default null,
600 p_pgm_id in number default null,
601 p_pl_id in number default null,
602 p_ordr_num in number default null, --iRec
603 p_rgr_attribute_category in varchar2 default null,
604 p_rgr_attribute1 in varchar2 default null,
605 p_rgr_attribute2 in varchar2 default null,
606 p_rgr_attribute3 in varchar2 default null,
607 p_rgr_attribute4 in varchar2 default null,
608 p_rgr_attribute5 in varchar2 default null,
609 p_rgr_attribute6 in varchar2 default null,
610 p_rgr_attribute7 in varchar2 default null,
611 p_rgr_attribute8 in varchar2 default null,
612 p_rgr_attribute9 in varchar2 default null,
613 p_rgr_attribute10 in varchar2 default null,
614 p_rgr_attribute11 in varchar2 default null,
615 p_rgr_attribute12 in varchar2 default null,
616 p_rgr_attribute13 in varchar2 default null,
617 p_rgr_attribute14 in varchar2 default null,
618 p_rgr_attribute15 in varchar2 default null,
619 p_rgr_attribute16 in varchar2 default null,
620 p_rgr_attribute17 in varchar2 default null,
621 p_rgr_attribute18 in varchar2 default null,
622 p_rgr_attribute19 in varchar2 default null,
626 p_rgr_attribute23 in varchar2 default null,
623 p_rgr_attribute20 in varchar2 default null,
624 p_rgr_attribute21 in varchar2 default null,
625 p_rgr_attribute22 in varchar2 default null,
627 p_rgr_attribute24 in varchar2 default null,
628 p_rgr_attribute25 in varchar2 default null,
629 p_rgr_attribute26 in varchar2 default null,
630 p_rgr_attribute27 in varchar2 default null,
631 p_rgr_attribute28 in varchar2 default null,
632 p_rgr_attribute29 in varchar2 default null,
633 p_rgr_attribute30 in varchar2 default null,
634 p_object_version_number out nocopy number,
635 p_effective_date in date
636 ) is
637 --
638 l_rec ben_rgr_shd.g_rec_type;
639 l_proc varchar2(72) := g_package||'ins';
640 --
641 Begin
642 hr_utility.set_location('Entering:'||l_proc, 5);
643 --
644 -- Call conversion function to turn arguments into the
645 -- p_rec structure.
646 --
647 l_rec :=
648 ben_rgr_shd.convert_args
649 (
650 null,
651 null,
652 null,
653 p_business_group_id,
654 p_rptg_grp_id,
655 p_pgm_id,
656 p_pl_id,
657 p_ordr_num, --iRec
658 p_rgr_attribute_category,
659 p_rgr_attribute1,
660 p_rgr_attribute2,
661 p_rgr_attribute3,
662 p_rgr_attribute4,
663 p_rgr_attribute5,
664 p_rgr_attribute6,
665 p_rgr_attribute7,
666 p_rgr_attribute8,
667 p_rgr_attribute9,
668 p_rgr_attribute10,
669 p_rgr_attribute11,
670 p_rgr_attribute12,
671 p_rgr_attribute13,
672 p_rgr_attribute14,
673 p_rgr_attribute15,
674 p_rgr_attribute16,
675 p_rgr_attribute17,
676 p_rgr_attribute18,
677 p_rgr_attribute19,
678 p_rgr_attribute20,
679 p_rgr_attribute21,
680 p_rgr_attribute22,
681 p_rgr_attribute23,
682 p_rgr_attribute24,
683 p_rgr_attribute25,
684 p_rgr_attribute26,
685 p_rgr_attribute27,
686 p_rgr_attribute28,
687 p_rgr_attribute29,
688 p_rgr_attribute30,
689 null
690 );
691 --
692 -- Having converted the arguments into the ben_rgr_rec
693 -- plsql record structure we call the corresponding record
694 -- business process.
695 --
696 ins(l_rec, p_effective_date);
697 --
698 -- Set the OUT arguments.
699 --
700 p_popl_rptg_grp_id := l_rec.popl_rptg_grp_id;
701 p_effective_start_date := l_rec.effective_start_date;
702 p_effective_end_date := l_rec.effective_end_date;
703 p_object_version_number := l_rec.object_version_number;
704 --
705 --
706 hr_utility.set_location(' Leaving:'||l_proc, 10);
707 End ins;
708 --
709 end ben_rgr_ins;
[Home] [Help]