1 Package ben_elp_shd as
2 /* $Header: beelprhi.pkh 120.1.12000000.1 2007/01/19 05:29:30 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Global Record Type Specification |
6 -- ----------------------------------------------------------------------------
7 --
8 Type g_rec_type Is Record
9 (
10 eligy_prfl_id number(15),
11 effective_start_date date,
12 effective_end_date date,
13 name varchar2(240),
14 description varchar2(2000),
15 stat_cd varchar2(30),
16 asmt_to_use_cd varchar2(30),
17 elig_enrld_plip_flag varchar2(30),
18 elig_cbr_quald_bnf_flag varchar2(30),
19 elig_enrld_ptip_flag varchar2(30),
20 elig_dpnt_cvrd_plip_flag varchar2(30),
21 elig_dpnt_cvrd_ptip_flag varchar2(30),
22 elig_dpnt_cvrd_pgm_flag varchar2(30),
23 elig_job_flag varchar2(30),
24 elig_hrly_slrd_flag varchar2(30),
25 elig_pstl_cd_flag varchar2(30),
26 elig_lbr_mmbr_flag varchar2(30),
27 elig_lgl_enty_flag varchar2(30),
28 elig_benfts_grp_flag varchar2(30),
29 elig_wk_loc_flag varchar2(30),
30 elig_brgng_unit_flag varchar2(30),
31 elig_age_flag varchar2(30),
32 elig_los_flag varchar2(30),
33 elig_per_typ_flag varchar2(30),
34 elig_fl_tm_pt_tm_flag varchar2(30),
35 elig_ee_stat_flag varchar2(30),
36 elig_grd_flag varchar2(30),
37 elig_pct_fl_tm_flag varchar2(30),
38 elig_asnt_set_flag varchar2(30),
39 elig_hrs_wkd_flag varchar2(30),
40 elig_comp_lvl_flag varchar2(30),
41 elig_org_unit_flag varchar2(30),
42 elig_loa_rsn_flag varchar2(30),
43 elig_pyrl_flag varchar2(30),
44 elig_schedd_hrs_flag varchar2(30),
45 elig_py_bss_flag varchar2(30),
46 eligy_prfl_rl_flag varchar2(30),
47 elig_cmbn_age_los_flag varchar2(30),
48 cntng_prtn_elig_prfl_flag varchar2(30),
49 elig_prtt_pl_flag varchar2(30),
50 elig_ppl_grp_flag varchar2(30),
51 elig_svc_area_flag varchar2(30),
52 elig_ptip_prte_flag varchar2(30),
53 elig_no_othr_cvg_flag varchar2(30),
54 elig_enrld_pl_flag varchar2(30),
55 elig_enrld_oipl_flag varchar2(30),
56 elig_enrld_pgm_flag varchar2(30),
57 elig_dpnt_cvrd_pl_flag varchar2(30),
58 elig_lvg_rsn_flag varchar2(30),
59 elig_optd_mdcr_flag varchar2(30),
60 elig_tbco_use_flag varchar2(30),
61 elig_dpnt_othr_ptip_flag varchar2(30),
62 business_group_id number(15),
63 elp_attribute_category varchar2(30),
64 elp_attribute1 varchar2(150),
65 elp_attribute2 varchar2(150),
66 elp_attribute3 varchar2(150),
67 elp_attribute4 varchar2(150),
68 elp_attribute5 varchar2(150),
69 elp_attribute6 varchar2(150),
70 elp_attribute7 varchar2(150),
71 elp_attribute8 varchar2(150),
72 elp_attribute9 varchar2(150),
73 elp_attribute10 varchar2(150),
74 elp_attribute11 varchar2(150),
75 elp_attribute12 varchar2(150),
76 elp_attribute13 varchar2(150),
77 elp_attribute14 varchar2(150),
78 elp_attribute15 varchar2(150),
79 elp_attribute16 varchar2(150),
80 elp_attribute17 varchar2(150),
81 elp_attribute18 varchar2(150),
82 elp_attribute19 varchar2(150),
83 elp_attribute20 varchar2(150),
84 elp_attribute21 varchar2(150),
85 elp_attribute22 varchar2(150),
86 elp_attribute23 varchar2(150),
87 elp_attribute24 varchar2(150),
88 elp_attribute25 varchar2(150),
89 elp_attribute26 varchar2(150),
90 elp_attribute27 varchar2(150),
91 elp_attribute28 varchar2(150),
92 elp_attribute29 varchar2(150),
93 elp_attribute30 varchar2(150),
94 elig_mrtl_sts_flag varchar2(30),
95 elig_gndr_flag varchar2(30),
96 elig_dsblty_ctg_flag varchar2(30),
97 elig_dsblty_rsn_flag varchar2(30),
98 elig_dsblty_dgr_flag varchar2(30),
99 elig_suppl_role_flag varchar2(30),
100 elig_qual_titl_flag varchar2(30),
101 elig_pstn_flag varchar2(30),
102 elig_prbtn_perd_flag varchar2(30),
103 elig_sp_clng_prg_pt_flag varchar2(30),
104 bnft_cagr_prtn_cd varchar2(30),
105 elig_dsbld_flag varchar2(30),
106 elig_ttl_cvg_vol_flag varchar2(30),
107 elig_ttl_prtt_flag varchar2(30),
108 elig_comptncy_flag varchar2(30),
109 elig_hlth_cvg_flag varchar2(30),
110 elig_anthr_pl_flag varchar2(30),
111 elig_qua_in_gr_flag varchar2(30),
112 elig_perf_rtng_flag varchar2(30),
113 elig_crit_values_flag varchar2(30), /* RBC */
114 object_version_number number(9)
115 );
116 --
117 -- ----------------------------------------------------------------------------
118 -- | Global Definitions - Internal Development Use Only |
119 -- ----------------------------------------------------------------------------
120 --
121 g_old_rec g_rec_type; -- Global record definition
122 g_api_dml boolean; -- Global api dml status
123 --
124 -- ----------------------------------------------------------------------------
125 -- |------------------------< return_api_dml_status >-------------------------|
126 -- ----------------------------------------------------------------------------
127 -- {Start Of Comments}
128 --
129 -- Description:
130 -- This function will return the current g_api_dml private global
131 -- boolean status.
132 -- The g_api_dml status determines if at the time of the function
133 -- being executed if a dml statement (i.e. INSERT, UPDATE or DELETE)
134 -- is being issued from within an api.
135 -- If the status is TRUE then a dml statement is being issued from
136 -- within this entity api.
137 -- This function is primarily to support database triggers which
138 -- need to maintain the object_version_number for non-supported
139 -- dml statements (i.e. dml statement issued outside of the api layer).
140 --
141 -- Prerequisites:
142 -- None.
143 --
144 -- In Parameters:
145 -- None.
146 --
147 -- Post Success:
148 -- Processing continues.
149 -- If the function returns a TRUE value then, dml is being executed from
150 -- within this api.
151 --
152 -- Post Failure:
153 -- None.
154 --
155 -- Access Status:
156 -- Internal Row Handler Use Only.
157 --
158 -- {End Of Comments}
159 -- ----------------------------------------------------------------------------
160 Function return_api_dml_status Return Boolean;
161 --
162 -- ----------------------------------------------------------------------------
163 -- |---------------------------< constraint_error >---------------------------|
164 -- ----------------------------------------------------------------------------
165 -- {Start Of Comments}
166 --
167 -- Description:
168 -- This procedure is called when a constraint has been violated (i.e.
169 -- The exception hr_api.check_integrity_violated,
170 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
171 -- hr_api.unique_integrity_violated has been raised).
172 -- The exceptions can only be raised as follows:
173 -- 1) A check constraint can only be violated during an INSERT or UPDATE
174 -- dml operation.
175 -- 2) A parent integrity constraint can only be violated during an
176 -- INSERT or UPDATE dml operation.
177 -- 3) A child integrity constraint can only be violated during an
178 -- DELETE dml operation.
179 -- 4) A unique integrity constraint can only be violated during INSERT or
180 -- UPDATE dml operation.
181 --
182 -- Prerequisites:
183 -- 1) Either hr_api.check_integrity_violated,
184 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
185 -- hr_api.unique_integrity_violated has been raised with the subsequent
186 -- stripping of the constraint name from the generated error message
187 -- text.
188 -- 2) Standalone validation test which corresponds with a constraint error.
189 --
190 -- In Parameter:
191 -- p_constraint_name is in upper format and is just the constraint name
192 -- (e.g. not prefixed by brackets, schema owner etc).
193 --
194 -- Post Success:
195 -- Development dependant.
196 --
197 -- Post Failure:
198 -- Developement dependant.
199 --
200 -- Developer Implementation Notes:
201 -- For each constraint being checked the hr system package failure message
202 -- has been generated as a template only. These system error messages should
203 -- be modified as required (i.e. change the system failure message to a user
204 -- friendly defined error message).
205 --
206 -- Access Status:
207 -- Internal Development Use Only.
208 --
209 -- {End Of Comments}
210 -- ----------------------------------------------------------------------------
211 Procedure constraint_error
212 (p_constraint_name in all_constraints.constraint_name%TYPE);
213 --
214 -- ----------------------------------------------------------------------------
215 -- |-----------------------------< api_updating >-----------------------------|
216 -- ----------------------------------------------------------------------------
217 -- {Start Of Comments}
218 --
219 -- Description:
220 -- This function is used to populate the g_old_rec record with the current
221 -- row from the database for the specified primary key provided that the
222 -- primary key exists, and is valid, and does not already match the current
223 -- g_old_rec.
224 -- The function will always return a TRUE value if the g_old_rec is
225 -- populated with the current row. A FALSE value will be returned if all of
226 -- the primary key arguments are null.
227 --
228 -- Prerequisites:
229 -- None.
230 --
231 -- In Parameters:
232 --
233 -- Post Success:
234 -- A value of TRUE will be returned indiciating that the g_old_rec is
235 -- current.
236 -- A value of FALSE will be returned if all of the primary key arguments
237 -- have a null value (this indicates that the row has not be inserted into
238 -- the Schema), and therefore could never have a corresponding row.
239 --
240 -- Post Failure:
241 -- A failure can only occur under two circumstances:
242 -- 1) The primary key is invalid (i.e. a row does not exist for the
243 -- specified primary key values).
244 -- 2) If an object_version_number exists but is NOT the same as the current
245 -- g_old_rec value.
246 --
247 -- Developer Implementation Notes:
248 -- None.
249 --
250 -- Access Status:
251 -- Internal Development Use Only.
252 --
253 -- {End Of Comments}
254 -- ----------------------------------------------------------------------------
255 Function api_updating
256 (p_effective_date in date,
257 p_eligy_prfl_id in number,
258 p_object_version_number in number
259 ) Return Boolean;
260 --
261 -- ----------------------------------------------------------------------------
262 -- |--------------------------< find_dt_del_modes >---------------------------|
263 -- ----------------------------------------------------------------------------
264 -- {Start Of Comments}
265 --
266 -- Description:
267 -- This procedure is used to determine what datetrack delete modes are
268 -- allowed as of the effective date for this entity. The procedure will
269 -- return a corresponding Boolean value for each of the delete modes
270 -- available where TRUE indicates that the corresponding delete mode is
271 -- available.
272 --
273 -- Prerequisites:
274 -- None.
275 --
276 -- In Parameters:
277 -- p_effective_date
278 -- Specifies the date at which the datetrack modes will be operated on.
279 -- p_base_key_value
280 -- Specifies the primary key value for this datetrack entity.
281 -- (E.g. For this entity the assignment of the argument would be:
282 -- p_base_key_value = :eligy_prfl_id).
283 --
284 -- Post Success:
285 -- Processing continues.
286 --
287 -- Post Failure:
288 -- Failure might occur if for the specified effective date and primary key
289 -- value a row doesn't exist.
290 --
291 -- Developer Implementation Notes:
292 -- This procedure could require changes if this entity has any sepcific
293 -- delete restrictions.
294 -- For example, this entity might disallow the datetrack delete mode of
295 -- ZAP. To implement this you would have to set and return a Boolean value
296 -- of FALSE after the call to the dt_api.find_dt_del_modes procedure.
297 --
298 -- Access Status:
299 -- Internal Development Use Only.
300 --
301 -- {End Of Comments}
302 -- ----------------------------------------------------------------------------
303 Procedure find_dt_del_modes
304 (p_effective_date in date,
305 p_base_key_value in number,
306 p_zap out nocopy boolean,
307 p_delete out nocopy boolean,
308 p_future_change out nocopy boolean,
309 p_delete_next_change out nocopy boolean);
310 --
311 -- ----------------------------------------------------------------------------
312 -- |--------------------------< find_dt_upd_modes >---------------------------|
313 -- ----------------------------------------------------------------------------
314 -- {Start Of Comments}
315 --
316 -- Description:
317 -- This procedure is used to determine what datetrack update modes are
318 -- allowed as of the effective date for this entity. The procedure will
319 -- return a corresponding Boolean value for each of the update modes
320 -- available where TRUE indicates that the corresponding update mode
321 -- is available.
322 --
323 -- Prerequisites:
324 -- None.
325 --
326 -- In Parameters:
327 -- p_effective_date
328 -- Specifies the date at which the datetrack modes will be operated on.
329 -- p_base_key_value
330 -- Specifies the primary key value for this datetrack entity.
331 -- (E.g. For this entity the assignment of the argument would be:
332 -- p_base_key_value = :eligy_prfl_id).
333 --
334 -- Post Success:
335 -- Processing continues.
336 --
337 -- Post Failure:
338 -- Failure might occur if for the specified effective date and primary key
339 -- value a row doesn't exist.
340 --
341 -- Developer Implementation Notes:
342 -- This procedure could require changes if this entity has any sepcific
343 -- delete restrictions.
344 -- For example, this entity might disallow the datetrack update mode of
345 -- UPDATE. To implement this you would have to set and return a Boolean
346 -- value of FALSE after the call to the dt_api.find_dt_upd_modes procedure.
347 --
348 -- Access Status:
349 -- Internal Development Use Only.
350 --
351 -- {End Of Comments}
352 -- ----------------------------------------------------------------------------
353 Procedure find_dt_upd_modes
354 (p_effective_date in date,
355 p_base_key_value in number,
356 p_correction out nocopy boolean,
357 p_update out nocopy boolean,
358 p_update_override out nocopy boolean,
362 -- |------------------------< upd_effective_end_date >------------------------|
359 p_update_change_insert out nocopy boolean);
360 --
361 -- ----------------------------------------------------------------------------
363 -- ----------------------------------------------------------------------------
364 -- {Start Of Comments}
365 --
366 -- Description:
367 -- This procedure will update the specified datetrack row with the
368 -- specified new effective end date. The object version number is also
369 -- set to the next object version number. DateTrack modes which call
370 -- this procedure are: UPDATE, UPDATE_CHANGE_INSERT,
371 -- UPDATE_OVERRIDE, DELETE, FUTURE_CHANGE and DELETE_NEXT_CHANGE.
372 -- This is an internal datetrack maintenance procedure which should
373 -- not be modified in anyway.
374 --
375 -- Prerequisites:
376 -- None.
377 --
378 -- In Parameters:
379 -- p_new_effective_end_date
380 -- Specifies the new effective end date which will be set for the
381 -- row as of the effective date.
382 -- p_base_key_value
383 -- Specifies the primary key value for this datetrack entity.
384 -- (E.g. For this entity the assignment of the argument would be:
385 -- p_base_key_value = :eligy_prfl_id).
386 --
387 -- Post Success:
388 -- The specified row will be updated with the new effective end date and
389 -- object_version_number.
390 --
391 -- Post Failure:
392 -- Failure might occur if for the specified effective date and primary key
393 -- value a row doesn't exist.
394 --
395 -- Developer Implementation Notes:
396 -- This is an internal datetrack maintenance procedure which should
397 -- not be modified in anyway.
398 --
399 -- Access Status:
400 -- Internal Row Handler Use Only.
401 --
402 -- {End Of Comments}
403 -- ----------------------------------------------------------------------------
404 Procedure upd_effective_end_date
405 (p_effective_date in date,
406 p_base_key_value in number,
407 p_new_effective_end_date in date,
408 p_validation_start_date in date,
409 p_validation_end_date in date,
410 p_object_version_number out nocopy number);
411 --
412 -- ----------------------------------------------------------------------------
413 -- |---------------------------------< lck >----------------------------------|
414 -- ----------------------------------------------------------------------------
415 -- {Start Of Comments}
416 --
417 -- Description:
418 -- The Lck process for datetrack is complicated and comprises of the
419 -- following processing
420 -- The processing steps are as follows:
421 -- 1) The row to be updated or deleted must be locked.
422 -- By locking this row, the g_old_rec record data type is populated.
423 -- 2) If a comment exists the text is selected from hr_comments.
424 -- 3) The datetrack mode is then validated to ensure the operation is
425 -- valid. If the mode is valid the validation start and end dates for
426 -- the mode will be derived and returned. Any required locking is
427 -- completed when the datetrack mode is validated.
428 --
429 -- Prerequisites:
430 -- When attempting to call the lck procedure the object version number,
431 -- primary key, effective date and datetrack mode must be specified.
432 --
433 -- In Parameters:
434 -- p_effective_date
435 -- Specifies the date of the datetrack update operation.
436 -- p_datetrack_mode
437 -- Determines the datetrack update or delete mode.
438 --
439 -- Post Success:
440 -- On successful completion of the Lck process the row to be updated or
441 -- deleted will be locked and selected into the global data structure
442 -- g_old_rec.
443 --
444 -- Post Failure:
445 -- The Lck process can fail for three reasons:
446 -- 1) When attempting to lock the row the row could already be locked by
447 -- another user. This will raise the HR_Api.Object_Locked exception.
448 -- 2) The row which is required to be locked doesn't exist in the HR Schema.
449 -- This error is trapped and reported using the message name
450 -- 'HR_7220_INVALID_PRIMARY_KEY'.
451 -- 3) The row although existing in the HR Schema has a different object
452 -- version number than the object version number specified.
453 -- This error is trapped and reported using the message name
454 -- 'HR_7155_OBJECT_INVALID'.
455 --
456 -- Developer Implementation Notes:
457 -- None.
458 --
459 -- Access Status:
460 -- Internal Development Use Only.
461 --
462 -- {End Of Comments}
463 -- ----------------------------------------------------------------------------
464 Procedure lck
465 (p_effective_date in date,
466 p_datetrack_mode in varchar2,
467 p_eligy_prfl_id in number,
468 p_object_version_number in number,
469 p_validation_start_date out nocopy date,
470 p_validation_end_date out nocopy date);
471 --
472 -- ----------------------------------------------------------------------------
473 -- |-----------------------------< convert_args >-----------------------------|
474 -- ----------------------------------------------------------------------------
475 -- {Start Of Comments}
476 --
477 -- Description:
478 -- This function is used to turn attribute parameters into the record
479 -- structure parameter g_rec_type.
480 --
481 -- Prerequisites:
485 -- In Parameters:
482 -- This is a private function and can only be called from the ins or upd
483 -- attribute processes.
484 --
486 --
487 -- Post Success:
488 -- A returning record structure will be returned.
489 --
490 -- Post Failure:
491 -- No direct error handling is required within this function. Any possible
492 -- errors within this function will be a PL/SQL value error due to conversion
493 -- of datatypes or data lengths.
494 --
495 -- Developer Implementation Notes:
496 -- None.
497 --
498 -- Access Status:
499 -- Internal Row Handler Use Only.
500 --
501 -- {End Of Comments}
502 -- ----------------------------------------------------------------------------
503 Function convert_args
504 (
505 p_eligy_prfl_id in number,
506 p_effective_start_date in date,
507 p_effective_end_date in date,
508 p_name in varchar2,
509 p_description in varchar2,
510 p_stat_cd in varchar2,
511 p_asmt_to_use_cd in varchar2,
512 p_elig_enrld_plip_flag in varchar2,
513 p_elig_cbr_quald_bnf_flag in varchar2,
514 p_elig_enrld_ptip_flag in varchar2,
515 p_elig_dpnt_cvrd_plip_flag in varchar2,
516 p_elig_dpnt_cvrd_ptip_flag in varchar2,
517 p_elig_dpnt_cvrd_pgm_flag in varchar2,
518 p_elig_job_flag in varchar2,
519 p_elig_hrly_slrd_flag in varchar2,
520 p_elig_pstl_cd_flag in varchar2,
521 p_elig_lbr_mmbr_flag in varchar2,
522 p_elig_lgl_enty_flag in varchar2,
523 p_elig_benfts_grp_flag in varchar2,
524 p_elig_wk_loc_flag in varchar2,
525 p_elig_brgng_unit_flag in varchar2,
526 p_elig_age_flag in varchar2,
527 p_elig_los_flag in varchar2,
528 p_elig_per_typ_flag in varchar2,
529 p_elig_fl_tm_pt_tm_flag in varchar2,
530 p_elig_ee_stat_flag in varchar2,
531 p_elig_grd_flag in varchar2,
532 p_elig_pct_fl_tm_flag in varchar2,
533 p_elig_asnt_set_flag in varchar2,
534 p_elig_hrs_wkd_flag in varchar2,
535 p_elig_comp_lvl_flag in varchar2,
536 p_elig_org_unit_flag in varchar2,
537 p_elig_loa_rsn_flag in varchar2,
538 p_elig_pyrl_flag in varchar2,
539 p_elig_schedd_hrs_flag in varchar2,
540 p_elig_py_bss_flag in varchar2,
541 p_eligy_prfl_rl_flag in varchar2,
542 p_elig_cmbn_age_los_flag in varchar2,
543 p_cntng_prtn_elig_prfl_flag in varchar2,
544 p_elig_prtt_pl_flag in varchar2,
545 p_elig_ppl_grp_flag in varchar2,
546 p_elig_svc_area_flag in varchar2,
547 p_elig_ptip_prte_flag in varchar2,
548 p_elig_no_othr_cvg_flag in varchar2,
549 p_elig_enrld_pl_flag in varchar2,
550 p_elig_enrld_oipl_flag in varchar2,
551 p_elig_enrld_pgm_flag in varchar2,
552 p_elig_dpnt_cvrd_pl_flag in varchar2,
553 p_elig_lvg_rsn_flag in varchar2,
554 p_elig_optd_mdcr_flag in varchar2,
555 p_elig_tbco_use_flag in varchar2,
556 p_elig_dpnt_othr_ptip_flag in varchar2,
557 p_business_group_id in number,
558 p_elp_attribute_category in varchar2,
559 p_elp_attribute1 in varchar2,
560 p_elp_attribute2 in varchar2,
561 p_elp_attribute3 in varchar2,
562 p_elp_attribute4 in varchar2,
563 p_elp_attribute5 in varchar2,
564 p_elp_attribute6 in varchar2,
565 p_elp_attribute7 in varchar2,
566 p_elp_attribute8 in varchar2,
567 p_elp_attribute9 in varchar2,
568 p_elp_attribute10 in varchar2,
569 p_elp_attribute11 in varchar2,
570 p_elp_attribute12 in varchar2,
571 p_elp_attribute13 in varchar2,
572 p_elp_attribute14 in varchar2,
573 p_elp_attribute15 in varchar2,
574 p_elp_attribute16 in varchar2,
575 p_elp_attribute17 in varchar2,
576 p_elp_attribute18 in varchar2,
577 p_elp_attribute19 in varchar2,
578 p_elp_attribute20 in varchar2,
579 p_elp_attribute21 in varchar2,
580 p_elp_attribute22 in varchar2,
581 p_elp_attribute23 in varchar2,
582 p_elp_attribute24 in varchar2,
583 p_elp_attribute25 in varchar2,
584 p_elp_attribute26 in varchar2,
585 p_elp_attribute27 in varchar2,
586 p_elp_attribute28 in varchar2,
587 p_elp_attribute29 in varchar2,
588 p_elp_attribute30 in varchar2,
589 p_elig_mrtl_sts_flag in varchar2,
590 p_elig_gndr_flag in varchar2,
591 p_elig_dsblty_ctg_flag in varchar2,
592 p_elig_dsblty_rsn_flag in varchar2,
593 p_elig_dsblty_dgr_flag in varchar2,
594 p_elig_suppl_role_flag in varchar2,
595 p_elig_qual_titl_flag in varchar2,
596 p_elig_pstn_flag in varchar2,
597 p_elig_prbtn_perd_flag in varchar2,
598 p_elig_sp_clng_prg_pt_flag in varchar2,
599 p_bnft_cagr_prtn_cd in varchar2,
600 p_elig_dsbld_flag in varchar2,
601 p_elig_ttl_cvg_vol_flag in varchar2,
602 p_elig_ttl_prtt_flag in varchar2,
603 p_elig_comptncy_flag in varchar2,
604 p_elig_hlth_cvg_flag in varchar2,
605 p_elig_anthr_pl_flag in varchar2,
606 p_elig_qua_in_gr_flag in varchar2,
607 p_elig_perf_rtng_flag in varchar2,
608 p_elig_crit_values_flag in varchar2, /* RBC */
609 p_object_version_number in number
610 )
611 Return g_rec_type;
612 --
613 end ben_elp_shd;
[Home] [Help]