1 Package ben_vpf_shd AUTHID CURRENT_USER as
2 /* $Header: bevpfrhi.pkh 120.0.12010000.1 2008/07/29 13:07:58 appldev ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Global Record Type Specification |
6 -- ----------------------------------------------------------------------------
7 --
8 Type g_rec_type Is Record
9 (
10 vrbl_rt_prfl_id number(15),
11 effective_start_date date,
12 effective_end_date date,
13 pl_typ_opt_typ_id number(15),
14 pl_id number(15),
15 oipl_id number(15),
16 comp_lvl_fctr_id number(15),
17 business_group_id number(15),
18 acty_typ_cd varchar2(30),
19 rt_typ_cd varchar2(30),
20 bnft_rt_typ_cd varchar2(30),
21 tx_typ_cd varchar2(30),
22 vrbl_rt_trtmt_cd varchar2(30),
23 acty_ref_perd_cd varchar2(30),
24 mlt_cd varchar2(30),
25 incrmnt_elcn_val number, --(15,6),
26 dflt_elcn_val number, --(15,6),
27 mx_elcn_val number, --(15,6),
28 mn_elcn_val number, --(15,6),
29 lwr_lmt_val number,
30 lwr_lmt_calc_rl number(15),
31 upr_lmt_val number,
32 upr_lmt_calc_rl number(15),
33 ultmt_upr_lmt number,
34 ultmt_lwr_lmt number,
35 ultmt_upr_lmt_calc_rl number(15),
36 ultmt_lwr_lmt_calc_rl number(15),
37 ann_mn_elcn_val number,
38 ann_mx_elcn_val number,
39 val number, --(15,6),
40 name varchar2(240),
41 no_mn_elcn_val_dfnd_flag varchar2(30),
42 no_mx_elcn_val_dfnd_flag varchar2(30),
43 alwys_sum_all_cvg_flag varchar2(30),
44 alwys_cnt_all_prtts_flag varchar2(30),
45 val_calc_rl number(15),
46 vrbl_rt_prfl_stat_cd varchar2(30),
47 vrbl_usg_cd varchar2(30),
48 asmt_to_use_cd varchar2(30),
49 rndg_cd varchar2(30),
50 rndg_rl number(15),
51 rt_hrly_slrd_flag varchar2(30),
52 rt_pstl_cd_flag varchar2(30),
53 rt_lbr_mmbr_flag varchar2(30),
54 rt_lgl_enty_flag varchar2(30),
55 rt_benfts_grp_flag varchar2(30),
56 rt_wk_loc_flag varchar2(30),
57 rt_brgng_unit_flag varchar2(30),
58 rt_age_flag varchar2(30),
59 rt_los_flag varchar2(30),
60 rt_per_typ_flag varchar2(30),
61 rt_fl_tm_pt_tm_flag varchar2(30),
62 rt_ee_stat_flag varchar2(30),
63 rt_grd_flag varchar2(30),
64 rt_pct_fl_tm_flag varchar2(30),
65 rt_asnt_set_flag varchar2(30),
66 rt_hrs_wkd_flag varchar2(30),
67 rt_comp_lvl_flag varchar2(30),
68 rt_org_unit_flag varchar2(30),
69 rt_loa_rsn_flag varchar2(30),
70 rt_pyrl_flag varchar2(30),
71 rt_schedd_hrs_flag varchar2(30),
72 rt_py_bss_flag varchar2(30),
73 rt_prfl_rl_flag varchar2(30),
74 rt_cmbn_age_los_flag varchar2(30),
75 rt_prtt_pl_flag varchar2(30),
76 rt_svc_area_flag varchar2(30),
77 rt_ppl_grp_flag varchar2(30),
78 rt_dsbld_flag varchar2(30),
79 rt_hlth_cvg_flag varchar2(30),
80 rt_poe_flag varchar2(30),
81 rt_ttl_cvg_vol_flag varchar2(30),
82 rt_ttl_prtt_flag varchar2(30),
83 rt_gndr_flag varchar2(30),
84 rt_tbco_use_flag varchar2(30),
85 vpf_attribute_category varchar2(30),
86 vpf_attribute1 varchar2(150),
87 vpf_attribute2 varchar2(150),
88 vpf_attribute3 varchar2(150),
89 vpf_attribute4 varchar2(150),
90 vpf_attribute5 varchar2(150),
91 vpf_attribute6 varchar2(150),
92 vpf_attribute7 varchar2(150),
93 vpf_attribute8 varchar2(150),
94 vpf_attribute9 varchar2(150),
95 vpf_attribute10 varchar2(150),
96 vpf_attribute11 varchar2(150),
97 vpf_attribute12 varchar2(150),
98 vpf_attribute13 varchar2(150),
99 vpf_attribute14 varchar2(150),
100 vpf_attribute15 varchar2(150),
101 vpf_attribute16 varchar2(150),
102 vpf_attribute17 varchar2(150),
103 vpf_attribute18 varchar2(150),
104 vpf_attribute19 varchar2(150),
105 vpf_attribute20 varchar2(150),
106 vpf_attribute21 varchar2(150),
107 vpf_attribute22 varchar2(150),
108 vpf_attribute23 varchar2(150),
109 vpf_attribute24 varchar2(150),
110 vpf_attribute25 varchar2(150),
111 vpf_attribute26 varchar2(150),
112 vpf_attribute27 varchar2(150),
113 vpf_attribute28 varchar2(150),
114 vpf_attribute29 varchar2(150),
115 vpf_attribute30 varchar2(150),
116 object_version_number number(9),
117 rt_cntng_prtn_prfl_flag varchar2(30),
118 rt_cbr_quald_bnf_flag varchar2(30),
119 rt_optd_mdcr_flag varchar2(30),
120 rt_lvg_rsn_flag varchar2(30),
121 rt_pstn_flag varchar2(30),
122 rt_comptncy_flag varchar2(30),
123 rt_job_flag varchar2(30),
124 rt_qual_titl_flag varchar2(30),
125 rt_dpnt_cvrd_pl_flag varchar2(30),
126 rt_dpnt_cvrd_plip_flag varchar2(30),
127 rt_dpnt_cvrd_ptip_flag varchar2(30),
128 rt_dpnt_cvrd_pgm_flag varchar2(30),
129 rt_enrld_oipl_flag varchar2(30),
130 rt_enrld_pl_flag varchar2(30),
131 rt_enrld_plip_flag varchar2(30),
132 rt_enrld_ptip_flag varchar2(30),
133 rt_enrld_pgm_flag varchar2(30),
134 rt_prtt_anthr_pl_flag varchar2(30),
135 rt_othr_ptip_flag varchar2(30),
136 rt_no_othr_cvg_flag varchar2(30),
137 rt_dpnt_othr_ptip_flag varchar2(30),
138 rt_qua_in_gr_flag varchar2(30),
139 rt_perf_rtng_flag varchar2(30),
140 rt_elig_prfl_flag varchar2(30)
141 );
142 --
143 -- ----------------------------------------------------------------------------
144 -- | Global Definitions - Internal Development Use Only |
145 -- ----------------------------------------------------------------------------
146 --
147 g_old_rec g_rec_type; -- Global record definition
148 g_api_dml boolean; -- Global api dml status
149 --
150 -- ----------------------------------------------------------------------------
151 -- |------------------------< return_api_dml_status >-------------------------|
152 -- ----------------------------------------------------------------------------
153 -- {Start Of Comments}
154 --
155 -- Description:
156 -- This function will return the current g_api_dml private global
157 -- boolean status.
158 -- The g_api_dml status determines if at the time of the function
159 -- being executed if a dml statement (i.e. INSERT, UPDATE or DELETE)
160 -- is being issued from within an api.
161 -- If the status is TRUE then a dml statement is being issued from
162 -- within this entity api.
163 -- This function is primarily to support database triggers which
164 -- need to maintain the object_version_number for non-supported
165 -- dml statements (i.e. dml statement issued outside of the api layer).
166 --
167 -- Prerequisites:
168 -- None.
169 --
170 -- In Parameters:
171 -- None.
172 --
173 -- Post Success:
174 -- Processing continues.
175 -- If the function returns a TRUE value then, dml is being executed from
176 -- within this api.
177 --
178 -- Post Failure:
179 -- None.
180 --
181 -- Access Status:
182 -- Internal Row Handler Use Only.
183 --
184 -- {End Of Comments}
185 -- ----------------------------------------------------------------------------
186 Function return_api_dml_status Return Boolean;
187 --
188 -- ----------------------------------------------------------------------------
189 -- |---------------------------< constraint_error >---------------------------|
190 -- ----------------------------------------------------------------------------
191 -- {Start Of Comments}
192 --
193 -- Description:
194 -- This procedure is called when a constraint has been violated (i.e.
195 -- The exception hr_api.check_integrity_violated,
196 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
197 -- hr_api.unique_integrity_violated has been raised).
198 -- The exceptions can only be raised as follows:
199 -- 1) A check constraint can only be violated during an INSERT or UPDATE
200 -- dml operation.
201 -- 2) A parent integrity constraint can only be violated during an
202 -- INSERT or UPDATE dml operation.
203 -- 3) A child integrity constraint can only be violated during an
204 -- DELETE dml operation.
205 -- 4) A unique integrity constraint can only be violated during INSERT or
206 -- UPDATE dml operation.
207 --
208 -- Prerequisites:
209 -- 1) Either hr_api.check_integrity_violated,
210 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
211 -- hr_api.unique_integrity_violated has been raised with the subsequent
212 -- stripping of the constraint name from the generated error message
213 -- text.
214 -- 2) Standalone validation test which corresponds with a constraint error.
215 --
216 -- In Parameter:
217 -- p_constraint_name is in upper format and is just the constraint name
218 -- (e.g. not prefixed by brackets, schema owner etc).
219 --
220 -- Post Success:
221 -- Development dependant.
222 --
223 -- Post Failure:
224 -- Developement dependant.
225 --
226 -- Developer Implementation Notes:
227 -- For each constraint being checked the hr system package failure message
228 -- has been generated as a template only. These system error messages should
229 -- be modified as required (i.e. change the system failure message to a user
230 -- friendly defined error message).
231 --
232 -- Access Status:
233 -- Internal Development Use Only.
234 --
235 -- {End Of Comments}
236 -- ----------------------------------------------------------------------------
237 Procedure constraint_error
238 (p_constraint_name in all_constraints.constraint_name%TYPE);
239 --
240 -- ----------------------------------------------------------------------------
241 -- |-----------------------------< api_updating >-----------------------------|
242 -- ----------------------------------------------------------------------------
243 -- {Start Of Comments}
244 --
245 -- Description:
246 -- This function is used to populate the g_old_rec record with the current
247 -- row from the database for the specified primary key provided that the
248 -- primary key exists, and is valid, and does not already match the current
249 -- g_old_rec.
250 -- The function will always return a TRUE value if the g_old_rec is
251 -- populated with the current row. A FALSE value will be returned if all of
252 -- the primary key arguments are null.
253 --
254 -- Prerequisites:
255 -- None.
256 --
257 -- In Parameters:
258 --
259 -- Post Success:
260 -- A value of TRUE will be returned indiciating that the g_old_rec is
261 -- current.
262 -- A value of FALSE will be returned if all of the primary key arguments
263 -- have a null value (this indicates that the row has not be inserted into
264 -- the Schema), and therefore could never have a corresponding row.
265 --
266 -- Post Failure:
267 -- A failure can only occur under two circumstances:
268 -- 1) The primary key is invalid (i.e. a row does not exist for the
269 -- specified primary key values).
270 -- 2) If an object_version_number exists but is NOT the same as the current
271 -- g_old_rec value.
272 --
273 -- Developer Implementation Notes:
274 -- None.
275 --
276 -- Access Status:
277 -- Internal Development Use Only.
278 --
279 -- {End Of Comments}
280 -- ----------------------------------------------------------------------------
281 Function api_updating
282 (p_effective_date in date,
283 p_vrbl_rt_prfl_id in number,
284 p_object_version_number in number
285 ) Return Boolean;
286 --
287 -- ----------------------------------------------------------------------------
288 -- |--------------------------< find_dt_del_modes >---------------------------|
289 -- ----------------------------------------------------------------------------
290 -- {Start Of Comments}
291 --
292 -- Description:
293 -- This procedure is used to determine what datetrack delete modes are
294 -- allowed as of the effective date for this entity. The procedure will
295 -- return a corresponding Boolean value for each of the delete modes
296 -- available where TRUE indicates that the corresponding delete mode is
297 -- available.
298 --
299 -- Prerequisites:
300 -- None.
301 --
302 -- In Parameters:
303 -- p_effective_date
304 -- Specifies the date at which the datetrack modes will be operated on.
305 -- p_base_key_value
306 -- Specifies the primary key value for this datetrack entity.
307 -- (E.g. For this entity the assignment of the argument would be:
308 -- p_base_key_value = :vrbl_rt_prfl_id).
309 --
310 -- Post Success:
311 -- Processing continues.
312 --
313 -- Post Failure:
314 -- Failure might occur if for the specified effective date and primary key
315 -- value a row doesn't exist.
316 --
317 -- Developer Implementation Notes:
318 -- This procedure could require changes if this entity has any sepcific
319 -- delete restrictions.
320 -- For example, this entity might disallow the datetrack delete mode of
321 -- ZAP. To implement this you would have to set and return a Boolean value
322 -- of FALSE after the call to the dt_api.find_dt_del_modes procedure.
323 --
324 -- Access Status:
325 -- Internal Development Use Only.
326 --
327 -- {End Of Comments}
328 -- ----------------------------------------------------------------------------
329 Procedure find_dt_del_modes
330 (p_effective_date in date,
331 p_base_key_value in number,
332 p_zap out nocopy boolean,
333 p_delete out nocopy boolean,
334 p_future_change out nocopy boolean,
335 p_delete_next_change out nocopy boolean);
336 --
337 -- ----------------------------------------------------------------------------
338 -- |--------------------------< find_dt_upd_modes >---------------------------|
339 -- ----------------------------------------------------------------------------
340 -- {Start Of Comments}
341 --
342 -- Description:
343 -- This procedure is used to determine what datetrack update modes are
344 -- allowed as of the effective date for this entity. The procedure will
345 -- return a corresponding Boolean value for each of the update modes
346 -- available where TRUE indicates that the corresponding update mode
347 -- is available.
348 --
349 -- Prerequisites:
350 -- None.
351 --
352 -- In Parameters:
356 -- Specifies the primary key value for this datetrack entity.
353 -- p_effective_date
354 -- Specifies the date at which the datetrack modes will be operated on.
355 -- p_base_key_value
357 -- (E.g. For this entity the assignment of the argument would be:
358 -- p_base_key_value = :vrbl_rt_prfl_id).
359 --
360 -- Post Success:
361 -- Processing continues.
362 --
363 -- Post Failure:
364 -- Failure might occur if for the specified effective date and primary key
365 -- value a row doesn't exist.
366 --
367 -- Developer Implementation Notes:
368 -- This procedure could require changes if this entity has any sepcific
369 -- delete restrictions.
370 -- For example, this entity might disallow the datetrack update mode of
371 -- UPDATE. To implement this you would have to set and return a Boolean
372 -- value of FALSE after the call to the dt_api.find_dt_upd_modes procedure.
373 --
374 -- Access Status:
375 -- Internal Development Use Only.
376 --
377 -- {End Of Comments}
378 -- ----------------------------------------------------------------------------
379 Procedure find_dt_upd_modes
380 (p_effective_date in date,
381 p_base_key_value in number,
382 p_correction out nocopy boolean,
383 p_update out nocopy boolean,
384 p_update_override out nocopy boolean,
385 p_update_change_insert out nocopy boolean);
386 --
387 -- ----------------------------------------------------------------------------
388 -- |------------------------< upd_effective_end_date >------------------------|
389 -- ----------------------------------------------------------------------------
390 -- {Start Of Comments}
391 --
392 -- Description:
393 -- This procedure will update the specified datetrack row with the
394 -- specified new effective end date. The object version number is also
395 -- set to the next object version number. DateTrack modes which call
396 -- this procedure are: UPDATE, UPDATE_CHANGE_INSERT,
397 -- UPDATE_OVERRIDE, DELETE, FUTURE_CHANGE and DELETE_NEXT_CHANGE.
398 -- This is an internal datetrack maintenance procedure which should
399 -- not be modified in anyway.
400 --
401 -- Prerequisites:
402 -- None.
403 --
404 -- In Parameters:
405 -- p_new_effective_end_date
406 -- Specifies the new effective end date which will be set for the
407 -- row as of the effective date.
408 -- p_base_key_value
409 -- Specifies the primary key value for this datetrack entity.
410 -- (E.g. For this entity the assignment of the argument would be:
411 -- p_base_key_value = :vrbl_rt_prfl_id).
412 --
413 -- Post Success:
414 -- The specified row will be updated with the new effective end date and
415 -- object_version_number.
416 --
417 -- Post Failure:
418 -- Failure might occur if for the specified effective date and primary key
419 -- value a row doesn't exist.
420 --
421 -- Developer Implementation Notes:
422 -- This is an internal datetrack maintenance procedure which should
423 -- not be modified in anyway.
424 --
425 -- Access Status:
426 -- Internal Row Handler Use Only.
427 --
428 -- {End Of Comments}
429 -- ----------------------------------------------------------------------------
430 Procedure upd_effective_end_date
431 (p_effective_date in date,
432 p_base_key_value in number,
433 p_new_effective_end_date in date,
434 p_validation_start_date in date,
435 p_validation_end_date in date,
436 p_object_version_number out nocopy number);
437 --
438 -- ----------------------------------------------------------------------------
439 -- |---------------------------------< lck >----------------------------------|
440 -- ----------------------------------------------------------------------------
441 -- {Start Of Comments}
442 --
443 -- Description:
444 -- The Lck process for datetrack is complicated and comprises of the
445 -- following processing
446 -- The processing steps are as follows:
447 -- 1) The row to be updated or deleted must be locked.
448 -- By locking this row, the g_old_rec record data type is populated.
449 -- 2) If a comment exists the text is selected from hr_comments.
450 -- 3) The datetrack mode is then validated to ensure the operation is
451 -- valid. If the mode is valid the validation start and end dates for
452 -- the mode will be derived and returned. Any required locking is
453 -- completed when the datetrack mode is validated.
454 --
455 -- Prerequisites:
456 -- When attempting to call the lck procedure the object version number,
457 -- primary key, effective date and datetrack mode must be specified.
458 --
459 -- In Parameters:
460 -- p_effective_date
461 -- Specifies the date of the datetrack update operation.
462 -- p_datetrack_mode
463 -- Determines the datetrack update or delete mode.
464 --
465 -- Post Success:
466 -- On successful completion of the Lck process the row to be updated or
467 -- deleted will be locked and selected into the global data structure
468 -- g_old_rec.
469 --
470 -- Post Failure:
471 -- The Lck process can fail for three reasons:
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) The row which is required to be locked doesn't exist in the HR Schema.
478 -- version number than the object version number specified.
475 -- This error is trapped and reported using the message name
476 -- 'HR_7220_INVALID_PRIMARY_KEY'.
477 -- 3) The row although existing in the HR Schema has a different object
479 -- This error is trapped and reported using the message name
480 -- 'HR_7155_OBJECT_INVALID'.
481 --
482 -- Developer Implementation Notes:
483 -- None.
484 --
485 -- Access Status:
486 -- Internal Development Use Only.
487 --
488 -- {End Of Comments}
489 -- ----------------------------------------------------------------------------
490 Procedure lck
491 (p_effective_date in date,
492 p_datetrack_mode in varchar2,
493 p_vrbl_rt_prfl_id in number,
494 p_object_version_number in number,
495 p_validation_start_date out nocopy date,
496 p_validation_end_date out nocopy date);
497 --
498 -- ----------------------------------------------------------------------------
499 -- |-----------------------------< convert_args >-----------------------------|
500 -- ----------------------------------------------------------------------------
501 -- {Start Of Comments}
502 --
503 -- Description:
504 -- This function is used to turn attribute parameters into the record
505 -- structure parameter g_rec_type.
506 --
507 -- Prerequisites:
508 -- This is a private function and can only be called from the ins or upd
509 -- attribute processes.
510 --
511 -- In Parameters:
512 --
513 -- Post Success:
514 -- A returning record structure will be returned.
515 --
516 -- Post Failure:
517 -- No direct error handling is required within this function. Any possible
518 -- errors within this function will be a PL/SQL value error due to conversion
519 -- of datatypes or data lengths.
520 --
521 -- Developer Implementation Notes:
522 -- None.
523 --
524 -- Access Status:
525 -- Internal Row Handler Use Only.
526 --
527 -- {End Of Comments}
528 -- ----------------------------------------------------------------------------
529 Function convert_args
530 (
531 p_vrbl_rt_prfl_id in number,
532 p_effective_start_date in date,
533 p_effective_end_date in date,
534 p_pl_typ_opt_typ_id in number,
535 p_pl_id in number,
536 p_oipl_id in number,
537 p_comp_lvl_fctr_id in number,
538 p_business_group_id in number,
539 p_acty_typ_cd in varchar2,
540 p_rt_typ_cd in varchar2,
541 p_bnft_rt_typ_cd in varchar2,
542 p_tx_typ_cd in varchar2,
543 p_vrbl_rt_trtmt_cd in varchar2,
544 p_acty_ref_perd_cd in varchar2,
545 p_mlt_cd in varchar2,
546 p_incrmnt_elcn_val in number,
547 p_dflt_elcn_val in number,
548 p_mx_elcn_val in number,
549 p_mn_elcn_val in number,
550 p_lwr_lmt_val in number,
551 p_lwr_lmt_calc_rl in number,
552 p_upr_lmt_val in number,
553 p_upr_lmt_calc_rl in number,
554 p_ultmt_upr_lmt in number,
555 p_ultmt_lwr_lmt in number,
556 p_ultmt_upr_lmt_calc_rl in number,
557 p_ultmt_lwr_lmt_calc_rl in number,
558 p_ann_mn_elcn_val in number,
559 p_ann_mx_elcn_val in number,
560 p_val in number,
561 p_name in varchar2,
562 p_no_mn_elcn_val_dfnd_flag in varchar2,
563 p_no_mx_elcn_val_dfnd_flag in varchar2,
564 p_alwys_sum_all_cvg_flag in varchar2,
565 p_alwys_cnt_all_prtts_flag in varchar2,
566 p_val_calc_rl in number,
567 p_vrbl_rt_prfl_stat_cd in varchar2,
568 p_vrbl_usg_cd in varchar2,
569 p_asmt_to_use_cd in varchar2,
570 p_rndg_cd in varchar2,
571 p_rndg_rl in number,
572 p_rt_hrly_slrd_flag in varchar2,
573 p_rt_pstl_cd_flag in varchar2,
574 p_rt_lbr_mmbr_flag in varchar2,
575 p_rt_lgl_enty_flag in varchar2,
576 p_rt_benfts_grp_flag in varchar2,
577 p_rt_wk_loc_flag in varchar2,
578 p_rt_brgng_unit_flag in varchar2,
579 p_rt_age_flag in varchar2,
580 p_rt_los_flag in varchar2,
581 p_rt_per_typ_flag in varchar2,
582 p_rt_fl_tm_pt_tm_flag in varchar2,
583 p_rt_ee_stat_flag in varchar2,
584 p_rt_grd_flag in varchar2,
585 p_rt_pct_fl_tm_flag in varchar2,
586 p_rt_asnt_set_flag in varchar2,
587 p_rt_hrs_wkd_flag in varchar2,
588 p_rt_comp_lvl_flag in varchar2,
589 p_rt_org_unit_flag in varchar2,
590 p_rt_loa_rsn_flag in varchar2,
591 p_rt_pyrl_flag in varchar2,
592 p_rt_schedd_hrs_flag in varchar2,
593 p_rt_py_bss_flag in varchar2,
594 p_rt_prfl_rl_flag in varchar2,
598 p_rt_ppl_grp_flag in varchar2,
595 p_rt_cmbn_age_los_flag in varchar2,
596 p_rt_prtt_pl_flag in varchar2,
597 p_rt_svc_area_flag in varchar2,
599 p_rt_dsbld_flag in varchar2,
600 p_rt_hlth_cvg_flag in varchar2,
601 p_rt_poe_flag in varchar2,
602 p_rt_ttl_cvg_vol_flag in varchar2,
603 p_rt_ttl_prtt_flag in varchar2,
604 p_rt_gndr_flag in varchar2,
605 p_rt_tbco_use_flag in varchar2,
606 p_vpf_attribute_category in varchar2,
607 p_vpf_attribute1 in varchar2,
608 p_vpf_attribute2 in varchar2,
609 p_vpf_attribute3 in varchar2,
610 p_vpf_attribute4 in varchar2,
611 p_vpf_attribute5 in varchar2,
612 p_vpf_attribute6 in varchar2,
613 p_vpf_attribute7 in varchar2,
614 p_vpf_attribute8 in varchar2,
615 p_vpf_attribute9 in varchar2,
616 p_vpf_attribute10 in varchar2,
617 p_vpf_attribute11 in varchar2,
618 p_vpf_attribute12 in varchar2,
619 p_vpf_attribute13 in varchar2,
620 p_vpf_attribute14 in varchar2,
621 p_vpf_attribute15 in varchar2,
622 p_vpf_attribute16 in varchar2,
623 p_vpf_attribute17 in varchar2,
624 p_vpf_attribute18 in varchar2,
625 p_vpf_attribute19 in varchar2,
626 p_vpf_attribute20 in varchar2,
627 p_vpf_attribute21 in varchar2,
628 p_vpf_attribute22 in varchar2,
629 p_vpf_attribute23 in varchar2,
630 p_vpf_attribute24 in varchar2,
631 p_vpf_attribute25 in varchar2,
632 p_vpf_attribute26 in varchar2,
633 p_vpf_attribute27 in varchar2,
634 p_vpf_attribute28 in varchar2,
635 p_vpf_attribute29 in varchar2,
636 p_vpf_attribute30 in varchar2,
637 p_object_version_number in number ,
638 p_rt_cntng_prtn_prfl_flag in varchar2,
639 p_rt_cbr_quald_bnf_flag in varchar2,
640 p_rt_optd_mdcr_flag in varchar2,
641 p_rt_lvg_rsn_flag in varchar2,
642 p_rt_pstn_flag in varchar2,
643 p_rt_comptncy_flag in varchar2,
644 p_rt_job_flag in varchar2,
645 p_rt_qual_titl_flag in varchar2,
646 p_rt_dpnt_cvrd_pl_flag in varchar2,
647 p_rt_dpnt_cvrd_plip_flag in varchar2,
648 p_rt_dpnt_cvrd_ptip_flag in varchar2,
649 p_rt_dpnt_cvrd_pgm_flag in varchar2,
650 p_rt_enrld_oipl_flag in varchar2,
651 p_rt_enrld_pl_flag in varchar2,
652 p_rt_enrld_plip_flag in varchar2,
653 p_rt_enrld_ptip_flag in varchar2,
654 p_rt_enrld_pgm_flag in varchar2,
655 p_rt_prtt_anthr_pl_flag in varchar2,
656 p_rt_othr_ptip_flag in varchar2,
657 p_rt_no_othr_cvg_flag in varchar2,
658 p_rt_dpnt_othr_ptip_flag in varchar2,
659 p_rt_qua_in_gr_flag in varchar2,
660 p_rt_perf_rtng_flag in varchar2,
661 p_rt_elig_prfl_flag in varchar2
662 )
663 Return g_rec_type;
664 --
665 end ben_vpf_shd;
[Home] [Help]