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