1 Package ben_pgm_shd AUTHID CURRENT_USER as
2 /* $Header: bepgmrhi.pkh 120.0.12020000.2 2012/07/03 13:11:24 amnaraya ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Global Record Type Specification |
6 -- ----------------------------------------------------------------------------
7 --
8 Type g_rec_type Is Record
9 (
10 pgm_id number(15),
11 effective_start_date date,
12 effective_end_date date,
13 name varchar2(240), -- UTF8 Change Bug 2254683
14 dpnt_adrs_rqd_flag varchar2(30),
15 pgm_prvds_no_auto_enrt_flag varchar2(30),
16 dpnt_dob_rqd_flag varchar2(30),
17 pgm_prvds_no_dflt_enrt_flag varchar2(30),
18 dpnt_legv_id_rqd_flag varchar2(30),
19 dpnt_dsgn_lvl_cd varchar2(30),
20 pgm_stat_cd varchar2(30),
21 ivr_ident varchar2(90), -- UTF8 Change Bug 2254683
22 pgm_typ_cd varchar2(30),
23 elig_apls_flag varchar2(30),
24 uses_all_asmts_for_rts_flag varchar2(30),
25 url_ref_name varchar2(240),
26 pgm_desc varchar2(2000),
27 prtn_elig_ovrid_alwd_flag varchar2(30),
28 pgm_use_all_asnts_elig_flag varchar2(30),
29 dpnt_dsgn_cd varchar2(30),
30 mx_dpnt_pct_prtt_lf_amt number(15),
31 mx_sps_pct_prtt_lf_amt number(15),
32 acty_ref_perd_cd varchar2(30),
33 coord_cvg_for_all_pls_flg varchar2(30),
34 enrt_cvg_end_dt_cd varchar2(30),
35 enrt_cvg_end_dt_rl number(15),
36 dpnt_cvg_end_dt_cd varchar2(30),
37 dpnt_cvg_end_dt_rl number(15),
38 dpnt_cvg_strt_dt_cd varchar2(30),
39 dpnt_cvg_strt_dt_rl number(15),
40 dpnt_dsgn_no_ctfn_rqd_flag varchar2(30),
41 drvbl_fctr_dpnt_elig_flag varchar2(30),
42 drvbl_fctr_prtn_elig_flag varchar2(30),
43 enrt_cvg_strt_dt_cd varchar2(30),
44 enrt_cvg_strt_dt_rl number(15),
45 enrt_info_rt_freq_cd varchar2(30),
46 rt_strt_dt_cd varchar2(30),
47 rt_strt_dt_rl number(15),
48 rt_end_dt_cd varchar2(30),
49 rt_end_dt_rl number(15),
50 pgm_grp_cd varchar2(30),
51 pgm_uom varchar2(30),
52 drvbl_fctr_apls_rts_flag varchar2(30),
53 alws_unrstrctd_enrt_flag varchar2(30),
54 enrt_cd varchar2(30),
55 enrt_mthd_cd varchar2(30),
56 poe_lvl_cd varchar2(30),
57 enrt_rl number(15),
58 auto_enrt_mthd_rl number(15),
59 trk_inelig_per_flag varchar2(30),
60 business_group_id number(15),
61 per_cvrd_cd varchar2(30),
62 vrfy_fmly_mmbr_rl number(15),
63 vrfy_fmly_mmbr_cd varchar2(30),
64 short_name varchar2(30), --FHR
65 short_code varchar2(30), --FHR
66 legislation_code varchar2(30),
67 legislation_subgroup varchar2(30),
68 Dflt_pgm_flag Varchar2(30),
69 Use_prog_points_flag Varchar2(30),
70 Dflt_step_cd Varchar2(30),
71 Dflt_step_rl number(15) ,
72 Update_salary_cd Varchar2(30),
73 Use_multi_pay_rates_flag Varchar2(30),
74 dflt_element_type_id number(15),
75 Dflt_input_value_id number(15) ,
76 Use_scores_cd Varchar2(30),
77 Scores_calc_mthd_cd Varchar2(30),
78 Scores_calc_rl number(15),
79 gsp_allow_override_flag varchar2(30),
80 use_variable_rates_flag varchar2(30),
81 salary_calc_mthd_cd varchar2(30),
82 salary_calc_mthd_rl number(15),
83 susp_if_dpnt_ssn_nt_prv_cd varchar2(30),
84 susp_if_dpnt_dob_nt_prv_cd varchar2(30),
85 susp_if_dpnt_adr_nt_prv_cd varchar2(30),
86 susp_if_ctfn_not_dpnt_flag varchar2(30),
87 dpnt_ctfn_determine_cd varchar2(30),
88 pgm_attribute_category varchar2(30),
89 pgm_attribute1 varchar2(150),
90 pgm_attribute2 varchar2(150),
91 pgm_attribute3 varchar2(150),
92 pgm_attribute4 varchar2(150),
93 pgm_attribute5 varchar2(150),
94 pgm_attribute6 varchar2(150),
95 pgm_attribute7 varchar2(150),
96 pgm_attribute8 varchar2(150),
97 pgm_attribute9 varchar2(150),
98 pgm_attribute10 varchar2(150),
99 pgm_attribute11 varchar2(150),
100 pgm_attribute12 varchar2(150),
101 pgm_attribute13 varchar2(150),
102 pgm_attribute14 varchar2(150),
103 pgm_attribute15 varchar2(150),
104 pgm_attribute16 varchar2(150),
105 pgm_attribute17 varchar2(150),
106 pgm_attribute18 varchar2(150),
107 pgm_attribute19 varchar2(150),
108 pgm_attribute20 varchar2(150),
109 pgm_attribute21 varchar2(150),
110 pgm_attribute22 varchar2(150),
111 pgm_attribute23 varchar2(150),
112 pgm_attribute24 varchar2(150),
113 pgm_attribute25 varchar2(150),
114 pgm_attribute26 varchar2(150),
115 pgm_attribute27 varchar2(150),
116 pgm_attribute28 varchar2(150),
117 pgm_attribute29 varchar2(150),
118 pgm_attribute30 varchar2(150),
119 all_inelig VARCHAR2(30),
120 object_version_number number(9)
121 );
122 --
123 -- ----------------------------------------------------------------------------
124 -- | Global Definitions - Internal Development Use Only |
125 -- ----------------------------------------------------------------------------
126 --
127 g_old_rec g_rec_type; -- Global record definition
128 g_api_dml boolean; -- Global api dml status
129 --
130 -- ----------------------------------------------------------------------------
131 -- |------------------------< return_api_dml_status >-------------------------|
132 -- ----------------------------------------------------------------------------
133 -- {Start Of Comments}
134 --
135 -- Description:
136 -- This function will return the current g_api_dml private global
137 -- boolean status.
138 -- The g_api_dml status determines if at the time of the function
139 -- being executed if a dml statement (i.e. INSERT, UPDATE or DELETE)
140 -- is being issued from within an api.
141 -- If the status is TRUE then a dml statement is being issued from
142 -- within this entity api.
143 -- This function is primarily to support database triggers which
144 -- need to maintain the object_version_number for non-supported
145 -- dml statements (i.e. dml statement issued outside of the api layer).
146 --
147 -- Prerequisites:
148 -- None.
149 --
150 -- In Parameters:
151 -- None.
152 --
153 -- Post Success:
154 -- Processing continues.
155 -- If the function returns a TRUE value then, dml is being executed from
156 -- within this api.
157 --
158 -- Post Failure:
159 -- None.
160 --
161 -- Access Status:
162 -- Internal Row Handler Use Only.
163 --
164 -- {End Of Comments}
165 -- ----------------------------------------------------------------------------
166 Function return_api_dml_status Return Boolean;
167 --
168 -- ----------------------------------------------------------------------------
169 -- |---------------------------< constraint_error >---------------------------|
170 -- ----------------------------------------------------------------------------
171 -- {Start Of Comments}
172 --
173 -- Description:
174 -- This procedure is called when a constraint has been violated (i.e.
175 -- The exception hr_api.check_integrity_violated,
176 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
177 -- hr_api.unique_integrity_violated has been raised).
178 -- The exceptions can only be raised as follows:
179 -- 1) A check constraint can only be violated during an INSERT or UPDATE
180 -- dml operation.
181 -- 2) A parent integrity constraint can only be violated during an
182 -- INSERT or UPDATE dml operation.
183 -- 3) A child integrity constraint can only be violated during an
184 -- DELETE dml operation.
185 -- 4) A unique integrity constraint can only be violated during INSERT or
186 -- UPDATE dml operation.
187 --
188 -- Prerequisites:
189 -- 1) Either hr_api.check_integrity_violated,
190 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
191 -- hr_api.unique_integrity_violated has been raised with the subsequent
192 -- stripping of the constraint name from the generated error message
193 -- text.
194 -- 2) Standalone validation test which corresponds with a constraint error.
195 --
196 -- In Parameter:
197 -- p_constraint_name is in upper format and is just the constraint name
198 -- (e.g. not prefixed by brackets, schema owner etc).
199 --
200 -- Post Success:
201 -- Development dependant.
202 --
203 -- Post Failure:
204 -- Developement dependant.
205 --
206 -- Developer Implementation Notes:
207 -- For each constraint being checked the hr system package failure message
208 -- has been generated as a template only. These system error messages should
209 -- be modified as required (i.e. change the system failure message to a user
210 -- friendly defined error message).
211 --
212 -- Access Status:
213 -- Internal Development Use Only.
214 --
215 -- {End Of Comments}
216 -- ----------------------------------------------------------------------------
217 Procedure constraint_error
218 (p_constraint_name in all_constraints.constraint_name%TYPE);
219 --
220 -- ----------------------------------------------------------------------------
221 -- |-----------------------------< api_updating >-----------------------------|
222 -- ----------------------------------------------------------------------------
223 -- {Start Of Comments}
224 --
225 -- Description:
226 -- This function is used to populate the g_old_rec record with the current
227 -- row from the database for the specified primary key provided that the
228 -- primary key exists, and is valid, and does not already match the current
229 -- g_old_rec.
230 -- The function will always return a TRUE value if the g_old_rec is
231 -- populated with the current row. A FALSE value will be returned if all of
232 -- the primary key arguments are null.
233 --
234 -- Prerequisites:
235 -- None.
236 --
237 -- In Parameters:
238 --
239 -- Post Success:
240 -- A value of TRUE will be returned indiciating that the g_old_rec is
241 -- current.
242 -- A value of FALSE will be returned if all of the primary key arguments
243 -- have a null value (this indicates that the row has not be inserted into
244 -- the Schema), and therefore could never have a corresponding row.
245 --
246 -- Post Failure:
247 -- A failure can only occur under two circumstances:
248 -- 1) The primary key is invalid (i.e. a row does not exist for the
249 -- specified primary key values).
250 -- 2) If an object_version_number exists but is NOT the same as the current
251 -- g_old_rec value.
252 --
253 -- Developer Implementation Notes:
254 -- None.
255 --
256 -- Access Status:
257 -- Internal Development Use Only.
258 --
259 -- {End Of Comments}
260 -- ----------------------------------------------------------------------------
261 Function api_updating
262 (p_effective_date in date,
263 p_pgm_id in number,
264 p_object_version_number in number
265 ) Return Boolean;
266 --
267 -- ----------------------------------------------------------------------------
268 -- |--------------------------< find_dt_del_modes >---------------------------|
269 -- ----------------------------------------------------------------------------
270 -- {Start Of Comments}
271 --
272 -- Description:
273 -- This procedure is used to determine what datetrack delete modes are
274 -- allowed as of the effective date for this entity. The procedure will
275 -- return a corresponding Boolean value for each of the delete modes
276 -- available where TRUE indicates that the corresponding delete mode is
277 -- available.
278 --
279 -- Prerequisites:
280 -- None.
281 --
282 -- In Parameters:
283 -- p_effective_date
284 -- Specifies the date at which the datetrack modes will be operated on.
285 -- p_base_key_value
286 -- Specifies the primary key value for this datetrack entity.
287 -- (E.g. For this entity the assignment of the argument would be:
288 -- p_base_key_value = :pgm_id).
289 --
290 -- Post Success:
291 -- Processing continues.
292 --
293 -- Post Failure:
294 -- Failure might occur if for the specified effective date and primary key
295 -- value a row doesn't exist.
296 --
297 -- Developer Implementation Notes:
298 -- This procedure could require changes if this entity has any sepcific
299 -- delete restrictions.
300 -- For example, this entity might disallow the datetrack delete mode of
301 -- ZAP. To implement this you would have to set and return a Boolean value
302 -- of FALSE after the call to the dt_api.find_dt_del_modes procedure.
303 --
304 -- Access Status:
305 -- Internal Development Use Only.
306 --
307 -- {End Of Comments}
308 -- ----------------------------------------------------------------------------
309 Procedure find_dt_del_modes
310 (p_effective_date in date,
311 p_base_key_value in number,
312 p_zap out nocopy boolean,
313 p_delete out nocopy boolean,
314 p_future_change out nocopy boolean,
315 p_delete_next_change out nocopy boolean);
316 --
317 -- ----------------------------------------------------------------------------
318 -- |--------------------------< find_dt_upd_modes >---------------------------|
322 -- Description:
319 -- ----------------------------------------------------------------------------
320 -- {Start Of Comments}
321 --
323 -- This procedure is used to determine what datetrack update modes are
324 -- allowed as of the effective date for this entity. The procedure will
325 -- return a corresponding Boolean value for each of the update modes
326 -- available where TRUE indicates that the corresponding update mode
327 -- is available.
328 --
329 -- Prerequisites:
330 -- None.
331 --
332 -- In Parameters:
333 -- p_effective_date
334 -- Specifies the date at which the datetrack modes will be operated on.
335 -- p_base_key_value
336 -- Specifies the primary key value for this datetrack entity.
337 -- (E.g. For this entity the assignment of the argument would be:
338 -- p_base_key_value = :pgm_id).
339 --
340 -- Post Success:
341 -- Processing continues.
342 --
343 -- Post Failure:
344 -- Failure might occur if for the specified effective date and primary key
345 -- value a row doesn't exist.
346 --
347 -- Developer Implementation Notes:
348 -- This procedure could require changes if this entity has any sepcific
349 -- delete restrictions.
350 -- For example, this entity might disallow the datetrack update mode of
351 -- UPDATE. To implement this you would have to set and return a Boolean
352 -- value of FALSE after the call to the dt_api.find_dt_upd_modes procedure.
353 --
354 -- Access Status:
355 -- Internal Development Use Only.
356 --
357 -- {End Of Comments}
358 -- ----------------------------------------------------------------------------
359 Procedure find_dt_upd_modes
360 (p_effective_date in date,
361 p_base_key_value in number,
362 p_correction out nocopy boolean,
363 p_update out nocopy boolean,
364 p_update_override out nocopy boolean,
365 p_update_change_insert out nocopy boolean);
366 --
367 -- ----------------------------------------------------------------------------
368 -- |------------------------< upd_effective_end_date >------------------------|
369 -- ----------------------------------------------------------------------------
370 -- {Start Of Comments}
371 --
372 -- Description:
373 -- This procedure will update the specified datetrack row with the
374 -- specified new effective end date. The object version number is also
375 -- set to the next object version number. DateTrack modes which call
376 -- this procedure are: UPDATE, UPDATE_CHANGE_INSERT,
377 -- UPDATE_OVERRIDE, DELETE, FUTURE_CHANGE and DELETE_NEXT_CHANGE.
378 -- This is an internal datetrack maintenance procedure which should
379 -- not be modified in anyway.
380 --
381 -- Prerequisites:
382 -- None.
383 --
384 -- In Parameters:
385 -- p_new_effective_end_date
386 -- Specifies the new effective end date which will be set for the
387 -- row as of the effective date.
388 -- p_base_key_value
389 -- Specifies the primary key value for this datetrack entity.
390 -- (E.g. For this entity the assignment of the argument would be:
391 -- p_base_key_value = :pgm_id).
392 --
393 -- Post Success:
394 -- The specified row will be updated with the new effective end date and
395 -- object_version_number.
396 --
397 -- Post Failure:
398 -- Failure might occur if for the specified effective date and primary key
399 -- value a row doesn't exist.
400 --
401 -- Developer Implementation Notes:
402 -- This is an internal datetrack maintenance procedure which should
403 -- not be modified in anyway.
404 --
405 -- Access Status:
406 -- Internal Row Handler Use Only.
407 --
408 -- {End Of Comments}
409 -- ----------------------------------------------------------------------------
410 Procedure upd_effective_end_date
411 (p_effective_date in date,
412 p_base_key_value in number,
413 p_new_effective_end_date in date,
414 p_validation_start_date in date,
415 p_validation_end_date in date,
416 p_object_version_number out nocopy number);
417 --
418 -- ----------------------------------------------------------------------------
419 -- |---------------------------------< lck >----------------------------------|
420 -- ----------------------------------------------------------------------------
421 -- {Start Of Comments}
422 --
423 -- Description:
424 -- The Lck process for datetrack is complicated and comprises of the
425 -- following processing
426 -- The processing steps are as follows:
427 -- 1) The row to be updated or deleted must be locked.
428 -- By locking this row, the g_old_rec record data type is populated.
429 -- 2) If a comment exists the text is selected from hr_comments.
430 -- 3) The datetrack mode is then validated to ensure the operation is
431 -- valid. If the mode is valid the validation start and end dates for
432 -- the mode will be derived and returned. Any required locking is
433 -- completed when the datetrack mode is validated.
434 --
435 -- Prerequisites:
436 -- When attempting to call the lck procedure the object version number,
437 -- primary key, effective date and datetrack mode must be specified.
438 --
439 -- In Parameters:
440 -- p_effective_date
441 -- Specifies the date of the datetrack update operation.
442 -- p_datetrack_mode
443 -- Determines the datetrack update or delete mode.
444 --
445 -- Post Success:
446 -- On successful completion of the Lck process the row to be updated or
447 -- deleted will be locked and selected into the global data structure
448 -- g_old_rec.
449 --
450 -- Post Failure:
451 -- The Lck process can fail for three reasons:
452 -- 1) When attempting to lock the row the row could already be locked by
456 -- 'HR_7220_INVALID_PRIMARY_KEY'.
453 -- another user. This will raise the HR_Api.Object_Locked exception.
454 -- 2) The row which is required to be locked doesn't exist in the HR Schema.
455 -- This error is trapped and reported using the message name
457 -- 3) The row although existing in the HR Schema has a different object
458 -- version number than the object version number specified.
459 -- This error is trapped and reported using the message name
460 -- 'HR_7155_OBJECT_INVALID'.
461 --
462 -- Developer Implementation Notes:
463 -- None.
464 --
465 -- Access Status:
466 -- Internal Development Use Only.
467 --
468 -- {End Of Comments}
469 -- ----------------------------------------------------------------------------
470 Procedure lck
471 (p_effective_date in date,
472 p_datetrack_mode in varchar2,
473 p_pgm_id in number,
474 p_object_version_number in number,
475 p_validation_start_date out nocopy date,
476 p_validation_end_date out nocopy date);
477 --
478 -- ----------------------------------------------------------------------------
479 -- |-----------------------------< convert_args >-----------------------------|
480 -- ----------------------------------------------------------------------------
481 -- {Start Of Comments}
482 --
483 -- Description:
484 -- This function is used to turn attribute parameters into the record
485 -- structure parameter g_rec_type.
486 --
487 -- Prerequisites:
488 -- This is a private function and can only be called from the ins or upd
489 -- attribute processes.
490 --
491 -- In Parameters:
492 --
493 -- Post Success:
494 -- A returning record structure will be returned.
495 --
496 -- Post Failure:
497 -- No direct error handling is required within this function. Any possible
498 -- errors within this function will be a PL/SQL value error due to conversion
499 -- of datatypes or data lengths.
500 --
501 -- Developer Implementation Notes:
502 -- None.
503 --
504 -- Access Status:
505 -- Internal Row Handler Use Only.
506 --
507 -- {End Of Comments}
508 -- ----------------------------------------------------------------------------
509 Function convert_args
510 (
511 p_pgm_id in number,
512 p_effective_start_date in date,
513 p_effective_end_date in date,
514 p_name in varchar2,
515 p_dpnt_adrs_rqd_flag in varchar2,
516 p_pgm_prvds_no_auto_enrt_flag in varchar2,
517 p_dpnt_dob_rqd_flag in varchar2,
518 p_pgm_prvds_no_dflt_enrt_flag in varchar2,
519 p_dpnt_legv_id_rqd_flag in varchar2,
520 p_dpnt_dsgn_lvl_cd in varchar2,
521 p_pgm_stat_cd in varchar2,
522 p_ivr_ident in varchar2,
523 p_pgm_typ_cd in varchar2,
524 p_elig_apls_flag in varchar2,
525 p_uses_all_asmts_for_rts_flag in varchar2,
526 p_url_ref_name in varchar2,
527 p_pgm_desc in varchar2,
528 p_prtn_elig_ovrid_alwd_flag in varchar2,
529 p_pgm_use_all_asnts_elig_flag in varchar2,
530 p_dpnt_dsgn_cd in varchar2,
531 p_mx_dpnt_pct_prtt_lf_amt in number,
532 p_mx_sps_pct_prtt_lf_amt in number,
533 p_acty_ref_perd_cd in varchar2,
534 p_coord_cvg_for_all_pls_flg in varchar2,
535 p_enrt_cvg_end_dt_cd in varchar2,
536 p_enrt_cvg_end_dt_rl in number,
537 p_dpnt_cvg_end_dt_cd in varchar2,
538 p_dpnt_cvg_end_dt_rl in number,
539 p_dpnt_cvg_strt_dt_cd in varchar2,
540 p_dpnt_cvg_strt_dt_rl in number,
541 p_dpnt_dsgn_no_ctfn_rqd_flag in varchar2,
542 p_drvbl_fctr_dpnt_elig_flag in varchar2,
543 p_drvbl_fctr_prtn_elig_flag in varchar2,
544 p_enrt_cvg_strt_dt_cd in varchar2,
545 p_enrt_cvg_strt_dt_rl in number,
546 p_enrt_info_rt_freq_cd in varchar2,
547 p_rt_strt_dt_cd in varchar2,
548 p_rt_strt_dt_rl in number,
549 p_rt_end_dt_cd in varchar2,
550 p_rt_end_dt_rl in number,
551 p_pgm_grp_cd in varchar2,
552 p_pgm_uom in varchar2,
553 p_drvbl_fctr_apls_rts_flag in varchar2,
554 p_alws_unrstrctd_enrt_flag in varchar2,
555 p_enrt_cd in varchar2,
556 p_enrt_mthd_cd in varchar2,
557 p_poe_lvl_cd in varchar2,
558 p_enrt_rl in number,
559 p_auto_enrt_mthd_rl in number,
560 p_trk_inelig_per_flag in varchar2,
561 p_business_group_id in number,
562 p_per_cvrd_cd in varchar2,
563 P_vrfy_fmly_mmbr_rl in number,
564 P_vrfy_fmly_mmbr_cd in varchar2,
565 p_short_name in varchar2, --FHR
566 p_short_code in varchar2, --FHR
567 p_legislation_code in varchar2,
568 p_legislation_subgroup in varchar2,
569 p_Dflt_pgm_flag in Varchar2,
570 p_Use_prog_points_flag in Varchar2,
571 p_Dflt_step_cd in Varchar2,
572 p_Dflt_step_rl in number,
573 p_Update_salary_cd in Varchar2,
574 p_Use_multi_pay_rates_flag in Varchar2,
575 p_dflt_element_type_id in number,
576 p_Dflt_input_value_id in number,
577 p_Use_scores_cd in Varchar2,
578 p_Scores_calc_mthd_cd in Varchar2,
579 p_Scores_calc_rl in number,
580 p_gsp_allow_override_flag in varchar2,
581 p_use_variable_rates_flag in varchar2,
582 p_salary_calc_mthd_cd in varchar2,
583 p_salary_calc_mthd_rl in number,
584 p_susp_if_dpnt_ssn_nt_prv_cd in varchar2,
585 p_susp_if_dpnt_dob_nt_prv_cd in varchar2,
586 p_susp_if_dpnt_adr_nt_prv_cd in varchar2,
587 p_susp_if_ctfn_not_dpnt_flag in varchar2,
588 p_dpnt_ctfn_determine_cd in varchar2,
589 p_pgm_attribute_category in varchar2,
590 p_pgm_attribute1 in varchar2,
591 p_pgm_attribute2 in varchar2,
592 p_pgm_attribute3 in varchar2,
593 p_pgm_attribute4 in varchar2,
594 p_pgm_attribute5 in varchar2,
595 p_pgm_attribute6 in varchar2,
596 p_pgm_attribute7 in varchar2,
597 p_pgm_attribute8 in varchar2,
598 p_pgm_attribute9 in varchar2,
599 p_pgm_attribute10 in varchar2,
600 p_pgm_attribute11 in varchar2,
601 p_pgm_attribute12 in varchar2,
602 p_pgm_attribute13 in varchar2,
603 p_pgm_attribute14 in varchar2,
604 p_pgm_attribute15 in varchar2,
605 p_pgm_attribute16 in varchar2,
606 p_pgm_attribute17 in varchar2,
607 p_pgm_attribute18 in varchar2,
608 p_pgm_attribute19 in varchar2,
609 p_pgm_attribute20 in varchar2,
610 p_pgm_attribute21 in varchar2,
611 p_pgm_attribute22 in varchar2,
612 p_pgm_attribute23 in varchar2,
613 p_pgm_attribute24 in varchar2,
614 p_pgm_attribute25 in varchar2,
615 p_pgm_attribute26 in varchar2,
616 p_pgm_attribute27 in varchar2,
617 p_pgm_attribute28 in varchar2,
618 p_pgm_attribute29 in varchar2,
619 p_pgm_attribute30 in varchar2,
620 p_all_inelig in varchar2,
621 p_object_version_number in number
622 )
623 Return g_rec_type;
624 --
625 end ben_pgm_shd;
[Home] [Help]