1 Package Body ben_opp_ins as
2 /* $Header: beopprhi.pkb 115.5 2003/09/25 00:28:55 rpgupta ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' ben_opp_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_opp_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_oiplip_f t
70 where t.oiplip_id = p_rec.oiplip_id
71 and t.effective_start_date =
72 ben_opp_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_oiplip_f.created_by%TYPE;
77 l_creation_date ben_oiplip_f.creation_date%TYPE;
78 l_last_update_date ben_oiplip_f.last_update_date%TYPE;
79 l_last_updated_by ben_oiplip_f.last_updated_by%TYPE;
80 l_last_update_login ben_oiplip_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_oiplip_f',
90 p_base_key_column => 'oiplip_id',
91 p_base_key_value => p_rec.oiplip_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_opp_shd.g_api_dml := true; -- Set the api dml status
130 --
131 -- Insert the row into: ben_oiplip_f
132 --
133 insert into ben_oiplip_f
134 ( oiplip_id,
135 effective_start_date,
136 effective_end_date,
137 oipl_id,
138 plip_id,
139 business_group_id,
140 legislation_code,
141 legislation_subgroup,
142 opp_attribute_category,
143 opp_attribute1,
144 opp_attribute2,
145 opp_attribute3,
146 opp_attribute4,
147 opp_attribute5,
148 opp_attribute6,
149 opp_attribute7,
150 opp_attribute8,
151 opp_attribute9,
152 opp_attribute10,
153 opp_attribute11,
154 opp_attribute12,
155 opp_attribute13,
156 opp_attribute14,
157 opp_attribute15,
158 opp_attribute16,
159 opp_attribute17,
160 opp_attribute18,
161 opp_attribute19,
162 opp_attribute20,
163 opp_attribute21,
164 opp_attribute22,
165 opp_attribute23,
166 opp_attribute24,
167 opp_attribute25,
168 opp_attribute26,
169 opp_attribute27,
170 opp_attribute28,
171 opp_attribute29,
172 opp_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.oiplip_id,
182 p_rec.effective_start_date,
183 p_rec.effective_end_date,
184 p_rec.oipl_id,
185 p_rec.plip_id,
186 p_rec.business_group_id,
187 p_rec.legislation_code,
188 p_rec.legislation_subgroup,
189 p_rec.opp_attribute_category,
190 p_rec.opp_attribute1,
191 p_rec.opp_attribute2,
192 p_rec.opp_attribute3,
193 p_rec.opp_attribute4,
194 p_rec.opp_attribute5,
195 p_rec.opp_attribute6,
196 p_rec.opp_attribute7,
197 p_rec.opp_attribute8,
198 p_rec.opp_attribute9,
199 p_rec.opp_attribute10,
200 p_rec.opp_attribute11,
201 p_rec.opp_attribute12,
202 p_rec.opp_attribute13,
203 p_rec.opp_attribute14,
204 p_rec.opp_attribute15,
205 p_rec.opp_attribute16,
206 p_rec.opp_attribute17,
207 p_rec.opp_attribute18,
208 p_rec.opp_attribute19,
209 p_rec.opp_attribute20,
210 p_rec.opp_attribute21,
211 p_rec.opp_attribute22,
212 p_rec.opp_attribute23,
213 p_rec.opp_attribute24,
214 p_rec.opp_attribute25,
215 p_rec.opp_attribute26,
216 p_rec.opp_attribute27,
217 p_rec.opp_attribute28,
218 p_rec.opp_attribute29,
219 p_rec.opp_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_opp_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_opp_shd.g_api_dml := false; -- Unset the api dml status
235 ben_opp_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_opp_shd.g_api_dml := false; -- Unset the api dml status
240 ben_opp_shd.constraint_error
241 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
242 When Others Then
243 ben_opp_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_opp_shd.g_rec_type,
252 p_effective_date in date,
253 p_datetrack_mode in varchar2,
254 p_validation_start_date in date,
255 p_validation_end_date in date) is
256 --
257 l_proc varchar2(72) := g_package||'insert_dml';
258 --
259 Begin
260 hr_utility.set_location('Entering:'||l_proc, 5);
261 --
262 dt_insert_dml(p_rec => p_rec,
263 p_effective_date => p_effective_date,
264 p_datetrack_mode => p_datetrack_mode,
265 p_validation_start_date => p_validation_start_date,
266 p_validation_end_date => p_validation_end_date);
267 --
268 hr_utility.set_location(' Leaving:'||l_proc, 10);
269 End insert_dml;
270 --
271 -- ----------------------------------------------------------------------------
272 -- |------------------------------< pre_insert >------------------------------|
273 -- ----------------------------------------------------------------------------
274 -- {Start Of Comments}
275 --
276 -- Description:
277 -- This private procedure contains any processing which is required before
278 -- the insert dml. Presently, if the entity has a corresponding primary
279 -- key which is maintained by an associating sequence, the primary key for
280 -- the entity will be populated with the next sequence value in
281 -- preparation for the insert dml.
282 -- Also, if comments are defined for this entity, the comments insert
283 -- logic will also be called, generating a comment_id if required.
284 --
285 -- Prerequisites:
286 -- This is an internal procedure which is called from the ins procedure.
287 --
288 -- In Parameters:
289 -- A Pl/Sql record structre.
290 --
291 -- Post Success:
292 -- Processing continues.
293 --
294 -- Post Failure:
295 -- If an error has occurred, an error message and exception will be raised
296 -- but not handled.
297 --
298 -- Developer Implementation Notes:
299 -- Any pre-processing required before the insert dml is issued should be
300 -- coded within this procedure. As stated above, a good example is the
301 -- generation of a primary key number via a corresponding sequence.
302 -- It is important to note that any 3rd party maintenance should be reviewed
303 -- before placing in this procedure.
304 --
305 -- Access Status:
306 -- Internal Row Handler Use Only.
307 --
308 -- {End Of Comments}
309 -- ----------------------------------------------------------------------------
310 Procedure pre_insert
311 (p_rec in out nocopy ben_opp_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_oiplip_f_s.nextval from sys.dual;
320 --
321 Begin
322 hr_utility.set_location('Entering:'||l_proc, 5);
323 --
324 --
325 -- Select the next sequence number
326 --
327 Open C_Sel1;
328 Fetch C_Sel1 Into p_rec.oiplip_id;
329 Close C_Sel1;
330 --
331 --
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_opp_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_opp_rki.after_insert
385 (
386 p_oiplip_id =>p_rec.oiplip_id
387 ,p_effective_start_date =>p_rec.effective_start_date
388 ,p_effective_end_date =>p_rec.effective_end_date
389 ,p_oipl_id =>p_rec.oipl_id
390 ,p_plip_id =>p_rec.plip_id
391 ,p_business_group_id =>p_rec.business_group_id
392 ,p_legislation_code =>p_rec.legislation_code
393 ,p_legislation_subgroup =>p_rec.legislation_subgroup
394 ,p_opp_attribute_category =>p_rec.opp_attribute_category
395 ,p_opp_attribute1 =>p_rec.opp_attribute1
396 ,p_opp_attribute2 =>p_rec.opp_attribute2
397 ,p_opp_attribute3 =>p_rec.opp_attribute3
398 ,p_opp_attribute4 =>p_rec.opp_attribute4
399 ,p_opp_attribute5 =>p_rec.opp_attribute5
400 ,p_opp_attribute6 =>p_rec.opp_attribute6
401 ,p_opp_attribute7 =>p_rec.opp_attribute7
402 ,p_opp_attribute8 =>p_rec.opp_attribute8
403 ,p_opp_attribute9 =>p_rec.opp_attribute9
404 ,p_opp_attribute10 =>p_rec.opp_attribute10
405 ,p_opp_attribute11 =>p_rec.opp_attribute11
406 ,p_opp_attribute12 =>p_rec.opp_attribute12
407 ,p_opp_attribute13 =>p_rec.opp_attribute13
408 ,p_opp_attribute14 =>p_rec.opp_attribute14
409 ,p_opp_attribute15 =>p_rec.opp_attribute15
410 ,p_opp_attribute16 =>p_rec.opp_attribute16
411 ,p_opp_attribute17 =>p_rec.opp_attribute17
412 ,p_opp_attribute18 =>p_rec.opp_attribute18
413 ,p_opp_attribute19 =>p_rec.opp_attribute19
414 ,p_opp_attribute20 =>p_rec.opp_attribute20
415 ,p_opp_attribute21 =>p_rec.opp_attribute21
416 ,p_opp_attribute22 =>p_rec.opp_attribute22
417 ,p_opp_attribute23 =>p_rec.opp_attribute23
418 ,p_opp_attribute24 =>p_rec.opp_attribute24
419 ,p_opp_attribute25 =>p_rec.opp_attribute25
420 ,p_opp_attribute26 =>p_rec.opp_attribute26
421 ,p_opp_attribute27 =>p_rec.opp_attribute27
422 ,p_opp_attribute28 =>p_rec.opp_attribute28
423 ,p_opp_attribute29 =>p_rec.opp_attribute29
424 ,p_opp_attribute30 =>p_rec.opp_attribute30
425 ,p_object_version_number =>p_rec.object_version_number
426 ,p_effective_date =>p_effective_date
427 ,p_validation_start_date =>p_validation_start_date
428 ,p_validation_end_date =>p_validation_end_date
429 );
430 --
431 exception
432 --
433 when hr_api.cannot_find_prog_unit then
434 --
435 hr_api.cannot_find_prog_unit_error
436 (p_module_name => 'ben_oiplip_f'
437 ,p_hook_type => 'AI');
438 --
439 end;
440 --
441 -- End of API User Hook for post_insert.
442 --
443 --
444 hr_utility.set_location(' Leaving:'||l_proc, 10);
445 End post_insert;
446 --
447 -- ----------------------------------------------------------------------------
448 -- |-------------------------------< ins_lck >--------------------------------|
449 -- ----------------------------------------------------------------------------
450 -- {Start Of Comments}
451 --
452 -- Description:
453 -- The ins_lck process has one main function to perform. When inserting
454 -- a datetracked row, we must validate the DT mode.
455 -- be manipulated.
456 --
457 -- Prerequisites:
458 -- This procedure can only be called for the datetrack mode of INSERT.
459 --
460 -- In Parameters:
461 --
462 -- Post Success:
463 -- On successful completion of the ins_lck process the parental
464 -- datetracked rows will be locked providing the p_enforce_foreign_locking
465 -- argument value is TRUE.
466 -- If the p_enforce_foreign_locking argument value is FALSE then the
467 -- parential rows are not locked.
468 --
469 -- Post Failure:
470 -- The Lck process can fail for:
471 -- 1) When attempting to lock the row the row could already be locked by
472 -- another user. This will raise the HR_Api.Object_Locked exception.
473 -- 2) When attempting to the lock the parent which doesn't exist.
474 -- For the entity to be locked the parent must exist!
475 --
476 -- Developer Implementation Notes:
477 -- None.
478 --
479 -- Access Status:
480 -- Internal Row Handler Use Only.
481 --
482 -- {End Of Comments}
483 -- ----------------------------------------------------------------------------
484 Procedure ins_lck
485 (p_effective_date in date,
486 p_datetrack_mode in varchar2,
487 p_rec in ben_opp_shd.g_rec_type,
488 p_validation_start_date out nocopy date,
489 p_validation_end_date out nocopy date) is
490 --
491 l_proc varchar2(72) := g_package||'ins_lck';
492 l_validation_start_date date;
493 l_validation_end_date date;
494 --
495 Begin
496 hr_utility.set_location('Entering:'||l_proc, 5);
497 --
498 -- Validate the datetrack mode mode getting the validation start
499 -- and end dates for the specified datetrack operation.
500 --
501 dt_api.validate_dt_mode
502 (p_effective_date => p_effective_date,
503 p_datetrack_mode => p_datetrack_mode,
504 p_base_table_name => 'ben_oiplip_f',
505 p_base_key_column => 'oiplip_id',
506 p_base_key_value => p_rec.oiplip_id,
507 p_parent_table_name1 => 'ben_oipl_f',
508 p_parent_key_column1 => 'oipl_id',
509 p_parent_key_value1 => p_rec.oipl_id,
510 p_parent_table_name2 => 'ben_plip_f',
511 p_parent_key_column2 => 'plip_id',
512 p_parent_key_value2 => p_rec.plip_id,
513 p_enforce_foreign_locking => false,
514 p_validation_start_date => l_validation_start_date,
515 p_validation_end_date => l_validation_end_date);
516 --
517 -- Set the validation start and end date OUT arguments
518 --
519 p_validation_start_date := l_validation_start_date;
520 p_validation_end_date := l_validation_end_date;
521 --
522 hr_utility.set_location(' Leaving:'||l_proc, 10);
523 --
524 End ins_lck;
525 --
526 -- ----------------------------------------------------------------------------
527 -- |---------------------------------< ins >----------------------------------|
528 -- ----------------------------------------------------------------------------
529 Procedure ins
530 (
531 p_rec in out nocopy ben_opp_shd.g_rec_type,
532 p_effective_date in date
533 ) is
534 --
535 l_proc varchar2(72) := g_package||'ins';
536 l_datetrack_mode varchar2(30) := 'INSERT';
537 l_validation_start_date date;
538 l_validation_end_date date;
539 --
540 Begin
541 hr_utility.set_location('Entering:'||l_proc, 5);
542 --
543 -- Call the lock operation
544 --
545 ins_lck
546 (p_effective_date => p_effective_date,
547 p_datetrack_mode => l_datetrack_mode,
548 p_rec => p_rec,
549 p_validation_start_date => l_validation_start_date,
550 p_validation_end_date => l_validation_end_date);
551 --
552 -- Call the supporting insert validate operations
553 --
554 ben_opp_bus.insert_validate
555 (p_rec => p_rec,
556 p_effective_date => p_effective_date,
557 p_datetrack_mode => l_datetrack_mode,
558 p_validation_start_date => l_validation_start_date,
559 p_validation_end_date => l_validation_end_date);
560 --
561 -- Call the supporting pre-insert operation
562 --
563 pre_insert
564 (p_rec => p_rec,
565 p_effective_date => p_effective_date,
566 p_datetrack_mode => l_datetrack_mode,
567 p_validation_start_date => l_validation_start_date,
568 p_validation_end_date => l_validation_end_date);
569 --
570 -- Insert the row
571 --
572 insert_dml
573 (p_rec => p_rec,
574 p_effective_date => p_effective_date,
575 p_datetrack_mode => l_datetrack_mode,
576 p_validation_start_date => l_validation_start_date,
577 p_validation_end_date => l_validation_end_date);
578 --
579 -- Call the supporting post-insert operation
580 --
581 post_insert
582 (p_rec => p_rec,
583 p_effective_date => p_effective_date,
584 p_datetrack_mode => l_datetrack_mode,
585 p_validation_start_date => l_validation_start_date,
586 p_validation_end_date => l_validation_end_date);
587 end ins;
588 --
589 -- ----------------------------------------------------------------------------
590 -- |---------------------------------< ins >----------------------------------|
591 -- ----------------------------------------------------------------------------
592 Procedure ins
593 (
594 p_oiplip_id out nocopy number,
595 p_effective_start_date out nocopy date,
596 p_effective_end_date out nocopy date,
597 p_oipl_id in number,
598 p_plip_id in number,
599 p_business_group_id in number,
600 p_legislation_code in varchar2 default null,
601 p_legislation_subgroup in varchar2 default null,
602 p_opp_attribute_category in varchar2 default null,
603 p_opp_attribute1 in varchar2 default null,
604 p_opp_attribute2 in varchar2 default null,
605 p_opp_attribute3 in varchar2 default null,
606 p_opp_attribute4 in varchar2 default null,
607 p_opp_attribute5 in varchar2 default null,
608 p_opp_attribute6 in varchar2 default null,
609 p_opp_attribute7 in varchar2 default null,
610 p_opp_attribute8 in varchar2 default null,
611 p_opp_attribute9 in varchar2 default null,
612 p_opp_attribute10 in varchar2 default null,
613 p_opp_attribute11 in varchar2 default null,
614 p_opp_attribute12 in varchar2 default null,
615 p_opp_attribute13 in varchar2 default null,
616 p_opp_attribute14 in varchar2 default null,
617 p_opp_attribute15 in varchar2 default null,
618 p_opp_attribute16 in varchar2 default null,
619 p_opp_attribute17 in varchar2 default null,
620 p_opp_attribute18 in varchar2 default null,
621 p_opp_attribute19 in varchar2 default null,
622 p_opp_attribute20 in varchar2 default null,
623 p_opp_attribute21 in varchar2 default null,
624 p_opp_attribute22 in varchar2 default null,
625 p_opp_attribute23 in varchar2 default null,
626 p_opp_attribute24 in varchar2 default null,
627 p_opp_attribute25 in varchar2 default null,
628 p_opp_attribute26 in varchar2 default null,
629 p_opp_attribute27 in varchar2 default null,
630 p_opp_attribute28 in varchar2 default null,
631 p_opp_attribute29 in varchar2 default null,
632 p_opp_attribute30 in varchar2 default null,
633 p_object_version_number out nocopy number,
634 p_effective_date in date
635 ) is
636 --
637 l_rec ben_opp_shd.g_rec_type;
638 l_proc varchar2(72) := g_package||'ins';
639 --
640 Begin
641 hr_utility.set_location('Entering:'||l_proc, 5);
642 --
643 -- Call conversion function to turn arguments into the
644 -- p_rec structure.
645 --
646 l_rec :=
647 ben_opp_shd.convert_args
648 (
649 null,
650 null,
651 null,
652 p_oipl_id,
653 p_plip_id,
654 p_business_group_id,
655 p_legislation_code,
656 p_legislation_subgroup,
657 p_opp_attribute_category,
658 p_opp_attribute1,
659 p_opp_attribute2,
660 p_opp_attribute3,
661 p_opp_attribute4,
662 p_opp_attribute5,
663 p_opp_attribute6,
664 p_opp_attribute7,
665 p_opp_attribute8,
666 p_opp_attribute9,
667 p_opp_attribute10,
668 p_opp_attribute11,
669 p_opp_attribute12,
670 p_opp_attribute13,
671 p_opp_attribute14,
672 p_opp_attribute15,
673 p_opp_attribute16,
674 p_opp_attribute17,
675 p_opp_attribute18,
676 p_opp_attribute19,
677 p_opp_attribute20,
678 p_opp_attribute21,
679 p_opp_attribute22,
680 p_opp_attribute23,
681 p_opp_attribute24,
682 p_opp_attribute25,
683 p_opp_attribute26,
684 p_opp_attribute27,
685 p_opp_attribute28,
686 p_opp_attribute29,
687 p_opp_attribute30,
688 null
689 );
690 --
691 -- Having converted the arguments into the ben_opp_rec
692 -- plsql record structure we call the corresponding record
693 -- business process.
694 --
695 ins(l_rec, p_effective_date);
696 --
697 -- Set the OUT arguments.
698 --
699 p_oiplip_id := l_rec.oiplip_id;
700 p_effective_start_date := l_rec.effective_start_date;
701 p_effective_end_date := l_rec.effective_end_date;
702 p_object_version_number := l_rec.object_version_number;
703 --
704 --
705 hr_utility.set_location(' Leaving:'||l_proc, 10);
706 End ins;
707 --
708 end ben_opp_ins;
[Home] [Help]