1 Package Body ben_pst_ins as
2 /* $Header: bepstrhi.pkb 120.3 2008/02/05 08:47:53 rtagarra noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' ben_pst_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_pst_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_pstn_rt_f t
70 where t.pstn_rt_id = p_rec.pstn_rt_id
71 and t.effective_start_date =
72 ben_pst_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_pstn_rt_f.created_by%TYPE;
77 l_creation_date ben_pstn_rt_f.creation_date%TYPE;
78 l_last_update_date ben_pstn_rt_f.last_update_date%TYPE;
79 l_last_updated_by ben_pstn_rt_f.last_updated_by%TYPE;
80 l_last_update_login ben_pstn_rt_f.last_update_login%TYPE;
81 --
82 Begin
83 hr_utility.set_location('Entering:'||l_proc, 5);
84 --
85 -- Get the object version number for the insert
86 --
87 p_rec.object_version_number :=
88 dt_api.get_object_version_number
89 (p_base_table_name => 'ben_pstn_rt_f',
90 p_base_key_column => 'pstn_rt_id',
91 p_base_key_value => p_rec.pstn_rt_id);
92 --
93 -- Set the effective start and end dates to the corresponding
94 -- validation start and end dates
95 --
96 p_rec.effective_start_date := p_validation_start_date;
97 p_rec.effective_end_date := p_validation_end_date;
98 --
99 -- If the datetrack_mode is not INSERT then we must populate the WHO
100 -- columns with the 'old' creation values and 'new' updated values.
101 --
102 If (p_datetrack_mode <> 'INSERT') then
103 hr_utility.set_location(l_proc, 10);
104 --
105 -- Select the 'old' created values
106 --
107 Open C_Sel1;
108 Fetch C_Sel1 Into l_created_by, l_creation_date;
109 If C_Sel1%notfound Then
110 --
111 -- The previous 'old' created row has not been found. We need
112 -- to error as an internal datetrack problem exists.
113 --
114 Close C_Sel1;
115 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;
123 --
120 Close C_Sel1;
121 --
122 -- Set the AOL updated WHO values
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_pst_shd.g_api_dml := true; -- Set the api dml status
130 --
131 -- Insert the row into: ben_pstn_rt_f
132 --
133 insert into ben_pstn_rt_f
134 ( pstn_rt_id,
135 effective_start_date,
136 effective_end_date,
137 excld_flag,
138 ordr_num,
139 position_id,
140 vrbl_rt_prfl_id,
141 business_group_id,
142 pst_attribute_category,
143 pst_attribute1,
144 pst_attribute2,
145 pst_attribute3,
146 pst_attribute4,
147 pst_attribute5,
148 pst_attribute6,
149 pst_attribute7,
150 pst_attribute8,
151 pst_attribute9,
152 pst_attribute10,
153 pst_attribute11,
154 pst_attribute12,
155 pst_attribute13,
156 pst_attribute14,
157 pst_attribute15,
158 pst_attribute16,
159 pst_attribute17,
160 pst_attribute18,
161 pst_attribute19,
162 pst_attribute20,
163 pst_attribute21,
164 pst_attribute22,
165 pst_attribute23,
166 pst_attribute24,
167 pst_attribute25,
168 pst_attribute26,
169 pst_attribute27,
170 pst_attribute28,
171 pst_attribute29,
172 pst_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.pstn_rt_id,
182 p_rec.effective_start_date,
183 p_rec.effective_end_date,
184 p_rec.excld_flag,
185 p_rec.ordr_num,
186 p_rec.position_id,
187 p_rec.vrbl_rt_prfl_id,
188 p_rec.business_group_id,
189 p_rec.pst_attribute_category,
190 p_rec.pst_attribute1,
191 p_rec.pst_attribute2,
192 p_rec.pst_attribute3,
193 p_rec.pst_attribute4,
194 p_rec.pst_attribute5,
195 p_rec.pst_attribute6,
196 p_rec.pst_attribute7,
197 p_rec.pst_attribute8,
198 p_rec.pst_attribute9,
199 p_rec.pst_attribute10,
200 p_rec.pst_attribute11,
201 p_rec.pst_attribute12,
202 p_rec.pst_attribute13,
203 p_rec.pst_attribute14,
204 p_rec.pst_attribute15,
205 p_rec.pst_attribute16,
206 p_rec.pst_attribute17,
207 p_rec.pst_attribute18,
208 p_rec.pst_attribute19,
209 p_rec.pst_attribute20,
210 p_rec.pst_attribute21,
211 p_rec.pst_attribute22,
212 p_rec.pst_attribute23,
213 p_rec.pst_attribute24,
214 p_rec.pst_attribute25,
215 p_rec.pst_attribute26,
216 p_rec.pst_attribute27,
217 p_rec.pst_attribute28,
218 p_rec.pst_attribute29,
219 p_rec.pst_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_pst_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_pst_shd.g_api_dml := false; -- Unset the api dml status
235 ben_pst_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_pst_shd.g_api_dml := false; -- Unset the api dml status
240 ben_pst_shd.constraint_error
241 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
242 When Others Then
243 ben_pst_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_pst_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:
292 -- Processing continues.
289 -- A Pl/Sql record structre.
290 --
291 -- Post Success:
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_pst_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 c1 is
320 select BEN_PSTN_RT_F_S.nextval
321 from sys.dual;
322 --
323 --
324 Begin
325 hr_utility.set_location('Entering:'||l_proc, 5);
326 --
327 --
328 open c1;
329 --
330 fetch c1 into p_rec.pstn_rt_id;
331 --
332 close c1;
333 --
334 --
335 hr_utility.set_location(' Leaving:'||l_proc, 10);
336 End pre_insert;
337 --
338 -- ----------------------------------------------------------------------------
339 -- |-----------------------------< post_insert >------------------------------|
340 -- ----------------------------------------------------------------------------
341 -- {Start Of Comments}
342 --
343 -- Description:
344 -- This private procedure contains any processing which is required after the
345 -- insert dml.
346 --
347 -- Prerequisites:
348 -- This is an internal procedure which is called from the ins procedure.
349 --
350 -- In Parameters:
351 -- A Pl/Sql record structre.
352 --
353 -- Post Success:
354 -- Processing continues.
355 --
356 -- Post Failure:
357 -- If an error has occurred, an error message and exception will be raised
358 -- but not handled.
359 --
360 -- Developer Implementation Notes:
361 -- Any post-processing required after the insert dml is issued should be
362 -- coded within this procedure. It is important to note that any 3rd party
363 -- maintenance should be reviewed before placing in this procedure.
364 --
365 -- Access Status:
366 -- Internal Row Handler Use Only.
367 --
368 -- {End Of Comments}
369 -- ----------------------------------------------------------------------------
370 Procedure post_insert
371 (p_rec in ben_pst_shd.g_rec_type,
372 p_effective_date in date,
373 p_datetrack_mode in varchar2,
374 p_validation_start_date in date,
375 p_validation_end_date in date) is
376 --
377 l_proc varchar2(72) := g_package||'post_insert';
378 --
379 Begin
380 hr_utility.set_location('Entering:'||l_proc, 5);
381 --
382 --
383 -- Start of API User Hook for post_insert.
384 --
385 begin
386 --
387 ben_pst_rki.after_insert
388 (
389 p_pstn_rt_id =>p_rec.pstn_rt_id
390 ,p_effective_start_date =>p_rec.effective_start_date
391 ,p_effective_end_date =>p_rec.effective_end_date
392 ,p_excld_flag =>p_rec.excld_flag
393 ,p_ordr_num =>p_rec.ordr_num
394 ,p_position_id =>p_rec.position_id
395 ,p_vrbl_rt_prfl_id =>p_rec.vrbl_rt_prfl_id
396 ,p_business_group_id =>p_rec.business_group_id
397 ,p_pst_attribute_category =>p_rec.pst_attribute_category
398 ,p_pst_attribute1 =>p_rec.pst_attribute1
399 ,p_pst_attribute2 =>p_rec.pst_attribute2
400 ,p_pst_attribute3 =>p_rec.pst_attribute3
401 ,p_pst_attribute4 =>p_rec.pst_attribute4
402 ,p_pst_attribute5 =>p_rec.pst_attribute5
403 ,p_pst_attribute6 =>p_rec.pst_attribute6
404 ,p_pst_attribute7 =>p_rec.pst_attribute7
405 ,p_pst_attribute8 =>p_rec.pst_attribute8
406 ,p_pst_attribute9 =>p_rec.pst_attribute9
407 ,p_pst_attribute10 =>p_rec.pst_attribute10
408 ,p_pst_attribute11 =>p_rec.pst_attribute11
409 ,p_pst_attribute12 =>p_rec.pst_attribute12
410 ,p_pst_attribute13 =>p_rec.pst_attribute13
411 ,p_pst_attribute14 =>p_rec.pst_attribute14
412 ,p_pst_attribute15 =>p_rec.pst_attribute15
413 ,p_pst_attribute16 =>p_rec.pst_attribute16
414 ,p_pst_attribute17 =>p_rec.pst_attribute17
415 ,p_pst_attribute18 =>p_rec.pst_attribute18
416 ,p_pst_attribute19 =>p_rec.pst_attribute19
417 ,p_pst_attribute20 =>p_rec.pst_attribute20
418 ,p_pst_attribute21 =>p_rec.pst_attribute21
419 ,p_pst_attribute22 =>p_rec.pst_attribute22
420 ,p_pst_attribute23 =>p_rec.pst_attribute23
421 ,p_pst_attribute24 =>p_rec.pst_attribute24
422 ,p_pst_attribute25 =>p_rec.pst_attribute25
423 ,p_pst_attribute26 =>p_rec.pst_attribute26
424 ,p_pst_attribute27 =>p_rec.pst_attribute27
425 ,p_pst_attribute28 =>p_rec.pst_attribute28
426 ,p_pst_attribute29 =>p_rec.pst_attribute29
427 ,p_pst_attribute30 =>p_rec.pst_attribute30
428 ,p_object_version_number =>p_rec.object_version_number
432 );
429 ,p_effective_date =>p_effective_date
430 ,p_validation_start_date =>p_validation_start_date
431 ,p_validation_end_date =>p_validation_end_date
433 --
434 exception
435 --
436 when hr_api.cannot_find_prog_unit then
437 --
438 hr_api.cannot_find_prog_unit_error
439 (p_module_name => 'ben_pstn_rt_f'
440 ,p_hook_type => 'AI');
441 --
442 end;
443 --
444 -- End of API User Hook for post_insert.
445 --
446 --
447 hr_utility.set_location(' Leaving:'||l_proc, 10);
448 End post_insert;
449 --
450 -- ----------------------------------------------------------------------------
451 -- |-------------------------------< ins_lck >--------------------------------|
452 -- ----------------------------------------------------------------------------
453 -- {Start Of Comments}
454 --
455 -- Description:
456 -- The ins_lck process has one main function to perform. When inserting
457 -- a datetracked row, we must validate the DT mode.
458 -- be manipulated.
459 --
460 -- Prerequisites:
461 -- This procedure can only be called for the datetrack mode of INSERT.
462 --
463 -- In Parameters:
464 --
465 -- Post Success:
466 -- On successful completion of the ins_lck process the parental
467 -- datetracked rows will be locked providing the p_enforce_foreign_locking
468 -- argument value is TRUE.
469 -- If the p_enforce_foreign_locking argument value is FALSE then the
470 -- parential rows are not locked.
471 --
472 -- Post Failure:
473 -- The Lck process can fail for:
474 -- 1) When attempting to lock the row the row could already be locked by
475 -- another user. This will raise the HR_Api.Object_Locked exception.
476 -- 2) When attempting to the lock the parent which doesn't exist.
477 -- For the entity to be locked the parent must exist!
478 --
479 -- Developer Implementation Notes:
480 -- None.
481 --
482 -- Access Status:
483 -- Internal Row Handler Use Only.
484 --
485 -- {End Of Comments}
486 -- ----------------------------------------------------------------------------
487 Procedure ins_lck
488 (p_effective_date in date,
489 p_datetrack_mode in varchar2,
490 p_rec in ben_pst_shd.g_rec_type,
491 p_validation_start_date out nocopy date,
492 p_validation_end_date out nocopy date) is
493 --
494 l_proc varchar2(72) := g_package||'ins_lck';
495 l_validation_start_date date;
496 l_validation_end_date date;
497 --
498 Begin
499 hr_utility.set_location('Entering:'||l_proc, 5);
500 --
501 -- Validate the datetrack mode mode getting the validation start
502 -- and end dates for the specified datetrack operation.
503 --
504 dt_api.validate_dt_mode
505 (p_effective_date => p_effective_date,
506 p_datetrack_mode => p_datetrack_mode,
507 p_base_table_name => 'ben_pstn_rt_f',
508 p_base_key_column => 'pstn_rt_id',
509 p_base_key_value => p_rec.pstn_rt_id,
510 p_enforce_foreign_locking => true,
511 p_validation_start_date => l_validation_start_date,
512 p_validation_end_date => l_validation_end_date);
513 --
514 -- Set the validation start and end date OUT arguments
515 --
516 p_validation_start_date := l_validation_start_date;
517 p_validation_end_date := l_validation_end_date;
518 --
519 hr_utility.set_location(' Leaving:'||l_proc, 10);
520 --
521 End ins_lck;
522 --
523 -- ----------------------------------------------------------------------------
524 -- |---------------------------------< ins >----------------------------------|
525 -- ----------------------------------------------------------------------------
526 Procedure ins
527 (
528 p_rec in out nocopy ben_pst_shd.g_rec_type,
529 p_effective_date in date
530 ) is
531 --
532 l_proc varchar2(72) := g_package||'ins';
533 l_datetrack_mode varchar2(30) := 'INSERT';
534 l_validation_start_date date;
535 l_validation_end_date date;
536 --
537 Begin
538 hr_utility.set_location('Entering:'||l_proc, 5);
539 --
540 -- Call the lock operation
541 --
542 ins_lck
543 (p_effective_date => p_effective_date,
544 p_datetrack_mode => l_datetrack_mode,
545 p_rec => p_rec,
546 p_validation_start_date => l_validation_start_date,
547 p_validation_end_date => l_validation_end_date);
548 --
549 -- Call the supporting insert validate operations
550 --
551 ben_pst_bus.insert_validate
552 (p_rec => p_rec,
553 p_effective_date => p_effective_date,
554 p_datetrack_mode => l_datetrack_mode,
555 p_validation_start_date => l_validation_start_date,
556 p_validation_end_date => l_validation_end_date);
557 --
558 -- Call the supporting pre-insert operation
559 --
560 pre_insert
561 (p_rec => p_rec,
562 p_effective_date => p_effective_date,
563 p_datetrack_mode => l_datetrack_mode,
564 p_validation_start_date => l_validation_start_date,
565 p_validation_end_date => l_validation_end_date);
566 --
567 -- Insert the row
568 --
569 insert_dml
570 (p_rec => p_rec,
571 p_effective_date => p_effective_date,
572 p_datetrack_mode => l_datetrack_mode,
573 p_validation_start_date => l_validation_start_date,
574 p_validation_end_date => l_validation_end_date);
575 --
576 -- Call the supporting post-insert operation
577 --
578 post_insert
579 (p_rec => p_rec,
580 p_effective_date => p_effective_date,
581 p_datetrack_mode => l_datetrack_mode,
582 p_validation_start_date => l_validation_start_date,
586 -- ----------------------------------------------------------------------------
583 p_validation_end_date => l_validation_end_date);
584 end ins;
585 --
587 -- |---------------------------------< ins >----------------------------------|
588 -- ----------------------------------------------------------------------------
589 Procedure ins
590 (
591 p_pstn_rt_id out nocopy number,
592 p_effective_start_date out nocopy date,
593 p_effective_end_date out nocopy date,
594 p_excld_flag in varchar2 default 'N',
595 p_ordr_num in number default null,
596 p_position_id in number,
597 p_vrbl_rt_prfl_id in number,
598 p_business_group_id in number,
599 p_pst_attribute_category in varchar2 default null,
600 p_pst_attribute1 in varchar2 default null,
601 p_pst_attribute2 in varchar2 default null,
602 p_pst_attribute3 in varchar2 default null,
603 p_pst_attribute4 in varchar2 default null,
604 p_pst_attribute5 in varchar2 default null,
605 p_pst_attribute6 in varchar2 default null,
606 p_pst_attribute7 in varchar2 default null,
607 p_pst_attribute8 in varchar2 default null,
608 p_pst_attribute9 in varchar2 default null,
609 p_pst_attribute10 in varchar2 default null,
610 p_pst_attribute11 in varchar2 default null,
611 p_pst_attribute12 in varchar2 default null,
612 p_pst_attribute13 in varchar2 default null,
613 p_pst_attribute14 in varchar2 default null,
614 p_pst_attribute15 in varchar2 default null,
615 p_pst_attribute16 in varchar2 default null,
616 p_pst_attribute17 in varchar2 default null,
617 p_pst_attribute18 in varchar2 default null,
618 p_pst_attribute19 in varchar2 default null,
619 p_pst_attribute20 in varchar2 default null,
620 p_pst_attribute21 in varchar2 default null,
621 p_pst_attribute22 in varchar2 default null,
622 p_pst_attribute23 in varchar2 default null,
623 p_pst_attribute24 in varchar2 default null,
624 p_pst_attribute25 in varchar2 default null,
625 p_pst_attribute26 in varchar2 default null,
626 p_pst_attribute27 in varchar2 default null,
627 p_pst_attribute28 in varchar2 default null,
628 p_pst_attribute29 in varchar2 default null,
629 p_pst_attribute30 in varchar2 default null,
630 p_object_version_number out nocopy number,
631 p_effective_date in date
632 ) is
633 --
634 l_rec ben_pst_shd.g_rec_type;
635 l_proc varchar2(72) := g_package||'ins';
636 --
637 Begin
638 hr_utility.set_location('Entering:'||l_proc, 5);
639 --
640 -- Call conversion function to turn arguments into the
641 -- p_rec structure.
642 --
643 l_rec :=
644 ben_pst_shd.convert_args
645 (
646 null,
647 null,
648 null,
649 p_excld_flag,
650 p_ordr_num,
651 p_position_id,
652 p_vrbl_rt_prfl_id,
653 p_business_group_id,
654 p_pst_attribute_category,
655 p_pst_attribute1,
656 p_pst_attribute2,
657 p_pst_attribute3,
658 p_pst_attribute4,
659 p_pst_attribute5,
660 p_pst_attribute6,
661 p_pst_attribute7,
662 p_pst_attribute8,
663 p_pst_attribute9,
664 p_pst_attribute10,
665 p_pst_attribute11,
666 p_pst_attribute12,
667 p_pst_attribute13,
668 p_pst_attribute14,
669 p_pst_attribute15,
670 p_pst_attribute16,
671 p_pst_attribute17,
672 p_pst_attribute18,
673 p_pst_attribute19,
674 p_pst_attribute20,
675 p_pst_attribute21,
676 p_pst_attribute22,
677 p_pst_attribute23,
678 p_pst_attribute24,
679 p_pst_attribute25,
680 p_pst_attribute26,
681 p_pst_attribute27,
682 p_pst_attribute28,
683 p_pst_attribute29,
684 p_pst_attribute30,
685 null
686 );
687 --
688 -- Having converted the arguments into the ben_pst_rec
689 -- plsql record structure we call the corresponding record
690 -- business process.
691 --
692 ins(l_rec, p_effective_date);
693 --
694 -- Set the OUT arguments.
695 --
696 p_pstn_rt_id := l_rec.pstn_rt_id;
697 p_effective_start_date := l_rec.effective_start_date;
698 p_effective_end_date := l_rec.effective_end_date;
699 p_object_version_number := l_rec.object_version_number;
700 --
701 --
702 hr_utility.set_location(' Leaving:'||l_proc, 10);
703 End ins;
704 --
705 end ben_pst_ins;
[Home] [Help]