1 Package per_pea_bus as
2 /* $Header: pepearhi.pkh 120.0.12010000.2 2008/08/06 09:21:03 ubhat ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 -- The following two global variables are only to be
9 -- used by the return_legislation_code function.
10 --
11 g_legislation_code varchar2(150) default null;
12 g_person_analysis_id number default null;
13 --
14 Procedure chk_person_id
15 (p_person_id in per_person_analyses.person_id%TYPE
16 ,p_business_group_id in per_person_analyses.business_group_id%TYPE
17 ,p_effective_date in date
18 );
19 --
20 -- For web special information types module.
21 -- Require call to chk_date_from_to, add into header.
22 --
23 procedure chk_date_from_to
24 (p_person_analysis_id in number default null
25 ,p_date_from in date
26 ,p_date_to in date
27 ,p_object_version_number in number default null);
28 --
29 -- ----------------------------------------------------------------------------
30 -- |---------------------------< insert_validate >----------------------------|
31 -- ----------------------------------------------------------------------------
32 -- {Start Of Comments}
33 --
34 -- Description:
35 -- This procedure controls the execution of all insert business rules
36 -- validation.
37 --
38 -- Pre Conditions:
39 -- This private procedure is called from ins procedure.
40 --
41 -- In Parameters:
42 -- A Pl/Sql record structre.
43 --
44 -- Post Success:
45 -- Processing continues.
46 --
47 -- Post Failure:
48 -- If a business rules fails the error will not be handled by this procedure
49 -- unless explicity coded.
50 --
51 -- Developer Implementation Notes:
52 -- For insert, your business rules should be executed from this procedure and
53 -- should ideally (unless really necessary) just be straight procedure or
54 -- function calls. Try and avoid using conditional branching logic.
55 --
56 -- Access Status:
57 -- Internal Table Handler Use Only.
58 --
59 -- {End Of Comments}
60 -- ----------------------------------------------------------------------------
61 Procedure insert_validate
62 (p_rec in per_pea_shd.g_rec_type,
63 p_effective_date in date);
64 --
65 -- ----------------------------------------------------------------------------
66 -- |---------------------------< update_validate >----------------------------|
67 -- ----------------------------------------------------------------------------
68 -- {Start Of Comments}
69 --
70 -- Description:
71 -- This procedure controls the execution of all update business rules
72 -- validation.
73 --
74 -- Pre Conditions:
75 -- This private procedure is called from upd procedure.
76 --
77 -- In Parameters:
78 -- A Pl/Sql record structre.
79 --
80 -- Post Success:
81 -- Processing continues.
82 --
83 -- Post Failure:
84 -- If a business rules fails the error will not be handled by this procedure
85 -- unless explicity coded.
86 --
87 -- Developer Implementation Notes:
88 -- For update, your business rules should be executed from this procedure and
89 -- should ideally (unless really necessary) just be straight procedure or
90 -- function calls. Try and avoid using conditional branching logic.
91 --
92 -- Access Status:
93 -- Internal Table Handler Use Only.
94 --
95 -- {End Of Comments}
96 -- ----------------------------------------------------------------------------
97 Procedure update_validate
98 (p_rec in per_pea_shd.g_rec_type);
99 --
100 -- ----------------------------------------------------------------------------
101 -- |---------------------------< delete_validate >----------------------------|
102 -- ----------------------------------------------------------------------------
103 -- {Start Of Comments}
104 --
105 -- Description:
106 -- This procedure controls the execution of all delete business rules
107 -- validation.
108 --
109 -- Pre Conditions:
110 -- This private procedure is called from del procedure.
111 --
112 -- In Parameters:
113 -- A Pl/Sql record structre.
114 --
115 -- Post Success:
116 -- Processing continues.
117 --
118 -- Post Failure:
119 -- If a business rules fails the error will not be handled by this procedure
120 -- unless explicity coded.
121 --
122 -- Developer Implementation Notes:
123 -- For delete, your business rules should be executed from this procedure and
124 -- should ideally (unless really necessary) just be straight procedure or
125 -- function calls. Try and avoid using conditional branching logic.
126 --
127 -- Access Status:
128 -- Internal Table Handler Use Only.
129 --
130 -- {End Of Comments}
131 -- ----------------------------------------------------------------------------
132 Procedure delete_validate(p_rec in per_pea_shd.g_rec_type);
133 --
134 -- ----------------------------------------------------------------------------
135 -- |-----------------------< return_legislation_code >-------------------------|
136 -- ----------------------------------------------------------------------------
137 -- {Start Of Comments}
138 --
139 -- Description:
140 -- This function gets the legislation code
141 --
142 -- Pre Conditions:
143 -- This private procedure will be called from the user hook procedures.
144 --
145 -- In Parameters:
146 -- the primary key of the table (per_person_analyses)
147 --
148 -- Post Success:
149 -- Processing continues.
150 --
151 -- Post Failure:
152 -- If the legislation code is not found then it errors out
153 --
154 -- Developer Implementation Notes:
155 --
156 -- Access Status:
157 -- Internal Table Handler Use Only.
158 --
159 -- {End Of Comments}
160 -- ----------------------------------------------------------------------------
161 --
162 function return_legislation_code
163 (p_person_analysis_id in per_person_analyses.person_analysis_id%TYPE
164 ) return varchar2;
165 --
166 end per_pea_bus;
[Home] [Help]