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