[Home] [Help]
PACKAGE: APPS.HXC_HAC_BUS
Source
1 Package hxc_hac_bus as
2 /* $Header: hxchacrhi.pkh 120.1 2006/06/08 15:17:53 gsirigin noship $ */
3 --
4 -- ---------------------------------------------------------------------------
5 -- |----------------------< set_security_group_id >--------------------------|
6 -- ---------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- Sets the security_group_id in CLIENT_INFO for the appropriate business
11 -- group context.
12 --
13 -- Prerequisites:
14 -- The primary key identified by p_approval_comp_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_approval_comp_id
19 --
20 --
21 -- Post Success:
22 -- The security_group_id will be set in CLIENT_INFO.
23 --
24 -- Post Failure:
25 -- An error is raised if the value does not exist.
26 --
27 -- Access Status:
28 -- Internal Development Use Only.
29 --
30 -- {End Of Comments}
31 -- ---------------------------------------------------------------------------
32 procedure set_security_group_id
33 (p_approval_comp_id in number
34 );
35 --
36 --
37 -- ---------------------------------------------------------------------------
38 -- |---------------------< return_legislation_code >-------------------------|
39 -- ---------------------------------------------------------------------------
40 -- {Start Of Comments}
41 --
42 -- Description:
43 -- Return the legislation code for a specific primary key value
44 --
45 -- Prerequisites:
46 -- The primary key identified by p_approval_comp_id
47 -- already exists.
48 --
49 -- In Arguments:
50 -- p_approval_comp_id
51 --
52 --
53 -- Post Success:
54 -- The business group's legislation code will be returned.
55 --
56 -- Post Failure:
57 -- An error is raised if the value does not exist.
58 --
59 -- Access Status:
60 -- Internal Development Use Only.
61 --
62 -- {End Of Comments}
63 -- ---------------------------------------------------------------------------
64 FUNCTION return_legislation_code
65 (p_approval_comp_id in number
66 ) RETURN varchar2;
67 --
68 --
69 -- ----------------------------------------------------------------------------
70 -- |---------------------------< insert_validate >----------------------------|
71 -- ----------------------------------------------------------------------------
72 -- {Start of comments}
73 --
74 -- Description:
75 -- This procedure controls the execution of all insert business rules
76 -- validation.
77 --
78 -- Prerequisites:
79 -- This private procedure is called from ins procedure.
80 --
81 -- In Parameters:
82 -- A Pl/Sql record structure.
83 --
84 -- Post Success:
85 -- Processing continues.
86 --
87 -- Post Failure:
88 -- If a business rules fails the error will not be handled by this procedure
89 -- unless explicity coded.
90 --
91 -- Developer Implementation Notes:
92 -- For insert, your business rules should be executed from this procedure and
93 -- should ideally (unless really necessary) just be straight procedure or
94 -- function calls. Try and avoid using conditional branching logic.
95 --
96 -- Access Status:
97 -- Internal Row Handler Use Only.
98 --
99 -- {End of comments}
100 -- ----------------------------------------------------------------------------
101 Procedure insert_validate
102 (p_effective_date in date
103 ,p_rec in hxc_hac_shd.g_rec_type
104 );
105 --
106 -- ----------------------------------------------------------------------------
107 -- |---------------------------< update_validate >----------------------------|
108 -- ----------------------------------------------------------------------------
109 -- {Start Of Comments}
110 --
111 -- Description:
112 -- This procedure controls the execution of all update business rules
113 -- validation.
114 --
115 -- Prerequisites:
116 -- This private procedure is called from upd procedure.
117 --
118 -- In Parameters:
119 -- A Pl/Sql record structure.
120 --
121 -- Post Success:
122 -- Processing continues.
123 --
124 -- Post Failure:
125 -- If a business rules fails the error will not be handled by this procedure
126 -- unless explicity coded.
127 --
128 -- Developer Implementation Notes:
129 -- For update, your business rules should be executed from this procedure and
130 -- should ideally (unless really necessary) just be straight procedure or
131 -- function calls. Try and avoid using conditional branching logic.
132 --
133 -- Access Status:
134 -- Internal Row Handler Use Only.
135 --
136 -- {End Of Comments}
137 -- ----------------------------------------------------------------------------
138 Procedure update_validate
139 (p_effective_date in date
140 ,p_rec in hxc_hac_shd.g_rec_type
141 );
142 --
143 -- ----------------------------------------------------------------------------
144 -- |-< chk_approval_comp_dates >----------------------------------------------|
145 -- ----------------------------------------------------------------------------
146 -- {Start Of Comments}
147 --
148 -- Description:
149 -- This procedure performs basic checks on the assignment dates to ensure
150 -- that they conform with the business rules.
151 -- At the moment the only business rule enforced in this procedure is that
152 -- the end date must be >= the start date and that the start date is not
153 -- null.
154 --
155 -- Prerequisites:
156 -- None.
157 --
158 -- In Parameters:
159 -- p_approval_comp_id
160 -- p_start_date
161 -- p_end_date
162 --
163 -- Post Success:
164 -- Processing continues.
165 --
166 -- Post Failure:
167 -- An exception is raised.
168 --
169 -- Developer Implementation Notes:
170 -- None.
171 --
172 -- Access Status:
173 -- Internal Row Handler Use Only.
174 --
175 -- {End Of Comments}
176 -- ----------------------------------------------------------------------------
177 --
178 PROCEDURE chk_approval_comp_dates
179 (p_approval_comp_id
180 IN hxc_approval_comps.approval_comp_id%TYPE
181 ,p_start_date
182 IN hxc_approval_comps.start_date%TYPE
183 ,p_end_date
184 IN hxc_approval_comps.end_date%TYPE
185 );
186 --
187 -- ----------------------------------------------------------------------------
188 -- |-< chk_invalid_dates_create >---------------------------------------------|
189 -- ----------------------------------------------------------------------------
190 -- {Start Of Comments}
191 --
192 -- Description:
193 -- This procedure is used to enforce the business rule that the start/end
194 -- dates of new records cannot overlap both the start and the end
195 -- dates of existing records.
196 --
197 -- Prerequisites:
198 -- None.
199 --
200 -- In Parameters:
201 -- p_approval_style_id
202 -- p_time_recipient_id
203 -- p_start_date
204 -- p_end_date
205 --
206 -- Post Success:
207 -- Processing continues.
208 --
209 -- Post Failure:
210 -- An exception is raised.
211 --
212 -- Developer Implementation Notes:
213 -- None.
214 --
215 -- Access Status:
216 -- Internal Row Handler Use Only.
217 --
218 -- {End Of Comments}
219 -- ----------------------------------------------------------------------------
220 --
221 PROCEDURE chk_invalid_dates_create
222 ( p_approval_style_id
223 IN hxc_approval_comps.approval_style_id%TYPE
224 ,p_time_recipient_id
225 IN hxc_approval_comps.time_recipient_id%TYPE
226 ,p_start_date
227 IN hxc_approval_comps.start_date%TYPE
228 ,p_end_date
229 IN hxc_approval_comps.end_date%TYPE
230 );
231 --
232 -- ----------------------------------------------------------------------------
233 -- |-< chk_invalid_dates_update >---------------------------------------------|
234 -- ----------------------------------------------------------------------------
235 -- {Start Of Comments}
236 --
237 -- Description:
238 -- This procedure is used to enforce the business rule that the start/end
239 -- dates of updated records cannot overlap both the start and the end
240 -- dates of existing records.
241 --
242 -- Prerequisites:
243 -- None.
244 --
245 -- In Parameters:
246 -- p_approval_comp_id
247 -- p_approval_style_id
248 -- p_time_recipient_id
249 -- p_start_date
250 -- p_end_date
251 --
252 -- Post Success:
253 -- Processing continues.
254 --
255 -- Post Failure:
256 -- An exception is raised.
257 --
258 -- Developer Implementation Notes:
259 -- None.
260 --
261 -- Access Status:
262 -- Internal Row Handler Use Only.
263 --
264 -- {End Of Comments}
265 -- ----------------------------------------------------------------------------
266 --
267 PROCEDURE chk_invalid_dates_update
268 ( p_approval_comp_id
269 IN hxc_approval_comps.approval_comp_id%TYPE
270 ,p_approval_style_id
271 IN hxc_approval_comps.approval_style_id%TYPE
272 ,p_time_recipient_id
273 IN hxc_approval_comps.time_recipient_id%TYPE
274 ,p_start_date
275 IN hxc_approval_comps.start_date%TYPE
276 ,p_end_date
277 IN hxc_approval_comps.end_date%TYPE
278 );
279
280 --
281 -- ----------------------------------------------------------------------------
282 -- |-< chk_overlapping_dates_create >-----------------------------------------|
283 -- ----------------------------------------------------------------------------
284 -- {Start Of Comments}
285 --
286 -- Description:
287 -- This procedure is used to enforce the business rule that dates of
288 -- records cannot overlap.
289 --
290 -- Prerequisites:
291 -- None.
292 --
293 -- In Parameters:
294 -- p_approval_style_id
295 -- p_time_recipient_id
296 -- p_start_date
297 -- p_end_date
298 --
299 -- Post Success:
300 -- Processing continues.
301 --
302 -- Post Failure:
303 -- An exception is raised.
304 --
305 -- Developer Implementation Notes:
306 -- None.
307 --
308 -- Access Status:
309 -- Internal Row Handler Use Only.
310 --
311 -- {End Of Comments}
312 -- ----------------------------------------------------------------------------
313 --
314 PROCEDURE chk_overlapping_dates_create
315 (p_approval_style_id
316 IN hxc_approval_comps.approval_style_id%TYPE
317 ,p_time_recipient_id
318 IN hxc_approval_comps.time_recipient_id%TYPE
319 ,p_start_date
320 IN hxc_approval_comps.start_date%TYPE
321 ,p_end_date
322 IN hxc_approval_comps.end_date%TYPE
323 );
324 --
325 -- ----------------------------------------------------------------------------
326 -- |-< chk_overlapping_dates_create >-----------------------------------------|
327 -- ----------------------------------------------------------------------------
328 -- {Start Of Comments}
329 --
330 -- Description:
331 -- This procedure is used to enforce the business rule that dates of
332 -- records cannot overlap.
333 --
334 -- Prerequisites:
335 -- None.
336 --
337 -- In Parameters:
338 -- p_approval_style_id
339 -- p_time_recipient_id
340 -- p_start_date
341 -- p_end_date
342 -- p_clashing_id
343 -- p_clashing_ovn
344 -- p_clashing_start_date
345 -- p_clashing_end_date
346 --
347 -- Post Success:
348 -- Processing continues.
349 --
350 -- Post Failure:
351 -- The id of the record which overlaps is returned.
352 --
353 -- Developer Implementation Notes:
354 -- None.
355 --
356 -- Access Status:
357 -- Internal Row Handler Use Only.
358 --
359 -- {End Of Comments}
360 -- ----------------------------------------------------------------------------
361 --
362 PROCEDURE chk_overlapping_dates_create
363 (p_approval_style_id
364 IN hxc_approval_comps.approval_style_id%TYPE
365 ,p_time_recipient_id
366 IN hxc_approval_comps.time_recipient_id%TYPE
367 ,p_start_date
368 IN hxc_approval_comps.start_date%TYPE
369 ,p_end_date
370 IN hxc_approval_comps.end_date%TYPE
371 ,p_clashing_id
372 OUT NOCOPY hxc_approval_comps.approval_style_id%TYPE
373 ,p_clashing_ovn
374 OUT NOCOPY hxc_approval_comps.object_version_number%TYPE
375 ,p_clashing_start_date
376 OUT NOCOPY hxc_approval_comps.start_date%TYPE
377 ,p_clashing_end_date
378 OUT NOCOPY hxc_approval_comps.end_date%TYPE
379 );
380 --
381 -- ----------------------------------------------------------------------------
382 -- |-< chk_overlapping_dates_update >-----------------------------------------|
383 -- ----------------------------------------------------------------------------
384 -- {Start Of Comments}
385 --
386 -- Description:
387 -- This procedure is used to enforce the business rule that dates of
388 -- records cannot overlap.
389 --
390 -- Prerequisites:
391 -- None.
392 --
393 -- In Parameters:
394 -- p_approval_comp_id
395 -- p_approval_style_id
396 -- p_time_recipient_id
397 -- p_start_date
398 -- p_end_date
399 --
400 -- Post Success:
401 -- Processing continues.
402 --
403 -- Post Failure:
404 -- An exception is raised.
405 --
406 -- Developer Implementation Notes:
407 -- None.
408 --
409 -- Access Status:
410 -- Internal Row Handler Use Only.
411 --
412 -- {End Of Comments}
413 -- ----------------------------------------------------------------------------
414 --
415 PROCEDURE chk_overlapping_dates_update
416 (p_approval_comp_id
417 IN hxc_approval_comps.approval_comp_id%TYPE
418 ,p_approval_style_id
419 IN hxc_approval_comps.approval_style_id%TYPE
420 ,p_time_recipient_id
421 IN hxc_approval_comps.time_recipient_id%TYPE
422 ,p_start_date
423 IN hxc_approval_comps.start_date%TYPE
424 ,p_end_date
425 IN hxc_approval_comps.end_date%TYPE
426 );
427 --
428 -- ----------------------------------------------------------------------------
429 -- |-< chk_overlapping_dates_update >-----------------------------------------|
430 -- ----------------------------------------------------------------------------
431 -- {Start Of Comments}
432 --
433 -- Description:
434 -- This procedure is used to enforce the business rule that dates of
435 -- records cannot overlap.
436 --
437 -- Prerequisites:
438 -- None.
439 --
440 -- In Parameters:
441 -- p_approval_comp_id
442 -- p_approval_style_id
443 -- p_time_recipient_id
444 -- p_start_date
445 -- p_end_date
446 -- p_clashing_id
447 -- p_clashing_ovn
448 -- p_clashing_start_date
449 -- p_clashing_end_date
450 --
451 -- Post Success:
452 -- Processing continues.
453 --
454 -- Post Failure:
458 -- None.
455 -- The id of the record which overlaps is returned.
456 --
457 -- Developer Implementation Notes:
459 --
460 -- Access Status:
461 -- Internal Row Handler Use Only.
462 --
463 -- {End Of Comments}
464 -- ----------------------------------------------------------------------------
465 --
466 PROCEDURE chk_overlapping_dates_update
467 (p_approval_comp_id
468 IN hxc_approval_comps.approval_comp_id%TYPE
469 ,p_approval_style_id
470 IN hxc_approval_comps.approval_style_id%TYPE
471 ,p_time_recipient_id
472 IN hxc_approval_comps.time_recipient_id%TYPE
473 ,p_start_date
474 IN hxc_approval_comps.start_date%TYPE
475 ,p_end_date
476 IN hxc_approval_comps.end_date%TYPE
477 ,p_clashing_id
478 OUT NOCOPY hxc_approval_comps.approval_style_id%TYPE
479 ,p_clashing_ovn
480 OUT NOCOPY hxc_approval_comps.object_version_number%TYPE
481 ,p_clashing_start_date
482 OUT NOCOPY hxc_approval_comps.start_date%TYPE
483 ,p_clashing_end_date
484 OUT NOCOPY hxc_approval_comps.end_date%TYPE
485 );
486 --
487 -- ----------------------------------------------------------------------------
488 -- |-< chk_master_detail_rel >-----------------------------------------|
489 -- ----------------------------------------------------------------------------
490 --
491 -- {Start Of Comments}
492 -- Description:
493 -- This procedure is used to enforce the business rule that if the
494 -- parent_comp_id and parent_comp_ovn are not null then a master record
495 -- must exist in the database.
496 --
497 -- Prerequisites:
498 -- None.
499 --
500 -- In Parameters:
501 -- p_parent_comp_id
502 -- p_parent_comp_ovn
503 --
504 -- Post Success:
505 -- Processing continues.
506 --
507 -- Post Failure:
508 -- An exception is raised.
509 --
510 -- Developer Implementation Notes:
511 -- None.
512 --
513 -- Access Status:
514 -- Internal Row Handler Use Only.
515 --
516 -- {End Of Comments}
517 -- ----------------------------------------------------------------------------
518 --
519 PROCEDURE chk_master_detail_rel
520 (
521 p_parent_comp_id IN hxc_approval_comps.parent_comp_id%TYPE
522 ,p_parent_comp_ovn IN hxc_approval_comps.parent_comp_ovn%TYPE
523 );
524 --
525 -- ----------------------------------------------------------------------------
526 -- |-< chk_parent_fields >-----------------------------------------|
527 -- ----------------------------------------------------------------------------
528 --
529 -- {Start Of Comments}
530 -- Description:
531 -- This procedure is used to enforce the business rule that if the
532 -- parent_comp_id is not null then parent comp ovn must also be
533 -- not null and vice versa.
534 --
535 -- Prerequisites:
536 -- None.
537 --
538 -- In Parameters:
539 -- p_parent_comp_id
540 -- p_parent_comp_ovn
541 --
542 -- Post Success:
543 -- Processing continues.
544 --
545 -- Post Failure:
546 -- An exception is raised.
547 --
548 -- Developer Implementation Notes:
549 -- None.
550 --
551 -- Access Status:
552 -- Internal Row Handler Use Only.
553 --
554 -- {End Of Comments}
555 -- ----------------------------------------------------------------------------
556 --
557 PROCEDURE chk_parent_fields
558 (
559 p_parent_comp_id IN hxc_approval_comps.parent_comp_id%TYPE
560 ,p_parent_comp_ovn IN hxc_approval_comps.parent_comp_ovn%TYPE);
561
562
563 --
564 -- ----------------------------------------------------------------------------
565 -- |-< chk_tim_cat >-----------------------------------------|
566 -- ----------------------------------------------------------------------------
567 --
568 -- {Start Of Comments}
569 -- Description:
570 -- This procedure is used to enforce the business rule that if the
571 -- parent_comp_id and parent_comp_ovn are not null then the
572 -- time category must be either 0 or belong to the list of
573 -- time categories in hxc_time_categories table.
574 -- The time_category_id field must be null if the parent_comp_id and
575 -- parent_comp_ovn are null.
576 --
577 -- Prerequisites:
578 -- None.
579 --
580 -- In Parameters:
581 -- p_parent_comp_id
582 -- p_parent_comp_ovn
583 -- p_time_category_id
584 --
585 -- Post Success:
586 -- Processing continues.
587 --
588 -- Post Failure:
589 -- An exception is raised.
590 --
591 -- Developer Implementation Notes:
592 -- None.
593 --
594 -- Access Status:
595 -- Internal Row Handler Use Only.
596 --
597 -- {End Of Comments}
598 -- ----------------------------------------------------------------------------
599 --
600 PROCEDURE chk_tim_cat
601 ( p_parent_comp_id IN hxc_approval_comps.parent_comp_id%TYPE
602 ,p_parent_comp_ovn IN hxc_approval_comps.parent_comp_ovn%TYPE
603 ,p_time_category_id IN hxc_approval_comps.time_category_id%TYPE );
604
605
606 -- ----------------------------------------------------------------------------
607 -- |-< chk_def_ela_rec_exists >-----------------------------------------|
608 -- ----------------------------------------------------------------------------
609 --
610 -- {Start Of Comments}
611 -- Description:
612 -- This procedure is used to enforce the business rule that
613 -- only one default ELA child record can exist for a parent.
614 --
615 -- Prerequisites:
616 -- None.
617 --
618 -- In Parameters:
619 -- p_approval_comp_id
620 -- p_time_category_id
621 -- p_parent_comp_id
622 -- p_parent_comp_ovn
623 --
624 -- Post Success:
625 -- Processing continues.
626 --
627 -- Post Failure:
628 -- An exception is raised.
629 --
630 -- Developer Implementation Notes:
631 -- None.
632 --
633 -- Access Status:
634 -- Internal Row Handler Use Only.
635 --
636 -- {End Of Comments}
637 -- ----------------------------------------------------------------------------
638 --
639 PROCEDURE chk_def_ela_rec_exists
640 (
641 p_approval_comp_id IN hxc_approval_comps.approval_comp_id%TYPE
642 ,p_time_category_id IN hxc_approval_comps.time_category_id%TYPE
643 ,p_parent_comp_id IN hxc_approval_comps.parent_comp_id%TYPE
644 ,p_parent_comp_ovn IN hxc_approval_comps.parent_comp_ovn%TYPE );
645
646 --
647 -- ----------------------------------------------------------------------------
648 -- |-< chk_tim_rcp >-----------------------------------------|
649 -- ----------------------------------------------------------------------------
650 --
651 -- {Start Of Comments}
652 -- Description:
653 -- This procedure is used to enforce the business rule that if the
654 -- parent_comp_id and parent_comp_ovn are not null then the
655 -- time recipient must be -1
656 -- The time_category_id field must belong to the list of time recipients
657 -- in the hxc_time_recipients table if the parent_comp_id and
658 -- parent_comp_ovn are not null
659 --
660 -- Prerequisites:
661 -- None.
662 --
663 -- In Parameters:
664 -- p_parent_comp_id
665 -- p_parent_comp_ovn
666 -- p_time_recipient_id
667 --
668 -- Post Success:
669 -- Processing continues.
670 --
671 -- Post Failure:
672 -- An exception is raised.
673 --
674 -- Developer Implementation Notes:
675 -- None.
676 --
677 -- Access Status:
678 -- Internal Row Handler Use Only.
679 --
680 -- {End Of Comments}
681 -- ----------------------------------------------------------------------------
682 --
683 PROCEDURE chk_tim_rcp
684 ( p_parent_comp_id IN hxc_approval_comps.parent_comp_id%TYPE
685 ,p_parent_comp_ovn IN hxc_approval_comps.parent_comp_ovn%TYPE
686 ,p_time_recipient_id IN hxc_approval_comps.time_recipient_id%TYPE );
687
688 --
689 -- ----------------------------------------------------------------------------
690 -- |-< chk_tim_cat_dup >-----------------------------------------|
691 -- ----------------------------------------------------------------------------
692 --
693 -- {Start Of Comments}
694 -- Description:
695 -- This procedure is used to enforce the business rule that
696 -- for a time category and a sequence only 1 row can exist.
697 -- Also for a time category the approval mechanisms must be
698 -- different but if they are same then the mechanism ids must be
699 -- different.
700 -- Prerequisites:
701 -- None.
702 --
703 -- In Parameters:
704 -- p_approval_comp_id
705 -- p_time_category_id
706 -- p_parent_comp_id
707 -- p_parent_comp_ovn
708 -- p_approval_mechanism
709 -- p_approval_mechanism_id
710 -- p_wf_name
711 -- p_wf_item_type
712 --
713 -- Post Success:
714 -- Processing continues.
715 --
716 -- Post Failure:
717 -- An exception is raised.
718 --
719 -- Developer Implementation Notes:
720 -- None.
721 --
722 -- Access Status:
723 -- Internal Row Handler Use Only.
724 --
725 -- {End Of Comments}
726 -- ----------------------------------------------------------------------------
727 --
728 PROCEDURE chk_tim_cat_dup
729 (
730 p_approval_comp_id IN hxc_approval_comps.approval_comp_id%TYPE
731 ,p_time_category_id IN hxc_approval_comps.time_category_id%TYPE
732 ,p_approval_order IN hxc_approval_comps.approval_order%TYPE
733 ,p_parent_comp_id IN hxc_approval_comps.parent_comp_id%TYPE
734 ,p_parent_comp_ovn IN hxc_approval_comps.parent_comp_ovn%TYPE
735 ,p_approval_mechanism IN hxc_approval_comps.approval_mechanism%TYPE
736 ,p_approval_mechanism_id IN hxc_approval_comps.approval_mechanism_id%TYPE
737 ,p_wf_name IN hxc_approval_comps.wf_name%TYPE
738 ,p_wf_item_type IN hxc_approval_comps.wf_item_type%TYPE);
739
740 --
741 --
742 -- ----------------------------------------------------------------------------
743 -- |-< chk_app_mech_for_child >-----------------------------------------|
744 -- ----------------------------------------------------------------------------
745 --
746 -- {Start Of Comments}
747 -- Description:
748 -- This procedure is used to enforce the business rule that
749 -- a child row cannot have the approval mechanism as
750 -- ENTRY_LEVEL_APPROVAL. Also if the child row is the default
751 -- row, then the approval mechanism cant be PROJECT_MANAGER.
752 --
753 -- Prerequisites:
754 -- None.
755 --
756 -- In Parameters:
757 -- p_time_category_id
758 -- p_approval_mechanism
759 -- p_parent_comp_id
760 -- p_parent_comp_ovn
761 --
762 -- Post Success:
763 -- Processing continues.
764 --
765 -- Post Failure:
766 -- An exception is raised.
767 --
768 -- Developer Implementation Notes:
769 -- None.
770 --
771 -- Access Status:
772 -- Internal Row Handler Use Only.
773 --
774 -- {End Of Comments}
778 (
775 -- ----------------------------------------------------------------------------
776 --
777 PROCEDURE chk_app_mech_for_child
779 p_time_category_id IN hxc_approval_comps.time_category_id%TYPE
780 ,p_approval_mechanism IN hxc_approval_comps.approval_mechanism%TYPE
781 ,p_parent_comp_id IN hxc_approval_comps.parent_comp_id%TYPE
782 ,p_parent_comp_ovn IN hxc_approval_comps.parent_comp_ovn%TYPE
783 );
784
785 --
786 -- ----------------------------------------------------------------------------
787 -- |---------< chk_allowable_extensions >-------------------------------------|
788 -- ----------------------------------------------------------------------------
789 --
790 -- {Start Of Comments}
791 -- Description:
792 -- Procedure to check allowable values for run_recipient_extensions.
793 --
794 -- Prerequisites:
795 -- None.
796 --
797 -- In Parameters:
798 -- p_run_recipient_extensions
799 -- p_approval_style_id
800 --
801 -- Post Success:
802 -- Processing continues.
803 --
804 -- Post Failure:
805 -- An exception is raised.
806 --
807 -- Developer Implementation Notes:
808 -- None.
809 --
810 -- Access Status:
811 -- Internal Row Handler Use Only.
812 --
813 -- {End Of Comments}
814 -- ----------------------------------------------------------------------------
815 --
816
817 Procedure chk_allowable_extensions
818 (
819 p_run_recipient_extensions in hxc_approval_comps.run_recipient_extensions%type
820 ,p_approval_style_id in hxc_approval_comps.approval_style_id%type
821 );
822
823 --
824 -- ----------------------------------------------------------------------------
825 -- |---------------------------< delete_validate >----------------------------|
826 -- ----------------------------------------------------------------------------
827 -- {Start Of Comments}
828 --
829 -- Description:
830 -- This procedure controls the execution of all delete business rules
831 -- validation.
832 --
833 -- Prerequisites:
834 -- This private procedure is called from del procedure.
835 --
836 -- In Parameters:
837 -- A Pl/Sql record structure.
838 --
839 -- Post Success:
840 -- Processing continues.
841 --
842 -- Post Failure:
843 -- If a business rules fails the error will not be handled by this procedure
844 -- unless explicity coded.
845 --
846 -- Developer Implementation Notes:
847 -- For delete, your business rules should be executed from this procedure and
848 -- should ideally (unless really necessary) just be straight procedure or
849 -- function calls. Try and avoid using conditional branching logic.
850 --
851 -- Access Status:
852 -- Internal Row Handler Use Only.
853 --
854 --
855 -- ----------------------------------------------------------------------------
856 Procedure delete_validate
857 (p_rec in hxc_hac_shd.g_rec_type
858 );
859 --
860 end hxc_hac_bus;