1 Package pqh_rei_bus AUTHID CURRENT_USER as
2 /* $Header: pqreirhi.pkh 120.0 2005/05/29 02:27:10 appldev 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_role_extra_info_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_role_extra_info_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_role_extra_info_id in number
34 ,p_associated_column1 in varchar2 default null
35 );
36 --
37 --
38 -- ---------------------------------------------------------------------------
39 -- |---------------------< return_legislation_code >-------------------------|
40 -- ---------------------------------------------------------------------------
41 -- {Start Of Comments}
42 --
43 -- Description:
44 -- Return the legislation code for a specific primary key value
45 --
46 -- Prerequisites:
47 -- The primary key identified by p_role_extra_info_id
48 -- already exists.
49 --
50 -- In Arguments:
51 -- p_role_extra_info_id
52 --
53 --
54 -- Post Success:
55 -- The business group's legislation code will be returned.
56 --
57 -- Post Failure:
58 -- An error is raised if the value does not exist.
59 --
60 -- Access Status:
61 -- Internal Development Use Only.
62 --
63 -- {End Of Comments}
64 -- ---------------------------------------------------------------------------
65 FUNCTION return_legislation_code
66 (p_role_extra_info_id in number
67 ) RETURN varchar2;
68 --
69 --
70 -- ----------------------------------------------------------------------------
71 -- |--------------------------<chk_role_info_type >-----------------------|
72 -- ----------------------------------------------------------------------------
73 -- {Start Of Comments}
74 --
75 -- Description:
76 -- Validates that the role information type exists in table
77 -- pqh_role_info_types where active_inactive_flag is 'Y'.
78 --
79 -- Pre Conditions:
80 -- Data must be existed in table pqh_role_info_types.
81 --
82 -- In Parameters:
83 -- p_information_type
84 --
85 -- Post Success:
86 -- Processing continues.
87 --
88 -- Post Failure:
89 -- An application error will be raised and processing is terminated.
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 Table Handler Use Only.
98 --
99 -- {End Of Comments}
100 -- ----------------------------------------------------------------------------
101 Procedure chk_role_info_type
102 (
103 p_information_type in pqh_role_info_types.information_type%type
104 );
105
106 -- ----------------------------------------------------------------------------
107 -- |---------------------------< chk_role_id >----------------------------|
108 -- ----------------------------------------------------------------------------
109 -- {Start Of Comments}
110 --
111 -- Description:
112 -- Verify that the value in role_ID is in the pqh_roles table.
113 --
114 -- Pre Conditions:
115 --
116 --
117 -- In Parameters:
118 -- p_role_id
119 --
120 -- Post Success:
121 -- Processing continues.
122 --
123 -- Post Failure:
124 -- An application error will be raised and processing is terminated.
125 --
126 -- Developer Implementation Notes:
127 -- For insert, your business rules should be executed from this procedure and
128 -- should ideally (unless really necessary) just be straight procedure or
129 -- function calls. Try and avoid using conditional branching logic.
130 --
131 -- Access Status:
132 -- Internal Table Handler Use Only.
133 --
134 -- {End Of Comments}
135 -- ----------------------------------------------------------------------------
136 Procedure chk_role_id
137 (
138 p_role_id in pqh_role_extra_info.role_id%type
139 );
140 --
141 -- ----------------------------------------------------------------------------
142 -- |--------------------< chk_multiple_occurences_flag >----------------------|
143 -- ----------------------------------------------------------------------------
144 -- {Start Of Comments}
145 --
146 -- Description:
147 -- Verify that the number of rows should not exceed one when
148 -- multiple_occurences_flag = 'N'.
149 --
150 -- Pre Conditions:
151 -- This procedure should execute after procedure chk_information_type.
152 --
153 -- In Parameters:
154 -- p_information_type
155 -- p_role_id
156 --
157 -- Post Success:
158 -- Processing continues.
159 --
160 -- Post Failure:
161 -- An application error will be raised and processing is terminated.
162 --
163 -- Developer Implementation Notes:
164 -- For insert, your business rules should be executed from this procedure and
165 -- should ideally (unless really necessary) just be straight procedure or
166 -- function calls. Try and avoid using conditional branching logic.
167 --
168 -- Access Status:
169 -- Internal Table Handler Use Only.
170 --
171 -- {End Of Comments}
172 -- ----------------------------------------------------------------------------
173 Procedure chk_multiple_occurences_flag
174 (p_information_type in pqh_role_extra_info.information_type%type
175 ,p_role_id in pqh_role_extra_info.role_id%type
176 );
177 --
178 -- ----------------------------------------------------------------------------
179 -- |-----------------------< chk_non_updateable_args >------------------------|
180 -- ----------------------------------------------------------------------------
181 -- {Start Of Comments}
182 --
183 -- Description:
184 -- Verify that the non updateable arguments not changed.
185 --
186 -- Pre Conditions:
187 --
188 --
189 -- In Parameters:
190 -- p_rec
191 --
192 -- Post Success:
193 -- Processing continues.
194 --
195 -- Post Failure:
196 -- An application error will be raised and processing is terminated.
197 --
198 -- Developer Implementation Notes:
199 -- For insert, your business rules should be executed from this procedure and
200 -- should ideally (unless really necessary) just be straight procedure or
201 -- function calls. Try and avoid using conditional branching logic.
202 --
203 -- Access Status:
204 -- Internal Table Handler Use Only.
205 --
206 -- {End Of Comments}
207 -- ----------------------------------------------------------------------------
208 Procedure chk_non_updateable_args (p_rec in pqh_rei_shd.g_rec_type);
209 --
210 -- ----------------------------------------------------------------------------
211 -- |---------------------------< insert_validate >----------------------------|
212 -- ----------------------------------------------------------------------------
213 -- {Start of comments}
214 --
215 -- Description:
216 -- This procedure controls the execution of all insert business rules
217 -- validation.
218 --
219 -- Prerequisites:
220 -- This private procedure is called from ins procedure.
221 --
222 -- In Parameters:
223 -- A Pl/Sql record structure.
224 --
225 -- Post Success:
226 -- Processing continues.
227 --
228 -- Post Failure:
229 -- If a business rules fails the error will not be handled by this procedure
230 -- unless explicity coded.
231 --
232 -- Developer Implementation Notes:
233 -- For insert, your business rules should be executed from this procedure
234 -- and should ideally (unless really necessary) just be straight procedure
235 -- or function calls. Try and avoid using conditional branching logic.
236 --
237 -- Access Status:
238 -- Internal Row Handler Use Only.
239 --
240 -- {End of comments}
241 -- ----------------------------------------------------------------------------
242 Procedure insert_validate
243 (p_rec in pqh_rei_shd.g_rec_type
244 );
245 --
246 -- ----------------------------------------------------------------------------
247 -- |---------------------------< update_validate >----------------------------|
248 -- ----------------------------------------------------------------------------
249 -- {Start Of Comments}
250 --
251 -- Description:
252 -- This procedure controls the execution of all update business rules
253 -- validation.
254 --
255 -- Prerequisites:
256 -- This private procedure is called from upd procedure.
257 --
258 -- In Parameters:
259 -- A Pl/Sql record structure.
260 --
261 -- Post Success:
262 -- Processing continues.
263 --
264 -- Post Failure:
265 -- If a business rules fails the error will not be handled by this procedure
266 -- unless explicity coded.
267 --
268 -- Access Status:
269 -- Internal Row Handler Use Only.
270 --
271 -- {End Of Comments}
272 -- ----------------------------------------------------------------------------
273 Procedure update_validate
274 (p_rec in pqh_rei_shd.g_rec_type
275 );
276 --
277 -- ----------------------------------------------------------------------------
278 -- |---------------------------< delete_validate >----------------------------|
279 -- ----------------------------------------------------------------------------
280 -- {Start Of Comments}
281 --
282 -- Description:
283 -- This procedure controls the execution of all delete business rules
284 -- validation.
285 --
286 -- Prerequisites:
287 -- This private procedure is called from del procedure.
288 --
289 -- In Parameters:
290 -- A Pl/Sql record structure.
291 --
292 -- Post Success:
293 -- Processing continues.
294 --
295 -- Post Failure:
296 -- If a business rules fails the error will not be handled by this procedure
297 -- unless explicity coded.
298 --
299 -- Developer Implementation Notes:
300 -- For delete, your business rules should be executed from this procedure
301 -- and should ideally (unless really necessary) just be straight procedure
302 -- or function calls. Try and avoid using conditional branching logic.
303 --
304 -- Access Status:
305 -- Internal Row Handler Use Only.
306 --
307 -- {End Of Comments}
308 -- ----------------------------------------------------------------------------
309 Procedure delete_validate
310 (p_rec in pqh_rei_shd.g_rec_type
311 );
312 --
313 end pqh_rei_bus;
[Home] [Help]